Add config for Jira base url

Summary

Ticket Link

Fixes https://github.com/mattermost/mattermost-plugin-jira/issues/860

Hello @varundey,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

Thanks for this @varundey :+1: Given the known requirements, this looks good to me.
I'm planning on closing https://github.com/mattermost/mattermost-plugin-jira/issues/860 as "Won't Do" since the requirements are unclear. I'll be closing this PR as a result if that happens. Thanks again for submitting this.

Closing due to invalid ticket https://github.com/mattermost/mattermost-plugin-jira/issues/860
Thanks for your work on this @varundey!


Cad1 fix

Hotfix for v0.3.0. Adds level1 correction to deal with very quiet reference signals.
Other additions:

Adds function compute_rms in clarity.utils
Adds test function for compute_rms
Add level1 parameter in compute_haaqi function
Add level1 value when calling compute_haaqi in cad1.task1.baseline.evaluate.py

This hotfix will be pushed into main in a different way to deal with the different updates.


New package: Superfacility v0.1.0

Registering package: Superfacility
Repository: https://github.com/NERSC/SFAPI.jl
Created by: @JBlaschke
Version: v0.1.0
Commit: 03371024fda162aef83ef4c3f481234c8f78cfba
Git reference: HEAD
Description: Julia Client for the NERSC Superfacilty API

[noblock] Looks good to me, although I'm confused that the bot didn't complain about the repo URL not ending with the package name... 🤔


 I am getting an error in this line.
I tried conda install utils, pip install utils but none of these seem to work.
How can i install this utils package.
Thanks

utils refers to utils.py in models

oh yeah I saw that later on thanks


Bump to v1.2

Signed-off-by: TomSweeneyRedHat<EMAIL_ADDRESS>First time using release.sh script, we'll see what Travis CI thinks.

Replaced by https://github.com/projectatomic/buildah/pull/862


[linux] Multiple partitions result in null mountpoint, description

For example, when examining an SD card being used as a system drive for something embedded, I get the following object:
{
    "device": "/dev/mmcblk0",
    "description": null,
    "size":<PHONE_NUMBER>4,
    "mountpoint": null,
    "name": "/dev/mmcblk0",
    "protected": false,
    "system": false
}

What I expect to see is more like:
{
    "device": "/dev/mmcblk0p2",
    "size": "67108864",
    "mountpoint": null,
    "name": "/dev/mmcblk0p2",
    "protected": false,
    "system": false,
    "description": "system-boot"
},
{
    "device": "/dev/mmcblk0p3",
    "size": "1073741824",
    "mountpoint": "/media/rsi-bryan/system-a",
    "name": "/dev/mmcblk0p3",
    "protected": false,
    "system": false,
    "description": "system-a"
},
{
    "device": "/dev/mmcblk0p4",
    "size": "1073741824",
    "mountpoint": "/media/rsi-bryan/system-b",
    "name": "/dev/mmcblk0p4",
    "protected": false,
    "system": false,
    "description": "system-b"
},
{
    "device": "/dev/mmcblk0p5",
    "size": "1675624448",
    "mountpoint": "/media/rsi-bryan/writable",
    "name": "/dev/mmcblk0p5",
    "protected": false,
    "system": false,
    "description": "writable"
},
{
    "device": "/dev/mmcblk0p6",
    "size": "28015853568",
    "mountpoint": "/media/rsi-bryan/68C2-99CB",
    "name": "/dev/mmcblk0p6",
    "protected": false,
    "system": false,
    "description": "68C2-99CB"
}

Note that, on this SD card, mmcblk0p1 is a UEFI BIOS boot parititon, so it doesn't (and shouldn't) actually appear as a "drive".
The following gets the complete block device table in linux without resorting to scripts (just one call to lsblk), and adapts it to drivelist-like output.
### In addition to the RM flag, any device on the USB or MMC bus must be removable.
uDev is actually really bad at recognizing this, and often marks MMCs as non-removable.
###
rxRemovable = /(?:^|\:)(?:mmc|usb)(?:\:|$)/

### translates from lsblk's output into drivelist's expected output ###
Drive = (device, parent) ->
    {
        device: device.name,
        size: device.size,
        mountpoint: device.mountpoint,
        ### in the linux scripts, drive.name and drive.device MUST be the same.  Why?  ###
        name: device.name,
        protected: device.ro == '1'
        system: !(device.rm == '1' || device.hotplug == '1' || rxRemovable.test(device.subsystems)),
        description:
            (device.label || device.model || device.uuid || device.serial) || (parent && (
             parent.label || parent.model || parent.uuid || parent.serial
        ))
    }

getDrivesLinux = (callback) ->
    child_process.exec 'lsblk -a -p -J -O -b', (error, stdout, stderr) ->
        return callback(error) if error?

        if not _.str.isBlank(stderr)
            return callback(new Error(stderr))

        ###
        lsblk incorrectly uses '\xHH' for escaping quotes in its JSON output.
        Incorrectly, as \x is not part of JSON.
        This replaces those with the \uCCCC equivalent, which is totes OK in JSON.
        ###

        stdout = stdout.replace(/\\x(\d{2})/g, '\\u00$1')
        devices = JSON.parse(stdout)
        ###
        Structure of lsblk -J output:
        {
            blockdevices: [
                { /* ... block device ... */
                    children: {
                        /* ... partition ... */
                    }
                }
            ]
        }
        ###
        return callback(new Error("Couldn't read block devices"), null) if !devices.blockdevices
        devices = devices.blockdevices
        drives = []
        devices.forEach (device) ->
            ###
            a block device without a recognizable filesystem (e.g., with partition table)
            is not a drive, but raw device filesystems (e.g., no partition table) are a
            reasonably common thing, especially in USB drives and SD cards. So we
            try to make a drive object for both, skipping those without an fstype.
            ###
            drives.push Drive(device) if device.fstype?
            return if !device.children
            device.children.forEach (partition) ->
                drives.push Drive(partition, device) if partition.fstype?
        callback(null, drives)

To be fair, lsblk -J has only been around since last November - probably wasn't on your radar back when linux.sh was written.

Hi @Fordi ,
Thanks a lot for the feedback. We are intentionally omitting the partitions since this module is only concerned with listing the available top-level drives. I suggest using drivelist to detect the available drives, and then use custom code in your application around it to fetch the partitions.
That being said, I'm happy to take a PR that extends the drive objects with a partition property including the partitions as an object array, however notice this should be implemented for all supported operating systems.

If that's the case, why bother including mountpoints at all?  You don't mount a top-level drive except in very specific cases (like some, but not all USB drives).
I'll fork and work on getting Linux/Windows implementations working in-place, but I'm going to need an assist for Darwin; I don't have a mac to develop against.

Hi @Fordi ,

If that's the case, why bother including mountpoints at all? You don't mount a top-level drive except in very specific cases (like some, but not all USB drives).

Yeah, the mount points are mainly informative. We just use them in Etcher (https://github.com/resin-io/etcher) as a way for users to quickly check if they are selecting the correct drive.

I'll fork and work on getting Linux/Windows implementations working in-place, but I'm going to need an assist for Darwin; I don't have a mac to develop against.

Sounds good. Happy to help with OS X.

Seems like #85, #69 and #98 are all asking for the same thing? I.e. more detailed information about which specific partition maps to a specific mountpoint.
I guess this could be accomplished by extending my suggestion in https://github.com/resin-io-modules/drivelist/issues/98#issuecomment-257262289 to make mountpoints return a dictionary instead of a list? E.g.
[
  {
    device: '/dev/sda',
    mountpoints: {
      '/': { partition: '/dev/sda1', size: 12345 },
      '/usr': { partition: '/dev/sda2', size: 678910 },
    },
    ...
  }
]

However I wonder if the people making these requests might also be looking for the information about all partitions on a drive, regardless of whether they're mounted or not? @Fordi @feliupe @squirrelpiles
IMHO that'd be outside the current scope of this 'drivelist' module.

@lurch I agree with this change. This hasn't been a priority for any of the resin.io products making use of this module, which is the only reason it has been pushed aside for now.

Seems like #85, #69 and #98 are all asking for the same thing? I.e. more detailed information about which specific partition maps to a specific mountpoint.

I'll close most of them to keep a single source of truth for discussion this feature.
Since changing the format of mountpoint is a breaking change, I suggest starting with the following:
[
  {
    "device": "/dev/sda",
    "mountpoints": [
      {
        "path": "/dev/sda1"
      },
      {
        "path": "/dev/sda2"
      }
    ],
    ...
  }
]

This way of displaying information doesn't add anything we don't have at the moment, while still provides room to keep adding any other valuable information without breaking the interface again.

Closing this in order to continue discussion on https://github.com/resin-io-modules/drivelist/issues/98


Fix typo middlware -> middleware.

Q
A

Fixed Issues?
No issue mentions this, but i can open one if so desired

Patch: Bug Fix?
Documentation improvement

Major: Breaking Change?
No

Minor: New Feature?
No

Tests Added + Pass?
Yes

Any Dependency Changes?
No

Thanks!


[+WATCH_FULLVIDEOs!] El Siri Viral Leaked Video On Social Media X Twitter [ZNOW7K]

7 sec ago El Siri Leaked Video Viral On Social Media. [+WATCH_FULLVIDEOs!] El Siri Viral Leaked Video On Social Media X Twitter [ZNOW7K]

El Siri’s latest video has gone viral, igniting conversations across numerous social media platforms. This rising digital creator, recognized for her engaging content—particularly her recent Spiderman-themed clip—has experienced a surge of interest from fans eager to find the full version. Many are flocking to platforms like Instagram, X (formerly Twitter), and Discord to check out her latest creations.
As the buzz intensifies, fans are actively sharing their reactions online, highlighting the vital role social media plays in elevating creators like El Siri. With her distinctive style and creative approach, she has quickly made a notable impact in the digital landscape, leaving many curious about her upcoming projects.


Close mint + Change limit numbers

Close mint and change numbers to 1024/1024 since people are still trying to claim. 133/258 is confusing.

How about changing the text Minting Live to Ended if this minting stopped?

if this minting stopped?

legit

yeah also pls dont forget to change the number of mints

yeah also pls dont forget to change the number of mints

this is too fast : )


Fixing restoring search suggestions

Fix for  #32

@arimorty So, is the fix OK for you?

Hi @jakubkrolewski,
Can you branch out from 'develop' and do a new pull request with your changes? In this library we merge new features into 'develop' rather than 'master'.
Thanks for contributing.

I've created new PR #41

Great, your changes were merged into develop and will be part of the next release.
Thanks again for contributing.


As a paying user, I want to receive refunds when closing my accounts to an EOA or contract address specified by me.

Is it ok handling this manually for now? I think the requirements for this need some discussion.

@plor: Yes, in light of what we have agreed on regarding account deletion we can leave this as manual for now. Are manual reimbursements possible already?

@benedictvscriticus We will need to figure out where the operations funds are held, then the process will be something like:

Close account so no more usage occurs
Wait for usage reconciliation to occur (unclear what cadence, but likely daily?)
Send funds to address (after verification of account ownership and closure)
Add a DEBIT to the PaymentLedger including refund tx to bring balance to 0

@plor then let's go down that route. I think that's a pretty good spec for v. 1.0


Can't finish a task on a progress

Hello,
I'm trying to implement some progress bar, but when I use a track function within a for when the task finishes it renders green. From my point of view, this means, that the task finished successfully.
for customer in track(get_credentials, description="Getting credentials..."):
    LOGIC WITHIN A FOR LOOP

Renders as:

I like this because after the process ends, the process bar renders on green color.
But when I use the following approach, when the task finishes it shows like a working state, instead of a green state.
from rich.progress import Progress, track, BarColumn, TimeRemainingColumn, TaskID, TextColumn

progress = Progress(
    "[progress.description]{task.description}",
    BarColumn(),# bar_width=None),
    "[progress.percentage]{task.percentage:>3.0f}%",
    TimeRemainingColumn(),
    auto_refresh=False,
)

with progress:
    task_1 = progress.add_task("[black]Getting ALL certs...", start=False, total=100)
    task_2 = progress.add_task("[black]Getting ALL servers...", start=False, total=100)
    task_3 = progress.add_task("[black]Getting ALL dns...", start=False, total=100)

    while not progress.finished:
        df_all_certs = get_all_certs(session)
        progress.update(task_1, advance=100, total=100, completed=100, refresh=True)

        df_all_servers = get_all_servers(session)
        progress.update(task_2, advance=100, total=100, completed=100,refresh=True)

        df_all_dns = get_all_dns(session)
        progress.update(task_3, advance=100, total=100, completed=100,refresh=True)

Renders as:

As those functions are not using a for loop, for my understanding, I'm not able to use track.
What I'm doing, is after any function ends, I update the task from 0 to 100, complete the task and perform a manual refresh, so I expected it will show the progressbar as OK (green) but instead, is showing was working
How can I get the same behavior from track on other tasks that do not have a sequence?
Any help will be appreciated.
Thank you

You’ve created your tasks with start=False, which shows the working state.


Reduce unnecessary error computation

...during overload resolution.  Based on a trace that was spending 30% of a (very slow) overload resolution elaborating errors that were then dropped.

Interestingly, (though, in hindsight, logically), this also affects things like semantic classification that depend on overload resolution to get contextual types.

@typescript-bot cherry-pick this to release-4.0


Fix aps tf

Resolved conflicts in answers, this was clear from the texts provided;
Fixed bug in file_handeling.save_answers_to_yaml --> it will now write the corrected answer;
Added my encodings to the raw data file rdp.csv

Closing (already merged with #30)


[MWPW-136492] Enable Locale-Specific Subtitles on Embedded Vimeo

Sets the subtitles of embedded Vimeo videos based on the user's locale.
Testing: Click on one of the "Play Video" buttons, the stage link will not have any subtitles chosen by default, whereas the branch link will have Spanish.
Resolves: MWPW-136492
Test URLs:

Before: https://stage--express--adobecom.hlx.page/es/drafts/embed-video-default-cc
After: https://mwpw-135726-embed--express--adobecom.hlx.page/es/drafts/embed-video-default-cc

Codecov Report

Merging #259 (a6f766c) into stage (6bddc2f) will increase coverage by 0.12%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##            stage     #259      +/-   ##
==========================================
+ Coverage   47.04%   47.16%   +0.12%
==========================================
  Files          29       29
  Lines        8839     8839
==========================================
+ Hits         4158     4169      +11
+ Misses       4681     4670      -11

Files Changed
Coverage Δ

express/blocks/shared/video.js
35.01% <50.00%> (+0.36%)
:arrow_up:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

I realize the getLocale is going to return 'us' for our en pages, which isn't a valid texttrack for vimeo. Can you make a us -> en swap or maybe chain a getLanguage and test the result of that?

I realize the getLocale is going to return 'us' for our en pages, which isn't a valid texttrack for vimeo. Can you make a us -> en swap or maybe chain a getLanguage and test the result of that?

Fixed this and updated languages available.


Restrict iam:PassRole to account wide instance IAM Roles

Restrict the iam:PassRole permission to the specific roles created for the controlplane and worker nodes.
We cannot remove the specific iam:PassRole action because the installer is creating the controlplane IAM instance profiles and needs to assign the controlplane IAM role when the controlplane node is created. The cluster it self will create the worker nodes and needs to assign the IAM instance profile and the worker IAM roles when they are created.
https://issues.redhat.com/browse/OSD-10327

rosa delete account-roles --region us-east-1 --prefix ManagedOpenShift
E: Instance Profiles are attached to the role. Please make sure it is deleted: iam-passrole-bvrmc-worker-profile,iam-passrole-xj7qr-worker-profile

Need to investigate this issue with role clean up.

/hold

Need to investigate this issue with role clean up.

Good catch


Update Font

The current font is copy styling, 'Roboto', sans-serif. The https://graphql.stepzen.com has a font-style for code of Roboto Mono",Menlo,Consolas,Monaco,Liberation Mono,Lucida Console,monospace, and we should match it to be consistent with the matching color scheme.

resolved in PR #4


[BUG] Type hinting bug in new 2.0.1 with Python 3.7,3.8

Describe the bug
With the latest update, type hinting features from python 3.9 have been added, which making the application no longer compatible for Python 3.7 and 3.8.
To Reproduce
Steps to reproduce the behavior:

Install 'awscliv2' on < Python3.9
Run the following command
``awsv2 --install```

Problem solving
The problem occurs since the refactoring at least in the interactive_process.py. It is related to the typ hinting in method signature with Popen[bytes], which will only beeing supported out of the box since Py3.9.
To solve it in 3.7 and 3.8 you can import from __future__ import annotations (See https://github.com/python/typeshed/issues/4948)

Thank you for the report! Will fix today

Fixed and released in 2.0.2. Please let me know if it works as it should.

Thank you 👍
The cli runs now on Python 3.7 successfully


Option to disable 'Select background image for...' when importing metadata

This function does work, but I don't really want to use it regularly.

I was about to raise an issue in the main repo about skipping the background choice prompt during general library imports, but here looks like a place to voice more support...
For large imports of new games (e.g. game bundles, enabling a new integration), I have to continuously select a background for many of the games that offer multiple, which means I can't leave the import unattended as it sits waiting for an answer each time. The prompt also interrupts any business in other apps whilst I'm waiting, which is rather annoying.  I'm really not fussed what background image is used so I'd quite like it to just take the first one.
Concrete example, importing the large itch.io bundles after claiming the games:

Maybe 10-20% of these are prompting for a preferred background.
I note the (third-party) IndieGala integration offers this option:

This would be useful to have as a general library import option, rather than every integration having to do it themselves.

This would be useful to have as a general library import option, rather than every integration having to do it themselves.

Not possible, Playnite has no control over how these images are downloaded, we ask metadata plugin for an image and how that plugin gets it (including showing some dialogs) is up to each plugin individually.
Plugins can already detect when  a download is in background or manual one and act accordingly, like IGDB one does for example, so if you are getting some dialogs during background download, I recommend raising an issue with plugins showing dialogs.


RFC: “prefer lowest” builds should be added to core modules

As part of the PHP8 support, I added a "prefer-lowest" build.
https://github.com/silverstripe/silverstripe-framework/commit/58e56064baa7ed811103fa71bd2c66818075aa01
As part of this I became aware that some versions of packages we claim to support were broken a couple of years ago, and it's gone more or less unnoticed.
I'd like to suggest that we avoid this, and in particular suggest 2 things:

prefer-lowest should be set as the build arg of at least 1 build in the matrix of key modules

dropping support a minor version of a dependent package is allowed in a minor release

The 2nd point basically clarifies that, for example, admin 1.6 might rely on a new framework feature provided in framework 4.6. The same applies to, say, monolog 1.13 vs 1.16.
Dropping support for php-parser ^2, IMO, violates this principle but since it happened 2 years ago I think the time has passed where reinstating ^2 support would have any value.
But the main point about this RFC is to ensure that our composer version dependencies are actually true. It's better that they are true and modified, than left unmodified but are actually lies. ;-)
I haven't defined what I mean by "key module". I know that we're reducing the importance of the "supported module" concept and also I'm not saying "90 modules must immediately be updated to include this". I'm more saying "let's agree that this is a good idea so that we can take that as read when per-repo PRs come up"
Cc @emteknetnz as this spun out of a comment of his on a PostgreSQL PR

One thing that will make this a bit awkward on modules: older versions of framework don't currently work with --prefer-lowest, as they lie about the minimum requirements for monolog, and php-parser. This is currently breaking this build: https://github.com/silverstripe/silverstripe-postgresql/pull/108
Potential solutions:

Patch composer.json in the historic minor release branches to correct this, and ensure that an old dev package of this form is used to run the prefer-lowest builds.
Add a specific require commands for these packages to the .travis.yml build of a given module
List these two packages with the correct minimum requirements as require-dev dependencies of the module.

My inclination is to go with the last option.

The other thing I would note here is that adding this retrospectively... can be fiddly and annoying. So while I still think it's a good idea, it may not be something that would be rapidly rolled out across all modules.
The main purpose of this RFC ticket is therefore to get preliminary pre-approval for any PRs introducing such builds on modules, so we don't need to have a "do you really need a prefer-lowest build?" discussion on a per-module basis. ;)

I think this is a good idea, we should document accurately the supported versions of our dependencies. prefer-lowest will allow us to test our module support more accurately.

List these two packages with the correct minimum requirements as require-dev dependencies of the module.

I think this is best too

@Cheddam @dnsl48 et al - do we have our module/travis best-practises documented anywhere? if not I might do a PR with some MD docs that include this recommendation

do we have our module/travis best-practises documented anywhere? if not I might do a PR with some MD docs that include this recommendation

No, I don't think we have any such documentation. However, we try to follow a general rule of never reduce existing test coverage when updating any CI configs. So, if it's added to all (any) modules, we won't be accidentally removing it any time soon.
Another point to consider is we usually try to test explicitly against every supported version and not just lowest/highest. That means, when a new minor version of a recipe is released, it is not always supported by all the previous versions of a module, but all the originally supported version bundles should be working together forever. Here's an example of that approach: https://github.com/silverstripe/silverstripe-userforms/blob/5.5/.travis.yml#L17
Even though we don't support userforms 5.6 with framework 4.3, userforms 5.5 with framework 4.3 should be always working, even after EOL. Even though, userforms composer requires "silverstripe/cms": "^4.0", we don't test it with prefer-lowest (perhaps we should be updating composer more often though).
For the core modules it's different because they are in lock-step, so we only test agains the same minor versions of the recipe and that's the case for the admin module.

For the core modules it's different because they are in lock-step

I disagree with this as a goal, although I can see how it might be a helpful simplification to avoid unnecessary dev effort.
If what you're saying is that, say, admin 4.6 requires 4.6, then it should say require: silverstripe/framework: 4.6. But maybe admin 4.6 works with framework 4.5? If so, a prefer-lowest build will either:

Provide that admin 4.6 works with framework 4.5 and therefore a more relaxed requirement is better, OR
Throw up a failure, which is fixed by tightening the requirement of admin.

IMO an approach that says "we only ever test this bundle of modules in this one specific combination" is a recipe for accidental coupling and, as such, less maintainable code. This is beyond the scope of this RFC but would be the kind of thing that can be documented, based on the results of future RFCs.

For the core modules it's different because they are in lock-step

I disagree with this as a goal,

Well, not saying this is a goal, rather an unspoken convention that we've discussed several times in the last couple years but did not document. We only "explicitly support" recipes and core recipes have all modules in lock-step by minor versions, so that's been our primary focus. Not saying we should not test everything else.

If what you're saying is that, say, admin 4.6 requires 4.6, then it should say require: silverstripe/framework: ^4.6

Yes, I believe this is our implicit convention because of the "only recipe is supported" principle. However, we never felt necessary updating all the modules composer requirements, since that would be additional toil and might actually allow someone use "unsupported" combinations of modules if necessary.
Even so, I believe having --prefer-lowest would be a good thing as it can help us to identify broken combinations earlier and either fix those issues or update composer.json wherever necessary.

Another point to consider is we usually try to test explicitly against every supported version and not just lowest/highest.

That's a good idea. Although every version can be quite onerous.

Well, not "every every", but "every currently supported", which is usually the last 2 minors :)

Good good. The other trick is that if, say, you rely on some as-yet-unreleased code (and 4.6 is the last stable minor) then you can update the dependency to ^4.7. This will force even prefer-lowest to pull the dev branch, but once 4.7.0 is released it will happily use that instead (provided prefer-stable is true)
I think another question is how much should be tested within each module's build matrix vs how much should be left to a kitchen sink or recipe build. What's the status quo with that? Do we have nightly scheduled builds on the recipes or a kitchen-sink equivalent?

Do we have nightly scheduled builds on the recipes or a kitchen-sink equivalent?

Yes, we run kitchen-sink and ss-installer builds daily for "current" and "next" versions. However, they only test matching versions of all modules. No "unsupported" combinations is tested there.

how much should be tested within each module's build matrix

We usually want to test all supported versions of the recipes. For satellite modules we also discussed internally that testing --prefer-lowest would be nice to have as well. However, that's a lot of work to add to it everywhere, so we just didn't find time for that so far.
It is different for core modules though. I don't remember if we ever discussed supporting core module combinations outside lock-step, so there was not much need in testing it.

Yes, we run kitchen-sink and ss-installer builds daily for "current" and "next" versions. However, they only test matching versions of all modules. No "unsupported" combinations is tested there.

Yeah I don't think you need to run unsupported kitchen sinks. Should we be running builds daily (or even weekly) for not-latest-but-still-supported recipes?
That would mean that individual modules might get away with builds only on the following core dependencies:

oldest stable
latest stable
4.x-dev
That might, in turn, reduce toil?

The weakness of the kitchen-sink build is that unmerged PRs aren't tested on it. So your module tests need to be the minimum required to confidently. Therefore the question is "would it be acceptable to merge a PR prior to testing against he 2nd-to-last version of the recipe"?

It is different for core modules though. I don't remember if we ever discussed supporting core module combinations outside lock-step, so there was not much need in testing it.

The prefer-lowest build will do this for us, and I believe will provide sufficient coverage of that situation, in situations where we haven't specifically marked composer.json to disallow the older package (because something breaks, and we're disinclined to bother fixing it).

This next comment is a bit of a brain dump of some speculative thoughts of mine. Feel free to ignore it, it's not really got any actionable suggestions right now, it's an attempt to provide more context for how I'm thinking about this.

It is different for core modules though. I don't remember if we ever discussed supporting core module combinations outside lock-step, so there was not much need in testing it.

But why is that of value? I'm getting a little ahead of myself. ;) One of my hopes for #9679 is that it will be possible to bump some of the subpackages up a major without needing to bump everything up a major. This would mean a lot of ^4 || ^5 in the composer.json requirements definitions. It's unclear as to how viable this would be, and is unlikely to unviable on every major. But for specific areas where we want to allow for some innovation without dropping massive upgrade projects on people, it might be useful.
In the short term, what I'm advocating in support of this is use composer.json to speak more precisely about what is required than "oh this is part of the recipe". So while testing the whole recipe should definitely be one of the tests, it shouldn't be the only test.
The benefit of decoupling is to be able to reason about packages independently for the bulk of the work on that package. Silverstripe makes this hard, but I'd hope the we can incrementally make it easier, and that our build tooling can help with this (by including some 'naked builds' in their travis makes which minimise the depednencies pulled in to run the test). Again, that's one of my goals with #9679
I would note that when I'm contributing to framework I usually do so on a framework checkout that is not part of an SS installation. Hence committing things like a .gitignore to framework. ;-) This is impractical at times, but keeps the decoupling top-of-mind for me.

A prefer lowest build is in the (relatively new) github actions CI which has been applied to all supported modules. We're following the practices proposed in this RFC so I'm going to close it as completed.


Updated Notebooks in version 1.5.x of the docs

Unable to resolve conflicts, will try starting from scratch again.


Integration tests executed on a real deployment as part of the CICD - Datasets

Same as for https://github.com/data-dot-all/dataall/issues/1220.
This issue is to track the progress for the Datasets modules.
It has its own dedicated issue because of the challenge of pre-existing infrastructure needed to test datasets

Required tests for basic coverage
For fresh deployments
For each of the following API calls we need to test authorized and unauthorized scenarios as well as all possible configurations (e.g. autoapproval...)

[ ] Create Dataset - includes testing if dataset is indexed in Catalog
[ ] Import Dataset - includes testing if dataset is indexed in Catalog
[ ] List Datasets
[ ] Edit Dataset
[ ] Delete dataset
[ ] Start crawler
[ ] Sync tables
[ ] Preview table
[ ] Delete table
[ ] Create folder
[ ] Delete folder

For backwards compatibility

[ ] Update created Dataset stack
[ ] Update imported Dataset stack
[ ] Create Dataset in updated Environment
[ ] Import Dataset in updated Environment

Full coverage [WIP]
For fresh deployments

[ ] AWS access to Dataset - Credentials
[ ] AWS access to Dataset - S3 redirect
[ ] Upload data
[ ] Profile table

For backwards compatibility
For the updated Dataset stacks:

[ ] AWS access to Dataset - Credentials
[ ] AWS access to Dataset - S3 redirect
[ ] Start crawler
[ ] Sync tables


Job logic questions

I have some questions about the lib I could not find answers for in the Wiki or FAQ

If multiple jobs are scheduled that rely on a network connection, will they all fire simultaneously once the network returns (or one at a time based on FIFO)? Can this be configured?

Is it possible to have dependencies between waiting jobs? So Job A fails so Job B (which may or may not be scheduled) will not run until Job A succeeds.

Newer jobs with the same tag override any others still waiting.

Thanks

The OS controls that. It's likely to happen. Jobs run in parallel, but you can change this with JobConfig.setExecutorService(..), although I wouldn't recommend that.
You better look at WorkManager https://github.com/evernote/android-job#workmanager
No, they don't. You can have multiple jobs with the same tag.

That leaves me no choice but to add some logic to each job when it fires to see if it should do the work or not.
Is there some way to interrogate the jobs?

What do you mean? You can always get the parameters and requirements.

So lets say a job is submitted twice during a period of no network (and the jobs require it). Could I check to see if there are other similar jobs waiting?

Yes, you can find all specific jobs by tag

Closing because of inactivity.


Revert "Add NS records for Con-PCA"

After further discussions with @zenine07 and @jsf9k, we realized that we do not need any public DNS lookups for Con-PCA.  All DNS will be handled in the COOL private zone (see https://github.com/cisagov/cool-pca-transitgateway-attachment/commit/af42c13e4f642cf718a3880a65ec34816af1f605).
Reverts cisagov/cool-dns-cyber.dhs.gov#34.

#ContinuousFailure for the win! 🤕


KeyError: 'test_labels'

Hello,
I wanted to redo your experiment, I found some problems. 'test_labels' is undefined in parse_args.

Hello,
you should download 'awa_demo_data.mat' before running this code.
Thanks.


Add MethodInvocationCounter Metric to Track Method Invocations within Classes

Overview
This PR introduces the MethodInvocationCounter metric, a new ClassLevelMetric designed to analyze and report on method invocation patterns within Java classes. The metric captures the frequency of invocations for each method within a class, providing insights into method dependencies and utilization.
Key Changes

CKClassResult.java (REFACTOR):

New Data Member: Added a private string field methodInvocations to store the formatted string representing method invocation statistics for each class.
Accessor and Mutator Methods: Added setMethodInvocation(String methodInvocations) and getMethodInvocations() to handle this new data. This allows the stored invocation data to be set during metric calculation and later retrieved for output.

MethodCounter.java (FEAT):

New Utility Class: Introduced to assist with counting and formatting method invocations. This class includes nested classes and methods that:

Store method invocation data (MethodInformation class).
Sort and format the collected data into a readable format (formatResult and toFormattedString methods).

This utility class provides a centralized way to manage method invocation data, ensuring consistency and reusability across different parts of the metric implementation.

MethodInvocationCounter.java (FEAT, FIX, REFACTOR):

Metric Implementation: This file defines the MethodInvocationCounter class which implements CKASTVisitor and ClassLevelMetric. It contains the logic to visit method declarations and invocations, and it populates the MethodCounter.MethodInformation data structure with this information.
Visitor Methods: Implements the visit(MethodDeclaration node) to set the current method context and visit(MethodInvocation node) to record invocations within the context of the current method.
Set Results: Overrides setResult(CKClassResult result) to format and set the method invocation data on the CKClassResult.

ResultWriter.java (REFACTOR):

Output Addition: Modified to include the methodInvocations in the output of the CK tool. This ensures that the collected method invocation data is written out alongside other metrics.

Implementation Details
The MethodInvocationCounter leverages the AST (Abstract Syntax Tree) to visit and analyze MethodDeclaration and MethodInvocation nodes within Java source files. For each class, it maintains a mapping of methods and the methods they invoke, along with the invocation counts. This data is then formatted into a human-readable string that summarizes the invocation patterns, making it easy to identify which methods are central to the functionality of the class.
Output
Here is an example of the Output generated when using CK to generate the class.csv for the ZooKeeper repository:

Usefulness
The MethodInvocationCounter metric is particularly useful for:

Identifying Key Methods: By highlighting methods with high invocation counts, developers can quickly identify the core components of a class.
Refactoring Opportunities: Methods that are heavily dependent on others or have high complexity might be candidates for refactoring to improve modularity and maintainability.
Optimizing Performance: Understanding method invocation dynamics can help in optimizing performance-critical parts of the application.
Documentation and Understanding: This metric provides a quick overview of class behavior, which can be beneficial for new developers or in documenting the system.

Conclusion
The addition of the MethodInvocationCounter provides valuable insights into method usage patterns, making it a useful tool for developers looking to maintain and improve the quality of their Java applications.

Hi, again.
So, the changes were made. Basically, the CK and Runner classes were modified to handle a new boolean execution argument (verbose).
In addition, the ClassLevelMetric interface was modified to include a new method named isVerbose, whose default return is false. With that in mind, any new class metric can overload this method and set the return value to true, which was done in the MethodInvocationCounter class.
If the verbose execution argument is set to true, every metric will be processed. Otherwise, it checks if the metric is not verbose, so it can be processed.
I acknowledge that this PR is massive. If you prefer, i can split it into two PRs: One for the verbose execution argument and another for the new class metric itself (MethodInvocationCounter).
Also, keep in mind that the build is failing. That's due to the fact that my older PR that fixes the build was not approved yet (#115). It's a simple PR, so it's fast to analyze.

Hi @mauricioaniche. The readme conflict is solved.


line_break_multiple_parameters too strict

I suggest that the check should not raise errors, if

there are multiple parameters of the same kind - for example only 'importing' parameters
the method call is used as an expression - for example in an if statement

Example:
* Bad example
method( IMPORTING parameter1 = value EXPORTING parameter2 = value ).

* Good example
method(
  IMPORTING
    parameter1 = value
  EXPORTING
    parameter2 = value ).

* Good example
method( parameter1 = value parameter2 = value ).

* Good example
IF method( IMPORTING parameter1 = value EXPORTING parameter2 = value ).
...
ENDIF.

To add 5 cents ...
One of my favorite videos. https://www.youtube.com/watch?v=ZsHMHukIlJY
The subject is clarified staring at 10:30 ~ 23:00 with some very bright examples at ~21:00+
In a nut shell: https://github.com/SAP/styleguides/issues/21 and comments
So imho method( parameter1 = value parameter2 = value ). is not good as the second param is not visually distinguished and is at random position.
P.S. though maybe I'd add an exception for methods with very short param names like built-in string functions ... :)

In the default setup it should be as strict as possible, then we can add additional configuration to allow more stuff

excellent video indeed. one of the key points is about line length and length of identifiers. the shorter and the more meaningful, the better. And when you do that imho you don't need to break things into multiple lines.
my_biggest_asset = max( val1 = my_car val2 = my_boat val3 = my_house ).
if max( val1 = my_car val2 = my_boat ) > min( val1 = my_house val2 = my_chateau ).
The rule makes sense but it should provide some flexibility like

Built-ins vs class method
direct method call/returning assignment vs expression that's part of another statement
Single type of parameter (just imp/exp/etc) vs mixed

Maybe the criteria is short key/value pairs ? E.g. a = 1 b = 'abc' is still readable, while iv_a_param = 1 iv_b_argument = 'abc' is already not. (just thoughts)

Number of params is configurable with #2076


Dashboard Auth[FreeIPA/AD/OpenLDAP] Users shouldn't be allowed to enable multiple auth in dashboard

Rancher | v2.5-05fbcbb75ba84a80c5aaa243985e892c52b9ac32-head
User Interface | v2.5-dev
Helm | v2.16.8-rancher1
Machine | v0.15.0-rancher51
From the dashboard auth providers, can enable AD, FreeLDAP, OpenIPA at the same time. This shouldn't be allowed from the dashboard.
From the ember UI, users are allowed to add one auth at a time.
On dashboard:

https://github.com/rancher/dashboard/issues/2114

This has never been actually been true; The API and Ui both work with multiple on, but it is generally confusing so the navigation to the others are hidden if something other than local is on in Ember, which is why it appears to allow only one.
Showing them all in Vue was at one point intentional because I wanted to solve some of that confusion, but there is API work needed so I thought I gave up and set the left nav item up to go straight to the one enabled non-local driver if there is one; @mantis-toboggan-md ?

Navigating via /auth/config redirects to whatever third-party provider is enabled, but there's also an auto-generated list view under /c/<cluster>/explorer/management.cattle.io.authconfig.
I left the list view alone because it's easier to tell what's going on when multiple providers are enabled, which, yes, can be done by navigating to a config page directly.

This is by design - navigating to Cluster Explorer -> More Resources -> Rancher -> Auth Providers will always show all providers and from there you could enable multiple - this is for advanced users/use cases only - the normal 'Users and Authentication' views do not let you do this.

@nwmac "Can you please validate that this is the way you were able to enable multiple and that you can not do this via 'Users & Authentication -> Auth Providers'." --> Can you let me know if this is through ember UI? I did not find this option on dashboard.
I'm on the v2.5-b4be2b22879d85f268dff655206b8e515d803142-head


Adding remove, rename, hasField, fieldCount, getAndRemove

Coverage increased (+0.9%) to 100.0% when pulling df30ebc1cee4d0150e1d688710531b29c883a1e9 on additional-helpers into 49eaf11c7f01caf98aab975da4238b6389b486f7 on master.


chore: Remove unnecessary field from StateCreator

Although it was a public field, it has been true by default and no code turns it off.
Let's remove the field entirely, so that it's theoretically a little bit easier to understand the code.
If any third-party code is using this field, it will break, but it's unlikely- If you ever turned it off, you are likely to have a helmfile.yaml that can be parsed only with Strict=false, which is impossible to be parsed with the standard Helmfile; a portability issue!

Ah, seems like I somehow missed the field is actually used somewhere! NVM. Closing.


MockClientState to RawMockClientState conversion ignores frozen_height

Bug Summary

The following implementation ignores frozen_height of MockClientState.
https://github.com/cosmos/ibc-rs/blob/ee92645e050f552bee9acdd17ba6468a624c710c/ibc-testkit/src/testapp/ibc/clients/mock/client_state.rs#L87-L96
So, the serialization-deserialization may not work as expected.
Details

For example, the following fails,
let header = MockHeader::new(Height::new(0, 1).unwrap());
let client_state = MockClientState::new(header).with_frozen_height(Height::min(0));
let raw_client_state = RawMockClientState::from(client_state);
let client_state_back = MockClientState::try_from(raw_client_state).unwrap();
assert_eq!(client_state, client_state_back);

We need to update the original ibc.mock definitions on ibc-proto-rs repo and fix the From implementation in this repo.
Version

<= v0.49.1

Note: the same happens with MockConsensusState and RawMockConsensusState where it ignores the commitment root.

@rnbguy I can pick this up.

sorry, I am already working on this on the feature branch https://github.com/cosmos/ibc-rs/tree/feat/refactor-testkit

closed by #1109


MomentInput is missing weeks

The MomentInput interface should include weeks. You can see that this is valid in Moment's docs: http://momentjs.com/docs/#/durations/creating/

Please fix this issue and send pull request. I'll review it.


React Native Example

Preflight Checklist

[X] I could not find a solution in the existing issues, docs, nor discussions
[X] I have joined the ZITADEL chat

Describe the docs your are missing or that are wrong
As a developer, I want to integrate my react native application in to ZITADEL, so my users can authenticate
Additional Context

Best practices: Browser vs. embedding
Mention Session API for embedding login; how to handle secrets in that case

@fforootd mentioned this guide here: https://twitter.com/ffo_sesp/status/1623278432644636674


Improve performance

We currently store a traceback for every node we create, but there is no public way to expose that information. This PR foregoes the creation of the traceback based on a (private) global variable which may be set when needed. This change provides a considerable speedup for the default configuration.
Checklist

[x] Added a CHANGELOG.rst entry

From external chat it appears this is for onnxruntime debugging only? If so, while nice to see where the Spox node was constructed that results in the failure, you should be able to determine which operator is the culprit from a runtime stack trace. This is only used internally so I'd be happy to remove it, but worth checking with @jbachurski who will know more.

Trackbacks are used so that if only a node name is available in an error message, you get a hint what node corresponds to it. This usually would happen at runtime, hence why there is something for ORT implemented. I'm happy for it to be disabled by default since these inspections can be rather slow.


Add config validation to check for liveDebugging without the experimental stability level

We cannot force Alloy to change its stability level, but we can warn the user to enable it.

% helm template k8smon charts/k8s-monitoring -f examples/default-values/values.yaml --set alloy.liveDebugging.enabled=true
Error: execution error at (k8s-monitoring/templates/kubernetes-monitoring-telemetry.yaml:2:3): To enable Alloy live debugging, you must set the stabilityLevel to "experimental":
alloy:
  alloy:
    stabilityLevel: experimental

Use --debug flag to render out invalid YAML

Hey @petewall - thanks for the implementation, but I think this missed the part where we also need to be able to set the stabilityLevel in the actual helm hook where the configuration is validated by the alloy command, i.e.
https://github.com/grafana/k8s-monitoring-helm/blob/64e01fcb7460fe6e61f7ad6277ae529a80aaacc2/charts/k8s-monitoring/templates/hooks/validate-configuration.yaml#L52-L91
We need to be able to set the stabilityLevel there as well. Without this, the only way to use livedebugging is to set configValidator.enabled = false

I was able to set the stability level and live debugging and get it working. Can you try again?
This change fixed the validation: https://github.com/grafana/k8s-monitoring-helm/blob/main/charts/k8s-monitoring/templates/hooks/validate-configuration.yaml#L55

Ah nice, thanks! Tried and worked :)


Sending Files

hi,
im using the socketio bot.
i want to know if you have example of sending a file via the client to botmaster implimentation.
ive found and got the following package working in seperate project:
https://www.npmjs.com/package/socketio-file-upload
but want to know how i could use it with botmaster, or if botmaster has a implimentation to handle files/bytes/bytearray?
regards
willem

I wanted to mark this as feature and NOT issue

This is essentially the same question as: https://github.com/botmasterai/botmaster-socket.io/issues/7
Redirecting there and closing this issue now


Add boilerplate

This sets up the repository to be easier to work with:

Add a generic .gitignore from https://github.com/github/gitignore/blob/master/Python.gitignore
Sort imports with isort and format the code with https://github.com/ambv/black
Add .editorconfig that tells various editors what settings to use for files
Add .pre-commit-config.yaml, a tool that installs other tools that get called on each commit. In this case, the hooks automatically format the code again and look for various paper cuts. Do pip install pre-commit to install the main tool and pre-commit install in your repository to install the Git hooks. They prolong commit time.
Add the tutorial as a sort of smoke test, to see that stuff works.
Add setuptools boilerplate for easy package building. Bonus: use the setuptools_scm package to automatically version the package according to Git tags. No more bumping the version number, just tag a commit.
Add Travis CI integration. This can later be used to automatically deploy a release upon tagging it.

The biggest issue for me with this pull request is the complete reformatting of the codebase. Not only it is not necessary, it completely mangles the code at several places, see jpeg or cff. Also, "easier to work with": I don't want to install tox or black just to be able to properly commit anything, and I'm not sure what the test tests. I will modify .gitignore, though, thanks! Do you wish to commit it separately? And maybe I should create a separate GitHub project for tutorial and documentation...
Please understand, I'm afraid this kind of boilerplate would cause more work, not less, and is not necessary at this early stage of development. If the time comes I wont be able to promptly merge the requests, I will reconsider.

On the contrary, boilerplate like this is beneficial from the time a project is born to keep it orderly and save you time down the road :) You just need to get used to it.

Using an automatted formatter(-on-save) frees up brain cycles and ensures that the different opinions about how code should look like are stifled at the core -- very useful in collaborative projects. I personally see no mangling. If you want to keep data blocks compressed, you could use # fmt: off/# fmt: on blocks though.
You don't necessarily need to install black, just pre-commit. If you manually want to format and lint stuff, you run pre-commit run -a or just commit and add modified files and re-commit.
tox will help you in testing for both Python 2 and 3 by running tests in both environments.
If you're interested in having some other tool for project/dependency management, you may want to have a look at https://github.com/takluyver/flit and https://github.com/sdispater/poetry.
The single test is just a smoke test really, to see that your example keeps working if you refactor the code.
Why seperate repos? You can generate docs with e.g. Sphinx, mkdocs or whatever else and use e.g. GitHub Pages to automatically deploy documentation as you go.

I think the boilerplate is a solution to a problem the library does not yet have. Once there are so many contributors and commits the maintainer (me) is not able to keep up with the pace then it would start to make sense to add it, not the other way around.
PS: As an example, the linter completely broke down the formatting of _z_z bytearray of jpeg: the few first spaces are significant as they hint at the missing DC coefficient in the zig-zag sequence and putting each coefficient on a separate line is less readable than it used to be. Repurposing the comments to suppress one particular linter does not seem to me like less work, neither.

The benefits of a formatter outweight possible inconveniences in the medium and long run.
Regarding tests and CIs, you'll make it harder to maintain and port the library to Python 2+3 if you opt out. It's easy to commit bugs, so a porting effort would require tests for a class and then you do the porting and run those tests with Py2/3 to ensure that stuff keeps working. This PR lays the groundwork for that.
Please add the setup.py at least (or tell me if you want to use poetry or flit instead), you'll just make it harder for contributors because they can't build and install the damn thing.

Done in https://github.com/xxyxyz/flat/commit/e1141d6d2f21f6e2915409c41ebc3d197683717d and https://github.com/xxyxyz/flat/commit/977afe6b5a1827faa66626e280fd92caad6e19f0, thanks for the suggestions!

I recommend you also add the setuptools_scm thing to setup.py -- it will automatically generate a MANIFEST for you and you can stop caring about version numbers, because setup.py will set it automatically according to git tags. No more commit version change and tag, just tag something.

I prefer the version number to be explicitly stated in the source code, it's then easier to find it out as it wont require running the script.
What Python 2+3 goes, I plan to drop the support for version 2 once the Python 3 work is ready.


BUG: Missing files causes job to fail, not return false as indicated

Code
You reference
if (hasMissingFiles) {
    const message = `❗ Missing files: ${missingFiles.join(', ')}`
    failExecution(message)
  }

however by calling failExecution you don't return false as the READEME says, you end up failing the stage, making the ability to do a check for files not existing no work.

Yes this is not working as described.


refactor(GCS+gRPC): move stub factory function

Split the factory function for StorageStub (with decorators) to its
own .h and .cc files. This will help as I add additional decorators
and member functions.

This change is

Part of the work for #7963


Authenticate access with personal access tokens documentation page is missing important part

Feedback from my customer：
The powershell code to base 64 encode the PAT is missing the prepending of the semicolon:
This line:
$B64Pat = [Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes("$MyPat"))
Should be:
$B64Pat = [Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes(":$MyPat"))
I say this because the bash code properly prepends the semicolon and when I’ve tried the powershell code without the prepending it doesn’t seem to work. Thus, I think the powershell code is missing the prepending of the semi-colon.

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

ID: 2bfea574-db69-a5fd-37fe-64ecfdac502a
Version Independent ID: 4037d475-f194-2ac9-ffd6-70530fc3140a
Content: Authenticate with personal access tokens - Azure DevOps
Content Source: docs/organizations/accounts/use-personal-access-tokens-to-authenticate.md
Product: devops
Technology: devops-security
GitHub Login: @chcomley
Microsoft Alias: chcomley

@NicoNBW - It looks like this one is already being fixed here: /MicrosoftDocs/azure-devops-docs/issues/11478
Thanks!


make bookinfo sample deployment non-root

Describe the feature request
There is no need of running the bookinfo example containers as root. There is already an open issue regarding the productpage image #23219.
Quick fix would be to add a user except root to the Dockerfiles.

lifecycle/staleproof

@howardjohn could you plrease reopen the issue and add lifecycle/staleproof ? Thanks

closed this in #28648


Unable to install opentest

While installing opentest on a new machine with reference to the following URL: 'https://getopentest.org/docs/installation.html'.
waiting for a long time with the following message lasting for eternity.

npm install opentest -g
[..................] / fetchMetadata: sill resolveWithNewModule<EMAIL_ADDRESS>checking installable status

This is an npm issue. Try to apply some of the solutions described here. Some of the ones that sound like could do the job are:

Update npm with the command npm install npm@latest -g.
Make sure your machine can reach npm at all times during the installation. That means both DNS name resolution and actually being able to access the IP address of the npm server.

Thank you
closing the issue


Feature: Audio Sensors for Recording Devices

Please make sure your feature isn't already listed on HASS.Agent's issue tracker:
https://lab02research.youtrack.cloud/
There's a list of open bugs & features on the right. On the left you can see what's being worked on, what's planned and what's ready for the next release.
If you're not sure, don't worry, just go ahead and we'll discuss :)

The "Audio" sensor type has a bunch of great data points for Playback devices, but it would be great if there was also an option to include this data for Recording devices as well! Specifically I was looking to find the muted state of the microphone to derive some automation.

+1 for this.  I'm looking at the audio sensor entities from HASS.Agent 2022.14.0 and there is an entity $HOST_audio_default_input_device_muted but it doesn't seem to update when I mute my microphone either within Zoom or withing the Sound Control Panel.


Fixed #5 -- Add support for django-nose and any other custom test c…

…ommands.

Add a TEST_WITHOUT_MIGRATIONS_COMMAND setting that should be a dotted path
to a management command class to use as a base class, to which we will add
the -n and --nomigrations arguments.

Remove -n and --nomigrations from sys.arg, in case we are extending a
custom that passes these along.

Released at https://pypi.python.org/pypi/django-test-without-migrations/
Thx all!


Issue of code generation when using input value reservation word field

If the field in the input schema is a reserved word, the Pair value of the fields method of the generated code is missing a backup (`) resulting in a compilation error.
Is there any way to solve the above issue?
used codegen version: 6.0.2
Example Input Schema:
input SampleInput {
  return: String!
}

Generated Code:
public class SampleInput(
  public val `return`: String,
) : GraphQLInput() {
  public override fun fields(): List<Pair<String, Any?>> = listOf("return" to return)
}

The generated code you posted does not seem to be from the dgs-codegen
plugin. This is what I see for the schema you posted:
public data class Person(
  @com.fasterxml.jackson.`annotation`.JsonProperty("reserved")
  public val reserved: kotlin.String,
) {
  public companion object
}

The above compiles fine. Could you please check your set up again?
On Sun, Sep 24, 2023 at 6:14 PM luke.89 @.***> wrote:

If the field in the input schema is a reserved word, the Pair value of the
fields method of the generated code is missing a backup (`) resulting in a
compilation error.
Is there any way to solve the above issue?
Example Input Schema:
input SampleInput {
return: String!
}
Generated Code:
public class SampleInput(
public val return: String,
) : GraphQLInput() {
public override fun fields(): List<Pair<String, Any?>> = listOf("return" to return)
}
—
Reply to this email directly, view it on GitHub
https://github.com/Netflix/dgs-codegen/issues/602, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ5JPXM7IDJXWBJR3GL4D4DX4DLGVANCNFSM6AAAAAA5FKMM2Y
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@srinivasankavitha
The issue related to reserved keyword field names occurs when generating code for the Client API.
The dgscode set for the gradle is as follows.
schemaPaths = mutableListOf("$projectDir/src/main/resources/schema/services.graphql")
    generateClient = true
    packageName = "com.****.****.domain.generated"
    generateDataTypes = true
    snakeCaseConstantNames = true
    generateKotlinClosureProjections = true
    generateKotlinNullableClasses = true
    language = "kotlin"

It appears that the problematic generated code is located under the 'dgs-codegen' folder, indicating that it is indeed generated by 'dgs-codegen'.

Oh I see, that's helpful. I didn't realize you were using generateKotlinClosureProjections for Client API.
@mbossenbroek - do we handle reserved keywords?

Yeah, I just missed the escaping in that spot. This PR fixes it & confirms with the example above: https://github.com/Netflix/dgs-codegen/pull/604
Feel free to merge/release at your leisure. Apologies for the delay there - I was out sick the past few days.

@srinivasankavitha
Thank you. 👍🏼
Do you happen to know when the version release is scheduled?


After metadata edit the user needs to refresh the page to see the changes reflected

The metadata cache needs some time to index the metadata updates and if you go back to the asset details page before that happens the updated values won't be reflected.
The experience is visible here: https://drive.google.com/file/d/1QCKPjfQbRh7SoNJPXNMLy1_IYZxfAxal/view?usp=sharing
Maybe we can update the user experience and provide a better experience.

From @DMats came this idea of waiting for certain amount of block confirmations, e.g. for the last tx. We could show that to user on submission screen and only after like 5 block confirmations the View Asset button becomes active

I think block confirmations after both the "create data tokens" transaction and the "set metadata" transaction are needed to mitigate against chain reorgs. I suppose it would have the added benefit of giving aquarius more time to cache the asset.

hmm, not a bad idea, but we need to implement something at a global level in the market so we can use it on all actions

While not a bad idea, not sure how we can implement this. The effort seems a bit too much and the gains are not that big.


Slow verification of programs combining multiple floating point values

(This is a re-post of my comment to PR #107, as requested by @zvonimir to streamline the discussion here.)
Hi!
I just found the floating point syntax update for Boogie and am very interested in it! Thanks for pushing this! :)
I just checked out the liammachado:improved_fp_syntax branch to play around with the FP implementation a bit. For examples combining two floating point values, the verification takes very long (so long I usually have to kill it early), e.g.:
procedure Exp1(a: float24e8, b:float24e8)
{
  var res: float24e8;
  assume(a > 0x1.0e0f24e8);
  assume(a < 0x4.0e5f24e8);
  assume(b > 0x1.0e0f24e8);
  assume(b < 0x4.0e5f24e8);
  res := a + b;
  assert(res > a);
  return;
}

Is that normal and intended? When using z3 directly to verify this using its FP syntax, it terminates very quickly.

Ok, so let me comment on this. Thanks for reporting @classner, we certainly appreciate any feedback on our floating-point implementation.
I believe what you are observing here is the effect of theory combination on Z3, since we observed similar behaviors in the past. Basically, it seems that the theory of floating-points performs much better when your query is exclusively in that theory, instead of also involving things such as uninterpreted functions, arrays, etc.
Now, if you run Boogie on your example and use /proverLog:test.smt, you will likely notice that the generated query contains more than just pure floating-points, and at the very least it will contain uninterpreted functions. At least I think so.
On the other hand, I suspect that your direct encoding into Z3 was purely in the theory of floating-points.
This difference in the theories used could explain the discrepancy in the rutimes, at least based on our experience.
We have been looking into using Z3 tactics to get around this problem, but we still did not get to the bottom of this completely.
I hope this helps. Thoughts?

The current version of Boogie (2.5.10) verifies the above example in (essentially) no time.


fix(data-workspace): reduce header height

Maybe we should merge https://github.com/dhis2/ui/pull/771 first as that removes the fixed height styles from table cells?

Maybe we should merge dhis2/ui#771 first as that removes the fixed height styles from table cells?

Yeah that makes much more sense. That PR needs a little bit of work done to it still. I'll put this one in draft and once https://github.com/dhis2/ui/pull/771 is merged we should be able to remove most/all of this table CSS.


⚠ Mobitopup has degraded performance

In da0bd40, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 25095 ms

Resolved: Mobitopup performance has improved in 65f05ea.


removing ploomber-extension

What happens?
we deprecated the funcionality, I attempted to remove it but tests are failing.
If anyone has some time, I'd appreciate some help: https://github.com/ploomber/jupysql/pull/1028
To Reproduce
see the logs from github
OS:
mac
JupySQL Version:
latest
Full Name:
Eduardo
Affiliation:
Ploomber

@idomic the issue I mentioned in our meeting


Fixed large variants in variant_key and added documentation and a test.

Closes #183
Made a small change that printed the alt/ref that is not long rather than "None" which was a bug from the last PR that changed variant_key.
I also added a line of documentation describing that what happens if "ref" or "alt" are over 50 base pairs. And I added a test that makes sure it prints correctly.

@pnrobinson @ielis
I don't know where this error is coming from - "ERROR tests/analysis/test_mtc_filter.py::TestHeuristicSamplerMtcFilter::test_filter_terms_to_test - ValueError: The CURIE 0025354 has no colon : or underscore _"
It appears to be happening during the creation of the fixture mtc_filter, could it be a bug in the hpo file?

@lnrekerle On my machine, this test is passed. Unlcear what the issue is, as I could not find an instance of that id without the prefix


Raylib examples?

Is your feature request related to a problem? Please describe.
Raylib is a c wrapper library for opengl there is a port for C# called raylib-cs
It would be cool if you could provide and example to hook into raylib's main window and provide texture and renderTexture widgets.
Not sure what is needed to do this but it would be really cool.
Describe the solution you'd like
Examples for hooking raylib-cs's MainWindow, RenderTexture2D and Texture2D into custom avalonia widgets.
Describe alternatives you've considered
I have considered using ImGui but it's unsafe and buggy.
I have also tried writing a my own opengl wrapper in C# but it's not easy.
Additional context
Raylib's uses a static window api so there can only be one window.

Sharing responsibility between multiple renderers is difficult. There are several scenarios here and it's not clear what you want:

Have an Avalonia app and want to embed a window's content drawn by Raylib as a child view -> use NativeControlHost or integrate with the compositor.
Have a Raylib app and want to use Avalonia -> Create a new Avalonia platform, probably.
Want to use Raylib to render Avalonia views -> create a vector rendering engine in Raylib and create a new Avalonia rendering backend.

Some are easier than others and mixed content tends to run into airspace issues.

Shouldn't be that difficult to render the Raylib window by wrapping it with NativeControlHost. Rendering Raylib textures as an Avalonia control will be much harder. AFAIK, any approach involving WriteableBitmap will pull from the GPU (previously rendered Raylib texture) to CPU (WriteableBitmap locked and being mutated with texture data), then push back to GPU to draw. I imagine there's a compositor-based approach for this, but the entire area is largely undocumented. Said implementation would be up to you.

I am trying to do similar thing (not with raylib, but with my own rendering/platform framework). And as far as I tried, there is no way to implement custom platform for avalonia outside of avalonia. I don't understand why everything I can implement myself is made "internal" and the only way is to download avalonia sources and patch it.

@cprkv Custom backends are supported though the APIs have no version stability guarantees. You need to opt-in using <AvaloniaAccessUnstablePrivateApis>true</AvaloniaAccessUnstablePrivateApis> in csproj and then you will be able to work with [PrivateApi], Impl-ending interfaces, etc. This exists so ordinary applications don't use these APIs and unknowingly take on higher breaking change risks and also so Avalonia has an easier time being split into multiple packages.


posh-ssh with RMM tools - Requested Registry access is not allowed

I'm trying to run a script using posh-ssh within a remote monitoring and management tool. Connectwise Automate in this case.
The script runs properly from a normal command line with a logged on user. However Connectwise most commonly does it's work as the localsystem account. I'm getting an error regarding registry access.
I'm wondering, if the registry is only used for is storing keys (that's all I could find it doing), if it might not be supportable to use a portable csv file instead?

Yes registry is used for storing keys, no it does not support key storage or validation via CSV. In a future release I can make it so when one disables key validations it does not try to open the registry key.

On Feb 28, 2017, at 12:40 PM, markwiater<EMAIL_ADDRESS>wrote:
I'm trying to run a script using posh-ssh within a remote monitoring and management tool. Connectwise Automate in this case.
The script runs properly from a normal command line with a logged on user. However Connectwise most commonly does it's work as the localsystem account. I'm getting an error regarding registry access.
I'm wondering, if the registry is only used for is storing keys (that's all I could find it doing), if it might not be supportable to use a portable csv file instead?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/darkoperator/Posh-SSH/issues/136, or mute the thread https://github.com/notifications/unsubscribe-auth/AAf0Hrx34DIB_ev966lxJ3bUOVlppQ-Rks5rhE4CgaJpZM4MOoYd.

Thanks Carlos. That sounds great.   Any ideas when that future release might be available?
I'd also like to respectfully request consideration of an alternate method (different from the registry) to validate keys at some point way in the future.
Thanks again

No clue on when I Would have version 2.0 out, have so many projects I only work on it once or twice a year on it a bit unless a major bug comes out

On Feb 28, 2017, at 1:20 PM, markwiater<EMAIL_ADDRESS>wrote:
Thanks Carlos. That sounds great. Any ideas when that future release might be available?
I'd also like to respectfully request consideration of an alternate method (different from the registry) to validate keys at some point way in the future.
Thanks again
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/darkoperator/Posh-SSH/issues/136#issuecomment-283105207, or mute the thread https://github.com/notifications/unsubscribe-auth/AAf0Hl2pvD-A7U02yQnsrBeNkK3bm8tYks5rhFdBgaJpZM4MOoYd.

will try to push version 2.0 after I'm finished with DEFCON

Yes it did, just use -Force

On Aug 21, 2017, at 9:22 AM, markwiater<EMAIL_ADDRESS>wrote:
Hi Carlos,
Did this change make it in to 2.0? I see that it was released a week or so back.
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/darkoperator/Posh-SSH/issues/136#issuecomment-323742920, or mute the thread https://github.com/notifications/unsubscribe-auth/AAf0Huc0X8UIx9Sb6MPFYwm2FEsONlzOks5saYSRgaJpZM4MOoYd.

Thank you!
On 8/21/2017 9:23 AM, Carlos Perez wrote:

Yes it did, just use -Force

On Aug 21, 2017, at 9:22 AM, markwiater<EMAIL_ADDRESS>wrote:
Hi Carlos,
Did this change make it in to 2.0? I see that it was released a week
or so back.
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/darkoperator/Posh-SSH/issues/136#issuecomment-323742920,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAf0Huc0X8UIx9Sb6MPFYwm2FEsONlzOks5saYSRgaJpZM4MOoYd.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/darkoperator/Posh-SSH/issues/136#issuecomment-323743176,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY4keFnxmRgWbRRrNoYybBnsq1d5ofsnks5saYTmgaJpZM4MOoYd.


OTA reference app needs updates for QueryStatus and DelayedActionTime

Starting the ota-provider reference app with the following options

./chip-ota-provider-app -f sw_image.txt -q UpdateNotAvailable
On the ota-requestor-app I see that the file is being downloaded.
Expected behavior - File should not be transferred.

set DelayedActionTime field to 600 seconds. The file gets transferred immediately.
Expected behavior - File should only be transferred after the time mentioned.

@akrithika27 On ToT, I do not see issue #2. Perhaps you tested this on an older commit.


Could not download correct snapshot version

Expected Behavior
I want to download a snapshot in my maven .But gradle told me Resource missing.When I open log,I found gradle download wrong version.
Gradle will download snapshot version by concating timestamp and buildnumber.It correct in almost all time.But there's something special about my situation .My maven-metadata.xml is
<metadata modelVersion="1.1.0">
    <groupId>org.bwae.auth</groupId>
    <artifactId>auth</artifactId>
    <version>0.0.1-SNAPSHOT</version>
    <versioning>
        <snapshot>
            <timestamp>20190524.065754</timestamp>
            <buildNumber>2</buildNumber>
        </snapshot>
        <lastUpdated>20190524065754</lastUpdated>
        <snapshotVersions>
            <snapshotVersion>
                <extension>jar</extension>
                <value>0.0.1-20190524.065752-1</value>
                <updated>20190524065754</updated>
            </snapshotVersion>
            <snapshotVersion>
                <extension>pom</extension>
                <value>0.0.1-20190524.065752-1</value>
                <updated>20190524065754</updated>
            </snapshotVersion>
            <snapshotVersion>
                <classifier>sources</classifier>
                <extension>jar</extension>
                <value>0.0.1-20190524.065752-1</value>
                <updated>20190524065754</updated>
            </snapshotVersion>
        </snapshotVersions>
    </versioning>
</metadata>

Snaptshot version not equal  timestamp with buildNumber.It is happens because I upload a  jar to maven failed last time,so, it build number will add one ,but snapshot version will not.
https://github.com/gradle/gradle/blob/a4ac29f8fab55e587130677f9d2df826dc0a8786/subprojects/dependency-management/src/main/java/org/gradle/api/internal/artifacts/repositories/resolver/MavenResolver.java#L181
so this logic is not correct.Snapshot version  should not relay on buildNumber
Current Behavior

gradle can not download the correct  snapshot version.
Downloading http://maven.bwae.org/repository/ae-public/org/bwae/auth/auth/0.0.1-SNAPSHOT/maven-metadata.xml to C:\Users\Luzz\AppData\Local\Temp\gradle_download9101900790421438102bin
Resource missing. [HTTP GET: https://maven.bwae.org/repository/ae-public/org/bwae/auth/auth/0.0.1-SNAPSHOT/auth-0.0.1-20190524.065754-2.pom]
Resource missing. [HTTP HEAD: https://maven.bwae.org/repository/ae-public/org/bwae/auth/auth/0.0.1-SNAPSHOT/auth-0.0.1-20190524.065754-2.jar]

Context

Steps to Reproduce

Deploy a jar to maven failed.And gradle will not work correctly
Your Environment

Build scan URL:

Sadly the Maven specification for these files does not say much about the consistency of the content, especially between the snapshotVersion and snapshot child nodes.
Given this is the result of failed deployment, the easiest solution is to attempt the deployment again or correct the maven-metadata.xml file itself.

Closing as there is no plan on changing this behavior from the Gradle side.


Rename recipient to target, to align with LCA nomenclature

/cc @eranco74
/cc @jeff-roche
/cc @omertuc
/hold
Let's merge this in coordination with @jeff-roche to not disrupt CI

Merging!


[android] FadeTransitions do not work with platform views using hybrid composition

FadeTransitions do not work on platform views that use hybrid composition. The example below uses a Google Map but this also applies to other platform views (like webviews).
Expected results: The Flutter logo and platform view are both fading, like when hybrid composition is disabled.
Actual results: The Flutter logo is fading while the platform view (Google Map in this case) is not.

Code sample
Example taken from the Flutter documentation for FadeTransition, with an added GoogleMap.
/// Flutter code sample for FadeTransition

// The following code implements the [FadeTransition] using
// the Flutter logo:

import 'package:flutter/material.dart';
import 'package:google_maps_flutter/google_maps_flutter.dart';

void main() {
  AndroidGoogleMapsFlutter.useAndroidViewSurface = true;
  runApp(const MyApp());
}

/// This is the main application widget.
class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      title: _title,
      home: MyStatefulWidget(),
    );
  }
}

/// This is the stateful widget that the main application instantiates.
class MyStatefulWidget extends StatefulWidget {
  const MyStatefulWidget({Key? key}) : super(key: key);

  @override
  State<MyStatefulWidget> createState() => _MyStatefulWidgetState();
}

/// This is the private State class that goes with MyStatefulWidget.
/// AnimationControllers can be created with `vsync: this` because of TickerProviderStateMixin.
class _MyStatefulWidgetState extends State<MyStatefulWidget> with TickerProviderStateMixin {
  late final AnimationController _controller = AnimationController(
    duration: const Duration(seconds: 2),
    vsync: this,
  )..repeat(reverse: true);
  late final Animation<double> _animation = CurvedAnimation(
    parent: _controller,
    curve: Curves.easeIn,
  );

  @override
  void dispose() {
    _controller.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Container(
      color: Colors.white,
      child: FadeTransition(
        opacity: _animation,
        child: Padding(
          padding: EdgeInsets.all(8),
          child: SafeArea(
            child: Column(
              children: [
                FlutterLogo(
                  size: 128,
                ),
                Expanded(
                  child: GoogleMap(
                    initialCameraPosition: CameraPosition(
                      target: LatLng(37.3861, 122.0839),
                    ),
                  ),
                ),
              ],
            ),
          ),
        ),
      ),
    );
  }
}

`flutter doctor -v` output
[✓] Flutter (Channel stable, 2.5.3, on Ubuntu 21.10 5.4.72-microsoft-standard-WSL2, locale en_US.UTF-8)
    • Flutter version 2.5.3 at /home/developer/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (5 weeks ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /home/developer/android
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /home/developer/android
    • ANDROID_SDK_ROOT = /home/developer/android
    • Java binary at: /usr/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_302-8u302-b08-0ubuntu2-b08)
    • All Android licenses accepted.

[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).

[✓] Connected device (1 available)
    • IN2023 (mobile) • <IP_ADDRESS>:43119 • android-arm64 • Android 11 (API 30)

! Doctor found issues in 2 categories.

Video demonstration
https://user-images.githubusercontent.com/14238527/142120687-55e5364e-f8b0-424f-9a30-4de85032f5ea.mp4
https://user-images.githubusercontent.com/14238527/142120745-b0b07609-fbc3-4ae0-981d-b0394539bd03.mp4

Reproducible on stable and master only on android.
The same behavior can be observed using webview_flutter with hybrid composition enabled.

videos
with hybrid composition
https://user-images.githubusercontent.com/88313112/142171765-178718e8-f9d8-4533-bc58-60e10a05b711.mov
without hybrid composition
https://user-images.githubusercontent.com/88313112/142171875-9c0ec0aa-539f-4f75-8c01-1b34269dd845.mov
iOS
https://user-images.githubusercontent.com/88313112/142180558-27e09d65-bab0-4edf-bdaf-315cfa21f0c0.mp4

flutter doctor -v
[✓] Flutter (Channel master, 2.6.0-12.0.pre.738, on macOS 11.6 20G165 darwin-arm, locale en-GB)
    • Flutter version 2.6.0-12.0.pre.738 at /Users/nexus/dev/sdks/flutters
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 09482cb80b (3 hours ago), 2021-11-16 23:42:34 -0500
    • Engine revision<PHONE_NUMBER>
    • Dart version 2.16.0 (build 2.16.0-14.0.dev)
    • DevTools version 2.8.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.62.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.28.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 11.6 20G165 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 96.0.4664.45

• No issues found!

[✓] Flutter (Channel stable, 2.5.3, on macOS 11.6 20G165 darwin-arm, locale en-GB)
    • Flutter version 2.5.3 at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (5 weeks ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 13.0, Build version 13A233
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[✓] VS Code (version 1.62.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.28.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 11.6 20G165 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 96.0.4664.45

• No issues found!

I have looked into this issue myself and I'm pretty sure I found the cause.
Here is a run-down of what I found:
onDisplayPlatformViews is being called for every platform view that is going to be displayed in the current frame. The FlutterMutatorView is responsible for applying various different layers to the platform view, such as clipping, transformation or opacity. To do this, FlutterMutatorView receives (here and ultimately here) a FlutterMutatorsStack and goes through all of the mutators and applies them on draw. These mutations are ultimately coming from the SceneBuilder from the Flutter Framework but were never fully implemented for Android platform views using hybrid-composition. I found this issue which tracks the implementation of various scene builder operations, but it wrongly marked pushOpacity and pushClipPath as implemented, which is not the case. You can see that the implementation of those scene builder operations is missing here.
This method essentially constructs the platform view draw instruction but omits the opacity layer, resulting in the problem of this issue. You can also see that the FlutterMutator class is missing a constructor for FlutterMutatorType.OPACITY.
So, in order to fix this issue, we need to:

Implement a constructor for FlutterMutatorType.OPACITY on the FlutterMutator class (here)
Implement a method pushOpacity on the FlutterMutatorsStack class (here)
Call pushOpacity on the mutator stack in the JNI implementation (here)
Implement opacity handling in the draw method of the FlutterMutatorView (here)
Bonus: Implement other missing scene builder operations (here)

To do this, we first need to make ourselves familiar with the layer tree and how it arrives on the Android side (so we don't mess up the order or anything else)
I'm going to attempt to implement this myself in the coming days as I don't think this is a high-priority issue seeing that it hasn't gained any traction yet and wasn't marked as important in the implementation issue here.

@danagbemava-nc could you remove the framework label and instead attach the engine label?
As the entire implementation is done in flutter/engine, I believe this is an engine issue.

cc @blasten. @WasserEsser investigation is spot on. It is a missing mutator stack application on Android.

The patch was reverted in https://github.com/flutter/flutter/issues/97079

I'll look into this more to see if there are other ways to do this.
If not, we could check whether or not we need the layer in the current frame and then only apply it in the cases where we need it.
This would avoid the performance hit for cases where it's not needed.

How's the progress going on this? Any upcoming fix/ workaround?

You should avoid using hybrid composition mode.

any news on this?

Wow, Just facing/understanding this issue 🙃 .
Any news on it ? In my case I display a WebView setup with HybridComposition and the AutoRoute transition animation is kinda Laggy because of this.
Thx


Version on umbrel says 24.05-modded

Should the version when using the production umbrel cln app have "-modded"?

Fixed with v24.08 Docker image.


run fail

2020-11-04T02:09:10.710Z	INFO	peermgr	peermgr/peermgr.go:193	connecting to bootstrap peers
2020-11-04T02:09:10.712Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:10.713Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:10.713Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:10.714Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:10.715Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:10.716Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:15.710Z	INFO	peermgr	peermgr/peermgr.go:193	connecting to bootstrap peers
2020-11-04T02:09:15.712Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:15.713Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:15.714Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:15.714Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:15.715Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:15.716Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:20.710Z	INFO	peermgr	peermgr/peermgr.go:193	connecting to bootstrap peers
2020-11-04T02:09:20.714Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:20.717Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:20.719Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:20.723Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:20.725Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:20.728Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:25.710Z	INFO	peermgr	peermgr/peermgr.go:193	connecting to bootstrap peers
2020-11-04T02:09:25.712Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:25.712Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:25.713Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:25.714Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff
2020-11-04T02:09:25.715Z	WARN	peermgr	peermgr/peermgr.go:196	failed to connect to bootstrap peer: dial backoff

failed to connect to bootstrap peer

Is the mirror on docker hub the mainnet?

I build lotus version is:v1.2.0

@symanovich-a

Log.txt

this is  log

hey @satonz
what is your cpu? we use intel


Simplistic load/save of yellowfin.

Trying to address: https://github.com/JianGoForIt/YellowFin_Pytorch/issues/9
The approach is to save anything that is potentially "stateful" in the optimizer. A quick sanity check indicates that this works.
Sanity check: https://gist.github.com/mrdrozdov/d3d6ac43a3130c799e4f3f5867853184

Hi @mrdrozdov
Thanks for trying out the optimizer and setup the PR. It is elegant and simple way. However, I still see other things needing to be saved and loaded.
The additional list is here
self._clip_thresh = clip_thresh
self._beta = beta
self._curv_win_width = curv_win_width
self._zero_debias = zero_debias
and I assume weight_decay is handled by the underlying pytorch sgd optimizer, right?
If these additional things are added in your PR, we will be happy to accept the PR.

@JianGoForIt I've added the missing values. Thank you for putting together a great project ^_^


Cannot update a component (ForwardRef(TouchRipple)) while rendering a different componentent (XYZ)

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
I am getting this warning while clicking IconButton.
Followed React Github page and new warning on React's website but can not implement this solution because this happens in MUI ripple i guess.
I am getting this warning:
Warning: Cannot update a component (ForwardRef(TouchRipple)) while rendering a different component (XYZ).

Expected behavior 🤔
No response
Steps to reproduce 🕹
Steps:

Context 🔦
No response
Your environment 🌎

`npx @mui/envinfo`
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://mui.com/r/issue-template or https://mui.com/r/ts-issue-template), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

I am currently experiencing this issue in this revision of my application: https://github.com/monetr/monetr/tree/2f24ace78835979fb70801ee5b2c234611013ed6
Specifically I am experiencing the issue when trying to render this component: https://github.com/monetr/monetr/blob/2f24ace78835979fb70801ee5b2c234611013ed6/ui/components/Goals/EditGoalView.tsx

This ended up being a completely unrelated issue, but this error is definitely misleading.
The fix ended up being https://github.com/monetr/monetr/commit/a067dc33ffa404632dc7a8cac57926c9407ece5d
I was passing an array of [[number, Element]] instead of an array of elements. No idea why this error manifests in that scenario?


Many gifs/videos on imgur show up as black squares

Probably similar to https://github.com/mozilla/tofino/issues/1050
Go to http://imgur.com/topic/Aww and browser for a while.

Dupe of #1050


Pluggable rule engine

It would be good if adding rules was as simple as telling CLI to look in a directory containing .py scripts that look something like:
@Rule(link="http://example.com/my-rule")
def obey_my_rule():
   ...

Can we keep the scope of this to be discovering rules within this repo?

@bloomonkey given we've merged #7; can we close this?


error when using a interface{} type

Error: failed to perform code-generation for CustomResources: (Generating deepcopy funcs
F1014 11:43:53.081904   73338 main.go:81] Error: Failed executing generator: some packages had errors:
errors in package "github.com/sstarcher/newrelic-operator/pkg/apis/newrelic/v1alpha1":
unable to format file "/Users/sstarcher/go/src/github.com/sstarcher/newrelic-operator/pkg/apis/newrelic/v1alpha1/zz_generated.deepcopy.go" (82:55: expected ';', found '{' (and 5 more errors)).

type AlertChannel struct {
	metav1.TypeMeta   `json:",inline"`
	metav1.ObjectMeta `json:"metadata"`
	Spec              AlertChannelSpec   `json:"spec"`
	Status            AlertChannelStatus `json:"status,omitempty"`
}

type AlertChannelSpec struct {
	Configuration interface{} `json:"configuration,omitempty"`
}

@shawn-hurley I'm not seeing metav1.RawData and it looks like unstructured.Unstructured  is specifically for Kubernetes objects as it expects a Kind
Specifically I don't see RawData under 	metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"

perfect thanks


Added template for package name

The missing template caused a compile error.

Thank you for the contributions :1st_place_medal: