add support for format JSONEachRow with Logs Panel

Is your feature request related to a problem? Please describe.
display the whole logs within logs panel without complex query
Describe the solution you'd like
add support for format JSONEachRow, display the whole log and allow user to specify the time column.
query would by more simple
select * from xxx format JSONEachRow
Describe alternatives you've considered
complex query like select time,toJSONString(tuple(x,y,z)) from xxx, while in this way, column name is absent.

We will support JSON type properly and avoid JSONEachRow - the driver uses native format. See https://github.com/grafana/clickhouse-datasource/issues/129

No, it's not JSON type, consider that we've created a table for nginx access_log, each field with a separate column.
e.g.
create table nginx_access (
    `time` DateTime,
    `host` LowCardinality(String),
    `request_uri` String,
    ...
)

with FOTMAT JSONEachRow, we can see a complete log(with field name).

Format controls the response format from ClickHouse. The driver uses the native format for performance reasons - Grafana uses this for communication.  Introducing support in the driver for JSONEachRow just for a logs panel is going to be hard to justify - not to mention we'd need to detect the format usage and switch the encoder.
If you used the JSON type for all the fields except time, then it will just be rendered as a JSON line shortly (next release probably). Tuples will also be rendered as JSON in the next release btw.

JSON type is pretty good for semi-structured data, but with nginx access_log we definitely know how the log looks like.
On the other hand, it should give a significant increase in performance (especially in the right indexing) with separate column, moreover we can use LowCardinality and codec to reduce disk space.
I didn't try with JSON type, but format limited rows vs store whole log with JSON type, I think I would prefer the former

Yes id imagine configuring some columns explicitly, to exploit codes etc, with a column for any remaining dynamic JSON. Either way in the next release of the plugin, tuples, maps and nested (and thus JSON) will be displayed as JSON.

Something fairly similar here with respect to the log view, some way to view just any arbitrary selected row in that format would be wonderful. It's a very confusing experience for folks if you have "logs" in a table.
You might have a log (like an nginx log) in a table with an actual schema, but you can only view columns that are string types at all, and even then only one shows up until you click a log and hit the 👁 next to the field. Some way to be able to show all the fields in that view besides the Grafana table view would be wonderful. It's possible of course to toString each column, but if you wanted to dynamically select those columns somehow (like with a Grafana variable), you're out of luck.


Dev

Remove-SPOFolder   added

Hi @NPrice99, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

This PR targets the master branch, and contains all changes in dev since the last master merge. I assume this is an incorrect PR and will close this one.


Revert "Run test_ordinals after update"

This reverts commit 0aca86b313d286be979629a3193a12e17bf7171a.
Previous commit caused "make update" to fail on a clean source tree,
since the test uses "apps/openssl" which isn't built yet.

Could we somehow test for the existence of apps/openssl and run the test if it is there, rather than reverting?

How about running test_ordinals as part of 'make test'?

It is run as part of test.  The idea is to run it before the build gets too far and wastes time, causes needless global warming, melts the polar ice caps, and so on.

The other idea is to have test_ordinals run test/run_tests.pl test_ordinals directly...

f6e9c5533101066b2c759986ae8694c0f1926735


[Bug] principle_components module seems to never be used anywhere

Perhaps this is another "specific to AWS" feature, in which case it would fall under #121

@chirranjeevigopal-TRI @patrickherring-TRI is this module going to be used down the line?

@ardunn Yeah, we still think we will use it, but it will need to be integrated into the validation module in order to function correctly.

Yeah, PCA or some unsupervised method to pick out anomalies will become part of the validation in the future. We have not gotten around to it yet, but will definitely do so.


CARDS-1881: Periodical export task that serializes new forms as CSVs

CARDS-1881
To test:
On http://localhost:8080/system/console/configMgr add a new item of "Survey csv export". By default, the task will be invoked each day at midnight - 12 am, and saved under the project root directory.

PROBLEM: works well for PROMS, not PREMS
In PREMS http://localhost:8080/system/console/configMgr is missing Surveys csv export

PROMS.pdf
PREMS.pdf

@IntegralProgrammer Update re code reorganization: move everything in a core module named scheduled-csv-export, and pull this module in only in the prems project.

This needs to be retested post refactoring. Nothing should have changed functionality-wise.

Looks good! heavy_check_mark Here's how I tested it:
1. Build this `CARDS-1881` branch with `mvn clean install`.

2. Start CARDS with `./start_cards.sh --project cards4proms --dev`.

3. Login to http://localhost:8080 as `admin`:`admin` and visit http://localhost:8080/system/console/configMgr and create a new _Survey csv export_ configuration with the following parameters:

* `Name`: `csvTest`

* `Frequency in days`: `1`

* `Export schedule`: `0 0 0 * * ? *`

* `Questionnaires to be exported`: `Patient information`

* `Save path`: `/file/system/path/to/csv/export/directory`

4. Visit http://localhost:8080/Subjects.csvExport?config=csvTest.

5. An `ExportedForms_Patient information` CSV file should be created that contains only the header row.

6. Create a new _Patient information_ Form and populate it with data.

7. Visit http://localhost:8080/Subjects.csvExport?config=csvTest.

8. The `ExportedForms_Patient information` CSV file should still only contain the header row.

9. With the _Patient information_ Form still open for editing, open a new tab and visit http://localhost:8080/bin/browser.html and set the `jcr:lastModified` property of that Form node to yesterday's date.

10. Visit http://localhost:8080/Subjects.csvExport?config=csvTest.

11. The `Exported_Forms_Patient information` CSV file should now contain a data row for the exported _Patient information_ form data.

12. Repeat this process for multiple _Patient information_ Forms. Ensure that each Form with a `jcr:lastModified` value of _yesterday_ is being written to a row in the CSV export of today's data.

13. Add other Questionnaires to the `Questionnaire to be exported` configuration parameter. Ensure that they are being exported to different files as well.

14. Set the `Export schedule` parameter to `0 * * * * ? *`. Verify that the export task is running once per minute.

15. Modify the `Frequency in days` parameter and verify that the expected Forms (given their `jcr:lastModified` property value) are being exported to CSV files.

16. Create another _Survey csv export_ task (call it `csvTest2`) and ensure that it, along with the previous _Survey csv export_ task (which we called `csvTest`) are both working as expected.

17. Delete the first `csvTest` export task. Ensure that the periodic CSV data export stops but that the `csvTest2` export task still continues.

18. Finally, delete the `csvTest2` export task and ensure that the data CSV data export stops.

:point_up: Re-tested this PR using these instructions after applying the refactoring / rebase. All looks good. @sashaandjic Please test and confirm.

We need the ability to export the answer labels instead of the values in the CSVs. The values are exported by default, while for exporting labels we need to include the labels processor in the export url, e.g. /Questionnaires/OED.labels.<other_processors>.csv.
To do: add a labels check-mark box to the OSGi configuration for the Scheduled CSV exporter. If that box is enabled, then .labels would be appended to the data export URL that is queried for obtaining the data to be written to the CSV file.

There are 10 new .java classes in the PR: 2 copies of ExportConfigDefinition, 2 copies of ExportConfig, etc. In short io.uhndata.cards.proms.internal.export package contains a full copy of io.uhndata.cards.scheduledcsvexport. Not sure we need 2 copies, we don't use them both. If yes - we definetly can avoid code duplication. If they were forgotten to be deleted at the step of moving to it's own scheduled-csv-export module, all changes to proms-resources/feature/src/main/features/feature.json have to be reverted as well.

We still have changes to proms-resources/feature/src/main/features/feature.json

We still have changes to proms-resources/feature/src/main/features/feature.json

Clarification: this change needs to be moved to the prems feature file so that the csv export task will be enabled in prems.

@marta- I might be wrong but I have doubts we need/use changes introdused in prems-resources/feature/src/main/features/feature.json at all.

@marta- I might be wrong but I have doubts we need/use changes introdused in prems-resources/feature/src/main/features/feature.json at all. Csv export task is already enabled in prems here and we have its own feature.json in scheduled-csv-export module.

I see, it's pulled in for the cards4prems project in start_cards.sh and docker_entry.sh. Indeed we can just remove those changes.

Looking at the commit history, I see 4 commits from August 4 for issue 1781 that are probably another imerge/rebase artifact and need to be removed via git rebase --interactive @sofi2002sofi .

@marta- I don't think commits from 1781 are artifacts. The 1881 issue specs state:

The the first version of the implementation of this export task could branch off of the CARDS-1781 branch for easier testing.

Left 2 comments (now can be seen before rebase commits)


⚠ Bofrost.es has degraded performance

In 8788c84, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1945 ms

Resolved: Bofrost.es performance has improved in 25a2420 after 6 minutes.


Hyphenation block chooser labels

Fix https://github.com/plone/volto/issues/2548

@sneridagh that's definitely a helpful fix, especially for German labels. Thanks, @ksuess!
I am playing devil's advocate here, isn't that a breaking change since we change the HTML structure? I guess it is highly unlikely that someone customized the blocks chooser. Though, I guess we should make a rule that every change in the HTML structure is at least fully documented, what do you think?

I don't think it's a breaking change in this case, as the "external api" of BlockChooser hasn't changed.

I agree with @tiberiuichim

@tiberiuichim @nzambello didn't we add a new span element here and therefore change our public API (the HTML structure of the component)?
https://github.com/plone/volto/pull/2549/files#diff-301c0d5d89f802bfc2c42e8dab539e6a5a7a5706aa8f8f64e01b3341084e7da5R128

Let me see if there is a way to avoid a change of the html.

Just for the record: the only reason I am so pedantic here is that I would like us to come up with a set of clear rules about breaking changes that we all can rely on in the future. This discussion is important. This has nothing to do with the PR itself, which is fine.

It's great that you have an I on such subjects, @tisto!

IMHO the HTML structure of components is allowed to change without declaring it a breaking change. Here's my reasons of thinking this:

if we regard Volto as a self-contained entity and the HTML change has side-effects in other parts (for example, css styling rules), then Volto also has the "fix" for that change, in the form of an updated CSS stylesheet.
I don't consider breaking component shadowing to be a sufficient form of breaking change. The shadowing mechanism is at least on the level of monkey-patching in terms of "things that are possible, but shouldn't be encouraged". We've worked hard and continue to work on creating an official API so that shadowing is not required. Even more, I think right now the recommended approach should be "if you find that you need shadowing, do it now, be prepared that it would break in the future, but also try to fix your need in Volto, by coming up with a proper extension point".

I guess that we have two different concerns everybody is feeling, surely is what I think myself:

As a maintainer of the product Volto, I want to consider a breaking change something is literally breaking projects or changing internal APIs without retrocompatibility (semver)
As Volto integrator, having some components customized or a custom theme, I'd like to have an highlight of what is changing under the hood in the HTML because I'll need to take action for that

I wouldn't consider this case as breaking because we added a span, but I understand that similar cases could affect a project theme or something else, so we should highlight a change in HTML.
So, could we consider this type of cases as minor or patch but show a change in html to integrators and developers through the changelog? Maybe using a label or a custom section.


Support for Qt Creator 4.0.0>=beta1

Trying to use version 3.6.0 of the plugin with the newly released Qt Creator 4.0.0beta1, it appears in an error state and the "Error Details" button of the "Installed Plugins" shows:
Could not resolve dependency 'Core(3.6.0)'
Could not resolve dependency 'ProjectExplorer(3.6.0)'

It shouldn't work :) I'll make 4.0.0 version near/after official Qt Creator's release.

@OneMoreRes v4.0.0 was released yesterday :) I would love to see this plugin also work with v4. Thank you for this software

@OneMoreRes v4.0.0 was released yesterday :) I would love to see this plugin also work with v4. Thank you for this software

Updated it.

Hi Sir,  I installed Qt Creator 4.5.1 and qtc-cppcheck  4.3.0, but when I restart my Qt Creator, there is an error oucrred as:   ould not resolve dependency 'Core(4.4.0)'
Could not resolve dependency 'ProjectExplorer(4.3.0)',
I tried to compile your code, but there are many dependency file absence, could you give me some advices? thanks!  Michael, email<EMAIL_ADDRESS>

Hi, Michael!
Plugin's version must match Qt Creator's version (difference in last digit is acceptable). Version for qtc 4.5.1 is here.


Feature Request: Add a partial function fo Function

First of all really great work! I think this will my standard library for all my javascript projects :)
Curring is nice but something the parameters are badly placed. Can you add the partial function from http://ejohn.org/blog/partial-functions-in-javascript/ ?

Intriguing... I like this idea. I would like it even better if it could be a part of the bind functionality, but I have a feeling that will interfere with es5 spec...
How about a "curry" function that accepts undefined parameters to fill in later?

OK! Sugar 1.1 is now released, and includess Function#fill. This will do what you want. The more I think about it this is really a powerful method, that I think adds a lot of value. Anyway, try it out!

Is there any cause why you give the methods own names? I think using methods names that are already taken in other programming languages would be more intuitive. This method for example has the same name as the partial method in python.

Yes, it's because I am first and foremost concerned with code being readable and easy to understand. Javascript quite often suffers for people porting functionality from other languages and bringing the names along for the ride, which are often all but unintelligible. In addition Javascript is somewhat special in that (and people always forget this) it isn't used solely by people with a heavy programming background but also designers who use it for just what they need.
Now, that all being said, I think you could make the case that having a method that does the same as something in Python (it always seems to be Python) but with a different name is of itself confusing and if you're coming from a Python background it hurts code readability. I think that's valid, as well. I think there's some common ground we can gain here with the use of aliases. I'll have a look into what would be required to make things more intuitive for Python devs.


Log WandB tables on main process

This PR fixes a small bug where tables of model completions were being logged on all processes.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Date Field: Is the "date" column ever needed?

There have been many changes to the Date Field in the past, and I admit that I lost track at a certain point.
At the moment I try to save birthdays to a date field, so I use the date field without time. I noticed that — in addition to the ISO date — there is a second column called "date" in the Date Field's database table. With UTC+1 as my timezone I see rows like this in the database table:
6012    13627    1970-02-16T00:00:00+01:00    1970-02-15 23:00:00

I wonder if that "date" column is ever used by the date field. What is the sense behind it? If it makes no sense, why is it there?
(Related question: Is it a wise decision at all to save birthdays using a Date Field?)

Related question: Is it a wise decision at all to save birthdays using a Date Field?

I think it clearly is.
Maybe @nilshoerrmann knows why... (?)

I thought about it, and I think it is a bad idea. If I would try and save "date and time of birth", a date field would be perfect. But the birthday is something different. Here's a simple example: You are born in Paris on December 12, let's say at 2 o'clock a.m. At that point in time it is December 11th in New York. Still, if someone form New York asks for your birthday, you would say "December 12", right? So "date and time of birth" (a date, technically) and "birthday" (never "localized"!) are two completely different things.
Still I wonder what this database column is about. :-)

The second database column is there for historical reasons and it has been proposed to remove it in another thread.

You are born in Paris on December 12, let's say at 2 o'clock a.m. At that point in time it is December 11th in New York. Still, if someone form New York asks for your birthday, you would say "December 12", right? So "date and time of birth" (a date, technically) and "birthday" (never "localized"!) are two completely different things.

Symphony always returns system times (based on the timezone specified in your config) so this won't be a problem as long as you don't convert dates to different timezones yourself (in JavaScript for instance).
I'd use a date field for the birthdays – otherwise you want be able to filter by dates (or use date comparisons in your DS).

Well, from a DB PoV, you would set in in a date column, without any notion of time/timezones.
In Symphony, I would still put it in a datetime field and consider it to be timezone-less.

PS:

There have been many changes to the Date Field in the past, and I admit that I lost track at a certain point

These changes have been UI related – the data storage hasn't changes over the last years.

Symphony always returns system times (based on the timezone specified in your config) so this won't be a problem as long as you don't convert dates to different timezones yourself (in JavaScript for instance).

Oh, in my eyes it will be an issue! If I save a birthday as 1980-12-12T00:00:00+01:00, then change Symphony's timezone from "Europe/Berlin" to "Europe/London", this date will be output as 1980-12-11T00:00:00+00:00, so my templates will display one day off (unless I do date calculations in my output templates).
Fortunately, filtering on thise birthdays will be done in Elasticsearch anyway (on indexed custom values composed of month and day, because I don't want to use the year). So I can choose any data type I like in Symphony.

If you always store the birthday with 12:00 as time, there shouldn't be a day shift when you change the system timezone.

As long as my system timezone is Europe/Berlin, I would have to use 13:00 as time, and I would have to change this suffixed time if I change the system timezone. Anyway, saving a birthday as (localized) date/time feels technically incorrect, see above.

@nilshoerrmann I have been tempted to add a timezone field setting in DateTime for quite sometimes now. By default, I would be the one configured by Symphony.
Michael would then be able to set his birthday as UTC and always treat it as such. MySQL handles timezones OK I guess.

If at all, the date field (or even better, a different field?) should have the ability to save a date that is never localized (i.e. has no timezone in effect at all). But there wouldn't be a big difference then from saving a string—apart from being able to use different formats for manual input.

You can pass a timezone to the date field along with the date and time, e. g. GMT.

I do not think that any timezone logic is suited well for a birthday (and so the Date Field can not be the right choice). I will give you another example: Imagine that someone living in London (GMT+00:00) is on holidays in Asia, but he was born in Australia. At which time do you think should he start celebrating his birthday? I would say: 00:00 local time, no matter where he was born or where he normally lives. We see that the "birthday" value is treated as a string value by human beings, which never changes if you switch timezones. (Any real date/time value does change, of course.)

Michael I agree with your theory. Also, DB can use not localized date time storage. Oracle even as a date (without time) type.
But in Symphony, do you really need this ? I mean, your birthday field will always be birthdays... setting it to UTC as no-localized would be sufficient IMO. It will always be like a non-localized version, no ?

So what do you suggest? Add functionality to the date field to output non-localized dates?
Well, we have a setting called "Display time"… Has this intended to do non-timezone stuff, maybe? What exactly do we expect if time is not displayed in the backend?
I will come back to this tomorrow or the day after tomorrow, it's already late here.

So what do you suggest? Add functionality to the date field to output non-localized dates?

Yeah, but non-localized dates in PHP does not exists. They are UTC or system defined. Moment.js treats non-timezoned values as UTC and keeps a private flag to know it does not have a valid timezone....
We could use MySQL DATE type, but that would only impact the storage size and sorting operations.

Well, we have a setting called "Display time"…

This is meant purely as a UI feature, i.e., display time in both publish views.
That's why I though about a Timezone setting. Or we could use MySQL type in order to "forget" about php's timezone...
I am open to ideas :) And you know Michael how I love to argue with you :)

I have to admit that in my eyes this is a purely theoretical or philosophical discussion:

As long as you don't plan to move your system to the international dateline, you are save with the date field because the timezone offset will never cause a day shift as long as you stick to noontime. As both, the server (PHP) and the browser (JavaScript), always require a timezone for dates, you will have to agree on a standard timezone for "timezone-less" date information, if you like to make use of the build in date and time features of both sides. Using GMT/UTC as default seems to be common practice.
If you don't need any build in date and time functionality – neither in the backend nor on the frontend – you can just save a plain date string in the format of YYYY-MM-DD and you will be able to parse that using XSLT. Of course, you could create a timezone-less date field but I don't see a need for it, if a normal input field does the job already.

The most important thing is that you as the developer of a site or an app are aware of timezones and related day shifts. You just have to figure out your way to stop day shifts for birthdays. And in Symphony, this can either be achieved by a standardized timezone values on the date field (used for input and output) or by not storing values as datetime but as text as thus using an input field.
I don't think that the date field needs to be adjusted to handle this.
It would just overcomplicate things because it means working against the system.

And just to make this point clearer: it's either you who agrees on a default timezone or a "timezone-less" field that does this under the hood without anyone noticing.

I have to admit that in my eyes this is a purely theoretical or philosophical discussion

Yep. But when I started it, I had more questions than answers. :-)

I don't think that the date field needs to be adjusted to handle this.

That is my feeling as well. Either I create a new field called "Birthday Field" or I go with a simple Input Field.
The main point of my original post was the database column, and Nils pointed out that it is a relict of the past. So I may open another issue saying "remove that column".
Thanks to everybody for the instructive discussion!

Thanks to everybody for the instructive discussion!

 And thanks to you too :)

@michael-e: My guess is that you need that for the app we both know. As you run Elasticsearch in the background, I'd use an input field with a custom validation rule for your favourite date format. You could also extend the output field, if you need special attributes in your XML: it just extends the default input field's output, see https://github.com/hananils/output_field/blob/master/fields/field.output.php#L31.

Thanks, @nilshoerrmann. Yes, it's the crazy app. :-)

I'd use an input field with a custom validation rule for your favourite date format

That's what I will probably do.


[Docs] Create Newcomer's meeting attendance folder for the week of 10/07/2024

Notes for Reviewers
This PR fixes #
I can't create a directory with name week-of-09/09/2024 so I created week-of-09-09-2024
I moved the attendance to the new directory
Signed commits

[x ] Yes, I signed my commits.

🚀 Preview for commit 600e9f8a840ebb3f4ad2c4f5223aa243dd568554 at: https://66e3708dfc0ec652584fedc3--meshery-docs-preview.netlify.app

🚀 Preview for commit 92cd855ee40ae723f3df3336c5be0eb5f1a8cf8d at: https://66e4088ec1ad5ce8986117d9--meshery-docs-preview.netlify.app


VS Code extension

make a vscode thing to integrate cargo scan into your vscode project

this is WIP! :)


NR-50701 Fix net CVE

Fix net package CVE
Builds the container for the current commit and checks the infrastructure-agent binaries (INTEGRATIONS NOT INCLUDED) with Trivy

is this fix available for nri-bundle (helm chart)? I scanned image /newrelic/infrastructure-bundle:2.8.32 with trivy and still the CVE-2022-27664

am I using the wrong image?


Can only reference singletons / initialize new classes

So, allow me to explain for a bit, I'm trying to wrap SpotifyWebAPI into this
I share it around using an @EnvironmentObject to my views, so, naturally, I just add it to my query:
struct CurrentPlaylstsQuery: QueryKey {
    let spotify: Spotify

which results in:

[!CAUTION]
Stored property type 'Spotify' does not conform to protocol 'Equatable', preventing synthesized conformance of 'CurrentPlaylstsQuery' to 'Equatable'

And OK, I get what it's trying to do, it's calculating the key based on the fields, smart!
However, that makes it quite hard to do what I'm trying to do here.
The SpotifyWebAPI needs a lot of initialization stuff related to authentication and I don't want to have to do that for every query, it's just right there in the environment and it feels kinda anti-swiftUI in the current way.
Is there a way to just exempt certain fields from being used as a key and manually provide them when initializing the query, or even better, making it possible to call the fetching function with optional extra arguments? (like react-query also does btw)
Thank you for listening to my ted talk.

Ehh never mind, I'll just use the shared singleton pattern stuff that seems to be quite common in swift as well.
Feel free to close if you don't agree with this.


adds filtering support to the nested loop operation

use integrated filter now instead of adding a filter projection to the nested loop

@dobe pls review

@mfussenegger can you pls continue reviewing (fixup) ?

I think the equals/hashCode implementation of the RowFilter isn't really required since it is never used in a Set/HashMap etc. so identity equality would be enough.
Anyway. Lgtm

the Predicate interface enforces at least the equals() implementation... hashCode can be removed sure (I generated both ;-)


@optional conflicts with Symfony Annotations

Hi, might I suggest removing, or renaming, the annotation/tag used in things like Pheal/Core/RowSet.php called "@optional" ?
See code below:
    /**
     * initialize the rowset
     * @param \SimpleXMLElement $xml
     * @param null $name
     * @param string $rowname
     * @optional String $name
     * @optional String $rowname
     */
    public function __construct($xml, $name = null, $rowname = 'row')

When using this, in conjunction with the widely used Doctrine Annotation system, a conflict occurs where the @optional tag is used with Doctrine itself.
The error message would read:
[Semantical Error] The annotation "@optional" in method Pheal\Core\RowSet::__construct() was never imported. Did you maybe forget to add a "use" statement for this annotation?
A way to get around this would be to either:

Remove the @optional tag from the docblocks, and replace them with the standard @param, but stating it's optional afterward in the description part of the line.
Add the @IgnoreAnnotation("optional")  part in the class's docblock, as shown below:

namespace Pheal\Core;

/**
 * class to implement EVE API RowSets
 * @IgnoreAnnotation("optional")
 */
class RowSet extends \ArrayObject implements CanConvertToArray
{

The second option, although it seems cleaner, is a bit counter intuitive as it's only Doctrine that seems to use that ignore facility.
I am willing to do the updates to the code and send you a pull request if you'd like? But I just wanted to check with you, the owner of the project, first.

@sarelvdwalt I'm not even sure where the @optionals are coming from, and I'm in favour of solution one, pull request welcome.
Besides that you might want to change your setup so the doctrine annotation system is not scanning all of vendor/ (that seems very inefficient))


Auto-detect year from running machine

Signed-off-by: LanderU<EMAIL_ADDRESS>

Done here: https://github.com/ros-realtime/ros-realtime.github.io


Restart failed XCTests in Fastlane

I am trying to restart the tests that failed through Fastlane.
Here is the script I am using without much success.
@test_retries = 3
TARGET_DEVICES = ["iPad Pro (9.7-inch)"]

lane :testRetry do
    testNames = ["Example_UITests/SearchForm_TestA", "Example_UITests/SearchForm_TestB"]
    UI.message("Testing only tests: #{testNames}")

    begin
        scan(
        scheme: "Example",
        devices: TARGET_DEVICES,
        output_types: 'junit',
        fail_build: false,
            only_testing: testNames,
            clean: true
      )
    rescue

       while @test_retries > 0
         failed_tests = find_failed_tests
         UI.message("Retrying failed tests: #{failed_tests}")

       break if failed_tests.empty?
       @test_retries -= 1
       scan(
             scheme: "Example",
         devices: TARGET_DEVICES,
         output_types: 'junit',
         fail_build: @test_retries.zero?,
         only_testing: failed_tests,
             clean: true
       )
        end
    end
end

def find_failed_tests
    report = File.open('test_output/report.junit') { |f| Nokogiri::XML(f) }
    suite_name = report.xpath('testsuites/@name').to_s.split('.')[0]

    test_cases = report.xpath('//testcase')

    only_testing = []
    test_cases.each do |test_case|

        next if test_case.xpath('failure').empty?

    test_class = test_case.xpath('@classname').to_s.split('.')[1]
    test_name = test_case.xpath('@name')
    only_testing << "#{suite_name}/#{test_class}/#{test_name}"
    end

    only_testing.join(',')
end

The issue that I am having is the failed tests are not being reported in junit. The report.xml just shows the passed tests.

Can you be a bit more precise which of your part of your code does not work as expected and how that relates to fastlane?


[cleanup][broker] Fix ClusterDataImpl#clone and add test

PR for tests

@lhotari - have you seen the errors in this build before? https://github.com/michaeljmarshall/pulsar/actions/runs/3833202322/jobs/6527659487
I could find any other builds with this issue, but I've had it fail twice now.

@lhotari - have you seen the errors in this build before? https://github.com/michaeljmarshall/pulsar/actions/runs/3833202322/jobs/6527659487
I could find any other builds with this issue, but I've had it fail twice now.

@michaeljmarshall I've seen it a few times. I created https://github.com/apache/pulsar/pull/19127 to address it.

Thanks for the workaround @lhotari!


kwokctl create cluster --runtime=kind not working

How to use it?

[ ] kwok
[ ] kwokctl --runtime=docker (default runtime)
[ ] kwokctl --runtime=binary
[ ] kwokctl --runtime=nerdctl
[X] kwokctl --runtime=kind

What happened?
root@dewiserver:/home/dewi/tmp# kwokctl create cluster --runtime=kind
Cluster already exists                                                                                cluster=kwok
Cluster is not ready yet, will be restarted                                                                                cluster=kwok
Deleting cluster "kwok-kwok" ...
Deleted nodes: ["kwok-kwok-control-plane"]
Cluster is starting                                                                                cluster=kwok
Creating cluster "kwok-kwok" ...
 ✓ Ensuring node image (docker.io/kindest/node:v1.27.1) 🖼
 ✓ Preparing nodes 📦
 ✓ Writing configuration 📜
 ✓ Starting control-plane 🕹
 ✓ Installing CNI 🔌
 ✓ Installing StorageClass 💾
 ✓ Waiting ≤ 1m0s for control-plane = Ready ⏳
 • Ready after 15s 💚
Set kubectl context to "kind-kwok-kwok"
You can now use your cluster with:

kubectl cluster-info --context kind-kwok-kwok

Not sure what to do next? 😅  Check out https://kind.sigs.k8s.io/docs/user/quick-start/
Loaded image                                                                       cluster=kwok image="registry.k8s.io/kwok/kwok:v0.2.0"
ERROR Failed cordon nodecluster=kwok err="cmd wait: /home/dewi/code/dot-files/bash_stuff/helpers/kubectl cordon kwok-kwok-control-plane: exit status 1\n+ exec /usr/bin/kubectl -s :8080 cordon kwok-kwok-control-plane\nE0505 08:56:01.086474   63851 memcache.go:265] couldn't get current server API group list: Get \"http://:8080/api?timeout=32s\": dial tcp :8080: connect: connection refused\nE0505 08:56:01.086584   63851 memcache.go:265] couldn't get current server API group list: Get \"http://:8080/api?timeout=32s\": dial tcp :8080: connect: connection refused\nE0505 08:56:01.087781   63851 memcache.go:265] couldn't get current server API group list: Get \"http://:8080/api?timeout=32s\": dial tcp :8080: connect: connection refused\nE0505 08:56:01.088970   63851 memcache.go:265] couldn't get current server API group list: Get \"http://:8080/api?timeout=32s\": dial tcp :8080: connect: connection refused\nThe connection to the server :8080 was refused - did you specify the right host or port?\n"
Cluster is started                                                                                cluster=kwok elapsed=33s
You can now use your cluster with:

        kubectl cluster-info --context kwok-kwok

Thanks for using kwok!

What did you expect to happen?
For it to successfully spin up a cluster using kind
How can we reproduce it (as minimally and precisely as possible)?
kwokctl create cluster --runtime=kind
Anything else we need to know?
No response
Kwok version
root@dewiserver:/home/dewi/tmp# kwok --version
kwok version v0.2.0 go1.20.4 (linux/amd64)
root@dewiserver:/home/dewi/tmp# kwokctl --version
kwokctl version v0.2.0 go1.20.4 (linux/amd64)
root@dewiserver:/home/dewi/tmp#

OS version
root@dewiserver:/home/dewi/tmp#  uname -a
Linux dewiserver 5.15.0-71-generic #78-Ubuntu SMP Tue Apr 18 09:00:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

This is a bug from an older version of Kind, can you try upgrading Kind and retrying?

Need more information, feel free to open it if you still have questions
/close

/kind support
/remove-kind bug


hJSX doesn't pass in data- attributes (or arbitrary attributes in general)

Using either h() or hJSX:
h('div', {'data-something': 'something'})

or

does not pass the data-something attribute to the element.
I haven't gotten anything besides className and id to work, for that matter. role also fails to show up.
This is confusing because I don't remember having this problem using hyperscript by itself.

h('div', {attributes: {'data-something': 'something'}})

Sorry about that, my mistake. It definitely works with h(). hJSX still doesn't work, though.

Ahh, I see. I'm used to being able to insert attributes directly in React. Thank you!

@Zacqary :
Works with hJSX and es6 template strings (note the backticks and the use of attributes instead of className)
var errorClass = a > 0 ?  'error' : ''';
 return (
        <div attributes={{class:`ui form success centered hello-form ${errorClass}`}} >

      );


Add regex status code checking

I sometimes need to not care as much about the exact status code returned and care more that it is not returning a certain status code specifically. This could easily be achieved using regex as I already use it with supertest ~0.21 but 1.0 broken nearly every test I had (lots of redirecting) but there are a bunch more tests that I just can not fix with out something like .expectnot or to be able to do something like .expect(/2!/) where it just checks that the first number in the status code isn't a 2... all other should be validated with the location or just plain error.

Hello, it sounds like there are two questions you are asking about.
The first is asking if an enhancement could be implemented in supertest to allow regex expressions for HTTP response codes.
The second question is asking about the handling of non 2xx response codes in supertest 1.0.0. This was corrected in version 1.0.1 with #224
if the above is correct, I think having a regex response code check could be a worthwhile feature.

Yeah, sorry, regex expressions for response codes is what I am asking for. Okay I think I just didn't update to 1.0.1 yet then.

bump? @mikelax

I would love to get this included, if you are able to submit a PR please go ahead and I will review.
I am going to bump the milestone to 1.3 given this may change the API for the status check.


Helper Z-Index

This will prevent the dragged item from falling behind items with high z-indexes (like modals).

Hey @jetpackjarrett, sorry for not getting back to you sooner.
The reason why I didn't implement something like this is I think z-indexes should be something that's managed by the end-user of the library, not by the library itself. Using z-index 999999 is generally a code-smell. As well, other libraries may already be assigning something to z-index 999999 (or greater), in which case the user would still need to overwrite the value you've assigned here with !important (also a code-smell).
If anything, it may be worth mentioning in the docs that this is something that can be achieved through applying a z-index to the helperClass.

@clauderic thanks for the feedback. For whatever reason, the helperClass would not apply a z-index. I'll give it another go.

Hmm, odd. Perhaps an issue with stacking contexts? (though unlikely, since the helper gets appended to the body)


Add README.md files for each data-structure/algorithm

Add documentation to each of the Data-structure/Algorithm next to the codes so a new user can understand them better. Each folder corresponds to one concept, so a README.md file within each folder would be quite helpful.
(You can start off by just adding the documentation to one of the algorithms/data-structure)

@erilyth What exactly to document about an algorithm ?

@codegagan A small description of what the algorithm/datastructure does and what it is used for which a person could read up and understand how the algorithm works. Once they understand what it is and how it works then they can go through the code and understand the implementation aspects as well.
(Lets consider Heaps for example, https://www.tutorialspoint.com/data_structures_algorithms/heap_data_structure.htm, something similar to the description provided there would be great!)

Can you assign me?

@anabastos You can start working on it, just submit a PR and it should be fine.

I'd like to help out with this too. Will work on the Stacks, Queues and Heaps part

@avi-jain Sure! Go ahead!

Hey @erilyth I'd like to work on Graphs if that's fine with you!

@salman-bhai Sorry, the README for graphs was already done, but if you have any improvements I would be glad to add them in.

@erilyth
I have added README for SORTING as well as BST if that's fine with you.Sorry I didn't asked you before.

@jatinrajani Merged! Thanks :)

Thanks!!

Hey @erilyth, i would like to contribute with segment tree's README, if that's okay.


tools/omnissm - Spillover into SQS queue when throttled

The primary change here is adding optional spillover for throttled SSM API calls to a SQS queue, however, there are a few other small changes/fixes:

Use trimpath when building omnissm binary (trimming local path from stack traces)
Fix a control flow error made when checking if items are in DynamoDB

This PR does not implement the other side of the SQS queue which would need to receive from it and json.Unmarshal based upon the type of message received to complete the throttled API call.  Also, the behavior when not given a spillover queue via environment variable OMNISSM_SPILLOVER_QUEUE is to simply return the errors as normal when exceeding the maximum retries (which currently default to 5).

one thing to note on the pr, seems to be the handling of the deferral not leaving state in the registration table, which could lead to multiple queue entries for a server, that could either be handled by the reconciler checking the registration table for state prior to processing, or capturing deferred registration in the table here (status field perhaps).

I have investigated the aws-sdk-go retryer more in depth and discovered it is nearly exactly what is being implemented here.  Because of this I'm recommending that instead of doing this we use the aws retryer and check that it is the type of error that was either a throttle or retryable error and send to the spillover queue in that case.  I am committing what I'm referring to shortly so that it will be available in the PR.


MeanSegmentEncoderTransform

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Before submitting (must do checklist)

[x] Did you read the contribution guide?
[x] Did you update the docs? We use Numpy format for all the methods and classes.
[x] Did you write any new necessary tests?
[x] Did you update the CHANGELOG?

Type of Change

[ ] Examples / docs / tutorials / contributors update
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Improvement (non-breaking change which improves an existing feature)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Proposed Changes

Add MeanSegmentEncoderTransform
Related Issue

Closing issues

closes #233

Codecov Report

Merging #265 (f423b72) into master (84dd469) will decrease coverage by 30.62%.
The diff coverage is 40.00%.

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

@@             Coverage Diff             @@
##           master     #265       +/-   ##
===========================================
- Coverage   86.56%   55.93%   -30.63%
===========================================
  Files          92       92
  Lines        4429     4446       +17
===========================================
- Hits         3834     2487     -1347
- Misses        595     1959     +1364

Impacted Files
Coverage Δ

etna/transforms/segment_encoder.py
40.54% <36.84%> (-59.46%)
:arrow_down:

etna/transforms/__init__.py
100.00% <100.00%> (ø)

etna/commands/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

etna/commands/backtest_command.py
0.00% <0.00%> (-96.43%)
:arrow_down:

etna/commands/forecast_command.py
0.00% <0.00%> (-92.00%)
:arrow_down:

etna/commands/__main__.py
0.00% <0.00%> (-87.50%)
:arrow_down:

etna/commands/resolvers.py
0.00% <0.00%> (-80.00%)
:arrow_down:

etna/analysis/feature_relevance/relevance_table.py
23.52% <0.00%> (-76.48%)
:arrow_down:

etna/analysis/outliers/density_outliers.py
22.72% <0.00%> (-75.00%)
:arrow_down:

etna/transforms/statistics.py
27.50% <0.00%> (-71.67%)
:arrow_down:

... and 52 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 84dd469...dba96aa. Read the comment docs.


Singularity containers do not run when working directory is a sshfs mount

When I try to run a singularity container from a command line, e.g. typing fsleyes in the terminal after loading the fsl module, and working directory is a sshfs mount (either the base of the mount, or a subdirectory), the container does not run, and I get this error:
ERROR  : Failed to open current working directory: Permission denied
Strangely, the same directory is accessible from within the Singularity container, as long as the container was executed from a different working directory. When it comes to launching from the menu of VNM -- when launching the GUI app (fsleyesGUI 6.0.4) all works fine, but when launching the Singularity container interactively (e.g., fsl 6.0.4), I get the same error. I guess all depends on the working directory where the container is launched from in each scenario.
Can you reproduce it?
FYI, I do the sshfs the simplest way possible:
sshfs USER@TARGET_HOST:TARGET_PATH SOURCE_PATH
Should I mount differently?

Dear @civier
you need to add your ssh-mounted directory to your SINGULARITY_BINDPATH environment module variable and then it should work.
Cheers
Steffen

It IS added to SINGULARITY_BINDPATH
As I said, when I start the container from a different working directory, the ssh-mounted directory IS accessible from the container!
I attach a screenshot of the problem. /fred is the directory which is ssh-mounted on our HPC:

That's the output when running Singularity with the --debug flag:
neuro@929c10268e06:/fred$ export PWD=pwd -P
neuro@929c10268e06:/fred$ singularity --debug exec --pwd $PWD /vnm/containers/mrtrix3_3.0.2_20201125/mrtrix3_3.0.2_20201125.simg mrview $@
DEBUG   [U=1000,P=28855]   persistentPreRun()            Singularity version: 3.7.0
DEBUG   [U=1000,P=28855]   persistentPreRun()            Parsing configuration file /usr/local/singularity/etc/singularity/singularity.conf
DEBUG   [U=1000,P=28855]   handleConfDir()               /home/neuro/.singularity already exists. Not creating.
DEBUG   [U=1000,P=28855]   setValue()                    Updated flag 'bind' value to: [/afm01,/afm02,/90days,/30days,/QRISdata,/RDS,/data,/short,/proc_temp,/TMPDIR,/nvme,/local,/gpfs1,/working,/winmounts,/state,/autofs,/cluster,/local_mount,/scratch,/clusterdata,/nvmescratch,/vnm,/fred,/dagg,/home]
DEBUG   [U=1000,P=28855]   execStarter()                 Saving umask 0022 for propagation into container
DEBUG   [U=1000,P=28855]   execStarter()                 Checking for encrypted system partition
DEBUG   [U=1000,P=28855]   Init()                        Image format detection
DEBUG   [U=1000,P=28855]   Init()                        Check for sandbox image format
DEBUG   [U=1000,P=28855]   Init()                        sandbox format initializer returned: not a directory image
DEBUG   [U=1000,P=28855]   Init()                        Check for sif image format
DEBUG   [U=1000,P=28855]   Init()                        sif format initializer returned: SIF magic not found
DEBUG   [U=1000,P=28855]   Init()                        Check for squashfs image format
DEBUG   [U=1000,P=28855]   Init()                        squashfs image format detected
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding SHELL environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding SUPERVISOR_GROUP_NAME environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding COLORTERM environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding SUPERVISOR_SERVER_URL environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding HOSTNAME environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding ModuleTable002 environment variable
VERBOSE [U=1000,P=28855]   SetContainerEnv()             Not forwarding SINGULARITY_VERSION environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding LMOD_DIR environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding PWD environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding MODULESHOME environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding ModuleTable_Sz environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding VTE_VERSION environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding LMOD_VERSION environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding LMOD_DEFAULT_MODULEPATH environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding GO_VERSION environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding LMOD_PKG environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding TERM environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding USER environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding LOADEDMODULES environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding DISPLAY environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding SHLVL environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding ModuleTable001 environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding LC_CTYPE environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding SUPERVISOR_PROCESS_NAME environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding MODULEPATH environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding LMFILES environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding LMOD_CMD environment variable
VERBOSE [U=1000,P=28855]   SetContainerEnv()             Not forwarding SINGULARITY_BINDPATH environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding DEBIAN_FRONTEND environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding OLDPWD environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding SUPERVISOR_ENABLED environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding BASH_FUNC_ml%% environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding BASH_FUNC_module%% environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding _ environment variable
DEBUG   [U=1000,P=28855]   SetContainerEnv()             Forwarding USER_PATH environment variable
VERBOSE [U=1000,P=28855]   SetContainerEnv()             Setting HOME=/home/neuro
VERBOSE [U=1000,P=28855]   SetContainerEnv()             Setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DEBUG   [U=1000,P=28855]   init()                        Use starter binary /usr/local/singularity/libexec/singularity/bin/starter-suid
VERBOSE [U=0,P=28855]      print()                       Set messagelevel to: 5
VERBOSE [U=0,P=28855]      init()                        Starter initialization
DEBUG   [U=0,P=28855]      load_overlay_module()         Trying to load overlay kernel module
DEBUG   [U=0,P=28855]      load_overlay_module()         Overlay seems supported by the kernel
VERBOSE [U=0,P=28855]      is_suid()                     Check if we are running as setuid
VERBOSE [U=0,P=28855]      priv_drop()                   Drop root privileges
DEBUG   [U=1000,P=28855]   read_engine_config()          Read engine configuration
DEBUG   [U=1000,P=28855]   init()                        Wait completion of stage1
VERBOSE [U=1000,P=28863]   priv_drop()                   Drop root privileges permanently
DEBUG   [U=1000,P=28863]   set_parent_death_signal()     Set parent death signal to 9
VERBOSE [U=1000,P=28863]   init()                        Spawn stage 1
DEBUG   [U=1000,P=28863]   startup()                     singularity runtime engine selected
VERBOSE [U=1000,P=28863]   startup()                     Execute stage 1
DEBUG   [U=1000,P=28863]   StageOne()                    Entering stage 1
DEBUG   [U=1000,P=28863]   prepareAutofs()               No autofs mount point found
DEBUG   [U=1000,P=28863]   Init()                        Image format detection
DEBUG   [U=1000,P=28863]   Init()                        Check for sandbox image format
DEBUG   [U=1000,P=28863]   Init()                        sandbox format initializer returned: not a directory image
DEBUG   [U=1000,P=28863]   Init()                        Check for sif image format
DEBUG   [U=1000,P=28863]   Init()                        sif format initializer returned: SIF magic not found
DEBUG   [U=1000,P=28863]   Init()                        Check for squashfs image format
DEBUG   [U=1000,P=28863]   Init()                        squashfs image format detected
DEBUG   [U=1000,P=28863]   setSessionLayer()             Overlay seems supported and allowed by kernel
DEBUG   [U=1000,P=28863]   setSessionLayer()             Attempting to use overlayfs (enable overlay = try)
VERBOSE [U=1000,P=28855]   wait_child()                  stage 1 exited with status 0
DEBUG   [U=1000,P=28855]   cleanup_fd()                  Close file descriptor 4
DEBUG   [U=1000,P=28855]   cleanup_fd()                  Close file descriptor 5
DEBUG   [U=1000,P=28855]   cleanup_fd()                  Close file descriptor 6
DEBUG   [U=1000,P=28855]   init()                        Set child signal mask
DEBUG   [U=1000,P=28855]   init()                        Create socketpair for master communication channel
DEBUG   [U=1000,P=28855]   init()                        Create RPC socketpair for communication between stage 2 and RPC server
VERBOSE [U=1000,P=28855]   priv_escalate()               Get root privileges
VERBOSE [U=0,P=28855]      priv_escalate()               Change filesystem uid to 1000
VERBOSE [U=0,P=28855]      init()                        Spawn master process
ERROR   [U=0,P=28855]      init()                        Failed to open current working directory: Permission denied
DEBUG   [U=0,P=28869]      set_parent_death_signal()     Set parent death signal to 9
VERBOSE [U=0,P=28869]      create_namespace()            Create mount namespace

That might answer this, though a bit different:
https://github.com/hpcng/singularity/issues/2638
I'll check later on

Interesting, but I don't know how to solve this problem.

The problem is that Singularity actually runs with suid, and before dropping the admin privileges, it tries to access the working directory as root. By default, sshfs mounts only allow the user that created them to assess the mount, and that is why Singularity gives the error:
ERROR : Failed to open current working directory: Permission denied
The solution is to allow the root user to access the sshfs mount. It is done in the following way:

add the line "user_allow_other" to /etc/fuse.conf within the VNM
add the option "-o allow_root" to the sshfs command

@stebo85 @aswinnarayanan Could you please add point 1 to the VNM container permanently? You may also want to have it as part of NeuroDesk installation script (in case user have admin rights)

Dear @civier
It would be good if you can try to add this yourself. It should only be one line in here:
https://github.com/NeuroDesk/neurodesk/blob/master/vnm/Dockerfile

great work @aswinnarayanan :) @civier can you test?

Resolved


always calls params to persist them into controller action

Bug Fix
Description
Current behaviour:

If we don't call params in the reflex, the form parameters will not be available in the controller action, it will only have params like :controller and :action

You can see this behavior in the expo with my PR for the validation example: https://github.com/hopsoft/stimulus_reflex_expo/pull/44/files , in the reflex I call params otherwise it will not validate, as the form params are missing.
Expected behaviour
calling params in then controller should yield the same result as calling params in the reflex, without having to call params in the reflex first.
Why should this be added
I think the current behavior is unexpected. I am however unsure how to best do this, and I am not adressing the root problem.
Also I made the instance_variables a bit clearer, as there is a params argument in initialize
Why is this happening
I don't fully understand it: @_params is used in the controller action to access to params. But I did not find out how it is getting set. I thought it was in  ActionPack Meta Line 159, but breakpoints there did not stop for me, so I am not sure if my tooling is failing me, or if this is really not called
But the suggested code makes sure that the @_params is set, so the right params come out for the controller action. This alleviates the problem, but does not solve the root problem of why this is happening in the first place. The header ["action_dispatch.request.parameters"] has all the params and should be used. 🤷
Nicer code?
maybe doing it like this would be prettier and more explicit
def initialize
  …
  @_params = ActionController::Parameters.new(request.parameters)
end

def params
  @_params
end

## Checklist

- [x] My code follows the style guidelines of this project
- [x] Checks (StandardRB & Prettier-Standard) are passing

Thanks for this one, @RolandStuder! Great catch.


My controller drift and I can't fix it

Hello,
When I map the joystic of my pro controller for switch, I allways drift. how can I fix it? it drift on the right, I put you a screeshot of range I get after mapping the joystick... normally I should have 0-100 but I have like 11-89 so it drift

I have the same issue have you fix it yet? I need the solution

It seems it's an issue for the pro switch controllers. I'm having the same issue as well.

It seems it's an issue for the pro switch controllers. I'm having the same issue as well.


Check that gradle plugin is installed from intellij plugin

I think I remember kotlin doing this where if you are in a .kt file in a project that does not have the kotlin gradle plugin applied it complains at you with an actionable dialog that will add the plugin for you. Would be nice if we did that same for .sq files

it should also show a similar dialog for version mismatches


NOT WORKING

It is not able to crawl the following website
https://webdev.1csalgo.workers.dev/0:/Academind Courses/React - The Complete Guide (incl Hooks, React Router, Redux)/

Hey I'm trying to open the colab notebook but it asks for permission . If you can send me your colab copy of this code of version 2  I can help you with that.

It is not able to crawl the following website
https://webdev.1csalgo.workers.dev/0:/Academind Courses/React - The Complete Guide (incl Hooks, React Router, Redux)/

it requires username and password.
write it to me and i'll check the pattern

It is not able to crawl the following website
https://webdev.1csalgo.workers.dev/0:/Academind Courses/React - The Complete Guide (incl Hooks, React Router, Redux)/

it requires username and password.
write it to me and i'll check the pattern

https://csalgoweb.telegramm.workers.dev/
Username & Password: VanGogh

Did it worked? @DanielLivingston32

Nope. It doesn't work for sites with username and password.

Nope. It doesn't work for sites that require username and password.


Added queue endpoints

Hey there!
I'm looking to add this to a personal project, so I quickly added these methods and some tests.
Let me know if you need me to change something. Thanks.

@rinukkusu Could you take a look at this?


Feature/search backpressure

codacy complaining about trivial things

Will this horizontally scale?

It is not, but there is no need to scale it horizontally (in my opinion) because this code is not the bottleneck. The bottleneck is currently the ES. To scale it horizontally we would need to use akka or (easier) Spark.

Cloud Foundry scales horizontally so all code should be in line with the 12-Factor Application Design guidelines.

should we have some representative tests of what this is addressing? (5k req's)


Package KEDA 2.0 chart

Figured while I was at it may as well open the PR for 2.0.0 chart
Related to #94

Using https://github.com/kedacore/charts/pull/97 instead of this one since there were merge conflicts


focusOnSelect fale, slidesToShow modification, initial state bugginess

I thought the focusOnSelect bug was due to my nested images (#647), but even without them it doesn't function.

slidesToShow tends to show little partials of obscured slides, is there any way i can hide those partials? I'd really just like to see 3 slides, not 3 and two halves.

also please note that the initial slides state is uneven and all messed up. I'm not sure why this is though, sorry.

I appreciate any advice on any of these points.
http://jsfiddle.net/basiclaser/5gwtug81/3/

It's because of variable width. They dont have a width because of background images.


direct_messages: Do not open compose box when navigating to DM conversation.

Remove start("private") call form on_narrow function in compose_actions.js.
Also, removed the if (narrow_state.narrowed_by_pm_reply()) logic that was used to keep compose_box closed in certain cases as now it will remain closed in every case.
Removed force_close option that was passed as opts.force_close to on_narrow that was used to keep compose_box closed while navigating between DMs, not needed it will remain closed now.

Fixes:
#25078

Screenshots and screen captures:
No still screenshots showing the change hence attaching the video:
https://user-images.githubusercontent.com/64723994/231818597-e07810c8-ce5c-48bf-8397-3f0fb787cb70.mp4

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

There's ongoing discussion on CZO as to whether we want to make this change.

Closing for now as not planned; we can always reopen if that changes.


Set a target DOM element to contain the neuroglancer component.

It should be possible to set a target DOM element when setting up the viewer object, so that all the changes to the page are done inside that. This has already been done for the main content of the viewer, but there are still status messages that need to be placed correctly. The current problem that needs to be conquered is that the method call to create those messages doesn't have access to the stored DOM target.

Look at ContextMenu & StatusMessage

Dealt with context menu by removing it from the page using display:none style instead of visibility: hidden

Left StatusMessage alone as it doesn't affect the rendering of the page, just looks odd when the message fall out to the bottom of the page. Not 100% urgent to fix.

See 41e8f62266ed4 for fix


Bronzeman mod affecting weapon presets in traders

SPT-Aki - version 3.8.3
Bronzeman mod - version 1.1.2
I've noticed that the mod is affecting weapon presets that are offered by traders, possibly only custom traders?
It could also be only affecting weapon presets that are barter trades, but I haven't tested that enough yet to figure it out.
An example without Bronzeman. (Custom trader "Lotus")

Same exact trade with Bronzeman loaded, you can also see it affecting other weapon presets.

And at least for the G36, I have the weapon in my stash already, and it still appears to be locked?
I have made sure to restart the client and server just in case, since I obtained it from a Sealed Weapon Crate.
This is my config file, if it helps.
{
    "unlocks": {
        "raidRunThrough": true,
        "raidDeath": false,
        "inventory": true,
        "quests": true,
        "foundInRaidOnly": false
    },
    "hideItems": false,
    "allTraders": true,
    "traders": [
        "54cb50c76803fa8b248b4571",
        "54cb57776803fa99248b456e",
        "579dc571d53a0658a154fbec",
        "58330581ace78e27b8b10cee",
        "5935c25fb3acc3127c3d8cd9",
        "5a7c2eca46aef81a7ca2145d",
        "5ac3b934156ae10c4430e83c",
        "5c0647fdd443bc2504c2d371"
    ],
    "includeRagfair": true,
    "ignoreCategories": {
        "keys": true,
        "specialEquipment": true,
        "secureContainers": true,
        "maps": true,
        "money": true,
        "foodAndDrink": false,
        "barterItems": false,
        "meleeWeapons": false,
        "throwables": false,
        "infoItems": false,
        "meds": false,
        "backpacks": false,
        "rigs": false,
        "weaponParts": false,
        "guns": false,
        "armourHelmet": false,
        "headphones": false,
        "armBands": false,
        "ammo": false,
        "ammoBoxes": false,
        "containers": true
    },
    "ignoreItems": [
        "5991b51486f77447b112d44f",
        "591094e086f7747caa7bb2ef",
        "5f4f9eb969cdc30ff33f09db",
        "5910959486f7747d96753485",
        "544fb5454bdc2df8738b456a",
        "5ac78a9b86f7741cca0bbd8d",
        "5b4391a586f7745321235ab2",
        "5910968f86f77425cf569c32",
        "Collectors_Case",
        "Trophy_Case"
    ],
    "requireUnlockComponents": true,
    "debug": false
}

Hey-o, apologies like you've noted in the SPT disc I'm not super active on this mod. Bursts of activity whenever I can manage.
If you set debug to `true in the mods config it will output any items that are allowed/filtered in the SPT console like this:
This should help with understanding why an item may be filtered, as since you've got requireUnlockComponents set to true it could be that the G36 you've unlocked doesn't have a mod on it that the preset does.
If that isn't helping then drop the SPT log here and I'll try and take a look if I get time in the future.


Method save a record being an instance

Feature description::
Currently to save a record in a table:
person_1 = Person(first_name="Teste 1", last_name="teste lastname", age=19, salary=5000)

person_1 = await Person.save(person_1)

This issue wants to add a new way to save, making it easier for the user:
person_1 = Person(first_name="Teste 1", last_name="teste lastname", age=19, salary=5000)

await person_1.save()

Need:
Make it easier for the user to save a new record.

The "person_1 = " in "await( Person.save(person1)" is unnecessary. This can be written as
"await Person.save(person1)" or "await person1.save(person1)".  However, person1 must be passed as a parameter to save because methods in Python do not have a hidden parameter of the object.

Thanks for the contribution!
I understand your point. I see this could be useful, as it would be simpler to code await person_1.save() than await Person.save(person_1).
Don't you see the need for it ?


 This breaks the SHA256 checksum of the license files used in clarify sections in cargo-about config files embedded in this repository, leading to warnings like this in CI:
2022-10-01 17:18:11.8629067 +00:00:00 [WARN] failed to validate all files specified in clarification for crate artichoke 0.1.0-pre.0: checksum mismatch, expected a7f7d7c7ab9585b1c5e43d592c648d6d3fff7debcf7cfbde301f63b02157444d
2022-10-01 17:18:11.8632725 +00:00:00 [WARN] failed to validate all files specified in clarification for crate artichoke-backend 0.19.0: checksum mismatch, expected a7f7d7c7ab9585b1c5e43d592c648d6d3fff7debcf7cfbde301f63b02157444d

This commit adds an additional step to the composite action to ensure git is configured with LF EOL behavior and does not normalize using autocrlf
See:

https://github.com/actions/checkout/issues/135

No warnings on windows in CI. Looks good to merge.


create a new folder yourself if you can't find it

RT.

Not sure I understand.

He is instructing people to create the ~/Library/Developer/Xcode/UserData/FontAndColorThemes directory, if it doesn't exist.  I think if you add that to the instructions, you can just close this issue.

How did you get that from RT?

OH - got it. The title and RT = Read Title.


🐛Huge performance issue in Tasks/Workers, LINQ issue

:bug: Describe the bug
In a lot of workers there is Task used incorrectly in IEnumerable which is not materialized once, but reenumerated by each call to this list of tasks. This leads to re-executing this list of tasks, so many of tasks is called 2x, 3x or even more.
To Reproduce
Check code of all workers and another classes where Tasks are used in IEnumerable
Screenshot of one place where this issue is

GetWitsmlObjectById is called twice for _expandableObjects.
Same issue in another workers like CopyLogWorker.... etc..

Nice catch! Stumbled upon the same problem when creating the CheckLogHeaderWorker, but didn't notice other workers had the same problem.
A quick fix is to turn the IEnumerable into a List with .ToList() before passing it to Task.WhenAll.


sendReliableMessage not always working

I noticed that sometimes sendReliableMessage for Real Time Multiplayer doesn't work. And that causes my game to stop working. I tried to avoid this in onRealTimeMessageSent with:
if (statusCode != GamesCallbackStatusCodes.OK) {                         //send again due to error                         sendMessage(lastMessage);               }
but this doesn't always work. Sometimes it tries to send the message again and again at least 100 times and sometimes the game continues, but sometimes it drops the player trying to send the message. How I can ensure that the message delivery is always successful? This is very unreliable now. Does other people face similar issues?
I notice that this is happening since last Monday - and that is the day of the last Google Play Services update.

I'm having the same problem and it happened when I imlemented my game last year not only recent updates from Google Play Services. I'm using version 12.0.1.


Is there any way to speed up loading Microsoft.xaml.Behaviors.dll?

I am finding that it takes around 10 seconds to load this DLL - longer than loading all of my other 50 DLLs combined.  this is on a quad core PC with 32GB RAM.
I have tried using WIX to install the application in the production environmenmt, and NGEN'ing all DLLs but it makes little if any difference
Any hints or tips on speeding this up would be appreciated

Can you explain how you got to the pinpoint the issue to that specific assembly? Also, can you tell me if this was on a debug or release build?

It happens in release and debug mode.
I noticed this assembly always took around d10 seconds to load in the VS output window.
I tried removing the next assembly to load from the solution which was one of my projects), but it made no difference
I have made sure there are no exceptions raised when the solution loads
In the production environment it takes the same 20 seconds to load all 53 assemblies as it does on my development PC.  On my development PC it takes 10 seconds out of the 20 seconds to load this single assembly.
I am measurting the time from when it says symbols loaded to when the next assembly says its symbols are loaded
Gordon
From: Pedro Lamas<EMAIL_ADDRESS>Sent: 15 September 2020 18:00
To: microsoft/XamlBehaviors<EMAIL_ADDRESS>Cc: Gordon Ireland<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/XamlBehaviors] Is there any way to speed up loading Microsoft.xaml.Behaviors.dll? (#197)
Can you explain how you got to the pinpoint the issue to that specific assembly? Also, can you tell me if this was on a debug or release build?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/microsoft/XamlBehaviors/issues/197#issuecomment-692846023 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AEOMXTD55NW7DBB7PY4Q54DSF6MSFANCNFSM4Q6HVNUA .  https://github.com/notifications/beacon/AEOMXTCUSJ22SL2N7HSQVJ3SF6MSFA5CNFSM4Q6HVNUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFFF73RY.gif

On site I have tried NGEN and installing in GAC vioa a Wix Installer, but it makes very little difference if any
From: Pedro Lamas<EMAIL_ADDRESS>Sent: 15 September 2020 18:00
To: microsoft/XamlBehaviors<EMAIL_ADDRESS>Cc: Gordon Ireland<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/XamlBehaviors] Is there any way to speed up loading Microsoft.xaml.Behaviors.dll? (#197)
Can you explain how you got to the pinpoint the issue to that specific assembly? Also, can you tell me if this was on a debug or release build?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/microsoft/XamlBehaviors/issues/197#issuecomment-692846023 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AEOMXTD55NW7DBB7PY4Q54DSF6MSFANCNFSM4Q6HVNUA .  https://github.com/notifications/beacon/AEOMXTCUSJ22SL2N7HSQVJ3SF6MSFA5CNFSM4Q6HVNUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFFF73RY.gif

GAC plays no role in UWP... this is a UWP app we are talking here, correct? I ask this as this is the UWP Xaml Behaviors, not the WPF one (that's a different repository!)

Now that I look at the assembly you pointed out, I see that the issue is for the XamlBehaviors for WPF, not this project!
Please open this issue on the correct repo, closing it as it is unrelated to this repo.

This a WPF application.  Definitely not UWP
The DLL is installed as a Nuget package :
It was recommended to me by Infragistics support team
From: Pedro Lamas<EMAIL_ADDRESS>Sent: 16 September 2020 10:01
To: microsoft/XamlBehaviors<EMAIL_ADDRESS>Cc: Gordon Ireland<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/XamlBehaviors] Is there any way to speed up loading Microsoft.xaml.Behaviors.dll? (#197)
GAC plays no role in UWP... this is a UWP app we are talking here, correct? I ask this as this is the UWP Xaml Behaviors, not the WPF one (that's a different repository!)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/microsoft/XamlBehaviors/issues/197#issuecomment-693273611 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AEOMXTAYZG2OEAVJIAIHYK3SGB5DVANCNFSM4Q6HVNUA .  https://github.com/notifications/beacon/AEOMXTCPWRDB3VXYJDGBCJTSGB5DVA5CNFSM4Q6HVNUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFFJIICY.gif

This repo is for the UWP Xaml Behaviors, the assembly you are referring to is from the WPF Xaml Behaviors; please re-open the issue here: https://github.com/microsoft/XamlBehaviorsWpf


Do we have any plans to support adding a new node(peer) dynamically into a nats cluster?

I think present gnats doesn't support adding new node dynamically into a gnats cluster dynamically...
Do we have any plans to support adding a new node(peer) dynamically into a gnats cluster?

Yes, that is next up after this large security release. We will add a gossip protocol for both cluster formation and for client notifications as well. See #126


Face misalignment

Does anyone know what is the problem here? It seems to be very misaligned causing the weird edges. Thanks

I think this was discussed in #8 and #17 and updated on main branch 2 weeks ago?

I think this was discussed in #8 and #17 and updated on main branch 2 weeks ago?

I'm not sure about that, I pulled this repo on June 4th which was less than a week ago. It's also not just about extending the box, the face is much smaller than the actual face, so even if I extend the box to cover the whole width, it's still gonna have a issue at the top and bottom


Update release.php

[x] Bug fix #…?
[ ] New feature?
[ ] BC breaks?
[ ] Tests added?
[x] Docs added?

I'm not sure if this is really a bug or not, but if this line is missing, deployer always tries to deploy as release 1 and doesn't take the contents of the .dep/latest_release file into account

Hey, thanks for your contribution!
May I ask how you found this problem? Because in theory while checking for the release number you should be in the directory 😅

Hi, thanks for your very quick response! I don't know why I'm not in that directory ... I guess I should be in that directory because get('releases_list') is executed directly before get('release_name'), right? Do you have any tips for me on how to further debug that problem?

Just changed the implementation of release_name to the following:
set('release_name', function () {
    $pwd = run('pwd');
    output()->writeln("$pwd");

    cd('{{deploy_path}}');

    $latest = run('cat .dep/latest_release || echo 0');
    return strval(intval($latest) + 1);
});

This outputs /home/deploy

Btw, using deployer v7.0.0-rc.3

Something changes the current directory for you, this must happen before release_name runs. But better safe than sorry. If all test are green, I'm happy to merge it. Thanks for the docgen update!

Let’s use within() here as it may affect different tasks.

@antonmedv changed it

@antonmedv I don't want to bother you, but it would be really great if you could have a look at this again - thanks 🙂

thanks a lot! 😊


Allow separate configuration of bitcoind cookie usage

Feature request:
Background
I'd like to have an option under [bitcoind] where I am able to make LND use a .cookie file at a given location to authenticate to bitcoind.
Your environment
The backend I'm using is bitcoind. LND and components are run in a containerized environment. This allows me to control aspects of networking and authentication on a different scale than regular systems. LND is making me choose between cookie authentication on localhost, or RPC user/pass authentication on a remote host. I would like to have both at the same time.
I would like for LND to consume and use at least these values:

hostname of bitcoind rpc server (container);
port of bitcoind rpc server (container);
path of bitcoind .cookie; (where it's mounted)

Relevant PR: https://github.com/lightningnetwork/lnd/pull/2280.


GT encoder has poor traLoss and traTarLoss

Hello,@xuebinqin thank you very much for your outstanding contributions and sharing on DIS. I encountered a problem while researching and training the GT encoder. The trained GT encoder has poor traLoss and traTarLoss, and the training was interrupted at epoch=10, generating: GTENCODER-gpu_itr_90000_traLoss_2.5166_traTarLoss_0.568_valLoss_0.3852_valTarLoss_0.0118_maxF1_0.9978_mae_0.0009_time_0.035759.pth. In contrast, the model trained without hypar["interm_sup"] = False has higher segmentation accuracy. I would like to ask what might be the reason for this?

When training without the GT encoder supervision, the trained model is gpu_itr_47500_traLoss_0.7772_traTarLoss_0.1048_valLoss_0.395_valTarLoss_0.0206_maxF1_0.9952_mae_0.0022_time_0.067231.pth, which surprisingly performs better than the GT encoder. Here are the comparison images below.


Bootstrap should support existing bucket.

Is your feature request related to a problem?
Pushing content update from terraform code is not common operation from CI/CD.
The content for vmseries update is manage by Security Teams.
Describe the solution you'd like
New bootstrap feature allows to support existing bucket without creating new from bootstrap module.
Describe alternatives you've considered
The bootstrap can be created from scratch using existing solution.

Duplicate of #177


Add "gh secret {list,create}" commands

Included in https://github.com/VirtusLab/scala-cli/pull/926.


Add some Lighteffects :)

Hi Mate I finally got it running. Yeah awesome!! My wife wow effect was just amazing! Thanks mate!
after googleling a bit i found that the author of some lighteffects u used also made some oter effects
https://github.com/atuline/FastLED-Demos
Would u mind to integrate them? I didn't really understand the code.
Would be awesome !!!
THanks for this more than awesome work!!!
Greeting from a happy happy man and also a happy woman from France :) 👍

i am working on it will post my code as soon as i finish probably this week :)

Great news! Thanks! In the meanwhile. Did u already see this project:
https://github.com/doctormord/Responsive_LED_Control

ok so where is the code WITH new added effects??

There is 2 links you have to add these effects to the brug code and the esp code just upload jt to your esp ..

PLease,please lead the blind man.
Which code goes where

HERE IS THE CODE FOR THE ESP
https://pastebin.com/RMPasRAU
AND ADD THESE TO YOUR HOME ASSISTANT CONFIG FILE IN ODDITION TO THE ONES FROM BRUH AUTOMATION  https://pastebin.com/ZLmpYK87

So I just remove the whole old code and add the new one from your file or I'm just adding stuff from the new code into the old one

On your ha config file you have the some effects add the missing ones the your old code and the esp code just use arduino ide and upload it ofc fill your wifi settings in it

Not that i understood your last comment...
I just add the "new effects" in my HA config.yaml and esp file just tree place the whole code with your code. Is this corect?

yes add the extra effect to your config.yaml and on your esp8266 (nodemcu) upload this https://pastebin.com/RMPasRAU
and dont forget to fill your wifi settings :
const char* ssid = "YourSSID"; //type your WIFI information inside the quotes
const char* password = "YourWIFIpassword";
const char* mqtt_server = "your.MQTT.server.ip";
const char* mqtt_username = "yourMQTTusername";
const char* mqtt_password = "yourMQTTpassword";
const int mqtt_port = 1883;
/**************************** FOR OTA **************************************************/
#define SENSORNAME "porch" //change this to whatever you want to call your device
#define OTApassword "yourOTApassword" //the password you will need to enter to upload remotely via the ArduinoIDE
int OTAport = 8266;

i got 1 strip (planing to add 2 more) so thats 300 LEDs so far i discovered :
inoise8mover-only one side lights
easing-doesn't go even half a strip
dotbeat-light on both sides but nothing in the middle
blur -only one side lights
most of effects kinda slugish.. animations speed is fastest
can you come up with solution?

update ! i added 9 more effects codes are on the same links
https://pastebin.com/RMPasRAU
https://pastebin.com/ZLmpYK87

Man this stuff makes sense to me one minute and loses me the next! I thought Hey it should be simple to change the candy cane to blue (matching my Christmas tree)... ive spent the last 30 minutes reading and getting more lost!

Guys im not a programmer i also dont know what i am doing :) i get lost all the time but adding these codes was easy its just add lines to this code from other codes some codes didnt work meany of them has lines in commen and meany i still did not yet because its not easy :)

That's fine and we don't complain or critique. We are grateful for what you are doing and just letting you know that some of the effects don't work. When/if you can ,check them out,if not -no problem. Not rush or obligation. Thank you so far i appreciate.

@sisensee
to change the colors search this line:
  setupStripedPalette( CRGB::Red, CRGB::Red, CRGB::White, CRGB::White);
then change it to your needs
like: setupStripedPalette( CRGB::Blue, CRGB::Blue, CRGB::White, CRGB::White);

Hi everyone
Thanks for this code.
Need somme help, I’m really really novice, I’ve done this project all things run proprelly but, I wouldlike to made an automation witch

Hi everyone
Thanks for this code.
Need somme help, I’m really really novice, I’ve done this project all things run proprelly but, I wouldlike to made an automation witch Will change the light effect every minute for exemple.
Can someone help me with this please...


Customized Plugin Config / Results Widgets

This feature allows us to clean up the Plugin Config / Results UI by using a customized widget instead of the default. It will enable #264

This is now blocking on https://github.com/webgme/webgme/pull/1621


DEX-265 An independent repository

Added "future" package for copy-pasted functionality from master;
Artifact version contains a compatible node's version;
NODE and other removed projects now included as ProjectRef;
"matcher" package is renamed to "dex";
configuration section now is "waves.dex" (was "waves.matcher");
Updated documentation;
Removed NODE-related projects;
Removed unnecessary configuration;

Please use "Create a merge commit" here. We shouldn't lose the history.


pass agent verbosity through to llmchain

before this change, you had to do agent.agent.llm_chain.verbose = True to get the same behavior

@hwchase17: Actually wait.... this would mess up printing. We should think about a better way to do this as this is needed for full tracing.


Extension issue

Issue Type: Bug
Extension Name: python
Extension Version: 2021.2.633441544
OS Version: Darwin x64 16.7.0
VSCode version: 1.52.0

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Thanks for the bug report, but unfortunately we need some more information from you in order to triage this issue appropriately. Please create a new bug by providing a filled-in copy of our issue template.


feat(KMS): derive keys for logs and async

Fixes #2290
Follows #2312

[!CAUTION]
Will nuke logs and async columns!

Uses KMS via tink FTL_KMS_URI, so fake-kms:// or aws-kms:// will work. Omitting will not encrypt.
Remove old plaintext keys envs.

NM our AI overlords fixed it for us!


Hooks

-refactor Calculator.js with hooks
-Update README.md file

@AnselemOdims Thanks a lot for the review and approval!


hipFuncGetAttributes is not working as expected.

cudaFuncGetAttributes(&kernel_attrs, kernel_func);
printf("%d  \n", kernel_attrs.sharedSizeBytes);

works fine with expected output.
hipFuncGetAttributes(&kernel_attrs, HIP_SYMBOL(kernel_func));
printf("%d  \n", kernel_attrs.sharedSizeBytes);

returns a random integer like an uninitialized variable.

Could you please try with https://github.com/ROCm-Developer-Tools/HIP/blob/roc-2.6.x/tests/src/runtimeApi/module/hipFuncGetAttributes.cpp ?

Could you please try with https://github.com/ROCm-Developer-Tools/HIP/blob/roc-2.6.x/tests/src/runtimeApi/module/hipFuncGetAttributes.cpp ?

Thanks, it worked with "reinterpret_cast".


fix: overwrite existing files in storage [ci skip]

Description

Adds --overwrite flag to storage uploads since overwrite behavior is now disabled by default

Testing required outside of automated testing?

[X] Not Applicable

Screenshots (if appropriate):

[X] Not Applicable

Rollback / Rollforward Procedure

[X] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

merge it with chore: ...

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Optimizations in lazy.py

Before:
lazy.py: 0.9059 seconds
tensor.py: 0.4541 seconds
shapetracker.py: 0.3458 seconds
ops.py: 0.2825 seconds
symbolic.py: 0.1162 seconds
helpers.py: 0.0586 seconds

After:
lazy.py: 0.5744 seconds
tensor.py: 0.4551 seconds
shapetracker.py: 0.2559 seconds
helpers.py: 0.2406 seconds
ops.py: 0.2400 seconds
symbolic.py: 0.1097 seconds

Deltas:
lazy.py         -0.33s
shapetracker.py -0.10s
ops.py          -0.05s
helpers.py      +0.19s
Net perf gain = -0.29s

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/codegen/linearizer.py            17              17
tinygrad/graph.py                          7               6
tinygrad/helpers.py                       52               9
tinygrad/lazy.py                         206             153
tinygrad/mlops.py                         37              19
tinygrad/ops.py                           47              23
tinygrad/runtime/lib.py                    4               0
------------------------------------------------------------
total                                    370             227
------------------------------------------------------------
lines added in the tinygrad folder: 143

Cooled down the copy paste, we lost a tiny bit of perf but the lazy ops are much more concise and readable now (apart from permute which has some optimizations that don't apply to other ops). We lost a tiny bit of perf but nothing crazy

Filename
Before
After
Delta

lazy.py
0.90s
0.59s
-0.31s

tensor.py
0.45s
0.44s
not stat-sig

ops.py
0.28s
0.23s
-0.05s

shapetracker.py
0.34s
0.22s
-0.12s

helpers.py
0.05s
0.22s
+0.17s

symbolic.py
0.11s
0.14s
+0.03s

TOTAL
2.13s
1.84s
-0.29s

Readability of movement ops looks good.
My main concern now is the addition of buffers to LazyOp. This puts state in two places, both in src and buffers. Can this be a cached method instead?

Actually this only solves half of the battle, the other half is attribute accesses. We can get around that with having @property stubs but then it gets a bit ridiculous and we end up with something like this in the LazyOp class:
def realize(self): raise NotImplementedError
def reduce_op(self, _): raise NotImplementedError
def reshape_op(self, _): raise NotImplementedError
def pad_op(self, _): raise NotImplementedError
def expand_op(self, _): raise NotImplementedError
def permute_op(self, _): raise NotImplementedError
def shrink_op(self, _): raise NotImplementedError
def stride_op(self, _): raise NotImplementedError
@property
def children(self): raise NotImplementedError
@property
def realized(self): raise NotImplementedError
@property
def shape(self): raise NotImplementedError
@property
def st(self): raise NotImplementedError
@property
def src(self): raise NotImplementedError
[a few more of these...]

I'm not quite sure what's preferable between

Disabling type checking in lazy.py in favor of having code completion
Reverting to Any and content with no completion

My gut feeling says 1. because lazy.py is entirely internal APIs so we don't break anything for end-users by playing fast and loose with types and i feel like the QoL of having completion outweighs having 100% sound typing
In the long term we probably don't actually need separate classes for LazyOp and LazyBuffer, i think it can all live under LazyBuffer and that would solve all the typing shenanigans

I actually don't mind 25 lines of stubs. It's a good way to start thinking about merging the classes.

Update on this, working on merging LazyOp and LazyBuffer into one, should give us a net saving in nlines and probably some additional perf as well

Cool, I'm curious to read it. My distinction was two fold.
LazyBuffer has a ShapeTracker. LazyBuffer can be realized. LazyOp doesn't and can't.

Maybe for now we should just merge this with the stubs? So it doesn't go stale.

Updated with stubs and addressed the thing about graph imports

Sweet, going to merge!
master:
codegen         mean runtime:  149.24ms, runs:   158.54,  146.31,  154.19,  150.24,  168.12,  143.27,  142.01,  142.79,  143.06,  143.87
methodcache     mean runtime:  141.55ms, runs:   158.67,  136.71,  136.79,  136.77,  136.66,  136.63,  165.18,  135.95,  135.75,  136.37
profile         mean runtime:  577.50ms, runs:   612.50,  595.11,  596.83,  554.52,  554.58,  562.47,  563.12,  568.43,  596.47,  571.01

this branch:
codegen         mean runtime:  103.21ms, runs:   186.60,   90.75,   90.47,   90.88,   90.44,  115.21,   91.01,   92.16,   91.96,   92.64
methodcache     mean runtime:   91.17ms, runs:    81.05,  111.85,   88.09,   88.08,   86.29,   85.49,   85.24,  113.39,   85.95,   86.26
profile         mean runtime:  362.23ms, runs:   401.66,  356.05,  346.72,  363.68,  376.81,  361.58,  352.67,  354.32,  356.23,  352.55

Is there more from #812?
I'm seeing 109.27 ms for the whole thing on my M1 Max

Yeah a couple more minor things, PR coming


Typo in documentation

Description
The following documentation has a minor typo
ain -> main
https://kedro-mlflow.readthedocs.io/en/stable/source/04_experimentation_tracking/01_configuration.html#context-mlflow-tracking-under-the-hood

Closed by #376


feat: use tier4_sensing_launch instead of sensing_launch

PR Type

Improvement

Related Links
https://github.com/tier4/autoware_launch/pull/308
Description

use tier4_map_launch in autoware.universe
avoid editing tier4_sensing_launch and sensing_launch when some changes are occurred.

Review Procedure

launch logging_simulator$ ros2 launch autoware_launch logging_simulator.launch.xml map_path:={path_to_map} vehicle_model:=lexus sensor_model:=aip_xx1

Confirm some sensor nodes are launched$ ros2 node list | grep sensing
/sensing/gnss/gnss_poser
/sensing/gnss/transform_listener_impl_563ad9eef388
/sensing/imu/imu_corrector
/sensing/lidar/concatenate_data
/sensing/lidar/left/crop_box_filter_mirror
/sensing/lidar/left/crop_box_filter_self
/sensing/lidar/left/pointcloud_preprocessor/transform_listener_impl_55c0db5f86b8
/sensing/lidar/left/pointcloud_preprocessor/transform_listener_impl_55c0db63c6b0
/sensing/lidar/left/pointcloud_preprocessor/transform_listener_impl_55c0db6e3eb0
/sensing/lidar/left/pointcloud_preprocessor/transform_listener_impl_55c0db84b5d0
/sensing/lidar/left/pointcloud_preprocessor/velodyne_node_container
/sensing/lidar/left/ring_outlier_filter
/sensing/lidar/left/velodyne_convert_node
/sensing/lidar/left/velodyne_interpolate_node
/sensing/lidar/rear/crop_box_filter_mirror
/sensing/lidar/rear/crop_box_filter_self
/sensing/lidar/rear/pointcloud_preprocessor/transform_listener_impl_556482feb910
/sensing/lidar/rear/pointcloud_preprocessor/transform_listener_impl_5564830429b8
/sensing/lidar/rear/pointcloud_preprocessor/transform_listener_impl_5564830a0650
/sensing/lidar/rear/pointcloud_preprocessor/transform_listener_impl_55648320a570
/sensing/lidar/rear/pointcloud_preprocessor/velodyne_node_container
/sensing/lidar/rear/ring_outlier_filter
/sensing/lidar/rear/velodyne_convert_node
/sensing/lidar/rear/velodyne_interpolate_node
/sensing/lidar/right/crop_box_filter_mirror
/sensing/lidar/right/crop_box_filter_self
/sensing/lidar/right/pointcloud_preprocessor/transform_listener_impl_55566669ce00
/sensing/lidar/right/pointcloud_preprocessor/transform_listener_impl_55566672fdb0
/sensing/lidar/right/pointcloud_preprocessor/transform_listener_impl_555666776af8
/sensing/lidar/right/pointcloud_preprocessor/transform_listener_impl_5556668523c0
/sensing/lidar/right/pointcloud_preprocessor/velodyne_node_container
/sensing/lidar/right/ring_outlier_filter
/sensing/lidar/right/velodyne_convert_node
/sensing/lidar/right/velodyne_interpolate_node
/sensing/lidar/top/crop_box_filter_mirror
/sensing/lidar/top/crop_box_filter_self
/sensing/lidar/top/pointcloud_preprocessor/transform_listener_impl_7f8988051100
/sensing/lidar/top/pointcloud_preprocessor/transform_listener_impl_7f89880e0350
/sensing/lidar/top/pointcloud_preprocessor/transform_listener_impl_7f89940e6f00
/sensing/lidar/top/pointcloud_preprocessor/transform_listener_impl_7f8998064e80
/sensing/lidar/top/pointcloud_preprocessor/transform_listener_impl_7f89a8006c08
/sensing/lidar/top/pointcloud_preprocessor/transform_listener_impl_7f89a807d3a0
/sensing/lidar/top/pointcloud_preprocessor/transform_listener_impl_7f89b45f4db0
/sensing/lidar/top/pointcloud_preprocessor/velodyne_node_container
/sensing/lidar/top/ring_outlier_filter
/sensing/lidar/top/velodyne_convert_node
/sensing/lidar/top/velodyne_interpolate_node

Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Code follows coding guidelines
[x] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code follows coding guidelines
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR: Required to pass before the merge.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

It is good if it is not necessary to customize in our company.

@yukkysaito The sensing.launch.xml calls each product sensing.launch.xml, so I believe that there are no product dependency.
However, I agree with you that this PR should be reviewd by team leaders.

@kenji-miyake @yukkysaito @tkimura4 @yn-mrse @0x126 I fixed exec_depend. Could you review again?