Improving the quality of the site.

I want to cool off on adding more entries until it is decided which static site generator to use and how to scale up the mainpage.
If you want to contribute in a way that keeps the site unbloated, you can do some of the following:

Fix grammar, spelling and clarity of published articles. Do not nitpick or apply school-marm rules, e.g. don't "fix" split infinitives or clear dangling modifiers or inane things like that. Clarity is first. You might also want to minimize long-winded instructions. Some list items have what seems like a paragraph.
Link recipes to other recipes that they already mentioned in the text. Like I did in 58268cd9a969968f5966e85f9bc221d02b861103 where an article on sourdough bread mentioned soughdough starter, which exists in an article already. Links are very good.
Apply the UNIX philosophy: if you link an article you might want to think about slimming it down to avoid repeating instructions. For example, I made src/pasta.md which is a retard's guide to boiling pasta. You might want to take other dishes that might include pasta and instead of repeating these directions, simply link to this page saying that a required ingredient is "cooked pasta." This saves space, but also keeps from cluttering more experienced cooks with obvious things. Pasta is just an example, this could probably be done with other kinds of directions.

Please do not add your name to the credits for these minor edits. Credits should be related only to recipe content. If you substantially improve a recipe, you may add your name and links to the credit list.

What are the limitations of blogit other than the relatively slow build speeds?

Here is one I can personally recommend: https://gohugo.io/

It's broken like 10 times if it runs into a improperly formatted page or something it doesn't know how to handle.

Also, here is a non-bloated Hugo theme I've used before: https://themes.gohugo.io/hugo-bearblog/

Zola is nice.

Jekyll is nice too, and fully integrated with github pages (and free). Which would remove the need for the vulture hosting.

A few more suggestions:

Use Git LFS for images: https://git-lfs.github.com/
Preview builds for PRs (things like Vercel make this very easy)
Automatically generate fallback jpegs for browsers without webp support (e.g. Safari)

Here is one I can personally recommend: https://gohugo.io/

Hugo is really nice. Though I'm not sure how well it'll integrate with the UI we currently have on our hands.

It's broken like 10 times if it runs into a improperly formatted page or something it doesn't know how to handle.

Any program will fail, more or less silently, on improper input. We should add a CI check that runs the generator and fails if the generator fails, so we don't merge breaking PRs.

I would personally recommend zola.
It's relatively unbloated, supports templates, themeing, and unlike Hugo, has automatic link checking. It's also written in Rust so it's probably more stable than Hugo and probably as fast if not faster.

Agreed. Github Actions is really nice and can run event-driven (ex: when someone opens a PR). @m-chrzan

Can Zola do tags?

@m-chrzan @DGKSK8LIFE Looks like someone is ahead of you on this. There is a PR open #351

As far as I know, tags are not built-in, but you can use shprtcodes to make a custom tag system.
Once implemented, calling a tag would look something like this:
{{ tags(tags=["dessert", "milk", "sweet"]) }}

Another option would be to use taxonomies to make the tags into categories.
Once implemented, you could add the tag categories to the metadata at the start of each markdown file, in TOML format:
+++
tags = ["dessert", "milk", "sweet"]
+++

Looks like the build is actually broken again. their is a ' in one of the filenames which breaks the makefile #475. Definitely would have been caught by a script that tries to build on PR.

I think this issue is doing two things at once:

Automatically detecting PRs which don't build
Better static site generator

I don't think blogit is should be blamed for invalid pages. A better CI config should catch the broken builds. If it ain't broke, why fix it? I don't see why investing time and effort into porting the code into another static site generator is necessary.

Invalid pages aren't the only issue. Slow build times are also an issue.

Barebones solutions like ssg5 using markdown.pl or blogit don't scale well because they are inherently minimalist.
I think of it as "the requirements go up, so it's necessary to switch to a program of a higher "bloat level"."
Static site generators like zola are built to handle larger static sites whereas the minimalist tools only scrape by doing the bare minimum of what they have to do. That isn't to say there are bad; on the contrary, they suit their minimalist use-cases.
based.cooking will only get larger over time, and minimalist solutions don't scale very well, or support the features like taxonomies, shortcodes, or themeing support, or take forever to build the site.
 I'm stating that we have new requirements and we need a new tool which can facilitate them.
(The only sites I can think of that actually need to be dynamic are forums and webshops, and even then you could switch to a mailing list or instant messaging program for the forum, or a static web shop, although that might actually end up being more difficult than a dynamic webshop in the long run.)

Can Zola do tags?

Zola can indeed do tagging, however they call it a "taxonomy".
I'd definitely recommend Zola. I use it for my SSGs. It builds very quickly, never have issues with it running.

Regarding blogit being slow, it's "slow" because I made it to rebuild everything every time. I figured it would be better at the beginning when modifications to the Makefile and the config were common, but now that the workflow is set up, it could be good to replace the make clean deploy by simply make deploy. By doing that, blogit can theoretically scale infinitely since it would then only build/rebuild the new/modified recipes, leveraging the Makefile smart dependency management.
Regarding builds breaking, blogit like most of the tools me and my mates develop, assumes the user is not being retarded. It assumes that all markdown files are properly formatted. Now if some of those assumptions are too strict, I'd say just extend the Makefile to catch more exceptions.
Regarding recipe quality, I spent a few hours fixing and reformatting absolutely everything to my own taste. It includes:

Proper formatting of servings/times
Typos
Removing all traces of personal story/personal pronouns like "I, My", etc
Putting all "I recommend/my favorite/..."  I think of emojis as some sort of soyspeak for man children.

I didn't bother submitting a PR for this since as you can see, it's probably too autistic/strict for other people's taste, and that's fine. However, some of it has value, like fixing typos and general reformatting. Re-injecting images is probably doable automatically with some scripting so I might give it a go to make something PR-able. For now it's all here.
Finally, to dramatically improve recipe qualities, I suggest developing/using an automatic formatter, ie script/app that reads recipe components semantically and can do some post processing to output a perfectly formatted recipe. Ideas around that include:

Sanity check of every fields, tags, etc.
Automatic conversion between measurement system (you ask for ingredients and their quantities separately, in any measurement system, so in the output file you can print all the conversions).
Semi-automatic recipe linking, you grep all existing recipe's name in the new recipe and if found, you offer the user to make it into a link.

I'm developing a proof of concept of this here. It shouldn't be mandatory to write all recipes using such a tool, of course, but the more people using it, the more the general quality of recipes will improve. Honestly, as much as I hate javascript. this would actually be a valid use for it so that normalfriends who don't want to bother with installing a script or program can just do it from a browser. You'd host it on an isolated page somewhere on based.cooking and would require people to copy-paste the output into github.

* Preview builds for PRs (things like Vercel make this very easy)

you can also use IPFS for this (as well as for hosting itself) it won't help with static generation caching though, unless you build some kind of script to fetch already-built files from IPFS :thinking:

I added links to the pasta recipes in #535 and removed the instructions from the recipes when possible and reasonable. Cleaning up some of the tags might also be useful.

Slightly different approach (slightly maximalist in implementation) but I do love Hakyll when it comes to having reasonably predictable builds. I usually don't worry about certain aspects of my site breaking. It's modeled after Hugo but written in Haskell.

I suggest that the measurement system be consistent, preferably metric.

any progress on this @LukeSmithxyz?

What's the state of the project? Are the issues of the main page and site generator still unsolved?
If so, I could suggest a simple and very flexible way to build the page without a stubborn static site generator, just using a markdown converter and a script language.
Regarding the main page: Only display the tags and the ten latest recipes and move the index of all recipe links to a separate html file. They still need to be on one page, so one can use ctrl+f to search the recipe titles.
So many people contributed still unmerged recipes. It would be sad to stop the project.

Out of curiosity, I created a python script, to see what it takes to build this site.
The resulting script uses only the markdown package, is 69 short lines long and builds all recipe pages, all tag pages and the main page in under a second (using a SSD): 0m00.73s real     0m00.68s user     0m00.04s system
I omitted RSS and Atom. The only thing to change are the template files (it only uses three). Otherwise it's an drop-in replacement.
Interested, @LukeSmithxyz ?

Come on, the project shouldn't end here! I love the idea, sad to see so many recepies that are still unmerged.


resize request exception error message is junk characters

Here is how I am using sharp:

    sharp("sample.jpg")
     .resize(parseInt(20))
     .toBuffer()
     .then(function(err, outputBuffer){
        if (err) {
            throw err;
        }
    })
    .catch(function (err){
        console.log('exception in sharp: '+err);
    });

This request is hitting exception and returning junk characters as error message:

exception in sharp: ï¿½ï¿½ï¿½ï¿½C
%-(0%()(ï¿½ï¿½C
(((((((((((((((((((((((((((((((((((((((((((((((((((ï¿½ï¿½
"ï¿½ï¿½ï¿½ï¿½"!A1Qï¿½ï¿½ï¿½ï¿½!ï¿½ï¿½
?ï¿½ï¿½ï¿½ï¿½Cï¿½ï¿½ï¿½ï¿½ï¿½Qï¿½Eï¿½ï¿½ï¿½;|ï¿½0ï¿½ï¿½ï¿½Ó¡Qï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½RYï¿½ï¿½fï¿½ï¿½4ï¿½ï¿½F%ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½> rMï¿½ï¿½ï¿½ï¿½
PuTTYPuTTYPuTTYPuTTYPuTTYPuTTY

What am I doing wrong?

JavaScript Promises resolve with a value via then() and reject with an error via catch() .
-     .then(function(err, outputBuffer){
+     .then(function(outputBuffer){


Implement bitsandbytes 4-bit and 8-bit quantization

Description

This PR introduces 8-bit (mixed int8 and float16) and 4-bit (FP4/NF4) direct quantization of weights using the bitsandbytes library.
Currently, models.FromPretrainedHFModel and generation.FromHFHub accept an optional BitsAndBytesConfig dataclass with quantization parameters. When present, the weights are automatically quantized during deserialization. This is only available for models running on CUDA GPUs.
At the time of this PR, the current version of bitsandbytes (0.39.0) supports both 8-bit and 4-bit backends, but neither expose the device parameter in their torch modules. We have an open PR that adds this, but the ETA is currently unknown. In the meantime, we'll need to build the library from source using this fork for testing purposes.
Types of change

Enhancement
Checklist

[x] I confirm that I have the right to submit this contribution under the project's MIT license.
[x] I ran the tests, and all new and existing tests passed.
[x] My changes don't require a change to the documentation, or if they do, I've added all required information.

Of, forgot to add, we should probably add to the readme how to install your fork of bitsandbytes, since this will probably be a popular feature. Similarly, it would be useful to add a short blurb to DEVELOP.md about how to determine what layers to exclude from quantization.


prebuilt binary for aarch64 platform

Thank you for developing such an useful tool. It works very well for me on x86 servers/computers. But recently we have server based on aarch64. I tried to compile and install MA on it, but did not succeed. I was wondering if there will be a prebuilt binary available to download or install via conda for aarch64?
Best,
Zhi-Luo

Hi,
Unfortunately, kswcpp - the dynamic programming library we use - relies on SIMD instructions that are not supported by aarach64.
Due to the work required for resolving this, we currently have no plans to make MA compatible with this architecture.
Sorry,
Arne and Markus


Update action to do pipy deployment

It's on progress on Pypi-PR
draft pypi module can be tested on : navigator-pypi
pip install br_navigator

is there a reason for be a draft ?

actually not, it will be triggered only on tags,
but the module name and version should be carefully set up beforece any official release,
it's better to validade the core-lib a bit more and test with br_navigator.

We can close this since we are using pypi-publish action with thrusted publishers.


EXP | with-jotai

What is the example you wish to see?
This is a good first issue if you want to contribute to our framework!
Jotai is an excellent state management library for React. It'd be awesome to have an example showing how it works with Plasmo.
Is there any context that might help us understand?
https://jotai.org/
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

I would like to contribute

@ColdSauce I am getting this issue :
 ERR_PNPM_NO_MATCHING_VERSION_INSIDE_WORKSPACE  In ../../cli/create-plasmo: No matching version found for @plasmo/config@* inside the workspace
while running the following command pnpm dlx plasmo init

Hey @Aarush-wadhia, sounds great, thanks for helping out!
Where are you running that command?

Hmm, interesting. It's complaining it can't find the plasmo/packages/config/ directory.
I couldn't get this to reproduce on our CI environment or my Mac locally, so I'm not sure why it's saying that for you.
Are you able to build other examples in the directory using pnpm? Does something like cd with-ant-design && pnpm build work?
Also, can you do pnpm dlx plasmo init in a random directory unrelated to Plasmo? Something like /tmp and see if that works?

Hmm, its weird when I create new project outside the plasma package it is working fine but inside the example package when I am using pnpm dlx plasmo init command it is giving the above mentioned error
And in my example folder I don't have any other examples it's empty folder

Ah - I think it's because you need to use --recurse-submodules when cloning our plasmo monorepo.
git clone git@github.com:PlasmoHQ/plasmo.git --recurse-submodules

For more info, check out our contributing docs.

I got the issue
My git is not allowing me to clone all the directories because of my ssh keys for which I have to change the git clone URL
Let me resolve this real quick

Hey @ColdSauce the issue is resolved.
Like I thought it was my ssh issue which I have resolved now and it is working fine
I will be working on with-jotai example

Hi, @ColdSauce it is showing zsh: command not found: plasmo while running command pnpm build or pnpm dev.

Have you done pnpm i?

Yes

Go to the monorepo root folder and run
pnpm i
pnpm build

and then try again

Go to the monorepo root folder and run
pnpm i
pnpm build

and then try again

The second cmd should be pnpm build:cli since we just want the plasmo cli to be built here I think. Also, you will need to do pnpm i again afterward to ensure the plasmo binary is properly linked

Go to the monorepo root folder and run
pnpm i
pnpm build

and then try again

The second cmd should be pnpm build:cli since we just want the plasmo cli to be built here I think. Also, you will need to do pnpm i again afterward to ensure the plasmo binary is properly linked

It worked
I did following steps
pnpm i
pnpm build:cli
pnpm i
pnpm build
Then I navigated to the examples folder in which I went to with-redux and then I run the command pnpm dev it started the development server but it didn't opened in any browser

for reference


Quests loading/reading asynchronously

What does your feature do?
This feature would just be a change from the original Bukkit configuration tools to a asynchronous reader, honestly though the best way to do this would be to be able to store the quests in a MySQL server and have them called from and loaded when needed rather than all of it loaded in RAM. MySQL also offers a lot more possibilities such as Multi-Server Quest synchronization and it just far more efficient to load what you need rather than loading everything in ram, as my question before asked about quest generation and having huge quantities of quests is not really viable in a bukkit config format as it would have to load possibly multi-gigabyte files constantly, MySQL integration can make this extremely simple though as you can store them on it instead, and we can also no longer have to do /questadmin reload to load the new quests therefore increasing stability, also making it a live edit plugin, meaning we can actually have people editing and creating quests whilst we also have possibly hundreds or thousands of players playing them. I really want this feature specifically because I love quests, and while it is great, I would also love to just make a copy of my server and get rid of all the maps and everything and simply just have a editing server where all the NPC's and things of that nature are close together so that my admins and quest editors don't have to fly around 2000+ block maps constantly to make a single quest. It would drastically speed up how fast we can make quests, and how many quests we can make.
Also a really good work around to deal with NPC's ID's synchronizing would simply be to give the ability to give a "Alias ID" So lets say for example we have 3 different servers and 3 of the "same" NPC's so what you could do is set a "Alias ID" for the NPC where it can refer to the NPC regardless of server or ID.
For example it could be stored like this:
Server1:
NPC-ID:

274
Alias: 255
Server2:
NPC-ID:
245
Alias: 255
Server3:
NPC-ID:
173
Alias: 255

Now in this example there are 3 NPC's on 3 different servers that each have different ID's (274, 245, 173)... But now if we make a quest we use the ALIAS, meaning we would use 255 as the NPC ID, and that would then handle synchronizing it between multiple servers, because for each server it would look at the Alias, then find the actual ID, for example if we looked at Server1, it would lookup Alias 255, then find Server1, then it would see the actual ingame ID and use that!
Also for locations you can follow the same methodology, giving a Alias usage so that if a player has to reach X location there are aliases for each of those.
This is obviously a very large undertaking on your behalf, however I think it would dramatically increase this plugin from being a simple replacement for like askyblock challenges, to making it a feasible tool to use as a full core gamemode, as of right now this plugin does not have the ability to have thousands or hundreds of thousands of quests as we have tested with a procedural generator to make quests, when we push past the several thousand mark, it literally takes up multiple gigabytes of ram, and crashes when you try to reload the server simply because it is IMPOSSIBLE to read 800,000+ Lines of config within a server tick (or even a few hundred server ticks) so the server just freezes and crashes from not having a tick within 60 seconds. MySQL not only solves this issue, it makes the plugin FAR more compatible with multiserver setups, and makes this plugin essentially infinitely scalable, this would majorly benefit everyone using this plugin, also that being said, you will probably also need to make another plugin to accompany this that would let people convert their MASSIVE configs and massive amount of already made quests into the MySQL server, that way people don't have to throw away hundreds if not thousands of hours of work just to get these features!
How would people use it?
Explained above!

While other people have asked for MySQL integration I do hope this is not marked duplicate because I believe I have gone above and beyond any of those requests and submitted a actual path to a solution, and how to start doing cross server synchronization.

Thanks for the suggestion. I've looked into it and it seems loading through the Bukkit implementations is thread-safe despite some serialization. The same cannot be said for saving configurations which, although not the purpose of this ticket, does appear as though it may be limited by how many characters a String can hold, which is<PHONE_NUMBER>. This amounts to a roughly 4 GB maximum file size.
As such, while exploring alternative I/O options would be optimal, you said it yourself that MySQL would be the best way to do this. Even if Quests were able to support large files, concurrency would be a concern, especially if someone wanted to use the same file for multiple servers as you've outlined.
I've gone ahead and made /questadmin reload run async (plugin enable is still sync because of a getOnlinePlayers() call which may or may not be thread-safe). I'll leave the stress-testing to you. Feel free to bring up your points about MySQL in #312 as well as your alias idea.
Use https://ci.codemc.io/job/PikaMug/job/Quests/92/


SiteIDs description needs more detail

If you are searching for Sites where the names include the dash/minus character you will get no hits.  You have to double the characters.
For example my lab tenant contains the site:
"https://contoso.sharepoint.com/sites/cats-are-cool"
If you run:
search-unifiedauditlog -startdate 3/3/2021 -enddate 4/4/2021 -siteids "https://contoso.sharepoint.com/sites/cats-are-cool"
you will get zero hits.
If you run:
search-unifiedauditlog -startdate 3/3/2021 -enddate 4/4/2021 -siteids "https://contoso.sharepoint.com/sites/cats--are--cool"
you get many hits.
This parameter is treating - as a special character.  You have to include two of them to tell the cmdlet that you mean to include one as a literal.
This behaviour also affects the Audit Log search on compliance.microsoft.com and protection.office.com because they run this cmdlet under the hood.
I would suggest a Note be added to the description of this parameter explaining that you need to double the dashes to have them treated properly.  The Help for the GUI should also be updated.
<EMAIL_ADDRESS>
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 75b757c9-b775-8294-91f7-870bead6a907
Version Independent ID: 54ebab36-97bb-cd9f-6eb2-12198af885e2
Content: Search-UnifiedAuditLog (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Search-UnifiedAuditLog.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@cablechewer, I added information to the SiteIds parameter description as you described.
Thanks for the feedback.
Closing


Windows 64 bit version?

Is there any chance to release prebuilt 64bit version to download?

The compressonator sdk did support 64bit build. but for the gui and commandline app now is running on 32bit configuration which run fine in 64 bit system as well. We will add 64 bit build to the app later, please keep an eye on the commit. Thanks.

The SDK library , CLI and GUI application sources are 64 bit compliant, however the 3rd party lib used to link them are still 32 bit. We are in process of updating them and will post new binaries soon.

Thanks. :)
BTW what command do I use if I want no mipmaps?

You can set the command line with -nomipmap
To see all of the commands simply run CompressonatorCLI with no parameters

Thanks. :)
Instant Close. :(

@aboood40091 , can you elaborate more on "instant close" issue? what commands did you run? thanks,

When I run CompressonatorCLI with no parameters, it opens and closes at the same time.

please run by typing the command "CompressonatorCLI" in the command window, instead of double click on the CLI app.

That's exactly what I did.

64 Bit applications available in V2.4 release


BUG: Missing definition of modelLst in init.Model.py

Describe the bug
When starting main.py in the Examples folder via VsCode I get an import Error for line #16

To Reproduce

Go to ...\RFEM_Python_Client\Examples
Click on main.py
execute it

Expected behavior
script stops at line 16

Desktop (please complete the following information):

Version of WIN10
Version of RFEM6

Additional context
I checked the referring init.model.py and it seems that the object modelLst is missing a definition in there

I recently encountered the same bug. modellst object is embedded in connectToServer method in initModel.py. My quick solution was to return modellst out of the method and then replace modellst with connectToServer() in the main file accordingly. I hope this helped.


only acccept cloud config files for certain providers

/hold

/test verify
Not sure I get how this caused that error...
Change looks good otherwise and is needed to unblock work.

/hold cancel


Mobile responsive

Let's look at Skeleton: http://getskeleton.com/

Plotting out loud for tonight's Code for SF brigade meet-up — maybe we could do a little responsiveness audit with any user testers / front-end engineers who come by.

Desktop is the main interface for the project, as we've seen from working with our partners at the school district. Mobile responsiveness is nice to keep an eye out for but not a critical feature.


Client: support reading with multicast

edit onSetup() to allow multicast requests
make sure that UDP listeners work also in case of multicast addresses (no changes should be required)

implemented with 9595e29


start: using a TextEncoder

Using PR to test out the preview packages on the cf-deployment.
This led to CF deployments just showing a blank screen with this error in the dashboard.
"This ReadableStream did not return bytes."

{
  "truncated": false,
  "outcome": "exception",
  "scriptName": "pages-worker--3280425-production",
  "diagnosticsChannelEvents": [],
  "exceptions": [
    {
      "name": "TypeError",
      "message": "This ReadableStream did not return bytes.",
      "timestamp":<PHONE_NUMBER>130
    }
  ],
  "logs": [],
  "eventTimestamp":<PHONE_NUMBER>070,
  "event": {
    "request": {
      ...
    },
    "response": {
      "status": 200
    }
  },
  "id": 0
}

Definitely on the right track here:
Now the invariant error UI is being displayed, with the correct HTML being sent down.

Likely something to do with the hydration or reading from the __TSR__ globals is causing this invariant failure.

Currently on "cf-pages" deployments, two known errors do exist.

On the client, hydration fails because of the invariant failure.

We know that React is working though since the invariant error is being displayed using the default TSR <ErrorComponent> with the button successfully toggling the React.useState boolean for the "open" state.

Loading the /posts route fails, because the routeTree has an error listed in the output logs.

"Error: Context is not available"


Discussion for Credential Persistence integration

Proposal to use SecretManagement  module to add credential persistence to PSGet v3. (blog post here).
Beginning initial design discussion and investigations in this issue.
cc: @PaulHigin

This looks good.  But I wonder why not just use SecretManagement outside PSGet?
Install-PSResource -Name myModule -Repository myRepo -ProxyCredential (Get-Secret -Name myRepoCred -Vault mySecretStore)

But if we want to integrate a credential store more tightly with PSGet, another option would be to just integrate the Microsoft.PowerShell.SecretStore module directly (without SecretManagement).  This would remove the vault choice and always store credentials on the local machine with SecretStore.  No vault options, but also less complex.
# Registers myRepo and stores credential in SecretStore for repo name 'myRepo'
Register-PSResourceRepository myRepo -URL path/to/my/repo -Credential $credential
Install-PSResource -Name myModule -Repository myRepo

We are very excited about the possibility of this feature!
I would like to provide two user cases that highlight how this feature would help my team:
Context:
Currently our Artifactory instance is set up to allow anonymous authentication from a set of approved IP addresses. This allows us to not pass in any credentials when we are registering our Powershell repository or pulling down packages on internally managed Jenkins agent VMs or local developer machines. However, Artifactory's anonymous auth configuration is limiting us because we cannot easily move our CI workflows to Github Actions or Azure DevOps pipelines due to the whitelisting requirement. We would like to get away from it while ensuring our packages are still only accessible internally. This feature would enable us to enforce auth for our Powershell repositories without having to update all of our build scripts to provide credentials for package handling.
Build infrastructure scenario:
As I mentioned, we have our own Jenkins instances and we prep our agent VMs via Packer image creation and running Chef post-provision. As part of this configuration, we are registering our Powershell repositories on the VM, in the user profile that Jenkins masters are using for establishing connections to their agents. All builds, then, proceed to run their scripts as these users on agents and no further authentication for Powershell packages is required with this setup. When we need to roll these VM user account passwords as part of our security practices, it is sufficient to update the Jenkins credential and re-establish the connection.
If we were to switch to forced auth today, not only we would need to pass in credentials during PSRepository registration, but also with every Module command, which would require a lot of changes in our build scripts. With this feature though, switching auth would only have the minimal impact of updating repository registration during agent setup. When it comes to supporting SecretManagement vs SecretStore, especially on CI infrastructure, having access to Azure Key Vault for these credentials would be immensely helpful for password rolling, because then we wouldn't need to update anything on the VM. We would just continue to read the new value from a key vault without any interruptions or maintenance.
Local developer scenario:
The same conditions apply to local developer machines and workflows. Because currently there isn't a way to store PowerShellGet credentials locally, every time a developer needs to pull down a module, they would get prompted with a credentials popup and this could be disruptive. Whereas, this feature would give them the ability to set it up once and forget about it, until maybe they have to update their password.

I think it makes sense to have some integration between PowerShellGet and SecretManagement so that the user doesn't have to explicitly pass credentials or know to pass which credentials for a specific repository.
I think it's ok to require pre-provisioning a vault with SecretManagement with the secret needed to authenticate, and then at PSRepository registration time inform PowerShellGet which secret to get from SecretManagement (secret name and vault) so it's implicit for any request to that PSRepository.
Since most users may not need this capability, the dependency on SecretManagement should be a soft dependency where if they try to use the feature, the error message should direct them to a doc page explaining how to make it work rather than requiring install as a dependent module.

I am in favour of avoiding an explicit hard requirement on another module when only a minority of use cases need it. We added Az modules into our dependency tree too eagerly, and now all my terminals incur a 20-second lag :-/

I've opened a pull request that follows the design proposal. The implementation only introduces a soft dependency on SecretManagement.

Everything works as it does now if you are not registering repositories with -Authentication.
It is assumed that the secret vault setup has already been done prior to invoking PowerShellGet. Otherwise, it throws the same SecretManagement errors if you are trying to use a vault that does not exist, or if SecretManagement module is not available, etc.

Looking forward to getting your feedback!

I started looking at the PR and then this associated Issue.  I feel this is a good start but am not sure if this is the correct design yet.  For example I feel the parameter name should not be -Authentication but maybe be -Credential or -CredentialInfo.  'Authentication' usually specifies an authentication type, not authentication credentials.
Also I feel we need to spend time thinking about error messages if/when SecretManagement is not installed, not configured, or the secret information is not available.  My concern is that SecretManagement error messages will be confusing to users, since the persistence mechanism is kind of buried in PowerShellGet.  We may want to test and/or catch errors and display better messages.
Also it may make more sense to store/retrieve authentication information as PSCredential since it encompasses username/password.  But would this be too limiting?  Would later repositories have different authentication mechanisms, and if so is there a way we can support them?
I will continue my PR review and feel this is a great feature, but we will probably have to make some design user experience changes.
In the future we will provide more written guidelines on how to propose/discuss new features, get acceptance, and create a implementing PR.
/cc @StevenBucher98


EnclaveFactoryTest - migrate tests from Junit4 to Junit5

PR description
EnclaveFactoryTest
Added dependency for junit.jupiter (junit5)
Removed dependency on junit 4
Migrated test from junit4 to junit5
Fixed Issue(s)
https://github.com/hyperledger/besu/issues/5566

@macfarla Plz review
Also dont know why 1 check is failing with -
Could not determine the dependencies of task ':spotlessCheck'.
> Could not create task ':spotlessGroovyGradleCheck'.
   > Could not create task ':spotlessGroovyGradle'.

any idea about this?


SVGs are not isolated in notebooks

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

Version: 1.75.0 (system setup)
Commit: e2816fe719a4026ffa1ee0189dc89bdfdbafb164
Date: 2023-02-01T15:23:45.584Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045
Sandboxed: No
Steps to Reproduce:

Open a notebook containing an SVG file that that has colliding symbol ids. See for example igraph/python-igraph#638
Issue occurs for both the built-in and the jupyter-extension svg renderer - isolate tag provided is ignored in both cases.

@DonJayamanne Does jupyter always embed svgs inside of iframes?

One thing I should have noted is that in the specific case listed above the library specifically attaches the metadata tag 'isolated': True as part of the repr function (igraph/python-igraph/pull/148), which causes jupyter to isolate it within an iframe. vscode ignores this tag.

@mjbvz sorry I missed this, no in Jupyter Notebooks, they are embedded within the same DOM.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Set 1.13 fixVersion to 1.13.6.

High-level description

DCOS-58755 - 1.13.5 release activity. Setting the version of master branch to 1.13.6

@mesosphere-mergebot label  ready for review

@mesosphere-mergebot merge-it


[BUG] Conversion compile issue

Hidet generated kernels contains cast operations such as:
__global__ void __launch_bounds__(500) hidet_compute_z(half* src, uint64_t* dst){
  dst[threadIdx.x] = (uint64_t)src[threadIdx.x];

will not compile due to the following error, as there is no explicit conversion defined from half to uint64_t
The proper conversion is defined here:
After some testing, only int64 and short cannot be directly casted, but would require additional handling, as seen in PR
source.cu(35): error: more than one conversion function from "half" to "uint64_t" applies:
            function "__half::operator float() const"
/usr/local/cuda/bin/../targets/x86_64-linux/include/cuda_fp16.hpp(204): here
            function "__half::operator short() const"
/usr/local/cuda/bin/../targets/x86_64-linux/include/cuda_fp16.hpp(222): here
            function "__half::operator unsigned short() const"
/usr/local/cuda/bin/../targets/x86_64-linux/include/cuda_fp16.hpp(225): here
            function "__half::operator int() const"
/usr/local/cuda/bin/../targets/x86_64-linux/include/cuda_fp16.hpp(228): here
            function "__half::operator unsigned int() const"
/usr/local/cuda/bin/../targets/x86_64-linux/include/cuda_fp16.hpp(231): here
            function "__half::operator long long() const"
/usr/local/cuda/bin/../targets/x86_64-linux/include/cuda_fp16.hpp(234): here
            function "__half::operator unsigned long long() const"
/usr/local/cuda/bin/../targets/x86_64-linux/include/cuda_fp16.hpp(237): here
            function "__half::operator __nv_bool() const"
/usr/local/cuda/bin/../targets/x86_64-linux/include/cuda_fp16.hpp(241): here

1 error detected in the compilation of "source.cu".

Hi @yaoyaoding all looks good now, could you take a final look ?

Thanks @xinli-git!


Impelement Joiner::Stop.

Current coverage is 65.76% (diff: 66.66%)

Merging #548 into master will increase coverage by 0.01%

@@             master       #548   diff @@
==========================================
  Files            84         84
  Lines         11843      11843
  Methods        1594       1594
  Messages          0          0
  Branches       1395       1395
==========================================
+ Hits           7786       7788     +2
+ Misses         3641       3638     -3
- Partials        416        417     +1

Powered by Codecov. Last update 9c75d70...6f61ef4

LGTM :+1:


Standard 10.0.0 stopped working when installed with pnpm

Maybe this is something that should be fixed on the pnpm side, but I don't know what caused the issue, so maybe someone could help me to understand.
From version 10, if standard is installed using pnpm, when running standard, it throws these errors: Resolve error: unable to load resolver "node".
pnpm uses a different node_modules structure and bin files format but standard worked fine till v10. Can someone point me to what was changed that could break this?

@zkochan What happens when you delete your node_modules and reinstall everything? Does that fix the issue?
Can you post the complete output from standard?

Yes, I tried removing node_modules. However, with pnpm it is not really needed because it always creates the same node_modules structure.
Here's a repo to reproduce https://github.com/zkochan/pnpm-standard. I committed the whole node_modules folder.
When running npm t, it fails with this:
><EMAIL_ADDRESS>test /home/zkochan/src/test/pnpm-standard
> standard

standard: Use JavaScript Standard Style (https://standardjs.com)
  /home/zkochan/src/test/pnpm-standard/index.js:1:1: Resolve error: unable to load resolver "node".
npm ERR! Test failed.  See above for more details.

I'm really sorry but I don't have the bandwidth to debug this at the moment, so I'm going to close this issue to reflect that. If you (or someone else!) figure out how to fix this bug and have further information to share, or want to send a PR, I'm happy to take a look again.

@feross I don't know what you did, but the issue has been fixed by<EMAIL_ADDRESS>So thank you or anyone else who contributed the mysterious fix!
(the issue might have been a missing dependency. npm and yarn flatten dependencies, so frequently packages work even if someone forgets to add a dependency to package.json. Maybe I'll investigate what was the issue later)

Glad it worked out for you!

I'm currently experiencing this issue now in my own repository. Suddenly my eslint throws this same error message after switching to pnpm (I am not using standard). Let's see if I can investigate more details...

@onlywei, feel free to file an issue in the pnpm repo

@zkochan currently putting out some fires, so I temporarily removed the import/order rule from my .eslintrc.json. When I have more bandwidth I can investigate more to be able to provide more details for a better issue report.

@onlywei Thanks for sharing. If you have additional info, that would be much appreciated.

@feross @zkochan I found the same issue happend in<EMAIL_ADDRESS>, but it really fixed in<EMAIL_ADDRESS>; below is my command log:
> standard --verbose|snazzy

standard: Use JavaScript Standard Style (https://standardjs.com)

\_\project\exec\npm\src\components\Menu.js
   1:1   error  Resolve error: unable to load resolver "node"  import/no-duplicates
  64:3   error  'componentWillReceiveProps' is not defined     no-undef
  67:3   error  'getArr' is not defined                        no-undef
  69:21  error  'arr' is not modified in this loop             no-unmodified-loop-condition
  74:3   error  'getKeys' is not defined                       no-undef
  81:3   error  'keySwitch' is not defined                     no-undef

\_\project\exec\npm\src\utils\fns.js
  3:3  error  Unexpected constant condition  no-constant-condition

\_\project\exec\npm\src\utils\global.js
  1:1  error  Resolve error: unable to load resolver "node"  import/no-duplicates

\_\project\exec\npm\src\view\index.js
  1:1  error  Resolve error: unable to load resolver "node"  import/no-duplicates

\_\project\exec\npm\src\view\root.js
  1:1  error  Resolve error: unable to load resolver "node"  import/no-duplicates

✖ 10 problems
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>pre: `standard --verbose|snazzy`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>pre script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.


cargo crev db git ... to not treat -args as it's own argument

Right now cargo crev db git -- commit -a has to be used, which is inconvenient. Anything after git can't be an argument to cargo-crev itself.

https://github.com/TeXitoi/structopt/issues/153

This could be somewhat less of a problem if https://github.com/dpc/crev/issues/40 was implemented.

https://users.rust-lang.org/t/clap-structop-a-way-to-not-require/23134/2


Add methods to modal for wizard step 2

Is your feature request related to a problem? Please describe.
The buttons related to https://github.com/mailchain/mailchain-web/issues/157 need to work
Describe the solution you'd like
Buttons should be added in #159
Buttons to add methods:

[ ]  Back: takes user back to Step 1
[ ]  Cancel: close model and discards changes
[ ]  Save Changes: call method described in #164

Additional context

Closing due to archiving repository


Forum is very unstable and returning lots "Error code: 500 error"

Describe your problem and - if possible - how to reproduce it
Add a Link to the page with the problem
https://www.freecodecamp.org/forum/
Tell us about your browser and operating system

Browser Name: Chrome
Browser Version: Latest
Operating System: Windows

If possible, add a screenshot here

It's not just the forum. The settings page was getting 500 errors, but is now failing to load and showing this loading symbol in an endless loop:

The curriculum was 500'ing as well previously, but is currently not loading my settings (I think the session was wiped, because it slowly loaded the sign-in button eventually).

FCC has communicated that their experiencing latency issues that are causing 500 errors. They also have had a banner up on the forum warning that it would be moving and going down for maintenance.

Okay. I didn't know how to communicate to whomever should know that there was a problem, which is why I hopped on GitHub. As a baby webdev with a tiny speck of knowledge about how to set up a web server, I didn't know if downtime alerts were sent to the appropriate person's cell phone, or whether that was even a thing for FCC.

The FCC Twitter is usually the best way to be updated when there is a known or planned outage.

The forum is up and running again now.


Board Review: Azure Storage Blob NIO

The Basics

Service team responsible for the client library: Azure Blob Storage
Link to documentation describing the service: https://azure.microsoft.com/en-us/services/storage/blobs/
Contact email (if service team, provide PM and Dev Lead<EMAIL_ADDRESS><EMAIL_ADDRESS>
About this client library

Name of the client library: Azure Storage Blob NIO
Languages for this review: Java
Link to the service REST APIs: https://github.com/Azure/azure-rest-api-specs/tree/storage-dataplane-preview/specification/storage/data-plane

Artifacts required (per language)
Java

Upload JAR to apiview.  Link: https://apiview.dev/Assemblies/Review/7afaef0b130546fcb6a95076ca7e543f
Link to samples for champion scenarios: https://gist.github.com/rickle-msft/71bb85115fa2e867841b83bf5df814a9

Champion Scenarios
A champion scenario is a use case that the consumer of the client library is commonly expected to perform.  Champion scenarios are used to ensure the developer experience is exemplary for the common cases.  You need to show the entire code sample (including error handling, as an example) for the champion scenarios.

Champion Scenario 1:

Describe the champion scenario:

A customer has a file containing a sequenced genome. They open the file, read a relevant portion of it, perform some analysis on the data they read, and write the results to an output directory.

Estimate the percentage of developers using the service who would use the champion scenario

100%: As far as we know, everyone who has requested this product has use for this exact scenario

Link to the code sample

https://gist.github.com/rickle-msft/71bb85115fa2e867841b83bf5df814a9

Agenda for the review
A board review is generally split into two parts, with additional meetings as required
Part 1 - Introducing the board to the service:

Review of the service (no more than 10 minutes).
Review of the champion scenarios.
Get feedback on the API patterns used in the champion scenarios.

After part 1, you may schedule additional meetings with architects to refine the API and work on implementation.
Part 2 - the "GA" meeting

Scheduled at least one week after the APIs have been uploaded for review.
Will go over controversial feedback from the line-by-line API review.
Exit meeting with concrete changes necessary to meet quality bar.

Thank you for your submission

[MS internal only]Video
Action Items:
Champion Scenario:

possible to try-catch that does auto close? Use that in champion scenario if possible

Consider edge cases difficult to code for:

Open same file twice for reading

Whichever string gets closed, gets committed, which invalidates the block list from the other. Second write throws
But this way of handling isn't what's normally expected for file system

e-tags could change between reads, which will throw if customer doesn't know,

document the assumption that nothing else is modifying on the file while operating on it

In general, document what limitations, assumptions, etc. there are

Consider how pluggable this is into existing code
How to get back/access to Blob client?

Consider how we want to approach this if customers want it in long run
Jeff's concern: Exposing this would give customer opportunity to do something risky. Ex: doing something to blob that changes e-tag, they'll no longer able to read. "I'd be cautious about it."
Ted's suggestion: Could we do something like AzureBlobFileSystem.GetBlobClient(URI path) that returned a client so you could just take your path and jump into our world?

SDK team to come up with way to name the package, especially for tools that are not truly client libraries but will be placed in SDK repos

be sure to go through the name of this (Azure Storage Blob NIO) before GA

Jonathan is okay with the APIView

Only need good java docs!

Next Steps:

Path to GA: nothing urgent here yet; focusing on iterating based on customer feedback
Follow up with Jonathan to get something blogged


[INF] Add pre-commit hooks to repository

Pre-commit hooks are a great way to push code style checks to the development machine, so that they automatically happen and thus we don't have to wait for the CI system to finish to  discover that it failed only on code style.
I will add in instructions to get started with pre-commit,  so that a bunch of checks are automatically done pre-commit.

I was just thinking about proposing optional pre-commit hooks yesterday! awesome


Disable failing bullet(-featherstone) tests on windows

🦟 Bug fix
Summary
We've recently accidentally started testing the Bullet and Bullet-featherstone plugins on Windows because one of our Jenkins nodes had Bullet installed. This created a few failures that looked like regressions, but were never meant to be tested. Instead of removing Bullet from the Jenkins node, we've decided to disable the failing tests so it's more explicit and so it'd be less steps to take in case we wanted to fix them down the road.
Also in this PR, I noticed that some of the tests were loading worlds from all plugins simultaneously instead of loading each plugin and world one by one. ~Perhaps some of the test failures are caused by that~, but in any case, I think we want to load the plugins one at a time, so I've made changes accordingly.
Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Maybe worth adding something like https://github.com/gazebosim/gz-rendering/blob/gz-rendering7/test/common_test/CommonRenderingTest.hh#L127-L138  to check for supported/unsupported?

Maybe worth adding something like https://github.com/gazebosim/gz-rendering/blob/gz-rendering7/test/common_test/CommonRenderingTest.hh#L127-L138 to check for supported/unsupported?

Done in https://github.com/gazebosim/gz-physics/pull/502/commits/0a86b2c4d63285e981a75b54d7d45740b15e86ce

The ABI checker is failing due to what seems the node running out of memory. Since this is only disabling tests, there should be no change in the ABI. Merging!


Prevent firing multiple requests?

From what I've seen in the code, no special treatment is done to prevent multiple network calls being fired in authenticateRequest.
This can be a problem, as a server can invalidate one of the returned tokens. Should the library handle this?

Great catch! We looked into this and I just opened a pull request that should fix the issue.

See #93.

Fixed by #93


Pagination Issue - Don't move to the next page

Laravel Version: 5.4
PHP Version: 5.6.30
Database Driver & Version: MySQL Ver 14.14 Distrib 5.7.17, for Linux (x86_64) using  EditLine wrapper

Description:

The pagination works apparently, but when I click to go to another page the data isn't loaded.
The links are generated successfully and the parameter is correct and is changed in each click: ?page=2 ?page=3...but it does not load the data from the new page.

Steps To Reproduce:
My Controller:
$data = \App\Model::paginate(10); return view('myview', ['data' => $data]);
My View:
{{ $data->links() }}

It appears to be working for me, please try to replicate the issue on a fresh laravel installation.

@themsaid I tried to install a new instance of laravel, but the problem persists and nothing appears in the log. I really don't know whats happening.
Any another ideia?

I dealing with a similar issue. I had to install Paginator from version 5.4 because I'm running WHMCS and they have heavily outdated components. The closest match I've found to solving this problem is that perhaps your NGinx is not configured properly, see here:
https://laracasts.com/discuss/channels/laravel/pagination-not-rendering-next-results
There they say you have to change in NGinx this:
try_files $uri $uri/ /index.php$args;
to
try_files $uri $uri/ /index.php?$query_string;
I would be curiously to know if you solved this problem because for me it's not working.


Exiting listin files logs exception

Describe the bug
After typing "n" for listing files it raises an exception

To Reproduce
Steps to reproduce the behavior:

Call python3 -m deepset_cloud_sdk.cli list-files for a wokspace with files
Type "n"
See exception

Expected behavior
No log line
Notes: this happens since the generator exits the context and does not close the loop properly with typer:
Here: (workflow)
here: CLI
Checklist

[ ] I added a label for the level of urgency of this bug (see definitions here)

cc: @wochinge


New release

Can you release the new version with protractor 2.0 please?

Sorry this was a mistake.


The use of Volcano batch scheduler

I used "kubectl apply -f spark-operator.yaml" to create the spark operator instead of using helm. Everything worked fine with the default scheduler.  Now I wanted to try the Volcano batch scheduler. How should I set the enableBatchScheduler flag in the yaml file? I added the following under sparkoperator in spark-operator.yaml , but it didn't work.
args:
- -enableBatchScheduler=true
Any suggestions? Thanks!

Have you enabled the mutating admission webhook by setting -enable-webhook=true? This feature needs the webhook to apply pod scheduler config to the driver and executor pods.

@liyinan926 Yes, I used spark-operator-with-webhook.yaml. The problem was that the operator failed to start after adding "enableBatchScheduler=true".  enableBatchScheduler is the parameter for helm install. I suspect we have a different name used in the yaml file just like enable-webhook for  _enableWebhook_. But what's the correct name?
Here is some additional information.
NAME                             READY   STATUS             RESTARTS   AGE
sparkoperator-5f9dc87556-j67tg   0/1     CrashLoopBackOff   1          13s
sparkoperator-init-756hs         0/1     Completed          0          13s
The spark-operator pod description looks like
Normal   Scheduled  3m21s                  default-scheduler  Successfully assigned spark-operator/sparkoperator-5f9dc87556-j67tg to minikube
Normal   Pulled     2m37s (x4 over 3m19s)  kubelet, minikube  Successfully pulled image "gcr.io/spark-operator/spark-operator:v2.4.4-v1beta2-latest"
Normal   Created    2m37s (x4 over 3m19s)  kubelet, minikube  Created container sparkoperator
Normal   Started    2m37s (x4 over 3m19s)  kubelet, minikube  Started container sparkoperator
Warning  BackOff    2m (x8 over 3m16s)     kubelet, minikube  Back-off restarting failed container
Normal   Pulling    107s (x5 over 3m20s)   kubelet, minikube  Pulling image "gcr.io/spark-operator/spark-operator:v2.4.4-v1beta2-latest"

The cmd flag is enable-batch-scheduler.

Great, the spark operator is now running. Thanks!
A new problem arose. Spark-pi didn't start and the pod was waiting for enqueue forever.
Type    Reason                 Age    From            Message
----    ------                 ----   ----            -------
Normal  SparkApplicationAdded  2m53s  spark-operator  SparkApplication spark-pi was added, enqueuing it for submission
I guess it may be related to Volcano's job queue. I tried default-queue, but it didn't work. How to specify the queue name in the spari-pi.yaml file?  Can anyone give an example? batchSchedulerOptions: queue: "queue1"

Yes
spec:
    batchSchedulerOptions:
        queue: <queue name>

hey @yuanchen8911 there is a demo regarding how to use queue: https://github.com/TommyLike/spark-operator-volcano-demo/tree/master/demos/queue

@yuanchen8911 recently I am working on integration testing on spark operator and volcano too. And found some issue regrading the cooperation:

Fix on spark operator: https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/pull/632  which was merged yesterday. and the image and the chart that I used which can work if you want a short way:

helm install incubator/sparkoperator --namespace spark-operator --set enableBatchScheduler=true --version 0.3.1 --set operatorImageName=tommylike/spark-operator --set operatorVersion=0.0.5 --set enableWebhook=true

Fix on volcano which makes gang-scheduling works: https://github.com/volcano-sh/volcano/pull/465.

Thanks, will try it. @TommyLike

Thanks a lot for your help. @TommyLike @liyinan926! It's working now.

Cool!

I have set the batchschedular to "volcano",but id do not work,why ,


Sudo necessity in ctest when update_VM.sh with option to install prerequisites

I tested the PR for the option to install prerequisites.
The script went through and no errors occured.
However, when I went to run the tests
cd ~/devel/buildVM/buils/SIRF/build
ctest -VV -R

then I receive the error
2: Test command: /usr/bin/python "-m" "nose" "--with-coverage" "--cover-package=sirf.Gadgetron" "src/xGadgetron/pGadgetron/"
2: Test timeout computed to be: 10000000
2: ERROR: HDF5 Error in ../../../src/H5FDsec2.c, line 348: unable to open file: name = 'tmp_1_1588583252375.h5', errno = 13, error message = 'Permission denied', flags = 13, o_flags = 242
2: ERROR: HDF5 Error in ../../../src/H5FD.c, line 812: open failed

This Permission denied error does not happen when I run
sudo ctest -VV -R

instead.

hmmm. this is very strange. Are you sure you haven't run sudo update_VM.sh ... at some point? I cannot see why the update script would do this (but then again, all bugs result in weird behaviour!)

ok maybe i did run sudo update_VM.sh

I'll download a fresh 2.1 and see what happens

Sorry for putting an unrelated error into this issue, I'll create a new issue if the answer isn't trivial.
fatal: ambiguous argument 'rel_4.0.1': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
From https://github.com/UCL/STIR
   8942f4e6..2a799b93  Siemens_mCT_additions -> origin/Siemens_mCT_additions
   fd8b7555..dcfda6b1  master                -> origin/master
 * [new branch]        release_4             -> origin/release_4
 * [new branch]        release_4.0           -> origin/release_4.0
 * [new tag]           rel_4.0.0             -> rel_4.0.0
 * [new tag]           stir_rel_4.0.0        -> stir_rel_4.0.0
error: pathspec 'rel_4.0.1' did not match any file(s) known to git.
CMake Error at /home/sirfuser/devel/buildVM/builds/STIR/tmp/STIR-gitupdate.cmake:147 (message):
  Failed to checkout tag: 'rel_4.0.1'

I ran cmake in build_VM and set the STIR tag to release_4, then re-ran the update script and got the same error. Suppose I could modify the default STIR tag in version_config.cmake, although that might get reset by the update script, too.

Didn't that happen last Friday as well, because the git fetch needed to be run with git fetch --tag?

yup. I thought I fixed that...

oh. maybe the problem is that version_config.cmake should specify origin/rel_4.0.1

Same error. I guess it's just not doing a git fetch?

can you create a snapshot (such that you can go back), and then do a git fetch by hand, and see what happens?

I ran git fetch --tags earlier (didn't think to create a snapshot, sorry) and then compilation was fine and all ctests passed.

Closing this and transferred discussion


Repo shows up as bare after migrating from svn

Gitea version (or commit ref): b9ae16d
Git version: 2.1.4
Operating system: Debian 8
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[ ] Not relevant

Description
After migrating an old svn repo following the guide here, the repo still shows up as bare in the ui, meaning it only shows instructions on how to initialize it instead of showing the code. The code is in the repo, when I clone the repo manually I get all the code.
When I commit & push a test file manually after this, the UI acts normal.

Did you see any errors in gitea.log?


version to 1.1.0

Codecov Report

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

@@             Coverage Diff              @@
##             master    #1536      +/-   ##
============================================
- Coverage     48.63%   48.62%   -0.01%
+ Complexity     1897     1896       -1
============================================
  Files           393      393
  Lines         11495    11495
  Branches       1192     1192
============================================
- Hits           5591     5590       -1
- Misses         5476     5477       +1
  Partials        428      428

Impacted Files
Coverage Δ
Complexity Δ

...amework/apollo/openapi/util/ConsumerAuditUtil.java
80.55% <0%> (-2.78%)
6% <0%> (-1%)

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 d80537a...5a66b2f. Read the comment docs.

Coverage decreased (-0.009%) to 52.353% when pulling 5a66b2fa8a16e0444d55a8557c12a71eb91164c9 on nobodyiam:version-to-1.1.0 into d80537a32429647f929ad34d3f8c1747a77e17df on ctripcorp:master.


DbContextOptionsBuilder UseInMemoryDatabase missing?

Steps to reproduce
This snippet of code is working on ASP.NET Core /EF 1.0 but after upgrading to 1.1 UseInMemoryDatabase is not resolved, has it moved or do we need to setup differently?
var services = new ServiceCollection();
services.AddEntityFramework()
.AddDbContext(options => options.UseInMemoryDatabase());
        ServiceProvider = services.BuildServiceProvider();

The issue
When using DbContextOptionsBuilder UseInMemoryDatabase is not found
Further technical details
EF Core version: (found in project.json or packages.config)  EF 1.1
Operating system: Windows 10
Visual Studio version: VS 2017
Other details about my project setup:

Actually, looks like it's a VS17 problem as there are a number of missing project references, will close this an EF issue.


Add integration tests

Description
I would be great to have an integration test for this package, to be sure it's working as expected.
I think for the beginning would be a test case where we run the example app, join the meeting, take a screenshot and compare this with the master screenshot great. It covers the integration with the native SDKs and checks if the user is able to join the meeting - and I think this is the most important thing.
We need to be sure that the Jitsi room is empty, because otherwise would be the UI a bit different. So generating a new room ID (like a uuid4) for every test would be good.
We should be able to run the integration tests in the Android Emulator and iOS Simulator with GitHub Actions 👍
I already started to implement this integration test (https://github.com/nilsreichardt/jitsi_meet_wrapper/tree/integration-tests). But I'm currently I stuck when I try to compare the screenshot with the master screenshot. So I created a Flutter issue for help: https://github.com/flutter/flutter/issues/103222

Will try to take a look at it the next days.

It's no problem for me to do this, I just wanted to create this issue to inform you / discuss the implementation with you, if needed 👍

Yeah, will try to have a look at your implementation. That's what I wanted to say ;)

I am sorry for not responding, but i currently don't have time to work on this issue.


Can create project without being an admin

I can create a project without being an admin. This does not seem to be correct.
Harbor v0.3.5.

Please clear browsing cache and try it again.
2016-09-10 4:11 GMT+08:00 bergtwvd<EMAIL_ADDRESS>
I can create a project without being an admin. This does not seem to be
correct.
Harbor v0.3.5.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vmware/harbor/issues/784, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEy15s8rtqcPg93y2TvVjX0zTFpgSO9Nks5qob1-gaJpZM4J5alg
.

Everyone signed up can create project as its owner act as project admin role.

That is correct, Currently any signed in user can create a project. However, this is not always desirable. For example, in my case, users should only have the rights to push into projects that they are a member of (not ones they create themselves on the fly). So I prefer this to become a site setting.

Just one additional comment. This isssue is (from user point of view) also related to the ability to delete a project (see https://github.com/vmware/harbor/issues/112). A site setting: allow project deletion by site admin only, or allow project deletion by the project admin,
P.s. Harbor v0.3.5 does not include #112.

Harbor provides a toggle for self-registration (default is ON), it would only allow admin to add user when the self-registration is turned off. Please refer it on our installation guide.

Yes, I know that option, and have already switched it "on".  But this option does not address this isssue.

I mean you should set this option to "off" that only allow admin to add user. The admin user can create a project and allocate 'developer' role for this project to others.

Sorry, I was confusing. I have already set self-registration to off.  But once the user has an account (created by the site admin) he can create projects has he likes. This is not desirable for every situation, and needs to be restricted to the site admin in these situations.

So far, by design, we can't prevent signed up user creating its own project.

Alothough the issue status got closed, I still wonder if this issue could be considered as a feature request for inclusion in the Harbor roadmap. Any thoughts on this?

Agree with @bergtwvd here: Would be nice to have control over who can create projects (and delete, as discussed in #112, once that is implemented).


Remove adding to sys.path when getting object.

We shouldn't need to do this, it should just happen on Package install.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#991  👈
#989
#990
#970 : 1 other dependent PR (#972 )
#971
#969
#968
#967
#966
#965
#964
#963
#962
main

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

Join @rohinb2 and the rest of your teammates on  Graphite


Task 01 -- Create GitHub account and fork two repositories

To access GitHub please create account or login.
To participate py-jupyter-nb repository please fork.
To participate nt8098-01-2022-2 repository please fork.

Report  your GitHub user link by repying to this message, e.g

https://github.com/dudung

This assignment is valid until 27 Jan 2023, 09.00 GMT+07.

https://github.com/ckhoirinaya

https://github.com/ntastutiningsih

Sudah membuat akun
http://github.com/jessicarusli/crispy-waddle


Make dashboard print a good error message when configuration is invalid

See https://github.com/dotnet/aspire/pull/3119#discussion_r1538599584

@JamesNK what configuration are you referring to here?  Is it authentication related?

Configuration here: https://github.com/dotnet/aspire/tree/main/src/Aspire.Dashboard#net-aspire-dashboard


xdg-desktop-portal-gnome: 42.1 -> 42.3

https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/compare/42.1...42.3?w=1
Changes in 42.3

Backport screencast session fixes

Changes in 42.2

Fix invalid usage of app chooder dialog after its destruction
Properly handle errors from file operations
Fix various memory leaks
Translation updates

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build xdg-desktop-portal-gnome


"no implicit conversion of Symbol into String" on failure_app.rb:83

I am getting this error with Devise 3.4.1, Ruby 2.2.0, and Rails 4.1.2. Here's the line:
options[:authentication_keys] = keys.join(I18n.translate(:"support.array.words_connector"))

We had a conflicting "support" key defined in a custom I18n locale file


Fix a typo in "maximum"

I was going to advise you to submit at PR at https://github.com/UPS-API/api-documentation but it seems that file is missing from there.. No idea why. If it's not fixed at the source it is likely to just get accidentally overwritten at some point.

I think The TForce* files were removed in an earlier update this year, I don't know why but they seem to be still working so I left them for now.

Ahh ok. If there is no other source for them I'm not opposed to merging this.


Bug-fix: Unable to rename list content type

Closes #4885
Noticed that for the post call to the csom endpoint, there was never a list:{listId} being passed, so it makes sense 😄
Resolved this so that the command now also will work on list content types.

Thank you @MathijsVerbeeck!

Manually merged


CLOUDP-167796: Migrate "Encryption at Rest using Customer Key Management" CLI stores to v2 sdk

Proposed changes

Jira ticket: CLOUDP-# CLOUDP-167796
EVG Patch: https://spruce.mongodb.com/version/6421cfcd0ae606fcdcda4707/tasks?sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC

Closes #[issue number]
Checklist

[x] I have signed the MongoDB CLA
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
[ ] I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
[ ] I have updated test/README.md (if an e2e test has been added)
[x] I have run make fmt and formatted my code

Further comments

@matt-condon @swattyT for this change we would need to move to the sdkv2-dev branch. Changes look good but let's hold with integrating it till we merge feature branch


Allow referrer for external websites for better analytics

As per Slack Discussion Thread,
Thanks, @mvshmakov for the deep dive:

Plausible identifies sources in 2 ways:

HTTP Referrer header.
UTM tags.

dvc.org has nofollow noopener noreferrer on all links and does not use manual UTM tags on any of them (proof attached). So, Plausible, in the case of dvc.org/docs/studio -> studio.iterative.ai/* requests, does not have a way to infer the source, so tags the request with “other”.

Screenshot

We cannot do anything with it on the Studio side because of the browser privacy features and the way Plausible works. Suggested solutions:

Allow referrer header in the links on dvc.org (and on all the rest of our websites that we want to track Studio links). I’m in favor of this option.
Manually UTM-tag all links that direct users to the Studio.

I would also prefer option 1 mentioned as mentioned by @mvshmakov. Also, as of 2023, it's already been years that major browsers have shipped with the fix.

It's not a recommendation but we might consider removing (as it will quick and straight forward solution) the noopener noreferrer from the rel attribute as I see almost every roughly almost more than 90% of traffic comes from the latest version of browsers.
Here is the source logic behind the external links. Here, we can create a domain whitelist and allow referrers.
This doesn't directly affect users or websites SEOs so I would say it's nice to have feature.

cc: @tapadipti @iterative/studio-frontend

@yathomasi @mvshmakov A clarification: The issue is not only with redirects to Studio, it's also with redirects to our other sites (eg, iterative.ai).  Option 1 will address issues with all these redirects, right?

The issue is not only with redirects to Studio, it's also with redirects to our other sites (eg, iterative.ai). Option 1 will address issues with all these redirects, right?

It depends on the analytics implementation on the respected websites. If analytics is using document.referrer to identify the referrer, then it'd work. Plausible on all websites will work.
Note that the fix in this repo would only work in one side. E.g., we still have the same noopener noreferrer thing on links on the Studio side, so dvc.org -> studio.iterative.ai would be tracked, but studio.iterative.ai -> dvc.org would not. This requires a separate fix on the Studio side.
@yathomasi I've dropped the support of noopener noreferrer in the Studio: https://github.com/iterative/studio/pull/5746. You can consider adding the list of trusted domains if you want to support older browsers.

Update: we've decided to go with rel="noopener", despite it is being implied on all modern browsers.


az extension add for Application Insights produces Directory not empty error.

This is autogenerated. Please review and update as needed.
Describe the bug
Adding extension for app insights to a deployment script has started to error.  Has been working up to now.  The script is run from a Windows Server build server.  The script is initiated from DevOps release pipeline.
Error is 'The command failed with an unexpected error. Here is the traceback:  ERROR: [WinError 145] The directory is not empty.  '
See below for output.
Command Name
az extension add -n application-insights --only-show-errors
or
az extension add --upgrade -n application-insights --only-show-errors
Errors:
2021-04-12T21:51:35.4438426Z ERROR: The command failed with an unexpected error. Here is the traceback:
2021-04-12T21:51:35.4460346Z ERROR: [WinError 145] The directory is not empty: 'C:\windows\ServiceProfiles\NetworkService\AppData\Local\Temp\tmpwtvhhesq\azext_applicationinsights\vendored_sdks\applicationinsights\models'
2021-04-12T21:51:35.4462016Z Traceback (most recent call last):
2021-04-12T21:51:35.4463132Z   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
2021-04-12T21:51:35.4472606Z   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 660, in execute
2021-04-12T21:51:35.4473602Z   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 723, in _run_jobs_serially
2021-04-12T21:51:35.4474427Z   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 716, in _run_job
2021-04-12T21:51:35.4477480Z   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\six.py", line 703, in reraise
2021-04-12T21:51:35.4478348Z   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 694, in _run_job
2021-04-12T21:51:35.4479552Z   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 331, in call
2021-04-12T21:51:35.4481079Z   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/init.py", line 811, in default_command_handler
2021-04-12T21:51:35.4505900Z   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/extension/custom.py", line 18, in add_extension_cmd
2021-04-12T21:51:35.4506763Z   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/extension/operations.py", line 327, in add_extension
2021-04-12T21:51:35.4507533Z   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/extension/operations.py", line 136, in _add_whl_ext
2021-04-12T21:51:35.4517954Z   File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/extension/operations.py", line 84, in _validate_whl_extension
2021-04-12T21:51:35.4518584Z   File "shutil.py", line 500, in rmtree
2021-04-12T21:51:35.4519042Z   File "shutil.py", line 390, in _rmtree_unsafe
2021-04-12T21:51:35.4519439Z   File "shutil.py", line 390, in _rmtree_unsafe
2021-04-12T21:51:35.4519826Z   File "shutil.py", line 390, in _rmtree_unsafe
2021-04-12T21:51:35.4520240Z   [Previous line repeated 1 more time]
2021-04-12T21:51:35.4520618Z   File "shutil.py", line 399, in _rmtree_unsafe
2021-04-12T21:51:35.4521009Z   File "shutil.py", line 397, in _rmtree_unsafe
2021-04-12T21:51:35.4521743Z OSError: [WinError 145] The directory is not empty: 'C:\windows\ServiceProfiles\NetworkService\AppData\Local\Temp\tmpwtvhhesq\azext_applicationinsights\vendored_sdks\applicationinsights\models'
2021-04-12T21:51:35.5294904Z To open an issue, please run: 'az feedback'
2021-04-12T21:51:39.6967856Z ERROR: The command requires the extension application-insights. Unable to prompt for extension install confirmation as no tty available. Run 'az config set extension.use_dynamic_install=yes_without_prompt' to allow installing extensions without prompt.
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
``

Expected Behavior
No error, loads the extension, continues.
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.21.0 *

Extensions:
application-insights 0.1.13

Additional Context

Seems like there is a change to behavior and need to set.  Did not see this in any release notes tho.
az config set extension.use_dynamic_install=yes_without_prompt


Update Rust toolchain to 1.61

Update to Rust release 1.61.0
🦀

[x] Update the version in rust-toolchain.toml (#2259).
[x] Run cargo clippy --all-features --fix, review and commit the automatic
fixes, and fix all reported lints. Try to resolve the root causes for
the lints rather than silencing them with #[allow(...)] (#2259).

Update the MSRV (optional)
Additional steps to perform in order to make the new minimal supported
Rust version:

[ ] Update the rust-version fields in all Cargo.toml files.
[ ] Update the msrv field in clippy.toml and fix all lints reported by
cargo clippy --all-features.
[ ] Update the MSRV shields in README files:

README.md
relayer-rest/README.md

[ ] Update the MSRV in the guide: guide/src/pre_requisites.md
[ ] Add a .changelog entry to the breaking-changes section,
announcing the new MSRV.

We are not using any 1.61 features yet (custom exit codes could be handy?), so no need to update the MSRV. The clippy failures are an issue in CI, though.


Initialization: revert change of default value of txindex

Even though Omni Core requires an enabled transaction index, changing the default value differs from what an user might expect when he or she switches from Bitcoin Core to Omni Core.
This PR restores the original default value to mirror Bitcoin Core's default behavior.
See: #42

I'm still concerned that this change will cause problems for integrators (who may have used this without realizing a txindex directive should be in the config since it wasn't needed) but as I can't actually think of an actual real world scenario (except refusing to start) it's probably just being overly risk averse - merging.

Yeah, it's aweful - either way. Though this one is the lesser evil in the long run, in my opinion.
Just make sure everyone gets the memo, so to speak. Re: integrators: it's mostly UI related, but the missing cs_main lock might justify an update nevertheless.


Cannot load Driver class error in zeebe-simple-monitor:2.1.0

Error : Caused by: java.lang.IllegalStateException: Cannot load driver class: org.postgresql.Driver
at org.springframework.util.Assert.state(Assert.java:97) ~[spring-core-5.3.9.jar:5.3.9]
DockerFile:
FROM ghcr.io/camunda-community-hub/zeebe-simple-monitor:2.1.0
COPY postgresql-42.2.23.jar /app/libs
Note:
Was working fine with 2.0.0 version of zeebe-simple-monitor

This is a duplicate of #298. The issue should be fixed with #254.


Pypi release

A placeholder issue to release Ansible SDK as a pypi package.

Initial release done on https://pypi.org/project/ansible-sdk/0.0.1/


Pick up new CodeMirror in release 1.4?

Are there already plans to pick up the new version of CodeMirror (with the new Twig mode) for version 1.4 of Brackets? I use a lot of Twig mixed with HTML and am looking forward to making a multimode extension using the "real" Twig and HTML modes. Maybe JavaScript, too.

Usually, code mirror integrations happen early in the cycle as that would give us enough testing window. The last code mirror integration happened as part of #11167 (cm master as on  May 26, 2015). The next code mirror integration will happen after release 1.4 if there are no blocking issues.

OK, so most likely in v1.5. Is Brackets still on a 4ish-week release/sprint cycle?

yes, 1.4 is due within the next 2 weeks.

Thanks.

I realize this is now closed so forgive me for commenting on a closed issue.
I just wanted to note that the post 1.0 release cycle has been more like a point release every 2 months or so.  @bobrocke if cm is updated at the beginning of the 1.5 release cycle you would be able to use the new Twig mode right away if you run Brackets off master.


Want to learn those award-winning papers

Hello, I would like to know where can I read those award-winning papers? Or, these papers have not yet been published?

ok, thanks!


Inputs.as_X methods are unintuitive

https://github.com/populationgenomics/production-pipelines/blob/f70c393faea03f3c382439708918159a3e89e5f5/cpg_workflows/workflow.py#L160-L187
These methods are used to cycle the outputs of previous stages into the next stage as input. Almost all our Stage outputs are Paths (required for the existence checking logic to trigger), but often we need String versions of those paths when using them as input. This creates an odd situation where the inputs.as_str() method should be perfect, but in practice is pretty pointless.
What I think it should do: Take the input to this method, and extract a requested value as a string
What it actually does: Take the input to this method, if it's not already a str, throw an exception. If it is a str, re-cast it as a str, then return that.
This feels like a functionality gap in the pipeline - in MANY places we have str(inputs.as_path(...), while inputs.as_str only has one usage which wouldn't break if we designed this properly.
It's a pretty core bit of functionality, but I would like to alter inputs.to_str to actually cast the relevant variable to a string, and fail if that's not possible, rather than the (silly, IMO) "check if X is a str, then cast as a str" logic we have.

Vivian to investigate:
Categorise under improving the developer experience.

I don't really care which team owns the pipeline, I want a better solution to this problem, and I'm happy to draft it myself.