yarn.lock actual resolved version seems to be ignored by dependabot version range alert

Our yarn.lock file contains a number of references to the kind-of package including ^3.xx, ^4.x.x, ^5.x. and ^6.x.x versions.
There is a dependabot alert for versions >= 6.0.0, < 6.0.3
CVE-2019-20149
moderate severity
Vulnerable versions: >= 6.0.0, < 6.0.3
Patched version: 6.0.3
Our yarn.lock references to ^6.x.x look like this:
<EMAIL_ADDRESS><EMAIL_ADDRESS>  version "6.0.3"
  resolved "https://registry.yarnpkg.com/kind-of/-/kind-of-6.0.3.tgz#07c05034a6c349fa06e24fa35aa76db4580ce4dd"
  integrity sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==

i.e. it has resolved to version "6.0.3" already but we are still getting the alert

We shipped a lot of improvements to yarn over the past year. Is this still reproducible?

Closing due to lack of user response.
Also, this repo / issue tracker is about the code that creates PR's to bump versions--whether from cron or from security alerts--but not about the security alerts themselves. Versus this issue is about the alerts themselves, not the resulting PRs.
So if you're still seeing issues, I suggest starting a discussion over in https://github.com/community/community/discussions/categories/code-security as that's probably the best way to reach the team that handles alerts. Feel free to drop a breadcrumb link on this issue to the discussion.


Revert "Firecert 2080"

Reverts rdkcentral/firebolt-certification-suite#56

Coverity detected 4 issues; a security concern.


[Hue] - CDPD-32891 - Cloud Break Template change for QP

See detailed description in the commit message.

Could you please squash the commit into one, usually we use only 1 comment/1 PR

@Amlesh1902 we are going to close this PR, looks abandoned.


chore(manager): start using identity package

VULN4OS-175
Secure Coding Practices Checklist GitHub Link

https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

[x] Input Validation
[x] Output Encoding
[x] Authentication and Password Management
[x] Session Management
[x] Access Control
[x] Cryptographic Practices
[x] Error Handling and Logging
[x] Data Protection
[x] Communication Security
[x] System Configuration
[x] Database Security
[x] File Management
[x] Memory Management
[x] General Coding Practices

Codecov Report
Base: 37.29% // Head: 37.29% // No change to project coverage :thumbsup:

Coverage data is based on head (e8d7b81) compared to base (9ac4a9a).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #141   +/-   ##
=======================================
  Coverage   37.29%   37.29%
=======================================
  Files          35       35
  Lines        2263     2263
=======================================
  Hits          844      844
  Misses       1300     1300
  Partials      119      119

Flag
Coverage Δ

unittests
37.29% <ø> (ø)

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

Impacted Files
Coverage Δ

manager/middlewares/authenticator.go
67.39% <ø> (ø)

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

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


McStas data loader and minimal data reduction as an example.

Related to #6.

@Justin-Bergmann
We have a couple of questions for you about this McStas loader...!
Will you ever need non-grouped data?
If not, we will just always group them into pixel IDs when you load a file.
Are p_x_y_n_id_t these variables always in the McStas simulation?
We would like to know what's the minimum requirements of NMX McStas simulation data event list name.
For example, if the event data path in the h5 file entry1/data/bank01_events_dat_list_p_x_y_n_id_t must contain at least p id t .
And we're going to hard-code the translation of each field, for example p is always weights.
So please let us know if the names might change in the McStas files...!

@Justin-Bergmann
We have a couple of questions for you about this McStas loader...!
Will you ever need non-grouped data?
If not, we will just always group them into pixel IDs when you load a file.
Are p_x_y_n_id_t these variables always in the McStas simulation?
We would like to know what's the minimum requirements of NMX McStas simulation data event list name. For example, if the event data path in the h5 file entry1/data/bank01_events_dat_list_p_x_y_n_id_t must contain at least p id t .
And we're going to hard-code the translation of each field, for example p is always weights. So please let us know if the names might change in the McStas files...!

Spontaneously, I can not imagine any situation where we would use non-grouped data and we still have all information available. So please go ahead.
Yes, each simulation must contain p, id and t and as far as I know  all p_x_y_n_id_t are always in the simulation
The names will never change as long its not changed in the code itself


Color conversion

Added a bunch of code to convert from/to different color formats.

There's a lot of tabs vs 3 spaces issues in this PR.

Ok that should be all of them :) sorry about that!

Thank you! I'm going to review this soon! I close this PR as a duplicate of all-in-one PR: #1334


reduce public API (rebased #61)

I merged master into #61 and fixed the conflicts

remove extra whitespace in expected &strs in test_quotations()
refactor split_constant_and_expr() to being an implementation of LpExpression, working on &self
refactored to have an LpExprArena, still needs reorganizing around it
mostly compiling code, only macros in dsl/operations.rs are non-functional, as they would have to take expr_arena as an extra argument that basic std::ops like Sub cannot
remove operations.rs submodule
version of Add, Sub, Mul implementations, just not working...
Revert "remove operations.rs submodule"
compiling version with Add, Sub and Mul implemented for LpExprArena
make sum and lp_sum work on Into instead of Into
most bugs should be fixed by testing, now
all warnings removed, extra match case in split_off_constant
tests all passing, code should be debugged -- yay!
refactor some LpExprArena functions for consistency and comprehension
refactor LpExpression to LpExprNode and LpExprArena to LpExpression; adapt native_cbc.rs to new architecture
debug compilation with --features "native_coin_cbc"
remove println()s used for debugging
restrict most LpExpression functions to pub(crate), move respective tests from tests/expression.rs and tests/quote.rs to test mod in variables.rs
remove unused if let statement
mark LpExpression::build() as only being used in tests
remove unused function LpExprNode::normalize()
make LpExpression::new() private to the module
make LpExpression::set_root_index() private to module
make LpExpression::push_as_expr() private to module variables.rs
make LpExpression::clone_expr_at_and_push() private to module variables.rs
make LpExpression::overwrite_expr_at() private to module variables.rs
make LpExpression::expr_clone_at() private to module variables.rs
remove LpExpression::get_root_expr() that was only used once and was a one-liner
make LpExpression::push_arena_at_root() private to module variables.rs
make LpExpression::clone_subtree_at_index_and_push() private to module variables.rs
move LpExpression::var_lit() back to native_cbc.rs, as that's the only place it is used
Add support for minilp
Add missing feature gate
Run tests with the minilp feature
Update README.md

I tried to add a test to see if it fixes #37, but it looks like it doesn't :
    #[test]
    fn simplify_deep_sum() {
        let count = 1000;
        let vars: Vec<LpExpression> = (0..count)
            .map(|i|
                &LpInteger::new(&format!("v{}", i)) * 2 + 1
            )
            .collect();

        let mut sum = lp_sum(&vars);
        let c = sum.simplify().split_off_constant();
        assert_eq!(c, count as f32);
    }

So it looks like it signicantly increases complexity, without fixing the initial issue :/

It looks like simplify repetitively calls show, which is a recursive function that allocates a large string !

@dlaehnemann @jcavat : I removed the recursivity in Show. It is still super slow (allocating a ton of strings during simplify is not a good idea), but at least it works now, it does not throw a stack error.

Great job guys! I merge and wait few days before upgrading to version 0.4.4 (or 0.5.0). (I will be off next week)


District Boundary Lookup API Call causes Django error on openstates.org site

Hello,
While trying to visualize API method calls manually, I found that the boundary lookup URL causes an error.
Error causing call:
http://openstates.org/api/v1/districts/boundary/sldl/nc-120/?apikey=ThisWasAKnownGoodKey
Result:
Piston/0.2.3rc1 (Django 1.6.2) crash report: Traceback (most recent call last): File "/projects/openstates/virt/src/billy/billy/web/api/handlers.py", line 89, in new_read obj = old_read(*args, **kwargs) File "/projects/openstates/virt/src/billy/billy/web/api/handlers.py", line 508, in read resp = rc.NOT_FOUND File "/projects/openstates/virt/src/django-piston/piston/utils.py", line 55, in __getattr__ class HttpResponseWrapper(HttpResponse): File "/projects/openstates/virt/src/django-piston/piston/utils.py", line 82, in HttpResponseWrapper content = property(HttpResponse._get_content, _set_content) AttributeError: type object 'HttpResponse' has no attribute '_get_content'

Yeah, this is the same as #248 - should be set in a few hours when I redeploy
Thanks!

@paultag Sorry for the dupe.  I appreciate your efforts.

Hey man, no worries! Thanks for the report!


Add files via upload

Working on a transliterative en-US|intl. (au français, lol) intelligence agent, assistant, and native Android OS push chat partner.

Merge | fork of the Google Remote Procedure Call gRPC master repository committed, checks cleared, Developer Actions Project made, and first milestone project attainment achieve (ru: lol). Here's to a transliterative intelligent Google Assistant add-on!


Add context propagation support

In the current implementation, weaver doesn't allow the user to propagate context information. We recommend users to define a struct that encapsulates the metadata information and add it as an argument to the method. However, more and more users are asking for an option to propagate metadata information using the context. This request comes especially from users that are using gRPC to communicate between their services, and gRPC provides a way to propagate metadata information using the context.
This PR implements a similar approach to gRPC [1] to propagate metadata information. We allow users to create a context where they can pass metadata as a map[string][]string.
E.g.,
...
ctx := context.Background()
meta := metadata.New(map[string][]string{"name":{"foo", "bar"}})
ctx = metadata.NewContext(ctx, meta)

dst.Get().Update(ctx, ....)

...
func( d *destination) Update(ctx, ...) (error) {
  meta := metadata.FromContext(ctx)
  vals := meta.Get("name")

  // Can call another component method with an updated context
  meta.Set("account", "x", "y")
  ctx = metadata.NewContext(ctx, meta)
  acct.Get().UpdateAccount(ctx, ...)
}

The user APIs are as follows:
// New creates a Metadata object that has operations
// to manipulate the metadata (e.g., Get, Set, Append, Delete.
func New(m map[string][]string) Metadata

// NewContext creates a new context that contains metadata meta, with
// parent context ctx.
func NewContext(ctx context.Context, meta Metadata) context.Context

// FromContext returns the metadata from the context. If the context
// doesn't have any metata, it returns an empty metadata.
func FromContext(ctx context.Context) Metadata

Note that similar to the gRPC metadata, we make sure the metadata keys are lowercased, because the user can create metadata w/o using our New() metadata constructor, hence they can set the keys however they want.
[1] https://pkg.go.dev/google.golang.org/grpc/metadata

@ghemawat do you mind taking a look? Tests are missing, but I would like to get your opinion on the APIs before I go ahead and polish the PR.

Sanjay, don't look at the PR yet. Some test is failing.

Sanjay, don't look at the PR yet. Some test is failing.

Never mind. Everything works as expected. We have a flaky test but that's not something introduced by this change.

Thanks Sanjay


add functionality to shut down gracefully in worker manager

https://github.com/gojekfarm/ping-kong/blob/186d13757d13ab4e4bca18fd10035efe9569f400/worker.go#L15

This commit https://github.com/gojekfarm/ping-kong/commit/36ccf52128695a6d4e3fd53e2f85ac3a70f8fb96 should fix this issue

Closing this, has already been integrated.


Main Scene not working on macOSX

When you create a new project in macOSX and run it for the first time it will not prompt you to set a main scene, and even if you set one in project settings it will do nothing

Please fill the issue template instead of deleting it.
As it stands, we don't have enough information to debug or fix anything.


Design qwik libraries / collections

How can a project can import a third party library exporting qwik components?

Should libraries run the optimizer?
Optimizer needs whole world information in order to rebundle symbols
How libraries export all components? metadata? or exported .ts .js file?
How to prevent symbol conflict names?
Does the optimizer need a library mode?
Vite has a lib mode, how can we easy integrate with it?
Optimizer might have to be strongly versioned
Optimizer might need to process different versions, how can we minimize the scope.

Qwik SDK requires this

Qwik package includes some metadata:
{
  qwik: { source: ''},
}

Library mode ships transpired .js files, without optimizer

Open questions:

Optimizer relies on some JSX syntax to make the transpirte, so we need to teach the optimizer to understand transpired JSX code.

Fixed by https://github.com/BuilderIO/qwik/pull/628


test: percent-encoded char in json-pointer

from https://www.rfc-editor.org/rfc/rfc6901#section-6:
   A JSON Pointer can be represented in a URI fragment identifier by
   encoding it into octets using UTF-8 [[RFC3629](https://www.rfc-editor.org/rfc/rfc3629)], while percent-encoding
   those characters not allowed by the fragment rule in [[RFC3986](https://www.rfc-editor.org/rfc/rfc3986)].

test passed with impl https://github.com/santhosh-tekuri/boon
if test is ok, will add to remaining drafts

This looks fine to me.  My only question is whether the JSON Schema Test Suite should test JSON Pointer things.

whether the JSON Schema Test Suite should test JSON Pointer things

Testing that the URI fragment is properly parsed into the underlying json pointer seems a very relevant thing to me.
[Tests pass over here; thanks!]

There's a bunch of similar tests here of various characters that are encoded in json pointers and in URIs (or both); these could be adapted to the form used by the test suite, but some are more suited to testing result output, as there's only so much you can test with just an expected valid/invalid response.
https://github.com/karenetheridge/JSON-Schema-Modern/blob/v0.564/t/errors.t#L1012-L1142

my intentioned is not have a test for each reserved char. I just want to test that an implementation percent-decodes the raw fragment before using

This case is already tested here (see "percent%field"). I'm going to close this as a duplicate.


Run multiple Deis clusters inside of one Kubernetes cluster

We need to make sure that we can run multiple Deis clusters inside of the same Kubernetes cluster. In fact, it's highly likely that some of our early testers will be using this feature.
This means:

We should not assume the namespace is "deis"
We should make sure that the "child" namespaces we create for apps do not collide. We could probably accomplish this by prepending the "parent" namespace to the child (e.g. "wild-socks" becomes "deis1-wild-socks"
We need to think long and hard about how we handle Ingress

What other things (label queries? service acounts?) are impacted?

+1

https://github.com/deis/router/pull/18 would be affected because it assumes the "deis" namespace

@arschles I have a PR to fix that already, but I haven't submitted because I need to rebase to master after deis/router#18 is merged.

also, deis/builder would be affected because it launches pods to run builds. we'd have to templatize the manifests to set the right namespace. not a big deal, bit worth mentioning

I'm concerned here about running two workloads on the same cluster. For instance, given this circumstance:

two "separate" deis clusters on the same kuebernetes cluster
both create a "staging" user
both create an application called "mytestapp"
first cluster pushes the app (fine, creates RC/service)
second cluster pushes the app <-- ALL HELL BREAKS LOOSE

What I'm trying to allude to is that there are going to be more conflicts than just the control plane itself. Were going to have to maintain an entire suite of logic just to support this use case, and I don't imagine many users would be doing this in prod anyways.

@bacongobbler I think this was the reasoning behind:

We should make sure that the "child" namespaces we create for apps do not collide.

But I do agree there are lots of other considerations.  @technosophos already mentioned it, but ingress is foremost on my mind.
Currently, I'm doing port mappings of host:80/443/2222 to router pod(s):80/443/2222.  This was intended to enable the load balancing strategy used in v1.x.  i.e. Put an ELB in front of the whole cluster and whichever ones happen to be hosting routers will pass the health check.  This has been a deliberate choice instead of using k8s a k8s service for the router with type: LoadBalancer because that won't work on infrastructure where the corresponding cloud provider implements that as a no op-- e.g. Vagrant and bare metal.
Obviously, that breaks down if you want to run two Deis clusters in one k8s cluster.
One option might be to allow one router to manage ingress to multiple Deis control planes (i.e. workflow and builder).  That actually sounds relatively easy.

Can we close this issue for now? I'm guessing we will solve this another way.

Hi guys, what's the status of this?
I'm new to Deis. I assumed I could deploy workflow to another namespace simply by supplying the namespace parameter to helmc install: helmc install --namespace=staging workflow-v2.1.0. Apparently it doesn't work that way. I guess I could change all namespace: deis lines in manifest files but I doubt if the code assumes the deis namespace too. That also leads to some maintenance headache too.
We would really love it if both staging and production workflow can be run in a single cluster. Without this, we simply can't use Workflow. Do we have a workaround right now? Is there any suggestion about managing staging/production environments with Workflow? Thanks in advance.

Right now certain components look for other components within the deis namespace. So this isnt completely feasible right now.


Add a ddev dbeaver command

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
Just like ddev heidisql but then for dbeaver.
dbeaver is multi OS, linux/mac/win & has really nice features.
Describe your solution
New file in the ddev/pkg/ddevapp/global_dotddev_assets/commands/host/ directory.
Where it will start dbeaver whenever possible.
Win

/mnt/c/Program\ Files/DBeaver/dbeaver.exe
/c/Program Files/DBeaver/dbeaver.exe
Linux
dbeaver-ce
Mac:
?

Describe alternatives
No response
Additional context
No response

A contribution is welcome. Please take a look at the other database browser commands in your global .ddev/commands/host directory, and model on those. The details about the annotations you'll want to add are at https://ddev.readthedocs.io/en/latest/users/extend/custom-commands/

As discussed in #4947 we'd love to see you create an add-on that will be able to mature in a faster-moving place. Since this requires support in so many places, and add-on is a better place for it to mature.

Thanks! It looks like this been released, but I don't see it under https://github.com/ddev/ddev/releases ...

@gitressa currently only in master, and the next DDEV v1.22.4 will likely be released this week.

Thanks for a fast answer @stasadev. The reason I asked is that I am trying to override DDEV 1.22.3 with a DDEV in .local/bin, but the standard 1.22.3 gives med ddev dbeaver ... I'll continue in #5451.

There is no harm in replacing /usr/bin/ddev with another binary in Ubuntu.
And in the next release of ddev, when you do sudo apt update, it will be automatically replaced with the new one.
This way you don't have to worry if you forget to change the binary.

Thanks, let's find the best method in #5451.
ddev dbeaver is included in https://ddev.readthedocs.io/en/latest/users/usage/database-management/#database-guis, I suppose because it follows dev-version (which is called master in DDEV?).

Answered in another thread. that's because ddev dbeaver is a custom command, it doesn't look up for ddev itself.


[WIP] Metro-like sequencing

This is a WIP PR, any suggestions and improvements either in code or in UX are welcome!
This PR adds basic Metropolis-like sequencing with steps repeats and few different gate modes.
Metropolis gate modes for reference

**This works only in Free track mode, so make sure your track Play Mode is set to "Free" under Track page

Under Gate layout you can find 2 (for now) new layers
REPEAT` which repeats current step N times

REPEAT MODE` which is like a switch on metropolis that determines how to send gates

EACH --  sends a gate for each step
FIRST -- sends first gate and waits for N - 1 pulses
ODD -- sends gate for each odd step (1, 3, 5)
TRIPLET -- sends gate for each third step, (1, 4, 7) creating triplet feel.

Some gate modes were available on unit already
mode 1 (gate for N steps long) -- simply go to step LENGTH and increase it to 100%
mode 4 (no gate for N steps) -- simply disable the gate in GATE page
TODO

[ ] add step Skip function (stage button double tap on metropolis).
[ ] new modes shortcuts

only stage sequencing
with negative offsets.zip

If I would be a programmer, I would like to help; not the case.
If is there anything else I can do, I'm in; I would really like to see this feature implemented in Performer.
Here is an image with the RYK M185 gate modes, maybe it helps.

Hey this looks amazing!

To install this follow installation guide from README page but instead of
git clone --recursive https://github.com/westlicht/performer.git do
cd performer
git clone --recursive https://github.com/vafu/performer.git
cd performer
git checkout vafu/metro-pr

and proceed with installation

@hotelbachelard Thanks for the interest!
To install this follow installation guide from README page but instead of
git clone --recursive https://github.com/westlicht/performer.git do
cd performer
git clone --recursive https://github.com/vafu/performer.git
cd performer
git checkout vafu/metro-pr

and proceed with installation

oh boy, ok. i'll have to read through that.
thanks for taking the time to develop all these features!!! the screenshots look really promising already :)

@hotelbachelard how do you update the module usually ?

@hotelbachelard how do you update the module usually ?

I've only updated the module once for the latest firmware, and just copied the firmware file onto SD card.

@hotelbachelard oh, ok, I think I can prepare the update so you could update is without compiling code yourself

@hotelbachelard
please try this, it contains some update files, I'm not sure which you've used before so included some of them.
metro_update.zip
LMK if it worked for you!

@hotelbachelard
please try this, it contains some update files, I'm not sure which you've used before so included some of them.
metro_update.zip
LMK if it worked for you!

Works great!! Just needed to put the UPDATE.DAT onto the SD and follow the manual update procedure.
Would you mind putting your negative gate offset test on this too?

This is awesome man! Thank you!

@hotelbachelard this is a version with offsets metro_offset_update.zip

Amazing, thanks so much!! Thanks for taking all this time to develop these amazing features on the module.
Just popped it into the Westlicht, works great.
Another challenge - is there a way to allow fine-tuning of all the probability and offset percentages, instead of just those 4 or 5 values?
Thanks again, REALLY appreciate all your work and communication.Heidi
---------------Music: http://www.bachelard.bandcamp.com
On Sunday, December 6, 2020, 2:20:42 p.m. EST, vafu<EMAIL_ADDRESS>wrote:

@hotelbachelard this is a version with offsets metro_offset_update.zip
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@hotelbachelard unfortunately there's a memory limit which doesn't allow us to go any more detailed that those few values. this would require hardware changes, using another MCU etc.

It's very cool to see some firmware hacking happening, after all, this is part of the reason why I made this project open source from the beginning, so people can add new functionality as they see fit. I know that the multi-stage feature was requested by quite some people for quite some time now and the reason it hasn't happened yet is that I haven't really found a good way to implement this properly. Some background: Up until a few month ago, I was under the false assumption that I don't really have enough bits per step left to add these additional layers. Originally the step data was 6 bytes and pretty much used up. I then realised that a step was actually using 8 bytes due to alignment in the struct, which was a silly mistake. So yay, an extra 16bits was suddenly available for extensions. However, the multi-stage feature still seemed quite tricky to get right. Your current implementation is sort of "added on top" triggering the same step multiple times. Now this works, but is breaking some assumptions. To begin with, as you mention right from the beginning this only works if play mode is set to "free". I always try to make things in a consistent way, this means that it should also work with the aligned mode. It's arguable that this is not really necessary, but I don't like breaking existing concepts. So there are two possibilities, either this is implemented in a way that allows it to work in aligned mode, which is tricky, or we would implicitly switch to "free" mode when there is a step with multiple stages. It's weird if a feature is not working just because some seemingly unrelated settings are used. But even when implicitly switching, things are not behaving as expected, which is confusing IMO. It doesn't stop there. This interacts with so many existing things it's hard to make sure nothing breaks. Is this working properly (in an expected way) with track linking, recording, conditions, gate lengths, etc etc. Back when I put some thought into this I found it super tricky to get consistent and "right". So what I ended up doing was adding a new track mode which would offer a different sequencing concept more in line with the RYK/metropolis style of sequencing. This allowed me to make something that is self-contained and easier to understand/reason about. The downside is that it adds a whole new track mode and will probably leave out a lot of features that are already in the note track. So naturally people will ask why feature X is not available in stage mode when it is in note mode. Bottom line of all of this, I didn't yet come up with a concept to make this all work without it feeling "out of place".
Now, I really don't want to discourage this kind of development and I really hope you don't take this the wrong way. But I hope you understand when I don't merge this pull request right away and cannot even offer concrete steps to make the merge happen. This change has far reaching consequences and I really need to think about it before deciding which way to go. The great thing here is that people can still use the modified firmware and get their hands on this feature even if it's not in the main release. And I always hoped for this to happen, so please keep up the great work!

@westlicht I absolutely understand your concerns, that's why PR is still marked as WIP and probably will be that way for quite some time until it will be extensively tested by me and anyone willing to help :)
Though so far from my testing everything works as I would expect it to, including track linking, gate length, conditions etc. I've not yet tested tons of things but I've tried to touch as less code as possible and not break everything else.
Regarding Aligned/Free -- yes, I don't like either that we see some new NO-OP layers in Aligned mode so I was thinking to make every new layer this PR adds appear only if Free mode is selected. Or maybe to keep everything consistent we can create new Stage track mode which will be using same NoteTrackEngine but with Free mode by default and no way to switch to Aligned.
By no means I'm not trying to merge this right away, I've been in development for quite some time and I'd rather make sure that my PR is working as expected instead of  creating tons of bugfixes later :D
I really love the codebase, it's a pleasure to work with the code, it's very well-thought and transparent, so thank you so much for this platform and making it open source!

@dragosandriana As suggested by you, I've added few more gate modes:
REPEAT MODE` which is like a switch on metropolis that determines how to send gates

EACH --  sends a gate for each step
FIRST -- sends first gate and waits for N - 1 pulses
ODD -- sends gate for each odd step (1, 3, 5)
TRIPLET -- sends gate for each third step, (1, 4, 7) creating triplet feel.

compiled firmware is in description
@hotelbachelard Please try this as well :)

Hi @westlicht - so great to hear from you, and thanks for taking the time to respond to these recent changes that @vafu made.
I absolutely appreciate your principles as a designer, and agree that for a module this complex and flexible and, as you say, where each part of the sequencer is related to many other functions, consistency and rigorous and thorough testing and thinking through implementation of new features are really important. And to be honest, being far, far away from being a designer and programmer, I was just excited primarily about the musical and rhythmic possibilities of the Step Repeat addition, as well as the negative offset.
I played with vafu's unofficial update today, and so far things are working pretty consistently on my end as well. Overdubbing the note track will erase any Step Repeat, as expected. I do like that the Step Repeat is part of the Gate menu rather than in a totally different track mode – for now.  Even in its current state,
The only thing I found, as mentioned above, is that now, Gate on/off is now affected on every page/menu in the Step sequence, and not just available with the Gate page.  I would like that fixed if possible, as I've been inadvertently turning steps off when I'm changing notes or other things.
Again, really really appreciate Simon's original fantastic design on the Westlicht and vafu's current flurry of work on it. It's really become a centerpiece in my system.

@hotelbachelard Ah, gate on/off from each page was my own changes that I did not intend to add here, sorry about that, let me revert those!

@hotelbachelard version with negative offsets
here's update with fixed gate on every page

@hotelbachelard
metro_gate_fix.zip
here's update with fixed gate on every page

You're the best!!

has this version the midi fixes and improvements added on v0.1.38?

hi, @franq87, yes, this is branched out from latest upstream master (after v0.1.39)

hi, @franq87, yes, this is branched out from latest upstream master (after v0.1.39)

Cool, will check it this week for sure, thanks for this @vafu

@vafu I think I found an issue, when you copy a track that has different repeat values to another track, it copy the values but it only works as a x1 value, you can modify the value but it still playing only at x1
I'm having a lot of fun with this btw

@vafu Hi, just wondering if you had your branch updated to last v1.40
also, thanks for this branch
cheers

@franq87 sorry it took me so long to get back to you! I tried to reproduce the issue you've described, but copying all values to another track worked for me. did I get the steps right?

set track 1 and track 2 mode to "Free"
create a sequence using repeats on track 1
copy pattern
go to track 2
paste pattern

Hey hi! I've just repeated again and it is all working, It seems I forgot to put the track on free mode
all working like a charm, super thanks for the update!

@vafu this is not related with metropolis sequencing but, I was just wondering if you see possible to enable step up as a destination on the CV assignments? Maybe running the track in free mode as your metropolis sequencer does? This would be super handy for using the performer to quantize random trigs/gates when dropping some s&h in

@franq87 what do you mean by "step up" in this context?
like advancing the step by external trig?

@franq87 what do you mean by "step up" in this context?
like advancing the step by external trig?

that's right, not sure if it would be very difficult to implement as the track should remain static until an impulse is received to one of the four CV inputs as long as the other tracks keeps running, but having that option would open the possibility of using a track as an arpeggiator, a quantizer for S&H sequencing among other things

Hey, absolute joy to have this alternate firmware, thanks for the contribution.
I wanted to note that after updating the module to this FW the Arturia Keystep became compatible with the device. I wonder if any tweaks were done to facilitate this?
In any ways, I take it! :D

Hi nice work on this feature @vafu
Are there a firmware file available with this feature for the latest upstream version? (v0.1.41)

ohhh that looks neat!
@westlicht did you consider adding this as optional 4th sequencer mode - note, cv/midi, curve, metro-note?
Or are your concerns more about cluttering the codebase?
@franq87 I was thinking about that idea too, it would be cool for generative sequences to be able to index steps by cv or advance manually. But I found an older issue where westlicht stated it would be quite troublesome to introduce such behavior into the current code logic.

@franq87 : you can abuse routing to address notes in a sequence byan external voltage. Route VCin to Fisrt AND last note (using two different but related routings) and you can have a one step long sequence, where the note is selected by the CV in and the step is triggered the conventional way. You can also use an internal sequence to route this instead of an external CV btw...

@franq87 : you can abuse routing to address notes in a sequence byan external voltage. Route VCin to Fisrt AND last note (using two different but related routings) and you can have a one step long sequence, where the note is selected by the CV in and the step is triggered the conventional way. You can also use an internal sequence to route this instead of an external CV btw...

I haven't explored this way, will try definitely

@franq87 : you can abuse routing to address notes in a sequence byan external voltage. Route VCin to Fisrt AND last note (using two different but related routings) and you can have a one step long sequence, where the note is selected by the CV in and the step is triggered the conventional way. You can also use an internal sequence to route this instead of an external CV btw...

That's exactly what I was going to suggest as well. It's one of the reasons the Westlicht is a keeper for what I need, that you can CV not only the last step (which merely changes pattern length on most other sequencers), but also the FIRST step, which allows you to loop/"window" smaller sequences within a longer pattern.
I can say that @vafu's firmware is great. I've been using it for a while now. The only bug I still see is that the Gate probability bar for each step is not visible, as it usually is when you're on that page in the official firmware—the function still works and you can see the probability percentage bar if you press on a particular step. I have not tested all the conditional stuff though.
@jbjhjm Yes, Simon has been quite meticulous on what sorts of features he "officializes," since any additional mode or feature can impact a number of other functions in the sequencer. Despite selfishly wishing for a few more features, I really appreciate Simon's vision of consistency.


Only draw loaded chunks that are in view

First a view distance check then use all 3 elements of the view

Got view distance down

Dividing the plane into in front of and behind the player and only drawing chunks in front


x2 boosted calcs are wrong for 12-3 and 12-6

here are two images for 12-3 and 12-6 calcs
https://imgur.com/a/Y1WiLIG

Hi @Gohei27, thanks a lot for detecting the problem and for raising this issue!
The number of calculated battles was working correctly for "No boost", "Raid Boost" and "XP boost", but it was wrong indeed for "Both Boosts" option (Raid boost and XP boost simultaneously).
I just released v1.0.6 which include the fix for this issue. Can you test it?

Will do, at work atmOn Feb 2, 2021 3:39 PM, Rafael Acosta<EMAIL_ADDRESS>wrote:
Hi @Gohei27, thanks a lot for detecting the problem and for raising this issue!
The number of calculated battles was working correctly for "No boost", "Raid Boost" and "XP boost", but it was wrong indeed for "Both Boosts" option (Raid boost and XP boost simultaneously).
I just released v1.0.6 which include the fix for this issue. Can you test it?
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.

First test was x3 4*'s @ lvl 25, it leveled them to just under 39. which is perfect imo since I was aiming just under. I'll test again later, but it is working

From: Rafael Acosta<EMAIL_ADDRESS>Sent: Tuesday, February 2, 2021 3:39 PM
To: rafaco/UnlimitedMultiBattles<EMAIL_ADDRESS>Cc: Gohei27<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [rafaco/UnlimitedMultiBattles] x2 boosted calcs are wrong for 12-3 and 12-6 (#1)
Hi @Gohei27https://github.com/Gohei27, thanks a lot for detecting the problem and for raising this issue!
The number of calculated battles was working correctly for "No boost", "Raid Boost" and "XP boost", but it was wrong indeed for "Both Boosts" option (Raid boost and XP boost simultaneously).
I just released v1.0.6https://github.com/rafaco/UnlimitedMultiBattles/releases/tag/v1.0.6 which include the fix for this issue. Can you test it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/rafaco/UnlimitedMultiBattles/issues/1#issuecomment-771966698, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACYQIAUJFA7DJU22QHNJZELS5BPH5ANCNFSM4V2B743A.


add support for Configuration API

The Configuration API feature has been implemented in Dapr runtime: https://github.com/dapr/dapr/pull/3606
It needs to be accessible via the SDK.

Closed by #110


Error no such file or directory trying to load the .txt file from temp

Hi,
I'm using "astro-font": "^0.0.60"  and having this error when run build.

@khoait
Thanks for reporting! Looking into this...

@khoait
Can you share your AstroFont configuration?
https://github.com/rishi-raj-jain/astro-font/blob/master/packages/astro-font/utils.ts#L186-L190 shall only load it when it's present 👀

Hi @rishi-raj-jain
my AstroFont config:
---
import { AstroFont } from "astro-font";
---

<AstroFont
  config={[
    {
      name: "Inter",
      src: [
        {
          style: "normal",
          weight: "400",
          path: "https://fonts.gstatic.com/s/inter/v13/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa2pL7SUc.woff2",
        },
        {
          style: "normal",
          weight: "500",
          path: "https://fonts.gstatic.com/s/inter/v13/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa2pL7SUc.woff2",
        },
        {
          style: "normal",
          weight: "700",
          path: "https://fonts.gstatic.com/s/inter/v13/UcC73FwrK3iLTeHuS_fvQtMwCp50KnMa2pL7SUc.woff2",
        },
      ],
      preload: true,
      display: "swap",
      selector: "body",
      fallback: "sans-serif",
    },
  ]}
/>

@khoait
Thanks for sharing the config!
It helped me:

fix the long filename problem that occured while reproducing the issue
write idiomatic code to scope operations that are not vital and implement error handling: https://github.com/rishi-raj-jain/astro-font/blob/master/packages/astro-font/utils.ts#L201-L207

Can you upgrade via:
pnpm add astro-font@latest

Also, by default the files are NOT created and localized.
To make sure the files are fetched and read from the local, add the fetch flag to your config object.

Hi @rishi-raj-jain, thanks for your quick response!
the error seems to be resolved and I can see local files are created correctly.
now I encounter another error. I'm using "astro-i18n": "^2.2.0" and there are some conflicts with astro-font I think.

Stacktrace
TypeError: Invalid URL
    at new URL (node:internal/url:775:36)
    at set route [as route] (C:\Users\------\node_modules\astro-i18n\dist\src\index.js:12:30049)
    at C:\Users\------\node_modules\astro-i18n\dist\src\index.js:12:36645
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///C:/Users/------/node_modules/astro/dist/i18n/middleware.js:35:22
    at async callMiddleware (file:///C:/Users/------/node_modules/astro/dist/core/middleware/callMiddleware.js:12:10)
    at async #tryRenderRoute (file:///C:/------/node_modules/astro/dist/core/pipeline.js:101:18)
    at async DevPipeline.renderRoute (file:///C:/Users/------/node_modules/astro/dist/core/pipeline.js:58:20)
    at async handleRoute (file:///C:/Users/------/node_modules/astro/dist/vite-plugin-astro-server/route.js:248:18)
    at async run (file:///C:/Users/------/astro/dist/vite-plugin-astro-server/request.js:50:14)
    at async runWithErrorHandling (file:///C:/Users/------/node_modules/astro/dist/vite-plugin-astro-server/controller.js:64:5)
    at async handleRequest (file:///C:/Users/------/node_modules/astro/dist/vite-plugin-astro-server/request.js:44:3)

Maybe this can go to another issue. Unfortunately I'll have to remove astro-font for now and use google font links instead.

@khoait
Thank you for getting back to me!
Per the error log, I do not think this is related astro-font.

Do let me know if after removing astro-font it works fine
Feel free to drop a GH link to the repo if possible so that I can spend my time into crafting the perfect experience of astro-font

@rishi-raj-jain yes, removing astro-font it works ok. you can see the error in this branch https://github.com/khoait/3edesign/tree/astro-font

@khoait
Hey, I just tested and it did build fine. The steps I followed:

git clone https://github.com/khoait/3edesign/tree/astro-font
npm install
npm install astro-font@latest
npm run build

Uploading Screen Recording 2024-01-08 at 6.28.19 PM.mp4…

https://github.com/rishi-raj-jain/astro-font/assets/46300090/a469948c-9cf9-4996-b317-0b4864d2f7bb

Totally appreciate your feedback and time that you took! Hope you get the time to try this again soon...

ok, that's strange. I see the error when running npm run dev. build then preview is ok though 😕

Hey @khoait,
Thank you for taking the time.
Even after you remove the astro-font lib, it errors out as the error is within the dev mode while using astro-i18n.
Please have a look:
https://github.com/rishi-raj-jain/astro-font/assets/46300090/8ce16f5f-74bc-4c31-852e-530927cdbd89

Even in the error logs of the screen recording you sent, the error is pointing out to: astro-i18n

Yeah, i can see it. That's why i mentioned there is some conflicts with astro-i18n only when astro-font is installed.
Anyway i really apprecitate your support! I'll look into this later when my project is more stable.

only when astro-font is installed.

Uninstalled it 👇🏻
https://github.com/rishi-raj-jain/astro-font/assets/46300090/a07fb9f4-0bc9-48cd-94e8-6d5497ec37aa

Anyway i really apprecitate your support!

My pleasure 🤞🏻

I'll look into this later when my project is more stable.

Alright


Remove method "student" in bootstrap.confidence_interval

The method "student" is not implementing the bootstrap-t method as described in the book by Efron and Tibshirani, page 160+.
In the book, the algorithm estimates the standard deviation for each bootstrap replica, which requires a double bootstrap. Let's say the estimator is s(x)

replicate a sample x* from the original sample x and compute s(x*)
bootstrap the std. deviation of s(x*) by bootstrapping again from x*, generating several replicas s(x**)
compute the studentized values (s(x*) - s(x))/std of s(x**)
generate a quantile function of these values and compute the interval from that

This differs from the implemention we have, which computes the std.dev. of s(x*), not std.dev. of s(x**). The difference is important. Our current implementation is identical to the percentile, because the percentile is transformation independent and we just apply a scaling and a shift to the bootstrap replicas.
Our options are to implement the bootstrap-t properly or to remove this method. I am in favor of removing, because the bootstrap-t is shown to be inferior to the bca method in the book, while being computationally even more expensive.

Another option would be to use the jackknife to estimate the standard deviation within each bootstrap sample as a less expensive alternative, but from what I'm seeing that's still pretty slow. So probably best to remove for now.

Comment: the jackknife is only faster for small samples.


github_contributions.csv

Why does this file have language-related content? This should be in es_ES.csv.

It’s explained here: https://github.com/mageplaza/magento-2-spanish-language-pack/blob/master/HOW-TO-CONTRIBUTE.md#step-2-update-github_contributionscsv
They separate es_ES.csv (the original file from the Magento team) from the one containing their own translations, and later merge both.


Finish and/or restart for interrupted liability execution

Now I use only short exection models no longer a minutes, but I hope to develop CPS with liabilities take days or weeks to complete. The main reason to make it short now because if something goes wrong while liability exection like application software error, server restart or batteries dischage - liability execution interrupts with no way to continue or even restart it.
I see there are open questions on how to continue interrupted execution with no missing older report data, for example.
But maybe it's possible to implement restart execution or even just allow to finish own liability which is not finished yet?

Any updates for this topic?

Available on robonomics_liability-nightly.

@akru, working on this issue in not finished yet.

Rly? Please let me known when finish.

@akru, please see PR #89

@strdn released as nightly

@khssnv, please see #89 description and feel free to ask any question about new behaviour


SnippetsProvider adds almost 5s to language server startup time

The logic to build up the cache in the SnippetsProvider is invoked synchronously in the constructor and delays the start of the language server when the user first opens a Bicep file. (It also adds the delay every time we need to debug the language server when working on Bicep.)
Measuring steps:

We're going to increasing the number of snippets over time, which will make the startup time worse. I think the best option is to make cache initialization to be asynchronous. The completion provider should then be able to serve up only the snippets that have been initialized up to that point. After 5s or so, it will be the full set.

IIRC the data being calculated doesn't actually need to be computed at run time as it should be deterministic for each Bicep version. Another option is to compute it when building Bicep, and embedding as JSON. Even if we make this cache initialization asynchronous, it'll still consume unnecessary resources.

Other thing to note is I think the delay is exaggerated when running with the debugger - I don't think it's too bad when running a release build (although I completely agree it should be avoided either way).


The value of DFT potential

Hello!
I need to get a single-point value of potential, in which all electrons are moving, from DFT-calculations. Can I get it from PySCF?

You have to follow this example: https://github.com/pyscf/pyscf/blob/master/examples/dft/31-xc_value_on_grid.py


fetch cluster ID for remotely mounted filesystem

Task: 288430 Find remote clusterid for filesystem - Cluster ID will not be there in new Storage Class
Task: 288504 Cache to reduce the number of rest calls with expiry

if filesystem type is remote, then cluster name and cluster ID are fetched and stored in map which has validity of 24 hours.

Logs
first iteration

I0119 12:27:51.840099       1 controllerserver.go:597] filesystem fs2 is remotely mounted, getting cluster ID information of the owning cluster.
I0119 12:27:51.840773       1 controllerserver.go:602] creating new connector for the cluster<PHONE_NUMBER>0375162524
I0119 12:27:51.840914       1 controllerserver.go:608] fetching cluster name for cluster<PHONE_NUMBER>0375162524
I0119 12:27:51.987362       1 controllerserver.go:614] fetching cluster details from cache map for cluster<PHONE_NUMBER>0375162524
I0119 12:27:51.987451       1 controllerserver.go:646] cluster details not present in cache map for cluster<PHONE_NUMBER>0375162524.
I0119 12:27:52.078688       1 controllerserver.go:654] adding cluster details in cache map for cluster<PHONE_NUMBER>0375162524.
I0119 12:27:52.078756       1 controllerserver.go:602] creating new connector for the cluster<PHONE_NUMBER>889582128
I0119 12:27:52.078915       1 controllerserver.go:608] fetching cluster name for cluster<PHONE_NUMBER>889582128
I0119 12:27:52.262825       1 controllerserver.go:614] fetching cluster details from cache map for cluster<PHONE_NUMBER>889582128
I0119 12:27:52.263041       1 controllerserver.go:646] cluster details not present in cache map for cluster<PHONE_NUMBER>889582128.
I0119 12:27:52.299865       1 controllerserver.go:654] adding cluster details in cache map for cluster<PHONE_NUMBER>889582128.
E0119 12:27:52.299932       1 controllerserver.go:672] volume filesystem fs2 is remotely mounted on Primary cluster, using owning cluster ID<PHONE_NUMBER>889582128.

Fetching cluster details from cache map in second iteration
I0119 12:30:39.783228       1 controllerserver.go:597] filesystem fs2 is remotely mounted, getting cluster ID information of the owning cluster.
I0119 12:30:39.783865       1 controllerserver.go:602] creating new connector for the cluster<PHONE_NUMBER>0375162524
I0119 12:30:39.783986       1 controllerserver.go:608] fetching cluster name for cluster<PHONE_NUMBER>0375162524
I0119 12:30:39.989435       1 controllerserver.go:614] fetching cluster details from cache map for cluster<PHONE_NUMBER>0375162524
I0119 12:30:39.989557       1 controllerserver.go:617] cluster details found from cache map for cluster<PHONE_NUMBER>0375162524
I0119 12:30:39.989738       1 controllerserver.go:620] checking if cluster details found from cache map for cluster<PHONE_NUMBER>0375162524 has expired.
I0119 12:30:39.989845       1 controllerserver.go:622] cluster details found from cache map for cluster<PHONE_NUMBER>0375162524 are valid.
I0119 12:30:39.989906       1 controllerserver.go:602] creating new connector for the cluster<PHONE_NUMBER>889582128
I0119 12:30:39.990403       1 controllerserver.go:608] fetching cluster name for cluster<PHONE_NUMBER>889582128
I0119 12:30:41.645483       1 controllerserver.go:614] fetching cluster details from cache map for cluster<PHONE_NUMBER>889582128
I0119 12:30:41.645628       1 controllerserver.go:617] cluster details found from cache map for cluster<PHONE_NUMBER>889582128
I0119 12:30:41.645726       1 controllerserver.go:620] checking if cluster details found from cache map for cluster<PHONE_NUMBER>889582128 has expired.
I0119 12:30:41.645824       1 controllerserver.go:622] cluster details found from cache map for cluster<PHONE_NUMBER>889582128 are valid.
E0119 12:30:41.645888       1 controllerserver.go:672] volume filesystem fs2 is remotely mounted on Primary cluster, using owning cluster ID<PHONE_NUMBER>889582128.

when cache map data has expired
I0119 12:58:03.657868       1 controllerserver.go:597] filesystem fs2 is remotely mounted, getting cluster ID information of the owning cluster.
I0119 12:58:03.658710       1 controllerserver.go:602] creating new connector for the cluster<PHONE_NUMBER>0375162524
I0119 12:58:03.658857       1 controllerserver.go:608] fetching cluster name for cluster<PHONE_NUMBER>0375162524
I0119 12:58:03.782437       1 controllerserver.go:614] fetching cluster details from cache map for cluster<PHONE_NUMBER>0375162524
I0119 12:58:03.782529       1 controllerserver.go:617] cluster details found from cache map for cluster<PHONE_NUMBER>0375162524
I0119 12:58:03.782617       1 controllerserver.go:620] checking if cluster details found from cache map for cluster<PHONE_NUMBER>0375162524 has expired.
I0119 12:58:03.782700       1 controllerserver.go:628] cluster details found from cache map for cluster<PHONE_NUMBER>0375162524 has expired.
I0119 12:58:03.865836       1 controllerserver.go:637] updating expired cluster details found from cache map for cluster<PHONE_NUMBER>0375162524.
I0119 12:58:03.865885       1 controllerserver.go:602] creating new connector for the cluster<PHONE_NUMBER>889582128
I0119 12:58:03.865998       1 controllerserver.go:608] fetching cluster name for cluster<PHONE_NUMBER>889582128
I0119 12:58:03.923493       1 controllerserver.go:614] fetching cluster details from cache map for cluster<PHONE_NUMBER>889582128
I0119 12:58:03.923587       1 controllerserver.go:617] cluster details found from cache map for cluster<PHONE_NUMBER>889582128
I0119 12:58:03.923684       1 controllerserver.go:620] checking if cluster details found from cache map for cluster<PHONE_NUMBER>889582128 has expired.
I0119 12:58:03.923795       1 controllerserver.go:628] cluster details found from cache map for cluster<PHONE_NUMBER>889582128 has expired.
I0119 12:58:03.962863       1 controllerserver.go:637] updating expired cluster details found from cache map for cluster<PHONE_NUMBER>889582128.
E0119 12:58:03.962925       1 controllerserver.go:672] volume filesystem fs2 is remotely mounted on Primary cluster, using owning cluster ID<PHONE_NUMBER>889582128.

sc.yaml
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: remotefileset
parameters:
  volBackendFs: fs2
provisioner: spectrumscale.csi.ibm.com
reclaimPolicy: Delete
volumeBindingMode: Immediate

pvc.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: remotefileesetpvc
  namespace: ibm-spectrum-scale-csi-driver
spec:
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 10Gi
  storageClassName: remotefileset

cluster stanza
  clusters:
    - id: "11607132480375162524"
      secrets: "ibm-spectrum-scale-gui-csiadmin"
      secureSslMode: false
      primary:
        primaryFs: "fs2"
        primaryFset: "primary-fileset-fs2-11607132480375162524"
        remoteCluster: "6551742611889582128"
      restApi:
        - guiHost: "ibm-spectrum-scale-gui.ibm-spectrum-scale"
    - id: "6551742611889582128"
      secrets: "csi-remote-mount-storage-cluster-1"
      secureSslMode: false
      restApi:
      - guiHost: "remote-csi-scalegui.fyre.ibm.com"

Duplicate PR.


[QoL] Remove the "Lock in Children" lock icon that appears when next to a shader property and only keep it in the right-click menu

Ever since this came to be, I have somehow always ended up mis-clicking and enabling this on random shader properties on accident when just expanding categories in the poi shader.
Sometimes it overlaps with other things in the UI for poi shaders (9.1.2).
To prevent this from occurring, I think that it should only be possible to lock in children if the property is right-clicked and then the option to do so is chosen.

fixed


import user.proto err

var PROTO_PATH = __dirname + '../lib/protos/user.proto';
var grpc = require('grpc');
var hello_proto = grpc.load(PROTO_PATH).helloworld;
D0726 11:46:08.857119000<PHONE_NUMBER>03424 ev_posix.c:101] Using polling engine: poll
/Users/zhangjinglong/console-web/node_modules/grpc/src/node/index.js:124
return loadObject(builder.ns, options);
^
TypeError: Cannot read property 'ns' of null
at Object.load (/Users/zhangjinglong/console-web/node_modules/grpc/src/node/index.js:124:28)
at Object. (/Users/zhangjinglong/console-web/controller/imageclassify.js:9:24)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/Users/zhangjinglong/console-web/controller/index.js:19:18)
at Module._compile (module.js:409:26)

This indicates that Protobuf.js failed to load the file. Are you sure the PROTO_PATH is correct? Are you sure the .proto file is syntactically correct?

I am actually having the same issue. And in my case I can confirm that the helloworld.proto is correct or appears to be because the server js file I'm running is loading the same .proto file without any issues.

I retract my previous statement. I did, in fact, have my path wrong. Glad I caught my mistake before I had anyone wasting too much time on this. So sorry.

@zxydaisy PROTO_PATH should be __dirname + '/../lib/protos/user.proto';


Remove db encryption with pgcrypto

Fixes: #779

@barreiro has there been any further progress on this? thanks

@barreiro the integration tests run with a built jar and therefore runs in prod mode by default.  We either need to enable ssl in the postgres container or do not enable by default for prod in application.properties and make sure it is highlighted in to docs that it is recommended to enable TLS in production.
I do not think creating and registering a self-signed cert for integration test will be simple

@barreiro please can you squash commits

LGTM, please squash and I will merge, thanks!

rebased and squashed


Namespace problem with AudioTools library

Problem Description
When using this library together with AudioTools, declaring A2DP_I2S_AUDIOTOOLS to be true and USE_AUDIOTOOLS_NS to be false will cause compilation to fail as in some places classes from the AudioTools library are used without heir namespace declaration.
Error output gives these error locations:

BluetoothA2DPOutputAudioTools.h:96
BluetoothA2DPOutputAudioTools.cpp:231

I'm using PlatformIO and am setting the flags directly in the platformio.ini.
Device Description
DFRobot FireBeetle 2 ESP32-E
Sketch
#include <AudioTools.h>
#include <BluetoothA2DPSink.h>

audio_tools::I2SStream out{};
BluetoothA2DPSink a2dp_sink(out);

void setup() {
    a2dp_sink.start("MyMusic");
}

void loop() {
    delay(1000); // do nothing
}

Other Steps to Reproduce
platformio.ini:
[env:dfrobot_firebeetle2_esp32e]
platform = espressif32
board = dfrobot_firebeetle2_esp32e
framework = arduino
build_flags =
    -D USE_AUDIOTOOLS_NS=0
    -D A2DP_I2S_AUDIOTOOLS=1
lib_deps =
    https://github.com/pschatzmann/arduino-audio-tools.git#v1.0.0
    https://github.com/pschatzmann/ESP32-A2DP.git

Provide your Version of the EP32 Arduino Core (or the IDF Version)
5.1.4
I have checked existing issues, discussions and online documentation

[X] I confirm I have checked existing issues, discussions and online documentation

I committed a correction!
Why would you need this ?

Thank you for the quick fix!
I am using your library together with Bounce2 and when using the AudioTools namespace I'm running into the problem of multiple Debouncer class definitions.
Im therefore quite happy that your library provides an own namespace to avoid this problem :)


FileCard label z-index

The FileCard label would appear over other dom elements (i.e. a fixed position header).
So I've just removed the z-index, this seems to have no negative impact, the label is still visible with or without a preview image, not sure why it was there to begin with. 😅

 Bug: A file label appears on the top bar when I scroll down


Fixed interception of POST requests for 3DS

A bug has been discovered where some requests are not correctly searching for the request body by URL.

@Erdemtsynduev Thanks for the fix!


Removes yakkety support, removes old raspbian repo

Rasbpian repo has been updated to 17.09.0-ce which includes a fix for
docker service calls on arm architecture, hence the removal of the old
apt repo for raspbian.
Also yakkety is no longer supported in the Docker CE releases so it is
effectively removed from the install script support
Signed-off-by: Eli Uriegas<EMAIL_ADDRESS>

cc @alexellis @StefanScherer

NOTE: Currently investigating the issue with raspbian/stretch, it may require a change more upstream.

@seemethere Thank you. 💯 It works on Raspbian Jessie (HypriotOS).

Successfully tested an update from 17.05.0-ce (installed with current get.docker.com script) to 17.09.0-ce with this script.

ping @andrewhsu

I would want to know this works fully with existing images built prior to the requirements for multi-arch only. There was discussion with @StefanScherer on Slack about this.
I'd worry that we'd upgrade and suddenly none of the containers which worked on 17.05 would be able to be scheduled on 17.x in a Swarm.

I've updated our PiCloud cluster to 17.09.0-ce today and I'm able to create services that are spread over three platforms (RPi with 32bit HypriotOS, RPi with 64bit HypriotOS, UP Board amd64).
But I'm always using multi-arch images stored in a private registry ("on-prem" on one of the nodes) for the demos.
The update went fine with this script from 17.05.0-ce (from a previous get.docker.com installation) to 17.09.0-ce.
For the 64bit ARM running a Debian Stretch I had to choose the Ubuntu Xenial DEB package as there is no Debian for arm64 at download.docker.com.

If this is working for you @StefanScherer then we'll schedule to bring the changes for this PR to test.docker.com for 17.10.0 ce rc2. And when 17.10.0 GA then the changes of this PR will be brought to get.docker.com.

@andrewhsu I did some further tests and I think we should go further as it looks good to me:
Creating a service in swarm mode works for images that are built on ARM machines.
works:
$ docker service create --name whoami -p 8080:8080 stefanscherer/whoami:rpi
$ docker manifest inspect -v stefanscherer/whoami:rpi | jq .Platform
{
  "architecture": "arm",
  "os": "linux"
}

doesn't work:
docker service create --name whoami -p 8080:8080 stefanscherer/whoami:linux-arm-1.4.1
$ docker manifest inspect -v stefanscherer/whoami:linux-arm-1.4.1 | jq .Platform
{
  "architecture": "amd64",
  "os": "linux"
}

This image is built on Travis (amd64) with a "FROM scratch -> COPY static go binary" docker build.
So this image has "amd64" as architecture.
I'm fine with this behaviour.
If you annotate such an image in a manifest list to be an "arm" image which is done for
works (as normal container):
$ docker run -d -p 8080:8080  stefanscherer/whoami:linux-arm-1.4.1

These cross compiled images can be used for normal docker-compose purposes and docker run.
also works (with a manifest list):
$ docker service create --name whoami -p 8080:8080 stefanscherer/whoami
$ docker manifest inspect -v stefanscherer/whoami | jq '.[].Platform'
{
  "architecture": "amd64",
  "os": "linux"
}
{
  "architecture": "arm",
  "os": "linux"
}
{
  "architecture": "arm64",
  "os": "linux"
}
{
  "architecture": "amd64",
  "os": "windows"
}

@alexellis WDYT?

The issues experienced in the tests here should be remedied when 17.10.0-ce-rc2 drops with the inclusion of this commit: https://github.com/docker/docker-ce/pull/263

Updating test.docker.com with these updates

This PR removed the GPG key checking, how did this not get reviewed?

@justincormack the gpg key is actually hosted on download.docker.com so it wasn't necessary to have it in the script anymore.

You do not remove security features with no comment in an unrelated commit. It is more secure to have the key in this file, in case you mirror it, or mirror the distro, and then have more assurance. Otherwise anyone who can compromise the repo can just swap out the key.


Keyerror in user.get_available_backends()

KeyError when accessing 'data' key in _get_backends_info response

Hello, Could you provide the version you use

Thank you for your assistance. It appears that my API token has expired. I have since refreshed it, and there are no longer any errors. Could you please advise on the recommended frequency for refreshing my API token? (pyquafu version 0.3.6)

Thank you for your assistance. It appears that my API token has expired. I have since refreshed it, and there are no longer any errors. Could you please advise on the recommended frequency for refreshing my API token? (pyquafu version 0.3.6)

You're welcome, yes for 0.3.6, the error message is not precise for now, we may make our backend backward compatible to show correct prompt about API token issue in the future. Also we have implemented better error handling and will release 0.4.0 soon, please stay tuned.
I suggest that you refresh API token every 3 months.


Unexpected Method Call... why

In a multi-threaded environment, I am getting an exception "Unexpected Method Call...., the previous call has not been completed" when I am trying to access multiple StorageFiles from multiple threads under load (one thread, one file)... If I throttle access by using a Semaphore so that this call is only made once across all threads (the other ones are waiting in front of the Semaphore), this error does not occur..
Is there some kind of "static" behavior that discourages multi-threaded/concurrent use of this method that I am not aware of?

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

ID: 7bd09af9-13d3-f3b3-496a-f6b751d6ec16
Version Independent ID: 3938e25a-d6b6-9564-086e-939e33f9ccec
Content: FileInformation.GetBasicPropertiesAsync Method (Windows.Storage.BulkAccess) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.storage.bulkaccess.fileinformation.yml&version=GBlive&_a=contents
Product: uwp
Technology: winrt-reference
Git Login: lastnameholiu
Microsoft Alias: alholiu

Hi @jhwheuer , I'm currently working to see if I can an answer to your question. Should there be any answers, I will circle back and possibly update our documentation to clarify. Many thanks for bringing this to our attention.


niri: 0.1.1 -> 0.1.2

Diff: https://github.com/YaLTeR/niri/compare/v0.1.1...v0.1.2
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@KiaraGrouwstra a new release already :sweat_smile: give it a shot.

@sodiboo you too, if you know a little about nixpkgs

I would like to use the niri package from nixpkgs as the default for my module, to benefit from caching capabilities of nixpkgs. But, it currently doesn't handle resources/ at all. Could you implement this? Here's how i do it: https://github.com/sodiboo/niri-flake/blob/a242626ab62f5deb2f4ee77a30c158b21bd279df/flake.nix#L91-L105

@KiaraGrouwstra @sodiboo Done? :smile:

yup, that should just about do it :3. now this package is useful to install, rather than basically being just precompiled binary

I'm curious, why is there a separate Cargo.lock for nixpkgs? Should it not be okay to include just ${src}/Cargo.lock? Is the one checked into nixpkgs different in any meaningful way?

The manual says this:

Exception: If the application has cargo git dependencies, the cargoHash/cargoSha256 approach will not work, and you will need to copy the Cargo.lock file of the application to nixpkgs and continue with the next section for specifying the options of thecargoLock section.

[x] reviewed the diff and commit messages
[x] made sure ofBorg build succeeded for all applicable platforms
[x] run nix-review for a reasonable amount of time without any failures (or marked preexisting failures as broken)

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1464

This review has been done with warden, please report any issues!
Packages built

✅ niri
nix-info -m

system: "x86_64-linux"
host os: Linux 6.1.77, NixOS, 24.05 (Uakari), 24.05.20240216.5863c27
multi-user?: yes
sandbox: relaxed
version: nix-env (Nix) 2.19.3
nixpkgs: /etc/nix/inputs/nixpkgs


feat(ui-ux): hide bottom nagivation when EMV network is selected

What this PR does / why we need it:
Which issue(s) does this PR fixes?:

Fixes DFC-177
Additional comments?:
Developer Checklist:

[ ] Read your code changes at least once
[ ] Tested on iOS/Android device (e.g, No crashes, library supported etc.)
[ ] No console errors on web
[ ] Tested on Light mode and Dark mode*
[ ] Your UI implementation visually matched the rendered design*
[ ] Unit tests*
[ ] Added e2e tests*
[ ] Added translations*

Codecov Report

:exclamation: No coverage uploaded for pull request base (feature/evm@1b9fad8). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             feature/evm    #4011   +/-   ##
==============================================
  Coverage               ?   16.51%
==============================================
  Files                  ?      455
  Lines                  ?    12283
  Branches               ?     4096
==============================================
  Hits                   ?     2028
  Misses                 ?    10214
  Partials               ?       41

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Dps calc ignores elemental dps

Physical Dps shows as the same as dps even thou there is flat elemental dmg on the weapon.
This seems to happen only when there is also flat added physical dmg on the weapon.
Tested on Quarterstaffs/Warstaffs
Staff with added phys and incorrect calc.

Fixed in #270


Change USER_COMMAND_MARK

Change USER_COMMAND_MARK to include escape characters so that the non-printing characters are not counted towards prompt length.

Without this, experimental instant mode has an issue where line breaks occur 10 characters too early, making the terminal a bit wonky.

On a slightly related note, in def instant_mode_alias(self, alias_name) in shells/bash.py, is it really necessary with the backspaces in mark = USER_COMMAND_MARK + '\b' * len(USER_COMMAND_MARK)? In my experience, it works just fine without them, and fucks up if anything appends something to the start of PS1 (such as enabling a python venv).


Add field type in composer.json

https://github.com/jjgrainger/wp-custom-post-type-class/issues/54

Why? It's not a plugin.

This is more of a library to be included in themes and plugins, not really a plugin or theme in itself.
I don't believe these edits will work.
Thanks for the request :)

:)
OK. But how could use a custom path?
Something like: https://getcomposer.org/doc/faqs/how-do-i-install-a-package-to-a-custom-path-for-my-framework.md


Old chat versions in quickstart

Describe the bug
As a new user doing the quickstart I would like to try the latest version of the project.
Looking at the script https://github.com/armadaproject/armada/blob/master/docs/local/setup.sh#L3-L10
The versions are very old
KIND_IMG="kindest/node:v1.21.10"
CHART_VERSION_ARMADA="v0.3.20"
CHART_VERSION_ARMADA_EXECUTOR_MONITORING="v0.1.9"
CHART_VERSION_KUBE_PROMETHEUS_STACK="13.0.0"
CHART_VERSION_NATS="0.13.0"
CHART_VERSION_POSTGRES="12.4.2"
CHART_VERSION_PULSAR="2.9.4"
CHART_VERSION_REDIS="4.22.3"

Expected behavior
At least I would like to see ARMADA and ARMADA_EXECUTOR_MONITORING to use latest version 0.8.2
I was not able to find a e2e tests that execute this quickstart flow in a github action

Hi,
Thanks for raising this!
We have deprecated this examples in https://github.com/armadaproject/armada/pull/3670 and now the official installation guide is https://github.com/armadaproject/armada-operator?tab=readme-ov-file#quickstart
I will close this as completed.


Past speaker page out of colours

The past speaker page has apparently run out of different colours for the sections. So the last 2 speaker sections are in the same colour. Looking for a fix.

Manually setting the background works. Looking for a better solution.

Edited the css file to add more colours


Test [DONT MERGE]

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/concepts/dirac-notation.md
72
51
34
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Docs Build status updates of commit aff7f99:
:warning: Validation status: warnings

File
Status
Preview URL
Details

articles/concepts/dirac-notation.md
:warning:Warning
View
Details

articles/concepts/dirac-notation.md

Line 159, Column 88: [Warning-xref-not-found] Cross reference not found: 'microsoft.quantum.more-informationn'.
Line 58, Column 0: [Suggestion-table-syntax-invalid] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines. NOTE: This Suggestion will become a Warning in late September, 2020.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Determine and document the CCLA/ICLA process, both from contributor & administrator sides

Determine and document the CCLA/ICLA process, both from contributor & administrator sides
TF needs to determine and document the CCLA/ICLA process, both from the contributo and the administrator sides.
Documenting it from the contributor side will help encourage more contributions by setting up expectations up front.
Documenting it from the administrator side will help clarify the process overall while also ensuring consistent results and easier process handoff as particpants join and leave the project.
Documenting any processes enables clear and open iteration on the processes. It's impossible to iterate on or hold people accountable to a process that exists only as oral history.
What's known about the contributor process so far

A new contributor visits the Documentation site
The contrib chooses either an ICLA or a CCLA from the Google Drive
According to the instructions he contrib either "submit using the project's automated system" or "email a pdf file of this Agreement to<EMAIL_ADDRESS>There's also an instruction that "if necessary" they should send a printed original signed Agreement to LF.
…then what?

Questions about the contributor side of things

[ ] What guidance can we provide to contributors to help them decide whether an ICLA or a CCLA is the right choice for them?
[ ] There's an automated system? If so, where is it and what are the instructions for how a contributor should use it?
[ ] Under what conditions would a contributor need to snail mail an original signed copy of the CLA?
[ ] Does the contributor receive any notification when their CLA has been accepted and processed? If so…

[ ] Who is responsible for processing the CLA?
[ ] Who is responsible for notifying the contrib?
[ ] How will they be notified?
[ ] If there is a notification, in what timeframe can they expect to receive it (and therefore know that they can start work)?

What's known about the administrative process so far
…very little. :-)

Section 7 of the Technical Charter requires all code contributors to have a signed CCLA/ICLA as well as all code contributions requiring a DCO.
Contributing companies have an associated CCLA-companyname group in Gerrit (under People > List Groups; may not be visible to non-admins). These groups contain people who are approved to submit code on behalf of the respective company.
Each company also has a CCLA-companyname-Admin Gerrit group. The people in this group are authorised to add people to their respective CCLA-companyname group (read: approve them to submit code on the company's behalf).
The signed CLAs appear to be stored in a Google Drive folder

Questions about the administrator side of things

[ ] If CLAs are emailed to<EMAIL_ADDRESS>then how do they find their way to the TF community to process?
[ ] What does that processing look like?
[ ] And who is responsible for doing it (or making sure that it happens)?
[ ] As a new company shows up with a signed CCLA, who is responsible for creating the necessary Gerrit groups and what is that process?
[ ] The existing process doesn't appear to cover the ICLA situation and only handles the corporate/CCLA one?
[ ] These CLAs include private contact information for contributors. They therefore should not be stored in what is in essence a public location (since anyone can get access to the Google Drive). Can we please store them in a more private location? A private GitHub repo or…?
[ ] Is there a standard LF process for this that we should be using?

Answer: No. Each project follows its own process. Here is a summary of how the LFN projects each handle intellectual property

[ ] And does the process ever move from the community to LF or is it always community-driven?

Answer: It appears to be commuity-driven, but can potentially be supported by LF infrastructure. For instance Kubernetes and some CNCF projects use CLA Check.

And finally…

[ ] How is CLA/DCO status verified when a contribution is received?

Additional resources about this:

LFN Project CLA Processes
CCLA/ICLA administration processes from other projects

Migrated to Jira: https://jira.tungsten.io/browse/TFB-1394


edited some wording in the documentation to make it more readable, ad…

…ded some comments to accompany code and help users learn react hooks :)

Thank you @gone-explauren


Need ZF2 Skeleton

We have invested in ZF2 and need to continue using composer to build ZF2 (not ZF3) skeletons. How am I to do this now. This repository is now ZF3. Please advise. Thanks so much!

You can use:
composer create-project -sdev zendframework/skeleton-application:^2.3 path/to/install

Thank you 😆
On Jul 17, 2016 6:38 PM, "webimpress"<EMAIL_ADDRESS>wrote:

You can use:
composer create-project -sdev zendframework/skeleton-application:^2.3
path/to/install
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zendframework/ZendSkeletonApplication/issues/367#issuecomment-233208388,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AExDcwm-Vkv0JBv7gfx61mf1gt8kJvaXks5qWq8CgaJpZM4JOU-Y
.

it can be closed then.

Yes. Thank you. Please close issue.

if you're a @mnino  ===  @mnino-glanbia you can close it by @mnino account.

Thank you. Closed


[Maven] fix comment

The ! prefix will unignore the file.
Reasons for making this change:
The comment was misleading.
Links to documentation supporting these rule changes:
N/A
If this is a new template:
N/A

i find 'exclude' more appropriate

After thinking about this for a while, I'm not sure either term is better. I like this example from the Gradle template:
# Avoid ignoring Gradle wrapper jar file (.jar files are usually ignored)
!gradle-wrapper.jar

@shiftkey made change as per your suggestion.

@tjkemper thanks!


[BUG] : Enhancing Founder Section....

Description
Needs proper alignment of element under founder section. Can have detailed descripion of the founder beside element with active social links which are now unactive..Overall, the page can be enhanced...
Screenshots

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

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

@tech-dhawal-03 As of now, we do not need it. We will let you know in the future if there is a need. Please search for another issue and raise it, which I'm happy to assign to you.

Don't forget to join our official Discord server.
And also follow us on Linkedin
And please ⭐ our repo


Prepare Python Release

Release Checklist

[ ] Python CI #4
[ ] Manylinux 2014 on Linux x86 (python 3.8 - 3.10)
[ ] Intel / Apple Silicon release on Mac (target latest MacOS and default python3 version, which is 3.10)
[ ] NO conda
[ ] Verify that we can pip install into clean env with no libarrow* pre-installed
[ ] Verify we can import pyarrow and lance
[ ] Verify we can create a pyarrow dataset with lance.dataset

after this we can make first public release on pypi.org

Should we use https://github.com/pypa/cibuildwheel ?


Fix a11y issues with Pipeline logs

Fixes RHOAIENG-2105
Description

Fixing a11y issues with Pipeline logs section flagged by axe Devtools

DownloadDropdown button lacked an aria-label, Logs alert lacked a component prop

How Has This Been Tested?

Add axe Devtools Chrome extension to your Chrome browser
Once you have Pipeline logs page open(Click on any node on any pipeline run), open Developer Tools and look for the "axe Devtools" tab, and Click on "Scan ALL of my page".
Do the same after clicking on the "View raw logs" from the kebab menu on the extreme right of the LogViewer toolbar.

Test Impact

Will be added in a future PR
Request review criteria:

Self checklist (all need to be checked):

[X] The developer has manually tested the changes and verified that the changes work
[X] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[X] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[X] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

WIP to address "Serious" and "Moderate" issues

/retest

/retest

the tests weren't failing locally 😮💨


feat(fee): adding a slope parameters to the os resources

This change is

Codecov Report
Attention: 9 lines in your changes are missing coverage. Please review.

Comparison is base (07ab39c) 71.90% compared to head (934a07d) 70.84%.

Files
Patch %
Lines

crates/blockifier/src/fee/os_usage.rs
10.00%
7 Missing and 2 partials :warning:

Additional details and impacted files
@@                           Coverage Diff                           @@
##           noa/add_calldata_length_to_fee_flow    #1362      +/-   ##
=======================================================================
- Coverage                                71.90%   70.84%   -1.07%
=======================================================================
  Files                                       59       59
  Lines                                     7830     7610     -220
  Branches                                  7830     7610     -220
=======================================================================
- Hits                                      5630     5391     -239
+ Misses                                    1808     1797      -11
- Partials                                   392      422      +30

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


[Feature] Stick Table Header When Scrolling

Something like this:

Normal state:

Sticky state:

Reference: https://www.astralweb.com.tw/pure-css-implementation-table-headers-columns-fixed/

Confirmed to work at 2a47c4e0702f25f1a741181a4080df08cbf336c3 .


collections/fave error - deviationid required error

Hi
I am trying to fav a deviation id without providing any folders. Here is the request I am making.
I get the deviationid required error. I've tried the request multiple ways - as form url encoded request and as json body and as query parameters.
https://www.deviantart.com/api/v1/oauth2/collections/fave?deviationid=796D596F-A30E-54C0-5C2C-5FB37DC57CE2&access_token={REMOVED}
{"error":"invalid_request","error_description":"Request field validation failed.","error_details":{"deviationid":"deviationid is required"},"status":"error"}
What am I doing wrong? Or is this a bug?

I've tried several variations of this request including:
D/OkHttp: --> POST https://deviantart.com/api/v1/oauth2/collections/fave?access_token=01ed56e88e379ed25a32d1c50cb9be2c217a2c156e384bd0d6
D/OkHttp: Content-Length: 112
D/OkHttp: Authorization: Bearer 01ed56e88e379ed25a32d1c50cb9be2c217a2c156e384bd0d6
D/OkHttp: Content-Type: application/x-www-form-urlencoded
D/OkHttp: accept-encoding: gzip, deflate
D/OkHttp: Accept: /
D/OkHttp: access_token=01ed56e88e379ed25a32d1c50cb9be2c217a2c156e384bd0d6&deviationid=DBFB035D-54BE-7063-2F9C-721345B56823
I still get the same response:
{"error":"invalid_request","error_description":"Request field validation failed.","error_details":{"deviationid":"deviationid is required"},"status":"error"}

The rquest works in Postman as form urlencoded body but not in my app.
Is there anything you can tell me from the server side about what is different between the two requests?
My client id is 9785.
Any requests I have sent to this endpoint that have been successful have been from Postman and unsuccessful ones have been from the app.

Can you provide any insight on this? Maybe you can tell me what I'm doing wrong?

I added the www into the url and formurlencoded the request and that seems to have solved my issue.


[IMPROVEMENT] environment_check.sh should check for the iscsi_tcp kernel module

Is your improvement request related to a feature? Please describe (👍 if you like this request)
It would be helpful if the Environment Check Script mentioned in the docs (https://longhorn.io/docs/1.6.2/deploy/install/#using-the-environment-check-script) checked for the iscsi_tcp kernel module, because even if open-iscsi is installed, it's possible for that module to not be present. For example:
master:~ # curl -sSfL https://raw.githubusercontent.com/longhorn/longhorn/v1.6.2/scripts/environment_check.sh | bash
[INFO]  Required dependencies 'kubectl jq mktemp sort printf' are installed.
[INFO]  All nodes have unique hostnames.
[INFO]  Waiting for longhorn-environment-check pods to become ready (0/1)...
[INFO]  All longhorn-environment-check pods are ready (1/1).
[INFO]  MountPropagation is enabled
[INFO]  Checking kernel release...
[INFO]  Checking iscsid...
[INFO]  Checking multipathd...
[INFO]  Checking packages...
[INFO]  Checking nfs client...
[INFO]  Cleaning up longhorn-environment-check pods...
[INFO]  Cleanup completed.

master:~ # lsmod|grep iscsi
scsi_transport_iscsi   192512  1
iscsi_ibft             12288  0
iscsi_boot_sysfs       20480  1 iscsi_ibft
scsi_mod              344064  4 sd_mod,scsi_transport_iscsi,libata,sg

master:~ # modprobe iscsi_tcp
modprobe: FATAL: Module iscsi_tcp not found in directory /usr/lib/modules/6.9.3-1-default

This can happen on SLES and openSUSE systems when using minimal VM images where the kernel-default-base package is installed as opposed to kernel-default (see https://www.suse.com/support/kb/doc/?id=000021147).
Describe the solution you'd like
This should do it:
--- environment_check.sh.orig	2024-06-04 07:48:37.743329009 +0200
+++ environment_check.sh	2024-06-04 07:47:59.136662354 +0200
@@ -332,6 +332,7 @@
       return 1
     fi
   fi
+  check_kernel_module ${pod} CONFIG_ISCSI_TCP iscsi_tcp
 }

 check_multipathd() {

It's probably worth also adding a note to the docs that on SUSE-based distros you want kernel-default installed, not kernel-default-base.
Describe alternatives you've considered
Update longhorn-iscsi-installation.yaml to install kernel-default on SUSE-based distros to make sure the module is actually present. I'm somewhat wary of this though, because installing a different kernel package requires a reboot. I think it's better to leave installing/updating kernel packages for the user to do manually.
Additional context
N/A

Pre Ready-For-Testing Checklist

[x] Where is the reproduce steps/test steps documented?
The reproduce steps/test steps are at:

Install a SLES or openSUSE system (can be a VM) with kernel-default-base instead of kernel-default. Verify that modprobe iscsi_tcp fails with "Module iscsi_tcp not found"
Run the old version of environment_check.sh on the system, note that it succeeds.
Run the new version of environment_check.sh on the system, verify that it flags "[ERROR] kernel module iscsi_tcp is not enabled on master"
Install kernel-default on the system, re-run the new version of environment_check.sh and verify that it succeeds.

[x] Does the PR include the explanation for the fix or the feature?

[x] Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
The PR is at https://github.com/longhorn/longhorn/pull/8705

[x] If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)?
The documentation issue/PR is at https://github.com/longhorn/website/pull/920

[x] If labeled: require/manual-test-plan Has the manual test plan been documented?
The updated manual test plan is at
See reproduce/test steps above.

Verified on master-head 20240620

longhorn master-head https://github.com/longhorn/longhorn/commit/f5109e31d29f0ad0dbcdab6870afa1916796908e

The test steps
https://github.com/longhorn/longhorn/issues/8697#issuecomment-2167325572
Result Passed

Create a cluster via https://github.com/longhorn/longhorn-tests/tree/master/test_framework/terraform/aws/sles
Check iscsi_tcp via CLI sudo lsmod|grep iscsi
By default iscsi_tcp is not enabled
Enable it using CLI sudo modprobe iscsi_tcp
The new version of environment_check.sh will verify whether iscsi_tcp is enabled or not.

Miscellaneous

If you want to use a system with kernel-default-base, follow these steps:

Run sudo zypper refresh

Search for the kernel package: sudo zypper search kernel-default

Install the kernel package: sudo zypper install kernel-default-base

Reboot the system: sudo reboot

After installing kernel-default-base, if you run sudo modprobe iscsi_tcp, you will encounter the following error:
modprobe: FATAL: Module iscsi_tcp not found in directory /lib/modules/5.14.21-150500.55.65-default


feat(motion_velocity_planner): add new motion velocity planning

Description

Cherry-pick https://github.com/autowarefoundation/autoware.universe/pull/7064 to improve the out_of_lane module.
Related links

https://tier4.atlassian.net/browse/RT0-30426
Tests performed

Psim
Bag replay (to confirm fix of https://tier4.atlassian.net/browse/RT0-30426)
Notes for reviewers

Requires launch PR: https://github.com/tier4/autoware_launch.x2/pull/676
Interface changes

Effects on system behavior

Less wrong out_of_lane stops.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[X] I've confirmed the contribution guidelines.
[X] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

There is some unexpected issue with avoidance so we will wait for the beta/v3.1.0 branch before adding this feature.


Fix ingests with unusual display aspect ratios

Display aspect ratios were seemingly being ignored in the livepeer pipeline so for now we're fixing that by sending jobs to mediaconvert when the display aspect ratio doesn't match the resolution of the video

@thomshutt ready for another review 🙏


trollop changed its name to optimist

I think we should rename trollop to optimist
https://github.com/vmware/rbvmomi/blob/master/lib/rbvmomi/trollop.rb
Because the project name of trollop has been changed to optimist
== [3.0.0] / 2018-08-24

* The gem has been officially renamed to optimist

PR：https://github.com/ManageIQ/optimist/pull/99/files
History：https://github.com/ManageIQ/optimist/blob/master/History.txt

I made a PR for this: https://github.com/vmware/rbvmomi/pull/145

Fixed by #145


Updating guidebook component

Style updates to match design spec
Updating markup

article to div
Renaming guidebook__title-wrap to guidebook__header and using header element
h1 to h2, h2 to p

Removing some nesting in SCSS to improve scanability and searchability
Removing unused variables and prefixing variables with guidebook
Replacing respond-to mixin with plain CSS @media
Utilizing max-width MQs to avoid property duplication/overriding
Some clean up/formatting updates

Nice


Auto login after register

Fixes #505
Proposed Changes

After registration user is automatically logged into to MedTagger.
Replaced user id with token as an /register endpoint response body
Saving token and user info, then logging into app (classic login flow)

Looks great! 🔥