Use of different LoadTestShape in the same locust file

Describe the solution you'd like
Customers need to periodically check if they can scale their web applications X times the current volume of requests per second to plan for scalability.
Thus, an observability tool is used to obtain throughput and latency SLAs, and the values obtained are used as a baseline to validate the ability to scale.
For this, it would be necessary, in the same test package, to have different users that run different tasks sets, with different LoadShapes, as in the example below:
from locust import (
    HttpUser,
    LoadTestShape,
    constant_throughput,
    task,
    SequentialTaskSet
)

class ProductShape(LoadTestShape):
    user_count = 1000
    spawn_rate = 1000

    def tick(self):
        return (self.user_count, self.spawn_rate)

class OrderShape(LoadTestShape):
    user_count = 100
    spawn_rate = 100

    def tick(self):
        return (self.user_count, self.spawn_rate)

class ProductTaskSet(SequentialTaskSet):

    @task
    def get_home(self):
        self.client.get("/products/")

class OrderTaskSet(SequentialTaskSet):

    @task
    def get_home(self):
        self.client.get("/orders/")

class ProductSearchUser(HttpUser):
    shape = ProductShape
    wait_time = constant_throughput(0.1)
    tasks = [
        ProductTaskSet,
    ]

class OrderSearchUser(HttpUser):
    shape = OrderShape
    wait_time = constant_throughput(0.5)
    tasks = [
        OrderTaskSet,
    ]

I was able to test scalability using just one LoadTestShape class, independently calculating the target troughput of each task, for a given target scale, using the function constant_throughput_at_scale(throughput).
from locust import (
    HttpUser,
    LoadTestShape,
    constant_throughput,
    task,
    SequentialTaskSet
)

time_limit = 120
scale = 10
user_classes_count = 2
users_per_class = 100

class ScaleTestShape(LoadTestShape):
    user_count = user_classes_count * users_per_class
    spawn_rate = user_classes_count * users_per_class

    def tick(self):
        run_time = self.get_run_time()

        if run_time >= time_limit:
            return None

        return (self.user_count, self.spawn_rate)

class ProductTaskSet(SequentialTaskSet):

    @task
    def get_home(self):
        self.client.get("/products")

class OrderTaskSet(SequentialTaskSet):

    @task
    def get_home(self):
        self.client.get("/orders")

def constant_throughput_at_scale(throughput):
    return constant_throughput(throughput * scale / users_per_class)

class ProductSearchUser(HttpUser):
    throughput = 0.67 #  SLA obtained in observability tool
    wait_time = constant_throughput_at_scale(throughput)
    tasks = [
        ProductTaskSet,
    ]

class OrderSearchUser(HttpUser):
    throughput = 2.5 #  SLA obtained in observability tool
    wait_time = constant_throughput_at_scale(throughput)
    tasks = [
        OrderTaskSet,
    ]

As we can see, the final throughput in the report (req / s) is 10 x (target scale) the SLAs.


RMN-doc-issues - Multiple documentation issues

Made changes in the documentation as per the Issues reported below:
https://github.com/suse-edge/suse-edge.github.io/issues/330
https://github.com/suse-edge/suse-edge.github.io/issues/337
https://github.com/suse-edge/suse-edge.github.io/issues/353
https://github.com/suse-edge/suse-edge.github.io/issues/301
https://github.com/suse-edge/suse-edge.github.io/issues/256
https://github.com/suse-edge/suse-edge.github.io/issues/348

@hardys I have combined multiple issues and created one PR. Can you please review? Thanks

Thanks @ranjinimn will review!  I think you have to add Fixes: #NNN to the description to auto-close the related issues.
For future PRs I would suggest adding several commits, e.g one commit fixing each issue as it will be easier to review, no need to un-squash this branch though :)

Sure, I will make a note of that. :)


[BLOCKING] Make CMakeLists.txt compatible with CMake 3.3

Export OpenMP as a PUBLIC target
Upgrade CMake to 3.3, to use the generator expression COMPILE_LANGUAGE:CXX. For the same reason, require CMake 3.11 for Visual Studio
Use CMake 3.3 in the build-cpu task of Jenkins
Remove -funroll-loops flag when compiled with MSVC

Closes #4415

Closing for now. I've made things quite too complicated. OpenMP doesn't really need to be a target


suggestions for cutoff scores when using the pre-trained model

In the DeepMased-publication two cutoff scores are mentioned: "conservative" and "relaxed". I would assume, when running DeepMasEd based on the provided pre-trained Model, I could use the same cutoff-scores as a rough starting point?
However i can't seem find concrete values for these cutoff scores in the publication or supplementary material.
Could you provide some suggestions for possible cutoff scorers when using the pre-trained models?

Thanks @jvollme for your interest in DeepMAsED! I advise you to use ResMiCo instead of DeepMAsED, given that it will generalize much better to novel data, especially with our recent updates to the model (the updated manuscript is soon to be published).

Thanks I will definitely try it out. However, since I already have made the calculations with deepmased, would it still be possible to provide a rough ballpark for reasanoble score cutoffs when using deepmased?

I definitely recommend re-doing the calculations with resmico. If you still have the BAM files, then it should be very fast & straight-forward.
With that said, I recommend assessing the AUCPR curves in the DeepMAsED and ResMiCo papers to determine the appropriate cutoff for your particular needs (high precision vs high recall).

I am sorry but i am afraid i am a bit too dumb: These curves plot precision against recall values. But where do i see which specific score cutoffs are associated with which recall and/or precision value? Just from these plot i don't seem to be able to determine any specific score cutoffs...

Hi @jvollme,
That is a very good question! Indeed, exact cutoffs are not given in the DeepMAsED paper. They are 0.145 and 0.308. Thank you for asking.

thanks!


Stranger1992/bass engine upgrade

Updated UnReal bass engine to 2.4.17 ( https://www.un4seen.com/ )
bass updated dll.zip
Also added in the ability for TEN to use sound samples at 44.1khz instead of 22.5khz if they are present.

I have removed all commits with my controversially incorrect code. The commits that remain are just the updated header files


Make sure second registry is loaded from config in Fluid Transformer

There is an "internal" Map of String -> FluidTransformer, input fluid -> transformation data, in registries.FluidTransformRegistry that isn't initialized from the loadJson method. One fix is simply iterating through gsonInput (aka registry), and registering each one into registryInternal.
Example:
...
registry = gsonInput;
for(FluidTransformer transformer : gsonInput)
registryInternal.put(transformer.getInputFluid(), transformer);
...
Obviously there are other ways of doing this, this is the way that came to my mind.
Good luck modding!

Thanks :-)


Fix: Empty sets not removed from item after UpdateExpression

DynamoDB does not support empty sets.  If the last item in a set is
deleted as part of an UpdateExpression, the attribute must be removed.
Ref: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.NamingRulesDataTypes.html
Fixes #3296

Coverage decreased (-0.3%) to 94.156% when pulling 23c78319fd02fbcf4d8301ab7f89a0d873efab62 on bpandola:fix-3296 into ea19466c381184a2bbfab946deaf982e33fc850c on spulec:master.


animation doesn't match value

After the animation ends, the value received does not match the previously set start postion

@sh-khashimov can you help me?


Run code by NodeJs

Hello,
How to run this code by nodejs without browser?

Hi @asedali,
To run Node.js code, you don't need a browser. You can do it using your terminal or command prompt. Here are the steps to follow:

Open a Terminal or Command Prompt: Make sure you have a terminal or command prompt open.

Navigate to Your Code's Directory: Use the cd command to navigate to the directory where your JavaScript file is located. For example:
cd /path/to/your/code

Run the Code: To run your Node.js script, use the node command followed by the filename:
node app.js

Remember to replace app.js with the actual name of your JavaScript file. This command will execute your Node.js code.

View Output: If your code produces any output (e.g., console.log statements), you'll see it in the terminal/command prompt.

Node.js is designed for server-side and command-line scripting, so it doesn't require a browser to run. It's a versatile platform that allows you to build various applications, from web servers to standalone scripts.
You could alternatively install xmrig. You can find the installation instructions in this repository: xmrig-install. Please follow the instructions provided there to install xmrig.
If you have any more questions or need further assistance, feel free to ask.
Thanks, Najm Ajmal


Can't read xlsm-file

Is xlsm format supported?
I open a document, but I get an error when calling Worksheet ("Sheet1")
Error text:
terminate called after throwing an instance of 'std :: invalid_argument'
   what (): stoul
Process finished with exit code 134

Is it possible to do xlsm-files support?

Hi @And-Rik
I don't get an error when opening an xlsm file. Here's what I tried:
I created an .xlsm file with a simple VBA script, that shows a messagebox when opening the workbook (GitHub don't allow xlsm files to be uploaded, so please xhange the file extension to .xlsm after downloading):
WorkbookWithMacro.xlsx
Then I run the following C++ code with OpenXLSX:
#include <iostream>
#include <iomanip>
#include <OpenXLSX/OpenXLSX.h>

using namespace std;
using namespace OpenXLSX;

int main() {

    XLDocument doc;
    doc.OpenDocument("/Path/To/Spreadsheet/WorkbookWithMacro.xlsm");
    auto wks = doc.Workbook().Worksheet("Sheet1");

    wks.Cell("A1").Value() = 3.14159;
    wks.Cell("B1").Value() = 42;
    wks.Cell("C1").Value() = "  Hello OpenXLSX!  ";
    wks.Cell("D1").Value() = true;
    wks.Cell("E1").Value() = wks.Cell("C1").Value();

    auto A1 = wks.Cell("A1").Value().Get<double>();
    auto B1 = wks.Cell("B1").Value().Get<unsigned int>();
    auto C1 = wks.Cell("C1").Value().Get<std::string>();
    auto D1 = wks.Cell("D1").Value().Get<bool>();
    auto E1 = wks.Cell("E1").Value().Get<std::string>();

    auto val = wks.Cell("E1").Value();
    cout << val.Get<std::string>() << endl;

    cout << "Cell A1: " << A1 << endl;
    cout << "Cell B1: " << B1 << endl;
    cout << "Cell C1: " << C1 << endl;
    cout << "Cell D1: " << D1 << endl;
    cout << "Cell E1: " << E1 << endl;

    doc.SaveDocument();

    return 0;
}

This works as expected.
Can you send me the code you use, along with the .xlsm file that fails?
Also, what compiler/platform do you use? Clang/GCC/MSVC, Windows, MacOS, Linux?

Yes, that is right.
On simple xlsm files, everything works. I had an error on only one file, which I can’t forward yet because of the privacy policy. It is surprising that when I save it again, the error does not repeat. I will analyze the file structure.
Thanks for the answer.


Flink files for streamingFileSink

Allow the class to be public instead of private.

There's a solution now which does not require changing Flink upstream.

@tweise: This is a WIP branch. Not planning on merging this. You can ignore this
PR for the time being. Will come back to this along with going on the correct process to upstream this change.


Blank page without a saved api key

** Supporting Details **
Provide the following:

Browser Version: Google Chrome
Headscale Version: the last one
Any Browser Errors (control+shift+i in chrome to see)

Describe the bug
I just upgraded to last version, finally it works.
Unfortunately if you try to open it in a browser where there isn't a key saved (or in incognito mode), it only shows a blank screen without any error in console.
Can you please check?
Thanks

This is what I get when I open up incognito:

Sorry, my fault. It was just a misconfiguration in the root path of the domain.
Thank you.


Scrolling over a video on mobile devices causes the video to start playing

Video starts playing on "touchstart" event on mobile devices.
MediaElement can't differentiate between tap and scroll.
Below is the workaround I used to get it to work right on mobile devices:
var isScrollOverVideo=false;
$(".mejs-overlay-play").on("click", function (e) {
$(this).closest(".videoBorder").find("video")[0].play();
});
$(".mejs-overlay-play").on("touchmove", function (e) {
isScrollOverVideo = true;
});
$(".mejs-overlay-play").on("touchend", function (e) {
if (isScrollOverVideo) {
isScrollOverVideo = false;
} else {
$(this).closest(".videoBorder").find("video")[0].play();
}
});
$('video').click(function () {
this.paused ? this.play() : this.pause();
});

@andreibaracuda Can you provide a URL so we can check this?

Closing this issue since no answer has been posted in more than 2 weeks. If you'd like to reopen this, let us know. Thanks!


fix(batch): remove task metrics after task finishes and ensure metrics are collected

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

Checklist For Contributors

[x] I have written necessary rustdoc comments
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Checklist For Reviewers

[x] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation

[x] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

Duplicate of #9378


tcp fast open error

[2020-12-29 01:46:20] [FATAL] fatal: /usr/local/etc/trojan/config.json(38): expected value
I removed line 38 and now its working again.

fixed


fix: register application webhook

see: https://gravitee.atlassian.net/browse/GKO-506

I really think this should be rebased after https://github.com/gravitee-io/gravitee-kubernetes-operator/pull/769 has been merged (It contains a commit that fixes the tests)


VERSIONDATE does not get replaced in tikz-trackschematic.sty

In all bash scripts (except create-release.sh) the replacement of VERSIONDATE is missing.
This breaks the scripts.
https://github.com/railtoolkit/tikz-trackschematic/blob/6dc00facc4d11a92a4761d214c6d7be1cf9fec5e/src/tikz-trackschematic.sty#L8

It is probably about line 194 in the shell script, but I can't understand your error at the moment: can you please provide more context? In particular, which "sed" version do you have, which OS are you using?
What does "sed --version" return?
sed is actually a bit problematic because there are many implementations. I have only tested it on Ubuntu in github actions and on a BSD. Have a look at lines 42 to 45 in the shell script as well.

When I execute pdflatex I get this error:
(/usr/local/share/texmf/tex/latex/local/tikz-trackschematic-dev/tikzlibrarytrackschematic-dev.code.tex)
! Missing = inserted for \ifnum.
<to be read again>
                   V
l.9

I can solve this by removing [VERSIONDATE tikz-trackschematic] completely or replacing VERSIONDATE it with a valid date.
This issue is discussed here: https://tex.stackexchange.com/questions/274650/missing-inserted-for-ifnum

Fixed issue with https://github.com/railtoolkit/tikz-trackschematic/commit/83a0a6f2ec573d53064c93ff1a5dd431155738af


Azure Logic Apps are not available for Azure Event Grid as documented

Documentation in the Azure portal and docs both show that we can use Azure Logic Apps to receive events, but you cannot select them from the endpoint list.

@atavallai
Please help with the link of document on which above document feedback request is created.
In case your query in not related to document content, open a new forum thread in MSDN forum or Stack Overflow as it could be better place to get help on your scenario. These forum community members could provide their expert guidance on your scenario based on their experience. Thanks.

Sorry, here are some links:
https://docs.microsoft.com/en-us/azure/event-grid/overview
https://azure.microsoft.com/en-us/services/event-grid/#overview
It's also referenced on the "Events" pane of a storage account in the portal:

But when you try and set up an event subscription, it's not in the drop down list:

Shows it's supported, you would need to use the Logic Apps interface and Event Grid Trigger, see links.  Perhaps Web Hook should be copied as Logic Apps in the Endpoint Details dropdown.
https://docs.microsoft.com/en-us/azure/event-grid/monitor-virtual-machine-changes-event-grid-logic-app
https://docs.microsoft.com/en-us/azure/event-grid/publish-iot-hub-events-to-logic-apps
https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-to-event-grid-integration-example?toc=%2Fazure%2Fevent-grid%2Ftoc.json&tabs=v2

I think we have this working now. So we don't need to set it up in Event Subscriptions section of the storage account.
We had tried just adding the Event Grid trigger yesterday with no luck, so then we assumed you had to do something with Event Subscriptions. However, we just tried it again and it works as expected.
Thank you all for your help.


Add files via upload

@Be-force Please provide us with an URL of a page on the official website where an IT-related long-term (>1 year) course is offered by the school. Thank you.

@Be-force You might miss my previous comment. Please react.

@Be-force I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the abovementioned issue. Thank you for the understanding!


[Feat] : Adding the same footer to "Beginner-Friendly Repos" page

feature

Adding the same footer seen on main page to "Beginner-Friendly Repos" page.

hey @Sriparno08 assign me this issue under JWOC

Assign me this under the label easy or medium

@Ananyamishra08 You're assigned.


[DS-3909] Added patch and withdraw methods to the item repository.

Also at Andrea Bollini's suggestion added eperson to the context object in the authentication filter.  https://github.com/4Science/DSpace/commit/2717b56557275ac05c66dea2d3c22238ad79c176 We made this change to see if it solves the authentication problem when updating the item withdrawn status. It may be temporary.
Minor edit.

This PR has been replaced/superseded by #2064.  Closing.


Generate a const array

Use bufconst to generate a const string. Fix issue 62

Done. Thanks for your advice about the commit.

Besides constant embed strings we also have variable strings (for example, see salg_type). Currently they have hardcoded support in prog package, but I would like to move them to sys files, so that people can add new similar types without touching prog package.
Adding trailing int8 array to ensure necessary buffer size does not look like a good solution, and it won't work at all for variable strings because their length is not known in advance.
I am thinking about something along the following lines:
Add type string that is always embed, i.e. no indirection implied.
It has 1 mandatory option that is either a quoted string for constants (string["wlan0"]) or refers to a new "string flags" type for variable strings:
string[slag_type]
slag_type = "des", "aes", "des3"

By default size of such type is equal to length of the string (including the terminating \x00). But it can be given the second option that specifies the size of the underlying buffer:
string["wlan0", 64]
string[slag_type, 48]
slag_type = "des", "aes", "des3"

Variable-length strings can only be used as fields of packed structs. Constant-length strings (either (1) a constant string, or (2) with explicit size, or (3) all string values are of the same size) can be used as fields of normal structs as well.
We can introduce a helper stringptr[...] type that is a shortcut for ptr[in, string[...]]. But maybe it's better to just spell it explicitly. Later we will probably have "string resources", so we will need out string pointers. For example:
resource foo_name: string["", 64]
ioctrl$create_something(..., arg ptr[out, foo_name])
ioctl$destroy_something(..., arg ptr[in, foo_name])

I've merged changes that provide full support for string buffers:
https://github.com/google/syzkaller/commit/5ed6283b64f91c8aa036122b18974aabed4c5249
https://github.com/google/syzkaller/commit/588a542b2a23ba477031bf20b4c46b0f40a04b7d
https://github.com/google/syzkaller/commit/3a65453870b12f5c42739c27d99df8fc58358f88
In short, string don't imply pointer indirection anymore. You can say:
ptr[in, string]
or just:
string
You can also say:
string["foo"]
or:
string[my_set_of_strings]
my_set_of_strings = "a", "bb", "ccc"
And you can specify string buffer as:
string["foo", 64]
string[my_set_of_strings, 64]
Please check if it works for you.
Closing this pull request.
Thanks for bringing up this problem


fix(form-field-range): Fix console error on updatePosition before componentWillLoad

✅ Closes: COMUI-2970

I was just wondering do you have some markup that I can use to display the error ?

I was just wondering do you have some markup that I can use to display the error ?

I couldn't find a reliable way. I set up an angular 18 playground and tried to do it that way but it wasn't really present. I ended up just commenting out the setInput in componentWillLoad so I could see how the defaults were used in updatePosition.

Seems like a timing issue as for me the componentWillLoad always executes before the OnResize decorator.


matrix-synapse: fix documentation

cc @jtojnar @florianjacob from the git blame.
My synapse deployment would work properly only with this change, but pinging you to check whether you have the same thing or it's some other configuration difference that forced me to add that. :)

I only touched the manual for cleanups and do not run Synapse but it looks to me like a typo.

I'm running a synapse instance without the proposed change - works swimmingly.

I run it without the suffix as well, and took it from the official documentation: https://github.com/matrix-org/synapse/blob/master/docs/reverse_proxy.rst
@Ekleog My guess would be that you don't have the proxy_set_header X-Forwarded-For $remote_addr; as in the upstream documentation and this is what's allowing nginx to work without the suffix. This header line is added by having services.nginx.recommendedProxySettings = true;, do you have that setting? I admit though that the block of recommended*Settings in the manual is easy to miss, and it probably doesn't get across that Proxy and Gzip are really not optional for the whole thing to work.

@florianjacob Unfortunately, I do have it set to true, and nixos-option services.nginx.recommendedProxySettings confirms my config file, so something else must be at play. I'm on 19.03, which is on <IP_ADDRESS>, maybe there is a link with something changing between versions?

I'm on 19.03, which is on <IP_ADDRESS>, maybe there is a link with something changing between versions?

I doubt it. I have been running it since the 0.2x.y days and running on 1.0.0 on 19.03.

That is weird. I've just checked my configuration, and in stuff that should concern synapse, the differences are:

I set the virtualHosts.*.listen option so that nginx listens on only one of my two IPs
I add proxyWebsockets = true alongside proxyPass = "..." (not sure it's required but it was there since a long time ago, so I guess it may be useful for something, and shouldn't break stuff
I use ipv4 localhost instead of ipv6, both in proxyPass and in matrix-synapse.listeners.0.bind_address (old-fashioned me)
I have matrix-synapse.public_baseurl set

None of these should, AFAIU, be able to change the observable behavior. At this stage I can see little options other than some weird upstream bug that I don't have time to track for now.
@peterhoeg Can I ask you to test on your server with the /_matrix addition? If it works for you too maybe it's better to just document the way that appears to work for everyone until the “why” can be sorted out?

It still works here if I add the /_matrix.

Just stumbled over this change in the synapse nginx documentation referencing a thing called “nginx uri canonicalization / normalization” - @Ekleog you did not have a trailing slash sneaking into your proxy_pass, did you? ;)
Generally we should write an integration test for the full setup described in the manual, for cases like this as a reproducible foundation to be able to split apart side effects from people's specific setups and actual bugs in the manual / software, and to detect breakage on updates of the related software.
My perl and general knowledge of NixOS testing facilities is bad, but I guess I'll eventually try that if no one else is faster.

Looking up my git history, I totally had a / that sneaked in. Thank you! Just pushed 5f33bcd953a17c903e407e6a5fce51039bae239c to rollback this change and make the need for absence of the / explicit :)

@Ekleog Great, I'm glad we were able to find the root cause. :) :+1:


Update verbosity call in sc.external.tl.phate

The phate too makes a call to a function named _settings_verbosity_greater_or_equal_than(), which appears to no longer exist, preventing phate from running at all.  I exchanged that call for a simple comparison that yields what I believe the old function returned.  In any case, the change results in phate being able to run.

Thank you!


Prevent errors parsing misformated project using default values

Resolves https://github.com/xcodeswift/xcproj/issues/101
Short description 📝
Assign default values to those values that are missing. By doing that, we allow developers open their projects and update them. To verify that the format is correct, they could use xclint and run it before saving their projects.
Solution 📦
Update the objects init method and their respective tests.
Implementation 👩💻👨💻

[x] Update constructors.
[x] Update tests.

GIF

Oh I don’t think it’s a good idea to assign default value for missing value.❌

@toshi0383 there's an open discussion on this issue. The problem by throwing errors if the properties are missing is that developer is not able to fix those issues because the project doesn't get parsed. We could solve it by using optionals, but we think that working with optionals will make all the code more verbose, full of if guard statements.
This change would be complemented with the xclint validator that the developer can use to make sure all the properties are valid.

Yea I saw that conversation. This is my opinion.

By default xcproj should fail parsing on missing required field. (throw error)
To make xclint to work with invalid pbxproj, we should be able to inject different Decoder from outside of xcproj framework.

Why do you think xcproj should fail the parsing? Projects generated by the Swift Package Manager cannot be read with xcproj, however, they can be opened with Xcode. They don't seem to be invalid for Xcode but they are xcproj. I see this very confusing for a developer using the tool. Let's say that I want to read my project to do some changes, and I get an error.

In general, a Parser should fail on unexpected structure. Setting default value for missing value is unexpected behavior for a Parser. Do we agree on this?
I think it's okay to make some fields Optional for SPM compatibility. If Xcode succeeds to open, xcproj should too.

So the solution should be "Make some fields optional for SPM compatibility", not "Assign default values to those values that are missing".

The rule to decide the optionality of an attribute could be, is Xcode able to handle a nil value for a given property? What do you think @esttorhe / @yonaskolb

I agree with @toshi0383; maybe we shouldn't assign a default value if missing except nil as long as Xcode can handle the missing value.
If Xcode can't handle the missing value we should fail the parsing.
Or if we want to go the extra mile provide an optimistic parsing that will add a default value to the missing fields (kind of like Xcode does)

Closing the PR. I opened another one where I'll tackle this differently based on your suggestions. I'll review the optionality of the values using Xcode.


[T3A4][T15-A4]AngShiYa

Ready for review

@AngShiYa

The error handling was expected in the save method (in StorageFile class) and not directly in the executeCommand method (in Main class).
You need to throw the error till the Main class, where you should call the function you created in the Textui class to print the error message.


Update about-releases.md

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[x] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Explanation why do I am explanation
On Tue, Jan 11, 2022, 08:36 github-actions[bot] @.***>
wrote:

Automatically generated comment ℹ
This comment is automatically generated and will be overwritten every
time changes are committed to this branch.
The table contains an overview of files in the content directory that
have been changed in this pull request. It's provided to make it easy to
review your changes on the staging site. Please note that changes to the
data directory will not show up in this table.
Content directory changes
You may find it useful to copy this table into the pull request summary.
There you can edit it to share links to important articles or changes and
to give a high-level overview of how the changes in your pull request
support the overall goals of the pull request.
Source Staging Production What Changed
content/repositories/releasing-projects-on-github/about-releases.md
https://github.com/github/docs/blob/f6bbde5c40876c5e82b898dc1f2f819cdde65e4f/content/repositories/releasing-projects-on-github/about-releases.md
Modified
https://docs-13929--patch-25.herokuapp.com/repositories/releasing-projects-on-github/about-releases
Original
https://docs.github.com/repositories/releasing-projects-on-github/about-releases
—
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/13929#issuecomment-1009556324, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AXHTBDYWTHDZ237OT5K6EMDUVONDFANCNFSM5LVGJWXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


⚠ Bofrost.com has degraded performance

In 3d582f2, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 1075 ms

Resolved: Bofrost.com performance has improved in 58fd148.


Clone of #611: Codecept/Nightmare (3.0.0) Helper Issues: _locate method can't find element in DOM

This was fixed last year (issue 611). Would appreciate if someone could verify whether _locate works in Nightmare 3.0.0?
What are you trying to achieve?
Locate an element in the DOM, and access its attribute values.
What do you get instead?
Trying to access an element in the DOM, but nightmare is not able to locate it.
• I click "#logout"
   Emitted | step.passed (I click "#logout")
   Step finished in 0.532 sec
   Emitted | step.start (I wait for element ".alert", 5)
 • I wait for element ".alert", 5
   Emitted | step.passed (I wait for element ".alert", 5)
   Step finished in 0.284 sec
   Emitted | step.start (I wait 5)
 • I wait 5
 > log: SAOrion: JWT token not found. Exiting
   Emitted | step.passed (I wait 5)
   Step finished in 5 sec
   Emitted | step.start (I see attribute contains ".alert", "innerHTML", "Signed out successfully.")
 • I see attribute contains ".alert", "innerHTML", "Signed out successfully."
null
   [1] Error | AssertionError: object tested must be an array, a map, an object, a set, a string, or a weakset, but null given
   Emitted | step.failed (I see attribute contains ".alert", "innerHTML", "Signed out successfully.")
   Step finished in 0.011 sec
   [1] Error | AssertionError: object tested must be an array, a map, an object, a set, a string, or a weakset, but null given
``` End debug output

> Provide test source code if related
'use strict'

let Helper = codecept_helper

class MyHelper extends Helper {
     async seeAttributeContains(locator, attribute, expectedValue) {

         // let's use chai assertion library
         const assert = require('chai').assert;

         // get nightmare instance
         const browser = this.helpers['Nightmare'].browser;

         // get the element
         const el = await this.helpers['Nightmare']._locate(locator);

         // get the element value
         const attributeValue = await browser.evaluate( (ele, attr) => {
             return codeceptjs.fetchElement(ele).getAttribute(attr);
         }, el, attribute);

         console.log(attributeValue)

         assert.include(attributeValue, expectedValue);
     }
}

module.exports = MyHelper

#### codecept.json
{
    "tests": "./tests/*_test.js",
    "timeout": 10000,
    "output": "./output",
    "helpers": {
        "Nightmare": {
            "url": "https://access.dev.secureauth.com/246/users/sign_in",
            "show": true,
            "waitforTimeout" : 100000,
            "desiredCapabilities": {
                "browserName": "chrome",
                "chromeOptions": {
                    "args": "['start-maximized']"
                }
            }
        },
        "MyHelper" : {
            "require" : "./common/codeceptjsCommon.js"
        }
    },
    "include": {
       "I": "./steps_file.js"
    },
    "bootstrap": false,
    "mocha": {},
    "name": "p77"
}

package.json (showing what all is installed)
{
  "dependencies": {
    "chai": "^4.1.2",
    "co": "^4.6.0",
    "codeceptjs": "^1.1.6",
    "nightmare": "^3.0.0",
    "nightmare-har-plugin": "^0.9.1",
    "nightmare-upload": "^0.1.1",
    "unirest": "^0.5.1",
    "webdriverio": "^4.12.0"
  }
,"scripts": {"test":"mocha tests/*.js"}, "license": "MIT", "name": "cloudAccess", "version": "0.0.1" }

Sorry, looks like Nightmare 3.0 is not supported yet.
nightmare-upload plugin can't be installed with Nightmare 3 so we can't proceed adopting it

Ok, nightmare-upload still works so Nightmare 3.0 can be used. Let me check what can be wrong with _locate

Ok, I see what's your issue.
_locate() returns an array, not a single element. So you need to use el[0] in your example

@DavertMik thanks for checking this out. Issue is nothing is returned. You are right in stating if i want to get the first element's value i need to use el[0]. When I go to get the value, i get:
object tested must be an array, a map, an object, a set, a string, or a weakset, but null given

Under verbose mode in the logs (using console.log), i get:
[ 0 ]
null

Wanted to say. Been using codeceptjs and nightmare a few days now. This is impressive. For now, instead of using a helper, using the following and it works for me.
I.seeElement(common.loginMessage)
I.see(common.sucessFullSignOut, common.loginMessage)


Metadata and provenance

There are various CSV data files in the repository in fitting_seasonal/fit and simulating_covid. There are some Rdata files in fitting_seasonal/analysis. Are these input or output? If they are input, where do they come from and which scripts use them? If they are output, which scripts produce them? In both cases, what data is contained in them?

This has been clarified in the readme.


Layers

Currently, Iced assumes widgets cannot be laid out on top of each other. We should implement support for multiple layers of widgets.
This is a necessary feature to implement many kind of interactables, like dropdown menus, select fields, etc.
iced_native will need to group widgets to perform layouting and process some events first for widgets positioned on top.
iced_wgpu will also need to process the scene graph and sort draw calls based on the different layers.

How would the depth of the widgets be determined? Maybe with something like this?
enum Depth {
    Above,
    Below,
    Topmost,
}

fn view(&mut self) -> Element<Message> {
    // ...
    Layer(SomeWidget::new(), Depth::Above)
    // ...
}

Then the current depth would have to be kept in the layouting state. Given a combobox for example, would it be best for the choice list to be part of the drawing code and the widget set to be on top (and ComboBox::new actually returns Layer(ComboBox {...}, Depth::Above) or the choice list be a separate widget, attached to the ComboBox's layout? Or maybe there's a better approach?

I do not have a particular approach in mind yet. There is definitely an interesting amount of exploration ahead of us here.
I do know using something like absolute indices (like z-index in CSS) can be quite painful and does not compose at all.
A relative Layer widget sounds like a good idea to me, as I think it should compose no matter where you decide to nest it. elm-ui follows a similar approach and the author gave a great talk in elm-conf with many interesting ideas. I recommend watching it for inspiration!

Given a combobox for example, would it be best for the choice list to be part of the drawing code and the widget set to be on top (and ComboBox::new actually returns Layer(ComboBox {...}, Depth::Above) or the choice list be a separate widget, attached to the ComboBox's layout? Or maybe there's a better approach?

I think layers (or at least event layers) will need to exist as a first-class concept in iced_native. As of now, they cannot simply be another widget because the runtime needs to be aware of them. In other words, update needs to be aware that layers on top should capture mouse events.
I am not yet sure about how we will end up implementing this. I do have the feeling that the different methods in the Widget trait are inherently coupled (node defines layout, which in turn affects update, draw, and hash_layout). Layers will make this coupling even more apparent.
I think the problem is telling us something here: we should define layout, update, and draw in a unified, declarative way. The runtime will then figure out how to process events and draw widgets. How could this API look like? I am not sure yet! :sweat_smile: This is where we should explore! I think the way iced_web works makes everything very composable and easy to extend.

I would like to add my 2 cents. In other GUI libraries like GTK under X11, such overlays are actually separate windows, and can therefore extend outside the actual application window.
In my opinion, this is very useful for dropdowns and menus. I collected a couple of screenshots to illustrate my point.
Selectbox

Menu

In such cases or in cases of very small windows, it looks like it would be desirable to have a similar effect in Iced, too. I'm absolutely not sure how difficult something like that is to achieve...

Isn't it better to achieve single instance window widget support @hecrj ?
After we can improve it to have such functionality like gimp has.
If such, in our app windows are crucial and we really want to use iced, so we can definetely contribute, but can you guide and write your general ideas about layers first naive implementaion, so I can submit draft for pull request?

Separate windows would be the ideal way to go, but aren't really supported by winit yet (https://github.com/rust-windowing/winit/issues/403), and even if it were I don't know if it would be portable to all platforms (e.g. Android).
FYI, for KAS I solved the event handling via specific support for "pop-ups" (still a bit hacky, but required to support closing menus when clicking under them and things like accelerator key bindings on the menus). For drawing it uses the depth buffer with some specific offsets (not the only option, but otherwise you'd need indirect drawing for each layer I believe).

@AshfordN  overlays do somewhat work but the issue become when you have a lot of overlays which ones should be rendered above the others. So in this case a lot of GUI libraries even Microsoft's UI stuff uses Z List rendering/ordering. All this means is they have a Arc connection point to a list and the list is just used for the rendering order. A list works the best for this method since you can Add children quickly above it and additions don't normally matter as much.  To use a faster method for rendering like a Array/Vec you would need to pull in the top most first and then everything else starting from its children and then back in reverse. so the children or top most object is first in the array. and moving them around should be OK to do as well. In C we would use memmove() but if you use Vec or an actual list should be good enough since both support those methods safely.
This would be

Need a connection point that can be added at view creation.
Decide if you want a slower list or a Vec .
Need to keep track of the current top most object and must place its children as the top most in the rendering list.
Make it so the Top most is the last rendered, based on how you decide to order it in the list.

Regarding child windows, there is now this PR for winit (X11 only): https://github.com/rust-windowing/winit/pull/2246
As @genusistimelord notes, having an application spawn multiple windows isn't exactly hard (KAS has had a "synchronised counter" example since very early on), but tying together event handling across windows for uses like menus is harder.

Is there any kind of requirement list?
What I could gather so far from the above discussions, other comments and some own ideas is that the layering system should allow:

Nested widgets (e.g. drop list) need to be able to display things above others even when higher in the widget tree
Layering should be able to be nested (like some subspace in the window where things are layered but don't overlap with the outside?)
Items on top of other items should get events first
There are "overlays" that belong to a widget like (drop list) and there are overlays that are independent like modals

This also means the layering system has to be accessible from inside a widget and probably also for a user in view

The ordering should be done rather relative instead of absolute (e.g. z-index, except for things like topmost) because users are mostly concerned with "I want this thing to go above/below that" (Relative to "that")
The layers probably need to support some kind of focus concept. When many dialogs stack the focused one should be on top (Iced would need a concept of focus for this, but one could try to keep it in mind)

This also implies that there is some kind of "baselayer" that is never on top of e.g. modals

There will be cases where the user wants to decide where things go but in many cases it should just work (you don't want to specify where the list of a drop-down goes or how to handle it)

These are just some ideas I gathered and a complete list would be helpful / would need to be discussed (maybe already exists and I just missed it).

Currently hector has kindof made layering possible with the ability to create more layering structs which is helpful for fixing the overlay issues.
Event wise the Zlist/Focus would generally be the fastest method for this as you would mostly check if it is over the focused item first. if not then detect what new thing it is over/handling and attempt to delegate the events upon those. Some older GUI went as far as building a Image map and using it to determine where the event occurred and what Colored index existed there.


V0.4 new EntryBuilder and merged TypicalEntries into SampleEntries

@CS2103JUN2017-T2/developers for EntryBuilder.java it's easier just to view the new file on it's own, cos the changes that github shows aren't really useful since everything's changed.
But please check the files under your components, in case I changed anything major, even though it's passing all tests.
Fixes #143

Coverage increased (+0.3%) to 77.612% when pulling a357c0e32ed74aefce01b1f076c8226a110cbdaa on V0.4_entrybuilder into c9a0cd66acd8b44a06e7dbf0a0a2ca4335dcbe71 on V0.4.


Region is not send back from the console

When a user registers the region defaults to aws/us-east-1 rather than the region used to create the token.

Fixed.


Metrics calculating

Excellent work!!, I follow the README to infer results, however,  I found the MANIQA is lower than the original paper (0.5050 vs 0.6198). I would greatly appreciate it if you could provide the calculation code.

Hello, this is likely a difference in the model version being tested.
We calculate the MANIQA metric with MANIQA_PIPAL-ae6d356b.pth.
You can refer the pyiqa for the calculate code.
The crop_boarder is set to 4 following previous work at X4SR task.
Please feel free to contact if you have any other questions.


Topology View

To run:

Copy and paste the following snippet in browser console. Snippet
Run featureActivator("DEV_GUARD", true) on the console after that.

/test all

/retest

/lgtm


React Typings: SVGAttributes has no Class or Id Fields

SVGAttributes extends DOMAttributes which does not contain the className or id fields. This means that the following is invalid TSX:
let element = <svg><circle class="foo" cx="0" cy="0" r="10"/></svg>

These attributes are present on the HTMLAttributes interface which also extends DOMAttributes. They should probably be moved from HTMLAttributes to DOMAttributes.

See #5893 which fixes the className part of this.
Agreed though in general that these need to be cleaned up.

Thanks @jbrantly, I'll close this issue since this is already in the works


fix: Add lifecycle ignore changes on s3_bucket resource to prevent configuration loop

add lifecycle ignore changes on s3_bucket resource to prevent configuration loop to fix https://github.com/terraform-aws-modules/terraform-aws-s3-bucket/issues/144
Description
add lifecycle ignore changes on s3_bucket resource for all new resources that are separate to prevent configuration loop
Motivation and Context

fixes lifecycle loop
Breaking Changes

How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[ ] I have tested and validated these changes using one or more of the provided examples/* projects

[ ] I have executed pre-commit run -a on my pull request

I tested it live because this is blocking my work 😞

I think I was able to reproduce the bug you described in #144, and this PR resolves it.
A message saying Note: Objects have changed outside of Terraform can be misleading for many users, but it is another issue with the Terraform core.
I have also added acl and versioning to ignore_changes just in case.
Merging and releasing now. Thank you!

This PR is included in version 3.0.1 :tada:


Add actions for API used by Root Coding robot

Minor comment: the geometry_msgs messages (e.g. Pose and Quaternion) express values as double (float64 in IDL).
I think we should use that in the input as well to be consistent.

I think we should be more expressive in the feedback and result field.
See the nav2 actions as example https://github.com/ros-planning/navigation2/tree/main/nav2_msgs/action
They often include things like "distance traveled" and "current pose" in the feedback, and "elapsed time" in the output.

I think we should be more expressive in the feedback and result field. See the nav2 actions as example https://github.com/ros-planning/navigation2/tree/main/nav2_msgs/action They often include things like "distance traveled" and "current pose" in the feedback, and "elapsed time" in the output.

Regarding the feedback, I am providing the same result as root https://github.com/iRobotEducation/root-robot-ble-protocol#command-17---navigate-to-position-finished-response
I can provide more intermediate feedback, like distance to goal


pull request for e2e test at 12/06/2016 08:56:01

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Added tests

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0ea5c9f). Click here to learn what that means.
The diff coverage is 79.68%.

@@            Coverage Diff            @@
##             master       #3   +/-   ##
=========================================
  Coverage          ?   60.21%
=========================================
  Files             ?        2
  Lines             ?      186
  Branches          ?       18
=========================================
  Hits              ?      112
  Misses            ?       67
  Partials          ?        7

Impacted Files
Coverage Δ

source/app/libpd.c
49.2% <25%> (ø)

tests/test_libpd.c
83.33% <83.33%> (ø)

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 0ea5c9f...9dd1934. Read the comment docs.


[Ubuntu] Update docker-compose assets filter

Description
Update jq filter patter to allow download v2 version due to  docker-compose-Linux-x86_64  is changed to docker-compose-linux-amd64
Related issue:
https://github.com/actions/virtual-environments/issues/4163
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

compose v2 should be installed as docker plugin, see https://github.com/docker/compose/issues/8687#issuecomment-929271959

compose v2 should be installed as docker plugin, see docker/compose#8687 (comment) (although it might be better if guys maintaining moby-* packages at packages.microsoft.com could add it to repository since compose is a plugin like buildx)

Thanks for the clarification! We will contact folks maintaining Microsoft moby packages


Google site verification

Going through a Google Site verification in order to be able to upload a sitemap to Google later...

merged and updated WWW


build erlang latest fails on M1, missing ex_doc

❯ beamup build erlang latest
 ✅ Downloading release source tarball from erlang/otp
Finished download in 11 seconds
 ✅ ./configure --prefix /Users/kwando/Library/Application Support/beamup/erlang/latest (done in 28 seconds)
 ✅ make -j 10 (done in 2 minutes)
 ✅ make -j 10 docs DOC_TARGETS=chunks (done in 6 seconds)
 ✅ make -j 10 install (done in 10 seconds)
 ⢀ make -j 10 install-docs                                                                                stdout: ERL_TOP=/private/var/folders/wv/gx6j3x2s6mx33f3jlx00h1k40000gn/T/otp.eM5NLfnw59sY/unpack/erlang-otp-9f1b71d INSTALLROOT="/Users/kwando/Library/Application Support/beamup/erlang/latest/lib/erlang" PATH=/private/var/folders/wv/gx6j3x2s6mx33f3jlx00h1k40000gn/T/otp.eM5NLfnw59sY/unpack/erlang-otp-9f1b71d/bootstrap/bin:"${PATH}" \
	make RELEASE_ROOT="/Users/kwando/Library/Application Support/beamup/erlang/latest/lib/erlang" release_docs
cd /private/var/folders/wv/gx6j3x2s6mx33f3jlx00h1k40000gn/T/otp.eM5NLfnw59sY/unpack/erlang-otp-9f1b71d/lib && \
	 PATH=/private/var/folders/wv/gx6j3x2s6mx33f3jlx00h1k40000gn/T/otp.eM5NLfnw59sY/unpack/erlang-otp-9f1b71d/bin:"${PATH}" ERL_TOP=/private/var/folders/wv/gx6j3x2s6mx33f3jlx00h1k40000gn/T/otp.eM5NLfnw59sY/unpack/erlang-otp-9f1b71d \
	 make BUILD_ALL=1 TESTROOT="/Users/kwando/Library/Application Support/beamup/erlang/latest/lib/erlang" release_docs
=== Entering application stdlib
/Applications/Xcode.app/Contents/Developer/usr/bin/make - --jobserver-fds=3,13 -j RELEASE_PATH="/Users/kwando/Library/Application Support/beamup/erlang/latest/lib/erlang"   release_docs_spec
make[5]: Nothing to be done for `release_docs_spec'.
/Applications/Xcode.app/Contents/Developer/usr/bin/make - --jobserver-fds=3,13 -j RELEASE_PATH="/Users/kwando/Library/Application Support/beamup/erlang/latest/lib/erlang"   release_docs_spec
 GEN	html/index.html
Could not find ex_doc!
 ❌ make -j 10 install-docs
Building Erlang for ref=latest id=latest
~ via  v1.22.0 took 2m56s
❯ beamup --version
beamup 0.4.1

Ah, thanks, yup, I thought I removed install-docs but guess I never did. I suppose I'll have it skip it and give a message that you can have it run if you install ex_doc.

Temp fix merged and release made: https://github.com/tsloughter/beamup/releases/tag/v0.4.2


Not able to Automate ti-mocha tests

Hi,
I am trying to automate ti-mocha tests using a Grunt build script and Appcelerator CLI.
As ti-mocha tests run from within the Appc alloy app, the tests are always executed when the app runs.
I would like to find out if there is a way to run ti-mocha test conditionally for e.g. by passing a flag as a part of the build arguments to Appcelerator CLI.
I'm using below command to run the app using CLI.
appc run -p ios
Please help me out of this.

There is no built-in test automation in the appc cli. What I would suggest is perhaps setting a property in your tiapp.xml to indicate that you want to run your tests, then checking for that property at runtime to determine whether or not to run your tests. Check the docs on Titanium.App.Properties for details on how you can do that.


Fix repo API listing stability

This addresses https://github.com/go-gitea/gitea/issues/12056
Repo listings are paginated in the API now. Unfortunately, they are
ORDER BY updated_unix which only has second resolution. This means that
if you do a listing when multiple projects were created at the same time
you can unstable ordering. If that unstable ordering happens at a page
boundary you may fail to get a complete repo listing.
To make things worse sorting by updated_unix means that we may never get
a complete listing because udpated_unix can change independent of our
API calls.
Fix this by making the API repo listing order by id instead.

As noted in the Issue I'm not sure this is a complete fix as other API pagination methods may have similar problems. I'm also in the process of getting this tested properly locally, but I wanted to get this up so that others could offer suggestions or additional fixes if necessary.

I'm doing more testing locally and I'm not sure this fixes the issue for us yet. In any case it should serve as a starting point for figuring it out.

New version does and ascending not descending sort. I realized that if a new repo is added during a listing we'll get that inserted at the front not the end using descending. If we use ascending it will be added at the end and a user paging through the list will see the new repo. In the end both should work, but ascending is a bit more friendly I think.

make lg-tm work


Add cmake_common_scripts repo

I had to manually create the PR because bloom-release kept giving me the same error when trying to create the oauth token. I have since manually created the token and added it the ~/.config/bloom file so hopefully on the next release it will not have an issue.
HTTP Error 404: Not Found (https://api.github.com/authorizations): None

This sometimes fails when the username or password are incorrect, try again?

I had to manually create the PR because bloom-release kept giving me the same error when trying to create the oauth token. I have since manually created the token and added it the ~/.config/bloom file so hopefully on the next release it will not have an issue.
HTTP Error 404: Not Found (https://api.github.com/authorizations): None

This sometimes fails when the username or password are incorrect, try again?

Is this ready to be merged?

Is this ready to be merged?

I have to say that the name of this package seems too generic to me. I'm sure that they are common for you, but in the broader context of a ROS distribution they aren't really common. I think some kind of prefix (ros_industrial_cmake_scripts), or something along those lines, would make it a lot more clear.

I want to check if this is absolutely necessary because a rename will cause us to have to update 15-20 package in the opensource along with our internal projects? I want to avoid causing issues on active projects if possible.

I have to say that the name of this package seems too generic to me. I'm sure that they are common for you, but in the broader context of a ROS distribution they aren't really common. I think some kind of prefix (ros_industrial_cmake_scripts), or something along those lines, would make it a lot more clear.

I want to check if this is absolutely necessary because a rename will cause us to have to update 15-20 package in the opensource along with our internal projects? I want to avoid causing issues on active projects if possible.

@clalancette What are your thought? If the changes needs to be made I will try and get everything updated over the weekend to limit the disruption to projects.

@clalancette What are your thought? If the changes needs to be made I will try and get everything updated over the weekend to limit the disruption to projects.

@ahcorde, @clalancette and @sloretz Is it possible to keep the package name cmake_common_scripts? This will require some work to go through and update all depending packages because this is the lowest level package that all of our packages depend on.

@ahcorde, @clalancette and @sloretz Is it possible to keep the package name cmake_common_scripts? This will require some work to go through and update all depending packages because this is the lowest level package that all of our packages depend on.

My opinion is still that the name of the package needs to be changed.  It's just too generic a name.  However, I'm willing to listen to other arguments about why we should keep the name as-is.

My opinion is still that the name of the package needs to be changed.  It's just too generic a name.  However, I'm willing to listen to other arguments about why we should keep the name as-is.

I find this very disruptive to find out that a package name needs to change at this point. If this is the case that this repository will be controlling the names of packages then there needs to be a process for requesting a name to avoid this complication.  I am not aware of any other package manager which controls the package name other than they must not conflict with an existing package name and as it stands now this does not conflict with any package name within rosdistro.

I find this very disruptive to find out that a package name needs to change at this point. If this is the case that this repository will be controlling the names of packages then there needs to be a process for requesting a name to avoid this complication.  I am not aware of any other package manager which controls the package name other than they must not conflict with an existing package name and as it stands now this does not conflict with any package name within rosdistro.

@clalancette wrote:

I'm willing to listen to other arguments about why we should keep the name as-is.

what sort of other arguments are you thinking of @clalancette?

@clalancette wrote:

I'm willing to listen to other arguments about why we should keep the name as-is.

what sort of other arguments are you thinking of @clalancette?

I have to say that the name of this package seems too generic to me. I'm sure that they are common for you, but in the broader context of a ROS distribution they aren't really common. I think some kind of prefix (ros_industrial_cmake_scripts), or something along those lines, would make it a lot more clear.

I don't think prefixing it with ros_industrial is a relevant prefix because they are not specific to ros_industrial they are specific to the software package cmake. How does adding a prefix make it more clear?
This package is a collection of cmake scripts no different than ament_cmake to make things more convenient. This package contains scripts for cmake commonly found when writing modern cmake reducing the amount cmake code written. I would argue that if you are writing modern cmake then the cmake code behind the macros within this package are common things you would do as everything should be attached to the target opposed to setting things globally. These macros keep your cmake file cleaner  by hiding the logic less prone to user error very similar to ament_cmake.

I have to say that the name of this package seems too generic to me. I'm sure that they are common for you, but in the broader context of a ROS distribution they aren't really common. I think some kind of prefix (ros_industrial_cmake_scripts), or something along those lines, would make it a lot more clear.

I don't think prefixing it with ros_industrial is a relevant prefix because they are not specific to ros_industrial they are specific to the software package cmake. How does adding a prefix make it more clear?
This package is a collection of cmake scripts no different than ament_cmake to make things more convenient. This package contains scripts for cmake commonly found when writing modern cmake reducing the amount cmake code written. I would argue that if you are writing modern cmake then the cmake code behind the macros within this package are common things you would do as everything should be attached to the target opposed to setting things globally. These macros keep your cmake file cleaner  by hiding the logic less prone to user error very similar to ament_cmake.

Would cmake_helper_scripts be better ok?

Would cmake_helper_scripts be better ok?

what sort of other arguments are you thinking of @clalancette?

Maybe "arguments" was the wrong term; other opinions is what I am looking for.

Would cmake_helper_scripts be ok?

Given my original argument, not really.  It is still really generic.  REP-144 lays out some guidelines.  Mostly I think this package name violates the first two "Global Rules".  But again, I am willing to listen to dissenting opinions and be overridden.

what sort of other arguments are you thinking of @clalancette?

Maybe "arguments" was the wrong term; other opinions is what I am looking for.

Would cmake_helper_scripts be ok?

Given my original argument, not really.  It is still really generic.  REP-144 lays out some guidelines.  Mostly I think this package name violates the first two "Global Rules".  But again, I am willing to listen to dissenting opinions and be overridden.

Could you perhaps suggest a name, based on what @Levi-Armstrong described is the purpose of the package?
There's indeed nothing really ros_industrial about it, so that would seem to rule out that prefix.
Some suggestions may help get this moving.

Could you perhaps suggest a name, based on what @Levi-Armstrong described is the purpose of the package?
There's indeed nothing really ros_industrial about it, so that would seem to rule out that prefix.
Some suggestions may help get this moving.

@clalancette Do you mind providing more information on how it violates the "Global Rules"? As @gavanderhoorn mentioned, suggestions would help move things along.  I have provided the Global Rules for others.
Global Rules:

Package names should be specific enough to identify what the package does. For example, a motion planner should not be called planner. If it implements the wavefront propagation algorithm, it might be called wavefront_planner. There's obviously tension between making a name specific and keeping it from becoming overly verbose
Using catchall names such as utils should be avoided. They do not scope what goes into the package or what should be outside the package
A package name should not contain ros as it is redundant. Exceptions include core packages and ROS bindings of an upstream library (e.g. moveit_ros)
The package name should describe what the package does, not where it came from. One of ROS's goals is to develop a canonical set of tools for making robots do interesting things. Then again, as stated in the rules below, if a package is specialized by an entity (lab, company, ...), prepend the name of the entity. But once the package is commonly used, owned and maintained, that name can be dropped as the package becomes the reference
Do not use a name that's already been taken. To check whether a name is taken, consult [2]. If you'd like your repository included in that list, see the tutorial at [3]

@clalancette Do you mind providing more information on how it violates the "Global Rules"? As @gavanderhoorn mentioned, suggestions would help move things along.  I have provided the Global Rules for others.
Global Rules:

Package names should be specific enough to identify what the package does. For example, a motion planner should not be called planner. If it implements the wavefront propagation algorithm, it might be called wavefront_planner. There's obviously tension between making a name specific and keeping it from becoming overly verbose
Using catchall names such as utils should be avoided. They do not scope what goes into the package or what should be outside the package
A package name should not contain ros as it is redundant. Exceptions include core packages and ROS bindings of an upstream library (e.g. moveit_ros)
The package name should describe what the package does, not where it came from. One of ROS's goals is to develop a canonical set of tools for making robots do interesting things. Then again, as stated in the rules below, if a package is specialized by an entity (lab, company, ...), prepend the name of the entity. But once the package is commonly used, owned and maintained, that name can be dropped as the package becomes the reference
Do not use a name that's already been taken. To check whether a name is taken, consult [2]. If you'd like your repository included in that list, see the tutorial at [3]

The name as it stands is way too generic. It fails both describing it's contents as well as using catchall naming elements. From the package name it defines the programming language and says "common" which doesn't say anything about what's inside of it.
Reading the headline of the README: "This contains a collection of useful CMake macros." which still doesn't even define a scope.
Looking inside I see content related to linting, cppcheck, coverage. test registration and running tests. There doesn't appear to be cross correlation between these except that they're in the same language and mostly relate to testing. The name should reflect what's expected to be found inside. So that as a potential user I can guess at what's inside. And as a potential contributor I can know if something I wrote would be good to add.
We have good examples of this in ROS 2 where there's ament_cmake_cppcheck which makes it clear what to look for inside the package, these could be similarly broken out instead of just lumped together. This level of granularity is valuable to the community to make things highly reusable and not cause cross coupling. The filter for naming is a proxy for being able to understand the scope of the package. If you can't name it easily that suggests that you don't have a clearly defined scope.
In slightly different circumstances, aka not inside the last release, with this large collection of miscellaneous macros, are there existing packages that it would make sense to contribute to instead of extending.
We don't require this level of granularity of developers and offer the escape valve of not having to use good names if the package is prefixed with the organization or other entity so as not to claim generality. If these packages are designed to be reused by many different organizations projects the scoping should be addressed.
Right now the only coherent scoping is by who the maintainer is and I think that for the sake of a minimal effort to deploy it prefixing with your choice of ros-i and swri would make sense. Since there's hopefully equivalents in ROS 2 already or places to contribute these functions there I hope that this package use is obviated in ROS 2. Otherwise if this was going to be something that could be used more generally it would be broken up and scoped better and or directly contributed to existing packages with related cmake functionality.

The name as it stands is way too generic. It fails both describing it's contents as well as using catchall naming elements. From the package name it defines the programming language and says "common" which doesn't say anything about what's inside of it.
Reading the headline of the README: "This contains a collection of useful CMake macros." which still doesn't even define a scope.
Looking inside I see content related to linting, cppcheck, coverage. test registration and running tests. There doesn't appear to be cross correlation between these except that they're in the same language and mostly relate to testing. The name should reflect what's expected to be found inside. So that as a potential user I can guess at what's inside. And as a potential contributor I can know if something I wrote would be good to add.
We have good examples of this in ROS 2 where there's ament_cmake_cppcheck which makes it clear what to look for inside the package, these could be similarly broken out instead of just lumped together. This level of granularity is valuable to the community to make things highly reusable and not cause cross coupling. The filter for naming is a proxy for being able to understand the scope of the package. If you can't name it easily that suggests that you don't have a clearly defined scope.
In slightly different circumstances, aka not inside the last release, with this large collection of miscellaneous macros, are there existing packages that it would make sense to contribute to instead of extending.
We don't require this level of granularity of developers and offer the escape valve of not having to use good names if the package is prefixed with the organization or other entity so as not to claim generality. If these packages are designed to be reused by many different organizations projects the scoping should be addressed.
Right now the only coherent scoping is by who the maintainer is and I think that for the sake of a minimal effort to deploy it prefixing with your choice of ros-i and swri would make sense. Since there's hopefully equivalents in ROS 2 already or places to contribute these functions there I hope that this package use is obviated in ROS 2. Otherwise if this was going to be something that could be used more generally it would be broken up and scoped better and or directly contributed to existing packages with related cmake functionality.

@clalancette and @tfoote Before I go through and change things, would the following name be acceptable swri_cmake_scripts?

@clalancette and @tfoote Before I go through and change things, would the following name be acceptable swri_cmake_scripts?

swri_cmake_scripts sounds good to me.

swri_cmake_scripts sounds good to me.

@clalancette and @tfoote Thank you for the support.

We don't require this level of granularity of developers and offer the escape valve of not having to use good names if the package is prefixed with the organization or other entity so as not to claim generality. If these packages are designed to be reused by many different organizations projects the scoping should be addressed.

Makes sense.

Since we are on the subject, I have an educational questions below.

We have good examples of this in ROS 2 where there's ament_cmake_cppcheck which makes it clear what to look for inside the package, these could be similarly broken out instead of just lumped together. This level of granularity is valuable to the community to make things highly reusable and not cause cross coupling. The filter for naming is a proxy for being able to understand the scope of the package. If you can't name it easily that suggests that you don't have a clearly defined scope.

Some recent discussion have come up about leveraging Project Modularization technique for some of our repositories other than the approach you provided having everything in separate packages. It sounds like this would not be an acceptable approach to use for a package to be released for ROS use?

@clalancette and @tfoote Thank you for the support.

We don't require this level of granularity of developers and offer the escape valve of not having to use good names if the package is prefixed with the organization or other entity so as not to claim generality. If these packages are designed to be reused by many different organizations projects the scoping should be addressed.

Makes sense.

Since we are on the subject, I have an educational questions below.

We have good examples of this in ROS 2 where there's ament_cmake_cppcheck which makes it clear what to look for inside the package, these could be similarly broken out instead of just lumped together. This level of granularity is valuable to the community to make things highly reusable and not cause cross coupling. The filter for naming is a proxy for being able to understand the scope of the package. If you can't name it easily that suggests that you don't have a clearly defined scope.

Some recent discussion have come up about leveraging Project Modularization technique for some of our repositories other than the approach you provided having everything in separate packages. It sounds like this would not be an acceptable approach to use for a package to be released for ROS use?

Some recent discussion have come up about leveraging Project Modularization technique for some of our repositories other than the approach you provided having everything in separate packages. It sounds like this would not be an acceptable approach to use for a package to be released for ROS use?

There's more than one approach to modularity. I'm not familiar with a canonical 'Project Modularization' technique do you have a link to the approach so we can look at the tradeoffs? The tradeoffs of any given approach will be dependent on the use cases.

Some recent discussion have come up about leveraging Project Modularization technique for some of our repositories other than the approach you provided having everything in separate packages. It sounds like this would not be an acceptable approach to use for a package to be released for ROS use?

There's more than one approach to modularity. I'm not familiar with a canonical 'Project Modularization' technique do you have a link to the approach so we can look at the tradeoffs? The tradeoffs of any given approach will be dependent on the use cases.


Azure Cloud Shell Connector Not Working

Environment
Windows build number: 10.0.18941.1001
Windows Terminal version (if applicable): Source

Steps to reproduce

Fresh Install of Terminal from Source
Try to open Azure Cloud Shell Connector

Expected behavior

Device Flow kicks off and you can connect to Azure

Actual behavior

Get following message

Could not connect to Azure. You may not have internet or the server might be down.

Opening up Fiddler, the request is failing, here is the request
POST https://login.microsoftonline.com/common/oauth2/devicecode HTTP/1.1
Connection: Keep-Alive
Content-Type: application/x-www-form-urlencoded; charset=utf-8
User-Agent: cpprestsdk/2.10.13
Content-Length: 57
Host: login.microsoftonline.com

client_id=0&resource=https://management.core.windows.net/

and response
HTTP/1.1 400 Bad Request
Cache-Control: no-cache, no-store
Pragma: no-cache
Content-Type: application/json; charset=utf-8
Expires: -1
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
x-ms-request-id: 036d9b04-0b15-4948-88e3-1298fe521f00
P3P: CP="DSP CUR OTPi IND OTRi ONL FIN"
Set-Cookie: fpc=AgBw0kjQZyJGh-9yya_oOWo; expires=Fri, 30-Aug-2019 13:29:10 GMT; path=/; secure; HttpOnly
Set-Cookie: esctx=AQABAAAAAAAP0wLlqdLVToOpA4kwzSnx6Nn0i9n3KONl8oqKUDrwVI49N60kNuXitGhI2l65usEtATWKSOh8_SSS6SxU8qs6Mc2TKjto45yvCwsR1FnOxysOiKELlbMM8oFUyR0pRNEedN5J_pDsAlMLiz5CCixbFrYu1kevQ7G277G0tWGQ1Bmr6yQvertj7I1EFoMdyWkgAA; domain=.login.microsoftonline.com; path=/; secure; HttpOnly
Set-Cookie: x-ms-gateway-slice=prod; path=/; secure; HttpOnly
Set-Cookie: stsservicecookie=ests; path=/; secure; HttpOnly
Date: Wed, 31 Jul 2019 13:29:10 GMT
Content-Length: 468

{"error":"invalid_request","error_description":"AADSTS50059: No tenant-identifying information found in either the request or implied by any provided credentials.\r\nTrace ID: 036d9b04-0b15-4948-88e3-1298fe521f00\r\nCorrelation ID: 62f6beea-e136-430d-8262-d762ad319f00\r\nTimestamp: 2019-07-31 13:29:10Z","error_codes":[50059],"timestamp":"2019-07-31 13:29:10Z","trace_id":"036d9b04-0b15-4948-88e3-1298fe521f00","correlation_id":"62f6beea-e136-430d-8262-d762ad319f00"}

Looks like no client_ id is being set in code. Do you need to set this somewhere?

This definitely isn't supposed to work at the moment. We need to manually embed our client ID in the code, and we're definitely not pushing that to the repo. We'll stamp that client ID into the build during the release process, but it won't work in local builds unfortunately.
This is now the issue for "Display a message when someone tries to use the azure connection in a local build without the client ID".
CC @PankajBhojwani and @DHowett-MSFT

So is there a workaround at the moment? Or should we just remove the profile?

There is no workaround right now, you can remove the profile if you don't want it. We will make it so this option does not show up in local builds in the future. Thank you!


version 1.0

RaccooChat Version 1.0.
Was realized multithread server. Was implemented function that makes a query every second on the server and gets all the new messages. All messages are stored in an array. And all users and positions of the last message that this user is got, also are stored in an array.
And also was implemented these functions:

get all command that we can use in the chat (/command);
connect and disconnect users;
it is possible to look who is online now (/users);
get last five message from the chat (/last).

RaccooChat Version 1.1.
Last changes:

test_gflag.cpp - c++ file for testing gflag and glog;
Client.py was divided on two separate files:
client.py - client;
RaccooChatClient.py - class for working with server;


ADLS Gen2 folders can not be sorted correctly by the column 'Last Modified'

Storage Explorer Version: 1.33.0-dev (96)
Build Number: 202311
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.1 (Apple M1 Pro)
Architecture: x64/x64/arm64
How Found: From running test cases
Regression From: Previous release (1.31.2)
Steps to Reproduce

Expand one ADLS Gen2 storage account -> Blob Containers.
Upload more than 2 folders with different last modified times.
Sort the folders by clicking the 'Last Modified' column.
Check whether the folders can be sorted correctly.

Expected Experience
The folders can be sorted correctly.
Actual Experience
The folders can't be sorted correctly.
Here is the record:

Verified this issue on the hotfix build 20231110.6. Fixed. So, we are going to close it.


Dependency Fix : Android app crushed when use version 6.1.1 #204

Text Encoder from text-encoding cause Issue with "The Property 'TextEncoder' is not exist"
. Fixed with the updated text-encoder library

@luacmartins / @Kicu - can you please review ?

@Elanthingal hey, thanks for contributing.
I will take a look at fast-text-encoding package and will review this PR tomorrow.

hey @Elanthingal
I have a few additional questions to better understand what this actually fixes.
We have recently added an Example app, in the /Example directory which allows us to test and develop react-native-qrcode-svg in isolation.
I can see that when building version 6.3.2 all 3 apps: web, ios, android work correctly and I get no errors.
Is it possible for you to switch to using version 6.3.2? and if there are still errors there can you provide an example reproduction for errors?
I can see that text-encoding is not supported anymore (although perhaps it still works), whereas fast-text-encoding is supported, so the library is probably fine. However we shouldn't be updating a dependency without understanding what exactly it fixes and when an old version doesn't work.

Sure. will comeback


Add hianime.to as source

Any change you could add hianime.to as a source?

hianime always there...


Correction for raw affiliation LIP, UMR 5668 CNRS, INRIA, ENS-Lyon, UCB-Lyon, France

Correction needed for raw affiliation LIP, UMR 5668 CNRS, INRIA, ENS-Lyon, UCB-Lyon, France
raw_affiliation_name: LIP, UMR 5668 CNRS, INRIA, ENS-Lyon, UCB-Lyon, France
new_rors: 04zmssz18;02kvxyf05;02feahw73;04msnz457
previous_rors: 04zmssz18;02kvxyf05;02feahw73
works_examples: W21092263
contact: 77e243b189a04016dd1eaf6b048161d4:138a3c21e44e53fd186eaec9e452 @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Replace Scaleway Container Registries with Github Registries

@km4rcus, to use Github COntainer Registry, we need personal access token generated for a user (here CMCC-Foundation with privileges for geolake repository and scope for read/write.


Other combat skills

When an item/weapon is created you only have the ordinary 6 skills to choose from.
In the core rules mines (AoR Table 5-5: Ranged Weapons p. 173) use Mechanics, and Ithorian Bellow-ability (AoR p. 58) use Resilience for its use.
I have no idea if there are more weapons or abilities that use different skills but wouldn't be surprised. Trandoshans use Brawl for their claws.

Just pushed an initial fix to the dev branch which enables all standard skills in the dropdown on the weapon sheet.
This won't yet capture any custom skills so it still needs a bit of further work, and it will also long term be a sheet option on each weapon item so that it defaults to only showing combat skills for convenience unless toggled to display all.

I've updated the skills to include custom skills in the list... it was double duty as the same list is used for modifiers.  Also sorted skills by abbreviation.  If that's not enough to close this, add what else is needed.  Not sure we need a toggle to turn this off and on, because if its turned off after values have been added that are not combat skills the drop down will be blank.

Closing this for now as I think the above addition of custom skills covers general usage.
The only reason for a toggle is just QoL really, as it's easier when creating lots of weapons to just see the combat skills only, rather than having to scroll through everything for what is a fairly uncommon use case.
Can tweak it to include a toggle later if people want it.


[WIP] prepared the deletion of a user in the admin area.

🍰 Pullrequest
prepared the deletion of a user in the admin area.

Button for filtering all deletedAdd users
new column in user search for deleting a user
new form to delete a user

Issues

fixes #1508
fixes #1507
fixes #1506

https://user-images.githubusercontent.com/1324583/154554594-6c6292bb-da5f-4318-8bed-56c4a98084d2.mp4

@ogerly Können wir das schließen?


Bug in markdown render with single quotation marks

Environment data

VS Code version: 1.58.2
Jupyter Extension version (available under the Extensions sidebar): v2021.8.1013163132
Python Extension version (available under the Extensions sidebar): v2021.6.944021595
OS (Windows | Mac | Linux distro) and version: Windows21H1
Python and/or Anaconda version: 3.9.2
Type of virtual environment used : N/A
Jupyter server running: Local

Expected behaviour
when there are code like these in a cell:
github

 Don't work fine

expected result in display:
[github](https://github.com/)

Don't work fine

Actual behaviour
when there are code like these in a cell:
github

 Don't work fine

actual result in display:
github(github

Don)

Don')

Don't work fine

where both github  in line 1 are hyperlinked
However, after remove the single quotation marks in Don't, it works just fine:
github

 Dont work fine

actual result in display:
[github](https://github.com/)

Dont work fine

Steps to reproduce:

open a new jupyter notebook
create a new cell and click the button "Change to markdown"
write down these code

github

 Don't work fine

Shift + Enter

Thanks for the issue @lyc0930. That issue will be solved with native notebooks.
You can try it now by following these steps:
https://github.com/microsoft/vscode-jupyter/wiki/Native-Notebook-Support-in-VS-Code

Thanks for the issue @lyc0930. That issue will be solved with native notebooks.
You can try it now by following these steps:
https://github.com/microsoft/vscode-jupyter/wiki/Native-Notebook-Support-in-VS-Code

Thanks, It seems to work just fine. It's great to see a brand new notebook in VSCode.


avoid_count Fehler

Hallo,
ich habe bei meinem Roborock S8 folgende Fehlermeldungen
Adapter Version 0.4.4

roborock.0
2023-11-09 10:18:06.323
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.19.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:06.293
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.18.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:06.221
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.17.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:06.149
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.16.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:06.024
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.15.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.954
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.14.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.877
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.13.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.763
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.12.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.737
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.11.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.669
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.10.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.552
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.9.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.483
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.8.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.455
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.7.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.342
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.6.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.271
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.5.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.245
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.4.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.177
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.3.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:05.101
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.2.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:04.980
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.1.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:04.949
warn
State "roborock.0.Devices.xxxxxxxxxxxx.cleaningInfo.Records.0.avoid_count" has no existing object, this might lead to an error in future versions

roborock.0
2023-11-09 10:18:04.337
warn
Failed to execute load_multi_map on robot xxxxxxxxxxxx Error: There was an error processing the request with id 5271 error: {"code":-10007,"message":"invalid status"}

Danke. Fixed in via https://github.com/copystring/ioBroker.roborock/commit/f804b9a2b0bab125d42af046e5ba9c244dc24718.

Dieser Fehler ist mit der dev Version jetzt weg, allerdings hab ich minütlich einen neuen:
roborock.0
2023-11-16 07:37:57.544	error	Failed to execute load_multi_map on robot 6jWcsplHN1hqrmHaTNyLfB Error: There was an error processing the request with id 1510 error: {"code":-10003,"message":"action locked"} at EventEmitter.listener102 (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock_mqtt_connector.js:286:14) at EventEmitter.emit (/opt/iobroker/node_modules/eventemitter2/lib/eventemitter2.js:1047:22) at MqttClient. (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock_mqtt_connector.js:182:9) at MqttClient.emit (node:events:514:28) at handlePublish (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/handlers/publish.ts:172:11) at handle (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/handlers/index.ts:29:17) at work (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/client.ts:728:17) at Writable.writable._write (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/client.ts:752:4) at writeOrBuffer (/opt/iobroker/node_modules/iobroker.roborock/node_modules/readable-stream/lib/internal/streams/writable.js:334:12) at _write (/opt/iobroker/node_modules/iobroker.roborock/node_modules/readable-stream/lib/internal/streams/writable.js:283:10)
roborock.0
2023-11-16 07:36:57.631	error	Failed to execute load_multi_map on robot 6jWcsplHN1hqrmHaTNyLfB Error: There was an error processing the request with id 4752 error: {"code":-10003,"message":"action locked"} at EventEmitter.listener102 (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock_mqtt_connector.js:286:14) at EventEmitter.emit (/opt/iobroker/node_modules/eventemitter2/lib/eventemitter2.js:1047:22) at MqttClient. (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock_mqtt_connector.js:182:9) at MqttClient.emit (node:events:514:28) at handlePublish (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/handlers/publish.ts:172:11) at handle (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/handlers/index.ts:29:17) at work (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/client.ts:728:17) at Writable.writable._write (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/client.ts:752:4) at writeOrBuffer (/opt/iobroker/node_modules/iobroker.roborock/node_modules/readable-stream/lib/internal/streams/writable.js:334:12) at _write (/opt/iobroker/node_modules/iobroker.roborock/node_modules/readable-stream/lib/internal/streams/writable.js:283:10)
roborock.0
2023-11-16 07:35:57.689	error	Failed to execute load_multi_map on robot 6jWcsplHN1hqrmHaTNyLfB Error: There was an error processing the request with id 4076 error: {"code":-10003,"message":"action locked"} at EventEmitter.listener102 (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock_mqtt_connector.js:286:14) at EventEmitter.emit (/opt/iobroker/node_modules/eventemitter2/lib/eventemitter2.js:1047:22) at MqttClient. (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock_mqtt_connector.js:182:9) at MqttClient.emit (node:events:514:28) at handlePublish (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/handlers/publish.ts:172:11) at handle (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/handlers/index.ts:29:17) at work (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/client.ts:728:17) at Writable.writable._write (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/client.ts:752:4) at writeOrBuffer (/opt/iobroker/node_modules/iobroker.roborock/node_modules/readable-stream/lib/internal/streams/writable.js:334:12) at _write (/opt/iobroker/node_modules/iobroker.roborock/node_modules/readable-stream/lib/internal/streams/writable.js:283:10)
roborock.0
2023-11-16 07:34:57.703	error	Failed to execute load_multi_map on robot 6jWcsplHN1hqrmHaTNyLfB Error: There was an error processing the request with id 3388 error: {"code":-10003,"message":"action locked"} at EventEmitter.listener102 (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock_mqtt_connector.js:286:14) at EventEmitter.emit (/opt/iobroker/node_modules/eventemitter2/lib/eventemitter2.js:1047:22) at MqttClient. (/opt/iobroker/node_modules/iobroker.roborock/lib/roborock_mqtt_connector.js:182:9) at MqttClient.emit (node:events:514:28) at handlePublish (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/handlers/publish.ts:172:11) at handle (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/handlers/index.ts:29:17) at work (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/client.ts:728:17) at Writable.writable._write (/opt/iobroker/node_modules/iobroker.roborock/node_modules/mqtt/src/lib/client.ts:752:4) at writeOrBuffer (/opt/iobroker/node_modules/iobroker.roborock/node_modules/readable-stream/lib/internal/streams/writable.js:334:12) at _write (/opt/iobroker/node_modules/iobroker.roborock/node_modules/readable-stream/lib/internal/streams/writable.js:283:10)

action locked bedeutet, dass dein Saugroboter irgendwie beschäftigt ist. starte den mal neu.


Add support for different Sonarqube token types

Hey, I just made a Pull Request!
Currently the plugin will only work if the token provided is a User token.
The following endpoints fail if a Project Analysis or Global Analysis token is used:

api/components/show
api/measures/component

This PR supports the use of Project Analysis and Global Analysis tokens should they be used.
Currently, if a Project or Global token is used the plugin just shows There is no SonarQube project with key xyz in the frontend and the backend api calls all succeed even though a 403 is returned by the SonarQube API, so it is very hard to understand what is wrong.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Bump as this is still relevant

Not stale

Hey @sblausten! Sorry for the delay here, been a pretty hectic few weeks for us!
This feels a little unfortunate to have to retry with the a different request, does it make more sense to provide another config option so that you can define the token type or something and then we can choose the authentication method?
Or is that not possible? Sorry just trying to understand the issue a little more?


Many tests

This library didn't had any automatic tests. As of today it made a good start with all the tests.
And resolved the following issues:

Fixed #45
Fixed #46
Fixed (partially) #47

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Switching team without changing class allows you to place other team's block colors

Minimap shows I am on the blue team, but my build gun has red blocks.

i think that was because it was in sandbox mode.


[pages] document Rust and Swift installation process

Document how to install Rust and Swift for your pages projects, since they aren't installed by default. Details that need to be tested and turned into docs here: https://pages.cloudflare-docs.workers.dev/pages/platform/build-configuration
Swift

Not installed by default. Supports any version that swiftenv can install later than 4.x. Versions 4.x and earlier will not work due to incompatible shared libraries. 5.2 is installed if Package.swift is present and no version is specified with SWIFT_VERSION or .swift-version.

Rust

Not installed by default. Supports any version that rustup can install.

Swift

Not installed by default. Supports any version that swiftenv can install later than 4.x. Versions 4.x and earlier will not work due to incompatible shared libraries. 5.2 is installed if Package.swift is present and no version is specified with SWIFT_VERSION or .swift-version.

Rust

Not installed by default. Supports any version that rustup can install.

It appears these docs were written for a newer version of Netlify's build-image than Pages uses?
For Swift, a pages build with neither SWIFT_VERSION set nor a Package.swift present outputs

19:24:49.376 | 5.2 is already installed.
19:24:49.380 | Using Swift version 5.2

So Swift 5.2 appears to be installed by default on Pages; this stopped being the case in https://github.com/netlify/build-image/commit/09c2cdcdf242cf2f57c9ee0fcad9d298fad9ad41 (Nov 2020).
As for Rust, both cargo and rustup are included in Netlify's image—"not installed by default" refers to no Rust toolchain being present, which you'd install yourself either with a rust-toolchain(.toml) file or via prefixing the build command with a rustup toolchain install. Neither cargo nor rustup are present in Pages; Netlify first added Rust support in https://github.com/netlify/build-image/commit/53b83b6bede2920f236b25b6f5a95334320dc849 (Dec 2020).

We've removed mentions of Rust and Swift in the docs, so this issue is out of date


Automated releases of SDK to NPM upon GH release

Description
Automated releases of SDK to NPM upon GH release
Related to #38
Acceptance criteria

Tasks

[ ]

@kelsos Is this a duplicate of https://github.com/raiden-network/light-client/issues/38 ? If yes, please go ahead and close it. Thanks :)

I would say that #38 contains this issue so yes I am closing this one.