Download button problem when video in different quality

hello
i active download button for player in html5 video muti sources 480p and 1080p 2 quility
but download video button not select qulity for download. default in download 480 and when
change quility, when 1080 in play, download button clicked download 480 version and when player, play 480p and click on download video button, download 1080
that is, the opposite happens!
If it was possible to click on the video download button. The quality of the video, select to download, is also great
however, there's a problem download button at the moment
and it's designed for a time only to put the video in one quality
but I also need time for a video with some quality
I'm sorry to bother you
thank you very much

I'm not able to replicate this on https://plyr.io ? Could you give some more information or better an example codepen or jsfiddle? This is why we have the bug template (that you removed!) 👍


math.Pow takes float64, not int

Describe the bug
When the ** operator is used on integers in a list, they are passed to math.Pow as-is. This does not work because math.Pow takes float64 arguments.
Python code example
def main():
	x = [2, 4]
	print(x[0]**x[1])

if __name__ == '__main__':
  main()

This works without a list because an integer literal is an untyped int, which just becomes float64 when used in math.Pow
Current behavior
package main

import (
	"fmt"
	"math"
)

func main() {
	x := []int{2, 4}
	fmt.Println(math.Pow(x[0], x[1]))
}

Expected behavior
I expected there to be a type conversion to float64 before passing the value to math.Pow
Go code example
package main

import (
	"fmt"
	"math"
)

func main() {
	x := []int{2, 4}
	fmt.Println(math.Pow(float64(x[0]), float64(x[1])))
}

Sorry I've been neglecting this for so long! I've decided to start trying to take a look at this project again to see if there's any room to improve it using Go generics, and I figured I'd knock out an "easy" issue to help get back up to speed with things. Thanks so much for leaving this!
I was hoping I'd eventually get some other contributors to take on some of these fixes but I might need to do more work in terms of setting up contribution guidelines and cleaning up the codebase before that happens...


Can't calculate length of a struct: "reflect: call of reflect.Value.Len on struct Value"

I noticed there is a problem when using the length function (len(..)) on a struct.
When I remove this function, it works fine.
The following program sample.go triggers a panic:
package main

import (
	"github.com/containous/yaegi/interp"
	"github.com/containous/yaegi/stdlib"
)

const payload = `
package main

import (
	"fmt"
)

type Version struct {
	Major int
	Minor int
	Patch int
}

func main() {
	currentVersion := Version{
		Major: 1,
		Minor: 11,
		Patch: 3,
	}

	if len(currentVersion) == 3 {
		fmt.Println("hello")
	}

	fmt.Println("Done")
}
`

func main(){
	var err error
	i := interp.New(interp.Options{})
	i.Use(stdlib.Symbols)

	_, err = i.Eval(payload)

	if err != nil {
		panic(err)
	}
}

Expected result:
$ go run ./sample.go
hello
Done

Got:
$ yaegi ./sample.go
16:3: panic
panic: reflect: call of reflect.Value.Len on struct Value

Sorry, I didn't use array.
Found the problem, now it is fixed:
package main

import (
	"github.com/containous/yaegi/interp"
	"github.com/containous/yaegi/stdlib"
)

const payload = `
package main

import (
	"fmt"
)

type Version struct {
	Major int
	Minor int
	Patch int
}

func main() {
	currentVersion := []Version{
		{
			Major: 1,
			Minor: 11,
			Patch: 3,
		},
		{
			Major: 1,
			Minor: 11,
			Patch: 3,
		},
	}
	var a int

	if len(currentVersion) == 2 {
		fmt.Println("hello")
	}

	fmt.Println("Done")
}
`

func main(){
	var err error
	i := interp.New(interp.Options{})
	i.Use(stdlib.Symbols)

	_, err = i.Eval(payload)

	if err != nil {
		panic(err)
	}
}


[Coverage] Only instrument functions which are definitions

The ASTs for functions which aren't definitions may not be fully
typechecked or well-formed, so: avoid looking at them.
This fixes at least one assertion failure seen while building a project
with coverage, and is probably good for some substantial compile-time
improvements with coverage enabled.
rdar://39069115

@swift-ci please smoke test

Yikes, I still need to add check lines to the lit test.

@swift-ci please smoke test

@swift-ci Please Test Source Compatibility

@swift-ci Please Test Source Compatibility

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge


  For example, if the start_consumer_from_sequence was 50, you'd get the following error:
memphis: consumer already exists with different uneditable configuration parameters (StartConsumeFromSequence/LastMessages)

It would useful to support deleting a consumer without having to first create it.  Something like:
await memphis.destroy_consumer(station_name="station", consumer_name="consumer", consumer_group="group")

This would make it easier to support recovery and time travel (replaying messages) for streaming engines that expect to be able to own and set the starting sequence number.

@rnowling-memphis There's a code block already exists that destroys the consumer, then do we really need to create a new method!
async def destroy(self):
        """Destroy the consumer."""
        if self.t_consume is not None:
            self.t_consume.cancel()
        if self.t_dls is not None:
            self.t_dls.cancel()
        if self.t_ping is not None:
            self.t_ping.cancel()
        self.pull_interval_ms = None
        try:
            destroy_consumer_req = {
                "name": self.consumer_name,
                "station_name": self.station_name,
                "username": self.connection.username,
                "connection_id": self.connection.connection_id,
                "req_version": 1,
            }
            consumer_name = json.dumps(
                destroy_consumer_req, indent=2).encode("utf-8")
            res = await self.connection.broker_manager.request(
                "$memphis_consumer_destructions", consumer_name, timeout=5
            )
            error = res.data.decode("utf-8")
            if error != "" and not "not exist" in error:
                raise MemphisError(error)
            self.dls_messages.clear()
            internal_station_name = get_internal_name(self.station_name)
            map_key = internal_station_name + "_" + self.consumer_name.lower()
            del self.connection.consumers_map[map_key]
        except Exception as e:


Add compilation and tests for documentation examples

Test added to private repo for basic usage: https://github.com/nats-io/java-nats-examples/blob/master/src/test/java/io/nats/jnats/AppTest.java
We need to add tests for:

[ ] TLS
[ ] Wildcard Subscriptions
[ ] Queue Groups
[ ] Advanced Usage
[ ] Clustered Usage

Obsolete for 2.0, all examples are now from the examples folder.


Manual Review Required for Token Update

[- I'm submitting a ...
[ ] bug report
[ ] feature request
[ *] question about the decisions made in the repository
[ *] question about how to use this project

Summary

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)]

I am from the WOOF team and we would like to ask if you could change our logo to this updated, Solana colored one as we already changed it everywhere except onchain?

(https://github.com/solana-labs/token-list/pull/5958)

whoever originally committed woof should affirm that this is ok in this comment thread

In the PR tree, the original committer has written.
Please check it
https://github.com/solana-labs/token-list/pull/5958

merged

Thank you guys - really appreciate!
Would there be an option to exclude the 1nc1nerator111111111111111 burn wallet off our Total Supply please?
Coingecko and Coinmarketcap cant show the correct Max Supply as they dont belive the wallet is real.
Its 98% of our supply which is burned and is hurting our visibility on those platforms.
If not, do you know how other projects did it, when they used the 1nc1nerator wallet?
Thank you a lot and all the best!


specs: add QGB specs

Overview

Closes https://github.com/celestiaorg/celestia-app/issues/1872
Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Codecov Report

Merging #1911 (9817154) into main (bdbdeb0) will increase coverage by 0.62%.
The diff coverage is n/a.

:exclamation: Current head 9817154 differs from pull request most recent head a2e3e6c. Consider uploading reports for the commit a2e3e6c to get more accurate results

@@            Coverage Diff             @@
##             main    #1911      +/-   ##
==========================================
+ Coverage   21.22%   21.85%   +0.62%
==========================================
  Files         120      117       -3
  Lines       13696    13304     -392
==========================================
  Hits         2907     2907
+ Misses      10499    10107     -392
  Partials      290      290

see 5 files with indirect coverage changes


fix code issue scanned by Coverity

Rewrite code for passing the coverity check

@EikanWang @chengjunlu  this PR also need to be merged for the release


enlarged image not on top

I want Enlarged image on top.
I use bootstrap 4 for layout this page. Left is col-md-4 and right one is col-md-8.

I have this issue as well, using flexbox-react for layout.

I had this same issue and was able to fix it with setting the class name for the enlarged image and setting the z-index in the css.
jsx:
<ReactImageMagnify {...{             enlargedImageContainerClassName: "enlargedImage", ...
css:
.enlargedImage {   z-index: 1; }

I had this issue as well and solved it the same way: z-index: 1.


Fix build setup requirement

Updated linux-building page, so that android-tools-fsutils is now android-sdk-libsparse-utils.
Small change, no QA done.
No issue opened.
Readiness

[x] Merge (pending reviews)
[ ] Merge after date or event
[ ] Draft

Overview
Why merge this PR? What does it solve?
Checklist
Optional. Add a 'x' to steps taken.
You can fill this out after opening the PR. "Did I..."

[x] Run spelling and grammar check, preferably with linter.
[x] Avoid changing any header associated with a link/reference.
[x] Step through instructions (or ask someone to do so).
[ ] Review for wordiness
[x] Match tone and style of page/section.
[ ] Run make linkcheck.
[ ] View HTML in a browser to check rendering.
[ ] Use semantic newlines.
[x] follow best practices for commits.

[x] Descriptive title written in the imperative.
[x] Include brief overview of QA steps taken.
[x] Mention any related issues numbers.
[x] End message with sign off/DCO line (-s, --signoff).
[x] Sign commit with your gpg key (-S, --gpg-sign).
[x] Squash commits if needed.

[x] Request PR review by a technical writer and at least one peer.

Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

Docs for 65d7ecd1b7c634643b565a70115ac4f62695f5a6 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2507/docs/artifacts/html/index.html

From a research PoV this seems true:
https://packages.ubuntu.com/jammy/android-sdk-libsparse-utils
And android-tools-fsutils doesn't show up as a package anymore when I do a search by package name on the same page.
LGTM


pass relevant element into focus/blur handlers

This patch enables the below code to function according to expectaitons - e.g. that a handler attached to a component receives the node that belongs to that component, not the previous node (in the case of focus) or the next node (in the case of blur).
import React from 'react'

function focus(el) {
  el.style.border.bg = 'red'  //should change border of newly focused element
}

function blur(el) {
  el.style.border.bg = 'white' // should change border of recently blurred element
}

const MyCmp = () => (
  <list
    onFocus={focus}
    onBlur={blur}
  />
)

export default MyCmp

I am a bit confused about this topic @davidmarkclements. Does this introduce a difference between how blessed would work itself?

no I don't think so - details of blesseds event system seems to be lacking, here's the deal

blessed emits an event - e.g. "select"
alongside that event it emits a secondary "sub event" e.g. "item" or "tab"
the event and subevent are (apparently) separated by a white space "select tab" (for instance)
so what actually comes through as the type param to this._eventListener is "select tab"
we pass type to start case making it "Select Tab" and we look for a prop on the user component called Select Tab
as far as I know you can't put props with spaces on a component with jsx (maybe there is some way, but it would certainly be unconventional)
So we have two choices, go generic  type.split(' ')[0] (onSelect) or go specific type.replace(/ /, '') (onSelectTab)
seems to me that going specific is the safest choice

Ok, I see your point and will merge. However, I think this issue may be raised to blessed just to be sure it was designed thusly on purpose.


Permission to use architecture diagram

Hi, I'm currently writing my PhD thesis whose topic is about graph visualization and in my thesis I want to use the image of architecture diagram in the Readme of your repository. I ask for your permission to be able to use this image in my thesis. If you give permission, I will cite the url of the image unless you want me to cite another resource.
Thanks in advance!

You can use the image as it is covered by the Apache license we have in this repo. Best of luck on your thesis!


Ignore all .iml files

Intellij also puts .iml files in sub directories if they are configured as modules (for example having main and test configures as separate modules).

Thanks, merging.


pip prop does not initiate pip

Be sure to search for your issue before opening a new one.
Current Behavior
pip prop doesn't actually enable pip. Using the demo app, pip control is never showing up in the regardless of source, and using React dev tools to toggle the prop on and off does nothing.
Expected Behavior
Expected to see the pip control button at least for something... and expected toggling the pip prop to turn pip on
Steps to Reproduce

Visit https://cookpete.com/react-player/
Load every test source

Environment

URL attempting to play: https://cookpete.com/react-player/
Browser: Chrome/Safari
Operating system: MacOS 10.14.5
jsFiddle example: n/a but fwiw doesn't work if adding a pip prop to this either https://jsfiddle.net/86ewraov/

Other Information

I've tried using a ref to initiate pip on the video object - but the  is not actually accessible as far as I can tell. I can however access the  tag in Chrome console and initiate pip programatically that way - document.getElementsByTagName('video')[0].requestPictureInPicture()
I don't know enough about refs to know if I can target the  element to be able to call this method or not, but so far all my efforts have been fruitless.

If manually calling requestPictureInPicture on the element is working then something weird must be going on, as that's exactly what ReactPlayer does
Note that pip is only currently supported when playing video files in recent versions of Chrome. I can visit https://cookpete.com/react-player in Chrome 76 on macOS and PIP works fine for any of the Files URLs (apart from the mp3):

Also note that there is a static method to check if PIP is supported: ReactPlayer.canEnablePiP(url)

Ah.. "when playing video files" is the key. I didn't get as far down the list as testing the files - gave up at DailyMotion! Thanks for helping me troubleshoot.
I couldn't determine that this is a limitation to the Chrome implementation. Can you point me in the direction of where to find info on this?
Would also be helpful to have this limitation visible in the Readme :)

I couldn't determine that this is a limitation to the Chrome implementation. Can you point me in the direction of where to find info on this?

https://developers.google.com/web/updates/2018/10/watch-video-using-picture-in-picture

Did you figure out how to work PiP with the youtube & other embeds?

Did you figure out how to work PiP with the youtube & other embeds?

@kenakingkong it's a limitation of the API that you need to have access to the  tag, and where youtube et al use iframe, you run into same-origin issues trying to reach in and call the PIP function. So until these streaming providers expose an API for PIP that is easily included in this library, we're stuck with file-only PIP.

@kenakingkong it's a limitation of the API that you need to have access to the  tag, and where youtube et al use iframe, you run into same-origin issues trying to reach in and call the PIP function. So until these streaming providers expose an API for PIP that is easily included in this library, we're stuck with file-only PIP.


Add expectDocCommentIncludes assertion

Adds an assertion to check the documentation comment of a given expression:
/** FooBar */
const foo = 'bar';

expectDocComment<'FooBar'>(foo);

Fails if the type parameter does not exist, is not a string literal, or does not match the given expression's doc comment.
In one project, I have a function that takes a set of user-defined extension functions and maps them onto the built-ins. expectDocComment can help ensure that the type hinting for the user-defined extensions are mapped correctly.

It doesn't really make sense to me that it's matching the whole doc comment. That would make the assertion huge. I think something like expectDocumentationCommentToContain() would be more practical. So you can assert that the doc comment contains a certain substring.

I agree, I wanted to see what your thoughts were before making the match non-exact. I went with expectDocCommentIncludes since it's less verbose and matches string.includes().

Can you fix the merge conflict?

Merged.


From survey builder, add ability to edit survey description (text at top)

E.g..

Right now the survey builder does not give the user the capability of editing the text near the top of each survey, which is customized from time to time.
This is needed in order to finalize the setup of the CPAP Adherence survey (currently on staging).

To note, the description for CPAP Adhernece is:

We are interested in getting some feedback from patients about how much they use their CPAP, and what motivates them to use CPAP.  Our hope is that the responses we receive will help guide us as we think about new ways to support patients as they begin and continue to use CPAP.
Please complete this survey if you have ever used CPAP at home (currently, or in the past).  Please note that the word ‘CPAP’ here refers to CPAP or any similar device including: auto-PAP, flexible pressure, expiratory pressure-relief, and bi-level PAP.


[Feature-14863][API] Support to manage what worker groups can be used for a project.

Purpose of the pull request
This PR will close #14863.
Brief change log
Verify this pull request
This change added tests and can be verified as follows:

Manually verified the change by testing locally.

The testing results are as follows:

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

Comparison is base (8a35e8b) 38.55% compared to head (b718908) 38.58%.

:exclamation: Current head b718908 differs from pull request most recent head f918784. Consider uploading reports for the commit f918784 to get more accurate results

Files
Patch %
Lines

...ce/impl/ProjectWorkerGroupRelationServiceImpl.java
61.79%
26 Missing and 8 partials :warning:

...r/api/controller/ProjectWorkerGroupController.java
40.00%
3 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##                dev   #15600      +/-   ##
============================================
+ Coverage     38.55%   38.58%   +0.02%
- Complexity     4777     4784       +7
============================================
  Files          1310     1312       +2
  Lines         44880    44942      +62
  Branches       4808     4796      -12
============================================
+ Hits          17305    17341      +36
- Misses        25692    25712      +20
- Partials       1883     1889       +6

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


Improve logging messages for world state recovery

The recoverWorldState method only logs the message that it started recovery after a correct block has been found. This may give the impression that the kernel is stuck, while in fact, it is searching through the block history for a correct block.
More logs need to be added to inform the user of the progress.

also, add a functionality for increasing the speed of search when it cannot find a block with a correct state easily


comment error.

Constant STATUS_NOT_FOUND‘s comments  is same as STATUS_FAILED .(in DownloadManager.java)
/**
* Status when the download has failed.
*/
public final static int STATUS_FAILED = 1 << 5;
/**
 * Status when the download has failed.
 */
public final static int STATUS_NOT_FOUND = 1 << 6;

Thanks. Updated.https://github.com/smanikandan14/ThinDownloadManager/commit/28d20cc7468b3182e83e23bf5c66019acacf6b06


Fix rbd volume for libvirt driver

Fix https://github.com/hyperhq/runv/pull/109 https://github.com/hyperhq/runv/pull/108
Depends on https://github.com/hyperhq/runv/pull/110

should not modify the code under Godep directly. code here will be overwritten when we update the dependencies.

Here is indeed a dependency update. We can't wait for libvirt-go upstream to accept it.

then you should also update the Godeps.json

sure


Make product unavailable if price is empty to avoid exception when adding product without price to basket

Fixes #1912

Shouldn't we use the pricing policy to determine if a price is available?

@mvantellingen right, I'll move check to pricing police. But in general, what do you think about solution?

@mvantellingen updated PR. Please check.


Make cat-angular to an npm module

NPM provides frontend dependency management features. Some libraries don't support bower (e.g. angular2). Having two frontend package management mechanisms would be an overkill for us, therefore we decided to go with npm only.
In order to be able to use cat-angular with npm, we need the dist folder to be part of the npm package.

Ping. Plan, opinion?

https://www.npmjs.com/package/cat-angular


Fix for CLOUDSTACK-8937 - XenServer migrations with storage failing i…

…n clustered management server environment
This pull request relates to the following Jira bug report:
https://issues.apache.org/jira/browse/CLOUDSTACK-8937
A previous fix was proposed for the 4.5 branch here: https://github.com/apache/cloudstack/pull/925
This was tested within a working environment and everything appeared to work fine.
@remibergsma Unfortunately I have not been able to test this within a running environment. Everything appears to compile ok and tests pass. I believe you are much further along in the Cloudstack automated testing arena, so I'm not sure if this is something you would be able to test at some point in the future?
If not I will be able to test it when my current workload permits and report back here with my findings.

LGTM, anyone tested this yet?

Ping @bhaisaab @atrbgithub
If I get some details on how to test - steps - I can give it a try.
Cheers,
Wilder

Hi @wilderrodrigues
To test this you would need to have 2 or more cloudstack management servers operating in a cluster with Xen hosts. Before applying this fix, when you try to live migrate vm's between hosts (root disks on local storage or primary storage), occasionally this will fail. It is random depending on which management servers are allocated the job.
After applying the change in the pull request, migrations should no longer fail.
Hope that is ok.
Thanks!

Hi @atrbgithub
Yes, the info clarifies feel things, but unfortunately I'm also busy and do not have time to write a test to cover it. I also have some refactoring/development to do and cannot be 100% allocated to write tests to run against other PRs.
Since you mentioned in your comment that Everything appears to compile ok and tests pass I thought you were talking about existing integration tests.
Unfortunately, unless someone tests this PR with the setup provided by @atrbgithub, I will have to hold a :-1:  against it.
Cheers,
Wilder

@atrbgithub please rebase against latest master and push -f, update on status of your PR

I believe this can be closed now. https://github.com/apache/cloudstack/pull/1336 and https://github.com/apache/cloudstack/pull/1596 address this problem.

closed as #1336 and #1596 address this problem.


Incorrect state management after VAO emulation

In this notebook: https://observablehq.com/@rreusser/strange-attractors-on-the-gpu-part-2
The particles use a VAO. It should look like this:

but when I disable the VAO extension, causing the particles to fall back to VAO emulation, the particles render correctly but the grid is incorrect:

The full axes command is:
  const drawFaces = regl({
    vert: `
    precision highp float;
    uniform mat4 uProjectionView, transform;
    uniform mat3 normalMatrix;
    attribute vec3 position, tangent, bitangent, normal;
    varying vec2 coord;
    varying vec3 p, n, t, b;

    void main () {
      ...
      gl_Position = uProjectionView * vec4(p, 1);
    }`,
    frag: `
    #extension GL_OES_standard_derivatives : enable
    precision mediump float;
    varying vec2 coord;
    varying vec3 p, n, t, b;
    uniform vec3 eye;

    void main () {
      ...
      gl_FragColor = vec4(vec3(0), alpha);
    }`,
    attributes: {
      position: boxVertices,
      normal: boxFaceNormal,
      tangent: boxFaceTangent,
      bitangent: boxFaceBitangent
    },
    uniforms: {
      transform: mat4scale(...),
      normalMatrix: mat3normalFromMat4(...),
      eye: regl.context('eye')
    },
    depth: { enable: true, mask: true },
    cull: { enable: true, face: 'back' },
    blend: {
      enable: true,
      func: {srcRGB: 'src alpha', dstRGB: 'one minus src alpha',
 srcAlpha: 1, dstAlpha: 1 },
      equation: { rgb: 'add', alpha: 'add' }
    },
    primitive: 'triangles',
    elements: boxFaceElements
  });

My hypothesis is that the position attribute is in the right state but that one of the normal, tangent, or bitangent attributes (which cause the grid to render correctly) are not in the correct state after using a VAO command.
I'll see if I can, but I don't yet have a more focused reproduction of the bug.
Attribute 0 of particle rendering has divisor 0, all others have divisor 1. That could potentially be a cause.

Confirmed, here is a notebook which reproduces the issue: https://observablehq.com/d/243a0f078d6865bd
The code is as follows. If the context is initialized with the OES_vertex_array_object extension, then the result is as expected: two red triangles using instancing and vao, and then a plain triangle with vertex colors using nothing fancy.
However, disabling the vao extension causes the OTHER draw command to render incorrectly.
const regl = createREGL({
  extensions: ['ANGLE_instanced_arrays', 'OES_vertex_array_object']
});

const vao = regl.vao([
  { divisor: 0, buffer: regl.buffer([[-0.1, -0.1], [0.1, -0.1], [0, 0.1]]) },
  { divisor: 1, buffer: regl.buffer([[-0.2, 0.4], [0.2, .4]]) }
]);

const drawWithVAO = regl({
  vert: `
    precision highp float;
    attribute vec2 xy, tri;
    void main () { gl_Position = vec4(xy + tri, 0, 1); }`,
  frag: `
    precision highp float;
    void main () { gl_FragColor = vec4(1,0,0,1); }`,
  attributes: { try: 0, xy: 1 },
  vao,
  depth: { enable: false },
  primitive: 'triangles',
  count: 3,
  instances: 2
});

const drawTriangles = regl({
  vert: `
    precision highp float;
    attribute vec2 xy;
    attribute vec3 color;
    varying vec3 vColor;
    void main () {
      vColor = color;
      gl_Position = vec4(xy, 0, 1); }`,
  frag: `
    precision highp float;
    varying vec3 vColor;
    void main () { gl_FragColor = vec4(pow(vColor, vec3(0.454)),1); }`,
  attributes: {
    xy: { buffer: regl.buffer([[-0.1, -0.5], [0.1, -0.5], [0, -0.3]]) },
    color: { buffer: regl.buffer([[1, 0, 0], [0, 1, 0], [0, 0, 1]]) }
  },
  vao,
  depth: { enable: false },
  primitive: 'triangles',
  count: 3
});

regl.poll();
drawWithVAO();
drawTriangles();

Can still reproduce this issue.


CLI Output seems to be not responsiv

The output from the slicing process is not in real time. The data is only recieved when the process ends.
https://github.com/FlorianJa/SlicerConnector/blob/f6431b31d1263cc6b26723a7dba61ae93f1925cf/SlicingBroker/PrusaSlicerBroker.cs#L52-L76

I have been trying to trace this issue, but it looks like the code itself have been changed, is this is still a relevant issue?

Yes, its still relavant. I disabled the consumer of these events because they did not work as expected.

Looks like maybe the issue might be related to the prusa process itself

Tried it with a separate application that prints to the console and still same problem


yarn run start does not work with fresh init — web page hangs

Environment

macOS Mojave 10.14.6 (18G95)
Node v12.10.0
npm 6.11.3
yarn 1.17.3

Steps to Reproduce

Run npm init @open-wc
Scaffold a new web component and say yes to everything, i.e.✔ What would you like to do today? › Scaffold a new project
✔ What would you like to scaffold? › Web Component
✔ What would you like to add? › Linting, Testing, Demoing
✔ Would you like to scaffold examples files for? › Testing, Demoing
✔ What is the tag name of your application/web component? … my-component
✔ Do you want to write this file structure to disk? › Yes
✔ Do you want to install dependencies? › Yes

Select Yarn as the package manager:✔ Do you want to install dependencies? › Yes, with yarn

cd my-component
yarn run start

Expected Behavior
Server starts and browser tab opens to demo page.
Actual Behavior
Server starts and browser tab opens to a blank page. Initial HTTP request is never fulfilled.
Terminal Output
$ yarn run start
yarn run v1.17.3
$ es-dev-server --app-index demo/index.html --node-resolve --open --watch
es-dev-server started on http://localhost:8000
  Serving files from '/my-component'.
  Opening browser on '/demo/'
  Using history API fallback, redirecting non-file requests to '/demo/index.html'

DOM Output
<!doctype html>

  <meta charset="utf-8">

Additional Info
When using npm run start, works as expected.
Terminal Output
$ npm run start
npm run start

><EMAIL_ADDRESS>start /Users/Hugh/Sites/redblue-test/my-component
> es-dev-server --app-index demo/index.html --node-resolve --open --watch

es-dev-server started on http://localhost:8000
  Serving files from '/Users/Hugh/Sites/redblue-test/my-component'.
  Opening browser on '/demo/'
  Using history API fallback, redirecting non-file requests to '/demo/index.html'

DOM Output
<!doctype html>

  <meta charset="utf-8">

        <my-component>
          some more light-dom
        </my-component>

Shadow DOM Output

Hello owc World! Nr. 5!

      <button>increment</button>

I tried to run the same steps, I dont get any errors. Is your version of yarn up to date


Adding more event object to the calendar

Hi Matt,
How do you add more object to the events array?
Normally you just pushing title, type, startsAt and endsAt from the directive. I want to add more like priority etc...
When i add priority  as an example to the current event i get undefined.

Sorted thanks managed to get a solution. Thanks to you new documentation awesome.


Remove clean_string function

Close #15

@phish108 Is #12 related?

@stlozhaw indeed, seems to be related to #12.


Browser hashes & queries getting lost in server (universal, server-side) example

In the server (universal) example, when I try to access http://localhost:8080/#foo via browser, the hash kind of disappears and the url transitions to http://localhost:8080/.
I found out that the hash and query properties in routing in the initial state (which is globally accessible at window.__initialState__) are empty strings.
When I remove the routing property on the client, the hashes and queries stay as intended, but I don't think it is a really good way to solve it.
What is the smartest way to handle this problem?

Hashes aren't communicated to the server. But it seems like we're converting the URL to have a hash of empty string instead of null/undefined. Not sure if this is a bug here or in history, but it definitely is the cause of the problem.

I'm having the same issue with browserHistory. As @glennreyes said, I was able to work around it by discarding the routing state sent down by the server, but this may create issues with apps that manipulate router state via redux actions.

In which cases are routing information in the initialState needed?

I'm not sure frankly. This lib is new to me - but I imagine something along the lines of the following:
Lets say I have a static needs(params, store): Promise method on my view components. This is called on the server as part of the async universal rendering flow defined in the react-router docs. And in this fn, I'm doing an API call for a particular resource, which happens to 404.
I feel like this is where I'd like to redirect to not-found component or some other page - and this would be the place to do it - all nicely encapsulated with redux.

I'm like 99% sure this is a history thing which is fixed in 3.0 with some of the state and key changes. Once Router has support for 3.0, we should be good.

I'm still seeing this issue. All my querystrings are lost in the server (they don't get passed to initial state).

I'm also dealing with this issue -- is there anything that can be done in the short term until support for history 3.0 is added to react-router?

@kelchm I had react-router-redux running and I could solve it by dealing with the state of search in state.routing.locationBeforeTransition. Hope this little detail helps you out a bit.

I actually fixed it somewhere on the server but this brought me to the root problem. 👍


reproduce Testing Farm's package installation

I've been debugging a weird failure in https://github.com/cockpit-project/cockpit-machines/pull/601. Long story short, it was because the packit/TF run ended up with the distro package version cockpit-machines-264-1, instead of the PR's COPR build (262.5.gblablabla). Yes, the distro version is newer -- long story, not important here.
The main issue is that it is totally not obvious how to install the tested package (locally built RPM or the automatically created COPR build) with tmt. The TF log makes it very obvious that TF spawns the machine, then has completely custom code to install the RPM from copr, and only then invokes tmt on that machine (supposedly with the provision --how connect?).
I find it rather hard to explain it to someone else how to reproduce a PR test failure locally with tmt run provision --how virtual. One has to jump through several hoops, like tmt run --until prepare, then figure out how to ssh in (tmt run login -l seems to destroy state, so one has to fish for the run-specific ssh command and the identity key), download/install the rpm, and then continue with --until report -l, then investigate the failure, and finally clean up with tmt run --since report -l.
I would like some way how to inject the package installation (or at least installing the copr repo) into the tmt command line, and Testing Farm to use that instead of its custom code. So that the whole run becomes reproducible locally, and the package installation becomes part of the tmt test log.
I don't particularly care about the "how" -- this could be something tailored such as --install-rpm, or something generic like running a shell script hook in between prepare and execute.

@TomasTomecek FYI, what we discussed on IRC.

@martinpitt yes, this is coming, @psss can point you to some tickets. We will unify how the artifacts are installed, tmt will takeover the responsibility, so it is reproducible in all environments (including your localhost)

@martinpitt for the particular run you have, it is now this:
https://artifacts.dev.testing-farm.io/246b3cdc-7f7e-46a1-b648-29855390e236/guest-setup-6b8652d0-3716-49d4-8df7-5402fec97df1/artifact-installation-6b8652d0-3716-49d4-8df7-5402fec97df1/

@thrix ! Glad to hear! I see, so currently there are some Ansible scripts which set up the VM, install the packages, and call tmt.
Cheers!

@martinpitt

there are some Ansible scripts which set up the VM

yes, they are here:

https://gitlab.com/testing-farm/infrastructure/-/blob/testing-farm/ranch/public/citool-config/guest-setup/pre-artifact-installation/entrypoint.yml
https://gitlab.com/testing-farm/infrastructure/-/blob/testing-farm/ranch/public/citool-config/guest-setup/post-artifact-installation/entrypoint.yml

install the packages, and call tmt

This is not done by Ansible, we have Python code doing that.

All these pieces will move under tmt, while the playbooks will be part of a tmt profile. And there will be different profile for Packit, Fedora CI, RHEL CI, CentOS Stream CI. We want to make the test environment prepartion well documented and available for contributions, so the CI communities can own and improve them.

Turns out that tmt can already do that. I just managed to reproduce a packit/COPR TF run from https://github.com/martinpitt/python-dbusmock/pull/160 with
tmt run --verbose --all prepare --how install --copr packit/martinpitt-python-dbusmock-160 --package python3-dbusmock-0.28.4-1.20221005140834271905.pr160.11.g7b122ec.fc37.noarch provision --how virtual --image fedora-37

With the improved "show me all logs" UI, all this information can at least be pieced together without having to manually type URLs "that one needs to know" :grin:
#1018 is the same thing, thus I am closing my issue as a duplicate.  Indeed let's fix the tmt reproducer steps, but no need to track this in two places.


Cooper pair box

What
It adds the class CooperPairBox model to chip.py
Why
Additional functionality for regions where code of Fluxonium model fails.
How
I calculate the Hamiltonian in charge basis a-nd diagonalize to be again in energy basis. The transformation to the energy basis is done for the initial ng-value.
Remarks
I noticed that sometimes tf.range() does not what it should when the used dimensions size is big.
Regarding the checklist below
-I don't know how to write tests properly.
-I am  not sure if a notebook is really necessary. You could just take the two_qubit_example and use CooperPairBox instead of Transmon except that I am not sure If coupling will work in the same way.
-The Documentation is generated automatically, isn't it? If not I don't know how to update it.
-Don't know how to add something the Upcoming Release section
Checklist
Please include and complete the following checklist. Your Pull Request is (in most cases) not ready for review until the following have been completed. You can create a draft PR while you are still completing the checklist. Check the Contribution Guidelines for more details. You can mark an item as complete with the - [x] prefix

[ ?] Tests - Added unit tests for new code, regression tests for bugs and updated the integration tests if required
[x] Formatting & Linting - black and flake8 have been used to ensure styling guidelines are met
[x] Type Annotations - All new code has been type annotated in the function signatures using type hints
[x] Docstrings - Docstrings have been provided for functions in the numpydoc style
[ ?] Documentation - The tutorial style documentation has been updated to explain changes & new features
[ ?] Notebooks - Example notebooks have been updated to incorporate changes and new features
[ ?] Changelog - A short note on this PR has been added to the Upcoming Release section

Re: Tests
The contributing guide has a section on tests to help onboard new contributors to writing tests for their code. The basic idea is to convert one of the scripts that you are using for checking your code into the structure for a test script following the pattern seen in the other tests in our repo. It also includes a link to resources to better understand how to write tests in python. Can you please go through them and let us know if they are not adequate/useful enough to help you write tests for this PR? We can use this feedback to improve the onboarding document.


permission

[Enter feedback here]

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

ID: 89132320-da86-8a4e-4468-cf651561892c
Version Independent ID: 4946284d-9666-4a15-9e03-72377693ecb0
Content: Copy Files Over SSH task - Azure Pipelines
Content Source: docs/pipelines/tasks/deploy/copy-files-over-ssh.md
Product: devops
Technology: devops-cicd
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

@lucassms9 Thank you for the feedback.
Can you please include more information surrounding this issue?


Uploading a stemcell of size 13GB gives error

We have a stemcell which we built from a vmdk file and has a file size of 13 GB.
When we tried to upload this to our director, obtained this error -

Uploading stemcell file:
Director responded with non-successful status code '413' response '
413 Request Entity Too Large

413 Request Entity Too Large
nginx

'
Exit code 1

Read through the bosh documentation that the size limit is 10GB only. Is there any way to increase this limit. Any one know how to modify nginx settings to increase this size.

yes, it's a setting for nginx that you can modify. i've found (and
adjusted) it for regular cloud-foundry/bosh
On Thu, Sep 7, 2017 at 5:58 AM, Ramya SG<EMAIL_ADDRESS>wrote:

We have a stemcell which we built from a vmdk file and has a file size of
13 GB.
When we tried to upload this to our director, obtained this error -
Uploading stemcell file:
Director responded with non-successful status code '413' response '
413 Request Entity Too Large 413 Request Entity Too Large
------------------------------
nginx '
Exit code 1
Read through the bosh documentation that the size limit is 10GB only. Is
there any way to increase this limit. Any one know how to modify nginx
settings to increase this size.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/bosh-lite/issues/437, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACdOJtS2vqQUH-82CM_WrKv3b3G8tWvCks5sf74xgaJpZM4PPk6z
.

@grafpoo  It would be a great help if you can point us to any link where we can get more details about tweaking the settings for nginx.

Hi - typically you should be using the stemcells from bosh.io for BOSH Lite / Warden. The VMDK stemcells are not supported in bosh-lite, and I don't think you'll be able to deploy to them after uploading. I'd strongly recommend using the stemcells from bosh.io to get started.
Do you mind describing why you're needing to create stemcells? We don't recommend this because they diverge from our officially maintained images with our base security and system settings that releases expect. Any customizations to VMs should be happening through BOSH releases which helps keep the stemcells relatively slim (much, much less than 13GB).

Hi, Thank you for the reply. We have experimented with the default stemcell that was available with bosh.io. However our research deals with usage of Windows 2012 R2 on VSphere. Hence the need for creating custom stemcell.
If someone can point out to a link or blog where in we can modify the file size limit and also on how to login to the Director, it will help us in proceeding with our exploration as currently we are stuck in this step.


Add examples for recursive fields in arangosearch Views & combining POSITION() with the array expansion operator

Submitting this PR per a discussion on Slack with @Dronplane and @Simran-B. When I first read this part of the documentation it wasn't clear to me where exactly to put the sub fields array.

@larsborn Should the 3rd POSITION() example point out that you don't need POSITION() if you only want to test whether a value is contained in a list of objects (boolean), like FILTER "value" IN doc.arr[*].attr?

I'll also make that point in the paragraph above. (in particular where returnIndex is described). Reasoning: When I read that sentence I thought POSITION is the way to go here. Along the lines of "why would there be the returnIndex argument if I'm supposed to use something entirely different?".

@Simran-B thanks for your patience and the additional paragraphs. This is ready for your review and thanks in advance!

@larsborn Thanks! returnIndex is specifically about getting the index back, which isn't possible with the IN operator. It makes more sense to me to reference it in a different place. Given the existing content and conventions, it makes the most sense to me to place it below the parameter description.

Sounds good!

A co-worker pointed out that using POSITION() can in fact be faster than using the IN operator, which I wasn't aware of. The function is compiled C++ code, whereas the AQL language construct iterates over VelocyPack data - which is potentially slower. However, you need to use the IN operator if you want to utilize indexes, and then it's a different story again. I thus reverted the recommendation of using IN over POSITION() that I had added.

Our example generation doesn't support forks, but I tested it locally and will use https://github.com/arangodb/docs/pull/1340 to re-generate them now.

Thanks a lot!

A co-worker pointed out that using POSITION() can in fact be faster than using the IN operator, which I wasn't aware of. The function is compiled C++ code, whereas the AQL language construct iterates over VelocyPack data - which is potentially slower. However, you need to use the IN operator if you want to utilize indexes, and then it's a different story again. I thus reverted the recommendation of using IN over POSITION() that I had added.

This is an interesting detail. Just so I fully understand it: given the list to iterate is very large then POSITION is (probably) faster if there's no index on the field being searched and IN is faster (probably) if there is an index? If that's really the case, should we document that? (happy to cobble together a first draft here again)

Basically yes, but I don't have any data to back this up, and there could be additional aspects, like memory utilization. There has also been a recent change to avoid copying data that might be related to the IN operator, although I'm not sure, but there is always a chance that the AQL optimizer is improved to automatically transform queries to better execution plans. Therefore, I wouldn't currently add any recommendations to the docs without hard evidence that one approach is clearly better than the other for a given situation, across different hardware configurations.


[VPS 0.4.121 - latest] +config.ts not respect alias import

Description
When I tried to import a custom layout in a specific page --> Impor that layout in +config.ts with alias(auto import from VsCode) ---> Not work.
The field config in pageContext will display like this Layout: '_import:#/layout/LayoutMain:default'. Normally, must be displayed like [Function: Mainlayout].
But when I tried to import with ../../layout/LayoutMain.tsx --> Worked. Hope you can take a look
Error Message + Error Stack
No response

That's very much possible. (And it's actually also on my to-do list to support aliases 🙂). Let me have a look.

Fix released in 0.4.122.


Losing connection...

Hi! Thank you so much for developing this app. I'm running the latest software updates on both the Karoo 2 and Ki2, and I moved the wireless transponder to be as close to the Karoo 2 as possible, however, I'm still losing connection with Ki2 after a 1 minute into my ride. The connection will randomly come back during the ride, but only for a few seconds. I've deleted the Ki2 and reinstalled it, but to no avail. Any other suggestions for how to maintain the connection? I have no other sensors loaded and do not typically connect my phone to the Karoo. Thanks!

Hi, you need to debug the problem on our side, I can give you some guidance to follow:
1 - Do you have Di2 registered in other devices? For example, do you have Di2 registered in a Garmin watch? If yes: try to have Di2 only added in Karoo an not in other devices at the same time.
2- Even if the Di2 wireless transponder is close to Karoo, try to check for signal quality:

It could be a signal issue, verify the signal between the wireless unit and Karoo. To do that, tap on the shifting device on the list of devices in Ki2. The signal value is displayed on the top when the shifting unit is connected. Signal values between -30 to -60dBm offer best and stable connectivity while a signal in range of -75 to -90dBm is degraded and can cause connectivity issues. There is nothing that can be done in the app/software to improve the signal. Recommendation is to move or rotate the shifting wireless unit, perhaps moving it a small amount could be enough or in some cases it may require relocating the wireless unit to another location in the bicycle closer to Karoo.

Other than that I'm not aware of any problems, so the issue might be with your setup. Can you try Di2 with another device?

Thanks for the response. The transponder is between -30 to -60 dBm, mostly in the -40 range and is located as close to the Karoo as it possibly can be. I have E-Tubes app on my iPhone for updating the software, but no other devices connected to the Karoo or to the Di2. I never had connection issues with the old set-up directly to the Karoo software. I'm wondering if an update to the Karoo interfered with the connection. 🤷🏻♀

So today I went for a 28 mile ride and decided to connect my iPhone to the Karoo 2 for messages. The Ki2 stayed connected the entire ride. I'm not sure what connecting my phone did, but maybe that's my solution!

I have the broken connection problem also. Very easy to repeat by stopping a ride  when connection lost and then restart ride again after some seconds and then after some seconds K2 connects again. The connection stays on and active something like 70-80s, displaying gear changes perfectly. Then the K2 display freezes, it stops showing the gear changes. The freeze state stays around 10-20sec and then K2 shows a message for the gears like waiting for connection. The battery status display stays on but I don't know if it's updated correctly.
I have auto pause enabled in K2, speed 4.0kph. Today I rode 80km and tested the am. sequence, very easy to repeat. Start ride, switch gears, monitor that gear changes are displayed correctly K2. Then after a while the K2 display freezes - it doesn't show gear changes anymore - and then wait some seconds more and K2 gear display boxes shows a message like connection lost or waiting to connect.
My setup on the bike is as follows:
Shimano Ultegra R8170 Di2 complete group using wireless shifters. Derailleurs are wired. Battery is inside the seat post. I don't have any additional Shimano wireless units.
K2 attached into middle and front of handlebars. Distance from K2 (middle of screen) to shifters (top of hood) around 21cm.
Software Versions:
Derailleurs:
FD: FD-R8150 V4.1.0 - latest 30.03.2023
RD: FD-R8150 V4.1.0 - latest 30.03.2023
Shifters:
ST-R8170-L V4.1.2 - latest 31.10.2022
ST-R8170-R V4.1.2 - latest 31.10.2022
Battery:
BT-DN300 V4.1.0 - latest 06.09.2023
The distance between K2 and derailleurs:
Front derailleur ~ 71cm (middle of FD unit to bottom part of K2)
Rear derailleur ~ 110cm (middle of RD unit to bottom part of K2)
The wireless signal strength seems to be ok. At least I'm not planning to buy any Shimano extra transponder ? until I know that it fixes the connection problem and install or even glue it into the bottom of K2 unit. I could turn wireless shifters inwards some mm but this causes that during riding I have to move my elbows outward.
One option could be to use wiring for shifters. There is one empty connection in battery and then I could use that connection with junction box to do the wiring.
I have tried following changes with K2 and E-Tube but no success. Playing with different channels so 1st I configured channels so that the system uses same channels Ch1 and Ch2 in K2 and Di2. Then I thought that maybe using same channels cause some sort interference. Then I changed channels so that Di2 uses Ch1 & Ch2 and K2 uses Ch3 & Ch4 but no difference.
I'm software engineer but I have no Android programming experience. Anyway I would try some sort of "low hanging fruit" changes into K2 software like playing with process/thread priorities ? The Ki2 software works but there seems to be some sort of integration issue into Di2 system that causes K2 to lose connection.
One possibility is also that Shimano Di2 software has feature that prevents SRAM/Hammerhead devices to connect.

One option would be to add simple timer (< 70s)  to K2 software that initializes the connection into Di2 devices periodically but the problem is what to display during the initialization period in K2 - old data ?

Addition to my configuration. I have the Shimano shifters top button configured as follows:
Left button:
Single-press - shift K2 page left
Double-press - take lap time
Continuous-press - zoom map in
Right button - shift K2 page right
Double-press - switch to map view
Continuous-press - zoom map out
I have been testing the shifter buttons inside without the bike moving, K2 displays that it is in auto-pause state. The shifter buttons seems to work as configured much longer than 1min. The K2 says when taking lap time with left shifter top button during auto-pause that "Only one lap allowed per pause".
I will do test ride tomorrow without auto-pause activated. Maybe it's the root cause that stops K2 Ki2 package working properly.

No auto-pause on today's ride. After the start K2 displayed gear status, battery status etc. normally for 60+ sec then stopped displaying changes. The error message on the K2 screen related to Di2 data was: "Waiting for data". So I don't know if connection was lost/broken or just that no data received.
Some sort of Di2 channel data recorder and analyzer would be useful to find out what happens and for debugging.

@walkingtheworld24 your solution worked for me! Thank you. Frankly I was quite worried about this issue and couldn't find the root cause. The signal quality was within the -30 to -40 range, the device was placed right below the handlebar, just cm away from my Karoo 2, so it had to be another issue. So, it seems like the bluetooth connection isn't kept alive unless I connect my Android phone to the Karoo 2 using the Karoo companion app. By doing this during my ride today I managed to keep the connection between my Karoo 2 and D-fly alive as well. In my view, your Ki2 project isn't the problem but the Karoo 2.

I had connection issues also, but the connecting the mobile worked for me also. Only thing that I don't like the notifications while driving, but perhaps I can reduce them from the mobile.

I would also like to confirm this is a very real and persistent bug with the App. It is not in any way linked to the signal quality. With the signal reported as -30dbm and the bluetooth unit positioned just 5cm from the Karoo, the issue still persists. What does alter the behaviour is the number of bluetooth devices you have active and the order in which they were paired. 0 or 1 Bluetooth device seems to be ok, but 2 is a fail. 3 strangely seems to work again. Pairing after the ride is active and di2 connected seems to have less of an impact than pairing all bluetooth devices before a ride, but this means reconnecting your sensors while trying to ride.
I understand this is free software, but please don't dismiss the reports above as a signal issue or an issue with the di2 unit.
Suggestions I could think of is to:

see if the di2 could be connected via bluetooth instead of Ant+ as the underlying issue might simply be Karoo's implementation of ant+
see if the priority of the di2 device can be raised to the top to make sure it is serviced before it times out.

Hi, I personally never had such disconnect problems, so for me it's tricky to replicate the issue and work on a potential fix.
I would ask anyone with this issue to help me troubleshoot and understanding the cause.
First let's understand your setup:

You mention Bluetooth a lot, Di2 should never be used with Bluetooth, only ANT. You should not connect to Di2 via Bluetooth and you should not connect to Di2 in the Karoo interface itself, only from Ki2.
Please make sure your Di2 setup has the firmware up to date, this includes the Wireless Di2 adapter if you have one 🙂
What other sensor/devices are connected in Karoo? Do you any other ANT sensor and do have your phone or other bluetooth devices paired? Using the SIM?

Now, after understanding that, there are two things you can do:

Collect ANT traces

Enable ANT recording:

Open Ki2
Go to Settings
Scroll down to General Settings
Enable "ANT Recording"
Exit Ki2
Restart Karoo so we get all the ANT logs from the beginning

Connect to a Di2 sensor from Ki2
Wait until the connection drop problem occurs
Extract the logs from Karoo
Enable Developer mode in Karoo (should be enabled already)
Enable MTP mode / File transfer mode in 'Select USB Configuration' in the developer options in Karoo
Connect Karoo to a computer
Use file explorer and open Karoo device
Inside Karoo internal storage, navigate to Android/data/com.valterc.ki2/
Look for a directory named 'ant-recording', it should have some text files inside
Copy those text files, they should have ANT logs from Ki2
Disable Ki2 ANT recording before re-using Karoo
Copy the content of the file to this issue in github

Collect logs from Ki2

Make sure you have Android Platform Tools in your computer (it's the same tool that was used to install Ki2)
Start your Karoo and use it normally, and do the actions that will cause the disconnects
Without shutting down the Karoo, connect it to your computer
In a Terminal/Powershell window, in the directory of the extracted Android Platform Tools, run each of the following commands separately:

.\adb.exe logcat -d -e ki2
.\adb.exe logcat *:W -d

Copy the output of those commands to this issue in github

If the output is too large to paste on github, please use a service like pastebin.

Hi Thank you for your response, keen to try help debug it.
Unfortunately the first part isn't working, I've attached a screenshot showing this folder is empty unfortunately, and yes logging is on in the general settings of Ki2 (and yes I rebooted :) ). That said hopefully the logcat is working. Another "interesting" point. When indoors, and no GPS signal ki2 seemed to stay connected. I had 2 goes at getting data through Logcat. The first attempt was indoors, at around 1300hrs I moved my PC outside so I could get a gps lock. And yes after a few minutes it did lose connection to the di2 again.
To answer your other questions:
Why mention bluetooth - Earlier in the Karoo 2s life it was plagued with connection issues. Most of them manifested when using a mix of bluetooth and Ant+ devices. People could fix this by using either all Ant+ or all Bluetooth. Karoo did some work in the background to provide an update that got the priority right, but for some time that "work around" was the only way to get things going for some. I have a watch which transmits HR and can only do bluetooth, with the ki2 app only using Ant+ there is no option to make all the connections bluetooth.
Update firmware - yep done. I've even plugged in via USB and forced a re-upload to try and fix this issue, but it doesn't appear related.
The other sensors I have are: a Rotor Inspider power meter which also provides cadence data. A Pixel Watch 2 which broadcasts HR over bluetooth. I do use the SIM in the Karoo. I do not carry a phone. The Rotor Inspider holds connection flawlessly on Bluetooth, but on Ant+ also loses connection after prolonged coasting down a hill, so my preference is to use the Inspider on bluetooth. When the Inspider and the Pixel Watch are on Bluetooth the Di2 disconnects after 2 minutes. If only the Pixel Watch 2 is on bluetooth things seem pretty good. Things are also more likely to be stable if I pair the watch after the ride is started - no idea why.
I will also try

carrying my phone
removing the sim
anything else that might help?

logcat.txt
![Screenshot 2024-09-14 123650](https://github.com/user-attachments/assets/1454ba

I already forgot the problems with Ki2 and Shimano Di2. Anyway at some point between March - April the shifter buttons started working so that  I can now switch between different screens and also take lap times. I haven't tried the Ki2 gear view. I have updated Ki2 whenever there is new update available. I also run the latest Shimano Di2 software for derailleurs and battery. I haven't updated the shifters because it requires wired connection and I don't see any need for shifter update now ... following the 1st rule of programming: if it works don't touch it.

One more bit of feedback. I went for a ride with the sim out. 2 minutes in it disconnected. This doesn't appear connect to the sim card in any way.
So I then paired my phone. Di2 stayed paired for the rest of the ride. So as others have said, the issue is definitely linked to the phone connection. The phone connection is bluetooth, hence why somehow, this is all related to bluetooth. I never carry a phone, rely on my pixel watch for calls.

Thanks for the logs, I see some familiar traces similar to the ones from the issue #233.
I will release a new Ki2 version today, it should fix that particular problem, but not 100% sure it will fix all connection issues. Give it a try.
In summary what is happening is that sometimes Karoo is automatically disabling the ANT radio, if some conditions are met, for example when no ANT sensor is registered in Karoo or if Karoo is not able to connect to any ANT sensors for a while.

Awesome, can confirm version 8.0 is a slam dunk so far for me! Have had a busy day with family, so have only been able to complete a 5 and 20 minute ride, but everything was completely flawless. Thank you!

Great! Closing this issue, if you encounter other problems let me know.


bad input data

What happens if someone gives you a file with bad input data, such as a sequence of all Ns? Programs should handle that gracefully.

Which programs do you mean?

All programs need to check for bad fasta files generally. That should be part of the functional testing.


Add a "Create Environment" option from the envrionment selection quick pick

Verification steps:

Install pre-release version of the python extension
run "python: select interpreter" command
You should see "create environment" option:


Use bolt_supported beaker helper

Pull Request (PR) description
Use new bolt_supported helper to conditionally setup and run beaker tests on bolt available platforms.

Requires - https://github.com/voxpupuli/beaker_puppet_helpers/pull/42.

Somewhat guessing what is meant to be put in modulesync config to overide default version of voxpup-acceptance.

I took the liberty of pushing straight to master and https://github.com/voxpupuli/voxpupuli-acceptance/actions/runs/8921727091 completed.


[Bug] Error when generating slices

Describe the bug
joern-slice cannot generate slices

joern seems to be able to parse the code, generating parsed files and cpg files. But cannot generate slices
Desktop (please complete the following information):

OS  Ubuntu 20.04
Joern Version 2.0.187
Java version JDK 19

Looking forward to your reply

I was able to reproduce this issue with the latest joern.
I searched the git log but did not find anything circe related.
@mpollmeier Any idea?

I was able to reproduce this issue with the latest joern. I searched the git log but did not find anything circe related other than #2980 in the last weeks. @mpollmeier Any idea?

Thank you for your reply. I also tried other versions of joern and JDK and the same problem occurred. can you tell me the version of os joern jdk you used when running successfully

I'm still running into this issue on JDK 18. Looking at the build to see if there is something obvious, but this used to work, as I used this via CLI quite a bit when I created it.

Ok it seems to work when I run Joern with Java 17 - could be limits around reflection or something

How tight are we coupled with circe there? Maybe we could replace it?

I've identified the following modules using it:

io.joern.joerncli.JoernVectors
io.joern.dataflowengineoss.slicing
io.joern.gosrc2cpg.model.GoMod
io.joern.gosrc2cpg.parser.GoAstJsonParser

So I'd say we could probably replace it with ujson fairly easily - would also reduce the footprint of our classpath.

Sorry for the silence, I was out sick (still not quite fit, slowly getting there though)
Yes that makes sense. I can do that tomorrow, unless @DavidBakerEffendi are you already on this?

@mpollmeier Haven't started anything on my side, so feel free to go ahead. Welcome back, and hoping for a speedy recovery!

I'm not against removing circe, but the quick fix is https://github.com/joernio/joern/pull/3978

fixed in next release (2.0.197)

and yes, there's now a test in the PR pipeline, so hopefully this won't crop up again


'test_list_topics:  failure during teardown

From: https://travis-ci.org/GoogleCloudPlatform/gcloud-python/builds/154249353#L800-L826
======================================================================
ERROR: test_list_topics (pubsub.TestPubsub)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/GoogleCloudPlatform/gcloud-python/system_tests/pubsub.py", line 61, in tearDown
    doomed.delete()
  File "/home/travis/build/GoogleCloudPlatform/gcloud-python/.tox/system-tests/lib/python2.7/site-packages/gcloud/pubsub/topic.py", line 203, in delete
    api.topic_delete(topic_path=self.full_name)
  File "/home/travis/build/GoogleCloudPlatform/gcloud-python/.tox/system-tests/lib/python2.7/site-packages/gcloud/pubsub/_gax.py", line 130, in topic_delete
    self._gax_api.delete_topic(topic_path)
  File "/home/travis/build/GoogleCloudPlatform/gcloud-python/.tox/system-tests/lib/python2.7/site-packages/google/cloud/pubsub/v1/publisher_api.py", line 403, in delete_topic
    self._delete_topic(request, options)
  File "/home/travis/build/GoogleCloudPlatform/gcloud-python/.tox/system-tests/lib/python2.7/site-packages/google/gax/api_callable.py", line 480, in inner
    return api_caller(api_call, this_settings, request)
  File "/home/travis/build/GoogleCloudPlatform/gcloud-python/.tox/system-tests/lib/python2.7/site-packages/google/gax/api_callable.py", line 468, in base_caller
    return api_call(*args)
  File "/home/travis/build/GoogleCloudPlatform/gcloud-python/.tox/system-tests/lib/python2.7/site-packages/google/gax/api_callable.py", line 433, in inner
    raise_with_traceback(GaxError('RPC failed', cause=exception))
  File "/home/travis/build/GoogleCloudPlatform/gcloud-python/.tox/system-tests/lib/python2.7/site-packages/google/gax/api_callable.py", line 430, in inner
    return a_func(*args, **kwargs)
  File "/home/travis/build/GoogleCloudPlatform/gcloud-python/.tox/system-tests/lib/python2.7/site-packages/google/gax/api_callable.py", line 64, in inner
    return a_func(*updated_args, **kwargs)
  File "/home/travis/build/GoogleCloudPlatform/gcloud-python/.tox/system-tests/lib/python2.7/site-packages/grpc/beta/_client_adaptations.py", line 305, in __call__
    self._request_serializer, self._response_deserializer)
  File "/home/travis/build/GoogleCloudPlatform/gcloud-python/.tox/system-tests/lib/python2.7/site-packages/grpc/beta/_client_adaptations.py", line 203, in _blocking_unary_unary
    raise _abortion_error(rpc_error_call)
GaxError: GaxError(RPC failed, caused by AbortionError(code=StatusCode.INTERNAL, details="Internal error encountered."))
``

I'm going to put on my Pollyanna/Candide hat and claim that #2195 has resolved this issue.


Determine DAG strategy for Data Exports

Determine how to structure one or more DAGs to support Data export flows. For example, one option would have a scheduled DAG that exported MARC records and then have the DAG trigger specific DAGs for OCLC, POD, and ShareVDE.

Done and in development.


build2 package suite: 0.16.0 -> 0.17.0

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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 326951 run on x86_64-linux 1

25 packages built:

bdep
bdep.doc
bdep.man
bpkg
bpkg.doc
bpkg.man
build2
build2.dev
build2.doc
build2.man
libbpkg
libbpkg.dev
libbpkg.doc
libbutl
libbutl.dev
libbutl.doc
libodb
libodb-sqlite
libodb-sqlite.dev
libodb-sqlite.doc
libodb.dev
libodb.doc
libstudxml
libstudxml.dev
libstudxml.doc


BUG: Read_parquet raises AttributeError when given a list of files

Is your feature request related to a problem? Please describe.
In pandas support read_parquet multiple files at once, but modin.pandas makes error that "AttributeError: 'list' object has no attribute 'startswith'".
So I have to use pd.concat, but It is too slower than pd.read_parquet at once.

@JoonHong-Kim thank you for reporting this issue. I can reproduce it at Modin commit d724802391524ad21847722d3d92f8448233f500 with the following:
import pandas
import modin.pandas as pd

df1 = pd.DataFrame([1], columns=['a'])
df2 = pd.DataFrame([2], columns=['a'])
df1.to_parquet('/tmp/a1.parquet')
df2.to_parquet('/tmp/a2.parquet')
print(pandas.read_parquet(['/tmp/a.parquet', '/tmp/b.parquet']))
print(pd.read_parquet(['/tmp/a.parquet', '/tmp/b.parquet']))

I'll see what we can do to fix this.

stack trace
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Input In [8], in <cell line: 1>()
----> 1 print(pd.read_parquet(['/tmp/a.parquet', '/tmp/b.parquet']))

File ~/software_sources/modin/modin/logging/logger_decorator.py:128, in enable_logging.<locals>.decorator.<locals>.run_and_log(*args, **kwargs)
    113 """
    114 Compute function with logging if Modin logging is enabled.
    115
   (...)
    125 Any
    126 """
    127 if LogMode.get() == "disable":
--> 128     return obj(*args, **kwargs)
    130 logger = get_logger()
    131 logger_level = getattr(logger, log_level)

File ~/software_sources/modin/modin/pandas/io.py:313, in read_parquet(path, engine, columns, storage_options, use_nullable_dtypes, **kwargs)
    309 Engine.subscribe(_update_engine)
    310 from modin.core.execution.dispatching.factories.dispatcher import FactoryDispatcher
    312 return DataFrame(
--> 313     query_compiler=FactoryDispatcher.read_parquet(
    314         path=path,
    315         engine=engine,
    316         columns=columns,
    317         storage_options=storage_options,
    318         use_nullable_dtypes=use_nullable_dtypes,
    319         **kwargs,
    320     )
    321 )

File ~/software_sources/modin/modin/core/execution/dispatching/factories/dispatcher.py:180, in FactoryDispatcher.read_parquet(cls, **kwargs)
    177 @classmethod
    178 @_inherit_docstrings(factories.BaseFactory._read_parquet)
    179 def read_parquet(cls, **kwargs):
--> 180     return cls.get_factory()._read_parquet(**kwargs)

File ~/software_sources/modin/modin/core/execution/dispatching/factories/factories.py:207, in BaseFactory._read_parquet(cls, **kwargs)
    199 @classmethod
    200 @doc(
    201     _doc_io_method_template,
   (...)
    205 )
    206 def _read_parquet(cls, **kwargs):
--> 207     return cls.io_cls.read_parquet(**kwargs)

File ~/software_sources/modin/modin/logging/logger_decorator.py:128, in enable_logging.<locals>.decorator.<locals>.run_and_log(*args, **kwargs)
    113 """
    114 Compute function with logging if Modin logging is enabled.
    115
   (...)
    125 Any
    126 """
    127 if LogMode.get() == "disable":
--> 128     return obj(*args, **kwargs)
    130 logger = get_logger()
    131 logger_level = getattr(logger, log_level)

File ~/software_sources/modin/modin/core/io/file_dispatcher.py:154, in FileDispatcher.read(cls, *args, **kwargs)
    131 @classmethod
    132 def read(cls, *args, **kwargs):
    133     """
    134     Read data according passed `args` and `kwargs`.
    135
   (...)
    152     postprocessing work on the resulting query_compiler object.
    153     """
--> 154     query_compiler = cls._read(*args, **kwargs)
    155     # TODO (devin-petersohn): Make this section more general for non-pandas kernel
    156     # implementations.
    157     if StorageFormat.get() == "Pandas":

File ~/software_sources/modin/modin/logging/logger_decorator.py:128, in enable_logging.<locals>.decorator.<locals>.run_and_log(*args, **kwargs)
    113 """
    114 Compute function with logging if Modin logging is enabled.
    115
   (...)
    125 Any
    126 """
    127 if LogMode.get() == "disable":
--> 128     return obj(*args, **kwargs)
    130 logger = get_logger()
    131 logger_level = getattr(logger, log_level)

File ~/software_sources/modin/modin/core/io/column_stores/parquet_dispatcher.py:649, in ParquetDispatcher._read(cls, path, engine, columns, **kwargs)
    640     if len(partitioned_columns):
    641         return cls.single_worker_read(
    642             path,
    643             engine=engine,
   (...)
    646             **kwargs,
    647         )
--> 649 dataset = cls.get_dataset(path, engine, kwargs.get("storage_options") or {})
    650 index_columns = (
    651     dataset.pandas_metadata.get("index_columns", [])
    652     if dataset.pandas_metadata
    653     else []
    654 )
    655 # If we have columns as None, then we default to reading in all the columns

File ~/software_sources/modin/modin/logging/logger_decorator.py:128, in enable_logging.<locals>.decorator.<locals>.run_and_log(*args, **kwargs)
    113 """
    114 Compute function with logging if Modin logging is enabled.
    115
   (...)
    125 Any
    126 """
    127 if LogMode.get() == "disable":
--> 128     return obj(*args, **kwargs)
    130 logger = get_logger()
    131 logger_level = getattr(logger, log_level)

File ~/software_sources/modin/modin/core/io/column_stores/parquet_dispatcher.py:330, in ParquetDispatcher.get_dataset(cls, path, engine, storage_options)
    328 for engine_class in engine_classes:
    329     try:
--> 330         return engine_class(path, storage_options)
    331     except ImportError as err:
    332         error_msgs += "\n - " + str(err)

File ~/software_sources/modin/modin/core/io/column_stores/parquet_dispatcher.py:68, in ColumnStoreDataset.__init__(self, path, storage_options)
     66 self._fs_path = None
     67 self._fs = None
---> 68 self.dataset = self._init_dataset()
     69 self._row_groups_per_file = None
     70 self._files = None

File ~/software_sources/modin/modin/core/io/column_stores/parquet_dispatcher.py:186, in PyArrowDataset._init_dataset(self)
    182 def _init_dataset(self):  # noqa: GL08
    183     from pyarrow.parquet import ParquetDataset
    185     return ParquetDataset(
--> 186         self.fs_path, filesystem=self.fs, use_legacy_dataset=False
    187     )

File ~/software_sources/modin/modin/core/io/column_stores/parquet_dispatcher.py:130, in ColumnStoreDataset.fs_path(self)
    128         self._fs_path = self.path
    129     else:
--> 130         self._fs, self._fs_path = url_to_fs(self.path, **self.storage_options)
    131 return self._fs_path

File ~/opt/anaconda3/envs/modin-dev/lib/python3.10/site-packages/fsspec/core.py:413, in url_to_fs(url, **kwargs)
    411     update_storage_options(options, kwargs)
    412     fs = cls(**options)
--> 413     urlpath = fs._strip_protocol(url)
    414 return fs, urlpath

File ~/opt/anaconda3/envs/modin-dev/lib/python3.10/site-packages/fsspec/implementations/local.py:194, in LocalFileSystem._strip_protocol(cls, path)
    191 @classmethod
    192 def _strip_protocol(cls, path):
    193     path = stringify_path(path)
--> 194     if path.startswith("file://"):
    195         path = path[7:]
    196     return make_path_posix(path).rstrip("/") or cls.root_marker

AttributeError: 'list' object has no attribute 'startswith'

Yup, I can confirm that we currently don't support list objects in the modin Parquet reader. We should try to get this in as soon as we can.
@JoonHong-Kim one work around would be to put the parquet files in a common folder (with nothing else) and then do pd.read_parquet('/tmp/parquet_files'). That should work.

@JoonHong-Kim I spent some time trying to get Modin to read the list of files at once, but I couldn't get it working. I'm sorry, but I don't have time to finish the fix now. Someone can tackle that separately in #5723 and use my branch here to get started. For now, I have #5725 for the workaround you have already, which is to read the files separately and then concat them.

Thx for yours kindness :) I think method of reading the files separetely and then concat being slower than read at once. So I report this issue.


Design and implement publishing data to OSM

Once the user answers the quests, they have to be pushed to OSM. This can be done live or the edits are stored and sent back later

Need to implement a system for storing and syncing this data
Also need to understand how the data is posted to OSM. (There is documentation available)

Outcome:

Classes/ Methods to upload the data to OSM implemented

This is enabled in the application with osmapi module. There is no syncing mechanism yet.


[berkeley] Fix nix CI test issue with directory ownership

There's an issue with the nix test in CI where it fails due to ownership of a directory not belonging to the current user (example here). This PR fixes it by changing recursively the ownership of that directory (/workdir) to the current user.
This PR also makes CI run the test when the test script or any nix-related file is changed.

!ci-build-me

!ci-build-me

!ci-build-me

nice!

!approved-for-mainnet


Privacy Policy Title

Feature request:
Currently in the Privacy Policy Screen, the title Privacy Policy seems to be too bland and empty in few sections while scrolling. If there was an Icon same as implemented in the Navigation Drawer, it would improve the overall Screen in various sections.
Current Privacy Policy Screen:

Privacy Policy in Navigation Drawer:

Maybe fixed on: #228 .

i want to do it


sandbox: create sandbox with network namespace path

follow up #8129

@samuelkarp PTAL

I'm in favor of switching back to the version with the proto update. There was already approval from those API owners to make that change before the final 1.7 release.


Can I override addTimestamps?

Can I override addTimestamps() method? I don't like some of the default settings it using like the timestamp type for both created_at and updated_at and that only the created_at gets the current timestamp.
I'd like to set both  created_at and updated_at as datetime type and default value on both to be NOW(), is that possible some how?

Does someone want to address this, or make a PR?


✨ New Documentation (No large files!) ✨

Checklist

[x] Appropriate branch selected (all PRs must first be merged to dev before they can be merged to master)
[x] Any modified or new methods or classes have helpful JSDoc and code is thoroughly commented
[x] The description lists all applicable issues this PR seeks to resolve
[ ] The description lists any configuration setting(s) that differ from the default settings
[ ] All tests and CI builds passing
[ ] The description lists all relevant PRs included in this release (remove this if not merging to master)
[ ] e2e tests are all passing (remove this if not merging to master)

Description

https://github.com/ibi-group/datatools-ui/pull/598#issue-664003285 but with no large files clogging git history
Images will now be hosted externally
Videos will be hosted on unlisted YouTube videos
No GIFs
Might be merged in 2028 ✨

Part 2 of getting this documentation done!

Was conflicted between this? Amy for mkdocs styling reasons and Binh for datatools knowledge?

@AdrianaCeric You should also revert the non-documentation changes that cause the E2E tests to fail.

@binh-dam-ibigroup I believe these are failing snapshots due to changes in naming?

Do you know how to update snapshots in datatools?

@binh-dam-ibigroup I believe these are failing snapshots due to changes in naming?

Like I said, for this PR, you should revert the non-documentation changes you made.


community: Add OKD Pipelines Operator

Built from branch okd-v1.2.x of https://github.com/jomeier/tektoncd-pipeline-operator.git
@LorbusChris
As promised ;-) Could you review that one, please? The operator image is in my personal quay.io registry.
It would be great to get a review by the devs of the original operator. The differences in the CSV file compared to the original operator from Red Hat are minimal.
During the creation of the CSV file described in the docs/release.md file in https://github.com/jomeier/tektoncd-pipeline-operator.git some unnecessary rolebindings were added to the CSV. I deleted them manually.
In addition I added the missing description, maintainer, icon (we should discuss, if we must create a different icon but I haven't done that yet) to the CSV.
The process of how to automate the CSV and how to take care about updates from older versions in the CSV is not clear to me.
We should clarify/discuss that.
Greetings,
Josef

/ok-to-test

@jomeier Should we wait for @LorbusChris to rewiew?

/lgtm

/hold
/retitle Add OKD pipeline operator

This essentially undoes the changes from https://github.com/operator-framework/community-operators/pull/2056
@nikhil-thomas we'd like to undo the retiring of the pipeline operator from the community catalog, since it's the only catalog available on OKD installs.
If this merges, do you think it's possible for the Pipeline team to update this release alongside releases to the catalog for OCP?

I'd like to wait a little for some more feedback on this. Will lift the hold after.

@jomeier and @ LorbusChris can we move it to Draft? In this case no tests are going to be executed until one presses "Ready for review"?

@jomeier sorry to be such a nitpicker here,
could you rename this PR as well as the commit message to community: Add OKD Pipelines Operator?
I'm not sure switching to draft is necessary here, since code-wise this lgtm. Just want somebody from the operator team to chime in (especially wrt future releases).

I had to force push the new commit message. Some labels were removed automatically because of that.

This essentially undoes the changes from #2056
@nikhil-thomas we'd like to undo the retiring of the pipeline operator from the community catalog, since it's the only catalog available on OKD installs.
If this merges, do you think it's possible for the Pipeline team to update this release alongside releases to the catalog for OCP?

oops, i missed this message.
@LorbusChris thank you for the heads up.
@jomeier I appreciate your effort and i do understand the need for this operator. 👍
The reason why we retired our community releases was because it was confusing our users, as we also have a Red Hat productized operator.
I see that you have listed OKD Pipelines Operator as the display name, and your are using the same logo as OpenShift Pipelienes Operator, in you csv. (
 )
@jomeier could you hold this pr for a day or 2 so that we can discuss this and reach a solution that fits all of us.

@jomeier a few additional pointers,
we have deprecated the repository: https://github.com/openshift/tektoncd-pipeline-operator#tektoncd-operator
current and future development is based on the main branch of https://github.com/tektoncd/operator
The key change that comes with this move is the change in CRDs.
The new operator uses 4 to 5 CRDs (and seprate reconcilers) instead of 1.
tektonconfigs.operator.tekton.dev, tektonpipelines.operator.tekton.dev, tektontriggers.operator.tekton.dev, tektondashboards.operator.tekton.dev, tektonaddons.operator.tekton.dev, instead of the old config.operator.tekton.dev (which is the CRD in OKD Pipelines Operator)
In addition, we also support a workflow/mechanism to support platform specific customizations. That is the code in tektocd/operator can be built for plain K8s, OCP or other platforms with platform specific customizations

/hold
duplicates the (Tekton Operator)[https://operatorhub.io/operator/tektoncd-operator] on OCP/OKD

@jomeier Thanks for the PR. There is currently an OpenShift Pipelines operator available on OpenShift based on the upstream Tekton CD Operator which is part of and is backed by the Tekton community. I find this fork of the downstream operator quite confusing for users.
Are there use-cases that are not covered with the existing upstream and downstream operators enabling Tekton Pipelines on OpenShift and OKD? It might be worth bringing this up in the Tekton WG calls to discuss if the upstream Tekton CD operator needs to improve in some ways to address the use-cases you are looking at.

Thanks all for chiming in here. If the upstream operator is expected to work and provides the same APIs as the OCP operator, then I think it'd be fine to use that.
WRT the OKD prefix - the OKD variant of the Windows-Machine-Config-Operator is prefixed with Community- (see https://github.com/operator-framework/community-operators/tree/master/community-operators/community-windows-machine-config-operator).

@siamaksade @nikhil-thomas @LorbusChris @dmesser @sbose78
Wow guys! That's quite lots of feedback. Thank you all!
I was not aware that the repo that I forked is now deprecated. That explains a lot.
I understood from @LorbusChris that the operatorhub.io catalog is not available in OKD because there are also operators that won't work out of the box in OKD. This repo here is the so called "community catalog" turned on as default in OKD and we like to bring the Tekton operator in here.
What is the right approach to do that to avoid code duplication?
I hope I understood that correctly and can do things in the right way with the next operator.

alternatively, we could probably also just enable the upstream catalog in OKD
cc @vrutkovs

But then we would get operators to OKD that maybe simply don't work because SCCs are missing, ...

@jomeier I proposed to @vrutkovs that we might end up having a catalog containing just the community versions of the OCP add-ons and that catalog would exclusively be present on OKD.

we could probably also just enable the upstream catalog in OKD

Upstream catalog operators are known not to work out-of-the box in OKD.

I proposed to @vrutkovs that we might end up having a catalog containing just the community versions of the OCP add-ons and that catalog would exclusively be present on OKD.

I don't mind, it would be a bit more complex to discover it, but whichever makes it happen on OKD without a pull secret is fine by me.

Nice!
So how do we proceed now? Who takes care about creating a new OKD community catalog ?

So from the tektoncd standpoint, we can provide 2 community operators from tektoncd/operator:

a vanilla kubernetes one (community)
an openshift optimized one (okd community) — this one would be very close to what openshift-pipelines is and should be the one that OKD would install.

We should work upstream to add publishing to the correct payload to operatorhub when we release upstream.
/cc @nikhil-thomas @savitaashture

@jomeier We do have the operator working group each thursday (at two different time, one EU+Asia friendly, one US friendly, on odd week) : see https://github.com/tektoncd/community/blob/main/working-groups.md#operator-and-deployment to join those (I think I need to update the calendar entry to reflect those two timelines).. There is also the #operator slack channel on the tekton slack (see here).

@vdemeester any update?

Closing it due to no activity. Feel free to reopen when needed


[Bug] [zeta][starter]fix bug (#4983)

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

Good job.


setConsent method implementation

Hi @dpa99c ,
we're using your plugin on our cordova / ionic app to implement firebase analytics, but we noticed that is missing the setConsent method implementation. Will you implement this feature in the future?
Thanks in advance for any response.

I've implemented the changes myself https://github.com/pinguluk/cordova-plugin-firebasex/tree/develop, but I couldn't get the iOS to work for some reason yet


[Bug]: CSV recording should including the appropriate number of time digits

Joulescope serial number
N/A
UI version
0.9.11
What OS are you seeing the problem on?
Windows 11
What happened?
When recording statistics data to a CSV file, the time is always shown with one decimal of precision.  However, the UI supports reduction frequencies up to 100 Hz.
What was expected?
The UI should record the CSV file with the appropriate precision for the reduction frequency.
How to reproduce?
Change File → Preferences → Device → setting → reduction_frequency.  Then record CSV files.  The CSV files always shows time with 1 digit of decimal precision.
Extra information
No response

Fixed in 0.10.9


Prevent timing out of kubectl

Fixes #38.

Tested this branch. It produced a more reliable instance build for me. 👍

Thanks for the feedback @c835722!


Use "supports-color" to detect if terminal supports colors

This solution still supports "--colors" and "--no-colors" for overriding the detected ability.
see https://github.com/sindresorhus/supports-color

That's probably a good idea :)

Thanks... :+1:


Use dereference instead of Destroy

Using Destroy() is a gotcha https://trac.osgeo.org/gdal/wiki/PythonGotchas#CertainobjectscontainaDestroymethodbutyoushouldneveruseit
A recommended method is to dereference the object, like feat = None, which is already done for parts of the cookbook before this PR.

Thanks!  Web site will be updated shortly.


Master

Thank you for contributing to openstack/openstack-ansible!
openstack/openstack-ansible uses Gerrit for code review.
Please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


Investigate Shell

Spike to implement turtle concept of Shell in Scala

ammonite shell: http://ammonite.io/#Ammonite-Shell

Types of executions:
- Native commands: in-house implemented commands
- Commands using Process abstraction.
How to connect/pipe those two kinds of executions to provide a way to combine them :thinking:


DID Document / Ledger Object metadata

The resolver should be able to not only return the actual DID Document or Ledger Object, but also metadata.
We need to define what metadata would be useful for a consumer and provide an option to resolve with metadata.
For example, the did:sov universal resolver driver  provides the following metadata:
Map<String, Object> didDocumentMetadata = new LinkedHashMap<> ();
		didDocumentMetadata.put("network", indyConnection.getPoolConfigName());
		didDocumentMetadata.put("poolVersion", indyConnection.getPoolVersion());
		didDocumentMetadata.put("submitterDid", indyConnection.getSubmitterDid());
		didDocumentMetadata.put("nymResponse", gson.fromJson(jsonGetNymResponse, Map.class));
		didDocumentMetadata.put("attrResponse", gson.fromJson(jsonGetAttrResponse, Map.class));

Source
There's also a section in the DID core spec about recommended properties: https://www.w3.org/TR/did-core/#did-document-metadata

This should be addressed in the Indy DID Method Spec first.

We should include metadata from the Indy-VDR RequestResult data


replace JavaModuleWrapper with AcJavaModuleWrapper

Replace JavaModuleWrapper with AcJavaModuleWrapper. This pr aim to enable further optimization of native modules. CoreModuleProvider provides optimization code for official framework, CustomModuleProvider provides optimization code for third-party views and modules. When there
is no optimization,  it will fallback to use methods of parent(JavaModuleWrapper).
The plan is : collect MethodDescriptors during compile time, avoid runtime search. Call method directly, avoid use reflection. Both official and third-party modules should be optimized.
Test Plan
When there is no optimization,  it will fallback to use methods of parent (JavaModuleWrapper).

This pr is one of a series prs derive from old PR 10084, which had proved to accelerate getMethodDescriptors and invoke methods
of native modules by nearly 60x, checkout and run benchmark: BenchMark.
The plan as follows:

Move MethodDescriptor out from JavaModuleWrapper
Add AcJavaModuleWrapper and replace JavaModuleWrapper with AcJavaModuleWrapper
Add ReactNativeModuleProcessor to handle ReactMethod annotations
Add library project to enable ReactNativeModuleProcessor and ReactPropertyProcessor
Update build.gradle file to enable annotations processors during build time
Provide compiler to optimize code write by app developers.

Where can I find the code that generates getModuleHelper? The performance improvements sound really good but it seems like there's some pieces missing here.

Nevermind, found your other PR's. I'll play around with this a bit, but codegen'ing a lot of metadata like this does can be very expensive from an app size perspective. It may still be useful to have it as an opt-in mechanism for specific modules.

This doesn't seem to work with multi-dex apps as it generates Lcom/facebook/react/bridge/JavaModuleWrapper$0 multiple times.
Your current benchmark is also quite synthetic. getMethodDescriptors is not a large part of the total startup cost of React Native, so even if this is an improvement, it may be a small one relative to the entire runtime, or even negative due to increased class-loading cost.

@javache Yes, the benchmark is simply about getMethodDescriptors method, but the optimization is more further, it is more memory friendly, avoid creating hundreds of JavaMethodWrapper. Recently i have not measure the impact on startup of React Native, but i have received feedback like below:


Set log rotation policies

As a project developer, I want log rotation policies applied where applicable, so that performance is unaffected while ensuring log data is properly migrated to Azure Monitor

[ ] Log rotation processes implemented, where necessary

Mentioned in #393


 Actually our Idsrv3 implementation runs fine but if we start now with idsrv3 of course our DB will fill with Idsrv3 data. Will it then be possible to upgrade later without losing any data / Tokens invalid etc? We are using idsrv3 on .net Core 1.1 together with EF Core + Idsrv EF Integration (user data in DB), Client and scope data in memory. Thanks for any hints.

I don't think you are running IS3 with .NET Core - they are not compatible...anyways.
There is no easy data migration path from 3 to 4.
If IS3 works for you - then by any means - use it. Maybe it is worth spending a day or so migrating to 4 to find out how much work it would be. IS4 is definitely the version where we'll spend our time and effort in the future.

closing for now - feel free to re-open if it needs further discussion.

Hi of course one can run it there is the OWIN bridge you guys provided an integration for that. Ok its asp.net Core on full .net framework :) thanks for the information its good to know we will probably Port it then before releasing.


Update cats-effect, cats-effect-kernel, ... to 3.2.0

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-kernel
org.typelevel:cats-effect-laws
org.typelevel:cats-effect-testkit

from 3.1.1 to 3.2.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, semver-minor

Superseded by #21.


Runtime syntax loading

Resolves #262.
I'm less-than-100% sure that https://github.com/remexre/gutenberg/blob/64fa890aa96a2aea351ed3ebe3257ed4b6d5dde5/components/rendering/src/markdown.rs#L104 is an appropriate course of action, but other than that, I've tested this on my own project and it works.

The code itself looks ok but I think I would like a test for it.
Also, can you run the benchmarks of the rendering sub-crate to see if there is any regression?

Okay, I'll add tests tonight.

9675ab190de74c1135d79681dfcefc644463cb93:
test bench_render_content_no_shortcode         ... bench:      58,594 ns/iter (+/- 273)
test bench_render_content_with_highlighting    ... bench:   1,073,077 ns/iter (+/- 5,828)
test bench_render_content_without_highlighting ... bench:     287,527 ns/iter (+/- 1,221)
test bench_render_shortcodes_one_present       ... bench:     217,656 ns/iter (+/- 1,169)

64fa890aa96a2aea351ed3ebe3257ed4b6d5dde5:
test bench_render_content_no_shortcode         ... bench:      61,328 ns/iter (+/- 157)
test bench_render_content_with_highlighting    ... bench:   1,074,319 ns/iter (+/- 7,664)
test bench_render_content_without_highlighting ... bench:     285,738 ns/iter (+/- 944)
test bench_render_shortcodes_one_present       ... bench:     235,043 ns/iter (+/- 788)

Ha, good thing for those tests, I didn't realize we didn't automatically chdir to the site being built.

Does this look good?

Nice, thanks!