Multiline Input

Admittedly this is a niche case, but it would be a nice configurable feature for the plugin to count the number of opening braces/parens/brackets and continue to accept input until the count is zero for each.

There is already this kind of code in Scheme Example (only on the page not in repo). It count if parents in S-Expressions are balanced. Check code (in the source) http://terminal.jcubic.pl/examples.php#dterm, the code check if parents/brackets are ballanced if no it accept more input and concatenate it and only then execute the code.
This feature is not for the terminal but for specific implementation, terminal can only help in implement it by the client. I can only make multiline input easier.

It was not easy to find, so I'll leave here the link: https://github.com/jcubic/jquery.terminal-www/blob/a4c593e516b738d361a745a214ce852306cda9b4/examples.php.in#L2265-L2296

IMHO better multiline is Shift+Enter, I've created better parenthesis match but in single input here https://jcubic.github.io/lips/ (source: https://github.com/jcubic/lips/blob/gh-pages/index.html#L192)

But there is also an option to overwrite ENTER keymap and insert newline when parenthesis are not balanced, I'll try to create example or update my parenthesis matching.

Our case is when a backend is responsible for distinguish whether a command is incomplete. But I guess I'm able to implement it just on server side and allows a client to send incomplete commands (maybe prompting will need some tweaking).

Here is better solution, for your case:
 var term;

 $(function() {
     term = $('<div/>').attr('id', 'term')
         .appendTo('body')
         .terminal(function(command) {
            this.echo('executing ' + command);
         }, {
             name: 'portfolio',
             keymap: {
                ENTER: function(e, original) {
                    this.pause();
                    $.jrpc('service.php', 'enter', [this.get_command()],
                        (response) => {
                            console.log(response);
                            if (response.result == '__ENTER__') {
                                this.insert('\n');
                            } else if (response.result == '__EXEC__') {
                                original();
                            }
                            this.resume();
                        }
                    );
                }
            },
             prompt: 'exec> '
         });
 });

<?php

require('json-rpc.php');

if (function_exists('xdebug_disable')) {
    xdebug_disable();
}

function balance($code) {
    $pa = str_split(preg_replace("/[^()]/", "", $code));
    $i = 0;
    foreach ($pa as $p) {
        if ($p == '(') {
            $i++;
        } else if ($p == ')') {
            $i--;
        }
    }
    return $i;
}

class Service {
    function enter($code) {
        $p = balance($code);
        if ($p < 0) {
            throw new Exception("Parenthesis error");
        } else if ($p > 0) {
            return "__ENTER__";
        } else {
            return "__EXEC__";
        }
    }
}

handle_json_rpc(new Service());

?>

Instead of JSON-RPC you can use normal ajax call and inside interpreter function you can call ajax. The only limitation is that you will have two requests. If you want one you will to put your code instead of "EXEC" and return exec value if result will be ENTER you insert \n normaly but if you have different value you just echo it and call original() note this in this case your interpreter can be empty (use $.noop) it will be only use to handle displaying of prompt.


[WIP] Center the whole menu

This is a PR for playing around with centering the menu.
Introduces: g:startify_center. This option should be set to the longest line you expect in the menu. Values between 50 - 80 probably make sense. Just play around a bit.

Just fyi I've been using this branch for a while now with no problems

Nice feature. Can't wait.

I've been running this at work for a while with my colleagues.
Nothing to report, you can merge as you see fit.

How would I go about using this in my configuration to center my menu as well? So, there's this new variable, but how can I use it? I didn't find anything in :h startify mentioning this..

Was this ever merged into master?

2023
I have added the changes to the current master branch. Not working. For example, setting let g:startify_center=80 make the cursor cannot go back from a certain column, but the text remains in the same place.

The custom headers is not centered in this branch, here is my minimal lazy.nvim config that works:
return {
  "mhinz/vim-startify",
  branch = "center",
  config = function()
    vim.g.startify_center = 50

    local function get_padding()
      local padding_left = 3
      if vim.g.startify_center then
        padding_left = math.floor((vim.fn.winwidth("%") - vim.g.startify_center) / 2)
      end
      return string.rep(" ", padding_left)
    end

    vim.g.startify_lists = {
      { type = "sessions", header = { get_padding() .. "Sessions" } },
      { type = "dir", header = { get_padding() .. "Most Recently Used (MRU)" } },
      { type = "dir", header = { get_padding() .. "(MRU) " .. vim.fn.getcwd() } },
      { type = "bookmarks", header = { get_padding() .. "Bookmarks" } },
    }
  end,
}


UI freezes when the auto-completion window pops up in large file.

When I press Ctrl+Shift+G to patch instruction, an auto-completion window will pop up, and the UI will freeze for a long time.
Is there an option to close this window?

I have the same issue.

same issue

Presumably there is some long-running initialization that is happening in the UI thread.   We should be able to put this initialization into a background thread with a dialog to prevent the UI from locking.  Whether or not it can be cancelled once started is less clear.

How large is the file, and what is the processor? Looking for info to reproduce it.

How large is the file, and what is the processor? Looking for info to reproduce it.

178mb .dll file
x86 64bit
with new project just open dll without auto analyze - freeze about 10seconds
with analized - freeze about 40sec

OK. From what I can tell, this has to do with auto-completion and symbols. We don't index symbols by name in the database (at least not yet), and so I end up loading all the symbols and indexing them during auto-completion, which is on the Swing thread :/ .

OK. From what I can tell, this has to do with auto-completion and symbols. We don't index symbols by name in the database (at least not yet), and so I end up loading all the symbols and indexing them during auto-completion, which is on the Swing thread :/ .

In my case, I don't need symbols at all in the autocomplete.
It is enough to output the syntax of the assembler commands.
Can add a setting - does not display symbols.

I don't think a toggle is really necessary here. We do actually have an index on symbols names, but the SymbolTable API doesn't let us scan it. My plan is to fix that and then use it to significantly speed up the assembler's symbol search.


Monorepo support

Hello! Does it has support for a mono repo? Scanning through multiple package.json?

hi @PlayMa256 unfortunately ntl does not offer any special support to mono repo structures out of the box right now but rest assured that's something I would love to support!
Thing is I'm not a monorepo person myself and I don't have any projects in my radar using it - that said I would love to hear from the people using it what would make sense for them.
Some questions to start with:

What are the current projects/ecosystems to support/test for? (thinking lerna, etc)
How does monorepo structured projects usually structure their tasks?
Do these projects usually aliases tasks to the top level?
What features are missing in ntl to make managing monorepos easier?

Let's get this conversation started 🚀

Hello! We have few people that would be interested on it!

What are the current projects/ecosystems to support/test for? (thinking lerna, etc)
Lerna, yarn workspaces

How does monorepo structured projects usually structure their tasks?
Usually they have tasks per package and sometimes they expose those tasks on the root package.json file.

What i mean:
Given we have the package: @test/my-cli with the following commands:
{
	"scripts": {
		"runSomething": "do-it"
	}
}

This could/would be exposed on the top level scripts as (using the yarn workspaces syntax):
...
"runSomething:my-cli": "yarn workspaces @test/my-cli runSomething"
...

Do these projects usually aliases tasks to the top level?
Sometimes they do!

What features are missing in ntl to make managing monorepos easier?
The only thing could be scanning through all the package.json files available inside any folder (excluding node_modules)

Awesome, that sounds like a great start!

There is a monorepo playground we have and you could have a look as well (https://github.com/entria/entria-fullstack)

👍 this kind of reference is very useful for adding tests

That can be helpful while developing it! I'll try to find sometime to help with this!

Great to hear! Personally I don't think I'll be putting much development time into the project right now so I'll leave this one open for the community to help 😊

FYI: i created a small package which helps finding all package.json files. I'm planning to add this as a helper to this feature!
https://github.com/PlayMa256/find-all-package-files

Hej, this is a great idea.
I’d like to work on this.
Or did you already started @PlayMa256?

Just a last Question about the list behavior when finding a monorepo.
Currently we are showing tasks like this:
$ ntl
⬢  Node Task List
? Select a task to run: (Use arrow keys)
❯ tasks
  start
  test
  build
(Move up and down to reveal more choices)

Option 1
In case of a monorepo we could provide a list of sub repos first:
$ ntl
⬢  Node Task List
? Select a repo or the root tasks select a task: (Use arrow keys)
❯ Root tasks
  checkbox
  confirm
  core
  editor
(Move up and down to reveal more choices)

Not sure about the wording though. Anyway: We would present the task list after choosing one.
Option 2
In case of a monorepo we show the root tasks and sub repos in the list:
$ ntl
⬢  Node Task List
? Select a root task to run or choose a sub repo to show their tasks: (Use arrow keys)
❯ bootstrap
  test
  checkbox
  confirm
  core
  editor
(Move up and down to reveal more choices)

Where the sub repos should be formatted other than the tasks (eg. colored and bold).
Any opinions on that?

Another important thing is to think about how the monorepo feature should go along with the --rerun flag 🤔

@mischah i had just started writing down, i wrote literally 2 lines hahaha, you can go ahead and do that!
Let me contribute to the discussions
I personally think that is going to be a better UX if we can have option 2 because there are many scripts that can be run on the root as well like global lint, tests, stuff like that!
Giving a list of scripts per package is the best idea!

ok, I have given this a fair amount of thinking and I would like to avoid as much as possible writing a custom implementation for handling the monorepo discovery logic. I would much prefer reusing some already existing code from one of the big projects, such as lerna project.getPackages():
https://github.com/lerna/lerna/blob/6c4ee5294002c0e464f557b149516017eccf2a07/core/project/index.js#L169-L176
Given that workspaces are a feature in npm's radar for v7 (maybe not v7.0 but def during v7.x life) it could be a very good idea to wait for it to land there before we implement it here (then we could hook to the APIs npm natively exposes) - but as I have stated before: if someone shows up with a PR and it seems to be something the community wants, I wouldn't mind merging it 😊

Update: The RFC for npm workspaces is out: https://github.com/npm/rfcs/pull/103


Related resources are not included if relationship field is omitted using Sparse Fieldsets

JSON:API specification allows to omit a relationship field required for linkage in a compound document using sparse fieldsets:

Compound documents require “full linkage”, meaning that every included resource MUST be identified by at least one resource identifier object in the same document. These resource identifier objects could either be primary data or represent resource linkage contained within primary or included resources.
The only exception to the full linkage requirement is when relationship fields that would otherwise contain linkage data are excluded via sparse fieldsets.
https://jsonapi.org/format/#document-compound-documents

The package does not handle that edge case yet. If relationship field is omit using a sparse fieldset the related resources are not included even if include query parameter is present.
Let's assume this request successfully returns all posts together with their comments: GET /posts?include=comments

If using a sparse fieldset, which omits the comments relationship of posts, the related comments are not included. The API response with 200 OK and the posts as primary data as if include query parameter was not present. Such a request may look like this:GET /posts?include=comments&fields[posts]=title,summary&fields[comments]=title

If including the relationship field in the sparse fieldset the response is as expected. To do so the request given above must be changed like this (assuming that the relationship field of posts resource is called comments):GET /posts?include=comments&fields[posts]=title,summary,comments&fields[comments]=title

This bug violated JSON:API specification as an API must return 400 Bad Request if not being able to process requested include query parameter. It must not ignore it. See https://jsonapi.org/format/#fetching-includes for details.
To be honest I don't see much use cases for using Sparse Fieldsets like this. I was just running into the issue due to a typo. Not supporting this edge case and returning a 400 Bad Request would be fine with me.

This seems to be a problem with the underlying neomerx/json-api encoder. There's an open issue on exactly this topic:
https://github.com/neomerx/json-api/issues/249
Under the hood, the include path is not ignored - the relationship will be eager loaded on the Eloquent model. It's the encoder that's deciding not to add it to the compound document when iterating through the data.
I'm not entirely sure what to do about this as I don't want to be making extensive changes to my fork of the neomerx package. I'm still hoping that neomerx will return at some point to maintain their package.
I think maybe leaving this issue open for the moment is fine. There's an easy workaround, which is to just make sure the relationship is also listed in the sparse fieldsets (which is a more logical request anyway).


Enable unknown options for all the build and run commands

What does this PR do?
When the build command was being generated with unknown options, the sh-validate-build "hook command" was failing due to these options, so what I did was to add support for all build-related commands.
How should it be tested manually?
yarn test
# or
npm test

Pull Request Test Coverage Report for Build 105

3 of 3 (100.0%) changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 103:
0.0%

Covered Lines:
1399

Relevant Lines:
1399

💛  - Coveralls


Added capture_stats() back to UpdateLiveStats

Short Description:
Fixed issue with UpdateLiveStats showing 0 for everything
I haven't seen an issue logged for this, but people in slack chat are talking about it.

👍


Add option to specify day of month for Recurring Donations

Critical Changes
Changes
Recurring Donations Enhancement

Users now have the option to specify which day of the month NPSP uses for installments on Recurring Donations. Add the Day Of Month field to your Recurring Donations page layout and enable field visibility for your user profiles. Day of Month sets the Close Date for installment Opportunities going forward when you populate the field.

Issues Closed

Fixes #3455

New Metadata
Custom Fields:

npe03__Recurring_Donation__c.Day_Of_Month__c

Deleted Metadata

@sam-knox Can you please review the changes in the changes section. I'm guessing we'll probably need to walk them through adding the field to the layout and updating field access or point them to docs?

**lurch: attach W-026252

Tracking W-026252

@rponti-sforg Is this fully tested? If so, can you mark as Approved?


add collapsibility to gui sections

Description
At the moment the GUI of the annotater is divided into five sections (widgets):

embeddings
segment
amg 2d / amg 3d
commit
clear

And these sections are displayed upon annotater start. This results in visual cluttering.
Solution
Make sections collapsible and only display relevant sections upon annotater start.

Done in #486


mgmt, fix network security group update rule from asg to servicetag

Description
issue: https://github.com/Azure/azure-sdk-for-java/issues/33291
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Prevent adversary from deleting rows in encrypted files

This PR amends the file encryption format such that each encrypted row explicitly includes the total number of rows in the file. This allows each enclave to identify the expected number of rows in the file, even if the file's decryption is distributed across multiple enclaves. As a result, each enclave in the cluster can verify that the total number of rows in the globally decrypted file (obtained via allreduce) matches their expected value.

LGTM


⚠ Bofrost.at has degraded performance

In 6c80f0d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 839 ms

Resolved: Bofrost.at performance has improved in 6b92fc9.


Expose a way to calculate total storage amount used by the system [JIRA: RCS-339]

Memo: Detailed storage stats #1120 is partial solution for this. it's not a raw disk usage in total but something that are invisible for users or normal storage stats does not show.

I think this is fine to close. If all Key-Value amount is known then it can calculated by our usual overhead calculators.


Updated AMI Values that fix bug #24 issue

Description
I updated the AMI values for palo fw, webserver, ubuntu server with most recent versions.  Details of exact versions are also included in the code.

following ami updates made:
panos byol 8.1.9.x version dated 08-14-2019
ubuntu xenial image version 16.04 dated 11-14-2019
amazon linux ami amzn-ami-hvm-2<IP_ADDRESS>90826-x86_64-gp2 released on 08-26-2019
Motivation and Context

Bug#24

https://github.com/PaloAltoNetworks/terraform-templates/issues/24
How Has This Been Tested?
Entire terraform template in multiple regions has not been tested, yet all images have been verified via the aws cli and are valid/consistent ami id.

Screenshots (if appropriate)

Types of changes

allows code to run as there are now valid ami.  current var references non-existent palo alto ami.  so currently non-working code.

Bug fix (non-breaking change which fixes an issue)

Checklist

[ ] I have updated the documentation accordingly.
[ x] I have read the CONTRIBUTING document.
[ x] I have added tests to cover my changes if appropriate.
[ ] All new and existing tests passed.

Thank you for the PR. I don't necessarily consider this a bug. I will valid the AMI's and approve the change shortly.
However,  intent of terraform is to allow one to customize the templates to suit your specific usecase. Hence the AMI image values are meant to be modified by the users.
Thanks again.


Just me or, can i not Import that stuff at all?

Import [Warning]: Unable to read MonoBehaviour, because definition for script DynamicBoneCollider wasn't found
Import [Warning]: Unable to read MonoBehaviour, because definition for script DynamicBone wasn't found
Topic says it all, if it's possible would love to get told a way to get support for it, many thanks in advanced.

Do you really need those MonoBehs? If so, you need to provide .net dll with those DynamicBone scripts to ripper along with game data files

Well, did find a work around, using something else after i unpack the file, but it be really nice if it did, how would i go about adding the .net dll's if i would want to do that, I'm kinda dumb when it comes to stuff like that. All i can see from DynamicBone is that they are only .cs files, not sure if there is any other Dynamic files, i did find a DynamicBone.dll file on the Beat Saber folder tho, and i tried putting it various places, like the base folder, The master folder the GUI folder, thirdparty folder etc, just tons of different places, also libraries, no clue what im really doing so, would love some guidance

You just need a game with all dlls in its Managed folder. This warning "Unable to read MonoBehaviour, because..." means that ripper can't find script DynamicBoneCollider in any of the dll's you provided.


Compile to ES5

Create-React-App yields the following error on build:
Failed to minify the code from this file:

        ./node_modules/mobx-location/src/mobx-location.js:17

Read more here: https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#npm-run-build-fails-to-minify

PS, thanks for this little package, it's very useful when creating one's own MobX-powered router.


Artifacts are created multiple times

Expected Behavior
Tekton Chains should only ever create one instance of an artifact type for a given TaskRun resource.
Actual Behavior
Tekton Chains creates the same artifact multiple times for any given TaskRun. So far, I've been able to verify that this occurs to OCI image signatures and transparency logs uploaded to Rekor.
Steps to Reproduce the Problem
The steps below are meant to be used on a "dedicated" cluster where no other TaskRun resources are being created.

Create a TaskRun resource, either directly or via a PipelineRun.
Wait for the TaskRun to complete successfully.
Inspect the logs of the tekton-chains-controller. Notice how there are more than one log messages about uploading to the transparency log. In my case, I see two entries:

2022-03-23T18:35:27.682Z info Uploaded entry to https://rekor.sigstore.dev with index 1775727
2022-03-23T18:35:28.094Z info Uploaded entry to https://rekor.sigstore.dev with index 1775728

Inspect the logs of the tekton-chains-controller. Notice how there are more than one log messages about uploading the image signature to the registry. In my case, I see two entries:

2022-03-23T19:05:27.149Z info Successfully uploaded signature for quay.io/lucarval/tekton-test@sha256:73ee4bff9c6b74cd09948e29e578b807c56eaf17257f21706053eb7619f58356
2022-03-23T19:05:29.318Z info Successfully uploaded signature for quay.io/lucarval/tekton-test@sha256:73ee4bff9c6b74cd09948e29e578b807c56eaf17257f21706053eb7619f58356

The repo usage logs in quay.io also report that the signature tag was first created, then immediately updated to point to a different image signature.
Additional Info
Most of the payload information is the same between the two example entries mentioned above:
$ diff <(curl -s 'https://rekor.sigstore.dev/api/v1/log/entries?logIndex=1775727' | jq '.') <(curl -s 'https://rekor.sigstore.dev/api/v1/log/entries?logIndex=1775728' | jq '.')
2c2
<   "79e45e89b83634776c7a4adad3ff84da1f0ebefd07133410b575772d69d58075": {
---
>   "0677b20f548c264c181ecfbbe51f04ee5fda9b3b3037a6ad606813fbb5c2dfa5": {
6c6
<     "body": "eyJhcGlWZXJzaW9uIjoiMC4wLjEiLCJraW5kIjoiaW50b3RvIiwic3BlYyI6eyJjb250ZW50Ijp7Imhhc2giOnsiYWxnb3JpdGhtIjoic2hhMjU2IiwidmFsdWUiOiIxZGZlNzgwMTk2YzgxM2Q1NzQ3YWFmMWRkZDk4N2I1NGE4NTlhNGRlMzlmMmY5Mjc4MTc3NzIxM2U5NzNmMzkxIn19LCJwdWJsaWNLZXkiOiJMUzB0TFMxQ1JVZEpUaUJRVlVKTVNVTWdTMFZaTFMwdExTMEtUVVpyZDBWM1dVaExiMXBKZW1vd1EwRlJXVWxMYjFwSmVtb3dSRUZSWTBSUlowRkZSWFpIYWtVNWNUWkJZVW8yVFhCTGFUZHNXVUZuY1hwTllrdDZNZ3BNY1hsRE5VMUhNR3haZVVkUlkwWkZXVEpHUzIxM1RWcFFZVGd5Vm5SVWFtaHFRbTF4VUdwWWFIazFlVWQzV2xnck1XNTJVbnBJTkhSQlBUMEtMUzB0TFMxRlRrUWdVRlZDVEVsRElFdEZXUzB0TFMwdENnPT0ifX0=",
---
>     "body": "eyJhcGlWZXJzaW9uIjoiMC4wLjEiLCJraW5kIjoiaW50b3RvIiwic3BlYyI6eyJjb250ZW50Ijp7Imhhc2giOnsiYWxnb3JpdGhtIjoic2hhMjU2IiwidmFsdWUiOiJkYzM0OWZjZTYzNzg2ZTIyZWM0YjM2YmIyNGUxMzQwNDIwZmZhMGFjMzNjNTQ1NDRiNTA4Y2U0MjQ0NGU5YmJmIn19LCJwdWJsaWNLZXkiOiJMUzB0TFMxQ1JVZEpUaUJRVlVKTVNVTWdTMFZaTFMwdExTMEtUVVpyZDBWM1dVaExiMXBKZW1vd1EwRlJXVWxMYjFwSmVtb3dSRUZSWTBSUlowRkZSWFpIYWtVNWNUWkJZVW8yVFhCTGFUZHNXVUZuY1hwTllrdDZNZ3BNY1hsRE5VMUhNR3haZVVkUlkwWkZXVEpHUzIxM1RWcFFZVGd5Vm5SVWFtaHFRbTF4VUdwWWFIazFlVWQzV2xnck1XNTJVbnBJTkhSQlBUMEtMUzB0TFMxRlRrUWdVRlZDVEVsRElFdEZXUzB0TFMwdENnPT0ifX0=",
9c9
<     "logIndex": 1775727,
---
>     "logIndex": 1775728,
13,17c13,17
<           "4979bda9afddf14ec64086e1656bda947e630c6a3d4346ce44ddcfbcb300428d",
<           "a53e860326fc625e1224d9f609c11828083dd61e76e03ae3a9ea4daf06088cce",
<           "b38d9b3af81f70c0d52e0f4468d8b3f5ba729b8e3f47a31d2e60facbe2e4ccc1",
<           "6a0d8314142892b27e0a297452f820b0370502530b39d39b24e44ce02278781a",
<           "f70d6ba20245a731631fdda969e7e1cd48803fe6767ca543fabcce5e114e9124",
---
>           "10b5c420b9ed5702affce91c0d1d2868087e70e7d9693422d69b7110853b1129",
>           "9afe194d71a7206bd0e72d894e56629aeb6c0511f8478941a0d97dc43102defb",
>           "7d6c25c2c6940fdb5bba86743942ae136e2d8d1287bc70e99e6bc5474e1235a0",
>           "94cb9d2268a61ba4908f10cd9df8272d46fbbc03fb15582c6943504264a4fd5c",
>           "82467d2986af5ea22c3aef508c7c447161be2e410471bb09a32d431390489122",
29c29
<         "logIndex": 1775727,
---
>         "logIndex": 1775728,
33c33
<       "signedEntryTimestamp": "MEUCIFycoCGa94fIfh1swAXXsyJCDv7LILWg+8M941teAllZAiEAq94HRyO7o/9TuE7VbOU+ZIBV5E/xS7A49QIyhR39blc="
---
>       "signedEntryTimestamp": "MEUCIQCdMnhWp/2YnUs7YZt8+1j+MDt2D74/UWDtf5mQMyWPIAIgKJilxSumjX1szEsxlajhCUORrpRDYqNrKLGWKekM2ho="

A closer look at the attestation.body attribute shows that the only difference is the hash value:
$ diff <(curl -s 'https://rekor.sigstore.dev/api/v1/log/entries?logIndex=1775727' | jq '.[].body | @base64d | fromjson') <(curl -s 'https://rekor.sigstore.dev/api/v1/log/entries?logIndex=1775728' | jq '.[].body | @base64d | fromjson')
8c8
<         "value": "1dfe780196c813d5747aaf1ddd987b54a859a4de39f2f92781777213e973f391"
---
>         "value": "dc349fce63786e22ec4b36bb24e1340420ffa0ac33c54544b508ce42444e9bbf"

Kubernetes version:

Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"archive", BuildDate:"2021-07-22T00:00:00Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3+b93fd35", GitCommit:"3a0f2c90b43e6cffd07f57b5b78dd9f083e47ee2", GitTreeState:"clean", BuildDate:"2022-02-11T05:26:59Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}

This is an OpenShift cluster:
$ oc version
Client Version: 4.8.0-202201210133.p0.g88e7eba.assembly.stream-88e7eba
Server Version: 4.9.23
Kubernetes Version: v1.22.3+b93fd35

Tekton Pipeline version:

$ tkn version
Client version: 0.21.0
Pipeline version: v0.28.3
Triggers version: v0.16.1

There's another possibility here. I found an article that states a controller should stick to One Custom Resource Modification at a Time. Digging through the code, it looks like in most cases, the TaskRun resource is only modified once. However! If the artifacts.taskrun.storage is set to tekton, it is also modified here.
Sure enough, if I change artifacts.taskrun.storage to oci, the issue goes away completely. I do see two entries in rekor, but that's because one is for the image signature and the other is for the attestation. This is ok.


Question: How to perform cross contract calls?

The ask! v0.1.0 (ask-old) supported the cross contract calls via the use of @dynamic decorator.
Example - https://github.com/ask-lang/ask-old/tree/master/examples/crosscall
Does ask! v0.4.0 supports the cross contract calls? There is no reference of @dynamic in docs and no examples.

This also need to we re-design.
The reasons are as follows:
There were certain problems with the previous design
Waiting for the design of ink4.0
The AssemblyScript version update caused some internal implementation and behavior to be adjusted


CompilerOptions in tsconfig.json

I am using s-js with nativescript and i have a problem. Importing default exported S from s-js is undefined.

NativeScript app need to comply with the CommonJS specification

import S from 's-js';
console.log(S) //undefined !!!!!!!!

Changing es2015 to commonjs in https://github.com/adamhaile/S/blob/master/tsconfig.json#L8 fixes this.

Hi @ismail-codar --
Hmm, that sounds like a bundling / packaging issue.  I haven't used NativeScript.  Do you know how it handles bundling modules?  Or how you're bundling the app?
The way the S package is set up, there's a "module" parameter in package.json that points to an es6-module version of the lib.  This should be picked up by any bundler that can handle es6 modules (webpack 2, typescript 2, rollup).
The package's "main" property points to a UMD version of the library that should work with CommonJS, RequireJS and in the browser.
It sounds like you're using es6 module syntax, but that your bundler is picking up the UMD version of the library.  Your bundler is then assuming that the default export from the library is accessed via a "default" property on the export object.  That's how some es6->CommonJS bundlers are working, but not all.  I'm using rollup to do the CommonJS bundling, and it generates CommonJS libs where the default export is the main export object.
In other words, your bundler is converting ...
import S from 's-js';

... to ...
var S = require('s-js').default;

... when it should be doing ...
var S = require('s-js');

Can you tell me more about your tsconfig.json and bunder settings, and maybe we can figure out what's going wrong?
-- Adam

Here is some experiments:
This is working on nativescript platform but intellisense not working with visual studio code.
var S = require('s-js');

And this not working in runtime (S = undefined) but intellisense is working with vscode.
import S from 's-js';

If module changed es2015 to commonjs all of working. The choice is yours. But using only commonjs is enough according to me. I do not know if there is any other reason/advantage to use module=es2015.

@ismail-codar es2015 modules are important for any current system that understands them (webpack 2, typescript 2, rollup), and for all future ones.
If I'm right about what's going on, the core issue is that something in your build system is getting crossed up about which version (UMD or es2015) of the S lib it should use.  Changing the tsconfig.json setting "fixes" it for you by putting the right lib in the wrong location.  But it will break any build system that is looking in the right place.
I haven't seen this repro in the build environments I'm using.  Would it be possible to post up a repro somewhere?  Or perhaps give some details about the build system you're using and the config files? Is this a TS-only build, or webpack, or rollup or somesuch?  I'd like to help, but I'm not sure where things are going awry.

Hi @adamhaile  I will publish my nativescript - s-js entegration work in a few days. It seems to be working fine right now.  Working on the a sample will be good for find a solution.

Sorry @adamhaile It's been a long time. Priority work, holiday etc..
I just send surplus-nativescript and configured example project Can you try it?
surplus-nativescript provides dom like methods for nativescript platform.. https://github.com/ismail-codar/surplus-nativescript/blob/master/dom.js
Native mobile application development with s.js and surplus is good feature and it seems to be working successfully.

Thanks for the example, Ismail.  I pulled and, yeah, I could repro the issue you're seeing.
The s-js package contains both es6 and commonjs modules, and what's going on is that typescript is compiling against the es6 modules, but nativescript is loading the commonjs one at runtime.  The commonjs module was assembled by rollup, and it uses a different convention than typescript for modules containing a single default export.  Specifically, typescript expects the default export to be at require('s-js').default while rollup puts it at just require('s-js').  When typescript loads require(s-js').default it gets undefined, as you saw.
There's no spec or dominant convention right now for how es6 modules should be compiled to commonjs ones, so I can see this issue coming up for other people.  I'm going to experiment with adding a hidden, nonenumerable property to S, S.default === S.  That should provide compatibility for build scenarios like yours.  I just want to verify that it doesn't slow down the other calls -- I've seen cases where adding a property via defineProperty() appeared to slow down all property accesses to an object.
If I follow, your approach in surplus-nativescript is to create proxies for the DOM API calls that surplus uses.  That's cool :).  There's another fellow doing some experiments with using a DOM-in-js implementation to do server-side rendering with surplus.  If you wanted to remove the cost of proxying the calls, you could fork the surplus compiler and rewrite compile.ts to generate code appropriate to Nativescript.
I am planning to do some improvements to surplus' docs and websites, for sure.  I want to boost JSX compatibility first.  As you noticed (spreads, dotted subcomponent names, etc), surplus initially only supported a subset of JSX.  I'm working now to fill that out while (hopefully) preserving performance.  I want to get that done before too many people come knocking.

Just pushed a version 0.4.4 that should add compatibility for more commonjs build scenarios.  Please confirm that it fixes your issue.

Thanks for the fix defineProperty good solution. I will try it now..
The performance of the surplus-preprocessor is not very important but generated code performance is important. It is necessary not to mix.
I think the other approach is actually for surplus-nativescript (rewrite compile.ts for genrating nativescript platform). But it would be difficult for me. Is the surplus preprocessor section some codes generated by ANTLR like compiler generator or handwritten? Something hard in both cases. Creating proxies is practical solution.
I think another approach would be more accurate. Thats typescript is allready best full featured JSX or TSX parser. It contains parser, AST and visitor. Instead of writing your own compiler typescript compiler and custom transform features can be solution.
You can check https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API and http://blog.scottlogic.com/2017/05/02/typescript-compiler-api-revisited.html

I made the necessary experiment. You can close this issue at any time.

Great, glad to hear it's working for you!


When install fails in EC2 with a LB Service ELB is orphaned

We have reproduced this issue with the latest release.

try to install a broken chart with a service that is a type: LoadBalancer
Go into aws console and you will see an ELB that is not connect to the cluster, is not tagged, and is orphanned.

@jroberts235 did I miss anything?

And if you do a helm delete RELEASE_NAME --purge the LB is not cleaned up?

Is this still failing with Beta.2? I cleaned up some of the generic deletion logic, and am hoping this fixes some of the cloud provider-specific issues.

@technosophos we are going to test beta 5 and get back to you.  Thanks for the follow-up!

Evidence seems to suggest that this was closed around beta-5. Please re-open if you reproduce with a new (>2.1.0) Helm.


sipsess: refactor and simplify SDP negotiation state

The SDP negotiation state is now tracked in a single enum which is used as a state machine to keep track of the current state of the SDP negotiation. This makes reasoning about the SDP negotiation much easier and less error prone.
Some details about SDP offer/answer are now enforced more strictly, e.g. the first reliable non-failure response to an INVITE MUST contain an SDP offer, if the INVITE contained no offer.
Read about SDP negotiation in the excellent informational RFC 6337.

Looks good now.


Add log will switch view back to list

When in logs view, adding a new log will switch the view back to list view

I implemented it in MainWindow so that there is logic to switch back to the Person List view when other commands apart from logs is used.
It is not perfect but it's a start.

Technically resolved as we removed toggling button and only allow switching to session log panel with logs. Any other command will revert back to the Person Contact list.

Technically resolved as we removed toggling button and only allow switching to session log panel with logs. Any other command will revert back to the Person Contact list.

Im slightly confused, do you mean its on purpose that adding a log will jump back to person list and to see the log added, we have to key in log i/

Yup. Rationale is that the UI does not have a UI manager where the individual components have listeners to refresh and update GUI components.
This way, it is more stable as we can guarantee that the execution of commands will always lead to up-to-date ui components.


Affinity values

This PR adds affinity configuration for #210

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Dmitrii Kashin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks @freehck-codefresh for the contribution!
We have to look this in more detail to check if this is compatible with the architecture of the integration. For instance KSM metrics are scraped from the infra pod running on the same node otherwise those metrics will be missing. There might be other issues that could appear just applying the affinity config to the Daemonset.

Thanks @freehck-codefresh for the contribution!
We have to look this in more detail to check if this is compatible with the architecture of the integration. For instance KSM metrics are scraped from the infra pod running on the same node otherwise those metrics will be missing. There might be other issues that could appear just applying the affinity config to the Daemonset.

@gsanchezgavier
On the one hand, I understand that your service is supposed to be deployed on each node of the cluster.
But in my specific case I just wanted to monitor some specific services and there were no need to deploy the full daemonset, I needed only several of them.
It's just a use-case when a user has sixty nodes, but need to send metric to NR only from couple of services.

@gsanchezgavier
On the one hand, I understand that your service is supposed to be deployed on each node of the cluster.
But in my specific case I just wanted to monitor some specific services and there were no need to deploy the full daemonset, I needed only several of them.
It's just a use-case when a user has sixty nodes, but need to send metric to NR only from couple of services.

Stale, closing it for now since not aligned with the architecture and would possibly create issues in the future 😕


[20.09] go_1_16: 1.16.2 -> 1.16.5

Motivation for this change
Fixes #128368
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 128442 at ef2a4082 run on x86_64-linux 1

2 packages built successfully:

go_1_16
minio


[build_catkin.sh] Adds auto-detect feature for catkin_ws and git repo

Force push created a plethora of commits here. Anyway, sent PR #137 for the same - closing this PR now.


refactor(terminal): add ViewportType

Follow-up to #1427
See https://github.com/ratatui/ratatui/pull/1427#issuecomment-2422090507
For after the release https://github.com/ratatui/ratatui/pull/1427#issuecomment-2422363853

I'm swinging back around to review older PRs. I wonder if you would mind summarizing the purpose of this to remind me a bit about the problem and how the solution fixes it? I don't recall the specifics, so this would be really helpful.

Ok, I think I possibly understand this a little better now.
Currently, when initializing the terminal with options, the caller can request FullScreen, Inline with a specific height, or a Fixed area viewport. This viewport is stored in the terminal struct. We also store the actual area that the viewport is using in the viewport_area field. From time to time we've made the error of thinking that Terminal::viewport.area is the value that indicates the current viewport's area. It is not. It is the requested area in the absence of resizing information.
This PR changes that a little to add a field name to the inline variant, and remove the Fixed variant's value. The purpose of that is to avoid the confusion.
What's missing (If my understanding is correct) is that both the Inline and Fixed area need to continue to tract these values so that the terminal viewport_area works correctly even when the terminal is resized to a size smaller than the requested height / fixed area. So both the existing values need to be kept. These should be used when resizing below the requested amount (and resizing back to the requested amount in order that the terminal rendering can just work regardless of whether there's enough space to render the requested amount.
Given that understanding, I think there's not a lot of value in adding a secondary enum to track this info with a changed name and removed FixedArea enum value. Instead I think it would be better to document the above in the enum and terminal field, and ensure that there is adequate testing of the mentioned invariants when resizing occurs. Additionally, renaming the params passed to the resize function so that their purpose is clear would be helpful. Last, we should investigate and ensure that the viewport when autoresize works correctly when the fixed viewport is set. I suspect this is not correct right now as we entirely skip resizing when a fixed viewport is set.

@joshka Sorry for the late response.
Your understanding of the problem matches mine.
I thought of this as having:

a user facing type, Viewport
an internal configuration variable without outdated info, ViewportType
the rest of the internal state, including the actual current area

In this context, I merely normalized ViewportType in terms of data model.
To me it seemed "efficient" to drop the unnecessary info, but if you prefer to reuse Viewport, there might be some benefit to that in terms of amount of code, so that is also fine by me.
Thank you for looking into this!

@joshka Sorry for the late response.

No probs.

Your understanding of the problem matches mine. I thought of this as having:
...
To me it seemed "efficient" to drop the unnecessary info, but if you prefer to reuse Viewport, there might be some benefit to that in terms of amount of code, so that is also fine by me.

Good to get confirmation I hadn't missed something. It was a while since I had really delved into that code.
Originally I agreed with the direction you took when you originally raised this, but on digging a bit deeper I think the rationale for keeping the existing struct makes more sense (because if represents what the caller wants, not what the terminal givens them). I'll slap something together along these lines in a few days (unless you'd like to continue along that line).


Top padding truncating service content just below in most recent nightlies

In macOS 11.6 and most recent Ferdi nightlies we're seeing a padding issue that is truncating content at the top of services (all services such as Mattermost, Discord, Gmail, etc.), here's a screenshot:

This is now resolved with most recent nightly.


Document best practice to avoid pipefail masking errors during image building

Problem description
When writing a Dockerfile it is common to see lines such as:
RUN curl https://some.thing/file.tgz | tar -xf -

However what is not obvious is that if the first part of a pipe command fails, but the second still returns a successful return code, Docker will consider the command successful, cache the result, and continue the build.
For example:
FROM alpine:3.2
RUN wget https://wrong | wc

Succeeds (although the error is printed by wget, wc happily continues and returns an exit code of 0)
Sending build context to Docker daemon 2.048 kB
Step 1/2 : FROM alpine:3.2
 ---> d95450e87d1e
Step 2/2 : RUN wget https://wrong | wc
 ---> Running in 4527cb186fb4
wget: bad address 'wrong'
        0         0         0
 ---> 617373b273b0
Removing intermediate container 4527cb186fb4
Successfully built 617373b273b0

Given how RUN is documented to operate, this behavior is technically correct and appropriate, however it doesn't feel obvious (it caught us out in our CI system) and I did find it surprising.
If a user does in fact want their build to fail if part of a pipe fails, this can be done in most cases by prepending the command with set -o pipefail, e.g.:
RUN set -o pipefail && wget https://wrong | wc

Results in a build failure as desired:
Sending build context to Docker daemon 2.048 kB
Step 1/2 : FROM alpine:3.2
 ---> d95450e87d1e
Step 2/2 : RUN set -o pipefail && wget https://wrong | wc
 ---> Running in e647fe34893a
wget: bad address 'wrong'
        0         0         0
The command '/bin/sh -c set -o pipefail && wget https://wrong | wc' returned a non-zero code: 1

Problem location

I couldn't find the information I wanted. I expected to find it near the following URL:
https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#/run
and/or:
https://docs.docker.com/engine/reference/builder/#run

Project version(s) affected
All
Suggestions for a fix
Add documentation to the best practices to suggest that users running commands that pipe using consider using set -o pipefail in their Dockerfile.
I'd be happy to contribute a Pull Request along the lines of the above if you think this suggestion has merit.

So it turns out that my suggestion of set -o pipefail works on alpine, but not Debian. I'd welcome better suggestions on a best practice here.
/bin/sh: 1: set: Illegal option -o pipefail


Default instance label to explicitly empty for federation.

@beorn7
Fixed #2844

All done thanks, PTAL.

:+1:
(Failing test is a flaky test in fanin. Has nothing to do with this change.)


Crash when switching between online wallet and cold wallet and vice versa

ried to switch to cold storage mode and I got stuck in a loop telling me that my node is not loading and i kept switching to the dev node, but it didn't make the change.
The only way out was to modify the wallet713v2.toml file and create a new instance.

Not observing crash while switching between online and cold wallet with the latest build.
Hence closing this ticket.


Telegram Instant View enhancements: Threads, community notes, polls

Implements thread unrolling for Instant View, community notes in Instant View, polls in instant view and community notes for status API.

is this available?
I have a hard time getting an Instant View with the thread unrolled

Yes, it’s available. Do you have an example of a post not working?

I tried these URLs, none would unroll the thread:
https://i.fixupx.com/AurorAlpes/status/1859591267211939911
https://u.fixupx.com/AurorAlpes/status/1859591267211939911
https://t.fixupx.com/AurorAlpes/status/1859591267211939911


fixes wrong after field in webhook payload

Fix #1350

LGTM

Let L-G-T-M work

Can we write some integration test for webhook?

LGTM


Fix async_stream.h warning on Visual Studio

Fixes #13939
Followup for https://github.com/grpc/grpc/pull/13713.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE              FILE SIZE
 ++++++++++++++ GROWIN ++++++++++++++
  [ = ]       0 [None]    +168  +0.0%

  [ = ]       0 TOTAL     +168  +0.0%

[trickle] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,955,002      Total (=)      1,955,002

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,843,758      Total (>)     10,843,751

 No significant differences in binary sizes

[microbenchmarks] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE              FILE SIZE
 ++++++++++++++ GROWIN ++++++++++++++
  [ = ]       0 [None]    +168  +0.0%

  [ = ]       0 TOTAL     +168  +0.0%

[trickle] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,955,956      Total (=)      1,955,956

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,843,888      Total (<)     10,843,892

 No significant differences in binary sizes

[microbenchmarks] No significant performance differences

@yang-g   added the operator to ClientAsyncReader and ClientAsyncWriter as well. PTAL.

****************************************************************

libgrpc.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

****************************************************************

libgrpc++.so

     VM SIZE              FILE SIZE
 ++++++++++++++ GROWIN ++++++++++++++
  [ = ]       0 [None]    +168  +0.0%

  [ = ]       0 TOTAL     +168  +0.0%

[trickle] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,955,968      Total (=)      1,955,968

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,843,887      Total (>)     10,843,883

 No significant differences in binary sizes

[microbenchmarks] No significant performance differences


Fix remove glossary term image

Background: Elsewhere in the code (e.g. in observations) the thumbnail is included in the images, but for whatever reason great pains were taken to exclude the thumbnail from GlossaryTerm#images... only some cases were missed and when I fixed them I didn't realize thumbnails were being deliberately excluded, so I made a mess of things.  I've been trying to clean this up and make GlossaryTerm thumbnails and images behave the same way they do in Observation ever since.
Recently I noticed yet again that there were three glossary terms with thumbnails but no images.  I cleaned these up by hand and went looking at the code yet again.  I found more code that was still behaving as if the thumbnail was not included in the images, so I fixed them.
I still don't understand how this pathological case arises in the wild -- that is how images are removed without the thumbnail being set to null.  But these changes definitely fix bugs, in any case, and would have to be done eventually one way or another.

Coverage decreased (-0.004%) to 92.62% when pulling a8174324f5a6f671f4e1e655365c67a230c36fad on fix-remove-glossary-term-image into 729b08403cfc01828bcd522cbe4e4a46d0726be8 on master.

(I emailed you about this, but just posting it here so it's easier to find.)
I was checking out the Image methods #reuse_image and #remove_images_from_object, and they seem to be able to work on any model, theoretically. #reuse_image uses a @mode ivar, and #remove_images_from_object uses a target_class param.
However, they may be behaving unexpectedly in Glossary Terms, because there is a whole different action for #reuse_image_for_glossary_term that does not call #reuse_image. And there is also a separate action #remove_images_for_glossary_term, but it calls #remove_images_from_object. In any case it seems like these separate actions could be DRY'd up to use the same routes with the ivar or param.
In any case it seems that either these "special" attach or remove methods for glossary term images are possibly related to the mystery of how thumbnail assignment/deletion gets confused?

@nimmolo -- I looked into it briefly.  It looks like images are added or removed from glossary terms exclusively via GlossaryTerm#add_image and #remove_image, and those two methods are well-tested for all possible cases, seemingly.  While I agree the current state of image controller actions is clearly not ideal, and that they should be DRYed, it doesn't appear to be the source of this problem.  I added one more test to be sure anyway.  But I'm going to have to give up on this and merge it before it gets behind again.


Fix image name option for encrypt-gce-image

When no --encrypted_image_name option is passed
the encrypt command now generates a name for the
encrypted image rather than failing silently. It
uses the same log that update-gce-image uses to
generate a same (but the session id will change
so this won't cause collisions).
Removes the validate option from encrypt-gce-image
because it wasn't doing anything.
Testing: encrypted an image without the
encrypted_image_name option and then ran
update-gce-image on that encrypted image

LGTM


DoNotTrack plugin is not blocking process scanner[Bug]

Before Reporting

[X] I found no existing issues matching my bug
[X] My issue is not caused by a plugin or theme

Describe the Bug
DoNotTrack plugin is not blocking the process scanner and is allowing discord to find what games are being played and put them in the registered game tab.  This seems to be broken across all third party discord clients, so it was probably some update.
Expected Behavior
When games are played they will not show up in the registered games tab and will not be shown in rich presence
Steps To Reproduce

Install DoNotTrack plugin
Play game, it will show up in the registered game tab

Operating System
Windows
Discord Version
Stable
BetterDiscord Version
1.8.5
Anything else?
No response

My issue is not caused by a plugin or theme

This is most definitely a problem with the plugin...


TimeSeriesDataFrame.convert_frequency SLOW !

Discussed in https://github.com/autogluon/autogluon/discussions/4058

Originally posted by raedbsili1991 April  7, 2024
Hello,
I am working with irregular data with that I want to convert to monthly data set using the convert_frequency("M", agg_numeric = "sum").
Here is an exemple of what look like my TimeSeriesDataFrame

I wanted to infer the "Monthly" frequency before starting forecasting.
However, the execution is "infintesily" slow! it never ended.
I also tried to replicate the https://auto.gluon.ai/stable/tutorials/timeseries/forecasting-indepth.html but it the convert_frequency() is also so slow!
requirements.txt
Why is this happening ?

Hi @shchur , Appreciate your reactivity, Thank you.
Here is the version output:

Regarding the execution of the code, it stills never-ending slow

Thanks @raedbsili1991, it seems that in your case the parallel processes created by joblib get stuck for some reason. Can you please try upgrading joblib to a newer version (v1.1 seems to be quite old).
pip install -U joblib

Alternatively, could you try disabling multiprocessing for convert_frequency with
df_irregular.convert_frequency(freq="D", num_cpus=1)

I assume that the above fix addressed the issue. Please feel free to re-open if this is not the case.


planuml: 1.2020.19 -> 1.2020.26

Plantuml complains that it's too old when a diagram is generated to PNG an
error occurs.

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@ofborg eval

@ofborg eval

Result of nixpkgs-review pr 108563 run on x86_64-linux 1

4 packages built:

plantuml
python37Packages.sphinxcontrib_plantuml
python38Packages.sphinxcontrib_plantuml
python39Packages.sphinxcontrib_plantuml

Result of nixpkgs-review pr 108563 run on x86_64-linux 1

4 packages built:

plantuml
python37Packages.sphinxcontrib_plantuml
python38Packages.sphinxcontrib_plantuml
python39Packages.sphinxcontrib_plantuml

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108563 run on x86_64-linux 1

4 packages built:

plantuml
python37Packages.sphinxcontrib_plantuml
python38Packages.sphinxcontrib_plantuml
python39Packages.sphinxcontrib_plantuml

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108563 run on x86_64-linux 1

4 packages built:

plantuml
python37Packages.sphinxcontrib_plantuml
python38Packages.sphinxcontrib_plantuml
python39Packages.sphinxcontrib_plantuml

I think the other two commits are unrelated to this one. Please clean that up.

I think the other two commits are unrelated to this one. Please clean that up.

Fixed and force pushed.

Fixed and force pushed.

Result of nixpkgs-review pr 108563 run on x86_64-linux 1

4 packages built:

plantuml
python37Packages.sphinxcontrib_plantuml
python38Packages.sphinxcontrib_plantuml
python39Packages.sphinxcontrib_plantuml

Result of nixpkgs-review pr 108563 run on x86_64-linux 1

4 packages built:

plantuml
python37Packages.sphinxcontrib_plantuml
python38Packages.sphinxcontrib_plantuml
python39Packages.sphinxcontrib_plantuml


"Patch" extends can modify core schema attributes

Summary
"Patch" extends can modify core schema attributes, potentially causing events generated with an extension to become incompatible with core OCSF schema and other private extensions.
Details
A patch extends, typically where an extension "patches" a class or object in the core schema. These are triggered by defining a class or object without a name and only an extends or where the name and extends are the same.
In the patch case, the attributes and profiles from the the patching definition (from the extension) are merged backwards to the base class or object. In other words, the patching extension definition modifies the core schema.
The problem is with the merged attributes. Existing attributes can be modified with this mechanism, potentially causing a resulting OCSF Schema that is incompatible with the core schema by, for example, changing the type of an attribute.
We should, I think, validate the these patching cases either do not modify existing attributes, or only allow backwards-compatible changes. The backwards-compatible changes approach could be tricky, so I would avoid it if possible. If needed, we will need to carefully consider what kinds of attribute changes are safe. We want extensions to be compatible with the core schema and other private extensions.

Agreed. The intention is for the patch extension to "extend" the core schema, not to modify it in any way. The main difference with a patch extension is that no new classification or types (classes, objects, categories) are added, only augmented.
Eg it is the only way an extension can create a profile that can apply to the core schema.


[stable/postgresql] Allow connection details to be set as global

Signed-off-by: Javier J. Salmeron Garcia<EMAIL_ADDRESS>
What this PR does / why we need it:
Extracted from the README
In more complex scenarios, we may have the following tree of dependencies
                    +--------------+
                    |              |
       +------------+   Chart 1    +-----------+
       |            |              |           |
       |            --------+------+           |
       |                    |                  |
       |                    |                  |
       |                    |                  |
       |                    |                  |
       v                    v                  v
+-------+------+    +--------+------+  +--------+------+
|              |    |               |  |               |
|  PostgreSQL  |    |  Sub-chart 1  |  |  Sub-chart 2  |
|              |    |               |  |               |
+--------------+    +---------------+  +---------------+

The three charts below depend on the parent chart Chart 1. However, subcharts 1 and 2 may need to connect to PostgreSQL as well. In order to do so, subcharts 1 and 2 need to know the PostgreSQL credentials, so one option for deploying could be:
helm install chart1 --set postgresql.postgresqlPassword=testtest --set subchart1.postgresql.postgresqlPassword=testtest --set subchart2.postgresql.postgresqlPassword=testtest --set postgresql.postgresqlDatabase=db1 --set subchart1.postgresql.postgresqlDatabase=db1 --set subchart2.postgresql.postgresqlDatabase=db1

If the number of dependent sub-charts increases, executing helm install can become increasingly difficult. An alternative would be to set the credentials using global variables as follows:
helm install chart1 --set global.postgresql.postgresqlPassword=testtest --set global.postgresql.postgresqlDatabase=db1

This way, the credentials will be available in all of the subcharts.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

Ping @desaintmartin @prydonius @tompizmor

Is there some common consensus about this in the helm community / this repository? It would be counterproductive if some other chart starts to use another solution.
If think it deserves a discussion during the meeting.

Yes, I agree, we can add this discussion to the following "Charts Office Hours" meeting. @javsalgar can you add it to the agenda if it's okay to you?

Thank you for spawning this discussion @javsalgar :bowing_man:

This looks ok to me. I'd like @prydonius to take a pass at it and it needs a rebase from master.

Thanks @mattfarina , merge issues fixed

/lgtm


feat: add user_space table to collect user's votes and proposals count per space

From the pitches https://www.notion.so/snapshotlabs/S-delegation-part-2-2b3186d8a33b4fd8b90c6575b6bf8000#bc7c1c9c785c46bdad69b4c8337771ca
This is a read-only part of the feature, which creates a new table to store the proposals_count and votes_count counters. The update side will be on sequencer: https://github.com/snapshot-labs/snapshot-sequencer/pull/127
This PR contains 2 changes:

Update to the schema.sql to include the new table
Add a script (run with yarn ts-node scripts/generate_user_space_counters.ts) to trigger the counters computation. (moved to sequencer)

Closing, see leaderboard instead


Pie mark labels in wrong positions

The Pie mark seems to occasionally misplace labels when assigning new data to an already displayed mark. The behavior is unpredictable (perhaps 30% of the time?), and can occur with a variety of input types and parameters. If a new view of the figure is created, the labels with display correctly. See the below code to reproduce the issue, as well as the attached screen captures.
from bqplot import Pie, Figure
import random
pie = Pie(sizes=[1,2,3])
fig = Figure(marks=[pie])
fig

data = [random.randint(1,100) for i in range(3)]
pie.sizes = data
pie.labels = [str(x) for x in data]

I've had a quick look I couldn't figure out the issue. Maybe @ChakriCherukuri you could take a look?

I can reproduce it here, it is in master, will attempt a fix.

A clear test is this:
from bqplot import Pie, Figure
import random
pie = Pie(sizes=[1,2,3], labels=['a', 'b', 'c'])
fig = Figure(marks=[pie])
fig

Giving the correct result:

Next cell:
pie.labels = ['b', 'a', 'c']
pie.sizes = [3,1,2]

Gives the wrong result (at least it seems wrong):

I suspect it has to do with the outer_join and join_key. It seems it wants to use the labels as keys, but I'm not sure I follow the logic. Is  @ChakriCherukuri the original author? Or do you know reasoning behind it @rmenegaux ?

A 'somewhat' fix seems to be (in Pie.js:draw) to do:
        was = _.sortBy(was, 'index');
        is = _.sortBy(is, 'index');

Since the label in used for the d3 key in the rest, but the order of the joined data is undefined, calling pie() with the unordered data does not make sense. However, when I execute:
data = [random.randint(1,100) for i in range(3)]
pie.sizes = data
pie.labels = [str(x) for x in data]

many times, it gives an issue after ~10 times:
widget.js:228 Error setting state: Maximum call stack size exceeded but i'm not sure if that is related.
Any input from the original devs would be appreciated.

@maartenbreddels I don't know anymore than you do here, @ChakriCherukuri could you lend a hand?

I'll take a look

Couple of problems I noticed after painful debugging:

Colors need to be tied to labels (not data indices) since labels are used as keys
Ideally data (labels plus sizes) should be processed in one shot. Currently labels are first getting updated and then sizes which is throwing off the outer_join

I am all in favor of adding a legend to display labels. There's way too much complex code to manage the transitions. If you all agree I'll add legend instead of labels inside, labels outside etc.

It would be a breaking change for anyone with notebooks that depend on the existing labels. This isn't necessarily an argument for or against, just something to be aware of.

The problem is not in transitions (even though the code is complex with custom tweens). It's in the joining of data based on labels as the join key. I'll dig in further to see if I can have a fix.
@kaiayoung I was not planning on dropping any Pie attributes. I just want to display them as legends instead of having separate logic for displaying inside or outside.

Finally figured it out. There were 3 data joins happening in the draw method, two with sorted data (based on labels) and the final one (without sort). This is messing up the slices and label placement. Fixed the issue.
Also IMHO it makes sense to set colors based on labels so that when the label order changes (like in the example by @maartenbreddels) the colors reflect the correct labels. I also added this fix

@rmenegaux looks like you have changed polyline stroke from black to white (bqplot.less) which is messing up the polyline rendering of Pie labels (when display_labels='outside' is selected). Please advise

@maartenbreddels the 'max call stack exceeded error' is due to the latest change in utils.deepCopy method. It doesn't support string types hence going to infinite recursive loop. I have a temporary fix added to my PR but you might want to revisit the code to take care of all data types


BIGTOP-3792: Mpack solr fail to start when kerberos enabled

Description of PR
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'BIGTOP-3638. Your PR title ...')?
[ ] Make sure that newly added files do not have any licensing issues. When in doubt refer to https://www.apache.org/licenses/

Testes it both on x86 and Arm64 hosts.
+1.

Merged, thanks @timyuer


Depending on crates that use wasm-bindgen

Hi! I have a crate that uses wasm_bindgen to expose a very limited number of methods to wasm.
My crate has a dependency that also uses wasm_bindgen and exports alot of methods which I do NOT want to expose when compiling my wasm file. Is it possible to skip processing wasm_bindgen marked items in the referenced crate so that my compiled wasm file only contain the methods I want to expose?

Duplicate of #3759.


Interior app refactor & github templates

What does this PR do?
Closes #97 & #99
What did I do?

corrected imports for generate_description.py
enhanced readme
added templates for improved github workflow

Test plan
ran
PYTHONPATH=. python examples/interior_design_assistant/api.py localhost 5000 examples/interior_design_assistant/resources/documents/ examples/interior_design_assistant/resources/images/fireplaces

Output:

Thanks for contributing 🎉!

thx!


Allow acmego to reformat other file types

(currently only .rs) when -f option is selected.

Thanks! I made some tweaks and committed.


allow override of prompt on signin

Closes/fixes #536
Checklist

[x] This PR makes changes to the public API
[x] I have included links for closing relevant issue numbers

thanks for contributing


Types Redux: tracking issue

Tracking issue for various tasks aimed at refactoring and simplifying the type system.
Some require refining and issues made

[x] #361
[x] #360
[x] #359
[x] #370
[x] #366
[x] #275
[x] Include in prelude: float, qubit, array (for existing tests)
[x] #409
[x] #408
[x] Decide whether to move Graph out of core (update: graph stays)
[x] #371

Closing as tracked issues are done.


Barcode doesn't scan on front camera

Hello,
when trying to scan barcode from front camera, it doesn't work. Barcode scanning seems to work only on back camera. QR codes are scanning fine on both cameras.
<QRCodeScanner
                    onRead={this.onRead}
                    cameraStyle={{
                        flex: 1,
                        width: Dimensions.get("window").width - 345,
                    }}
                    topViewStyle={{ flex: 0, height: 0, width: 0 }}
                    bottomViewStyle={{ flex: 0, height: 0, width: 0 }}
                    cameraType={this.props.cameraType} // "front" | "back"
                    reactivate={true}
                    fadeIn={false}
                    reactivateTimeout={2000}
                    showMarker={true} />

Versions:
"react-native-camera": "1.2.0",
"react-native-qrcode-scanner": "1.0.1",
"react-native": "0.51.0",
"react": "16.2.0",
iOS version tried: 11.4.1, but happens on multiple iPads here in office with different versions
Any ideas? Could it caused by low quality front camera (iPad Air 2) or horizontally flipped scanning on front camera?

+1

Hi,
Please help on this

it seems to be related with a bug on react-native-camera side, did you check for this same problem over there @avjabalpur?

well, I did find in advance an issue over there telling that is not possible to be able to, for now. It's Google MLKit limitation, as you check here https://github.com/react-native-community/react-native-camera/issues/2363#issuecomment-509765993
So, I'll be closing this one, and if you want  to work in any workaround to solve this problem, please, make a suggestion in react-native-camera instead


BasicTree获取选中的key都变成["0-0-1","0-0-0-0","0-0-0-1"]

BasicTree :replaceFields="{ title: 'title', key: 'id' }" 已经设置了id，获取选中的key都变成["0-0-1","0-0-0-0","0-0-0-1","0-0-0-0-1","0-0-0","0-0"]

replaceFields这个属性在3.0已经废弃，尝试fieldNames


bug: invalid entities

after new validation was added to dmss, som actions in dm-cli fails due to errors in modeling accross repos.

outdated


ScriptDetour Improvement

Unless I am misunderstanding this is really bad practice.
std::ifstream inFile;
inFile.open(detourDir.string());
if (inFile.good() && fileName != "runString.lua") {

	std::string content((std::istreambuf_iterator<char>(inFile)),
		(std::istreambuf_iterator<char>()));
	if (!strcmp(content.c_str(), fileContent.c_str()))return {};

	fileContent = content;
	return fileContent;
}
else {
	std::ofstream outDetourFile;
	outDetourFile.open(detourDir.string());
	if (outDetourFile.good())
	{
		outDetourFile << fileContent;
		outDetourFile.close();
	}
}

The problem is that you are saving every server file into the detour folder, in my original code this was not the intention.
The intention was for people to place the scripts themselves.
The reason for this is that when you have all the scripts pre placed in the detour folder you will no longer be getting any script updates from servers because there is already a script there.
A better solution for a runtime detour would be to instead have the detour scripts that users add append onto the original script. This way you can do stuff like rerouting functions without replacing the entire file.
OldEpicFunction = EpicFunction
EpicFunction = function()
    -- Do your own stuff
    OldEpicFunction()
    -- Do your own stuff
end

Something like this would probably work?
std::ifstream inFile;
inFile.open(detourDir.string());
if (inFile.good() && fileName != "runString.lua") {

	std::string content((std::istreambuf_iterator<char>(inFile)),
		(std::istreambuf_iterator<char>()));
	if (!strcmp(content.c_str(), fileContent.c_str()))return {};

	fileContent = fileContent + "\n\n" + content;
	return fileContent;
}

Hi, totally forgot to reply to this issue but pretty sure every issue about this has been resolved. Detouring doesn't saves any lua file anymore, only the folders for convenience purposes.


Pylint marking curses methods as incorrect

Environment data

VS Code version: 1.40.2
Extension version (available under the Extensions sidebar): 2019.11.50794
OS and version: Windows 10 1903 x64
Python version (& distribution if applicable, e.g. Anaconda): 3.8.0
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: windows-curses 2.1.0
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): N/A

Expected behaviour
VS Code should not mark the code as incorrect.
Actual behaviour
VS Code mark the code as incorrect, if I hover I get this error:

Module 'curses' has no 'curs_set' member

Steps to reproduce:
import curses

def main(scr):
    curses.curs_set(0)

curses.wrapper(main)

Logs
##########Linting Output - pylint##########
************* Module test_curse_github_issue
5,4,error,no-member:Module 'curses' has no 'curs_set' member

--------------------------------------------------------------------

Your code has been rated at 0.00/10 (previous run: 10.00/10, -10.00)

Hi,
If you check the logs, this error is being reported from pylint. Please open your issue at https://github.com/PyCQA/pylint.


Add channel id overflow handling

Coverage decreased (-1.5%) to 87.734% when pulling 0be3b9245043491a82a0251912a27970c56983aa on feature/channel-id-overflow into 8556d8c2a3484116ea5f3f77613b8a0d9b18f936 on master.

Coverage decreased (-1.5%) to 87.708% when pulling dbca6a7656b1e5ab28b22de89bd17f3bca1f41e2 on feature/channel-id-overflow into 8556d8c2a3484116ea5f3f77613b8a0d9b18f936 on master.

Coverage decreased (-1.2%) to 87.952% when pulling fa67bd041d54bdeddd54f5e62780b6d3167a52a0 on feature/channel-id-overflow into 8556d8c2a3484116ea5f3f77613b8a0d9b18f936 on master.

Coverage decreased (-1.2%) to 87.952% when pulling fa67bd041d54bdeddd54f5e62780b6d3167a52a0 on feature/channel-id-overflow into 8556d8c2a3484116ea5f3f77613b8a0d9b18f936 on master.


Navigate

use open pilot

If you have an actual issue, you can make a new issue with a description of the problem.


Export token.json During data load Command Process

Is your feature request related to a problem? Please describe.
Currently, the data load command process does not export the token.json file, which is necessary for subsequent PCA reduction and other processing steps.
Describe the solution you'd like
Modify the data load command process to include a step that exports the vocabulary and embeddings to a token.json file. This file should contain all tokens and their corresponding 384-dimensional embeddings.
Describe alternatives you've considered

Manually exporting the token.json file after the data load process, but this adds an extra step and potential for errors.
Integrating the export step into a different part of the workflow, but it makes more sense to do it during the data load process for efficiency and consistency.

Additional context
This change is necessary to streamline the workflow and ensure that the token.json file is available for the PCA reduction script (reduce.py). The token.json file should be structured as follows:
{
    "token1": [0.1, 0.2, 0.3, ..., 0.384],
    "token2": [0.4, 0.5, 0.6, ..., 0.384],
    "token3": [0.7, 0.8, 0.9, ..., 0.384],
    ...
}

okay successfully implemented and tested against our tiny and training_data test sets


optimization not loading some js

Hi
Thanks for the guide I have install the code but it does not find some script

The section will only find scripts injected by Shopify apps via the Script Tag API.
If the script you want to block is added via the Script Tag API, please send me a link where I can replicate the issue.
Thanks

Hi
For example we have installed this on the website which does not show
https://developer.reevoo.com/docs/overview
Also googletagmanager

googletagmanager is not added via Script Tag API: https://shopify.dev/docs/api/admin-rest/2023-01/resources/scripttag
Not sure about Reevoo.
The app/section will only help optimize those scripts that are injected by Shopify


Improvement #225 Update Facebook SDK in iOS up to v4.x

Catching up SoomlaFacebook to Facebook iOS SDK v4.10.1.

@borisspektor, it's ready to review+merge.


Cloudflare delay doesn't work.

I set a delay time, but it didn't take effect. It still clicked quickly. fail to pass the captcha.

Thank you for reporting the issue. We'll address this bug in our next update.

Do you pass the CAPTCHA if you click manually?

Do you pass the CAPTCHA if you click manually?如果您手动点击，您会通过验证码吗？

I can pass the CAPTCHA if I click manually.


feat: update dependencies

Description

Fixed the CI release pipeline to run on push and pull request triggers.

Fixes # (issue)
Type of change

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

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Expand on the deletion in Reconcile()

I was stuck for hours because I didn't update to the storage. I hope this clarification helps others.

@tanin47 thanks for the contribution.  would you sign the cla?

I already signed it I think. (The robot just added the flag yes.)

@tanin47 Thanks.  Sorry for the late response, have been on leave for the past 5 weeks.


Message Pack support for streaming parameters

The protocol changes aren't reflected in MessagePack. When the Json side is cleaned up and finalized, I will port the changes to MessagePack. This will involve writing new tests and/or adapting existing tests to run with both protocols.

Done via https://github.com/aspnet/AspNetCore/pull/4300


JPG image not displayed via Image.file()

Steps to Reproduce
The code leading to errors was taken from https://github.com/flutter/plugins/blob/master/packages/image_picker/example/lib/main.dart.
I tried the example to figure out how to take images in Flutter, and I soon realized that JPG pictures are not displayed on my older phone Samsung Galaxy A5 (2015) (listed in the flutter doctor -v output). There are no problems on the new phone or with the PNG image format.
So when I select JPG images, the screen stays white, but PNG images are displayed as desired.
Basically it comes down to these two lines:
_imageFile = await ImagePicker.pickImage(source: source);
Image.file(_imageFile)

Execute code from https://github.com/flutter/plugins/blob/master/packages/image_picker/example/lib/main.dart.

Logs
flutter run --verbose
https://pastebin.com/ubMhG1U0
flutter analyze
Analyzing test_project...
No issues found! (ran in 3.7s)

flutter doctor -v
[✓] Flutter (Channel beta, v1.5.4-hotfix.2, on Linux, locale en_GB.UTF-8)
    • Flutter version 1.5.4-hotfix.2 at /home/martinniederl/development/flutter
    • Framework revision 7a4c33425d (2 weeks ago), 2019-04-29 11:05:24 -0700
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /home/martinniederl/Android/Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /home/martinniederl/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] Android Studio (version 3.3)
    • Android Studio at /home/martinniederl/android-studio
    • Flutter plugin version 34.0.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[✓] VS Code (version 1.33.0)
    • VS Code at /usr/share/code
    • Flutter extension version 3.0.2

[✓] Connected device (2 available)
    • POCOPHONE F1 • 7fa18afc • android-arm64 • Android 9 (API 28)
    • SM A500FU    • 951ad3cd • android-arm   • Android 5.0.2 (API 21)

• No issues found!

I am facing the same issue with old moto phone.  Is there a work around ?

Incase you havent found a work around, I converted the image to PNG using Image package and it started working.

I was facing the same issue with a Motorola E5. In my case the problem was related with the image's size, I wasn't able to display any large size pictures.
If you don't want to convert the image to PNG as it can increase file's size, you can compress the image with the flutter_image_compress package and then display it.

Actually, I realized that the issue is with the file size. There is an option for maximum width and height in the image_picker methods. That kinda compress the file to manageable size. I can now see the image load immediately on the UI.

Then I will probably need 2 versions of the picture: A compressed one for displaying in the app and the original one for sending to the backend.
But I am sure that this is not the intended behavior and I will not close the issue yet.

Having the same problem with big jpg images. Image source does not matter, both assets and network image displayed as white rectangle with proper aspect ratio.
Reproduces only on android, works fine on ios.

Hey just wanted to add this thread in case it might provide some insight.
I was experimenting with using https://pub.dev/packages/image_cropper plugin .
After taking the photo if I increase the scale while cropping ever so slightly (increased from 75% to 78%) and the image starts to display normally.

Hi @MartinNiederl
This seems to be fixed, running the code sample  on API 22 (Android 5.0)
JPG Image is loaded just fine.
If you're still experiencing this issue, please can you please provide your flutter doctor -v and flutter run --verbose?
I will reopen the issue
Thank you


Pick Your Potion Issue

Stage 7 of Pick your Potion has a typo, its supposed to be "Gems" instead of "Gyms"

Typo has been corrected


Buildx pushing to quay - 401 unauthorized

https://github.com/docker/buildx/issues/327
https://github.com/docker/buildx/issues/327#issuecomment-733058083
https://github.com/containerd/containerd/issues/4622#issuecomment-716746004
Fix may be pulled through - https://github.com/moby/buildkit/pull/1921

Executive summary:
Pushing to Quay works on initial push (first tags in image repo)
Updating an existing tag (or deleting a tag and re-pushing it) causes a 401 Unauthorized error as can be seen here

Executive summary:
Pushing to Quay works on initial push (first tags in image repo)
Updating an existing tag (or deleting a tag and re-pushing it) causes a 401 Unauthorized error as can be seen here


Move HTML classes to namespace

Would this require adding a prefix everywhere?
use namespace XhpLib\HTML as h;
...
$link = <h:a href="...">...</h:a>;

Or would we expect people to do
use type XhpLib\HTML\a as a;
use type XhpLib\HTML\div as div;
...

Would this require adding a prefix everywhere?

Yep...

Or would we expect people to do

use type XhpLib\HTML\{a, div};
... or more likely, a separate library adding aliases/wrappers in the root namespace.
"HTML is not special" is an aspirational goal that can:

be tried in a relatively straightforward way now
be undone by a separate library
be undone in xhp-lib easily in the future

also, expecting most code in the future to be namespaced - so it'll already need to be <:a> instead of <a>; adding the NS isn't a much bigger usability change.

There's also arguments for it not to be special even if only used for frontend work:

encouraging usage of React rather than Hack-generated HTML (though I'm still in the 'progressive enhancement' boat :) )
encouraging usage of safer wrappers, eg <ui:link> instead of <a>


Ensures id in labelcontent for correct label and description ids

Description
Fikser https://altinn.slack.com/archives/C02EJ9HKQA3/p1724673207635629

Related Issue(s)

closes #{issue number}

Verification/QA

Manual functionality testing

[ ] I have tested these changes manually
[ ] Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
[ ] No testing done/necessary

Automated tests

[ ] Unit test(s) have been added/updated
[ ] Cypress E2E test(s) have been added/updated
[ ] No automatic tests are needed here (no functional changes/additions)
[ ] I want someone to help me make some tests

UU/WCAG (follow these guidelines until we have our own)

[ ] I have tested with a screen reader/keyboard navigation/automated wcag validator
[ ] No testing done/necessary (no DOM/visual changes)
[ ] I want someone to help me perform accessibility testing

User documentation @ altinn-studio-docs

[ ] Has been added/updated

[ ] No functionality has been changed/added, so no documentation is needed
[ ] I will do that later/have created an issue

Support in Altinn Studio

[ ] Issue(s) created for support in Studio

[ ] This change/feature does not require any changes to Altinn Studio

Sprint board

[ ] The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
[ ] I don't have permissions to do that, please help me out

Labels

[ ] I have added a kind/* label to this PR for proper release notes grouping
[ ] I don't have permissions to add labels, please help me out

Report here indicates the fix possibly did not work in the reported case: https://altinn.slack.com/archives/C02EJ9HKQA3/p1726827365926899?thread_ts=1724673207.635629&cid=C02EJ9HKQA3


Add support for showing bitrate

It would be cool to show bitrates and (if possible) encodings in the Web UI.
If possible, we should differentiate between fixed and variable-rate compression

Is this for showing the bitrate in the catalogue, or is it for showing the bitrate while you're playing the file?

Ideally in the catalogue.

We need to now implement something in the frontend to display it.
The iTunes importer will pick this value up if set by iTunes, but we now need a good way to extract this from audio files which are imported using the path walker.

How do we plan on supporting variable bitrates? Do we want to show MP3 V0 rather than an actual bitrate value?
Maybe showing that it is V0 should be part of how we should what format the file is in.

Yes, so having variable bit rates is an issue - and it would seem that in this case iTunes shows the average.  Apparently my commit message wasn't clear enough and GitHub chose to close this issue :-).
In future the Tchaik library should probably have a better type for the "BitRate" field, it would seem that an integer isn't enough here.
For the moment, it would seem that the next step would be to implement reading this from the underlying audio file (hopefully MP3, MP4/ALAC and FLAC) and then once that is done change the library format for the BitRate field.

I'm adding support in dhowden/tag for calculating bitrate for the different formats (I need it for my own project).
I had a different library to do the job, but It make sense to add the support into tag directly


Doubt: In experiment and results, you have provides links to parameters. is this paramenters trained on BDD100k dataset?

Yes, the parameters are of ResNet/DeepLab V3+ and are trained on BDD100k drivable area segmentation.
Which issue or doubt do you have?

Hey thanks for quick reply. I just want to know whether I can use that parameters for quick test on a random image?

You can use them.
I have tested them on random images including driving scenes in youtube and BDD100k videos.
Samples on BDD100k videos: https://www.youtube.com/watch?v=-dzS8VlVmk4&list=PLn3JZxvQvVuAbhz5ep4X-dysT9jLMMQpv
You should consider many things. Good  luck.


Enable redirect on beta.webcomponents.org

@samuelli now maybe the repository needs a rename? 😁

@abdonrd Yes! Any ideas? :)

Maybe webcomponents/www will be fine?

@samuelli I propose webcomponents.org. But www is okey for me too!


Support default exports for entity classes

Describe the bug
When EntityFactory creates an entity and config.discovery.requireEntitiesArray is false, the module loading for Entity doesn't support models defined as default exports.
Source code
The source code causing this bug is in the createEntity() method here:
const path = utils_1.Utils.absolutePath(meta.path, this.config.get('baseDir'));
Entity = require(path)[meta.name];

Models that are defined as export default class are not supported.  A simple fix here may be checking if meta.key or default exists as a key on require(path).
Stack trace
UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'prototype' of undefined
    at EntityFactory.createEntity (c:\...\node_modules\mikro-orm\dist\entity\EntityFactory.js:64:45)
    at EntityFactory.create (c:\...\node_modules\mikro-orm\dist\entity\EntityFactory.js:27:29)
    at EntityManager.merge (c:\...\mikro-orm\dist\EntityManager.js:160:80)
    at EntityManager.find (c:\...\node_modules\mikro-orm\dist\EntityManager.js:59:33)
    at process._tickCallback (internal/process/next_tick.js:68:7)
...

To Reproduce
Steps to reproduce the behavior:

Create a model that is the default export of a module.
Run application and create a document in a mongo collection
Restart application
Run a simple query that loads an entity from a MongoDb collection

Expected behavior
The module should load regardless of if it's the default export or not.
Additional context
N/A
Versions
I'm running 3.0.0-rc.5

Dependency
Version

node
?

typescript
?

mikro-orm
?

your-driver
?

Default exports are not supported for entities, but sure we can do something about that :]

Even just adding a note to the docs on models may be enough so a newbie doesn't get stuck for a while debugging the issue.

Will be fixed in next RC.


Conversion bug with Refined Storage exporters

Issue description:
Eggs passing through an exporter are converted to a different type of egg when using Hatchery
What happens:
Putting a Refined Storage exporter on a chest, filtering with any Hatchery egg and setting "Compare ore dictionary" to "Yes" will export normal eggs as the filtered Hatchery egg allowing conversion from ordinary egg into whatever Hatchery egg you're filtering on.
What you expected to happen:
Eggs should be taken from a Refined Storage system and be placed in the chest as the same type of egg.
Steps to reproduce:

Put Refined Storage exporter on a chest.
Set the filter to any type of Hatchery egg.
Set "Compare ore dictionary" to "Yes".
Chest will fill up with the filtered Hatchery egg instead of normal Minecraft eggs.

Version (make sure you are on the latest version before reporting):

Minecraft: 1.12.2
Forge: <IP_ADDRESS>24
Refined Storage: 1.5.31
Hatchery: 2.1.2
Chickens: 6.0.4

Does this issue occur on a server? Yes

Cross-posted as a Hatchery issue as well: https://github.com/GenDeathrow/Hatchery/issues/147

Just did a little more testing and it only seems to export as the incorrect type when the original egg comes from a Compact Drawer via a Refined Storage External Storage.
Having the eggs in a Refined Storage system itself doesn't seem to be an issue.

#1619


Does the conductor suport authorization for admin UI?

Hey @MaksimRT, no, Conductor UI doesn't support authorization at this time.


Bump 1.4.3 final (for release!)

What do these changes do?
Bumping version to 1.4.3 which includes:

Updates to NEWS
Updates to DESCRIPTION and README
Integrates updates since 1.4.3rc2. Notable ones:

Compatibility with uvloop
Expanded tox environments

Are there changes in behavior for the user?
Shouldn't be any.
Related issue number
Closes #322
Checklist

[x] I think the code is well written
[x] Unit tests for the changes exist
[x] GitHub CI all green
[x] Documentation reflects the changes
[x] Add a news fragment into the NEWS.rst file

All green, yay!
At around 2022-12-21T14:00 UTC if there are no blow ups and/or objections, I'm going to merge this and release 1.4.3-final.


The Carbon Dev Site Doesn't Work in IE

Describe the bug
I'm unable to view the dev site in Internet Explorer. It appears there is some type of syntax error that is preventing the page from loading. The page seems to work fine in Chrome, Firefox, and Edge
https://engineering.cerner.com/carbon-graphs/#/
Expected behavior
Be able to access the dev site in Internet Explorer.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser: Internet Explorer

This issue is actually caused by a dependency uplift in carbon-site-helpers. I've logged an issue to that project https://github.com/cerner/carbon-site-helpers/issues/32.
This should just be a dependency uplift once the above issue is fixed

:tada: This issue has been resolved in version 2.4.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Read default image creds for each request

Part of the point of being able to provide a docker config is to be
able to mount it from a volume, and thereby be able to update it on
the fly (e.g., with a sidecar).
But this won't work if it's read only at startup. So, just check it's
OK when we start, and otherwise read it every time we are asked for
credentials.

This should solve most of the ECR problem provided the user can refresh the creds themselves. Nice!

thanks @aaron7 :space_invader:


Errors during bytecode analysis should result in user-comprehensible messages (with source location)

I am running into this exception:
AttributeError: 'DataFlowAnalysis' object has no attribute 'op_LOAD_CLOSURE'

This isn't helpful to users. Instead, it would be useful to tell users

that the error is caused by an as-of-yet unsupported Python construct
which statement (Python source location) triggered this

such that they can attempt to change their code to work around the limitation.
(This is similar inspirit to https://github.com/numba/numba/issues/2112.)

https://github.com/numba/numba/pull/2251 improves the error messages substantially.

https://github.com/numba/numba/pull/2329 have addressed this.
Closing.


Insomnia Designer, Documentation: Repo folder should be .insomnia instead of .designer

Describe the bug

Note: Designer does not currently support repositories that contain files outside the root ".designer" folder.
In order to clone, the repository must exist and also contain the root .designer/ folder.
https://support.insomnia.rest/article/96-git-sync (accessed 29 April 2020, 21:59 ET)

However, when I look at my git repo:
> ls -a
.  ..  .git  .insomnia

And if I use the folder .designer instead (https://github.com/rmharrison/insomnia-designer-medium/tree/designer-folder-test)

Desktop (please complete the following information):

OS: Ubuntu 19.10
Installation Method: .deb
App Version<EMAIL_ADDRESS>
Root cause resolution
I couldn't find your support docs hosted in github. Host them in a repo alongside the code, so the support and code are better able to remain in sync.

Thanks for reporting this! I went ahead and updated the docs to change references of .designer to .insomnia


Setup repository labels

I find it useful to include priority, difficulty and type useful to organize issues. It's also good for welcoming contributors in the project (e.g. they can start with the simple issues to get some context on the project).
This is the setup that I've used for xcodeproj, what do you think @yonaskolb?

Personally I think it's a bit overkill for such a small project, but I have no problem with it. Sure, you can add them 😀

Done 😛