Container Security Operator v1.0.5

Updates to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

@J0zi Could you review this, please?

@alecmerdler, there is a pipeline issue on our side. Bear with us.

/test CVP


SBOL UML first implementation

UML implementation working as far as smoke tests of library creation and simple calibration protocol

Thank you, @danbryce ; the commented code is next on the block for updates, and just needed to be out of the way to keep from interfering in current runs. Not the cleanest practice, but it shouldn't last long.

My other observation is that you are keeping a list of behaviors and treating the protocol as sequential (at least in the example I saw).  I think that a list is fine, but it may be better as a set.  The flows will imply a partial ordering that may be different from the total ordering implied by the list.

The representation and library support that: just use execute_primitive instead of primitive_step.
The primitive_step function is a macro for execute_primitive plus order(last_step,this_step), to allow easier translation of "paper protocols".

Sorry to be so dense, but what do you mean by "UML implementation"? Is it that uml.ttl is the core of this PR?  I'm trying to find my way through this PR, but I need a little bit more explanation in PR description; I don't know what's being attempted, so it's hard to know how to evaluate it.

The code in __init__ is an sbol_factory pattern. @bbartley and I are discussing potential ways to make this more "normal", but right now that's the monkey-patching pattern is the only way we've figured out for adding methods to the autogenerated classes.  Potential alternatives under consideration:

Generating code and inserting chunks
Generating code that then respects blocks edited with a certain format
Inserting "silent" extension classes into the inheritance hierarchy

None of these seem significantly less ugly; if you can figure out a better alternative, I'm happy to hear it.

@rpgoldman

Sorry to be so dense, but what do you mean by "UML implementation"? Is it that uml.ttl is the core of this PR? I'm trying to find my way through this PR, but I need a little bit more explanation in PR description; I don't know what's being attempted, so it's hard to know how to evaluate it.

You are correct. uml.ttl is the core of the PR, with uml/__init__.py the helper classes to allow one to build protocols compactly with it.  Everything else is either consequences of that changes or tests validating that it lets us specify a protocol.

One possible issue: the uml.ttl file seems to use Turtle* notation, rather than simple Turtle. The difference comes when dealing with quads and reification.  I ran the following command to translate uml.ttl to uml-flattened.ttl:
docker run -v `pwd`:/models turtlestar2turtle /models/uml.ttl > uml-flattened.ttl

I can't figure out how to attach the file to the issue, so I have committed it. If it's important to have a translation, we will have to figure out how to keep it synced and also figure out how tools that won't process Turtle* can download the flattened equivalent.


add profiles to allow multiple instances with different addons and themes in the same time

it would be nice to add profiles, for example:
Profile A: has A theme and A Enabled addons...
Profile B: has B theme and B Enabled addons...
i think this will help when working on different projects

I am not sure if I understand your requirement correctly. Profiles are independent of each other and each one can be configured with a theme and different extensions.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


[FRONTEND WITH FRAMEWORK]: Angular(5.2) -> Defining a route

Description

What is route?
How to add route to application?
What is route order?
Explain with syntax/example
Reference :- https://angular.io/guide/router

(Week 5 Issue)
Note:-

Don't copy paste, we would be merging after reviewing the PR.
Changes should be made inside "Frontend_Web_Development_React_Angular_Vue/Angular/Week5" directory
Tasks would be assigned on First Come First Serve Basis

Domain
Frontend Dev React/Angular/Vue
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

I will create a pr for other issue till tomorrow so, If You would like to assign it to me Then please assign it to me.


Migrates the camel-aws-sqs integration tests to the shared test infra

[x] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md

Thanks. I would probably focus on the Aws2 components. The v1 will be deprecated at some point

Thanks. I have that one in progress too :)


Facing issue when running "pip install -v -e ." on windows machine

Facing issue when running "pip install -v -e ." on windows machine
config{
windows:10
cuda 10.2
python:3.8}

Updating pip worked for me.
python -m pip install --upgrade pip

As explained here https://forums.developer.nvidia.com/t/strange-link-error-seen-by-multiple-people-while-building-pytorch-cpp-cuda-extensions/145261/2 the issue happens because long resolves to 32-bit int on Windows as opposed to 64-bit long long on Linux. Replace the two occurrences of long in sigmoid_focal_loss_cuda.cu with int64_t and it will work fine.


Clipping is "delayed" in renderer 2.1 release

If you check out
https://lightning-tv.github.io/solid-demo-app/#/
And keep pressing down. The images go outside of the clipped area and then disappear. Seems like with the new renderer 2.1 release clipping isn't happening every frame.

And sometimes breaks

So in 2.1 a lot of operations are suppressed when it goes out of bounds to save excess CPU, as what's the point of doing changes to something that isn't visible anyway.
But it seems the bounds detection is going off early or it's racing with clipping when you're moving fast. Will have a look to see if this is simply a matter of reordering the operations or if we need to keep track of in bound changes vs outbound changes.

We are having the same issue in our React renderer

We are having the same issue in our React renderer

I'd recommend to stick to 2.0 until we figure this out.

Just to add to this, may or may not be related, but when animating things off screen or onto the screen, it will often either not animate at all or not show up at all.

It is, its not properly propagating the change down from parents to children in all cases.


Add support for Storage::drive besides Storage::disk

[x] Added or updated tests
[x] Documented user facing changes
[x] Updated CHANGELOG.md

Changes
Storage::drive is an alias for Storage::disk so can be supported by just checking for it in the StorageDynamicStaticMethodReturntypeExtension
Breaking changes
None

Thank you.


doc suggestion for customize page

The [customize] (http://www.getmdl.io/customize/index.html) page of the docs do a great job of showing how to customize the color theme. However, some users may want more customization. I happen to know that simply adding an extra css file that loads last, with whatever customization a user wants, will override anything in MDL, but not every user will be aware that. Adding something to that effect might be helpful.
Great job so far. I'm especially impressed how fast issues are being addressed. Thanks for this.

adding an extra css file that loads last, with whatever customization a user wants, will override anything in MDL, but not every user will be aware that.

Considering this is a fundamental part of web dev, people using MDL should know this. There is a certain level of expected knowledge with any documentation project.

unsub
On Tue, Jul 7, 2015 at 6:42 PM, Jonathan Garbee<EMAIL_ADDRESS>wrote:

adding an extra css file that loads last, with whatever customization a
user wants, will override anything in MDL, but not every user will be aware
that.
Considering this is a fundamental part of web dev, people using MDL should
know this. There is a certain level of expected knowledge with any
documentation project.
—
Reply to this email directly or view it on GitHub
https://github.com/google/material-design-lite/issues/841#issuecomment-119364991
.

@addyosmani Do you think this is really necessary to add to the customizer page?
It is superfluous content at best to the great majority of users. We'd be better off spending time focusing on Sass level customization documentation to help developers get their own build pipeline going in that regard then handling this low-level information.

Imo, this content should be deferred to an FAQ. I consider it P2 compared to focusing on better improving the docs situation for Sass.

Superceded by https://github.com/material-components/material-components-web/issues/49


Disable "swiping" on mobile w/ cssMode: true ?

How to disable "swiping" effect on mobile with cssMode: true ?

anyone?

cssMode is just a CSS's overflow: auto, so you can set/unset overflow: hidden on swiper to prevent it


Thank you - I love carbon!!

Hello! I just wanted to say that I really love carbon and I wanted to say THANK YOU!

AAAAAND I close this "issue" - it is not an issue - it is a THANK YOU note :-)

@denisenepraunig thank you for the kind words 😍


FutureWarning: sort(columns=....) is deprecated, use sort_values(by=.....)

@tzonghao Can you take a look at this? It has to do with pandas.
This was reported in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802079

Alex, I won't have access to computer until sometime next week.

On: 17 October 2015 17:28, "Alexandre Viau"<EMAIL_ADDRESS>wrote:
@tzonghaohttps://github.com/tzonghao Can you take a look at this?

Reply to this email directly or view it on GitHubhttps://github.com/influxdb/influxdb-python/issues/258.


Panic with percli offline migrate

What did you do?
I'm trying to migrate the grafana NodeExporterFull dashboard to Perses using percli.
What did you expect to see?
No response
What did you see instead? Under which circumstances?
I'm getting this panic error
./bin/percli migrate -f ~/tmp/node-exporter-full.json
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0xc3129b]

goroutine 1 [running]:
github.com/perses/perses/internal/cli/cmd/migrate.(*option).offlineExecution(0xc00032e8f0, {0xc000706000?, 0xcf2d80?, 0xc000300150?})
        /home/nsun/workspace/perses/internal/cli/cmd/migrate/migrate.go:132 +0x5b
github.com/perses/perses/internal/cli/cmd/migrate.(*option).Execute(0xc00032e8f0)
        /home/nsun/workspace/perses/internal/cli/cmd/migrate/migrate.go:115 +0x10a
github.com/perses/perses/internal/cli/cmd.Run({0xf5d4a0, 0xc00032e8f0}, 0xc000334608, {0xc000308440, 0x0, 0x2})
        /home/nsun/workspace/perses/internal/cli/cmd/cmd.go:42 +0xdd
github.com/perses/perses/internal/cli/cmd/migrate.NewCMD.func1(0xc00032d300?, {0xc000308440?, 0x4?, 0xdd8ed7?})
        /home/nsun/workspace/perses/internal/cli/cmd/migrate/migrate.go:153 +0x32
github.com/spf13/cobra.(*Command).execute(0xc000334608, {0xc000308420, 0x2, 0x2})
        /home/nsun/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:985 +0xaca
github.com/spf13/cobra.(*Command).ExecuteC(0xc000328008)
        /home/nsun/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1117 +0x3ff
github.com/spf13/cobra.(*Command).Execute(...)
        /home/nsun/go/pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1041
main.main()
        /home/nsun/workspace/perses/cmd/percli/main.go:97 +0x105

The json file is downloaded from Grafana website:
1860_rev37.json
By the way, the online import feature works correctly.
System information
No response
Perses version
Master branch
Perses configuration file
No response
Logs
No response

Interesting that you see this message only in "offline" I think the migration cannot be done offline as long as it needs the API endpoint. @AntoineThebaud you can confirm ?
There should be a far better error message though, and not a pity nil dereference 😅. Let me set a big priority on this.

Oops I see the code failing is named offlineExecution so I might be completely wrong in my assumption 😅

Yes there is a logic to use the local fs instead of a remote Perses server in order to retrieve the schemas powering the migration.
Will have to dig in the issue here..


feat(optimus): add api for listing the secrets

Conflicts from previous branch, closing PR. Will reopen after resolving conflicts.


Inconsistent detection of gamepad status

The function 'input_player_using_gamepad' returns true while the function 'input_player_get_gamepad' still returns -1. This happens when the code is run on the same frame as the async "gamepad connected" event. I'm using standard xInput and PS4 controllers and the function input_player_get_gamepad otherwise returns the proper index.

Turns out, 'input_player_using_gamepad' does not account for the gamepad being disconnected. It only checks to see if the last connected source was a gamepad. For code like this to work, you must also run a check to see if the source is connected using 'input_player_connected'

Will add a note to the docs to reflect this, thanks for following up with your final findings


Draft

Opening this so that I have something to assign me to. I'm wondering whether we @drwelby should do a working session and prepare this more so that it can go into a broader review?

@m-mohr I have time available to do a working session. I also wonder if we can do some kind of FOAF group within the ard.zone schedule next week.

@m-mohr I have time available to do a working session.

Sounds good. Let me know what time would suit you best.

I also wonder if we can do some kind of FOAF group within the ard.zone schedule next week.

Sounds good, too, although I'm only attending for a couple of selected talks. But if you have a time slot, let me know and I'll try to join.

@drwelby @m-mohr Does this PR represent the most up-to-date work on this extension so far?

@duckontheweb I've noodled on it some more, but if you have any quick feedback on what's in the PR as it stands I'll try to account for it before update.

Merging to main since this has enough feedback as an initial draft to be a good starting point.


no product descriptions after following installation instructions

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
newest with php 8.1
Issue Description
I get

but nothing is clickable I mean nothing moves to another more descriptive page, is this normal?  I ran all the migrate commands everything so expected a bit more in terms of having a full app instead of just the top page.
https://webkul.com/blog/laravel-ecommerce-website/
Preconditions
Installed from composer.
Steps to reproduce
install from composer, follow directions on installation instruction page.
Expected Result
I'd want a bit more than just a top page to really see your app.  This is very sad.
Actual Result
not much to talk about here.
Screenshots
No response
Additional context
No response

In the starting phase, there are no categories and products. Once you create categories and products, you will be able to see them. For a cleaner look, we have provided a simple design. However, you are free to customize this as needed.

Just to confirm the Github repo, the installation seems to have some php artisan db seed command but that does nothing?  I checked some of the tables and they were empty.  Is that correct?  What I want instead is the demo you provide at https://demo.bagisto.com/ locally so I pentest it and just get a better idea of how everything is glued together.  I believe some other frameworks like Saleor provides this, ie. a mock store that actually has products.

@nyck33 This feature is on our roadmap; users will be able to choose whether they want to proceed with sample data during installation.

why would you have that db seed command in your installation instructions?


functions passed as properties to the resolve object of $routeProvider are not converted to minification friendly dependency injection syntax

For example, this code doesn't change after ng-annotate is run on it when invoked via gulp-ng-annotate:

    $routeProvider.when('/myurl', {
        templateUrl: 'mytemplate.html',
        controller: 'mycontroller',
        resolve: {
            myproperty: function(myservice) {

            }
...

I would expect this to be output:

    $routeProvider.when('/myurl', {
        templateUrl: 'mytemplate.html',
        controller: 'mycontroller',
        resolve: {
            myproperty: ['myservice', function(myservice) {

            }]
...

gulp-ng-annotate is a very lightweight wrapper, and after inspecting its source briefly I don't think it's causing the issue ( see: https://github.com/Kagami/gulp-ng-annotate/blob/master/index.js ).

@davidjnelson, if you were able to solve this issue, I would like to know how.  I have a very similar problem.

ng-annotate only matches when it detects that we're inside an angular module (to reduce false positives). Try:
angular.module("MyMod").directive("pleasematchthis", function() {
// ...
$routeProvider.when('/myurl', {
    templateUrl: 'mytemplate.html',
    controller: 'mycontroller',
    resolve: {
        myproperty: function (myservice) {
        }
    }
});
// ...
});

The following is inside a module and does not get parsed by ngAnnotate
angular.module('routes', ['ngRoute'])
.config(function($routeProvider) {
    $routeProvider
    .when('/register', {
        templateUrl: 'register.html',
        controller: "RegisterController",
        authRequired: false,
        reloadOnSearch: false,
        resolve: {
            occupationTypes: function($q, UserService) {
                return UserService.getOccupationTypes();
            }
        }
    })
});

The following does not get parsed by ngAnnotate despite being inside a module. If I change myProvider. to $routeProvider. it works, but that is not an option for me
angular.module('routes', ['ngRoute'])
.config(function($routeProvider) {
    // Extend the default route provider, to set some default params
    var myProvider = angular.extend({}, $routeProvider, {
      when: function(path, route) {
        var defaults = {
          'authRequired': true
        };
        $routeProvider.when(path, angular.extend({}, defaults, route));
        return this;
      }
    });

    myProvider

    .when('/register', {
        templateUrl: 'register.html',
        controller: "RegisterController",
        authRequired: false,
        reloadOnSearch: false,
        resolve: {
            occupationTypes: function($q, UserService) {
                return UserService.getOccupationTypes();
            }
        }
    });
});

@Slessi It's close to impossible for ng-annotate to figure out what myProvider is using static analysis. But don't despair because you can just mark it up explicitly:
occupationTypes: function($q, UserService) {
                "ngInject";
                return UserService.getOccupationTypes();
            }

@olov MMk. Kind of annoying as I have many resolve functions like that (trimmed the file down for relevance), but oh well, thanks for your response!


Settings to dropdown popup

Move all settings selections to new dropdown popup
Move right sidebar in own razor source
some smaller fixes and refinements

drop-down behaviour has changed
E.g. on settings - workflow - state matrix page it is not clear that we are dealing with the master matrix (field empty). Also the lowest input state is now empty instead of "draft".

drop-down behaviour has changed E.g. on settings - workflow - state matrix page it is not clear that we are dealing with the master matrix (field empty). Also the lowest input state is now empty instead of "draft".

now fixed by #2009


Overflowed Search on Tablet

The search doesn't look good if there are 4 items in the menu, shop.ditectrev.com for live demo

Hey there, you can likely modify this with some CSS in your application (maybe decrease the size of the search?).

lol, it should stay as an improvement


Update http2-server to 9.4.35.v20201120

Updates org.eclipse.jetty.http2:http2-server from 9.4.34.v20201102 to 9.4.35.v20201120.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.eclipse.jetty.http2", artifactId = "http2-server" } ]

labels: library-update

Superseded by #3912.


Replacing deprecated sass-convert

According to https://github.com/SassDoc/sass-convert/issues/10#issuecomment-378757188 it seems that sass-convert is deprecated and should be replaced.

sass-convert functionality is not yet provided in Dart implementation (more details: GitHub/Dart Sass/Are you planning to implement sass-convert?). I'll close this issue, and you can follow homepage for more updates about this.
I'll wait few more months, or I'll replace sass-convert with some alternative (node-sass, Sass.js).


GUACAMOLE-1701: Implement connection date and time before and after restrictions.

This pull request implements an additional restriction type in the guacamole-auth-restrict extension that allows Connection and ConnectionGroup objects to be made available only after a certain date and/or only up to a certain date, adding to the overall ability to finely control when connections and connection groups are available. The changes will add the top two options in the following screenshot:

Error messages will be similar to those thrown when the connection is restricted using the other (existing) options.

Mind posting a screenshot demonstrating what this woud look like?

Mind posting a screenshot demonstrating what this woud look like?

Sure, I've edited the original post and added that :-).

LGTM


Project reproduction without attribution

Hi,
Just a heads up Uvacoder has used this code to add to their own profile without attribution.
I have personally blocked this account for doing the same thing to several of my own projects.
This account and a couple of similar ones are doing this to many projects on GitHub.
I have reported this behaviour but nothing seems to have come from it.

This account and a couple of similar ones are doing this to many projects on GitHub.

You should see the spooky clones of my old Gatsby blog still making the rounds. 👻
Seriously though, this project is meant for others to do with as they please so fine by me.
Also, not entirely without attribution from @Uvacoder though a bit oddly placed. 😄


Historial data widget theming

When using a darker theme with the historical data widget, it's hard to see the axis / label due to the default "black/dark grey" colour used by the widget

This PR changes legend and axis colours to match the line colour so that the legend/axis can actually be read on dark themes/night mode

Particularly relevant on tablets in high brightness with dim screens
Closes #129

@mxtommy / @godind I'm not massively familiar with angular, so there may be better ways to trigger this, but seemed like a reasonable way to improve the theming on the historical widget. I use the default modern dark theme and found on bright days it was almost impossible to read the axis with the default dark grey axis lines

Hi @VibroAxe   Not sure how else to reach out.I need help beta testing the latest Kip Master branch code. Can you help?
This release will have major changes and I need support testing before releasing. Could you run the latest Master and see how it goes in general?
Thanks

Hey @godind I can, but not for a week or two. Boat currently doesn't have internet so I can't access remotely. What are the changes?

If you were using 1.3, the biggest v2 change is the introduction of shared configuration. It moves all Kip config data from the browser local storage to the SK server storage, with the exception of the connection information that stays local. Kip now has the ability to authenticate as a user on the SK server on startup and automatically retrieve the lastedt Kip config before loading the app. This enables you to share Kip config with any device as long as you use the same SK credentials. It's a thing that annoyed me for a longtime.
Prior, every time you switched browser or device, you had to rebuild your page layout, widgets general settings, etc. In many case a long process, and that, just to use your phone or tablet. If you changed something on your Pi later, you had to redo everywhere. That problem is gone.
It's a breaking change and pre-v2 configuration will be deleted for all users upgrading.
Obviously it's also a big architectural change: a bootstrap approach and changing the internal services load order, a new server storage service, improved network service, remote config handling features, plus UI and handling of the authentication process and it's divers usecases.
I've tested as best I can but my setup is miles away from covering lots of different environments.
It also includes the removal of the SK full-doc service as the primary SK data retrieval approach in favor of the delta service for improved performance and diminished CPU load. Plus many other small things. I'll write the changelog today with details. I hope other contributers will join the effort, but we are a small group of 7 with really just 2-3 partially active!
Your help will be very much appreciated. I'd say just fire up the app and see how the new login process works for you. There might be a few upgrade or environment issues left. Backup you old config  using v1.x from the configuration menu before, if you still need to revert to the v1 version at some point.
Enjoy the fun 😉

Here are the release notes. Do you have a better way to communicate? I can be reached at<EMAIL_ADDRESS>V 2.0.0
New features

Breaking Change - Kip configuration sharing using SignalK user key data storage feature
Support for Signal K User authentication
Kip authentication flow and UI
Race Timer widget
Ah and kWh units support. Special thanks to amirlanesman
New Storage Service
New Authentification Service
New App bootstrap Init Service

Improvements

Migration to RxJS WebSocket
Support for Signal K Delta Metadata updates
Retirement of full.service in favor of the Delta service for improved preformance, reduced CPU load and code simplification
Kip configuration data split into Connection and Configuration files enhancing Kip configuration sharing
Enhanced Request Service support
Enhanced Console logging for improved tracing and debugging
Various dependency upgrades
Code cleanup and documentation

Fixes

widget-numeric.component.html code typo preventing proper theme rendering. Special thanks to mhaberler
Issue where simple linear gauge assumes min value=0. Special thanks to amirlanesman


Head & Wrist Receiver not work

test with OSCQueryExplorer-0.0.6.zip:
Head & Wrist Receiver not work. (three cubes locate at 0.0.0, on the ground at the same place). no timestamp shows.
Tancker-sender can work.
Anyone can resolve this issue?

I use quest3, and Vrc runs on it.
I read tips below:
To do this, your application should advertise its OSC and OSCQuery services, and the address tree it serves from OSCQuery should contain a path that matches something VRChat can send. Right now, that is:
/avatar - will receive /avatar/change as well as /avatar/parameter/* messages.
/tracking/vrsystem - will receive /tracking/vrsystem/head, /tracking/vrsystem/leftwrist, /tracking/vrsystem/rightwrist and /tracking/vrsystem/pose messages, after a user accepts an additional legal notice in VRChat.
what does it mean by the address tree? should I configure it somewhere?
Now when I open OSCQueryExplorer by Head & Wrist Receiver. There is nothing happen on quest3. ni HUD

what I'm using is quest3. VRchat works quest3. OSCQuery  works on win10.
in my browser, <IP_ADDRESS>:port can show json, but localost:port can not.


Add issues template

I would like to add a issues template in this repository. I believe that having a standardised template will help streamline the contribution process, ensuring that all necessary information is included and making it easier for maintainers to review issues.
Could you please assign this issue to me under GSSOC'24.

Please assign this issue to me under GSSOC'24


chore: changed npm with pnpm

I saw some pnpm commands on scripts and I thought it would make sense to install packages using pnpm as well

yeah, I think pnpm is superior to npm, though that's not saying much; I started with pnpm but removed it when I was getting unrelated problems. Switching back to pnpm makes sense

rebased to current master


[Feature Request] RTL Language Support

Description
Unlike English and others, some languages are written from Right-To-Left (RTL), which can sometimes be challenging when translating.
On the main page, I noticed that it translated to my language which is in Hebrew but instead of putting the '...' after the sentence, it put it before.
I will now add a little adjustment that will include some of the RTL languages that were mentioned in #101.
Feel free to fix or add more in the future to support your own language.
Possible Solution:
Create an array that will hold the wanted RTL language codes in such a way that it is easy to concatenate.
in \src\Components\MasonryLayout\MasonryBox\MasonryBox.jsx line 48' .
 const RTL_LANGUAGES = ["ar", "he", "az", "dv", "ku", "fa", "ur"];
  const BIDText = (

      {RTL_LANGUAGES.includes(languages[ipObj.ipInfo?.country_code]) ?

 ...{t("BEFORE-I-DIE")}
 :

 {t("BEFORE-I-DIE")}...

      }

  );

Screenshots
Before changes:

After changes:

Checklist

[X] I have checked for duplicate issues
[X] I have read the Contribution Guidelines
[X] I am willing to work on this issue (optional)

@zigelnik Great job on the detailed and well-organized write-up about the open issue! The solution of using an array to hold RTL languages is a great UI fix that will benefit speakers of these languages. Thank you, Tal, for your contribution. Please proceed with creating a pull request✅
I have a quick question, were the screenshots taken from your local server during development? I noticed that the map is not displayed under your name, and I just wanted to confirm if that is the case. As the code is using the Google Maps API and at first look at your screenshots this would be my guess as to why you are not able to see the contributor location on the map if it is in your local dev server.

@zigelnik Great job on the detailed and well-organized write-up about the open issue! The solution of using an array to hold RTL languages is a great UI fix that will benefit speakers of these languages. Thank you, Tal, for your contribution. Please proceed with creating a pull request✅
I have a quick question, were the screenshots taken from your local server during development? I noticed that the map is not displayed under your name, and I just wanted to confirm if that is the case. As the code is using the Google Maps API and at first look at your screenshots this would be my guess as to why you are not able to see the contributor location on the map if it is in your local dev server.

Thanks again.
Yes, you are right. I did take those screenshots while running my local server run. Sharp eyes you have there.
I will now create a pull request and refer it to here. #154

@zigelnik Great job on the detailed and well-organized write-up about the open issue! The solution of using an array to hold RTL languages is a great UI fix that will benefit speakers of these languages. Thank you, Tal, for your contribution. Please proceed with creating a pull request✅
I have a quick question, were the screenshots taken from your local server during development? I noticed that the map is not displayed under your name, and I just wanted to confirm if that is the case. As the code is using the Google Maps API and at first look at your screenshots this would be my guess as to why you are not able to see the contributor location on the map if it is in your local dev server.

Thanks again. Yes, you are right. I did take those screenshots while running my local server run. Sharp eyes you have there. I will now create a pull request and refer it to here. #154

Good to know, as I'm still always seeing what is the best way to develop and collaborate when we need to work on a feature that is using the API keys, and wanted to double-check 😉. This issue has been successfully closed from pull request #154. Thank you, Tal!


Close and destroy databases being left open during tests

There were several tests in the Database suites that were failing to
close test Databases that had orderedChunkCaches in them (backed by
levelDBs). Close them.
I was ALSO failing to destroy the cache used in LocalDatabase
instances only while testing Pull(). That's cleared up now as well.

PTAL
This seems to have cleared up the issues when I run the tests locally

Diff Coverage
File Path

•••••••••• 100%
go/datas/local_database.go

•••••••••• 100%
go/datas/local_batch_store.go

Powered by Codecov. Last update 12ddb66...23e8f09


Escape +, - and | at beginning of a line

Sometimes a line in a code block needs to start with a +, - or | but right now that's not possible without triggering the "line highlighting".
Example here: https://www.prisma.io/docs/more/style-guide/mdx-examples#tabbed-blocks

Potential solutions:

Escape special character e.g. with \ (but what if the file needs to start with \+? 😅 )
Additional option to configure line highlights via props of MDX component if necessary

Solution: pass selected lines as annotation on a code block:
```js{4,7-11;edit | 5,13;add}
const typeDefs = `
  type Query {
    info: String!
    feed: [Link!]!
  }

  type Link {
    id: ID!
    description: String!
    url: String!
  }
`
```


Reference: Installation directory layout

Documents the layout of the installed directory hierarchy

I think it would also be great to link back here from the command line options reference that talks about installed directories.


fix grammar error

it is not very important,but I think the modification makes the coders read more conviently！
Signed-off-by: huqun<EMAIL_ADDRESS>

Job: Docker-PRs-WoW-TP4 FAILED:

---
	      56	docker-1.11.0-dev.exe.md5
  0%
100%
	    New File  		      88	docker-1.11.0-dev.exe.sha256
  0%
100%
	    New File  		  27.1 m	docker.exe
  0.0%
  3.6%
  7.3%
 11.0%
 14.7%
 18.3%
 22.0%
 25.7%
 29.4%
 33.0%
 36.7%
 40.4%
 44.1%
 47.8%
 51.4%
 55.1%
 58.8%
 62.5%
 66.1%
 69.8%
 73.5%
 77.2%
 80.8%
 84.5%
 88.2%
 91.9%
 95.6%
 99.2%
100%

------------------------------------------------------------------------------

               Total    Copied   Skipped  Mismatch    FAILED    Extras
    Dirs :         1         0         1         0         0         0
   Files :         4         4         0         0         0         0
   Bytes :   54.39 m   54.39 m         0         0         0         0
   Times :   0:00:00   0:00:00                       0:00:00   0:00:00

   Speed :<PHONE_NUMBER> Bytes/sec.
   Speed :            60434.599 MegaBytes/min.
   Ended : Friday, February 12, 2016 8:14:07 AM

+ ec=0
+ set +x
INFO: Linking the built binary to /d/CI/CI-f609f
---

LGTM


Support chunkwm

Description
I'd like to see support for chunkwm. At the moment, neofetch appears to identify chunkwm as the deprecated kwm.
It also detects my terminal (alacritty) as "launchd," but that's a separate issue.
$ brew services list`

Name       Status  User Plist
pulseaudio started Will /Users/Will/Library/LaunchAgents/homebrew.mxcl.pulseaudio.plist
chunkwm    started Will /Users/Will/Library/LaunchAgents/homebrew.mxcl.chunkwm.plist
dbus       stopped
skhd       started Will /Users/Will/Library/LaunchAgents/homebrew.mxcl.skhd.plist
mpd        started root /Library/LaunchDaemons/homebrew.mxcl.mpd.plist
mysql      stopped

Neofetch version
NeoFetch 3.3.0
Installed via homebrew:
Poured from bottle on 2017-09-25 at 11:26:23
Screenshot

Verbose log
https://gist.github.com/LEARAX/e85cc44a6f57b70964b038ee94f26bbd#file-neofetchlog-txt-L715

I just saw this commit. When will it be released?

When I get time to make a new release. It takes me a good 2-3 hours to release a new version and make sure things go smoothly.
I’ve got a break from university coming up so I’ll probably make a release then.


Reference customer workload

This adds an example customer workload which includes:

amq-broker (AMQP + MQTT), volatile, no volumes or storage yet.
app-api
app-core
app-web
app-plugin1 restricted to talk only to app-api:8080

Which issue(s) this PR addresses:

Closes #

/lgtm

USHIFT-75


drawerBackgroundColor is not working

I want to change background color of drawer. I've included new prop that you added on the documentation but it doesn't work. The version of react-navigation is  react-navigation": "1.0.0-beta.12
const Drawer = DrawerNavigator(
  {
    Home: {screen: HomeScreen},
    Profile: {screen: ProfileScreen},
    Settings: {screen: SettingsScreen},
  },
  {
    initialRouteName: "Home",
    drawerPosition: "left",
    drawerBackgroundColor:"#222222",
    disableOpenGesture: true,
    contentComponent: props => <DrawerContent {...props} />,
    contentOptions: {
      inactiveTintColor: "#0dc45c",
      activeBackgroundColor: "#383834",
      activeTintColor: "#0dc45c",
       },

  },
);

How can I fix this?
Please also make your documentation a bit more detailed if possible.

Hi @ArtyomBaykov! It looks like this is not a bug of the library nor a feature request, so I'll close it: I suggest next time you use Stack Overflow which is better suited for answering these types of questions. I also encourage you to join the Reactiflux community on Discord. There are React Native and React Navigation channels with helpful people who might be able to answer your question. I would also like to mention that there is a collection of helpful links and tutorials for React Navigation in the README which might be helpful for you.
That said:

you are expecting a feature added in v1.0.0-beta.14 to work in v1.0.0-beta.12
you haven't followed the issue template
if you don't think the documentation is good enough, feel free to open a PR to improve it

If you believe that you are experiencing a bug or have a feature request, please open a new Issue following the dedicated template or submit a PR.

Hey did you manage to fix this? I am having trouble making my drawer menu have a transparent bg. I am using a custom drawer
{
contentComponent: CustomDrawer,
drawerBackgroundColor: 'black',
}
My email is<EMAIL_ADDRESS>@tuananh11594 @ArtyomBaykov


'Methods' keyword not translated

In the spell palette view, the headers' names aren't translated.
For example, the keyword 'Methods':

Well, you can do it by your self: go to the forum but not github.
I think so anyway.


[ZEPPELIN-4619] Run a note from the commandline

What is this PR for?
This PR adds a command-line option to run a single note.
The code is pickled from https://github.com/apache/zeppelin/pull/3356.
Usage is
bin/zeppelin.sh --run <noteId>

The command will launch a Zeppelin server and run a given note, and terminate on after all paragraph's successful run (with exit 0) or terminate on any paragraph error (with exit 1).
What type of PR is it?
Feature
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-4619
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

Thanks @Leemoonsoo LGTM

I removed a useless test. Thanks, @zjffdu for the review. I'll merge to master.


MA Server - Linkplay based audio renderer - Progress bar

What version of Music Assistant has the issue?
ghcr.io/music-assistant/server:38af96a5
The problem
I have several DLNA audio renderers from different models and manufacturers sharing a chipset from LinkPlay.
These are well recognized from MA server but when playing from web interface actual playback position is showing non sense values.  i.e. total track time 04:14  playing time 07:12 !
More precisely pressing pause stop actual playing time display but it looks like the counter keeps running in the background...  I believe this is also the main reason why a queue is not played. It plays only one element then stops...
How to reproduce
Allways
Relevant log output
I settled DLNA provider to DEBUG but don't see any relevant information...
2023-06-13 15:32:51,030 INFO  music_assistant.providers.dlna  -- Player does not support next uri
2023-06-13 15:32:51,030 DEBUG music_assistant.providers.dlna  -- Enqued next track (Prince - Darling Nikki) to player Office DLNA
2023-06-13 15:32:52,381 DEBUG music_assistant.providers.dlna  -- Received event for Player Office DLNA: <UpnpService(urn:upnp-org:serviceId:AVTransport, uuid:FF310001-A06C-C39B-FFFC-81C3FF310001)>
2023-06-13 15:32:52,383 DEBUG music_assistant.providers.dlna  -- Received event for Player Office DLNA: <UpnpService(urn:upnp-org:serviceId:AVTransport, uuid:FF310001-A06C-C39B-FFFC-81C3FF310001)>
2023-06-13 15:36:36,838 DEBUG music_assistant.providers.dlna  -- Received event for Player Office DLNA: <UpnpService(urn:upnp-org:serviceId:AVTransport, uuid:FF310001-A06C-C39B-FFFC-81C3FF310001)>
2023-06-13 15:36:36,838 DEBUG music_assistant.providers.dlna  -- Received event for Player Office DLNA: <UpnpService(urn:upnp-org:serviceId:AVTransport, uuid:FF310001-A06C-C39B-FFFC-81C3FF310001)>
Additional information
No response
What version of Home Assistant Core are your running
Not relevant
What type of installation are you running?
Home Assistant Container
On what type of hardware are you running?
Linux

@Sonusss were you able to make progress with Marcels suggestion?

Well, It works barely with DLNA in flow mode but indeed it's flaky.  Actually I installed MA server on my laptop (Ubuntu) for testing.
I bought a new storage for my pi4 and will shortly give a non-destructive try to 64bits... In the  meantime I bought also a https://raspiaudio.com/produit/mncast for testing. Native Linkplay integration with multiroom would  be a plus as I still have 3 players... And finally, I got addicted to MA, you made a great job and I will make everything possible to make it work for me !  THANK YOU ALL

Latest news: I finally got all working on 64bits OS on my pi4.  Just waiting now for native Linkplay integration. My renderers are worst in Airplay mode than DLNA. There is already a Linkplay integration in HA but don't know if it helps...
https://github.com/nagyrobi/home-assistant-custom-components-linkplay

I think I will close this as the original issue appears resolved. Linkplay support is an enhancement that you can upvote here  https://github.com/orgs/music-assistant/discussions/1200#discussioncomment-5658820


Some updates for building new containers

A couple changes I found useful for building a new docker image.

Since the work to move everything to java 8,a newly-built docker image barfs unless this is upgraded to Java 89
The new image pulls in thrift 0.10.0, which breaks things... similar to this problem in pycassa.  So, downgrading thrift to 0.9.3 is necessary.
I think that 'ROLLUP_KEYSPACE' conditional only worked by totally not working.  Fixed it to make sense and actually work.

Changes Unknown when pulling ff1343f770e4aa3e1f237cb72717c3ccb5d091b2 on stackedsax:stackedsax/dockerfile_updates into ** on rackerlabs:master**.


Cant create a project

when i write ng new test
it give details in the terminal but don't create the project

Hi, you should give more information about your problem, angular-cli version your using, OS version & so on.

Im using the latest version of the cli , OSX El Capitan
I got all these:
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
installing ng2
create .clang-format
create .editorconfig
create src/app/gametime.component.css
create src/app/gametime.component.html
create src/app/gametime.component.spec.ts
create src/app/gametime.component.ts
create src/app/environment.ts
create src/app/index.ts
create src/app/shared/index.ts
create src/favicon.ico
create src/index.html
create src/main.ts
create src/system-config.ts
create src/tsconfig.json
create src/typings.d.ts
create angular-cli-build.js
create angular-cli.json
create config/environment.dev.ts
create config/environment.js
create config/environment.prod.ts
create config/karma-test-shim.js
create config/karma.conf.js
create config/protractor.conf.js
create e2e/app.e2e.ts
create e2e/app.po.ts
create e2e/tsconfig.json
create e2e/typings.d.ts
create .gitignore
create package.json
create public/.npmignore
create tslint.json
create typings.json
Successfully initialized git.
⠴ Installing packages for tooling via npm
├── es6-shim (ambient)
├── angular-protractor (ambient dev)
├── jasmine (ambient dev)
└── selenium-webdriver (ambient dev)
Installed packages for tooling via npm.
And nothing is created

Everything looks fine to me, maybe, just maybe, inside your terminal, you're not in the location you think you are so the project does get generated but not where you expect it to be. Could you check that?
This happens to me sometimes, when I navigate away from the directory I usually scaffold my projects into, or am inside one of the projects... I forget that my terminal isn't pointing where it should and I'm left scratching my head for a second. :)

No im in the location

@nicolaselmir so you have folder test Inside of which there is nothing?

Try another name. I got something similar:
E:\projects\test>ng init
We currently do not support a name of `test`.

Yes, I run into the same issue. "test" is some kind of reserved name and doesn't work. All other names should work. It's a bit unfortunate as apparently many new users try out naming their first project to play with CLI 'test'...

Just tried a ng new myproject after having updated to 1.0.0-beta.5 and it errored with this message :
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
Cannot find module 'config-chain'
Error: Cannot find module 'config-chain'
    at Function.Module._resolveFilename (module.js:326:15)
    at Function.Module._load (module.js:277:25)
    at Module.require (module.js:354:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/opt/node/5.4.0/lib/node_modules/angular-cli/node_modules/npm/lib/config/core.js:2:10)
    at Module._compile (module.js:398:26)
    at Object.Module._extensions..js (module.js:405:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Module.require (module.js:354:17)

This is the result of ng version :
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
angular-cli: 1.0.0-beta.5
node: 5.4.0
os: linux x64

Any idea ?

Ok just a case of updating with an already global install of angular-cli. Uninstall then reinstall is the key :)

Considering this fixed.

jesse:test jesse$ ng new test
Project name "test" is not a supported name.

I don't get it, why am I not allowed to create a project called test?

I think is just a name convention like when a password should have more than 6 characters.
I couldn't create a project called "app" so i had to use "apptesting" and then i renamed the folder project to "app"

can we reopen this issue?


Fix NIFI-3142: ExtractHL7Attribute processor: Route a flowfile to REL_FAILURE if processing the flow…

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[n/a] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[n/a] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[n/a] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[n/a] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[n/a] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
… file throws an exception that is not an HL7Exception for the ExtractHL7Attribute processor.
Fixed by changing the catch block to catch a throwable object instead of an HL7Exception object in the onTrigger method.

@klinvill
Is this PR still needed or was it identified as a data quality issue?

@klinvill Do you know what version of NiFi you were running against? The NumberFormatException error was fixed in 1.1.0 by NIFI-2887 and a relevant segment added to the unit tests. NIFI-3142 suggests you ran into this against 1.0.0, and given the time you reported it at NiFi 1.1.0 had only been out for a short time so I wouldn't be surprised if you hadn't upgraded yet. Is this right? As for the NPE, I'll see if I can reproduce it but I don't know if I exactly follow the scenario. Is it an unrecognized segment name as in it's just bad HL7 or a segment that's unsupported for a particular version?

@jfrazee Apologies for the delayed response. I was running it against NiFi 1.0.0. The client I was working for at the time was using a few non-standard HL7 messages that were resulting in exceptions. The exceptions weren't really the problem (the failed messages just require specialized processing). The real problem was that the exceptions thrown were not HL7Exceptions so the NiFi processor didn't know where to route the message and the flowfile stayed in the queue to be processed at a later time. We were handling a large volume of these messages so the processor quickly got overloaded with the flowfile backlog. We ended up fixing this locally by simply routing all exceptions to failure so that the flowfiles would be moved out of the queue. I understand @mattyb149's point about how catching all exceptions could lead to data loss. Unfortunately I no longer have access to the messages or workflows that are failing so I'll go ahead and close this request. Thank you all for the help, if I run into this situation again I'll add in additional business logic and submit it back as a pull request.


fix gated build due to protobuf dependency error

Fix the gated build in interpret-community repository failing due to latest protobuf being incompatible with the version of tensorflow<2.5 used in interpret-community tests.  We pin to protobuf<4 to resolve the issue.

Codecov Report

Merging #524 (5b075eb) into master (9b765da) will decrease coverage by 0.29%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #524      +/-   ##
==========================================
- Coverage   86.70%   86.41%   -0.30%
==========================================
  Files          62       62
  Lines        4063     3976      -87
==========================================
- Hits         3523     3436      -87
  Misses        540      540

Flag
Coverage Δ

unittests
86.41% <ø> (-0.30%)
:arrow_down:

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

Impacted Files
Coverage Δ

...erpret_community/mimic/models/explainable_model.py
81.57% <0.00%> (-3.21%)
:arrow_down:

...ython/interpret_community/common/base_explainer.py
86.95% <0.00%> (-1.05%)
:arrow_down:

...mmunity/_internal/raw_explain/data_mapper_utils.py
80.85% <0.00%> (-0.79%)
:arrow_down:

...hon/interpret_community/explanation/explanation.py
84.94% <0.00%> (-0.76%)
:arrow_down:

...n/interpret_community/shap/gpu_kernel_explainer.py
22.55% <0.00%> (-0.58%)
:arrow_down:

...hon/interpret_community/mimic/models/tree_model.py
90.90% <0.00%> (-0.48%)
:arrow_down:

...interpret_community/mimic/models/lightgbm_model.py
85.63% <0.00%> (-0.33%)
:arrow_down:

python/interpret_community/common/aggregate.py
90.32% <0.00%> (-0.31%)
:arrow_down:

...n/interpret_community/mimic/models/linear_model.py
93.50% <0.00%> (-0.16%)
:arrow_down:

...community/_internal/raw_explain/feature_mappers.py
95.72% <0.00%> (-0.15%)
:arrow_down:

... and 13 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 9b765da...5b075eb. Read the comment docs.


Update get_target_distribution_upload.m

Remove the content of conditional intensity measure to build the correlation matrix which is only used for the algorithm of nearest positive definiteness matrix.

Remove the content of conditional intensity measure for the application of nearest positive definiteness matrix.


Bump versions and add documentation.

Codecov Report

Merging #77 (698c3cd) into master (42bbbcc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #77   +/-   ##
=======================================
  Coverage   96.78%   96.78%
=======================================
  Files          20       20
  Lines        4070     4070
=======================================
  Hits         3939     3939
  Misses        131      131

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 42bbbcc...698c3cd. Read the comment docs.


The action "SWS: Undo edit cursor move" occasionally fails to respond

I have been observing this situation for a long time, but unfortunately, until now, I have not found a way to reproduce it 100%. I can only report this situation first, to see if you can find out where the problem is, and update the situation in the future if a reproducible method can be found.

The cursor position is checked once per defer cycle. Any moves in-between cycles would not be noticed. Maybe that's what you're observing?

I mean this action seems to have a "cursor movement history", running it will go back to the position in the history in reverse order, but under some specific conditions, this record will be cleared, in this case running this action will have no response at all.

There's one cursor stack per project and it should be cleared only when the project is closed. It checks for dangling stacks belonging to closed project when loading projects and on undo. Let me know if you find steps to duplicate anything strange.


Document running specs on s390x CPU architecture [ci skip]

This PR fixes #1083, and an a rework for https://github.com/ruby/spec/pull/1084#issuecomment-1739243422.
What do you think? Could you review? You can check the modified README here. Thank you.

Thanks for your review!


Update request: universal-android-debloater 0.6.2 → 1.0.2

Package name: universal-android-debloater
Latest released version: 1.0.2

Current version on the unstable channel: 0.6.2
Current version on the stable/release channel: None

[x] Checked the nixpkgs pull requests

Notify maintainers
@KamilaBorowska

Note for maintainers: Please tag this issue in your PR.
The app had a major release update. Thank you!
Current version is broken due to lists format change.

Add a :+1: reaction to issues you find important.

Current version is broken due to lists format change.
care to elab?


Add lsward command

This replaces the personslist column with a list of wards when lsward is used. Any other command replaces it with personlist. Still a little buggy. Patient count and Staff count does not update immediately.

Just to check, what happens if index based command (eg delete 1) is called when displayed list is wards?

I see, good that behaviour is still defined. Brought it up because I thought it might be confusing/interpreted as a bug when index 1 on screen shows a ward but when you delete 1 it deletes a person silently. Might be good to mention this in UG

Maybe it might be better to make it as Jin suggested to always have 3 columns? Or maybe we make it such that when we lsward, we make the predicate of filteredpersonslist always false so that filteredpersonslist is empty and all index commands do not work until you list the persons again.


Requirements for the project

Please review..

Please also make the setup file able to read requirement.txt and also remove the inbuilt dependencies of python.


Update Tutorial to use Hooks instead of class components

I think the react docs are a fantastic place for people to start getting into React. Seems like hooks are where we want people to learn React so it makes sense to update the tutorial to use hooks instead.
Let me know what you think. I'm sure we'd get a lot of people willing to contribute this.

I’d love to help out! 👋 we probably need to figure out how to rewrite stuff though - it might lead to a few new sections and a few deleted ones

Would love to help too!

I'm definitely interested to help! 😄
I've actually recreated the Tic Tac Toe tutorial using hooks.
Solution 1
In this solution, I've followed the original tutorial step-by-step, and tried to keep it as identical as possible.
Here is the CodePen for the final result
Following are the pens for all the code check points as provided in the tutorial:

Tic Tac Toe - Hooks - Starter
Tic Tac Toe - Hooks - Point 1 (Passing Props)
Tic Tac Toe - Hooks - Point 2 (Interactive Component)
Tic Tac Toe - Hooks - Point 3A (Lifting State Up)
Tic Tac Toe - Hooks - Point 3B (Lifting State Up)
Tic Tac Toe - Hooks - Point 4 (Taking Turns)
Tic Tac Toe - Hooks - Point 5 (Declaring a Winner)
Tic Tac Toe - Hooks - Point 6A (Adding Time Travel)
Tic Tac Toe - Hooks - Point 6B (Adding Time Travel)
Tic Tac Toe - Hooks - Point 6C (Adding Time Travel)

Solution 2
In this video, featuring @gaearon and Mattias Petter Johansson, Dan mentioned that the original tutorial had the logic of the application and history intertwined together, and that it would be interesting to create a custom hook and use reducers to separate them out. So, I've given it a shot - it was actually very interesting 😄
I think this approach might be interesting to add as a bonus/advanced section to the tutorial to demonstrate what is possible using custom hooks.
Here is a CodePen for the final result using a custom hook for history
I think the main consideration would be to change the code to using declared functions instead of arrow functions.
I would be very interested to get feedback on the code, and will also gladly help with the documentation as well if you would like to proceed with this.
Thanks!

@abdusabri I'm not super familiar with the tutorial as I preferred to learn React via its docs, but as far as I can tell from the final step, this looks like a very solid translation of the original class logic to hooks. My only complains are ones I'd also have of the original.

Thanks for the feedback @nickmccurdy!
How should we proceed with this? Should i start working on the documentation? Do you know someone from the core team who should be mentioned here?

I started working on the docs (see #1788) but don't have a pull request yet, hopefully will soonish.

@nickmccurdy, thanks for working on the docs. The documentation I wanted to start working on is for the tutorial only. Basically, the write up and steps that would go along with the code I've provided. Docs for this issue and #1788 would be complimentary to each other, correct?

Yea, I think so. Personally I'm more familiar with the docs than tutorial, but this seems like a good approach for users that prefer the tutorial, as they are both alternative ways for new users to learn React.

Linking this to https://github.com/reactjs/reactjs.org/pull/3063 from @DaniAkash which contains an updated tutorial using hooks


🐛 useHookAtTopLevel doesn't report hooks used outside of non-hook functions

Environment information
CLI:
  Version:                      1.5.3
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           windows

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         unset
  JS_RUNTIME_VERSION:           "v21.6.2"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "pnpm/8.15.1"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           true
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 false

Workspace:
  Open Documents:               0

What happened?
In this code:
function notAhook() {
	useSomeHook()
}

useHookAtTopLevel does not show an error for useSomeHook not being used inside a component-named or hook-named function.
Playground link
Expected result
useHookAtTopLevel should show an error for useSomeHook not being used inside a component-named or hook-named function.
References:

https://react.dev/learn/state-a-components-memory#meet-your-first-hook
https://legacy.reactjs.org/docs/hooks-rules.html#only-call-hooks-from-react-functions

Code of Conduct

[X] I agree to follow Biome's Code of Conduct

I’m not entirely sure how to fix this, since we don’t want to show diagnostics when a hook is called from inside a test function, for instance. Do you know how the ESLint plugin handles this?

we don’t want to show diagnostics when a hook is called from inside a test function

Sorry, I'm not sure what you mean by this. Can you show an example? I'm imagining something like this:
test("something", () => {
	const value = useWhatever()
})

...which isn't valid anyways 🤔

You’re pretty close :)
For instance:

import { renderHook } from '@testing-library/react';
import useCustomHook from './useCustomHook';

test('should do something', () => {
  const { result } = renderHook(() => useCustomHook());

  // Assertions based on the hook's return value
  expect(result.current.someValue).toBe(/* expected value */);
});

Alright, that's very curious 🤔  The rule seems to just ignore unnamed callbacks passed to other functions

I don't know if I like this heuristic. Off the top of my head, I feel like it'd be more sensible to search specifically for functions named test, it, and describe and maybe allow configuring others.

Somewhat related to the above, they're apparently planning on letting you call use inside of useMemo

I don't know if I like this heuristic. Off the top of my head, I feel like it'd be more sensible to search specifically for functions named test, it, and describe and maybe allow configuring others.

I'm a bit split on this one as well. I would appreciate it if we didn't need additional config for this; it doesn't feel intuitive if this required configuration. But I also agree the heuristic leaves something to be desired.
Meanwhile, I do think we catch hook usages inside anonymous functions that are inside other hooks or component functions. So maybe the heuristic is acceptable if it only applies to top-level anonymous functions?


Revert "Fix broken links at plugins documentation"

This reverts commit 354147df012dd35f82e59e3511d9be4fc7610352 (PR #15787)
There is a known problem between the links for documentation created with make build and documentation in github (Check #15546)

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "broken-links-revert" git@github.com:agonzalezro/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

cc: @calavera  & @thaJeztah

LGTM, thanks!


Feature request: procfs TotalFileDescriptorsLen

Often times when debugging for a fd leak - it is not clear which process is the root cause of such leak and having the exact count instance wide would be really helpful.
The implementation can be done fairly straight-forwardly using fs.AllProcs() and proc.FileDescriptorsLen() that looks something like below in https://github.com/prometheus/procfs/blob/ff0ad85f7e8bcd5c677d99143f14a2a3aab533aa/proc.go#L245:
ps, err := fs.AllProcs() // this is a list of processes

sum = 0

for _, process := range ps {

c, err := process.FileDescriptorsLen()

sum += c
}

Can implement it if procfs team thinks it's worthwhile to be part of the project

This can already be accomplished with process-exporter: https://github.com/ncabatoff/process-exporter#open_filedesc-gauge

@dswarbrick For sure. Is it reasonable to consider that an additional data point for incorporating such feature into procfs itself?

Seems trivial enough to implement in the caller, don't feel like we need to implement that here

ACK, in that case, I think this can be closed now.


[Language Text] Remove phase control

After it has been removed from the swagger.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-language-text


Updated README.md with badges and index

I have added specified badges in issue #31

Added Bundlephobia badge for minified package size
Added Bundlephobia gziped package size

Added few more relevant badges - Forks, Stars, Issues

Contributed to  Better documentation in the Readme #26

Created Index section in README.md for better accessibility.
Added proper anchor tags, so that user can click on title from index and directly jump to preferred section.

Please assign me this sir.


clarify what true looks like in output

Is your feature request related to a problem? Please describe.
DBeaver display of boolean is slightly confusing.
Describe the solution you'd like
If I have a boolean column, I'd like it more obvious.
ex: postgres
select true;

It shows a [v] for the output pane.
A "v"?  What type is that?  What am I seeing?
Suggestion/feature request for UI:
[true] and [false] or possibly show a "real-er" checkmark...
Cheers!

This feature does exist, but you have to dig through the preferences a bit.
Click on the "Window" menu and choose "Preferences". Navigate to the editors section, and there is a section to set how Booleans display. Screenshot attached for reference.

That's interesting, mine on OS X just shows up as a "v" like [v]" like...what does v stand for? :)

And you can change it in the Preferences.


deprecation warnings

TASK [geerlingguy.jenkins : Wait for Jenkins to start up before proceeding.] ***
[DEPRECATION WARNING]: always_run is deprecated. Use check_mode = no instead..
This feature will be removed in version 2.4. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
ok: []
[WARNING]: Consider using get_url or uri module rather than running curl
TASK [geerlingguy.jenkins : Get the jenkins-cli jarfile from the Jenkins server.] ***
[DEPRECATION WARNING]: always_run is deprecated. Use check_mode = no instead..
This feature will be removed in version 2.4. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.
ok: []

@acaudle - Sorry to close this quickly, but basically I purposely am keeping always_run until Ansible 2.3 is released. Ansible 2.2 introduced the new check_mode module, and I don't want to break compatibility with everyone using Ansible 2.0 and 2.1 just because there's a new variable... so I'm waiting to make the change so people have more time to upgrade.


Make the insides of AllocationHandle private

Let's stay conservative, to for example allow adding more fields to it (in particular consider a thicc pointer) or turn it into a union (e.g. if the need for storing a DeviceSize ever arises).

Curious why you made AllocationHandle transparent except in documentation?


big image (68 megapixels) does not display entirely

🐛 Bug

I am trying to display a very large image (6898 x 9946 pixels), but only the part of it is displayed: the bottom part is black. If I display only a part of the image, everything works fine. From my experience, problems start to occur from image size > ~55 megapixels.
To Reproduce
This is the code to reproduce the issue with a random image:
img = np.random.randint(0, 100, size=(6898, 9946))
with napari.gui_qt():
...:     v = napari.view_image(img)
This is the result that I get:

Displaying the first 8000 pixels in x gives the result that I expect:
with napari.gui_qt():
...:     v = napari.view_image(img[:,:8000])

The problem starts to occur starting from the x-size of ~8200 pixels
Environment
napari: 0.2.12
Platform: Linux-3.10.0-1062.4.3.el7.x86_64-x86_64-with-redhat-7.7-Maipo
Python: 3.7.6 (default, Jan 8 2020, 19:59:22) [GCC 7.3.0]
Qt: 5.14.1
PySide2: 5.14.1
VisPy: 0.6.4
NumPy: 1.18.1
SciPy: 1.4.1
scikit-image: 0.16.2
Dask: 2.12.0
GL version: 4.6.0 NVIDIA 440.31
MAX_TEXTURE_SIZE: 32768

Hi @amedyukhina, sorry that you're running into this problem and thanks for reporting it. This is actually the same problem as reported in #458 that we still havn't fixed yet, but will hopefully get to soon as it is coming up a lot for people.
What's happening now is that we have a size threshold (8095) above which we're actually automatically generating an image pyramid under the hood to avoid passing too big images to your graphics card. We've actually probably been too conservative here and are planning to improve this behavior (see #736 for a summary of these issues).
For now, I'm curious if you pass is_pyramid=False to view_image if that might help.
Otherwise as I'll start work on a fix soon - @jni I will get to this during the world coordinates work after #1042 merges, either during the first PR or in a followup

Passing is_pyramid=False solves the issue. Thanks for your quick response!

Passing is_pyramid=False solves the issue. Thanks for your quick response!

Ok good to know, thanks for the quick test and response too. It's a bit of a bandaid unfortunately. I'm going to leave this issue open for now and will close once we have a solution that doesn't require passing another keyword argument


playlist error 504 / Unhandled promise rejection

Since Update 1.2.1 my spotify-premium adapter keeps restarting with the error shown in the loogfiles down below. On the same day i updated js and node.
I already deleted the instance and re-added it - no success.
I then tried to remove all special characters like äöü oder unerlines etc., re-added again with no success.
`host.raspberrypi
2022-09-04 09:49:52.526	error	instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.raspberrypi
2022-09-04 09:49:52.526	error	Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
host.raspberrypi
2022-09-04 09:49:52.526	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:925:52
host.raspberrypi
2022-09-04 09:49:52.526	error	Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'trackIds')
host.raspberrypi
2022-09-04 09:49:52.525	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
spotify-premium.0
2022-09-04 09:49:51.854	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
spotify-premium.0
2022-09-04 09:49:51.852	info	terminating
spotify-premium.0
2022-09-04 09:49:51.782	error	Cannot read properties of undefined (reading 'trackIds')
spotify-premium.0
2022-09-04 09:49:51.781	error	TypeError: Cannot read properties of undefined (reading 'trackIds') at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:925:52 at processTicksAndRejections (node:internal/process/task_queues:96:5)
spotify-premium.0
2022-09-04 09:49:51.780	error	unhandled promise rejection: Cannot read properties of undefined (reading 'trackIds')
spotify-premium.0
2022-09-04 09:49:51.780	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
spotify-premium.0
2022-09-04 09:49:51.777	warn	error on load tracks(getPlaylistTracks): 504 owner: zät id: 4PXQ3juDvehA6KFeh71blF
spotify-premium.0
2022-09-04 09:49:51.777	warn	Error: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:360:38 at processTicksAndRejections (node:internal/process/task_queues:96:5)
spotify-premium.0
2022-09-04 09:49:51.776	warn	Error: at sendRequest (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:248:21) at getPlaylistTracks (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:1047:12) at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:917:25
spotify-premium.0
2022-09-04 09:49:51.775	warn	http request error not handled, please debug
spotify-premium.0
2022-09-04 09:49:49.978	error	playlist error 504
spotify-premium.0
2022-09-04 09:49:49.977	warn	Error: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:360:38 at processTicksAndRejections (node:internal/process/task_queues:96:5)
spotify-premium.0
2022-09-04 09:49:49.976	warn	Error: at sendRequest (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:248:21) at getUsersPlaylist (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:1004:16) at reloadUsersPlaylist (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:824:12) at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:196:21 at processTicksAndRejections (node:internal/process/task_queues:96:5)
spotify-premium.0
2022-09-04 09:49:49.974	warn	http request error not handled, please debug`
Versions:

Adapter version: 1.2.1
JS-Controller version: 4.0.23
Node version: 16.15.1
Operating system: Debian

Additional context
I also tried to set the playlist refresh intervall to 0 without success.
Is there any chance for me to debug the http request? Loglevel is on debug but there is not that much information.
A few days ago the adapter juzst threw the playlist error. Now it is crashing immediatly with unhandled promise exception.
Maybe i can send you my client id and secret if u want to test it out?
EDIT: I just tried the adapter version 1.2.1 on an old  Windows-iobroker instance (js 2.1.1 / node v10.17.0)  with exactly the same errors.
`

|   |   |
-- | -- | -- | --
spotify-premium.0 | 2022-09-04 10:06:21.532 | warn | (22316) error on load tracks(getPlaylistTracks): 504 owner: zät id: 4PXQ3juDvehA6KFeh71blF
spotify-premium.0 | 2022-09-04 10:06:21.532 | warn | (22316) Error at request.then.response (C:\Program Files\iobroker\iOBrokerZWindows\node_modules\iobroker.spotify-premium\main.js:360:38) at process._tickCallback (internal/process/next_tick.js
spotify-premium.0 | 2022-09-04 10:06:21.532 | warn | (22316) Error at sendRequest (C:\Program Files\iobroker\iOBrokerZWindows\node_modules\iobroker.spotify-premium\main.js:248:21) at getPlaylistTracks (C:\Program Files\iobroker\iOBrokerZWindows
spotify-premium.0 | 2022-09-04 10:06:21.532 | warn | (22316) http request error not handled, please debug

`
Thank you
Zaetti

Any news on this one? :)

same issue here

same here

sorry for asking again 🙈 any news ? :)

I also have problems with restart loops after api errors:
2022-10-23 13:11:33.660 - warn: spotify-premium.0 (401130) unexpected api response http 503; continue polling
2022-10-23 13:11:33.727 - info: spotify-premium.0 (401130) State value to set for "spotify-premium.0.player.playlist.tracksTotal" has to be type "string" but received type "number"
2022-10-23 13:11:44.149 - info: spotify-premium.0 (401130) State value to set for "spotify-premium.0.player.playlist.tracksTotal" has to be type "string" but received type "number"
2022-10-23 13:12:31.801 - info: chromecast.0 (559825) NestHub - Playing - spotify:track:2XNaKS5wO5rPdgpPYVKria
2022-10-23 13:12:31.974 - warn: spotify-premium.0 (401130) State "spotify-premium.0.playlists.spotify-37i9dQZF1EQpj7X7UK8OOF.trackList" has no existing object, this might lead to an error in future versions
2022-10-23 13:16:24.635 - info: chromecast.0 (559825) NestHub - Playing - spotify:track:3ovjw5HZZv43SxTwApooCM
2022-10-23 13:16:24.959 - warn: spotify-premium.0 (401130) State "spotify-premium.0.playlists.spotify-37i9dQZF1EQpj7X7UK8OOF.trackList" has no existing object, this might lead to an error in future versions
2022-10-23 13:18:39.667 - error: spotify-premium.0 (401130) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2022-10-23 13:18:39.668 - error: spotify-premium.0 (401130) unhandled promise rejection: undefined
2022-10-23 13:18:39.668 - error: spotify-premium.0 (401130) undefined
2022-10-23 13:18:39.675 - info: spotify-premium.0 (401130) terminating
2022-10-23 13:18:39.675 - warn: spotify-premium.0 (401130) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-10-23 13:18:39.836 - warn: spotify-premium.0 (401130) error on load tracks(getPlaylistTracks): 503 owner: spotify id: 37i9dQZF1DWX7rdRjOECPW
2022-10-23 13:18:40.227 - error: host.iobroker Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'stateString')
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[1]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), :3:12)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[1]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:937:32
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[1]: at runMicrotasks ()
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[2]: TypeError: Cannot read properties of undefined (reading 'listNumber')
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[2]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), :3:12)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[2]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[2]: at createOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:387:13)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:958:21
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[2]: at runMicrotasks ()
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[3]: TypeError: Cannot read properties of undefined (reading 'listString')
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[3]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), :3:12)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[3]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[3]: at createOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:387:13)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[3]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:961:21
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[3]: at runMicrotasks ()
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[4]: TypeError: Cannot read properties of undefined (reading 'stateString')
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[4]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), :3:12)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[4]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[4]: at createOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:387:13)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[4]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:964:21
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[4]: at runMicrotasks ()
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[5]: TypeError: Cannot read properties of undefined (reading 'trackIdMap')
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[5]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), :3:12)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[5]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[5]: at createOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:387:13)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[5]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:967:21
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[5]: at runMicrotasks ()
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[6]: TypeError: Cannot read properties of undefined (reading 'trackIds')
2022-10-23 13:18:40.228 - error: host.iobroker Caught by controller[6]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), :3:12)
2022-10-23 13:18:40.229 - error: host.iobroker Caught by controller[6]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
2022-10-23 13:18:40.229 - error: host.iobroker Caught by controller[6]: at createOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:387:13)
2022-10-23 13:18:40.229 - error: host.iobroker Caught by controller[6]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:970:21
2022-10-23 13:18:40.229 - error: host.iobroker Caught by controller[6]: at runMicrotasks ()
2022-10-23 13:18:40.229 - error: host.iobroker Caught by controller[6]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-10-23 13:18:40.229 - error: host.iobroker Caught by controller[7]: TypeError: Cannot read properties of undefined (reading 'songs')
2022-10-23 13:18:40.229 - error: host.iobroker Caught by controller[7]: at eval (eval at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:372:19), :3:12)
2022-10-23 13:18:40.229 - error: host.iobroker Caught by controller[7]: at loadOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:373:13)
2022-10-23 13:18:40.229 - error: host.iobroker Caught by controller[7]: at createOrDefault (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:387:13)
2022-10-23 13:18:40.229 - error: host.iobroker Caught by controller[7]: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:973:21
2022-10-23 13:18:40.229 - error: host.iobroker Caught by controller[7]: at runMicrotasks ()
2022-10-23 13:18:40.229 - error: host.iobroker Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-10-23 13:18:40.229 - error: host.iobroker instance system.adapter.spotify-premium.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2022-10-23 13:18:40.229 - info: host.iobroker Restart adapter system.adapter.spotify-premium.0 because enabled```

same issue here

Reproducable for me by playing playlist "Christmas Hits" (The biggest Christmas songs of all time)  (and... yeah I know... :D ).
`

spotify-premium.0
2022-12-04 18:02:04.818
warn
Terminated (UNCAUGHT_EXCEPTION): Without reason

spotify-premium.0
2022-12-04 18:02:04.817
info
terminating

spotify-premium.0
2022-12-04 18:02:04.722
error
undefined

spotify-premium.0
2022-12-04 18:02:04.722
error
unhandled promise rejection: undefined

spotify-premium.0
2022-12-04 18:02:04.721
error
Unhandled  promise rejection. This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch().

spotify-premium.0
2022-12-04 18:02:03.530
info
starting. Version 1.2.2 in /opt/iobroker/node_modules/iobroker.spotify-premium, node: v16.17.0, js-controller: 4.0.23

spotify-premium.0
2022-12-04 18:02:00.458
warn
Terminated (UNCAUGHT_EXCEPTION): Without reason

spotify-premium.0
2022-12-04 18:02:00.457
info
terminating

spotify-premium.0
2022-12-04 18:02:00.368
error
undefined

spotify-premium.0
2022-12-04 18:02:00.368
error
unhandled promise rejection: undefined

spotify-premium.0
2022-12-04 18:02:00.368
error
Unhandled  promise rejection. This error originated either by throwing inside of  an async function without a catch block, or by rejecting a promise which  was not handled with .catch().

`
Sadly, the adapter is not very communicative in terms of debugging.. :)

Anybody found a temporary solution for this till now?
`

spotify-premium.0
2023-01-22 09:37:37.086
error
playlist error 504

spotify-premium.0
2023-01-22 09:37:37.086
warn
Error: at /opt/iobroker/node_modules/iobroker.spotify-premium/main.js:360:38 at runMicrotasks () at processTicksAndRejections (node:internal/process/task_queues:96:5)

spotify-premium.0
2023-01-22 09:37:37.085
warn
Error: at sendRequest (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:248:21) at getUsersPlaylist (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:1004:16) at reloadUsersPlaylist (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:824:12) at Timeout.pollPlaylistApi [as _onTimeout] (/opt/iobroker/node_modules/iobroker.spotify-premium/main.js:1650:5) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7)

spotify-premium.0
2023-01-22 09:37:37.085
warn
http request error not handled, please debug

`

Any news on this one? Adapter became unusable 😔

I changed to calling the official Spotify app. Adapter crashes way to often

Moin !
Ist dieses Problem noch aktuell ?
Ich würde mich gerne darum kümmern, aber ich kann es aktuell nicht nachvollziehen.

Guten Morgen,
Ich habe wegen des Fehlers den Adapter deaktiviert und springe in der vis in die Spotify App ab. Ich könnte in 3 Wochen nach dem Urlaub nochmal schauen, ob das Problem noch besteht

Guten Morgen,
Ich habe wegen des Fehlers den Adapter deaktiviert und springe in der vis in die Spotify App ab. Ich könnte in 3 Wochen nach dem Urlaub nochmal schauen, ob das Problem noch besteht

Vielen Dank für Dein Feedback. Dann gehe ich davon aus , dass das Problem noch besteht.
Ich versuche mal das nachzuvollziehen ( und zu beheben ) .

Ich kann dies nicht nachvollziehen. Wie genau kann ich es reproduzieren ?

Ich habe den Adapter Mal reaktiviert. Früher wurde es in Zusammenhang mit nicht mehr existierenden Playlisten und Songs gebracht in der Bibliothek, zu denen dann keine Infos mehr abgerufen werden konnten.


Suggested fix for #476

Hey!
This PR should produce the result @reinecke is after in #476
When passing an NDF timecode with a DF frame Rate to opentime.from_timecode calculation respects the NDF TC and does not remove frames.

Codecov Report

Merging #488 into master will decrease coverage by 0.08%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #488      +/-   ##
==========================================
- Coverage   88.23%   88.14%   -0.09%
==========================================
  Files          68       68
  Lines        6900     6901       +1
==========================================
- Hits         6088     6083       -5
- Misses        812      818       +6

Impacted Files
Coverage Δ

opentimelineio/opentime.py
92% <100%> (+0.02%)
:arrow_up:

opentimelineio/adapters/fcp_xml.py
91.86% <0%> (-0.47%)
:arrow_down:

opentimelineio_contrib/adapters/fcpx_xml.py
93.28% <0%> (-0.47%)
:arrow_down:

opentimelineio_contrib/adapters/hls_playlist.py
90.68% <0%> (-0.31%)
:arrow_down:

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 878c67f...fa0c812. Read the comment docs.


DELETED /usr/local

With this in /usr/local/etc/poudriere.conf config:
BASEFS=/poudriere
ZROOTFS=/usr/local/poudriere
POUDRIERE_DATA=/usr/local/poudriere/data

After creating first Jail - like that command below:
# poudriere jail -c -j 14-1-R-amd64 -v 14.1-RELEASE

Entire /usr/local will be deleted.
Why?

While this in /usr/local/etc/poudriere.conf config does NOT destroy entire /usr/local dir.
BASEFS=/usr/local/poudriere
ZROOTFS=/poudriere
POUDRIERE_DATA=/usr/local/poudriere/data

So the 'problem' seems to be ZROOTFS from my understanding ...

Oh, hi, that's the thing I emailed you about some time ago. I hope no one got hurt too badly because of this. Backups, backups, backups...

@bileslav
Yes - I remember - I will add a warning to the article with link to this issue.
What is even more interesting ... there is NOTHING there at ZROOTFS place ...
root@poudriere-14-2:~ # find /poudriere/
/poudriere/
/poudriere/jails
root@poudriere-14-2:~ #

Interesting ... I have just set ZROOTFS to /dev/null and everything still works ...
root@poudriere-14-2:~ # grep ^ZROOTFS /usr/local/etc/poudriere.conf
ZROOTFS=/dev/null

What version of Poudriere?
Do you have ZPOOL set?
I am using this for a long time
ZPOOL=tank1
ZROOTFS=/vol1/poudriere
BASEFS=/vol1/poudriere
POUDRIERE_DATA=${BASEFS}/data

Great. But why it deletes /usr/local dir?
I already found a solution that works with ZROOTFS set to /dev/null value.
Fix the problem - do not seek the solution in workarounds.
It has to be bulletproof - not kill each user that did not lost tons of data by trying ...

I haven't looked at the sources, but isn't it possible that it must not be a directory / filesystem that is already occupied by other data, because Poudriere is trying to create other sub-filesystems in it?
I agree that it should have some sort of security check so that the user doesn't lose data.
If I understand it right, the BASEFS is the target mount point, ZROOTFS is the filesystem under the ZPOOL.
In your case from the first post, is it true that the filesystem /usr/local/poudriere is set to mount under /poudriere?
Do you have ZPOOL set right?

Whatever the reason for this, it is definitely not OKAY. We need a validation to prevent this. I'll look into it if no one else gets to it.

As I understood ZROOTFS is the dataset, not directory.
When you set ZROOTFS=/usr/local/poudriere, you are instructing poudriere to use "ZPOOL/ZROOTFS", in other words
zroot/usr/local/poudriere
As zroot/usr is already mounted on /usr, poudriere will create ZROOTFS datasets hierarchically, so:
zroot/usr -                           already mounted on  /usr (default)
zroot/usr/local/ -                 poudriere will mount on /usr/local
zroot/usr/local/poudriere - poudriere will mount on /usr/local/poudriere
So, ZFS creates the new dataset and mounts it to a directory already in use (/usr/local/).
Therefore, your /usr/local/ will remain "erased" due to the creation of a new dataset mounted on it.
But note that probably your /usr/local/ was not really deleted.
If you "zfs unmount" your datasets, your /usr/local/ probably still exists.
But as long as the zroot/usr/local/ dataset is mounted, it will appear empty to you.
Its a ZFS thing and configuration, nothing wrong to poudriere as I can see.
So I use in my configurations:
ZPOOL=zroot
ZROOTFS=/poudriere     (its a dataset)
BASEFS=/usr/local/poudriere     (its a directory)
In my settings above:
zroot is already mounted on "none" (default)
And poudriere will create the datasets (ZPOOL/ZROOTFS):
zroot/poudriere (mounted on "none" - due to hierarchy)
zroot/poudriere/jails (mounted on "none" - due to hierarchy)
And poudriere jails and ports datasets will be created and mounted on BASEFS:
zroot/poudriere/jails/poudriere_jail  mounted on /usr/local/poudriere/jails/poudriere_jail
zroot/poudriere/ports/HEAD  mounted on /usr/local/poudriere/ports/HEAD

There is some logic in it ... and there is not.
With ZROOTFS=/usr/local/poudriere it can create (and destroy in the process) these:

zroot/usr
zroot/usr/local
zroot/usr/local/poudriere

... but if I set it up as ZROOTFS=/dev/null then why it does not create these?

zroot/dev
zroot/dev/null

I did tests you mentioned, and worked perfectly here. I tested on FreeBSD 14.2 fresh install.
With ZROOTFS=/dev/null, poudriere created these: zroot/dev and zroot/dev/null


JavaScript

#JavaScript
Story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
##Acceptance
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I can see the four topics I learned listed along with a suggestion on what I should study first

learned about if, for, let, const, function


inflight dependencies

As per Checkmarx SCA scan reports In NPM inflight there is a Memory Leak because some resources are not freed correctly after being used. It appears to affect all versions, as the issue was not addressed and no fix is found. Are we planning to resolve this in near future or might be not using inflight package in near future release.

inflight will be dropped in v9.


Idacbca patch 1

Enabled Codecov

Added xml file
Added Github action

Codecov Report

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

@@            Coverage Diff            @@
##             master       #2   +/-   ##
=========================================
  Coverage          ?   95.71%
=========================================
  Files             ?        4
  Lines             ?      140
  Branches          ?        0
=========================================
  Hits              ?      134
  Misses            ?        6
  Partials          ?        0

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 7b35514...f130eae. Read the comment docs.


'module' object has no attribute 'init_tracer'

???

It seems the example is broken...

Examples are being rewritten at the moment.


Rename Azure Function ToDeleteTrigger to DataDeletionTrigger

Part of #1968
What is being addressed
As discussed in PR #2584, ToDeleteTrigger is renamed to DataDeletionTrigger
How is this addressed

Renamed files and references

/test


Fiat balances don't show up (sometimes)

Title/Description
Fiat balances don't show up.
Environment

Browser: Chrome
Safe: https://gnosis-safe.io/app/#/safes/0x699DC71d975007E57397cfd8De61440F9F4aCcD7/balances
Wallet: none
App Version: 2.1.1
Environment:

production (mainnet)

Steps to reproduce

Open https://gnosis-safe.io/app/#/safes/0x699DC71d975007E57397cfd8De61440F9F4aCcD7/balances

Expected result
See fiat balances
Obtained result
No fiat balances
Screenshots

A user reported that the balances would not load at all. For me, they would load sometimes, sometimes not.

Reminder: the pr was merged, once we release we must check with the user if the problem was solved before closing this issue. CC @francovenica