notification events from CRI runtime

The major container runtimes, containerd and cri-o, both offer extensive hooking mechanism we can leverage to get container lifecycle events while the podresources API catches up. It could work like this:

the RTE opens a notification socket on a well known location
RTE offer a client program to be called from the CRI runtime hooks
When a noteworthy container lifeycle event (create and remove; what else?) happens, the hook calls the client to notify RTE
Depending on further design decisions, RTE either trusts the client program with the data it received from the notification socket, or performs a full GetAllocatable/List poll to update its status.

This is a good idea and definitely worth exploring! Currently, I only see PreStart and PostStop hooks here which should take care of the container lifecycle event you mentioned above (create and remove). In addition to this, I can think of update lifecycle event where resources are updated but that could be phase 2 of this work.

@swatisehgal, @fromanirh my college interested in this, but for solving issues with PLEG.
He has a draft at https://github.com/ikeeip/containerd/tree/cri_subscribe_events

@AlexeyPerevalov very nice! thanks for letting us know. I'll surely have a look ASAP.

implemented in https://github.com/k8stopologyawareschedwg/resource-topology-exporter/pull/54 (merged)


no role on summary element

test case
currently says the button role is valid, but this is no longer allowed.
Note: if the above link breaks, check this test case (which may not work, unless the above is broken).

Removed button role as allowable on summary elements.

verified as updated.  thank you


go build linux error

I tried to build the example of examples/webrtc into Linux in the Mac environment, but an error occurred.
What is the reason and how to solve it?
Compile webrtc example
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build main.go
The following error occurs
# github.com/pion/mediadevices/pkg/driver/microphone
../../pkg/driver/microphone/microphone.go:29:16: undefined: malgo.AllocatedContext
../../pkg/driver/microphone/microphone.go:36:8: undefined: malgo.DeviceInfo
../../pkg/driver/microphone/microphone.go:48:19: undefined: malgo.InitContext
../../pkg/driver/microphone/microphone.go:48:42: undefined: malgo.ContextConfig
../../pkg/driver/microphone/microphone.go:86:31: undefined: malgo.DeviceInfo
../../pkg/driver/microphone/microphone.go:105:19: undefined: malgo.DeviceConfig
../../pkg/driver/microphone/microphone.go:106:22: undefined: malgo.DeviceCallbacks
../../pkg/driver/microphone/microphone.go:123:30: m.ID undefined (type *microphone has no field or method ID)
../../pkg/driver/microphone/microphone.go:141:23: undefined: malgo.InitDevice
../../pkg/driver/microphone/microphone.go:199:27: m.Formats undefined (type *microphone has no field or method Formats)
../../pkg/driver/microphone/microphone.go:199:27: too many errors
# github.com/pion/mediadevices/pkg/codec/x264
../../pkg/codec/x264/params.go:49:9: undefined: newEncoder
# github.com/pion/mediadevices/pkg/codec/opus
../../pkg/codec/opus/params.go:71:9: undefined: newEncoder

Hi @anamyip, these codecs requires CGO since they use C libraries.

Hi @anamyip, codecs requires CGO since they use C libraries.

How to modify the following command?
CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build main.go


Pip install fails on Arch Linux image

This pipeline fails due to the action trying to install gcovr into the system directory.
What needs to be done first is to create a virtual environment for Pip. I tried to this before calling into the action with python -m venv venv && source venv/bin/activate but it's not reusing the environment inside the action, so it must be done inside the action..

Can you try using the main branch instead: threeal/gcovr-action@xml-out?
It includes a change that installs gcovr using pipx instead of pip (see #204). By default, pipx should install gcovr to the home directory. However, your runner may need to support pipx in this case.

Can you try using the main branch instead: threeal/gcovr-action@xml-out?

I was using already the xml-out tag. It doesn't include the change to pipx though. I'm now testing with  threeal/gcovr-action@main

With main tag, I get a different error, now it doesn't find the pipx binary:
Error: Failed to restore gcovr cache:
Failed to get PIPX_BIN_DIR: Unable to locate executable file: pipx.
Please verify either the file path exists or the file can be found within a
directory specified by the PATH environment variable. Also check the file mode
to verify the file is executable.

source

I'm sorry, I meant the main tag. However, as mentioned earlier, this change requires pipx to install gcovr.
Since your runner doesn't support pipx, I suggest updating the image to support pipx, as GitHub's default images also support pipx (see this). But if you can't do this, adding a step to install pipx in the workflow may be helpful.
Another hack may be to install gcovr directly before running this action. You can use Arch Linux's package manager to do this, or use pip to install it in the home directory.

Ok, installing pipx seems to be a solution. Not sure if one should expect that or the action could try to install it first via pip or something but that it's in official GitHub images is an argument for the former. Thanks!


Golovinsky refactoring and improvements

I'll resolve conflicts later

TODO:

[ ] Removing / Adding object to the tree
[ ] Removing / Adding object's components

@seigtm, take a look. It's ready to merge


Changed header example in README.

First of all, X-CUSTOM-HEADER doesn't mean anything, you'd probably want it to be X-API-VERSION.
Secondly, x-* headers considered harmful, so let's just make it API-VERSION.

Thanks. I merged this in and also replaced all occurrences of X-CUSTOM-HEADER from the specs and rdoc comments so it's consistent with the docs.

Rock.


Allow existing term update when bulk importing term.csv

Currently the term import only adds new terms, it doesn't update existing ones.
Part of the work for #66 is a "bulk term update" thing to specify the linkage from children to parents -- if that field were included in the export, it would suffice.
To add:

acceptance tests for update
docs about how the term is found -- e.g. updating the term itself will result in a new term

Merged into the develop branch, will be in next launch.

Launched.


Fix failures on nightly scheduled builds

I believe we have a 2nd PR that needs to be merged in order for nightlies to pass:
https://github.com/eclipse/build-openj9/actions

FYI @sophia-guo

Yes, I will make a PR to add other related files, mainly MIT license files.
Also need to do a release for nightly to consume.

All failing with Unable to resolve action `eclipse/build-openj9@v1
@sophia-guo - was I supposed to take an action here, or can you do a release?

v1 has been released last Nov. I didn't see the the failure of failing with Unable to resolve action eclipse/build-openj9@v1
`? Could you please point me to the failure?

yes sorry, I was looking at a run from 3months ago... thanks for creating issues on some of the recent failures...
I know they are rolling out more build changes (cmake stuff), I presume the build instructions are also being updated, and have not looked at the failures in this repo yet so do not know if there is a relationship or not.

With jdk 16 enabled all issues should have been tracked by separated issues. This one is related with the release v1 and MIT licenses, which has been done. So I will close this one.


Update: Implement Custom Cursor Follower Effect with Redux State Management

Issue Title
Implement Custom Cursor Follower Effect with Redux State Management
Issue Description
:red_circle: Enhancement Aim :
To enhance the user experience by implementing a visually engaging custom cursor follower effect that dynamically responds to user interactions.
:red_circle: Changes :

Implement a custom cursor effect that follows the mouse movement.
Change the cursor appearance based on hover states over specific elements (e.g., buttons, links).
Store the cursor state (open/close) in Redux for consistent behavior across components.
Include smooth animations for cursor transitions.
Reference a demo for inspiration: Minimalistic Cursor Effect.

Full name: Tejas Benibagde
What is your participant role? GSSOC - ext , hactoberfest

hey @tejasbenibagde  ,please assign me this issue under GSSOC'24 Extd and hackerfest.

This type of cursor is not required.


Mapping issue: Cannot migrate Related links

I am new to using the solidify migration tool and am having difficulty getting the related link types to export from jira and import to ADO for all issue types.  The parent and child work correctly but not the others.  We are still using the jira server NOT cloud version.  here is the code I have that does not seem to work -- what am I missing in my config file? NOTE: I did look up each one in jira under the advanced JCL to see if the source was correct and they appear to match the names i have listed below.  Could it be on the ADO side?
"link-map": {
"link": [
{
"source": "Epic",
"target": "System.LinkTypes.Hierarchy-Reverse"
},
{
"source": "Parent",
"target": "System.LinkTypes.Hierarchy-Reverse"
},
{
"source": "Child",
"target": "System.LinkTypes.Hierarchy-Reverse"
},
{
"source": "Relates",
"target": "System.LinkTypes.Related"
},
{
"source": "Relates to",
"target": "System.LinkTypes.Related"
},
  { "source": "clones",
    "target": "System.LinkTypes.Related"
  },
  {
    "source": "is cloned by",
    "target": "System.LinkTypes.Related"
  },
  {
    "source": "blocks",
    "target": "System.LinkTypes.Related"
  },
  {
    "source": "is blocked by",
    "target": "System.LinkTypes.Related"
  },
  {
    "source": "is duplicated by",
    "target": "System.LinkTypes.Duplicate-Forward"
  },
  {
    "source": "duplicates",
    "target": "System.LinkTypes.Duplicate-Forward"
  }
]

Here is the link map I usually use for Relates links:
      {
        "source": "Relates",
        "target": "System.LinkTypes.Related"
      },

Other than that, it could be that you either haven't mapped a particular link type, or maybe there are other errors in the migration log that need to be addressed first? This could cause some revisions to fail to import.

@Alexander-Hjelm -- have you successfully been able to migrate the relationship types of clones or is cloned by?  If so would you be willing to share what code  you used for those relationship types as an example for me to see how those worked for you?

Haven't tried myself, but I reckon it would be something like this:
    {
    "source": "is cloned by",
    "target": "System.LinkTypes.Related"
  },

  {
    "source": "clones",
    "target": "System.LinkTypes.Related"
  },

I am having the same issue, the links for the Epic migrate over fine but the liks for other ticket types do not. No errors occur but the links do not appear in the JIRA Export file.
"link-map": {
"link": [{
"source": "Epic",
"target": "System.LinkTypes.Hierarchy-Reverse"
},
{
"source": "Parent",
"target": "System.LinkTypes.Hierarchy-Reverse"
},
{
"source": "Child",
"target": "System.LinkTypes.Hierarchy-Forward"
},
{
"source": "Relates to",
"target": "System.LinkTypes.Related"
},
{
"source": "Duplicates",
"target": "System.LinkTypes.Duplicate-Forward"
},
{
"source": "Clones",
"target": "System.LinkTypes.Related"
},
{
"source": "Relates to",
"target": "System.LinkTypes.Related"
},
.......

Thanks, I'll remove the duplicate relates to. I'll add Cloners too, thanks.

Thanks [new2migration]!!!  adding 'Cloners' worked to get them over, odd because we don't even use it in our JIRA, but whatever works.
It does appear I still have one issue, they come over BUT they do not come over as the correct 'link type', they are all 'Related'. SO I need to troubleshoot that now.

@psaunders2 - There is no "cloned" or "blocked" type relationship in ADO so in the above we mapped ours to "related".  I would suggest reviewing the available link types in ADO and if related if not what is desired select one that exists that may work better.

@Alexander-Hjelm, how should we map Causes and is caused by link types in tool v3.0.328 ?

@anurao98 Please submit your support ticket as a new Issue.


Refactor code to functions

As possible, move code from scripts to functions so as to enable easy use by others. E.g., creating file paths at the top of bianry_to_nc.py.

Created esd_paths function


(fix): The logo and experiment description are missing inside charthub

What happened:
The logo and experiment description are missing inside the charthub for node drain experiment.
What you expected to happen:

How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:

#https://github.com/litmuschaos/chaos-charts/pull/81


I can't type s or c when naming the supports

Preparation

[X] I tested the latest release
[X] I looked at other issues (even the closed ones)
[X] I read the Troubleshooting Guide

FGO server
NA
FGA build number
2074
Describe the bug
title, there is really not much else to be said
Video
title
Device model
Samsung s21+
Android version
11
Screen size
No response
RAM
8

Can't reproduce


thoughts about window.navigator.noUI and page visibility api

Hi,
this is a follow-up of https://github.com/tmpvar/jsdom/issues/642.
The Page visibility API looks like a way for client code to know if it's running in a "half browser" or not:
document.visibilityState == "prerender"
I like that because:

it does not define a non standard property
for some use cases (isomorphic server rendering) the name is natural
the check is harmless, browsers not supporting the api return undefined
it might not even be up to jsdom to set that value - userland can set it to prerender
in its server rendering code if needed.

Interesting. I'd be open to changing this (and removing noUI). Pull request welcome. You'd want to implement the IDL at https://www.w3.org/TR/page-visibility/#sec-document-interface using the new IDL-based architecture discussed in https://github.com/tmpvar/jsdom/blob/master/Contributing.md#architecture

Ok, so can you have a quick look at
https://github.com/kapouer/jsdom/commit/78bfd15688c79008797bab24af6a1525bae40fc4 ?
The choices i've made to always return true for "hidden" and "prerender" for visibilityState seem all right - but you probably have a better grasp of which default values they should be.

Also please check https://github.com/kapouer/jsdom/commit/e1d481be523edd6a61d06c36a210f00ac3460202;
which calls for two decisions to make:

do you want to deprecate navigator.noUI before removing it ?
what is the best replacement to advise ? document.hidden or document.visibilityState == 'prerender' ?

document.hidden can happen quite often in various situations on a real browser with UI.
I met the prerender state on Safari 9 when i started typing the url of a recently visited web page i developed using a client-side library that actually manages the prerender state. Interestingly, Safari runs the web page with that visibilityState, and emits the visibilitychange event when the page becomes visible.
What i like about prerender is the fact that in both cases (server jsdom or client prerendering) the meaning is the same.

do you want to deprecate navigator.noUI before removing it ?

We can just leave it in until the next major version. Add a // TODO MAJOR to do so.

what is the best replacement to advise ? document.hidden or document.visibilityState == 'prerender' ?

The latter sounds better to me, I agree.


"Cannot find module" error due to missing runtime dependency in generated file

context and steps to reproduce
i want to use graph-client in a web service, so i...

follow instructions on https://thegraph.com/docs/en/querying/querying-from-an-application/#graph-client for basic setup: add dev dependency, add .graphclientrc.yml
run graphclient build
reference generated code in .graphclient/ in application code, e.g. execute
run application locally => success
deploy application to external system which requires fresh production build =>  runtime error

status quo

Cannot find module '@graphql-mesh/utils' in generated /app/dist/.graphclient/index.js

expected

generated file /app/dist/.graphclient/index.js has correct runtime dependencies
docs mention how to install peer deps as runtime deps, e.g. npx install-peerdeps -Y @graphprotocol/client-cli

workaround

install all graph-client-related peer deps manually
install all deps seen among generated .graphclient/index.js imports

please try step #2 first since step #1 may not be relevant
example
yarn add @graphql-tools/delegate @graphql-tools/wrap @graphql-tools/utils @graphql-mesh/types @graphql-mesh/types @graphql-mesh/types @graphql-tools/delegate @graphql-tools/merge @envelop/core graphql-tag @graphql-mesh/cache-localforage @whatwg-node/fetch @graphql-mesh/graphql @graphql-mesh/merger-bare @graphql-mesh/http @graphql-mesh/runtime @graphql-mesh/store @graphql-mesh/cross-helpers @graphql-mesh/types

concerns

not documented in https://thegraph.com/docs/en/querying/querying-from-an-application/
huge manual effort - is there a smaller set of meta modules which should be installed as runtime deps?
workaround approach may break when generated index.js refers to new imports

Please create a reproduction on CodeSandbox or StackBlitz. Thanks!


boost::thread_resource_error: Resource temporarily unavailable

Hi,
I'm trying to make your plugin working on Debian 7 64bit, but can't get it to work. I get an error from the boost library or something, as soon as I start connecting to MySQL (see below). The plugin does load though.
I'm using mysql_static.so, mysql client version 5.6.12. Also tried mysql_5.5.so, and compiling the plugin myself, but I can't get it to work.
I had a test server running on a Windows 7 environment aswell with the same code, where it worked fine.
I can't add debug code since the server dies after mysql_connect. Do you have any idea what's wrong?
$ ./samp03svr
Started server on port: 7789, with maxplayers: 30 lanmode is OFF.
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injectorboost::thread_resource_error >'
what():  boost::thread_resource_error: Resource temporarily unavailable
Aborted
Code using:
initMysql()
{
print("Connecting to MySQL...");
MySQL = mysql_connect("<IP_ADDRESS>", "samp", "samp", "password", 3306, true);
new error = mysql_errno(MySQL);
new errorString[100];

format(errorString, sizeof (errorString), "Connect: %i", error);

print(errorString);

}

Looks like your machine doesn't have enough resources to create the internal MySQL threads. Try closing some programs and deactivate the connection pool (set pool_size in mysql_connect to 0) if you don't use parallel queries (mysql_pquery).

Setting the pool_size to 0 seems to have fixed it.
Got some other problems now, but don't have time to debug now.
Thanks for your help! :)

No problem.


container logs are truncated

Environment summary
Ubuntu 16.04 64-bit installed with apt
az version 2.0.23
I have a CLI program that outputs JSON to stdout.
I created a container that outputs over 36000 characters of JSON onto a single line
When I run az container logs -g my-rg -n my-cg --container-name my-container
It only returns the last ~2200 characters.
I ran the same container in ACS and verified that it wasn't anything wrong with the container

I can report that we just ran into the same problem, so it still does not appear solved.

I can report that we just ran into the same problem, so it still does not appear solved.

We have a logic app that creates an Azure Container Instance then gets the logs using the "Get logs from a container instance" step which I beleive uses the same api that "az container logs" uses. On examining the captured logs, sometimes it is complete and sometimes the begining part is missing to a variable degree. If I were to look at the logs directly on the container within Azure Container Instance then the logs are always complete, however when the "Get logs from a container instance" step is run, I see the same truncation.

Same issue here - I have a container that runs uwsgi/flask/nginx. The default behavior is to log to the STDERR logs which lands in the ACI log.
After a while due to lots of output - if an issue is encountered which causes a halt of the process - the cause of the issue is not present in the log due to this ACI truncation.
If truncation is due to Azure only giving limited "Free Space" for ACI instance logs - would be a nice feature to allow us to manually allocate a blob storage to alleviate this issue.

I'm also being impacted by this issue.

Update?

I too am being impacted by this issue.

It's 2024 and I'm still impacted by the issue (.net core app). Impossible to debug startup problems, as I see only useless last lines of the logs.


Module sterk verouderd

De module werkt niet naar behoren en loopt 3 versies achter.
'Get payment methode' werkt niet. Haalt niets binnen.
Module is ook niet compatible met <IP_ADDRESS> zoals beweert op de site.
Er is ook niets gewijzigd behalve de versie naam t.o.v. vorige module.

Hi EvaP76,
I have to use Google Translate, I hope I understood the problem correctly.
We tested the compatibility of ICEPAY Payment Module v2.0.8 with OpenCart 2.2.0 and and haven't found any problems with "Get My Payment Methods" button.

Can you please check if Merchant ID and Secret Key settings are correct?
You can find more information about the module in Manual for merchants and developers
Please let me know if you have any questions.

Thank you for your reply.
But the current version is <IP_ADDRESS>. It’s by far not compatible.
Also in the last version, only the version title has changed, but nothing in the code.
A new compatible version is long overdue.
Thanks.

On 18 Jan 2017, at 11:10, tsygankov<EMAIL_ADDRESS>wrote:
Hi EvaP76,
I have to use Google Translate, I hope I understood the problem correctly.
We tested the compatibility of ICEPAY Payment Module v2.0.8 https://github.com/ICEPAYdev/OpenCart-2.x/releases/tag/2.0.8 with OpenCart 2.2.0 and and haven't found any problems with "Get My Payment Methods" button.
https://cloud.githubusercontent.com/assets/15112699/22059791/fb57b696-dd76-11e6-8e90-09ea46d4c7cd.PNG
Can you please check if Merchant ID and Secret Key settings are correct?
You can find more information about the module in Manual for merchants and developers https://icepay.com/downloads/pdf/manuals/opencart/Manual_2.0.8.pdf
Please let me know if you have any questions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/ICEPAYdev/OpenCart-2.x/issues/5#issuecomment-273435748, or mute the thread https://github.com/notifications/unsubscribe-auth/ANq0kQT323PewYcM0T9hv6OShVrCi-EOks5rTeUtgaJpZM4LlsYW.

Hi EvaP76,
At the moment we do not have a module that is compatible with OpenCart v2.3.x, however we started working on the problem yesterday.
As a workaround you can try using an ocmod extension that fixes v2.2-v2.3 compatibility issues, for example this one. I can't guarantee that if will fix the compatibility issue because we haven't tested this solution yet.

Also in the last version, only the version title has changed, but nothing in the code.

There are some minor changes between v.2.0.7 and v2.0.8 that fix the OpenCart 2.2.0 compatibility issues.
You can review the changes by executing:
git diff 2.0.7 2.0.8
in .2.1.0b we introduced the SendCloud integration.
You can review the changes by executing:
git diff 2.0.8 2.1.0b
Please let me know if you have any other questions.


Put terraform-docs imports after 3rd-party packages

Prerequisites
Put an x into the box(es) that apply:

[ ] This pull request fixes a bug.
[ ] This pull request adds a feature.
[x] This pull request enhances existing functionality.
[ ] This pull request introduces breaking change.

For more information, see the Contributing Guide.
Description
Enforcing goimports -local <string> to put terraform-docs imports and packages after 3rd-party packages.
Issues Resolved
List any existing issues this pull request resolves.
Checklist
Put an x into all boxes that apply:

[ ] I have read the Contributing Guidelines.

Tests

[ ] I have added tests to cover my changes.
[ ] All tests pass when I run make test.

Documentation

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Code Style

[x] My code follows the code style of this project.

Codecov Report

Merging #264 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #264   +/-   ##
=======================================
  Coverage   81.68%   81.68%
=======================================
  Files          34       34
  Lines        1796     1796
=======================================
  Hits         1467     1467
  Misses        274      274
  Partials       55       55


Remove reference in README to web-browsers

See comment on #15

@sanfilip can we close this PR?

Hi TBBle.  We are including your doc change as-is in the latest readme as part of a new release.  Thanks for clarifying this.


Improve position for ControlledMenu with anchorPoint

Hi everyone,
Here is a potential fix / improvement for this issue: https://github.com/szhsin/react-menu/issues/694
Hope you like it, leave me comment if you want to change something here. Also, you can cancel it
and add it by yourself if you want.
Thank you for this awesome library!

Hi @panciumihai ,
Thanks for creating this PR.
You made a good point that context menu could use the same position implementation as a dropdown menu, by treating the anchor point as a one-pixel anchor rectangle.
However, instead of duplicating a similar function with the dropdown menu, context menu should re-use the dropdown menu implementation by passing in the one-pixel rectangle into the function. I have implemented the change in a new commit.


egressgw: steer traffic to the right interface using BPF

see commits
Fixes: https://github.com/cilium/cilium/issues/23504

/test

/test

/ci-verifier

/test

/test

/test

/test

/test

/test

/test

BTW, when doing upgrade from v1.14 -> v1.15, shouldn't we remove old IP rules/routes?

good point :bulb: yes, I'll add back some logic to do the cleanup when the manager is initialized :+1:

/test

Sorry for the drive-by post-merge comment/review. I just noticed this change while I was investigating how the old feature worked (looking into auto-direct-node-routes improvements). Something that confused me for a bit: The documentation still mentions this flag. Since the flag is now a no-op, should the docs be removed too?
https://docs.cilium.io/en/latest/network/egress-gateway/#eks-s-eni-mode

Sorry for the drive-by post-merge comment/review. I just noticed this change while I was investigating how the old feature worked (looking into auto-direct-node-routes improvements). Something that confused me for a bit: The documentation still mentions this flag. Since the flag is now a no-op, should the docs be removed too?
https://docs.cilium.io/en/latest/network/egress-gateway/#eks-s-eni-mode

Yep, we'll still need to go through the whole doc update dance (also mention the deprecation etc) :+1:.


Fixed the css aligning;

Changed the last breadcrumb centering.
Created additional css rules for the list to align all items of the list properly

An additional style applied conditionally: when isLast is true, it applies the styles.link styles along with the alignItems: 'center' property; otherwise, it applies only the styles.previous styles. I can see that line 26 is commented and I believe it should be removed.

The promlem is not in the conditinal render, but in the MUI styles applying. I commented the previous solution to check whether we would be able to align these items with another solution.

An additional style applied conditionally: when isLast is true, it applies the styles.link styles along with the alignItems: 'center' property; otherwise, it applies only the styles.previous styles. I can see that line 26 is commented and I believe it should be removed.

The promlem is not in the conditinal render, but in the MUI styles applying. I commented the previous solution to check whether we would be able to align these items with another solution.

So, if now styles works correct we can remove commented line?

An additional style applied conditionally: when isLast is true, it applies the styles.link styles along with the alignItems: 'center' property; otherwise, it applies only the styles.previous styles. I can see that line 26 is commented and I believe it should be removed.

The promlem is not in the conditinal render, but in the MUI styles applying. I commented the previous solution to check whether we would be able to align these items with another solution.

So, if now styles works correct we can remove commented line?

Yes, I removed it


[ic-search-bar] a11y violations

Summary of the bug
E2E a11y testing on ic-search-bar has shown critical violations. A ticket (#1939) already exists for an aria-allowed-attribute accessibility violation for ic-search-bar/ic-select, but creating more a11y tests for ic-search-bar has revealed further violations: aria-required-attribute and aria-valid-attribute (see below).
🪜 How to reproduce
Uncomment the commented out a11y tests in the ic-search-bar Cypress tests and run tests.
See the errors.
To see the aria-required-attribute and aria-valid-attribute errors specifically, run the following tests:
"should render search bar with options - no filtering"
"should render search bar with custom empty option list text"
"should render search bar with characters until suggestion set - no show"
"should render search bar with characters until suggestion set - show"
"should render search bar with long option labels"
📸 Screenshots or code

🖥 📱 Device

Type: Cypress a11y testing

🧐 Expected behaviour
All a11y tests should pass. To check this please uncomment the a11y tests in the ic-search-bar Cypress tests.

Looks like its complaining about not having aria-controls and complaining about having aria-owns so is it not just changing this line - aria-owns={menuRendered ? menuId : undefined}

These issues and similar ones have been seen before. Some useful links for context around aria, ids and shadow-dom:

https://nolanlawson.com/2022/11/28/shadow-dom-and-accessibility-the-trouble-with-aria/
https://caniuse.com/?search=ariaControlsElements

issue seems to be caused by the aria-owns & aria-controls being set on the  element inside the shadowDom of ic-text-field, which cannot refer to the ic-menu


iFrame containing Angular app won't resize smaller

The problem
I'm struggling with getting the iframe to resize smaller when the iframe's content shrinks. It will resize larger just fine but will then stay at the larger size no matter what happens to the content of the iframe.
If the "log": true option would log which heightCalculationMethod is being used and what the calculated values are once it's done retrieving them it may help in debugging this issue. As it is, it simply reports:
[iFrameSizer][pwProgramsAndMajorsAppFrame] Trigger event: parentIFrame.size() iframeResizer.contentWindow.js:140
[iFrameSizer][pwProgramsAndMajorsAppFrame] No change in size detected iframeResizer.contentWindow.js:140

My implementation
My iFrame contains an Angular app. I've added a manual resize within the Angular controller in a watch:
$scope.$watch(function() {
    if(!parentIFrame) {
        return;
    }

    setTimeout(function() {
        parentIFrame.size();
    }, 0);
});

The $watch function in Angular will trigger on each digest cycle; the relevance here is that it also triggers after anything that may change the page appearance or size. I added this as the autoResize was also not correctly detecting that the iFrame's content had gotten smaller.
I've tried this with every available heightCalculationMethod including "lowestElement" which claims:
[iFrameSizer][pwProgramsAndMajorsAppFrame] Trigger event: parentIFrame.size() iframeResizer.contentWindow.js:140
[iFrameSizer][pwProgramsAndMajorsAppFrame] Parsed 132 HTML elements iframeResizer.contentWindow.js:140
[iFrameSizer][pwProgramsAndMajorsAppFrame] Element position calculated in 1ms iframeResizer.contentWindow.js:140
[iFrameSizer][pwProgramsAndMajorsAppFrame] No change in size detected iframeResizer.contentWindow.js:140

My iframe:
<iframe id="pwProgramsAndMajorsAppFrame" style="width: 100%;" src="myWebsite.example"></iframe>

Browser: This occurs in all of:

Chrome 50.0.2661.75 (64-bit)
Firefox 43.0.1
Safari 9.1

iframe-resizer: Version 3.5.3
Angular: Version 1.4.8
Unfortunately I'm unable to provide a link to my test page as the content is under NDA, but if an example is needed I may be able to isolate the issue in a generic example.
Something I've noticed that may help is that the html and body elements of my iframe's content page have their height set to "auto" by default and will take on the height of the iframe that iframe-resizer sets, though the top-level element within the body is the one that is changing size. By using the Chrome inspector and removing the height attribute on the iframe itself, it will resize up to the appropriate size on the next resize if the content is larger (but never smaller).

Most likely a CSS issue, see troubleshooting section of docs.

I'll take a closer look at the docs then and get back to you early next week. Thanks for responding quickly.

Would you consider adding the additional logging or would you accept a pull request to that effect?

The resize method is logged when set or changed, look further back in the log.

No I'm referring to the actual calculated values of the height and width that iframe-resizer uses to determine if the page changed in size.
[iFrameSizer][pwProgramsAndMajorsAppFrame] Trigger event: Mouse Down iframeResizer.contentWindow.js:140
[iFrameSizer][pwProgramsAndMajorsAppFrame] No change in size detected iframeResizer.contentWindow.js:140
[iFrameSizer][pwProgramsAndMajorsAppFrame] Trigger event: Mouse Up iframeResizer.contentWindow.js:140
[iFrameSizer][pwProgramsAndMajorsAppFrame] No change in size detected iframeResizer.contentWindow.js:140
[iFrameSizer][pwProgramsAndMajorsAppFrame] Trigger event: mutationObserver: [object HTMLDivElement] childList iframeResizer.contentWindow.js:140
[iFrameSizer][pwProgramsAndMajorsAppFrame] No change in size detected iframeResizer.contentWindow.js:140

It doesn't log that information.

Here is a Plunker that demonstrates the issue. This has no custom CSS.
https://plnkr.co/edit/0VxXHEi8u88gw2wDebjY?p=preview

@davidjbradshaw It seems that adding
<!DOCTYPE html>

to the top of the iframe's content was enough to get the iframe to downsize, but it would cut off the bottom few pixels, and changing the heightCalculationMethod to "max" cleared that up. Strange!

+1  worked for me too. How strange!
This folks is why if you solve your problem you should update your tickets!
Thx

Remove height: 100%; from CSS  of body tag solves to me.


Standardize PowerShell SemVer Parsing Logic

We have PowerShell SemVer parsing logic duplicated in a couple locations and should consolidate and standardize them.

https://github.com/Azure/azure-sdk/blob/master/eng/scripts/Update-Release-Versions.ps1#L26-L58
https://github.com/Azure/azure-sdk-for-net/blob/master/eng/Update-PkgVersion.ps1#L48
https://github.com/Azure/azure-sdk-for-cpp/blob/master/eng/Update-PkgVersion.ps1#L48

Originally posted by @weshaggard in https://github.com/Azure/azure-sdk-for-cpp/pull/52

Thanks for tackling this @damirault


Server Request Help: Instances vs References

With Instaloader, one can create a Profile instance from a given username with the following snippet of code:
loader = Instaloader()
loader.load_session_from_file(login_name)
profile = Profile.from_username(loader.context, target_profile)

Q1. Am I correct in assuming the last line makes a single request to the Instagram server? Am I also correct in assuming I am creating a data object (and not a reference) that is being stored in the "profile" variable?
target_full_name = profile.full_name
Q2. Am I correct in assuming this does not make a request to the server, but retrieves a parameter from the data object in the profile variable?
followers = profile.get_followers()
Q3. Am I correct in assuming this makes another request to the server and stores the data object in the "followers" variable? The documentation says the return type is "NodeIterator[Profile]". Does this mean I am storing the data object for each profile from the target's followers? Or am I making a reference to each of those profiles?
Q4. If I am storing the data object for each profile, does that mean extracting information from the data object for these profiles will NOT make additional requests to the server? (Because I already have it stored in the "followers" variable?)
Or does it operate as a reference and thus: each moment I extract additional parameters from a follower profile, it will require an additional request to the server?

With Instaloader, one can create a Profile instance from a given username with the following snippet of code:
loader = Instaloader()
loader.load_session_from_file(login_name)
profile = Profile.from_username(loader.context, target_profile)

Q1. Am I correct in assuming the last line makes a single request to the Instagram server? Am I also correct in assuming I am creating a data object (and not a reference) that is being stored in the "profile" variable?

Yes, Profile.from_username() does make a single request to Instagram, which contains most of the profile metadata, and returns a Profile instance with that data included.

target_full_name = profile.full_name
Q2. Am I correct in assuming this does not make a request to the server, but retrieves a parameter from the data object in the profile variable?

Yes, full_name is already included in the data structure returned by Profile.from_username() and accessing it will in this case not trigger any further requests.

followers = profile.get_followers()
Q3. Am I correct in assuming this makes another request to the server and stores the data object in the "followers" variable? The documentation says the return type is "NodeIterator[Profile]". Does this mean I am storing the data object for each profile from the target's followers? Or am I making a reference to each of those profiles?
Q4. If I am storing the data object for each profile, does that mean extracting information from the data object for these profiles will NOT make additional requests to the server? (Because I already have it stored in the "followers" variable?)
Or does it operate as a reference and thus: each moment I extract additional parameters from a follower profile, it will require an additional request to the server?

get_followers() makes one request to the server and returns a NodeIterator. Some of the followers are already included with a thin data structure, containing only basic information. Iterating this iterator or accessing the items it yields will trigger further requests as required.

Thank you so much! So:
   profile = Profile.from_username()

will already have the .userid, .username and .is_private properties, but will:
followees = profile.get_followees()

also have those same properties? They seem like basic properties to me, but from reading the documentation and nodeiterator.py file I didn't discern that those properties are also retrieved (only the username, I think). So I am led to believe simply requesting the userid of each followee from followees would be an additional request - is that correct?


unable to unpin from taskbar

unable to unpin certain items from taskbar
for some it works for some it doesnt

Try the latest version 1.9

1.9 didn't change anything, some apps have their context open, some don't...

1.9 didn't change anything, some apps have their context open, some don't...

it did fix it for me but for version 1.9 you have the option to disable Shell from being used on taskbar and use the original windows one by adding this reg key
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Nilesoft\Shell\Disable]
"Taskbar"=dword:00000001


GEOWAVE-116: GeoTools query example

GeoTools query example to address #116

Coverage decreased (-0.32%) to 62.86% when pulling 8059ac942325409992dd40cc5a39191dcb7d3a94 on GEOWAVE-116 into 60bbef801f046a5ff8e39e2d4e6a9a28cc27abe8 on master.

Coverage decreased (-0.32%) to 62.86% when pulling 8059ac942325409992dd40cc5a39191dcb7d3a94 on GEOWAVE-116 into 60bbef801f046a5ff8e39e2d4e6a9a28cc27abe8 on master.


Create cli recovery

not really an issue but an idea.
Create a cli based recovery just in case xserver breaks and we cn acsess the gui recovery.

Well, this runs out of a seperate stateless system with it's own kernel,
but by tapping the reboot menu, and then selecting command line mode, you
can access the full suite of recovery tools.
On Fri, Jul 10, 2020, 10:18 AM puntillol59<EMAIL_ADDRESS>wrote:

not really an issue but an idea.
Create a cli based recovery just in case xserver breaks and we cn acsess
the gui recovery.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dahlia-os/system-recovery/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEOTEHHW3YUVPUDVD7AQZTTR24PM3ANCNFSM4OWULWZA
.

ok, closing issue


Update to containerd 1.3.0 vendor

Signed-off-by: Justin Terry (VM<EMAIL_ADDRESS>

Why did this need to be updated?


bump ws to 7.2.0

Is there a particular reason?

the version 7.0.0 of ws has some fixes that I am facing in my setup right now. The error I am facing for readyState is the same as mentioned in their release notes.
Also, they seem to have dropped support for node 6.

Alright, thanks for the clarification.

When can we expect a new release with this updated dependency?

Right now: 0.28.1.

Thanks


Feature dataset checkpoint strategy

Description
This PR modifies enable_checkpoint in the Pipeline.generate to allow a more behaviour during the generation (saving while generating).
The following example allows saving the CustomDataset every 100 generations to disk.
By default, it will use DatasetCheckpoint(save_frequency=-1), which replicates the previous behaviour of enable_checkpoints=True.
from distilabel.utils.dataset import DatasetCheckpoint

pipe.generate(
    ...,
    dataset_strategy=DatasetCheckpoint(save_frequency=100)
)

Closes #168  and #193.

Added a small reference in the docs, inside a new section of the Pipeline from the concept guides


Fix RequiredKeys and OptionalKeys

Introduces a simple fix that allows the compiler to more easily recognize that both RequiredKeys and OptionalKeys for some type A are assignable to keyof A. This fix allows, for example, to easily define a generic type that contains all required keys of another:
type RequiredPart<A extends object> = Pick<A, RequiredKeys<A>>

Before this fix, the user would have had to give a further hint to the compiler by specifying the second type parameters of Pick in the example above as an intersection between RequiredKeys<A> and keyof<A> to obtain the same effect.

Going to close this, thanks @stefanobaghino for this PR and @ajafff for reviewing


More split outs from #339

Ok, these commits should complete #324.
I'll start on the next after review.

Looks good beside the few nits I mentioned.

Fixed the nits. Thanks for the review.

That was quick :-) Merging…


Escape characters shown on user preferences screen

See below:

This will need a fix for both 2.6.9 and 2.7.0.
This ticket is to fix for 2.6.9.
Please create another issue for 2.7.0 by cloning this one. You'll need to create a PR against the 2.6.9 release branch and one against master.
The change that broke this is here:
https://github.com/rancher/dashboard/pull/6822/files#diff-316ed9b2628e1438c50d24acd6d498b6957248543643f69b63528eee0761b1ddL210
You need to put that line back to what it was.

@bisht-richa This ticket needs a forward port tickets created.

Ticket #6958 - Test Results - ✅
With Docker on a single-node instance:
Verified on rancher v2.7-8062f1e3ab7bff870dfab195ff699a308644168a-head:

Fresh install of rancher v2.7-head
Navigate to User Preferences > Advanced
Verified - No escape characters shown; as expected

Screenshot:


fix(Pipelines): run pipeline with cloudrun argument

The run of pipelines in local with docker was not working properly.
Changes
Please list / describe the changes in the codebase for the reviewer(s).

Use cloudrun argument instead of run in container launch cmd.

The run command is supposed to work with a mounted volume containing the pipeline and is used with the CLI of openhexa-sdk-python. "cloud run" is the one where we download the pipeline from the server and run it in a pod/container depending of the architecture. Since it is supposed to mimick what we'll have on the production servers, I think cloudrun is the correct command to run.

Ok, so I guess that's it's more a naming issue imho. I'll write that down somewhere else.


Change access permissions to single API action

This may have already been done or explained, but I haven't been able to find it anywhere.
I'd like to be able to access the getuserstatus action for any specified key without giving full admin rights to that key. Thank you.

This is not possible. Users are not allowed to fetch information about other users.
I would strongly suggest not doing this. The status includes each users balance on their account. Exposing this information to anyone will allow attackers to search for potential targets with many coins.

Some of that information is already exposed on the donors page and the
stats pages
I assume the availability of those usernames and transaction volumes has
already been considered. Users can choose to show up anonymously, which is
a big difference.
On Sun, Jan 3, 2016 at 5:27 AM Sebastian Grewe<EMAIL_ADDRESS>wrote:

This is not possible. Users are not allowed to fetch information about
other users.
I would strongly suggest not doing this. The status includes each users
balance on their account. Exposing this information to anyone will allow
attackers to search for potential targets with many coins.
—
Reply to this email directly or view it on GitHub
https://github.com/MPOS/php-mpos/issues/2479#issuecomment-168489947.

As far as I know there is no direct public available API endpoint or website overview that shows the exact amount of coins in a users account. Donations just shows what they have donated, not what they currently have in their account.
As for your original question, there is no such system in place allowing permissions to specific API functions that would allow a user to cross check for other users unless they are admins.


Using python for lambda functions

Environment information
using amplify v2

Description
hi would like to use python for some of the lambda functions. It looks like this is not supported yet but can see this.
https://github.com/aws-amplify/amplify-backend/issues/1543
Assuming this issue will not be supported soon - What would be the next best approach to do this? Is it to create an API gateway and cognito auth and run the queries that way or is there a better approach?

Hey @cookiejest, thank you for reaching. As the RFC: https://github.com/aws-amplify/amplify-backend/issues/1543 provides this is currently not supported. But wanted to provide some information on this.
To create a python function you can utilize the CDK Lambda construct: https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_lambda-readme.html
and build the function using local commands as the construct will default to docker to build the function and the CICD deploy may fail.
Also, CDK does provide a pythonFunction construct but do note this is experimental.
Additionally, you can create the function on the console or a tool and reference the function for your use cases using the fromFunctionArn method.
But do note that functions created or referenced by CDK cannot be used with the Data schema or use other attributes such as the access property to provide access to the function directly.

Ok, as I am not able to use experimental approach, I decided to deploy python lambda functions separately in another repo and keep amplify updated via graphQL. However I havn't figured out a clean way to add custom graphql yet within the amplify v2.
I listed this seperately under #1838

You can try this simple approach to create a custom python lambda resource<EMAIL_ADDRESS>

cool! What user will the custom function run under? If want to add the equivilent of only authenticated, is it possible?

cool! What user will the custom function run under? If want to add the equivilent of only authenticated, is it possible?

#1602 You can check my pr, it's allowing to use custom runtimes in data resources.ts, you can use go, python functions in graphql query and mutations

cool! What user will the custom function run under? If want to add the equivilent of only authenticated, is it possible?

#1602 You can check my pr, it's allowing to use custom runtimes in data resources.ts, you can use go, python functions in graphql query and mutations

i saw it. I can see it's blocked at the moment as the AWS team would need to do additional house keeping to support it properly, I cannot risk using the separate branch for my project unfortunately!

You can try this simple approach to create a custom python lambda resource<EMAIL_ADDRESS>
Thanks, this looks more stable but has to introduce docker complexity. Maybe it would be better if had an example deploying amplify app and associated resources via SAM so amplify can be adopted by people already with a deployment pipeline and just using amplify for the front end auth with cognito?
Thanks!

cool! What user will the custom function run under? If want to add the equivilent of only authenticated, is it possible?

#1602 You can check my pr, it's allowing to use custom runtimes in data resources.ts, you can use go, python functions in graphql query and mutations

i saw it. I can see it's blocked at the moment as the AWS team would need to do additional house keeping to support it properly, I cannot risk using the separate branch for my project unfortunately!

You can try this simple approach to create a custom python lambda resource<EMAIL_ADDRESS>
Thanks, this looks more stable but has to introduce docker complexity. Maybe it would be better if had an example deploying amplify app and associated resources via SAM so amplify can be adopted by people already with a deployment pipeline and just using amplify for the front end auth with cognito?
Thanks!

You don't need to use docker, you can bypass this

@MarlonJD any example of how?

Hey @cookiejest,
You can check this https://github.com/aws-amplify/amplify-backend/pull/1602#issuecomment-2209424964 for more context.
Additionally, you'll need the changes from PR #1602. You can cherry-pick and use them as needed. I've also added related documentation here, but it's not merged yet.

ok cool that looks more clear, i would start using this when it gets merged into the main!


Message not delivered for large audience. V5.5.1

The Company Communicator App version 5.5.1 has been deployed successfully on the production tenant. However, while sending messages to 'everyone in chat', there's been a significant failure rate of 40-50%, affecting 80,000 out of 140,000 users. Despite the error message indicating a failure to install the user app due to unavailability in the App catalog, this doesn't seem to be the case universally. Further investigation reveals 404 and transportation connection errors for the failed requests in the App Insight. Interestingly, previous versions (V5.4) of the app were able to broadcast messages seamlessly to 150,000 users. The query now is to identify the potential issues with this current version of the app. Any insights or feedback on this matter would be highly appreciated.

Hi @itsmeprodyut ,
Thanks for raising the query. Please confirm on the below queries.

Could you please share the export data of one message which delivered to all 150k users in v5.4 and one with 80k failure in latest version
Once you updated to the latest version, did you observe any gradual increase or decrease in the success count?

Thank you for your attention to the ongoing issue we're encountering with our Microsoft Teams app deployment.
To provide some context, we have initiated a separate deployment of version 5.5.1 to a distinct resource group, accompanied by a dedicated Azure AD app registration. This approach was undertaken to prevent any potential conflicts with the previous version, which remains active. However, as the previous version is incompatible with New Teams, we have maintained the Azure resources for this version while we ensure the successful integration of the new version.
Unfortunately, despite our efforts, the installation of the app for approximately 80,000 users has failed after an extended period of 4 to 5 hours. Regrettably, due to the sensitive nature of client data, we are unable to share detailed logs or information in an open forum. Our client is a significant entity with an established unified support system with Microsoft, emphasizing the importance of confidentiality and stringent data handling protocols.
Upon further investigation, we observed that the proactive installation settings were incorrectly configured for the data-function and send-function, with the values set to false. Subsequent adjustments were made to set these values to true for both the prep-function and data function. As a result, we re-initiated the broadcasting, successfully reaching 60,000 out of 150,000 users. While this adjustment yielded a notable increase in user reach, it raises questions about the necessity of such changes, as outlined in a relevant troubleshooting blog.
We suspect that the installation failure for the remaining 80,000 users may be attributed to throttling issues or other technical constraints. As sharing logs and detailed information publicly is not feasible, we propose re-initiating this discussion internally with Microsoft and in collaboration with our client through our unified channel. We believe that involving your team in this investigation could provide valuable insights and expedite the resolution process.
Given that our environment is in production, with approximately 140,000 real-time users, replication in a UAT/DEV environment is impractical. Furthermore, testing by repeatedly sending messages from production to live users is not viable due to potential disruption.
We appreciate your understanding and support in addressing this critical issue. Please let us know the best course of action to proceed with collaboration and investigation.

Hi @gsv022 ,
We have retry sending message today and this time it has failed for 37K users. Looks like there is an increase of numbers in each iteration. Now we have 37K users left for the proactive installation and that will potentially work in next iteration ! Any suggestion ?

Hi @itsmeprodyut ,
We will get back to you with proper response soon


Fix indentation

Screenshot before changes:

Screenshot after changes:

Thanks for the PR!
Can you remove the one on the spacing for clip1? It's actually not intended to have a space after the ## so that you can just remove the commenting and have it be in line for use in the code directly.
Otherwise this looks good.

@mvirgo Thanks for the response :)
I have done the required changes. Please review.

Merged, thanks again!


Drop PyTorch 1.7 testing from the CI

What does this PR do?
For preparing the upcoming release, we plan to drop PyTorch 1.7 testing from the CI. Partially fixes https://github.com/PyTorchLightning/pytorch-lightning/issues/12161.

Does your PR introduce any breaking changes? If yes, please list them.
Waiting for the CI to turn green.
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃
cc @tchaton @rohitgr7 @akihironitta @carmocca @borda

The CI section in README.md needs updating, too.

Thanks, @akihironitta! Done. https://github.com/PyTorchLightning/pytorch-lightning/blob/drop/pytorch-1.7/README.md

@awaelchli thanks! We plan to do those in a separate PR as per the linked issue description.


Bad pagination logic in JDBC user store manager when filtering with identity and non-identity claims

Describe the issue:
We discovered a problem during the investigation of an issue where the SCIM2/Users API returned only 2 results despite setting count to 3 and having a large totalResults value.
The issue arises due to incorrect offset calculation in the pagination logic, specifically the unnecessary subtraction of the offset value by 1 before it's used in the SQL query, leading to overlapping results the first and second pages:
Finished reading results from query: SELECT . . . LIMIT 3 OFFSET 0
Got 3 users in the result: [SECOND/aaron42, SECOND/adam85, SECOND/adrianasullivan]

Finished reading results from query: SELECT . . . LIMIT 3 OFFSET 2
Got 3 users in the result: [SECOND/adrianasullivan, SECOND/agonzalez, SECOND/aguirrejason]

Here you can see the repeated username adrianasullivan at the end of the first page and at the beginning of the second.
For additional context, these logs were manually added at UniqueIDJDBCUserStoreManager::executeQueryAndGetUsernames [1] and UniqueIDJDBCUserStoreManager::doGetUsernameListWithID [2]:
private List<String> executeQueryAndGetUsernames(Connection dbConnection, SqlBuilder sqlBuilder,
                                                 FilterConfigs filterConfigs, String type)
        throws SQLException {

// . . . [omitted for brevity] . . .

            try (ResultSet rs = prepStmt.executeQuery()) {
                while (rs.next()) {
                    processUsernameResultSet(rs, usernames);
                }
                // added extra log below
                log.info(String.format("Finished reading results from query: %s", rs.getStatement().toString()));
            }
        }
    }
    return usernames;
}

@Override
protected UniqueIDPaginatedUsernameSearchResult doGetUsernameListWithID(Condition condition, String profileName,
                                                                        int limit, int offset, String sortBy,
                                                                        String sortOrder)
        throws UserStoreException {

// . . . [omitted for brevity] . . .

			usernames = executeQueryAndGetUsernames(dbConnection, sqlBuilder, filterConfigs, type);
			// added extra log below
			log.info(String.format("Got %d users in the result: %s", usernames.size(), usernames));
			result.setUsers(usernames);

// . . . [omitted for brevity] . . .
}

It's important to note that there are no duplicate user entries in the database. The duplicates observed in the logs are a result of the faulty pagination logic.
This was confirmed by checking the same logs after removing the subtraction in the UniqueIDJDBCUserStoreManager::adjustOffsetForDatabase method [3]:
private void adjustOffsetForDatabase(String type, OffsetLimit offsetLimit) {
	// removed subtraction
    offsetLimit.setOffset(Math.max(offsetLimit.getOffset(), 0));

// . . . [omitted for brevity] . . .
}

Result:
Finished reading results from query: SELECT . . . LIMIT 3 OFFSET 0
Got 3 users in the result: [SECOND/aaron42, SECOND/adam85, SECOND/adrianasullivan]

Finished reading results from query: SELECT . . . LIMIT 3 OFFSET 3
Got 3 users in the result: [SECOND/agonzalez, SECOND/aguirrejason, SECOND/ahoward]

The reason why this can cause missing results in the SCIM2/Users endpoint (and the second problem in this pagination logic) is due to how the while loop [4] depends on the size of aggregateUsernameList in the condition to stop iterating, even though there can be duplicates in the list returned from getFilteredUsernames; causing the loop to exit early and collecting fewer users than necessary.
Duplicates are removed after the loop has exited [5], which can reduce the size of aggregateUsernameList below the requested count, but the loop doesn't continue to fetch more users. Ideally, we would've used a Set rather than a List to avoid duplicates while running the loop.
Again, please note there are no duplicate user entries in the database.
Please see the gist [6] for an example of this happening. The values were based on our reproduction attempt of the issue.
How to reproduce:

Set up an Identity Server 5.11.0 and MySQL instance.
Add the below to the deployment.toml file:

[scim2]
enable_complex_multivalued_attribute_support = true
consider_max_limit_for_total_results = false

[scim2_multi_attribute_filtering]
use_pagination = true

Start the server with --debug 5005, attach the JVM to an IDE with the carbon-kernel repository checked out in the tag corresponding to the component version, and add a breakpoint at [7]. Optionally, you can add extra log lines, build the component, and add it to the patches directory.
Create a secondary MySQL JDBC user store.
Create some users and populate their profiles with values for both identity and non-identity claims. In our test, we created two custom claims and used http://wso2.org/claims/accountState for the identity claim; removing the read-only flag in the scim2-schema-extension.config and adding the custom claims too. Then, we used a Python script to run POST requests to the SCIM2/Users endpoint and populate the user store domain.
Run a GET SCIM2/Users request with a mix of identity and non-identity claims in the filter, specify the user store domain in the domain, and include non-zero pagination values to count and startIndex.
See the repeated result in the first and second iteration.

Note: Reproducing the missing results in the SCIM2/Users response is hard, since it's a very specific edge-case scenario. You can see the gist [6] for a simulation based on a real reproduction attempt.
Expected behavior:
The OFFSET clause in a SQL query is used to skip a specified number of rows (inclusive 0-based index) before starting to return rows from the query. Therefore, it shouldn't get subtracted by 1.
Also, if we're relying on the size of a collection to determine the end of a iteration, it shouldn't contain duplicates.
Environment information:

Product Version: IS 5.11.0 (likely affecting more recent major versions)
Database: MySQL
Userstore: JDBC

[1] https://github.com/wso2/carbon-kernel/blob/f22e659eb79c5ffe91498d3ab832dcad13989524/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/jdbc/UniqueIDJDBCUserStoreManager.java#L3606
[2] https://github.com/wso2/carbon-kernel/blob/f22e659eb79c5ffe91498d3ab832dcad13989524/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/jdbc/UniqueIDJDBCUserStoreManager.java#L3565
[3] https://github.com/wso2/carbon-kernel/blob/f22e659eb79c5ffe91498d3ab832dcad13989524/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/jdbc/UniqueIDJDBCUserStoreManager.java#L3674
[4] https://github.com/wso2/carbon-kernel/blob/f22e659eb79c5ffe91498d3ab832dcad13989524/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/AbstractUserStoreManager.java#L16787-L16811
[5] https://github.com/wso2/carbon-kernel/blob/f22e659eb79c5ffe91498d3ab832dcad13989524/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/common/AbstractUserStoreManager.java#L16814
[6] https://gist.github.com/vfraga/df83deef1551075f89a9fa48f48b08e2
[7] https://github.com/wso2/carbon-kernel/blob/f22e659eb79c5ffe91498d3ab832dcad13989524/core/org.wso2.carbon.user.core/src/main/java/org/wso2/carbon/user/core/jdbc/UniqueIDJDBCUserStoreManager.java#L3593

This issue is not reproducible with the latest updates of the product. Hence closing the issue.


Add ease to switch componet's toggle animation

This simply adds an ease to make the toggle animation feel more natural and less linear.
Before:

After:

Note that even though I recorded these before/after gifs in 60fps, they may not be an accurate representation of the animation and obviously are not good as the browser live demo. So I suggest to see it in action ;)

Don't notice any difference with this one I'm afraid :(

Don't notice any difference with this one I'm afraid :(

That's weird, you should be able to see a difference, this is something that is also documented in Tailwind CSS docs and is a noticeable feature. Maybe try increasing the duration and see if your eyes can catch that ?
Either way I agree that this can be considered a minor tweak, but would definitely say it's the little things that make it nice

I'll take another look :)


org.gradle.internal.os.OperatingSystem.current().isFreeBSD() doesn't exist

This code
        if (!(org.gradle.internal.os.OperatingSystem.current().isLinux()
                || org.gradle.internal.os.OperatingSystem.current().isFreeBSD()
                || org.gradle.internal.os.OperatingSystem.current().isMacOsX())) {

Fails:
> No signature of method: org.gradle.internal.os.OperatingSystem$FreeBSD.isFreeBSD() is applicable for argument types: () values: []

org.gradle.internal.os.OperatingSystem.current().isFreeBSD() needs to be replaced with org.gradle.internal.os.OperatingSystem.current().getName().contains("FreeBSD") instead for it to work.
However, https://docs.gradle.org/current/javadoc/org/gradle/nativeplatform/platform/OperatingSystem.html says that isFreeBSD() should be available.
gradle-5.0 on FreeBSD 12

We've seen some unofficial distribution on FreeBSD if I remember correctly. Can you please clarify how did you install Gradle 5.0 on your FreeBSD? It would be great if you can paste gradle -v output here.

gradle is installed from the package pkg install gradle.
$ gradle -v

Welcome to Gradle 5.0!

Here are the highlights of this release:
 - Kotlin DSL 1.0
 - Task timeouts
 - Dependency alignment aka BOM support
 - Interactive `gradle init`

For more details see https://docs.gradle.org/5.0/release-notes.html

------------------------------------------------------------
Gradle 5.0
------------------------------------------------------------

Build time:   2018-11-26 11:48:43 UTC
Revision:     7fc6e5abf2fc5fe0824aec8a0f5462664dbcd987

Kotlin DSL:   1.0.4
Kotlin:       1.3.10
Groovy:       2.5.4
Ant:          Apache Ant(TM) version 1.9.13 compiled on July 10 2018
JVM:          1.8.0_212 (Oracle Corporation 25.212-b04)
OS:           FreeBSD 12.0-STABLE amd64

You're looking at two different types with the same name.  The internal API doesn't have a isFreeBSD method. It's best you don't use org.gradle.internal types as they can change without warning.


Do we an option to "Enable Camera by default" ?

Hi Team
We have an option to hide camera but we don't have option to set the default value for it, similar to Mic.

Greetings! I am acknowledging your github issue. We will take this back to the team and try to find you an answer soon!

https://github.com/Azure/communication-ui-library/discussions/3379
I would like to focus your attention to the middle of the doc where we talk about setting the default camera setting

This is of course based on if there is a valid camera connected as well. Try it out and hopefully this helps? We would love to hear if this was able to solve your issue!

Hi @alkwa-msft
The api adapter.joinCall will skip the config screen. It is not what we want, we want to toggle the Camera On by defaut in the Config Page.

Hi @lovedota, to toggle the camera on, or set a different default camera, you can use the adapter interface:
// Start mic unmuted
adapter.unmute();

// Turn camera on by default
if (adapter.getState().devices.cameras.length !== 0) {
  const camera = adapter.getState().devices.selectedCamera ?? adapter.getState().devices.cameras[0];
  adapter.setCamera(camera).then(() =>
    adapter.startCamera({
      scalingMode: isMobileSession ? 'Fit' : 'Crop'
    })
  );
}

Thanks @JamesBurnside !!!!


Update tree view after creating a snippet

When I create a snippet - I want the tree view on the left to be updated after creating the snippet.
Current behavior:
A user has to reload the page to view the newly created smippet.
Proposed behavior:
The tree view is updated after saving the snippet.

Hi madflow,
you don't have to reload the page, you can right click the parent node and refresh it to get the current children, but updating the tree automatically would be more appropriate indeed. Issue noted.

👍 Thanks for the tip! Yes - I was aiming at "no user triggered refresh needed".

Implemented. This will be available in the next release, which is coming out next week (12 Sept)

:+1:


fixed identitybanner on mobile

Corrected mobile identity banner size.
Increased mobile font-size to 16px to stop iOS from focusing the window.
consolidated the class IdentityBannerImage and fixed the typo, missing ;

Before

After

Thanks again @Firewaters, this looks great!


fix: qq search

fix: continue fix qq search
chore: up deps
fix: windows wco color error
related:
https://developer.chrome.com/docs/workbox/caching-strategies-overview/
https://developer.mozilla.org/en-US/docs/Web/API/Cache

After some test, I think that the use of cache is still quite immature and should not be prioritized and consume time testing. I've reverted the change on that and it pr only now contains fixes on qq and some dep updates

After some test, I think that the use of cache is still quite immature and should not be prioritized and consume time testing. I've reverted the change on that and it pr only now contains fixes on qq and some dep updates

Sure. It usually takes longer time to confirm code correction when merging global framework functions such as cache. It's still a good try to improve performance.


Rasa x problem decoding in portuguese language

Rasa Version : 2.3.0
Rasa SDK Version : 2.3.1
Rasa X Version : 0.37.0
Python Version : 3.7.6
Operating System : Windows-10
Issue:
when running rasa x in my project in portuguese get the above error, can you help?
I can train the model, run it and deploy it to an rest channel, the only thing that doens't work is rasa x
I tested rasa x with the sample rasa init and trained model and it works fine
Error (including full traceback):
when running rasa x in my project in portuguese get the above error, can you help?
I can train the model, run it and deploy it to an rest channel, the only thing that doens't work is rasa x
I tested rasa x with the sample rasa init and trained model and it works fine

Command or request that led to error:
rasa x

Content of configuration file (config.yml) (if relevant):
# Configuration for Rasa NLU.
# https://rasa.com/docs/rasa/nlu/components/
language: pt
pipeline:
   - name: SpacyNLP
     model: "pt_core_news_lg"
   - name: SpacyTokenizer
   - name: SpacyFeaturizer
   - name: RegexFeaturizer
   - name: RegexFeaturizer
   - name: LexicalSyntacticFeaturizer
   - name: CountVectorsFeaturizer
   - name: CountVectorsFeaturizer
     analyzer: char_wb
     min_ngram: 1
     max_ngram: 4
   - name: DIETClassifier
     epochs: 100
   - name: EntitySynonymMapper
   - name: ResponseSelector
     epochs: 100
     retrieval_intent: faq
     scale_loss: false
   - name: ResponseSelector
     epochs: 100
     retrieval_intent: chitchat
     scale_loss: false
   - name: FallbackClassifier
     threshold: 0.7
     ambiguity_threshold: 0.1

# Configuration for Rasa Core.
# https://rasa.com/docs/rasa/core/policies/

policies:
- name: TEDPolicy
  max_history: 10
  epochs: 20
  batch_size:
  - 32
  - 64
- max_history: 6
  name: AugmentedMemoizationPolicy
- name: RulePolicy
  core_fallback_threshold: 0.3
  core_fallback_action_name: "action_default_fallback"
  enable_fallback_prediction: True

Content of domain file (domain.yml) (if relevant):

Thanks for raising this issue, @rctatman will get back to you about it soon✨
Please also check out the docs and the forum in case your issue was raised there too 🤗

@rctatman in advance, using an down grade of versions to the following it works
Rasa X | Rasa Open Source | Rasa SDK
0.32.2 | 1.10.14 | 1.10.2
We need help because we have bots to go to production

It only works , in rasa 2.0,  if i remove the following chars:
á, à, ã, õ, é. í, ú , ç, ê

@TyDunn does this belong in CDD Inbox? If so, does it go into the backlog?

@rctatman no news so far?


Image fails to run on Ubuntu Server 21.04

OS
Distributor ID: Ubuntu
Description:    Ubuntu 21.04
Release:        21.04
Codename:       hirsute

Docker
Docker version 20.10.10, build b485636

Labels
                "org.opencontainers.image.created": "2021-06-17T22:37:49.252Z",
                "org.opencontainers.image.description": "Murmur (Mumble) Server",
                "org.opencontainers.image.licenses": "Apache-2.0",
                "org.opencontainers.image.revision": "2ea7e1759fc0a9bbebca6ba59797837fd81c6283",
                "org.opencontainers.image.source": "https://github.com/goofball222/murmur",
                "org.opencontainers.image.title": "Murmur (Mumble) Server",
                "org.opencontainers.image.url": "https://github.com/goofball222/murmur",
                "org.opencontainers.image.vendor": "The Goofball -<EMAIL_ADDRESS>                "org.opencontainers.image.version": "1.3.4"

Compose file
version: '3'

services:
  murmur:
    image: goofball222/murmur
    container_name: murmur
    ports:
      - 64738:64738/tcp
      - 64738:64738/udp
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ./cert:/opt/murmur/cert
      - ./config:/opt/murmur/config
      - ./data:/opt/murmur/data
      - ./log:/opt/murmur/log
    environment:
      - TZ=UTC

How to reproduce
Simply run a docker-compose up -d for a docker-compose.yml file with the above mentioned contents.
Expected results
The container starts and continues to run.
Actual results
The container exits immediately with the following log:
standard_init_linux.go:228: exec user process caused: exec format error

I forgot to check the architecture, and just now saw that it's amd64, and I was trying to run it on a Raspberry Pi.


latte-dock crashes systematically on start

Describe the bug
Since the 21.11 upgrade, latte-dock always crashes on start.
Steps To Reproduce
Steps to reproduce the behavior:

Build a system with nixos-21.11
Run latte-dock

Expected behavior
Latte-dock should work normally.
Screenshots
[user@system:~]$ latte-dock
KCrash: Attempting to start /nix/store/7y6wi812h7vs6cxinq4j4h7zshs1pwiv-latte-dock-0.10.0/bin/latte-dock
KCrash: Application 'latte-dock' crashing...
[1]    774438 segmentation fault (core dumped)  latte-dock

Additional context

Tested on two different machines with brand new users and new home directories (to rule out possible issues with existing dot files).
Issue exists since the 21.11 upgrade.

Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.4, NixOS, 21.11 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.4`
 - channels(root): `""`
 - nixpkgs: `/nix/store/wnmzij43q35h8vil2apilxzkfnjcdj4p-source`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Can you help test #149946?

Yes it fixes the issue and I don't see any other bugs with this version, thx!

~ ❯❯❯ latte-dock
KCrash: Attempting to start /nix/store/11p8la1n0b67vq7vsryc4xr6g6kgv6hg-latte-dock-0.10.4/bin/latte-dock
KCrash: Application 'latte-dock' crashing...
"An instance is already running!, use --replace to restart Latte"
[1]    31978 segmentation fault (core dumped)  latte-dock
~ ❯❯❯ latte-dock --replace                                                                                ✘ 139
KCrash: Attempting to start /nix/store/11p8la1n0b67vq7vsryc4xr6g6kgv6hg-latte-dock-0.10.4/bin/latte-dock
KCrash: Application 'latte-dock' crashing...
[1]    34083 segmentation fault (core dumped)  latte-dock --replace

Nevermind, I did latte-dock --cc and now it works fine :)


Fix Android version

Hi,
This PR fixes 2 problems encountered on Android:

A bug introduced here where the source prop wasn't set on Android.
Reloads the webview once the javascript has been injected, as it needs to be done to be able to use the newly created javascript interface. See [addJavascriptInterface(Object object, String name)](http://developer.android.com/intl/es/reference/android/webkit/WebView.html#addJavascriptInterface(java.lang.Object, java.lang.String)):

Note that injected objects will not appear in JavaScript until the page is next (re)loaded.

Using that it works perfectly for us, thanks for the project!
Let me know if I can do something else.

@Bhullnatik, Thanks for the PR.


Improve UUID generation

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

Comparison is base (d3352e3) 90.04% compared to head (a8a7889) 90.03%.

Additional details and impacted files
@@              Coverage Diff              @@
##           beta/v4.0     #622      +/-   ##
=============================================
- Coverage      90.04%   90.03%   -0.02%
=============================================
  Files            132      132
  Lines          15026    15029       +3
=============================================
+ Hits           13530    13531       +1
- Misses          1496     1498       +2

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


Add legend panel

Add legend panel to Analyze Sequences mode that tells users what GC, Sr_CAI, and Ce_CAI values are.

Address with push: https://github.com/astrasb/Strongyloides_Codon_Adapter/commit/726ceeac6db87db9d79e2d718a310672dc6beef6


User guide for porting namelist/diagnostic to v2.0

porting.rst, with instructions on how to port a namelist/diagnostic to v2.0
new doc/ directory in ./esmvaltool/: this should contain documentation files concerning v2.0 only
some documentation files for v2.0 are still in ./doc/ and shall be moved to ./esmvaltool/doc/, to avoid mixing documentation for v1.0 and v2.0

@zechlau please go through porting.rst and let me know if something is unclear.

Don't worry about readthedocs integration for now. I will sort it out


Add servicePrincipalsByAppId method to Graph Api

Example : GET /72f988bf-86f1-41af-91ab-2d7cd011db47/servicePrincipalsByAppId/9469b9f5-6722-4481-a2b2-14ed560b706f/objectId?api-version=1.6 HTTP/1.1
{"odata.metadata":"https://graph.windows.net/72f988bf-86f1-41af-91ab-2d7cd011db47/$metadata#Edm.String","value":"3eb9d9f3-371c-4d24-a60a-d7681c48c071"}
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-node

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/5458
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/5458/commits/28bd22698beb44fdfb82def00081657783ae7571

Automation for azure-sdk-for-java


Add multi-platform Docker builds for Papermerge

This pull request introduces multi-platform support for Papermerge's Docker image using Docker Buildx in GitHub Actions. With this update, the Docker image will now be built for the following platforms:

linux/amd64: Standard x86_64 architecture (most servers and PCs).
linux/arm64: Generic 64-bit ARM.
linux/arm/v5: Older 32-bit ARM (legacy systems).
linux/arm/v7: 32-bit ARM, including devices like Raspberry Pi 3.
linux/arm64/v8: Modern 64-bit ARMv8 devices (e.g., Raspberry Pi 4, AWS Graviton).

Why This Change?
Previously, the Docker image was limited to linux/amd64, preventing it from running on other architectures without using emulation. By adding multi-platform support, users can deploy Papermerge on ARM devices, including Raspberry Pi and other embedded systems, significantly expanding its usability.
What’s Changed?

Updated the GitHub Actions workflow to use docker/setup-buildx-action for multi-platform builds.
Modified the build process to target additional CPU architectures (arm64, arm/v5, arm/v7, and arm64/v8).

Testing

The updated workflow builds images for all specified platforms and pushes them to Docker Hub (or the configured container registry).
The images have been tested locally using Docker Buildx with QEMU emulation to ensure proper functionality across platforms.

The cloud image is obsolete. It will go away. Sorry for confusion. The correct image is the "standard" - where you opened another PR.
Anyway, I am closing this PR, again - because the "cloud" image is obsolete.


Structure and rename SQL files belonging to table/SQL connector tests

Description:
$subject for the ease of maintenance
The relevant files are in,
/tests/ballerina-test/src/test/resources/datafiles/ directory

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/10197


Continuous timelock release

Allows continous timelock vesting per #8. Updates tests and adds new tests.
Note this PR also includes commits from API3 token changes and hence is marked as a draft until those changes are moved into master.

Implemented in 1729487 according to the comments here


Support being able to run parsing sass through --stdin rather than via path

Right now if you pass sass in via --stdin there is no :filename so I think it hits this line of code:-
https://github.com/chriseppstein/sass-globbing/blob/master/lib/sass/globbing/importer.rb#L43
I think in this case it would be reasonable to fall back to using Dir.pwd and in fact this can be 'hacked' to work by changing def find to:-
def find(name, options)
  # In many places the code assumes that `options[:filename]` is the
  # file sass is running on - even though the only information that it
  # seems to actually need/use is the directory in which that file
  # lives.
  options[:filename] = Dir.pwd+'/hack' unless options[:filename]
  if name =~ GLOB
    find_glob(name, options[:filename], options) {
      "/* No files to import found in #{comment_safe(name)} */"
    }
  else
    super(name, options)
  end
end

But I don't like this implementation as it's really hacky.
(Also if this is fixed, it will fix https://github.com/docpad/docpad-plugin-sass/issues/22)

this plugin requires a filename to work. import a file on disk that does the globbing.


Two projects with same slug and recipient address

These two projects have the same slug and recipient address.
Shouldn't this be impossible?
https://giveth.io/project/women-economic-empowerment
Project IDs are 2881 and 2882
Maybe we can delete the one that is not verified?

@WhyldWanderer I checked and we have only one project with the slug "women-economic-empowerment" that id = 2881.

Yes.. I believe the 2882 one got deleted in the end. However it doesn't solve the issue as Giveth shouldn't allow for this use case.
Maybe it's still worth doing some testing to create some projects with the same title to see what happens on the backend?

@WhyldWanderer of course, I did some testing, it's impossible to add duplicate projects with UI, but by sending multiple direct requests to backend at the same time, I could create different projects with same title and wallet address.
To solve this, I added a unique index for slug field in Project entity. Also, we had some projects with duplicate slug on staging and production that I solved them all.
I've sent the PR and it's waiting for review.

The PR for this issue is ready. I'll merge it on staging after SuperFluid release.

@maryjaf to test and verify

It has been resolved and know there is no way to create one project with same name and address


Release 7.0.0

Questions
Answers

Description?
Release 7.0.0

Type?
refacto

BC breaks?
yes

Deprecations?
no

Fixed ticket?
~

How to test?
~

PR merged, well done!
Message to @PrestaShop/committers: do not forget to milestone it before the merge.


Staging repository is not in desired state (not_found): StagingRepository(id=orgpostgresql-1612804902325, state=released, transitioning=false)

I've the following (I use https://github.com/vlsi/nexus-stub as a poorman's Nexus).
Are you sure state=release, transitioning=false is not valid state for Nexus as it promotes a staging repository?
AFAIK GNSP required either not_found or released state (see (expected [released, not_found]) in https://github.com/Codearte/gradle-nexus-staging-plugin/issues/110#issue-425034006 )
publish-plugin:
    Execution failed for task ':releaseNexusStagingRepository':
        io.github.gradlenexus.publishplugin.RepositoryTransitionException: Staging repository is not in desired state (not_found): StagingRepository(id=orgpostgresql-1612804902325, state=released, transitioning=false). It is unexpected. Please checkNexus logs using its web interface - it can be caused by validation rules violation. If not, please report it to https://github.com/gradle-nexus/publish-plugin/issues/ with '--info' logs
            at io.github.gradlenexus.publishplugin.internal.StagingRepositoryTransitioner.assertRepositoryInDesiredState(StagingRepositoryTransitioner.kt:62)
            at io.github.gradlenexus.publishplugin.internal.StagingRepositoryTransitioner.effectivelyChangeState(StagingRepositoryTransitioner.kt:42)
            at io.github.gradlenexus.publishplugin.internal.StagingRepositoryTransitioner.effectivelyRelease(StagingRepositoryTransitioner.kt:35)
            at io.github.gradlenexus.publishplugin.ReleaseNexusStagingRepository.transitionStagingRepo(ReleaseNexusStagingRepository.kt:40)
            at io.github.gradlenexus.publishplugin.AbstractTransitionNexusStagingRepositoryTask.transitionStagingRepo(AbstractTransitionNexusStagingRepositoryTask.kt:66)
            at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
            at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
            at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
            at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)

See https://github.com/Codearte/gradle-nexus-staging-plugin/issues/37 for autoDropAfterRelease.
However, it is not clear if release+drop should be atomic or not.
If release and drop are handled separately, then it might be possible to observe the repository in state=release, transitioning=false state.

@szpak Could you please take a look?

When I was writing that code the Nexus API v2 documentation was quite poor. AFAIR, I needed to take a look in the source code of a Maven counterpart plugin to use some features (e.g. autoDrop). Most likely, I had a reason to implement it that way and your case tends to confirm that. I will tweak the implementation in GNPP.

I needed to take a look in the source code of a Maven counterpart plugin

I'm afraid Maven plugin uses "the official Nexus client" which has closed sources.

I'm facing a similar issue in a Kotlin Multiplatform project. It is built and released simultaneously across 3 different hosts (Linux/macOS/Windows). They all fail late in the process with a similar message, for example:
> Task :publishToSonatype
> Task :closeSonatypeStagingRepository

> Task :releaseSonatypeStagingRepository FAILED

FAILURE: Build failed with an exception.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

Use '--warning-mode all' to show the individual deprecation warnings.
* What went wrong:
See docs.gradle.org/7.0.2/userguide/command_line_interface.html#sec:command_line_warnings
Execution failed for task ':releaseSonatypeStagingRepository'.

> Staging repository is not in desired state [released, not_found]: StagingRepository(id=comdoist-1024, state=closed, transitioning=false). It is unexpected. Please checkNexus logs using its web interface - it can be caused by validation rules violation. If not, please report it to gradle-nexus/publish-plugin/issues with '--info' logs
Execution optimizations have been disabled for 7 invalid unit(s) of work during this build to ensure correctness.

When I check Nexus, they show up as closed, and after a few seconds, they are released. The workflow itself is very basic. Configuration two [1] [2].
Can there be a race condition, or is this misconfiguration on my part?

@goncalossilva It is not expected. I checked your logs and - as it should be - you have different staging repositories created in every build (]here](https://github.com/Doist/doistx-normalize/runs/2593142479#step:9:51) and here). They should be closed independently. With too short timeout they could be still "closed" , but "transitioning". However, it is not the case here:

StagingRepository(id=comdoist-1023, state=closed, transitioning=false)

It's strange that they are effectively released after while :thinking: . Does it (being released) occur during the workflow execution or some time later?
To diagnose it I propose to:

Add -i to the Gradle execution with ./gradlew publishToSonatype ...
Run the workflow.
Check when exactly the repositories are marked as released in Nexus UI (in comparison to the given workflow execution).
Remove the repositories section from the publishing block - it should be not needed (I don't know if it can break anything)
Run the workflow.


"x" emoji is misleading when destroying a site

When using ness destroy, the output looks like this:

The ❌  emoji sends a signal as if the site destruction failed, but it seems like it succeeded (exit code 0 and no errors).

Yeah, that emoji means something went wrong 😅. The real issue here is that it exited with 0 (and without listing any errors). Will look into this!

This should be fixed with #37.


Is something like multiline bullet completion supported?

Hi! Not sure if this is the correct place to ask questions, it's not really an issue.
I'm just wondering if something like this is supported, or am i doing something wrong? I'm trying to integrate markdown-oxide to codemirror, and got the completion working. However, search on bullet list items only works on content that is on the first line of the bullet. I'm not sure if I'm doing something wrong.
I also checked it in the VS Code extension, and the same thing happens. Seems like this isn't supported? Or maybe I need to configure something?

Thanks!

Hey!
This is not supported yet. I did a naive regex parsing bc it was fast and easy.
With v1 I'm using treesitter and this will be solved!

Gotcha. Looking forward to it!


Update container-insights-cost.md

Fixed link to Prometheus docs

@bwren
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


[WFLY-11235] Server with HA profile bound to <IP_ADDRESS> sends cluster topology containing this address to client

Jira: https://issues.jboss.org/browse/WFLY-11235
When binding <IP_ADDRESS> in the target EJB server, it will broadcast such any-address to the whole cluster, which leads to the problem that the client will try to locate such EJB service using <IP_ADDRESS>, and it will fail.
Proposed fix is trying to use InetAddress.getLocalHost().getHostAddress() as the destination address in case such any-address is specified. There will still be problem if multiple network interfaces available and it may return an IP address which is not a desired one, but in that case, there should be more requirements on how to specify it IMO, and binding to <IP_ADDRESS> is not a recommended way for production.
Updated:
Proposed fix is trying to throw a RuntimeException if binding to <IP_ADDRESS> in cluster mode when an EJB is deployed.
There is no tests attached, because it needs 2 physical separated machines(like VMs) to reproduce. I attached the reproducer in the linked Jira for verification. (WFLY-11235-reproducer.zip)
Please make sure your PR meets the following requirements:

[ ] Pull Request title is properly formatted: [WFLY-XYZ] Subject or WFLY-XYZ Subject
[ ] Pull Request contains link to the JIRA issue(s)
[ ] Pull Request contains description of the issue(s)
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Attached commits represent units of work and are properly formatted

Choosing a "random" interface is a bad idea.
<IP_ADDRESS> is a misconfiguration.  It should throw an error, not pick something that could be wrong (and could change in unexpected ways).

@dereed I agree it is not the good way to solve the problem. But binding to <IP_ADDRESS> is corner cases(and not a recommend way for production), and this proposed changes should be able to solve most of the corner cases. :)
But I don' t think <IP_ADDRESS> is a misconfiguration, when it is used via bin/standalone.sh -b <IP_ADDRESS>, the services will be available on different interfaces. It should also be useful in case you don't know exactly what IP address will be like in a new created docker container. :)

Oh, I just noticed the comment from Brad, I will check it. :)

@dereed / @gaol I am not sure about the state of this one, so I am adding the hold label

@kabir thanks, I will update this PR soon after discussion in the downstream Jira. :)

Close this PR, triage proposing a warning message in this case tracked by https://issues.jboss.org/browse/JBEAP-15874.
https://issues.jboss.org/browse/WFLY-11235 is deferred


VirusTotal needs new screenshot

They’ve updated their look.
https://github.com/caskroom/homebrew-cask/blob/master/doc/cask_language_reference/stanzas/sha256.md#updating-the-sha256

The VirusTotal look has changed and reverted to the original a few times in the last couple of weeks.
It was briefly displaying the new look for me today but has since changed back.
I'll update the screenshot once the new look is permanent.

I managed to get a screenshot of the new look but VirusTotal has again reverted to the original look.
https://github.com/caskroom/homebrew-cask/pull/37531


Move the endpoints to v2.0?

We should ensure that developers start onboarding to the v2 endpoints as they're protocol compliant and easier to work with.  The authorities listed here are v1, so they do not interop with the protocol documentation provided everywhere else.

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

ID: 36ad8cf5-067f-6715-eabf-f0254d6ed7c8
Version Independent ID: 8a4ff617-6d6b-d6ef-1691-82c9477a73e4
Content: Azure AD authentication & national clouds - Microsoft identity platform
Content Source: articles/active-directory/develop/authentication-national-cloud.md
Service: active-directory
Sub-service: develop
GitHub Login: @negoe
Microsoft Alias: negoe

@hpsin Thanks for your question. We are checking on this and will respond to you soon.

@hpsin Thank you for pointing this out. I have updated the endpoints with v2.0 as mentioned below:

Authorization common endpoint: https://login.microsoftonline.de/common/oauth2/v2.0/authorize.
Token common endpoint:
https://login.microsoftonline.de/common/oauth2/v2.0/token.

@bernie-msft is this ok with you? @SumitParikh ?


i found a bug with your titlebar

this is my code
when i select the light the icon is black
instead is white ,but when i select light to use system setting,the icon color is not change,
but select from dark to use system setting the codition is normal
https://github.com/WinUICommunity/WinUICommunity/assets/125177842/d34aa112-a994-4fba-a26d-b6f3b6d42b08

Hi @LanHuangJG
titlebar does not handle background colors. you can do this your self like this:
currentWindow.AppWindow.TitleBar.ButtonBackgroundColor = Colors.Transparent;
also if you use WinUICommunity.Core package, you can use ThemeService which will handle everything.
https://github.com/WinUICommunity/WinUICommunity/assets/9213496/a64aa0b6-f931-4853-90ac-2f0014c0acf4


the git clone depth should be 15 instead of 14

In the toutorial
https://docs.angularjs.org/tutorial/
step "Download install Phonecat"
in my opinion you need to git clone with the depth 15 instead of 14
Because you need the Step-0 in the next Tutorial-step

The tutorial has been updated yesterday. There are two new steps now, so the instructions have been updated to mention --depth=16. Make sure to refresh your page to get the new content (you might need to disable your browser's cache).


modify: AVCodecContext stat_in/stat_out accessor

Current coverage is 26.03%

Merging #14 into master will increase coverage by +0.44% as of 181dec6

@@            master     #14   diff @@
======================================
  Files            4       4
  Stmts         2348    2362    +14
  Branches        73      77     +4
  Methods          0       0
======================================
+ Hit            601     615    +14
  Partial         33      33
  Missed        1714    1714

Review entire Coverage Diff as of 181dec6

Powered by Codecov. Updated on successful CI builds.

Thanks!