Risk levels inaccurate due to undercounting in data sources vs wastewater data?

Summary

As people are increasingly using at-home tests instead of PCR, I'm concerned that the data sources for microCOVID are underreporting risk. Trends in wastewater data substantiate this concern
Am I missing anything, such that we think that microCOVID's risk calculations are still sufficiently accurate to be useful? If not, any suggestions on how to adjust to account for this?

Details
(HT: My friend Alice)
Because so many COVID cases aren't officially recorded, I checked to see if microCOVID's calculator factors in COVID levels in wastewater--wastewater is a more accurate way of measuring COVID levels. To do this, I did a site search of https://www.microcovid.org/ for wastewater and got no results. Then I checked the CovidActNow site, which you said that microCOVID sources from, and it doesn't track wastewater, at least not in Alameda County. See  https://covidactnow.org/us/california-ca/county/alameda_county/?s=30471905 . Because you said that microCOVID also sources from John Hopkins, I checked their COVID map here: https://coronavirus.jhu.edu/us-map --, from what I found, they don't appear to track wastewater either. See https://bao.arcgis.com/covid-19/jhu/county/06001.html .
Unfortunately, the COVID levels in Alameda County's wastewater are going up, and those levels are now higher than they were on February 9. You can see this from the screenshot I took below from https://data.covid-web.org/ . (I used "log" for the Y axis scale, so you can clearly see how COVID levels in wastewater have recently been changing.)

The CovidActNow and the John Hopkins COVID map don't reflect a recent rise in COVID levels to anything like the levels on February 9. So I don't think those sites are accurately reflecting the recent increase in COVID levels. I'm guessing that more people are using home tests (which are now much more easily available and are reimbursable by insurance) instead of PCR tests. The New York Times Case Tracker explains the following about COVID cases that are included on their graphs:

Confirmed cases and deaths, which are widely considered to be an undercount of the true toll, are counts of individuals whose coronavirus infections were confirmed by a molecular laboratory test.

This explanation is on the NYT's case tracker page for Alameda County here: https://www.nytimes.com/interactive/2021/us/alameda-california-covid-cases.html .
Given the increasing COVID levels in Alameda County wastewater, and given that microCOVID's calculator doesn't seem to factor in those increases, I think that microCOVID is underestimating the /COVID risk at events around Alameda County

@sameerjain0123 I'm not really sure how to interpret this wastewater data here. The increase that you're talking about from 2/9/22 to 2/15/22 goes back down after that. Possibly noise?
The microcovid model accounts for underreporting in general, but I don't know if it would account for a change in the underreporting factor due to a shift from people getting PCR tests to people using at-home antigen tests. It's not clear to me that the data you're sharing actually shows a statistically significant discrepancy here between JHU data and wastewater data given the possible noise/imprecision of the wastewater data, but I'm not an expert on the data side and will defer to others on that point.


Feature Request: View favorites only option

Would be nice to have a toggle to only see pokemon you have selected in favorites list.

Now added


Add the main structure to all pages

A basic header, footer and navigation. Nothing fancy or overly configurable at the moment.
Just the first basic framework for the UI.

Closing in favour of more specific tasks


Refactoring Bootstrapper to introduce better coverage and testing

I have completely refactored the bootstrapper. The initial problem why I started this is just that this simple tool got rather complex during the last year. In the beginning it was just ~80 lines, but more and more features were integrated which introduce also bigger complexity. Therefore, I refactored it to have some test in place and also removed some bugs which I discovered btw. I think this gives some benefit to all users of paket, as everyone checks in the bootstrapper and rely on its correct functionality.
The following items are tested from now on:

parameter evaluation
download strategies (github, nuget, cached)
download strategy resolution
bootstrapping behaviour

I also improved the CachedDownload strategy which before behaved like a bootstrapper on its own and now is only a strategy, and rely that the bootstrapper will do his job.
After refactoring we should have a test coverage of ~90%, before there was nearly none. The only downside is, that my refactoring increased the size of the bootstrapper by ~5kB, which is excusable if I look on the plus side.
Besides that the following bugs were removed

When you call paket.bootstrapper.exe prerelease and after that paket.bootstrapper.exe, the second call does not use the latest version
minor issue with selecting versions in nuget strategy when prereleases were not ignored effectively

The following features were also added.

non evaluated command line arguments are printed on console
with the parameter --help a help page is now displayed with short explanation of parameters

I'm sorry for the bigger PR, but for me it seemed like the best way to succeed.

Yeah. Sorry for that. Didn't want to hurt you.

@Stift great huge job! I wish we could write in in F#, in FP style, but we cannot.

@vasily-kirichenko Thx.
I also would like to do that instead of doing this csharpiness stuff, but the Fsharp.Core still blocks us from doing so.

I think it's fine for now, but it would make a cool case study to refactor this further to get rid of mocks and interfaces in C#.
But on the other hand I'm not sure if that brings us anything. This the bootstapper and I'm super happy that someone takes time to make that thing work well.

You can get rid of interfaces and mocks, but then you use delegates all over the place and pass them around. At least, the code is still readable. As said before, I just wanted to have tests for now and increase the coverage on that tool.
I'm absolutely happy if someone wants to join and make this cool case study (with me). Now that we have testing in place this should be even easier.

yes primary goal is to make that thingy useable and get everything under test. well done!


add sui-field-count for sui-indexer-alt

Description
title, so that we can replace hard-coded field count in pipelines.
a crate did very similar things but it's archived, so prob better to have our own impl, also b/c the functionality is relatively simple  https://github.com/discosultan/field-count
Test plan
added tests in models/

Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:
[ ] REST API:

@wlmyng thanks for the quick review, this is to replace hardcoded column count like
https://github.com/gegaowp/sui/blob/1a85800a7686e825f6258e8a034384ee6a88e845/crates/sui-indexer-alt/src/handlers/sum_obj_types.rs#L27

@gegaowp, broader question, is there a reason we can't use the existing field_count crate? It seems like it offers the exact same set of features, and it would make it easier for us to share the indexing framework if we re-used the existing crate (one fewer crate for us to publish/maintain).

@amnn

is there a reason we can't use the existing field_count crate

it's very similar indeed while as mentioned in the desc. the crate is archived and it's relatively easy to impl. so I decided to impl. one for our own.

a crate did very similar things but it's archived, so prob better to have our own impl, also b/c the functionality is relatively simple https://github.com/discosultan/field-count

Ah missed that, sorry! Makes sense.


Fix nightly build

ct lint --all --config .github/ct-redpanda.yaml
Linting charts...
Error: failed loading configuration: specifying both, '--all' and '--charts', is not allowed
failed loading configuration: specifying both, '--all' and '--charts', is not allowed
Error: Process completed with exit code 1.

https://github.com/redpanda-data/helm-charts/actions/runs/5687162122/job/15415137752#step:6:11

I pushed one correction to this fix as none of the Github action workflow was triggered. Our PR requires summary and lint jobs.


Refactoring Configurations

Describe the feature
@sfxcode  Should we change Docker Environment Configuration to MongoDB Configuration?

Needed REST Routes

[ ] Update Configuration at MongoDB
[ ] Restart Service (to activate new Settings)
[ ] "Register Configuration" with Values from Config-File


WIP [docs] improvements to docs related to JSON references.

WIP / don't merge :)
In your latest version of the docs, config/json_references/README.md contains a great example of how to use the config fragments in practice. Very handy and something I was missing in the previous docs. This complements docs/configuration.md very well now.
Not sure if I am supposed to make changes directly in the .md files but I found it was easier to read this way. If you like any of these ideas we can migrate them into the right place later.
Changes I made

adding links to jq website
explain environment variable interpolations the other way around (I found it more important to know what to use them for, then to explain why this works.)
removed unused json-pointer reference

Questions about the docs

These references can be nested. What does this mean, and what would be a use case for this?
Is the documentation easier to read when foo.yaml references bar.yaml? Or the other way around? I am undecided myself :)
"fragment" and "snippet" are used interchangeably in the docs. Snippet more often than fragment. Would it be easier to always use "fragment", as that is the name of the section as well ("Fragmenting Your Configuration")
do we need the directory ./config/ in the example, or does it only confuse the reader? I suspect you got it in there so that you can talk about the relative file paths?

Questions about benthos and/or fragmenting

does the config fragment that I use in $ref have to be a fully functional config on its own? or can it just a fragment that only works once it is referenced from a larger config?

I am asking because $ref: ./modules/group.yaml would be a more straightforward ref example than $ref: ./modules/group.yaml#/pipeline/processors/0

What happens if A references B and B references A? (circular)
What does benthos do when I load a config that is not functional?
You had some documentation about json-pointers before. Did you remove that completely?

Ace, changes look good.

"These references can be nested." is meant to mean that if config foo.yaml references config bar.yaml, which in turn references baz.yaml, then Benthos will resolve all of these references as it traverses them

I did reconsider the ordering of foo.yaml and bar.yaml but I don't have strong feelings either way

Good point, I got cold feet on the term 'fragment' at some stage because I also needed to talk about the 'fragment' of the path URI, which is something else entirely. I think it probably makes sense to change all cases of 'fragment' to 'snippet', will need a section title change, maybe 'Reusing Configuration Snippets'

Yeah that's in there just to make it clear that the path is relative, I don't think it's needed necessarily so if it adds confusion then I'm happy for it to be removed

No need for it to be fully functional on its own, but it does need to be valid YAML. I wanted to show in the main example that it's possible to access fields within the snippet as I consider it best practice to have functioning snippets that can be tested in isolation. I'm not opposed to simplifying the example but in that case I would at least want to follow it with a section explaining the paths and benefits of doing so.

Circular references get caught and reported as an error ('caught' in a very crude sense, I have a ceiling of reference layers that prevents it from happening)

If you try and reference a config that is broken then Benthos will print an error message similar to if the root config file was broken in the same way

I removed the json-pointers spec link as for most people the path 'is what it looks like' and the json references spec links to it itself in the relevant section. Not opposed to adding it back in but I'd be a little worried of sending people down a rabbit hole if they mistake it for being necessary reading.


Add Tags filter to search results

Essentially this will also contain a list of "Variables", though only those where the search matches to one of the Spout labels.

For the tag results, do you mean that it is an exact search on the label, and it doesn't include variables where the tag isn't an exact match? (But it's still essentially showing variables?)


WinUI 3: DataTransferManager.DataRequested event not firing for ShowShareUIForWindow

The following code is taken directly from https://learn.microsoft.com/en-us/windows/apps/develop/ui-input/display-ui-objects#for-classes-that-implement-idatatransfermanagerinterop
My breakpoint inside the DataRequested event handler is never hit and so when the Share UI opens no data is being passed to it.
#HomePage.xaml.cs
...
[System.Runtime.InteropServices.ComImport]
[System.Runtime.InteropServices.Guid("3A3DCD6C-3EAB-43DC-BCDE-45671CE800C8")]
[System.Runtime.InteropServices.InterfaceType(
    System.Runtime.InteropServices.ComInterfaceType.InterfaceIsIUnknown)]
interface IDataTransferManagerInterop
{
    IntPtr GetForWindow([System.Runtime.InteropServices.In] IntPtr appWindow,
        [System.Runtime.InteropServices.In] ref Guid riid);
    void ShowShareUIForWindow(IntPtr appWindow);
}

static readonly Guid _dtm_iid =
    new Guid(0xa5caee9b, 0x8708, 0x49d1, 0x8d, 0x36, 0x67, 0xd2, 0x5a, 0x8d, 0xa0, 0x0c);

private void Button_Click(object sender, RoutedEventArgs e)
{
    // Retrieve the window handle (HWND) of the current WinUI 3 window.
    var hWnd = WinRT.Interop.WindowNative.GetWindowHandle(App.MainWindow);

    IDataTransferManagerInterop interop =
    DataTransferManager.As
        <IDataTransferManagerInterop>();

    IntPtr result = interop.GetForWindow(hWnd, _dtm_iid);
    var dataTransferManager = WinRT.MarshalInterface
        <DataTransferManager>.FromAbi(result);

    dataTransferManager.DataRequested += (sender, args) =>
    {
        Debugger.Break();
        args.Request.Data.Properties.Title = "In a desktop app...";
        args.Request.Data.SetText("...display WinRT UI objects that depend on CoreWindow.");
        args.Request.Data.RequestedOperation =
            DataPackageOperation.Copy;
    };

    // Show the Share UI
    interop.ShowShareUIForWindow(hWnd);
}

Am I doing something wrong or is this broken?
Shamelessly CCing @oldnewthing as the seemingly main contributor to the docs linked above (feel free to reach me on Teams).

I tried out the code example as published, just to confirm that it works, and it does (I sent the string to myself via Outlook). Then I added the Debugger.Break(); line, and hit F5. When I click the button, the event handler runs, then the DataRequested handler runs, and VS stops in the debugger on that line.
I'll go ahead and close for now, but feel free to continue the discussion and/or reopen the issue if I closed it in error.
Thanks!
-Steve


Update ADT normalization docs

For CITE-seq, we're going to fall back on log1p if size factors fail rather than not normalizing at all. We'll need to document this!
Source: https://github.com/AlexsLemonade/scpca-nf/pull/343#discussion_r1245324370

Also document this new metadata variable in sce contents - https://github.com/AlexsLemonade/scpca-nf/pull/343#discussion_r1245384759

Closed by #121


refactor: rename camunda/zeebe repo

Description
Which problem does the PR fix?
The repository camunda/zeebe will be renamed to camunda/camunda, this PR adjusts all references to this repository.

WHY
The name of this repository will be changed to align better with its new role as a monorepo containing multiple products of the stack.
https://github.com/camunda/zeebe/issues/18206

related https://github.com/camunda/zeebe/issues/18206

What's in this PR?

I renamed all occurrences of github.com/camunda/zeebe. I didn't do this for camunda/zeebe as this will change occurrences for docker images (which we do not plan to change yet).
For posterity, the following script has been used.
#!/bin/bash

set -euox pipefail
path=$1

# Replace occurence in markdown files
find "$path" -type f -exec sed -i -E 's|github.com/camunda/zeebe([/#])?|github.com/camunda/camunda\1|g' {} \;

count=$(git -C "$path" status | grep modified -c)
echo "$count files have been updated."

if ag 'github.com/camunda/zeebe/' "$path" > /dev/null
then
  echo "There are still some occurences left, that need to be renamed! "
else
  echo "All occurences of 'github.com/camunda/zeebe/' have been renamed!"
fi

Checklist
Please make sure to follow our Contributing Guide.

Before opening the PR:

[ ] In the repo's root dir, run make go.update-golden-only.
[ ] There is no other open pull request for the same update/change.
[ ] Tests for charts are added (if needed).
[ ] In-repo documentation are updated (if needed).

After opening the PR:

[ ] Did you sign our CLA (Contributor License Agreement)? It will show once you open the PR.
[ ] Did all checks/tests pass in the PR?

@aabouzaid not sure why the IT are failing. Do you know?

@aabouzaid not sure why the IT are failing. Do you know?

Probably a glitch. Rebased to main and it worked as expected.
Thanks for the PR :raised_hands:


WithVolumes method added to Deployment

WithVolumes method allows to configure volumes on the Deployment object

Hi @yprokule please check this PR. It was essentially done besides my last two comments:
https://github.com/openshift-kni/eco-goinfra/pull/165/files#r1385208288
https://github.com/openshift-kni/eco-goinfra/pull/165/files#r1385209332
https://github.com/openshift-kni/eco-goinfra/pull/165/files#r1385208752
Es

/lgtm


fix(android): fix JS error when RN version is a github URL

What:
In file-operations.js parseFile(), validate the RN version string before doing the version check.

Why:
A developer using this tool will see a crash if importing react-native directly from github instead of using a release version.

How:
See changes in file-operations.js
Checklist:

[x] I read the contributor guidelines
[x] My commit messages & PR title follow Conventional Changelog Standard
[x] I added tests for my new feature

This is a nice catch. There seems to be some overlap with https://github.com/peggyrayzis/react-native-create-bridge/pull/37. Maybe we can combine the 2.

@jarretmoses if you want to add the fix and the new test to #37 that is fine with me

@dlowder-salesforce I think separate is fine. Mine is actually a WIP when I can get back to fixing 1 thing. This PR shows a nice way of handling the tests though thanks!

@jarretmoses merge conflicts resolved, tests are passing


Issue 12537 - Templatizing opEquals results in infinite recursion in the compiler

https://issues.dlang.org/show_bug.cgi?id=12537

@WalterBright This is ready to merge.

Looks reasonable to me.  @WalterBright ?

@WalterBright Ping

Thanks!


[Core] Reduce operation processor duplication

The currently implemented processors (commands, user context menu items) seemingly have some code duplication. See if a common base class can be created for the identical behavior. Also consider that support may eventually be implemented for message context menus items, too.

Closing, as it is handled by #118.


fix: update postgresql image tag to avoid bitnami broken release

Which problem does the PR fix?
Related to: https://github.com/bitnami/containers/issues/74788
What's in this PR?
Rollback to the latest working image to avoid the broken, broken release with an error at startup:
 2024-11-12T10:45:13.897968389Z /opt/bitnami/scripts/libpostgresql.sh: line 395: POSTGRESQL_REPLICATION_USE_PASSFILE: unbound variable

Checklist
Please make sure to follow our Contributing Guide.

Before opening the PR:

[ ] In the repo's root dir, run make go.update-golden-only.
[ ] There is no other open pull request for the same update/change.
[ ] Tests for charts are added (if needed).
[ ] In-repo documentation are updated (if needed).

After opening the PR:

[ ] Did you sign our CLA (Contributor License Agreement)? It will show once you open the PR.
[ ] Did all checks/tests pass in the PR?

It's expected the upgrade pipeline always fails as some of the released charts have the affected PostgreSQL versions.


muse-io doesn't work with Muse2016 model

It seems because of a change in how Bluetooth works, the Muse2016 can't pair with a MacBook/work with muse-io , am I right in asserting that?

@mrmayfield thanks for your interest. You are right! pyMuse gets the data sent by MuseIO via OSC messages and Muse2016 doesn't support MuseIO. We haven't tested it as we don't have any Muse2016.
It would be nice to bypass MuseIO and integrate Bluetooth support directly into pyMuse. We will work on it!

Thanks for the response. I am able to get those OSC signals via the Muse Monitor app though. I think that's the best workaround at the moment though you still have to sidestep MuseIO. I may hack around and see what I can come up with today to patch in support, what do you think?

Indeed, that's a proper solution for now. We have recently introduced a new processing pipeline framework that is quite powerful but that is not completely tested and integrated as it is still under development. We will probably continue to work on it in the next few months. You can take a look into the file test_ttih.py to see how to use it while we document it.
If you only need to extract data from the Muse without processing, you can bypass the pipeline and fetch the data from the IO. Any feedback would be helpful for us, although the development is still very preliminary!


some downgrade instructions are missing

the Method 1 you mentioned is for WebOS 1.x - 5.x and uses webosapp.club/downgrade
But there is also this method for WebOS 6.0 (which requires the activation of Developer Mode beforehand):
webosapp.club/online and then installing ExpertMode Downgrade application , then rebooting  the TV.
I didn't write the full instructions, but I guess the downgrade method for WebOS 6.0 should be included in your guide.
Thanks so much for your very helpful guide.. Best wishes.

I still do not understand did the firmware rollback work for you?


Respond to Queries about Platform

Summary
There are a few queries from Alex about the wording for the platform. I'm putting them here so we can discuss them visibly.
## Add stories page - Welcome to AutSPACEs registration
There was an unresolved query for Bastian to decide from your earlier comments about a sentence on the relationship between Open Humans and the AT Institute. I currently have:
The Alan Turing Institute has been working with Open Humans to create AutSPACEs. Is this wording okay?
Learn more page - Our goals
These are in a different order on the home page – and the wording is a little different (ie influencing rather than advising). Which is the preferred order/wording?
Content guidelines - What and who AutSPACEs is for
Do you still plan to add links for professional support, or should I delete the reference to these?
Content guidelines - What is and isn't okay to mention
Do you still plan to add a link for racial slurs?
Content guidelines - Writing on behalf of others
Do you still plan to add links for resources for parents/carers, or should I remove the mention of these?
Help - What does being an AutSPACEs moderator involve?
The current wording implies, but doesn't state outright, that moderators need to be autistic. Is this correct or yet to be decided? If correct, I'll make it explicit.

Learn more page - Our goals
These are in a different order on the home page – and the wording is a little different (ie influencing rather than advising). Which is the preferred order/wording?
I believe the wording on the home page is the more up-to-date one - I think the "influencing" wording comes from community feedback.

Content guidelines - What and who AutSPACEs is for
We decided on taking out references to other organisations as we don't have affiliations with them - however there were a lot of requests for linking to other organisations for support (e.g. Samaritans). Don't know if we ever settled this one.

Content guidelines - Writing on behalf of others
Do you still plan to add links for resources for parents/carers, or should I remove the mention of these? As above. A lot of this is around clarifying what the platform is and isn't for which is in the moderation guidelines

Help - What does being an AutSPACEs moderator involve?
The current wording implies, but doesn't state outright, that moderators need to be autistic. Is this correct or yet to be decided? If correct, I'll make it explicit.
A lot of people felt very strongly that moderators should be autistic, or that at least one autistic person should look over submissions - but we need to make sure that's feasible? One option to balance it might be to have an autistic person overseeing, or supporting, moderation overall who people could appeal to - but that might create a lot of pressure.

Following the co-working:
1. Welcome to AutSPACEs
Wording is okay as is but make a link to the PIS where we have more details on the connection between AutSPACEs & OH
2. Learn more page - Our goals
Keep the order from the front page (share, influence & educate) and then also add the headings on the "learn more" page
3. Content guidelines - who AutSPACEs is for:
Remove AutSPACEs cannot offer professional support, however, we can link you to appropriate sources if necessary.
4. Do we plan to link to a list racial slurs?
Remove reference to link as we don't have a good resource at hand
5. Links for resources for carers
Remove reference to If you need more support as a carer or parent, we recommend these resources: [link to resources?]
6. Who are the moderators?

What does being an AutSPACEs moderator involve?
Thank you for your interest in becoming a moderator for AutSPACEs. This is a hugely important and valuable role. As a moderator you will have a direct impact on the experiences of people using the AutSPACEs platform. You can help ensure that AutSPACEs is a welcoming and inclusive space where autistic people can be heard.

Need to be clear here that we are in the process of developing the process for community members to become moderators. Not live yet, reasons: data protection, ethics responsibility, …


Fix: Windows compatibility for file operations during parsing

Problem
Two Windows-specific issues in the PhenixParser:

The parser was using Unix grep command which isn't available on Windows systems
The file operations were using Unix-specific symlinks which failed on Windows systems

Changes
XML Parsing

Replace Unix grep command with Python's native file reading and regex for channel metadata extraction
Maintain same output format and behavior as original grep implementation

File Operations

Add Windows-specific handling for symlinks using hard links
Maintain original Unix behavior
Add directory creation for copy operations
Minimal changes to ensure cross-platform compatibility

Testing
Windows
Tested on Windows with network share paths:

Channel metadata extraction works correctly
Regular file copying works
Symlink operations are replaced with hard links
Tested path: \\samba-pool-mann-pub\pool-mann-pub\User\MarcOeller_PUB\Phenix\MJFF\24_10_22_MJFF_Lausanne\

Unix

Verified all functionality works as before on Unix systems
Original symlink behavior is preserved
Channel metadata extraction maintains original behavior

Done all the requested changes including pre-commit checks.


Deployment updates

Deployment script

Simplifying Parameters for deployment script:

All SQL related parameters are optional and populated with defaults for simplicity and security.
Resource group name is optional and can be inferred from the web app prefix
ARM template default is the local ./deploy.json

replace MSDeploy in ARM with PowerShell script Deploy

this fixes issue where cannot run the deployment script locally (#95)
simplifies deployment but removing the need to push zip packages to storage blob
clears the path for using Linux Web App in the future (the MSDeploy extension is only available for windows)

Other updates

Replace get-AzureRMContext command with the newer AZ equivalent - Get-AzContext -> confirmed this works the same in the cloud shell
Updated method of creating the landingPageAppRegistration by using the New-AzureADApplication -> this removes the dependency on the jq utility that is not installed by default on users' machines

ARM template

Add KeyVault support

Arm template deploys a KeyVault
Web app get managed identity with access to KeyVault
Connection string to SQL and AAD secret get stored in KeyVault and referenced in Web App via App Service KeyVault References for optimal security

Other

Fix SLQ firewall setting (#170)
Cleanup some variables and parameters in the ARM template.
Removed MSDeploy extension since it causes issues with publishing when not using correct CompressArchive version

That's fair. We can turn that back into a mandatory parameter.
But it's still an option to provide it if users want to....Maybe we can look at adjusting the naming convention? I noticed a lot of folks (as well as the official MS docs) recommend pre-pending the Resource Group Name with "rg"
Open to make the change(s) either way

Nah, it's cool. Not that big a deal given it's optional. I'll try to run
the installer tomorrow.
On Wed, Jan 26, 2022, 4:57 PM Alex Drenea @.***> wrote:

That's fair. We can turn that back into a mandatory parameter.
But it's still an option to provide it if users want to....Maybe we can
look at adjusting the naming convention? I noticed a lot of folks (as well
as the official MS docs) recommend pre-pending the Resource Group Name with
"rg"
Open to make the change(s) either way
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/Commercial-Marketplace-SaaS-Accelerator/pull/183#issuecomment-1022744410,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAPZZUJKHMCFE3CGWGF4R3UYCJ6XANCNFSM5ME2DO3A
.
You are receiving this because you commented.Message ID:
@.***
.com>

Happy to see this reviveved. Happy to finish the work on this if need be. Just let me know what needs to be done.
@code4clouds , @msalemcode let me know if you want to book a chat to talk though this.

We will follow this PR on #279


ISPN-11399 BasicComponentRegistryImpl can block when starting a compo…

…nent
https://issues.redhat.com/browse/ISPN-11399

integrated! thanks @wburns !


Include frontmatter metadata in directory_contents templatetag output

I'm not sure, but I feel like it's already resolved
@register.simple_tag(takes_context=True)
def directory_contents(
    context, directory: str = None, exclude: str = None
) -> Dict[str, str]:
    if not directory:
        request = context["request"]
        directory = request.path
    elif isinstance(directory, SafeString):
        # Force SafeString to be a normal string so it can be used with `Path` later
        directory = directory + ""

    if directory.startswith("/"):
        directory = directory[1:]

    content_paths = get_content_paths(directory)
    contents = []

    for path in content_paths:
        if path.name != "index.md":
            path_slug = path.name[:-3]
            content_slug = path_slug
            content_directory = get_content_directory()

            if directory:
                content_slug = f"{directory}/{path_slug}"
                content_directory = content_directory / directory

            if exclude:
                if exclude.startswith("/"):
                    exclude = exclude[1:]

                if exclude == content_slug:
                    continue

            (_, metadata) = get_html_and_markdown(content_slug)

            contents.append(metadata)

    return contents

the line below precisely
 (_, metadata) = get_html_and_markdown(content_slug)

Yeah, I think you are right. Looks like I added this in 0.15.1. 😄


Fix semantic check for max_length < total_len

max_length is specified in bytes while total_len is counted in bits, so convert
accordingly when comparing.

thanks for catching this


dart:html not support webkitEnterFullscreen

I am using Flutter for development. Now there is a scenario. I need to click on a video to achieve a full screen display effect. In Chrome browser, I can use Request FullScreen, but it doesn't work in safari browser. I tried to use webkitEnterFullscreen and it generated an error, here is my error message.

Questions like this are best suited for a user forum like StackOverflow, where many users are present to answer specific questions.

I think you want the enterFullscreen() method from VideoElement.
I'm closing the bug since dart:html has this support, but please re-open the bug if that method is broken.


Automated cherry pick of #8590: fix: secgroup cache tenant_id

Cherry pick of #8590 on release/3.5.
#8590: fix: secgroup cache tenant_id

Codecov Report

Merging #8591 into release/3.5 will decrease coverage by 2.66%.
The diff coverage is 0.00%.

@@              Coverage Diff               @@
##           release/3.5   #8591      +/-   ##
==============================================
- Coverage         6.14%   3.47%   -2.67%
==============================================
  Files              761     307     -454
  Lines           118373   63376   -54997
==============================================
- Hits              7269    2205    -5064
+ Misses          110445   61016   -49429
+ Partials           659     155     -504

Flag
Coverage Δ

#aFlag
3.47% <0.00%> (-2.67%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/cloudcommon/notifyclient/notify.go
1.83% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/cachedimages.go
1.73% <0.00%> (-0.04%)
:arrow_down:

pkg/compute/models/capabilities.go
0.00% <0.00%> (ø)

pkg/compute/models/cloudregions.go
1.54% <0.00%> (-0.04%)
:arrow_down:

pkg/compute/models/cloudsync.go
0.00% <0.00%> (ø)

pkg/compute/models/cloudsyncelasticcache.go
0.00% <0.00%> (ø)

pkg/compute/models/dbinstance_secgroups.go
0.00% <0.00%> (ø)

pkg/compute/models/dbinstancejoints.go
0.00% <0.00%> (ø)

pkg/compute/models/dbinstancenetworks.go
0.00% <0.00%> (ø)

pkg/compute/models/dbinstances.go
0.74% <0.00%> (-0.01%)
:arrow_down:

... and 465 more

Continue to review full report at Codecov.

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


HTML in prompts is swallowed and not visible in chat

Version: 1.83.0-insider (Universal)
Commit: 254b455d8f1f02b3621e1c7c6c19798ea58945b9
Date: 2023-09-27T05:57:10.217Z
Electron: 25.8.2
ElectronBuildId: 23977753
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 22.5.0
Steps to Reproduce:

Open Copilot Chat
Type a prompt such as

I'd like to create the worker like this:
<script>
  const worker = new Worker('js/Worker.js');
</script>
And then use it in the code like this:
  myWorker = document.worker;
Can I do that?

When you submit the prompt, it will appear in the chat history but WITHOUT the <script> tags or what's between them!
(Actually, when pasting the above prompt, even Copilot didn't see the tags or their content!  That's a new one on me!)

Hi @ChrisMiami ,
Thanks for filing the issue.
For now, you can use wrap your code containing html into markdown inline code (wrapped with backticks) or code blocks (wrapped with triple backticks), e.g.,
I'd like to create the worker like this:
\`\`\`
<script>
  const worker = new Worker('js/Worker.js');
</script>
\`\`\`
And then use it in the code like this:
  myWorker = document.worker;
Can I do that?

(without backslashes before backticks)

Thank you for patience with this!

https://github.com/microsoft/vscode-copilot-release/issues/107


Question about forcing state objects to use the registry

I have models coming in from many different places in my app and I would like them to all be forced to use the registry. For example, if I new SomeModel({ id: 1 }) and a model with ID 1 is already in the registry, I would like it to return that, instead of a new state object. Is it possible to highjack the state constructor and inject something like that?

You can create simple wrapper to do that, something like
function storeSomeModel (data) {
    return registry.lookup(data.modelType, data.id) || new SomeModel(data);
}

Hi, sorry to drop in on this @kamilogorek, but could you expand on the above suggestion a bit?
-How and where would I hook into this? model.fetch and model.save?
@adamyonk you wouldn't happen to have an example of whatever solution you ended up with?
Cheers.

going to close this, feel free to re-open if unanswered.


.haml file extension not working without .html on Turbo

Hi,
thanks for the great new feautures!
Detail:
Env
Rails 7.0.4
Ruby 3.1.2
haml-rails 2.0.1
"@hotwired/turbo": "^7.2.0"
Scenario
Create new app with any scaffold (customers by example)
I have no show view: Edit and create goes from index directly to form and back if successfully saved (i do'nt think that this matters)
Turboframes not applied (all links like before turbo, so that turbo defaults to the body)
Turbo is inited and works, see it in developer console and on the speed on the browser.
Current Behaviour
Now change app/views/customers.index.html.erb to index.haml
Visit http://localhost:5100/customers/3/edit
click Submit
=> The Browser History (url) remains on /customers/3/edit
=> The Form remains visible (looks like redirect_to customers_path did'nt work
=> The new html is doubled: the content of head added below the body and the content of the new body (customers/index) below.

Then change index to index.html.haml
navigate to the form and click submit
it all works like expected:
=> the browser history changes to /customers
=> its displaying the customers list like expected
So, for now i can work but would be happy if i can name .haml files like usual without the html extension
All the other views (edit, partials like _form) are named just by .haml (example: edit.haml)  and are working properly. I just had to rename the index view for the form-submission. index.haml would work for navigating by link! Mentioned behaviour is only by redirect after Form Submission.
many thanks!
Christian

Hello! I'm afraid this is not a Turbo bug, nor a turbo-rails bug either.


Why did you rename el.min.js to gr.min.js?

Your Environment

flatpickr version used: 4.6.9
Browser name and version: Google Chrome 106.0.5249.62 (Official Build) (64-bit)
OS and version: Windows 11 Version 22H2 (OS Build 22621.608)

Why did you rename el.min.js to gr.min.js ?
The ISO 639-1 code for Greek is el. The el code is used in every framework, e.g. Angular. There is no gr code.
Also, this is a breaking change for every code flatpickr is integrated into. For example, the Formio platform now reports:
flatpickr: invalid locale el

Formio.js:1832          GET https://cdnjs.cloudflare.com/ajax/libs/flatpickr/4.6.9/l10n/el.min.js net::ERR_ABORTED 404

Is there any good reason for this naming change?

I just observed this in a project that I work on as well.  el is the correct language code for Greek.


Reject received mails

Hi,guys
look at the mail.log：

who can help me please,help.

I send a mail from another server to modoboa,and get the log above.Do anyone has solutions?

Here comes new problem:
The qq.com mail server sent twice ,the first time failed ,and the second time success.I tried many times,but nothing changed.Need i to add qq.com or anything else configuration to any files?

Hi,
it looks like you are sending emails from a blacklisted IP address. Postscreen is enabled on your server and protects you against SPAM. Those log messages are normal. If you want to receive, just try with a valid sender (use a gmail address or equivalent).

China have the Grate Fire Wall as strong as the great wall.Gmail is not so convenient,i will have a try later.And qq.com should not be in any blacklist,it is a normal domain.

Ok. Since your requests are not related to Modoboa but to Postfix, could you please ask your questions on its official mailing list ?
Thank you.

OK,thank you.


Make sure to clearly document the behavior and supported scenario for log classifications

We need explicit docs that state:

The user cannot and should not modify the array after passing it to az_log_set_classifications
The user must make sure to end the array with a terminator.
What does passing NULL or an empty array mean, and why it is distinct.
User-defined classifications are supported.

cc @JeffreyRichter, @RickWinter

User-defined classifications are NOT supported. They happen to work but we are not committed to this. Also, the function to log something is internal; not public.


Adding Filter Bottom Sheet

Summary
Describe the goal of this PR. Mention any related Issue numbers. Please note that we do not normally
accept new externally-contributed PRs to this repo unless it's something Slack-relevant and came
up in prior discussion
Requirements (place an x in each [ ])

[ ] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[ ] I've read and agree to the Code of Conduct.

Superseded by #101


WebSocket...

don't forget ./bootstrap.sh ...

Hi @erqan, excuse me for the long delay in reviewing this.
Websocket support is a great idea, thanks for working on it!
I'm just concerned that we are adding quite a lot of new code to twister compilation without adding a configure option to disable them. What do you think, may optionally disable compiling this extra code in a non messy way?

merged, thanks!
I actually got a compilation failure with websocket enabled due to some openssl defines:
https://github.com/zaphoyd/websocketpp/issues/599
I'm unsure if we should rather fork their main repository to include the compilation fix instead.


Error create image from Dockerfile

Hello @danihodovic!!
I've a problem with image creation
Step 7/10 : RUN poetry config virtualenvs.create false && poetry install --no-interaction #!COMMIT
 ---> Running in 3212599f0a54
Skipping virtualenv creation, as specified in config file.
Installing dependencies from lock file

  SolverProblemError

  Because celery (5.0.5 git rev allow-heartbeats-in-tests) depends on pycurl (==<IP_ADDRESS>) which doesn't match any versions, celery is forbidden.

  So, because celery-exporter depends on celery (5.0.5 git rev allow-heartbeats-in-tests), version solving failed.

  at /usr/local/lib/python3.8/site-packages/poetry/puzzle/solver.py:241 in _solve
      237│             packages = result.packages
      238│         except OverrideNeeded as e:
      239│             return self.solve_in_compatibility_mode(e.overrides, use_latest=use_latest)
      240│         except SolveFailure as e:
    → 241│             raise SolverProblemError(e)
      242│
      243│         results = dict(
      244│             depth_first_search(
      245│                 PackageNode(self._package, packages), aggregate_package_nodes
The command '/bin/sh -c poetry config virtualenvs.create false && poetry install --no-interaction #!COMMIT' returned a non-zero code: 1

I tried change dependency and celery repository, but still failing

@hiaselhans updated the dependencies in #72. Try building now. I've pushed the latest and 0.0.2 tags to danihodovic/celery-exporter.


chore(dependencies): react

Coverage remained the same at 100.0% when pulling 19098b4ab95a0f3bd18f46484f960aceb4037e6e on dependencies/react into 93896d34b07c77c72067128b548b625628f9d775 on master.

Coverage remained the same at 100.0% when pulling 19098b4ab95a0f3bd18f46484f960aceb4037e6e on dependencies/react into 93896d34b07c77c72067128b548b625628f9d775 on master.


Improve logging framework and configuration

The logging framework right now relies on the python logging module which has rich configuration capabilities which have not been utilized yet. Currently the logs are output on stderr which are redirected to some files when running the builder and writer as daemons. This could be improved with loghandlers for easier access to the logs.

duplication of issue #9

Has been improved. Future issues will address specific changes.


Backport "Avoid jpath in example" to LTS

Backports #20775 to the LTS branch.
PR submitted by the release tooling.
[skip ci]

No regressions detected in the community build up to lts-20902.
Reference


Grant: Substrate Tokenomics Survey

Project Abstract
A survey of some economic models used to develop Substrate (Dotsama) blockchain/token economies.
The published literature will be from the rational expectations equilibrium (a.k.a. no-arbitrage) approach to economic analysis.
Grant level

[x] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[ ] A BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (aUSD/USDT) address for the payment of the milestones is provided in the application.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).

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

I think this would be a valuable addition to the space, but the price does seem rather expensive.
This was filed as a Level 3 grant (> $100k), but I only see three milestones, each for $18k (= $54k). Perhaps there is something I am missing here or it was simply a typo?

@Noc2:

add the overview section:

Done, and I've cleaned out non-research elements from the milestones.
@Noc2 and @laboon:

the price does seem rather expensive

A couple of things will help a lot:

Could you point to grants you consider comparable? (I did seek guidance here but got no response)
Could you indicate items/topics/milestones you think should be de-scoped.

I'll wait the other reviewer feedback to see where you all land before revising scope etc.

Thanks for the application. After reading it, I struggle to see the clear scope and contribution of this study. As far as I understand, you intend to "[...] provide a creative synthesis of existing token-economy research" of the Polkadot parachains? How would that look like? You state that you do this by reviewing their whitepapers, and published/working papers. While many of the former exist, rigorous (academic) token economic research is mostly absent. From the existing whitepapers, most parts focus on the usecases and initial distribution schemes. The token economics is mostly limited to some arbitrarly defined inflation rate which is split between collators and potentially stakers (if existing). As another dimension of your analysis, you mention different types of tokens. I'd not expect much other tokens than utility tokens that pay for transaction fees, are used in governance for voting and/or might be used for staking. Other token types are virtually absent as they'd constitute clear securities.
You also state that you will not be answering "[...] any particular token-economy design question". Further, I am also missing details on how you intend to analyse the situation with respect to the rational expectations equilibrium. The high price-tag and those open points make me question the contribution of the study and thereby how much it is needed.
In the case I've misinterpreted your approach, could you further elaborate?

Thanks @jonasW3F and @dsm-w3f for the thoughtful feedback. I believe we are at 4 out of 5 reviewers?
@dsm-w3f thanks for the prompt to update my Linked-In status. If you could update your comment accordingly, I'd appreciate that. I'm currently looking for my next contract.

@Noc2 and @laboon:

the price does seem rather expensive

A couple of things will help a lot:

Could you point to grants you consider comparable? (I did seek guidance here but got no response)

As best I can infer/guess... the comparable you have in mind is Milestone 1 of Uncollateralized Stablecoin Research
Correct?

Context to proposed budget:
I assumed (correctly it appears) my day rate would be out of budget. I used the midpoint of the Glassdoor salary distribution for a Senior Economist (USA): USD 156k p.a.
I was originally unable to find a related research topic. The only grant I was familiar with related to re-implementation of prior on-chain IPFS grants @ 15K USD/month
Since then I found Milestone 1 of Uncollateralized Stablecoin Research

@dsm-w3f

What will be the methodology planned for searching papers in the following categories?

I've added methodology to the Milestone 1 deliverables.

Is common to use systematic approaches for doing academic literature reviews, such as systematic reviews or systematic mappings. This increase the confidence in the review. Working papers and whitepapers are considered grey literature and could have another approach for searching.

This exercise will be closest to a "Rapid Review", see Grant MJ, Booth A. A typology of reviews: an analysis of 14 review types and associated methodologies. Health Info Libr J. 2009 Jun;26(2):91-108. doi: 10.1111/j.1471-1842.2009.00848.x. Review. PubMed PMID: 19490148.

There is only one researcher doing all the work. How would you deal with researcher bias in the data collection/extraction for the papers in this case?

I have adjusted the source of the research to eliminate mysely as a source of bias in the collection of research papers.
The Polkadot networks are those Parachains elected as at 19 December 2022.

We are developing an appropriate template for research grant submission.

That is great.  This application targets the current template requirements, since that is all that is known.

This is working in progress and should be ready soon. My apologies to have to deal with an inappropriate template for deliverables in a research grant. To summarize, the main deliverable for a research grant is the knowledge generated by the research, which should be transferred to the audience in some format, in your case a research paper. In this way, the final delivery from the grant should be the full paper available online somewhere (a preprint on arxiv.org would be enough).

This was addressed under Future Plans:

The working paper will be posted to SSRN (e.g. FEN - Cryptocurrency Research eJournal), IDEAS, Arxiv (q-fin.GN)

I've repeated the detail in the final milestone.

The deliverables in your application are most research questions. What would be expecting to receive in those deliverables? Text, tables, methodology, all of them? It is unclear to me the format of the deliverable and if all prerequisites to evaluate them will be present (methodology, raw data, analysis procedures, text describing the results). Usually, research projects are organized and developed in this order (could be different in your case): goals definition, methodology definition, execution, raw results extraction, data analysis, comparison with related work, complete the writing of the paper, and publishing. Could you please explain what will be the process that you will follow to perform the research and how they are time-based- related to your milestone deliveries planned? The milestones should be time-based in the order of delivery.

I've attempted to address these questions.
Please let me know if anything further is required.

Researcher Profile, could you please provide a profile in at least one research indexer (Google Scholar, Researchgate, or another one)? This is just to have your publication record.

https://www.researchgate.net/profile/Mark-Van-De-Vyver-2

@jonasW3F

Thanks for the application. After reading it, I struggle to see the clear scope and contribution of this study. As far as I understand, you intend to "[...] provide a creative synthesis of existing token-economy research" of the Polkadot parachains?

I've clarified this point.

You state that you do this by reviewing their whitepapers, and published/working papers. While many of the former exist, rigorous (academic) token economic research is mostly absent.

The presence/absence of rigorous (academic) token economic research is the subject of this survey.
How many papers are required to say "rigorous (academic) token economic research is mostly" complete? This depends on your idea of 'rigor' and 'complete'. If you know of an existing survey establishing what you claim, could you please point it out?

From the existing whitepapers, most parts focus on the usecases and initial distribution schemes. The token economics is mostly limited to some arbitrarly defined inflation rate which is split between collators and potentially stakers (if existing).

I currently share this assessment. But, I'm not persuaded this state-of-affairs is because richer ideas don't exist.

As another dimension of your analysis, you mention different types of tokens. I'd not expect much other tokens than utility tokens that pay for transaction fees, are used in governance for voting and/or might be used for staking.

As above.

Other token types are virtually absent as they'd constitute clear securities.

Or are other token types virtually absent because they haven't been introduced?  Nonetheless, I've clarified that what is/not considered a security is out of scope.

You also state that you will not be answering "[...] any particular token-economy design question".

Correct, this is a survey, hence limited to what the existing literature addresses. Within the scope of the deliverables, I am not committing to solving any particular token-economy design question.

Further, I am also missing details on how you intend to analyse the situation with respect to the rational expectations equilibrium.

I use REE to delimit the scope of the genera token-economy research literature.  The REE framework naturally suggests some features of an economy, and I've now indicated where that is.  I had given an outline of the approach when justifying the exclusion of cryptocurrencies.
Let me know if the changes don't address a particular point to your satisfaction.

@taqtiqa-mark thank you for your answers. After we started this application review, we approved a new template for research grants application. Would you mind adjusting your application to this new template? I think there will be a few changes but especially in the deliverables section, we will have a better structure. Regarding your answers:

Rapid Review is ok as a methodology since time is always a constraint. Just make sure that this doesn't affect the quality of your review and state the approach in the methodology. I think you will be able to find proper guidelines to perform this kind of review.
Researcher bias is more on how the researcher extracts data and analyses it since could be influenced by its background and beliefs than to set a fixed scope for data for analysis. Usually, research bias is reduced by having more than one researcher doing data analysis in an independent way and comparing the results. As this cannot be done when having only one researcher at least plan to declare this threat to the validity in the paper.

For now, I'll wait for my colleagues to circle back to their comments. Let me know if you plan to adjust the application to the new template.

For now, I'll wait for my colleagues to circle back to their comments. Let me know if you plan to adjust the application to the new template.

I'll also wait on their feedback before moving to the new template.

This pull request has been mentioned on Polkadot Forum. There might be relevant details there:
https://forum.polkadot.network/t/polkadot-the-centralized-decentralized-ecosystem/1412/7

Hi @taqtiqa-mark friendly reminder to look at the requested changes above. Thanks!

I've updated the application to use the new research template.
I've reduced the budget as requested, and update the scope accordingly.
Appreciate any feedback and suggestions.

I added some comments/requests in the body of the application. I think now the proposal is a more informal paper (working paper). Is that right? I made some comments considering the formalism of research papers. If the focus of the paper has changed, let me know and some of my comments regarding methodology could not be applicable. There are other comments that need to be fixed anyway.

@dsm-w3f , thanks for the detailed feedback. It will help if you can add Blocking: before each detail that is blocking approval, and break it into a separate paragraph.
Re the search - I'm surprised you had access, unless you are a resident of NSW? To confirm, they took about a week to respond? That was the time frame I was advised.  Did they indicate which of the databases they searched?

It will help if you can add Blocking: before each detail that is blocking approval, and break it into a separate paragraph.

I expect that all be resolved/answered before my approval.

Re the search - I'm surprised you had access, unless you are a resident of NSW? To confirm, they took about a week to respond? That was the time frame I was advised. Did they indicate which of the databases they searched?

I just used the link that you posted. For me is just a search engine, Is it something different from that? Why use a service that is not freely available to anyone? Any advantage to using this service?

I expect that all be resolved/answered before my approval.

I've resolved all the issues I can. I've asked @Noc2 to resolve the only open issue - unless you do so you're self.

Why use a service that is not freely available to anyone?

This is the debate about the subscription vs surveillance business models.

Any advantage to using this service?

These databases provide impact factors which are used in the selection criteria you have been reading for some time now.  While flawed they are useful as an initial quality filter that is not biased against the newest research.

I expect a delay of a week or two wrt Milestone 1:
It has taken a while to disentangle what blockchain token economy features arise from non-discretionary chain properties (Substrate requirements) and what are discretionary (Polkadot implementation choices).
The good news is that, so far, the problematic features are discretionary and can be elided wlog. The bad news is the descriptions will have to be by reference to Substrate - otherwise the text will read as criticisms/refutation of claims that DOT is not a security, and distract from the objective - bringing to light tools/technology applicable to designing a token-economy.


Support deploy cilium related services

https://skywalking.apache.org/docs/skywalking-showcase/next/readme/#features
I think this table is not updated, and is Cilium k8s only?

The documentation has been updated, and the Cilium is k8s only.

Which parts in the docs are mentiong scopes? K8s or docker compose or both?

Which parts in the docs are mentiong scopes? K8s or docker compose or both?

Sorry, I forget to adding note about this.


hallelujah!

regardless,monsieur.
the content would be irrelevant to the repository.
it shall be..
that..
may i know the origin that u have beening offline of the qq for long time?
we , the qq group fellows all miss u cordially.
could we be casted for ur one glimpse?we desire to have ur assistance and softness.
please,your highness.we begged for one opportunity of the pity taken.
forgive my irritation.
SALUTARY!

qwq

暌违数月。难忘雅言。盼吕佬早归。😭😭😭😭😭😭

好啊

lyt！！

暌违数月。难忘雅言。盼吕佬早归。😭😭😭😭😭😭

好啊

lyt！！

难忘雅言。盼吕佬早归。😭😭😭😭😭😭

好啊

lyt！！


versioning: derisk deployment w/ poor man's versioning

Versions currently used marks starting at version -0
Adds a %dummy mark
Symlinks future upgrades of mark types to the %dummy mark, preventing kick-resubscribe loops, however this has poor UX, because the subscriber isn't aware that the versions are out of syncs. This technique also requires more effort when the marks are upgraded, because all subscriptions must be restarted by hand

This PR significantly derisks the deployment timeline, because once this is merged the only hard dependency for release is the actual OTA logic itself, which is fairly constrained in scope.
A full implementation of versioning is to follow in subsequent PRs
Reviewers:

Want hard approval from @arthyn
@ryjm, @tomholford you should try to wrap your brains around this, it's worthwhile to understand why we're doing it and the necessity of version negotiation

spoke about this a little to liam but I really want to understand what steps we'd need to take to avoid having to manually update each (notwithstanding making everyone else do it). my naive assumption was to just write a gate that uses a version:state top level face that becomes the only change one needs to make their upgrade their marks. obviously this is easy from just a single player app, but i'd really like to understand what scaling / p2p syncing problem make a more elegant solution untenable. i'm currently assuming it's a fundamental design choice to avoid a much more malevolent problem, but that fact that i can't seem to nail it down.
case in point - having to walk people through graphs store updates for each app was an experience i don't want to recereate, especially since i had to go trough a bunch of old ones and do the same.
again this is coming from the right side of the bell curve but it's been nagging me for a while. @liam-fitzgerald gave me a good starting point to that today but i cant shake the feeling that there's a better way to do this. hopefully liam and i come to some sort understanding as he trashes my house tomorrow.

We still need to do this for for DMs, but it's a less pressing issue, as it
doesn't materially impact the network as much
On Tue, Oct 04, 2022 at 03:37:11, Jake Miller @.***>
wrote:

spoke about this a little to liam but I really want to understand what
steps we'd need to take to avoid having to manually update each
(notwithstanding making everyone else do it). my naive assumption was to
just write a gate that uses a version:state top level face that becomes
the only change one needs to make their upgrade their marks. obviously this
is easy from just a single player app, but i'd really like to understand
what scaling / p2p syncing problem make a more elegant solution untenable.
i'm currently assuming it's a fundamental design choice to avoid a much
more malevolent problem, but that fact that i can't seem to nail it down.
case in point - having to walk people through graphs store updates for
each app was an experience i don't want to recereate, especially since i
had to go trough a bunch of old ones and do the same.
again this is coming from the right side of the bell curve but it's been
nagging me for a while. @liam-fitzgerald
https://github.com/liam-fitzgerald gave me a good starting point to
that today but i cant shake the feeling that there's a better way to do
this. hopefully liam and i come to some sort understanding as he trashes my
house tomorrow.
—
Reply to this email directly, view it on GitHub
https://github.com/tloncorp/landscape-apps/pull/966#issuecomment-1266529340,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALFCFFSJRL65UNKLWGZYORTWBPNCPANCNFSM6AAAAAAQ34H7GE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@ryjm, @tomholford you should try to wrap your brains around this, it's worthwhile to understand why we're doing it and the necessity of version negotiation

Thanks for flagging this. Of course I am still a hoon n00b, but tead through the changes and seems pretty straightforward.

a hoon… what? someone needs to take a gander at the bible (you know the one)
On Wed, Oct 05, 2022 at 1:17 AM, tomholford @.***>
wrote:

@ryjm https://github.com/ryjm, @tomholford
https://github.com/tomholford you should try to wrap your brains around
this, it's worthwhile to understand why we're doing it and the necessity of
version negotiation
Thanks for flagging this. Of course I am still a hoon n00b, but tead
through the changes and seems pretty straightforward.
—
Reply to this email directly, view it on GitHub
https://github.com/tloncorp/landscape-apps/pull/966#issuecomment-1267953797,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPYHEYDNNFRHMKGCWUQXYLWBUFM3ANCNFSM6AAAAAAQ34H7GE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@ryjm @arthyn @tomholford We good here?


Add warning generators

Add generators of EnergyScaleWarning, TooManySamplesWarning and TooFewSamplesWarning warnings.

I am a bit worried about providing TooManySamplesWarning. without knowing the ground states of a problem creating a warning about drawing too many samples is not a great idea.
What if the first excited state is highly degenerate and you need a billion samples to see the ground state? - regardless of how we implement this specific Warning, it will throw an error for this specific example which is extremely misleading.

There is a case to be made that that's a very poor QPU problem, though I agree distinguishing that case will be very difficult.

I disagree with that comment. It may simply be a hard problem with a hard landscape that other heuristics will fail too (possibly worse than the QPU).

Fair enough, and it is definitely true that there will be many heuristics worse than the QPU at that problem. In any case, there is no way (that I know of) to detect that case, so maybe better to leave "too many samples" as a research topic.

#255 adds EnergyScaleWarning and ChainStrengthWarning

do you want me to wait for this to be merged before adding TooFewSamplesWarning

#255 has been merged

so another question, the samples related warning are applicable to classical solvers as well... you think they belong to dwave.system or dimod

Let's keep them in dwave-system for now


f222 support

Is the f222 model supported? And if not, is there any workaround?

You can load local ckpt/safetensor  https://lama-cleaner-docs.vercel.app/models/stable_diffusion#load-local-ckptsafetensors


CI has 54 warnings under Annotations

https://github.com/RustAudio/rodio/actions/runs/8711480431


index 50 is out of bounds

Hi
I am trying to use convert_dataset.py on my simulation. I converted the xtc to pdb containing only CA, having 100,001 MODEL. The number of residues are 489 and I run as follow:
python convert_dataset.py --MDfolder data/pdb/  --num-residues 489
I tried also
python convert_dataset.py --MDfolder data/pdb/ --pdb-start 1 --num-residues 489 --train-interval 2000 --validate-interval 2000
but I get:
Generate Train
Start: 1th PDB
Traceback (most recent call last):
File "convert_dataset.py", line 344, in
features, edges = convert_dataset_md_single(MDfolder, startIndex=1, experiment_size=1, timestep_size=50,
File "convert_dataset.py", line 304, in convert_dataset_md_single
features.append(read_feature_MD_file_slidingwindow(MDfolder+"ca_"+str(
File "convert_dataset.py", line 129, in read_feature_MD_file_slidingwindow
feature[numStep, 0, int(words[4])-aa_start] = float(words[5])
IndexError: index 50 is out of bounds for axis 0 with size 50
From the code I could not see where the error is from.
The demo ca_1.pdb worked fine.  I am using 1 GPU A100 and 60G of memory
Any help to understand the options requirement?

Did you find any solution to this?

Yes -
I add --test-interval 2001 too. Basically 100,001/50 ~ 2001

Thanks!


Documentation/API improvement: SceneReference is serialized so we must check AssetGuidHex not empty, else need IsValid method

I wanted to check if SceneReference was null before using it, but due to serialization, Unity creates a default instance with invalid fields (sceneAsset is null, strings are empty, other properties cause exception on access).
So, basically, my null check if (mySceneReference != null) is always verified, and my code tries to use it even when not set.
Trying to access BuildIndex then causes an obscure error:

KeyNotFoundException: The given key '' was not present in the dictionary.
System.Collections.Generic.Dictionary`2[TKey,TValue].get_Item (TKey key) (at <7560840559c84ffbb83a08c4696f01f7>:0)
Eflatun.SceneReference.SceneReference.get_Path () (at Library/PackageCache/com.eflatun.scenereference@1.2.2/Runtime/SceneReference.cs:26)
Eflatun.SceneReference.SceneReference.get_BuildIndex () (at Library/PackageCache/com.eflatun.scenereference@1.2.2/Runtime/SceneReference.cs:31)

There's not much to do about it if we want to serialize the whole class, but at least the README documentation should indicate in usage that before using the field, it may be good to check for if (!string.IsNullOrEmpty(mySceneReference.AssetGuidHex) or the likes.
I also tried to check mySceneReference.sceneAsset != null, but the field is internal so I could not access it. I suppose we could add a bool IsValid() method that checks sceneAsset to avoid the more complicated AssetGuidHex check.

In fact, I found what I suggested in a competing (but unmaintained) third-party repository: https://github.com/JohannesMP/unity-scene-reference/blob/master/unity-scene-reference/Assets/source/SceneReference.cs#L39
Check the IsValidSceneAsset getter:
#if UNITY_EDITOR
    // What we use in editor to select the scene
    [SerializeField] private Object sceneAsset;
    private bool IsValidSceneAsset
    {
        get
        {
            if (!sceneAsset) return false;

            return sceneAsset is SceneAsset;
        }
    }
#endif

It is even better than my suggestion as it also checks for SceneAsset type, as sceneAsset is merely an object.

Good idea, I will get to it soon.

@hsandt Implemented in #24. Will be included in the next release.

Included in 1.3.0.


Mixer adapter HandleAuthorization() called twice in 1.0.0-snapshot.0

After upgrading my Mixer and adapter from 0.8 to 1.0.0-snapshot.0, I'm seeing the adapter's HandleAuthorization() function being called twice per request instead of once as expected.

Can you please elaborate on what attributes you are seeing? Is it happening
for a single sidecar?
On Mon, Jul 2, 2018, 9:02 PM Scott Ganyo<EMAIL_ADDRESS>wrote:

After upgrading my Mixer and adapter from 0.8 to 1.0.0-snapshot.0, I'm
seeing the adapter's HandleAuthorization() function being called twice per
request instead of once as expected.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/6804, or mute the thread
https://github.com/notifications/unsubscribe-auth/AJGIxtcm3YCLGKj_rxGI9NbPRsTsD15zks5uCuzXgaJpZM4VAQrN
.

@theganyo can you share a dump of your rules?  is it possible we have multiple rules configured for the handler?

It also looks like the handler is run with two different contexts (differing sets of attributes).

NAMESPACE      NAME                     AGE
istio-system   apigee-rule              2h
istio-system   kubeattrgenrulerule      2h
istio-system   promhttp                 2h
istio-system   promtcp                  2h
istio-system   stdio                    2h
istio-system   tcpkubeattrgenrulerule   2h```

BTW: My apigee-rule is simply:
apiVersion: config.istio.io/v1alpha2
kind: rule
metadata:
  name: apigee-rule
  namespace: istio-system
spec:
  match: destination.namespace == "default"
  actions:
  - handler: apigee-handler.apigee
    instances:
    - apigee.authorization
    - apigee.analytics

@kyessenov Could you take a look at this please?

@theganyo You are seeing a Check call from ingress/ingressgateway, and then another one at the server-side sidecar. If you get latest build, you should condition on context.reporter.kind==outbound and source.labels to select ingress check, or context.reporter.kind==inbound and destination.labels to select the sidecar server check.
Attribute 196 is context.reporter.local which got deprecated.

The conditions that I need to use in my rules keep changing and I'm very confused. Last time I had an issue with changes to Mixer calls (moving to 0.8) it was recommended that I select on namespace. Is there a FAQ on how rules should be set up now - for at least the most common scenarios? I assume there's some overall matcher strategy that I haven't quite grokked so that my rules won't break from release to release? Or is this just being worked out iteratively?

We had several last-minute changes to update the rules, mostly due to the increased amount of data piped into mixer. Conceptually, everything is same, but the rules must be more selective to maintain compatibility with older versions. There is a new dimension context.reporter.kind that selects which side of the connection attributes are flowing from. The values are inbound for the server and outbound for the client.
In a typical deployment, a request goes through at least two proxies:
(internet) -> (ingress proxy) => (app proxy) -> (app)
The middle connection has two Check calls. One outbound from ingress and inbound to the app. This is a different model from <0.8 when ingress check was treated as "inbound to ingress". It's a consequence of the whole redesign of the networking abstractions in the last version.
If your intent is to apply a check on the ingress, then you should apply a predicate of the form context.reporter.kind = "outbound" && source.labels["app"] == "ingressgateway". If your intent is to apply a check on all incoming connections to the backend app, then use a predicate context.reporter.kind == "inbound" && destination.labels["app"] == "backend".
Let me know if this makes things a bit more clear. We'll try to document these changes in the release notes.

Re: namespace. That's another last-ditch attempt to fix the model pre-release. The new config selection uses the namespace of the reporter to scope the config. That means we use the config namespace of the client for outbound, and the server for inbound. Placing the config into the right namespace would make the rule visible to mixer.

Ok, thanks. FYI - I tried your rule, but it looks like context.reporter.kind isn't available in 1.0.0-snapshot.0. I'll switch to a later build and try it soon.

I've now moved from 1.0.0-snapshot.0 to just building off the release-1.0 branch and this no longer seems to be an issue. Did something change?

We merged the rename context.reporter.kind change about 8 days ago. So it sounds like you picked the build after the change.

Sorry, no I mean the original issue is no longer happening. In other words, my original rule:
match: destination.namespace == "default"

is working as expected again and HandleAuthorization() is only being called 1 time.

May we get a dump of attributes that you see? I think we should expect to see two calls...

@costinm did you by any chance disable ingress checks?

I'm now seeing "Creating bag with attributes" calls, but a single call to HandleAuthorization():
2018-07-10T22:52:44.954980Z	debug	attributes	Creating bag with attributes: &CompressedAttributes{Words:[wwTcvmHzvQ7Dlui2qwj43GlKJAAOOwmo istio://default/services/helloworld outbound curl/7.54.0 e5024c32362cc6c4 /hello x-envoy-decorator-operation helloworld.default.svc.cluster.local:5000/hello x-api-key localhost 4e418c41-3526-91f7-a5d4-c7fa698ed597 <IP_ADDRESS> */* istio-system helloworld.default.svc.cluster.local default helloworld kubernetes://istio-ingressgateway-84698b4d5d-q8n9g.istio-system],Strings:map[int32]int32{3: -18,4: -14,17: -6,18: -10,19: 90,22: 92,25: -4,131: 92,152: -15,166: -1,190: -2,191: -17,192: -16,193: -15,197: -18,201: -3,},Int64S:map[int32]int64{},Doubles:map[int32]float64{},Bools:map[int32]bool{177: false,},Timestamps:map[int32]time.Time{24: 2018-07-10 22:52:44.883501408 +0000 UTC,},Durations:map[int32]time.Duration{},Bytes:map[int32][]byte{},StringMaps:map[int32]StringMap{15: {map[-9:-1 121:-5 122:135 31:-10 100:92 118:113 98:-12 102:-11 46:-13 123:-5 33:-6 86:-4 32:90 -7:-8]},},}
2018-07-10T22:52:45.046282Z	debug	attributes	Creating bag with attributes: &CompressedAttributes{Words:[helloworld.default.svc.cluster.local default kubernetes://istio-ingressgateway-84698b4d5d-q8n9g.istio-system wwTcvmHzvQ7Dlui2qwj43GlKJAAOOwmo istio://default/services/helloworld /hello sec-istio-authn-payload CkVjbHVzdGVyLmxvY2FsL25zL2lzdGlvLXN5c3RlbS9zYS9pc3Rpby1pbmdyZXNzZ2F0ZXdheS1zZXJ2aWNlLWFjY291bnQSRWNsdXN0ZXIubG9jYWwvbnMvaXN0aW8tc3lzdGVtL3NhL2lzdGlvLWluZ3Jlc3NnYXRld2F5LXNlcnZpY2UtYWNjb3VudA== x-api-key e5024c32362cc6c4 localhost 4e418c41-3526-91f7-a5d4-c7fa698ed597 <IP_ADDRESS> */* curl/7.54.0 cluster.local/ns/istio-system/sa/istio-ingressgateway-service-account helloworld kubernetes://helloworld-v2-795b456c84-l5nlg.default inbound],Strings:map[int32]int32{3: -3,6: -16,17: -6,18: -11,19: 90,22: 92,25: -15,131: 92,152: -1,154: -18,155: -2,163: -16,166: -4,174: -16,190: -5,191: -17,192: -2,193: -1,197: -18,201: -19,},Int64S:map[int32]int64{151: 5000,},Doubles:map[int32]float64{},Bools:map[int32]bool{177: true,},Timestamps:map[int32]time.Time{24: 2018-07-10 22:52:45.026808004 +0000 UTC,},Durations:map[int32]time.Duration{},Bytes:map[int32][]byte{150: [0 0 0 0 0 0 0 0 0 0 255 255 10 1 0 78],},StringMaps:map[int32]StringMap{15: {map[46:-14 -9:-4 32:90 33:-6 118:113 86:-15 122:135 123:-10 31:-11 98:-13 100:92 55:134 121:-10 102:-12 -7:-8]},},}
2018-07-10T22:52:45.049282Z	debug	adapters	HandleAuthorization: Subject: []interface {}{authorization.Subject{User:"", Groups:"", Properties:map[string]interface {}{"json_claims":"", "api_key":"wwTcv..."}}}, Action: authorization.Action{Namespace:"default", Service:"helloworld.default.svc.cluster.local", Method:"GET", Path:"/hello", Properties:map[string]interface {}{}}	{"adapter": "apigee-handler.apigee.istio-system"}

Oh, it appears someone removed destination.uid from the client-side telemetry. That makes it impossible to resolve destination.namespace to apply the rule.

@costinm https://github.com/istio/istio/blob/master/pilot/pkg/proxy/envoy/v2/eds.go#L129 this line seems to be not executed and breaks mixer rules. What happened, any ideas?

@theganyo another possibility is that you have some old envoy lurking around. Are you sure you are using the latest proxy in your test?

It's hard to be completely sure, but it certainly should be. I:

started a clean Kubernetes env
grabbed the latest Istio build: https://gcsweb.istio.io/gcs/istio-release-pipeline-data/daily-build/release-1.0-20180710-09-15/
built my Mixer against release-1.0 branch and updated the samples/istio/istio-demo-auth.yaml policy and telemetry to use my image
applied istioctl kube-inject -f samples/helloworld/helloworld.yaml

If a previous proxy crept in, I don't know how.

I think I know what's happening now. For Check() calls on the client-side (gateway here), destination.uid is not available. It's only available for Report() (due to how envoy picks an LB endpoint post routing, not during routing). Our kubernetes adapter uses this attribute to derive destination.namespace, which you use in the policies. What we do know on the client during the check call is destination.service.namespace, however, which on kubernetes is guaranteed to match destination.namespace (part of k8s isolation contract).
@douglas-reid Do you think it is reasonable to add a derivation from destination.service.namespace to destination.namespace? Given that this is going to be a common attribute to use, I think it'd be useful to derive for client-side (gateway) checks.

@douglas-reid side note: it's painful to decode compressed attributes in these reports. We should print decoded attributes if possible.

Also, using the matcher you suggested above:
match: context.reporter.kind == "inbound" && destination.labels["app"] == "backend"
Remains unusable in latest daily build. It doesn't match any requests to my service.

I'll have to debug why the rule does not work... I swear it should, and tests partially exercise that. Can you confirm that the rule is placed in the same namespace as destination, and that the pod has a label app=backend?

Ah... ok. I'm guessing the 2nd part of that rule with destination.labels["app"] == "backend" is just an application label and doesn't have any special meaning? So, I should be able to simply use context.reporter.kind == "inbound" to match any pod in the namespace. Is that correct?

Yes, that would match whatever pod in the namespace of the rule.
On Wed, Jul 11, 2018, 4:29 PM Scott Ganyo<EMAIL_ADDRESS>wrote:

Ah... ok. I'm guessing the 2nd part of that rule with destination.labels["app"]
== "backend" is just an application label and doesn't have any special
meaning? So, I should be able to simply use context.reporter.kind ==
"inbound" to match any pod in the namespace. Is that correct?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/6804#issuecomment-404341833, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJGIxvAoe6-3vTj3UKzQo2IzOY5z7bilks5uFopwgaJpZM4VAQrN
.

Ok, thanks. So my original issue I have here is resolved. I don't know if you want to leave this open for the destination.service.namespace/destination.namespace and the compressed attributes attributes issues you mentioned above...

👍 I'll close it. I reopened this issue to be able to track it more easily from github UI.


Separating Pubs and Subs

This should now be easily doable, and will simplify a lot the topic interfacing.
Note we wouldn't be able to easily remove a publisher, while an interfacing sub is also setup, but this isolates the issue to a more specific use case.
Implementing dual update loop (one for all state, one for diffs only) both running, would make that cleanup simpler, and more solid for multimaster (no need to rely on get_num_connections, instead we wait for the full state loop to run and cleanup leftovers...)

Done and 0.3.0 has been released.


[Feature Request] Is there a plan for vue3 compatibility and support?

Existing Component
否
Component Name
vue3 compatibility and support
Description
Element, is it just a maintenance phase now? Do you have plans for compatibility and support of vue3?

YES!  🎉🎉🎉 Element Plus - A Vue.js 3.0 UI library 🎉🎉🎉
https://github.com/element-plus/element-plus/issues/147

Duplicate of #20375


Pin grabbits and pybids to specific versions in Dockerfile

These two packages evolve quickly and often break backwards compatibility. We should pin them to be in control when our side needs updating when pybids API changes.

#1281 works for containers. The python distribution requires we also set versions on the setup script (i.e. here)

Are we worried about that?

Oh no, just to note it down
On Fri, Sep 14, 2018, 15:45 Chris Markiewicz<EMAIL_ADDRESS>wrote:

Are we worried about that?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/issues/1279#issuecomment-421363094,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkhxg7A_Q8jZr35YN4DzMWpk6uBUHrIks5ua7LigaJpZM4WnRsO
.

I personally wouldn't be.
Best,
Chris
PS Apologies for brevity and potential typos. This message was composed on
a phone.
On Fri, Sep 14, 2018, 9:45 AM Chris Markiewicz<EMAIL_ADDRESS>wrote:

Are we worried about that?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/issues/1279#issuecomment-421363094,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkpx_Gg42K8lxlWb2eOakunTOy9vxSks5ua7LigaJpZM4WnRsO
.


Fixing Logo in Navbar

What happened?

Fixing the "Cloneit" logo in navbar.
How can we reproduce this bug?
NA
Desktop Information (Optional)
No response
Urgency (Optional)
Medium priority

I would like to work on this issue under gssoc22
Please assign me this issue!


Bump build number

Bump build number to have a build compatible with osqp-eigen 0.7.0 . We should eventually setup migrators for osqp-eigen, but in the short term this should work fine.
Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


Add new _foundation_unicode and _FoundationCShims c modules to windows build script

Now that Foundation is producing new C modules (_foundation_unicode and _FoundationCShims) that clients depend upon because we do not enable library evolution for our modules, we need to ensure these modules are correctly installed into the just built SDK like the existing dispatch C modules.

https://github.com/apple/swift-corelibs-foundation/pull/4991
https://github.com/apple/swift-collections/pull/395
https://github.com/apple/swift-foundation/pull/708
@swift-ci please build toolchain Windows platform

This corrected the issue in the windows toolchain build (the build above made it much farther than before)

@swift-ci please smoke test

This also needs a change to the packaging manifest in https://github.com/apple/swift-installer-scripts.

This also needs a change to the packaging manifest in https://github.com/apple/swift-installer-scripts.

Yep I'll post a change to that repo that also includes updates for all of the new libraries being added

Error: Error: swift.exe exited with code -1073741515.

-1073741515 = 0xc0000135, which I believe is DLL not found. I think that there are some path tweaks needed.

Error: Error: swift.exe exited with code -1073741515.

-1073741515 = 0xc0000135, which I believe is DLL not found. I think that there are some path tweaks needed.

Thanks! That's super helpful, there's likely still an issue to resolve here but this PR at least gets us a lot closer. Previously the toolchain build failed while building TSC since it couldn't find these modules but now it makes it all the way to the swift-inspect build before failing. I'll investigate what might be missing, perhaps we're not copying one of the new Foundation dll's over properly

@compnerd it looks like this change currently fails with the existing SCL-F because these _foundation_unicode / _FoundationCShims directories do not yet exist. Do you have a suggestion on how we could update the build script to only copy these if they exist so that we can stage this change in without requiring it to be landed in lockstep with the Foundation recore merge?

Hmm, you could check if the directory exists via the Test-Path command in powershell.

@swift-ci please smoke test

@swift-ci please smoke test


Wrong ad prefab search filter if there are other assets with a similar name

Hi guys!
I ran into an SDK initialization issue when trying to test ads in the Unity editor.
I have a script named "RewardedAdManager" and DummyAppodealClient finds this script and tries to use it as an ad and I get an error.
https://github.com/appodeal/appodeal-unity-plugin-upm/blob/4c9c09738284b39a5d78bdb380e8163474f2e050/Runtime/Platforms/Monetization/Dummy/DummyAppodealClient.cs#L219
I suggest adding an explicit asset type to the filter string:
var assetGuids = AssetDatabase.FindAssets(prefabName + " t:prefab");

It helps for me.
Perhaps you should mention this behavior somewhere, because it's not obvious that you shouldn't have assets with names similar to your prefab's name)
Thank you!

@EraCat2, hi. Thanks for your suggestions!
I already renamed those files to minimize the risk of having other assets with similar names. This change will be included in v3.1.x release which should hopefully be published in 1-2 weeks.
I like your idea to use a type filter when finding test ad assets. I added this task to my backlog.


TOP p1/p2 adjustments for aether strats

NA raid community aka Aether generally uses Sausage Roll's strats for TOP
P1 toolbox: https://ff14.toolboxgaming.space/?id=758088204654761&preview=1
P2 toolbox: https://ff14.toolboxgaming.space/?id=043186470764761&preview=1
differences from existing module:

Group numbers for P1 are inverted - G1 is NW CCW, G2 is N CW - I didn't change this because I figured it would be too much trouble for a purely aesthetic change, the existing module does priority fine
Pivot point for Pantokrator safe spots is NE/SW instead of N/S
Party Synergy G2 order for Remote Glitch is GPOB - purple and orange don't swap, they just go to arena edge
Swap priority for P2 flare stacks is north rather than south

There are presumably additional differences in later phases but I haven't gotten that far since I prog in PF

whoops gotta fix my shitty math

the logic for panto NE/SW is completely wrong, not sure what i did but this needs another pass

ok, it wasn't THAT wrong