How to extract manual and kinetic feature for aist++ pkl data(train/test)?

Hi, @Luke-Luo1
Thanks for your fantastic work! I eagerly wonder how to extract manual and kinetic feature for aist++ pkl data(train/test)?
I am aware of the difference between popdg dataset and aist++ dataset, in which kinetic foward i.e. "full_pose" smpl_forward is different in dataset.py:
for popdg, in ../dataset/load_popdanceset.py(line:169-198)
        smpl = SMPLSkeleton()
        # to Tensor
        root_pos = torch.Tensor(root_pos)
        local_q = torch.Tensor(local_q)
        # to ax
        bs, sq, c = local_q.shape
        local_q = local_q.reshape((bs, sq, -1, 3))

        # After the extraction of PoPDanceSet using HyBrIK,
        # rotation adjustments need to be made to ensure that the human body's z-axis is oriented upwards.
        root_q = local_q[:, :, :1, :]
        root_q_quat = axis_angle_to_quaternion(root_q)
        rotation = torch.Tensor(
            [0.7071068, -0.7071068, 0, 0]
        )
        root_q_quat = quaternion_multiply(rotation, root_q_quat)
        root_q = quaternion_to_axis_angle(root_q_quat)
        local_q[:, :, :1, :] = root_q

        # The coordinates of the human body's root joint
        # need to be shifted and scaled to fall within the range of [-1, 1].
        pos_rotation = RotateAxisAngle(-90, axis="X", degrees=True)
        root_pos = pos_rotation.transform_points(
            root_pos
        )
        root_pos[:, :, 2] += 1
        root_pos[:, :, 1] -= 5

        # do FK
        positions = smpl.forward(local_q, root_pos)  # batch x sequence x 24 x 3

but in EDGE, there are: (in ../dataset/dance_dataset.py, line 144 - 169)
smpl = SMPLSkeleton()
        # to Tensor
        root_pos = torch.Tensor(root_pos)
        local_q = torch.Tensor(local_q)
        # to ax
        bs, sq, c = local_q.shape
        local_q = local_q.reshape((bs, sq, -1, 3))

        # AISTPP dataset comes y-up - rotate to z-up to standardize against the pretrain dataset
        root_q = local_q[:, :, :1, :]  # sequence x 1 x 3
        root_q_quat = axis_angle_to_quaternion(root_q)
        rotation = torch.Tensor(
            [0.7071068, 0.7071068, 0, 0]
        )  # 90 degrees about the x axis
        root_q_quat = quaternion_multiply(rotation, root_q_quat)
        root_q = quaternion_to_axis_angle(root_q_quat)
        local_q[:, :, :1, :] = root_q

        # don't forget to rotate the root position too 😩
        pos_rotation = RotateAxisAngle(90, axis="X", degrees=True)
        root_pos = pos_rotation.transform_points(
            root_pos
        )  # basically (y, z) -> (-z, y), expressed as a rotation for readability

        # do FK
        positions = smpl.forward(local_q, root_pos)  # batch x sequence x 24 x 3

So I guess that there must be relative change in ../eval/extract_features.py(line: 24 - 50):
        smpl = SMPLSkeleton()
        pos, q = data["pos"], data["q"]
        scale = data["scale"]
        pos *= scale

        pos = torch.from_numpy(pos).unsqueeze(0)

        q = torch.from_numpy(q).unsqueeze(0).view(1,-1,24,3)

        root_q = q[:, :, :1, :]
        root_q_quat = axis_angle_to_quaternion(root_q)
        rotation = torch.Tensor(
            [0.7071068, -0.7071068, 0, 0]
        )
        root_q_quat = quaternion_multiply(rotation, root_q_quat)
        root_q = quaternion_to_axis_angle(root_q_quat)
        q[:, :, :1, :] = root_q

        pos_rotation = RotateAxisAngle(-90, axis="X", degrees=True)
        pos = pos_rotation.transform_points(
            pos
        )
        pos[:, :, 2] += 1
        pos[:, :, 1] -= 5

        keypoints3d = smpl.forward(q, pos).detach().cpu().numpy().squeeze()  # b, s, 24, 3

Thanks for your great contribution all the time! I am truly grateful and looking forward to your kind instruction.
Best wishes!

Both in the AIST++ dataset and the PopDanceSet, the purpose of these adjustments is to ensure that the dancer faces forward towards the audience. Whether it’s through array cameras in AIST++ or monocular 3D keypoint detection in PopDanceSet, the extracted 3D body data needs to be correctly aligned when placed into the SMPL model. This alignment involves adjusting the coordinates and orientation of the body to standardize the direction the dancer is facing.
Best regards


Simple E2E tests

This PR introduces simple E2E tests that will test device discovery based on selectors for:

Discover PF - vendor, device, driver - netdev
Discover PF - vendor, device, driver - vfio
Discover PF - vendor, device
Discover VF - vendor, device, driver - netdev
Discover VF - vendor, device, driver - vfio
Discover VF - vendor, device
Discover VF - vendor, device, driver
Discover PF and VF - vendor, device, driver

Example for configuring self-hosted test machine's interfaces (README) and example github workflow were also added.
The test itself will restart Device Plugin's daemonset, check if the devices were discovered properly and proceed to the next test case.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1572

Relevant Lines:
2036

💛  - Coveralls

Hi all,
I've resolved the merge conflicts, rebased on top of current master, fixed failing checks and updated readme a bit. Hope we can get this merged soon!

I would like to close this and have something similar to what we have in the sriov-cni https://github.com/k8snetworkplumbingwg/sriov-cni/pull/282https://github.com/k8snetworkplumbingwg/sriov-cni/pull/282
to install the SRIOV operator with a custom device plugin from the PR and run our full test on it


Rework around skipping a build

Currently, we have something like if project.skip: return None in prepare_build which is then handled at trigger_build helper. It's not a really good workflow and we probably want to raise an exception instead and manage it in a proper way.
https://github.com/rtfd/readthedocs.org/blob/14942e9c1322a320ec3ecd34fe6a797e975d3a6f/readthedocs/core/utils/__init__.py#L98-L104
Additionally, we were thinking on managing this from a signal or similar that could be extended from outside. As an example, in .com we will probably be using something like organization.disabled where we will want to skip those builds also.
Also, the error message shown in the project detail page should be extended to show different messages depending on the skip reason. Currently, it's fixed to resource usage.
Ref: #4255

Related https://github.com/rtfd/readthedocs.org/pull/4991


N+1 Queries For current_user

Every time I try something like:
current_user.charts

Where a charts is another model with a many to many relationship with the user. In a controller, bullet gem alerts me there is an N+1 query:
N+1 Query detected
  User => [:charts]
  Add to your finder: :includes => [:charts]

I can usually get around this by doing Chart.where(user: current_user) but this is a lot less pleasant to work with.
Is there something simple I am missing or does current implementation of current_user prevents us from optimizing performance?

The current implementation of the current_user method is nothing but User.find(id) that is if everything is set as default and nothing is overridden or changed in the configuration file. So my humble opinion is that current_user is not causing the N+1 queries. Have you tried current_user.includes(:charts) and then access the attributes from the charts relationships ?

User.find(id).includes(:relationship) doesn't work. It should be User.includes(:relationship).find(id)

Yeah you are absolutely right, sorry about it. my beginners mistake... :(

Yeah, the problem is it's hard to chain includes onto a current_user as currently designed.

@duboff You can use .from_token_payload to solve this.
e.g.
class User

  def self.from_token_payload payload
    User.includes(:relationship).find(payload["sub"])
  end

Let me know if this solves your issue and feel free to re-open if not. Thank you!

Hi @nsarno, this does help but that now means I have to eager load the relationship everywhere which is not ideal either. Typically you only need the relationship in each controller.
I also can't (as far as I can figure out) reimplement the current_user method. Maybe it would make sense to pass relationships to it as an argument? Happy to try that myself if you think it makes sense.

@duboff You should be able to define your own current_user method. Knock checks if the method is already implemented before defining it.
Also I don't really think this qualify as a N+1 query in the sense where N will always equal to 1 in this instance (which Bullet can't know about). So the impact should never be significant and might not require the extra optimization work. This is of course up to you to assess.
As far as Knock is concerned, I don't believe it's worth the extra lines of code.


Any way to use the original images

Hi,
I was implementing some models to do VQA and found your repo really useful. However, it seems like I can only get the FRCN_FEAT and BBOX_FEAT as image inputs to the model. Is there any way to take the original images as inputs and not the extracted features?

It is not that easy and needs plenty of modifications. Currently we do not have such plan to support this.


bugfix: add /etc/hosts volume

Describe what this PR does / why we need it
Does this pull request fix one issue?
Fixes https://github.com/chaosblade-io/chaosblade/issues/263

Describe how you did it
Describe how to verify it
Special notes for reviews

@jianxingzhe Thank you for reporting the bug and fix it. Please check your git config user and email configuration.


Update Linear task status

As an improvement would be nice to be able to update the status of the task when the context menu is displayed.

I'm working on this now and should soon be complete. I will update here when it's done. Thanks

Fantastic, I've never coded on Kotlin or Java, so still getting somewhat aquainted with it. But would be great to see the branch, as per pure curiosity :)

@umbertix I've implemented this feature. Please have a look at the code in PR #23.


Add "back to top" button

As requested in #30 port over the back to top button script used on Made Mistakes.

+1


Certain Machine Crates Cannot Have Contence Pulled Apon Opening

Description
Radiation collector, containment filed generator, singularity generator, or emitter all cannot be pulled after opening corresponding crate.
Reproduction

Spawn any crated PA component: radiation collector, containment filed generator, singularity generator, or emitter in a crate.
Open said crate and pull the machine note that the machine is unanchored.
Anchor machine then unanchor machine.
Pull machine.

Additional context

Checked debug variables no noticed difference in any of the components' variables (looked at emitter with an anchored then unachored machine and an untouched machine)
AME controller has no issue
did not test radiation collector ordered from shuttle
There is a map in rotation that has this issue as it has packed radiation collectors (cant recall witch map)

Remove space glue from crated anchorable objects; should be and easy fix just use some space cleaner. Alternative: a paint scraper could be used instead, but this would be more work as the glue is sticky and the paint scrper would need to be implemented.

The collector from the shuttle works exactly the same way. Field generators, too.


Add more recorder tests

Description:
Add more tests for the recorder rewrite.
I removed state.origin as it was added with the rewrite but was not being used.
I noticed one regression, we no longer store utc_offset. The reason this was saved was for data mining/visualizations. It allows people reading the database to know if the light went on at 9am or 2pm without having to read the timezone from configuration.yaml. @rhooper, do you know if there is a way to store this in the timestamp or should we add the column again?
Example entry for configuration.yaml (if applicable):
recorder:

Checklist:
If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

This PR looks good, and I think it should work with non-sqlite backends.  I'd like to test before merging, but won't get a chance until tomorrow.

This PR will be merged when we get 👍  by @rhooper that it works fine on MySQL.

Works fine with MySQL


(maint) Use trapperkeeper-metrics webservices in PuppetDB

This commit changes PuppetDB to use the metrics-webservice from
tk-metrics now that the code from PuppetDB's metrics API has been ported
there and released so that it may be used by any trapperkeeper service.

@cprice404 looks like the transition went smoothly, thanks for all the help

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/590/
Test PASSed.


Day294

Resolves #600.

Pull Request Test Coverage Report for Build 1121

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

Totals

Change from base Build 1119:
0.0%

Covered Lines:
5

Relevant Lines:
5

💛  - Coveralls


Feature idea: automatically generate config

It would be nice to have the configuration file generated automatically on first run (if it does not exist).

Implemented by 35f193a.


Password protection for the block explorer + electrum pinned server mac app + proxy tab + electrs upgrade

Hey,
Apparently you can set a password for the explorer.
On the side of caution, maybe it is better not to share the link publicly.

Hi,
-added info on how to run Electrum on Mac in the form of an .app
-added info on how to make sure you get direct connection to your node in case you have been previously using TOR under Proxy tab in Electrum
-added section on how to proceed with updating Electrs if you have files that are changed locally

Thanks for your contribution. This pull request was resolved with the update to RaspiBolt version 3.


How to add custom drawings to iD editor's map?

HI!
I have some coordinates XY and would like to show a pin (or some other custom image) at those coordinates in iD editor. That pin shouldn't be included in osm changeset, I just want to render it on the map while user is using iD editor. That should look like this:

Can this be done with existing iD code?
What part of code should be changed/forked to support this scenario?

Thanks!

@lsecerovic Press F and on the "Customized map data" option you can load a file to use as reference while mapping


Background proxy side-effects

I was trying to show nicer details for a proxy object by pulling them from the resolved object, but calling resolvedObject while getting details tends to happen before the object gets selected in the main interface. (I think because it appears in the results during a partial match.) That forces the object to be resolved and cached before it’s actually displayed.
There also seems to be something calling for details just after the interface is dismissed, which is even worse because of this sequence:

The user dismisses the interface
The proxy cache is intentionally cleared
Something calls detailsOfObject: which calls resolvedObject which grabs and immediately re-caches the current value of the proxy

Then, sometime later:

The user calls up the proxy
It has a (potentially very old) cached value, so that gets returned

I’m not sure what the best answer is here, other than for developers to avoid calling resolvedObject when they just want the already resolved value. So for now, this gives us a way to do that.

I'm assuming you're planning on doing something with cachedProxyTarget once it's merged, so I'll merge this and wait and see!

Yeah, I was going to use it in the Zoom plug-in. It turns out this didn’t really solve the problem, but including it is pretty harmless.


bug(gatsby-source-strapi): The plugin "gatsby-source-strapi" created a node of a type "File" owned by "gatsby-source-filesystem".

ERROR during gatsby develop after upgrade to Gatsby 5.9.0 &  gatsby-source-filesystem 5.9.0 (with gatsby-source-strapi 3.2.0)
Log:
ERROR #11321  API.NODE.EXECUTION
"gatsby-source-strapi" threw an error while running the sourceNodes lifecycle:
The plugin "gatsby-source-strapi" created a node of a type owned by another plugin.
The node type "File" is owned by "gatsby-source-filesystem".
To Reproduce
Steps to reproduce the behavior:

yarn update with below config
gatsby develop

Expected behavior
Gatsby develop should not fail
System Info
"gatsby": "^5.9.0",
"gatsby-source-filesystem": "^5.9.0",
"gatsby-source-strapi": "^3.2.0",
"react": "^18.2.0",
"node": "18.13.0"

Same here.
Same version of gatsby and package. same result.
Works on gatsby 5.7.0

I also encountered the error after upgrading Gatsby to5.9.0.
I got it working again by specifying the gatsby-source-strapi plugin before gatsby-source-filesystem in the config.
    {
      resolve: 'gatsby-source-strapi',
      options: strapiConfig
    },
    {
      resolve: 'gatsby-source-filesystem',
      options: {
        name: 'pages',
        path: './src/pages/'
      },
      __key: 'pages'
    }

Not sure if this will help, but I seem to only be having issues with images retrieved from Strapi. Everything seems to be working properly for me.

I also got this error trying to upgrade to the mentioned packages and versions. It seems that rolling back just the Gatsby package fixed the original error, although it did end up failing due to a different one. The new error seems unrelated... Maybe due to having newer plugin packages that are incompatible with the older gatsby? This at least seems to indicate that the original issue is with a change in the 5.9.0 gatsby package.
Before upgrading:
    "gatsby": "^5.8.1",
    "gatsby-plugin-apollo": "^4.0.3",
    "gatsby-plugin-gatsby-cloud": "^5.8.0",
    "gatsby-plugin-image": "^3.8.0",
    "gatsby-plugin-postcss": "^6.8.0",
    "gatsby-plugin-sharp": "^5.8.1",
    "gatsby-source-filesystem": "^5.8.0",
    "gatsby-source-strapi": "^3.1.3",
    "gatsby-transformer-remark": "^6.8.0",
    "gatsby-transformer-sharp": "^5.8.0",

After upgrading:
    "gatsby": "^5.9.0",
    "gatsby-plugin-apollo": "^4.0.3",
    "gatsby-plugin-gatsby-cloud": "^5.9.0",
    "gatsby-plugin-image": "^3.9.0",
    "gatsby-plugin-postcss": "^6.9.0",
    "gatsby-plugin-sharp": "^5.9.0",
    "gatsby-source-filesystem": "^5.9.0",
    "gatsby-source-strapi": "^3.2.0",
    "gatsby-transformer-remark": "^6.9.0",
    "gatsby-transformer-sharp": "^5.9.0",

At this point I got the exception about gatsby-source-strapi trying to create a File node, so I rolled back to "gatsby": "^5.8.1",, leaving all the plugins on the newest versions. After that, I got the following:
  TypeError: The 'compilation' argument must be an instance of Compilation

  - NormalModule.js:228 Function.getCompilationHooks
  - WebpackAssetsManifest.js:784 WebpackAssetsManifest.handleCompilation
    [frontend]/[webpack-assets-manifest]/src/WebpackAssetsManifest.js:784:18
  - Hook.js:14 Hook.CALL_DELEGATE [as _call]
    [frontend]/[tapable]/lib/Hook.js:14:14
  - Compiler.js:1122 Compiler.newCompilation
    [frontend]/[gatsby]/[webpack]/lib/Compiler.js:1122:26
  - Compiler.js:1166
    [frontend]/[gatsby]/[webpack]/lib/Compiler.js:1166:29
  - Hook.js:18 Hook.CALL_ASYNC_DELEGATE [as _callAsync]
    [frontend]/[tapable]/lib/Hook.js:18:14
  - Compiler.js:1161 Compiler.compile
    [frontend]/[gatsby]/[webpack]/lib/Compiler.js:1161:28
  - Compiler.js:524
    [frontend]/[gatsby]/[webpack]/lib/Compiler.js:524:12
  - Compiler.js:986 Compiler.readRecords
    [frontend]/[gatsby]/[webpack]/lib/Compiler.js:986:5
  - Compiler.js:521
    [frontend]/[gatsby]/[webpack]/lib/Compiler.js:521:11
  - Hook.js:18 Hook.CALL_ASYNC_DELEGATE [as _callAsync]
    [frontend]/[tapable]/lib/Hook.js:18:14
  - Compiler.js:518
    [frontend]/[gatsby]/[webpack]/lib/Compiler.js:518:20

Same problem here. In my Strapi collection, I have a "main_image" and "carousel_images" it I call bouth at the same time the error happens:
gatsby-config.ts

  collectionTypes: [
    {
      singularName: "job",
      queryParams: {
        populate: {
          title: "*",
          job_categories: "*",
          main_image: "*",
          // carousel_images: "*", ---> if take of the comment the code broke.
        },
      },
    },
  ],

Started getting this same error with Gatsby v5 & Strapi v3.6.9.

File is used for images yes, so images would be the trigger.
@xSyki , enableStatefulSourceNodes seems to be opt-in. If we are not using it, nothing should break I guess?
It's kind of hard to mention that you don't support a version before it is released, right? ;)
@ramit-mitra Strapi 3 isn't supported by the latest version of this package. You can only use v1.
I am currently still on Gatsby 4, so I cannot really help directly with this error. Plus I have no free time to look into it currently. I invite everyone here to contribute into getting this error solved.

I got the same error with gatbsy 5.8.1. I tried to use gatsby 5.7.0 but still getting the error.
Is there a good package combination where it works at the moment?

I renamed a bunch of the variables in /gatsby-source-strapi/dist/download-media-files.js to
https://gist.github.com/rileybathurst/81ccfc5ef46e9c2b93f3105ffee3b58b
I don't know which one is the fix but something in here lets the site build.
renaming in the src file would be way more useful but this is going to require testing to know what I'm actually adjust and make sure I am not breaking things

Is there anyone here who has fixed this problem?

Hello,
I have the same trouble
Error: The plugin "gatsby-source-strapi" created a node of a type owned by another plugin.
The node type "File" is owned by "gatsby-source-filesystem".
If you copy and pasted code from elsewhere, you'll need to pick a new type name
for your new node(s).
The plugin creating the node:

I renamed a bunch of the variables in /gatsby-source-strapi/dist/download-media-files.js to https://gist.github.com/rileybathurst/81ccfc5ef46e9c2b93f3105ffee3b58b
I don't know which one is the fix but something in here lets the site build. renaming in the src file would be way more useful but this is going to require testing to know what I'm actually adjust and make sure I am not breaking things

UPDATE:
Now it works, but you have to change the line 57 in  /gatsby-source-strapi/dist/gatsby-node.js to
const existingNodes = getNodes().filter(n => n.internal.owner === gatsby-source-strapi || n.internal.type === "strapiFile");
Regards

downgrading to gatsby 5.7.0 and gatsby-source-filesystem 5.8.0 worked for me.

@laurenskling I attempted the suggested approach (enableStatefulSourceNodes) but unfortunately did not achieve the desired outcome.
Considering the issue stems from the node ownership override by the gatsby-source-filesystem plugin, it appears that the current fix is not ideal. In order to address this problem, I should propose an option within the createRemoteFileNodemethod from the gatsby-source-filesystem plugin that allows users to prevent the override of ownership when it used with another plugin. This approach would provide a more flexible and customizable solution.

Gatsby maintainer here 👋
Can you please open a bug report in our repo about this: https://github.com/gatsbyjs/gatsby/issues/new?assignees=&labels=type%3A+bug&projects=&template=BUG_REPORT.yml
This shouldn't happen and is probably a regression from https://github.com/gatsbyjs/gatsby/pull/37782
The current PR https://github.com/gatsby-uc/plugins/pull/431 shouldn't be merged as this needs to be fixed inside gatsby
Thanks!

Gatsby maintainer here 👋
Can you please open a bug report in our repo about this: https://github.com/gatsbyjs/gatsby/issues/new?assignees=&labels=type%3A+bug&projects=&template=BUG_REPORT.yml
This shouldn't happen and is probably a regression from gatsbyjs/gatsby#37782 The current PR #431 shouldn't be merged as this needs to be fixed inside gatsby
Thanks!

Hello @LekoArts, I don't understand why it's considered a regression in gatsby ?! This current plugin is managing nodes without ownership of them. I believe that's a bad practice, isn't it?

In simple terms:

We tell users to use createRemoteFileNode like this: https://www.gatsbyjs.com/plugins/gatsby-source-filesystem/#createremotefilenode
Your PR is changing the createNode function for createRemoteFileNode
It should continue to work how we document it in the public docs

File nodes should be managed by gatsby-source-filesystem and that's how it used to work in the past.

Hey @tinque are you doing anything other than the https://github.com/tinque/gastby-uc-plugins/commit/1a174f827be2b3810b9f7b2be27f0f85fd505560 updates? I am still hitting the issue with those updates
I get a console error showing
err Error: The plugin "gatsby-source-strapi-file" created a node of a type owned by another plugin.
  The node type "File" is owned by "gatsby-source-filesystem".

  If you copy and pasted code from elsewhere, you'll need to pick a new type name
  for your new node(s).

  The node object passed to "createNode":

          {
"id": "07830568-75f4-5d49-adf8-34461fe2d611",
"children": [],
"parent": null,
"internal": {
    "contentDigest": "2cfc1069b5169da43528a756686748c2",
    "type": "File",
    "mediaType": "image/webp",
    "description": "File \"http://<IP_ADDRESS>:1340/uploads/TWIG_Member_Seal_2022_23_41c176880a.webp\"",
    "owner": "gatsby-source-strapi-file",
    "counter": 76
},
"sourceInstanceName": "__PROGRAMMATIC__",
"relativePath":

".cache/caches/gatsby-source-strapi-file/0fe16aae7ec04193134414747f7d0c86/TWIG_Member_Seal_2022_23_41c176880a.webp",
"extension": "webp",
"prettySize": "14 kB",
"modifiedTime": "2023-05-26T03:51:00.279Z",
"accessTime": "2023-05-26T03:51:00.181Z",

Hey @rileybathurst 🙂
Did you remove your .cache folder after applying the patch?

I have executed the command gatsby clean and deleted the Cache folder, but I still get the same error message @tinque

Gatsby maintainer here 👋
Can you please open a bug report in our repo about this: https://github.com/gatsbyjs/gatsby/issues/new?assignees=&labels=type%3A+bug&projects=&template=BUG_REPORT.yml

I went ahead and created an issue at https://github.com/gatsbyjs/gatsby/issues/38117 to track this topic upstream in Gatsby.
@LekoArts please update the title so something that makes sense for the Gatsby Repo. Let me know it the ticket over there needs more information that is not present in this thread.

Hey @rileybathurst 🙂 Did you remove your .cache folder after applying the patch?

Yeah I used the gatsby clean and keep getting the error

@tinque I confirm that the proposed PR doesn't work, using: gatsby 5.8.1, gatsby-source-strapi 3.2.0. Still getting the same error message "The node type "File" is owned by "gatsby-source-filesystem"", even after running gatsby clean.

In node_modules/gatsby-source-strapi/dist/gatsby-node.js, if you remove the internal type check of "File" in the below line (line 57):
const existingNodes = getNodes().filter(n => n.internal.owner === gatsby-source-strapi || n.internal.type === "File");
And then remove the touchNode on line 78 of download-media-files.js and return the fileNodeID when cached (see below taken from lines 76-80), then both pieces will work.
    fileNodeID = cacheMediaData.fileNodeID;
    //touchNode(getNode(fileNodeID));
	return fileNodeID;
  }```

has anyone tried @solvticians-be 's answer?

@orkunzozturk I confirm that @solvticians-be 's change appears to be working.

Not trying to hijack the thread, but I have noted this same issue with the Directus source plugin for gatsby.
The same error and issue, while reverting to gatsby 5.8 and gatsby-source-filesystem 5.8 things work again.
https://github.com/directus/gatsby-source-directus/issues/25

Not trying to hijack the thread, but I have noted this same issue with the Directus source plugin for gatsby.
The same error and issue, while reverting to gatsby 5.8 and gatsby-source-filesystem 5.8 things work again.
https://github.com/directus/gatsby-source-directus/issues/25

Hence @LekoArts is saying they need to fix a bug in Gatsby. 😄

Not trying to hijack the thread, but I have noted this same issue with the Directus source plugin for gatsby.
The same error and issue, while reverting to gatsby 5.8 and gatsby-source-filesystem 5.8 things work again.
directus/gatsby-source-directus#25

Hence @LekoArts is saying they need to fix a bug in Gatsby. smile

Indeed, merely adding further context to the issue.

I fixed it by moving resolve 'gatsby-source-strapi' above the gatsby-source-filesystem and then ran the gatsby clean command.

I fixed it by moving resolve 'gatsby-source-strapi' above the gatsby-source-filesystem and then ran the gatsby clean command.

can you send a screenshot with package.json?

Also having this issue, moved gatsby-source-strapi to top of plugins, ran gatsby clean multiple times, and manually deleted the .cache directory, still no dice. Attached are screenshots of my package.json and gatsby-config.ts.
![Screenshot from 2023-05-31 13-29-36](https://github.com/gatsby-uc/plugins/assets/122010931/620b43a6-53d9-4311-

9119-9bd560dfa77b)

Rolling back to gatsby ~5.8.0 fixes it for me.


DefaultEndpointNameFormatter prefix and includeNamespace has not effect for generic types

Is this a bug report?
Yes

Can you also reproduce the problem with the latest version?
Yes
Environment

Operating system: Linux
Visual Studio version: Jetbrains Rider
Dotnet version: core 3.1

Steps to Reproduce

Use DefaultEndpointNameFormatter for generic Consumer or Message type
Expected Behavior

_prefix and _includeNamespace has effect for GetConsumerName, _includeNamespace has effect for GetMessageName when type has generic argument
Actual Behavior

GetConsumerName and GetMessageName just returns the short name of the generic type
Reproducible Demo

Hi @phatboyg this issue is still not fixed for at least GetMessageName method of DefaultEndpointNameFormatter:

I must set message type wrapped into any generic type to get queue name with prefix.


Minor: Update release schedule in README

Which issue does this PR close?
Related to https://github.com/apache/arrow-rs/issues/6016
Rationale for this change
Update the calendar with the anticipated release schedule so downstream crates can plan
What changes are included in this PR?
Update README with release schedule
Are there any user-facing changes?
Just docs

Thanks @tustvold


Numba and sparse arrays

My branch: https://github.com/pygae/clifford/tree/hugo/performance
Contains some ideas about how to improve performance with minimal effort, I haven't tested it with any large pieces of code but it is significantly faster at simple geometric products  in 5d cga.
Basically it uses the multiplication tables to generate functions using the sparseness

def get_mult_function(mult_table):
    '''
    Returns a function that implements the mult_table on two input multivectors
    '''
    non_zero_indices = mult_table.nonzero()
    k_list = non_zero_indices[0]
    l_list = non_zero_indices[1]
    m_list = non_zero_indices[2]
    mult_table_vals = np.array([mult_table[k,l,m] for k,l,m in np.transpose(non_zero_indices)],dtype=int)

    @numba.njit
    def gmt_mult(value,other_value):
        output = np.zeros(32)
        for ind,k in enumerate(k_list):
            l = l_list[ind]
            m = m_list[ind]
            output[l] += value[k]*mult_table_vals[ind]*other_value[m]
        return output
    return gmt_mult

Is this the kind of generator style code you were thinking of @moble ?
Also do you happen to have any ideas on further optimisations/improvements? I'm fairly new to the world of numba etc

Probably worth linking this in here https://github.com/arsenovic/clifford/issues/10

@hugohadfield , to put this issue into context. currently clifford is too slow for you. you might show this with a profiler, then you will know if/when you have solved your problem.
there were  three solutions mentioned (i think)  to improve performance:

improve matrix ops
refactor MV's to use bitmap reprs
use pyversor as a backend.

what order speedup  is expected from each, and what are pro's and con's? as @chrisjldoran, mentioned the matrix repr is known to be sub-optimal. this fact is also elaborated on in part III of Dorst's book.  so, improving matrix ops only makes sense to me if you want to make it work as soon as possible, and you only need a moderate speedup. from @moble notebook, the different matrices ops where only ~20% different.

Apologies, I really did not give much context for this.
To asses the performance of this library and to learn conformal GA I have been playing around with a variety of toy problems. One of these is a planar 3d cga version of the radon transform. It is not very well coded but serves as a nice model for the type of problem someone new to field might think of coding up.
The notebook https://gist.github.com/hugohadfield/4b0718c4d7662dec8d71cf76d2d499c6 contains the code and a profile output (sorry about the formatting, I couldn't work out how to make it nicer) of the program. The main thing to note is that of the 54.058 seconds that it ran for, it spent 47.189 in the mul method and 38.159 in numpy.core.multiarray.dot .
I therefore decided to dive into the mul method to see what might be done in the short term to improve it.

improving matrix ops
As @moble notebook shows it is possible to get small improvements from using the @ operator.
refactor MV's to use bitmap reprs as L Dorst etc suggest. This likely requires writing a fair amount of code but is likely to give big improvements.
use pyversor as a backend. Again likely to involve a fair amount of code/adds big dependencies.
use a code generator to roll custom functions for each layout. Requires writing/supporting a code generator.
@moble suggested writing a pure python based generator implementation that can be jitted and is super fast. This again is likely to require a fair amount of code.

I decided to go for a quick hybrid of 1, 4 and 5. The above function generator uses the sparsity of the existing multiplication table matrix to generate a function that directly multiplies the multivector value arrays, this is then stored with the layout. The aim of using numba is that it can optimise the partial completion of these functions quite nicely and give big speed ups.
This notebook shows the original speed of the multiplication functions https://gist.github.com/hugohadfield/0ec15132f892fbac60b4594155547a36
This one shows the improved speed:
https://gist.github.com/hugohadfield/d5ef2bc3fe2c3d8c32d7e8b32de4c0cd
Overall we are looking at around a 65.9/14.7 = 4.48 ~= 4.5 times speedup for 5d GAs. Its not amazing but not awful for a first shot either.
Reprofileling our original radon transform https://gist.github.com/hugohadfield/fa963c93dc9633d74659203d3700314c
we now see that it runs in 19.056 seconds
spending 11.805 of those in mul
and only  2.198 in gmt_mult
My conclusion, in the short term (assuming that the behaviour of this implmentation is identical, will require more testing) this prevents the matrix product operations being the bottleneck, it is now other inefficiencies in the code.

This looks good.  I didn't realize just how sparse these multiplication tables are, but looking at them in this case I find these sparsities:
lcmt: 0.74%
omt:  0.74%
imt:  1.19%
gmt:  3.13%

That's pretty substantial, alright, so it makes a lot of sense that these should speed up substantially with your new treatment.
I have one suggestion for your *performance.ipynb notebooks.  When you have a cell like
%%timeit
cf.MultiVector(layout,value=np.random.rand(n_dims))*cf.MultiVector(layout,value=np.random.rand(n_dims))

The timing it outputs includes the time taken to allocate and populate the rand arrays, and construct the multivectors from them, which you presumably don't care about.  The %%timeit magic allows for setup code that doesn't get included in the timing.  You just include it on the same line as the magic.  So I suggest doing something like
def setup(n_dims):
    a = cf.MultiVector(layout,value=np.random.rand(n_dims))
    b = cf.MultiVector(layout,value=np.random.rand(n_dims))
    return (a, b)

and then
%%timeit a,b = setup(n_dims)
a*b

On my computer those two constructions take 5 microseconds.  If I subtract that from each of your numbers, you got a speedup of 60.9/9.7 ~= 6.3 times.  Even better!
The only other optimization I can think of would be using the "sparsity" of the input to restrict the range of sums you have to do over each index of the *mt arrays.  For example, if you multiply two vectors, you're looping over a lot of terms that are only relevant for objects of other grades.  But unless you're mostly multiplying just vectors or bivectors, I kind of don't expect that to have a big effect.  And the complexity of coding up subclasses at this point is probably just not worth it.

@hugohadfield: I think this:
mult_table_vals = np.array([mult_table[k,l,m] for k,l,m in np.transpose(non_zero_indices)],dtype=int)

Can be written more efficiently as
mult_table_vals = mult_table[non_zero_indices]

@moble thanks for the notebook tips, I just added in some jitting of the layout comparison too and it gives some improvement, now at 60.9/5.86=10.4 times faster and probably at the end of the easy wins...
https://gist.github.com/hugohadfield/c3d044c1aeb0d9922e4da690151c0611
On my radon transform
18946259 function calls (18892445 primitive calls) in 15.071 seconds
Ordered by: cumulative time
ncalls  tottime  percall  cumtime  percall filename:lineno(function)
1    0.000    0.000   15.071   15.071 {built-in method builtins.exec}
1    0.032    0.032   15.071   15.071 :4()
800    0.002    0.000   14.186    0.018 :153(planar_radon_transform)
800    0.387    0.000    9.127    0.011 :32(intersect_spheres_and_plane)
821216    1.630    0.000    8.557    0.000 init.py:747(mul)
204000    0.428    0.000    6.451    0.000 :16(MeetSpheres)
800    0.081    0.000    4.958    0.006 :161()
204000    0.402    0.000    4.877    0.000 :19(generate_sphere_from_dual)
1237895    0.814    0.000    4.537    0.000 init.py:713(_checkOther)
1444774    0.611    0.000    2.204    0.000 init.py:736(_newMV)
821221    2.090    0.000    2.090    0.000 init.py:210(mv_mult)
2792189    0.553    0.000    1.962    0.000 {built-in method builtins.isinstance}
1029158    0.337    0.000    1.818    0.000 init.py:371(ne)
204000    1.395    0.000    1.782    0.000 init.py:1165(call)
1444774    0.881    0.000    1.593    0.000 init.py:673(init)
1029158    1.141    0.000    1.481    0.000 init.py:367(eq)
204001    0.290    0.000    1.435    0.000 init.py:843(sub)
1242911    0.843    0.000    1.409    0.000 abc.py:178(instancecheck)
206403    0.460    0.000    1.024    0.000 init.py:763(rmul)
1447970    0.716    0.000    0.716    0.000 {built-in method numpy.core.multiarray.array}
6    0.000    0.000    0.605    0.101 dispatcher.py:294(_compile_for_args)
6    0.000    0.000    0.605    0.101 dispatcher.py:554(compile)
6    0.000    0.000    0.604    0.101 dispatcher.py:70(compile)


Bug in saving/retrieving gold standard cache on Windows

First, let's write a test to see if binary entries can be written and read correctly.

One must use ios :: binary to ensure that streams are opened in the binary mode.


Review the database fields length

The name field has 50 characters, to integrate with Auth0 and store in it a "firstName + lastName" the field needs to be increased.

@mihaidma Auth0 doesn't have firstName & lastName fields, they're probably store in user_metadata. So the question to what number to increase it is quite difficult since anyone can come up with a number higher than what you propose to suite her needs.
Just an observation... My opinion is that the name field should be dropped altogether and i'm pretty sure @p16 agrees with me :D

for a first+last name an 126 will do and will be categorized as short string, but 255 is fine with me:
The storage requirement for a short string (up to 126 bytes) is 1 byte plus the actual string, which includes the space padding in the case of character. Longer strings have 4 bytes of overhead instead of 1. Long strings are compressed by the system automatically, so the physical requirement on disk might be less. Very long values are also stored in background tables so that they do not interfere with rapid access to shorter column values.
I agree that the name field is kind of useless and could be removed.


MQTT LWT Support

Closes #117
Add config options for the Generic MQTT integration to register an LWT message with the broker.
I used the SetWill function with a string payload rather than the SetBinaryWill as suggested in the original issue as I figured it would be more useful for the majority of users (who would probably just want to send some JSON or something anyway), and easier to use than having to configure a byte array in the config file.

Rebased onto current master (post-rename) and forced pushed.

I'm closing this issue. I believe https://www.chirpstack.io/gateway-bridge/changelog/#v3110 does cover the use-case with the connection-state message, which uses both LWT and the state of the [GW] > [GW Bridge] connection.


How to see latest images first?

How can I get to see my latest images first or scroll to the last image and then if I want to see old images I can swipe down to see as in Default ImagePickerController?

Can you say more about that scenario?

Looks like, it already is providing latest images.


Error 5 when reading data from Disc

Have tried multiple times to dump multiple game discs but keep getting error 5.
Am dumping to an SD Card recently formatted to FAT32.
Was able to dump digital game no problem, but discs are not working.
Am using the dumplingapp.com exploit.
Have tried having disc in on start-up and also inserting disc during dumpling running, both give same result. Always Error 5.

Unfortunately error 5 is an error that the Wii U gives dumpling when it can't read any further on the disc. There's not really any I can work around the error.

Is it my Wii U at fault then? It reads and plays the games fine still.

Anything I can do to fix the issue too? I'm using the exploit rather than having a soft modded Wii U

Yeah, sorry. I was wrong initially and I thought this was just a scratchy disc. I've been busy finding a fix for this issue for a bit, will let you know when it's released.


(PUP-4527) merge 4527 from 3.x and fix up earlier merge mistakes

This merges the implementation of PUP 4527 into stable (from 3x) and provides fix up of earlier merges that added back calls to the migration checker (from PUP 4127).
A safety mechanism is added (raising errors) if any of the methods that should not be called in the migration checker is called by mistake.

CLA signed by all contributors.


Perform Gradle builds using the Gradle wrapper script

Run "gradle wrapper" using the installation of Gradle located on the host
in an initial build where no gradlew script is present.  Use gradlew for
subsequent builds.
See https://github.com/flutter/flutter/issues/9842

@jakobr-google @mit-mit

What's the status of this PR?

cc @mravn-google

It's now owned by me. I'll self-assign once I start working on it.

There has been some discussion on this, see https://github.com/flutter/flutter/pull/9882.

@jason-simmons This does not appear to solve our current Gradle versioning problems. If I run gradle wrapper in the android folder of a newly created Flutter project, Gradle needs to be able to interpret my build.gradle file which is written for a particular version of Gradle. In my case, since I have Gradle 4.0 installed, it fails with
$ gradle wrapper
Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/mravn/apps/hej/android/build.gradle' line: 20

* What went wrong:
A problem occurred evaluating root project 'android'.
> A problem occurred configuring project ':app'.
   > Failed to notify project evaluation listener.
      > com.android.build.gradle.tasks.factory.AndroidJavaCompile.setDependencyCacheDir(Ljava/io/File;)V

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED in 7s

What we need, I think, is for the Gradle wrapper to be present in the correct version in our template, as already suggested in #9882.
Adding gradle-wrapper.jar to our template would just be following standard practice, even though it is a binary. GitHub itself appears to have embraced this practice, having published a standard .gitignore file that un-ignores gradle-wrapper.jar.
I'm looking into our reasons for not accepting #9882, such as licensing issues.


Add estimDate property, fix deliveryDate v2

Thanks @tucoinfo , added some check to your code before merging ;) .


[XR Editor] Update the set of excluded permissions

A few permissions including the USE_SCENE permission are being renamed with the launch of the Meta Spatial SDK, so we update the excluded list to avoid requesting them on app start.

Thanks!


SpatialUnderstanding fails to extract the first mesh of any room model

Overview
If you run the SpatialUnderstandingExample scene in the Editor the SpatialMappingManager uses a room model as the spatial source. The room model files contain separate meshes, for example default_MeshPart0, default_MeshPart1 and default_MeshPart2. This issue applies to all room models in the MixedRealityToolkit: FakeSpatialMappingMesh, MediumRoomWithHomeFurniture and SRMesh.
Expected Behavior
All room meshes should be consumed by the SpatialMappingManager and processed by the SpatialUnderstanding scripts to create and render corresponding playspace meshes.
Actual Behavior
The SpatialMappingManager consumes the separate meshes and creates corresponding GameObjects in the scene. The first one (always called roomMesh-0) is never extracted correctly by the SpatialUnderstanding.dll. To be exact, the GeneratePlayspace_ExtractMesh_Setup(out int vertexCount, out int indexCount) function in SpatialUnderstandingCustomMesh.Import_UnderstandingMesh() returns 0 instead of 1 for this mesh. Therefore it is not rendered in the scene.
Steps to reproduce
Just open and play the SpatialUnderstandingExample scene in the Unity Editor and try every single room model. A corresponding playspace mesh for roomModel-0 is never generated.
Unity Editor Version
2017.1.2p1
Mixed Reality Toolkit Release Version
HoloToolkit-Unity-v1.2017.1.2
HoloToolkit-Unity-Examples-v1.2017.1.2

Closing issues older than 180 days. If this is still an issue, please reactivate with recent information.


Cleans the directory prior to a new building being published

This fixes issue #11 to ensure that prior to doing a publish we have a clean build directory and we don't pull in any extra files.

Great!


Rich text first link

Q
A

Bug fix?
[X]

New feature?
[ ]

New sample?
[ ]

Related issues?
fixes #672

What's in this Pull Request?

A hyperlink can be added at the beginning
An empty hyperlink is not allowed (added check)

Thank you @Abderahman88 for the fix!


run Gratipay 140

139

26 (20) accounts reviewed.

Droplet taking a long time to spin up again ...

Backup taken and verified.

Droplet spun up and updated.

Script started.

Script ran for 15 minutes (0:15:06.657959).

Pinned https://twitter.com/Gratipay/status/563372648823283712.

Log downloaded and droplet destroyed.

MassPay done and posted back for 83 users.

Escrow shuffled.

Logs uploaded in https://github.com/gratipay/logs/commit/d922b0b3ee8404699ed55cfe84e32aa5910ef43f.


Is passport.initialize() not needed?

Hi everyone,
I can't see passport.initialize() middleware being used in any part of the code. Could you help me understand if it's not needed to use anymore?

If im not wrong, its because we are already using
var authRouter = require('./routes/auth');
app.use('/', authRouter);

So we dont need to pass passport.initialize()

As of v0.5.1, passport.initialize() is no longer needed.  Details on the blog.


IANA TZs should resolve in a case-insensitive way

Hi. I found this promising project 15 minutes ago. I think a found a bug.
I think the library should resolve IANA time zones in a case insensitive way. The following unit tests show the problem.
[TestMethod]
public void TZDB_GetTimeZoneWithIanaId_EuropeParis_WrongCase_ShouldResolve()
{
    string input = "europe/paris";
    var result = TZDB.DB.GetTimeZoneWithIanaId(input);
    Assert.IsNotNull(result);
    Assert.AreEqual("Romance Standard Time", result.MicrosoftId);

    // FAILED
    // threw exception:
    // System.Collections.Generic.KeyNotFoundException:
    // The given key was not present in the dictionary.
}

[TestMethod]
public void TZDB_GetTimeZoneWithIanaId_EuropeParis_ShouldResolve()
{
    string input = "Europe/Paris";
    var result = TZDB.DB.GetTimeZoneWithIanaId(input);
    Assert.IsNotNull(result);
    Assert.AreEqual("Romance Standard Time", result.MicrosoftId);
    // PASS
}

Am I wrong?

hmm. this is a tricky one. If we are taking the lead of for example, java 8, the current behavior of being case sensitive is consistent with that implementation.


'TVVLCKit/TVVLCKit.h' file not found

when i use<EMAIL_ADDRESS>and the project error reporting (in target 'react-native-vlc-media-player' from project 'Pods')
and Xcode reporting 'TVVLCKit/TVVLCKit.h' file not found
System environment：
macOS  13.2.1
Node.js v19.9.0
react-native 0.71.7
iPhone 14 Pro Max  iOS 16.4

Should be fixed with https://github.com/razorRun/react-native-vlc-media-player/pull/154

thanks for you job


When you start a new GitHub sign in flow while in a sign in flow already you get this notification

It shouldn't be shown because it's not important.

Verification steps:

Sign out of GitHub if you're signed in in VS Code
Start but don't hit Continue in the sign in flow for GH PR extension
start and do hit Continue in the sign in flow for GitHub issues extension (or Settings Sync or GitLens)
Now hit Continue on the other tab that opened (for GH PR extension)

You should be logged in to everything and you don't get the notification above.


useUserPassFlow property not working

As detailed in Zendesk ticket #4007, we define property useUserPassFlow, but check userPassFlow.
The correction is to be implemented in OAuth2Feature.java and TestOAuth2Feature.java.

done with #90


"unresolved import" and other errors with bindgen on remote workspaces

I'm using bindgen and cbindgen in unison to create C->Rust->C bindings for our project so we can start using Rust. I finally got the build happy and everything works, but in VSCode I'm getting "unresolved import" errors in my Rust files for all imports coming from bindgen. For example, the line use crate::bindings::foo; claims that foo is unresolved.
Similar to #6289 I'm using an include! macro to bring in stuff from bindgen:
include!(concat!(env!("OUT_DIR"), "/rust_bindgen.rs"));

From that issue I tried enabling the correct extension settings:
...
        "[rust]": {"editor.formatOnSave": true},
        "rust-analyzer.linkedProjects": [
            "/depot/project/rust/Cargo.toml"
        ],
        "rust-analyzer.cargo.loadOutDirsFromCheck": true,
        "rust-analyzer.procMacro.enable": true,
        "rust-analyzer.debug.engine": "ms-vscode.cpptools",
        "rust-analyzer.debug.openDebugPane": true,
        "rust-analyzer.rustfmt.extraArgs": ["--config-path", "/depot/build/rustfmt.toml"],
...

But the issue persists. I'm running VSCode attached to a Container running on a remote host (using the VSCode Remote Container extenion). I'm getting the following panic from Rust Analyzer Language Server log:
thread 'main' panicked at 'internal error: entered unreachable code', crates/proc_macro_srv/src/proc_macro/bridge/mod.rs:256:5
stack backtrace:
   0: std::panicking::begin_panic
   1: <proc_macro_srv::proc_macro::bridge::api_tags::Method as proc_macro_srv::proc_macro::bridge::rpc::DecodeMut<S>>::decode
   2: <proc_macro_srv::proc_macro::bridge::server::Dispatcher<proc_macro_srv::proc_macro::bridge::server::MarkedTypes<S>> as proc_macro_srv::proc_macro::bridge::server::DispatcherTrait>::dispatch
   3: <proc_macro_srv::proc_macro::bridge::closure::Closure<A,R> as core::convert::From<&mut F>>::from::call
   4: proc_macro::bridge::scoped_cell::ScopedCell<T>::replace
   5: std::thread::local::LocalKey<T>::with
   6: <proc_macro2::imp::TokenStream as core::iter::traits::collect::IntoIterator>::into_iter
             at /home/dan/.cargo/registry/src/github.com-1ecc6299db9ec823/proc-macro2-1.0.24/src/wrapper.rs:292
   7: proc_macro2::token_stream::<impl core::iter::traits::collect::IntoIterator for proc_macro2::TokenStream>::into_iter
             at /home/dan/.cargo/registry/src/github.com-1ecc6299db9ec823/proc-macro2-1.0.24/src/lib.rs:1229
   8: syn::buffer::TokenBuffer::inner_new
             at /home/dan/.cargo/registry/src/github.com-1ecc6299db9ec823/syn-1.0.54/src/buffer.rs:53
   9: syn::buffer::TokenBuffer::new2
             at /home/dan/.cargo/registry/src/github.com-1ecc6299db9ec823/syn-1.0.54/src/buffer.rs:112
  10: <F as syn::parse::Parser>::parse2
             at /home/dan/.cargo/registry/src/github.com-1ecc6299db9ec823/syn-1.0.54/src/parse.rs:1207
  11: syn::parse::Parser::parse
             at /home/dan/.cargo/registry/src/github.com-1ecc6299db9ec823/syn-1.0.54/src/parse.rs:1161
  12: syn::parse_macro_input::parse
             at /home/dan/.cargo/registry/src/github.com-1ecc6299db9ec823/syn-1.0.54/src/parse_macro_input.rs:139
  13: serde_derive::derive_deserialize
             at /home/dan/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_derive-1.0.118/src/lib.rs:89
  14: core::ops::function::FnOnce::call_once
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libcore/ops/function.rs:232
  15: proc_macro::bridge::client::Client<fn(proc_macro::TokenStream) .> proc_macro::TokenStream>::expand1::run::{{closure}}
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libproc_macro/bridge/client.rs:394
  16: proc_macro::bridge::client::run_client::{{closure}}::{{closure}}
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libproc_macro/bridge/client.rs:362
  17: proc_macro::bridge::scoped_cell::ScopedCell<T>::set::{{closure}}
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libproc_macro/bridge/scoped_cell.rs:79
  18: proc_macro::bridge::scoped_cell::ScopedCell<T>::replace
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libproc_macro/bridge/scoped_cell.rs:74
  19: proc_macro::bridge::scoped_cell::ScopedCell<T>::set
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libproc_macro/bridge/scoped_cell.rs:79
  20: proc_macro::bridge::client::<impl proc_macro::bridge::Bridge>::enter::{{closure}}
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libproc_macro/bridge/client.rs:310
  21: std::thread::local::LocalKey<T>::try_with
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libstd/thread/local.rs:262
  22: std::thread::local::LocalKey<T>::with
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libstd/thread/local.rs:239
  23: proc_macro::bridge::client::<impl proc_macro::bridge::Bridge>::enter
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libproc_macro/bridge/client.rs:310
  24: proc_macro::bridge::client::run_client::{{closure}}
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libproc_macro/bridge/client.rs:355
  25: <std::panic::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libstd/panic.rs:318
  26: std::panicking::try::do_call
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libstd/panicking.rs:292
  27: __rust_maybe_catch_panic
  28: std::panicking::try
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libstd/panicking.rs:270
  29: std::panic::catch_unwind
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libstd/panic.rs:394
  30: proc_macro::bridge::client::run_client
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libproc_macro/bridge/client.rs:354
  31: proc_macro::bridge::client::Client<fn(proc_macro::TokenStream) .> proc_macro::TokenStream>::expand1::run
             at /var/tmp/portage/dev-lang/rust-1.41.1/work/rustc-1.41.1-src/src/libproc_macro/bridge/client.rs:394
  32: proc_macro_srv::proc_macro::bridge::server::run_server
  33: proc_macro_srv::dylib::Expander::expand
  34: proc_macro_srv::cli::run
  35: rust_analyzer::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
fatal runtime error: Rust panics must be rethrown
[ERROR proc_macro_api::process] proc macro server crashed, server process state: Ok(Some(ExitStatus(ExitStatus(134))))

I tried to create a minimal repro at https://github.com/dfarley1/rust_foo.
First I tried the repro locally, where the imports appear to resolve. For example hovering over (*foo).bar on foo.rs:6 correctly shows that bar is a c_int, but "go to definition" (ctrl+click) on crate::bindings::foo gets me the following panic from Rust Analyzer Language Server log:
Panic context:
> request: textDocument/hover HoverParams {
    text_document_position_params: TextDocumentPositionParams {
        text_document: TextDocumentIdentifier {
            uri: Url {
                scheme: "file",
                host: None,
                port: None,
                path: "/home/dan/rust_foo/rust/src/protocols/foo.rs",
                query: None,
                fragment: None,
            },
        },
        position: Position {
            line: 0,
            character: 22,
        },
    },
    work_done_progress_params: WorkDoneProgressParams {
        work_done_token: None,
    },
}

thread '<unnamed>' panicked at 'assertion failed: `(left == right)`
  left: `HirFileId(MacroFile(MacroFile { macro_call_id: EagerMacro(EagerMacroId(13)) }))`,
 right: `HirFileId(FileId(FileId(870)))`', crates/hir_expand/src/lib.rs:467:9
stack backtrace:
   0: rust_begin_unwind
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:483
   1: std::panicking::begin_panic_fmt
             at /rustc/7eac88abb2e57e752f3302f02be5f3ce3d7adfb4/library/std/src/panicking.rs:437
   2: hir_expand::InFile<&rowan::api::SyntaxNode<syntax::syntax_node::RustLanguage>>::original_file_range
   3: ide::display::navigation_target::NavigationTarget::from_named
   4: <D as ide::display::navigation_target::ToNav>::to_nav
   5: ide::hover::hover
   6: std::panicking::try
   7: ide::Analysis::hover
   8: rust_analyzer::handlers::handle_hover
   9: <F as threadpool::FnBox>::call_box
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I copied the repo to my remote container to see what happens there and I get the same error as in my actual project: "unresolved import" on crate::bindings::foo and 'internal error: entered unreachable code', crates/proc_macro_srv/src/proc_macro/bridge/mod.rs:256:5.
I've tried blowing away target directory in both environments as well as the entire /home/dan/.vscode-server in the container and restarting VSCode to make sure I'm not caching bad stuff. I'm using VSCode v1.52.0, rust-analyzer v0.2.416, and download whatever the latest language server is whenever VSCode prompts me to.

@dfarley1 I found that from your log , you are using rustc-1.41.1, right now we only support the latest stable version of rust, would you mind to try to update it and see if the problem is gone away ?
And it will be nice to use nightly of rust-analyzer since we did fix some bugs related to proc-macro recently. (or waiting for next release in coming monday)

I updated to Rust v1.48 and the nightly Rust Analyzer. I'm experiencing the same issues except I'm not getting any logs from Rust Analyzer Language Server or the Trace (I guess I don't have it enabled though), just unresolved imports.

It seem to be fixed, feel free to reopen it if needed.


Update source-ip.md

add en content and some updates

@jiaj12 still working on this?

/close
No response from author for over 1 month.


Removing external url on navigation and query actions.

Remove external calls on third party websites.

Changes Unknown when pulling 06cd970b8a4dfd8ca5481c98f6ed22e717d570dd on ranch:test/remove-external-url into ** on knq:master**.

Changes Unknown when pulling 85fc570d05d8fefbd29745e1d2f12464dcd6c6b5 on ranch:test/remove-external-url into ** on knq:master**.


[Automation] Generate Fluent Lite from Swagger advisor#package-2020-01

[Automation] Generate Fluent Lite from Swagger advisor#package-2020-01

/azp run java - advisor - ci

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure.resourcemanager:azure-resourcemanager-advisor


Regression - opening more than 1 .sql script not working correctly

Hello,
It looks like there is some issues with tab when we open more than 1 script (.sql files).
I remember that it works fine before, but I cannot say when this regression starts.
The problem is arround openning vs connecting .sql scripts:

tabs tabs overwrites each other
tabs always display "Disconnected"

I can see the is an open ticket #228, but i'm not sure this is the same issue.

I hope this can help to fix the problem.
Regards

UPDATE
The new ADS version seems to fix the bug:
Version: 1.48.0 (system setup)
Commit:<PHONE_NUMBER>ef8254b7c22a5dc55af7f8a1dea93f
Date: 2024-02-27T00:05:08.293Z
VS Code: 1.82.0
Electron: 25.9.8
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
I close the issue.


fix failing jtreg build job

fixes: https://github.com/adoptium/temurin-build/issues/2697

Were you able to manually test this?

Were you able to manually test this?

Yeah I've confirmed that this fixes the failure

PMC approved.  We may need the latest jtreg for 17 release debug


App keeps forgetting settings in v0.0.6 and latest git/v0.0.7

Hey I noticed in v0.0.6 that immediately after I close the app and open it back up, it completely forgets what mods I had installed. It seems to completely ignore the SelectedMods list in the AppSettings json file while it reads all of the other options in the file. Odd thing is too is that it will save the options but as soon as I open the app back up, it just resets the mods selected and only has BSIPA selected with none of my other previously selected options. To prove the point further, I even tried to see if removing BSIPA from the AppSettings file would make a difference (to make it look like as if I selected none) and upon the next restart of the app, BSIPA was selected again. Tried with both the prepackage binary (BeatSaberModManager-linux-x64.zip) and upcoming nixpkgs update PR (which I downloaded and had to modify to get it to compile since there's a issue with the PR build's build options). The issue isn't present on 0.0.5.
Edit: Also tried it against the current git revision (8bf3611a8b33c95e7a0340504894cf7b46822107), and the bug is still present there too
(This I found out was because the commit that updated Program.cs wasn't tagged along with v0.0.6, so this is specifically in the source builds and not in the prepackaged binary) Another bug I notice is that the version number isn't correct in the Source files (which I notice that the source files weren't updated but the pre-packaged binary was)

System Information:
 - system: `"x86_64-linux"`
 - host os: `Linux 6.11.7, NixOS, 24.11 (Vicuna), 24.11.20241111.3f42f0b`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.23.4`
 - nixpkgs: `/nix/store/cwj8vq6zrah0qw21czisvha98lg367m0-aj5384f4ax3fg64zkxrw0b7daka0dxfr-source`

I'm not a C developer but I suspect this change here is what caused the breakage:
https://github.com/affederaffe/BeatSaberModManager/commit/0eadaee43ece5bf2635548acf26c4c2556183a4c#diff-f4e60960f750d743832012f2a0348f86d2e70cfe73cc1cd10a1b86195b13f600L50-L55

This bug is quite critical and I therefore decided to block https://github.com/NixOS/nixpkgs/pull/339370.

 (Oh how wise they are, they know so much better than us...)
We'll have to refactor it so that external users have simple methods to interact with this object or just expose the object directly and init it as an empty set. I also don't get why this two member variables that do the same thing complexity needs to exist in the first place.


Filter repositories with no name at Data providers page

Hot fix to prevent infinite loading of repositories on Data providers page.
Changes:

improved sort comparator to avoid comparing nulls
filtered repositories with no name (name: null)

Shouldn't the repository with name "name" be discarded as well?

@mcancellieri good point! Thank you for the remark. I am on it

I added the filter. However, it looks really bad. It's less than thousand but looks like a thousand and it's really bad.

ok now i understand better, thank you


[sigh] fix resign of nested apps

Fix a bug introduced with: https://github.com/fastlane/fastlane/pull/7004
as reported here: https://github.com/fastlane/fastlane/issues/7155

there was a another PR - i like the one more as it features a spec https://github.com/fastlane/fastlane/pull/7154


Lookback query

Please review these changes.  The lookback query is an exciting new feature that we've been using for a while at my company.
It supports a cohort from a query or dataSource useful for trend analysis between Periods.
Example:
Data:
[ (T-1, 1), (T-2, 2), (T-3, 3) ]
Possible cohort:
T-1 join T-2 = 1,2
T-2 join T-3 = 2,3
T-3 join _ = 3,null
Example query and results are in the attached documentation.

@a2l007 Please add refactor the movingAverage/rollingAverage when that is accepted separately.
Will Sketches supported?

@michael-trelinski thank you for your contribution! Would you please write a proposal for this PR? Here is the link: https://github.com/apache/incubator-druid/issues/new/choose.

@michael-trelinski thank you for your contribution! Would you please write a proposal for this PR? Here is the link: https://github.com/apache/incubator-druid/issues/new/choose.

Should I add this as a Feature/Change or a Proposal?  I can see merits for both.
Also, IntelliJ lied to me and the unit tests were broken, so I pushed another commit, which hopefully fixes it.

I think Feature/Change label is for asking some new features or changes of existing features to the community. So, it is more about what is needed and why. Proposal is Feature/Change + how to implement and rationale about its design.
I think Proposal is more proper for your case.


SW-1903 Show bagIds on View accession

The top row is starting to look so busy,, and uneven. Why this design? Why isn't this in the details section? We stick the plant ids in the details.

The top row is starting to look so busy,, and uneven. Why this design? Why isn't this in the details section? We stick the plant ids in the details.

Is the design specified the bug https://terraformation.atlassian.net/browse/SW-1903

The top row is starting to look so busy,, and uneven. Why this design? Why isn't this in the details section? We stick the plant ids in the details.

Is the design specified the bug https://terraformation.atlassian.net/browse/SW-1903

Yes, I understand that :) was just commenting on the decisions involved.
Looks like maybe we need less width for the edit icon on desktop (and spacefillers)? so the spacing across top row elements are even?

The top row is starting to look so busy,, and uneven. Why this design? Why isn't this in the details section? We stick the plant ids in the details.

Is the design specified the bug https://terraformation.atlassian.net/browse/SW-1903

Yes, I understand that :) was just commenting on the decisions involved. Looks like maybe we need less width for the edit icon on desktop (and spacefillers)? so the spacing across top row elements are even?

New spacings:

Thanks 🎉 Do you have a screenshot example for a long list of Bag IDs? just a sanity check...


Add support for Yandex Lockbox

Issue: #308
This is the implementation itself. We have tested it manually and it looks like it is pretty workable.
I am also going to add some tests and documentation soon.
However just to ensure I am heading in the right direction could you please take a brief look at the code?

Hey @AndreyZamyslov! Thanks for the PR!
I also want to do some manual tests with lockbox to accompany my review here. I created an account there and I am waiting for Lockbox to be available on my free trial. A quick look over code tells me that you are going in the right direction.

When I have access to it I will give a bit more feedback here :)

@knelasever We used the instructions below for testing.
Hope this helps :)
Prerequisites

Yandex.Cloud CLI installed: https://cloud.yandex.com/en-ru/docs/cli/quickstart
Create k8s namespace ns1:
kubectl create namespace ns1
Create lockbox secret es1:
yc lockbox secret create --name es1 --payload '[{"key": "password","textValue": "p@$$w0rd#1"}]'
Run the External Secret Operator (for example, via make run)

Steps

Create service account sa1 giving the access to lockbox secret es1:

yc iam service-account create --name sa1
yc lockbox secret add-access-binding --name es1 --service-account-name sa1 --role lockbox.payloadViewer
yc lockbox secret list-access-bindings --name es1 # just to ensure the correct access binding has been added
yc iam key create --service-account-name sa1 --output key1.json # write the created authorized key to key1.json file

Create k8s secret yc and put the authorized key there:

kubectl --namespace ns1 create secret generic yc --from-file=authorized-key=key1.json

Create SecretStore object:

kubectl --namespace ns1 apply -f - <<< '
apiVersion: external-secrets.io/v1alpha1
kind: SecretStore
metadata:
  name: ss
spec:
  provider:
    yandexlockbox:
      auth:
        authorizedKeySecretRef:
          name: yc
          key: authorized-key
'

Create ExternalSecret object:

kubectl --namespace ns1 apply -f - <<< '
apiVersion: external-secrets.io/v1alpha1
kind: ExternalSecret
metadata:
  name: es1
spec:
  secretStoreRef:
    name: ss
    kind: SecretStore
  target:
    name: secret1
  data:
  - secretKey: password
    remoteRef:
      key: e6qlehp8d8j4c84tct65 # ID of lockbox secret es1
      property: password # (optional) payload entry key of lockbox secret es1
'

Result
k8s secret secret1 is accessible:
kubectl --namespace ns1 get secret secret1 -ojson | jq -r ."data"."password" | base64 -D

Awesome! It helped a lot. Since Lockbox always expects lockbox secrets to store key values (you cant just throw text directly), implementation and tests can go in the same direction as we have for Hashicorp vault (and you already went that way, which is perfect). I tested dataFrom behaviour, data without property and with property and everything seems fine. Templating seems fine as well.
Looking at the code, I am also pleased with what I see. :)
I am good with merging this when we have some tests :smile:

Added tests.
Documentation is on the way.

@knelasevero  I've added the docs.
But also I suddenly realized there is a problem with making requests to Lockbox in lockboxProvider :)
A new connection (via ycsdk.SDK instance) is created and closed for each secret refresh now instead of reusing one long-lived connection.
I want to add some more commits fixing this.

Thanks for adding docs!

But also I suddenly realized there is a problem with making requests to Lockbox in lockboxProvider :)
A new connection (via ycsdk.SDK instance) is created and closed for each secret refresh now instead of reusing one long-lived connection.

Do you mean that we close the connection and create a new client every time in the controller? That's intended, right?
Or do you mean something else?

@knelasevero I have added the changes I wanted and a bit more tests.
Could you please take another look at this? Are these changes good enough to be merged?

Do you mean that we close the connection and create a new client every time in the controller? That's intended, right?

Yes, I think that's ok in general.
But it was not a very good idea to create a new Yandex.Cloud SDK object for every NewClient() call in lockboxProvider. It was my bad and I've fixed it in the latest commit

I see that check-diff failed. But make check-diff passes if I run it locally.

Rebase with master and make generate. We got some changes on types and CRDs :)

/ok-to-test sha=ec7d3a3

/approve

Thanks @AndreyZamyslov ! Gonna merge soon!

Thanks @AndreyZamyslov ! Gonna merge soon!
That's awesome!

/merge

@knelasevero Thank you for your help! It was really pleasant contribution experience :)
Just one more question, how soon will the new version be released?

@AndreyZamyslov thanks for the feedback! Also thanks so much for the PR again :)
I have some important fixes to get out there, and they should get out asap, lockbox will go together with them. I would expect another release this week, latest next week

@knelasevero Great, thanks!


Broadcasting of matmul does not work with parallel

[x] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
[x] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

The following code snippet throws a TypingError error as-is, but it works perfectly fine if you deactivate 'parallel = True'. I have checked the online available resources as much as possible, did not find any hints on this. Sorry if it's a known missing feature!
import numpy as np
from numba import njit

k = 2
n = 3

alpha = np.random.rand(k, n, n)
N = np.random.rand(n, n)

@njit(
    parallel = True
)
def mul(alpha, N):
    return alpha*N

res = mul(alpha, N)

Thanks for the report. From https://numba.readthedocs.io/en/latest/user/parallel.html#supported-operations:

Multi-dimensional arrays are also supported for the above operations when operands have matching dimension and size. The full semantics of Numpy broadcast between arrays with mixed dimensionality or size is not supported, nor is the reduction across a selected dimension.

So I think this is a documented limitation.


To support Terraform v1.2.0 or above

Fixes: #252
Signed-off-by: Aishwarya Kamat<EMAIL_ADDRESS>

Let me update the job config to use the latest Terraform version.

Let me update the job config to use the latest Terraform version.

@yussufsh Sure. Thanks

/retest


Add delay_mechanism option to PTP domain

For setting delay_mechanism to P2P.

Thanks for your patch!
Could you add a test for this?  It doesn't have to be a new test file, perhaps an addition to an existing test in tests/tests_*.yml?

Sure, i can try. Is it possible to run the tests locally?

Sure, i can try. Is it possible to run the tests locally?

If you are using Fedora or CentOS or RHEL, see https://linux-system-roles.github.io/contribute.html
You'll need to install tox and tox-lsr.  And also standard-test-roles-inventory-qemu.  Your system should support KVM.
Download the config file from https://raw.githubusercontent.com/linux-system-roles/linux-system-roles.github.io/master/download/linux-system-roles.json to ~/.config/linux-system-roles.json
Then you can run the tests locally like this: tox -e qemu-ansible-core-2.12 -- --image-name centos-8 tests/tests_default.yml
Note that you may run into errors if you are using some other VMs on your system using some other hypervisor like virtualbox.
Check the artifacts/ directory - there are some log files there that may help debug problems.

any update?


Ficus hf variant

Purpose

Changes:

Pillar blocks are created each N pbft blocks
Pillar votes for pillar block N have period N+1
pbft block N+1 is not finalized unless we have also > 50% of pillar votes with period N+1

This change fixes:

potentially getting stalled due to missing pillar chain votes that would no longer be generated
asserts are not triggered anymore
the latest set of validators control pillar chain consensus

This change requires:

testnet reset
TaraClient contract change: https://github.com/Taraxa-project/bridge/blob/master/src/eth/TaraClient.sol#L105 - blocks[i].block.period + 1 should be used

evm pr https://github.com/Taraxa-project/taraxa-evm/pull/242
How does the solution address the problem

Changes made

/deploy

PR NET pr-2806 Successfully deployed!explorerhttps://explorer-pr-2806.prnet.taraxa.io  RPChttps://rpc-pr-2806.prnet.taraxa.io Indexerhttps://indexer-pr-2806.prnet.taraxa.io Boot NodesBoot Node <IP_ADDRESS>Boot Node <IP_ADDRESS>Boot Node 3<IP_ADDRESS> RPC NodesRPC Node <IP_ADDRESS>RPC Node <IP_ADDRESS>RPC Node 3<IP_ADDRESS>

/cleanup

prnet cleaned-up successfully

prnet cleaned-up successfully


Intermittent b2 errors (?) cause "pack ID does not match" errors during "restic check --read-data"

Output of restic version
restic 0.9.5 compiled with go1.12.4 on freebsd/amd64
How did you run restic exactly?
I have a few layers of scripts, but roughly:
export RESTIC_PASSWORD_FILE=...
export RESTIC_REPOSITORY=b2:...

SIZE=1000
for x in `seq 1 $SIZE`; do
  echo $x/$SIZE
  ./restic_0.9.5_freebsd_amd64 check --read-data-subset=$x/$SIZE
done

The output relevant to this issue is, e.g.:
18/1000
using temporary cache in /tmp/restic-check-cache-158036280
created new cache in /tmp/restic-check-cache-158036280
create exclusive lock for repository
load indexes
check all packs
check snapshots, trees and blobs
read group #18 of 2021 data packs (out of total 510823 packs in 1000 groups)
Pack ID does not match, want 11ec3b05, got f54a743e
[23:05] 100.00%  2021 / 2021 items

duration: 23:05
Fatal: repository contains errors

What backend/server/service did you use to store the repository?
b2
Expected behavior
restic should use check b2 full file downloads against the sha1 integrity information given by b2, retrying if necessary. This will help distinguish between transient errors and more serious errors.

Actual behavior
restic catches the transient corruption and reports "pack ID does not match".

Steps to reproduce the behavior
Due to the nature of the bug, there's really no way to reproduce this. I saw it happen with 5 pack files in a 2.5TB repository, so perhaps running check against a large enough b2 repo will eventually encounter it.

Do you have any idea what may have caused this?
Yes, after I had manually verified that the pack files had the correct sha256 sum (using the info from https://github.com/restic/restic/issues/2191 ), I dug into the b2 backend code and noticed that the b2 library it's using (blazer) already keeps track of sha1 info returned by b2 and exposes methods to check it, but the b2 backend doesn't use it.
Do you have an idea how to solve the issue?
Yes, I will send a PR with an initial solution.
Did restic help you or made you happy in any way?

restic is great otherwise! I've been very happy with it.

There are seems to be two independent issues/ideas here: a) use b2-specific file checksum and b) retry failed checksum validation.
As I mentioned in #2303, I am not in favour of b2-specific checksum validation as it seems redundant.
I am on the fence about retries. On one hand I agree it makes sense to retry failed checksum validation during restore. On the other hand, failed checksum validation does indicate a problem somewhere, be that backend, network or local system, so it is probably useful to know about them during check.

I'm not tied to the b2-specific checksum validation. I think we do need some sort of retry on checksum failure during check (not sure if that currently happens during restore?), as it apparently can happen transiently.
My suggestion is, during checksum failure in check, print a warning with the failed checksum and retry some small number of times, and if it continues to fail treat it as it is now, as a failure. How does that sound?


[Question] Is Recaf not support Java 17?

Can't save with version 17, Is this because Recaf not support 17 yet ?
Under 16 will flash green while press Ctrl+S but 17 will flash red and print this in console:
Reason: 'Fix the invalid input'

https://github.com/Col-E/Recaf/blob/master/src/main/java/me/coley/recaf/ui/controls/node/ClassNodeEditorPane.java#L144
Needs to be updated, hasn't been touched in a long time.

Closing as 4.X is the only branch we're working on going forward.


OCPBUGS-27670,OCPBUGS-27585: [release-4.14] bump github.com/go-git/go-git/v5 to v5.11.0

Bumps github.com/go-git/go-git/v5 to v5.11.0 to address the following CVEs:

CVE-2023-49568
CVE-2023-49569

All other dependency changes are a result of the go-git bump + a go mod tidy + go mod vendor

/hold until #39 merges

/lgtm
/approve
/label backport-risk-assessed

@everettraven looks like the title needs a bit of editing. I see two issues mentioned.

Its allowed to mention multiple issues

/test openshift-e2e-aws

@everettraven looks like the title needs a bit of editing. I see two issues mentioned.

Its allowed to mention multiple issues

Oh it's addressing two issues, I see.

/label cherry-pick-approved

/label qe-approved

/jira refresh

/hold cancel

/jira refresh

/jira refresh


Devmode

I'm trying to update to 9.2, but when i select "DevMode" on RxTools menu i just get a black screen.

Did you copy and paste the rxtools.bin only or the entire RXTools folder?

Copied only the rxtools.dat and what was said in the tutorial.

What is your system version?

5.1.0-4U

Retried several times but same result?
If no, then retry it several more times.
If yes, then it's an incompatible issue of launching 2.5.2 Devmode on higher main version -4 frankenfirmwares, which gives you 2 choices only to solve this problem:

Cartridge upgrade to 6.0.0-4U - 6.3.0-4U, then use MSET to boot rxTools Devmode
Cartridge upgrade to 9.9, enter HBL, use SaveSysupdater to DG to 9.2

Actually i just used Pokemon X to update to 6.0 and it worked. It seems that the rxTools devmode for 5.0 isn't working properly


A successful activity log shows when using an existing folder name to rename another ADLS Gen2 folder

Storage Explorer Version: 1.17.0
Build Number: 20210127.3
Branch: main
Platform/OS: Windows 10/ CentOS 7.6.1810 (Core)/ MacOS Catalina
Architecture: ia32/x64
Regression From: Previous build (20210123.6)
Steps to Reproduce

Expand one ADLS Gen2 account -> Blob Containers.
Create a blob container -> Create two folders to it.
Use a folder name to rename another folder.
Check whether a failed activity log shows or not.

Expected Experience
A failed activity log shows.

Actual Experience
A successful activity log shows.

Fix merging into main in ~15min.

Fix merging into main in ~15min.

Hi @MRayermannMSFT      Verified on build 20210128.6. Nothing happens after clicking the 'Rename' action in the ADLS Gen2 blob container. So we re-open this issue and will keep eye on it.

Hi @MRayermannMSFT      Verified on build 20210128.6. Nothing happens after clicking the 'Rename' action in the ADLS Gen2 blob container. So we re-open this issue and will keep eye on it.

Verified on build 20210129.2. This issue has been fixed. So we close it.

Verified on build 20210129.2. This issue has been fixed. So we close it.


curaengine: 4.1.0 -> 4.2.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/curaengine/versions.
meta.description for curaengine is: '"A powerful, fast and robust engine for processing 3D models into 3D printing instruction"'.
meta.homepage for curaengine is: '"https://github.com/Ultimaker/CuraEngine"
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 4.2.0 with grep in /nix/store/ykbjyzknn09fssb2acdcry4i46blk48y-curaengine-4.2.0
directory tree listing: https://gist.github.com/cfdd42f795e9bc70b63588370137635a
du listing: https://gist.github.com/1811db328204eb525473ef726d1c2494

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

6 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
cura
curaengine

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ykbjyzknn09fssb2acdcry4i46blk48y-curaengine-4.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A curaengine https://github.com/r-ryantm/nixpkgs/archive/cc9933581a2d2a4febbdf9f86e387cefd9979bf5.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/ykbjyzknn09fssb2acdcry4i46blk48y-curaengine-4.2.0
ls -la /nix/store/ykbjyzknn09fssb2acdcry4i46blk48y-curaengine-4.2.0/bin

cc @abbradar for testing.

Superceded by #66315.


Playground feature request: ability to import file from disk

Title.
I'd love to see the result of some operations on my own pictures <3

This should already be fairly straightforward, see for example this playground link. Though, perhaps this could be made easier via some kind of GUI.
Let's tag this as an enhancement. Very happy to accept a PR, if you're able.

For GUI, literally all you'd need is a  I imagine...

Indeed, I meant some kind of "Files"-tab where you can manage the preloaded files and perhaps have them persist to IndexedDB. But maybe that's too complicated.
For now, I can recommend the playground link above.


the tree.add_node() methd

could you tell me ,how used the tree.add_node() method,i try many times,but it's not working ,way?

have tree object in your controller
2 .just use tree.add_node(parent, newNode) you can also add the third parameter, index for the new node inside children array of parent.

i have the same question,before i down the demo by the 'npm install',the function of add_node is working,and the remove_node method is always just a mass,later i down the demo from the webpage,the remove_node is normal,but the add_node function is not working,it's your pleasure to show me the answer.

tree.add_node(node, {});
tree.reload_data();// u can not see the new node without runing this method!


multitrack should complain about unbound ids

When used with #:transitions, should multitrack complain about using producers not in the multitrack?
For example, the following references blue-color and green-color that are not in the multitrack but reports no errors:
#lang video

(define circ-png "../examples/circ.png")
(define vid-mp4 "../examples/vid.mp4")

 (multitrack
  circ bg color
  #:transitions
  (list (composite-transition 0 0 1/2 1/2 #:top circ #:bottom bg)
        (composite-transition 1/2 0 1/2 1/2 #:top blue-color #:bottom bg)
        (composite-transition 0 1/2 1/2 1/2 #:top green-color #:bottom bg)))
(define bg (clip vid-mp4))
(define circ (image circ-png))
(define green-color (color "green"))
(define blue-color (color "blue"))

Yes it should, and no, it currently doesn't.

Commit 1c2a183e86d4fbf6bc6cc486aa4ee49bd1e606a2 should fix this.