[tuner] Reduce maintenance burden and prepare for more codegen Pipelines

This is an uber-issue for making the tuner easier to maintain. The current implementation has a few issues that make the tuner library fragile and prone to getting out of sync with the IREE compiler. Specifically, we identified the following issues:

There are two ways to (re-)configure executable sources:
a. By updating the lowering config and translation info in-situ. This is used when producing candidate dispatches using executable benchmarks as the source-of-truth.
b. By using the transform dialect library script to match root ops and apply compilation info attributes to them. This is used during the model candidate compilation and benchmarking stage.
As a result, we have duplicate logic to apply configurations found by the constraint solver. The fix is to write a pass that strips existing configuration from executable sources, and then use transform dialect to re-configure them. This can be done as a separate invocation of iree-opt.

The MLIR processing is mostly string-based. While this allowed us to quickly prototype, it makes the code prone to getting out of sync with the IREE compiler. The lowering configs and translation info attributes are considered compiler-internals and there's no stability guarantee as to the exact structure and format of these attributes. As a result, every time the format changes, we have to update the parsing and printing logic in the tuner to match the new format in the compiler.
Here, the proposed solution is to expose these key attributes (translation info, compilation info, and MFMA intrinsic info) through python bindings. We already have it for the GPU pipeline options that can be used as a template for future bindings: https://github.com/iree-org/iree/pull/18840.

Make it easier to identify 'root ops'. We can make the IREE compiler annotate the root lingalg ops with a new attribute that the tuner can use to recognize them, without having to duplicate the compiler logic.

The Configuration representation is modeled after the requirements of the LLVMGPUVectorDistribute pipeline. This made it so that the surrounding code makes implicit assumptions about the problem representation. Instead, we should define an interface that allows us to support multiple compilation pipelines, such that the generated SMT constraints are specific to both the pipeline and the dispatch kind. Further, the constraint generation code should be decoupled from the parsing/printing code, such that projects like TKW can use just the constraint generation and benchmarking infra.

Move from two stages of compile-and-benchmark to just one. This made sense for SDXL where the best isolated dispatch does not necessarily perform best across the whole model, but it may not be necessary or even sufficiently general for other applications. This is related to the libtuner.TuningClient class; clients should be able to define their own tuning stages with libtuner providing the interface to specify the compilation and benchmarking commands.

Tasks

[ ] Add an iree-opt pass to strip configuration from executable sources (incl. executable benchmarks) @bangtianliu
[ ] Update the tuner to generate candidate dispatches using the new iree-opt pass and transform dialect specs. @bangtianliu
[ ] Expose key attributes via python bindings. @kuhar
[ ] Make the tuner use python bindings to parse and print attributes.
[ ] Modify IREE to annotate root ops with a new unit attribute.
[ ] Update the tuner to identify root ups using the new unit attribute produced by IREE.
[ ] Add support for the TileAndFuse pipeline. @bangtianliu and @Max191
[ ] Move constraint generation logic out of the parsing/printing logic in candidate_gen.py.
[ ] Use only one compile-benchmark stage in TuningCandidate. Update the existing example to adapt to this change.

cc: @MaheshRavishankar @nithinsubbiah @bangtianliu @Max191

Thanks @kuhar . Could you also add a pointer to where the tuner lives today.
The tasks you described are related to making it easy to maintain the tuner. One more thing we need to think about is how to make it easy to maintain and update the tuner script. Specifically questions to answer are

We currently use the result of tuner (the TD script) during compilation. Do we maintain a default script that is somewhere in IREE codebase that gets loaded.
How does a developer update the tuner script if they need to (i.e they change the lowering config/translation info could there be a tool that "ports" the configuration over)
Could we have multiple TD scripts passed to the compiler. My answer to this would be no, but it might be useful to have a tool to "merge" TD scripts. This could also be the mechanism to update the tuner script. You create a new tuner script and "update".

For now just noting some top-of-mind questions.

@MaheshRavishankar The tuner lives under the tuner directory in this repo. The questions you listed are very relevant but not to the tuner itself but the iree project -- I decided to decouple these two sets of concerns. I will answer your questions under an iree issue and add a link here.

The IREE issue that explains the logistics of how we maintain tuning specs and apply them in the codegen flow is here: https://github.com/iree-org/iree/issues/19214


Update linux install instructions

There is no pecl extension available for kafka
No releases available for package "pecl.php.net/kafka"

@robsontenorio yeah sry, i added this a bit prematurely, i am still in touch with the php community to add it to PECL :smile:
i will remove that for the time being, thx for the input :heart:

@robsontenorio yeah sry, i added this a bit prematurely, i am still in touch with the php community to add it to PECL :smile:
i will remove that for the time being, thx for the input :heart:

@nick-zh
Will pecl rdkafka be renamed to pecl kafka? Or they are different projects?
I am getting started now. And that is a bit confusing.

@nick-zh
Will pecl rdkafka be renamed to pecl kafka? Or they are different projects?
I am getting started now. And that is a bit confusing.

These are different projects, i will follow a different philosophy than the original project and want to move faster
I am sorry for the confusion this is posing on you :bow:

These are different projects, i will follow a different philosophy than the original project and want to move faster
I am sorry for the confusion this is posing on you :bow:

@nick-zh Maybe some footnotes about diferences between that libraries/ext/package would be useful for newcomers.
Thanks for your helping!

@nick-zh Maybe some footnotes about diferences between that libraries/ext/package would be useful for newcomers.
Thanks for your helping!

Agreed, thank you for the input. I will add this tomorrow

Agreed, thank you for the input. I will add this tomorrow


fix: TableCopy reference to global RAID_CLASS_COLORS to prevent taint.

Related Issues:

https://legacy.curseforge.com/wow/addons/lfg-group-finder-bulletin-board?comment=623

Taint occurs on line 61 where global table data was modified with Tool.ClassColor[k] = v; whenever CUSTOM_CLASS_COLORS existed.

@Vysci this ones pretty breaking for people using any addons with CUSTOM_CLASS_COLORS, i think it should get a hotfix update.


Change all feature names in cad file to helpful/descriptive names

closed with https://github.com/leapedcamera/Igor/commit/fc6755a4be5590adc04a950e342061106de37418


How about micrometer?

I wonder if it would be useful to think about this as a Micrometer metrics reporter rather than solely a Prometheus one? My understanding is that users could then choose any of the systems that Micrometer supports, of which Prometheus is one.
https://micrometer.io/
I haven't used micrometer personally in any project yet, so I don't know what potential limitations or drawbacks there might be to such an approach.

Thanks for the suggestion.
I'm not too familiar with Micrometer so correct me if I'm wrong. I see Micrometer as an API to define metrics. Kafka already uses its own libraries for defining metrics.
I think you mean a Kafka metrics reporter could grab the existing Kafka metrics and create the matching Micrometer metrics. Then we would need a way to specify the monitoring system to target and rely on Micrometer to do it. Unfortunately it looks like to setup the export mechanism you need some code so it's not completely free to support many systems.
At the moment, I've mainly built this to use it with Strimzi where Prometheus is the main target monitoring system and supporting other tools would have some additional cost.


tests directory is a module unto itself causing import errors for any project with a local tests directory

What is the current behavior?
When you install deepgram-sdk in python, there are two packages created. One importable with from deepgram import ... and one with from tests import ...
deepgram and tests are two folders added under /home/vscode/.local/lib/python3.10/site-packages
In my projects whenever I do from tests.test_ai_models.test_openai.py there is a pytest import error that says that it cannot find test_ai_models under tests. This is because tests redirects to deepgram's package. Its very common for projects to have a dedicated tests directory, so this seems like unwanted behavior.
Steps to reproduce
Run pip install deepgram-sdk.
Please tell us about your environment
I'm using VSCode and a devcontainer. My main operating system is PopOs, but in the dev container its Debian. I'm using Python 3.10.14.

lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 12 (bookworm)
Release:        12
Codename:       bookworm

Other information
I'm 95% sure the problem gets solved if you just remove the init.py from the tests directory.

This was fixed in this PR:
https://github.com/deepgram/deepgram-python-sdk/pull/453
I will cut a patch release in a few minutes.

This should be available in the next few minutes:
https://github.com/deepgram/deepgram-python-sdk/releases/tag/v3.5.1


Default container starting without puppeteer (instant crash)

Hi, I tried your content checker and it didn't work in the basic "try it" version. I am new to apify, so I understand there maybe a problem with the way the Docker is started, but I couldn't figure out how to fix it on my own. I have added the failed run url along with the log: https://my.apify.com/view/runs/pcRvjQdbiwYJrse1S

Hello,
Thanks for pointing this out, I fixed it. Please try again.

Thanks for the quick fix, works as expected now.

Hello,
Thanks for pointing this out, I fixed it. Please try again.

Thanks for the quick fix, works as expected now.


Improve performance of ConsolidatorScanPriority comparison

Description
This introduces a new Comparer and supplies it to the PrioorityQueue constructor. This yields 5-10 percent improvement in data points per second for all Lean benchmarks on my machine.
Related Issue
See issue #8451
Motivation and Context
The ConsolidatorScanPriority type implements IComparable and is used as the priority in the SubscriptionManager's priority queue. Due to the way comparison is handled for the case when PriorityQueue is not supplied with IComparer instance explicitly, an intermediate ObjectComparer is used for the comparison that eventually delegates comparison to ConsolidatorScanPriority.CompareTo.
Requires Documentation Change
No
How Has This Been Tested?
Lean benchmarks
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[x] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

Hey @starteleport! Thank you for the contribution. Could you please add some simple test/benchmark proof we can run to assert the improvement? A reference/documentation proof would be great too 🙏
A quick review, I see priority queue seems to be creating a single comparer instance.

Sure!
Here are the benchmark results:
|                             Method |     Mean |    Error |   StdDev |   Gen0 | Allocated |
|----------------------------------- |---------:|---------:|---------:|-------:|----------:|
|                           Baseline | 19.77 us | 0.321 us | 0.301 us | 0.1831 |   1.63 KB |
|       ComparerDelegatingToBaseline | 13.02 us | 0.272 us | 0.731 us | 0.1984 |   1.63 KB |
| SealedComparerDelegatingToBaseline | 12.68 us | 0.250 us | 0.267 us | 0.1984 |   1.63 KB |
|                   ExplicitComparer | 12.09 us | 0.176 us | 0.164 us | 0.1984 |   1.63 KB |

Benchmark code
using BenchmarkDotNet.Attributes;
using BenchmarkDotNet.Configs;
using BenchmarkDotNet.Diagnosers;
using BenchmarkDotNet.Jobs;
using BenchmarkDotNet.Running;

var summary = BenchmarkRunner.Run<Bench>();

[Config(typeof(BenchmarkConfig))]
public class Bench
{
    private (ConsolidatorScanPriority, ConsolidatorScanPriority)[] _priorities;

    [GlobalSetup]
    public void Setup()
    {
        _priorities = Enumerable.Range(1, 100)
            .Select(_ => new ConsolidatorScanPriority(DateTime.UtcNow, Random.Shared.NextInt64(1000)))
            .Select(c => (c, c))
            .ToArray();
    }

    [Benchmark]
    public long Baseline()
    {
        long count = 0;
        var queue = new PriorityQueue<ConsolidatorScanPriority, ConsolidatorScanPriority>(_priorities);

        while (queue.TryDequeue(out var element, out var priority))
        {
            count += element.Id;
        }

        return count;
    }

    [Benchmark]
    public long ComparerDelegatingToBaseline()
    {
        long count = 0;
        var queue = new PriorityQueue<ConsolidatorScanPriority, ConsolidatorScanPriority>(
            _priorities,
            ConsolidatorScanPriority.DelegatingComparer);

        while (queue.TryDequeue(out var element, out var priority))
        {
            count += element.Id;
        }

        return count;
    }

    [Benchmark]
    public long SealedComparerDelegatingToBaseline()
    {
        long count = 0;
        var queue = new PriorityQueue<ConsolidatorScanPriority, ConsolidatorScanPriority>(
            _priorities,
            ConsolidatorScanPriority.DelegatingSealedComparer);

        while (queue.TryDequeue(out var element, out var priority))
        {
            count += element.Id;
        }

        return count;
    }

    [Benchmark]
    public long ExplicitComparer()
    {
        long count = 0;
        var queue = new PriorityQueue<ConsolidatorScanPriority, ConsolidatorScanPriority>(
            _priorities,
            ConsolidatorScanPriority.ExplicitComparer);

        while (queue.TryDequeue(out var element, out var priority))
        {
            count += element.Id;
        }

        return count;
    }
}

public class BenchmarkConfig : ManualConfig
{
    public BenchmarkConfig()
    {
        // Configure your benchmarks, see for more details: https://benchmarkdotnet.org/articles/configs/configs.html.
        AddJob(Job.Default);
        //AddLogger(ConsoleLogger.Ascii);
        //AddExporter(MarkdownExporter.GitHub);
        AddDiagnoser(MemoryDiagnoser.Default);
        //Add(TargetMethodColumn.Method, StatisticColumn.Max);
        //Add(RPlotExporter.Default, CsvExporter.Default);
        //Add(EnvironmentAnalyser.Default);
    }
}

internal class ConsolidatorScanPriority : IComparable
{
    /// <summary>
    /// The next utc scan time
    /// </summary>
    public DateTime UtcScanTime { get; }

    private sealed class UtcScanTimeIdRelationalComparer : IComparer<ConsolidatorScanPriority>
    {
        public int Compare(ConsolidatorScanPriority? x, ConsolidatorScanPriority? y)
        {
            if (ReferenceEquals(x, y)) return 0;
            if (y is null) return 1;
            if (x is null) return -1;
            var utcScanTimeComparison = x.UtcScanTime.CompareTo(y.UtcScanTime);
            if (utcScanTimeComparison != 0) return utcScanTimeComparison;
            return x.Id.CompareTo(y.Id);
        }
    }

    public static IComparer<ConsolidatorScanPriority> ExplicitComparer { get; } =
        new UtcScanTimeIdRelationalComparer();

    internal class ConsolidatorScanPriorityComparer : IComparer<ConsolidatorScanPriority>
    {
        public int Compare(ConsolidatorScanPriority? x, ConsolidatorScanPriority? y)
        {
            return x?.CompareTo(y!) ?? -1;
        }
    }

    internal sealed class ConsolidatorScanPrioritySealedComparer : IComparer<ConsolidatorScanPriority>
    {
        public int Compare(ConsolidatorScanPriority? x, ConsolidatorScanPriority? y)
        {
            return x?.CompareTo(y!) ?? -1;
        }
    }

    public static IComparer<ConsolidatorScanPriority> DelegatingComparer { get; } =
        new ConsolidatorScanPriorityComparer();

    public static IComparer<ConsolidatorScanPriority> DelegatingSealedComparer { get; } =
        new ConsolidatorScanPrioritySealedComparer();

    /// <summary>
    /// Unique Id of the associated consolidator
    /// </summary>
    public long Id { get; }

    public ConsolidatorScanPriority(DateTime utcScanTime, long id)
    {
        Id = id;
        UtcScanTime = utcScanTime;
    }

    public int CompareTo(object obj)
    {
        if (obj == null) return 1;

        var other = (ConsolidatorScanPriority)obj;
        var result = UtcScanTime.CompareTo(other.UtcScanTime);
        if (result == 0)
        {
            // if they are the same let's compare Ids too
            return Id.CompareTo(other.Id);
        }

        return result;
    }
}

The whole point of this change is to avoid using ObjectComparer that gets created via InitializeComparer -> Comparer<TPriority>.Default -> ComparerHelpers.CreateDefaultComparer(typeof(T)), which in turn delegates to System.Collections.Comparer.Default.Compare that has extra type checks.
If this queue wasn't used in a hot spot, this optimisation wouldn't make much sense, but I believe it would be beneficial to grab this low hanging fruit.


Write tests for #876

Hey @samuelcolvin, I stumbled across your patch for the Django Debug Toolbar, and I really liked it. I saw that the blocking issue was tests, so I went ahead and wrote some. What are your thoughts? Are you willing to merge these changes into your own branch?
(I'm not sure that L.155-157 in tests/test_integration.py are strictly necessary, but I was running into some weirdness with the Toolbar's redirect functionality and permanent 301 redirects, so that was my workaround.)

Looks good to me apart from my question, but I don't pretend to be knowledgeable enough to be the main reviewer.
I'm going to merge this so tests run then I/we can fix any more problems on the upstream PR.


[WebToolsE2E][Aspire]Create an Aspire Starter Application via CMD, open endpoint of 'webfrontend', the web page shows incorrectly.

REGRESSION INFO: Works fine on Aspire.ProjectTemplates.8.0.0-preview.1.23557.2
INSTALL STEPS

Clean machine: Win11 x64 23h2 ENU
Install the latest VS Code
Download the latest released C# DevKit [1.2.2]
Install 8.0.100 SDK
CLI workload update and install aspire workload: [Aspire.ProjectTemplates.8.0.0-preview.2.23606.12]
Apply NuGet Feeds

REPRO STEPS

Open CMD, creating an Aspire Starter App using following commands:

dotnet new aspire-starter -o aspirestarter
cd aspirestarter
code .

In the VS Code, click 'Extension' tab, click '...' to installl the C# DevKit. (Or simply do dotnet run of the AppHost project in the command line)
Under the solution explorer, right-click the aspirestarter.AppHost > Debug > Start New Instance
Go to http://localhost:18888/
On the dashboard, click the endpoint of webfrontend

Some notes:

This issue doesn't repro on VS.
This issue also repro on MacOS.

ACTUAL
The web page shows incorrectly.

EXPECTED

Note that I can reproduce this issue with simply doing dotnet run in the command-line too. I've updated the repro steps. This seems to be a recent regression because our validation team did not run into this issue during last week's validation using CLI.

Verified on Aspire.ProjectTemplates.8.0.0-preview.2.23610.1, this issue has been fixed.


make pdfin build folder not work

Hi all, please help
/home/peter/workspace/neorv32/docs>make pdf
[ -f revnumber.txt ] && REVNUMBER='-a revnumber='"$(cat revnumber.txt)" || unset REVNUMBER; \
asciidoctor-pdf $REVNUMBER \
  -a allow-uri-read \
  -a pdf-theme=neorv32-theme.yml \
  -r asciidoctor-diagram \
  datasheet/main.adoc \
  --out-file public/pdf/NEORV32.pdf
Traceback (most recent call last):
        6: from /usr/bin/asciidoctor-pdf:25:in `<main>'
        5: from /usr/lib/ruby/vendor_ruby/asciidoctor/cli/options.rb:274:in `parse!'
        4: from /usr/lib/ruby/vendor_ruby/asciidoctor/cli/options.rb:274:in `each'
        3: from /usr/lib/ruby/vendor_ruby/asciidoctor/cli/options.rb:276:in `block in parse!'
        2: from /usr/lib/ruby/vendor_ruby/polyglot.rb:65:in `require'
        1: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
/usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require': cannot load such file -- asciidoctor-diagram (LoadError)
        20: from /usr/bin/asciidoctor-pdf:25:in `<main>'
        19: from /usr/lib/ruby/vendor_ruby/asciidoctor/cli/options.rb:274:in `parse!'
        18: from /usr/lib/ruby/vendor_ruby/asciidoctor/cli/options.rb:274:in `each'
        17: from /usr/lib/ruby/vendor_ruby/asciidoctor/cli/options.rb:276:in `block in parse!'
        16: from /usr/lib/ruby/vendor_ruby/polyglot.rb:65:in `require'
        15: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:156:in `require'
        14: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:168:in `rescue in require'
        13: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:168:in `require'
        12: from /var/lib/gems/2.7.0/gems/asciidoctor-diagram-2.2.3/lib/asciidoctor-diagram.rb:1:in `<top (required)>'
        11: from /var/lib/gems/2.7.0/gems/asciidoctor-diagram-2.2.3/lib/asciidoctor-diagram.rb:1:in `require_relative'
        10: from /var/lib/gems/2.7.0/gems/asciidoctor-diagram-2.2.3/lib/asciidoctor-diagram/a2s.rb:2:in `<top (required)>'
         9: from /var/lib/gems/2.7.0/gems/asciidoctor-diagram-2.2.3/lib/asciidoctor-diagram/a2s.rb:2:in `require_relative'
         8: from /var/lib/gems/2.7.0/gems/asciidoctor-diagram-2.2.3/lib/asciidoctor-diagram/a2s/extension.rb:1:in `<top (required)>'
         7: from /var/lib/gems/2.7.0/gems/asciidoctor-diagram-2.2.3/lib/asciidoctor-diagram/a2s/extension.rb:1:in `require_relative'
         6: from /var/lib/gems/2.7.0/gems/asciidoctor-diagram-2.2.3/lib/asciidoctor-diagram/a2s/converter.rb:2:in `<top (required)>'
         5: from /var/lib/gems/2.7.0/gems/asciidoctor-diagram-2.2.3/lib/asciidoctor-diagram/a2s/converter.rb:2:in `require_relative'
         4: from /var/lib/gems/2.7.0/gems/asciidoctor-diagram-2.2.3/lib/asciidoctor-diagram/util/cli_generator.rb:2:in `<top (required)>'
         3: from /usr/lib/ruby/vendor_ruby/polyglot.rb:65:in `require'
         2: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
         1: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
/usr/lib/ruby/2.7.0/tempfile.rb:121:in `<top (required)>': superclass mismatch for class Tempfile (TypeError)
make: *** [Makefile:9: pdf] Error 1

This looks similar to https://github.com/stnolting/neorv32/issues/250, so it might be a problem with your asciidoctor installation.
Does make html work as expected?
Btw, you can find prebuilt PDF version of the latest data sheet here.

it works in other ubuntu now, thanks


hack for galaxy version parsing for existing workflows

Description
Allows for re-indexing of existing Galaxy workflows for version information
Review Instructions
After initial run of EntryResource.updateLanguageVersions galaxy workflows should have language versions.
If interested in SQL query to look at results (adds gxformat2 and gxformat1)
webservice_test=# select count(descriptortypeversions), descriptortypeversions from version_metadata group by descriptortypeversions order by count;
 count | descriptortypeversions
-------+------------------------
     0 |
     2 | v1.1    1.0
     2 | 1.0     v1.0
     2 | 1.0     draft-2
     2 | 4.0
     2 | v1.2    v1.0
     3 | gxformat2
     9 | 1.1
    10 | v1.2    v1.1
    13 | 1
    15 | development
    15 | v1.2    v1.1    v1.0
    28 | v1.2
    39 | v1.1    v1.0
   142 | draft-2 1.0
   152 | v1.1
   445 | 2
   705 | gxformat1
  2103 | v1.0
  8504 | draft-2
 35537 | 1.0
(21 rows)

New github app updates for Galaxy workflows should have them too
Issue
https://github.com/dockstore/dockstore/issues/5270
Security
None known
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that you pass the basic style checks and unit tests by running mvn clean install
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
[x] If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
[x] Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
[x] Do not serve user-uploaded binary images through the Dockstore API
[x] Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
[x] Do not create cookies, although this may change in the future
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

Looks a little funny, but works


Option to auto hold Push To Talk key

Hey there,
EXP Soundboard has a nice feature where you can set a specific key to be pressed while sound is being played, so you don't need to use some push to talk keys manually all the time while playing sounds.

I'll look into it. :)

Maybe even implement this in a way where there can be a global PTT key or application specific PTT keys in combination with #5

Another great idea.


Can't set Font of StyleClassedTextArea

Hello i'm doing this:
	area.setFont(Font.font(20));

But nothing happens the font stays the same.
This is my StyleClassesTextArea:
private StyleClassedTextArea area = new StyleClassedTextArea();

And i'm called the setFont method in the start method above stage.show();

Hi, use this instead:
area.setStyle("-fx-font-size: 20;");

Maybe I should just remove fontProperty on text area altogether.

I just created a branch to remove this. However, if the skin is going to be removed (#206), would it actually be worth it to keep the fontProperty?

Removing the skin doesn't make much difference here. Propagating the `font

I believe this issue can be closed now.

Yes, thank you.


Remove loki workaround

IAM-1229
Upstream problem appears to be fixed by https://github.com/canonical/loki-k8s-operator/pull/453

It appears that there is no 5.20 lxd release anymore, so the tests are failing. Can we use latest/stable instead?
https://github.com/canonical/openfga-operator/blob/447c799f2c0859915d3eef234d942bfa0365cfa7/.github/workflows/tests.yaml#L36

I understand that setting latest/stable will remove some chores from our team. For example, when the release disappears from the upstream like in the mentioned case.
But doesn't it mean that with latest/stable, it could be possible for the OpenFGA charm consumers to accidentally get a new major LXD version, which might be non-compatible with the charm?
According to the LXD docs, current stable 5.x channels are 5.21/stable and 5.0/stable (claimed to be LTS). I would suggest one of these if there are no strong objections.

It appears that there is no 5.20 lxd release anymore, so the tests are failing. Can we use latest/stable instead?
https://github.com/canonical/openfga-operator/blob/447c799f2c0859915d3eef234d942bfa0365cfa7/.github/workflows/tests.yaml#L36

I understand that setting latest/stable will remove some chores from our team. For example, when the release disappears from the upstream like in the mentioned case.
But doesn't it mean that with latest/stable, it could be possible for the OpenFGA charm consumers to accidentally get a new major LXD version, which might be non-compatible with the charm?
According to the LXD docs, current stable 5.x channels are 5.21/stable and 5.0/stable (claimed to be LTS). I would suggest one of these if there are no strong objections.

Agreed, I updated the lxd version. BTW isn't it weird that a release just disappeared or am I stupid?

Agreed, I updated the lxd version. BTW isn't it weird that a release just disappeared or am I stupid?

I wouldn't expect something like that to happen. Asked the LXD team for comments.


feat: remove AnyNetwork usage

Migrates EthApi to using Ethereum network instead of AnyNetwork
This would allow to make https://github.com/paradigmxyz/reth/pull/12215 cleaner as with https://github.com/alloy-rs/alloy/pull/1460 AnyNetwork rpc transaction structure is a bit different

good to merge or should we hold off until #12215 is ready?

good to merge or should we hold off until #12215 is ready?

good to merge, it should make #12215 less painful


Emit events when a marker is found and lost, when using aframe's

What kind of change does this PR introduce?
New feature
Can it be referenced to an Issue? If so what is the issue # ?
#217
How can we test it?
Check the aframe/examples/marker-events.html that I created.
Summary
When an <a-marker> is found or lost, there is currently no event emitted (as far as I know), to "the outside world". In other words, currently an application that is using AR.js cannot react to the marker becoming visible or invisible.
With my addition, markerFound and markerLost  events will be emitted when the marker changes its visible state. The events are only emitted for <a-marker> elements which have emitevents='true' set.  emitevents defaults to false, so there will be no additional events emitted for any of the existing users of the AR.js library.
Does this PR introduce a breaking change?
No.
Other information
I also created a new build, and updated some README and CHANGELOG files. If these should be excluded from the pull request, let me know and I could make the adjustments.

What I really need is this one. Referencing #294

This is great! How can I download this branch to use in my project?

Hey @peterlunglum,
You can download my forked version git@github.com:nikolaymihaylov/AR.js.git and then do a git checkout tags/1.5.2 for the changes that are currently present in this pull request.
Keep in mind that this pull request has already diverged a lot with the original repository, so by choosing to use my forked version, you won't be getting other improvements or bugfixes for AR.js.
The proper solution would be to get this pull request merged to the main repository. I do not know what its maintainers think about my changes though.

@nikolaymihaylov A really great job! I just tried it and it works really well with Hiro marker and Kanji, but I cannot make it work with a custom marker for example like
<a-marker preset="custom" type="pattern" url="./332A.patt" id="332-A" registerevents>
</a-marker>

Am I doing something wrong or is just that custom markers are not supported on your branch?

Hey, there is an ongoing effort to sync this branch with the latest dev at: https://github.com/nikolaymihaylov/AR.js/pull/1 Thanks @MaesterChestnut for the effort!
We have an issue with it though. If someone has time to take a look, your help is appreciated!

+1 on this :-)

@nikolaymihaylov can you please resolve conflicts first?

@nikolaymihaylov the PR I have to your branch (which does not have these merge conflicts) now works as expected. If you merge my PR to your branch, this PR should be ready for merging

@MaesterChestnut and @nikolaymihaylov this is a big feature in my opinion. What needs to be done to make this ready to merge?

it solves https://github.com/jeromeetienne/AR.js/issues/217

@nikolaymihaylov please my PR into yours or else I'll need to open a separate PR for this feature

The branch in this pull request is now brought up-to-date. Thanks again @MaesterChestnut for your effort in the pull request https://github.com/nikolaymihaylov/AR.js/pull/1
I have now excluded the build files from the pull request, which will hopefully make this easier to merge. That means that for anyone using my latest dev branch, you'll need to run the make minify as described in https://github.com/jeromeetienne/AR.js#how-to-release- .
If anyone has based their applications on this pull request, you can still use the tag 1.5.2 that I had created, as described in https://github.com/jeromeetienne/AR.js/pull/303#issuecomment-384413920, which has the old build files. That is, of course, not recommended, since the code is outdated by now.

I hope this branch be merged. But while it is not a short solution is:
At your HTML:
<a-marker preset='hiro' id="amarker" ref="amarker">
Create a method to verify the marker state:
verifyMarker() {
    //var amarker = this.$refs.amarker; // vuejs
    var amarker = document.querySelector("#amarker")
    if(amarker.object3D.visible == true) {
        console.log('marker is visible');
    }
    else {
        console.log('marker is lost');
    }
}

At some point start your verification:
setInterval(this.verifyMarker, 1000); // 1000 means 1 second

Any plans to test and merge this pull request? It seems pretty robust and it'll do wonders for making AR.js more useful.

HI @nikolaymihaylov, I will test it myself. I only ask you if you can give me a builded version of your AR.js so I can directly import it on my example and test it. Something like:    <script src="https://jeromeetienne.github.io/AR.js/aframe/build/aframe-ar.js"></script> will be great :) Thanks a lot


Make timeout before next run of a change configurable

Apply 10 seconds timeout for RollingRestartChange as the default 0.5 seconds
is way too often for the operation of this change.
Internal ticket: 789
Review

[ ] Tests
[ ] Documentation
[ ] CHANGELOG

:+1:

:+1:


POR in OraklNode codebase

Description
test files included yet not in github action
Works same as js POR.

fetches price from data provider
read last info from the contract (last submitted value, last submitted time)
checks if should be reported
if should be reported, read roundId from the contract
report with current value and roundId

To be noticed

Reports to currently existing por aggregator contract based on orakl-config aggregator json file
Should have por environment variables set to run

Other updates

separated few fetcher functions to be referenced from por application
added ChainHelper.PublicAddress() function which returns public address of submitter

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

Deployment

[ ] Should publish npm package
[ ] Should publish Docker image

@coderabbitai review


Toolbar needs an accessible name

<Toolbar aria-label="Default" {...props}>

Closing as this one is already done


MarqoVectorStoreDriver.query vector

Currently, MarqoVectorStoreDriver.query always returns an empty list as a vector value. That behavior should be conditional based on the value of include_vectors. @RaynorChavez, how hard would it be to add that functionality?

Hi @vasinov, thanks for bringing that up! Fixed it with PR: https://github.com/griptape-ai/griptape/pull/108

Thanks!


fix: make fetch atomic

We fetch into a temp directory now and then fs.rename() into the target dir.
With fs.rename() being an atomic operation we don't leave target dir in an
inconsistent state if failure happen in some parallel installation process.
Supersedes #549
Fixes #547

Also I fixed the test written for this use case. I'll add the fix to this PR

I like this solution more and more. It is such a simple and clever solution. Probably all the directory manipulations should be done this way. Especially this one, which can potentially leave a broken hardlinked package on a fatal crash

@zkochan yes, ideally all code which manipulates store should be written that way.

Also I fixed the test written for this use case. I'll add the fix to this PR

Thanks!

Unfortunately that test was working only with the old solution, so I just removed it

Awesome! Thanks!


Allow to change engraving options

Currently, engraving options are constant values coded using
 #define OPTION VALUE

Need to create a storage class to manage rendering options:

User should be able to change all engraving options/default values
Also, read some engraving options from json file associated to SMuFL music font

Closing. Time ago I used issues to track my TODO list. This is no longer the case and so I prefer to remove old issues I created.


"Use" Should perform some checks to be sure it doesn't overwrite any files in the current directory

It might also be worthwhile to add an optional parameter to rename the thing that gets copied. (Should probably happen after #8 is fixed)

This is actually a bug right now. The program crashes if you try to use a template that contains a folder that shares the name of a folder in the current directory.


Question regarding the Python random seed & achieving replicable results

Hey there! 👋
I'm seeking some help to better understand how the custom Python random seed impacts the replicability of the results.
Currently this project is using a seed value of 20.
However, I've noticed that when evaluating a group of 10 images, the most aesthetically pleasing image changes depending on the seed value used. I find this somewhat confusing, as I expected the "best" image in the group to remain consistent regardless of the Python random seed value.
I'd appreciate any insights or advice you can provide to help clarify this issue.
Is there a special reason why 20 is used here - does this value produces the best results overall?
Thank you for your assistance! ❤🖖

Thank you for using our models.
The effect of different seeds on the results may be caused by the following reasons: In order to adapt to the pre-trained weights, our model can only process 224-sized images. Therefore, when infererence a picture, it is necessary to randomly crop the area of the picture 20 times, so that it can cover the whole picture as much as possible. Different random seeds may result in different areas to be cropped.
You can increase the number of crops to achieve a stable effect.

Thank you for the prompt & insightful response!
Upon increasing the number of crops as you suggested, I observed more consistent results.
Nonetheless, I noticed some variability when evaluating a group of three images (A, B, C), with B being my preferred image. While most seeds tend to favor image B, there are instances where the scores differ, occasionally by a substantial margin.
This leads me back to my original inquiry about the choice of random seed setup_seed(20). Have you found this particular seed value to yield better results compared to other seeds? Is the selection of seed 20 related to the initial 20 crops of 224x224 employed in the model, or is it merely coincidental?
Additionally, I have a question regarding the scale of 0.8. Could you please provide more information on why this value was chosen? As I understand it, this downscales the cropped patch during the evaluation process?
Your code implementation has been an excellent learning resource!
Thank you once more for your exceptional work and prompt help.

Thank you for the prompt & insightful response!
After increasing the number of crops (to 1000) as per your suggestion, I did observe more consistent results. However, some variability still persists when evaluating a group of three images (A, B, C), with B as my preferred choice. While the majority of seeds seem to favor image B, there are instances where the scores diverge, at times by a notable margin.
This leads me back to my original inquiry about the choice of random seed setup_seed(20). Have you found this particular seed value to yield better results compared to other seeds? Is the selection of seed 20 related to the initial 20 crops of 224x224 employed in the model, or is it merely coincidental?
Additionally, I have a question regarding the scale of 0.8. Could you please provide more information on why this value was chosen? As I understand it, this downscales the cropped patch during the evaluation process?
Your code implementation has been an excellent learning resource! Thank you once more for your exceptional work and prompt help.

The seed 20 is actually coincidental.

Thank you for the prompt & insightful response!
After increasing the number of crops (to 1000) as per your suggestion, I did observe more consistent results. However, some variability still persists when evaluating a group of three images (A, B, C), with B as my preferred choice. While the majority of seeds seem to favor image B, there are instances where the scores diverge, at times by a notable margin.
This leads me back to my original inquiry about the choice of random seed setup_seed(20). Have you found this particular seed value to yield better results compared to other seeds? Is the selection of seed 20 related to the initial 20 crops of 224x224 employed in the model, or is it merely coincidental?
Additionally, I have a question regarding the scale of 0.8. Could you please provide more information on why this value was chosen? As I understand it, this downscales the cropped patch during the evaluation process?
Your code implementation has been an excellent learning resource! Thank you once more for your exceptional work and prompt help.

Thanks for your attention to our work!
Seed 20 is actually coincidental! We didn't try other seed in our model.
When we train our model, we found that the scale of 0.8 reach the best results. So, this hyper-parameter is set to 0.8.


Bug: Change Storage Account for VHD Scanning

What type of PR is this? Changes the storage account used for vhd scanning so that it uses an account without a lock

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2627

Relevant Lines:
3458

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2627

Relevant Lines:
3458

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2627

Relevant Lines:
3458

💛  - Coveralls


Use Postgres as the database

While the plan had always been to use
Postgres as the database, the goal was to
introduce it as late as possible to keep the developer experience as
simple as possible for as long as possible. Unfortunately the migration
tests in #13 are failing because the database doesn't persist across
commands in the tox environments.
Rather than spending time making changes to the tox environments just to
try to stick to in-memory SQLite for a little
longer, this will move the project over to Postgres right now. The
check-migrations environment is being merged with the
test-migrations environment to simplify managing them. They're now
known as migrations.
Each tox environment that requires a database will look for a specific
environment variable that it will then pass along to the application as
DATABASE_URI.

@jonafato I'd like to get your thoughts on this approach. It makes local testing harder, but using separate environment variables would allow someone to export each into their session without having to juggle between them.

We use tox-docker in other projects to make testing during development easier. It may be worth using here as well if you'd like to avoid the explicit need to run a postgres server in a dev environment.

I considered this. I decided not to go that route because it forces people to have Docker installed and running whereas the current approach requires access to Postgres, either in Docker, locally, or remotely. Plus GitHub Actions seems to handle Postgres nicely, so CI doesn't need to explicitly wait for it to be ready.

Providing default values for the additional database settings would also make for a (marginally) smaller setup process. In other projects, I've done things like append -test to the existing database URI. Given that this is a small project, it's not likely worth a lot of time, but reducing the number of things that a first time contributor needs to do to start contributing while also reducing the number of settings that need to be managed in unison can be nice.

This is another thing I went back and forth on. It's a fairly lightweight change to make if it's tripping people up. I suspect most people will rely on CI for tests though.


Improve performance and size of event listener handling

Pull Request Test Coverage Report for Build 839f049a0a5530b59736db66e6a3e6ae3987dbfc-PR-4

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-2.3%) to 96.466%

Files with Coverage Reduction
New Missed Lines
%

src/diff/index.js
1
93.39%

src/diff/props.js
1
86.27%

src/create-element.js
2
83.87%

Totals

Change from base Build 967c2c0ee2b9b4041976f784c8a9379c73858011:
-2.3%

Covered Lines:
522

Relevant Lines:
528

💛  - Coveralls


Fixed package.json so it works with tree-sitter CLI

Current package.json doesn't have the tree sitter object. This means when it is used with tree-sitter CLI, tree-sitter CLI doesn't understand that kt is the Kotlin file extension, and doesn't find a parser.
The patch adds the object and specifies the kt file extension.

Moved to #88.


Hooks can only be called inside the body of a function component. (https://fb.me/react-invalid-hook-call)

Introducing ' observer ' to the component results in triggering of the above error.
here is my code  :
import React from 'react'
import { Form } from 'semantic-ui-react'
import {inject , observer} from 'mobx-react'

const Login = observer((props) => {

    const [username, setUsername] = React.useState(``)
    const [password, setPassword] = React.useState(``)

    const  handleSubmit = async () => {

        try {

            fetch('api/cockpit/authUser?token=xxxxx', {
            method: 'post',
            headers: { 'Content-Type': 'application/json' },
            body: JSON.stringify({
                user: username,
                password
            })
        })
        .then(user => user.json())
        .then(user => {
            console.log(user.active)
            props.store.loggedMsg = user.active
        })

        } catch (error) {
            props.store.loggedMsg = error
        }
    }

    return (
        <>
            <Form onSubmit={handleSubmit}>
                <Form.Group>
                    <Form.Input placeholder='Username' value={username} onChange={(e) => setUsername(e.target.value)} />
                    <Form.Input
                        placeholder='Password'
                        type='password'
                        value={password}
                        onChange={(e) => setPassword(e.target.value)}
                    />
                    <Form.Button content='Submit' />
                </Form.Group>
            </Form>
           { console.log(props.store.loggedMsg)}
        </>
    )

})

export default inject('store') (Login)

Do I have to resort to mobx-light ?

You either can wait for MobX v6 (#644) or use mobx-react-lite for components using hooks.

...Or use <Observer> sections instead of the observer wrapper for
function components
On Mon, Mar 11, 2019 at 11:48 AM Hypothesis<EMAIL_ADDRESS>wrote:

Closed #656 https://github.com/mobxjs/mobx-react/issues/656.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/656#event-2193511856, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABvGhONR1QKUiCrqN1vzktB0UW-p3MTnks5vVjSJgaJpZM4bnZMB
.

I'm using mobx-react-lite 1.4.0 alongside mobx-react 5.4.3. I normally don't see this error until I'm using React chrome dev tools to inspect the tree. To be more specific, it only happens once I actually click on the the main component that wraps the function component using state. The function components inside the main "container" component are using useContext hook and a few useState hooks that were already in there; they're wrapped in observer function imported from mobx-react-lite and the main components isn't. I can still develop and have it working but due to the above I can't really inspect or debug which can be a total nightmare when building complex UIs. Has this behavior been observed by anyone else?

I suggest upgrading to mobx-react@6.
Op ma 17 jun. 2019 21:16 schreef Imran Ali Zaidi<EMAIL_ADDRESS>
I'm using mobx-react-lite 1.4.0 alongside mobx-react 5.4.3. I normally
don't see this error until I'm using React chrome dev tools to inspect the
tree. To be more specific, it only happens once I actually click on the the
main component that wraps the function component using state. The function
components inside the main "container" component are using useContext hook
and a few useState hooks that were already in there; they're wrapped in
observer function imported from mobx-react-lite and the main components
isn't. I can still develop and have it working but due to the above I can't
really inspect or debug which can be a total nightmare when building
complex UIs. Has this behavior been observed by anyone else?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/656?email_source=notifications&email_token=AAN4NBGAWJP5SXHKLP4KFA3P27PIFA5CNFSM4G45SMA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX4FQ5Y#issuecomment-502814839,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAN4NBEQAZ7BKI4AUU4JIM3P27PIFANCNFSM4G45SMAQ
.

I would like to migrate completely but there's still plenty of class components in the code base using decorators. My understanding is decorators are not part of mobx-react-lite and I inferred since they're not there they aren't in mobx-react 6 either?

@imranzaidi If you use mobx-react@6 you will still have inject/observer available and mobx-react-lite will be automatically used for your refactored functional components.

@FredyC Ah gotcha, thanks!


Minor typo in non_chrome_process_accessing_chrome_default_dir.yml - s/firefox/chrome

Details
It looks like some copy/paste happened there. Offering a PR to get rid of it.
Checklist
Not relevant - no deep modificaitons

[ ] Validate name matches <platform>_<mitre att&ck technique>_<short description> nomenclature
[ ] CI/CD jobs passed ✔
[ ] Validated SPL logic.
[ ] Validated tags, description, and how to implement.
[ ] Verified references match analytic.

Thank you!


Response Option Group

There seems to be no info on what the "Response Option Group" (on table Workflow Response, 1521) is for. It is used above, but no explanation for it. Please provide this.

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

ID: fd5146d7-ecb6-2a30-8343-20720d68af62
Version Independent ID: d4b1eb4c-971d-9ba5-4d69-41e128773323
Content: Walkthrough: Implementing New Workflow Events and Responses - Dynamics NAV
Content Source: dynamics-nav/Walkthrough--Implementing-New-Workflow-Events-and-Responses.md
Product: dynamics-nav-2018
GitHub Login: @jswymer

Statical Prism shows the following usage:
Object	Context	Code
**Table 1523** Workflow Step Argument	Field Response Option Group	CalcFormula=Lookup("Workflow Response"."Response Option Group" WHERE (Function Name=FIELD(Response Function Name)));
**Table 1531** Workflow Step Argument Archive	Field Response Option Group	CalcFormula=Lookup("Workflow Response"."Response Option Group" WHERE (Function Name=FIELD(Response Function Name)));
**Codeunit 1521** Workflow Response Handling	Procedure AddResponseToLibrary	WorkflowResponse."Response Option Group" := ResponseOptionGroup;

This does not look very important, 2 FlowFields and an assigment. Makes it even more mysterious. So, what's this field about?


fix(@angular/cli): remove unnecessary promise around "open"

Closes #19915

@googlebot I signed it!


question: Specify size of malloc arena

I am using the Up Squared board with the following settings:
CONFIG_CPLUSPLUS=y
CONFIG_NEWLIB_LIBC=y
CONFIG_LIB_CPLUSPLUS=y

For k_malloc I can specify the memory size using:
CONFIG_HEAP_MEM_POOL_SIZE=207872000

However, I did not find a way to do the same for malloc.
CONFIG_MINIMAL_LIBC_MALLOC_ARENA_SIZE=207872000

works only when MINIMAL_LIBC is used. With no settings, I can only allocate 1mb of memory using malloc.
Is there a different config setting I have to use in my case?

That should be CONFIG_NEWLIB_LIBC_MAX_MAPPED_REGION_SIZE.

Thanks, that's the setting I was searching.


Configuration

The old version of neXtSIM was configured using one or more configuration files, as well as command line configuration.
The new version neXtSIM_DG should also be configured in the same way. However, this should be done a cleaner, more modular manner. I have created an experimental repository on my github, which can be ported across, although without the humorous names.
The experimental repository contains code providing the following features:

Configuration from multiple files (specified on the commando line).
Overriding the config file values by specifying values on the command line.
Splitting up the option descriptions so that they can be defined in (or near to) the class that they will configure.
By providing a usable base class, objects can even be configured automatically.

It has one downside: all of the configuration files must be reopened and reread once per object being configured.

Merged.


Make a PR template

I am a GSSoC23 contributor.
Kindly assign me this issue.
@cleveranu @Shreyaar12

I am already working on this. Please assign me this issue, so that I can create a PR asap.

@artimanputra can you please assign me this issue.


Doc: Renamed sections

Codecov Report

Merging #1047 (90996ed) into main (70585bd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1047   +/-   ##
=======================================
  Coverage   56.92%   56.92%
=======================================
  Files          73       73
  Lines        2259     2259
  Branches       66       66
=======================================
  Hits         1286     1286
  Misses        973      973

Continue to review full report at Codecov.

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


Add redirect fields, canonical endpoint field, and rework HTTP probing logic

This does a few things:

Adds some fields describing the nature of the immediate and eventual redirects: whether the redirects go to an https:// URI, whether it goes to a www subdomain, whether the redirect leaves the hostname, and whether the redirect leaves the hostname's parent (registerable) domain.
Adds a Canonical URL field to the CSV and JSON output, that is determined using a port of the logic from site-inspector. This makes use of the extra redirect fields mentioned above.
Changes the way that HTTP/HTTPS endpoints are inspected, by first hitting each endpoint with following redirects disabled. If a redirect is detected, the endpoint is pinged again with following redirects enabled, and then information about the eventual redirect is parsed. This creates some additional requests compared to the previous method, but greatly simplifies the logic, and allows the exception handling to be limited more tightly.
 If it then works, the TLS error is overlooked and the endpoint's behavior is processed and analyzed. If it still doesn't work, then it's assumed to be a protocol error or some other novel issue that is preventing the connection from being established, and the endpoint is labeled not live.
When redirects are followed, they are followed with certificate validation turned off. This greatly reduces the risk of having a certificate error get thrown when following redirects starting from an http: endpoint. Detecting a certificate error there during that process isn't of any real value to us, as all we care about is the eventual redirect destination URI.
This refactoring to HTTP probing logic also removes the generic except: that was swallowing all errors (even Ctrl-C interrupts).
Unfortunately, I had to disable requests caching (the --cache option now does nothing) because of a bug in how requests-cache handles redirects and the follow_redirects and verify parameters. I've filed this bug here: https://github.com/reclosedev/requests-cache/issues/70 To re-enable caching, we'll either need to fix the bug in requests-cache, or route around it somehow by using another method of writing our own caching layer.

:guitar: Most excellent!


Feature Request: a command to add an existing version to goenv (instead of installing it)

Jenv has an option to add an already-installed Java version to its list of known installed versions.
That would also be useful in goenv, and would allow us to bypass issue https://github.com/syndbg/goenv/issues/106.

@hmijail the issue is that certain architectures are not supported in older releases of go, and would require to be built from source.
That being said, this is "fixed" with a current workaround to display an architecture isnt supported. Automation is currently grabbing new versions of golang for us, so we dont need to rely on users creating PRs


Preview pane not working in Files (Preview)

Description
Preview pane doesn't show the file preview, just the rotating loading circle. Tried with jpg, pdf, txt.
Steps To Reproduce
No response
Expected behavior
Preview pane should show the file contents.
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22000.856
Windows Version
Windows 11 Pro Version	21H2 OS build	22000.856 Windows Feature Experience Pack 1000.22000.856.0
Relevant Assets/Logs
debug.log
debug_fulltrust.log

Merging with #9780


Unique component key for dynamic rendering

In track.jsx, getKey(), added : child.key + fallbackKey;

@piq9117  I think, it is not a good idea to use index as key. It is better to generate unique key with uuid or some other method and pass unique keys  to the slides

I don't see any benefit in adding index to the key already passed to slide.

Warning: flattenChildren(...): Encountered two children with the same key, `cloned0`. Child keys must be unique; when two children share a key, only the first child will be used.
    in div (created by Track)
    in Track (created by InnerSlider)
    in div (created by InnerSlider)
    in div (created by InnerSlider)
    in InnerSlider (created by Slider)
    in Slider (created by SliderWindow)
    in div (created by SliderWindow)
    in SliderWindow (created by CreateReport)
    in div (created by CreateReport)
    in CreateReport
    in main (created by MainLayout)
    in div (created by MainLayout)
    in MainLayout (created by Wrapper)
    in div (created by Wrapper)
    in Wrapper

Thank you for the review. I get this error when I dynamically add elements to the slider. What is the solution for this problem?

Can you give a code snippet to replicate this issue ?

export default class SliderWindow extends Component {
    render () {
        const {photos} = this.props;
        const settings = {
            dots: true,
            infinite: true,
            speed: 500,
            slidesToShow: 1,
            slidesToScroll: 1
        }
        const images = _.map(photos, (p, i) =>
            // pretty much just gets the src from the parent

        );
        return (

                <Slider {...settings}>
                    {images}
                </Slider>

        );
    }
}

This is my child component where the Slider resides.

I tried this  https://jsfiddle.net/20bumb4g/898/
couldn't replicate your issue.
Can you replicate your issue with above jsfiddle and give me a link to debug

Somehow this works perfectly fine https://jsfiddle.net/Piq9117/gon6295z/10/
but it always shows an error in our app, maybe it's something else. Thank you for catering to my concerns. I'll get back to you once I get to the root of this problem. Again, thank you.

It seems that on the fiddle it works as it is production and therefore not throwing dev issues, i believe. I have tried this as well and am having the same issue.
What I believe is happening is  that a key from slick-slider is being set to the dynamically created key, when it already has one, therefore causing issues. I could be wrong.
here is my snippet. I'm doing it a bit different, same issue.
`
var SDCWidget = React.createClass({
render: function sdc_widget() {
var settings = {
dots          : true,
infinite      : true,
speed         : 500,
slidesToShow  : 4,
slidesToScroll: 1,
buttons       : true,
};
	var slides = data.slides.map(function (slideNode, index) {
		return (

				<Slide slide_info={slideNode} key={index} />

		)
	});

	return (

			<ModuleTitle module_title={data.module_title} />

				<Slider {...settings}>
					{slides}
				</Slider>

	);
}

});
if (document.getElementById('sdc_widget')) {
var data = {
type        : 'sdc_widget',
module_title: 'Most Popular',
slides      : [
{
id  : 1,
img : 'http://placekitten.com/g/300/200',
desc: 'Cat does not know react'
},
{
id  : 2,
img : 'http://placekitten.com/g/300/300',
desc: 'This Cat Knows React'
}
]
};
ReactDOM.render(
	<SDCWidget data={data} />,
	document.getElementById('sdc_widget')
);

}
`

#398 fixes this issue

0.12.3 fixed the issue for me.

Can confirm that upgrading to 0.12.3 fixed for me as well.


when I predict the model, how to change test.py? not need ys

normally just give the decoder_input a start flag

How to build the predict graph? Trouble to understand loading the trained viarbles to decode,because the decode variables in a for loop.Thanks!


License file not found

I was trying to run the example/main.py but came across this error. How can I fix it?
UserWarning: conda builds of osqp are built on shared libraries; by the design of osqp, these have a different Application Binary Interface (ABI) than those required for codegen, and this is therefore not supported.   warn( Traceback (most recent call last):   File "/vol/datastore/zhenyu/opt/cvxpygen/examples/main.py", line 31, in <module>     cpg.generate_code(problem, code_dir='nonneg_LS')   File "/home/zhenyu/miniconda3/lib/python3.10/site-packages/cvxpygen/cpg.py", line 78, in generate_code     solver_interface.generate_code(code_dir, solver_code_dir, cvxpygen_directory, parameter_canon)   File "/home/zhenyu/miniconda3/lib/python3.10/site-packages/cvxpygen/solvers.py", line 305, in generate_code     shutil.copyfile(os.path.join(cvxpygen_directory, 'solvers', 'osqp-python', 'LICENSE'),   File "/home/zhenyu/miniconda3/lib/python3.10/shutil.py", line 256, in copyfile     with open(dst, 'wb') as fdst: FileNotFoundError: [Errno 2] No such file or directory: 'nonneg_LS/c/solver_code/LICENSE'

This is related to your osqp installation. Please use a pip build of osqp for now: pip install osqp

I have already installed the OSQP. And this problem still happened even I used another solver.


Add  Hofierka 2002 model

This model is currently being used by PVGIS but is not available through pvlib at the moment.

I think the full reference is Jaroslav Hofierka, Marcel Suri, The solar radiation model for Open source GIS: Implementation and applications.  Proceedings of the Open source GIS - GRASS users conference, 2002.
Available here: https://www.researchgate.net/publication/2539232_The_solar_radiation_model_for_Open_source_GIS_Implementation_and_applications

Most of the modeling steps described in this publication are no longer being used by PVGIS as they get GHI/DNI from external sources (satellite derived).
I think the really only useful step to add to pvlib in order to be able to replicate pvgis is the Muneer transposition model:
Muneer, T., 1990, Solar radiation model for Europe. Building services engineering research and technology, 11: 153-163.


Windows + Android error

Hi guys, have been trying to get a simple demo setup locally and keep running into the same issue. I'm using Windows, testing on android device + emulator and have tried using Expo development build as well as just RN.
The error is Invariant Violation: TurboModuleRegistry.getEnforcing(...): 'RNRapidsnark' could not be found. Verify that a module by this name is registered in the native binary.

Hi!
Please consider using branch release/0.0.1-alpha.6
I'm currently looking into this issue and trying to reproduce.
I'll push additional expo example once I'll get success scenario.

I've added working example for Expo in separate branch - expo_example.
You can find subfolder expo_example.
Works for both Android and iOS.

Tried a fresh setup using release/0.0.1-alpha.6 branch and the same error is being triggered, maybe a Windows issue. This is true for a new expo build and also the original example in the repo.
Few things I'm having to do after first build fails (and android folder is generated) that could offer some clues:

Adjusting minSdk version from 23 to 24 in build.gradle
Setting newArchEnabled=true in gradle.properties

Also just curious about the expo_example you included, it looks like a submodule but only seeing a commit hash included. Sorry if I'm missing something basic.

Added you to a repo showing the full installation and setup in case that helps

By reviewing your example I can say two things:

Example app fails with or without react-native-rapidsnark. I've created a branch that demonstrates that.
Please drop Expo Go - it doesn't support lot of things like linking native modules. Please use pure Expo (development builds instead of hot reload) or pure React Native.

Apologies, the file references were just fixed.
Have been using Expo development builds, building locally and tried EAS.


feat: extract model to separate classes

This PR is a simple extraction of existing classes that were sitting in one giant file. It prepares for greater changes to the messages / model.

Coverage decreased (-0.5%) to 75.871% when pulling ba5e9e09782b7384b0c164192866f66e625421ae on feature/extract-model into 3aec154239e1ffa79006640f36d9b3f743acff09 on dev.


NTR: Frizzled Nuclear Import pathway

Please provide as much information as you can:

Suggested term label:

Frizzled Nuclear Import pathway

Definition (free text)
The series of molecular signals initiated by binding of a Wnt protein to a frizzled family receptor on the surface of the target cell, followed by internalization and cleavage of the frizzled receptor to yeild a C-terminal fragment that is imported into the nucleus. The frizzled C-terminal fragment is incorporated into  large ribonucleoprotein particles and stimulates their egress via nuclear budding.

Reference, in format PMID:#######
PMID:22579286
PMID:22510459

Parent term(s)

GO:0035567 	non-canonical Wnt signaling pathway

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?

Plus new regulation terms:
-regulation of Frizzled Nuclear Import pathway
--positive regulation of Frizzled Nuclear Import pathway
--negative regulation of Frizzled Nuclear Import pathway

Synonyms (please specify, EXACT, BROAD, NARROW or RELATED)

FNI (EXACT)
Frizzled Nuclear Import Wnt Pathway (EXACT)

Cross-references

For enzymes, please provide RHEA and/or EC numbers.

Can also provide MetaCyc, KEGG, Wikipedia, and other links.

Any other information

+[Term]
+id: GO:0140709
+name: Frizzled Nuclear Import pathway
+namespace: biological_process
+def: "The series of molecular signals initiated by binding of a Wnt protein to a frizzled family receptor on the surface of the target cell, followed by internalization and cleavage of the frizzled receptor to yeild a C-terminal fragment that is imported into the nucleus. The frizzled C-terminal fragment is incorporated into large ribonucleoprotein particles and stimulates their egress via nuclear budding." [PMID:22510459, PMID:22579286]
+synonym: "FNI" BROAD []
+synonym: "Frizzled Nuclear Import Wnt Pathway" EXACT []
+is_a: GO:0035567 ! non-canonical Wnt signaling pathway
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/21483 xsd:anyURI
+created_by: pg
+creation_date: 2021-09-08T09:11:25Z
+
+[Term]
+id: GO:0140710
+name: regulation of Frizzled Nuclear Import pathway
+namespace: biological_process
+def: "Any process that modulates the frequency, rate or extent of a Frizzled Nuclear Import pathway." [PMID:22510459, PMID:22579286]
+synonym: "regulation of FNI" BROAD []
+synonym: "regulation of Frizzled Nuclear Import Wnt Pathway" EXACT []
+intersection_of: GO:0065007 ! biological regulation
+intersection_of: regulates GO:0140709 ! Frizzled Nuclear Import pathway
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/21483 xsd:anyURI
+created_by: pg
+creation_date: 2021-09-08T09:14:01Z
+
+[Term]
+id: GO:0140711
+name: positive regulation of Frizzled Nuclear Import pathway
+namespace: biological_process
+def: "Any process that activates or increases the frequency, rate or extent of a Frizzled Nuclear Import pathway." [PMID:22510459, PMID:22579286]
+synonym: "positive regulation of FNI" BROAD []
+synonym: "positive regulation of Frizzled Nuclear Import Wnt Pathway" EXACT []
+intersection_of: GO:0065007 ! biological regulation
+intersection_of: positively_regulates GO:0140709 ! Frizzled Nuclear Import pathway
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/21483 xsd:anyURI
+created_by: pg
+creation_date: 2021-09-08T09:17:38Z
+
+[Term]
+id: GO:0140712
+name: negative regulation of Frizzled Nuclear Import pathway
+namespace: biological_process
+def: "Any process that stops, prevents, or reduces the frequency, rate or extent of a Frizzled Nuclear Import pathway." [PMID:22510459, PMID:22579286]
+synonym: "negative regulation of FNI" BROAD []
+synonym: "negative regulation of Frizzled Nuclear Import Wnt Pathway" EXACT []
+intersection_of: GO:0065007 ! biological regulation
+intersection_of: negatively_regulates GO:0140709 ! Frizzled Nuclear Import pathway
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/21483 xsd:anyURI
+created_by: pg
+creation_date: 2021-09-08T09:18:32Z

Thanks!


Add DockerHost class

This moves this class https://github.com/spotify/helios/blob/master/helios-testing/src/main/java/com/spotify/helios/testing/DockerHost.java#L18 and this class https://github.com/spotify/helios/blob/master/helios-services/src/main/java/com/spotify/helios/servicescommon/DockerHost.java#L29 from Helios to docker-client.

@mattnworb @gimaker @rohansingh

lgtm

Tests passed but I canceled because I used rebuild with ssh.


Support PostgreSQL realtime data synchronize

Support this feature by PostgreSQL logical replication(test_decoding plugin).
Reference #3598

Hi @avalon566 , do we decide to use test_decoding? not wal2json?

We implement this by test_decoding first, and then use wal2json if don't meet the requirements.


Trigger event after all events run.

Create a new event trigger that will run after all events run. If it's not possible, can trigger event after 10ms without events, for instance. If I do unlink after 10ms it'll trigger done, for instance. If I remove 1000 files without create this gap, done not will be trigged, but after 10ms after the last event, it'll be triggered.
Real case: for instance, if I watch .less files, and I have a folder with it and I remove it, it'll trigger unlink for each file first, and lastly unlinkDir. But if I do it with a lot dir on same time, it'll mix events between unlink and unlinkDir. And I like run a code after all events (rebuild my index, from my code, and I need that no events is running).

I don't see how this is something chokidar ought to provide. You're just asking for a timer to fire when there haven't been events in a little while, which you can easily implement yourself.
What meaning does it have anyway? Who's to say that right after the event you're asking for is fired, 11ms after the prior event, another legit change event won't happen?
If chokidar's events trigger a long-running process in your implementation, you should have events that occur during that processing just flip a dirty bit so your process can know it has to run again after the prior cycle is done.


Rework MediaListUI

ToDo

[ ] Use selected AudioFileCover as Background but blurry
[ ] Orientate on Groovy or Spotify for the list styling
[ ] add a bit more meta data

Maybe look into something like so: https://gist.github.com/superic/8165746
Hopefully support for similar arrives in Avalonia sooner or later!


Unclear how to change colors of time picker(showTimePicker)

At the moment it is very unclear how to change the colors of showTimePicker, e.g. the red handle color. Don't find answers even on google. Suggesting to document it more clearly or add appropriate arguments to showTimePicker for management of its colors.

gintas-mac:domukpizzaapp gintas$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.18.0-10.0.pre, on Mac OS X 10.15.4 19E287, locale en-GB)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.6)
[!] VS Code (version 1.43.2)
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (3 available)

! Doctor found issues in 1 category.
gintas-mac:domukpizzaapp gintas$

CC @rami-a @darrenaustin

Hi @Gintasz I'm currently working on a revamp of TimePicker to support better theming but it's still a WIP (hope to have it ready in the coming weeks). Currently, the picker gets the red color from your ThemeData.accentColor, so customizing that would change this. Hope this helps

Hello @Gintasz, I just submitted #59191 that adds a time picker theme that allows you to customize the various colors, closing this now :)

@rami-a How does one change the button ('Cancel', 'OK') colours?

Hello @DriftingShadows, the time picker uses the new TextButtons as of https://github.com/flutter/flutter/pull/61492 and the easiest way to change the color of those buttons is to specify a textButtonTheme on your ThemeData. Hope that helps.

Hello @DriftingShadows, the time picker uses the new TextButtons as of #61492 and the easiest way to change the color of those buttons is to specify a textButtonTheme on your ThemeData. Hope that helps.

Thanks for that. I swear I'm on the latest flutter version (v1.20). TextButton isnt a widget for me (and as such textButtonTheme isnt a thing either). Am I doing something wrong?

Ah I believe the TextButton change has not landed in stable yet, so then the TimePicker is using FlatButtons, which you can adjust the color of by using ButtonTheme. If you only want to change the TimePicker's button colors, you can use the builder param of showTimePicker and wrap the widget with a custom Theme.


How do i disable void dodge enchantment?

Hello!
Lately the mobs with void doge are annoying me when they teleport for outside of my mob farm, i opened the config folder but i cant find the enchantment void dodge or the place for disable.

enchantmentBlacklist in dungeons_gear-common.toml


Make Python3.6+ compliant

To get a wider user base and ensure we can support both Python2.7 and Python3.6+, we'll need to make some changes:

[ ] Ensure all dependencies from requirements.txt are Py3.6+ compatible
[x] Ensure all exceptions are handled correctly
[x] Handle print as print(foo) versus print foo
[x] Use fstrings  and new format method in places where it makes sense:
[ ] ...
[ ] ... ongoing as I find more requirements

new: info(f'{artifact} tags: {result}')

original: info('%s tags: %s' % (artifact, result))

new:
build_version = 'v{}.{}-{}_{}'.format(__app_major, rev_count.strip(), rev_hash.strip(), __app_stage)
app_version = 'v{}.{}_{}'.format(__app_major, rev_count.strip(), __app_stage)

old:
build_version = 'v%s.%s-%s_%s' % (__app_major, rev_count.strip(), rev_hash.strip(), __app_stage)
app_version = 'v%s.%s_%s' % (__app_major, rev_count.strip(), __app_stage)

If this issue isn't resolved, this project is dead

Hey @q2dg , I'll see if I can add py3 compatibility to this project.

Hey all,
I will happily merge any PRs for Py3 compatability and I definitely appreciate the interest in this project. Unfortunately I haven't had much time to activately maintain this- I hope this changes in the near future, but anything I can do to facilitate support here let me know

Starting on this now. I'll keep everyone updated on the status.


Networkutils rfc2732

Previously bracketed addresses provided to strToIPv6 would return null.

jenkins ok to test

That's a great example of an appropriate thing to unit-test.


Modal AutoFocus broken with React 16 because of render unstable changes

Rendering a Modal component with defaults fails in React 16 with:
Uncaught TypeError: Cannot read property 'parentNode' of undefined

The root cause is because the Modal's autoFocus is attempting to reference the this._dialog which is set via callback and does not exist as result of changes made in unstable_renderSubtreeIntoContainer.
Reference: https://github.com/facebook/react/issues/10309

Reactstrap: 4.8.0
React: 16.0.0-beta.3
Components: Modal

Steps to reproduce issue

Specify a new Modal component with no autoFocus attribute or autoFocus={true}

Demonstration
https://www.webpackbin.com/bins/-Kr2BOnFO9GcE691BLYr

Reference Notes:

AutoFocus is used to ensure that pressing the Escape key registers the event.
A separate autoFocus property was added to allow custom elements to be automatically focused on load. This conflicts directly with the keyboard property and should be resolved.

[ ] Move the escape click handling to the document element and catch via bubble. This would remove need for reference to the dialog for focusing and ensure compatibility with keyboard. It would also allow removal of autoFocus property as it's not needed.
[ ] Otherwise, fixing the timeout focus logic would work and keep both properties; however, there exists the untested case where setting keyboard = true and autoFocus = false currently does not work.

Would there be any issue moving the event listener to the document?

Multiple Modals, which bootstrap itself does not support, so we can probably drop support as well(?). The issue becomes, which Modal is being closed.
Yes, autoFocus = false does break the keyboard, but autoFocus = false was meant to allow the user to control focus himself/herself, focusing on something within the Modal which would allow esc to work. I wonder if we could determine if focus is in the Modal via document.activeElement and not auto focus the modal, thus removing the need for autoFocus prop on Modal.

Good points. Sounds like we should handle a couple other outstanding issues as well and get the Modal alll  tidied up. I've added multiple modals into the checklist above.
As far as multiple modals .... I'm not sure on the best practice. Weird things happen in different libraries (e.g. Sometimes things stack including more backdrops, others have a single persistent backdrop and single active modal)

Yeah, for multiple modals there is a ton of questions and because bootstrap doesn't support it, we cannot reference the way bootstrap does it. I am for removing multiple modals to be more inline with bootstrap itself.

Supporting a single modal is obviously easier; however, there could be valid use cases for multiple modals:
Example of the multiple modal concept:
Click the delete trashcan icon button in the main form:
http://jsfiddle.net/KyleMit/QqqxF/224/show/light/
I wouldn't mind supporting this as it wouldn't be too difficult to implement. Specifically:

Move back the escape listener to document (if keyboard = true)
Single backdrop only
Allow multiple modals. Latest modal pushes z-index above backdrop. Previous ones below.
If keyboard = true, escape closes top modal (if last modal or only 1, backdrop gets closed)

Just going to leave this here since A11y should also be included when talking about some of these changes https://github.com/davidtheclark/react-aria-modal. #310 would be nice since we are talking about focus management.
@davidtheclark did a great job making react-aria-modal and all of the smaller components/libraries it utilizes. It would be awesome to leverage those same libraries and even react-aria-modal itself (just managing/mapping props to be more inline with bootstrap). Food for thought.


Handling division by 0

Fixed issue with division by 0 (similar to v_check_wlm_query_trend_hourly.sql)

Which scenario leads to a non-zero value for total_queue_time_sum with a zero value for total_exec_time_sum?

When I run the original query on my cluster I got the following error:

An error occurred when executing the SQL command:
SELECT trunc(a.service_class_start_time) AS day,
a.service_class,
b.condition AS service_class_condition,
COUNT(a.query) AS qu...
Amazon Invalid operation: Divide by zero;
Execution time: 8.95s

I've checked the source data and saw this:
day        | service_class | service_class_condition          | total_queue_time | total_exec_time
2016-07-29 | 7	           | (user group: wlm_queue_dataload) | 180132174        | 0

I've investigated further using the following query
SELECT *
  FROM stl_wlm_query a
  JOIN stv_wlm_classification_config b
    ON a.service_class = b.action_service_class
  WHERE a.service_class = 7
  AND trunc(a.service_class_start_time) = '2016-07-29';

which returned this:
userid|xid     |task   |query  |service_class|slot_count|service_class_start_time|queue_start_time   |queue_end_time     |total_queue_time|exec_start_time    |exec_end_time      |total_exec_time|service_class_end_time|final_state|id|condition                        |action_seq|action   |action_service_class
125   |15541113|2780821|2780822|7            |1         |2016-07-29 00:07:29     |2016-07-29 00:07:29|2016-07-29 00:10:29|180132174       |2000-01-01 00:00:00|2000-01-01 00:00:00|0              |2016-07-29 00:10:29   |Completed  |7 |(user group: wlm_queue_dataload) |0         |assign#7 |7

I'm guessing there was an issue with Amazon on that day which might have caused this particular entry (quick search confirms there was an outage on around that time)

Regardless of the root cause for that particular issue, it's worth hardening this calculation - knowing that this DIV/0 is possible in rare edge cases.


paragraph block non editable in visual mode

Hey Sebastian,
When a header had been typed in raw mode followed by a paragraph of text and they are not separated by an empty line (only a line break), it's OK in markdown. They are correctly rendered in html.
But if you switch to Visual mode, it 's impossible to edit the paragraph to make a change. Both header and paragraph end up on the same block. Simply adding and empty line between them in raw mode is enough to solve this but that seems to be a bug...
Olivier

Hi Olivier,
yes, the visual markdown editor has not a super clean markdown logic, will add a fix-label, but to clean it up completely I have to analyse the whole markdown document in depth and I want to avoid it right now...

#55 with more bugs with markdown parsing.

starting with version 1.4.0 the markdown-blocks for the visual editor are detected with the parsedown-library, this should solve all issues with markdown in visual mode.

published with version 1.4.0


Remove CrosslingualTask & MultilingualTask?

https://github.com/embeddings-benchmark/mteb/blob/main/mteb/abstasks/CrosslingualTask.py & https://github.com/embeddings-benchmark/mteb/blob/main/mteb/abstasks/MultilingualTask.py are essentially the same thing and the is_crosslingual & is_multilingual attributes are only used to change the console color I think 🤔
In the spirit of reducing complexity & keeping it simple I think we can:
(a) Merge them into just MultilingualTask
(b) Remove both - I don't think we need these classes, as checking whether a task is multilingual should be as simple as len(self.metadata_dict["eval_langs"]) > 1. But maybe we don't even need that check - ideally it just works out of the box with multilingual or monolingual I think by just iterating through whatever languages are there? We have already standardized the format for that (https://github.com/embeddings-benchmark/mteb/issues/251#issuecomment-2036569253) I think 🤔
Curious if @KennethEnevoldsen has thoughts!

Yeah, I think you are right; we could just factor these out. It would require some work, though. I think it could be done in two steps. 1) replace CrossLingual with Multilingual and 2) factor Multilingual into Abstask.


Register SimpleCaching.jl

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/75250
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.1 -m "<description of version>" 213d8868267d610b86c0e2f946951d81bd424aa4
git push origin v0.2.1

Also, note the warning: This looks like a new registration that registers version 0.2.1.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.


Add ability to specify hooks-dir

Right now I have a shell script in my program that I'm using to launch a container. It works pretty well, but if I could use a rust crate instead, that'd be kinda cool.
I'm pretty sure that there's no way to specify the --hooks-dir option through this crate, and I'm wondering if such a thing could be added? Depending on my availability in the next week, I could give it a go.

https://docs.podman.io/en/latest/markdown/podman.1.html#hooks-dir-path


auto mode

HI
I need this: when turn on, need to start with auto mode  ?
how?
Thanks

HI @batmanvip123,
I didn't try it out, but you can try to call handleAutoStart() at the end of the setup() function.
Regards
Tobias

where exactly??
thanks
V V ned., 2. dec. 2018 ob 00:48 je oseba Tobias Blum <
<EMAIL_ADDRESS>napisala:

HI @batmanvip123 https://github.com/batmanvip123,
I didn't try it out, but you can try to call handleAutoStart() at the end
of the setup() function.
Regards
Tobias
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/toblum/McLighting/issues/273#issuecomment-443468339,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AoSnbduA51j61Y1QVxLDiivJnS1C3UTSks5u0xUvgaJpZM4Y86_f
.

Here: https://github.com/toblum/McLighting/blob/7a44a76aca74d8501f6018c1d9dfc28a43ae45ee/Arduino/McLighting/McLighting.ino#L897
Just try a ittle bit what works best.


Add OpenSSF Best Practices Badge

The CNCF require that we start the process of achieving a OpenSSF best practices badge.
https://bestpractices.coreinfrastructure.org/en
The tool scans a repo and provides a report of the items that are incomplete or missing.

The Java SDK recently achieved a 100%.
https://bestpractices.coreinfrastructure.org/en/projects/6241

The Java SDK recently achieved a 100%.
https://bestpractices.coreinfrastructure.org/en/projects/6241

swag

Challenge accepted.  I'll try and spend some time this week going through that list before submitting the project.  @beeme1mr  I assume we can re-submit as many times as we address issues?

PR for contributing doc: https://github.com/open-feature/go-sdk/pull/104


Drawer image not showing up

Hi guys, I wonder why my navigation bar not showing up by default? even if I put the drawer image on the scene
Version

react-native-router-flux v3.10.10
react-native v0.40.0

Expected behaviour
Drawer (burger icon) should appear on the navbar by default. And when I use the drawerImage props, it should show the icon.
Actual behaviour
Drawer Image (burger icon) doesn't appear and drawerImage props not working.
Code
const myImage= require('../assets/images/Menu 1.png');
<Scene key="main" initial>
                <Scene key="employeeList" component={EmployeeList} hideNavBar />
                <Scene
                    key="homeScreen"
                    component={HomeScreen}
                    initial
                    tabs
                    sceneStyle={{ paddingTop: 56 }}
                    drawerImage={myImage}
                />
            </Scene>

Here's the picture

It should be a router problem architecture ?
i do like this and it works, ( i'm new, not sure it's the better way)
sidebarButton   = () => (
        <TouchableHighlight onPress={() => { Actions.refresh({ key: 'drawer', open: true }); }}>
            <Image source={require('../assets/img/burger-menu.png')}/>
        </TouchableHighlight>
    );

<Scene key="drawer" component={SideBarContainer} open={false} >
    <Scene key="home" renderLeftButton={this.sidebarButton} type="replace" tabBarStyle={styles.tabBarStyle}>
        <Scene key="A"  title="a" />
        <Scene key="B"  title="b" />
    </Scene>
</Scene>

@aDEVE thanks for pointing the way out, I changed the Router to Class Based Component and then add a function like that and call it from renderLeftButton props like you did. Thanks man


Upgrade to 0.56.1(2) makes Home Assistant hang

Home Assistant release (hass --version):
0.56.1 and 0.56.2
Python release (python3 --version):
3.5.3
Component/platform:
Home Assistant on Debian 9 amd64
Description of problem:
After trying to startup with systemd after upgrading (in virtualenv), Home Assistant just hangs on these lines in log:
oct 23 20:57:18 server systemd[1]: Started Home Assistant.
oct 23 20:57:21 server hass[2268]: 2017-10-23 20:57:21 INFO (Thread-2) [homeassistant.config] Upgrading configuration directory from 0.56.0 to 0.56.2
oct 23 20:57:21 server hass[2268]: Config directory: /home/homeassistant/.homeassistant
Nothing more.
Expected:
Expected to run as normal, downgrading to 0.56.0 makes it work again with the same config.
Problem-relevant configuration.yaml entries and steps to reproduce:

?
?
?

Traceback (if applicable):

Additional info:
What debug information can I attach?

Do you have any zwave devices? Sometimes after upgrading my instance will take around 20 minutes to fully come up and display the UI.

Look like your config folder is locked

@pvizeli oh. You are really right! Thank you!) A week ago I moved Home Assistant to another machine... and yes. The problem was caused by rights.
Files .HA_VERSION, .uuid and .ios_conf had root owner.
I am fool :).


loginPopup() never returns when redirect page is on another domain

Core Library
MSAL.js (@azure/msal-browser)
Wrapper Library
Not Applicable
Public or Confidential Client?
Public
Documentation Location
docs.microsoft.com
Description
I've got a single page SPFx app which is aiming to get some api tokens to pass to another app in order to let it access the graph api.  My SPFx app calls loginPopup() and everything goes well, to the point where my redirect page (on a different domain from the SPFx app) is rendered and has a code and client_info in the url.   I've not found any authorititave docs on how this process is suppsed to be completed.  CoPilot has suggested running             msalInstance.handleRedirectPromise(window.location.href)
But with extra logging turned on i can see that i get the message<EMAIL_ADDRESS>: Info - handleRedirectPromise called but there is no interaction in progress, returning null.'
I can see that the initial call to  loginPopup() is waiting for something, and it correctly throws an error (user_cancelled) if i just close the popup, so it doesn't seem like I'm that far off where I should be.   I can't find a page or example in the documents that describes the flow for loginPopup() and I'm not sure if this is even the right approach.

This is expected behavior as per design. The redirectUri must be on the same domain as where you started the flow. The browser blocks access to the hash fragment and storage in cross-origin contexts for privacy reasons and this is a hard technical blocker even if we wanted to try to support this use case.
For SPFx apps you should be using Sharepoint's auth library instead of MSAL directly


crictl can not pull image from internal registry

Description
pull image from internal registry failed with error failed to resolve reference  ###, no scope specified for token auth challenge
i guess it due to image name itself, but the same name works with containerd 1.2.9
Steps to reproduce the issue:
1.sudo crictl pull a-b-c.eng.companyname.com/staging/ccm/manager:v1.0.0
Describe the results you received:
FATA[0000] pulling image failed: rpc error: code = Unknown desc = failed to pull and unpack image "a-b-c.eng.companyname.com/staging/ccm/manager:v1.0.0": failed to resolve reference "a-b-c.eng.companyname.com/staging/ccm/manager:v1.0.0": no scope specified for token auth challenge

Describe the results you expected:
Output of containerd --version:
containerd github.com/containerd/containerd v1.3.0 36cf5b690dcc00ff0f34ff7799209050c3d0c59a

Any other relevant information:

i believe this is the same issue with https://github.com/containerd/containerd/issues/3556


Integrate Auth with CAS

Right now we're using OSF session authentication. We should integrate with CAS. Ultimately this will be OAUTH2 and relying on #30, but we could do an intermediary step with tokens.

Notes for meeting with @icereval
Integration use cases

OSF usage in Dev
OSF usage  in staging/production
Third party usage in staging/production

@abought is working on the piece that handles third party usage. I expect we'll have our own secret keys for OSF usage in staging/production much as we do for third party addons, but Michael may suggest we do this another way. I'm not sure what's involved in handling for dev testing, so I will need to learn about that as well.
I'm also not sure if, once we merge develop in, our current cookie-based authentication breaks.
Open Questions

[ ] Does cookie based authentication break when we merge in develop
[ ] Do we just consider the OSF a standard OAUTH2 application with our own secret keys, or do we use another method
[ ] If yes above, what do devs do to generate keys on develop (just use the UI that @abought is making?)
[ ] Should we use CAS library for integration into DRF Auth or just send a request?
[ ] Should we have any non-OAUTH methods of integrating into CAS?
[ ] Does @chrisseto's fake cas work here, would it need updating, or should we always just require CAS for API work?

Fake cas should work because Waterbutler works

Probably cookie base authentication will still work, so merging with develop should result in no extra immediate work.

For OSF development, we will be using the existing "Pull data off the cookie" method. This will make the most sense and is super easy. This means that we won't need to do anything special for authentication to get internal developers to use the API. :tada:
We should use the CAS library for integrating the DRF authentication.

@abought Is there anything else needed to consider this closed above and beyond what will be done in #30?

Not at the moment, but I'd like to see the feature used a bit (say in one of our API clients) before completely closing the book.

Okay. Next time @alexschiller is around, he can try out this method instead of basic auth.

I'm going to leave this open here. If you come up with new issues, @abought, file them on the main repo. If you are happy with this, then close it.


Fixes #63 adds PresetSelection to Wizard and Configuration

Added PresetSelection to the configurationWindow and the SetupWizard.

The state in the configurationWindow does not reflect the value from the config we receive. This is most likely an issue with the component itself. haven't been able to pinpoint this yet. It does however work correctly for the Wizard.

Currently when the config window first loads, the configured Preset is not selected in the config UI
PS C:\Users\anath\redhat\tray-electron> crc config view
- network-mode                          : user
- preset                                : podman

@anjannath I mentioned this in comment https://github.com/code-ready/tray-electron/pull/111#issuecomment-1019901994
This is resolved in https://github.com/code-ready/crc-react-components/commit/38bafa7f195f802b39d90832267c40c0aa4902e3

Should work now