SLING-6053 SlingAuthenticator identifies wrong sibling node with AuthenticationInfo

https://issues.apache.org/jira/browse/SLING-6053

Added with commit:  2bd37e44f4bbdb0acab8354b960760b7ef3f97a7
https://github.com/apache/sling/commit/2bd37e44f4bbdb0acab8354b960760b7ef3f97a7


Adds an option to let users provide a method to customise auth requests

Fixes #13

Looks good in principle :+1: Might need to make a few tweaks to the tests and add one or two more but that should be simple enough. Will take a proper look at this as soon as I get some time! Thanks!

Cool. I also added error handling in sendAuthorisationRequest
It will now call handleAuthResponse only when the HTTP status code is 200-300 and there aren't any other server errors.

I still want this to be merged so will try and take a look at this this evening.


Drop positional scanning

Right now, Scan() helpers work with positional arguments. We should switch to column/field names.
Related to #144.

How should it works ? Can you add examples ?

I don't know. 😄 That v2 placeholder issue.


Module Request: hal_unisoc

This RFC issue is targeted towards adding Unisoc HAL libraries as a module to zephyr. Currently, there is only UWP5 HAL is available here: https://github.com/unisoc/hal_uwp5.git
This HAL library will be used by SoCs such as UWP5661 SoC in 96Boards IVY5661 board. The rest of the HALs for different family SoCs from Unisoc can also be hosted in this module in future!
Preferred repository/module name: hal_unisoc
Once the module is added, I'll open a PR for adding the UWP5661 SoC and IVY5661 board support.

tagging @galak @MaureenHelm @carlescufi

@Mani-Sadhasivam are you still waiting for this module? I can create the repo

@carlescufi Yes, please. I'm blocked.

https://github.com/zephyrproject-rtos/hal_unisoc


Patch InsecureTokenProvider's user parameter with missing field name

Description
The InsecureTokenProvider constructor requires a user field. This field extends the IUser type  with an additional name field.
This is already a field that InsecureTokenProvider expects, but the type definitions for the parameters just haven't been updated accordingly.
I have already opened a PR to update the documentations accordingly:

https://github.com/MicrosoftDocs/azure-docs/pull/100676

i'm a bit worried about this change. do all drivers set the name field? currently they are not required too, but change will make it seem like "name" is a required field for test code. this could lead to test code that doesn't match the production behavior.


FFDC update: Jounalctl update with keyword from failure test case name

Create snippet from journalctl search

[ ]  Extract snippet based on common keyword "failed"

[ ] Extract snippet based on keyword from test case name

[ ] Extract snippet from keyword from the snippet of the failed text

@ssombar assign this to you. Basically we need to create snippet based on the above logic.
Let know if you have question. Please ping me if you want to understand more.
This snippet should be added in ffdc.

This is already there in FFDC as part of the general.txt


Rename FreeRTOS-IoT-Libraries directory

Add LTS-Beta1 suffix to the existing FreeRTOS-IoT-Libraries directories to support differentiating them from C-SDK development branch libraries that will be added later
Description
Rename the following 2 directories as:

FreeRTOS-Plus/Source/FreeRTOS-IoT-Libraries -> FreeRTOS-Plus/Source/FreeRTOS-IoT-Libraries-LTS-Beta1
FreeRTOS-Plus/Demo/FreeRTOS_IoT_Libraries -> FreeRTOS-Plus/Demo/FreeRTOS-IoT-Libraries-LTS-Beta1

Test Steps
Using custom jobs to verify that demos are building
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks

/bot run checks

Build failing due to an issue in the OTA demo file (aws_iot_ota_update_demo.c) which is unrelated to the changes in this PR.
Fix will be created in a separate PR.


Modrinth modpack import support

It would be nice to be able to import Modrinth modpacks, from either an already downloaded file or a URL. I know most Modrinth packs are on GitHub as well, but it would still be a nice feature for packwiz.

It's a duplicate. Didn't see the other version previously.


When hash has a single quote, Firefox always sees current fragment and new fragment as different

When the hash contains a single quote character, Firefox (version 20.0 on Ubuntu) will encode it as %27 in the string window.location.href.  This variable provides the value of current when the function checkUrl() is run.  However the value of this.fragment  to which it is compared is got from whatever is passed to Backbone.router.navigate().  If we encode the hash that is passed to this function with encodeURIComponent() (or even encodeURI()), even Firefox will not encode the single quote to %27.  So the variables this.fragment and current will always be different.
Solution: Backbone should decode the URI components before comparing them because
decodeURIComponent("%27") = "'";
encodeURIComponent("'") = "'";

I propose:
1439c1439,1441
<       if (current === this.fragment && this.iframe) {

---
>       var decodedCurrent = decodeURIComponent(current);
>       var decodedFragment = decodeURIComponent(this.fragment);
>       if (decodedCurrent === decodedFragment && this.iframe) {
1442c1444
<       if (current === this.fragment) return false;

---
>       if (decodedCurrent === decodedFragment) return false;

@braddunbar


Vertical responsiveness

aim of this is to mitigate all the manual fixing we have to male stuff fit nicely inside 13" macbooks etc, and is based on (& works directly with) the @responsive-font principles.
3 key parts:

2x base css variables, 1 handling font, another elements (this might be overkill for a starter kit -- we needed this option for our latest project). 3 associated height breakpoints with these variables. see base.css
.segment has vertical scaling based on the 3 breakpoints.
a utility mixin v-scale; a shorthand for specific scaling of elements. i.e:

.foo {
  @include v-scale(padding-bottom, 600px);
}

@geirlandro @k80 @mdmagnusson wanna take a look at this? have made some updates based on feedback, but @k80 i am struggling for a naming convention! any thoughts on that would be very helpful.
I also removed the copy mixin as I am not sure how useful that is in practice, & emptied out the heading & subheading mixins as i think they should be written from scratch per project. I realise this probably should have gone in another PR, but sue me.

@k80 updated unitless baseline  & renamed the v-scale mixin. looking OK?


Correction for raw affiliation Elsa, Research Group for Environmental Lifecycle and Sustainability Assessment, Montpellier, France; ITAP, Univ Montpellier, INRAE, Institut Agro, Montpellier, France

Correction needed for raw affiliation Elsa, Research Group for Environmental Lifecycle and Sustainability Assessment, Montpellier, France; ITAP, Univ Montpellier, INRAE, Institut Agro, Montpellier, France
raw_affiliation_name: Elsa, Research Group for Environmental Lifecycle and Sustainability Assessment, Montpellier, France; ITAP, Univ Montpellier, INRAE, Institut Agro, Montpellier, France
new_rors: 003vg9w96;03573dx38;03rnk6m14;051escj72;00ftatp57
previous_rors: 003vg9w96;03573dx38;03rnk6m14;051escj72
works_examples: W4390811469
contact: 55ffd211ddec5bad06a3fa946b70fae3:fd39c115d65d0e57388ecc597701149cda7e @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


fix serve.model_path usage

the config on disk has config.model and serve.model_path.
This commit fixes two things:

when --model-path is specified in ilab serve, the config on disk is updated to have this path
ilab chat uses config.serve.model_path as opposed to config.chat.model so now we will always chat by default with the same model that is being served

resolved #880

I can't seem to re-open this... anyone else have the button?

@cdoern you might need to delete/recreate your fork, there's some guidance in Slack for this


RateLimitError

Describe the bug
I am receiving a RateLimitError meaning that the number of tokens is too high for my OpenAI account.
When using gpt-4o-mini:
Exception has occurred: RateLimitError
Error code: 429 - {'error': {'message': 'Request too large for gpt-4o-mini in organization org-amMe on tokens per min (TPM): Limit 200000, Requested 395648. The input or output tokens must be reduced in order to run successfully. Visit https://platform.openai.com/account/rate-limits to learn more.', 'type': 'tokens', 'param': None, 'code': 'rate_limit_exceeded'}}
It is reaching the tokens per minute while requesting almost 400k tokens per minute. The issue with this is that one would need Tier2 in openai API to be able to use this lib.
Expected behavior
I would expect to be able to run this lib even with the lowest tier available on OpenAI. It should be slower yes, but still run.

Thanks for reporting this.
This adds more fuel to the fire of our discontent towards LangChain. It's a heavy dependency, it's slow to load and execute, yet we have to manually handle many low-level aspects (rate limits, context window sizes and chunking, ...).
I was having the same problem while testing the Mistral integration a few weeks ago. Their token rate limit is generous, but the API rejects individual requests if they come in at a rate of more than one per second. The fix for time rate limits is trivial through langchain, but the fix for token limits seems to be a little more complex.
We'll handle this as soon as the fixes for #593 and #594 will be published.

Also seeing it. We are not using very much of the rate limit at all so the error is confusing.
Also it's reporting a strange org ID that I don't recognize in the error.
I suspect this is an issue with not adding project and organization to the client connection.

Proposed solution:
stateDiagram-v2
    [*] --> check_rate_limit

    state limit_rate_split <<fork>>
    check_rate_limit --> not_available : dictionary miss
    check_rate_limit --> limit_rate_split : dictionary hit (by provider)

    limit_rate_split --> limit_by_model : specific model available
    limit_rate_split --> limit_by_provider : only provider-wide info

    state limit_rate_join <<join>>
    limit_by_model --> limit_rate_join
    limit_by_provider --> limit_rate_join

    not_available --> [*] : do not put limit
    limit_rate_join --> [*] : impose limit

    note left of check_rate_limit
    rate_limit : dict
    - base_limit
    - models
    end note

The rate limit dictionary will look something like this:
rate_limits = {
    "provider1": {
        "base_limit" : {
            "time_limit": 1,
            "token_limit": 200000
        },
       "models": {
           "model1" : {
               "time_limit": 0.3,
               "token_limit": 300000
            },
            "model2" : {
               "time_limit": 0.5,
               "token_limit": 200000
            },
    }
}

On top of this, I might add a generic exponential backoff retry to all models

hi, please update to the new beta


Question about Text data in MoNuSeg and request trained weight

Hello, I have some question and request.

In the MoNuSeg dataset, how was the text data utilized?
Could you provide a trained weight?

thanks.

@chunmeifeng
Hello, your work is impressive.
Will you be releasing a tutorial for its operation in the future?
Thank you very much！！！


Support lua 5.3 integer representation

See #22 . The origin pr mix some other feature.

Ping @mpx. This looks good. Normally we cannot expect the initial portion of a string accepted by strtod can also be accepted by strtoll (Infinity, Inf, NaN, nan(222), etc). However, the form accepted by RFC 8259 is much narrower and this patch should work.


Two versions of the labelled text area.

This is a step towards fixing issue #57.
In TeX.html, we add an aria-label. This way the textarea is announced and the original description is also reachable from the screen reader.
In MathML.html, we turn the description into a label. This takes it out of the normal flow for the screenreader it will only be read twice if the entire table is selected.
Personally I think the latter is good, but have a look.

Unless there any objections I'd go with the version implemented in MathML.html.

I'm OK with either one.  I haven't been doing the testing with the screen readers, so don't know which is more effective or more widely usable.


Better XPC release/retain usage, plist handling, omnibox usability

Remove all xpc_retain calls from dictionary + query code
Call xpc_retain whenever making a new XPCObject
Allow : and / switches during filtering
Don't write plist if no changes (as it sits there is always validation before write, but don't do it unless we need to, esp since plist::Value implements PartialEq)

Update:
The always call xpc_retain scheme we are testing here is causing memory to leak (try dumpstate where shmems get leaked, a few megs at a time 😱 ). I need to explicitly determine what the criteria are for retaining and releasing. There are two cases:

Usage in an Obj-C block
Usage in a dictionary about to be dropped (which drops its children ??)

I found a Fortinet tech article that has some detailed RE of XPC objects with ref counts -- I will see if there is anything that can be rigged there, but drowning with work for the next day or two: https://www.fortinet.com/blog/threat-research/a-look-into-xpc-internals--reverse-engineering-the-xpc-objects

Yay it seems to be working:


[cls] or pooled embedding?

When i using event_cls to access a classification, the predicted labels come from cls or pooled embedding? If you can point that part of code to me, would be great helpful to me. Thanks.

In most cases, [CLS] token embedding and pooled embedding are the same.
But some transformer model outputs don't have pooler outputs. In that case, pooler outputs would be token-wise average embedding.
https://github.com/JayYip/m3tl/blob/master/m3tl/modeling.py#L54
https://github.com/JayYip/m3tl/blob/master/m3tl/problem_types/cls.py#L38


Preview fix

Places preview view fixed top and makes it stay there.

My pull request is probably incomplete, as you can have bar at the bottom as well. You might better just look at the code and insert your own code for it. In conclusion, don't merge, add your own.


fix: add missing dependency for building on fedora

This adds a missing dependency for building on Fedora 41. Without this package I got the following cmake error:
-- Configuring done (1.0s)
CMake Error in src/CMakeLists.txt:
  Imported target "Qt6::WidgetsPrivate" includes non-existent path

    "/usr/include/qt6/QtWidgets/6.8.0"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.

CMake Error in src/CMakeLists.txt:
  Imported target "Qt6::WidgetsPrivate" includes non-existent path

    "/usr/include/qt6/QtWidgets/6.8.0"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.

-- Generating done (0.1s)
CMake Generate step failed.  Build files cannot be regenerated correctly.

This error does not pop up and cmake configures correctly if qt6-qtbase-private-devel is installed.

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


Add Menu page

Fixed #17
design: https://xd.adobe.com/view/126b5014-bff3-428d-a186-1a5a2d2b1e3b-4738/
Menu to start the game (may gets 2 more buttons later, if I implement the highscore)

@manuelsanchez2 thanks for your review 💌
what do you mean with "refactor the two existing components". In which way? ❔ 🤔 💭

I mean what Jonas Imm suggested in my pull request
https://github.com/manuelsanchez2/doicheliving-app/pull/41
Try to set the two components in the component folder :)


Update dependencies for security fix; Match DELETE case insensitively

What was the dependency that needed the security fix?

rack and ffi: https://github.com/brightcove/brine/network/alerts


VM images at Management Group level

It appears the vm images parameters has to be from one of the subscriptions.  I am trying to implement a policy at management group level ( that has multiple subscriptions) and would like to define the image with no dependency on subscription. Is this possible?

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

ID: f6b44c4f-dc45-7de8-1234-3c581c8deb57
Version Independent ID: 055a02f5-2f18-4398-6c3c-80a408519193
Content: Sample - Approved VM images - Azure Policy
Content Source: articles/governance/policy/samples/allowed-custom-images.md
Service: azure-policy
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

HI @medavamshi Thank you for your feedback! We will review and update as appropriate.

@medavamshi Shared image galleries can help you.
We can create a shared image gallery in a subscription and then share it with the other subscriptions.
In the policy we can give only the subscription id where the shared image gallery resides.
I didn't try it out, But this can help.
Another solution is to provide the image id urls from all the subscriptions and add it to the policy.
Try this out and let me know if you face any challenges.

Interesting about shared galleries. I haven't tried that one before. I thought about last option but was wondering if there is an easy way at management group level. Thanks for sharing about shared image gallery. I will surely try that. Appreciate your response.

Shared gallery images has to be custom or can they be one of the images from MS?  I guess I will read the blog first about shared gallery.

Shared image galleries  are for custom images only. Marketplace images are already available to subscriptions.

ok thank you.  So it appears i have to allow images from all subscriptions in the policy for market place images.

Providing all the images from marketplace which a subscription requires is difficult.
I think  you can have * also in the image ids.
With that you can whitelist a publisher with one entry.  I am sure that providing wildcard is supported for a single value.
But here we need to specify multiple providers in a array. I will verify for array and let you know.

@medavamshi Did you had a chance to get this working

I haven't tested this one yet .  a wildcard isn't an option if we have to allow only few images.  Only option i could see is included all the 4 subscriptions and allow each image on each subscription. I will try this next week

@medavamshi Try that out and let me know.
Since this issue dont need a document update, I will close this issue.
You can post your further questions in this MSDN forum.


Object with three.js WebGLRenderer importing error

jest version: 20.0.4
node version: 8.0.0
yarn version: 0.21.3
npm version: 5.0.3

Do you want to request a feature or report a bug?
It may be a bug.
What is the current behavior?
I created a class with a render function and set a Three.js renderer in it. like below:
class Netjsongraph {
  render () {
    const renderer = new THREE.WebGLRenderer({
      alpha: true,
      antialias: true   // perform antialiasing
    });
}

https://github.com/netjson/netjsongraph.js/blob/dev/src/netjsongraph.three.js#L174-L177
testing code:
import Netjsongraph from '../src/netjsongraph.three.js';

test('Module importing', () => {
  expect(Netjsongraph).toBeDefined();
  expect(new Netjsongraph()).toBeInstanceOf(Netjsongraph);
});

there is no error when run jest.
What is the expected behavior?
I want to abstract this property to a default value of this class. like below:
const defaults = {
  renderer: new THREE.WebGLRenderer({
    alpha: true,
    antialias: true   // perform antialiasing
  })
};

class Netjsongraph {
   constructor () {
      this.renderer = defaults.renderer
   }
}

https://github.com/netjson/netjsongraph.js/blob/0d04f6912bbae2a9f6597eb1157cb84255ab6c8a/src/netjsongraph.three.js#L36-L39
but there is a error occur when I run jest (include jest --no-cache, jest --env=jsdom):
 FAIL  tests/api.spec.js
  ● Test suite failed to run

    TypeError: Cannot read property 'getExtension' of null

      at Object.get (node_modules/three/build/three.js:19663:21)
      at new WebGLRenderer (node_modules/three/build/three.js:20096:14)
      at Object.<anonymous> (src/netjsongraph.three.js:36:13)
      at Object.<anonymous> (tests/api.spec.js:1:128)
          at <anonymous>

    .....

  console.log node_modules/three/build/three.js:19874
    THREE.WebGLRenderer 85

  console.error node_modules/three/build/three.js:20090
    THREE.WebGLRenderer: Error creating WebGL context.

This might because there is no WebGL context in test environment, So how to fix it?

refrence: https://github.com/netjson/netjsongraph.js/commit/552cceb41e1bff60a4d5e109de1ac00541d8f4cf#commitcomment-22709412

I believe this is more like a feature request.
The jsdom environment does not have webgl context. If your tests are focus on scripts rendering data rather than other scripts, you better chose those test framework that run in browser.
So you need to mock those functions that need render context or send data to render context, and focus on other parts of scripts.
Just checked three.js, they don't have test for render scripts either.

why close?

+1

+1

I have the same problem too..


RSS HTTP 403

When periodically fetching the RSS feeds for a user's deviations, I sometimes get a 403.
What would be the possible cause of this and how can it be avoided?
Thanks in advance.

Hi @frobinsonj,
How quickly are you accessing the RSS feeds? You may be hitting rate limits and need to slow down your fetching.

Shouldn't a rate limit properly return a 429 and not a 403?
Regardless, I'm having the same issue.
Seems to be like rolling the dice on either getting an error or getting a feed, checking them every 3 minutes, as I figured 1 or 2 minutes would be too much.

It is quite common to utilise a 403 for rate limit errors as the service is forbidding your service request. I'll talk to some other team members to confirm this is the case in this example.
To avoid this, we suggest moving to the full API system which has this same data in a better format with authentication applied.

Could either of you please share the full error or a screenshot of this so I can pass it along to the correct team member for more debugging?

This appears to be an issue with us expecting to receive a 429 response instead of the 403. I believe changes on our end have fixed the issue we were experiencing. Thanks for your response.


gitAndTools.git-interactive-rebase-tool: remove patch

Motivation for this change
Removes patch to disable tests, instead runs them in single threaded
mode.
See discussion in MitMaro/git-interactive-rebase-tool#172
Things done

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

[ ] NixOS
[ ] macOS
[x] 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/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@masaeedu thank you for following up on this.  I've changed the checkPhase with checkFlagsArray and enabled it for darwin, I hope you don't mind.

@marsam Thanks! Could you clarify what the libiconv, Security thing does? I'm unfortunately not very familiar with how stuff for Mac works.

Could you clarify what the libiconv, Security thing does?

sure, libiconv is an Apple fork of gnu's libiconv and provides iconv() implementation for character set conversion.  Security is the darwin API for securing data. IIUC both are required by the libgit2 crate on darwin


Add rack deflater

https://github.com/JumpStartGeorgia/Bootstrap-Starter/blob/master/config/application.rb

Assets are already being zipped (by Nginx, maybe?) ---> no need for Rack deflater


Limited error trace

Use case
We're using a custom mixin (deprecate($version)) in vendor/deprecate.scss to tell us where to look at when a piece of code is deprecated.
Unfortunately, node-sass doesn't give us a full trace of the error and we can't trace where the error originated from.
Ruby Sass
Very useful output, which tells us where to look (ui/components/buttons/flavors/base/index.scss):
Error: Deprecated code was found: please remove it to continue.
        on line 129 of ui/vendor/deprecate.scss, in `deprecate'
        from line 74 of ui/components/buttons/flavors/base/index.scss
        from line 26 of ui/components/index.scss
        from line 28 of ui/index.scss
  Use --trace for backtrace.

Node Sass
Not so useful, outputs a JSON object with only one level of depth.
No way to guess that we should look at ui/components/buttons/flavors/base/index.scss.
{
  "formatted": "Error: Deprecated code was found: please remove it to continue.\n        on line 129 of ui/vendor/deprecate.scss\n>>     @error 'Deprecated code was found: please remove it to continue.';\n   ----^\n",
  "message": "Deprecated code was found: please remove it to continue.",
  "column": 5,
  "line": 129,
  "file": "/Users/kdeloumeauprigent/workspace/salesforce/design-system-internal/ui/vendor/deprecate.scss",
  "status": 1
}

Temporary workaround
Until we get better information from @error, use @warn instead. It gives the necessary amount of info:
WARNING: Deprecated code was found: please remove it to continue.
    on line 129 of ui/vendor/deprecate.scss
    from line 30 of ui/utilities/visibility/flavors/collapsed-expanded/index.scss

This situation may improve with the next release

@kaelig this may be fixed in the upcoming beta. Subscribe to #1349 for updates on that release.

Closing this as I think it was fixed in the last version.

Sorry, it's not fixed. See the linked issue above.


OCPBUGS-42864: Add sample kickstart files to microshift-release-info RPM and document usage

/jira refresh

/test ?

/test test-rpm verify

/test images

/lgtm

The failures are not related to the current PR changes.
/override ci/prow/e2e-aws-tests ci/prow/e2e-aws-tests-arm

/override ci/prow/e2e-aws-tests-arm


"Unable to perform checkout" when creating zarf package for custom helm chart

Environment
Device and OS: 2019 MacBook Pro i9 16gb RAM
App version: 0.19.5
Kubernetes distro being used: minikube
Other:
Steps to reproduce

zarf package create

Expected result
A created Zarf package.
Actual Result
zarf package create -l trace
...
DEBUG   Compressing objects: 100% (50/50), done.
└ (/home/runner/work/zarf/zarf/src/internal/message/spinner.go:29)
DEBUG   Total 1544 (delta 56), reused 80 (delta 45), pack-reused 1446
└ (/home/runner/work/zarf/zarf/src/internal/message/spinner.go:29)
DEBUG   Git checkout /var/folders/q7/8gxmyqr11wdd0v1j0jktx8lmwx1zpl/T/zarf-3432438332
└ (/home/runner/work/zarf/zarf/src/internal/git/checkout.go:76)

DEBUG   reference not found
└ (/home/runner/work/zarf/zarf/src/internal/git/checkout.go:93)
   ERROR:  Unable to perform checkout
└ (/home/runner/work/zarf/zarf/src/internal/git/checkout.go:93)

Visual Proof (screenshots, videos, text, etc)

Additional Context
This is for a custom chart for my project that is hosted on a private GitLab repo. It is just one component with the helm chart, with the url pointed to the repo. gitPath is set to the chart path. I can run all of the Zarf examples perfectly fine, so I'm not certain why this is not working for me. Additionally, I can physically go to the location Zarf is trying to go to and manually run git checkout fine as well. I also can add the repo as a standalone "repo" component and that gets packaged fine too.
EDIT: Realized I didn't tag the repo I was pulling from. That fixed it.

Thanks you for updating this, sorry we're at 2022 OSS NA right now and slow to reply. I think Zarf should still provide a cleaner validation for users when this happens, what do you think @YrrepNoj @RothAndrew?


[FIXED] [BUG] .SMA file regression error

Is there an existing issue for this?

[X] I have searched the existing issues and none matched.

Operating System
windows 10
CPU
i7
GPU
3070
Storage
ssd
Game Version
5.0.0-041
Game Mode
pump
Theme
default theme.
Describe the problem
.sma song files are not loaded using this version 0.5 alpha, everything else is loaded.
The songs are not visible as if they never were loaded.
Things done:

[x] deleted cache
[X] Check the log (it does not show any error)
[X] Check with a different file. It happens the same with different files
[X] check in a different computer, It happens the same in different computers
[X] Check with a different version. SMA songs are loaded correctly in 0.4.19 LTS

it is the crashinfo:
created log at: Sun Jun 04 22:20:17 2023
Compiled 20221031 @ 22:03:57 (build 438801a9b6) (OS Win 10 64Bit)
FileSink shutdown at: 22:20:50 763005

Describe what should happen
.sma songs should be loaded.
Relevant Log output
created log at: Sun Jun 04 22:14:32 2023
[Time]		[Level]		[Thread]	[Log]
22:14:32	TRACE		Main Thread
...
22:14:32	TRACE		SongThread(1)	Attempting to load  53 songs from "PIU_20th"
22:14:32	TRACE		SongThread(0)	Attempting to load  0 songs from "AdditionalSongs"
22:14:32	TRACE		SongThread(0)	Loaded 0 songs from "AdditionalSongs"
22:14:32	TRACE		SongThread(1)	Song '/Songs/PIU_20th/1949/' points to a music file that doesn't exist, found music file '1949.mp3'
22:14:32	TRACE		SongThread(1)	Song::SaveToSSCFile('Cache/Songs/Songs_PIU_20th_1949.ofcache')
22:14:32	TRACE		SongThread(1)	Song '/Songs/PIU_20th/8 6/' points to a music file that doesn't exist, found music file '8 6.mp3'

I.. may hve broken them when i was fixing the parsers for windows 11, i'll ensure they are working for 042!
Thanks for the catch and report

Fixed in 042

You are in pump game mode right? I can load .sma fine on my windows system.
I'll reopen this and double check what it's doing.
Thanks for letting me know it's still being annoying.

are you able to join our discord to do some testing before we release 043?


Changes 3

Tasks

[x] /docs/ page not found, should go to ./
[x] Anything with /docs/ is broken
[x] Atmosphere pro spelling
[x] Remove app from atDude
[x] Light mode atPlatform image
[x] Atsign.com on the right

Thanks for this @JeremyTubongbanua
One small thing: the content under content/ does not need to be moved to content_dev/.

Yeah ahaha I realized.. I will move it back


uefi : fix broken build due to missing edk2 submodule

This change updates EDK2 to stable202408.01. This is a minor update with only one additional commit compared the previous version which fixes missing subhook submodule issue by switching to TianoCore mirror.
https://github.com/tianocore/edk2/compare/edk2-stable202408...edk2-stable202408.01
For the curios, Adding a patch to fix the issue is not straightforward because the docker ADD  command clones the repository and initializes the submodules at once (before applying any patches).

Hm... In theory, the tests should have success, then... And they are still red =(

Hm... In theory, the tests should have success, then... And they are still red =(

This has nothing to do with the EVE stucking at boot in Eden, this just fixes building EDK2 from source which is broken (even old versions are broken).

@shjala but we still have to update the hashes in the dependent Dockerfiles...


docs: add QRL docs.

I've made some typo and grammatical suggestions in mhevery/qwik#1
I also made a couple of inline comments above where it was either a question of style or I didn't understand your intent.

@jimt Thank you for your improvments. I have incorporated them into the PR.


I wish /docs/user-guide/compute-resources/ had a valid link to Resource QoS (broken link to https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/resource-qos.md)

I wish /docs/user-guide/compute-resources/ had a valid link to Resource QoS (broken link to https://github.com/kubernetes/kubernetes/blob/master/docs/proposals/resource-qos.md)

Also broken from http://kubernetes.io/docs/user-guide/production-pods


Dependency Injection / Controller Factory in Sails

I came across sails recently and found it to be an awesome library. However I could not able to find any way to bootstrap dependency injection into sails controllers. The main reason being that I could not find a way to elegently add custom behavior to the point where the controllers are created. In other words, I wasn't able to find a proper application seam with which I could bootstrap DI.
What I expect is some sort of a controller factory module which news up the controller modules. This controller factory would by default have a method such as createController(path) i.e.
module.exports = function controllerFactory {
  this.createController = function(controllerPath){
    var ControllerClass = require(controllerPath);
    return new ControllerClass();
  }
}

Now if sails allowed this function to be overridden in some way, I could use a DI container to get an instance of the controller with all dependencies injected via constructor injection instead of the default behavior like so
module.exports = function controllerFactory {
  this.createController = function(controllerPath){
    var controller = iocContainer.getInstance(controllerPath); //assume controller is a named dependency registered in the iocContainer using the path.
    return controller;
  }
}

Any services could also be injected into controllers (auto wired) too. This would make the controllers and services more testable since all dependencies can now be mocked in unit tests.
Is there no way to do this with the current sails setup. I'm also looking at hooks though it feels more of a hack to bootstrap DI that way. Am I missing something?
P.S. I'm a great fan of intravenous as a DI mechanism for javascript.
http://www.royjacobs.org/intravenous/
Any earlier experiences on bootstrapping DI with sails would be greatly appreciated.

Another fan of intravenous here!
+1

+1

https://github.com/balderdashy/sails/issues/2178

. I'm also looking at hooks though it feels more of a hack to bootstrap DI that way.   Am I missing something?

@harindaka Nope!  You're right on target.  Sails core is implemented almost entirely as hooks-- it's the recommended way to go about customizations like this.  When I've done this sort of thing in the past (usually on the front-end, since personally I'm a fan of CJS), I've implemented it by first building a dependency graph, then using that graph to wire up actual references.
These days, we use machinepacks in lieu of services almost exclusively (or sometimes as services, if we're feeling lazy :p).
cc @vromanchakvakoms @jrosseel @RWOverdijk

One more thing to add, in case this helps for your hook, @harindaka:  http://requirejs.org/docs/node.html


Bug: LualineRenameTab has stopped working?

Self Checks

[x] I'm using the latest lualine.
[x] I didn't find the issue in exsisting issues or prs.

How to reproduce the problem

I think just install the Plugin and try to use :LualineRenameTab
Expected behaviour
Up until this morning when I did a PlugUpdate, this command would rename my tab
Actual behaviour
E492: Not an editor command: LualineRenameTab main

nope, this is a me problem. Big apologies.

Can you please explain how you fixed this? I'm getting the "not an editor command" error when I type :LualineRenameTab as well. Plugin was installed under LunarVim config.

Did you guys ever get to the bottom of this?


'Connection aborted.', ConnectionResetError(54, 'Connection reset by peer'

How can I solve this problem? I've been struggling for a long time and can't find a solution. Please help me     thanks!!!

macOS 13.2.1 / M1

Python version 3.11.3


 That is, whenever two TLA+ values a and b of the same type have to be compared, the rewriter produces an SMT constraint a = b <=> ... that encodes structural equality of a and b.
Another approach would be to introduce axiomatic equality that is using quantifiers. That, however, requires a major change in the encoding.

This could be implemented in a completely different encoding


Support retrieving default voice

Why
Add in support for determining the default Voice used after calling the library's getAvailableVoicesAsync method.
How
I tried to follow the existing spec for WebVoice which simply adds in a property called isDefault to the voice object. Because isDefault will now supported across all platforms (Web, iOS, and Android), I also updated the Typescript types to reflect this change by moving the property from WebVoice to Voice.
Test Plan
Tested in the Paper mobile app and confirmed isDefault is set as expected.
Checklist

[ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
[ ] Conforms with the Documentation Writing Style Guide
[ ] This diff will work correctly for expo prebuild & EAS Build (eg: updated a module plugin).

@gabrieljoelc can you clarify how I should bump the package version? it seems like I should do that on the publish-fork branch after I merge this into main?


[WIP] Use spawner processes to speed up spawning

SCons tends to grow large in RAM usage. It's expensive for large processes to fork().
The best solution would be vfork(), but CPython doesn't support it properly (see this issue for latest status).
Until CPython has it (and in order to support older versions as well), I added the --process-spawner SCons options, which lets each Worker create its private "spawner" process. Further exec_subprocess() calls by that Worker will send the Popen requests to the spawner via simple IPC (pickle messages over stdin/stdout), and the spawner will Popen the requested process, wait for its result and send it back to the Worker.
Overall it's quite simple, yet for RAM-heavy SCons it adds a huge speedup.
Discussed (with some performance benching) in https://pairlist4.pair.net/pipermail/scons-users/2020-June/008286.html and https://github.com/SCons/scons/pull/3703 (specifically this comment, this one and this)
Tasks:

[x] Take a look at replacing the IPC with mutltiprocessing module
[x] Pipe back exceptions raised in the spawner (and add a test for that)
[x] Run a full-build benchmark, on a real project (and not partial builds of MongoDB / SCons artificial benchmarks)
[ ] Write tests (or: modify some existing tests to use --process-wrapper)
[x] Make sure all spawner extra code is only executed if on POSIX

Contributor Checklist:
I still have to finish these (I just want an ack from one of you the maintainers that this looks okay)

[ ] I have created a new test or updated the unit tests to cover the new/changed functionality.
[ ] I have updated CHANGES.txt (and read the README.rst)
[ ] I have updated the appropriate documentation

Please fix sider issues.
Is this PR in your opinion ready to merge, or still a work in progress?

Is this PR in your opinion ready to merge, or still a work in progress?

The concept is not going to change much. I am planning to add a few more features before I think it's ready to merge, though. I'll update the description with tasks. I'll complete them further on this week.

About multiprocessing: I created a modified version that uses multiprocessing.Pool with the spawn context (so workers are not heavy forks of the main SCons Python process, but lightweight scripts). You can see it here. According to my tests, it performs a bit worse (benchmarks of perl scons_bld.pl builds, default settings).
multiprocessing

real    0m50.058s
user    2m38.115s
sys     1m0.131s

current version

real    0m45.071s
user    2m32.627s
sys      0m55.708s

Given these results I'll stick with the plain version.

I benched the build of Godot:
godot with spawner

real    4m52.019s
user    32m16.345s
sys     2m14.654s

godot master

real    4m53.794s
user    32m13.860s
sys     2m27.330s

This amounts to a tiny 0.5% improvement (user+sys time). I wasn't expecting to see much because Godot's SCons doesn't use too much RAM (starts at 60MB, climbs up to 150MB). Impact becomes more obvious as RAM usages grows.

I'm not seeing any compelling results above.
Do you have any examples where you have notable improvements?
Also, probably good to show peak memory usage as that's the main stated reason to use vfork?

Do you have any examples where you have notable improvements?

I don't have an open-source example with heavy memory consumption at hand (if you know of any project that might fit, please let me know and I'll try on it).
I was thinking this week to take a more accurate measuring: the problem with a simple time is that it also takes into account the time spent by GCC and all other tools executed by SCons. What we really want to measure here is the time of SCons only (and when using the process spawner, the time of SCons + all spawner processes). This will give the percentage of improvement over current SCons, which is really the metric we seek.
Obviously, if that metric shows no notable improvement, then it's not worth it. Though, like I said, for projects with heavy memory consumption, this is proved useful (I can share some results of Godot build where I forced SCons to take, say, 500MB. Difference becomes notable)

Did you try --debug=time ?

Did you try --debug=time ?

Nope, cool! Will try that, thanks for the tip.

Okay, I tried with --debug=time, but I didn't completely understand how it accounts times between SCons and executed commands, and anyway, it is based on clock time and not CPU time.
So I tried the following - I added this small snippet:
import resource
r = resource.getrusage(resource.RUSAGE_SELF)
print("main", r.ru_utime, r.ru_stime, file=sys.stderr)

to SCons' main() and to the spawner.py code - right before they exit. This should give accurate accounting for CPU time for the SCons process and the child spawners.
Trying again with Godot. On this branch without --process-spawner, the result is: main 34.841785 8.357901, so a total of 43.07 CPU seconds for SCons.
On this branch with --process-spawner, the result is main 33.671169 1.498248 plus 8 spawner processes (I used -j 8):
spawner 0.095034 0.14987699999999998
spawner 0.142122 0.13424999999999998
spawner 0.103977 0.096798
spawner 0.091567 0.122125
spawner 0.12446299999999999 0.111069
spawner 0.084918 0.127081
spawner 0.107025 0.121252
spawner 0.083006 0.162874

that account to 1.85 seconds. So the total is 37.02.
I admit this doesn't look notable comparing to the total build time for Godot (which is about 2k CPU seconds) but it is a notable portion of the SCons time (about 15%), as and as SCons' time grows, this part grows as well. With SCons at 700MB~ ,the --process-spawner version cuts by half the SCons time (it remains at 37-38 seconds, while the standard version climbs to 75-80).

@Jongy - The MongoDB build might be another one to try if you want some additional data points. We too would like to see SCons be faster.

@bdbaddog What do you think about these results? There is no huge effect on the build time, but that's as far as it could go, since SCons itself is only a small portion of that time. But the improvement in SCons-only time is definitely notable, and like I said this is aimed at projects consuming more RAM, where this change is much more effective.
Also you can see in the this comment - when SCons is under stress, this change has positive effects.
Waiting for your approval (or disapproval :) before I go on with this.

Curious how much RAM are you seeing SCons take.
I've seen cmake take > 5G of RAM..
There's chances that other things you're doing in your build are causing larger than necessary scons footprints.

IIRC it was about 1.5G, but I don't have access to the code at the moment, so can't verify. It's indeed very likely the build doesn't really need those 1.5G - like every other program, it can be optimized. Nonetheless, this idea proposed here had notable effects on the build time, at practically zero cost.

@grossag - Thanks for they update and keeping an eye on developments related to this PR. :)

Just FYI as of Python 3.10 Linux Python's subprocessing module uses vfork() instead of fork() unless the caller specifically disables it. So this pull request may not be needed anymore.

Yup, as noted in the description - tracking ticket was https://bugs.python.org/issue35823 and it got merged in 3.10. This PR is far less relevant now

@Jongy - so safe to say the recommended fix now is to use python 3.10+? If so, let's close this PR.

@Jongy - so safe to say the recommended fix now is to use python 3.10+? If so, let's close this PR.

Yes. It will cover the SCons case (that is, the subprocess usage of SCons).
I'll close the PR, I see no need to introduce the extra complexity, given that people can just upgrade to 3.10

I'm generally fine with this resolution, too, but... it's not true that everyone can just upgrade to 3.10+. We keep hearing from people who can't "because" (usually an IT/Security thing restricting from using a Python not provided by the Linux distribution in question).  We also need to get off using os.spawnve on Windows, but that's got its own trackers...

@Jongy - One question for you. On the system(s) where the spawner was making a notable difference, how much RAM did the system(s) have?

@Jongy - One question for you. On the system(s) where the spawner was making a notable difference, how much RAM did the system(s) have?

16GB. However the physical RAM size doesn't matter, what matters is the amount of pages in the pagetables in the app - which is the RSS of the app divided by page size. Using hugepages, for examples, will very likely reduce the slowdown drastically. RSS I described here.


feature profilev2 distinguish Sink and Operator in pipelineX

Proposed changes
    4651:VHASH  JOIN
    |    join  op:  INNER  JOIN(BROADCAST)[]
    |    equal  join  conjunct:  lo_orderdate  =  d_datekey
    |    runtime  filters:  RF002[in_or_bloom]  <-  d_datekey(-1/0/2097152)
    |    cardinality=600,037,902
    |    vec  output  tuple  id:  11
    |    vIntermediate  tuple  ids:  10
    |    hash  output  slot  ids:  4  75  77
    |    Operator:
    |        BlocksReturned:  1.92K  (1920)
    |        CloseTime:  avg  19.587us,  max  26.59us,  min  15.441us
    |        OpenTime:  avg  66.501us,  max  75.926us,  min  61.871us
    |        ProjectionTime:  avg  5.484ms,  max  6.315ms,  min  4.754ms
    |        RowsReturned:  4.7908M  (4790800)
    |        TotalTime:  avg  86.690us,  max  101.781us,  min  77.842us
    |    Sink:
    |        InputRows:  2.556K  (2556)
    |        OpenTime:  avg  147.864us,  max  185.534us,  min  132.322us
    |        TotalTime:  avg  360.5us,  max  1.158ms,  min  195.150us
    |
    |----4648:VEXCHANGE
    |              offset:  0
    |              Operator:
    |                  BlocksReturned:  1
    |                  CloseTime:  avg  11.267us,  max  20.244us,  min  6.306us
    |                  OpenTime:  avg  67.221us,  max  73.599us,  min  62.633us
    |                  RowsReturned:  2.556K  (2556)
    |                  TotalTime:  avg  81.920us,  max  108.185us,  min  74.641us
    |              Sink:
    |                  BlocksSent:  1
    |                  CloseTime:  avg  29.205us,  max  29.205us,  min  29.205us
    |                  InputRows:  2.556K  (2556)
    |                  OpenTime:  avg  133.74us,  max  133.74us,  min  133.74us
    |                  TotalTime:  avg  198.534us,  max  198.534us,  min  198.534us
    |
    4641:VHASH  JOIN
    |    join  op:  INNER  JOIN(BROADCAST)[]
    |    equal  join  conjunct:  lo_suppkey  =  s_suppkey
    |    runtime  filters:  RF001[in_or_bloom]  <-  s_suppkey(-1/0/2097152)
    |    cardinality=600,037,902
    |    vec  output  tuple  id:  9
    |    vIntermediate  tuple  ids:  8
    |    hash  output  slot  ids:  64  24  59  60  61  62  63
    |    Operator:
    |        BlocksReturned:  1.92K  (1920)
    |        CloseTime:  avg  21.882us,  max  32.631us,  min  15.891us
    |        OpenTime:  avg  55.200us,  max  60.702us,  min  50.896us
    |        ProjectionTime:  avg  10.54ms,  max  11.397ms,  min  8.905ms
    |        RowsReturned:  4.7908M  (4790800)
    |        TotalTime:  avg  77.814us,  max  87.173us,  min  68.149us
    |    Sink:
    |        InputRows:  40.125K  (40125)
    |        OpenTime:  avg  137.168us,  max  152.243us,  min  122.9us
    |        TotalTime:  avg  1.597ms,  max  11.215ms,  min  188.947us
    |
    |----4638:VEXCHANGE
    |              offset:  0
    |              Operator:
    |                  BlocksReturned:  12
    |                  CloseTime:  avg  7.987us,  max  8.927us,  min  6.340us
    |                  OpenTime:  avg  61.461us,  max  66.696us,  min  59.136us
    |                  RowsReturned:  40.125K  (40125)
    |                  TotalTime:  avg  79.53us,  max  141.973us,  min  67.339us
    |              Sink:
    |                  BlocksSent:  12
    |                  CloseTime:  avg  27.211us,  max  33.353us,  min  24.170us
    |                  InputRows:  40.125K  (40125)
    |                  OpenTime:  avg  111.630us,  max  116.382us,  min  106.843us
    |                  TotalTime:  avg  177.994us,  max  196.904us,  min  156.678us
    |
    4628:VHASH  JOIN
    |    join  op:  INNER  JOIN(BROADCAST)[]
    |    equal  join  conjunct:  lo_partkey  =  p_partkey
    |    runtime  filters:  RF000[in_or_bloom]  <-  p_partkey(-1/0/2097152)
    |    cardinality=600,037,902
    |    vec  output  tuple  id:  7
    |    vIntermediate  tuple  ids:  6
    |    hash  output  slot  ids:  48  34  35  39  40  41
    |    Operator:
    |        BlocksReturned:  1.92K  (1920)
    |        CloseTime:  avg  16.230us,  max  20.813us,  min  12.623us
    |        OpenTime:  avg  58.839us,  max  74.260us,  min  55.719us
    |        ProjectionTime:  avg  9.460ms,  max  10.561ms,  min  8.433ms
    |        RowsReturned:  4.826478M  (4826478)
    |        TotalTime:  avg  75.920us,  max  96.90us,  min  70.698us
    |    Sink:
    |        InputRows:  55.736K  (55736)
    |        OpenTime:  avg  138.102us,  max  151.891us,  min  130.916us
    |        TotalTime:  avg  2.329ms,  max  16.487ms,  min  199.868us

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run feut

run buildall

run p1


Implement Airnode whitelisting

Closes https://github.com/api3dao/signed-api/issues/98
Rationale
Adding the configuration option for whitelisting addresses is simple, but there is a special case - how to whitelist all? We can have a special meaning for empty array, similarly how it's done in Airnode but I think it would be better for this to be explicit and set it to "all" instead (string literal instead of an array). Alternatively, we can drop the "whitelist all" use case.
The naming is "allowedAirnodes", because it's about Airnode addresses, but the service is not Airnode but Pusher. I don't mind this, because Pusher and Airnode are related.
The "allowedAirnodes" configuration is used for both inserting/querying the data. The "list airnode addresses" endpoint is unchanged, because when all Airnodes are allowed we would need to scan the data storage anyway.

I couldn't catch the "querying" part, can you explain it?

I mean that an API call to get data for an non-whitelistested Airnode address with return 403.


test(transformer): tidy up transform checker

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

#6287  👈
#6286
main

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

Join @overlookmotel and the rest of your teammates on  Graphite


Peek should be more like a popup rather than a window

Description of the new feature / enhancement
When opening Peek with the shortcut, it opens as a separate app and is treated as a separate app, it would be more convenient if it was more like a popup (no maximize/minimize, no icon in taskbar, etc. )
Scenario when this would be used?
when using the Peek feature it would be more time consuming to have to close the app and it taking up more taskbar space is also an issue.
Supporting information
No response

it would be great if it also closed when losing focus and say pressing esc instead of much more involving alt+f4

/dup https://github.com/microsoft/PowerToys/issues/26137. Will be fixed in hotfix next week


Documentation suggestion

I think it should be mentioned that observe(...) call is side-effectful. It runs the function first time immediately (to evaluate those proxies) and the reaction is almost always a side-effect like logging, mutating, with probably the only exception of doing nothing...
import { observable, observe } from '@nx-js/observer-util';

const counter = observable({ num: 0 });

+ // this calls countLogger and logs 0
const countLogger = observe(() => console.log(counter.num));

// this calls countLogger and logs 1
counter.num++;

There's a section of Reaction scheduling but it describes another aspect (of scheduling, while the first time it's always a sync run, no matter which scheduler is applied, right?).

Hi!
You can pass the { lazy: true } flag to do not run it immediately. If you pass it, you have to call the returned reaction once later to kick-off the observation process. See the related docs section.
import { observable, observe } from '@nx-js/observer-util';

const counter = observable({ num: 0 });

+ // does not call countLogger
const countLogger = observe(() => console.log(counter.num), { lazy: true });

// this does not react yet, the returned reaction has to run once to kick off the observation process
counter.num++;

// this runs the reaction and starts the observation
countLogger()

// this also runs the reaction (observation is already started)
counter.num++;

This is useful when you don't own the control flow of the program. See my other lib (react-easy-state) for a real life example of the usage.

Ok, thanks for clarification.


[Shopify] Fix sync catalog price issue

Summary
When users try to synchronize prices through the action available on Shopify Catalogs page. Only the 100 first prices are synchronized. So if the Shopify Catalog contains more than 100 product, only 100 of them will be updated.
This problem results from a difference between two GraphQL requests made during this process:

codeunit 30296 "Shpfy GQL CatalogPrices"
'{"query": "query { catalog(id: "gid://shopify/Catalog/{{CatalogId}}") { id priceList {id currency prices(first:100) {edges {cursor node {variant {id product {id}} price {amount} compareAtPrice {amount}}} pageInfo {hasNextPage}}}}}"}'

codeunit 30297 "Shpfy GQL NextCatalogPrices"
'{"query": "query { catalog(id: "gid://shopify/Catalog/{{CatalogId}}") { id priceList {id prices(first:100, after:"{{After}}") {edges {cursor node {variant {id} price {amount} compareAtPrice {amount}}} pageInfo {hasNextPage}}}}}"}'

Some necessary nodes are missing in NextCatalogPrices. Here is a fixed request :
'{"query": "query { catalog(id: "gid://shopify/Catalog/{{CatalogId}}") { id priceList {id currency prices(first:100, after:"{{After}}") {edges {cursor node {variant {id product {id}} price {amount} compareAtPrice {amount}}} pageInfo {hasNextPage}}}}}"}'
Work Item(s)
Fixes #27535
Fixes AB#556528

@glachana could you please pull from main? looks like the builds are failing because branch is not up to date

@onbuyuka it should be fine now.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 26432.

Availability update: We will publish a fix for this issue in the next update for release 25.
Build ID to track: 26895.

@JesperSchulz hello! Sorry for asking but when referring to build ID, are u referring to the build ID of the Shopify Connector or the base app?

26895

All our Apps are currently built together and get the same Build ID. Both the BaseApp and the Shopify app should have a version with that ID. In this case we're referring to the following build: 25.2.26895.0 from the 19-11-2024.


Fix PropType and Docgen in static builds for Info

Issue:
https://github.com/storybooks/storybook/issues/1661
PropTypes get removed during our build and Docgen never runs so the Prop Table in Info shows up empty and undefined.
What I did

set webpack static build environment to dev to prevent PropTypes from being stripped out
added docgen plugin to static build babelrc
created new story component in example to show PropType table from fallback method
updated storyshots

How to test
run cra-kitchen-sink and check the 3 AddonInfo buttons.
Is this testable with jest or storyshots?
yes
Does this need a new example in the kitchen sink apps?
yes
Does this need an update to the documentation?
no
If your answer is yes to any of these, please make sure to include it in your PR.

set webpack static build environment to dev to prevent PropTypes from being stripped out

Can we find a way to restrict this to prop-types package?

@Hypnosphi I think the babel-preset-react is the one that strips out the PropTypes when compiling for production. I'll see what I can do there in terms of making that run in dev.
We don't really have a framework for turning features on and off in Webpack without using a custom Webpack config. Sadly, we never enabled custom .babelrc configs for static builds.
New issue created to track custom babel config: https://github.com/storybooks/storybook/issues/1731

I think the babel-preset-react is the one that strips out the PropTypes when compiling for production

As far as I know, this logic lives inside prop-types package

Actually yeah, I was thinking of how flow types are stripped out. I can't find any documentation on how to supply the NODE_ENV other than the link on the bottom of the readme. https://github.com/facebook/prop-types#proptypescheckproptypes which links to https://facebook.github.io/react/docs/optimizing-performance.html#webpack
That's what I'm doing already to unset the production flag. Any other suggestions?

One possible solution is to add custom loader just for `prop–typesˋ package which will do nothing but replace ˋ‘process.env.NODE_ENV‘ˋ with ˋ‘“production“‘ˋ

@Hypnosphi That feels really hacky.
I don't think the benefits of avoiding a dev webpack flag outweigh the cost of maintaining a custom webpack plugin.

That feels really hacky

That's exactly what DefinePlugin does for all the packages

Removed the webpack dev environment. Definitely agree on the performance but I think making webpack settings option is out of scope of this bug fix.

Well, now it's only babel, mut maybe it won't hurt to have this plugin always
Please address the unit tests failure

how can I get the file-stub locally without modifying it manually?
    -      src="logo.svg"
    +      src="file-stub"

@ndelangen @shilman any thoughts on this getting merged into master instead of 3.3? it's a small change to prod babel config and a new example app story.

Gave up on trying to rebase it to master. It's just gonna go into 3.3.


App Update Behavior: App crashed on the phone and Preset Customizations didn't retain on the tablet

Describe the bug
Tablet: After the upgrade app on the Galaxy S6 tablet, custom categories and phrases are retained as before. Timing and sensitivity settings are retained as before. But preset categories’ customization didn’t retain. All presets are updated as a fresh new install.
Phone: While trying to upgrade the app on the Galaxy S8 Phone, the Vocable keeps stopping error occurred and the app crashed.
To Reproduce
Before updating the app,

Add a custom category and phrase
Hide a category
Reorder a category
Update hover time
Update sensitivity
Update the app

Expected behavior

Custom categories and phrases still exist
Hidden category is still hidden
Category reordering is preserved
Hover time is same as before
Sensitivity is same as before
All other presets and unchanged categories remain as before

Actual Behavior
Tablet: Custom categories and phrases are retained as before. Timing and sensitivity settings are retained as before. But preset categories’ customization didn’t retain. All presets are updated as a fresh new install.
Phone: Vocable keeps stopping error occurred and the app crashed.
Devices:
Tablet: Galaxy S6 tablet - Android 12
Phone: Galaxy S8 Phone - Android 9

Since artifacts of old builds weren't being saved anywhere, had to do some archaeological work to get a pseudo-1.5.2 build to be able to reproduce this bug. The branch for creating that build is: experiment/attempt-to-build-1.5.2.
Upgrading from a release build on that branch to a release build from main persists all settings and categories except, the phrases in the categories don't seem to migrate. Further investigation needed.

Going to skip having someone manually validate upgrade path until we're ready to ship, since there are more schema changes coming.


close server

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[ ] I'm not able to find an open issue that reports the same bug
[ ] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: windows 11
- Continue version: Published
2023-05-28, 01:17:59
- IDE version:
- Model: All (ollama)
- config.json:

Description
Very often, the autocomplete model does not work and a regular chat may simply not work either. there are errors about the server connection or something like that, as well as models are often unloaded by themselves
To reproduce
No response
Log output
No response

which version of Ollama are you using (there's currently something bad happening between Continue and Ollama 0.4.x, see https://github.com/continuedev/continue/issues/2838#issuecomment-2474492124)? which models?

3090 ti and 16 ram

try downgrading ollama to 0.3.14: https://github.com/ollama/ollama/releases/tag/v0.3.14
If it works then, you're definitely hitting the issue I'm trying to fix in https://github.com/continuedev/continue/pull/2935

+1 to @fbricon , please follow along in https://github.com/continuedev/continue/pull/2935 👍

Please update to Ollama 0.4.4 now, see https://github.com/ollama/ollama/releases/tag/v0.4.4:

Fixed issue where Ollama would freeze when processing requests in parallel (e.g. when using code completion tools)


Handle rate limits

When the GitHub API decides it's time to rate limit a certain IP address, it still returns a valid JSON reponse but with a HTTP 403 status code:
{
    "message":"API rate limit exceeded for xxx.xxx.xxx.xxx. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)",
    "documentation_url":"https://developer.github.com/v3/#rate-limiting"
}

As a result, the repo card has undefineds all over the place :(

Would be nice to catch this and maybe apply a CSS class to the container so the cards can be hidden / replaced with something meaningful.

Fixed!


shadcn

#111
try it out
Notes

lru_redux is a Ruby gem providing an efficient and optionally thread-safe Least Recently Used (LRU) cache.

not clean install, closing for now


Add support for react-mode

The React layer for Spacemacs defines react-mode. Add support for formatting react-mode buffers.

Thanks!


I would like to add "Quick sort" code in java

This issue aims to add a coding problem named Quick sort along with its solution to the repository. Pls assign this issue @YuweAEC

you can proceed with the pr @Visha17

I will start working on this

sure work on this and raise the pr

i will try to work on this too.

Yes sure go for it @Ayahelmaoui


Desfire commands

Hi all,
My RFID project  is with CLRC663 using stm32l0. So far with the help of the code here I managed to get ATQA, UID, SAK, ATS and also read and write to Mifare classic card, work. However I can not get it work with desfire commands! I need to create application, select it, create file and so on but I could not get the native commands work, I even tried to wrap it with ISO 7816 but still no gain. Is their any library that i can download? Nxp's library is so complicated .
Many thanks in advance.

Hi, see to this : https://www.mifare.net/support/forum/topic/desfire-ev1-selectapplication-command/

Thanks for the help. However my problem is beyond this. No command works after ATS! I think I am not sending the commands right! So I got an array like Send_Re[4]= {0x5A, 0x01,0x01,0x01}; which th3 three byte 0x01 is my AID which is created using nxp app. Now I am trying to select this app so I write Send_Re into fifo and afterwards I transieve it and once the communication finished(IRQ0 clears) I read the fifo again. Is there anything wrong with this?

This is my ATS function which works fine.
uint64_t PICC_RequestATS(uint8_t* ats){
CLRC663_write_reg(CLRC663_REG_COMMAND,CLRC663_CMD_LOADPROTOCOL);  //write_reg(0x00,0x0D);
CLRC663_flush_fifo();      											// Flush_FiFo
CLRC663_write_reg(CLRC663_REG_TXCRCPRESET, 0x19);
CLRC663_write_reg(CLRC663_REG_RXCRCCON, 0x19);          			// CRC auto calculation is activated for CRC16
uint8_t Send_req1[]= {0xE0, 0x80};
CLRC663_write_fifo(Send_req1, 2);          //RATS,E0
CLRC663_write_reg(CLRC663_REG_COMMAND, CLRC663_CMD_TRANSCEIVE);     //Start tranceive command
Clrc663_irq_wait(0x18, 0x2);  							            // Wait for irq0 to clear, showing the
uint8_t len = CLRC663_fifo_length();//read FIFO length
CLRC663_read_fifo((uint8_t*) &ats, len);   // Read FIFO,Expecting ATS,after receiving the ATS the PICC enters protocol
return ats;

}
However for selecting the App I do exactly the same thing and got different response each time which is neither of the response specified in the AN. Here is my code:
uint8_t PICC_SelectApp(uint8_t* result){
CLRC663_write_reg(CLRC663_REG_COMMAND,CLRC663_CMD_LOADPROTOCOL);  //write_reg(0x00,0x0D);
CLRC663_flush_fifo();      											// Flush_FiFo
CLRC663_write_reg(CLRC663_REG_TXCRCPRESET, 0x19);
CLRC663_write_reg(CLRC663_REG_RXCRCCON, 0x19);          			// CRC auto calculation is activated for CRC16
uint8_t Send_req1[]= {0x5A, 0x01, 0x01, 0x01};
CLRC663_write_fifo(Send_req1, 4);          //RATS,E0
CLRC663_write_reg(CLRC663_REG_COMMAND, CLRC663_CMD_TRANSCEIVE);     //Start tranceive command
Clrc663_irq_wait(0x18, 0x2);  							            // Wait for irq0 to clear, showing the
uint8_t len = CLRC663_fifo_length();//read FIFO length
CLRC663_read_fifo((uint8_t*) &result, len);   // Read FIFO,Expecting ATS,after receiving the ATS the PICC enters protocol
return result;

}
I even tried sending {0x02, 0x5A, 0x01, 0x01, 0x01} or {0x90, 0x5A, 0x01, 0x01, 0x01} but still does not work. I do not know what the problem might be. Any help really appreciated.

Ok.
AN11022 has a description for the Appids acquisition sequence
Fig 14. NFC Cockpit with CLEV6630A / CLEV6630B: Activation of a MIFARE DESFire EV1 card + Get Version
Compare with your algorithm of work.

Thanks alansbor, I got PPS and application select work . Now I am working on authentication . Is it exactly the same process?

I was glad to help. Read all the manuals from the chip manufacturer and everything will be fine.


specify all the dependencies version in setup.py

Make sure these boxes are checked before submitting your issue - thank you!

[ x ] I have checked the superset logs for python stacktraces and included it here as text if any
[ x ] I have reproduced the issue with at least the latest released version of superset
[ x ] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.26.2
problem with pandas version: 0.20.3
Expected results
run charts, the charts should render some beautiful graphs.
Actual results
raise error 'Series' object has no attribute 'items'
Steps to reproduce
when setup everything, click one example charts, the charts cannot rendered.
This is because Pandas version is too low. after upgrading pandas to 0.23.3, this error disappear.

Please specify all the dependencies installation version.
The version of pandas is not enough, at least 0.23.3 will solve this problem.
https://github.com/apache/incubator-superset/blob/c1e6c68a3ed31d3875b6d9dfac1484d8897d6561/setup.py#L79

@mistercrunch @williaster specify all the third party lib version is a very good engineering practice.
I have came across another similar problem. markdown has new version available, when I build superset image half years later, it somehow installed the newest version which failed my older features.
In superset == 0.26.2, markdown should be 2.6.11 otherwise if you run superset version, it fails.
Strongly advice to specify all the version in setup.py, otherwise, don't know what will come across in the long run.

@john-bodley bringing this up again as many people are having issues with a pip install superset at the moment. I wonder if we should go to a default of pinning most library and allowing version ranges for libs where people may need flexibility (pandas, celery. //)

@mistercrunch thanks for raising this. I've been re-looking into how to best configure Python applications (as opposed to packages). It seems that the recommended approach is not to pin specific versions in setup.py but rather in requirements.txt (or similar) per here and others.
It seems in our case your setup.py is not prescriptive enough or contains lower bounds which aren't viable, i.e., clearly pandas==0.18.0 is not suffice for superset==0.26.2 and the setup.py should be modified to include viable versions. I believe this is the responsibility of the developer who is creating a breaking dependency change to update setup.py and re-generate requirements.txt.

@john-bodley  the big question is whether we think pip install superset should just work or be allowed to get in a bad state (open version guarantees it will). Without upper-bounds on version ranges, we're kind of asking for it. For instance we know that celery>=5.0.0, when it comes out, is very very likely to break things in Superset.
We need to either:

add an extra steps in the installation docs recommending cloning the repo and installing the requirements.txt file
actively managing ranges in setup.py, quickly release with bound ranges as soon as something is known to be broken
ping setup.py and tell users that if they want to mess with lib versions, they can make their own build by messing with setup.py in their fork, this also means manually, periodically bumping to make sure we don't use stale libs
add a step in the build matrix that checks whether an indeterministic pip install superset (without reqs.txt) currently leads to a broken build, that way we know quickly when pip install superset is broken
?

@mistercrunch, I believe that pip install superset should work, however installing Superset is not suffice due to environment specific dependencies. It may be good to understand how other organizations deploy it. Could there be a circumstance where people need to use a different SQLAlchemy version based on their database?
I agree with your points, especially 1, 2, and 4. Let me keep looking into this.

I can tackle 1

@john-bodley maybe this helps, you can and should only specify requirements in one place.  If you like requirements.txt, you can pull them into setup.py with a trick like this:
https://github.com/wikimedia/analytics-wikimetrics/blob/master/setup.py#L25
And for everyone's sanity, it's always good to pin exact or at least compatible versions (^X.Y.Z should work if everyone takes semver seriously).  You can even make a build process through setup.py that installs all the node dependencies too.

@mistercrunch when you say "version ranges" for setup.py, do you mean that from the new upstream version (ideally 0.29?) all the deps in setup.py will not cause a broken build with bdist_wheel (0.26.3 cannot be built in this way for example) ? If so it would be great to have a documentation about how to properly build superset, so everybody is on the same page. What do you think?


Short switch -v for version.

Thanks, I have tested the completion generator with this change and unfortunately it broke. I'm going to fix the completion generator first and will then merge this commit

done now, merging

Sorry about the completion generation - maybe we can automate testing that? ;-)

Sorry about the completion generation - maybe we can automate testing
that? ;-)

also thought about it but it's pretty hard to test bash code and I'm not aware of any completion automation which provides me a good return result for a test. I think it would be possible if we rewrite the completion python code which creates the bash sequences to be testable. But that would be a not so small side project which I would consider not a prio at the moment


chore(nextjs): Add deprecation warning for app-beta subpath export

Description
The implementation in app-beta was an attempt to support the NextJS app-router early on. Since the app-router release is stable we will deprecate the @clerk/nextjs/app-beta subpath export and suggest using the stable @clerk/nextjs exports instead.
In this PR the following hacks were applied to add JSDocs and console warnings deprecations:

we could not add a single deprecation warning in the app-beta/index.ts because it did not work so deprecated was added in each file
Replaced import from @clerk/clerk-react with module to show deprecation warning (see: packages/nextjs/src/app-beta/client/clerk-react.ts)
Use import with aliases for re-exported modules of @clerk/clerk-react to add JSDoc deprecations only for the exports from the app-beta

Since the whole folder app-beta will be removed in the next major version, there is no need to worry about those hacks.

Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[x] (If applicable) JSDoc comments have been added or updated for any package exports
[x] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[x] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[x] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

@dimkl What were the issues you ran into with adding the deprecation warning to app-beta/index?

@BRKalow , @LekoArts adding a deprecation in the app-beta/index.ts seems to be ignored.
I have created the following screenshots to showcase that add a  warning to the module, the warning is visible to the console but the warning in the index.ts is not.
The following steps were applied:

add deprecation warning to index.ts and to auth.ts and a console.log
<javascript_repo> git status to show that those changes were saved
<javascript_repo> npm run build -- --force && npm run yalc:all to create clean build and push that build to the playground
<javascript_repo>/playground/nextjs npm run dev to start an application with NextJS app-beta
navigate to http://localhost:4011 to trigger application logs
Search for deprecation warnings and console log in the application logs

Ok, makes sense 👍 I'd need to dive deeper into how you could run a side-effect when a module is imported. With a quick search I couldn't find previous art on this.

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


feat(getTxData()): Added method for retrieving tx data

:tada: This PR is included in version 4.3.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


New version: vim.vim.nightly version 9.1.0151

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Hi @chrisbra,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 861.)

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-03-05 16:52:35.264 [FAIL] Installer failed security check. Url: https://github.com/vim/vim-win32-installer/releases/download/v9.1.0151/gvim_9.1.0151_x86.exe Result: 0x80004005

(Automated response - build 861.)

@wingetbot run

@wingetbot run


Move to Alpine.js Sort plugin

Donate 💰 to fund this issue

You can donate funding to this issue. We receive the money once the issue is completed & confirmed by you.
100% of the funding will be distributed between the Filament core team to run all aspects of the project.
Thank you in advance for helping us make maintenance sustainable!

I noticed this issue is currently unassigned, and I would like to help with it. Can I take on this task?
If there are any specific guidelines or requirements I should follow, please let me know.
Thank you!

Hi, @awcodes are you interested in someone else helping out here? If yes, maybe pass on any info @CharrafiMed might need? Or maybe you don't have any information for them and they can go ahead and start working on the ticket? Thanks

@CharrafiMed feel free to take a crack at it. I started it but, didn't get very far. Let me know if you have any questions.

@awcodes oki thanks, I will start working on it soon.

I think this was attempted quite a bit and we weren't able to get it working with all the same features we had before


aurbuild: use the pacman cache as package pool

This would eliminate the issue of checksum mismatches entirely, without a removal logic. Check how to keep some safeguards from pacman -Sc, and if separate cache dirs can be used.

Implemented, though you'll have to rebuild the repose database.

Won't this result in all packages in your cache being added to the repository?

Nope, since you'd use a different CacheDir, which is placed after the first entry, i.e.:
CacheDir = /var/cache/pacman/pkg
CacheDir = /var/cache/pacman/custom

If a package is not already in either directory, pacman downloads it to the first. See pacman.conf(5)

Interesting. Thanks for such a speedy reply, I really appreciate it.
It's been a few weeks since I last looked at aurutils and I noticed you've also implemented signing. I'll definitely be deleting my fork soon once I've tested the new version!


add header part

-Linter Configured
-Readme file added

Header part created
Proper Gitflow

Hi @Yonasle
I'm @MohammadYaser  your reviewer for this PR. ✋
Your project is complete! There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Highlights
You have written a clean code ✅
Functrional app. ✅
Optional suggestions
N/A
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


LCFS - Government users can edit their comments

Description:
Government users can edit their internal comments that they have previously added within the transfer feature:

[Edit] button is visible on previously added comments by that same user (see wireframe)
Clicking on the edit button allows the user to edit their comment
User can then save the edited comment or cancel the edits
If the user saves the edited comment, then a new date/time stamp is displayed to indicate when the edit was made. The date / time of the original comment remains visible.
Only the date/time of the last edit is displayed in the case where a comment has been edited multiple times.
Editing a comment does not impact the sorting of comments, which is based on descending order (most recent comment at the top) determined by the comment's original date/time stamp which is always visible in the UI
There are no restrictions on when government users can add / edit comments. For example, an analyst can add/edit a comment before or after they make a recommendation to the director; they can also / add edit the comment after the transfer has been recorded / refused.

Related cards / dependencies:
#259
Wireframe:

Example of an edited comment: https://preview.uxpin.com/59145260c7d8cc48969ac79401cc03d84843c3d9#/pages/165112777/simulate/no-panels

Purpose and benefit to user:
Allows the government user to change their comment if they discover an error, spelling mistake, or grammatical issue
Based on the information provided, the last three sections of the sprint ticket can be completed as follows:
Acceptance Criteria:

[ ] Given I am a government user, When I click the [Edit] button on a comment I have previously added, then I should be able to edit the content of the comment.
[ ] Given I am a government user, When I save the edited comment, then the comment should display the new date/time stamp of the last edit while retaining the original date/time stamp.

Development Checklist:

[ ] Implement the visibility of the [Edit] button on comments added by the same government user.
[ ] Enable the editing feature for comments, allowing users to modify the content.
[ ] Ensure the system updates and displays the new date/time stamp for the last edit alongside the original date/time stamp on saving the edited comment.

Notes:

It is important to ensure the original date/time stamp of the comment is always visible, regardless of the number of edits.
The sorting of comments should remain based on the original date/time stamp to maintain chronological order in the conversation.
Testing should cover scenarios where comments are edited multiple times to ensure the display of date/time stamps is consistent and accurate.
Editing a comment by removing all text in it would save as an empty text box, but retain the name and date stamp of the user. This allows for deletion of comment, but keeps a record of the user that was involved in commenting. Avoids allowing user to completely delete record of historical comments.

Hey team! Please add your planning poker estimate with Zenhub @hamed-valiollahi @kevin-hashimoto @prv-proton

When I input an internal comment and select 'add comment', the text box is replaced by a message that says 'error loading comments: Network Error' and the comment is not saved. Please see screenshot for error:

@Grulin, thanks for reporting the issue! I also couldn't reproduce the issue you mentioned. It could be an internet or server environment issue. Could you please check once more and let me know if it's still there? Then, Alex and I can look into it together. Thank you!


Pabot and Data Driver optimization

I have 10k test cases in excel and used Data driver test template with optimize_pabot=Binary. Am using pabot for parallel execution with 10 processes but in the result I see pabot form 59 executions. Could u pls help me understand how the optimize_pabot options are working?? Though I initiated 10 processes i see 59 executions and how is that possible?? Also in a machine with 4vCPU and 16GB memory how many processes can be launched to run in parallel?? If the number of processes are more i see it is taking more time for execution what could be the reason behind it. Thank in Advance

This tracker is for bug reports and enhancement requests Robot Framework core, not for Pabot or DataDriver or for questions in general. I suggest you ask this on our Slack or Forum. You can find them both via robotframework.org.


Maps Support

Provide maps in the tracker for areas that may have a lot of checks to remember.

Initial maps are pushed live, other issues with them or missing checks should be written as separate tickets


FIX: public API for joint plot in viz (following common patterns)

it should have been like that in the first place, no deprecation needed.

not done yet, don't merge.

Fine with me. I forgot why I initially used the other name.

why was this necessary?

why was this necessary?

because we expose our viz methods as public functions and we wrote this somewhere in a paper. I would ask the other way round: why would you want to break consistency here?

because we expose our viz methods as public functions and we wrote this
somewhere in a paper. I would ask the other way round: why would you want
to break consistency here?

I am thinking that their should be "one way to do things" but let's avoid a
massive PR just for this.

yes and we have always done it this way.
On Wed, Feb 17, 2016 at 10:02 PM, Alexandre Gramfort <
<EMAIL_ADDRESS>wrote:

because we expose our viz methods as public functions and we wrote this
somewhere in a paper. I would ask the other way round: why would you want
to break consistency here?

I am thinking that their should be "one way to do things" but let's avoid a
massive PR just for this.
—
Reply to this email directly or view it on GitHub
https://github.com/mne-tools/mne-python/pull/2896#issuecomment-185401787
.

@agramfort you finally agreed that this is good to go, right? Anyone else? I'll merge in a while if no one objects.

just echoing what @dengemann mentioned, our viz module has all of the plotting functions where you can supply it the proper object and it does the plotting. we then have these functions inherited as methods to their respective modules. it's been that way for a while. LGTM @dengemann


[BUG] App is not loading

Description
I was just looking at the repo and trying to explore the app. But looks like it's not loading.
OS: Windows
Browser: Google Chrome
Screenshots

Any additional information?
No response
What browser are you seeing the problem on?
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[ ] I'm a GSSoC'24-Extd contributor
[ ] I'm a Hacktoberfest'24 contributor
[ ] I am willing to work on this issue (optional)

@jjaijg there is an issue with deployment it doesnot work when deployed online but works good when deployed locally

Oh ok. Thanks @sharmavikas4

@jjaijg are you working on it

``


Set default image to public ecr

Description
Please include the following:

A meaningful PR title guidelines
A summary of the change
Which issue is fixed (if there is one)
Relevant motivation and context

How can this be tested?
Please include some guiding steps on how to test this change during a review.

What environment is necessary for the change to be noticeable ?
What needs to be enabled/applied for the change to be noticeable ?

Checklist

[ ] Unit tests have been updated/added
[ ] PR is labeled accordingly with a single label
[ ] I have read and understood the contribution guidelines

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (5ae21da) 64.76% compared to head (754515e) 64.76%.

:exclamation: Current head 754515e differs from pull request most recent head 4d6902d. Consider uploading reports for the commit 4d6902d to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2532   +/-   ##
=======================================
  Coverage   64.76%   64.76%
=======================================
  Files         248      248
  Lines       16229    16229
=======================================
  Hits        10511    10511
  Misses       4917     4917
  Partials      801      801

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[NEW]: This may be worth watching (not necessarily adding yet)

Date
2022-06-07
Description
https://www.twitlonger.com/show/n_1ss24a6 is promising an info dump of a HUGE collection of Telegram messages that promises to reveal some rather ... shocking ... behaviour on the part of cryptobros.  It's probably not worth posting this now, but perhaps keeping an eye on it and getting a copy of the dump would be interesting if it's real.
Links
https://www.twitlonger.com/show/n_1ss24a6
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
No response
Personal link
https://twitter.com/adyingnobody

I'm keeping an eye on it. It seems likely to be a hoax, but can't hurt to wait and see.


Add metadata

Adds metadata functionality to the library.

@dalepotter this looks to be an early solution towards implementing the changes required for #166 (in a way that scales to Schemas and Rulesets).
#213 used a different approach so that the complete attribute could be quickly added for validation purposes.
What is the current state of this PR? Will it work as the base for a fix to #166?


Add Kiva.com to an existing purpose and add a new purpose.

Looks good to me 👍
I have resolved the conflicts and am merging it.


Allow LogSerializer to be disabled to facilitate usage in Unity iOS

Unity iOS apps using the Unity equivalent of NewtonSoft.Json library crash when trying to JSON serialize objects with properties.  This PR is to add a mechanism to disable the serialization of arbitrary objects for logging purposes, which is the only code change required to have this library working in Unity iOS apps.

But that means that logging is broken in that situation. Any other ideas?

Probably the best alternative would be to remove the {get;set;} from AuthorizeState and OidcClientOptions classes (since these are the only two classes that get passed to LogSerializer.Serialize()).  That will allow the logging to work properly on iOS.  Or we could override ToString() on those classes and manually construct the log message instead of using JsonConvert.SerializeObject.  Sadly fixing the root cause I believe requires a changes to the IL2CPP code generation that Unity employs for iOS builds, which seems to be stripping required code from the generated properties, or changes to the Unity-compatible Json.Net library to handle properties differently.  We've had this problem with our own code, it's not something specific to this library, and our solution was to use fields instead of properties on classes that need to be serialized.  There are two threads with info on this here and here.  What do you think?

thanks!

thank you!  i'm thinking to write a sample unity app showing how to use this with unity for android/ios.
would that be something that makes sense to add to the IdentityModel.OidcClient.Samples repo?

Put it somewhere on github - i can link to it from the readme.

Sample code added here:
https://github.com/peterhorsley/IdentityModel.OidcClient.Samples/tree/unity-sample
Videos showing the sample running:
https://codenature.info/pub/unityauth/android-identitymodel-unity-sample.mp4
https://codenature.info/pub/unityauth/iphone-identitymodel-unity-sample.mp4
If you'd prefer I can make a separate repo for this to keep it dis-associated.  Or if you are happy to bring Unity into the list of platform samples I can raise a PR on the samples repo.

separate repo with a readme would be cool - so you can link to the videos. I will link to your repo from my readme. thanks!

ok i put it here: https://github.com/peterhorsley/Unity3D.Authentication.Example

Thanks!


HDDS-4681. SCM webui display wrong Node counts.

What changes were proposed in this pull request?
Fix SCM webui Node Counts display.
The order is follow hdds.proto#NodeState and hdds.proto#NodeOperationalState.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4681
Please replace this section with the link to the Apache JIRA)
Test on docker-compose.

+1 pending CI. Looks like a small missing piece in the UI as a result of the addition of NodeOperationalState. Thanks for the patch.
CC @sodonnel

+1 pending CI. Looks like a small missing piece in the UI as a result of the addition of NodeOperationalState. Thanks for the patch.
CC @sodonnel

+1

+1

Thanks @flirmnave for the patch. Thanks @lamber-ken @cku328 for reviewing this. Merged.

Thanks @flirmnave for the patch. Thanks @lamber-ken @cku328 for reviewing this. Merged.

Thanks @smengcl @lamber-ken @cku328 for reviewing.

Thanks @smengcl @lamber-ken @cku328 for reviewing.

Thanks for this change - this was on the "todo list" for decommission, but I never got it - HDDS-2641. I think I can resolve that one now as a duplicate of this one.

Thanks for this change - this was on the "todo list" for decommission, but I never got it - HDDS-2641. I think I can resolve that one now as a duplicate of this one.

Actually, HDDS-2641 was to show the actual nodes decommissioning and their pending replication stats, similar to how the Namenode WebUI does in HDFS. I will leave HDDS-2641 open for now as something we can add in the future. Feel free to take that one if you like, as I won't have time for it in the near future.

Actually, HDDS-2641 was to show the actual nodes decommissioning and their pending replication stats, similar to how the Namenode WebUI does in HDFS. I will leave HDDS-2641 open for now as something we can add in the future. Feel free to take that one if you like, as I won't have time for it in the near future.


Osram Smart+ Plug

Ostam smartplug reports electrical measurement cluster but device doesn't support it

Pull Request Test Coverage Report for Build 483848711

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 83.032%

Totals

Change from base Build 476463521:
0.04%

Covered Lines:
3215

Relevant Lines:
3872

💛  - Coveralls

Pull Request Test Coverage Report for Build 483848711

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 83.032%

Totals

Change from base Build 476463521:
0.04%

Covered Lines:
3215

Relevant Lines:
3872

💛  - Coveralls


Minor sync issues due to non bundled playhead information

As the remaining time in a video and the elapsed time in a video are not reported in the same message, there is a slight difference in reported playhead position depending on which is relied upon.
Bundling these (with the "duration") in one message would alleviate this issue.

Yes, this is a side-effect of the way the OSC is packaged and emitted. I've been staying away from bundles as I'm not sure how good support for them is and wanted v1 to be (a bit more) guaranteed to work. Might add support for bundles future releases - let me know if you've ever had issues with them and had to drop back to plain-ol single messages.

Not really. The individual addresses still


Text field operators missing on Godot 3.0

Operating system or device - Godot version:
Godot 3.0 Alpha 1
Issue description:

On Godot 2.1.x you could use operators on text fields, for example on the display size you could type 1920/2 and you get 960. This functionality is missing on Godot 3.0, also it would be nice if we could use the tab key and the shift+tab to go to the next field or the previous without having to press enter to confirm the value and select the next one using the mouse.
Steps to reproduce:
Link to minimal example project:

Duplicate of  #9500.


shim-unsigned: Force using shim-15 for aarch64

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/tools/cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary

There is a regression in shim-15.4 aarch64 builds where, if built with
binutils pre-2.35, the binary will fail to boot with "Synchronous Exception"
error.
See upstream shim issues page for more details.
Force using shim-15 release for aarch64 only.
Older cert is expired. Use new cert instead.
Signed-off-by: Chris Co<EMAIL_ADDRESS>Does this affect the toolchain?

NO
Associated issues

Links to CVEs
Test Methodology

Local build

It looks like the spec change is a revert, so I'm not pushing for the fixes I've suggested in that file, since we're not making anything worse than it already was, but it might be worth fixing these small things, since we're already here. And increment the release version to "6" due to the change to the Vendor tag.

I was also debating this after I reverted the spec. I opted to go the safer route and minimize the deltas from the older shim-15 version. The only spec deltas are:

New cert file
Release number bump from 4 to 5 with corresponding changelog entry.

Once 15.4's aarch64 build issues are sorted out upstream, I'll move us forward again and apply all the proper spec formatting.


Enable CodeCoverage monitoring as part of the build

We should enable CodeCoverage monitoring as part of the build. See https://codecov.io/gh/hyperledger/quilt for e.g., or some other tool.

I have enabled codecov - @nkramer44 please confirm if this is working as expected?

@alloyxrp Yes working as expected.  Just need to get my config right!