Feature/extend pick functionality

Description:
Extended pick feature functionality by adding multiple path arguments and allowing nested pick using string dot path notation or array path variant
PR status:

[x] Version bumped
[x] Change-log updated
[x] Tests added or updated
[x] PR keeps 100% test coverage
[x] Linter is applied
[x] Const arrow functions are used instead of pure function definitions where applicable
[x] Functions are listed in alphabetic order in index.js, index.d.ts and readme

also branch has conflicts


Introduce Static Application Security Testing (SAST)

What would you like to be added:
Please, ensure that a linter is enabled, a new release is created, and deployed.

Python code shall be scanned with Bandit
Bash scripts shall be scanned with ShellCheck

Why is this needed:
Security & Compliance

/assign


Adding FlyWire body IDs to URL

Function for adding body IDs to display while creating a FlyWire URL.
Similar to fafbseg function flywire.encode_url, example:
url = fafbseg.flywire.encode_url(segments=720575940642841623)

@eichlerkathi Can you please check if it works, the example is under:
https://github.com/SridharJagannathan/pyroglancer/blob/master/pyroglancer/examples/unit_examples.ipynb
you can start looking from example 3 onwards

Works, thank you!


Implement custom sorting based on rules.

SortRules allows us position file whatever we like, based on Regexp match.
It's very useful in finding files when you know exactly where they will occur in hierarchy in explorer. E.g.: Interfaces will always placed at the top.

Thanks for your PR. However before providing PR it is usually best to first start a discussion.
Regarding this the issue is that we already have a sort option, and adding another one does not really make sense. https://github.com/Microsoft/vscode/wiki/How-to-Contribute
Also I am not sure what issue would this feature solve. We do not just merge everythign into vscode otherwise there would be too much bloat.
Due to the above will not merge in this PR

I am totally fine with your decision :D
On day-to-day basis I works with my custom build, this feature comes from there. I decided it is better to show implementaion right away, becouse I already had it, that's why I didn't create disscussion. Sharing it cost me nothing.
What issue it solves? Probably none :) In last update (version 1.31) I notice that it include Tree UI improvements, which refers to problem with navigation in files explorer. I finds helpful knowledge that all interfaces I have are listed at the top, or more generally that my explorer is sorted some logically / functional way. Then quick glance at explorer and I know what abstractions files I have to deal with. I don't have to typing to filter files.

Ok, thanks for explanation. Still not merging it in though :)

Clossing as out of scope.
Thank you again for your PR.


Calculated Sankey node width

Currently, Sankey node width is hard coded. Since some configurations have a small number of sets, the hard coded value can look excessively small sometimes. The width of the Sankey nodes should be calculated from the number of columns in the Sankey diagram.

And when diagram gets a LOT bigger, it's often hard to see what's going on. I don't think it should always fit in one screen width - when the calculeted width gets to some minimum value, the diagram shoul just get wider, not denser, so it's still readable


ODIM-78 Remove compiled proto files from GIT repo

Please add the entry in the .gitignore file for .pb.go

Added entry to ignore pb.go files


Updates to support multiple dotnet targets

support v3.5, v4.0, v4.5.2, v4.7.2 and dotnetcore2.2
added support for Appveyor build

This is the continuation of #415, rebased with current version, fixed some merge errors and problems with excluded code. This is still work in progress.

@tebjan - this seems to work basically, at least under Windows - for a problem under Linux there is a separate issue.
I won't wait anymore for the original author for merging - support for Linux and for NetStandard can be added later - but I would like you to check and try this PR to make sure nothing is broken or missing before merging.

looks good to me. i am just wondering why there is the need for so many .net frameworks. since the lowest version will work with any project that targets this or a newer framework.

Good question - I actually don't know.
Currently, the unit tests in AppVeyor work only with .NET 4.5 and higher, and in .NETCore, due to the MS test framework, but that is not a real reason...

Actually, I will just remove the unneeded versions, leaving only .NET 3.5 and .NETCore - you are right, this is not needed, I just hadn't questioned that...

Ok, I amended the last commit accordingly.

it doesn't hurt either. so, i think you can leave the 4.5 if it helps to have the tests running.

The tests also run with 3.5 - only the unit test project itself has to be 4.5, so this is not an issue.

ping me if you think it's ready for another nuget release.

This is still work in progress.

this seems to work basically, at least under Windows

Anything in particular others can help on?

Anything in particular others can help on?

Yes - make it work under Linux :)
If have not tested it myself, but there is at least #427 that needs fixing - any help is welcome!

I made a pull request for this. Unfortunately, I couldn't figure out how to make a pull request consisting only of my change, so I made it separately at https://github.com/vvvv/SVG/pull/450.

I made a pull request for this. Unfortunately, I couldn't figure out how to make a pull request consisting only of my change, so I made it separately at #450.

I should have merged back first... well, I will use yours instead, thanks a lot!

Closing - will use the new PR instead.


feat: Add OS detection hook and update search dialog

Description
This PR addresses issue #1758 and introduces the following changes:

Added a new file useOSDetection.ts which contains a custom hook for detecting the user's operating system.
Updated the file search-dialog.tsx by importing and using the useOSDetection hook.
Made necessary UI changes to handle OS-specific text in the search dialog.

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[x] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents
Fixes #1758
Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
No
[optional] What gif best describes this PR or how it makes you feel?
XD

Very nice! Code wise, this looks solid. Thanks for tackling this.
The styling looks abit cramped to me?

I wonder if this also deserves it's own styling. Curious what others think?

I agree that it's a little cramped.

Very nice! Code wise, this looks solid. Thanks for tackling this.
The styling looks abit cramped to me?

I wonder if this also deserves it's own styling. Curious what others think?

Thank you for the comments! I can definitely work on updating the styling a bit and give it more room to breath.


[vcpkg-cmake] Remove cmake generator support restrictions

Describe the pull request

What does your PR fix?
Removes generator restrictions from vcpkg_cmake_build. When arriving in this function, the generator was already used successfully for build system generation, so there is no reaon for failing here. There is still a point in printing a warning if we don't how to control the build tool (verbosity, parallelism). Resolves #22368 if using the maintainer functions from port vcpkg-cmake. Fixes building packages which assume the make build tool, e.g. by using $(MAKE) for recursive invocations.
Rectifies the configure command mentioned in that message.
Adds Unix Makefiles support. (Tested locally with libwebsockets:x64-linux. Total port build time is equal to Ninja, app. 20 s.)
Integrates the documentation update from #21763.
Adds Xcode support by @luncliff, cherry-picked from #22631.

Which triplets are supported/not supported? Have you updated the CI baseline?
all, no
(No effort is made to acquire make for windows. I assume cmake will already complain in the configure step if cannot find the build tool.)

I will merge this with a bundle of other rebuild-the-world changes.

It would be nicely complemented by vcpkg-cmake-config changes, such as https://github.com/microsoft/vcpkg/pull/22546.


Include footer links in the template

The Performance Platform makes use of govuk_template, but we're hosted on www.gov.uk - so having the footer links available would be really useful for us. We're a special case technically, of course.
For now we've included the HTML and CSS because we need to be consistent across multiple frontend apps while we're transitioning to our own infrastructure, but as @bradleywright notes that doesn't work long-term.
Does anybody have any thoughts on making the GOV.UK footer links available in this project?

I'm doing a general clean up of old and/or state issues, so closing this.
We've lived with this for going on 3 years and quite a few people involved aren't working on the projects anymore.


Managed Identity Resource ID

Description
Add the ability to use a managed identity resource ID for supported services.
All SDK Contribution checklist:

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

General Guidelines and Best Practices

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

Testing Guidelines

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

I've got tests locally which I'll add tomorrow.

API changes have been detected in com.azure:azure-identity. You can review API changes here
API changes
+         public DefaultAzureCredentialBuilder managedIdentityResourceId(String resourceId)
+         public ManagedIdentityCredentialBuilder resourceId(String resourceId)

API changes have been detected in com.azure:azure-identity. You can review API changes here
API changes
+         public DefaultAzureCredentialBuilder managedIdentityResourceId(String resourceId)
+         public ManagedIdentityCredentialBuilder resourceId(String resourceId)


Allow MessagingUsers to be created from service accounts

why
Allow MessagingUsers to be created from service accounts.  This will allow applications running in Kubernetes to use their service account credentials to authenticate against the address space
Proposal
Update the Keycloak plugin to recognize a new type of credential for a service account - from a SASL perspective it will need to be sent using PLAIN.  The plugin will find the user, see it is a service account based user, and then attempt to authenticate with Kubernetes using the service account name / password.
Testing
Test that a messaging user can be created from a service account
Test that the credentials of the service account can be used to make a messaging connection
Test that using the credentials of a service account which is not a messaging user does not allow a messaging connection to be made
Test that using an incorrect password for the service account does not allow a successful connection
Documentation
Update docs on creating messaging users
Tasklist

Do service accounts have passwords? (I thought they did not and just had tokens generated).

@grs sorry - was writing from the point of view of SASL where it is a password... from the point of view of the service account it is a token (although not an OAUTH one)

makes sense (allowing password file to be specified in the connect.json supported by proton python, c++ and rhea would then be nice)

@lulf it will need to be a new authentication type - we can't use the federated identity as (in general) the service accounts need not be being served by an oauth provider (I assume that is the case for standard kubernetes).  I'm thinking that the (Keycloak) user will be created with a new type of credential "serviceAccount" or whatever, and which (at most) will hold the details of the Kuberenetes server.  On getting a login attempt for a user with such a credential, Keycloak will simply send the "password" received as a token to the  Kubernetes server and see if it is authenticated (there's a question here as to whether it should check that the username matches the authenticated account that Kubernetes finds)

@lulf that's the plan - yes


Fix Read The Docs build, update paths to readthedocs.io

The Read The Docs build has been broken for nine months 😢
http://django-nose.readthedocs.io
This add the requirements needed to make the build pass.  It also updates the paths to readthedocs.io that changed on April 27, 2016:
https://blog.readthedocs.com/securing-subdomains/

Fixed build at http://django-nose.readthedocs.io/en/fix_rtd/. Will merge when TravisCI agrees.

Coverage remained the same at 68.326% when pulling 237fe8bf6f893e42f980bf8146482a65f8fd2fe6 on fix_rtd into 5202a545dbafcb074740f9bacdc88241a4d006eb on master.

Coverage remained the same at 68.326% when pulling 237fe8bf6f893e42f980bf8146482a65f8fd2fe6 on fix_rtd into 5202a545dbafcb074740f9bacdc88241a4d006eb on master.

Coverage remained the same at 68.326% when pulling 237fe8bf6f893e42f980bf8146482a65f8fd2fe6 on fix_rtd into 5202a545dbafcb074740f9bacdc88241a4d006eb on master.

Coverage remained the same at 68.326% when pulling 237fe8bf6f893e42f980bf8146482a65f8fd2fe6 on fix_rtd into 5202a545dbafcb074740f9bacdc88241a4d006eb on master.


FullRLNCEncoder produces encodings that cannot be decoded

While very unlikley, FullRLNCEncoder can produce encodings that cannot be decoded.  The attached file produces such an example.  Note that data.go uses crypto/rand.  To make the example reproducable, I needed to update data.go to use math/rand.  Also, github was not allowing me to upload the patch file as a .patch, but since txt files are okay, I renamed to .patch.txt
enc-dec-fail.patch.txt

Hi @dlm, this is interesting ! Thank you very much for reporting the error. I'll take a deep look.

@itzmeanjan no problem.  Glad to help out!


Fix cart quantity doubling

1. Why is this change necessary?
Because adding items to empty cart, when any promotion item is active, doubles the quantity of added items.
2. What does this change do, exactly?
It changes the way that errors in CartRuleLoader are handled - the error of type "PromotionCartAddedInformationError" is omitted, because it's logically not an error, so the cart is not saved "for persisting errors", which prevents preloading already filled cart, when it should be empty.
3. Describe each step to reproduce the issue or behaviour.

Create an promotion in Admin Panel -> Marketing -> Promotions, which is applicable in your current state
Try to add a item to the cart
Quantity should be doubled (you should see that two items was added in default)
Another way:
Make an successful order
Create an promotion in Admin Panel -> Marketing -> Promotions, which is applicable in your current state
Go to order history page and try to add to cart the order which you have made earlier
The added quantity should be doubled

Didn't tested with more than one item in cart, but it seems that the issue is independent of quantity for any product/item.
4. Please link to the relevant issues (if any).
https://github.com/shopware/platform/issues/1008
5. Checklist

[x] I have written tests and verified that they fail without my change
[/] I have squashed any insignificant commits
[/] I have written or adjusted the documentation according to my changes
[/] This change has comments for package types, values, functions, and non-obvious lines of code
[/] I have read the contribution requirements and fulfil them.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 12 committers have signed the CLA.:white_check_mark: jleifeld:white_check_mark: runelaenen:white_check_mark: shyim:x: taltholtmann:x: philipgatzka:x: pweyck:x: leichteckig:x: Haberkamp:x: tobiasberge:x: OliverSkroblin:x: ssltg:x: raknisonYou have signed the CLA already but the status is still pending? Let us recheck it.


Repackage for Node

this PR includes a few changes:

[x] Update cargo deps
[x] Rework package.json to include type: "commonjs" (proper detection in nodejs, even with es module loader)
[x] include serde-wasm-bindgen
[x] update nodejs example

when I try to run the node example, I get the following error:
❯ npm run start

><EMAIL_ADDRESS>start
> node --experimental-specifier-resolution=node --experimental-wasm-modules index.js

(node:170287) ExperimentalWarning: The Node.js specifier resolution flag is experimental. It could change or be removed at any time.
(Use `node --trace-warnings ...` to show where the warning was created)
/home/geal/dev/biscuit/biscuit-wasm/dist/snippets/biscuit-auth-c2c5e1119121bf61/inline0.js:2
export function performance_now() {
^^^^^^

SyntaxError: Unexpected token 'export'
    at Object.compileFunction (node:vm:360:18)
    at wrapSafe (node:internal/modules/cjs/loader:1078:15)
    at Module._compile (node:internal/modules/cjs/loader:1113:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1203:10)
    at Module.load (node:internal/modules/cjs/loader:1027:32)
    at Module._load (node:internal/modules/cjs/loader:868:12)
    at Module.require (node:internal/modules/cjs/loader:1051:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (/home/geal/dev/biscuit/biscuit-wasm/dist/biscuit.js:2:66)
    at Module._compile (node:internal/modules/cjs/loader:1149:14)

That code comes initially from the rust crate: https://github.com/biscuit-auth/biscuit-rust/blob/master/biscuit-auth/src/time.rs#L40-L42
It needs to measure time to limit execution. That snippet used to work with the previous version, should it be updated?What would be the new syntax?

I'm testing another approach in https://github.com/biscuit-auth/biscuit-wasm/pull/6 where we would move to a single ES module. It looks like it is loaded properly, but the generated code is apparently invalid (and that code is used under the hood for random number generation, we can't remove it easily)

@flyboarder @ptondereau I think I'll merge #6 tomorrow if there are no other concerns. I validated that it works, there's just the caveat that the latest getrandom version requires this in node apps:
https://github.com/biscuit-auth/biscuit-wasm/pull/6/files#diff-72739caf9bbc4a6afefa4d344a2414a8f5cc2ac32ab3b001d66459bbea2da8e3R3
Maybe that can be directly integrated in the library.
Shipping a cjs module should be fine too, we would just have to validate that it loads correctly in browsers, as tested here.
I have no strong opinion on cjs vs esm, I was just told that esm is the future (and supports async loading which is nice with wasm), so might as well switch to it :smile:


TurboWarp blocks "(...) mouse button down?" does not work when Pen+ is rendering triangles

if i'm using Pen+ to render triangles, the mouse button down block (including the one from scratch) always reports false, but if i create a project using sprites, the mouse button down block works as expected.

I will try and fix that in version 6 thanks for reporting this bug.

is this fixed in v6?

I'm pretty sure since I have gotten mouse interaction working in games. I
think originally it was a thing with their thing of turbowarp since I could
never replicate it.
On Mon, Aug 28, 2023 at 3:01 PM GarboMuffin @.***>
wrote:

is this fixed in v6?
—
Reply to this email directly, view it on GitHub
https://github.com/TurboWarp/extensions/issues/170#issuecomment-1696218672,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ6YTTWBSTBHOJZMBK6KIKTXXTTJBANCNFSM6AAAAAAUHSENL4
.
You are receiving this because you commented.Message ID:
@.***>

@GarboMuffin It seems to be fixed


Trouble with no-unused-vars rule

Before You File a Bug Report Please Confirm You Have Done The Following...

[X] I have tried restarting my IDE and the issue persists.
[X] I have updated to the latest version of the packages.

What version of ESLint are you using?
v8.32.0
What version of eslint-plugin-astro are you using?
0.21.1
What did you do?

Configuration
{
  "extends": [
    "plugin:astro/recommended"
  ],
  "rules": {
    "no-unused-vars": "error"
  },
  "overrides": [
    {
      "files": [
        "*.astro"
      ],
      "parser": "astro-eslint-parser",
      "parserOptions": {
        "extraFileExtensions": [
          ".astro"
        ],
        "ecmaVersion": "latest"
      }
    }
  ]
}

---
import SomeComponent from '../components/SomeComponent.astro';
---

<SomeComponent />

What did you expect to happen?
I was hoping that the Astro plugin would work with the no-unused-vars rule.
What actually happened?
/path/to/src/pages/problem.astro
  2:8  error  'SomeComponent' is defined but never used  no-unused-vars

Link to Minimal Reproducible Example
https://stackblitz.com/edit/github-nzoac8?file=README.md
Additional comments
Much like the eslint-plugin-react allows ESLint rules (such as no-unused-vars) to work with JSX, I was hoping that this plugin would allow the same for Astro components.  I see that there are integration tests using the no-unused-vars rule, but it looks like those don't cover the use of a variable from a component script in a component template.

Thank you for the quick fix, @ota-meshi!

@ota-meshi - I've just tried upgrading to the latest plugin and parser versions and this issue came up again (https://github.com/planetlabs/maps/pull/501).
Let me know if I should open a new issue in the eslint-plugin-astro project or in astro-eslint-parser.

I see that the regression was reported in https://github.com/ota-meshi/eslint-plugin-astro/issues/378


Integration with the HuggingFace Ecosystem

This is so great! You guys are addressing a lot of pain points in large model training with simple APIs!
One question: what would be the integration for huggingface ecosystem? For example:

Can we directly load model with from_pretrained method, and automatically convert it to NanotronModel? Or we need to manually define a model class in Nanotron style and write some cutom loading logics?
Can we easily export model checkpoints to HF/safetensors format?

For now most transformers architectures should be supported with minimal changes (like adding PipelineBlock for pp  or column / row linears for TP). We'll have easy to follow templates for that soon, but for now we can use llama as an example :)
While training we save checkpoints in safetensors format which enables resuming training from those. And can easily be adapted HF's transformers depending on your model's modeling!


What is our primary email contact?

<EMAIL_ADDRESS>(listed on the website) bounces. We should fix this on the homepage.

In my Google account for Citizen Labs, I do not see the Admin icon in my apps list (like I do for another G-Suite account that I administer), so I'm assuming that either Allen or Jace or both have control over the email accounts.

I am trying to create a Google Group with the email address as<EMAIL_ADDRESS>That way multiple people can see and respond to incoming emails. We could do an alias, but my understanding is that an alias can only go to a single person - not a group.

I faced the same problem with another groups a couple years ago. We ended up making it a behind-the-scenes distribution list (not visible to the sender up front), but it's been kind of clumsy, since it's so hard to tell who has seen and/or responded to the messages.

<EMAIL_ADDRESS>&<EMAIL_ADDRESS>are now in a collaborative inbox that all Board Members are free to join. Invitations to join the group has been sent out.


[FIX][broker]Fix the issue of incorrect publish time obtained through admin api when encountering anomalies in the broker's timezone.

Fixes #21891

Motivation

I encountered an issue in the production environment where the publish time obtained through the admin API was inaccurate.By reviewing the source code, I found that the broker had already made the conversion before returning the publish time, which means that the time string is related to the broker's timezone and it would be incorrect if the broker's timezone were incorrect.This bug may bring troubles in certain usage scenarios.

Verifying this change

[x] Make sure that the change passes the CI checks.

This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

By reviewing the source code, I found that the broker had already made the conversion before returning the publish time, which means that the time string is related to the broker's timezone and it would be incorrect if the broker's timezone were incorrect.This bug may bring troubles in certain usage scenarios.

@tikafu I noticed your in-depth investigation in https://github.com/apache/pulsar/issues/21891#issuecomment-1892970655 . Since we cannot break an existing interface, we should be understand exactly what the issue is by reproducing the issue in a unit test and fixing that particular actual issue.
My assumption is that if the text formatted contains the timezone information, it should be possible to parse that into the timestamp later. Perhaps it is a bug in the org.apache.pulsar.common.util.DateFormatter after all?

More likely a JVM bug: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8177021 ,
https://bugs.openjdk.org/browse/JDK-8177021 . Problem report was with 1.8.0_201 (Jan 2019). The bug JDK-8177021 has been updated "Cannot Reproduce" in 2021, so it has been fixed.


BrowserHistory doesn't render sub-routes in 1.0.0-beta2

HashHistory works, BrowserHistory doesn't. React 0.13.3, Chrome.
/#/b path with HH: both A and B components are rendered
/b path with BH: only A component is rendered, no error is thrown

import React from 'react'
import {Router, Route} from 'react-router'
import BrowserHistory from 'react-router/lib/BrowserHistory'

class A {
  render() { return
Hello A {this.props.children}
 }
}

class B {
  render() { return
Hello B
 }
}

const history = new BrowserHistory()
const rootElement = (
    <Router history={history}>
      <Route path='/' component={A}>
        <Route path='b' component={B} />
      </Route>
    </Router>
)

React.render(rootElement, document.body)

It behaves the same in Firefox and Explorer.

OK. thats because browser is looking for the path on the server (I was placing the link into browser url).


check for "experiencing BlueFS spillover" in ceph

as described in https://tracker.ceph.com/issues/38745 , and case 00326782, hotsos should check for message "BlueFS spillover detected " to check for the rocksdb's level-sized issue.
$ ceph -s
cluster:
id:     815ea021-7839-4a63-9dc1-14f8c5feecc6
health: HEALTH_WARN
BlueFS spillover detected on 1 OSD(s) <--
Also, even if this situation has not been hit, we should check between ceph-osd versions 15.2.6->15.2.10 if the option bluestore_volume_selection_policy is not set to "use_some_extra" because then the vulnerability still exists.
So this is the second check to be made, to check for the vulnerability if the ceph packages fall between 15.2.6 and 15.2.10,
$ sudo ceph daemon osd.1 config show|grep -i policy
"bluestore_volume_selection_policy": "use_some_extra",

The following can be used as a guide on how to implement this:
https://github.com/canonical/hotsos/blob/master/defs/scenarios/storage/ceph/auth_insecure_global_id_reclaim_allowed.yaml

There are two parts to this check.
a) simply check if we see BlueFS spillover detected in the ceph status, or the detailed status, and report the bug if that string is found.
b) Check between ceph-osd versions 15.2.6->15.2.10 to see if bluestore_volume_selection_policy is not set to use_some_extra and if that is the case, report the vulnerability.
I can see that a) is easily implemented using the approach shown in https://github.com/canonical/hotsos/blob/master/defs/scenarios/storage/ceph/auth_insecure_global_id_reclaim_allowed.yaml but I am not sure if the scenarios can also take min-version, fixed-version, etc like how the bugs do, and how I'd check for the value of bluestore_volume_selection_policy. Would I need to add a property to the class CephMon(CephDaemonBase) and return that value? just like we do for osdmaps_count?
class CephMon(CephDaemonBase):

    def __init__(self):
        super().__init__('mon')

    @property
    def osdmaps_count(self):
        report = self.cli.ceph_report_json_decoded()
        if not report:
            return 0

        try:
            return len(report['osdmap_manifest']['pinned_maps'])
        except (ValueError, KeyError):
            return 0

@nkshirsagar so you can implement this is one of two ways; either using bugs (i have added support for the requires property to bugchecks [1]) or as a scenario. If you use a scenario you will need to implement all the requirements as properties (which you can then call using the requires property). Its up to you which one fits best.
[1] https://github.com/canonical/hotsos/tree/master/defs#bugs

thank you for https://github.com/canonical/hotsos/pull/273/files @dosaboy++
I am trying to consume it this way, as a command, with both the A and B parts defined in bugs/storage/ceph.yaml , with one bug check under 38745 ,and the vulnerability under  vulnerable_to_38745
38745:
  settings:
    package: 'ceph-osd'
  input:
    command: ceph_health_detail_json_decoded
  expr: '.+BlueFS spillover detected on'
  hint: 'spillover'
  raises:
    message: >-
      installed package '{package_name}' with version {version_current} has a
      known bug https://tracker.ceph.com/issues/38745.
vulnerable_to_38745:
  input:
    command: ceph_daemon_config_show
    options:
      kwargs:
        name: 'bluestore_volume_selection_policy'
    value: 'use_some_extra'
    operator: ne
  settings:
    package: 'ceph-osd'
    versions-affected:
      - min-broken: 15.2.6
        min-fixed: 15.2.11
  raises:
    message: >-
      Vulnerability to a known bug https://tracker.ceph.com/issues/38745.
      Please set bluestore_volume_selection_policy of all OSDs to use_some_extra

posting info from discussion with @nkshirsagar
now that https://github.com/canonical/hotsos/commit/21ad59ed5878c03afc9a1de5553181c93713cb64 is landed you can do:
requires:
or:
- property: core.plugins.storage.ceph.CephDaemonConfigShowAllOSDs.bluestore_volume_selection_policy
value: [use_some_extra]
- property: core.plugins.storage.ceph.CephDaemonConfigShowAllOSDs.bluestore_volume_selection_policy
value: []

Thank you for the help @dosaboy
But I'm still having a build failure. I've simplified the yaml to this
38745:
  input:
    command: ceph_health_detail_json_decoded
  expr: '.+BlueFS spillover detected on'
  hint: 'spillover'
  raises:
    message: >-
      installed package '{package_name}' with version {version_current} has a
      known bug https://tracker.ceph.com/issues/38745.
38745:
  settings:
    package: 'ceph-osd'
    versions-affected:
      - min-broken: 15.2.6
        min-fixed: 15.2.11
  requires:
    or:
      - property: core.plugins.storage.ceph.CephDaemonConfigShowAllOSDs.bluestore_volume_selection_policy
        value: [use_some_extra]
        operator: ne
      - property: core.plugins.storage.ceph.CephDaemonConfigShowAllOSDs.bluestore_volume_selection_policy
        value: []
        operator: ne
  raises:
    message: >-
      Vulnerability to a known bug https://tracker.ceph.com/issues/38745.
      Please set bluestore_volume_selection_policy of all OSDs to use_some_extra

THe build fails with
======================================================================
ERROR: test_bug_checks (test_storage.TestStorageBugChecks)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/nikhil/HDD_MOUNT/Downloads/hotsos_fork/hotsos/.tox/py3/lib/python3.8/site-packages/mock/mock.py", line 1346, in patched
    return func(*newargs, **newkeywargs)
  File "/home/nikhil/HDD_MOUNT/Downloads/hotsos_fork/hotsos/tests/unit/test_storage.py", line 641, in test_bug_checks
    YBugChecker()()
  File "/home/nikhil/HDD_MOUNT/Downloads/hotsos_fork/hotsos/core/ycheck/__init__.py", line 630, in __call__
    return self.run_checks()
  File "/home/nikhil/HDD_MOUNT/Downloads/hotsos_fork/hotsos/core/ycheck/__init__.py", line 620, in run_checks
    ret = self.run(self.searchobj.search())
  File "/home/nikhil/HDD_MOUNT/Downloads/hotsos_fork/hotsos/core/ycheck/bugs.py", line 133, in run
    pkg_ver = bugsearch['context'].apt_all.get(pkg)
AttributeError: 'NoneType' object has no attribute 'apt_all'
-------------------- >> begin captured logging << --------------------
root: DEBUG: loading bugs definitions for plugin=storage
root: DEBUG: loaded plugin 'storage' bugs - sections=1, events=1
root: DEBUG: bug=38745 path=None
root: DEBUG: no search terms registered so nothing to do
root: DEBUG: requirements provided as groups
root: DEBUG: op=or has 2 requirement(s)
root: DEBUG: calling property core.plugins.storage.ceph.CephDaemonConfigShowAllOSDs.bluestore_volume_selection_policy
root: DEBUG: creating filesearcher with max=2 processes
root: DEBUG: path=/tmp/tmp7wfcztu4/tmp9ryz5_2r
root: DEBUG: files=1 searches=1
root: DEBUG: completed searches (results=3)
root: DEBUG: requirement check: property core.plugins.storage.ceph.CephDaemonConfigShowAllOSDs.bluestore_volume_selection_policy <built-in function eq> ['use_some_extra'] (result=True)
root: DEBUG: calling property core.plugins.storage.ceph.CephDaemonConfigShowAllOSDs.bluestore_volume_selection_policy
root: DEBUG: creating filesearcher with max=2 processes
root: DEBUG: path=/tmp/tmp7wfcztu4/tmpye383pma
root: DEBUG: files=1 searches=1
root: DEBUG: completed searches (results=3)
root: DEBUG: requirement check: property core.plugins.storage.ceph.CephDaemonConfigShowAllOSDs.bluestore_volume_selection_policy <built-in function eq> [] (result=False)
--------------------- >> end captured logging << ---------------------

----------------------------------------------------------------------
Ran 210 tests in 12.082s

FAILED (errors=1)
ERROR: InvocationError for command /home/nikhil/HDD_MOUNT/Downloads/hotsos_fork/hotsos/.tox/py3/bin/nosetests --verbose tests/unit (exited with code 1)

(I've used the same bug number for both the sections.)
It seems like hotsos expects a context section in the yaml.
I see in the openstack folder, for eg, openstack.yaml contains,
# This file is used to define overrides applicable to contents of this
# directory including subdirectories.
requires:
  property: core.plugins.openstack.OpenstackChecksBase.plugin_runnable
context:
  apt-all: core.plugins.openstack.OpenstackBase.apt_packages_all

and the OpenstackBase class contains,
class OpenstackBase(object):

    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)
        self.ost_projects = OSTProjectCatalog()
        other_pkgs = self.ost_projects.package_dependencies
        self.apt_check = checks.APTPackageChecksBase(
                                  core_pkgs=self.ost_projects.packages_core,
                                  other_pkgs=other_pkgs)
        self.nova = NovaBase()
        self.neutron = NeutronBase()
        self.octavia = OctaviaBase()

    @property
    def apt_packages_all(self):   <--
        return self.apt_check.all

Would I need something equivalent in a new defs/bugs/storage/ceph.yaml file like the openstack.yaml? Though there is no apt_packages_all defined in Storagebase , or CephChecksBase that I can see.

Hi @dosaboy , I've implemented the vulnerability as a bug and the detection of the actual log string as a scenario. I left the vulnerability in the bug since I figured I'd need to implement the requirements as properties if I moved it to a scenario. The actual string check in the logs did not need to check any properties so I moved it to scenarios. There's a problem though, since there's no (from what I can see) launchpad bug opened here, so I want to rely on the upstream bug. However, the "id" field in the hotsos output always appends the bug number to the launchpad URL...
So when I test it on a sosreport, I see,
bugs-detected:
- desc: Vulnerability to a known bug https://tracker.ceph.com/issues/38745. Please
set bluestore_volume_selection_policy of all OSDs to use_some_extra
id: https://bugs.launchpad.net/bugs/38745
origin: storage.auto_bug_check
I also see in potential-issues, the scenario check show up properly.. It needs some justify or line wrap to not have the one long line at the end.. (test wrapped around here so looks OK but in hotsos output the entire output from "known ceph bug..." and the URL too is all on one line..)
potential-issues:
CephWarnings:
- 'This node has Ceph OSDs running on it but is not using cpufreq scaling_governor
in "performance" mode (actual=ondemand). This is not recommended and can result
in performance degradation. To fix this you can install cpufrequtils and set
"GOVERNOR=performance" in /etc/default/cpufrequtils. You will also need to
disable the ondemand systemd service in order for changes to persist. NOTE:
requires node reboot to take effect. (origin=storage.auto_scenario_check)'
- Known ceph bug https://tracker.ceph.com/issues/38745 detected. See <--https://docs.ceph.com/en/latest/rados/configuration/bluestore-config-ref/#sizing
(origin=storage.auto_scenario_check)
I've sent this initial PR just to show you the way I'm doing it..  if it is OK to do it this way then I can start to work on the unit test.


Advanced copy of cell values as qouted text does not work

Description
When I make a copy of selected cells from grid by advanced copy and choose Quote cell values, the result is not qouted

DBeaver Version
Comunity Version <IP_ADDRESS>401072024
Operating System
Windows 10
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Hello @sykyman
You need to use another setting for data quoting - the "Always quote values" setting.

The first one has another condition.

Oh, thank you. My misstake. I do not know, why i used this one.


Improvement for k8s.io/docs/concepts/overview/working-with-objects/field-selectors/

need more real examples on how to use the field selectors. whats the best way for me to check the status of a pod /container which is in COMPLETED state.  I used to check the current status of pods which are in Running ( --field-selector=status.phase!=Running), but how to list the pods which are in terminating state ( Terminating state.) using field selectors or how to list then with the Reason of terminating …?

Thanks for the suggestion
/priority backlog

/remove-lifecycle stale

/remove-lifecycle rotten
/lifecycle-freeze
We have got many complaints on this:
#9807 #15197 #15214 #15459 #19775 #20041 #20046

/reopen

/lifecycle-frozen

/lifecycle frozen
/language en
/kind feature

I would like to provide some more examples and am happy to do the PR. Any preferences whether I add the extra examples in this page, or as a new page under /Tasks/ (e.g. /tasks/manage-kubernetes-objects/field-selectors or something similar)?

/assign

Also see https://github.com/kubernetes/website/issues/40701

With the many issues raised as linked to this, plus the above-mentioned #40701 by @sftim, it's worth us noting what the acceptance criteria for this issue would be for us to be satisfied with the outcome, on top of it being helpful to users

Closing in favor of https://github.com/kubernetes/website/issues/47642
/close not-planned


404 Error on download Arcade Artworks

I was about to download the clean arcade artwork for the FBNEO roms i have and the download stops with a 404 Error on the aa.zip file. Im sure that was not part of the romset but i think a simple "ignore" button for errors would be nice ;)

Fixed - will be in the next release


Fix URL encoding of error report for Thunderbird

Thunderbird doesn't seem to convert the plus signs in encoded error report URLs back to spaces, so we end up with unreadable error reports.

Fix tested and confirmed via Deploy Preview. :tada:


scaled output messes up bar

Thanks for tagging a new release, and allowing build with 0.12 zig.
I build and tried this on void linux, and it looks and feels quite nice.
One issue I encounter is that, for scaled output, the bar is messed up,
namely there's one more black bar below it.
By scaled, I mean wlr-randr --output eDP-1 --scale 2 in river init.
Also, it'd be nice to have a -Dpie configure option, to produce pie executables.
Finally, what are your thoughts about implementing a config file?
instead of piping the output and/or poling frequently, the config file could contain
the actual command(s) I want to run, e.g date '+%a %Y-%m-%d %H:%M',
and their polling time, e.g. 5s,
as well as possibly the various options for font, color, etc,
similar to dwm but without the need to rebuild it.

Hi, thanks for the report! Lack of support for scaled outputs is currently a known limitation (levee, on which creek is based, didn't properly support this originally either). I don't use scaled outputs right now, hence it hasn't been a priority for me personally to address this. Additionally, it's not that easy to support in the current code base. One major problem in this regard is the lack of a good abstraction for fcft+pixman within the code base. Essentially, all calculations in src/render.zig would therefore have to be adjusted in a way that they take the scale factor into account. Probably, it would be good to first refactor the code in a way that provides a good widget/drawing abstraction on top of fcft and pixman, which could then be enhanced to take the scale factor into account. Patches implementing that are more than welcome.
I like the -Dpie suggestion, I will add that in a second.
I am personally not a fan of config file support, but feel free to maintain you own fork if this is of interest to you.

I see, thanks for the explanation. I understand your point about config.


Unable to load codebehind file when page exist within a directory

When a page exists within a directory, and not at the root of the project, and attempts to reference a code behind file within the same directory using only the file name of the codebehind file, aspnet_compiler throws an exception.  On v0.3.0, the exception thrown suggests the base path is not relative, while on the v0.3.1 preview based on pull request #274, it attempts to find the code behind file at the root rather than within the directory.  This is occurring on Windows, and I believe unlikely to occur on Linux in the second case.
Reproduce

Create a CoreWebForms project
Add a directory to the project
Add an aspx file to the directory
Add a corresponding aspx.cs to the same directory
Wire up the aspx file to use the aspx.cs file as a code behind file
Attempt to build the project

Expected result
Build proceeds normally.
Actual result
Build fails when aspnet_compiler is run, when it throws an HttpParseException, as noted above.
Additional details
In the case of v0.3.0, it appears that the virtual paths for aspx pages are created as relative paths rather than absolute paths, as an example, Directory\Page.aspx rather than \Directory\Page.aspx or /Directory/Page.aspx or /Directory\Page.aspx.  When the code behind file is specified as Page.aspx.cs, an attempt is made to generate a virtual path of the code behind file using the aspx page as the base path, and since the code behind file is not an absolute path, it attempts to combine the parent of the aspx page, Directory\ and the code file.  However, this fails, as the base path is not absolute.
This appears to have changed in the packages based on #274, as some of the virtual path handling is now in SystemWebAdapters.  In this case, the path of the aspx files are absolute, but it makes use of \ for directory separators, while using / for the root, /Directory\Page.aspx.  While this format would work properly by attempting to combine the parent of the aspx page path with the code behind file path, the SystemWebAdapters code instead uses UrlPath.GetDirectory, which appears to only work using / as a directory separator.
Workaround
By specifying the code behind file using an absolute path rather than a relative path, it works on both versions.

This appears to be a duplicate of #259, or, at least a more generic view of the problems causing #259, and I believe this will also be fixed by #260.


Injecting Store in Custom Authenticator

I am trying to inject store by initializes in my custom authenticator but it is note working. It throws error "Attempting to inject an unknown injection: store:main".
import CustomAuthenticator from '../authenticators/custom';
/import CustomAuthorizer from '../authorizers/custom';/
export function initialize(application) {
application.register('authenticator:custom', CustomAuthenticator);
application.inject('authenticator:custom', 'store', 'store:main');
}
export default {
name: 'authentication',
before:'ember-simple-auth',
after: 'store',
initialize: initialize
};

Instead of injecting the store in an initializer you should inject it explicitly in the custom authenticator's implementation:
// app/authenticators/custom.js
…
export default Base.extend({
  store: Ember.inject.service()
})

It looks like you're on an older Ember Data version though that doesn't define the store service.

Doesn't seem to be a problem with ESA.


Ref references need to not be copy local

Description
Trying to build a netstandard application using msbuild, FAKE and paket (yes, it seems it's doable, and not even that hard), I've run into the problem that reference assemblies are being copied to the output directory, which blows up at runtime (when the reference assemblies are loaded, you get an error saying this is a reference assembly basically).
Oh, and if it's not clear, what I'm calling reference assemblies is anything found in a nuget package under the "ref" folder (as opposed to the "lib" folder).
Repro steps
Add System.Runtime as a dependency.
Expected behavior
The ref package should be added as Private: false (Copy local: false, my limited understanding of MSBuild has lead me to believe that these are the same).
<When Condition="$(TargetFrameworkIdentifier) == '.NETStandard' And $(TargetFrameworkVersion) == 'v1.5'">
  <ItemGroup>
    <Reference Include="System.Runtime">
      <HintPath>..\..\packages\System.Runtime\ref\netstandard1.5\System.Runtime.dll</HintPath>
      <Private>False</Private>
      <Paket>True</Paket>
    </Reference>
  </ItemGroup>
</When>

Actual behavior
It's added such that it's copied to the output directory.
<When Condition="$(TargetFrameworkIdentifier) == '.NETStandard' And $(TargetFrameworkVersion) == 'v1.5'">
  <ItemGroup>
    <Reference Include="System.Runtime">
      <HintPath>..\..\packages\System.Runtime\ref\netstandard1.5\System.Runtime.dll</HintPath>
      <Private>True</Private>
      <Paket>True</Paket>
    </Reference>
  </ItemGroup>
</When>

Known workarounds
Manually fix msbuild file every time you do paket install.
Related information

Operating system: windows
Branch: not sure, I've done paket.bootstrapper and paket.bootstrapper prerelease
.NET Runtime, CoreCLR or Mono Version: .NET 4.6
Performance information, links to performance testing scripts: ?

For now this is the correct thing to do. In the future I think we need to analyse the runtime folder (see todo in my dotnetcore PR). This is because we might need to copy other files to the output directory (especially when compiling for netcoreapp). This is what the runtime.json is for (if I understood that correctly).
It doesn't matter for now as nobody is using fsproj to compile for netcoreapp and it's not recommended either. Exception is the new FAKE which is compiling scripts for netcoreapp and therefore needs this information :(

@matthid Actually, that's exactly what I was doing. I did a full day of experimenting to see if I could compile to .NETStandard using regular fsc, fake, msbuild and paket, just by slightly modifying the fsproj files. And it worked. I managed to produce dlls that were .NETStandard 1.3, meaning they should (in theory) run on .NET Core and .NET regular. The tests failed spectacularly though, cause paket was copying ref-assemblies and xunit was loading them (cause local dir has precedence over framework it would seem). Thus it blew up, and I made this issue.
As per my understanding, anything in the ref folder should be reference assemblies only. IE; it only contains metadata (method names, but no implementation). Though I don't know what runtime.json is.

Guys we already analyze runtime folder. And I think I set copylocal to false in recent commit

@forki what we do right now is not enough as we need to parse runtime.json and handle the runtime tree. For example if runtime.json says that 'run-a' includes 'run-b' we need to copy files from the 'run-b' folder to the output, even when we compile for 'run-a'. the runtime.json specifies the dependency tree.
for example 'win7-x64' includes 'win-x64' includes 'win' ... but we should threat the strings as black boxes, see https://docs.microsoft.com/en-us/dotnet/articles/core/rid-catalog
@Alxandr It only matters if you want to produce and run a netcoreapp application which should run on itself... For a netstandard library and simple usage of it we don't need that...
Note that my analysis might be wrong so please correct me in that case...

Hi,
This change seems to create another issue.
In a c# project in net45 We're using Microsoft.Extensions.Options.ConfigurationExtensions that use System.ComponentModel.TypeConverter that contains a ref folder. To run it, we needs the dll in the bin folder
Moreover we can't override it using copy_local:true
https://github.com/fsprojects/Paket/blob/master/src/Paket.Core/ProjectFile.fs#L644
let privateSettings =
                        if relativePath.Contains @"\ref\" then "False"
                        elif copyLocal then "True" else "False"

@evilz Yeah but copying the dll from the ref folder is still wrong. We need to copy the file from the lib folder (if at all).

Maybe always using the ref folder was not the correct thing for now (until we get that sorted out) :/

@matthid It's look that the files are exactly the same
PS P:\> cd O:\System.ComponentModel.TypeConverter.4.1.0\lib\net45
PS O:\System.ComponentModel.TypeConverter.4.1.0\lib\net45> Get-FileHash -Path .\System.ComponentModel.TypeConverter.dll

Algorithm       Hash                                                                   Path
---------       ----                                                                   ----
SHA256          0AD6A7017A54D99E102C17F40EA45D312AAEED96664EA5FF6DE1755BD4F6C6FD       O:\System.ComponentModel.Type...

PS O:\System.ComponentModel.TypeConverter.4.1.0\ref\net45> Get-FileHash -Path .\System.ComponentModel.TypeConverter.dll

Algorithm       Hash                                                                   Path
---------       ----                                                                   ----
SHA256          0AD6A7017A54D99E102C17F40EA45D312AAEED96664EA5FF6DE1755BD4F6C6FD       O:\System.ComponentModel.Type...

@evilz Maybe for this package. But I don't think they need to be the same in all situations...
IMHO "ref" stands for reference assemblies and might not contain any code (only API surface). Therefore they should never be copied to the output directory.

Can we just force the copy_local to copy the lib from lib folder ?
Is this a good quick fix ?

I think copying the binary from the lib folder is actually the correct fix. But it isn't a quick fix as we need to generate additional stuff into the project file...
A quick fix might be to ignore the ref folder for now. But that might break other people (for example me in FAKE)...

@evilz I changed it so that your manual changes are used. @matthid this is probably just a temporary fix

@forki thank ! I will test this next monday.


cdnjs outdated

Hello -
Great library. I see that cdnjs.com has this hosted and it is severely out of date (v1.5.3). I've looked at their update process, and it seems after 1.5.3 was tagged the compiled.min (signature_pad.min.js) version of the library was removed from this repo. Therefore it hasn't updated on cdnjs.
I thought about issuing a pull on cdnjs to update to your docs/js version of signature_pad.umd.js, but that seems like a hack.
Is there a possibility this could be resolved somehow?
Here is the settings file for cdnjs (https://github.com/cdnjs/packages/blob/master/packages/s/signature_pad.json).

If there is a way to serve the file from npm you can use the dist/signature_pad.umd.min.js file.

Due to a white listed network, we allow self hosted or cdnjs. We'll self host it, but the reason I wrote this is, cdnjs is really out of date. It would seem better to remove it, than have such old libraries being used.
If the docs/js/signature_pad.umd.js was updated as part of the build the cdnjs settings could grab it.

I meant to serve from cdnjs from npm instead of a git repo. It looks like type is set to "git" but maybe it could be "npm"?

It seems like OP fixed this themselves in https://github.com/cdnjs/packages/pull/1087, so think this can be closed now

I did update cdnjs, but it looks like someone changed my pull and the map files are missing from the cdn. :-1:
I was awaiting for cdnjs to update, which it looks like it updated. I'll re-pull and update the mask again to include the map files, unless someone else wants to.

I'll re-pull and update the mask again to include the map files

Looks like this was completed in https://github.com/cdnjs/packages/pull/1106


Bug: Cannot set global plugins with shallowMount

Expected behavior
Global components should be registered in plugins and stubbed as other children using shallowMount/shallow: true
Current behavior
Project has registered global components as vue plugins (objects with install function).
ShallowMount with global.plugins throws next:
'TypeError: Cannot set property tagName of [object Element] which has only a getter'
whereas simple Mount works okay
To Reproduce
  function factory() {
    return shallowMount(Master, {
      global: {
        plugins: [LayoutPlugin],
      }
    })
  }

Related information

@vue/test-utils version: 2.0.0-rc.18
vue version: 3.1.5
ant-design-vue version: 2.2.8

@tsiotska Sorry for the delay, this issue slipt through my inbox
Did you find a solution?
I see that you're using a fairly old vue version. Did you try to update to the latest vue version (and of the other dependencies)?
If that does not work let me know and we'll investigate.

@cexbrayat Thank you for feedback.
I've made a reproduction with simple test case below
https://github.com/tsiotska/vue-test-utils-reproduction/blob/test-utils/1276/src/app.spec.js#L19
I updated  "vue" to"^3.2.33", "@vue/test-utils" to "2.0.0-rc.21" and critical error became just a warning. Plugin components started to be stubbed as well as other children with shallowMount, but there's no possibility to 'unstub' that component, if you do that it'll be completely removed

Hi @tsiotska
Sorry we took so long to get back to you.
I think what you're trying to do in this repro is not possible: shallowMount will stub everything, even if you pass false to a stub. So maybe you should use mount in that case.


Challenge: Fibonacci

What's going on here? I know Vlad started separate issue for Fibonacci by mistake, so you @JumongEric should complete your own and make a pull request

@JumongEric  you need to continue work on fibbonaci


Add jQuery 3.0.0 incompatibility note

Re. https://github.com/lemonmade/bigfoot/issues/54: this is just a temporary note in README.md while I'm spending time on a workaround. It'll be removed with a solution.

Thanks @lukasschwab!


zernike.arbitrary_basis still sometimes clips the edges of apertures

I ran across this when looking at the basis calculated for a square aperture:

This appears to be the result of using the wrong formula for the center of the array when calculating the padding for the aperture. The expression
padding = ( int(ceil((max_extent - shape[0] / 2.))), int(ceil((max_extent - shape[1] / 2.))) )

should be
padding = ( int(ceil((max_extent - (shape[0] - 1) / 2.))), int(ceil((max_extent - (shape[1] - 1) / 2.))) )

@mperrin pointed this error out when I submitted this code originally, and I thought I'd fixed this everywhere, but I apparently overlooked this one.
Opening a PR with the fix!

Fixed in #241.


Pass Hrp by reference

The Hrp type is a struct containing an 83 byte arary, as such it should be passed by reference (borrowed) not copied.

I feel like if it implements Copy then we ought to copy it. And if it's too big to pass by reference then we ought to remove Copy from it.
What threshold do you have in mind for copying by reference vs copy?

I feel like if it implements Copy then we ought to copy it. And if it's too big to pass by reference then we ought to remove Copy from it.

I thought a struct was Copy if all its fields were Copy irrespective of how big it is. Isn't Copy more about how cheap/expensive it is to do than about how big it is? Hrp is just an array so its cheap to copy but we still don't want to do so in every function call because its big, right? (Definition of "big" below.)

What threshold do you have in mind for copying by reference vs copy?

I had 32 bytes in mind, based on discussion a few years ago about passing hashes by copy.

I thought a struct was Copy if all its fields were Copy irrespective of how big it is.

You need to explicitly derive Copy, and if you don't want people to copy your structure, you shouldn't implement it. If some fields are non-Copy then you can't derive it, but you're never obilgated to derive it.
32 bytes seems a little small, though I could believe that that's roughly where the performance starts to equal out.
In this case though I don't think the performance benefit (if there is one) outweighs the loss of ergonomics. It's not like anybody would ever be manipulating Hrps in a tight loop.

I'm pretty much convinced but

It's not like anybody would ever be manipulating Hrps in a tight loop.

We don't store addresses on chain but does any software store them, I could imagine exchanges might. Would they ever need to loop over every [mainnet] address they have and call one of our function that takes an Hrp using the same hrp::BC variable.

I'm convinced. I'll change this to "remove pass-by-reference"

Regarding Copy, just forget that terrible name. What it should've been called is WillNotImplDrop. Then the decision is clear: if a type will never implement Drop it should be Copy.

@Kixunil it also shouldn't be Copy if it has state that we don't want the user to accidentally duplicate (e.g. iterators) or if it's massive (e.g. contains 20 fields which are all 100-byte arrays). In these cases the name Copy seems to give the right intuition.

The compiler will produce exactly the same amount of memcpy calls with Copy or without it. I

If Copy is missing then users will be forced to pass-by-reference in most cases.

Which will also produce memcpy calls whenever they need owned value inside the function.
I think this is not something for libraries to decide, it's better to have lints and such if any actual performance benefit can be identified.

You can't get an owned value from a borrow of a non-Copy type.

I think this is not something for libraries to decide,

I believe we're only making this decision for our own internal code. And for our public APIs we have to decide whether to take a value by reference or by value.

You can if it's Clone, which does memcpy underneath for types with derived Clone that could've been Copy.

I believe we're only making this decision for our own internal code.

I'd be fine with this.


[multimodal] Fix mmcv reference if import failed

Error message that guide user to install mmcv won't print before this fix.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Before this fix, what would happen if mmcv is not installed?

The mmcv will not be imported when we init the dataset and the error will raise for the line model_config: mmcv.utils.config.Config,.

CI is not passed.

Fixed. It was because the import code was wrong.


Admin: Send Custom Mail Preview to Self

When admin creates a mail and would like to send it, it would be nicer if we could test send a mail to admin first. This is necessary because sometimes mails turn out unexpected and doesn't match the preview mail shown.
Describe the solution you'd like
Along with edit and send, a send to self option is desirable.
page: http://localhost:3000/custom_mails/1

Are you working on this? (Yes/No)
No

I think adding a button Send to self
https://github.com/CircuitVerse/CircuitVerse/blob/2898a70401ae1d7521a9e8c51347ec9710a74bdf/app/views/custom_mails/show.html.erb#L5
and adding a simple user_mailer to self can do the trick


how to add lenses or remove lenses?

@ps6067966 The lenses are added or removed from the snap dashboard. If you want to show a specific set of lenses then you can setup multiple lenses groups.


test harsh bot

Note: Providing complete information in the most concise form is the best way to get help. This issue template serves as the checklist for essential information to most of the technical issues and bug reports. For non-technical issues and feature requests, feel free to present the information in what you believe is the best form.
For Q & A and discussion, please start a discussion thread at https://discuss.mxnet.io
Description
(Brief description of the problem in no more than 2 sentences.)
Environment info (Required)
What to do:
1. Download the diagnosis script from https://raw.githubusercontent.com/apache/incubator-mxnet/master/tools/diagnose.py
2. Run the script using `python diagnose.py` and paste its output here.

Package used (Python/R/Scala/Julia):
(I'm using ...)
For Scala user, please provide:

Java version: (java -version)
Maven version: (mvn -version)
Scala runtime if applicable: (scala -version)

For R user, please provide R sessionInfo():
Build info (Required if built from source)
Compiler (gcc/clang/mingw/visual studio):
MXNet commit hash:
(Paste the output of git rev-parse HEAD here.)
Build config:
(Paste the content of config.mk, or the build command.)
Error Message:
(Paste the complete error message, including stack trace.)
Minimum reproducible example
(If you are using your own code, please provide a short script that reproduces the error. Otherwise, please provide link to the existing example.)
Steps to reproduce
(Paste the commands you ran that produced the error.)

What have you tried to solve it?

@mxnet-label-bot add [bug, duplicate]

@mxnet-label-bot, remove [bug]

@mxnet-label-bot, update [bug, duplicate]

@mxnet-label-bot, remove [duplicate]

@mxnet-label-bot, remove [bug, duplicate]

@mxnet-label-bot remove [bug]

@mxnet-label-bot update [question, bug]


pypi release

Hi,
it would be nice to have this available on PyPI so that we could install simply with pip install sentry_mattermost and update it automatically when a new version is released.
Since you have already a working setup.py, if you have a PyPI account you should be able to publish it simply with:
python setup.py register
python setup.py sdist upload

Thanks

Hi @mtorromeo, thanks for reporting this. I just uploaded the package to Pypi :)
https://pypi.python.org/pypi/sentry_mattermost


No compilation error on a weird line.

Hi,
I have this line wich by mistake took from a javascript code buit forgot to add "="
public require: "ngModel";
It compiles ok (Im pretty sure it should not), and the line is not in the corresponding .js!
Is it a Eclipse plugin bug or a TypeScript? Is there a way to configure the plugin to show those errors?
Thanks.

I believe this is controlled by TypeScript itself. The Eclipse plugin doesn't really dig into the contents of the source files directly.


Update to MRTK v2.7.3

Also adds a "_dev" suffix to the version string in WorldLockingManager to distinguish between a snapshot release (no "_dev") and a prerelease in ongoing development (with "_dev").

/azp run


Debugger Environment Variables Bleed Between Extension Host Launch Configs

VSCode Version: 1.51.1
OS Version: Windows 10

launch.json:
{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Run Extension A",
      "type": "extensionHost",
      "request": "launch",
      "args": [
        "--extensionDevelopmentPath=${workspaceFolder}"
      ],
      "outFiles": [
        "${workspaceFolder}/out/**/*.js"
      ],
      "preLaunchTask": "${defaultBuildTask}"
    },
    {
      "name": "Run Extension B",
      "type": "extensionHost",
      "request": "launch",
      "args": [
        "--extensionDevelopmentPath=${workspaceFolder}"
      ],
      "outFiles": [
        "${workspaceFolder}/out/**/*.js"
      ],
      "env": {
        "FOO": "BAR"
      },
      "preLaunchTask": "${defaultBuildTask}"
    }
  ]
}

Steps to Reproduce:

Use the above launch.json to debug an extension
Use "Run Extension A", observe that process.env.FOO is undefined. End debugger.
Use "Run Extension B", observe that process.env.FOO is defined. End debugger.
Use "Run Extension A" again, observe that process.env.FOO is still defined, when that's unexpected.

It seems that the environment variables are being set in a persistent way, so once it is set in one configuration, it will also be set when another is run. Unsetting them by using null has no effect, so it's likely at a level below that. My only work around is to set it on both configurations with different values.

Does this issue occur when all extensions are disabled?: Yes/No

/duplicate #83187

Ugh, I did try searching first. Sorry about that.

@dsanders11 no problem.


Style bug: Charts - space around circle nodes missing

Describe the bug
A styling issue was introduced in 4.5.0 where the clear space around the circle nodes on line charts is either missing or only partial, which is going to cause us a11y issues.
Screenshot of styling bug

To Reproduce
Steps to reproduce the behavior:

Go to Storybook or Docs (4.5 or 4.6) and look at any of the charts based on lines, such as Line and Area
Notice that the space around the circles that gives them visual separation is only kind of visible on the right side
Also notice that if you hover over a circle node, it fixes itself.
To see the correct styling you can go to Docs 4.4

Expected behavior

There isn't a white border on the circles with Safari 18

I tested as well, and the only issue I found was the same Safari issue Chris pointed out.

In our case, Safari doesn't support filter: drop-shadow, so we decided to leave it as it is until Safari updates/Other solutions.


Read Only

I have my Aggregate Result Fields set to Read Only yet it seems all users are able to edit these fields.  Can you help by telling me what I am doing wrong?

Hi @Stephen-J-Russell - the best place for support is generally the DLRS Community at https://trailhead.salesforce.com/trailblazer-community/groups/0F9300000009O5pCAE?tab=discussion, but I can try to help you here as well.
For the fields in which you're storing your aggregate result, are you marking them as Read-Only on the page layout or in the User Profiles?

@Stephen-J-Russell can you provide some details. Are you talking about the field that is the result field on the parent object, or the field that actually lives on the DLRS configuration object?
DLRS is setup to write to the Parent's field no matter the user's permissions. It can be setup to respect sharing settings if desired.
If DLRS refused to update the parent depending on a user's settings then the field would fall out of sync with the actual data.
If you'd like to avoid users being able to cause writes to a parent's field then you'll need to use the Scheduled or Scheduled Full Calculate modes instead of Realtime and the Scheduled Apex should. be run as a user with the proper access.
If there is something else happening and I've totally missed the mark please feel free to clarify for me and we can go from there.


Showcase - Have Bot Create Thread for Each Post

Per user/mod suggestion, it would be a nice-to-have for the bot to start a thread for each showcase embed. Users/mods cannot start threads but the bot is able to which could foster conversation around postings.

Do you mean a thread in the showcase channel, or a thread where the showcase was posted? Would it be thread-overload if every showcase had a thread?

IIRC correctly the idea was for every showcase image to have a thread in the showcase channel as the bot was the only one capable of doing so. I believe they auto archive after 24hours so I dont think it would get too crazy under normal circumstances and should clean itself up after initial interest dies off. However, I dont know enough about threads so not 100%- I know they'll get auto archived but im not sure if they stick around in an archived status for perpetuity that could be revived at any point. I didn't really weigh the merits of this one, i just offered to submit the issue to GH on a mods behalf who otherwise couldnt.

If this would lead to a large list of archived threads then yeah I would agree that would definitely be overkill and could see that causing issues potentially

What if each showcase message had a button that people could press to "Start Discussion". This button would open the thread on the showcase post and disable the button. We could also move the Original Message field on the embed to a link button

I just tried creating a thread in the showcase channel and I was able to, so it would seem like this isn't necessary?

Yeah I agree this seems unnecessary, going to close this one out.


Broadlink rm2 fails after upgrade to 0.67

Using HASS.io with raspberry pi 3+ and upgraded to HASS.io 0.67 and now the broadlink rm2 doesn’t seem to work?
Worked perfectly for all previous versions of the application :(

Duplicate of #13799 fixed in #13906


pass props from CoreLayout to Nav or Main component

Hello,
I done tutorial from reactjs.co related to add session props to my app. Now I am still developing my app and I have new requirements. What i want to do is to pass props from my CoreLayout to for example Nav or Main Conatainer
let's say that's my code of CoreLayout.js
class CoreLayout extends Component = {
return (

{this.props.children}

)
}
I want to do in correct way.
What I tried to do is to create CoreLayoutContainer but I am stucked with
Invariant Violation: The root route must render a single element
in this situation my code is similar to normal Containers with reducers
so container file, index.js file is similar to others container and index.js. Main changes is in index.js of all routes I included there index.js of CoreLayout and try change component: CoreLayout to component: CoreLayout(store) but this no works and as I said I stucked with previously mentioned error
I hope you can help me :)
Best Regards,
Cezary

Invariant Violation: The root route must render a single element
it will be better if you show us more of your code


Devel

Vignette is a Vignette which is able to run, referenced in the package's website.

Merging.


chore(protocol): fix a performance issue

makes driver 4.6 times faster
test:
const times: number[] = [];

for (let i = 0; i < 100; i++) {
  const t0 = performance.now();
  const result = await col.find({}).toArray();
  const t1 = performance.now();
  assertEquals(result.length, 494); // just to make sure all docs received
  times.push(t1 - t0);
}

const avg = times.reduce((a, b) => a + b, 0) / times.length;

console.log(took ${avg} ms);

before result: took 42.91281719999999 ms
after result: took 9.241063190000006 ms
nodejs result: 6.83 ms

Nice work!

@manyuanrong It's a good time for a new release (i think we don't have any breaking changes)


Setting lowest limits under Performance Settings crashes the project on load

Godot version
3.5 stable
System information
Garuda Linux, 5900HX, 6800M
Issue description
My project was very slow on HTML export on tablets so I set all the limits on the lowest possible values under Performance settings and now I'm unable to even load the project. It crashes on load.
Steps to reproduce
Set all the limits to the lowest value under Performance Settings. The project will crash and it will crash on load on every subsequent effort to open it.
Minimal reproduction project
Unfortunately I can't provide the project because it's for a company. The default scene though is all 2D and consist of 2 images, 3 buttons and 3 labels.

Set all the limits to the lowest value under Performance Settings. The project will crash and it will crash on load on every subsequent effort to open it.

Which settings did you decrease, and to which values?

I changed these 3 from:
limits/multithreaded_server/rid_pool_prealloc=0
limits/message_queue/max_size_kb=1024
limits/command_queue/multithreading_queue_size_kb=1

to
limits/multithreaded_server/rid_pool_prealloc=1
limits/message_queue/max_size_kb=65536
limits/command_queue/multithreading_queue_size_kb=16

and now the project opens.
Can I get any advice on how I can make my completely 2D project runs adequately on tablets?

Can I get any advice on how I can make my completely 2D project runs adequately on tablets?

Try rendering at a lower resolution by setting the stretch mode to 2d and setting the Shrink option to 2 (or even 3). This will make 2D elements larger, so you'll have to compensate for this by making text smaller and reducing camera zoom.
Other than that, there isn't much to do – most Android tablets are firmly in the low-end space, and the HTML5 export comes with significant overhead that a native Android export doesn't have to deal with.


Collections from publishComposite no longer reactive in Meteor 1.2.1?

Hello,
I see that publish-composite latest is as of 0.9.0. I am on 1.2.1 and can confirm that collections published with Meteor.publishComposite are no longer reactive. Is there any updates coming in the near future for 1.2.1 support?

+1

Working here.

works great for me as well.

Yes, I actually had some flawed logic that was getting in the way. Sorry for the false alarm.


Roll20 Changes (pm 2021-03-30) broke roll templates on Shadowrun Sixth World sheet AND some translations.

Quite a bit of data collection has been posted on the official Character Sheet Enhancements thread on the forums starting here: https://app.roll20.net/forum/post/9883156/character-sheet-enhancements/?pageforid=9950454#post-9950454

And broken again 3 hours later.  Please merge my pull-request that fixes this temporarily so the players can use the character sheet and enjoy their games over the long holiday weekend.


feat: disable chatwoot errywhere

Description
Chatwoot isn't quote ready for primetime - issues were found on mobile.
This PR just undoes what https://github.com/shapeshift/web/pull/4739 did.
Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A
Risk
Almost literally 0.
Testing
N/A
Engineering
N/A
Operations
N/A
Screenshots (if applicable)
N/A

Current dependencies on/for this PR:

develop

PR #4746   👈

This comment was auto-generated by Graphite.


Fix FileHandleGenerator inside HiveConnector

A recent refactor https://github.com/facebookincubator/velox/pull/7725 missed passing the connector config
to the FileHandleGenerator in the HiveConnector.

@mbasmanova can you please help review this? This fixes a regression.

@majetideepak CI is failing:
The following tests FAILED:
        289 - velox_s3read_test (Timeout)

Thanks. Would you confirm that the new tests fails without the fix?

Yes, I confirmed the test fails without the fix.

@mbasmanova the test is now passing. Thanks!


Email templates should be taken from defined  frontend theme(s)

With cascading themes it's easy to set up different shops with one code base and several sub themes for each installation.
When putting email templates in /themes/, they're not recognised when emails are sent from the backend, e.g. Order_StatusEmail.ss
IMHO sending emails should switch to the defined frontend theme, send the email and switch back for each email.
When email templates are in app/templates, this should still overrule themes' templates.

fixed by #799


Ignore lines that start with : ping

When testing the client with streaming chat, I noticed the JSON parser crashes for lines that start at with ": ping", I believe its because the api sends chunks with event: ping which needs to be ignored

I I didn't notice such a thing before. Do you think this is new behavior? Do you have any sample code or prompt?

I I didn't notice such a thing before. Do you think this is new behavior? Do you have any sample code or prompt?

I was using the client with text-generation-webui openai plugin  and noticed the crash. Then I checked the official python implementation from openai and saw the ping messages in their src/test_streaming.py

I have made some updates. I thought that maybe someone might find this data useful, so I kept it as optional.
Could you test my implementation to see if it helps? I couldn't test it because I don't have any prompts to trigger pings. I would greatly appreciate it if you could share one with me.


我的机器无法连接到huggingface，但是下载了离线clip-vit无法使用

我修改了文件 vim /root/.cache/huggingface/modules/transformers_modules/build_mlp.py 并且将vision_tower = 'openai/clip-vit-large-patch14-336' 替换为了本地路径，但是再次执行就被重写覆盖了

You may replace the model = AutoModel.from_pretrained('internlm/internlm-xcomposer2-4khd-7b') with model = AutoModel.from_pretrained('xxx'), where xxx is your local model path.

You may (1) download the HF repo into your local path, (2) modify the build_mlp.py and (3)replace the model = AutoModel.from_pretrained('internlm/internlm-xcomposer2-4khd-7b') with model = AutoModel.from_pretrained('xxx'), where xxx is your local model path.您可以（1）将 HF 仓库下载到本地路径，（2）修改 build_mlp.py，并（3）将 model = AutoModel.from_pretrained('internlm/internlm-xcomposer2-4khd-7b') 替换为 model = AutoModel.from_pretrained('xxx') ，其中 xxx 是您的本地模型路径。

我指的是openai/clip-vit-large-patch14-336，我在运行internlm-xcomposer2-vl-7b报错了
raise EnvironmentError(
OSError: We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like openai/clip-vit-large-patch14-336 is not the path to a directory containing a file named config.json.
Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/transformers/installation#offline-mode'.

Please down the xcomposer2-vl-7b HF repo into your local path, otherwise, your modification will be overwritten.

Please download the xcomposer2-vl-7b HF repo into your local path, otherwise, your modification will be overwritten.请将 xcomposer2-vl-7b HF 仓库下载到您的本地路径，否则，您的修改将被覆盖。

是的，做上述操作之前我已经下载到了本地路径..

Please download the xcomposer2-vl-7b HF repo into your local path, otherwise, your modification will be overwritten.请将 xcomposer2-vl-7b HF 仓库下载到您的本地路径，否则，您的修改将被覆盖。

依旧会被覆盖，我也尝试了用LMDeploy 部署，依旧失败

请将 xcomposer2-vl-7b HF 仓库下载到您的本地路径，否则，您的修改将被覆盖。

依旧会被覆盖，我也尝试了用LMDeploy 部署，依旧失败

请问这个问题解决了吗

一样的问题，.cache/huggingface/modules/transformers_modules/build_mlp.py文件每次运行时候会刷新，导致无法从local加载openai/clip-vit-large-patch14-336
有人解决了吗

您好，您的邮件我已收到，我将尽快查看！This is an automatic reply, confirming that your e-mail was received. Thank you

您好，您的邮件我已收到，我将尽快查看！This is an automatic reply, confirming that your e-mail was received. Thank you

Just remove the huggingface dir in .cache, rectify the script in local path and run the code from scratch.

一样的问题，.cache/huggingface/modules/transformers_modules/build_mlp.py文件每次运行时候会刷新，导致无法从local加载openai/clip-vit-large-patch14-336 有人解决了吗

您好，您的邮件我已收到，我将尽快查看！This is an automatic reply, confirming that your e-mail was received. Thank you


[PE-D][Tester C] Search command duplicate prefixes does not work

Before:

After:

Search commands with duplicate prefixes for name seem to always fail since the search commands appears to only display users that match all prefixes.
Perhaps one way to fix this would be to not allow duplicate prefixes for name. Another possible fix is to have the search feature return users that match any of the criteria similar to AB3's find feature (i.e. the example shown in the image above should return Bernice Yu and David Li).

Labels: type.FunctionalityBug severity.Low
original: jingjie88/ped#13

Intended behavior. Agree that it should be limited to one name per search if this is the case.


std.range.flatten

bearophile_hugs reported this on 2014-02-02T08:53:12Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=12062
CC List

greeenify
greensunny12
jack (@JackStouffer)
jens.k.mueller

Description
I suggest to add to std.range a range designed to flatten a given n-dimensional range.

A simple usage example:

int[][] mat = [[1, 2], [3, 4]];
auto mu = mat.flatten.uniq;

std.range.flatten should take a range, range of ranges, range of range of ranges, etc, and yield the scanned items.

A possible signature:

Flatten flatten(ScanType scan = ScanType.rows(), Range, Targs...)(Range input, int maxDepth=-1, Targs args);

Where maxDepth tells it a what depth to stop, defaulting to -1 that means to reach the bottom.

ScanType can be:

enum ScanType {
    rows,
    columns,
    bidirectionalRows,
    bidirectionalColumns,
}

Later more scans can be added:

enum ScanType {
    rows,
    columns,
    bidirectionalRows,
    bidirectionalColumns,
    zigZag,
    hammingCurve,
    zCurve,
    rectBlocked
}

args is used by ScanArgs.rectBlocked, to specify the nx and ny of a 2D block. The blocked scan is useful because it's a cache-friendly scan for large 2D arrays.

Ideally flatten should yield references of the items, so you can increase all matrix items by 1 with code like:

int[][][] mat = [[[1, 2], [3, 4]], [[5, 6], [7, 8]]];
foreach (ref x; mat.flatten)
    x++;

greeenify commented on 2016-12-27T10:39:08Z
I guess it's not well known, but `joiner` without arguments behaves like `flatten`:

https://dlang.org/phobos/std_algorithm_iteration.html#.joiner

It just flattens one dimensions though.

greeenify commented on 2016-12-27T10:39:32Z
(sorry didn't mean to close this)

jack (@JackStouffer) commented on 2016-01-18T06:40:45Z
This can be superseded by using std.experimental.ndslice and byElement

greensunny12 commented on 2016-08-30T01:23:02Z
> This can be superseded by using std.experimental.ndslice and byElement

nslice only works on RandomAccesRanges, so I believe this is still a valid request.


SUTD Scratch!

Name of Student Organisation*
SUTD Scratch!
Cluster
Arts
Classification
Fifth Row
Description
SUTD Scratch is a community filled with people with a passion for sound and music.
We learn to mix tracks across multiple genres and put our skills to the test to liven up school, private and external events.
The club aims to cultivate aspiring DJs who have a passion for mixing music, regardless of skill level. We hope to create a space for students who have an interest in DJing to come together and enjoy different genres of music.
Join us and scratch your music itch today :D
Training / Meeting Timings
Wednesdays and Fridays 19.30 - 22.00
Student Organisation Introduction Video
[If applicable, Insert Youtube link to your introduction video here]
Name / Contact of President
Aaron Soares @cargofast
Other Relevant Links
Telegram group: https://t.me/joinchat/DgT-PSyMIrQ0MDE1
Instagram: @sutdscratch

hi, we will follow up with the intro video link ASAP :)

Hi there! @FolkLoreee thanks for submitting the event on github.
May we know what is the location of the training event or is it mostly online?

hi @ExtremelySunnyYK. I've updated the issue with our training location. Thanks!


[#3824] improvement(client-python): Support generating pydoc from client-python code

What changes were proposed in this pull request?

Use pydoc to generate docs
Add Gradle task doc to generate docs (it will create a docs folder and generate all doc html files in it)

Why are the changes needed?
Fix: #3824
Does this PR introduce any user-facing change?
No
How was this patch tested?
./gradlew clients:client-python:test

Hi @noidname01 can you please post some screenshots about the generated pydoc?

Hi @noidname01 can you please post some screenshots about the generated pydoc?

Hi @jerryshao, I have uploaded some screenshots of generated doc html above.


1 test fails

Describe the bug
========================================================================================= FAILURES ==========================================================================================
_________________________________________________________________________________ test_merge_large_midifile _________________________________________________________________________________

    def test_merge_large_midifile():
        mid = mido.MidiFile()
        for k in range(5):
            t = mido.MidiTrack()
            for _ in range(10000):
                t.append(mido.Message("note_on", note=72, time=1000 + 100 * k))
                t.append(mido.Message("note_off", note=72, time=500 + 100 * k))
            mid.tracks.append(t)

        # Add meta messages for testing.
        meta1 = mido.MetaMessage('track_name', name='Test Track 1')
        meta2 = mido.MetaMessage('track_name', name='Test Track 2')
        meta3 = mido.MetaMessage('time_signature',
                                 numerator=4,
                                 denominator=4,
                                 clocks_per_click=24,
                                 notated_32nd_notes_per_beat=8)
        unknown_meta = mido.UnknownMetaMessage(0x50, b'\x01\x02\x03')

        mid.tracks[0].insert(0, meta1)
        mid.tracks[1].insert(0, meta2)
        mid.tracks[2].insert(0, meta3)
        mid.tracks[3].insert(0, unknown_meta)

        start = time.time()
        merged = list(mido.merge_tracks(mid.tracks, skip_checks=True))
        finish = time.time()

        merged_duration_ticks = sum(msg.time for msg in merged)
        max_track_duration_ticks = max(
            sum(msg.time for msg in t) for t in mid.tracks)
        assert merged_duration_ticks == max_track_duration_ticks
>       assert (finish - start) < 3.0
E       assert<PHONE_NUMBER>.2717257 -<PHONE_NUMBER>.1018417) < 3.0

tests/midifiles/test_tracks.py:74: AssertionError
============================================================================== 1 failed, 121 passed in 14.11s ===============================================================================

To Reproduce
Regular PyTest run.
Context (please complete the following information):

Operating system name & version: FreeBSD 14.1
Python version: 3.11
mido package version: 1.3.3

Additional context
FreeBSD port.

The failing assertion is a little weird since it's testing that mido.merge_tracks runs in under 3 seconds for this scenario.  That duration will vary from machine to machine, so it's really an assertion about the machine running mido, not mido itself. I'd recommend just removing the assertion for that reason.
That said... it does look like there might be opportunity to make the code for mido.merge_tracks more efficient. Right now it's gluing each track's messages together end-to-end in a single list, and then sorting all of the messages in that list by their start time. So if you have 16 tracks, track 16's first message will be towards the end of a long list, and sort has to do quite a lot of work.
Seems like there's probably a better way to create the merged+sorted list, since the messages for each individual track are presumably already sorted by time. Any CS students out there who are currently taking an algorithms class? Lol

A quick consultation with ChatGPT suggests that what might be needed here is a k-way merge algorithm:

In computer science, k-way merge algorithms or multiway merges are a specific type of sequence merge algorithms that specialize in taking in k sorted lists and merging them into a single sorted list


Node Pressure Eviction threshold

Hi,
I am new to k3s and I was going through the document and saw the concept ' Node Pressure Eviction '.
I wanted to carry out this use case for my basic setup - One Master, One Agent.
Use-Case:
What I wanted to carry out was that if the Memory(RAM) goes below a certain threshold then I want my pods to be evicted from the node and then gets scheduled to other available node. I read about 'Hard Eviction'  and wanted to implement the same. But I a, struggling with some basic issue.
Issue I am struggling with

I am not able to manipulate or change the Threshold for eviction. I understand kubelet has a role to play but installing k3s doesnt come with kubelet service.

When I am filling up my system with grabage RAM, I could see all the pods are evicting from the node even the system critical and they are getting scheduled on the same.

Help I am looking for

Is there any way I can carry out the use case in k3s.
How can I change the hard eviction threshold.
Any other alternative way.

installing k3s doesnt come with kubelet service.

The kubelet is built in to k3s, and is run as a subprocess of the k3s supervisor process. You can tune pass arguments through to the kubelet via the --kubelet-arg flag.
Documentation references:

https://rancher.com/docs/k3s/latest/en/installation/install-options/server-config/#customized-flags-for-kubernetes-processes
https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/

Hi brandon,
Thanks for the quick reply. Do we need to pass this --kubelet-arg=arg=value while installing k3s or we after installing we can run this as CLI.
If my understanding is correct then:
--kubelet-arg= memory.available<4Gb will ensure a eviction when the memory goes below 4Gb.
Also it would be better If you could help me with the complete command.
Thanks.

Also I read that CLI for kubelet has been depreciated and it is to be used with Config file. But I could not find anywhere the config file for the same.

The CLI args have been deprecated for ages and show no actual signs of going away; I would continue to use them.
You can pass it while installing k3s, or edit the systemd unit for k3s to add the args post-install, and then restart the service.

Hi Brandon,
Yes I was able to execute the kubelet configration which you mentioned above and it was working perfectly fine. I used to start the k3s server with those argument and it was working. But since I installed k3s with script instead of binary that option is not feasible. I'll try to check with the systemd file. That should work.

@brandond you can also set the args in the the KUBECONFIG.yaml, right?
kubelet-arg:
  - "eviction-hard=imagefs.available<case>,memory.available<case>,nodefs.available<case>,nodefs.inodesFree<case>"


Storage Group helpers

SDK should support some common functionality for Storage Group creation. Currently, it is only implemented in neofs-node repository and is used only in CLI but the new clients are expected.
Should be implemented in that repo:

Storage group creation. Input: CID, members, SDK client (or that could be a method of the client); output: correct storage group that contains only physical objects members in the correct order.
Storage group validation: Input: CID of storage group: output: validation result (seems like bool is enough). Should check if the storage group has been build correctly according to 1. (see comments)

Do client applications outside neofs-node monorepository need to perform 2 op? I guess it's only needed for pre-store validation on storage nodes and within audit routine. If I'm correct I'd gather validation functionality in neofs-node (at least for now).

Do client applications outside neofs-node monorepository need to perform 2 op

Well, seems like no external use-cases for that, agree.

With just №1 left it duplicates #308.


Make a missing PID "unknown" rather than "error".

This likely indicates a badly configured Homebrew plist but it's something that should be exposed to Homebrew contributors rather than users who find it confusing. CC @antstorm for thoughts and code review.

Maybe it's worth adding a CLI option that would act similar to HOMEBREW_DEVELOPER flag in this context (since I'm not sure of the other side effects of setting HOMEBREW_DEVELOPER on the system). Otherwise looking good!

@antstorm Any suggestions for a name?

--debug / -d… or maybe --verbose / -v, since it actually gives a bit more verbose output

Let's leave it as-is for now but 👍 to having one of those flags output more debugging information.


[Waila] Power readings disappear on Thermal Expansion with EnderIO enabled

Having a slight problem with Waila tooltip showing the power readings on any Thermal Expansion items when I have EnderIO enabled, once disabled it works again.
Tried on a fresh 1.7.10 Minecraft install with:
Forge <IP_ADDRESS>7
CoFHCore-[1.7.10]3.0.0RC5-207
ThermalDynamics-[1.7.10]1.0.0RC5-94
ThermalExpansion-[1.7.10]4.0.0RC6-138
ThermalFoundation-[1.7.10]1.0.0RC4-58
Waila-1.5.9_1.7.10
EnderIO-1.7.10-<IP_ADDRESS>9
All the mods by TeamCOFH are release versions but also tested using latest alpha ones but still the same.

where did you get forge Forge <IP_ADDRESS>7 ?? the latest version that i can find is 1291 ,, it's probably something to do with Waila config EIO option appear in Waila config when installed try messing with those , or use a dev version of EIO and see if this problem still occur

This is fixed in dev builds.

Ahh thank you for ino tterrag1098
As for forge 6210classick I use MultiMC that can download any Forge version needed. If need to get it manually then they are located here http://files.minecraftforge.net/minecraftforge/1.7.10

@benten2000 You using wrong page to get Forge. The latest supported Forge for 1.7.10 is <IP_ADDRESS>1, <IP_ADDRESS>xx is usable for 1.8. It's a bit difficult, but the 1.7.10 branch is not contains the accepted Forge releases. Use http://files.minecraftforge.net/minecraftforge/ to determine available - and usable - Forge releases to avoid unexpected bugs.

Sorry but you're completely wrong. Forge master branch has moved to 1.8 so
any 1.7 releases are now on the 1.7.10 branch. His link is perfectly valid.
On Mar 11, 2015 4:32 AM, "Gabor Garami"<EMAIL_ADDRESS>wrote:

@benten2000 https://github.com/benten2000 You using wrong page to get
Forge. The latest supported Forge for 1.7.10 is <IP_ADDRESS>1, <IP_ADDRESS>xx
is usable for 1.8. It's a bit difficult, but the 1.7.10 branch is not
contains the accepted Forge releases. Use
http://files.minecraftforge.net/minecraftforge/ to determine available -
and usable - Forge releases to avoid unexpected bugs.
—
Reply to this email directly or view it on GitHub
https://github.com/CrazyPants/EnderIO/issues/2069#issuecomment-78222885.

And how stable these forge releases are? I heard some problems with these new forge and some mods. Is there any new big change that I should worry about?

If any mod has bugs with these versions it is their fault. Forge has not broken backwards compat in any way.


fix: remove failing npm audit and fix duplication

Implement Alec's feedback from this review: https://github.com/bcgov/digital_marketplace/pull/177 (fix CI running twice and remove npm audit)
The goal is to keep the main branch green

Related issue: https://github.com/button-inc/digital_marketplace/issues/10

Per our call, @BCerki will merge this (very first merge so no need to post in chat before doing so, but it never hurts to exercise the muscle)


sqs supports a max of 15 minutes of delay

to get more than that we'll need to write our own thing

I should've caught this in review