Remove circular dependency from debugging code

This circular dependency is giving me problems with browserify, see
substack/node-browserify#1068.
Move the debug property from request to request.Request, and
define a property at the old location to pass through to the new
location for backwards compatibility.

Review @simov @seanstrom @FredKSchott ?

Looks good, though are we forced to have the debug module inlined into request.js ?

I was having trouble thinking of a clean way to pass the needed flag.  I guess something like this would work though:
lib/debug.js
module.exports = function(Request) {
  Request.debug = // do process.env check
  return function debug(msg) {
    if (Request.debug) {
      // do stuff
    }
  }
}

and in request.js
var debug = require('./lib/debug')(Request)

Do you think this is better than just having it inlined?

Ehm, It's probably better to have it inline. Now that I see the alternative.

+1 lgtm (with 1 small comment)

Yeah that's one of the reasons I wanted some review on this.  It's here because the linter complains about use of Request before it's defined otherwise, and moving it to the bottom makes it complain about the same thing with debug.

@FredKSchott I guess I could put var debug at the top, then debug = function()... at the bottom, would that be better?

Ah yea, I see that now. In that case I'm fine with what you have written, it makes sense given the layout. Although it also means our constructor could never call debug, which is a shame.
Not sure if defining var debug at the top buys us much, that would confuse me even more :)
The only other solution I can think of would be to define some var isDebugEnabled to hold the flag instead, and then expose some Request.getDebug/setDebug methods for index.js to hook into that check that flag. But... that's not too much cleaner.

Agreed, and I'd rather avoid adding more machinery here.  Somebody besides me want to merge this?
Minor issues in the scheme of things, but I've been reminded of this article a lot lately:  http://stilldrinking.org/programming-sucks

Haha yea, but I'm glad these are our problems now, vs "what the hell is this code doing please halp"
Also fwiw, you can always enable/disable eslint rules within certain code blocks:
/*eslint-disable no-alert, no-console */

alert('foo');
console.log('bar');

/*eslint-enable no-alert */

thanks @seanstrom for the separation of duties


*: update and fix clippy happy.

@ngaut @BusyJay @disksing

LGTM

Coverage increased (+0.1%) to 81.707% when pulling 210979921cf8148a03af296e64ad7332fd8d2a98 on siddontang/update into ea32cc6525ed02eb4706282d60031877ba4b04aa on master.

LGTM

Coverage increased (+0.2%) to 81.756% when pulling cdc9bdfa2ea1ecf88487522bda2d695f63d2417e on siddontang/update into ea32cc6525ed02eb4706282d60031877ba4b04aa on master.


Auto column sizing

Goal
Currently the Glide Data Grid requires you to submit a width for every column. This is convenient for us because there is no real difficulty in figuring out what they should be, the user tells us. However it means we are just pushing that work off to the user. To make things better we can instead detect a "good" width and let the end user adjust from there.
API Changes
export interface GridColumn {
    readonly width?: number;
    readonly title: string;
    readonly group?: string;
    readonly icon?: GridColumnIcon | string;
    readonly overlayIcon?: GridColumnIcon | string;
    readonly hasMenu?: boolean;
    readonly style?: "normal" | "highlight";
    readonly themeOverride?: Partial<Theme>;
    readonly trailingRowOptions?: {
        readonly hint?: string;
        readonly addIcon?: string;
    };
}

Basically width is to become optional.
Implementation details
Width detection is to be based off of a variety of factors.

getCellsForSelection must be implemented or all widths will be calculated from the first row only, and only once they are displayed.
If getCellsForSelection is defined, the first 10 rows are to be fetched and evaluated for each cell type and content. The correct cell renderers will then be created and queries.
Each cell renderer will be able to optionally implement a getOptimalWidth call which will return back a desired width for that cell.
The final column width will be no more than 500px unless room is left over without horizontally scrolling
The final column size will be no less than 35px
The final column size will be equivalent to the largest result from from the 10 measured cells after throwing away any cells whose total width is more than twice the average width of all 10 cells. This is to prevent one cell containing the completed worse of shakespear from throwing an otherwise small column all out of whack.

Issues
This is not strictly speaking backwards compatible. It means that a library written against the current API may be relying on width always being set. That said I think the risk of people experiencing this kind of issue are minimal and the gains are worth the slight break. Most people will not experience this break, if any, as they are the creators of their columns and all existing valid columns have a defined width. In short will the API breaks, nobody will experience a breaking change.
Version bump requirement

Minor version bump

Fixed in 3.4.0


CongitoUserPool does not update successfully on deploy (Regression)

This error is back on deploys with a cognito user pool.  It was previous reported here: https://github.com/sst/ion/issues/617 and a fix in a dependency resolved it for a while.  However, it is now back on version 3.1.12 of sst.
It may be worth exposing the ignoreChanges pulumi option which will allow a work around to be put in place.

Can u give this a try:
const pool = new sst.aws.CognitoUserPool("MyPool", {
  transform: {
    userPool: (args, opts) => {
      opts.ignoreChanges = ["schemas"];
    }
  }
});

btw, Is it an upstream Pulumi/Terraform issue? If so, could u link to the GH issue?

Yes, that works, thanks! I believe it is an upstream issue.


Add human readable IAQ scores

From table 4, page 9 of the BME680 datasheet, I've added in the AQ classification (good, average, etc), tidied up the formatting of the output and made a couple of extremely trivial pylint fixups. My coding skills are still pretty basic and there is probably a much more efficient way to do this, so feel free to reject this if it's unsuitable.

Never mind. I took the air quality reading to be a reflection of the IAQ scale in the datasheet rather than  a percentage. As an aside, is it worth adding a percent symbol after the air quality output, and maybe something to indicate if a low or high percentage is good?


[BUG] Can't preview accent on dressing room url

When trying to preview my accent SpiritOfKalang, I can't seem to get a preview on this dressing room link:
https://www1.flightrising.com/dgen/dressing-room/dragon?did=72163803&skin=0&apparel=29582,21832,33816,9452,35549,35536,44227&xt=dressing.png
I used this existing dragon:
https://www1.flightrising.com/dragon/72163803
With this outfit:
https://www1.flightrising.com/dressing/outfit/1909230
The resulting screen just shows the base dragon without the outfit applied.

@JavaMeana This is due to caching, one of my many pains to keep traffic to FR as low as possible. If you look on the preview result page there is a blue alert under the images that says it is a cached version. At the end there is a clickable link that will clear the cache and it will then re-generate the preview with the new info.

In this case what happened was you previewed it on a real dragon which had something equipped, so I generated both the dragon and apparel previews. Then when you used the dressing room preview I checked to see if there were already cached images for that dragon and both the base dragon and apparel image existed, thus returning them right away without doing any further processing.
To prevent having dozens of images saved for each dragon whenever someone changes their apparel, I opted to put the burden of clearing the cache to the user by letting them forcibly regenerate the image.

I see! How odd, I pressed the link in the blue window but just got the same
result back, could it be an issue on my end? No matter how many times I
clicked the reload, I just got the same images BUT when I tried previewing
later on, it did work normally again. What I did differently however is at
first I was previewing with the link from my manage skins and the second
time I used the link through normal skin browsing but I doubt that would
have caused the issue.
On Sun, 10 Apr 2022, 17:24 Perry van Velzen, @.***>
wrote:

@JavaMeana https://github.com/JavaMeana This is due to caching, one of
my many pains to keep traffic to FR as low as possible. If you look on the
preview result page there is a blue alert under the images that says it is
a cached version. At the end there is a clickable link that will clear the
cache and it will then re-generate the preview with the new info.
[image: image]
https://user-images.githubusercontent.com/672037/162626757-8fdf2b8f-0453-44c8-b23e-c73a65aebf81.png
[image: image]
https://user-images.githubusercontent.com/672037/162626784-970529fe-4362-4bd3-be8c-c107f5dbc553.png
In this case what happened was you previewed it on a real dragon which had
something equipped, so I generated both the dragon and apparel previews.
Then when you used the dressing room preview I checked to see if there were
already cached images for that dragon and both the base dragon and apparel
image existed, thus returning them right away without doing any further
processing.
To prevent having dozens of images saved for each dragon whenever someone
changes their apparel, I opted to put the burden of clearing the cache to
the user by letting them forcibly regenerate the image.
—
Reply to this email directly, view it on GitHub
https://github.com/Nensec/FRTools/issues/23#issuecomment-1094296625, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AV36TTRWP64JTE55CXS35Q3VELXCDANCNFSM5TA6ITOQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

They should result in the same link anyway. I am guessing your browser is caching the images (which it should). I don't know if I can force a browser to download the new images and cache those instead of the original ones. Normally speaking a browser won't even attempt to get a newer version if it is already cached, so I don't have much control over it : /

No worries at all! I now know where the issue lies so I can know what to do
in the future ty! Have a great rest of your day!
On Sun, 10 Apr 2022, 22:56 Perry van Velzen, @.***>
wrote:

They should result in the same link anyway. I am guessing your browser is
caching the images (which it should). I don't know if I can force a browser
to download the new images and cache those instead of the original ones.
Normally speaking a browser won't even attempt to get a newer version if it
is already cached, so I don't have much control over it : /
—
Reply to this email directly, view it on GitHub
https://github.com/Nensec/FRTools/issues/23#issuecomment-1094367665, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AV36TTWT35XYQRCYPXE34NTVEM56LANCNFSM5TA6ITOQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Predicate return type is lost when the predicate is passed as a parameter.

🔎 Search Terms
predicate return type passed parameter
🕗 Version & Regression Information
Latest to date.
⏯ Playground Link
https://www.typescriptlang.org/play/?target=99&jsx=0#code/JYOwLgpgTgZghgYwgAgGIHt0EZkG8CwAUAJAyYBcyAzmFKAOYDcRxV6AthGABYMD6EADZUIlAK4gA1iHQB3EM0IBfIkVCRYiFBnQAmPCzLpKIMewBG0RcTgye0PjwbipM+YpWE14aPCTIAITgoAxJzYJdpOQUiT1VCABMIBEFglAR0EBpkYKhKAAodHAAfNEx9UqCoAEoAbQBdRSIklLTkGAkEMGBM5G44Kj4jAB4AFQA+fLBKUerKMGRgKmRR5AgAD0gQBOXcdopkCSj5ZCVkAH4V5BMIADcreKIMrIWoHABeHKgoADoYUAS+X6gyM1QAhIxkAB6KFlbDIUo6fSAHg3AJH7j0IHRAXR6IGQCXQQwBwwACmtNhBtst8nxKLYAJ7VZDvcbIcyYQQQWyTAAOUAgCWACDgkEoJKZBBI-LAYigeNyfwB+T5AqFIog1Q88We2Sg+k+BKJ2yBAyGmHBkJhcJKcIqgWCyEAMuREIA
💻 Code
declare const arr: (Foo1 | Foo2 | Bar)[];

declare function has_foo<T>(t: T): t is T extends { foo: unknown } ? T : never;

const r1 = arr.find(has_foo)!; // Foo1 | Foo2 🎉

function do_find<P extends (_: any) => boolean>(predicate: P) {
	return arr.find(predicate); // same line as in r1
}

const r2 = do_find(has_foo)!; // Foo1 | Foo2 | Bar ❌

Definitions of Foo1, Foo2 and Bar in the playground to reduce clutter.
🙁 Actual behavior
Predicate type narrowing lost.
🙂 Expected behavior
Predicate type narrowing preserved.
Additional information about the issue
Is it only because the predicate is passed as a parameter or is it something else 🤔

function do_find<P extends (_: any) => boolean>(predicate: P) {
  return arr.find(predicate); // same line as in r1
}

It's not the same. P is not defined as a predicate here, so a different find overload is resolved, which does not use predicates and does not narrow types.
// For reference
interface Array<T> {
  find<S extends T>(predicate: (value: T, index: number, obj: T[]) => value is S, thisArg?: any): S | undefined;
  find(predicate: (value: T, index: number, obj: T[]) => unknown, thisArg?: any): T | undefined;
}

You need something like this to pass generic predicates:
function do_find<R extends typeof arr[number]>(predicate: (t: typeof arr[number]) => t is R) {
  return arr.find(predicate);
}

A predicate function type is not the same as a function returning a boolean. You need to mimic what the find itself is doing with its overloads to make it work: TS playground

I had done
function do_find<P extends (_: any) => _ is any>(predicate: P)

to make it clear that P IS a predicate, and the result is even worse.

@bgenia I also had tried something similar to your solution but it didn't work.
function do_find<T, R extends T>(predicate: (t: T) => t is R) {
  return arr.find(predicate); // error
}

The do_find function is not supposed to know about the typeof arr[number], so that one is not practical.

Your arr isn't represented in the parameters list so there is no way for TS to infer that type from anywhere here. do_find<Whatever1, Whatever2>(somePredicateForWhatever) is a valid invocation and you want the return arr.find(predicate); to error here because of that

@Andarist You provided the same solution, El = (typeof arr)[number].
The original point was that the whole type of the parameter was generic under P and maybe it's assumed that it should be brought complete, and be able to infer.
But if you say that it's not possible then ok. 🤷

The answers are based on the examples you provided.

Sorry, I'm not looking for answers or workarounds. I'm just making a report of how the type that is completely wrapped by the generic type parameter loses information... or any other way you could express it. The examples are a simplification to get the point across, not to be taken literally.

What exactly are you trying to achieve?

Like I said, just reporting. I always feel like there's an air of defensiveness though.

Like I said, just reporting. I always feel like there's an air of defensiveness though.

What you've initially reported is working as intended (boolean functions are not predicate functions).
If you still think that there is an issue to report I think you should restate it accordingly. What exactly is wrong? What behavior do you expect?

boolean functions are not predicate functions

ehr, I don't think that's how extends clauses in the type parameter work, like I mentioned before, they only determine the "upper bound" for the type and a predicate indeed satisfies this bound.
type Test<T> = T extends { (_: any): boolean } ? true : false;
type X = Test<typeof has_foo>; // true

The type is resolved upon invokation and typeof has_foo is what should be assigned to P as required by the parameter predicate: P.
The report is that somehow part of typeof has_foo is lost.
These also dont work:
function do_find<P extends (_: any) => _ is any>(predicate: P)
function do_find<S>(predicate: (_: any) => _ is S)
function do_find<T, S extends T>(predicate: (_: T) => _ is S): S

What exactly is wrong?

If you think there's nothing wrong, or that this is intended behavior, then no problem 👐 I misunderstood what predicate: P where P is typeof has_foo represents.
Close the issue and we're cool ✌

The way you're writing it, it could only work if generic calls were "stamped out" into concrete calls, but they're not. The body of do_find has to be analyzed only in terms of its type parameters. I also don't understand what you're trying to do with the has_foo definition.
The correct way to do it looks like this

declare const arr: (Foo1 | Foo2 | Bar)[];

declare function has_foo(t: unknown): t is (Foo1 | Foo2);

const r1 = arr.find(has_foo)!; // Foo1 | Foo2 🎉

function do_find<P extends (typeof arr)[number]>(predicate: (_: any) => _ is P) {
	return arr.find(predicate);
}

const r2 = do_find(has_foo)!; // OK

Thanks for trying to explain this is something that's not supported.
I don't understand you guys insisting that "trying to do something".
The issue was simple "typeof has_foo had information that got lost when received as parameter". The purpose of the examples are irrelevant.
But good news, I think I found the problem.
The information that gets lost is the conditional after the t is in the declaration of the predicate, perhaps because it's too deep or something, it gets elided or simplified.
Specifically the part of the constraint { foo: unknown }, so moving the declaration <T>(t: T): t is T extends { foo: unknown } ? T : never into an auxiliary interface, we can save the constraint so it doesn't get lost, like so:
interface AuxInterface<U> { <T>(t: T): t is T extends U ? T : never }
declare const new_has_foo: AuxInterface<{ foo: unknown }>;

But now we have to declare has_foo as a const because as a function there's no space to save it. The signatures are still the same.
Therefore the problem is in the declaration of the predicate, not in the receiving side... well not completely true.
Having function do_find<U>(predicate: { <T>(t: T): t is T extends U ? T : never }) would also omit the information after t is, so aux interface is needed here too.
function do_find<U>(predicate: AuxInterface<U>) {
	return arr.find(predicate);
}

const r3 = do_find(new_has_foo)!; // Foo1 | Foo2 🎉

Notice that typeof arr[number] was not required anywhere 👍... even though you guys were so vehement about it.
https://www.typescriptlang.org/play/?target=99&jsx=0#code/JYOwLgpgTgZghgYwgAgGIHt0EZkG8CwAUAJAyYBcyAzmFKAOYDcRxV6AthGABYMD6EADZUIlAK4gA1iHQB3EM0IBfIkVCRYiFBnQAmPCzLpKIMewBG0RcTgye0PjwbipM+YpWE14aPCTIAITgoAxJzYJdpOQUiT1VCABMIBEFglAR0EBpkYKhKAAodHAAfNEx9UqCoAEoAbQBdRSIklLTkGAkEMGBM5G44Kj4jAB4AFQA+fLBKUerKMGRgKmRR5AgAD0gQBOXcdopkCSj5ZCVkAH4V5BMIADcreO8NPxQAQTF1gEkfTSRhgFVxnhkGNJtMVnNkAsllcNlsdsh-hcrjd7iFPC1UlB0plsiAILI+P1BkZKO8vj8XsM9qTDq5oqdxk0vIQAPSs9qdbq9BLoIagBIAyYAB2xCWACDgkEoe1BUxmkOhy1WcIg22WSMuq1R0FO1VCHRAXR6IGQvP52yF+VFEHFkulyHJ32eWiF+oIJGxYDEUFNuQAdDABdaxRKpRBqh54hksgsoPoALxmvlB7b5YlDTDVACEjGQ7LK2GQpR0FUCwWQgBlyIgx7JQADMyCT5tTCXy+MJGaMObzBaKxcL+kAPBuASP2iEA
If still considered intended behavior or not a defect, feel free to close.


[WIP] update mongo velero br process to work on z arch

Mongo does not accept ssl commands on z and all of the backup and restore commands rely on ssl to connect to mongo to run these commands so as of this writing, z is not a supported architecture for backup and restore of mongo. This problem was initially addressed in multi instance and bedrock 4 migration scripts with these prs: https://github.com/IBM/ibm-common-service-operator/pull/1308 & https://github.com/IBM/ibm-common-service-operator/pull/1330. The logic used in this pr comes directly from those two previous prs as this is the same problem.
Testing
velero process

prep a z environment for backup and restore via velero
deploy the z specific backup resources for mongo
proceed with velero backup restore as usual
verify backup completes successfully (will need to check the logs of the backup to verify, it may say "completed" without backing up)
on either the same cluster or a new cluster, restore the mongo-data according to velero steps
verify this actually restored via logs

workaround process

can use same cluster setup for this test
run the backup with ./mongo-backup.sh   true
verify completion
run the restore with ./restore-mongo.sh  true
verify completion

These changes will also need to be applied to the scripts repo since these changes will likely need to be picked up from there for 4.0, 4.1, 4.2, and LTSR. I will open that pr after this one is completed.

replace this pr with https://github.com/IBM/ibm-common-service-operator/pull/1531 and #1530, closing


Order of pages in left side navigation

The pages under the Architecture heading are not displayed in any meaningful order which makes it hard to scan the page titles. It would be helpful if these were displayed alphabetically
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dce3b9c5-ef05-1ff3-a6fe-052f48a9b471
Version Independent ID: f6d3e8e8-37c5-43e6-6185-58f8511dee7e
Content: Hybrid Security Monitoring using Azure Security Center and Azure Sentinel - Azure Architecture Center
Content Source: docs/hybrid/hybrid-security-monitoring.md
Service: architecture-center
Sub-service: reference-architecture
GitHub Login: @doodlemania2
Microsoft Alias: pnp

@DeanGross
Thanks for your feedback! We will investigate and update as appropriate.

Thanks @DeanGross, yep good feedback, I agree. Ill look into it.


test

Signed-off-by: André Martins<EMAIL_ADDRESS>Please ensure your pull request adheres to the following guidelines:

[ ] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[ ] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Thanks for contributing!

Fixes: #issue-number
<!-- Enter the release note text here if needed or remove this section! -->

test-missed-k8s

test-upstream-k8s

test-upstream-k8s

test-missed-k8s

test-missed-k8s

test-upstream-k8s

test-missed-k8s


We don't use the Ubuntu kernels and DKMS anymore

Signed-off-by: Sven Dowideit<EMAIL_ADDRESS>this applies to all releases since 0.8
though we should contemplate retrofitting it.

backported to 1.0.5_ #2110


v3: workbox-analytics throws error on sync

Library Affected:
v3 beta workbox-google-analytics
Browser & Platform:
Google Chrome v64
Hi again guys!
I'm trying trying to use the v3 beta workbox-google-analytics library for offline analytics.
While offline, events are being stored in IndexedDB, but when returning online, I get this error:
Uncaught (in promise) TypeError: Failed to construct 'Request': The provided value is not of type '(sequence<sequence<ByteString>> or record<ByteString, ByteString>)'
    at n.toRequest (workbox-background-sync.prod.js:1)
    at workbox-background-sync.prod.js:1
    at Generator.next (<anonymous>)
    at n (workbox-core.prod.js:1)
    at workbox-core.prod.js:1
    at <anonymous>
toRequest | @ | workbox-background-sync.prod.js:1
-- | -- | --
  | (anonymous) | @ | workbox-background-sync.prod.js:1
  | n | @ | workbox-core.prod.js:1
  | (anonymous) | @ | workbox-core.prod.js:1

And from the network tab it doesn't appear that the stored requests are being sent.
Note: The IndexedDB entry is removed nonetheless. Also, if I queue up multiple events in IndexedDB, it looks like only one is removed.
I have a glitch demo with code. Any ideas?

I've altered the demo to force debug mode and work as a web page offline and the errors quickly mount up:
https://glitch.com/edit/#!/copper-cough?path=sw.js:7:35
The full error is:
workbox-background-sync.dev.js:125 Uncaught (in promise) TypeError: Failed to construct 'Request': The provided value is not of type '(sequence<sequence<ByteString>> or record<ByteString, ByteString>)'
    at StorableRequest.toRequest (workbox-background-sync.dev.js:125)
    at workbox-background-sync.dev.js:354
    at Generator.next (<anonymous>)
    at step (workbox-core.dev.js:14)
    at workbox-core.dev.js:25


metrics for disk reads / writes are not very useful

Aside from the issue of the selector not working with them, the legend for those metrics say just things like "Disk Writes Bps per Server".
That isn't very useful, because not all lines will have the same name.
Replacing it with something like Disk Writes Bps per Server {{instance}} makes it better, because now it at least show us which instance we are looking at when hovering the mouse over.

Also related to:
https://github.com/scylladb/scylla-grafana-monitoring/issues/187


Enhance json structure to match api

This issue was moved to consortium/hybrid-publishing-research#45


List supported Windows OS?

Would it be possible to maintain a list of supported Windows OSes for Azure here?
I'm aware of this document but it doesn't address 32/64 bit versions.
https://support.microsoft.com/en-us/help/2721672/microsoft-server-software-support-for-microsoft-azure-virtual-machines

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

ID: ff5b5898-88d9-7aec-1516-e157e92564a7
Version Independent ID: f9807092-172c-d8d0-fc7d-17204faea51b
Content: Windows Virtual Machines Overview
Content Source: articles/virtual-machines/windows/overview.md
Service: virtual-machines-windows
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@dcbrown16 Azure only supports 64 bit systems. So everything you find in the doc you mentioned will all be 64 bit.
@iainfoulds maybe we should mention this in this document?

Thanks, @MicahMcKittrick-MSFT. I have created a PR to add in the 64-bit support and link to supported operating systems, roles, and features. When that PR merges, this issue will automatically close.

Very helpful, thanks @iainfoulds !


.wbn collision mesh off in mint preview

.wbn with a .bin collision mesh generated from webaverse.com/build registers collisiions two meters off (-y in blender) when in mint preview. Is fine when minted and deployed to parcel.
https://user-images.githubusercontent.com/20630604/106535321-dd014d00-64aa-11eb-92c9-cd1f65328149.mp4
using temple.wbn
https://www.dropbox.com/sh/qidrc6opidsjolm/AABuMUC8eORYleqLVFSeheiya?dl=0

Is the mint preview offsetting anything?

https://github.com/webaverse/app/blob/54692554777f7e40d49d5e2db8c0822e9e53e4e7/world.js#L494

I checked, it should be fixed now.


Newsletters: add 197 (2022-04-27)

[x] Lede, merge summaries, update RCs/releases, add topics @harding
[x] StackExchange section @bitschmidty

Note, the text mentions a thing I posted, so the usual rule applies where I recurse myself from making the ultimate decisions about major edits to that section (or the decision to remove the section if people think it shouldn't be included).
I also have strong opinions about other aspects of the CTV news item, so please please please tell me if you think I'm being biased or unfair in any way.  Thank you for reviewing!

I added two commits for the stack exchange section. The second one adds a (I think) nice image which is creative commons and I have email permission to use from the website author. But we can drop easily if anyone thinks it doesn’t add value

@Xekyo

While the mailing list is important and I'm fine with only covering content from it, I think it could be mentioned that the upcoming activation attempt sparked debates and discussions across many venues, not just on the mailing list.

Sure, I have no problem mentioning that conversations happened elsewhere (and we already mention the chat on bitcoin-wizards).  However, I encourage any of us who learn information useful to the discussion in other venues to relay that info to the mailing list so that it's accessible to everyone watching and participating in the global conversation, as well as being easy to find for future researchers trying to understand why we made the decisions we did.

Thanks for another great summary of a hard-to-summarize issue, @harding!

Made edits for all feedback (thanks so much @adamjonas @jamesob @Xekyo !), added missing content, and added lots of topic links this week.  Reviewed the B.SE section---which is really nice this month!, thanks @bitschmidty !
I'm especially pleased with how this issue turned out, thanks everyone!

ACK 7f61c5ca814a2cb8da6b6382996c767b4bcc5223

Great summaries of the CTV activation discussions (and great newsletter overall!), @harding thank you! 🚀

Indeed. As always the technical summaries are exceptional. I have strong disagreements on what you are bringing focus to and what you're not but that is the only criticism I can have with this newsletter. It is a wonderful asset for the community. Thanks for getting this out at a stressful time for all of us.


Upgrade prettier and add debug on failure

Assisting me in debugging CI-only checks failure in #24, which will target the branch underlying this pull request soon.

This work ends up being removed in #36 and #38, however I've got quite a stack of PRs in place so am leaving this one in place. Feel free to approve without reviewing so it can merge down.


UI support for self registration with multiple channels

Related to https://github.com/wso2/product-is/issues/9754
Issue
Currently IS supports account confirmation via recovery email and external verification. If the user wants to verify his/her account after self-registration using a different channel (Eg: SMS to the mobile) other than EMAIL, Identity server does not support it. This limitation demands user to provide a email at the self registration even though user does not prefer that channel.
Requirement

When the user self register, ask the user to provide a channel (SMS or EMAIL etc.) which he preferrers to be the account confirmation channel. If the user specify a channel, confirm the user account via specified channel.
If the user does not provide a channel, resolve a notification channel and verify the account via resolved channel.
If account confirmation is managed externally, support account confirmation and account unlocking

User self registration scenarios
When a user logins to an application for the first time, the user has the ability to self register. At the self registration process user has the option to provide email and/or mobile. Following two scenarios can be identified.

Provide either the email address or mobile number.
Provides both mobile number and email address.

In the first scenario, If the user provides only one value, that value will be considered as the preferred channel for that user.
In the second scenario, If the user provides both values, there should be an option to select, most preferred communication channel. After selecting that option all the verification and notifications shall be via the preferred channel only.
User Narratives related to self registration scenarios
Narrative 1(User only provides email)

Navigate to the application and click on register.
Provide only the email with other required claims.
User receives a confirmation link to the provided email.
User clicks the confirmation link.
System verifies the user.

Narrative 2 (User only provides mobile)

Navigate to the application and click on register.
Provide only the mobile with other required claims.
User receives an SMS OTP.
User enters the received OTP and proceed registration.

Narrative 3 (User provides both email and mobile)

Navigate to the application and click on register.
Provide the mobile and email with other required claims.
User will be asked to select a preferred communication channel.
User will be notified from the UI that the verification will be via the communication channel selected above. If needed the user has the option to switch the mechanism.
User verification will be triggered from the selected channel.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Cannot find 'fastify'

I am trying to run butler sos through node but am getting an error 'Error: Cannot find module 'fastify'. I see that you updated the fastify-metrics dependency in version 6.0.2, I just wanted to see if this is an issue that other people are having or if it is something wrong on my end. I was running the version 6.0.1 and once I noticed my issue I updated to version 6.1.2 but error is still persisting.
I also want to note that it had been working for me for a while and this is my first time noticing any issues.

Environment:

Windows Server 2016
Containerisation: no
Butler SOS v6.1.2
node butler-sos.js

Any help would be greatly appreciated!

According to the last time my Grafana dashboard received data the issue occurred on Thursday November 4th around 7:30pm if that helps or changes anything. No changes have been made to Butler on that server until today when the issue was brought to my attention.

Hi,
Thanks for reporting this,I'll in what ways I can.
Focus last month or two has been on taking the Butler tool to the next level (including a significant re-write to make things more stable, scalable, future proof, secure etc).
The plan is to do a similar exercise for Butler SOS during coming weeks/month, so good things are coming.
That won't help you in this case though, of course.
I will do a fresh install of v6.1.2 here to see if I can replicate the problem.
The library "Fastify" that's mentioned in your error is the new framework used to handle various http/web stuff. It's way more modern, supported and in general good than the previously used one, so the change is a good one. But it should work too...
One question:
I assume this error occurred after an upgrade from some earlier version to v6.1.2?
If that's not the case - for example if this occurred spontaneously - it's very strange...

v6.1.2 works fine here, when installed from the release package.
But you have to install all dependencies after unzipping the file you downloaded (butler-sos-butler-sos-v6.1.2.zip).
This is done by running npm I from within the src subdirectory.
Something like this:
➜  butler-sos-butler-sos-v6.1.2 cd src
➜  src npm i
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to the maintained and new drop-in replacement @breejs/later at https://github.com/breejs/later 🚀 Thanks and happy hacking! 🚀  @niftylettuce

added 324 packages, and audited 325 packages in 2s

54 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
➜  src

Note: The warning about the later library being deprecated is something that will be addressed in next version of Butler SOS, tracked in #252.

Adding to the above, if I don't run nom I I get exactly the error you describe.
Sooo... could it be that you forgot to do a npm I?
Or that the src/node_modules directory has been deleted?
General installation instructions are found at butler.ptarmiganlabs.com.

Hi,
Thank you for helping me out! I am now realizing that my node_modules directory is deleted. I really don't understand how that happened and I was out when it randomly went down lol. Either way I was able to get it back up and working, thank you for your help!

Good to hear things worked out!


Question: Retrieve port transceiver information for switches?

Hi Team - I would like to use the API to retrieve information about installed transceivers for devices that support pluggable SFPs.  For example, the MS120 on the Dashboard portal, I see:

But when I retrieve the port status via the API there is no information about the transceiver; for example:

I appreciate any guidance or suggestions you could offer.  Thank you!

Hi Jeremy, the best place to ask this type of question about the API's capabilities is in the community forum. Thanks for raising this and I hope to see you there!


Refactor and Expand Dask-Dataframe ORC API

TODO:

[x] (GENERAL) Refactor existing read_orc API to expose a customizable engine interface
[x] (GENERAL) Test coverage for all new features
[x] (WRITE) Add basic to_orc support for pyarrow-4.0
[x] (WRITE) Support write_index option
[x] (READ) Support index
[x] (READ) Support partition_stripe_count (similar to parquet's split_row_groups)
[x] (READ) Support aggregate_files option for multi-file partitions (solution/API should match #7557 )

Planned for a Follow-up PR:

(WRITE) Support append
(WRITE) Support partition_on
(READ) Support "hive-like" directory partitioning

@randerzander @VibhuJawa - This is still early and rough, but please feel free to suggest specific API requirements to help guide the progress.

@dask/io - I am highly motivated to support partition_on in ORC (on the read and write side), but I'd like to implement that seperately.  This PR is makes the necessary changes to mimic the parquet-Engine approach so that downstream libraries (like dask-cudf) can resuse the dask-dataframe logic for reading ORC datasets with multi-stripe and multi-file output partitions.

I'm not sure why the new test failed while writing the test files with pyorc, but I'm hoping is was just a fluke (otherwise, I'm not really sure how to test the offset file-aggregation behavior).

cc @martindurant @jorisvandenbossche in case either of you have thoughts on this

This currently does not support partitioned datasets, right?
Is there interest in having that as well? The ORC file format is not yet supported in the pyarrow.datasets API to discover partitioned datasets, but that could be added. And then I suppose it could be used similarly as in the Parquet engine to read partitioned datasets.

This currently does not support partitioned datasets, right? Is there interest in having that as well?

Right - I have (mostly/roughly) implemented partitioning in a separate branch for a follow-up PR.

The ORC file format is not yet supported in the pyarrow.datasets API to discover partitioned datasets, but that could be added. And then I suppose it could be used similarly as in the Parquet engine to read partitioned datasets.

Yes.  There are RAPIDS uses who would absolutely benefit from having ORC support within the pyarrow.datasets API

Yes. There are RAPIDS uses who would absolutely benefit from having ORC support within the pyarrow.datasets API

ORC could just be another parquet engine!


[FEATURE] Implement Auto Labeling for Issues and PRs

This pull request introduces a GitHub Actions workflow to automatically label issues and pull requests based on specific keywords found in their titles or descriptions. The action checks for keywords such as "bug," "feature," "enhancement," and more, and applies the relevant labels accordingly.
I have tested the code with raising some issues locally, this works perfectly fine as labels are assigned to them accordingly

Key features:

Uses GitHub Actions to automate the labeling process.
Matches keywords against predefined labels to streamline categorization.
Enhances workflow efficiency, particularly for open-source contributions.

This implementation will improve issue and PR management, especially during events like Hacktoberfest.
✅ Checklist
Before submitting the PR, please make sure you have completed the following:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation (if applicable).
[x] My changes generate no new warnings.
[x] I have tested it locally and it works fine.
[x] Any dependent changes have been merged and published in downstream modules.

Hey @shubhagarwal1 , Please make the pr to the test branch.


Extend tailwind-merge configuration

For what version of Nuxt UI are you suggesting this?
v2.x
Description
I know you guys are working hard on V3, but I really like to see this feature still in V2. We all know that not everybody will move over to V3 right away.
I have to set my strategy to override, because tailwind-merge doesn't know about my custom tailwind extends.  Take the Pro LandingGird as example. Classes are added to the grid items to set the right cols. By doing this with strategy set to override, all other classes will be overridden.
I saw some sort of solution in #925 , but that didn't work. It's also not documented and can't find it in the module either.
I know have to create my own merge config, but that will not work for Nuxt UI.
Additional context
You may wonder why I need this. Thats because I'm also using Tailwind Fluid, and try to replicate a design library that uses different spacings etc.

I don't think it's possible at the moment. However, I did this PR back in the days that I ended up not merging that might solve this: https://github.com/nuxt/ui/pull/1108

Hi @benjamincanac ,
Thanks for looking at it. It did see that PR as well.
What are the next steps? I'm a bit confused as you mention it is not possible while that PR might fix the issue?

This could be reopened but a lot has changed meanwhile and the refactor might need to be done on other components as well. I don't have time for this at the moment so feel free to open a PR 😊

Duplicate nuxt/ui#1939.

Hi @benjamincanac,
I'll see what I can do. Just as a reference, the PR seems quite accurate already, right?
Simply change the imports and make sure the twMerge key from the app.config will be merged in there as well.
If you could confirm it will give me a better start 😊

I've restored the fix/925 branch, you can checkout it and merge from dev to resolve the conflicts. Then open a PR from this branch that targets dev.


Revert set/get dispIncr back

Revert the polympo_getMeshOnSurfDispIncr_f and polympo_setMeshOnSurfDispIncr_f back using kokkos parallel for loop.
solving issue #44 , vtp file looks good now:

Looks good for advection/push test. However, I would like to use Kokkos:parallel_for loop for element-loop in MPMesh::CVTTrackingElmCenterBased instead of pumipic parallel-for loop: auto calcCenter = PS_LAMBDA(const int& elm, const int&, const int&){.

Merged and deleted branch.


避免OpenStack不支持安全组部署失败

这个 PR 实现什么功能/修复什么问题:
避免OpenStack不支持安全组部署失败
是否需要 backport 到之前的 release 分支:

release/2.8.0
release/2.7.0
release/2.6.0

/cc @yousong @swordqiu

/cherrypick release/2.8.0

/cherrypick release/2.7.0

/cherrypick release/2.6.0

Codecov Report

Merging #419 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #419      +/-   ##
=========================================
- Coverage    7.95%   7.95%   -0.01%
=========================================
  Files         320     320
  Lines       51102   51102
=========================================
- Hits         4066    4063       -3
- Misses      46651   46653       +2
- Partials      385     386       +1

Flag
Coverage Δ

#aFlag
7.95% <ø> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/util/rbacutils/rabc.go
68.56% <0%> (-1.14%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b70e005...104461a. Read the comment docs.

/approve
/lgtm


(feat) Sync with upstream (confluentinc/cp-helm-charts)

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. helm upgrade on minikube, helm install on gke)

You are pulling all changes from upstream then why one extra commit came from your side?

You are pulling all changes from upstream then why one extra commit came from your side?

This repo is one commit ahead of upstream so when I pull the changes It show there is some conflict that's why I have to add one more commit to resolve that


use which for npm and lein check

Signed-off-by: Ryan P.C. McQuen<EMAIL_ADDRESS>

Thanks for the pull! @kenny-evitt thanks for reviewing Cygwin!

Thank you!


add esp32c5 support

Add esp32C5 support based on esptool implementation
https://github.com/espressif/esptool/blob/master/esptool/targets/esp32c5.py

hi @brianignacio5 why this esp32c5.ts can't recognize the<EMAIL_ADDRESS>

Hi @lijunru-hub Sorry the screenshots you provided doesn't help me much to troubleshoot the problem.
Could you using esptool-js live demo https://espressif.github.io/esptool-js/ and show the information shown there ?
I believe it might be related to the magic number used in your board. Unfortunately I have only tested with one board and I'm unaware of other boards magic numbers. Will update this accordingly.


Relax auth requirements

Context: https://github.com/GoogleCloudPlatform/google-cloud-php/pull/594

Codecov Report

Merging #87 into master will decrease coverage by 0.59%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master      #87     +/-   ##
=========================================
- Coverage   89.98%   89.39%   -0.6%
=========================================
  Files          31       31
  Lines        1887     2159    +272
=========================================
+ Hits         1698     1930    +232
- Misses        189      229     +40

Impacted Files
Coverage Δ

src/ApiCallable.php
89.58% <0%> (-2.42%)
:arrow_down:

src/Testing/MockServerStreamingCall.php
85.71% <0%> (-1.79%)
:arrow_down:

src/LongRunning/OperationsClient.php
78.14% <0%> (-1.71%)
:arrow_down:

src/Testing/MockBidiStreamingCall.php
81.25% <0%> (-1.68%)
:arrow_down:

src/Jison/Parser.php
84.03% <0%> (-1.25%)
:arrow_down:

src/BidiStream.php
96.96% <0%> (-1.11%)
:arrow_down:

src/GrpcConstants.php
81.39% <0%> (-1.11%)
:arrow_down:

src/FixedSizeCollection.php
82.53% <0%> (-0.48%)
:arrow_down:

src/Serializer.php
91.5% <0%> (-0.47%)
:arrow_down:

src/ClientStream.php
100% <0%> (ø)
:arrow_up:

... and 20 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cbc6710...174b31b. Read the comment docs.

LGTM

Will cut a new patch release to include this today

Awesome, thank you!


Move to winit+wgpu from SDL

[ ] Move rustzx code base to winit+wgpu
[ ] Native CLI version for testing / other integrations (will substitute current rustzx SDL-based binary)
[ ] Make SDL-based subsystem optional kill it completely

It is not GUI-related, but in order to make SDL optional, we also need to add new audio backend via cpal

[x] pacmancoder/rustzx#101

UPD: Updating this task due to decision to use web-based GUI via tauri-apps/wry instead of iced

UPD: Updating this task due to decision to use web-based GUI via tauri-apps/wry instead of iced

Have you considered egui as a UI frontend instead? Pretty intuitive and easy to use and also web ready.

@ArjunNair I have considered it previously, but rejected this idea due to the early days of the library (at the moment it was very rapidly changing) and also because I wanted to minimize the dependencies number/compilation times. I might revisit this decision in the future tho


filesystem access issues running LLVM tests

Great tool, thanks (specially for us folks new to silverblue)
Building LLVM seems to work, however I'm seeing filesystem access issues when attempting to run the tests.
Possibly related to #9
Environment:
fedora-silverblue: 29.20181101.0 (2018-11-01 14:01:23)
fedora-toolbox: cf2347fe562dd78210c7245f5ded268d8ea7f18a
runc version 1.0.0-rc5+dev
commit: 7463241d645ba55b05b103673e322542661b0ad8
spec: 1.0.1-dev
/var/home btrfs rw,nodev,noatime,seclabel,compress=zstd,ssd,space_cache,subvol=/home
Steps to reproduce:

Create a default fedora-toolbox and enter it
sudo dnf update -y && sudo dnf builddep -y llvm
sudo dnf install -y svn
create and/or cd into $HOME/src
svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
cd llvm && mkdir build && cd build

cmake -GNinja \
  -DCMAKE_INSTALL_PREFIX=/opt/llvm \
  -DCMAKE_BUILD_TYPE=Release \
  -DLLVM_USE_LINKER=gold \
  -DLLVM_OPTIMIZED_TABLEGEN=ON \
  -DLLVM_USE_SPLIT_DWARF=ON \
  ..

run ninja check-llvm

Expected: LLVM tests to run successfully
Actual: (cut out the traceback for brevity/readability)
Running the LLVM regression tests
                                       -- Testing: 28397 tests, 16 threads --
0% [------------------------------------------------------------------------------------------------------------]
OSError: [Errno 30] Read-only file system
FAILED: test/CMakeFiles/check-llvm
ninja: build stopped: subcommand failed.

That was with LLVM commit 10c750cc3f45be8d.

Sounds great! Thanks for getting in touch.

Duplicate of #9


Create data browser evolutionary roadmap with stakeholders

┆Issue Number: HCAB-355

@theathorn I think we can close this. Let's discuss. This was for browser next steps presentation at the last f2f and tickets created from that.


Fatal "unknown event type" with "samples\02-animation"

(This was the last hurdle to run on Windows!)
In World::update_scene when updating the animation events, and EventHeader with a type of 27 appears.
This is currently unhandled in the switch statement, and throws this fatal error (debug mode):
CE_FATAL("Unknown event type");

This can be ignored to continue running, perhaps downgrade this warning to a log?

In the samples\01-physics demo there is a similar error for the physics event type.
But this is a buffer overflow as the event type is 0x3F800000 which is a float value of 1.0f!

Cannot reproduce this. I tested with both VS2017 and MinGW in debug mode.

This only occurs with the "win32" platform. It does not occur on "x64".
Some locals:

size = 32
read = 16
(eh) = 0x0f24e510 {type=27 size=0 }

Note the size is 0, so the event is skipped

This should do it: https://github.com/dbartolini/crown/commit/b58824c3618654c999ef0952a98b81b96bb67ab6

Thanks.
The physics event processing will also need this - see:
https://github.com/dbartolini/crown/commit/b58824c3618654c999ef0952a98b81b96bb67ab6#diff-112c1c4fea0725727cda5af8b8cae2e4L182
On 20 February 2018 at 23:57, Daniele Bartolini<EMAIL_ADDRESS>wrote:

This should do it: b58824c
https://github.com/dbartolini/crown/commit/b58824c3618654c999ef0952a98b81b96bb67ab6
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dbartolini/crown/issues/78#issuecomment-367163960,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABkWyFsxLzdV5EwJ8WNxdCdXoD9Nlhuoks5tW1vbgaJpZM4SMn4t
.

Right, thank you. :)


Add NorthMacedonia import to init

Fix missing import for NorthMacedonia class/country.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.857%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5781

Relevant Lines:
5849

💛  - Coveralls

I don't know how to fix coverage

Merged: thank you very much! 👍


Add "copy" button to code blocks

Code blocks, at least in the tutorials, should come with a "copy" button, allowing users to conveniently copy code snippets to the clipboard.
Not sure if this is something that needs to be addressed upstream?

I recently added sphinx-copybutton to mne-bids and several other repos, and it does the job very well: https://github.com/executablebooks/sphinx-copybutton

Hey, I'm working on this!


Error in Ansible

TASK [common/add_packages : Add new repositories keys] *************************
changed: [k8s-m-1] => (item={'key': 'https://download.docker.com/linux/ubuntu/gpg'})
failed: [k8s-m-1] (item={'key': 'https://packages.cloud.google.com/apt/doc/apt-key.gpg'}) => {"ansible_loop_var": "item", "changed": false, "item": {"key": "https://packages.cloud.google.com/apt/doc/apt-key.gpg"}, "msg": "Unable to extract key from '-'", "stderr": "gpg: WARNING: no command supplied.  Trying to guess what you mean ...\ngpg: [don't know]: invalid packet (ctb=0a)\n", "stderr_lines": ["gpg: WARNING: no command supplied.  Trying to guess what you mean ...", "gpg: [don't know]: invalid packet (ctb=0a)"], "stdout": "pub:-:2048:1:FEEA9169307EA071:1614614617:1677728521::-:\nuid:::::::::Rapture Automatic Signing Key (cloud-rapture-signing-key-2021-03-01-08_01_09.pub):\nsub:-:2048:1:AA42F36EE8BEEE0E:1614614617::::\npub:-:2048:1:8B57C5C2836F4BEB:1607040606:1670154510::-:\nuid:::::::::gLinux Rapture Automatic Signing Key (//depot/google3/production/borg/cloud-rapture/keys/cloud-rapture-pubkeys/cloud-rapture-signing-key-2020-12-03-16_08_05.pub) <glinux-team@google.com>:\nsub:-:2048:1:48419E688DD52AC0:1607040606::::\n", "stdout_lines": ["pub:-:2048:1:FEEA9169307EA071:1614614617:1677728521::-:", "uid:::::::::Rapture Automatic Signing Key (cloud-rapture-signing-key-2021-03-01-08_01_09.pub):", "sub:-:2048:1:AA42F36EE8BEEE0E:1614614617::::", "pub:-:2048:1:8B57C5C2836F4BEB:1607040606:1670154510::-:", "uid:::::::::gLinux Rapture Automatic Signing Key (//depot/google3/production/borg/cloud-rapture/keys/cloud-rapture-pubkeys/cloud-rapture-signing-key-2020-12-03-16_08_05.pub) <glinux-team@google.com>:", "sub:-:2048:1:48419E688DD52AC0:1607040606::::"]}

My version information:
  master U:1  ~/gitrepos/others/ansible-vbox-vagrant-kubernetes                                       13:03:32  ⚡79%  jesseadelman
 1 ❯ ansible --version
ansible [core 2.11.0]
  config file = None
  configured module search path = ['/Users/jesseadelman/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/Cellar/ansible/4.0.0/libexec/lib/python3.9/site-packages/ansible
  ansible collection location = /Users/jesseadelman/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.9.5 (default, May  4 2021, 03:36:27) [Clang 12.0.0 (clang-1<IP_ADDRESS>)]
  jinja version = 3.0.1
  libyaml = True
  master U:1  ~/gitrepos/others/ansible-vbox-vagrant-kubernetes                                       13:07:37  ⚡79%  jesseadelman
❯ vagrant --version
Vagrant 2.2.16

Happy to provide more info, more shell output, if you like. :) Thanks.

@boldandbusted thanks for opening an issue. Unfortunately I have not been able to reproduce the error (please check VirtualBox Internet access - instructions below).
I am running the command vangrat up after having upgraded all packages to:

vagrant: 2.2.16
virtualbox: 6.1.16
ansible 2.9.9
'bento/ubuntu-20.04' version '202105.25.0' (vagrant box update if needed)

I believe the error was an issue with a broken downloaded GPG file
https://packages.cloud.google.com/apt/doc/apt-key.gpg
    TASK [common/add_packages : Add new repositories keys] *************************
    changed: [k8s-m-1] => (item={'key': 'https://download.docker.com/linux/ubuntu/gpg'})
    changed: [k8s-m-1] => (item={'key': 'https://packages.cloud.google.com/apt/doc/apt-key.gpg'})

    TASK [common/add_packages : Add new repositories to sources] *******************
    changed: [k8s-m-1] => (item={'repo': 'deb [arch=amd64] https://download.docker.com/linux/ubuntu focal stable'})
    changed: [k8s-m-1] => (item={'repo': 'deb https://apt.kubernetes.io/ kubernetes-xenial main'})

Could you please check again?
Access to the Internet from inside a VirtualBox machine
Please check also that you have access to the Internet from inside the VBox machines:
(password is vagrant)
$ ssh<EMAIL_ADDRESS>The authenticity of host '<IP_ADDRESS> (<IP_ADDRESS>)' can't be established.
ECDSA key fingerprint is SHA256:j6zxL49UqzfRcIdpQiPwbpt7t7JuqthrrJBtXDkeEjk.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
<EMAIL_ADDRESS>password: **vagrant**
Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-73-generic x86_64)
...
This system is built by the Bento project by Chef Software
More information can be found at https://github.com/chef/bento
Last login: Thu Jun 10 15:40:48 2021 from <IP_ADDRESS>

vagrant@k8s-m-1:~$ ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=63 time=2.76 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=63 time=3.03 ms

Thank you! It was a local issue with Ansible and Vagrant setups.


Create the first migration for the model User using sequelize and sequelize-cli

For now, let's limit this to Users.
There are 2 ways we can go about doing this:

create the database first and the tables first and then hook up Sequelize to those
let Sequelize create the tables

The first options is much more complicated in terms of code in Javascript and I don't think it gives us any advantage.  @mwiech99 have a look at Sequelize Getting started https://sequelize.org/master/manual/getting-started.html and more detailed section about connecting to a non-empty database (migrations).
The big downside of creating tables first and then hooking it up with Sequelize is that we will still need to setup the ORM models for it anyway, so we would be doing double work for no reason.
My summary recommendation is:

use Sequelize to setup as much as possible
use other means to setup any complicated constraints, additional tables not used by the backend, etc.

https://github.com/kpagacz/wiki-on-fire/issues/53 should be done prior to this.


Expand: show expanded macro name and its location

Close #4766
This change will be help to debug a macro.
Example 1:

Example 2 (nested expansion is supported):

You can focus the line "# expand macro ...".

Could anyone review this?

Repeat: Could anyone review this? @RX14 @mverzilli @ysbaddaden

This is awesome 👍  Thanks @MakeNowJust


Create CHANGELOG.md

Coverage decreased (-0.1%) to 96.335% when pulling 2180c23f554ca00dfb79452efe85ef6cbd67a422 on changelog into 14b73c869ccbb77885a999e25efcce40486ff81c on master.

NOTE: We should try to stick to a changelog format like http://keepachangelog.com/

I'm more in favor of using the same format as react
https://github.com/facebook/react/blob/master/CHANGELOG.md

[x.x.x] - yyyy-mm-dd
Release type: [ bug fixes, features, miscellaneous( dependency upgrade, build changes, etc ) ]
Bug Fixes

description ( @outsidecontributer #pullrequest )

Features

description ( @outsidecontributer #pullrequest )

Breaking Changes

description ( @outsidecontributer #pullrequest )

Removed Deprecations

description ( @outsidecontributer #pullrequest )

New Deprecations

description ( @outsidecontributer #pullrequest )

Miscellaneous

description ( @outsidecontributer #pullrequest )

Contributers

Name @outsidecontributer

[1.0.0] - 2016-07-09
Features
CLI
You can start deepstream via a command line interface. You find it in the bin directory. It provides these subcommands:

start
stop
status
install
info
hash
append a --help to see the usage.

File based configuration
You can now use a file based configuration instead of setting options via ds.set(key, value).
deepstream is shipped with a conf directory which contains three files:

config.yml this is the main config file, you can specify most of the deepstream options in that file
permissions.yml this file can be consumed by the PermissionHandler. It's not used by default, but you can enable it in the config.yml
users.yml this file can be consumed by the AuthenticationHandler. It's not used by default, but you can enable it in the config.yml

For all config types support these file types: .yml, .json and .js
Constructor API.
There are different options what you can pass:

not passing any arguments ( consistent with 0.x )
passing null will result in loading the default configuration file in the directory conf/config.yml
passing a string which is a path to a configuration file, supported formats: .yml, .json and .js
passing an object which defines several options, all other options will be merged from deepstream's default values

Valve permissions rules
You can write your permission into a structured file. This file supports a special syntax, which allows you to do advanced permission checks. This syntax is called Valve.
Enhancements
no process.exit on plugin initialization error or timeout
deepstream will not longer stops your process via process.exit(). This happened before when a connector failed to initialise correctly #243 instead it will throw an error now.
Currently the API provides no event or callback to handle this error
other than subscribing to the global uncaughtException event.
process.once('uncaughtException', err => {
  // err.code will equal to of these constant values:
  // C.EVENT.PLUGIN_INITIALIZATION_TIMEOUT
  // or C.EVENT.PLUGIN_INITIALIZATION_ERROR
})

Keep in mind that deepstream will be in an unpredictable state and you should consider to create a new instance.
Breaking Changes
Permission Handler
In 0.x you can set a permissionHandler which needs to implement two functions:

isValidUser(connectionData, authData, callback)
canPerformAction(username, message, callback)

In deepstream 1.0 the isValidUser and onUserDisconnect`` is no longer part of the permissionHandler and is instead within a new handler: authenticationHandler.
You can reuse the same 0.x permission handler except you will have to set it on both explicitly.
const permissionHandler = new CustomPermissionHandler()
ds.set( 'permissionHandler', permissionHandler )
ds.set( 'authenticationHandler', permissionHandler )

Plugin API
All connectors including, the permissionHandler, authenticationHandler and logger all need to implement the plugin interface which means exporting an object that:

has a constructor
has an isReady property which is true once the connector has been initialized. For example in the case a database connector this would only be true once the connection has been established. If the connector is synchronous you can set this to true within the constructor.
extends the EventEmitter, and emits a ready event once initialized and error on error.

Logger and colors options
The color flag can't be set in the root level of the configuration anymore.
The default logger will print logs to the StdOut/StdErr in colors.
You can use the deepstream.io-logger-winston which can be configured in the config.yml file with several options.
Connection redirects
deepstream clients now have a handshake protocol which allows them to be redirected to the most efficient node and expect an initial connection ack before logging in. As such In order to connect a client to deepstream server you need also to have a client with version 1.0 or higher.
More details in the client changelog.


added support for sql tracing and replaced removal of “-123”

The replacement of removal of “-123” was needed to support filenames with a dash.  links like /routes/web-api.php:123 did not work


(MINOR) Add --certs and --tree options

Add --certs and --tree options
--certs extracts the certificate chain
--tree displays a graphic tree view of manifest store structure
(MINOR) added to catch changes from update to 0.17.0 c2pa-rs update.

Codecov Report

Merging #106 (8c0bcc9) into main (9d9bb77) will decrease coverage by 0.37%.
The diff coverage is 71.42%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #106      +/-   ##
==========================================
- Coverage   78.53%   78.17%   -0.37%
==========================================
  Files           5        5
  Lines         382      394      +12
==========================================
+ Hits          300      308       +8
- Misses         82       86       +4

Impacted Files
Coverage Δ

src/main.rs
66.42% <71.42%> (+0.02%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Some styles loads with delay after the page first render!

After page load, the first time elements has default browser css styles and only after 1-3 second they became as they should be (look at the video https://cl.ly/c374d670fe2a )

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
I see changing styles while the page is being rendered
Expected Behavior 🤔
Render correctly styled element immediately
Steps to Reproduce 🕹

Steps:

Clone the repo https://github.com/mui-org/material-ui/tree/master/examples/nextjs
Add any element (I use the <TextField Element variant="outlined" /> for example)
Push The Refresh button in you browser and you will see this issue

Your Environment 🌎

Tech
Version

Material-UI
v4.4.0

React
latest

Browser
Chrome

OS
Mac OS

I see changing styles while the page is being rendered

Could you expand on this, what specifically change?

I use the

This is expected, we rely on the availability of the layout measurements to correctly position the gap. You could work around the problem by setting a background color to the label that matches the background. We could document this limitation in https://material-ui.com/components/text-fields/#limitations. Do you want to handle it? :)

@oliviertassinari Here is video with the issue https://cl.ly/89229cfd77e2

Some more details:
I put this element:
<TextField
autoFocus={true}
variant="outlined"
className="auth-input"
InputLabelProps={{
shrink: true,
}}
/>
I'm using shrink: true, because without it, there is another bug (with placeholder and autofill chrome).
here is the image: https://cl.ly/0f4be49aac03/Screenshot%2525202019-09-05%252520at%25252021.39.00.png
Here is the video: https://cl.ly/5a0f7a688c1b
If somebody wuold tell how to solve this issue, it would be great!

I'm using shrink: true, because without it, there is another bug (with placeholder and autofill chrome).

See #14427.

I use the <TextField Element variant="outlined" />

This is expected, we rely on the availability of the layout measurements to correctly position the gap for the label. You could work around the problem by setting a background color to the label that matches the background. We could document this limitation in https://material-ui.com/components/text-fields/#limitations. Do you want to handle it? :)

@oliviertassinari Can I document this if possible 😄

It would be nice for this to wait for #17483

Agree, we should also wait for the direction #17680 takes.

We have found a solid solution in #17680. It should do it.


Can't downgrade read-only database from version 2 to 1

Hello! Trying to create pre-populated database.
My Database
@Database(entities = {Series.class}, version = 2, exportSchema = false)
...
public static AppDatabase getDatabase(Context context) {
    if (INSTANCE == null) {
 synchronized (AppDatabase.class) {
     if (INSTANCE == null) {
    INSTANCE = RoomAsset.databaseBuilder(context,
            AppDatabase.class, DB_NAME)
             .allowMainThreadQueries()
                .build();
       }
       }
       }
        return INSTANCE;
    }
Problem is:
`I/SQLiteAssetHelper: successfully opened database cymbalsbase.db
W/SQLiteAssetHelper: Can't downgrade read-only database from version 2 to 1:
Upgrading database cymbalsbase.db from version 2 to 1...
missing database upgrade script: databases/cymbalsbase.db_upgrade_0-1.sql
E/SQLiteAssetHelper: no upgrade script path from 2 to 1
D/AndroidRuntime: Shutting down VM
E/AndroidRuntime: FATAL EXCEPTION: main`
What can i do?

try to uninstall the current version and install a new one and see if the problem still exists.

I can't reproduce this error on my end, can you provide the steps leading to this exception?

I uninstall app on emulator and install it, then i get this error.
Can you tell me how i can provide steps?

I still can't reproduce your error.
can you provide a minimum working example so I can work on fixing this problem.

W/SQLiteAssetHelper: Can't downgrade read-only database from version 2 to 1
I solve this problem by using read-write database instead or you can change database version to 1.


standardize addresses and coordinates

add a column to locations for standardized_address
use the USPS address information API to standardize addresses, which will be helpful in identifying duplicate data
We've currently applied to the USPS for access to the API.

I don't know the full scope of this issue, so please excuse if this suggestion is off-base.
I've had pretty good results in standardizing / normalizing addresses with the Tiger Geocoder address normalizer.
A pro is that you can host it on your own server and do a lot of stuff quickly with SQL.  Of course, that comes with the con of having to maintain the installation.
There's apparently an address standardizer library for Python (maybe several), and there are some other open source libraries available.


Improve integration tests

[#155582520]
1 Change log level of integration test to info
2 Disable sequelize log of apiserver

@boyang9527 updated.

LGTM


All records received during initial snapshot must have zero Uint64(0) _version

.. now there is a timestamp ms  plus  a serial number,      but this value may be greater than the value calculated during  cdc event processing, especially when the snowflake.id  is disabled.

in the example on the screenshot the version is calculated from GTID position, it is obvious that the  ReplacingMergeTree engine  cannot works properly

context:
version: 2.3.0
snowflake.id: "false"

I would also like to note that snowflake id values are only comparable between values of the same type of snowflake id; they cannot be compared with an arbitrary timestamp.
... especially considering that a custom time offset is used for snowflakeid generator.
https://github.com/Altinity/clickhouse-sink-connector/blob/1027f19af3e94dd1638d7dc986870b3b6842987a/sink-connector/src/main/java/com/altinity/clickhouse/sink/connector/common/SnowFlakeId.java#L16


Regarding serial port helper vs code extension

how to send enter key word.
can we communicate via python with your tool?for sending and receiving data

For now, only through @hex:0a to send \n. I will update to support it in send string.
Let me think about it. It's not support now.

@johnuwd there is support to send escape characte now. you can update to 0.0.6 to get it.

For the feature 2, maybe I can create a http server to recv data what you want to send. and you give me a web url to recv data what I recv. What you think?


Releasing third party package for ROS2

I am releasing a (third party) package for the first time, and #33777 has just been merged. The build log is showing compilation and clang-tidy warnings. I have 2 questions regarding this problem:

I followed this ROS1 bloom tutorial and made patches to the upstream CMakeLists.txt to exclude building some of the targets. However, from the build log, it seems like the upstream repository instead of the release repository is cloned and it results in building the full sets of (default target) declared in the upstream repo. The compile warnings also come from the build targets that are supposed to be excluded. How does patching works for the ROS2 build farm? Is it still the same as what's shown in the ROS1 tutorial?
Is clang-tidy run on the entire codebase on the upstream repo? Since I do not have direct control over the upstream repo, is there a way to ignore clang-tidy warnings for third-party packages like the one I am releasing for?

Edit: It seems like there are separate builds for Fdev and Fsrc, and if I understand this correctly, Fsrc is using the release repo for building the release binary. Should I worry about Fdev build being unstable?

Close by #33876.


Working with RTK Query?

Hello,
I've just installed your plugin and i don't see any update for RTK Queries.
Is it already supported?
I can monitor the requests on the react-native-web side with the chrome redux extention. So it will be good to support that too :)
Maybe another plugin for flipper already do that?
Thanks for your work :)

It should be supported. I will check for it.


YouTube api Error 401: deleted_client

After running main.py and copy and pasting the url in browser it shows this problem

Run python3 main.py in your computer terminal (terminal or cmd). You have to sign in to your Youtube Account through the link the script will give you. It's going to ask you: "Please visit this URL to authorize this application:..." so you copy that link, paste it in your browser, and then sign into your Google account. Then paste the authentication code you get back into your terminal. It will then say "Starting Scraping" and sign into your instagram account.

it seems that i am having something similar, a uri is being misdirected.. can any tell me what uri this is supposed to point to ? everything else runs successfully up until authorization.


Suggestion

[Enter feedback here]
In the remove-inboxrule cmdlet I would like to see the ability to clean out all rules including hidden rules rather than have to instruct users to use outlook.exe /cleanrules.
Suggestion
remove-inboxrule -mailbox<EMAIL_ADDRESS>-cleanrules

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

ID: 619045f2-4093-ef53-8b1f-4674a7fc478b
Version Independent ID: fcf4649d-4571-76cf-c309-f6c6aba08184
Content: Remove-InboxRule (exchange)
Content Source: exchange/exchange-ps/exchange/Remove-InboxRule.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@officedocsbot assign @yogkumgit

Hello @stephent122, thanks for your feedback.
For feature requests, I need to kindly redirect you to this resource https://office365.uservoice.com/.
There, your suggestion will reach the product team.

@stephent122  Thank you very much for your kind feedback. Considering your valuable feedback, as advised please log this issue as a User Voice. Concerning team will evaluate and take the appropriate action, as per their schedule. We proceed here to close it. Thanks again for taking out some time and sharing your feedback.


Upstream improvements

This PR merges upstream improvemenets from the roots/bedrock project. It is a partial fix for pressbooks/private#113
Notes
We have not pulled upstream changes since inital creation. See<EMAIL_ADDRESS>for full changelog.

Opened in wrong repo. Sorry!


feat(tutorial): complete step 5

mybluemix.net URL: http://carbon-tutorial-sky9090126com.mybluemix.net/#/
Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

@kellychurchill I added the mybluemix.net URL to the PR description, please check again, thank you.


Okta compatibility updates

Inconsistencies have been discovered between Okta's API and the OAuth2 implementation in this library that affect its ability to successfully get all the way through the authorization flow.
These issues, which are addressed in this change set, are as follows:

The client credentials are included in both the body (params) and in the basic authorization header; Okta will issue a 403 in response to this.
Okta's response containing the access token is JSON-encoded, and since oauth2 does not by default support the JSON mimetype, the JSON string containing the token is treated as the token itself, which results in a 401 when making the final request to authenticate the user back to Okta.

Heya, thanks for approving and sorry for the late response (same, re: notification)
No concern of backwards compatibility; Okta's OAuth2 API doesn't have any sort of versioning.


Initial framework for pod construction architecture refactor.

When proposing against upstream, I will make the git history in such a way that each element that was moved from the old architecture to the new, will be moved in separate commits. Reviewing would most optimally be done commit by commit, but still all in the same pull request because we'd rather get the entire refactor in at once.(i.e. it's difficult to break this refactor out into logical chunks).
Almost there right now - still needs tests for KubernetesConf and each of the two builders.

Closing in favor of https://github.com/apache/spark/pull/20910.


Docker pull "manifest not found"

Based on this issue it appears that the docker image "mcr.microsoft.com/oss/nginx/nginx:stable" is no longer available. I attempted to use the :stable and :latest tags, but neither worked. Opening this issue issue and then hoping to submit a pull request to make this documentation usable again 😄

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

ID: 22dc1f78-5ef2-391c-732f-740c0ca12880
Version Independent ID: ffad8c17-c1e6-fb99-3a39-98be4d6ed091
Content: Push & pull container image - Azure Container Registry
Content Source: articles/container-registry/container-registry-get-started-docker-cli.md
Service: container-registry
GitHub Login: @tejaswikolli-web
Microsoft Alias: tejaswikolli

@mitchelldirt
Thanks for your feedback! We will investigate and update as appropriate.

@mitchelldirt
Thanks for your feedback! We will investigate and update as appropriate.

I opened up this pull request to solve the issue :) I'm not sure if using the official Nginx image is the direction you'd want to take.
If you'd prefer something else I can update my PR.
Thanks 😇

@mitchelldirt
Thanks for creating PR, once document author approves the changes should go live soon.


New example: compute exp(x)

Pull Request Test Coverage Report for Build 998408899

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.411%

Totals

Change from base Build 987173076:
0.0%

Covered Lines:
1954

Relevant Lines:
1994

💛  - Coveralls


Taghelper: Razor populated attribute value not accesible in taghelper but shows "Microsoft.AspNet.Razor.Runtime.TagHelpers.DefaultTagHelperContent"

When I have a razor template with
<div<EMAIL_ADDRESS>@Model.Title
</div>

and create a taghelper targeting "mytag-demo" the value in the taghelper is not the Title of the model object but "Microsoft.AspNet.Razor.Runtime.TagHelpers.DefaultTagHelperContent".
Taghelper demo:
	[HtmlTargetElement(Attributes = "mytag-demo")]
	public class MyTagDemoTagHelper : TagHelper
	{
		[HtmlAttributeName("mytag-demo")]
		public string MyTag { get; set; }

		public override void Process(TagHelperContext context, TagHelperOutput output)
		{
			output.Attributes.Add("data-mytagvalue", MyTag);
		}
	}

now it outputs
<div data-mytagvalue="Microsoft.AspNet.Razor.Runtime.TagHelpers.DefaultTagHelperContent">
The Model Title
</div>

This behaviour was introduced in 1.0.0-beta8-15653  in the previous release 1.0.0-beta8-15618 it worked fine. Am I missing something or is this a bug?

Seems related to this - https://github.com/aspnet/Razor/commit/323befaaf10a4c3bf90f73153065b331a5e8ace0
cc @rynowak

@rynowak Looks like we have a test gap in MVC for generic TagHelper cases that have attribute values intermixed with @value.
https://github.com/aspnet/Mvc/blob/d8d0a1ab89d61713fe60ec4b5a2994b7907646a9/src/Microsoft.AspNet.Mvc.Razor/RazorPage.cs#L253
Is ToStringd at codegen here when a user intermingles @s.
I knew we had it for a reason :smile:. The right fix for this will probably be a code generation change to use GetContent rather than re-adding ToString

Waitttt there's no test gap. The build fails.

Thanks for the report. @rynowak has been fixed this via:
https://github.com/aspnet/Razor/commit/c9341ee3d7c75bc97ef0f825bac25b48bd74134b
https://github.com/aspnet/Mvc/commit/80add92de8ad839e26dba236c873f51ef039740d


Error when executing &reverse

Message: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
Stack Trace: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at new NodeError (node:internal/errors:329:5)
at Socket.Writable.write (node:internal/streams/writable:331:11)
at /home/esmBot/esmBot/utils/image.js:109:21
This happened when i tried to reverse this gif https://tenor.com/view/catan-tableflip-i-quit-you-cheater-angry-gif-4955758

Seems like something happened with the connection to the image servers, should be fixed now.


Fix for the fallback issue

These code changes resolve the following issue that were reported related to fallback feature:
If all nodes in PRIMARY_PLACEMENT are down, connection go to FIRST_FALLBACK nodes, now if a node in PRIMARY_PLACEMENT come back up, all new connections do not go to that node but are rather equally distributed between this node and FIRST_FALLBACK nodes.

Closing this PR as the issue has already been taken care of in PR #4


Numpy compatible max

Description
numpy amax operator
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

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

Changes
Comments
@haojin2 @reminisce

@stu1130 Can you look into the CI failures on this one ?
@mxnet-label-bot Add [Numpy, pr-awaiting-review, Operator]

ping @haojin2 for 2nd review


hstgrp not found

Zabbix running with MySQL. Zabbix version 3.4.7.
When I attempt to launch influx-zabbix I get an error: [...db-zabbix/log/log.go:299 Error()] [E] Error while executing script: Error 1146: Table 'zabbix.hstgrp' doesn't exist
The error is accurate, as that Table does not exist, and never has.
How do I omit the query that looks for hstgrp Table?

You can either upgrade your Zabbix setup (3.4 is not supported for quite some time) or use older version of this project prior to #16.


[gateway] wip http extauth sspi ntlm

This is an implementation of HTTP_EXTAUTH_SSPI_NTLM.
it can be enabled with /gt:http|auto,extauth-sspi-ntlm

Refer to this link for build results (access rights to CI server needed): https://ci.freerdp.com//job/PullRequestTester/8395/

sorry, did clang-format on the mentioned files...

@freerdp-bot test

@freerdp-bot test please


Render error

When I run terminalizer render Name
throws me this error:
Error:
  Error:
(electron:4827): Gtk-WARNING **: 03:34:45.617: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version

Are you using the KDE version of Manjaro, by chance? I have consistently run into this error on a variety of packages, including terminalizer.

Are you using the KDE version of Manjaro, by chance? I have consistently run into this error on a variety of packages, including terminalizer.

same (using Manjaro KDE)

@Achazwl I was never able to overcome this issue, so I ended up using https://github.com/asciinema/asciicast2gif instead.


Opacity support

Is it possible to add opacity support? It is useful in animations (without bounce) :)

Never made it?

+1

+1

Not enough demand for this?

I'd love to take a crack, but it's been years since I've done Backbone, and I've never worked with Coffee. :(

Come on Joel! We all know you can make it during lunch break ;-)

:+1:

+1

+1


Compress extension using minify

Zipped bundle without minify: 8.1K
Zipped bundle with minify: 7.7K
The savings are not that great, most likely because it doesn't compress the icons and license.
(Note I'm including the license in the bundle because people with a bit of technical knowledge can download the source directly from the Web Store instead of going to GitHub.)
I also don't like the difficulty of installing this tool which could be a pain point for contributors.

Closing in favour of #37 - the minified zipped bundle of that solution comes in at 5.4K 🥇


Map some various things

Bootstrap.init seems to basically call all default registration stuff (now registerDefaults instead of init), so maybe it should be renamed as well?


Webgui access over port other than 5800

I'd like to know if its possible to run handbrake docker together with mkvtoolnix. Everytime I try to do this, I can only access the one wich GUI is over port 5800.
The other, usually running at port 5900, returns the message ERR_EMPTY_RESPONSE when trying to access.

Sure, you just need to map port 5800 to another one with the -p parameter of the docker run command.
For example, if you use -p 5801:5800, you can then access the container's web UI via port 5801.

Thank you very much! :) 👍

What if I use my own docker network using the macvlan driver? Docker ignores -p in this case...

In this case the port can't be changed.

Note that this is now possible, with the variable WEB_LISTENING_PORT.


forc build - Create "build plan" before beginning compilation

Currently, the process of compiling dependencies is intertwined with fetching the program's immediate child dependencies before then resolving and compiling child dependencies recursively.
It could be worth splitting this step into:

Construct "build plan" as a graph of all dependencies.
Compile the graph of dependencies in topological order.

By creating a build plan as a separate first step there are a few potential benefits:

Detect cycles before beginning compilation.
Support dependency graph visualisations (e.g. .dot files) even if one or more dependencies don't compile successfully.
More easily avoid compiling duplicate dependencies more than once.
Better prepare for potentially supporting something like Forc.lock and reproducible builds in the future.
Pave the way for compiling multiple dependencies concurrently.
Friendlier interop with hermetic build systems like Nix.

Adding a forc plan command
It could be useful to break this work into a separate forc plan command and then implementing forc build in terms of using forc plan as the first step of the build process.
I'm imagining the standalone forc plan command could behave as follows:

Recursively fetch all dependencies into .forc/. This step would not begin any compilation, but rather just recursively fetch and inspect Forc.tomls until we've acquired all required dependencies. Fetching dependencies should probably happen in breadth-first-search order, where each of the Forc.toml's immediate dependencies are fetched before inspecting and fetching the dependencies of the children. We can construct the dependency graph during this traversal, maintaining awareness of cycles and duplicates by updating a set of already-visited dependencies as we go.
Report cycles. If any cycles are detected, report the error to the user. Cycles should be reported as a list, starting from the first dependency that was encountered and ending in the last.
Warn the user about dependencies that appear multiple times with differing versions. cc @sezna I think technically we could probably successfully compile with a couple different versions of the same dependency. But this would probably cause a lot of bloat and potentially cause some strange errors with trait/type mismatches if those two dependencies interact in the top-level code somehow... We probably do want to support it though, I can imagine a user using two different libraries that happen to depend on different versions of some particular util dependency that doesn't actually interact or cause any issues downstream. A warning is probably enough in these cases to at least raise awareness?
Output the dependency graph as .json or .dot. The file would contain a list of nodes (with a path to the manifest or root for each fetched dependency), and a list of edges that describe the dependencies between each node.


CTA page fixes

Major content and image changes to the CTA page

Tugboat has finished building the preview for this pull request!
Link:

https://pr182-k54xqkoepqeisee2zcedxigevsqeyhkq.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6103c061378c5fd4877359e8

Tugboat has finished building the preview for this pull request!
Link:

https://pr182-k54xqkoepqeisee2zcedxigevsqeyhkq.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6103c061378c5fd4877359e8

Tugboat has finished building the preview for this pull request!
Link:

https://pr182-k54xqkoepqeisee2zcedxigevsqeyhkq.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6103c061378c5fd4877359e8

Tugboat has finished building the preview for this pull request!
Link:

https://pr182-k54xqkoepqeisee2zcedxigevsqeyhkq.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/6103c061378c5fd4877359e8


Having a pyproject.toml will break diagnosticSeverityOverrides in settings.json

Diagnostic severity overrides in user settings or workspace settings are ignored if the workspace also contains a pyproject.toml.
Environment data
Pylance v2024.6.101
Repro Steps

open an empty folder in VSCode
create a .vscode/settings.json file with the following contents{
    "python.analysis.diagnosticSeverityOverrides": {
        "reportUnknownParameterType": "warning"
    }
}

create a test.py file with contents:def test(x): ...

create an empty pyproject.toml file

Expected behavior

Actual behavior
No error or warning is reported.

Deleting pyproject.toml will fix the issue.
The same behavior applies to user settings.
This issue is not present in the current release version of pylance (2024.6.1).

thanks for reporting! I can repro in 6.101 & 6.102

This issue has been fixed in prerelease version 2024.6.103, which we've just released. You can find the changelog here: CHANGELOG.md


Bug fix in SamePadding that pad_width and pad_height are misplaced

Issue #, if available:
Pad_width and pad_height are misplaced. It may cause the following conv layer's output has a different size when stride param of SamePadding is a tuple and stride[0] != stride[1].
Description of changes:
swap the pad_width and pad_height.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-438-1 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-438/1/index.html

@zhreshold Can you take a look at this PR?

Thanks for your contribution!


Azure maintenance, edgedb failed to reconnect to backend Postgres db

EdgeDB Version: {'4.2+9856f3d'}
EdgeDB CLI Version: EdgeDB CLI 4.0.2+80e48a7
OS Version: node:18-bullseye-slim (base image)

Steps to Reproduce:

Deployed to azure following edgedb guide https://www.edgedb.com/docs/guides/deployment/azure_flexibleserver
Azure had a maintenance event where the backing Postgres server was brought down and back up.
Edgedb container failed to reconnect to the backing Postgres server when it was made available again. With the error:

ERROR 14 2023-12-03T06:29:41.248 edb.server: Connection to the system database is closed.
---- Exception occurred: could not create directory "pg_tblspc/16386/PG_15_202209061/31817": No such file or directory ----

1. edb.server.pgcon.errors.BackendError: could not create directory "pg_tblspc/16386/PG_15_202209061/31817": No such file or directory

---- Traceback ----

    /usr/lib/x86_64-linux-gnu/edgedb-server-4/lib/python3.11/site-packages/edb/server/tenant.py, line 585, in _reconnect_sys_pgcon
        > conn = await self._pg_connect(defines.EDGEDB_SYSTEM_DB)
    /usr/lib/x86_64-linux-gnu/edgedb-server-4/lib/python3.11/site-packages/edb/server/tenant.py, line 438, in _pg_connect
        > rv = await pgcon.connect(
    edb/server/pgcon/pgcon.pyx, line 385, in connect

    edb/server/pgcon/pgcon.pyx, line 1580, in sql_execute

    edb/server/pgcon/pgcon.pyx, line 1566, in _sql_execute

edb.server.pgcon.errors.BackendError: could not create directory "pg_tblspc/16386/PG_15_202209061/31817": No such file or directory
ERROR 14 2023-12-03T06:31:06.628 asyncio: Task exception was never retrieved
future: <Task finished name='Task-3225' coro=<Tenant._reconnect_sys_pgcon() done, defined at /usr/lib/x86_64-linux-gnu/edgedb-server-4/lib/python3.11/site-packages/edb/server/tenant.py:580> exception=BackendError('could not create directory "pg_tblspc/16386/PG_15_202209061/31817": No such file or directory')>

The error shown from the application container where edgedb cli tool is installed was:
edgedb error: BackendUnavailableError: cannot fetch database version: Postgres is not available: terminating connection due to administrator command
  Server traceback:
      Traceback (most recent call last):
        File "edb/server/protocol/binary.pyx", line 959, in edb.server.protocol.binary.EdgeConnection.main_step
        File "edb/server/protocol/binary.pyx", line 910, in execute
        File "edb/server/protocol/binary.pyx", line 704, in _execute
        File "edb/server/protocol/frontend.pyx", line 133, in get_pgcon
        File "edb/server/protocol/frontend.pyx", line 127, in edb.server.protocol.frontend.FrontendConnection.get_pgcon
        File "/usr/lib/x86_64-linux-gnu/edgedb-server-4/lib/python3.11/site-packages/edb/server/tenant.py", line 661, in acquire_pgcon
          raise errors.BackendUnavailableError(
      edb.errors.BackendUnavailableError: Postgres is not available: terminating connection due to administrator command

The maintenance event from azure details are below:

The issue was fixed at the time by restarting the edgedb container.
The expectation is that edgedb should be able to gracefully handful a similar maintenance event and reconnect automatically when the backing Postgres database becomes re-available.

@fantix, it seems we are giving up on attempt to reconnect the the backend too easily:
https://github.com/edgedb/edgedb/blob/7601ba076c4e0ef810f6239a7b0238f6a4b6e056/edb/server/tenant.py#L618-L624
Is there a reason why we are not retrying on all backend errors?

I think the reason was to rely on a failover event, but it doesn't make much sense to me now. The conditions here are fine, I'll change the raise below into a log for backend errors that we don't recognize, so that the retry loop can go on.