bash: disable glibc malloc on other platforms

Description of changes

Disables use of glibc malloc on all other platforms - not just musl.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

oops this change ended up affecting a larger scope than intended. apologies.


Add option to expose admin port via Apache load balancer

Add loadBalancerExposeAdminPort boolean property to create domain inputs
Handle the new property in create-weblogic-domain.sh
Add additional test/verification in run.sh
Modified the doc (md files)

The QUICKTEST and full version of the run.sh passed locally with LB_TYPE=APACHE and default.
@rjeberhard @monica @rosemarymarano

LGTM


Chat LLM adds an extra sentence in front of SQL queries, produces Output Parsing Error

System Info
python==3.11
langchain==0.0.246
Who can help?
No response
Information

[ ] The official example notebooks/scripts
[X] My own modified scripts

Related Components

[X] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[ ] Agents / Agent Executors
[ ] Tools / Toolkits
[X] Chains
[ ] Callbacks/Tracing
[ ] Async

Reproduction

db_chain = SQLDatabaseChain.from_llm(chat_llm, db, use_query_checker=True, verbose=True)#, query_prompt=PROMPT)
chat_llm=AzureChatOpenAI(deployment_name="gpt-35-turbo-16k",
model_name="gpt-35-turbo-16k" )
tools=[Tool(
func=db_chain.run,
name="Database Search",
description="useful for when you need to lookup specific queries on the ATLASIQ Schema"
)]
prefix = """ You are an expert Snowflake SQL data analyst, who writes queries with perfect syntax,
and performs necessary computations on that data in the AtlasIQ Schema. Your goal is to answer the following questions as best you can.
When there are multiple results for the same quantity, return all of them. DO NOT hallucinate an answer if there is no result."""
suffix = """Begin!"

{chat_history}
Question: {input}
{agent_scratchpad}"""
prompt = ZeroShotAgent.create_prompt(
tools,
prefix=prefix,
suffix=suffix,
input_variables=["input", "chat_history", "agent_scratchpad"],
)
memory = ConversationBufferMemory(memory_key="chat_history")
llm_chain = LLMChain(llm=chat_llm, prompt=prompt)#,  callbacks=[custom_handler.short_chain(
new_zero_agent = ZeroShotAgent(llm_chain=llm_chain, tools=tools, verbose=True)
agent_chain = AgentExecutor.from_agent_and_tools(
agent=new_zero_agent, tools=tools, verbose=True, memory=memory, handle_parsing_errors=True)
agent_chain.run(query)
Expected behavior
I expect the query to be synthesized and executed but instead, I get an unnecessary explanation of why the query is correct "The original query does not contain any of the mentioned mistakes. Therefore, here is the reproduced original query:
SELECT SUM(total_operating_expenses)
FROM expense_income_table
WHERE market = 'Seattle'
AND period = '202305'The original query provided does not contain any of the mentioned mistakes. Hence, the original query is reproduced below:
SELECT SUM(total_operating_expenses)
FROM expense_income_table
WHERE market = 'Seattle"<- which causes the output parsing error

@mroytman-eqr Hi, were you able to solve the problem?

I am getting the same error. If the special characters are attached to the words in the text then the LLM is unable to parse it and hence I get the Output Parsing error. I tried removing all the special characters and then trying but I was still getting the same error. Was anyone able to fix it?


PP-9851 Rename capture specific queue helpers

The capture queue will be extended to perform a number of asynchronous
charge operations.
Update the name of the capture queue helpers (message handler, process,
queue model) to have the more generic "charge async operations" naming
structure.
Anything relating to actually capturing a charge will remain the same
for now as capture will still be a job processed by this queue.

Although we think it's a good idea for charge operations to be close together, it transpires there already exists a generic task queue which would meet the requirements of something that only needs to guarantee to run once (like authorisation). We'll update acceptance criteria to use that instead.


Feat/162580 command args and file structure.

Added command line args functionality.
Reformatted Scripts file structure.

🎯 suggestion: The build pipeline is failing because it does not know which solution to build.  The workflow needs to be updated to include the solution to execute.
@MartinSandersAND I'll sort this for you, will push the changes to your branch
MSBUILD : error MSB1011: Specify which project or solution file to use because this folder contains more than one project or solution file.


Wrapping authenticate in try/catch prevents redirect

Hi, I am seeing an issue that I think is specific to the TOTP strategy. but please let me know if that is incorrect.
I am getting intermittent Unhandled Promise Rejection errors for the deployed version of the app specifically during a login POST request.  In order to be able to catch these errors, I would like to be able to wrap the authenticate call in a try/catch, as follows:
  try {
    await authenticator.authenticate(TOTP_STRATEGY, request, {
      successRedirect: route("/verify"),
      failureRedirect: currentPath,
      throwOnError: true,
    });
  } catch (error) {
    console.error("error: ", error);
    return json({
      authError: "Sorry, something went wrong.  Please try again.",
    });
  }

This is based on the recommended way to handle errors in the main auth docs.
However, if wrapping an authenticate call in try/catch there is no redirect to the verify route.
Any suggestions re. how to enable catching errors, while still also supporting a redirect to verify?  Thanks for any tips or insights!

Hello @andersr, Remix Auth TOTP is a strategy built on top of remix-auth, so, handling errors and authentication should be done the way remix-auth outlines (as you already mentioned).
I had a talk with Sergio about this on Discord (time ago). He also suggested handling errors just like the provided docs by you recommend.
To redirect after catching an error, you might wanna clone the request at the beginning (if required). Then, in the catch block, use that to redirect and set any cookies from the original request.
Haven't had much time to dive in, but you could probably go with something like this:
export async function action({ request }: DataFunctionArgs) {
  const url = new URL(request.url)
  const currentPath = url.pathname

  try {
    await authenticator.authenticate('TOTP', request, {
      successRedirect: '/verify',

      // If error, redirect back to current path.
      failureRedirect: currentPath,
    })
  } catch (exception) {
    if (exception instanceof Response ) {
      // You can also check for the current path for more granular control.
      // if(exception.headers.get('location') === '/login') ...

      // Do something else.
      // ...

      // Redirect with response headers.
      // This will ensure that everything in the original request is preserved.
      return redirect('/verify', {
        headers: {
          'Set-Cookie': await commitSession(
            await getSession(exception.headers.get('Set-Cookie')),
          ),
        },
      })
    }

    // Bubble up any other exception.
    throw exception
  }
}

To be honest I was in this situation before and not sure if I was able to handle it properly either, seems kinda tricky.
Give it a try and notice me how it goes.

Hey @dev-xo - thanks for the quick reply!  I updated my try/catch block to match what you have above and now it redirects as expected.  However, one thing I wasn't clear on is why one would redirect to /verify if there is an exception(?)
Thanks again!

Navigate to the route you need, @andersr.
The code example was just a quick draft trying to assist with your current issue.
Everything working as expected? If so, I'm gonna close this for now.

Ok, thanks, makes sense.  Yes, everything is working as expected.

Been kinda busy lately, but I'd like to keep improving the library.
As soon as I get some time, maybe I can come up with an error handling example.
If you have any examples or find some better ways to handle errors in both remix-auth and remix-auth-totp, feel free to share it, @andersr!


Create Authenticated User Sitemap

Background & Context
Currently, our sitemap only includes the pages on the public website. To better understand the experience of our internal and external users and inform future feature development, our team needs a shared understanding of the sitemap from an authenticated user's POV.
The findings & sitemap help inform:

Short-term: Where the automated key tool (#7862) should live on the site
Long-term: IA strategy

Open Questions

[ ] What does an authenticated sender see on the RS website and how can we reproduce it from our Admin accounts?
[ ] What does an authenticated receiver receiver see on the RS website and how can we reproduce it from our Admin accounts?
[ ] What is the IA of the Prime Admin Tools section?

Working Links

Sitemap Mural

Existing work: Website content audit

Acceptance Criteria

[ ] Discovery: Ask engineers which senders and receiver profiles we can use as representative models for building the sitemap
[ ] Authenticated sitemap created in Mural
[ ] Permissions of the different user types (Prime Admin, Sender, and Receiver) included on the sitemap
[ ] Share sitemap with the team
[ ] Incorporate feedback as needed
[ ] Share the link as reference in onboarding documents

Review Info

Design Lead to review

Close per Jillian


RFC collections: misleading breadcrumbs and multiple parent collections

Originally by fcosta on 2012-12-19
Apprently linked to the multiple (and obsolete) parent collections, misleading crumbreads appear, at least in cds like:
Home > Administrative Support (AS) > Translation and Minutes
Obsolete parent collections links are left apparently because it is not easy to suppress them (not possible in WebSearch UI.

I have a related question. Do we still want to allow multiple parents for a collection? Wouldn't be easier to allow only "forest" of collections. Then for each collection there is only one path to the root.
convert:
    A
   / \
  B   C
 /
C

to:
    A
   / \
  B   D
 /
C

where D.dbquery := C.dbquery.
Is anybody using it in production? (cc @invenio-developers)

To add to @jirikuncar's question, there's also an issue of regular vs virtual collection tree.  A collection may be attached to the regular tree in one place and have one regular parent there, all the while it is also attached to the virtual collection tree and having one or more regular parents there.  If most Invenio sites aim at the simplification of the collection tree, leaving the job for later faceting, we may want to restrict all the various possibilites in Invenio 2, especially if they are "underused" in Invenio 1.

Answering @jirikuncar question, we have this situation in CDS in a few places
mysql> select id_son, count(*) c from collection_collection group by id_son having c > 1;
+--------+---+
| id_son | c |
+--------+---+
|      3 | 2 |
|      5 | 2 |
|     16 | 2 |
|     19 | 2 |
|     20 | 2 |
|     22 | 2 |
|     23 | 2 |
|     24 | 2 |
|     25 | 2 |
|     26 | 2 |
|     27 | 2 |
|     30 | 3 |
|     31 | 3 |
|     32 | 3 |
|     33 | 3 |
|     34 | 3 |
|     35 | 4 |
...

One of the most visible examples could be the collection Presentations & Talks which is attached to two different regular parents, also Academic Training Lectures which it is attached to a regular parent and to a virtual parent, but the relation with the parents is regular in both cases.
If needed I can try to list the different situations we have, but probably we cover most of them ;-)

One of the most visible examples could be the collection Presentations & Talks which is attached to two different regular parents [...]

However is this still wanted, considering the ongoing simplification of the collection tree?

@tiborsimko you are right, I should check the new collection tree for this kind of situations.

Shall we change the collection graph to collection tree where each collection has only a single parent?

[ ] single parent for collection
[ ] decide on tree structure encoding

:+1: as this would simplify authorization policy. For a given collection it would be always clear (given the chain of parents) whether it is public or not.

@tiborsimko you are right, I should check the new collection tree for this kind of situations.

Good, please check if this is still wanted, and let's proceed from that.

Invenio-Collections is using nested sets that prevent this problem.


klipper: unstable-2023-01-07 -> unstable-2023-02-01

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for klipper is: The Klipper 3D printer firmware
meta.homepage for klipper is: https://github.com/KevinOConnor/klipper
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-01-08 in filename of file in /nix/store/n0x66fgy5fc13f44laz5ndfdild1a48n-klipper-unstable-2023-01-08

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
klipper
klipper-firmware
klipper-flash
klipper-genconf

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n0x66fgy5fc13f44laz5ndfdild1a48n-klipper-unstable-2023-01-08 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A klipper https://github.com/r-ryantm/nixpkgs/archive/62fc600f4e99c2e3b891a819f31d93eb446a76f7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n0x66fgy5fc13f44laz5ndfdild1a48n-klipper-unstable-2023-01-08
ls -la /nix/store/n0x66fgy5fc13f44laz5ndfdild1a48n-klipper-unstable-2023-01-08/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

klipper
klipper-firmware
klipper-flash
klipper-genconf

Maintainer pings
cc @lovesegfault @zhaofengli @cab404 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for klipper is: The Klipper 3D printer firmware
meta.homepage for klipper is: https://github.com/KevinOConnor/klipper
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-01-13 in filename of file in /nix/store/90najx992iwscmh66w3fnk4k3fxgcsak-klipper-unstable-2023-01-13

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
klipper
klipper-firmware
klipper-flash
klipper-genconf

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/90najx992iwscmh66w3fnk4k3fxgcsak-klipper-unstable-2023-01-13 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A klipper https://github.com/r-ryantm/nixpkgs/archive/fdc59882bb9b10d921ee6ea85aec0d423a4dce17.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/90najx992iwscmh66w3fnk4k3fxgcsak-klipper-unstable-2023-01-13
ls -la /nix/store/90najx992iwscmh66w3fnk4k3fxgcsak-klipper-unstable-2023-01-13/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

klipper
klipper-firmware
klipper-flash
klipper-genconf

Maintainer pings
cc @lovesegfault @zhaofengli @cab404 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for klipper is: The Klipper 3D printer firmware
meta.homepage for klipper is: https://github.com/KevinOConnor/klipper
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-01-17 in filename of file in /nix/store/riw6jkcwjqhxxxhgc8bmxhkimac9lfvq-klipper-unstable-2023-01-17

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
klipper
klipper-firmware
klipper-flash
klipper-genconf

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/riw6jkcwjqhxxxhgc8bmxhkimac9lfvq-klipper-unstable-2023-01-17 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A klipper https://github.com/r-ryantm/nixpkgs/archive/4401a1eda3c1db304bcf75055130f2572ccc13e0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/riw6jkcwjqhxxxhgc8bmxhkimac9lfvq-klipper-unstable-2023-01-17
ls -la /nix/store/riw6jkcwjqhxxxhgc8bmxhkimac9lfvq-klipper-unstable-2023-01-17/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

klipper
klipper-firmware
klipper-flash
klipper-genconf

Maintainer pings
cc @lovesegfault @zhaofengli @cab404 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for klipper is: The Klipper 3D printer firmware
meta.homepage for klipper is: https://github.com/KevinOConnor/klipper
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-01-25 in filename of file in /nix/store/yrjnl4mb9zdlf2f84b52y3gb3gw65nvc-klipper-unstable-2023-01-25

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
klipper
klipper-firmware
klipper-flash
klipper-genconf

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/yrjnl4mb9zdlf2f84b52y3gb3gw65nvc-klipper-unstable-2023-01-25 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A klipper https://github.com/r-ryantm/nixpkgs/archive/2b2b36333e3d68436b3d3a1a9a03996f9e7691ae.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/yrjnl4mb9zdlf2f84b52y3gb3gw65nvc-klipper-unstable-2023-01-25
ls -la /nix/store/yrjnl4mb9zdlf2f84b52y3gb3gw65nvc-klipper-unstable-2023-01-25/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

klipper
klipper-firmware
klipper-flash
klipper-genconf

Maintainer pings
cc @lovesegfault @zhaofengli @cab404 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for klipper is: The Klipper 3D printer firmware
meta.homepage for klipper is: https://github.com/KevinOConnor/klipper
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-02-01 in filename of file in /nix/store/4rbb5anq18bra057wkfzcmfmxz3541aw-klipper-unstable-2023-02-01

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
klipper
klipper-firmware
klipper-flash
klipper-genconf

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4rbb5anq18bra057wkfzcmfmxz3541aw-klipper-unstable-2023-02-01 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A klipper https://github.com/r-ryantm/nixpkgs/archive/df953d321bfed8e2e276f5cda04ad9282252cfc2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4rbb5anq18bra057wkfzcmfmxz3541aw-klipper-unstable-2023-02-01
ls -la /nix/store/4rbb5anq18bra057wkfzcmfmxz3541aw-klipper-unstable-2023-02-01/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

klipper
klipper-firmware
klipper-flash
klipper-genconf

Maintainer pings
cc @lovesegfault @zhaofengli @cab404 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for klipper is: The Klipper 3D printer firmware
meta.homepage for klipper is: https://github.com/KevinOConnor/klipper
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2023-02-03 in filename of file in /nix/store/gjqcklvsn6a08g527fa69580c0bjql59-klipper-unstable-2023-02-03

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
klipper
klipper-firmware
klipper-flash
klipper-genconf

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gjqcklvsn6a08g527fa69580c0bjql59-klipper-unstable-2023-02-03 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A klipper https://github.com/r-ryantm/nixpkgs/archive/daa795fef97147df88c4954b5c5b8cfd29b53d2d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gjqcklvsn6a08g527fa69580c0bjql59-klipper-unstable-2023-02-03
ls -la /nix/store/gjqcklvsn6a08g527fa69580c0bjql59-klipper-unstable-2023-02-03/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

klipper
klipper-firmware
klipper-flash
klipper-genconf

Maintainer pings
cc @lovesegfault @zhaofengli @cab404 for testing.


MudInput.FullWidth has no effect.

Bug type
Component
Component name
MudInput
What happened?
Setting FullWidth="true" does not cause the component to take up the entire with of the parent element.
Expected behavior
Component should take up the entire width of its parent element.
Reproduction link
https://try.mudblazor.com/snippet/wOQwucFAAfCOGXgo
Reproduction steps
See try.mudblazor link.
Relevant log output
No response
Version (bug)
6.0.6
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I think this is an expected result. Full width works only if parent has a width value. 100% of unknown is unknown. Am i wrong?

I believe I may have misused MudBlazor in this instance.  After years of HTML, I was so used to typing in <input that I typed in <MudInput without considering that it may not be the correct component.  I think the component we're expected to use is MudTextField.  Testing reveals that MudTextField has full width by default, along with many other input components.  https://try.mudblazor.com/snippet/wuQGOmPBJooKVYsM  Please let me know if that is the case.
If MudInput is an internal component, it'd be nice if it could be hidden or a warning placed on it.  I do not believe Blazor currently has any mechanism for making internal components in the way we would make an internal class.  But it's possible to place components the user isn't expected to use into a different namespace like MudBlazor.Internal.  This would at least make users jump through a small hoop before they shoot themselves in the foot.

I think this is an expected result. Full width works only if parent has a width value. 100% of unknown is unknown. Am I wrong?

Expected behavior based on the API alone, without prior knowledge of implementation details, would be that giving the element FullWidth="true" would give the element full width.  If it's not possible, I would expect an Exception instead of the component silently misbehaving, which may not be reasonably possible given the nature of Blazor and the web.  I tested and this can be easily implemented by switching the display mode to block, but if MudInput is meant to be an internal component, that could be a terrible idea.


Enum Deserialization panicked at 'attempt to subtract with overflow'.

I was experimenting with rkyv in libp2p.
All tests are passing locally but, when i  send bytes to other peer and deserize them

let archived = unsafe { archived_unsized_root::(&bytes[..]) };
let req = archived.deserialize(&mut Infallible);

I got panicked at 'attempt to subtract with overflow', C:\Users\PramUkesh.cargo\registry\src\github.com-1ecc6299db9ec823\rkyv-0.7.20\src\util\mod.rs:137

let size = mem::size_of::();
gives 56

but when i serialize the value i got 32 bytes for  MailboxRequest::Ping, in tests it works withou any issue(but how?), and parsing on receiver side panics due to mem::size constraint.
#[derive(Debug, Clone, PartialEq, Eq, Archive, Deserialize, Serialize)]
pub enum MailboxRequest {
    Ping,
    Publish(MailboxRecord),
}

#[derive(Debug, Clone, PartialEq, Eq, Archive, Serialize, Deserialize)]
pub struct MailboxRecord {
    pub(crate) key: String,
    pub(crate) value: String,
    pub(crate) timeout_sec: u64,
}

#[derive(Debug, Clone, PartialEq, Eq, Archive, Serialize, Deserialize)]
pub enum MailboxResponse {
    Pong,
    Publish(MailboxResult),
}

#[derive(Debug, Clone, PartialEq, Eq, Archive, Deserialize, Serialize)]
pub enum MailboxResult {
    Success,
    Error,
}

fn bytes_to_res(bytes: &[u8]) -> Result<MailboxResponse, io::Error> {
    let archived = unsafe { archived_unsized_root::<MailboxResponse>(&bytes[..]) };
    let req = archived.deserialize(&mut Infallible);
    match req {
        Ok(req) => match req {
            MailboxResponse::Pong => Ok(MailboxResponse::Pong),
            MailboxResponse::Publish(res) => Ok(MailboxResponse::Publish(res)),
        },
        Err(e) => Err(invalid_data(e)),
    }
}

fn bytes_to_req(bytes: &[u8]) -> Result<MailboxRequest, io::Error> {
    let archived = unsafe { archived_unsized_root::<MailboxRequest>(&bytes[..]) };
    let req = archived.deserialize(&mut Infallible);
    match req {
        Ok(req) => match req {
            MailboxRequest::Ping => Ok(MailboxRequest::Ping),
            MailboxRequest::Publish(req) => Ok(MailboxRequest::Publish(req)),
        },
        Err(e) => Err(invalid_data(e)),
    }
}

fn res_to_bytes(req: MailboxResponse) -> impl AsRef<[u8]> {
    let mut serializer = AllocSerializer::<0>::default();
    serializer.serialize_unsized_value(&req).unwrap();
    let buf = serializer.into_serializer().into_inner().to_vec();
    println!("{:?}", buf);
    buf
}

fn req_to_bytes(req: MailboxRequest) -> impl AsRef<[u8]> {
    let mut serializer = AllocSerializer::<0>::default();
    serializer.serialize_unsized_value(&req).unwrap();
    let buf = serializer.into_serializer().into_inner().to_vec();
    println!("{:?}", buf);
    buf
}

/// Creates an `io::Error` with `io::ErrorKind::InvalidData`.
fn invalid_data<E>(e: E) -> io::Error
where
    E: Into<Box<dyn std::error::Error + Send + Sync>>,
{
    io::Error::new(io::ErrorKind::InvalidData, e)
}

mod tests {
    use std::mem;

    use super::*;

    static PING: MailboxRequest = MailboxRequest::Ping;
    static PING_BYTES: [u8; 32] = [0u8; 32];
    static REQ_BYTES: [u8; 32] = [
        1, 0, 0, 0, 0, 0, 0, 0, 107, 0, 0, 0, 0, 0, 0, 1, 118, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0,
        0, 0, 0,
    ];

    fn get_publish_req() -> MailboxRequest {
        let req = MailboxRequest::Publish(MailboxRecord {
            key: "k".to_string(),
            value: "v".to_string(),
            timeout_sec: 0,
        });
        req
    }

    #[test]
    fn test_req_to_bytes() {
        let buf = req_to_bytes(PING.clone());
        assert_eq!(buf.as_ref(), PING_BYTES);

        let req = get_publish_req();
        let buf = req_to_bytes(req);
        assert_eq!(buf.as_ref(), REQ_BYTES);
    }

    #[test]
    fn test_bytes_to_req() {
        let buf = bytes_to_req(&PING_BYTES.clone()).unwrap();
        assert_eq!(buf, PING);
        let buf = bytes_to_req(&REQ_BYTES.clone()).unwrap();
        assert_eq!(buf, get_publish_req());
    }

    #[test]
    fn intercahnge() {
        let bytes = req_to_bytes(MailboxRequest::Ping);
        assert_eq!(bytes_to_req(bytes.as_ref()).unwrap(), MailboxRequest::Ping);
    }

    #[test]
    fn test_size() {
        let size = mem::size_of::<MailboxRequest>();
        println!("size: {}", size);
    }
}

That line in util/mod.rs is:
archived_value::<T>(bytes, bytes.len() - mem::size_of::<T::Archived>())

This is calculating the position of the root object by walking back from the end of the buffer. So if your object is 32 bytes, it will walk 32 bytes back from the end of the buffer and assume that is the location of the root object. Because this subtraction is underflowing, that suggests that the buffer you're receiving is incomplete since it's too small for your root object. Could you print out the length of the buffer on the sending side and receiving side to make sure that all of the bytes are making it over the wire?

but when i serialize the value i got 32 bytes for MailboxRequest::Ping, in tests it works withou any issue(but how?), and parsing on receiver side panics due to mem::size constraint.

I already mentioned that, the req_to_bytes outputing 32 bytes only for MailboxRequest::Ping, so buf is 32bytes on both sides.

Repo is Here : https://github.com/canewsin/p2p-poc

Your code only tests how many bytes are sent. You are not checking how many bytes are received.
From peer:
req_to_bytes: 32 bytes = [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

To peer:
bytes_to_req: 0 bytes = []

As you can see, the receiver has received a message of length 0. This will fail to deserialize for the previously mentioned reason. I asked you to print out the bytes on both the sending a receiving sides because I suspected this could be the underlying issue.
Code:
fn bytes_to_req(bytes: &[u8]) -> Result<MailboxRequest, io::Error> {
    println!("bytes_to_req: {} bytes = {:?}", bytes.len(), bytes);
    ...
}

fn req_to_bytes(req: MailboxRequest) -> impl AsRef<[u8]> {
    ...
    println!("req_to_bytes: {} bytes = {:?}", buf.len(), buf);
}

Because this looks like the underlying cause of the issue, I'm going to close this for now. If you run into any further problems after fixing this, please feel free to reopen, file a new issue, or drop by the discord server for help.

Thanks, I found a bug in my code which consumes bytes before processing read_variant(&bytes) in particular;


create_installer_windows error renaming msi file

openjdk8-openj9 Windows milestone 1 build fails in the create_installer_windows job with
mv OpenJDK8-jdk_x86-32_windows_openj9-<IP_ADDRESS>.msi OpenJDK8U-jdk_x86-32_windows_openj9_jdk8u212-b01_openj9-0.14.0-m1.msi OpenJDK8U-jre_x86-32_windows_openj9_jdk8u212-b01_openj9-0.14.0-m1.msi
mv: target 'OpenJDK8U-jre_x86-32_windows_openj9_jdk8u212-b01_openj9-0.14.0-m1.msi' is not a directory
Build step 'Execute shell' marked build as failure

Looks like mv has three arguments instead of two?
See job: https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_windows/284/console

@lumpfish , are you able to trigger new build with same options (because job 284 is gone)
(openjdk8-openj9 Windows milestone 1)
If yes, you can run it, I have modified the shell script wich rename msi

Thanks @douph1 - I will resubmit.

@douph1 - different error now unfortunately:
+ for FILE in *.msi
+ case $FILE in
+ mv OpenJDK8U-jre_x86-32_windows_openj9_jdk8u212-b01_openj9-0.14.0-m1.msi OpenJDK8U-jre_x86-32_windows_openj9_jdk8u212-b01_openj9-0.14.0-m1.msi
mv: 'OpenJDK8U-jre_x86-32_windows_openj9_jdk8u212-b01_openj9-0.14.0-m1.msi' and 'OpenJDK8U-jre_x86-32_windows_openj9_jdk8u212-b01_openj9-0.14.0-m1.msi' are the same file
Build step 'Execute shell' marked build as failure
Archiving artifacts
Finished: FAILURE

Job is at: https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_windows/303/console

@lumpfish please kick the job off again. Think I've fixed it.

build ok https://ci.adoptopenjdk.net/job/build-scripts/job/release/job/create_installer_windows/324/console


Casting pointer to usize and back have unexpected behavior

I tried this code:
//! This module contains a dummy implementation of a slice iterator.
//!
//! It shows how computing pointer offset by using integer arithmetic + casting does not yield
//! the same result as operating on pointer directly.

#![feature(core_intrinsics)]

use std::marker::PhantomData;

#[kani::proof]
fn check_addr_offset() {
    let array = [0, 1, 2];
    let slice = &array;
    let mut iter = MyIter::new(slice);
    let first = iter.next().unwrap();
    let second = iter.next().unwrap();
    let third = iter.next().unwrap();
    assert!(iter.next().is_none());
    assert_eq!(*first, 0);
    assert_eq!(*second, 1);
    assert_eq!(*third, 2);
}

#[kani::proof]
#[kani::stub(addr_offset, ptr_offset)]
fn check_ptr_offset() {
    check_addr_offset();
}

pub struct MyIter<'a> {
    ptr: *const i8,
    end: *const i8,
    phantom_data: PhantomData<&'a i8>,
}

impl<'a> MyIter<'a> {
    pub fn new(slice: &[i8]) -> Self {
        MyIter { ptr: slice.as_ptr(), end: addr_offset(slice.as_ptr(), slice.len()),
        phantom_data: PhantomData
        }
    }

    pub fn next(&mut self) -> Option<&'a i8> {
        if self.ptr == self.end {
            None
        } else {
            let result = unsafe { &*self.ptr };
            self.ptr = addr_offset(self.ptr, 1);
            Some(result)
        }
    }
}

/// Version of offset that converts pointer to usize, performs the offset, then cast the result.
fn addr_offset(ptr: *const i8, byte_offset: usize) -> *const i8 {
    ptr.addr().wrapping_add(byte_offset) as *const i8
}

/// Version that does a pointer offset directly via intrinsic.
fn ptr_offset(ptr: *const i8, byte_offset: usize) -> *const i8 {
    unsafe { std::intrinsics::arith_offset(ptr, byte_offset as isize) }
}

using the following command line invocation:
kani dummy_iter.rs

with Kani version: 0.56.0
I expected to see this happen: Verification to succeed.
Instead, this happened: The harness where we compute offset using the pointer address fails, while the one doing the offset in the pointer directly succeeds.
Note that for some reason, the second element is set to a non-deterministic value, while the third element is correct. I enabled -Z uninit-checks as well as --extra-pointer-checks, and none of them detected any other issue.
This issue is a blocker for #90.

@remi-delmas-3000 @tautschnig, I could really use your help to understand what's going on.


feat(build): #614 allow duplicates flag

Add a generalization of the problem to avoid
sending duplicates to batch


Remove period in ROCKET_S_ADMIN__86

This will remove the extra period in the name that shows up when playing the card

Might send a revert for this. The name does include the dot, hadn't noticed at first.
Bit annoying on log though, but this causes deck import to fail if the list uses the dot (opposite case would still show the card)

Might send a revert for this. The name does include the dot, hadn't noticed at first.
Bit annoying on log though, but this causes deck import to fail if the list uses the dot (opposite case would still show the card)

I believe you’re right, we’ll need to re-add the period to the name.  I didn’t realize the dot was part of the actual name.


local files should not be graded

Description
Local files in firefox (those with a file:// URL) should not be graded.
Steps to Reproduce

Create an html file
open the html file in firefox

Expected behavior:
The website should not be graded, similarly to what is done with about: URLs.
Actual behavior:
The website gets a C, because it has unknown privacy practices, and an unencrypted connection (obviously, because it is a local file)

Also, ping on #364


mininet works on Kali Linux if:

If you're trying to install mininet and you're running kali (for whatever reason) all you have to do is add this line to the install script in the /utils folder: "[ "$DIST" = 'Kali' ] && DIST='Debian'"

Hi ! I've problem to run 'sudo mn' in kali linux after installed the mininet from github. do you know to fix this?


Ask for help (by Newbie)

Hey anybody，I got some mistakes by the following command line:

scenedetect --input video.avi  --stats video_minlen25.stats.csv detect-content --threshold 30 list-scenes   --min-scene-len 25

where the information as follows:

[PySceneDetect] Loaded 1 video, framerate: 25.00 FPS, resolution: 640 x 480
[PySceneDetect] Downscale factor set to 3, effective resolution: 213 x 160
[PySceneDetect] No scene detectors specified (detect-content, detect-threshold, etc...),
or failed to process all command line arguments.
Usage: scenedetect list-scenes [OPTIONS]

Error: no such option: --min-scene-len

If you can answer me, I will be very grateful.  And  @Breakthrough , Thanks for your work!

Hi @ThisMoment1;
There is no --min-scene-len option for the detect-content or list-scenes command, that's why you're facing this issue.  --min-scene-len is only applied to detect-threshold.  If you use this command, it will work:
scenedetect --input video.avi --stats video_min.stats.csv detect-content --threshold 30 list-scenes

If you would like, you can file a feature request for adding a minimum scene length flag to the detect-content command.
Thanks.

@Breakthrough, Thank you very much for your reply, which is very helpful to me.In addition, I think it may be possible to add the function of --min-scene-len to detect-content, so as to increase the operability.

@Breakthrough, thank you very much for your reply, which is very helpful to me. In addition, I will try to submit a feature request -- to add the --min-scene-len  flag to detect-content command. Thanks for your work and advice.

Hi @ThisMoment1;
Sorry, I forgot that there IS actually a --min-scene-len flag for detect-content.  My apologies.  What you want for your original command is:
scenedetect --input video.avi --stats video_minlen25.stats.csv detect-content --threshold 30 --min-scene-len 25 list-scenes

Let me know if this helps.  Thanks!

Hi, @Breakthrough ;
Yes, it works. Thanks for your paitent advice.


Localization?

Any plans to bring localization to the templates?
Using @Localizer as show here seems a good option IMO. Particularly for templates like Web Application with Authentication which have a nice set of pages and code ready to use. But only if your target audience understands English 😉.

We currently have a sample here: https://github.com/aspnet/Entropy/tree/dev/samples/Localization.StarterWeb
This should serve as a good starting point.

We could consider at least shipping this as an out-of-band (OOB) template.

@Eilon

https://github.com/aspnet/Entropy/tree/dev/samples/Localization.StarterWeb

Great! That's exactly as I was thinking 😉 .
May I help with some PR? I already did some work with the ASP.NET Core Web App/Razor (with authentication) template.

@fdcastel thanks! That would be up to @DamianEdwards to figure out, so let's see what he thinks.

@hishamco at this time we don't have plans to ship such a template, so I recommend starting out by writing a new template in your repo


Meshes are colored by the color of objects added to the viewer when moving the camera

When adding color to one object (i.e. an sphere using addSphere) in the viewer, all my meshes take this color.
When adding  more than one colored object (each object has a different color), the meshes take these colors and the color change when moving the camera .

This bug comes from OSG and not from Gepetto-Viewer. Closing issue.


Undocumented setting "ALLOWED_CLIENT_HOSTS"

What I'm trying to achieve
While I was trying to create new staff members via the Dashboard 2.0 I came across a new setting "ALLOWED_CLIENT_HOSTS" in the saleor core. Unfortunately I don't know, what this setting is doing, what is affected when I change it and I can't find any documentation on that issue anywhere
What I expected to happen
I'm expecting to understand all settings before I'm using it.

Thanks for reporting. This seting is used to configure the list of trusted client (storefront) domains. I'll move it to saleor-docs repo and we'll fix it there.


Feature Request reaorganize tabs

I would like to be able to   reorganize the tabs and move one to  the left or right just like a browser

#1256  #443

also to have a sort of way to manage many open tabs... If I have 3 WSL tabs 1 cmd and two powershells tabbed it get's out of the UI at the right side of the tab bar (so I can't close the last tabs unless I close the first ones).

@paradonym Okay, put that request into one of the bugs I linked above?


After running, the "requirement.txt" has no content within

I attempted to execute the pipreqs cmd command at all levels of the project engineering directory, including using the uft-8 encoding parameter option, but this did not have any effect. It seems like this and there was not any warning or error.

It doesn't traverse subfolders. I'm not sure if this issue has been resolved. You have to run in the same folder as the code is.


Update Configuration Cache docs to cover new approach to input tracking

Mandatory input declaration for system properties, environment variables
and gradle properties is gone. Only some access patterns are
discouraged.
This PR also covers input list in the configuration cache report.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

Link to the rendered doc: https://builds.gradle.org/repository/download/Gradle_Master_Check_BuildDistributions/47940320:id/distributions/gradle-7.4-docs.zip!/gradle-7.4-20211209201047%2B0000/docs/userguide/configuration_cache.html

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


Fixes writing TarGzip and ReadApk on non-files

Fixes writing TarGzip and ReadApk on non-files

@alistair-mclean


[v.next] Remove JS-related checks

Removing checks which look at the loaded JS files since I don't intent on porting them over (and Bootstrap might not depend on jQuery anyway in the future). More specifically the following checks and their related tests are removed:

W005 (jQuery)
W013 (Bootstrap version)
W015 (Bootstrap 4 detection)
E007 (Only one copy of Bootstrap)

Possibly some node packages are not required any more afterwards. Not important right now, something for the end spurt.
Status

Code: Done
Tests: Done
Wiki: Still to do

Personally, I do find these checks useful though.

OK, I have been convinced that those checks have value after all. Might port it over after all at some point (but it does not nessarily have to be me, PRs from others are welcome!)
Adding check for popper.js sounds like a good idea and has been added to the list at #424.


Missing protocol listings compositors report support for?

https://github.com/vially/wayland-explorer/tree/main/protocols (and https://github.com/vially/wayland-explorer/tree/main/src/data/protocols) has some missing protocols as reported by the following command:
for i in $(awk -F'"' '/interface/ {print $4}' src/data/compositors/*.json | sort | uniq); do
    [ $(grep -r src/data/protocols/ -we $i | wc -l) -eq 0 ] && echo $i
done

zwp_input_method_manager_v2
zwp_text_input_manager_v1
zwp_text_input_manager_v2
zxdg_exporter_v1
zxdg_importer_v1
zxdg_shell_v6

Not sure if some of those are false positives. Both Sway and Mir for example report support for e.g. zwp_input_method_manager_v2 (https://gitlab.gnome.org/World/Phosh/phosh/-/blob/main/protocol/input-method-unstable-v2.xml?) but that doesn't appear to be visible on https://wayland.app/protocols/input-method-unstable-v2, but I'm not so sure on the origins of that one.

@vially Any comment?

zwp_input_method_manager_v2

As you've found out, this interface is part of the input-method-unstable-v2 protocol which has not been merged upstream yet. This issue has some more context about state of the various Wayland input protocols.
It looks like this protocol may make its way upstream at some point, but it may be merged under the input_method_v3 name.

zwp_text_input_manager_v1
zwp_text_input_manager_v2

These interfaces are coming from the text-input-unstable-v1 and text-input-unstable-v2 protocols respectively. They have been superseded by text-input-unstable-v3 and that's why they are not listed on the site (see the motivation for this below).

zxdg_exporter_v1
zxdg_importer_v1

These interfaces are coming from the xdg-foreign-unstable-v1 protocol which has been superseded by xdg-foreign-unstable-v2.

zxdg_shell_v6

This interface is coming from the xdg-shell-unstable-v6 protocol which has been superseded by xdg-shell (stable).
Which protocols should and should not be listed on Wayland Explorer
Usually Wayland Explorer only lists protocols which have been merged upstream and are not deprecated [^1].
But this is not a hard-requirement and it may make sense to add some deprecated or in-progress protocols as long as they are marked appropriately in the UI.
The main reason why some deprecated protocols are not listed is to make it less likely for users to land on these protocols from search engines. But I think a better solution would be to display them but mark them as deprecated and make it easy to navigate to their non-deprecated options.
[^1]: External protocols are a bit special and are an exception to this rule.

But I think a better solution would be to display them but mark them as deprecated and make it easy to navigate to their non-deprecated options.

Yes please ^^ A big red bar or something making it clear they're deprecated, shouldn't be used anymore for new things and linking to the pages for the non-deprecated version would be great. They could be shown at the bottom of https://wayland.app/protocols/
I suppose they can also be periodically dropped when no compositor reports support for them any longer (have moved on to the non-deprecated versions).

zwp_input_method_manager_v2

As you've found out, this interface is part of the input-method-unstable-v2 protocol which has not been merged upstream yet. This issue has some more context about state of the various Wayland input protocols.
It looks like this protocol may make its way upstream at some point, but it may be merged under the input_method_v3 name.

Especially with this one there's a bit of a problem: some compositors (current examples being both sway and mir) have "moved on" from zwp_input_method_v1 and no longer support it, while weston only supports v1 (https://wayland.app/protocols/input-method-unstable-v1#compositor-support)
It would be nice to see that there is indeed some form of input method support even if it's a non-merged proposal. Perhaps it can be labelled somehow to make it clear it's not official yet?


add lottie animations

I would like to see examples of lottie animations in the gallery. I would like to add this feature :)

We added Windows support for Lottie and got it merged over a year ago. Lottie animations are a popular way to add rich animations, and seem like a good candidate for a sample in the gallery app. If I recall there are two paths: either runtime loading of Lottie animations, or use of codegen to create C++Windows Composition calls to Lottie that are highly optimized. The former is more inline with the cross-platform approach to Lottie, whereas the latter is the best for performance.
@victor0814gui, glad to hear you'd be willing to make a contribution to gallery to add a page showing usage of lottie animations. We would accept a PR with that. You have any more in mind?
Contribution guide here: https://github.com/microsoft/react-native-gallery/wiki/Contributing-to-React-Native-Gallery
FYI to @chiaramooney and @jonthysell in case they have anything to add about requirements a new gallery page would need to meet and/or considerations for Lottie specifically.

Thanks for the reply. I would also like to add the @react-native-community/netinfo and react-native-svg packages.


Stray output from conda-stage --stage

CONDA_STAGE_ACTION=activate; conda deactivate; conda activate "/tmp/conda-stage-m4jA/snowflakes"

Looks like a stray "echo $cmd"

It's not just stray output, the activate actually never takes place. More clues;
(snakes) [hb-test@dev2 ~]$ CONDA_STAGE_DEBUG=true conda activate snakes
/wynton/home/bengtsson/hb-test/miniconda3/envs/snakes/etc/conda/activate.d/zzz.conda-stage-auto.sh ...
Auto-staging Conda environment 'snakes'. To disable, call 'conda-stage --auto-stage=disable'
DEBUG: conda-stage() ...
DEBUG: Next CLI argument: --stage
DEBUG: action: stage
DEBUG: debug: true
DEBUG: verbose: true
DEBUG: force: false
DEBUG: args: [n=0]
INFO: Staging current Conda environment (/wynton/home/bengtsson/hb-test/miniconda3/envs/snakes) to local disk ...
DEBUG: - Using conda-stage 0.5.0
DEBUG: - Current Conda environment: snakes
DEBUG: - Using conda 4.12.0
INFO: [ONCE] Installing conda-pack, because it was missing ...
DEBUG: Additional 'conda install' options: --yes
Collecting package metadata (current_repodata.json): done
Solving environment: done

## Package Plan ##

  environment location: /wynton/home/bengtsson/hb-test/miniconda3/envs/snakes

  added / updated specs:
    - conda-pack

The following NEW packages will be INSTALLED:

  conda-pack         conda-forge/noarch::conda-pack-0.7.0-pyh6c4a22f_0
  python_abi         conda-forge/linux-64::python_abi-3.9-2_cp39

The following packages will be SUPERSEDED by a higher-priority channel:

  ca-certificates    pkgs/main::ca-certificates-2022.3.29-~ --> conda-forge::ca-certificates-2021.10.8-ha878542_0
  certifi            pkgs/main::certifi-2021.10.8-py39h06a~ --> conda-forge::certifi-2021.10.8-py39hf3d152e_2

Preparing transaction: done
Verifying transaction: done
Executing transaction: done
INFO: Total installation time: 31 seconds
DEBUG: - Using conda-pack 0.7.0
DEBUG: - CONDA_PREFIX=/wynton/home/bengtsson/hb-test/miniconda3/envs/snakes
DEBUG: - Stage cache path: /wynton/home/bengtsson/hb-test/miniconda3/envs
DEBUG: - Packaged Conda environment: /wynton/home/bengtsson/hb-test/miniconda3/envs/snakes.tar.gz (59116146 bytes; 2022-04-16 20:37:50.000000000 -0700)
DEBUG: - Stage path: /tmp/conda-stage-jXaB/snakes
INFO: Extracting /wynton/home/bengtsson/hb-test/miniconda3/envs/snakes.tar.gz (59116146 bytes; 2022-04-16 20:37:50.000000000 -0700) to /tmp/conda-stage-jXaB/snakes
INFO: Total extract time: 2 seconds
INFO: Disable any /tmp/conda-stage-jXaB/snakes/etc/conda/activate.d/*.conda-stage-auto.sh scripts
INFO: Activating staged environment
INFO: Unpacking (relocating)
INFO: Total 'conda-unpack' time: 0 seconds
DEBUG: Command to activate staged Conda environment: CONDA_STAGE_ACTION=activate; conda deactivate; conda activate "/tmp/conda-stage-jXaB/snakes"
INFO: Activating staged Conda environment: /tmp/conda-stage-jXaB/snakes
DEBUG: action='stage
stage'
DEBUG: CONDA_STAGE_ACTION=stage
stage
CONDA_STAGE_ACTION=activate; conda deactivate; conda activate "/tmp/conda-stage-jXaB/snakes"
DEBUG: conda-stage() ... done (exit_code=0)
/wynton/home/bengtsson/hb-test/miniconda3/envs/snakes/etc/conda/activate.d/zzz.conda-stage-auto.sh ... done


how to get all distinct dimensions?

how to get all distinct dimensions?

i mean i want to get distinct dimesion values,if demesions has three. a , b , c
for example:
a : 'e' , b : 'r' , c: 'fs'
a : 'sa' , b : 'r' , c: 'fs'
a : 'e' , b : 'kjkj' , c: 'fs'
i want get dimesion a distinct value 'e','sa'

@zengzhihai110 I believe you can get it via select query http://druid.io/docs/latest/development/select-query.html
Also If you are only interested on Top N values you can use a TopN query.

@zengzhihai110 your best bet is a lexicographic topN, which can paginate
through all values of a dimension.
http://druid.io/docs/latest/querying/topnmetricspec.html
On Wed, Sep 16, 2015 at 2:08 PM, Nishant<EMAIL_ADDRESS>wrote:

@zengzhihai110 https://github.com/zengzhihai110 I believe you can get
it via select query
http://druid.io/docs/latest/development/select-query.html
Also If you are only interested on Top N values you can use a TopN query.
—
Reply to this email directly or view it on GitHub
https://github.com/druid-io/druid/issues/1733#issuecomment-140895666.

thanks


Utility tool: reraise_as_click_exception

Proposed changes
small utility tool for reraising exceptions as click.ClickException. Prevents the need to write an additional test for test coverage each time where we now use the following pattern:
try:
    ...
except <Type[Exception]> as e:
    raise ClickException(str(e))

Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to agents-aea?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
[ ] Lint and unit tests pass locally with my changes and CI passes too
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that code coverage does not decrease.
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

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

Codecov Report
Base: 96.91% // Head: 96.91% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (a5816bf) compared to base (fba104d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #458   +/-   ##
=======================================
  Coverage   96.91%   96.91%
=======================================
  Files         208      208
  Lines       18922    18929    +7
=======================================
+ Hits        18338    18345    +7
  Misses        584      584

Flag
Coverage Δ

unittests
96.91% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

aea/cli/utils/click_utils.py
94.59% <100.00%> (+0.26%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

failures

ubuntu 3.7 - reading stdout from click.CliRunner.invoke - issue #171>       assert "Done" in result.stdout
E       AssertionError: assert 'Done' in 'Updating hashes\n'
...
FAILED tests/test_cli/test_package_manager/test_lock.py::TestLockCommand::test_lock

macos 3.10 - issue #456E       TypeError: Parameter to MergeFrom() must be instance of same class: expected cosmos.base.v1beta1.coin_pb2.Coin got cosmos.base.v1beta1.coin_pb2.Coin.
...
FAILED tests/test_cli/test_transfer.py::TestCliTransferFetchAINetwork::test_integration
FAILED tests/test_cli/test_transfer.py::TestCliTransferFetchAINetworkWithPassword::test_integration

windows 3.8 - reading stdout from click.CliRunner.invoke - issue #171>       assert test_param.message in result.output
E       AssertionError: assert 'OK!' in 'Processing C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\tmp70yl09gq\\packages\\fetchai\\connections\\gym\\connection.yaml\n'
E        +  where 'OK!' = _TestPublicIdParameters(side_effect=[[(None,)], [], [('fetchai', 'gym', '0.19.0')]], exit_code=0, message='OK!').message
E        +  and   'Processing C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\tmp70yl09gq\\packages\\fetchai\\connections\\gym\\connection.yaml\n' = <Result okay>.output
...
FAILED tests/test_cli/test_check_packages.py::TestCheckPackagesCommand::test_check_public_id_failure_wrong_public_id[test_param2]

windows. 3.9 - timeout while waiting for loop to start (rare)            multiplexer1.connect()
>           multiplexer2.connect()
...
aea\multiplexer.py:814: in connect
    self._thread_runner.start()
aea\helpers\async_utils.py:319: in start
    self.call(asyncio.sleep(0.001)).result(1)
aea\helpers\async_utils.py:286: in result
    return self._future.result(timeout)
...
>                   raise TimeoutError()
E                   concurrent.futures._base.TimeoutError
...
self._thread_runner.start()
...
FAILED tests/data/dummy_aea/vendor/fetchai/connections/local/tests/test_misc.py::test_communication


Updating UI/UX design of Landing page

Hey, I'm a UIUX designer And I have worked on many projects before where I have improved the designs of the website. So I think I can update the design of swapreads, as the current design does not match what the website caters So we can change the typography, colour schemes, Visual hierarchy to make the website more engaging and user friendly.
Please assign this issue to me under GSSoc'24 (Level-3)

@PiyushKalyanpy Show me the screenshot after updating the UI in your local system. If I liked it then I will surely merge it.


Update adiabatic 3SAT example and fix from_symbolic issues

Following #249, this updates our adiabatic3sat example to use the new symbolic Hamiltonian functionality. It also changes the parsing of symbolic Hamiltonians because there were a few issues with the previous implementation, particularly it was failing when the symbolic Hamiltonian contained powers, eg. H = Z1 ** 2 + Z2 ** 2. The current version seems to work in all cases I tried, when the Hamiltonian is a polynomial function of tensor products of one-qubit matrices. I believe it is almost always the case.
As you can see in the 3SAT example code (in functions.py) using from_symbolic significantly simplifies the construction of custom Hamiltonians since we avoid many of the complicated functions we previously had there. However there is a performance issue that remains. Here are some benchmarks of the adiabatic3sat/main.py using Trotterized Hamiltonian on CPU:

nqubits
master
symbolic (this PR)

4
1.89493
2.81755

8
9.10203
15.76547

10
11.64693
20.20957

12
13.97034
23.07952

14
14.59212
23.76182

16
18.73169
30.16241

20
51.17262
73.60861

I thought that this is because from_symbolic recreates some Hamiltonian objects during the TrotterHamiltonian construction, however a fix that I had in mind did not help much, so I am still investigating how to improve on this.

Thanks. The performance deterioration is dominated just by the hamiltonian/sympy construction, right?

Thanks. The performance deterioration is dominated just by the hamiltonian/sympy construction, right?

This what I believe as well, however I would like to do a few more tests to confirm this. I am not sure if at these sizes sympy alone can justify this difference because the Hamiltonians do not have that many terms (eg. the 20 qubit one is just 17 clauses).
Another reason for the difference could be that in the master we exploit the fact that the same Hamiltonian term is applied to all qubits. To demonstrate this better, for example for the TFIM there are two ways to construct the TrotterHamiltonian:
matrix = np.kron(matrices.Z, matrices.Z) + np.kron(matrices.X, matrices.I)
# Use the same term for all qubits
term = Hamiltonian(2, matrix, numpy=True)
term_dict = {(i, i + 1): term for i in range(nqubits - 1)}
term_dict[(nqubits - 1, 0)] = term
trotter_ham = TrotterHamiltonian.from_dictionary(term_dict)

# Use different terms
term_dict = {(i, i + 1): Hamiltonian(2, matrix, numpy=True) for i in range(nqubits - 1)}
term_dict[(nqubits - 1, 0)] = Hamiltonian(2, matrix, numpy=True)
trotter_ham = TrotterHamiltonian.from_dictionary(term_dict)

Clearly the first approach is more efficient because it calculates the exp(-1j * dt * matrix) only once and uses it for all pairs, while the second will repeat the same calculation many times. This is just a 4x4 matrix so it is not a huge exponentiation but there will still be a difference. I think that from_symbolic currently follows the second method. I fixed this in another branch but there was no improvement in the 3SAT performance.

Ok, you could try to profile the symbolic to numeric transformation in the _SymbolicHamiltonian, there might be some specific symbolic operation or combination of operations which might be inefficient.

Ok, you could try to profile the symbolic to numeric transformation in the _SymbolicHamiltonian, there might be some specific symbolic operation or combination of operations which might be inefficient.

I did some profiling and the problem seems to not be related to sympy. Particularly I observe that the matrix exponentiation (expm) function has cumtime 2.6sec for 10 qubits on my local machine when using master while this is 16sec when using this branch. Therefore I believe the main performance issue is what I wrote above. I pushed a fix that reduces the expm time to 8sec for this example but I will have a more detailed look a bit later.

Great, let us know if you find further evidences.

I reverted the last commit because it seemed to break the example in terms of finding the right bitstring solution. At the current state this PR should work okay modulo the performance issue mentioned in the first post. If you like we can merge this to #249 to avoid confusion and I can open a new PR with the performance fix once we have that. Otherwise I will push it directly here.

Ok, lets keep this open until the performance is sorted out.

I fixed the issue and now the 3SAT solution agrees with master, so there are no issues in terms of result.
In terms of performance, I played a bit with reducing the duplicate Hamiltonian objects created by make_compatible and could improve performance slightly, but still not reach the level of master. Here is the updated version of the table from the first post:

nqubits
master
symbolic (first post)
symbolic (latest push)

4
1.89493
2.81755
1.87313

8
9.10203
15.76547
12.55959

10
11.64693
20.20957
15.52563

12
13.97034
23.07952
21.11225

14
14.59212
23.76182
21.23374

16
18.73169
30.16241
23.90576

20
51.17262
73.60861
66.17026

According to the profiling, now hamiltonian.exp is called the same number of times from this branch and master, however expm is called ~6x more from this branch for (for 12 qubits). This fully explains the performance difference shown in the table. It happens because the custom functions used to create the Hamiltonians on master take better advantage of caching compared to the "automatic" creator in make_compatible.
Note that the performance difference is problem dependent. For example I tried adiabatic evolution with TFIM as H1 and there is no difference between this PR and master, because in this case it happens that the automatic Hamiltonian agrees with the one from master.

Ok, so in summary the symbolic approach introduces a tiny overhead due to extra calls / missed caching. I think that is an acceptable compromise, however I would suggest to highlight this issue in the docs, saying that the numerical approach may be faster than the symbolic one.

Ok, so in summary the symbolic approach introduces a tiny overhead due to extra calls / missed caching. I think that is an acceptable compromise, however I would suggest to highlight this issue in the docs, saying that the numerical approach may be faster than the symbolic one.

Just for a check, I tried using the normal sum(X) Hamiltonian in the 3SAT example (instead of normalizing using times) and performance is improved by a few seconds however it is still not as fast as master. Therefore what I wrote in the previous post is not really true.
In any case, I updated the docs in several places (in make_compatible docstring, in the adiabatic evolution how-to example and in the symbolic Hamiltonians how-to example) mentioning that making the Hamiltonians compatible manually when using Trotter decomposition for adiabatic evolution may lead to better performance than relying on this automatic algorithm. I will keep doing some tests to find other cases where these performance differences exist, however if you believe the difference is acceptable then this PR should be okay now.

Great, thanks. I think we can merge this now.


Rgetz update iiod context script

A few minor tweaks to update the file, and make it more useful on non-FPGA systems.

I have tested on x86 (HWMON); RPi (CN0566 [no HAT EEPROM]); and ZedBoard (FMCOMMS3). I have a few more I will add later today.


 As some firmware still have a few issues with spike, they are commented out at the moment.

Thanks for the changes :)


New version: Google.PlatformTools version 35.0.2

Checklist for Pull Requests

[X] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.9 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Duplicate of #190804


fix: remove ibm z pictograms

Closes https://github.com/carbon-design-system/carbon-website/issues/3100

ibm z pictograms are not longer visible

@aagonzales I think so, based on this comment https://github.com/carbon-design-system/carbon/pull/11973


Publish library on crates.io?

Hi @estin ,
geosuggest has not been published yet on crates.io.
It'd be great if you do as geosuggest supports updates from geonames, unlike other static reverse geocoder libraries on crates.io.

Hi! I will try to prepare geosuggest for publish on crates.io
Before publish it needs to resolve next tasks

update dependencies
better docs
example of library mode
index updater
refactor for more clear rust code (optional)

done


Fixes Azure Storage Explorer Download

CodePlex does some redirecting and downloading using ajax.  In order to
get this to work it requires a little bit of automation.

:+1:


Fixing doc for HTTP and --no-webid

Heh, you guys, don't forget to delete the branches after merging :)


[Bug][Github] Error inserting raw rows into _raw_github_api_pull_request_commits (500)

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
The GitHub plugin pipeline task for a GitHub repository with;

~ 125,000 commits
~ 40,000 pull requests (open & closed)

Logs:
TODO: Working on obtaining them, need to increase the request timeout of nginx

Simplified Task JSON:
{
    "id": 125907,
    "createdAt": "2023-10-25T19:15:17.77Z",
    "updatedAt": "2023-10-25T19:19:15.662Z",
    "plugin": "github",
    "subtasks": [
        "collectApiPullRequests",
        "extractApiPullRequests",
        "collectApiComments",
        "extractApiComments",
        "collectApiPullRequestCommits",
        "extractApiPullRequestCommits",
        "collectApiPullRequestReviews",
        "extractApiPullRequestReviews",
        "collectApiPrReviewCommentsMeta",
        "extractApiPrReviewComments",
        "collectAccounts",
        "extractAccounts",
        "collectAccountOrg",
        "ExtractAccountOrg",
        "enrichPullRequestIssues",
        "convertRepo",
        "convertPullRequestCommits",
        "convertPullRequests",
        "convertPullRequestReviews",
        "convertPullRequestLabels",
        "convertPullRequestIssues",
        "convertPullRequestComments",
        "convertAccounts"
    ],
    "options": "{\"connectionId\":5,\"githubId\":509,\"name\":\"xxxx/xxxx-xxxx-xxx-xxxxxx-xxx\",\"timeAfter\":\"2023-04-24T00:00:00-04:00\"}",
    "status": "TASK_FAILED",
    "message": "subtask collectApiPullRequestCommits ended unexpectedly\nWraps: (2)\n  | combined messages: \n  | {\n  | \terror inserting raw rows into _raw_github_api_pull_request_commits (500)\n  | \t=====================\n [...] \terror inserting raw rows into _raw_github_api_pull_request_commits (500)\n  | }\nError types: (1) *hintdetail.withDetail (2) *errors.errorString",
    "errorName": "subtask collectApiPullRequestCommits ended unexpectedly\ncaused by: error inserting raw rows into _raw_github_api_pull_request_commits (500), [...] error inserting raw rows into _raw_github_api_pull_request_commits (500)"
    "progress": 0.17391305,
    "progressDetail": null,
    "failedSubTask": "collectApiPullRequestCommits",
    "pipelineId": 57,
    "pipelineRow": 6,
    "pipelineCol": 14,
    "beganAt": "2023-10-25T19:15:18.344Z",
    "finishedAt": "2023-10-25T19:19:15.655Z",
    "spentSeconds": 237
}

Full Task JSON (1.2MB):
devlake-github-500.json
Screenshot:

What do you expect to happen
I expected this task to be successful.
How to reproduce
This is a good question, I am guessing with a repository with a significant amount of PRs and commits.
Anything else
Possibly related to https://github.com/apache/incubator-devlake/issues/6320
Version
v0.18.0
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Are error messages when you "hover to view the reason" the same with devlake-github-500.json?
@mkaufmaner

Are error messages when you "hover to view the reason" the same with devlake-github-500.json?

I am trying to get the logs but when the pod restarted with the updated nginx configuration the logs got blown away. Rerunning the task now to get the logs. Will probably take a few minutes.

@d4x1 Updated the main bug report with the full log for the failed github task. Uncompressed they are 32.7MB. See https://github.com/apache/incubator-devlake/files/13178290/task-129911-2-1-github.log.zip

@d4x1 Upon further investigation, it appears to be due to a resource limitation on our GHE server and the requests are timing out. Wish we could get graphql working, which we may get working after upgrading our GHE to the latest stable version of 3.10, but that is TBD.
Side note; is there a client side request timeout I should be worried about? I tried looking through the source code and documentation but couldn't find anything.

Time default timeout of github graphql is 30s, but you can change it by setting an Env Var named API_TIMEOUT, keep in mind the s part is required, you can specify s for seconds, m for minutes and h for hours.

Closed due to inactivity,


Add SplitOnProvidedLabel enrichment

Splits a resource into multiple resources when multiple providedLabel are present.
This is useful when a mapping error or limitation in partner data makes it impossible/impractical to split resources properly at mapping time. This is the case with NARA's subject mapping (it's not clear yet whether "impossible/impractical" is the case--this may simply be our mistake).

:tada:


fix(links): Fix article links at bottom of Manage Protected Devices page

Manage protected devices with Microsoft 365 Business Premium.
Two of the links at the bottom 404 Page Not Found currently.
Can't replace third link Add a managed device aka m365bp-app-protection-settings-for-android-and-ios.md because it was "yanked" out here on 9/14/22.  I've tried to find where it was redone or replaced with no joy.
Signed-off-by: jmeridth<EMAIL_ADDRESS>

@denisebmsft could you please take a look at this PR?  I ask because you have made changes to this page previously.  Thank you in advance.  Cheers.

@efrene can you please take a look at this PR? Do I need to make any changes? Thanks /cc @denisebmsft

bump @efrene @denisebmsft


Align our controllers on the args provided to commissioning

Problem
chip-tool and chip-device-ctrl are not consistent in terms of which of node id and fabric id they allow to be provided and how those get used....
Proposed Solution
Align this between the controllers.

I'm not actually sure this makes sense given the totally different ways the controllers end up being used (e.g. the need to keep providing the node id in chip-device-ctrl but not in chip-tool....)


[MM-51751] Fix regex for tags trigger in CI/CD

Summary
Fix CD workflow trigger
Ticket Link
https://mattermost.atlassian.net/browse/MM-51751

Codecov Report
Patch and project coverage have no change.

Comparison is base (a640624) 23.33% compared to head (22d2509) 23.33%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #14   +/-   ##
=======================================
  Coverage   23.33%   23.33%
=======================================
  Files           3        3
  Lines          60       60
=======================================
  Hits           14       14
  Misses         44       44
  Partials        2        2

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Improve volume control

The volume control currently only works with a static volume button in home assistant.
It can be improved by implementing it in a way the scrollbar from home assistant can be used.
Originally posted by @ptimatth in https://github.com/alexmohr/sonyapilib/pull/40#issuecomment-539183893

@ptimatth You don't have to implement this if you don't want to, I've just added the issue that the idea can be tracked :)

@Liborsaf Is solved by #66 in combination with the MR over in the media player repo?

#66 Just reports the volume, for this issue it will need to also implement set volume from what I understand from #40 (comment), Can take a look into that tomorrow :)


Instance generator doesn't work with package declaration defined in module port list.

Hello,
Firstly I wanted to say how excellent this plugin is and how helpful it has been for my systemverilog coding.
I do have one request when you are doing an update to the plugin. When trying to use a create instance from a module that imports a package in the port list like below the module instance is not created.  A normal module port list works fine.
module example import RTL_pkg::*;                #(parameter                                    REV_CORE = 16'h0000,                  parameter                                    NUM_CORE  = 16'h0000)                 (input  logic                                 clk_sys,                      input  logic                                 reset_n,                      input  logic [(ADDR-1):0]                    address,                      input  logic                                 write                        );

I only get an issue if I ommit the endmodule like in your example. But if I add the endmodule then it works as expected

Thanks for having a look at it TheClams. Unfortunately, it never works for me with the package defined within the module port list. For example this example works without the package defined in the port list.
`module reg_data #(parameter WIDTH = 1)
(
input  logic                   clk,
input  logic                   reset_n,
input  logic [(WIDTH-1):0]     data_in,
output logic [(WIDTH-1):0]     data_out
);
// Register data
always_ff @(negedge clk or negedge reset_n)
begin
if (!reset_n)
begin
data_out  <= 'b 0;
end
else
begin
data_out  <= data_in;
end
end
endmodule : reg_data`
However this example does not work with the package defined in the port list.
`module reg_data import RTL_pkg::*;
             (
             	input  logic                   clk,
             	input  logic                   reset_n,
             	input  logic [(WIDTH-1):0]     data_in,
             	output logic [(WIDTH-1):0]     data_out
             );

// Register data
always_ff @(negedge clk or negedge reset_n)
begin
if (!reset_n)
begin
data_out  <= 'b 0;
end
else
begin
data_out  <= data_in;
end
end
endmodule : reg_data`.
Could you possibly try this second example?
Thanks
mm4dd

I tried both ST3 and ST4, but I still can't reproduce:

Maybe check which version of the plugin you have ?

Hi TheClams. Thanks for trying my code. I have uninstalled and reinstalled the pluggin and it is V2.24.1. I think it is the latest. I am not sure what the issue is but it has never worked properly for me using packages with my setup. I appreciate taking the time to look at my issue anyways. Cheers mm4dd.

Ok this is indeed the latest version for ST3...
There is explicit code to handle the import statement so it is quite strange it does not work for you.
Which OS are you using ? I tested this only on Windows, I could test it again on Linux during the week.

I finally have managed to get the instance tool to work for my package instance port list. I had to reinstall the package a few times to get it to finally work. Thanks for all you assistance TheClams.


Sample's files is unusable for binary files

It gives pydantic errors because Sample has hardcode file contents to be str

Ah, I see, the files should be listed by path not by contents.  This should be made clear in the documentation.

Thanks! Here are some improvements to those docs: https://github.com/UKGovernmentBEIS/inspect_ai/pull/513

Resolved with https://github.com/UKGovernmentBEIS/inspect_ai/pull/513


Are instructions to build as root correct?

Here: https://github.com/OLSF/libra/wiki/Validator-Onboarding-Guide
it says:

Is that correct? (fwiw it doesn't work for me).

Can I haz trace please :)

$ sudo make bins
[sudo] password for ubuntu:
#Build and install genesis tool, libra-node, and miner
cargo run -p stdlib --release
bash: cargo: command not found
Makefile:43: recipe for target 'bins' failed
make: *** [bins] Error 127

(in general building as root is a bad idea and it seems to work to build not as root).

So that error for cargo is that you didn't complete the installation.  Seems you didn't initialize the cargo path, or reset the terminal. We probably need more instructions around that.
Also you are right sudo would only be needed for make deps.

Cargo is on my user's path.


Image format list not sorted and shuffling

it's flickering like crazy
updates at 60fps....

 % cargo --version
 cargo 1.81.0 (2dbb1af80 2024-08-20)

CLI :
 % ./target/debug/spectro-cam-rs
2024-12-19T16:26:22.237Z INFO  [egui_glium::painter] Using GL 1.4
2024-12-19T16:26:22.312Z WARN  [spectro_cam_rs::gui] Could not open camera Name: USB 2.0 Camera: USB-ZH, Description: Video4Linux Device @ /dev/video1, Extra: , Index: 1 with format None: Could not get device property CameraFormat: Failed to Fufill
2024-12-19T16:26:22.312Z WARN  [spectro_cam_rs::gui] Could not open camera Name: USB 2.0 Camera: USB-ZH, Description: Video4Linux Device @ /dev/video1, Extra: , Index: 1 with format AbsoluteHighestResolution: Could not get device property CameraFormat: Failed to Fufill
2024-12-19T16:26:22.312Z WARN  [spectro_cam_rs::gui] Could not open camera Name: USB 2.0 Camera: USB-ZH, Description: Video4Linux Device @ /dev/video1, Extra: , Index: 1 with format Exact(CameraFormat { resolution: Resolution { width_x: 640, height_y: 480 }, format: MJPEG, frame_rate: 30 }): Could not get device property parameters: Invalid argument (os error 22)
2024-12-19T16:26:22.312Z WARN  [spectro_cam_rs::gui] Could not open camera Name: USB 2.0 Camera: USB-ZH, Description: Video4Linux Device @ /dev/video1, Extra: , Index: 1 with format Exact(CameraFormat { resolution: Resolution { width_x: 640, height_y: 480 }, format: YUYV, frame_rate: 30 }): Could not get device property parameters: Invalid argument (os error 22)
2024-12-19T16:26:22.312Z WARN  [spectro_cam_rs::gui] Could not query camera Name: USB 2.0 Camera: USB-ZH, Description: Video4Linux Device @ /dev/video1, Extra: , Index: 1

Thanks for the report. I am at the moment in the progress of fixing all the introduced bugs after upgrading the dependencies.
I will get to this in the new year.


Getting response 400 but still not triggering error handler function on IE 9

Hi,
My upload is working fine for chrome and firefox but on IE9, when I upload a file and server responds with 400, neither success nor my error callback handler is getting called.
I am also sending the response data back from server. And I can see the data in developer tool.

That is already mentioned in the readme file, see the old browsers known issues section.


ORecordDuplicatedException upon new record after cluster has been truncated but index still has it

com.orientechnologies.orient.core.storage.ORecordDuplicatedException: Cannot index record Some_Class{xxxxx}: found duplicated key 'xxxxx' in index 'some_key' previously assigned to the record #28:0 RID=#28:0
	at com.orientechnologies.orient.core.index.OIndexTxAwareOneValue.checkEntry(OIndexTxAwareOneValue.java:224)
	at com.orientechnologies.orient.core.index.OClassIndexManager.checkIndexedPropertiesOnCreation(OClassIndexManager.java:341)
	at com.orientechnologies.orient.core.index.OClassIndexManager.checkIndexes(OClassIndexManager.java:585)
	at com.orientechnologies.orient.core.index.OClassIndexManager.onRecordBeforeCreate(OClassIndexManager.java:410)
	at com.orientechnologies.orient.core.hook.ODocumentHookAbstract.onTrigger(ODocumentHookAbstract.java:226)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.callbackHooks(ODatabaseDocumentTx.java:1069)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.executeSaveRecord(ODatabaseDocumentTx.java:1966)
	at com.orientechnologies.orient.core.tx.OTransactionNoTx.saveRecord(OTransactionNoTx.java:159)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:2568)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.save(ODatabaseDocumentTx.java:121)
	at com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:1768)
	at com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:1759)

We face this issue when we truncate the clusters upon application restart and we add a record which previously existed(meaning a new record with same key as before) but it fails because index still has the record from past.
For our application it is okay to clear the index upon start, so we can solve the issue currently by clearing the index using
OIndex.clear();

Though we have solution for us but issue seems important in general.

Hi @mecp
which version are you using? If it's 2.1.7 it's definitely a bug.
Thanks
Luigi

We are using 2.1.7
regards.

Hi @mecp .
How did you truncate cluster ?
By call of com.orientechnologies.orient.core.metadata.schema.OClassImpl#truncate or directly through com.orientechnologies.orient.core.storage.OCluster#truncate ?
In case of last one , that is expected behaviour, because cluster does not know anything about indexes and indexes are managed on higher class level.

That's how we truncate the cluster.
db.command(new OCommandSQL("truncate cluster " + clusterName)).execute();

This issue was marked next hotfix at 2.1.7, It's 2.1.11 already but reply came only yesterday. Anyway for us it is not urgent as I had mentioned, because in our use case we have a workaround.

How did you truncate cluster ?
By call of com.orientechnologies.orient.core.metadata.schema.OClassImpl#truncate or directly through com.orientechnologies.orient.core.storage.OCluster#truncate ?

Related to above question, I would like to suggest that the Java Native API should have clearly documented boundaries for user APIs and internal-only APIs.

Well , about next hotfix milestone. It means next hotfix after it will be fixed by developer.
If you need next hotfix in literally next released hotfix I suggest you to subscribe to commercial support.
About issue itself, you should use
db.command(new OCommandSQL("truncate class " + className)).execute();
For the reason declared above.

I would like to suggest that the Java Native API should have clearly documented boundaries for user APIs and internal-only APIs.
We are working on the way to separate this API.
I am closing this issue but if solution will not work for you, I will appreciate if you reopen it.

Well , about next hotfix milestone. It means next hotfix after it will be fixed by developer.
If you need next hotfix in literally next released hotfix I suggest you to subscribe to commercial support.

No as I told it was only for understanding purposes, thanks for clarification.

About issue itself, you should use
db.command(new OCommandSQL("truncate class " + className)).execute();

Why should I use your suggestion when what I want is to truncate a cluster only, but not all the data from a class, wouldn't I loose all the class data instead of just a cluster if I do what you suggest? And why should records from a truncated cluster have an entry in some index, shouldn't process of truncating the cluster also remove those records from indexes?

Well you persuaded me, I will fix this issue in couple of hours.

Fixed

Thanks. :+1:


table view with two way sync

Table view visualization with two way sync is implemented.
https://github.com/opensearch-project/observability/issues/916

Codecov Report

Merging #1022 (53a3975) into main (a1490cc) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #1022   +/-   ##
=========================================
  Coverage     71.87%   71.87%
  Complexity      291      291
=========================================
  Files            42       42
  Lines          2311     2311
  Branches        240      240
=========================================
  Hits           1661     1661
  Misses          509      509
  Partials        141      141

Flag
Coverage Δ

opensearch-observability
71.87% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Please address the comments and resolve the conflicts for this PR.


Ender blast problems

[ ] Endstone cuboid can't be broken: http://youtu.be/PlLt4nD7Jh4
[ ] No velocity and tps in the spawn area                ^
[x] Proximity alarm error: https://github.com/twizmwazin/CardinalPGM/issues/607
[ ] Can place water near Endstone Cuboid
[ ] The wool room can be broken with tnt

Related with https://github.com/twizmwazin/CardinalPGM/issues/153 , https://github.com/twizmwazin/CardinalPGM/issues/120 and https://github.com/twizmwazin/CardinalPGM/issues/605

Ender blast was removed from the rotations, i think we should close this and reopen when it be reuploaded

Just because a map isn't in the Overcast Network rotations doesn't mean it shouldn't work properly with Cardinal.

@iEli2tyree011 I know, but maybe there were errors for the xml, i don't know

@TiTo-418 I have a funny feeling that isn't why it was removed

@twizmwazin I read somewhere in oc.tc forums that the map makers decided to remove it bcos it played poorly (or that's what they said)

Tested and wool room can't be broken with tnt anymore


Testability statements section3

Completed testability statements for Baseline Standard Section 3.1.

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


Document cryptographic key storage ADR

see comments here https://github.com/get10101/10101/pull/33#discussion_r1083545169

Note: we want to support BIP39 seed phrases


[9.x] Fix getController on Route class

The getController method obviously assumes that the $this->action['uses'] is always a string and it starts to parse it, But it is sometimes a Closure.
Laravel internally uses this method only after it makes sure that the controller is an action in the run method, but since this is a public method it should have a way to cover the below usage.

Since the isControllerAction is protected we can not expect the caller to check it before calling the  getController.

To prove the bug, you can run this on a newly installed laravel instance from a typical controller method or a command.
foreach (app('router')->getRoutes()->getRoutes() as $route) {
     dump($route->getController());
}

This can be considered as a breaking change since it was throwing a TypeError before, now instead it is returning null.

Using latest version of laravel 9.x:

(I just stumbled upon this bug when I was working on my laravel-microscope package.)

Methods runController, getControllerClass, and getControllerMethod have the same behavior as they assume isControllerAction has already been checked.
External code should be calling $route->isControllerAction() before invoking $route->getController().

@derekmd Yeah, An other way of fixing it is to wrap it in a try/catch and handle the TypeError. This does not cause a duplicate call and we can re-throw the TypeError with a better message to preserve the backward compatibility.


JenkinsDownloadArtifacts task fails with "Cannot find module 'underscore'"

Question, Bug, or Feature?
Type: Bug
Enter Task Name: JenkinsDownloadArtifacts
Environment

Server - Azure Pipelines or TFS on-premises?

If using Azure Pipelines, provide the account name, team project name, build definition name/build number: private

Agent - Hosted or Private:

If using private agent, provide the OS of the machine running the agent and the agent version: agent OS: Windows Server 2019, agent version: 2.211.0

Issue Description
JenkinsDownloadArtifacts started failing with 'Cannot find module 'underscore'' with version 1.211.0. Currently downgraded to using version 1.208.0 as a workaround.
Task logs
JenkinsDownloadArtifact_log.txt
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting

Enabled debug logs on the pipeline

Error logs
(Duplicate of task logs)
JenkinsDownloadArtifact_log.txt

We are also facing this issue this Morning using 1.211.0, worked fine in 1.208.0 looks like #16907 is the culprit @PavloAndriiesh

I would have thought this is the PR that cause it: #16910

Yes you are correct, seems I picked the wrong one, updated.

This has broken numerous releases for us, completely by surprise after automatic agent updates. We have too many agents to manually roll them all back.

Sorry for the breakage. We are in the process of rolling back the change.

Any updates on this, it's been 2 Days since we have been unable to run any releases. We are unable to do a work around as the release is a large process created a long time ago. It will take significant effort to move it all to yaml pipelines where we can specify the exact version.


Platform view accessibility does not respond to taps on Moto G 4

Running the webview example project on a Moto G 4, tapping on elements within the webview does not focus them. Instead, to give talk back focus to anything within the webview, I have to swipe left/right. Tapping on Flutter widgets, however, does correctly focus them for talk back.
The Moto G 4 that I'm using is running Android 7.0.

CC @amirh

@mklim

At a first glance it's worth pointing out that this is Android N, so probably unrelated to the brittle workarounds we've needed to add post O. Probably some other problem with the a11y ID behavior though.

Hi @matthew-carroll  @mklim
Is this issue still valid?
Thank you

The Moto G 4 that I'm using is running Android 7.0.

@matthew-carroll Hello, this particular model seems to be discontinued now. Is there a way for you to confirm if the original issue / behavior you reported still occurs with latest stable ?

No. This issue is 5 years old. I'm sure at the time I was using a device from the Flutter team's test devices. Please follow up with current team members to see what makes sense in terms of repro.


Sort subsections within sections

I was feeling the need for it each time I was navigating BIDS, but seeing
https://github.com/bids-standard/bids-specification/pull/1128/files#diff-98d0f806abc9af24e6a7c545d3d77e8f9ad57643e27211d7a7b896113e420ed2 suggesting the same made me propose it.
I think having subsections sorted where there is no really really a requirement for order helps visitor to navigate the document/website instead of doing linear search among all subsections.

Fine as is for me but always wondering if we should not put a comment in the yml saying that those sub sections are ordered alphabetrically.

I rebased and added a comment for each of those sections. AFAIK comments are ok for yaml so hopefully it would not break any workflow. Check it out


Updating async header annotations...

Updating async header annotations as per RPaaS documentation.

Hi, @subbartt. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.


insert into case sensitive

CREATE TABLE `Test3` (
  `k1` int(11) NULL COMMENT "",
  `gmt_create` date NOT NULL DEFAULT "1990-04-24" COMMENT ""
) ENGINE=OLAP
DUPLICATE KEY(`k1`)
COMMENT "OLAP"
DISTRIBUTED BY HASH(`k1`) BUCKETS 2
PROPERTIES (
"replication_num" = "1",
"in_memory" = "false",
"storage_format" = "DEFAULT"
);

insert into Test3(K1, GMT_create) values(1, "2021-01-01");

The problem has just been fixed.
#1376