Turning Status object to String?

Really need some help been stuck on this for a couple of days. I have my program working but I'm stuck on one thing.
My program successfully grabs a tweet that I'm mentioned in and displays it. The problem is that since the tweet is directed at me it contains my Twitter username. For example, "@mytwittername their message" I get that in my output but I need to remove "@mytwittername" from the tweet. To make my reply to make sense.
I've done everything I could find to convert it to a String but had no luck at all. How can I remove my username from there tweet?
Heres my code:
tweets = api.search(q="@mytwittername",count=100,include_entities=True)
t = ['@mytwittername', '@MyTwitterName']

for s in tweets:
    sn = s.user.screen_name
    m = "@%s message" % (sn)
    s = api.update_status(m, s.id)
    #print(dir(s))

for result in tweets:
    print (result.text)

One of the things I tried, but since I can't make it a String it won't work:
for userName in result.text:
    if userName == "@mytwittername":
        result.text.replace("@mytwittername", "")
        print (userName)
    else:
        print("No username")

Status.text that you're using is a string.

for userName in result.text:
    if userName == "@mytwittername":
        result.text.replace("@mytwittername", "")
        print (userName)
    else:
        print("No username")

This will simply iterate through every character in the text of the Tweet and print "No Username" for each character, since a single character will never == "@mytwittername".
You can simply do something like:
for result in tweets:
    if result.text.startswith("@mytwittername"):
        parsed = result.text[len("@mytwittername"):]

Note, this will still have the space after the mention at the beginning of parsed.
You can also use .replace as you attempted to do if you want to replace it anywhere in the string.
Alternatively, you could use the in_reply_to_screen_name attribute of the Status/Tweet object or the screen_name attribute of the User object from the user attribute of the Status object like you attempted to, in place of "@mytwittername".


Not contain package github.com/pion/example-webrtc-applications/play-from-disk-h264

Your environment.

Version: Release or SHA
Browser: include version
Other Information - stacktraces, related issues, suggestions how to fix, links for us to have context

What did you do?

go get github.com/pion/example-webrtc-applications/play-from-disk-h264

What did you expect?
Download play-from-disk-h264
What happened?
go get github.com/pion/example-webrtc-applications/play-from-disk-h264
go: downloading github.com/pion/example-webrtc-applications v1.0.0
go get: module github.com/pion/example-webrtc-applications@upgrade found (v1.0.0), but does not contain package github.com/pion/example-webrtc-applications/play-from-disk-h264

On the other hand,
why we put play-from-disk in /pion/webrtc/examples, but play-from-disk-h264 in /pion/example-webrtc-applications?

Thanks for catching that @katepangLiu I fixed the instructions!


Update Lago Version

Please update Lago version to the latest.
I tried to do it myself but I got some errors in migrate job.

Any plan to upgrade lago-helm-charts to the latest version?

Its done to 1.8.1


Removed deprecated replace shift functionality

I am going through some of the issues mentioned in this blog post from 2016 and I think it is time that we finally remove the ability to shift from the replace function in arrow. A deprecation warning has been in place since 2016, so I think it is an appropriate time to remove this functionality.

Codecov Report

Merging #624 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #624   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           8      8
  Lines        1512   1487   -25
  Branches      227    226    -1
=====================================
- Hits         1512   1487   -25

Impacted Files
Coverage Δ

arrow/arrow.py
100% <ø> (ø)
:arrow_up:

arrow/parser.py
100% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b9d1171...11215e6. Read the comment docs.

Thank you for continuing to improve Arrow. However, two points:

The documentation has not been updated. https://arrow.readthedocs.io/en/latest/#replace-shift
I had literally no idea this removal was coming because I did not know it was even deprecated to begin with. I think you need to link prominently link to the change / history log from the documentation, and explicitly warn in documentation about breaking the API in an future release well before you break it!

Hey @damonlynch, thanks for the feedback. A warning has been set on the function since 2016 and it was well overdue for removal. We are trying to tackle the biggest complaints about arrow and this was one that was talked about quite a bit, so we thought it was time to finally remove it. I will submit a PR the clean up the docs and to improve the wording in the history file. We currently have the change noted in our change log, but the wording can be clarified.


NUnitTestAdapter.WithFramework 2.0.0

Type: Incomplete
Summary:
NUnitTestAdapter.WithFramework 2.0.0
Details:
Declaring NONE
Resolution:
NuGet metadata and project links are broken.
ClearlyDefined nuspec: license "none"
Affected definitions:

NUnitTestAdapter.WithFramework 2.0.0

Closed; curated version in #5145.


Fix link typo in docs

Thanks for this great library - noticed this typo in link

:tada: This PR is included in version 7.6.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


BindableList events should provide the original list

When you need to run some post-processing on the list after an insertion or removal has occurred, there's currently no way to do this and retain access to the original list without storing an intermediate list, since if you access the bindable list during ItemsRemoved it will contain the post-mutated collection.
As for how to do this, there's a few things we have to consider:

Performance - raw performance + allocations. Do we want to incur the hit of allocating a new list with every event, and every propagation of said event?
The API - we probably want to return a custom class that we can adjust later on, similar to ValueChangedEvent<T>.

Bumping this up in priority, since it'll help with solidifying the implementation of things like RearrangeableListContainer.


Packaging ffmpegServer fails when running debug packaging

This is caused by trying to copy a link. Need to handle softlink erros


[Table Visualizations] Update test

Description
This PR updates tests, so that it no longer needs to test direction, because the direction logic was moved to the OUI components, instead of custom visTable__groupInColumns class that is used currently. Without this, the tests will fail when the PR that removes visTable__groupInColumns will be merged, as this class will no longer exist.
https://github.com/opensearch-project/opensearch-dashboards-functional-test/blob/6823c8202eb8aca8ec1ef1dee41c9e25f65622ab/cypress/integration/core-opensearch-dashboards/opensearch-dashboards/apps/vis_builder/vis_types/table.spec.js#L60
Issues Resolved
Solves https://github.com/opensearch-project/opensearch-dashboards-functional-test/issues/730
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@ananzh I see some actions are failed due to error:
InvalidConfigurationError: Unknown configuration key(s): \"ml_commons_dashboards.enabled\". Check for spelling errors and ensure that expected plugins are installed.

It seems the reason is we passed configureation ml_commons_dashboards.enabled while ml-commons-dashboards plugin is not installed, is this a known issue?

@curq I create a follow-up issue to assign to you https://github.com/opensearch-project/opensearch-dashboards-functional-test/issues/740


Screen.onClose is misleading

It closes the screen by calling client.setScreen(null), so it's not an "listener" for closing screens like the name would suggest.

This is Screen.close in Yarn, but if I recall correctly that caused some naming conflicts for me when trying to add another mod to my dev env, so my only option to get that mod in my dev env was to switch to QM where it wasn't close


Expansion panel should jump to the panel header when next/previous button is clicked

Bug:
Currently if you have a large content inside of an expansion panel which overflows the page size in height, and when you click on the next/previous button, the next/previous panel is opened right in the middle or where you currently are. You don't know which panel is currently opened.
What is the expected behavior?
It should jump to the panel header when next/previous button is clicked.
What is the current behavior?
The next/previous panel is opened from the coordinates of your current view points.
What are the steps to reproduce?

Scroll down
Click on the next button
The next panel is opened
You don't know which panel is exactly opened
You need to scroll up to the panel's header to see it (Destination Panel)

https://stackblitz.com/edit/angular-hrwk2j
What is the use-case or motivation for changing an existing behavior?
Users are confused because they don't know which panel is currently opened.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
5.0.4

@g-sari did you manage to find a way of making this work?


(Flaky-tests) Reduce flakiness of tests

Increased test timeouts and made other changes to tests.
Fixes https://github.com/apache/pulsar/issues/2647
Fixes https://github.com/apache/pulsar/issues/2651
Fixes https://github.com/apache/pulsar/issues/6014
Fixes https://github.com/apache/pulsar/issues/6198
Fixes https://github.com/apache/pulsar/issues/6224
Fixes https://github.com/apache/pulsar/issues/6232
Fixes https://github.com/apache/pulsar/issues/6254
Fixes https://github.com/apache/pulsar/issues/6256
Fixes https://github.com/apache/pulsar/issues/6299
Fixes https://github.com/apache/pulsar/issues/6304
Fixes https://github.com/apache/pulsar/issues/6306
Fixes https://github.com/apache/pulsar/issues/6352
Fixes other flaky tests that still need issues created for them.
Master Issue: #6137
Motivation
Need to resolve these flaky tests.
Modifications

Fixes issues caused by test timeouts being too short. (The majority of changes in this PR are in this category.)
Fixes issues caused by hanging tests resulting from no timeouts.
Fixes Prometheus test issues (since these required more extensive changes to the tests.) There were multiple race conditions and concurrency issues in how we were getting data from Prometheus. (A more robust change would migrate our use of Prometheus to the new approach used in the Go Functions, but I don't think that change is necessary at this time.)
Changes that introduced awaitility library. (Only used in a couple of places to avoid the use of Thread.sleep.)
Fixes involving concurrency issues on topic names. (There were a few in this category.)

Among other things, this PR fixes all issues like this: java.lang.AssertionError: expected [val1-9] but found [val1-6]

@merlimat It looks like there might be some overlap between this PR and the one you were working on (https://github.com/apache/pulsar/pull/5328). It looks like that PR is stale. Would you like me to merge your changes into this one and pick up responsibility on it?

@merlimat Same with this one: #5333

It would be easier to fix more of these in a single PR because otherwise, each of the smaller PRs would need to be re-run many times just to get all of the flaky tests to pass.

Looks like a couple of the commits from this PR (https://github.com/apache/pulsar/pull/6202/commits/e292cbac6d34a38c0c778c615a1285467f6fcad4 and https://github.com/apache/pulsar/pull/6202/commits/79afaeedf7296ec85d53bc15120bdb2b4c95d70b) fixed the Docker disk space availability issue.

@tuteng I see that you beat me to fixing the Github YAML files that were causing the 2 GB build error.

488dfb                                               1c2ba70605594626b2431b6dde9a799b   adfaaeaa780e        17 seconds ago      27.1MB
alpine                                               3.8                                c8bccc0af957        12 days ago         4.41MB
alpine                                               3.9                                82f67be598eb        12 days ago         5.53MB
alpine                                               3.10                               af341ccd2df8        12 days ago         5.56MB
node                                                 10-alpine                          cb69d515e572        2 weeks ago         80.5MB
node                                                 12-alpine                          b0dc3a5e5e9e        2 weeks ago         85.2MB
alpine                                               latest                             e7d92cdc71fe        2 weeks ago         5.59MB
node                                                 10                                 d9b29c7fd8c0        3 weeks ago         908MB
node                                                 12                                 7a73e56f893c        3 weeks ago         913MB
buildpack-deps                                       stretch                            2adbcf3b6aff        5 weeks ago         835MB
debian                                               9                                  f6c68e2ad82a        5 weeks ago         101MB
debian                                               8                                  5d7d9c6338e8        5 weeks ago         129MB
jekyll/builder                                       latest                             4605d94a6b36        3 months ago        564MB
alpine                                               3.7                                6d1ef012b567        11 months ago       4.21MB
mcr.microsoft.com/azure-pipelines/node8-typescript   latest                             9a948d360778        16 months ago       595MB

It seems that this PR of Sijie https://github.com/apache/pulsar/pull/6174/files#diff-a618acbf44f9234d2ba74c8f64ce98f9  has fixed this problem and deleted some unusable images, but I think there should be room for optimization. The image above is the image before packaging, and the image below is the image after packaging. I think that many images can be deleted. If you have time, you can try to delete some. If not, I will try to fix this problem. Thanks @devinbost
apachepulsar/pulsar-test-latest-version              2.6.0-SNAPSHOT                     7f0e65aad492        22 seconds ago      2.8GB
apachepulsar/pulsar-test-latest-version              latest                             7f0e65aad492        22 seconds ago      2.8GB
apachepulsar/pulsar-standalone                       2.6.0-SNAPSHOT                     dd63c9e78a54        53 seconds ago      2.76GB
apachepulsar/pulsar-standalone                       latest                             dd63c9e78a54        53 seconds ago      2.76GB
pulsar-standalone                                    2.6.0-SNAPSHOT                     dd63c9e78a54        53 seconds ago      2.76GB
pulsar-standalone                                    latest                             dd63c9e78a54        53 seconds ago      2.76GB
apachepulsar/pulsar-all                              2.6.0-SNAPSHOT                     29098fc2d364        11 minutes ago      2.74GB
apachepulsar/pulsar-all                              latest                             29098fc2d364        11 minutes ago      2.74GB
pulsar-all                                           2.6.0-SNAPSHOT                     29098fc2d364        11 minutes ago      2.74GB
pulsar-all                                           latest                             29098fc2d364        11 minutes ago      2.74GB
<none>                                               <none>                             6af8ce67f92f        12 minutes ago      1.35GB
apachepulsar/pulsar-grafana                          2.6.0-SNAPSHOT                     20053b07a232        14 minutes ago      286MB
apachepulsar/pulsar-grafana                          latest                             20053b07a232        14 minutes ago      286MB
pulsar-grafana                                       2.6.0-SNAPSHOT                     20053b07a232        14 minutes ago      286MB
pulsar-grafana                                       latest                             20053b07a232        14 minutes ago      286MB
apachepulsar/pulsar                                  2.6.0-SNAPSHOT                     fd65abad4278        14 minutes ago      1.52GB
apachepulsar/pulsar                                  latest                             fd65abad4278        14 minutes ago      1.52GB
pulsar                                               2.6.0-SNAPSHOT                     fd65abad4278        14 minutes ago      1.52GB
pulsar                                               latest                             fd65abad4278        14 minutes ago      1.52GB
<none>                                               <none>                             258ebca6b41e        17 minutes ago      495MB
pulsar-dashboard                                     2.6.0-SNAPSHOT                     b3cbd1b91e92        37 minutes ago      1.25GB
pulsar-dashboard                                     latest                             b3cbd1b91e92        37 minutes ago      1.25GB
apachepulsar/pulsar-dashboard                        2.6.0-SNAPSHOT                     b3cbd1b91e92        37 minutes ago      1.25GB
apachepulsar/pulsar-dashboard                        latest                             b3cbd1b91e92        37 minutes ago      1.25GB
488dfb                                               1c2ba70605594626b2431b6dde9a799b   adfaaeaa780e        47 minutes ago      27.1MB
python                                               3.7-stretch                        b76227722757        3 days ago          941MB
openjdk                                              8-jdk-slim                         4229f5fb33f9        3 days ago          284MB
openjdk                                              8-jdk                              0bfcee65c8ca        3 days ago          488MB
alpine                                               3.8                                c8bccc0af957        12 days ago         4.41MB
alpine                                               3.9                                82f67be598eb        12 days ago         5.53MB
alpine                                               3.10                               af341ccd2df8        12 days ago         5.56MB
node                                                 10-alpine                          cb69d515e572        2 weeks ago         80.5MB
node                                                 12-alpine                          b0dc3a5e5e9e        2 weeks ago         85.2MB
alpine                                               latest                             e7d92cdc71fe        2 weeks ago         5.59MB
node                                                 10                                 d9b29c7fd8c0        3 weeks ago         908MB
node                                                 12                                 7a73e56f893c        3 weeks ago         913MB
buildpack-deps                                       stretch                            2adbcf3b6aff        5 weeks ago         835MB
debian                                               9                                  f6c68e2ad82a        5 weeks ago         101MB
debian                                               8                                  5d7d9c6338e8        5 weeks ago         129MB
busybox                                              latest                             6d5fcfe5ff17        5 weeks ago         1.22MB
jekyll/builder                                       latest                             4605d94a6b36        3 months ago        564MB
alpine                                               3.7                                6d1ef012b567        11 months ago       4.21MB
apachepulsar/pulsar-build                            debian-9                           466f9e1a7d0f        12 months ago       757MB
apachepulsar/pulsar-build                            manylinux-cp37-cp37m               e19877a430f5        12 months ago       1.28GB
apachepulsar/pulsar-build                            manylinux-cp27-cp27mu              898db154a6ea        12 months ago       1.29GB
mcr.microsoft.com/azure-pipelines/node8-typescript   latest                             9a948d360778        16 months ago       595MB
grafana/grafana                                      4.3.1                              2cdb407c0fa4        2 years ago         286MB

Fixes #6258

@tuteng Were you responding to my question in #6268 ?
I'll be happy to clean up more of the images.

@tuteng I probably won't be able to get to the task of cleaning up those docker images until I'm able to get beyond a couple of other flaky tests that have been giving me some trouble.
For example, one of the tests seems to be hanging, but I need to figure out how to identify which test is hanging either by using a remote debugging session or using jstack because it's not clear from the logs.

@tuteng I probably won't be able to get to the task of cleaning up those docker images until I'm able to get beyond a couple of other flaky tests that have been giving me some trouble.
For example, one of the tests seems to be hanging, but I need to figure out how to identify which test is hanging either by using a remote debugging session or using jstack because it's not clear from the logs.

Thank you for your feedback. @devinbost  I'm already following up on this problem. In addition to the lack of storage, there are some other problems. I think I've fixed them. After this test passes https://github.com/AmateurEvents/pulsar/pull/11, I will create a new pr

@devinbost Having a huge PR makes it very difficult to review each change. It would be better to break it down in individual fixes.

@merlimat The problem I'm running into is that with the flaky tests, with smaller PRs, there are so many flaky tests that even after retriggering the build 10 times by editing comments on code files, there are still so many flaky tests that I can't get all the tests to pass at once.
Having multiple PRs just multiplies that problem.
As a consequence, I have two feature PRs for Go functions that are blocked by the flaky tests. They've been blocked for many days even though they are feature-complete.

@merlimat For example, see how many times we needed to re-run the tests to get the tests to pass for this PR: #6031

@merlimat
I can split this PR into smaller ones once I'm satisfied with my progress on it.
However, it's not going to be realistic for me to create a PR for each of the flaky tests I've fixed (perhaps 20+ PRs) because it would be quite a burden for me to need to re-run all of the flaky tests for each one of those PRs and rebase all of the PRs every time new changes were merged to master until someone with sufficient authority decides to merge them.
If it's okay, I can break this PR into major parts to make the review more manageable. Either way, I've touched a large number of tests, so it's going to be time-consuming to review the code changes in any case.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

@sijie @merlimat I need some guidance about how I should split up this PR into smaller PRs since it fixes quite a lot of issues.
I'm choosing to omit a few specific flaky tests from this PR that are deeper issues (and may involve actual code fixes rather than just fixing tests.)
In this PR, all of the changes are fixing tests, not actual code.
I could break it up into:

Fixes of issues caused by test timeouts being too short. (The majority of changes in this PR are in this category.)
Fixes of issues caused by hanging tests resulting from no timeouts.
Fixes of Prometheus test issues (since those were more extensive changes to the tests).
Changes that introduced awaitility library. (Only used in a couple of places to avoid the use of Thread.sleep.)
Fixes involving concurrency issues on topic names. (There were a few in this category.)

Thoughts?

This PR fixes all of the issues like java.lang.AssertionError: expected [val1-9] but found [val1-6]

After this PR, we only need to get the regex test (https://github.com/apache/pulsar/issues/6332), throttling test (https://github.com/apache/pulsar/issues/6301), and state test (https://github.com/apache/pulsar/issues/6200) fixed, and we will have resolved all of the most common flaky tests.

FYI, there's a test that's periodically hanging. Please don't merge until I resolve it. Everything else with this PR is ready for review.

/pulsarbot run-failure-checks

This PR is currently blocked by: https://github.com/apache/pulsar/issues/6389

@sijie Since it might be a while before I'm able to get back to this, we probably should get it reviewed and merged so at least some of the flaky tests are fixed.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

@sijie On second thought, it looks like the remaining test failures are rather stubborn, so this PR might just need to stay on hold until I'm able to resume working on it.

We have lots of CI failure,
this work looks very valuable
is it worth to rebase to current master ?

Closed as stale. There's too many conflict to continue :/

The related works, if still valuable, can be rebased on the master and submitted one by one so that we can merge it quickly.


Workaround to avoid scrolling on iOS devices

This will avoid the scrolling triggered by sliding as described in #68.
Seems to work, however it does not seem to be a clean solution to the
problem.

@markinfurkin where exactly did you put the event.preventDefault();?

jquery.twentytwenty.js file:
slider.on("touchmove", function(event) {
event.preventDefault();
});

Could you please pull this? seems to work just fine with @markinfurkin fix


SIP details

http://way.wunder.io/working-at-wunderkraut/equipment-and-expenses/sip-phone-setup/
SIP details are out of date - server settings for 193.xx.xx.xx shoud be replaced by pop8.orbvoip.com

Updated. See https://github.com/wunderkraut/WunderWay/pull/69


[Bug] Urgent need for network proxy function through port

Unable to connect to api.vrchat.cloud .This almost renders the software unusable.
Due to DNS pollution and blocking of some Cloudflare servers, it is no longer possible to connect to the only two server IPs of this API.

We hope to be able to implement the function of network proxy based on ports to cope with complex network situations in multiple regions.
Version [VRCX 2024.06.12]

Duplicate https://github.com/vrcx-team/VRCX/issues/818#issuecomment-2174002250


Command line: Extract Schematron parameters from XSpec file

This pull request derives from #409. So needs to be handled after that.

CLI (xspec.bat and xspec.sh) already extracts Schematron parameters. But they are extracted as strings in a primitive way.
This pull request fixes it by extracting the parameters in the same way as XSpec for XSLT.
As a result,

Problems mentioned in schematron-param-001.xspec are fixed.
Schematron parameters are now tested. (test/schematron-param-001.xspec used to do no tests.)

Although this pull request contains a lot of commits for historical reasons, all that needs to be reviewed in the end is a single commit (1aeb2432c1d1f9b4e6f93ad9db2c0a36fbe2aa47).

@cirulls
Merged this bug fix.


Upgrade to repo-config v0.5.2

All the changes are related to regenerating the files using the cookiecutter templates in repo-config v0.5.2.

Remove extensions from replay file
Add empty Introduction variable
Bump repo-config version to v0.5.2.
Add common pylint options
Add common source paths for isort
Add editorconfig file
Use repo-config for linting examples in docstrings
ci: Checkout submodules
Add a workflow to make sure release notes are updated
Don't ship development files in the source distribution
Add and sort mkdocs markdown extensions
mkdocs: Add comment with more info about cross-linking
Bump setuptools version

Rebased and fixed the wrong removal of the benchmarks exclusion.

It would be good to merge this soon (before merging other dependabot stuff) as I got a few conflicts when rebasing.


Tiered Storage: add JClouds HttpClient driver

Motivation
Apache JClouds supports Apache HttpClient as library to perform HTTP class, that is better of the standard JDK HttpUrlConnection based provider.
See https://github.com/jclouds/jclouds/tree/master/drivers/apachehc
Modifications
Modifications:

add ApacheHCHttpCommandExecutorServiceModule module
add jclouds driver based on Apache HTTP Client
add a new ShadedJCloudsUtils that is needed to workaround some problems with the shading of Guice (AbstractModule class is problematic)
add system property pulsar.jclouds.use_apache_hc to disable the new driver in case of problems

Verifying this change
I have tested this manually.
Does this pull request potentially affect one of the following parts:
Tiered Storage

@eolivelli please share the stack trace of the blocked thread which is the original motivation to switch to use Apace HttpComponents/HttpClient for JClouds.

/pulsarbot run-failure-checks


Nuxt Hook (page:start/ page:finish) not working with layouts

Environment

Operating System: Darwin
Node Version:     v18.14.2
Nuxt Version:     3.4.3
Nitro Version:    2.3.3
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      app, build, runtimeConfig, modules, css, plugins, postcss, vite, auth
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-exuhyz
Describe the bug
Apparently the nuxt hook page:finish / page:start are not working when using layouts in NUXT.
Everything is working like expected when you don't have a layouts folder. My console.logs are showing after adding a layouts folder its not working anymore.
Additional context
No response
Logs
No response

Anyone knows a solutions or workaround?

Anyone knows a solutions or workaround?

@glennovische
You are using RouterView inside layouts/default.vue, which should be <slot /> instead.
Check the docs: https://nuxt.com/docs/guide/directory-structure/layouts


WIP: Mobile Wrapper

This is a WIP to create a mobile binding.

Coverage decreased (-0.3%) to 80.999% when pulling 4f298139ea28223e9565cfd38c6ab8d3206aac50 on gomobile into 5eec00e0bc0d88657e78c8c74ef658efe1d422a0 on master.


Migrated PR missing Comments and Files changed, not able to restore branch

Description
The comments and files on a migrated PR by two mannequin users and branch restore was not able to be preformed.

Commits and File changes for infinity symbol

Source system show one commit and seven file changes.
If you restore the branch prior to the migration the content comes over fine, but restoring every branch to every PR is not workable.

Reproduction Steps

support ticket #2125076


Refactor item-counter

The item-counter component is a low-level component used in several places in the UI. It's used do increase or decrease the quantity of a cart item, during or after the add-to-cart action. While it's a super simple component, the implementation is quite complicated. As part of a wider cart refactor, we like to refactor this code.
Refactoring:

simplify DOM (it's just 2 buttons and an input)
simplify component logic
rely on formControl for quantity state (i.e. disabled) and quantity savedValues
use the number input type to benefit form numeric support
drop bootstrap for the UI

Additionally, there are a few functional changes we propose:

allow for submitting the quantity form by using the enter key
move the buttons outside the keyboard control for a11y – if the mouse cannot be used, the focus on the input is enough to control the quantity with numeric keyboard, arrow keys, or plus and minus keys

Stretch:

In some business fractional units are used for quantity, while this is rare, it would be great if we can support this.
We might want to introduce validation messages
we might want to take the existing cart count into account; currently only the stock value is used for the max number, this is however invalid in case the item is already added to the cart.

This is a follow up on #830

fixed with #4863

QA steps please.

Let's keep QA on hold until we finished #7056


chore: release 4.7.2

:robot: I have created a release *beep* *boop*
4.7.2 (2021-07-13)
Performance Improvements

improve the running speed of the check command (29cb82c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/mili-project-manager/mili/releases/tag/v4.7.2 :sunflower:


Using token metadata client sdk

This PR switches the Token Metadata crate to use the Rust client SDK instead of the program crate.

Added an entry on the CHANGELOG. I have not tested the changes on the anchor types, as I was relying on the existing ones.


Dictionary keys can be forzenset

>>> l = ["Geeks", "for", "Geeks"]
>>> s=frozenset(l)
>>> s
frozenset({'for', 'Geeks'})
>>> dict={1:'a',2:{s:'frozenset'}}
>>> from trace_dkey import trace
>>> trace(dict,p)
[]

this should return [2,s]
but this is very tricky as frozenset are ast.Call object [<ast.Call object at 0x7fafe8919d90>]

I think you have used the undeclared  variable p in the last statement
>>> trace(dict,p)


Failed to read Video ID from data

Hello, I've used this few months ago worked fine back then but now after downloading course preview it gives error "Failed to read Video ID from data"
Any solution?

I got this error when the cookie expires

cookies are new though didn't expire


Enable RTD builds PR support

RTD people have an experimental feature of providing builds for PRs.  See e.g. https://github.com/con/open-brain-consent/pull/50 where it was already enabled and tested.
I do not have admin privileges for RTD for this project, so the most I could do is to pester RTD people to enable the feature for this repository, which I was told they have done!  So it is now for people with the super powers to actually make it work.  Should be quite straightforward, see https://docs.readthedocs.io/en/latest/guides/autobuild-docs-for-pull-requests.html for the documentation and common gotchas. In my case it was the need "to disconnect and reconnect to GitHub service" as now described in that document.

Enabled and added @yarikoptic as maintainer.

Possibly it only works with Sphinx?

I think that it just needs adjusting permissions for RTD integration on github side.
I have done already a cycle on RTD by removing the linkage to github and trying to add it again:
Could not add webhook for BIDS Specification. Make sure you have the correct GitHub permissions.
The project BIDS Specification doesn't have a valid webhook set up, commits won't trigger new builds for this project. See the project integrations for more information.
and indeed I have no super powers in this organization/repository.  @effigies please go to RTD, remove the hook and try to add it again in https://readthedocs.org/dashboard/bids-specification/integrations/123217/ (if you have super powers here on github for bids-standard organization)

you can push or force push more to #485 to see if RTD emerges in the status.

There's definitely something wrong with the authentication. I have full permissions, but it wouldn't add the webhook. I added it manually, and it builds, but it won't push to the "checks" section.

Ah, had to go to https://github.com/settings/applications, find the app, click, and grant access to bids-standard. Then the webhook could be resynced.

so it works, issue resolved, thanks @effigies !

While we're on the topic, do we want to drop the CircleCI doc build?

wow, cool that this is possible now :-)
I'd say let's test it out for a bit and then remove CircleCI if we don't find any fault with the new RTD feature

So far I am happy with it. From my side, we can switch the docs artifact from circleci off.
Then we can also use https://github.com/bids-standard/bids-specification/blob/master/.circleci/artifact_path to point to the PDF build of the docs.
the artifact_path should also become a GitHub action like we already have on the bids-website, because I think the way we currently have it is outdated and may not be supported in the future anymore.


Request: request for kodi plugins iptv client

the rg353 series surport kodi media player.
but the arkos didn't complie iptv client include. and the kodi official dosent support install on rg353v by yourself due to dependence error.
hopefully the arkos will support  iptv client inbox like the official system .
i have use rg353v as my handle media center. use it play game, listen to  music and web radio.
the plugins addr: https://github.com/kodi-pvr/pvr.iptvsimple

Odd, not sure why that pvr plugin wasn't built and added.  I should have a solution available to test and confirm functionality shortly.

Hi,
I just built this plugin and Kodi seems to have loaded it fine. If you can help test this and provide feedback on if it functions as expected or not, I'd appreciate it.

Take the attached compressed file (arkosbackup.tar.gz) and put it in your roms/backup folder. Do not uncompress the contents! Just place the file as is in your roms/backup folder. If you don't have a backup folder in the roms folder, just create it.  If you're using a 2 SD card setup on your device, this must be done from SD1(TF1 Slot).

Then go into the Emulationstation Menu, scroll to Options, hit A, then go to Advanced, hit A, then scroll all the way down to Restore Settings, hit A.

Once completed, launch Kodi, configure the iptv client and verify functionality.

Let me know how it works out for you.
arkosbackup.tar.gz

yeah,i've tested and it it works !!
my device is rg353vs v2. the latest arkos version:ArkOS_RG353V_v2.0_01152023
thx for your great work.

Awesome.  Thanks for confirming.  I'll include it with the next update as well for others.


BAPP-524: Add location to basename profile / TextRecords

Form: Default

Form: Filled

On the profile

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


JVM core dump on launch on Plasma desktop

it crash on launch, there are problem with the system tray:
GRAVE: [15] impl.osdependent.SystemTray.getDefaultSystemTray().57 Failed to initialize java.awt.SystemTray
java.lang.UnsupportedOperationException: java.lang.reflect.InvocationTargetException
at net.java.sip.communicator.impl.osdependent.SystemTray$AWTSystemTrayPeer.(SystemTray.java:158)
at net.java.sip.communicator.impl.osdependent.SystemTray.getDefaultSystemTray(SystemTray.java:52)
at net.java.sip.communicator.impl.osdependent.jdic.SystrayServiceJdicImpl.(SystrayServiceJdicImpl.java:126)
at net.java.sip.communicator.impl.osdependent.OsDependentActivator.start(OsDependentActivator.java:156)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:2152)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2070)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1297)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at net.java.sip.communicator.impl.osdependent.SystemTray$AWTSystemTrayPeer.(SystemTray.java:150)
... 9 more
Caused by: java.lang.UnsupportedOperationException: The system tray is not supported on the current platform.
at java.awt.SystemTray.getSystemTray(SystemTray.java:186)
... 14 more
17:01:35.659 GRAVE: [15] impl.osdependent.SystemTray.getDefaultSystemTray().64 Failed to initialize the desktop.tray implementation.
17:01:35.659 GRAVE: [15] impl.osdependent.jdic.SystrayServiceJdicImpl.().136 Failed to create a systray!
java.lang.UnsupportedOperationException: Failed to initialize the desktop.tray implementation.
at net.java.sip.communicator.impl.osdependent.SystemTray.getDefaultSystemTray(SystemTray.java:66)
at net.java.sip.communicator.impl.osdependent.jdic.SystrayServiceJdicImpl.(SystrayServiceJdicImpl.java:126)
at net.java.sip.communicator.impl.osdependent.OsDependentActivator.start(OsDependentActivator.java:156)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:2152)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2070)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1297)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
at java.lang.Thread.run(Thread.java:745)
(java:6701): GLib-GObject-WARNING **: cannot register existing type 'GdkWindow'
(java:6701): GLib-GObject-CRITICAL **: g_object_new: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
(java:6701): GLib-GObject-WARNING **: cannot register existing type 'GdkWindow'
(java:6701): Gdk-CRITICAL **: IA__gdk_window_is_viewable: assertion 'GDK_IS_WINDOW (window)' failed

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x00007f83e4158ecc, pid=6701, tid=140204486719232

JRE version: OpenJDK Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14)
Java VM: OpenJDK 64-Bit Server VM (25.45-b02 mixed mode linux-amd64 compressed oops)
Problematic frame:
C  [libgdk-x11-2.0.so.0+0x6becc]
(java:6701): GLib-GObject-WARNING **: cannot register existing type 'GdkWindow'
(java:6701): Gdk-CRITICAL **: IA__gdk_window_add_filter: assertion 'window == NULL || GDK_IS_WINDOW (window)' failed

Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

An error report file with more information is saved as:
/tmp/hs_err_pid6701.log
(java:6701): GLib-GObject-WARNING **: cannot register existing type 'GdkWindow'
(java:6701): Gdk-CRITICAL **: IA__gdk_window_new: assertion 'GDK_IS_WINDOW (parent)' failed
(java:6701): GLib-GObject-WARNING **: cannot register existing type 'GdkWindow'
(java:6701): Gdk-CRITICAL **: _gdk_x11_window_get_toplevel: assertion 'GDK_IS_WINDOW (window)' failed
[thread<PHONE_NUMBER>64224 also had an error]

If you would like to submit a bug report, please visit:
http://bugreport.java.com/bugreport/crash.jsp
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.

[1]    6701 abort (core dumped)  jitsi

dump even with wmsystemtray, one time did not crash (it seems frozen) and i have the following output:
ALSA lib pcm_dsnoop.c:614:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1024:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2267:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_dsnoop.c:614:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1024:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:963:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1024:(snd_pcm_dmix_open) unable to open slave
*** Error in `/bin/java': double free or corruption (!prev): 0x00007f1fac548000 ***

Same here:
$ jitsi -v
Jitsi 2.9.5456

$ jitsi
...
2015-06-12 17:50:39.787 SEVERE: [15] impl.osdependent.SystemTray.getDefaultSystemTray().57 Failed to initialize java.awt.SystemTray
java.lang.UnsupportedOperationException: java.lang.reflect.InvocationTargetException
        at net.java.sip.communicator.impl.osdependent.SystemTray$AWTSystemTrayPeer.<init>(SystemTray.java:158)
        at net.java.sip.communicator.impl.osdependent.SystemTray.getDefaultSystemTray(SystemTray.java:52)
        at net.java.sip.communicator.impl.osdependent.jdic.SystrayServiceJdicImpl.<init>(SystrayServiceJdicImpl.java:126)
        at net.java.sip.communicator.impl.osdependent.OsDependentActivator.start(OsDependentActivator.java:156)
        at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
        at org.apache.felix.framework.Felix.activateBundle(Felix.java:2152)
        at org.apache.felix.framework.Felix.startBundle(Felix.java:2070)
        at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1297)
        at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:497)
        at net.java.sip.communicator.impl.osdependent.SystemTray$AWTSystemTrayPeer.<init>(SystemTray.java:150)
        ... 9 more
Caused by: java.lang.UnsupportedOperationException: The system tray is not supported on the current platform.
        at java.awt.SystemTray.getSystemTray(SystemTray.java:186)
        ... 14 more
2015-06-12 17:50:39.788 SEVERE: [15] impl.osdependent.SystemTray.getDefaultSystemTray().64 Failed to initialize the desktop.tray implementation.
2015-06-12 17:50:39.788 SEVERE: [15] impl.osdependent.jdic.SystrayServiceJdicImpl.<init>().136 Failed to create a systray!
java.lang.UnsupportedOperationException: Failed to initialize the desktop.tray implementation.
        at net.java.sip.communicator.impl.osdependent.SystemTray.getDefaultSystemTray(SystemTray.java:66)
        at net.java.sip.communicator.impl.osdependent.jdic.SystrayServiceJdicImpl.<init>(SystrayServiceJdicImpl.java:126)
        at net.java.sip.communicator.impl.osdependent.OsDependentActivator.start(OsDependentActivator.java:156)
        at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
        at org.apache.felix.framework.Felix.activateBundle(Felix.java:2152)
        at org.apache.felix.framework.Felix.startBundle(Felix.java:2070)
        at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1297)
        at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
        at java.lang.Thread.run(Thread.java:745)
[xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:179: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed.
Aborted (core dumped)

Sometimes starting jisti works. Still getting the same exceptions, but the application then works:
2015-06-12 18:00:14.555 SEVERE: [15] impl.osdependent.SystemTray.getDefaultSystemTray().64 Failed to initialize the desktop.tray implementation.
2015-06-12 18:00:14.556 SEVERE: [15] impl.osdependent.jdic.SystrayServiceJdicImpl.<init>().136 Failed to create a systray!
java.lang.UnsupportedOperationException: Failed to initialize the desktop.tray implementation.
        at net.java.sip.communicator.impl.osdependent.SystemTray.getDefaultSystemTray(SystemTray.java:66)
        at net.java.sip.communicator.impl.osdependent.jdic.SystrayServiceJdicImpl.<init>(SystrayServiceJdicImpl.java:126)
        at net.java.sip.communicator.impl.osdependent.OsDependentActivator.start(OsDependentActivator.java:156)
        at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
        at org.apache.felix.framework.Felix.activateBundle(Felix.java:2152)
        at org.apache.felix.framework.Felix.startBundle(Felix.java:2070)
        at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1297)
        at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
        at java.lang.Thread.run(Thread.java:745)
2015-06-12 18:00:16.062 SEVERE: [41] impl.osdependent.jdic.SystrayServiceJdicImpl.checkInitialized().464 Systray not init

Some questions:

What is Plasma?
Could you please create a Gist with the content of the /tmp/hs_err_pid*.log and link them here?

The java stack traces mentioned above would not cause a crash. It's an indication that the tray icon could not be initialized. This is most likely due to an unsupported desktop. In that case, please open a bug with your distribution/desktop environment provider that Java 8 doesn't support tray icons.

Plasma is KDE.

Jitsi debug output: https://gist.github.com/digitician/754e678d86a2790b9fa4
JVM error log: https://gist.github.com/digitician/bae1d5da3b0de64bfdbf

Hm. The discussion #66 is related to this. Can you please try to unset KDE_FULL_SESSION and see if Jitsi is able to start?

Difficult to test. It does not always crash, so while I don't see a crash with KDE_FULL_SESSION unset at the moment, I don't know if it solved the issue. Will try to remember to unset this before starting Jitsi and let you know if it still crashes at some point.

Any update? Otherwise I'm going to close this.

For me it work unsetting KDE_FULL_SESSION.
System tray still fail to load, but jitsi seems to work fine.

The system tray is a whole different story and primarily a problem of Java.
I'm not sure how to proceed with this. If you have any suggestions, please post them in PR#66.

Its not related to #66
KDE 5 dont support the old xembed based system tray anymore.
Thats the reason, why jitsi crashes.
https://bugs.launchpad.net/ubuntu/+source/tasque/+bug/1448512

Fine, whatever. We can still conclude that unsetting KDE_FULL_SESSION (which we are currently using as the indication to load the GTKLookAndFeel) makes Jitsi launchable. And we can also conclude that it's not really a Jitsi problem when a desktop environment decides to drop a method to show system trays that a lot of applications and frameworks depend on.
I was referring this to #66 because I'm looking for a more general approach in deciding which look and feel to load on Linux.


Add new devices

Codecov Report

Merging #136 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #136      +/-   ##
============================================
+ Coverage     99.13%   99.14%   +<.01%
- Complexity     2532     2557      +25
============================================
  Files           487      492       +5
  Lines          4766     4807      +41
============================================
+ Hits           4725     4766      +41
  Misses           41       41

Flag
Coverage Δ
Complexity Δ

#phpunit
99.14% <100%> (ø)
2557 <20> (+25)
:arrow_up:

Impacted Files
Coverage Δ
Complexity Δ

src/Factory/Device/Mobile/JollaFactory.php
100% <ø> (ø)
4 <0> (ø)
:arrow_down:

src/Factory/Device/Mobile/AcmeFactory.php
100% <ø> (ø)
4 <0> (ø)
:arrow_down:

src/Factory/Device/Mobile/LanixFactory.php
100% <ø> (ø)
4 <0> (ø)
:arrow_down:

src/Factory/Device/Mobile/DigmaFactory.php
100% <ø> (ø)
4 <0> (ø)
:arrow_down:

src/Factory/Device/Mobile/CreativeFactory.php
100% <ø> (ø)
4 <0> (ø)
:arrow_down:

src/Factory/Device/Mobile/LenovoFactory.php
100% <ø> (ø)
4 <0> (ø)
:arrow_down:

src/Factory/Device/Mobile/GeneralMobileFactory.php
100% <ø> (ø)
4 <0> (ø)
:arrow_down:

src/Detector.php
80.76% <ø> (ø)
11 <0> (ø)
:arrow_down:

src/Factory/Device/Mobile/ErgoFactory.php
100% <ø> (ø)
4 <0> (ø)
:arrow_down:

src/Factory/Device/Mobile/LifewareFactory.php
100% <ø> (ø)
4 <0> (ø)
:arrow_down:

... and 273 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 904f658...54cf1dc. Read the comment docs.

Pull Request Test Coverage Report for Build 1151

39 of 39 (100.0%) changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 99.09%

Totals

Change from base Build 1142:
0.008%

Covered Lines:
4247

Relevant Lines:
4286

💛  - Coveralls


add new StorageDriver: rawblock

The driver creates raw-file-block for every images/valume.
It likes vfs driver in the operation creating an image from
the parent. Both drivers do the operation by copying, but
rawblock driver tries to copy the parent by reflink.
So the copy-on-write is supported for the rawblock driver
if the backing(host) filesystem supports copy-on-write.

If the backing filesystem is btrfs, rawblock driver
supports copy-on-write now. If the backing filesystem
is xfs, the rawblock driver will test whether it is
reflink-enabled, if true, rawblock driver supports
copy-on-write.

rawblock driver vs vfs driver:
  hypervisor handles block better than dir(9p, sharefs).
  rawblock driver supports copy-on-write

rawblock driver vs devicemapper:
  loopback-based devicemapper is too ugly.
  rawblock driver (will) use loopback only when manipulate
    the filesystem in host.

The rawblock driver is also the base feature prepared for
dax support and pages-shared across VMs.

Signed-off-by: Lai Jiangshan<EMAIL_ADDRESS>

# hyperctl info
Images: 4
Containers: 0
PODs: 1
Storage Driver: rawblock
  Backing Filesystem: xfs
  Support Copy-On-Write: false
  Block Filesystem: xfs
  Block Size: 10GB
...

lgtm!

travis build failed, looks like download lvm source failed.

@laijs  we need change the lvm download link to: ftp://sources.redhat.com/pub/lvm2/LVM<IP_ADDRESS>.tgz
or newer version:
ftp://sources.redhat.com/pub/lvm2/LVM<IP_ADDRESS>.tgz
The fedora site has retired.


trailing spaces not allowed in code block

I'm encountering this error. I saw issue #190 and that a change was made for that, so I wasn't expecting to get this error—not sure if my case is the same or different.
Inside my .md file, I have a Python code fragment within a code block:
    if kind == "rect":
        l, w = spec  # assign tuple elements
        draw_rect(l, w)

    elif kind == "circle":
        draw_circle(spec)

The "blank" line is included for clarity and has four spaces, which are needed to preserve the integrity of the if...else construct as a unit. I don't need the spaces for the page to look right, but if someone copy/pasted the fragment, they'd end up with a syntax error. So, I've kept four spaces in the line. But that's giving me an error.
Is this a different issue than #190? Am I missing something?
Thanks!

Yes, it looks like the same issue. When I try your example, it does not report an issue: https://dlaa.me/markdownlint/#%25m%23 Issue 292

    if kind %3D%3D "rect"%3A
        l%2C w %3D spec  %23 assign tuple elements
        draw_rect(l%2C w)

    elif kind %3D%3D "circle"%3A
        draw_circle(spec)

Could you please double check what version of markdownlint you're using or show how to reproduce the issue (either linking to a file or in the playground above)?
Thanks!

I have v 0.35.2. When I use @outdated, in the marketplace search, it tells me I don't have any out-of-date extensions
When I copy/paste from my md file into the playground (replacing what was there), I get three occurrences of the error. Same if I load the entire .md file. I'm not sure how to give you a link to the playground with my file, but you can get it here:
https://github.com/PeterConstable/PythonTutorial/blob/master/9_Sample_Program.md

Your example used indented code blocks, but the file you link to uses code fences. The original change allowed blank lines in indented code so that it wouldn’t be broken up undesirably. That’s not an issue with code fences, so blank lines continue to be reported as a violation there.
Are you sure that Python requires a blank line with exactly four spaces in order to maintain proper syntax? If so, then it would seem that the earlier allowance may need to be made for code fences as well.

Indentation in Python is syntactic. If you leave out indentation spaces, you've changed the construct and can end up with syntax errors.
You can use any amount of indentation. However:
"Use 4 spaces per indentation level."
https://www.python.org/dev/peps/pep-0008/#indentation

I was vaguely aware that Python treats indentation as a structural requirement, but I am surprised that it would require indentation for blank lines.
This section in the document you linked to seems not to mention that for blank lines: https://www.python.org/dev/peps/pep-0008/#blank-lines
And this section explicitly calls out that trailing whitespace is to be avoided everywhere: https://www.python.org/dev/peps/pep-0008/#other-recommendations
Is your example exceptional for some reason? Is that discussed anywhere?

You don't think that syntactic requirement would supersede an "avoid" recommendation?
Looking at the spec, it's not 100% clear to me what exact syntactic requirements would be. On the one hand, this is relevant:
"In the standard interactive interpreter, an entirely blank logical line (i.e. one containing not even whitespace or a comment) terminates a multi-line statement."
https://docs.python.org/3.8/reference/lexical_analysis.html#blank-lines
The part that's not clear to me is what is considered a multi-line statement. In my case there are 3 errors that involve two specs: functdef and if_stmt. Let's consider the latter:
if_stmt ::=  "if" assignment_expression ":" suite
             ("elif" assignment_expression ":" suite)*
             ["else" ":" suite]

https://docs.python.org/3.8/reference/compound_stmts.html#grammar-token-if-stmt
The blank line is occurring within suite.
suite         ::=  stmt_list NEWLINE | NEWLINE INDENT statement+ DEDENT
statement     ::=  stmt_list NEWLINE | compound_stmt
stmt_list     ::=  simple_stmt (";" simple_stmt)* [";"]

My understanding is that if_stmt — its full parse — would be considered a multi-line statement. So, without the spaces in the blank line, then the standard interactive interpreter would terminate the statement at that line. And that's exactly what I'm encountering, and the problem I'm trying to avoid.
(In a .py file executed as a script, an entirely blank line doesn't cause this problem.)

Thanks, I’ll look at opting fenced code blocks into the exception.

Thanks. Blank line in interactive mode being handled differently than in a script is somewhat motivated: when editing multi-line statements, the console needs some way to detect when end of statement is intended. They could have required entry of a truly empty line (no spaces), but that would have impacted usability in interactive mode. At any rate, for better or worse, it's long-standing practice now.

Also would like to see this implemented. In my use case, I am generating markdown documentation for databases and so can't guarantee (as is the case with my demo code) that the code within a database follows markdown best practices.
Giving a pass to the code blocks allows me to more tightly control my markdown, while not erroring out for the fenced code blocks that originate elsewhere.


Several Major Issues: Challenges Not Passing, Dependencies Out of Date, More...

Describe your problem and how to reproduce it:
Quality Assurance and Testing with Chai - Run Functional Tests using a Headless Browser:
Link: https://www.freecodecamp.org/learn/information-security-and-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-using-a-headless-browser
Issue 1: Tests not passing (Major)
The Headless Browser challenges are not passing. I tried replacing my code with the Solution on the Hint page, and it's not working. For some reason, however, "You should assert that the headless browser request succeeded." is passing.  All 29 tests are passing.
Relevant Information
My logs when I run the test: https://gist.github.com/krisb1220/a76a7db2ae66adf3f60ba5caa9bcb097#file-log-txt
My 2_functional_tests.js file: https://gist.github.com/krisb1220/a76a7db2ae66adf3f60ba5caa9bcb097#file-2_functional_tests-js
My project: https://glitch.com/edit/#!/krisb-fcc-information-quality
Issue 2: Outdated Packages (Minor)
Packages are out of date
Quality Assurance and Testing with Chai - Run Functional Tests using a Headless Browser II:
Link:
https://www.freecodecamp.org/learn/information-security-and-quality-assurance/quality-assurance-and-testing-with-chai/run-functional-tests-using-a-headless-browser-ii
Issue 1: Tests not passing (Major)
Same as above; except no tests are passing, even though all tests are passing.
Relevant information:
SEE ABOVE -- SAME AS ABOVE.
Exercise Tracker Project
Issue 1: Outdated Mongoose/Mongo (Major)
Mongoose is outdated. It doesn't allow you to connect using the normal connection method as taught in the cirriculum. The package.json needs to be changed to the following:
https://github.com/krisb1220/boilerplate-project-exercisetracker/blob/glitch/package.json
I've added a PR to the boilerplate repo that changes the Package.json and fixes this issue.
https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/pull/24
Issue 2: Outdated Node Version (Major)
The Node version is heavily outdated. It's running Node 6. async and await keywords are not able to be used - along with all other ES6 features. I've created a Package.json that fixes the issue. I've also gone ahead and created an entirely new Glitch template that fixes the issue.
Issue 3: Unclear Instructions 1 (Minor)
Although this isn't a huge issue, it's a requirement that the "duration" variable from response after posting to /api/exercise/add is required to be an integer.
Issue 4: Unclear instructions 2 (Minor)

The third requirement states that "User object needs to be returned with the added exercise". This is not the case. From the instructions, it appears that it's required to return the full user object as you would on the /api/exercise/log page. What needs to be returned is a summary object with the users username, their _id,  as well as the exercise data. The returned object should look like the below:
{
"username":"krisb1220",
"_id":"5eba18ae93e4aa5b2434991f",
"description":"coded",
"duration":20,
"date":"Thu May 14 2020"
}

Issue 3: Code breaks server.js (Major)
Also, on the Exercise Tracker project, the following code breaks the server if users do not place their endpoints before it. See my pull request on the boilerplate repo, as I've clarified this with comments:

// Not found middleware
app.use((req, res, next) => {
  return next({status: 404, message: 'not found'})
})

// Error Handling middleware
app.use((err, req, res, next) => {
  let errCode, errMessage

  if (err.errors) {
    // mongoose validation error
    errCode = 400 // bad request
    const keys = Object.keys(err.errors)
    // report the first validation error
    errMessage = err.errors[keys[0]].message
  } else {
    // generic or custom error
    errCode = err.status || 500
    errMessage = err.message || 'Internal Server Error'
  }
  res.status(errCode).type('txt')
    .send(errMessage)
})

Fixes
Repo: https://github.com/krisb1220/boilerplate-project-exercisetracker/tree/glitch (NOT MASTER BRANCH, GLITCH BRANCH) --- Pull request on the original repo has been submitted
Project Page: https://glitch.com/~freecodecamp-exercise-tracker-project
Project Code Page: https://glitch.com/edit/#!/freecodecamp-exercise-tracker-project
Advanced Node and Express - Implement the Serialization of a Passport User
https://www.freecodecamp.org/learn/information-security-and-quality-assurance/advanced-node-and-express/implement-the-serialization-of-a-passport-user
Issue 1: Deprecated Connection Method (Major)
The MongoDB connection method shown in the instructions has been deprecated. The challenge doesn't currently pass using the non-deprecated option. I simply used the non-deprecated option to pass the challenge and changed it after, but some users may not realize this is an option.
Proper Connection Method:
const MongoClient = require('mongodb').MongoClient;
const MongoOptions = {useUnifiedTopology: true, useNewUrlParser:true};
const Client = new MongoClient(process.env.DATABASE, MongoOptions);

Client.connect((err, db)=>{
  if(err) console.error(err);
  else console.log("connected to databse");
})

Method Shown  (Deprecated, soon to be removed)
mongo.connect(process.env.DATABASE, (err, db) => {
  if(err) {
    console.log('Database error: ' + err);
  } else {
    console.log('Successful database connection');

    //serialization and app.listen
  }
});

Advanced Node and Express - Create New Middleware (MAJOR) [Edited]
Issue 1: Challenge only passes if you change the index.pug template's  attribute to Home Page. Thanks to @magnus195 for pointing this out to me :)
Tell us about your browser and operating system:

Browser Name: Chrome
Browser Version: "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36"
Operating System: Windows 10

If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):

Also, on the Exercise Tracker project, the following code breaks the server:

// Not found middleware
app.use((req, res, next) => {
  return next({status: 404, message: 'not found'})
})

// Error Handling middleware
app.use((err, req, res, next) => {
  let errCode, errMessage

  if (err.errors) {
    // mongoose validation error
    errCode = 400 // bad request
    const keys = Object.keys(err.errors)
    // report the first validation error
    errMessage = err.errors[keys[0]].message
  } else {
    // generic or custom error
    errCode = err.status || 500
    errMessage = err.message || 'Internal Server Error'
  }
  res.status(errCode).type('txt')
    .send(errMessage)
})

Just had the issue with my middleware not passing at advanced Node. Had to add "Home page" to the template :|

Just came here to write this issue up as well.  This a good summary of the issues I have found with the exercises on glitch, so much that I decided to write them locally and use ngrok to tunnel them externally to be tested.
But to reiterate the biggest points that need some touching up:

outdated node version (glitch supports to ver. 12.0.0), node package versions
outdated mongo/mongoose connection conventions that don't align with the mongo atlas URI

lots of remnants of the old mlab connection details

each boilerplate has lots of extra boilerplate

an example is the error handling middleware in the exercise tracker boilerplate.

inconsistent boiler plate

things are defined in several ways, while this may convey how unopinionated expressjs is, it may be detrimental to students developing a style from reading examples

microservice problems are generally poorly specified for return values and format.

exercise tracker is by far the most egregious example of this

my issue here https://www.freecodecamp.org/forum/t/exercise-tracker-4th-user-story/397475

I am willing to help with these things if it can be triaged and pointed out where best to contribute by a more senior contributor

Just to increase visibility, #37590 describes challenges with this exercise from another perspective

+1 for Exercise Tracker Project having outdated package versions for mongoose and mongodb.  Just today I was copying code blocks from the previous project, URL shortener, wondering why my mongoose save() method was failing to save the document.

Hello! First time posting, sorry if this is the wrong place.
In regards to the first issues mentioned for Quality Assurance and Testing with Chai:
The challenge instructions, the Repl.it boilerplate comment instructions and the test failure messages are inconsistent to what the challenge submission test is actually asserting.
Run Functional Tests using a Headless Browser challenge and Repl.it instructions and the test failure messages indicate to use "Cristoforo" and "Colombo", but the the test assertions. require "Marco" and "Polo", respectively.
Run Functional Tests using a Headless Browser II Repl.it instructions and the test failure messages indicate to use "Amerigo" and "Vespucci", but  the challenge instructions and the test assertions require "Cristoforo" and "Colombo", respectively.
I personally wasn't able to pass these tests, until I checked the challenge testing repositories.
Hope this helps!
Headless I:

Headless II:

Heya @mwinser - we are working on a PR currently to fix those concerns. 🙂

Thanks again @krisb1220 for all of these details and everyone else for your input.
Some general notes:

We decided to remove Mongo, Mongoose, some other dependencies, and the Node version from the boilerplates and allow learners to install them as they work on the projects. This will allow for some extra practice with the command line and setup, and prevent us from having to review and merge package / Node updates.
The endpoints for several of the API challenges, including the Exercise Tracker project, were recently updated. Some of the test text has also been updated since this issue was opened.

Here's a checklist so we can keep track of everything that still need further investigation or a fix:
Quality Assurance and Testing with Chai
Run Functional Tests using a Headless Browser and Run Functional Tests using a Headless Browser II

[x] Tests not passing (https://github.com/freeCodeCamp/freeCodeCamp/pull/40330)
[ ] Packages outdated (will be fixed in https://github.com/freeCodeCamp/freeCodeCamp/pull/43065 and https://github.com/freeCodeCamp/boilerplate-mochachai/pull/42)

Exercise Tracker Project

[x] Outdated Mongoose / Mongo versions (https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/pull/42)
[x] Outdated Node version (https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/pull/45)
[ ] Unclear instructions for user story 4 and / or 5 (Needs further investigation)
[ ] Unclear instructions for user story 4 (Needs further investigation)
[x] Code breaks server.js (Boilerplate was simplified in https://github.com/freeCodeCamp/boilerplate-project-exercisetracker/pull/42)

Advanced Node and Express
Implement the Serialization of a Passport User

[x] Deprecated connection method (https://github.com/freeCodeCamp/boilerplate-advancednode/pull/11)

Create New Middleware

[x] Challenge only passes if you change the index.pug template's <title> attribute to Home Page (https://github.com/freeCodeCamp/boilerplate-advancednode/pull/11)

All of the points mentioned above, along with some others, should be fixed with the PRs in my last comment.
Thanks again everyone for your valuable feedback, and for helping us improve the backend curriculum.


Can not run: ResourceUnavailable: (:) [], ApplicationFailedException

Windows Terminal version
1.16.10261.0_x64
Windows build number
19044.2006
Other Software
No response
Steps to reproduce
Install from powershell, but can't startup
start in powershell:
cd C:\Program Files......
.\WindowsTerminal.exe
Expected Behavior
No response
Actual Behavior
+ CategoryInfo : ResourceUnavailable: (:) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed

You almost certainly shouldn't be attempting to run WindowsTerminal.exe out of our package directly. When the app is installed, it should install an "app execution alias" for wt.exe. The path for that should be something like %localappdata%\Microsoft\WindowsApps\wt.exe - does that work/?

@zadjii-msft not work, I start wt.exe in powershell, but it no response, no any output and not return.

Try running where wt. If that can't find it, then either the wt App Execution Alias isn't enabled, or your %PATH% is messed up.
First try toggling the App Execution Alias for WT off then on the screen at https://stackoverflow.com/a/66539884/1743
If that doesn't work, then make sure C:\Users\<your user>\AppData\Local\Microsoft\WindowsApps\ is on your PATH


Ensure unique VPN tlsauth secrets for different tlsauth keys

How to categorize this PR?

/area control-plane
/kind bug
What this PR does / why we need it:
The secret containing the VPN tlsauth key has always the same name vpn-seed-server-tlsauth-a1d0aa00, currently.
The secretsmanager works as designed. The hash calculation uses the provided config only. Unfortunately, in this case it is only the secret name prefix itself, as the tlsauth key is a purely random value.
In edge cases, e.g. if the vpn-seed-server-tlsauth-* secret is deleted, the secret is recreated with the same name but a new key. This can lead to situations where pods of vpn-seed-server and vpn-shoot (and kube-apiserver in the HA case) have different tlsauth keys, as the deployments stay unchanged. They have only a reference to the secret name, which remains the same, although its data has changed. In such cases the vpn-seed-server reports errors on client connection like
Authenticate/Decrypt packet error: packet HMAC authentication failed

With this PR it is ensured, that the secret has as an unique name with respect to the key itself and the deployments are updated accordingly.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Introducing .gitguardian.yaml to avoid incident with false positive.
Release note:

Ensure unique VPN tlsauth secret names for different tlsauth keys.

⚠ GitGuardian has uncovered 2 secrets following the scan of your pull request.

These are false positives. I've already tried to avoid incidents by introducing a match in the .gitguardian.yaml file.

/cc @ScheererJ

/assign

/hold

/assign

AFAIK this one can be closed @MartinWeindel @rfranzke?

Isn't it good practice to have unique names for immutable secrets?
Unfortunately, the secretsmanager relies on static config to calculate the secret name and cannot guarantee uniqueness with respect to the secret data.

Maybe, but if we decide to improve this part, I assume it's definitely not the approach taken in this PR. The problematic situation you describe is also very far-fetched FMPOV. If a human user is manually tampering with the secrets, they should know what they do and also manually restart the affected components after a reconciliation.
Hence, I also vote for closing it. If you want, open a new, dedicated issue with the problem statement. If we decide to improve it, I assume we should do it directly in the secrets manager.

/remove-approve


[EKS] panic: runtime error: index out of range [0] with length 0

Bug Report

General Information

Environment description - EKS

Kernel version Linux arch 5.18.12-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 15 Jul 2022 15:33:02 +0000 x86_64 GNU/Linux

Orchestration system version in use

➜  ~ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.2", GitCommit:"f66044f4361b9f1f96f0053dd46cb7dce5e990a8", GitTreeState:"archive", BuildDate:"2022-06-18T07:33:51Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"22+", GitVersion:"v1.22.10-eks-84b4fe6", GitCommit:"cc6a1b4915a99f49f5510ef0667f94b9ca832a8a", GitTreeState:"clean", BuildDate:"2022-06-09T18:24:04Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.24) and server (1.22) exceeds the supported minor version skew of +/-1

Link to relevant artifacts (policies, deployments scripts, ...)
Target containers/pods

To Reproduce

Instruction
-> aws eks --region <region-code> update-kubeconfig --name <cluster-name>
-> karmor install
output

➜  ~ karmor install
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
github.com/kubearmor/kubearmor-client/install.autoDetectEnvironment(0xc000127400)
        /home/runner/work/kubearmor-client/kubearmor-client/install/install.go:363 +0x5d7
github.com/kubearmor/kubearmor-client/install.K8sInstaller(0xc000127400, {{0x1dc20e8, 0xb}, {0x1ddb80f, 0x1a}, {0x0, 0x0}, 0x0})
        /home/runner/work/kubearmor-client/kubearmor-client/install/install.go:32 +0x6e
github.com/kubearmor/kubearmor-client/cmd.glob..func4(0x2fc69c0?, {0x1db7cf8?, 0x0?, 0x0?})
        /home/runner/work/kubearmor-client/kubearmor-client/cmd/install.go:19 +0x52
github.com/spf13/cobra.(*Command).execute(0x2fc69c0, {0x301b2f8, 0x0, 0x0})
        /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.4.0/command.go:856 +0x67c
github.com/spf13/cobra.(*Command).ExecuteC(0x2fc6c40)
        /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.4.0/command.go:974 +0x3b4
github.com/spf13/cobra.(*Command).Execute(...)
        /home/runner/go/pkg/mod/github.com/spf13/cobra@v1.4.0/command.go:902
github.com/kubearmor/kubearmor-client/cmd.Execute()
        /home/runner/work/kubearmor-client/kubearmor-client/cmd/root.go:43 +0x25
main.main()
        /home/runner/work/kubearmor-client/kubearmor-client/main.go:9 +0x17

Instruction 2

Expected behavior
A description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.

I am suspecting here the nodes are not ready!
Can you please share the output for
kubectl get nodes -owide
and
Archive generate by
karmor sysdump?
Thank You!

Can you raise this issue on kubearmor-client? Thanks.

Should be handled in https://github.com/kubearmor/kubearmor-client/releases/tag/v0.7.12.
Please reopen if any updates or if you have more context for this error.


Fix - update python runtime

Updating python version in runtime.txt as 3.9.10 is no longer supported in Python Buildpack 1.7.53

Codecov Report

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

:exclamation: Current head 3fdc3b6 differs from pull request most recent head 579bfa6. Consider uploading reports for the commit 579bfa6 to get more accurate results

@@            Coverage Diff             @@
##             develop     #143   +/-   ##
==========================================
  Coverage           ?   32.61%
==========================================
  Files              ?       60
  Lines              ?     3017
  Branches           ?      521
==========================================
  Hits               ?      984
  Misses             ?     2021
  Partials           ?       12

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d409aca...579bfa6. Read the comment docs.


Nofiy tweaks

This distinguishes notifications in channels from unread messages and allows to configure a list of words to notify about

If I may, there is a typo in your PR title
~notiy~ => notify


Proposal: Change the DNS impl for the nerdctl network

What is the problem you're trying to solve
For now, the nerdctl uses the /etc/hosts file to record the DNS for the different containers.
But in some circumstances, we need to maintain the different hosts file for different containers (add a record when a container create successfully, delete a record when a container delete successfully)
If the file is not right, there should be some DNS issues for the user, such as #1149
So maybe we need to use a better way to record the DNS.
Describe the solution you'd like
Maybe we can use dnsname as a reference.
The dnsname makes a CNI plugin to record the DNS item. It allocates a dnsmasq process for each network. I think it's a good example for us.
cc @AkihiroSuda @junnplus @fahedouch
Additional context
No response

@AkihiroSuda would you mind helping me to add a label kind/proposal for this project?

SGTM,  think it is a good idea to delegate dns recording to the dnsmasq rather than nerdctl

SGTM as an opt-in.
The default should remain files, as dnsname is not a part of https://github.com/containernetworking/plugins

The default should remain files, as dnsname is not a part of https://github.com/containernetworking/plugins

Yes, the people can choose DNS engine theirself

Please let me know if I'm hitting this limitation or another one:
When running nginx using docker, the correct way to use the resolver command is to pass it the ip of the Docker DNS resolver, <IP_ADDRESS>
When running nginx using docker, nerdctl-provided DNS resolver (whatever it writes in /etc/resolv.conf, <IP_ADDRESS> in my case) can only resolve external names, and any names on the nerdctl network are hardcoded in /etc/hosts only, so nginx cannot resolve them.


Incorrect tuning curves for unsampled bins

At the moment, when a particular bin of a feature is unsampled, the tuning curve functions will set the average firing rate for that bin to zero.
This seems incorrect?
We do not know if there is no firing for that bin, hence, does it not make more sense to set it to NaN?

The tuning curves are normalized by occupancy. NaNs represents bin that have never been visited. 0 indicate no spikes. You can see an example here or you can run this code :
import numpy as np
import pynapple as nap
import matplotlib.pyplot as plt

dt = 0.1
features = np.vstack((np.cos(np.arange(0, 1000, dt)), np.sin(np.arange(0, 1000, dt)))).T
features = nap.TsdFrame(t=np.arange(0, 1000, dt),d=features)

ts_group = nap.TsGroup({0:nap.Ts(t=[0, 500, 999])})

tcurves2d, binsxy = nap.compute_2d_tuning_curves(
    group=ts_group, features=features, nb_bins=10
)

plt.figure(figsize=(12, 6))
plt.subplot(121)
plt.plot(features[:,0], features[:,1])
tmp=ts_group[0].value_from(features)
plt.plot(tmp[:,0], tmp[:,1], 'o')
plt.title("Feature + Spikes")
plt.subplot(122)
extents = (
    np.min(features[:,1]),
    np.max(features[:,1]),
    np.min(features[:,0]),
    np.max(features[:,0]),
)
plt.imshow(tcurves2d[0].T, origin="lower", extent=extents, cmap="viridis")
plt.title("Tuning curve")
plt.show()

I understand, and it seems to be so for 2D tuning curves.
However, when I tried yesterday for 1D tuning curves:
138    for k in group_value:
139        count, _ = np.histogram(group_value[k].values, bins)
140        count = count / occupancy
141        count[np.isnan(count)] = 0.0
142        tuning_curves[k] = count
143        tuning_curves[k] = count * feature.rate

line 141 seems to be setting NaNs to 0.
In the 2D version, this line is commented.

Good catch. In fact, it's quite rare to have a 1d feature that does not span its whole extent. This is high priority so I will bump a new version as soon as possible. Leaving it open until it is resolved.

New version 0.7.1 is out with a fix to this issue.
Closing it.


release-pr is created wrong

Bug description
flying-sheep/xdot-rs#29 was created with conflicts and wrong changes (the diff displayed by GitHub seems to include a lot of changes that have been made long ago)

Would you like to work on a fix? n

To Reproduce
Unknown
Expected behavior
PR is created with just changes to package version and changelog
Environment

OS: N/A
release-plz version: 0.5

Thank you for reporting the issue.
This also happened to me. I reported it in https://github.com/MarcoIeni/release-plz/issues/615
I will add your pr as an example in that issue and close this one because it's a duplicate.
If you find a way to reproduce this issue, let me know so that it would be easier to debug.

as a workaround, I think closing the pr and running release-plz again should work.

Here are the logs:
  2023-05-05T11:44:29.563305Z  INFO  xdot: next version is 0.2.4 (✓ API compatible changes)
    in packages_to_update
    in next_versions with input=UpdateRequest { local_manifest: "/tmp/.tmpaZVcIc/xdot-rs/Cargo.toml", registry_manifest: None, single_package: None, changelog_req: ChangelogRequest { release_date: None, changelog_config: None }, registry: None, dependencies_update: false, allow_dirty: false, repo_url: Some(RepoUrl { scheme: "https", host: "github.com", port: None, owner: "flying-sheep", name: "xdot-rs" }), packages_config: PackagesConfig { default: UpdateConfig { semver_check: Lib, changelog_update: true }, overrides: {} } }
    in update with input=UpdateRequest { local_manifest: "/tmp/.tmpaZVcIc/xdot-rs/Cargo.toml", registry_manifest: None, single_package: None, changelog_req: ChangelogRequest { release_date: None, changelog_config: None }, registry: None, dependencies_update: false, allow_dirty: false, repo_url: Some(RepoUrl { scheme: "https", host: "github.com", port: None, owner: "flying-sheep", name: "xdot-rs" }), packages_config: PackagesConfig { default: UpdateConfig { semver_check: Lib, changelog_update: true }, overrides: {} } }
    in release_pr with input=ReleasePrRequest { git: Github(GitHub { remote: Remote { owner: "flying-sheep", repo: "xdot-rs", token: Secret([REDACTED alloc::string::String]), base_url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("api.github.com")), port: None, path: "/", query: None, fragment: None } } }), labels: [], update_request: UpdateRequest { local_manifest: "/home/runner/work/xdot-rs/xdot-rs/Cargo.toml", registry_manifest: None, single_package: None, changelog_req: ChangelogRequest { release_date: None, changelog_config: None }, registry: None, dependencies_update: false, allow_dirty: false, repo_url: Some(RepoUrl { scheme: "https", host: "github.com", port: None, owner: "flying-sheep", name: "xdot-rs" }), packages_config: PackagesConfig { default: UpdateConfig { semver_check: Lib, changelog_update: true }, overrides: {} } } }

    Updating xdot v0.2.3 (/tmp/.tmpaZVcIc/xdot-rs) -> v0.2.4
  2023-05-05T11:44:30.878025Z ERROR  cannot rebase from default branch: error while running git with args `["rebase", "main"]:
- stdout: Auto-merging .gitignore
CONFLICT (add/add): Merge conflict in .gitignore
Auto-merging Cargo.lock
CONFLICT (add/add): Merge conflict in Cargo.lock
Auto-merging Cargo.toml
CONFLICT (add/add): Merge conflict in Cargo.toml
- stderr: Rebasing (1/50)
error: could not apply dc55b10... WIP
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply dc55b10... WIP
    in release_pr with input=ReleasePrRequest { git: Github(GitHub { remote: Remote { owner: "flying-sheep", repo: "xdot-rs", token: Secret([REDACTED alloc::string::String]), base_url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("api.github.com")), port: None, path: "/", query: None, fragment: None } } }), labels: [], update_request: UpdateRequest { local_manifest: "/home/runner/work/xdot-rs/xdot-rs/Cargo.toml", registry_manifest: None, single_package: None, changelog_req: ChangelogRequest { release_date: None, changelog_config: None }, registry: None, dependencies_update: false, allow_dirty: false, repo_url: Some(RepoUrl { scheme: "https", host: "github.com", port: None, owner: "flying-sheep", name: "xdot-rs" }), packages_config: PackagesConfig { default: UpdateConfig { semver_check: Lib, changelog_update: true }, overrides: {} } } }

  2023-05-05T11:44:30.880562Z ERROR  cannot update release pr 27: error while running git with args `["stash", "pop"]:
- stdout: .gitignore: needs merge
Cargo.lock: needs merge
Cargo.toml: needs merge
The stash entry is kept in case you need it again.. I'm closing the old release pr and opening a new one
    in release_pr with input=ReleasePrRequest { git: Github(GitHub { remote: Remote { owner: "flying-sheep", repo: "xdot-rs", token: Secret([REDACTED alloc::string::String]), base_url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("api.github.com")), port: None, path: "/", query: None, fragment: None } } }), labels: [], update_request: UpdateRequest { local_manifest: "/home/runner/work/xdot-rs/xdot-rs/Cargo.toml", registry_manifest: None, single_package: None, changelog_req: ChangelogRequest { release_date: None, changelog_config: None }, registry: None, dependencies_update: false, allow_dirty: false, repo_url: Some(RepoUrl { scheme: "https", host: "github.com", port: None, owner: "flying-sheep", name: "xdot-rs" }), packages_config: PackagesConfig { default: UpdateConfig { semver_check: Lib, changelog_update: true }, overrides: {} } } }

  2023-05-05T11:44:33.934200Z  INFO  opened pr: https://github.com/flying-sheep/xdot-rs/pull/29
    in open_pr
    in release_pr with input=ReleasePrRequest { git: Github(GitHub { remote: Remote { owner: "flying-sheep", repo: "xdot-rs", token: Secret([REDACTED alloc::string::String]), base_url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("api.github.com")), port: None, path: "/", query: None, fragment: None } } }), labels: [], update_request: UpdateRequest { local_manifest: "/home/runner/work/xdot-rs/xdot-rs/Cargo.toml", registry_manifest: None, single_package: None, changelog_req: ChangelogRequest { release_date: None, changelog_config: None }, registry: None, dependencies_update: false, allow_dirty: false, repo_url: Some(RepoUrl { scheme: "https", host: "github.com", port: None, owner: "flying-sheep", name: "xdot-rs" }), packages_config: PackagesConfig { default: UpdateConfig { semver_check: Lib, changelog_update: true }, overrides: {} } } }

as a workaround, I think closing the pr and running release-plz again should work.

hmm, I already closed an earlier PR like this.

2023-05-05T11:44:30.878025Z ERROR  cannot rebase from default branch: error while running git with args `["rebase", "main"]:

What causes this? release-plz is run by CI on a clone from main. Where does it get the commit from that it tries do apply its changes to?


[FEATURE] Port poolifier to bun

Duplicate issue

[X] I've searched for any related issues and avoided creating a duplicate issue.

Description
Bun is the fastest JS runtime at the time

Create a forked repo called poolifier-bun: https://github.com/poolifier/poolifier-bun
Remove cluster pools
Use bun tools
Use bun APIs
Implement pools on top https://bun.sh/docs/runtime/nodejs-apis#node-worker-threads

Evaluate if a code reconciliation is possible after the stable release.
Attachments
No response

Is there a better way to achieve this without forking and maintaining two separate codebases?

I doubt it. And in any case, the first step is to test current bun support regarding worker_threads. And the initial portage work is far from working. Bun worker_threads support does not seem to be stable enough yet to execute poolifier code without fixing bun.

Required upstream PRs:

https://github.com/oven-sh/bun/pull/6521

Looking forward to using this with bun

Looking forward to using this with bun

Given the current state of bun worker_threads integration, that will not happen anytime soon: most poolifier tests fail or hang.
I think making a package from the Deno portage using standardized web workers will likely work sooner with bun, given that web workers need only stabilisation work.

Initial npm release done: https://www.npmjs.com/package/poolifier-web-worker


LNBIts/IP2Tor

Tried to test LNUrlW using IP2Tor.  Was able to create and fund wallet and withdrawal link.  However i get the attached error when trying to receive sats using Breez wallet.

Try to add LetsEncrypt (with a duckdns domain) to LBbits. Its now in 1.6RC3 for testing under subscriptions.

Thanks, that worked!
https://liab-blitz.duckdns.org:38950/withdraw/JCHJNhKySd7sdoNk5Gosmn


idasen: init at 0.7.1

Motivation for this change
Add idasen
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

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

[x] Fits CONTRIBUTING.md.

Whoops, sorry about that CI failure, I accidentally included a line I should not have when I was staging.

Made the requested changes, thanks for the review!


Enforce usage of mypy-diff

Currently, we don't enforce anything.
Although it may not be feasible to rectify all existing issues, we must ensure that we do not introduce any new ones.
This can be done easily on the CI by ensuring that we do a mypy-save on the master branch and then checkout on the branch that needs to be tested.

No longer relevant, we're now using mypy-baseline in the ci


[Snyk] Upgrade: @storybook/addons, @storybook/client-api

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade multiple dependencies.
👯♂ The following dependencies are linked and will therefore be updated together.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Name
Versions
Released on

@storybook/addonsfrom 7.3.2 to 7.4.0
4 versions ahead of your current version
a month agoon 2023-08-29

@storybook/client-apifrom 7.3.2 to 7.4.0
4 versions ahead of your current version
a month agoon 2023-08-29

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Check out a preview of your pull request here: https://alphasite-appservice-dev-pr-preview-3.azurewebsites.net


Feature/blobstore-business-cards-server

Created BlobstoreURL servlet to handle generating a Blobstore URL (which should be used as the endpoint for the POST request on the front-end) and returning it to the client.
Created BusinessCard servlet to 1) Handle POST requests that contain a business-card image (validates the input, stores the download URL in datastore) and 2) handle GET requests from the client and respond with a list of all stored download URLs of business cards.
Also created HttpServletWithUtilities as an extension to the regular HttpServlet to allow for utility functions (converting a list to JSON, getting value of parameter) to be universally accessible via inheritance. Will add future utility functions to this servlet.

Trying fix for storing images without using ImageService - this will allow this to work in prod

All good now - to get this working on production server a new approach was required. ImagesService couldn't be used, but BlobstoreService has the ability to serve files from their blobkeys.
In order to implement this, some minimal front-end changes were needed.
Form:

Sample Hosted Image:


changed balance to allow negative values

For now, I have allowed the balances to be negative as well. This could be a bug in the explorer api which we can investigate further.

Solves https://github.com/Electra-project/electra-api/issues/4


Improve implementations of EfCoreTreeRepository

@RayMMond Hi:
Thanks for your nice work,looks much better .
I will check and merge it asap .Thank you

@RayMMond 👍
Thank You,
I will modify some code from your pr
If there are any problems, we can discuss

Why didn't commit to this PR and merge into dev?

@RayMMond
I will close this p.r and those code already merged to dev and master


Incorporate final AMR metadata sets (from the original "19")

They are in Box, ready for incorporation

DONE.


update substrate to polkadot-v0.9.40

better to do them first? or maybe do them in the next release branch?

merge https://github.com/rust-blockchain/ethereum/pull/50 ?
release a new version of ethereum?
release a new version of evm?

@sorpaas PTAL

@sorpaas friendly ping

@koushiro I have bumped substrate rev further up and fixed some of the breaking changes.
I have also removed pallet-timestamp over UnixTime. Would to like some feedback before I propose a change.
https://github.com/subspace/frontier/tree/subspace-v1

@koushiro I have bumped substrate rev further up and fixed some of the breaking changes.
I have also removed pallet-timestamp over UnixTime. Would to like some feedback before I propose a change. https://github.com/subspace/frontier/tree/subspace-v1

The changes related to pallet_timestamp I think you can extract it separately and open a PR into upstream.

@sorpaas PTAL

@sorpaas PTAL

@sorpaas could you review and merge this PR? I wanna to update the substrate to polkadot-v0.9.42 ASAP.

CI broken on the master branch due to https://github.com/paritytech/frontier/pull/1031

Hmm there are now more errors in tests..

it caused by #1030, I don't why no git conflicts occur 😕  I'm fixing it now


fix the rare case of infinite loop

The function randomLevel has a very low probability to fall into an infinite loop. Besides, we can use rand.Float64() to generate a pseudo-random number between 0.0 and 1.0, instead of using rand.Int31() and the mask operation.

the current version of randomLevel is:
func randomLevel() int16 {
var level int16 = 1
for level < maxLevel {
if rand.Float64() < probability {
break
}
level++
}
return level
}