Add new hub breakpoints

Description
This PR adds the new breakpoints to the config. This also adds the new and existing breakpoints under new names using the name format screen-{width in pixels}.
This format is an improvement over the original format because:

It's more scalable. With the old format, adding a new breakpoint in between breakpoints meant the other breakpoints would have to be renamed in both the config and the code. Now it's just the screen and width number.
It's more readable. When looking at class names, it's easier to understand what screen size the breakpoint is for. Compare screen-875:flex to xl:flex. You would need to look at breakpoints.js to know what xl is if you didn't memorize it.

I've left the old breakpoint names so we can refactor existing usages in future PRs.

@liaprins-czi I added you as a reviewer in case you want to take a look at the breakpoints and verify I got everything 😄

Honestly idk about this one. While on one hand it's easier to add new breakpoints, on the other, it makes it significantly more difficult to adjust breakpoint values. For example, on napari.dev, we realized that one of the tablet breakpoints should be moved up to kick in at smaller widths since at some point the buttons started looking too wide.
If we were to rename these to be a bit less confusing, I would group them based upon what device we're targeting (at least for <1150px), e.g. phone-sm, tablet-md, etc. This naming would be based on how the breakpoints align with commonly used devices' screen sizes, e.g. an iPhone XR would fall under the phone-md size in portrait mode and phone-xl or tablet-xs in landscape mode. I don't think that being unable to see the pixel widths associated with each breakpoint is that big a deal, since you can always check it by hovering over the class name in your IDE.

Thank you for the feedback @kne42! This one definitely had me thinking 😆 Naming things really is the hardest to do in CS.

it makes it significantly more difficult to adjust breakpoint values.

Thank you for calling this out. I did a comparison and it seems both approaches have costs. It depends on what kind of changes we're making:
1. Adding a new breakpoint for a specific component
screen-<size>
This approach is better because all it takes is adding a new screen to the breakpoint config and adding it to the component.
Example:

Commit adding breakpoint and usage: https://github.com/chanzuckerberg/napari-hub/commit/2a1102f552131b65f6bfb90809c4c6832445e662

<device>-<size>
This approach isn't great because it may require us to shift existing breakpoints and also update previous usages to those shifted breakpoints.
Example:

Commit to add breakpoint. Notice how we have to shift the other ones: https://github.com/chanzuckerberg/napari-hub/commit/5bb78afc2a81b8f78e707979daf65ea0f80e5607
Commit to fix previous usages. After shifting, we now have need to update all the previous usages: https://github.com/chanzuckerberg/napari-hub/commit/b747004480e2d30d6be3c5e4cbc0d83e4d467a49

2. Modifying an existing breakpoint
screen-<size>
This approach isn't great because you need to update all the usages to the different screen size, much like the other approach when adding a new breakpoint:
Example:

Commit for modifying existing breakpoints to a new screen: https://github.com/chanzuckerberg/napari-hub/commit/3f37db36765b6833ab10f218b8bf9a1f6f8eac7a

<device>-<size>
This approach is better because it's a one line change:
Example:

https://github.com/chanzuckerberg/napari-hub/commit/22575058f087bc1e5f27136a8fc4ab674e9784a2

I would group them based upon what device we're targeting

I'm not too keen on naming things based on devices because breakpoints should be based on content. Although I know there are device names in the Figma, the non-standard device breakpoints lead me to believe that it was designed based on the content.

I don't think that being unable to see the pixel widths associated with each breakpoint is that big a deal, since you can always check it by hovering over the class name in your IDE.

Editors without Tailwind plugins and PR reviewers won't be able to hover to see the breakpoint value. Although, we should probably encourage folks to use VSCode when contributing for the best dev experience.

Ultimately this appears to be a decision based on which approach will be doing more as we add more content to the website: will be adding new breakpoints, or will we be modifying existing breakpoints?
So far we've only added new breakpoints, so I've tried optimizing for the former. But based on what you're saying, we may have to do the latter. But we can't do both unfortunately I'm missing something 😢

For example, on napari.dev, we realized that one of the tablet breakpoints should be moved up to kick in at smaller widths since at some point the buttons started looking too wide.

Also keep in mind that with this approach, modifying a single breakpoint may have unintentional ripple effects. It may fix the buttons when it's looking too wide, but what about other components using the same breakpoint? What if it breaks another part of the UI? Then again, this isn't necessarily a bad thing either if those ripple effects are accounted for.

Also how would you would feel about staying consistent with Tailwind's approach and just incrementing the xl number? lol:
module.exports = {
  // Special screen size for fresnel when using `lessThan` queries.
  zero: 0,
  xs: 300,
  sm: 375,
  md: 400,
  lg: 495,
  xl: 550,
  '2xl': 560,
  '3xl': 600,
  '4xl': 655,
  '5xl': 725,
  '6xl': 875,
  '7xl': 1150,
  '8xl': 1425,
};

Also how would you would feel about staying consistent with Tailwind's approach and just incrementing the xl number? lol:
module.exports = {
  // Special screen size for fresnel when using `lessThan` queries.
  zero: 0,
  xs: 300,
  sm: 375,
  md: 400,
  lg: 495,
  xl: 550,
  '2xl': 560,
  '3xl': 600,
  '4xl': 655,
  '5xl': 725,
  '6xl': 875,
  '7xl': 1150,
  '8xl': 1425,
};

Not a fan of this whatsoever; using an {n}xl naming convention with this many values is just an eyesore (a confusing one at that). I think that the name should actually be representative of how big something's going to be: xl to 2xl is only a 10px difference and yet it might make you think it's 100+.

also @liaprins-czi it would be great to get your opinion on this:

Ultimately this appears to be a decision based on which approach will be doing more as we add more content to the website: will be adding new breakpoints, or will we be modifying existing breakpoints?

That article you linked about tying things to devices and the other arguments/examples you've made are very convincing, so I've changed my mind and am now in favor of your screen-{width} approach.

Thank you! If this bites us back somehow in the future, pls point all your fingers at me 👉 🧑💻 👈

I'm not too keen on naming things based on devices because breakpoints should be based on content. Although I know there are device names in the Figma, the non-standard device breakpoints lead me to believe that it was designed based on the content.

Yes I agree with this in terms of the fact that the breakpoints are determined by the content: I just show what the design would look like on three of the most-differentiated screen sizes when I am iterating / exploring design ideas, and then show them in those sizes for the final designs.
However, if it easier for you all to have the naming conventions for the breakpoints be based on devices, that is fine with me and totally up to you! One thing to keep in mind is that the breakpoints that the landing page has that the plugin page does not have (currently 560px, 655px, and 725px) were added solely to account for the way the headline + illustration + bulleted text responds to screen width changing. This means a couple of things:

You could consider naming them for their function, i.e. title-3-lines for the 655px breakpoint, since that is the point of that breakpoint existing: when the headline goes to 3 lines that is when the styles for that breakpoint should enact. Again, i have no skin in the game in terms of how the breakpoints are named since I will not be referencing them or using them like you, so this is just an idea, in case it is helpful!
Very relatedly:

Ultimately this appears to be a decision based on which approach we will be doing more as we add more content to the website: will be adding new breakpoints, or will we be modifying existing breakpoints?
At this point for v0 the designs should not be changing at the point of adding new breakpoints, but like Kira said there might be small changes especially / likely exclusively for those breakpoints that occur only on the landing page (currently 560px, 655px, and 725px). These might change because they are set depending upon when certain functional thresholds are met (i.e. when the number of lines per bullet point change), and it might be that this is at a slightly different pixel-width in the HTML / the way it renders than it was on my Figma when I was doing the resizing there.

One other thing: Lucy just updated the text of the middle bullet to be shorter, now it is Install into napari with confidence.  I have updated the designs, and for now not changing the breakpoint widths! But if this makes it look really weird at certain screenwidth, we may want to adjust the point at which the (currently) 725px breakpoint occurs. This will not mean adding any new breakpoints, though!!!
Hopefully that helps! Please let me know if any questions or concerns
(And also this is assuming the font we are using loads properly, if it falls back to a different font then this would technically happen at a different screen width, but that is fine! They will still be able to read it even in different font and different / slightly wonkier layout.)

You could consider naming them for their function

I like this idea, I'm open to revisiting how we name breakpoints in the future when we're not feature churning. It would be great if we can establish a global set of breakpoints and then name them using the standard (xs, sm, md, etc.). And then breakpoints for specific features can be named based on function as you mentioned.

there might be small changes

Then it'll definitely take a bit more tedious effort to rename everything if we, for example, change a breakpoint to screen-725 to something like screen-700. Until we figure out a naming scheme, let's stick with this approach for now


ExperimentalWarning: buffer.File is an experimental feature and might change at any time

Bug report

[x] I confirm this is a bug with Supabase, not with my own application.
[x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
Looks like uploadOrUpdate is triggering ExperimentalWarning error.
ERROR	(node:8) ExperimentalWarning: buffer.File is an experimental feature and might change at any time
    at emitExperimentalWarning (node:internal/util:274:11)
    at new File (node:internal/file:40:5)
    at makeEntry (node:internal/deps/undici/undici:4366:44)
    at _FormData.append (node:internal/deps/undici/undici:4258:23)
    at StorageFileApi.<anonymous> (/var/task/index.js:146080:20)
    at Generator.next (<anonymous>)
    at /var/task/index.js:146037:71
    at new Promise (<anonymous>)
    at __awaiter2 (/var/task/index.js:146019:14)
    at StorageFileApi.uploadOrUpdate (/var/task/index.js:146072:16)

To Reproduce
  const responds = client.from(l`bucketName`).upload(
    path,
    new Blob([JSON.stringify(data)], {
      type: "application/json",
    }),
    {
      upsert: true,
    }
  );

System information

Version of supabase-js: [2.5.5]
Version of Node.js: [18.19.2]

Hi @fenos, could you take a look? Any ways to mitigate this warning?

Running into this same problem here. Only direct usage of storage-js in our codebase is importing a FileObject type
Error message on our end appears consistent with the one originally mentioned
import { FileObject } from '@supabase/storage-js';

Is there any resolution? @thorwebdev


v2.0.0

Adds support for PHP7 (up to 7.2) and the MongoDB library for PHP. Updates tests accordingly.

Thanks!


Build Error Ember 2.12.3

Adding ember-cli-swiper within an addon instead of an app we are receiving a build error - Cannot read 'import' of undefined located in ember-cli-swiper index.js on line 38.

Please include steps to reproduce and example code to debug.


Improve backspace behavior when cursor is at the beginning of a node

Expected Behavior:

If a node is indented, hitting backspace once should outdent it once. (When we support more levels of indenting, each time they hit backspace it would be outdented once.)
If the user hits backspace again, the node contents should be moved up to the previous line, at the end of the node above.

Actual behavior:
Nothing happens when you try to backspace at the beginning of a node.
FYI, Tana doesn't do #1, but it feels natural to me. Let me know if you disagree.
Video of Tana:
https://recordit.co/EXoN4cDXHA

see commit message for specific changes to verify


Secretary needs start/stop/send/redact options

Redacting messages have been addressed with a5728acf
not sure what you mean by start/stop. Could you elaborate?

There has to be a start and end point for meetings.
Only contributions posted between the start and end form part of the official record of a meeting.
Also I would expect start to be the point at which attendance starts to be collected. Only people present during a meeting count towards quorum.

AIUI the quorum is only required for beginning the meeting, so an end point I think is moot.
As for the start point, I'm asking around for suggestions on what would be a good fit.

AIUI the meeting has to start before quorum can be assessed.
The meeting can only proceed beyond a certain point once quorum has been reached.
There has to be an end point; further posts must not be included in the meeting report.


could not find "Matrix6d"

I encountered some problems when compiling the source code. Can you open the complete compilation project。
for example, i could not find "Matrix6d".

You may add
typedef Matrix<double, 6, 6> Matrix6d;
in the head of QuaternionFilter.h

I encountered some problems when compiling the source code. Can you open the complete compilation project。 for example, i could not find "Matrix6d".

You may add
typedef Matrix<double, 6, 6> Matrix6d;
in the head of QuaternionFilter.h
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: @.>
发送时间: 2022年11月26日 16:44
收件人: @.>
抄送: @.***>
主题: [chuanstudyup/MPU9250] could not find "Matrix6d" (Issue #1)
I encountered some problems when compiling the source code. Can you open the complete compilation project。
for example, i could not find "Matrix6d".
―
Reply to this email directly, view it on GitHubhttps://github.com/chuanstudyup/MPU9250/issues/1, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMKQNKPVLHE3IOWR3JJS57LWKHEWJANCNFSM6AAAAAASL4SEGA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Indicate if the network drive is disconnected by updating its icon

This is an additional feature request that I mentioned here: #1100 Just to track them separately
Current icon for a disconnected network drive:

Proposal:

currently this is already indicated with the system icons


chore(web): better panic

Checklist

[x] Confirmed that run-checks all script has been executed.
[x] Made sure the book is up to date with changes in this PR.

Related Issues/PRs
Changes
Provides better panic support on web to help debug issues like #1034

You might consider using start. I do so here.

here

Done! I considered it, but we already had a start point so thought that'd be fine. Updated to be more proper.

@antimora @nathanielsimard should be good to go now!


Update submodule 'lib/websocketpp' to the latest version

This fixes a bunch of build errors between boost 1.69.0 and websocketpp component.

Included in https://github.com/socketio/socket.io-client-cpp/commit/af68bf3067ab45dc6a53261284e0da9afd21b636. Thanks a lot for the pull request.

Included in https://github.com/socketio/socket.io-client-cpp/commit/af68bf3067ab45dc6a53261284e0da9afd21b636. Thanks a lot for the pull request.


Will ELMAH be ported to ASP.NET Core?

I'm having a hard time finding information about this. I realize there is cloud-based elmah.io project (https://elmah.io/) that is has a beta out for .NET Core, but that's a different project and in no way affiliated with ELMAH (at least I think it is)...
any info you could provide would be helpful.

I realize there is cloud-based elmah.io project…but that's a different project and in no way affiliated with ELMAH (at least I think it is)...

That's correct. It's a completely different project run by @ThomasArdal.

Will ELMAH be ported to ASP.NET Core?

It's more of an “if & when time permits” than a definite “no”. If it depends entirely on me then I'm afraid for you that it'll be on my agenda and when I'm ready to ship my first ASP.NET Core project. If some people have already jumped on that bandwagon, well-versed in ASP.NET Core, care about backward compatibility & would like to help make it happen sooner then it could.

@mgmccarthy I'm Thomas, the founder of elmah.io and as @atifaziz says, it's a different project with what turned out as a bad naming choice.
I have promissed Atif to look at ELMAH for ASP.NET Core. I decided to implement the beta for elmah.io first, to find out how middleware are implemented for ASP.NET Core. I feel that the implementation is in pretty good shape right now and I would love to merge the implementation back to the ELMAH project.
@atifaziz Would you mind taking a look at the implementation for Elmah.Io.AspNetCore and share if you would want some of the code. Maybe just for inspiration. I know there's an OWIN branch on ELMAH, but I guess that one were never actually ported to Core, right?

@ThomasArdal Thanks for sharing that Thomas but it's only a very small piece (posting an error) of the entire feature set and so the bulk of the work (UI, mailing, authorisation, log stores, refactoring of code & packages, testability, etc.) is still pending requires a fair amount of time.

I know there's an OWIN branch on ELMAH, but I guess that one were never actually ported to Core, right?

Correct.

@atifaziz I know 😄 Should we create a new branch for core or do you want to continue the work on the owin branch?

A new branch on top of the owin one probably makes sense but before that, I think that the existing repo needs to be refactored into different ones: one for the core bits and then separate ones for the error log implementations so each can have its own issues, versions and release cycles. Then merge that structure into the OWIN version and then start the ASP.NET Core port. That's just thinking from the top of my head.

On 14 Oct 2016, at 07:14, Thomas Ardal<EMAIL_ADDRESS>wrote:
@atifaziz I know 😄 Should we create a new branch for core or do you want to continue the work on the owin branch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@atifaziz I'm not sure about the state of the OWIN branch. Would it make sense to create a 2.0 branch from master and make the split there? Then pick the changes from the owin branch that makes sense for core and put them into the 2.0 branch? Or do you believe that the owin branch is in a state where we could build 2.0 from that?

@ThomasArdal master represents the latest development, which is already 2.0.

@atifaziz Ok. Is ELMAH on the owin branch still based on modules? Was looking into creating middleware for core instead.

@ThomasArdal ASP.NET Core borrows the ideas of middleware from OWIN. In fact, it even [supports OWIN middleware][aspnetcore-owin]. So naturally the owin branch isn't based on modules. Have a look at Owin.cs where most of the attempt was done & works to a very large extent. See the following extension methods that setup the middleware in the pipeline via IAppBuilder:

UseElmahWeb
UseElmahLogging
UseElmahMailing

I mostly stopped working on all this when I found out that ASP.NET vNext (at the time) wasn't going to be based on OWIN. Wanted the let the dust settle down.

@atifaziz Makes sense. I will have a look at porting the OWIN middleware to ASP.NET Core middleware when time allows. Thanks.

Is the release date for elmah .net core planned :)

@milla See my earlier comment:

If it depends entirely on me then I'm afraid for you that it'll be on my agenda and when I'm ready to ship my first ASP.NET Core project. If some people have already jumped on that bandwagon, well-versed in ASP.NET Core, care about backward compatibility & would like to help make it happen sooner then it could.

@ThomasArdal any progress made on porting the OWIN middleware to ASP.NET Core middleware?
I'd like to jump in and help, but I'm currently using most of my free time on another open source project which I would like to use ELMAH on.

@mgmccarthy No :( Haven't had time to look at it either.

the existing repo needs to be refactored into different ones: one for the core bits and then separate ones for the error log implementations so each can have its own issues, versions and release cycles.

This was done in #418.

I don't know why Microsoft doesn't pick this up. This library is the main reason I don't use .net core (System.DirectoryServices is another, but that is coming out in core 2.1).

@frattaro  This is exactly my case too. I can't afford the subscription for elmah.io :(


unable to find optional library org.apache.http.legacy

are you trying to compile soulissapp ?

closed with Zozzariello removal


Handle a typeof TypeQuery

Fixes https://github.com/Kotlin/ts2kt/issues/92

Let's discuss. It seems to me that in this particular case we can try to go further and substitute typeof Something with just Something.

I love that idea.  Are there cases where we don't actually have access to know what type the variable is?
How about this change be accepted for now since it does better than simply failing and skipping the var completely?


[network-data] remove all matching entries from RemoveRloc methods

This commit makes changes to ensure the Leader::RemoveRloc methods
remove all matching entries from a BorderRouterTlv or HasRouteTlv
It adds new methods to BorderRouterTlv and HasRouteTlv to get the
first entry or last entry and allow an easier way to iterate over all
the entries.
This commit also adds a new helper method RlocMatch() to simplify
the comparison of RLOC16 values (exact match vs router id match).

PR https://github.com/openthread/openthread/pull/2905 helped fix the issue to clean a child-added network data when its parent is removed. This PR address a related issue where if there were multiple matching entries, only the first one would have been removed (we would break from the loop going over entries upon finding a match).

This fixes how we remove multiple "matching" entries. It's correct that if we do an exact match, there should be only one entry per RLOC. This issue applies when the relaxed definition of matching (i.e., aExactMatch=false where router ID is checked) is used.
A parent router node and its child can both register the same on-mesh prefix. If the parent is gone, when we perform a remove we should ensure to remove both entries (which would be under the same BorderRouterTLv). In the original code, after a match we would break and not continue to seach and would not remove the child entry.
I have a pending toranj test-case creating this situation which currently fails on master but passes with this change. Will submit it as a new PR after some code clean up.

Thanks for the clarification - that makes sense now. I think we could do a better job clarifying "Match". For example, Router ID vs. RLOC16.
I also think we should transition to a policy where tests are included in to the PR to help demonstrate that the PR actually fixes the bug.
Thoughts?

I agree. Suggest replacing the bool aExactMatch with an enum MatchMode definition (say kRloc16Match, kRouterIdMatch) and change all the code to use this instead. Perhaps a future improvement.
I like the policy of requiring tests along with the change. It'd be good to keep commits separate (to help with cherry-picking of fix without the test).
Will clean up the test and add it to this PR.

Pushed a new commit on this PR which adds a toranj test case:
 Network topology

   r1 ----- r2
            |
            |
            c2 (sleepy)

Test covers the following steps:

Every node adds a unique on-mesh prefix.
Every node also adds a common on-mesh prefix (with different flags).
Verify that all the unique and common prefixes are present on all nodes are associated with correct RLOC16.
Remove r2 from network (which removes c2 as well) from Thread partition created by r1.
Verify that all on-mesh prefixes added by r2 or c2 (unique and common) are removed on r1.


pwm: mcpwm: esp32c6: Add support

Add MCPWM support to ESP32C6

some small adjustment, sorry
should be ready for review now


Retina Gravatar

Would you accept a PR that adds a retina=true attribute and then proceeds to fetch a 2x Gravatar of the requested display size?

Of course! That'd be awesome!


Ionic 2 CLI

I am having issues with the emulator, run works fine so does the emulator on its own but when I try to add in some other options like so:
ionic emulate ios --livereload --consolelogs --serverlogs --target='iPhone-6'
I get issues as though it is just serving the app:
[18:02:02]  console.warn: Native: tried calling StatusBar.styleDefault, but Cordova is not available. Make sure to
include cordova.js or run in a device/simulator
[18:02:02]  console.warn: Native: tried calling Splashscreen.hide, but Cordova is not available. Make sure to include
cordova.js or run in a device/simulator
I have tried to delete the build and then re-add from the start but still the cordova.js file is missing!
ionic -v: 2.1.12
node -v: v6.7.0
npm -v: 3.10.6
Any help would be great as I cant test anything if cordova and livereload arent able to work together.

Can you try updating to the latest CLI release?
npm install -g ionic@latest

Just did it there.. heres my ionic info:
    Cordova CLI: 6.4.0
    Ionic Framework Version: 2.0.0-rc.3
    Ionic CLI Version: 2.1.17
    Ionic App Lib Version: 2.1.7
    Ionic App Scripts Version: 0.0.45
    ios-deploy version: 1.9.0
    ios-sim version: 5.0.8
    OS: macOS Sierra
    Node Version: v6.7.0
    Xcode version: Xcode 8.1 Build version 8B62

the command i executed was:
    ionic emulate ios --livereload --consolelogs --serverlogs

and I still get the missing cordova console errors:
    console.warn: Native: tried calling StatusBar.backgroundColorByHexString, but Cordova is not available. Make sure to include cordova.js or run in a device/simulator
    [17:22:27]  console.warn: Native: tried calling Splashscreen.hide, but Cordova is

Running into the same, using ionic emulate ios -lcs --target iPhone-6s. Without the -lcs the app runs. With -lcs I get just a black screen and this in the console...
[14:35:12]  error opening ws message: {"category":"console","type":"info","data":["Ionic Storage
            driver:","asyncStorage"]}
[14:35:12]  console.warn: Native: tried calling StatusBar.styleDefault, but Cordova is not available. Make sure to include cordova.js or run in a device/simulator
[14:35:12]  console.warn: Native: tried calling Splashscreen.hide, but Cordova is not available. Make sure to include cordova.js or run in a device/simulator
[14:35:13]  console.warn: Native: tried accessing the Network plugin but Cordova is not available. Make sure to include cordova.js or run in a device/simulator

Side note: I noticed @REPTILEHAUS uses --target='iPhone-6'. For me, using = or ' or " always results in a simulator not found. Not sure what the correct syntax is/should be.

+1


Add release notes for 2.12.0 release

Description
Add release notes for 2.12.0 release
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Will raise manual backports


Missing toggleEnabled

I was looking though the code and noticed that this function is gone but still called. For example,
https://github.com/nccgroup/tracy/blob/646976adbc24bc4947a1e459a3624f30757594f6/plugin/scripts/highlight.js#L67
Should we remove these calls?

Yes, we should. I have been meaning to do that for a while now.


Some VM series/size lack of cache size in GiB

Hi team,
I am asking on behalf of our customer. They believe some of the VM series are lacking the size of the host cache in GiB. For example, Esv3-series has the cache size in GiB:

And this value is missing for Edsv5-series:

Are we going to optimize our document with more detailed and accurate information?

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

ID: a3950928-1977-9c38-3289-79fd011058f3
Version Independent ID: b349d902-2b31-b303-6313-020da737a901
Content: Ebdsv5 and Ebsv5 series - Azure Virtual Machines
Content Source: articles/virtual-machines/ebdsv5-ebsv5-series.md
Service: virtual-machines
Sub-service: sizes
GitHub Login: @priyashan-19
Microsoft Alias: priyashan

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

@GlenGengMicrosoft
Please follow up on this GitHub case related to cache size in GiB document update, which is a duplicate of https://github.com/MicrosoftDocs/azure-docs/issues/118732.

Checking back on this. This doesn't appear to be resolved. Ebds_v5 supports caching but the entire cached specs column is missing. Form the MS doc: https://learn.microsoft.com/en-us/azure/virtual-machines/disks-performance it says to refer the VM Size to determine a VM Size cached limits. The column is missing from the Ebds_v5 sizes to determine cached limits.


Not detecting beacons from wish.com emails.

Does not detect email beacons sent by wish.com in their emails.
<img id="email-beacon" src="http://www.wish.com/email-beacon.png?utm_campaign=2021-02-22_SHIPMENT_CONFIRMATION_<removed>&uuid=<removed>&cmpgnid=2021-02-22_SHIPMENT_CONFIRMATION_<removed>&ee=v1_2LaP22BArxLeSQGig1coHQeyzqYnLareXp7HajXKqjeypKPutzp3H9881Dhaa2rYSNiER7p2dVHA&utm_source=SHIPMENT_CONFIRMATION&template=emails%252Fremix%252Fnotifications%252Ftransaction_item_status_update.html&recvuid=<removed>" height="1px" width="1px" />

Removed some ids above.
It seems to track that I've read the shipping status, but I don't care.

Just to double check, are you seeing:
A.  (no tracker detected)
or B.  (possible tracker detected)?

I'm seeing A: No tracker detected and when I click on the mark for information. The dialog is:

Thanks for your submission, this will be addressed.


Don't use 64-bit integers on 32-bit platforms

It should probably work to globally replace

uint64_t with size_t and
int64_t with ptrdiff_t (or preferably size_t as well unless signed integers are really required)

Oh, yes. It looks like we already use size_t inconsistently, and this is definitely something we should be more consistent about.
I can work on a fix for this in the next few days hopefully.
Thanks for pointing this is out!

I was able to eliminate uint64_t and nearly all uses of int64_t.
There was one function used in timsort that relies on signed arithmetic that I was not able to easily workaround. ptrdiff_t is not guaranteed to be big enough to hold most size_t (i.e., ptrdiff_t might be 32 bits, since it is related to pointers and not memory size), so I had to keep int64_t in that one function.

On 32-bit systems, ptrdiff_t should be the same as int32_t and this can be a problem with char arrays that have more than 2G elements. If sort.h is supposed to work with such arrays, you really need 64-bit integers or some other workaround. But a 2G char array would typically be sorted with counting sort.
The C standard also doesn't guarantee that ptrdiff_t has at least as many bits as size_t, but I don't think there's a platform where this doesn't hold true. Unfortunately, C89 doesn't require SIZE_MAX and PTRDIFF_MAX. The following compile-time check works on every platform that provides a C99-conformant stdint.h:
#include <stdint.h>

#if defined(SIZE_MAX) && defined(PTRDIFF_MAX) && PTRDIFF_MAX < SIZE_MAX / 2
  #error Unexpected size of ptrdiff_t
#endif

(For C++ you'd need std::numeric_limits.)


Not working for personal (Live) Microsoft accounts.

Tenant restrictions mechanism is not working for personal (Live) Microsoft accounts.
This defeats the whole purpose of the mechanism.
Users in companies that want to restrict O365 exclusively to the corporate tenant, can still access their uncontrolled personal mailboxes and onedrives.

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

ID: 89ea5c2d-4602-25b8-3cdd-60cfb5c31895
Version Independent ID: 35d4af7e-72e4-7c40-9dd6-b8490ee73f0d
Content: Manage access to cloud apps by restricting tenants - Azure
Content Source: articles/active-directory/manage-apps/tenant-restrictions.md
Service: active-directory
GitHub Login: @barbkess
Microsoft Alias: barbkess

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

@BartJocque Please note that Tenant Restriction is an Azure Active Directory feature for SaaS applications for which the authentication request is coming to Azure AD URLs to authenticate: login.microsoftonline.com, login.microsoft.com, and login.windows.net. As stated in document, for each incoming request to login.microsoftonline.com, login.microsoft.com, and login.windows.net, insert two HTTP headers: Restrict-Access-To-Tenants and Restrict-Access-Context. Hence, if the request coming for any other tenant other than one part of Restrict-Access-To-Tenants, the login request will fail. So allowing access to co-operate tenant will help in that regard. If the request is coming for personal mailbox, where user account authentication attempt goes to some other tenant , then it will be blocked from login.
Further, you can look for option to restrict Office 365 to our corporate devices using Active Directory conditional access device policies for Office 365 services.

I fully understand that it has been designed like that,  but the personal live logins ( which can btw also be done through login.microsoft.com and login.microsoftonline.com) are a real backdoor for Tenant Restrictions.
You can supersecure the Corporate Tenant, but users can bypass all of this just by using their private accounts.
Also , I don't understand how conditional access would be applied to personal accounts ? Would that not be the same limitation as above.

@BartJocque Sorry but can you please further elaborate on it. If personal login request through login.microsoft.com and login.microsoftonline.com goes to different tenant, which is restricted, then it will not be authenticated. So I still need to understand in which scenario personal account authentication can still pass even through tenant restriction is in place.

one scenario is where a user logs in from the powerpoint 2016 or word 2016 app , the tenant restrictions feature is defeated. ( -> user can access his personal one drive ).

@BartJocque When user login through powerpoint 2016 or word 2016 app, the login request will go through ogin.microsoftonline.com and HTTP headers: Restrict-Access-To-Tenants and Restrict-Access-Context will be inserted.  This will take care that if login request is going to some other tenant it will fail. So if user is using personal login then authentication of it will fail as personal login account exists in another tenant which is not part of Restrict Tenant Access list.

Thanks for the feedback.
but that's not the behaviour what we are currently perceiving.
Will double check our setup and configurations and update you later.
tx.

I made a trace while reproducing the issue : logging to my personal O365 from within PowerPoint 2016.
First there was a connection to auth.gfx.com and then a redirect to login.live.com.
I think that the problem is that login.live.com does not enforce tenant restrictions ?

@BartJocque Thanks for added information. I see your point.
@barbkess Please let me if you can provide more information related to above query. Even with Tenant restriction the user will be able to open office apps using their personal Microsoft Account as authentication request will go through login.live.com.

@BartJocque I am still trying to get more information from our service team in this regard. I will update you on this issue as soon as I have more information to share.

@BartJocque As per update from our Service Team below is the information we got -

Hi,
Thanks for you answer.
I do understand that firewall and proxy policies are the primary means to block access to consumer services.
However, we have opened 0365 access as per MS recommendation ( https://support.content.office.net/en-us/static/O365IPAddresses.xml ) , and there is no distinction in that list between corporate and consumer services.
How can we know what services are needed for consumers and what services are needed for corporate access ?
We would expect you to publish that information. (e.g. one xml for corporate access and one xml for consumer access)
Kind regards
Bart

@BartJocque Please confirm if you already have support case open on this issue. If yes, that will be best place to further discuss this issue. We can also involve relevant service team contact in the support case.

@BartJocque Please continue to work with support case to further help you out on your scenario. This platform is to help customer ask queries as they use the Azure published documentation and provide there valuable inputs to improve it. We try our level best to help out, however, there are some feature limitations which could be surfaced through Product Feedback forums as well. Apart from creating document feedback , you can also use the "Give Product Feedback" button in our documents now which will take you directly to the appropriate product feedback page.
We will now move ahead and close this documentation feedback request.

@MohitGargMSFT @@barbkess
Solution is to block storage.live.com and d.docs.live.net

@BartJocque Great that you figured out the solution and many thanks for sharing with us. This will help us if another customer faces similar situation.


[Feature]: SQLTarget Record before Schema should fail nicely

Feature scope
Targets (data type handling, batching, SQL object generation, etc.)
Description
Should go on SQL Target milestone
https://github.com/MeltanoLabs/target-postgres/blob/main/target_postgres/tests/test_standard_target.py#L64 is the record_before_schema test
We should fail nicely, this test was taken from https://github.com/MeltanoLabs/target-sqlite/blob/master/tests/test_target_sqlite.py#L23-L32
We should probably do the validation in the SDK

Here's an example implementation https://github.com/MeltanoLabs/target-postgres/pull/57


Metric request error in 7.1.0

I'm still getting some metric request errors in 7.1.0. This query will do it:
from(bucket: "dns")
  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
  |> filter(fn: (r) => r["_measurement"] == "queries"
    and r["_field"] == "id"
    and r["tap_type"] == "CLIENT_RESPONSE"
    and r["status"] == "NXDOMAIN")
  |> group(columns: ["qname"])
  |> count()
  |> group()
  |> sort(columns: ["_value"], desc: true)
  |> yield(name: "count")

This query was copied from influxdb2/chronograf.

can you post an issue in:
https://github.com/grafana/grafana
please include sample output we can test with:
https://github.com/grafana/grafana/tree/master/pkg/tsdb/influxdb/flux/testdata


Introduce dartboard reapply

Convenience command to destroy and then apply again

LGTM, but maybe we add to the README or somewhere else with details on how reapply and redeploy are different?
Information that might be useful:

Possible side effects of reapply vs redeploy
When you might want to reapply instead of redeploy and vice versa

Completely agreed, addressed with  99f93e0


[RFC] Grammar for inverted operator.

In the recent issues (#968, #989) raised the need for inverted binary operators aka a binary operator where the right hand side parameter of the operator should be this.
I suggest the grammar:
class Foo {
  (rhs)op(this) { }
}

It is far from perfect, but it set a base for the discussion.
The aim is to provide a dedicated grammar for such operators, that don't collide with unary and binary operators. It also aims to help to reason and think about the code, because the inversion of operands is not an intuitive thing.
Examples of such operators are:
123 in [4, 5, 6] // where it should would act like: [4, 5, 6].contains(123)
"foo" ~~ "bar"   // where it should would act like: "bar".contains("foo") or RegExpt.new("bar").match("foo") or ...

Why not just op?

This is the same grammar as binary operator, and is confusing. The fact that operands are inverted make them hard to reason and think about, in particular when the grammar don't reflect that inversion.

Could an example be given of when this is useful in real life since those other two threads are super super long. :)

@joshgoebel mhermier put two in the OP.  E.g, for 123 in [4, 5, 6], you could implement the operator two ways:

123.in([4,5,6])
[4,5,6].contains(123)
In the former case, individual values have to know about the different types of containers.  In the latter case, containers only need to know about themselves.  I think the second approach is more cohesive, and would probably be easier to maintain.  Does that help?

(I have also noticed the GH issue interface is not ideal for long discussions :( )

I like the idea --- what about just (lhs)op?  E.g.,
class CustomContainer {
  (needle)in { /* find _needle_ in _this_ */ }
  +(elem) { /* append _elem_ to _this_ */ }
}

As far as I know, parentheses cannot be overridden in Wren :) , so the syntax would be unambiguous.  Since we already have implicit this when this is on the LHS, I think we could do it when this is on the RHS also.  What say you?

mhermier put two in the OP.

They were added after I requested a small example. :)  But yes it's all quite clear now what this feature would be useful for now. I see one small potential issue...
// object is a Bird and object2 is a Plane
object.relatedTo(object2)

Today just by looking at that code I can be certain that relatedTo exists and is a non-static member of the Bird class. So if I go digging into the source I know exactly where to look.  After adding this feature I can no longer be certain of this... I'd have to first look in Bird and then failing to find the method I'd have to go look for a RHS method in Plane...
I'm not sure this is resolvable or a major problem?... but it's a thought.  Perhaps a different syntax at the dispatch site could resolve this but then that might defeat the whole point of it appearing seamless.

@joshgoebel sorry for duplicating mhermier's effort :)
Fair point about "where is this defined?" --- the same concern exists in C++.  If I understand correctly, the scope of this proposal is operators, and you can't add new operators from a .wren file.  So object.relatedTo(_) would always be a method of object.
The Wren programmer would have to know that a+b was a.+(b) and a in b was b.contains(a).  However, the new syntax would make that clear.  We could also issue a helpful error message if someone tried to define in(_) but only (_)in was valid.

There is no such confusion op is a place holder for an operator not for a regular name. Therefore '.' lookup don't apply here, and don't change.
I don't thought much of the possibilites of that change. This is just an idea not thought much, but maybe we can have:
// object is a Bird and object2 is a Plane
object.relatedTo(object2) // The usual behavior
object relatedTo object2 // As an inverted operator

@mhermier true --- if we did allow custom-defined binary operators, (_)op vs. op(_) would be an easy way to assign which was which.  For custom-defined operators, we would have to figure out associativity.

There is a huge down side to allowing user defined operator:
   [a b, c, d, e]
//     ^ error will be cough here, complaining about missing right hand side of inverted operator here
//    ^ instead of here complaining about missing ','

@mhermier makes sense --- I think it's fine not to add user-defined operators at the moment.

User defined operators are one of the worst things invented, if not the worst.
Parsing them is a nightmare, and understanding them is even more. Can you tell what the <*> operator means? (Not a joke! IIRC I saw it in a F# codebase).

User defined operators are one of the worst things invented, if not the worst.

They are, even worse than un-sliced bread!
Scala anyone?
But, seriously, I do like @cxw42's syntax in https://github.com/wren-lang/wren/issues/1002#issuecomment-830859422 for dealing with inverted operators.

That syntax is nice, it would go in pair with current unary operator syntax, but here lies the problem I have with it. It doesn't emphasis the operator nature of the operator. Adding (this) in the signature explicit the nature without requiring the operator keyword.

That's a fair point.
I'd be happy with or without the (this) frankly.

The is also another argument, but I don't know if the grammar would allow them. How would we write an unary right operator signature?

How would we write an unary right operator signature?

Are you thinking about something like a++ if  we get compound assignment operators?

Yes, how would the signature look like in the method definition?

Well, I'm not sure whether the likes of a++ and a-- would be a good idea anyway as (in combination with the corresponding prefix operators) they're a can of worms even in C/C++.
It might be better to just go with a += 1 and a -= 1 instead.
If that were the case, then I think that any object which supported the + or - operators should automatically support += and -= with the appropriate meaning and that you shouldn't be able to override the compound assignment operators in isolation.
But to answer the question you posed, I guess you'd have to involvethis, perhaps:
(this)op { \\ ... }


An error occurred: module 'ffmpeg' has no attribute 'input'

I'm using subtitle on an mp4 file. Here's what I get:
python subtitle.py /path/to/file.mp4
Model base exists
file /path/to/file.mp4 data/42537cf8-b515-42ec-bfaa-779a2fe644f2.wav.vtt /path/to/file_subtitled.23
An error occurred: An error occurred: module 'ffmpeg' has no attribute 'input'
ERROR:root:An error occurred: cannot unpack non-iterable NoneType object

It seems subtitle didn't just want ffmpeg, but something else, or more specific. Yet - the README doesn't say so, and the subtitle.py doesn't fail immediately. It calls whisper, and only once that's done remembers that it needs things I don't have. And I don't even know how to provide it with the "input" attribute.

The code currently only works on Linux. If you are running it on Linux, try reinstalling the Python package or running it in a different environment. You can try:
pip install -r requirements.txt

The code currently only works on Linux.

I am running on Linux. But - if you thought that might not be the case, then maybe you should perform a platform check and warn if it's not Linux (or refuse to run even). Anyway, will try (re)installing the requirements as you suggest.

Use GitHub Codespaces. If the error persists, please let me know.

Use GitHub Codespaces.

I don't quite understand what you mean.

Ok, this worked for me:
Apparently, I had several modules installed:

ffpmeg
ffmpeg_input
ffmpeg-python

I removed all of them, and installed only ffpmeg-python. Then this error went away. @innovatorved : I really wish you'd do a bit more robust package-checking, to let the users know what they should or shouldn't have.


GPA - Exclude LM error

Hello Guys,
I encountered an error in the Slicer 5.4.0 version, respectively in the recent GPA module.
It is not possible to run GPA, when I want to exclude some LMs. See the error below - probably related to the updated numpy library
Traceback (most recent call last):
File "C:/Users/admin/AppData/Local/slicer.org/Slicer 5.4.0/slicer.org/Extensions-31938/SlicerMorph/lib/Slicer-5.4/qt-scripted-modules/GPA.py", line 1220, in onLoad
self.LMExclusionList=[np.int(x) for x in self.LMExclusionList]
File "C:/Users/admin/AppData/Local/slicer.org/Slicer 5.4.0/slicer.org/Extensions-31938/SlicerMorph/lib/Slicer-5.4/qt-scripted-modules/GPA.py", line 1220, in
self.LMExclusionList=[np.int(x) for x in self.LMExclusionList]
File "C:\Users\admin\AppData\Local\slicer.org\Slicer 5.4.0\lib\Python\Lib\site-packages\numpy_init_.py", line 313, in getattr
raise AttributeError(former_attrs[attr])
AttributeError: module 'numpy' has no attribute 'int'.
np.int was a deprecated alias for the builtin int. To avoid this error in existing code, use int by itself. Doing this will not modify any behavior and is safe. When replacing np.int, you may wish to use e.g. np.int64 or np.int32 to specify the precision. If you wish to review your current use, check the release note link for additional information.
The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:
https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations
Thank you for all the effort!

Looks like a numpy change that broke it. Thanks for reporting it.
@smeolfe

@smrolfe


Fix for intermittent test failure

Motivation and Context
Theres an intermittent bug in the case service tests where it gets stuck attempting to contact the IAC service wiremock. This only happened occasionally so its hard to test.
What has changed

Added classrule to the wiremock
Added a thread sleep to allow the wiremock to shutdown and wake up between tests.

How to test?

running mvn clean install and it passing. When testing this I had to run it constantly just in case it happened again, so you may need to keep running the tests just to be thorough. Only merge when confident you can't replicate the bug.

Hung on the second time too


Remove dependencies already prenset in IP BOM

all those deps are already in ip-bom:6.0.0.CR29
with exactly the same versions

@mbiarnes please take a look.

yepp - these deps are in jboss-ip-bom 6.0.0.CR30 too

Merged into master and 6.3.x


⚠ Bofrost.be has degraded performance

In b69b473, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1281 ms

Resolved: Bofrost.be performance has improved in 0030349 after 8 minutes.


Issue with Conan when compiling for ARMHF (arm32v7) with Focal (20.04)/GNU C++ v10 compiler

I get a compile crash when using Conan C++ Package Manager for architecture ARMHF (arm32v7) but same process successfully functions for amd64 and arm64 architectures. I am using the recently released Ubuntu Focal (20.04) and the repo versions of cmake, G++, openssl etc.
Output below is using cmake 3.16.3 but issue also occurs when I directly compile cmake 3.17.1. I'm using Conan branch 1.24 for the build process.
This may be down to the fact Focal uses G++ v10 whereas Eoan is G++ v9 - but I'm surprised if this issue is just occuring on the ARMHF build process.
`

ERROR [linux/arm/v7 stage1-build  8/15] RUN mkdir /home/nmos-cpp/Development/build &&     cd /home/nmos-cpp/Development/build &&     cmake     -G "Unix Makefiles"     -DCMAKE_BUILD_TYPE:S  19.6s

[linux/arm/v7 stage1-build  8/15] RUN mkdir /home/nmos-cpp/Development/build &&     cd /home/nmos-cpp/Development/build &&     cmake     -G "Unix Makefiles"     -DCMAKE_BUILD_TYPE:STRING="Release"     -DCMAKE_CONFIGURATION_TYPES:STRING="Release"     -DCXXFLAGS:STRING="-Os"     -build /home/nmos-cpp/Development/build .. &&     if [ -n "4" ]; then echo "Making multi-threaded with 4 jobs"; make -j4; else echo "Making single-threaded"; make; fi:
#52 0.426 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 0.426   list sub-command REMOVE_ITEM requires two or more arguments.
#52 0.426 Call Stack (most recent call first):
#52 0.426   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 0.426   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 0.426   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 0.426   /usr/share/cmake-3.16/Modules/CMakeDetermineCCompiler.cmake:116 (CMAKE_DETERMINE_COMPILER_ID)
#52 0.426   CMakeLists.txt:5 (project)
#52 0.426
#52 0.427
#52 0.718 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 0.718   list sub-command REMOVE_ITEM requires two or more arguments.
#52 0.718 Call Stack (most recent call first):
#52 0.718   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 0.718   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 0.718   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 0.718   /usr/share/cmake-3.16/Modules/CMakeDetermineCCompiler.cmake:116 (CMAKE_DETERMINE_COMPILER_ID)
#52 0.718   CMakeLists.txt:5 (project)
#52 0.718
#52 0.718
#52 1.003 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 1.003   list sub-command REMOVE_ITEM requires two or more arguments.
#52 1.003 Call Stack (most recent call first):
#52 1.003   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 1.003   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 1.003   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 1.003   /usr/share/cmake-3.16/Modules/CMakeDetermineCCompiler.cmake:116 (CMAKE_DETERMINE_COMPILER_ID)
#52 1.003   CMakeLists.txt:5 (project)
#52 1.003
#52 1.003
#52 1.295 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 1.295   list sub-command REMOVE_ITEM requires two or more arguments.
#52 1.295 Call Stack (most recent call first):
#52 1.295   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 1.295   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 1.295   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 1.295   /usr/share/cmake-3.16/Modules/CMakeDetermineCCompiler.cmake:116 (CMAKE_DETERMINE_COMPILER_ID)
#52 1.295   CMakeLists.txt:5 (project)
#52 1.295
#52 1.295
#52 1.579 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 1.579   list sub-command REMOVE_ITEM requires two or more arguments.
#52 1.579 Call Stack (most recent call first):
#52 1.579   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 1.579   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 1.579   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 1.579   /usr/share/cmake-3.16/Modules/CMakeDetermineCCompiler.cmake:116 (CMAKE_DETERMINE_COMPILER_ID)
#52 1.579   CMakeLists.txt:5 (project)
#52 1.579
#52 1.579
#52 1.684 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 1.684   list sub-command REMOVE_ITEM requires two or more arguments.
#52 1.684 Call Stack (most recent call first):
#52 1.684   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 1.684   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 1.684   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 1.684   /usr/share/cmake-3.16/Modules/CMakeDetermineCCompiler.cmake:116 (CMAKE_DETERMINE_COMPILER_ID)
#52 1.684   CMakeLists.txt:5 (project)
#52 1.684
#52 1.684
#52 1.969 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 1.969   list sub-command REMOVE_ITEM requires two or more arguments.
#52 1.969 Call Stack (most recent call first):
#52 1.969   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 1.969   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 1.969   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 1.969   /usr/share/cmake-3.16/Modules/CMakeDetermineCCompiler.cmake:116 (CMAKE_DETERMINE_COMPILER_ID)
#52 1.969   CMakeLists.txt:5 (project)
#52 1.969
#52 1.970
#52 2.258 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 2.258   list sub-command REMOVE_ITEM requires two or more arguments.
#52 2.258 Call Stack (most recent call first):
#52 2.258   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 2.258   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 2.258   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 2.258   /usr/share/cmake-3.16/Modules/CMakeDetermineCCompiler.cmake:116 (CMAKE_DETERMINE_COMPILER_ID)
#52 2.258   CMakeLists.txt:5 (project)
#52 2.258
#52 2.258
#52 2.550 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 2.550   list sub-command REMOVE_ITEM requires two or more arguments.
#52 2.550 Call Stack (most recent call first):
#52 2.550   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 2.550   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 2.550   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 2.550   /usr/share/cmake-3.16/Modules/CMakeDetermineCCompiler.cmake:116 (CMAKE_DETERMINE_COMPILER_ID)
#52 2.550   CMakeLists.txt:5 (project)
#52 2.550
#52 2.550
#52 2.847 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 2.847   list sub-command REMOVE_ITEM requires two or more arguments.
#52 2.847 Call Stack (most recent call first):
#52 2.847   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 2.847   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 2.847   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 2.847   /usr/share/cmake-3.16/Modules/CMakeDetermineCCompiler.cmake:116 (CMAKE_DETERMINE_COMPILER_ID)
#52 2.847   CMakeLists.txt:5 (project)
#52 2.847
#52 2.847
#52 3.030 -- The C compiler identification is unknown
#52 3.072 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 3.072   list sub-command REMOVE_ITEM requires two or more arguments.
#52 3.072 Call Stack (most recent call first):
#52 3.072   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 3.072   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 3.072   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 3.072   /usr/share/cmake-3.16/Modules/CMakeDetermineCXXCompiler.cmake:111 (CMAKE_DETERMINE_COMPILER_ID)
#52 3.072   CMakeLists.txt:5 (project)
#52 3.072
#52 3.072
#52 3.422 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 3.422   list sub-command REMOVE_ITEM requires two or more arguments.
#52 3.422 Call Stack (most recent call first):
#52 3.422   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 3.422   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 3.422   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 3.422   /usr/share/cmake-3.16/Modules/CMakeDetermineCXXCompiler.cmake:111 (CMAKE_DETERMINE_COMPILER_ID)
#52 3.422   CMakeLists.txt:5 (project)
#52 3.422
#52 3.422
#52 3.772 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 3.772   list sub-command REMOVE_ITEM requires two or more arguments.
#52 3.772 Call Stack (most recent call first):
#52 3.772   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 3.772   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 3.772   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 3.772   /usr/share/cmake-3.16/Modules/CMakeDetermineCXXCompiler.cmake:111 (CMAKE_DETERMINE_COMPILER_ID)
#52 3.772   CMakeLists.txt:5 (project)
#52 3.772
#52 3.772
#52 3.833 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 3.833   list sub-command REMOVE_ITEM requires two or more arguments.
#52 3.833 Call Stack (most recent call first):
#52 3.833   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 3.833   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 3.833   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 3.833   /usr/share/cmake-3.16/Modules/CMakeDetermineCXXCompiler.cmake:111 (CMAKE_DETERMINE_COMPILER_ID)
#52 3.833   CMakeLists.txt:5 (project)
#52 3.833
#52 3.833
#52 3.893 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 3.893   list sub-command REMOVE_ITEM requires two or more arguments.
#52 3.893 Call Stack (most recent call first):
#52 3.893   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 3.893   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 3.893   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 3.893   /usr/share/cmake-3.16/Modules/CMakeDetermineCXXCompiler.cmake:111 (CMAKE_DETERMINE_COMPILER_ID)
#52 3.893   CMakeLists.txt:5 (project)
#52 3.893
#52 3.894
#52 4.004 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 4.004   list sub-command REMOVE_ITEM requires two or more arguments.
#52 4.004 Call Stack (most recent call first):
#52 4.004   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 4.004   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 4.004   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 4.004   /usr/share/cmake-3.16/Modules/CMakeDetermineCXXCompiler.cmake:111 (CMAKE_DETERMINE_COMPILER_ID)
#52 4.004   CMakeLists.txt:5 (project)
#52 4.004
#52 4.004
#52 4.348 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 4.348   list sub-command REMOVE_ITEM requires two or more arguments.
#52 4.348 Call Stack (most recent call first):
#52 4.348   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 4.348   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 4.348   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 4.348   /usr/share/cmake-3.16/Modules/CMakeDetermineCXXCompiler.cmake:111 (CMAKE_DETERMINE_COMPILER_ID)
#52 4.348   CMakeLists.txt:5 (project)
#52 4.348
#52 4.348
#52 4.712 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 4.712   list sub-command REMOVE_ITEM requires two or more arguments.
#52 4.712 Call Stack (most recent call first):
#52 4.712   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 4.712   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 4.712   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 4.712   /usr/share/cmake-3.16/Modules/CMakeDetermineCXXCompiler.cmake:111 (CMAKE_DETERMINE_COMPILER_ID)
#52 4.712   CMakeLists.txt:5 (project)
#52 4.712
#52 4.713
#52 4.788 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 4.788   list sub-command REMOVE_ITEM requires two or more arguments.
#52 4.788 Call Stack (most recent call first):
#52 4.788   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 4.788   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 4.788   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 4.788   /usr/share/cmake-3.16/Modules/CMakeDetermineCXXCompiler.cmake:111 (CMAKE_DETERMINE_COMPILER_ID)
#52 4.788   CMakeLists.txt:5 (project)
#52 4.788
#52 4.788
#52 4.854 CMake Error at /usr/share/cmake-3.16/Modules/CMakeCompilerIdDetection.cmake:26 (list):
#52 4.854   list sub-command REMOVE_ITEM requires two or more arguments.
#52 4.854 Call Stack (most recent call first):
#52 4.854   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:211 (compiler_id_detection)
#52 4.854   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:230 (CMAKE_DETERMINE_COMPILER_ID_WRITE)
#52 4.854   /usr/share/cmake-3.16/Modules/CMakeDetermineCompilerId.cmake:32 (CMAKE_DETERMINE_COMPILER_ID_BUILD)
#52 4.854   /usr/share/cmake-3.16/Modules/CMakeDetermineCXXCompiler.cmake:111 (CMAKE_DETERMINE_COMPILER_ID)
#52 4.854   CMakeLists.txt:5 (project)
#52 4.854
#52 4.855
#52 5.041 -- The CXX compiler identification is unknown
#52 5.094 -- Check for working C compiler: /usr/bin/cc
#52 6.358 -- Check for working C compiler: /usr/bin/cc -- works
#52 6.366 -- Detecting C compiler ABI info
#52 7.539 -- Detecting C compiler ABI info - done
#52 7.569 -- Check for working CXX compiler: /usr/bin/c++
#52 8.810 -- Check for working CXX compiler: /usr/bin/c++ -- works
#52 8.825 -- Detecting CXX compiler ABI info
#52 10.12 -- Detecting CXX compiler ABI info - done
#52 10.13 -- Downloading conan.cmake from https://github.com/conan-io/cmake-conan
#52 11.08 -- Conan: checking conan executable
#52 11.10 -- Conan: Found program /usr/local/bin/conan
#52 15.81 -- Conan: Version found Conan version 1.24.1
#52 15.81
#52 15.81 -- Conan: Adding bincrafters remote repository (https://api.bintray.com/conan/bincrafters/public-conan)
#52 19.37 WARN: Remotes registry file missing, creating default one in /root/.conan/remotes.json
#52 19.51 -- Conan: Automatic detection of conan settings from cmake
#52 19.52 CMake Error at build/conan.cmake:127 (if):
#52 19.52   if given arguments:
#52 19.52
#52 19.52     "STREQUAL" "GNU"
#52 19.52
#52 19.52   Unknown arguments specified
#52 19.52 Call Stack (most recent call first):
#52 19.52   build/conan.cmake:496 (conan_cmake_settings)
#52 19.52   cmake/NmosCppConan.cmake:19 (conan_cmake_run)
#52 19.52   CMakeLists.txt:13 (include)
#52 19.52
#52 19.52
#52 19.53 -- Configuring incomplete, errors occurred!
#52 19.53 See also "/home/nmos-cpp/Development/build/CMakeFiles/CMakeOutput.log".
#52 19.53 See also "/home/nmos-cpp/Development/build/CMakeFiles/CMakeError.log".

failed to solve: rpc error: code = Unknown desc = executor failed running [/bin/sh -c mkdir /home/nmos-cpp/Development/build &&     cd /home/nmos-cpp/Development/build &&     cmake     -G "Unix Makefiles"     -DCMAKE_BUILD_TYPE:STRING="Release"     -DCMAKE_CONFIGURATION_TYPES:STRING="Release"     -DCXXFLAGS:STRING="-Os"     -build /home/nmos-cpp/Development/build .. &&     if [ -n "$makemt" ]; then echo "Making multi-threaded with $makemt jobs"; make -j$makemt; else echo "Making single-threaded"; make; fi]: buildkit-runc did not terminate successfully make: *** [Makefile:18: buildx] Error 1

I don't think this issue is Conan related, looks very similar to this one: https://gitlab.kitware.com/cmake/cmake/-/issues/20568

Yes, I agree. My issue does appear to be very similar to https://gitlab.kitware.com/cmake/cmake/-/issues/20568
I have commented on this issue and provided full logs etc. Let's see where it runs to... Thanks

Further digging into this it appears an issue with glibc...
Building using Bionic means a glibc version < 2.28, Focal is >2.28 - It appears the READDIR is returning NULL due to a 32-bit / 64-bit filesystem mapping issue.
https://bugs.launchpad.net/qemu/+bug/1805913
Not sure yet if there is easy way round this bug/issue?

Apparently resolved by https://gitlab.kitware.com/cmake/cmake/-/merge_requests/5258.


Background for the "need help" button is off

When you hover over the "?" button on the top right, the background color is blue instead of green.

Ya sure!!!

Take a look at #325 for understanding of how it works!


Visual Studio 2022, Detect Microsoft.VisualStudio.Component.VC.Tools.x86.x64 for 142

In order to locate the build tools for previous releases I used the following command.
For 2017:
& "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe"  -property installationPath -nologo -latest -version "[15,16)" -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64

For 2019:
& "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe"  -property installationPath -nologo -latest -version "[16,17)" -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64

This seems to still work for the 2022 payload:
& "C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe"  -property installationPath -nologo -latest -version "[17,18)" -products * -requires Microsoft.VisualStudio.Component.VC.Tools.x86.x64
C:\Program Files\Microsoft Visual Studio\2022\Community

But not for the old build tools, which worked perfectly fine with the 2019 release.

Closing for now as the error could be located in my script.

If you aren't installing the Release channel for VS2022, you need to pass --prerelease. Even now that VS2022 has GA'd, if you remain on the Preview channel you'll still need --prerelease.

I am on the release channel I just looked up the wrong component id (I failed to read the script I last updated with the 2019 release).
For 2017 its Microsoft.VisualStudio.Component.VC.v141.x86.x64
for 2019 its Microsoft.VisualStudio.Component.VC.<IP_ADDRESS>.x86.x64 ( a less specific version number would be handy but I'd need to complain at a different team)


Added return for when dnsdb doesn't contain results

Fixed an issue that would trigger the following error whenever a dnsdb search doesn't contain results:
DNSDB Exception: 765: unexpected token at 'Error: no results found for query.'
Error: no results found for query.
#<Thread:0x000055caa47e7998@/var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client.rb:107 run> terminated with exception (report_on_exception is true):
Traceback (most recent call last):
	12: from /var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client.rb:108:in `block (2 levels) in query'
	11: from /var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client/provider/dnsdb.rb:53:in `lookup'
	10: from /usr/lib/ruby/2.5.0/timeout.rb:108:in `timeout'
	 9: from /usr/lib/ruby/2.5.0/timeout.rb:33:in `catch'
	 8: from /usr/lib/ruby/2.5.0/timeout.rb:33:in `catch'
	 7: from /usr/lib/ruby/2.5.0/timeout.rb:33:in `block in catch'
	 6: from /usr/lib/ruby/2.5.0/timeout.rb:93:in `block in timeout'
	 5: from /var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client/provider/dnsdb.rb:78:in `block in lookup'
	 4: from /var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client/provider/dnsdb.rb:91:in `parse_json'
	 3: from /var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client/provider/dnsdb.rb:91:in `each'
	 2: from /var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client/provider/dnsdb.rb:92:in `block in parse_json'
	 1: from /usr/lib/ruby/2.5.0/json/common.rb:156:in `parse'
/usr/lib/ruby/2.5.0/json/common.rb:156:in `parse': 765: unexpected token at 'Error: no results found for query.' (JSON::ParserError)
Traceback (most recent call last):
	12: from /var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client.rb:108:in `block (2 levels) in query'
	11: from /var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client/provider/dnsdb.rb:53:in `lookup'
	10: from /usr/lib/ruby/2.5.0/timeout.rb:108:in `timeout'
	 9: from /usr/lib/ruby/2.5.0/timeout.rb:33:in `catch'
	 8: from /usr/lib/ruby/2.5.0/timeout.rb:33:in `catch'
	 7: from /usr/lib/ruby/2.5.0/timeout.rb:33:in `block in catch'
	 6: from /usr/lib/ruby/2.5.0/timeout.rb:93:in `block in timeout'
	 5: from /var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client/provider/dnsdb.rb:78:in `block in lookup'
	 4: from /var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client/provider/dnsdb.rb:91:in `parse_json'
	 3: from /var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client/provider/dnsdb.rb:91:in `each'
	 2: from /var/lib/gems/2.5.0/gems/passivedns-client-2.1.11/lib/passivedns/client/provider/dnsdb.rb:92:in `block in parse_json'
	 1: from /usr/lib/ruby/2.5.0/json/common.rb:156:in `parse'
/usr/lib/ruby/2.5.0/json/common.rb:156:in `parse': 765: unexpected token at 'Error: no results found for query.' (JSON::ParserError)

^bump


Terminal Sandbox

is there a way to sandbox the terminal to the user home?

That's up to whatever program (e.g. bash) you run in the terminal. Terminado just lets a web page talk to it. I don't know much about sandboxing, but you could use standard unix permissions to limit what the user can see, or run the terminals inside containers/VMs.

Thanks!


chore(renovate): update GitHub Actions major versions in docs

Summary
Originally wanted to update the reference to astral-sh/setup-uv in https://docs.astral.sh/uv/guides/integration/github/, but thought it could be nice to automate those updates through Renovate. The custom manager will look for any major version GitHub Action reference in any Markdown file in docs directory, and raise a PR to update it.
Possible improvements:

We could separate those updates from updating the actions updates for uv's own GitHub Actions workflow, which would end up raising 2 different PRs instead of grouping them (example of the current behaviour without this improvement in https://github.com/mkniewallner/mkv-playground/pull/4 where we update the doc reference at the same time as a real dependency usage in a workflow).
Should the PRs be raised immediately, to handle the update as soon as possible, instead of waiting for the regular weekly Monday schedule? This would ensure that astral-sh/setup-uv references are handled as early as possible.

Test Plan
I've tested that with https://github.com/mkniewallner/mkv-playground/blob/00ddfb69003843ad57d05f9ef036e655aaf765d7/renovate.json5 and https://github.com/mkniewallner/mkv-playground/blob/00ddfb69003843ad57d05f9ef036e655aaf765d7/docs/integeration/foo.md, where Renovate raised 2 PRs:

https://github.com/mkniewallner/mkv-playground/pull/13
https://github.com/mkniewallner/mkv-playground/pull/4

Thank you! This is great.
I don't mind a weekly cadence.
Separate pull requests seems kind of nice? But maybe not necessary. Is it hard to do? I'm willing to wait and see if it's problematic.

Separate pull requests seems kind of nice? But maybe not necessary. Is it hard to do? I'm willing to wait and see if it's problematic.

I don't think it's hard to do, will play with that in my test repository then update this PR (or report back if this is in the end).

Separate pull requests seems kind of nice? But maybe not necessary. Is it hard to do? I'm willing to wait and see if it's problematic.

I don't think it's hard to do, will play with that in my test repository then update this PR (or report back if this is in the end).

Played with that in https://github.com/mkniewallner/mkv-playground/commit/4c3ea0d2c8b6d1fd6351c2a1b3dca90e53f84886 (inspired by an example from Renovate itself), and it works well:

real dependency usage: https://github.com/mkniewallner/mkv-playground/pull/4/files
dependency reference in the documentation: https://github.com/mkniewallner/mkv-playground/pull/16/files


Add JSPatch to Bridging section

Following the recommendation of @dkhamsing, I created a new section called Bridging.
Related to #232

Can you please rebase?

@lfarah, rebased.


Build pods are evicted midway during the build

When I do kubectl get image_name I can see that the status of the image indicates that it is False. But I when I try to inspect the pod on which the build was running on by running kubectl get pod image-build-pod-name, I'm getting: Error from server (not found). Ideally even if there was a failure during the build due some misconfiguration it should not be removing the pod since the logs from the pod will have the information regarding why it failed.
This happens very randomly. I'm running multiple builds and all of them succeed mostly, but at times when there is failure, the pod seems to be evicted.
Another side effect I noticed is that when I try to access the logs of the build using the kpack-cli by running kp build logs image_name, the command hangs and does not return anything for quite a while. I believe this is because the kpack-cli was not able to find the associated pod from which it was to retrieve the logs from.
Is there something I'm missing which is causing the pods to be evicted or removed completely midway while the build is happening? I've also added pod disruption budgets to the pods which are provisioned by the kpack, to see if that would do anything, but to no avail.

Closing this for now, please reopen if you still have this problem


Update node agent key/cert file to be the same as workload key/cert, …

…extract requested identity from cert
Release note:

NONE

I am adding unti test for GetServiceIdentity now, but the logic is ready for review now.

I added a do-not-merge label and will not remove it until the unit test is ready

@wattli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
4344f3850173639b9b71e44231c6927e4e8e7829
link
/test auth-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wattli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
d264a0ae279b91ff5a8f48aa73ce00103bc2d649
link
/test auth-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wattli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
21e3d94ce541f4b7d93f0b3c0fb5204ada4f18b9
link
/test auth-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wattli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
5870d6098c3a840bf2656158d683b44bda40f881
link
/test auth-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wattli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
f247e8d23717139a9fb04b8bbb55f5c4c6c58f6d
link
/test auth-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wattli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
2f0042b407e0e57bf9a227ccc58b36568a9b0b42
link
/test auth-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wattli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
4c09db55b032b617d8742b009d259ebc60cd550e
link
/test auth-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@lookuptable , please take a look

@wattli: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
4562796595716f38c71719912a482939545973de
link
/test auth-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/approve
/lgtm


secret_generator: s/ignores/removes/ in test desc

What
Change the test description to make it clearer that existing passwords which
are no longer "requested" will be removed from the output. This is based on
a discussion with Alex when reviewing #442, where I asked if we needed to do
this manually and he pointed out that the code already does it.
How to review

Confirm that the change and commit message makes sense.
Confirm that Travis build passes.

Who can review
Not @dcarley

LGTM, I will merge as soon as travis finishes.


what does OpenAI Style Endpoints mean?

@Josh-XT found your comment here and I'm curious - just creating a docker…
what openAI-API endpoints do you support?
version 1.x.x?
functions?

Hello! By OpenAI style, I mean that you can use the OpenAI Python module or any other software that uses OpenAI endpoints to point at this server to run through a local model of your choosing instead of OpenAI's servers or models.
Please see the examples notebook here.


feat(client): handle multiple editors mobile

Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the main branch of freeCodeCamp.
[ ] I have tested these changes either locally on my machine, or GitPod.

Ref #46178

Hey @bbsmooth,
Last night there was a poor attempt to solve this, it did not work, and I went to bed.
This commit will make it possible to switch between tabs. Note that when resizing the screen below 769px while it is active it will not work as intended.
It does work when starting your session from 768px or lower and there is only one editor open. I will try to find a fix as we want it to work anytime the user changes their screen size.

I have another thought on this that I'll throw out there. Perhaps instead of making the decision for the user about whether they can view only one or both editors at a time, we instead allow them to choose. I'm no designer, so take this idea with a grain of salt, but I'm picturing icons that allow people to choose either single view or double view. And I know there has been talk of stacking the editors vertically instead of horizontally, so we could have two icons for the double view, one for stacking side-to-side and the other for stacking one on top of the other. Something like this would give our users the flexibility they need to use what works best for them.

Since phones have a limited usable space, turning panes into tabs for smaller screens is very common.
Although we have adopted this convention, users with average phone screen sizes can use the multi pane layout by tilting their phone.

I've never been fond of using "mobile" to describe smaller width view ports because it assumes that a small device like a phone will always be used, but I only need to zoom in a few hundred percent on my 1920 x 1200 monitor before I've triggered the "mobile" layout. Also, in my opinion, 769px width is way too small to have two editors side by side, I'd much rather have them one on top of the other or just use them one at a time if I can't have that. My point being that we can't anticipate how much px width a user is going to have regardless of what device they are using, so perhaps we shouldn't be defining strict cutoffs for such things and instead strive to give the user the flexibility to decide for themselves.
Now is any of the above technically an accessibility failure? No. Just because the user might have to do a few extra clicks to get the editors the way they want them does not mean they can't use them. Similarly, not having the ability to stack the editors on top of each other doesn't mean they can't use them. But I was under the impression that we are eventually going to give the user a choice on how to stack the editors and so I was thinking that if we are going to give them that choice then we might as well give them a third choice of never stacking the editors.
Again, not technically an accessibility issue, so I'm not insisting on anything here, just trying to think ahead a little and provide the best experience for everyone.


Use latest typescript 1.7.5 (instead of 1.7.3)

Is it possible to update the typescript dependency for this?
In particular, before this version there is some bug that creates multiple file monitors, which causes sluggishness in file system access. Issue here:
https://github.com/Microsoft/TypeScript/issues/6016

You shouldn't use the watch option of TypeScript in gulp. Instead you can use gulp.watch. But I have updated TypeScript as you suggested.

Thanks!
I am using the gulp.watch option, but since this was a bug in typescript, i wasn't sure if it might be affecting my dev env (there's some delay when writing to filesystem). Thanks again!


Clarifications about ports in 0.17

Add section about port modules and explain how to add one to a project, and what happens if you don't.
Try to clarify how to upgrade outgoing ports and where to call them.

@evancz quite a few people getting confused by this (seems like the compiler hint doesn't help enough, this would be handy)

Thanks, that helped a bit. Still trying to figure out how to import that module (I cannot find module 'Ports') and after that how to use an incoming port to initialize the app.

Oh, by looking at elm-todomvc I figured out what was expected of me :smile:
I really thought I have to make a module called Ports and import it.

I think it's too late. Sorry I did not update this sooner. @eeue56, can you reach out to me in other channels if you think there's something serious. Enough random people ping my @ that it is too much noise to respond to reliably.


Update to latest TCK version

Update to TCK 1.0.0-M11

Needs updating NOTICE and LICENSES due to added dependency.


add options for helm function

Feature request
Almost every run of the helm chart require providing value files, the name of the chart and the namespace . This require to use local function instead of helm and make helm function almost useless with real world examples.

thanks! Ya, it should be straightforward to add new arguments. Let me see what we can do here

Fixed in #2218 . The arguments should be available in the latest tilt release