ERROR: Could not find a version that satisfies the requirement torch==2.4.1+cu121

Hi,
Getting error, while running this :
(venv-ui) PS C:\Users\Administrator\Desktop\clearn\clean-ui> pip install -r requirements.txt
Requirement already satisfied: transformers==4.45.1 in c:\users\administrator\desktop\clearn\clean-ui\venv-ui\lib\site-packages (from -r requirements.txt (line 1)) (4.45.1)
Requirement already satisfied: gradio==4.44.0 in c:\users\administrator\desktop\clearn\clean-ui\venv-ui\lib\site-packages (from -r requirements.txt (line 2)) (4.44.0)
ERROR: Could not find a version that satisfies the requirement torch==2.4.1+cu121 (from versions: 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.4.0, 2.4.1)
ERROR: No matching distribution found for torch==2.4.1+cu121
[notice] A new release of pip is available: 24.0 -> 24.2
[notice] To update, run: python.exe -m pip install --upgrade pip
(venv-ui) PS C:\Users\Administrator\Desktop\clearn\clean-ui>

Hi, try installing via this command:
pip install torch==2.4.1+cu121 --index-url https://download.pytorch.org/whl/cu121

Be sure to activate the environment with the command (if it has not been activated) before installing:
.\venv-ui\Scripts\activate

Thanks, I just reviewed this on my channel https://www.youtube.com/watch?v=hi4tcrCH8RY
Thanks for great work.


Limit the number of alert per second in configuration.

Assap triggers many notifications per second, add an option to limit it in the configuration panel.

The issue has been resolved.


[BUG] Withdraw amount text field is not limited to any amount of digits.

Describe the bug
Withdraw amount text field is not limited to any amount of digits.
To Reproduce

Go to the portfolio page
Withdraw on of the tokens you hold
Insert a very very long number (more than 30 digits)

Expected behavior
The text field should be limited to 18 digits after the dot and 12 digits before
Screenshots

Stale


Initial popover focus management

GAUD-6562
This PR adds initial focus management to the PopoverMixin. In summary:

focus the first focusable in the consumer content if it exists
focus the Popover itself if there isn't a focusable in the consumer content
a noAutoFocus property
open, close, and toggleOpen methods, with the option of applying focus or not
more tests

This does not include focus trapping - that will be added in a separate story.

I snuck in a fix to the animation time.
Aside from that, I think this is all set, unless you're looking for more changes here. I plan to change the API in my next PR. I can do that here, but figured it would be better done separately since it will involve changing a bunch of code that's not related to this focus management story.


Update sbt-jmh to 0.4.0

Updates pl.project13.scala:sbt-jmh from 0.3.7 to 0.4.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "pl.project13.scala", artifactId = "sbt-jmh" } ]

labels: sbt-plugin-update, semver-minor

Codecov Report

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

@@           Coverage Diff           @@
##           master      #38   +/-   ##
=======================================
  Coverage   84.52%   84.52%
=======================================
  Files          28       28
  Lines         814      814
  Branches       27       27
=======================================
  Hits          688      688
  Misses        126      126

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 6419ddf...141c9d9. Read the comment docs.


Google cast stops after 30 seconds - Nest hub

Hi,
After the Nest Hub is updated to Fuchsia it stops if I cast home assistant after 30 seconds now instead of 10 minutes as before.
Would it be possible to Use disableIdleTimeout as mentioned in Google docs?
https://developers.google.com/cast/docs/reference/web_receiver/cast.framework.CastReceiverOptions
window.castReceiverManager.start({statusText: "Application is starting", disableIdleTimeout: true});

@dannymertens Please try this:
https://github.com/swiergot/ha-catt-fix
It fixes the 10 minutes timeout, perhaps the 30 seconds timeout has the same root cause.

@dannymertens you need to ask developer of Cast app https://github.com/stestagg/dashcast

Dropping the ha-catt-fix.js file into the AppDaemon's custom_javascript folder does seem to work.


[QUESTION] Reading / Writing Dictionary<string, object>

I currently have an issue writing/reading a particular object structure into and out of LiteDB. Using LiteDB 5.0.12
Below is an example of the object structure I am using with the majority of properties ommited as they're irrelevant. The Properties property is of type Dictionary<string, object> so we are able to use whatever we need as a key's value.
Dictionary<string, object> customProps = new Dictionary<string, object>();
customProps.Add("key1", 1);
customProps.Add("key2", "Hello");
customProps.Add("key3", true);
customProps.Add("key4", DateTime.Now);
customProps.Add("key5", new TimeSpan(1, 20, 0));
dynamic exp = new ExpandoObject();
exp.prop1 = "val1";
exp.prop2 = "val2";
customProps.Add("key6", exp);
var scope = new UserScope
{
...
Policy = new Policy
{
...
Properties = customProps
...
}
};
When saving this object to LiteDB (inserting or updating) the below is what is stored:
{
...
"Properties": {
"key1": 1,
"key2": "Hello",
"key3": true,
"key4": {
"$date": "2022-11-23T13:39:25.5220000Z"
},
"key5": {
"$numberLong": "48000000000"
},
"key6": [
{
"_type": "System.Collections.Generic.KeyValuePair2[[System.String, System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e],[System.Object, System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], System.Private.CoreLib",         "Key": "prop1",         "Value": "val1"       },       {         "_type": "System.Collections.Generic.KeyValuePair2[[System.String, System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e],[System.Object, System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]], System.Private.CoreLib",
"Key": "prop2",
"Value": "val2"
}
]
}
}
Reading this object back out of LiteDB results in null values:
{
"Policy": {
...
"Properties": {
"key1": 1,
"key2": "Hello",
"key3": true,
"key4": "2022-11-23T13:39:25.522+00:00",
"key5":<PHONE_NUMBER>0,
"key6": [
{
"Key": null,
"Value": null
},
{
"Key": null,
"Value": null
}
]
}
}
}
Using Dictionary<string, object> doesn't seem to be an issue with basic values in the value side as object, for example string, int, datetime etc but using anything slightly more complex seems to be resulting in unexpected behaviour.
Am I missing something here or would I need to use a converter of some sort or something similar?
Any assistance would be appreciated.

I can't reproduce this. Using this unit tests with my litedb branch.
Yes this unit test failed because seems as litedb don't know how to work with ExpandoObject and i think it's normal because for me it seems as highly anti-pattern for database. It convert ExpandoObject to object but with correct values.
    public class Issue2253_Tests
    {
        [Fact]
        public void DictionaryWithObject()
        {
            var ms = new MemoryStream();
            var litedb = new LiteDatabase(ms);

            var customProps = new Dictionary<string, object>
            {
                { "key1", 1 },
                { "key2", "Hello" },
                { "key3", true },
                { "key4", DateTime.Now },
                { "key5", new TimeSpan(1, 20, 0) }
            };
            dynamic exp = new ExpandoObject();
            exp.prop1 = "val1";
            exp.prop2 = "val2";
            customProps.Add("key6", exp);
            var scope = new UserScope
            {
                Policy = new Policy
                {
                    Properties = customProps
                }
            };

            var collection = litedb.GetCollection<UserScope>("test");
            collection.Insert(scope);

            ms.Position = 0;
            litedb = new LiteDatabase(ms);

            var getCustomPropsBack = collection.FindOne(a => true);
            Assert.Equal(scope, getCustomPropsBack);
        }

        private class UserScope
        {
            public object Policy { get; set; }
        }

        private class Policy
        {
            public Dictionary<string, object> Properties { get; set; }
        }
    }


Dont be thrown out of elog after some hours

Avoid to be thrown out of the logbook after few hours (dont know what current default timeout is), e.g. by auto-renewing tickets or providing longer lifetime tickets

it's now 2 weeks, so should be fixed


Question: difference between fetch and asyncData

Hi!
It is confusing when to use fetch and when asyncData
They both can:

access context (store, params)
both can be called from the server-side

If I understand correctly I should use fetch when I want to fill the store and asyncData when I want to set up component data.
But asyncData can access store too. So why there are these two methods?

fetch for vuex, asyncData for page data?

Use asyncData only when you need to return data for the current component.
Use fetch when you want to work with the store.

@cretueusebiu answer is the one :)
When you need to fetch some data for the store especially for a specific page (like search results), use fetch, otherwise, use asyncData.


get/set currentFolder and None

I'm trying to figure out how to change the currentFolder. Right now, I can only get it working by changing back to root.
securityHandler = arcrest.AGOLTokenSecurityHandler(username, password)
content = arcrest.manageorg.Administration(url, securityHandler).content
user = content.users.user()

for folder in user.folders:
        title = folder['title']
        print("Analyzing {}".format(title))
        user.currentFolder = title

Here's the output from the interpreter:
>>> print(user.currentFolder)
{'username': None, 'created': None, 'id': None, 'title': 'root'}
>>> user.currentFolder = "scada"
>>> print(user.currentFolder)
{'username': 'Paul', 'title': 'SCADA', 'id': 'bedd85f873ba4fe0b061ec2873ccec89', 'created':<PHONE_NUMBER>000L}
>>> user.currentFolder = None
>>> user.currentFolder = "downloads"
>>> print(user.currentFolder)
{'username': 'Paul', 'title': 'Downloads', 'id': '8c60bceab595422595526ebf039fdadb', 'created':<PHONE_NUMBER>000L}
>>> user.currentFolder = "scada" # this won't change back to the scada folder
>>> print(user.currentFolder)
{'username': 'Paul', 'title': 'Downloads', 'id': '8c60bceab595422595526ebf039fdadb', 'created':<PHONE_NUMBER>000L}

ref

Here is an example of get/set the currentFolder:
    admin = arcrest.manageorg.Administration(securityHandler=sh)
    content = admin.content
    user = content.users.user()
    for folder in user.folders:
        print ("looking in folder: ", folder)
        user.currentFolder = folder['title']
        print (user.items)

Hope this helps.

Thanks Andrew for the example.
Thanks Mike for the latest commit. It's working great.


Delete phrase from custom category

Description:

Adds logic to allow user to delete a phrase from a custom category directly from the list of phrases
The phrase will be totally deleted from the database if it is only associated with the category currently being viewed. Otherwise it will remain in the database for its other categories
Figma link

When I delete the last phrase in a category, the page numbers at the bottom go a little weird.

When I delete the last phrase in a category, the page numbers at the bottom go a little weird.

Actually looks like Cameron resolved this in #285

Verified phrases can be deleted individually.
Verified Confirmation modal popup.
Verified, if the same phrase is in multiple categories, they can be deleted independently, and is reflected accurately on the Home screen.


Refactor worker job handling

Register standalone job handler functions via decorator.
Make connection attrs and methods non private
Use snake-case names.
Disable some pylint errors.
Use super when possible.

I've ran a simple sanity test. Seems to work. Functionality shouldn't have been changed.

This is awesome! looks much leaner, great work!

I've tested plugins on both Python 2 and 3 now, and it seems to work. Besides the questions/comments above I think this is ready.

I will check it out and do a quick test

Great!

Looks good to me, I ran two or three plugins which train deep learning models, and they are functioning as expected, I do see a few error logs from console, but that seems from the browser.
I think we can merge this, thanks for the great job you did!

Maybe you want to bump the version number such that we can tell from the version in case there is problem.

I've bumped the version.


[PHPStanRules] Fixes #2405 Add ForbiddenMethodCallByTypeInLocationRule

All checks have passed 🎉 @TomasVotruba it is ready for review.
Question: When I add implements ConfigurableRuleInterface on the rule, The Code Analysis / Coding Standard README Sync (pull_request) action is Green, do you think I still need to manually add to packages/phpstan-rules/docs/phpstan_rules.md ? Or it will be re-generated next on merge?

rebased.

All checks have passed 🎉 @TomasVotruba I think it is ready.

Or it will be re-generated next on merge?

I plan to implement this in next day or two, so you can skip it completely now.

Thank you


[MODULES-378] Module resource loader follows symbolic links (1.8.x)

1.8 port of #250
JIRA: https://issues.redhat.com/browse/JBEAP-18544
Upstream issue: https://issues.redhat.com/browse/JBEAP-18585 / https://issues.redhat.com/browse/MODULES-378
Upstream PR: #251 / #250

@dmlloyd i think the failures were caused by missing backport of MODULES-395. I opened #253 to fix that


Giveaway Sorter: fix compatibility with Giveaway Extractor for non-cached results

GA Sorter works for GAs extracted with GA extractor only when using cached results. Non-cached results refuse to sort, either via autosort or manually. A functional workaround is to (re-)extract and then simply to refresh the page, as the refresh then enables the sorter.
Tested in new tabs with 8.3.0 on latest Pale Moon.

It's working fine for me, so perhaps I already fixed it with #1243. Can you try the latest pre-release?

Sure. I installed 8.3.2-dev.2 and will find a moment to look at those issues again tomorrow.

Yeah, looks like that fixed it. Nice; thanks.


Need a config option to turn off humanize().

Version latest version
Expected behaviour
I want my labels to be rendered as-is and not be modified by the tcomp-form lib..
Actual behaviour
Your humanize function is messing my labels up .

@rahimlila The humanize function is just trying to provide meaningful defaults. You can override them https://github.com/gcanti/tcomb-form/blob/master/GUIDE.md#label

I'm using v 0.6.3 but cannot seem to get this working. upgrading to latest
breaks the whole app, so that would be painful.
how can i get this to work with 0.6.3?
On Mon, May 16, 2016 at 2:42 PM Giulio Canti<EMAIL_ADDRESS>wrote:

Closed #328 https://github.com/gcanti/tcomb-form/issues/328.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/gcanti/tcomb-form/issues/328#event-662217391


Unable to create authority

Hi,
I am trying to get Lemur up and running for internal use in my company. The inital idea is to use Lemur for automating certificate generation and distribution to our nodes for internal security.
While creating an authority using CFSSL plugin I get following error:
[2017-04-24 14:40:17,169] ERROR in schema: Unable to load certificate
Traceback (most recent call last):
File "/www/lemur/lemur/common/schema.py", line 158, in decorated_function
resp = f(*args, **kwargs)
File "/www/lemur/lemur/authorities/views.py", line 223, in post
return service.create(**data)
File "/www/lemur/lemur/authorities/service.py", line 108, in create
cert = upload(**kwargs)
File "/www/lemur/lemur/certificates/service.py", line 220, in upload
cert = Certificate(**kwargs)
File "", line 4, in init
File "/www/lemur/lib/python3.4/site-packages/sqlalchemy/orm/state.py", line 414, in _initialize_instance
manager.dispatch.init_failure(self, args, kwargs)
File "/www/lemur/lib/python3.4/site-packages/sqlalchemy/util/langhelpers.py", line 66, in exit
compat.reraise(exc_type, exc_value, exc_tb)
File "/www/lemur/lib/python3.4/site-packages/sqlalchemy/util/compat.py", line 187, in reraise
raise value
File "/www/lemur/lib/python3.4/site-packages/sqlalchemy/orm/state.py", line 411, in _initialize_instance
return manager.original_init(*mixed[1:], **kwargs)
File "/www/lemur/lemur/certificates/models.py", line 125, in init
cert = lemur.common.utils.parse_certificate(kwargs['body'])
File "/www/lemur/lemur/common/utils.py", line 53, in parse_certificate
return x509.load_pem_x509_certificate(body, default_backend())
File "/www/lemur/lib/python3.4/site-packages/cryptography/x509/base.py", line 43, in load_pem_x509_certificate
return backend.load_pem_x509_certificate(data)
File "/www/lemur/lib/python3.4/site-packages/cryptography/hazmat/backends/multibackend.py", line 341, in load_pem_x509_certificate
return b.load_pem_x509_certificate(data)
File "/www/lemur/lib/python3.4/site-packages/cryptography/hazmat/backends/openssl/backend.py", line 1175, in load_pem_x509_certificate
raise ValueError("Unable to load certificate")
ValueError: Unable to load certificate
Unable to load certificate
Traceback (most recent call last):
File "/www/lemur/lemur/common/schema.py", line 158, in decorated_function
resp = f(*args, **kwargs)
File "/www/lemur/lemur/authorities/views.py", line 223, in post
return service.create(**data)
File "/www/lemur/lemur/authorities/service.py", line 108, in create
cert = upload(**kwargs)
File "/www/lemur/lemur/certificates/service.py", line 220, in upload
cert = Certificate(**kwargs)
File "", line 4, in init
File "/www/lemur/lib/python3.4/site-packages/sqlalchemy/orm/state.py", line 414, in _initialize_instance
manager.dispatch.init_failure(self, args, kwargs)
File "/www/lemur/lib/python3.4/site-packages/sqlalchemy/util/langhelpers.py", line 66, in exit
compat.reraise(exc_type, exc_value, exc_tb)
File "/www/lemur/lib/python3.4/site-packages/sqlalchemy/util/compat.py", line 187, in reraise
raise value
File "/www/lemur/lib/python3.4/site-packages/sqlalchemy/orm/state.py", line 411, in _initialize_instance
return manager.original_init(*mixed[1:], **kwargs)
File "/www/lemur/lemur/certificates/models.py", line 125, in init
cert = lemur.common.utils.parse_certificate(kwargs['body'])
File "/www/lemur/lemur/common/utils.py", line 53, in parse_certificate
return x509.load_pem_x509_certificate(body, default_backend())
File "/www/lemur/lib/python3.4/site-packages/cryptography/x509/base.py", line 43, in load_pem_x509_certificate
return backend.load_pem_x509_certificate(data)
File "/www/lemur/lib/python3.4/site-packages/cryptography/hazmat/backends/multibackend.py", line 341, in load_pem_x509_certificate
return b.load_pem_x509_certificate(data)
File "/www/lemur/lib/python3.4/site-packages/cryptography/hazmat/backends/openssl/backend.py", line 1175, in load_pem_x509_certificate
raise ValueError("Unable to load certificate")
ValueError: Unable to load certificate
What can I do now.

Please ensure that the following values are set in your lemur.conf:
http://lemur.readthedocs.io/en/latest/administration.html?highlight=CFssl#cfssl-issuer-plugin

What is the syntax for those values?  Common names?  Paths to a pem file?

They are strings, if you want to read from a file you can use open('myfile.txt', 'r').read().

Thank you.  Providing the public certificate via a file solved my errors.

Appolgies for coming back again on this and that too so late. I did try to stick in the pem formated string in the CFSSL_ROOT parameter but I still get the same error

@gunjanvarshney do you have the other values defined per the docs? What version of Lemur are you running?

I am not sure what version is lemur as I followed steps on http://lemur.readthedocs.io/en/latest/quickstart/ but on centos. there would be dependencies differences but I was able to make it.
I have following in my ~/.lemur/lemur.conf.py file
CFSSL_URL =
CFSSL_ROOT =
CFSSL_INTERMEDIATE =

Are the above variables set? Do they have values?

yes both URL and Root have values. intermediate doesnt. do you want me to send the details.

Make sure you are including the entire PEM file.
It should look something like:
CFSSL_ROOT="""-----BEGIN CERTIFICATE-----
MIIEGjCCAwICEQCbfgZJoz5iudXukEhxKe9XMA0GCSqGSIb3DQEBBQUAMIHKMQsw
...
TxzhT5yvDwyd93gN2PQ1VoDat20Xj50egWTh/sVFuq1ruQp6Tk9LhO5L8X3dEQ==
-----END CERTIFICATE-----
"""


Adds Top Level CORS MIddleware

Description
Recently pulled the latest version of supersim and was running into cors issues again. We recently updated how the reverse proxy is created and how we forward the requests. The issue is we aren't adding the cors header back to the response. The last issue was related to not handling options request.
This PR adds a top level cors middleware that handles options requests and applies the cors headers to all responses so we can avoid breaking this again in the future.

looks good to me. A lot cleaner to use middleware


NotionClient class was renamed to Client

Hello! I don't know if this was planned due to it being a beta version and whatnot, but using notion_api: ^2.0.0-beta2 in the dependencies and using the example, there is an error due to a class name change from NotionClient to Client.
I'm not familiar with issues or commenting on other people's packages, just wanted to let you know that the example is outdated with the most recent version 😁

Yeess, I'm so sorry but I haven't touch this project in a while and I could not finish to let the beta version working, so probably is as you say and the fact that probably notion already change stuff with his API, but I'm not sure.
If it helps feel free to use the code as a base because I don't know when I'm going to be able to work again in this package, but thank you for letting me know, I will let the Issue open hoping for the best 😢


Support for delegates.

This could be really appreciated in some cases. While it's probably an edge case for standard message serialization, it would really simplify process of restoring behavior from events/snapshots of actor's state in persistence scenarios.

Done, bith normal delegates and closures are now supported.


Fix conflicting parameter types in definition warnings

At Timehop we build our app with the -Weverything flag and the DeskApiClient produces a lot of warnings that we don't feel comfortable suppressing. We've created our own fork of this repo and have manually disabled this warning using #pragma clang diagnostic ignored in each offending file. But an ideal solution would be to fix the warnings.
To reproduce the problem you can add -Woverriding-method-mismatch to Other Warning Flags in the Xcode build settings.

We created an internal work item to address this in the future. We'll definitely take a look at cleaning up these warnings. Thanks!

@nartiles Just wondering if there's been any progress on this. Thanks a lot!

@mergesort We took a look at the warnings and they are not valid. We set the appropriate class at runtime of these DSAPIResource subclasses to match what's in the method names so these are fake warning. See
DSAPIResource.m, - (instancetype)initWithDictionary:(NSDictionary *)dictionary client:(DSAPIClient *)client
...
// Set the class of the object to the class returned by the web service for self
   object_setClass(self, [self.client classForClassName:_dictionary[kLinksKey][kSelfKey][kClassKey]]);

It is safe to suppress them. We have no plans to add #pragma statements at this time to suppress this.
Instead of forking your own code to suppress these, we recommend you simply use Inhibit all warnings on the DeskAPIClient framework or pod.


PHP 5.4 compatibility issues

Getting Started
The above page says that Doctrine 2 is PHP 5.4+ compatible but in reality it is not.
The class Doctrine\Common\Proxy\ProxyGenerator contains the following code which requires PHP 5.5 and above:
    protected $placeholders = [
        'baseProxyInterface'   => Proxy::class,
        'additionalProperties' => '',
    ];

PHP 5.5 - New features - class name

You can explicitly require older doctrine/common. Version 2.6 (current) requires 5:5+, older version PHP 2.5 requires PHP 5.4+.

Okay. Thank you. Are they interchangeable? Should I expect any major drawbacks in the functionality?
I already have the Domain structure and I am just trying to use it on different machine where the PHP currently cannot be upgraded.

Docs page indeed needs updating: specifically, removal of explicit requirements, since composer tells you those.
We could simplify it to something like "always use the latest stable version of PHP".
Anyway, this is typically caused by a composer update issued on a machine with newer PHP versions, and then deploying via composer install on a machine with older PHP versions (tip: don't do that, or specify a platform version in your composer.json).
If you want to help out with the wording, check getting-started.rst and edit it to reflect the wording that you'd prefer.

Was handled by @BreiteSeite in #5892


add image to launch screen and change login screen (remove facebook a…

…nd google buttons)

 change design for login and launch screens


Feature Request: Specifying valid dates that are not neighboring

I have a use-case where the user should choose a date from a list of dates that are not neighboring/contiguous. For example:
04-10-2018
04-11-2018
04-13-2018
04-17-2018
04-18-2018
04-19-2018

As you can see, there are some missing dates: 04-12-2018, 04-14-2018, 04-15-2018, 04-16-2018.
Would you be able to augment the element to support this use case? The existing min-date and max-date properties on px-calendar-picker don't suffice, unfortunately. One way might be with a valid-dates property that takes an array.

Maybe you can consider using a dropdown instead if it's just a list of specific dates

That's a nice, simple solution. I'll go that way for now, thanks!


Can't locate specified Dockerfile: Dockerfile

Hi, Marcel
I tried to run containers, but error occurs like the below,
$ docker-compose up -d
Creating network "dockercitoolstack_prodnetwork" with driver "bridge"
Creating volume "dockercitoolstack_nexus-data" with default driver
Creating volume "dockercitoolstack_jenkins-data" with default driver
Building nexus
ERROR: Cannot locate specified Dockerfile: Dockerfile

I guess that there is something wrong at your docker-compose.yml.
services:
nexus:
build: ./docker-nexus3 -> ./nexus
Could you check it out?

Nexus directory is actually a nested git repo, so when you start clone, you
also must define:
git clone --recursive http://...
On Mar 18, 2018 3:08 PM, "unipark00"<EMAIL_ADDRESS>wrote:
Hi, Marcel
I tried to run containers, but error occurs like the below,
$ docker-compose up -d
Creating network "dockercitoolstack_prodnetwork" with driver "bridge"
Creating volume "dockercitoolstack_nexus-data" with default driver
Creating volume "dockercitoolstack_jenkins-data" with default driver
Building nexus
ERROR: Cannot locate specified Dockerfile: Dockerfile
I guess that there is something wrong at your docker-compose.yml.
services:
nexus:
build: ./docker-nexus3 -> ./nexus
Could you check it out?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/marcelbirkner/docker-ci-tool-stack/issues/63, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AbrAG3YZXRcO-42Tyq0jInN_mYM6uS7Mks5tfk4ugaJpZM4SvK8W
.

hi even am getting the same error with docker compose file

i am getting this error. Please help me.
ERROR: Cannot locate specified Dockerfile: Dockerfile


[HUDI-1997] Adding Note for explicitly setting HIVE_AUTO_CREATE_DATABASE

What is the purpose of the pull request
Update the documentation to add a note for setting HIVE_AUTO_CREATE_DATABASE
Brief change log
Updated configurations.html to add note
Committer checklist

[X] Has a corresponding JIRA in PR title & commit

[X] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@n3nash @vinothchandar  pls review


[6.0][Concurrency] Don't error on isolated property wrapper initializers inside MainActor-isolated structs.

Explanation: The following code currently emits an error under -swift-version 6:
@MainActor
protocol InferMainActor {}

@propertyWrapper @MainActor
struct Wrapper<T> {
  var wrappedValue: T {
    fatalError()
  }

  init() {}
}

@MainActor
class C {
  nonisolated init() {}
}

struct S: InferMainActor {
  @Wrapper var value: C // error: main actor isolated default value in a nonisolated context
}

This was caused by a rule that removed @MainActor from stored properties, which was gated behind -swift-version 6. This rule is incorrect, because the property can have an isolated default value. The proper rule for allowing nonisolated access to isolated stored properties of structs within the module is proposed in SE-0434, and implemented under GlobalActorIsolatedTypesUsability.

Scope: Only impacts stored properties of global-actor-isolated structs under the Swift 6 language mode.

Risk: Low; the change only impacts the Swift 6 language mode, which isn't yet in a shipping version of the Swift compiler.

Testing: Add a test case.

Reviewer: TBD

Main branch PR: https://github.com/apple/swift/pull/73168

@swift-ci please test


Add build option for coverage

Description

In order to get coverage output that can be parsed by tools like gcov, it is necessary to build with special flags:  -fprofile-arcs and -ftest-coverage

This currently means that one must add the following arguments to colcon build:
--ament-cmake-args -DCMAKE_CXX_FLAGS="${CMAKE_CXX_FLAGS}  -fprofile-arcs -ftest-coverage " -DCMAKE_C_FLAGS="${CMAKE_C_FLAGS}  -fprofile-arcs -ftest-coverage "

For example, see https://ci.ros2.org/view/nightly/job/nightly_linux_coverage/210/consoleFull

While this is manageable in a CI server, it is burdensome when trying to generate coverage locally because of the length of the argument and the subtleties of escaping the arguments for CMake.

This issue proposes adding a flag (e.g., --with-coverage-flags) to colcon build which wraps the long arguments above.

Naturally, for other supported compilers (clang?), the with-coverage-flags option could also handle the specific compile flags.

Motivation

Making it easier for developers to generate coverage locally

Expected  behavior
colcon build --with-coverage --ament-cmake-args <other args>

works like
colcon build --ament-cmake-args -DCMAKE_CXX_FLAGS="${CMAKE_CXX_FLAGS}  -fprofile-arcs -ftest-coverage " -DCMAKE_C_FLAGS="${CMAKE_C_FLAGS}  -fprofile-arcs -ftest-coverage " <other args>

Optionally, it could be useful to also include -DCOVERAGE_RUN=1 such that developers can adjust test behavior during coverage test runs.

For example, any timing-sensitive tests will tend to fail during coverage runs because of the extra CPU cycles, so the threshold for timeouts may need to be adjusted: e.g.,

#ifdef COVERAGE_RUN
    timeout = 20
#else
    timeout = 5
#endif

Future work

There could also be an extension to colcon test_results to digest coverage results: e.g.,

colcon build --with-coverage
colcon test
colcon test_results --output-coverage

There are certainly many different cases where simplifying the command line arguments would be beneficial. I am not sure what the right approach for that would be.
I don't think adding those to colcon-core is a good approach since there is an infinite amount of different ones which could be useful and the "core" tries to be as small as possible - e.g. it doesn't know about CMake. colcon-cmake could be a package where this feature is added but I am not even convinced that adding a command line option to "abbreviate" the verbose version is the right way to go.
I would image this more like a "profile" / "config" feature. Somewhere there is a set of preconfigured options like "coverage" which defines to what existing command line options this should expand to. Maybe something like the --meta option or along those line. I haven't used it for such a case yet but it might be a starting point.

@dirk-thomas I think something like the --meta feature may be a clean way to implement this feature. A generic solution could be to allow aliasing of command line parameters? e.g.,
People could define an alias in the root of their workspace:
{
    "build": {
        "symlink-install": true
        "arg-alias": {
            "with-coverage" : "--ament-cmake-args -DCMAKE_CXX_FLAGS=\"${CMAKE_CXX_FLAGS}  -fprofile-arcs -ftest-coverage \" -DCMAKE_C_FLAGS=\"${CMAKE_C_FLAGS}  -fprofile-arcs -ftest-coverage\" "
        }
    }
}

So
colcon build --with-coverage

would expand to the long command
The challenges I see are that:

It would require some modifications so that if a non-existent argument is passed to colcon, colcon will look in the .meta file for aliases before exiting with an error.
It would require some changes to the argument parser to include these aliases in colcon --help
Arguments like --ament-cmake-args would need to become additive, so that one could use:

colcon build --with-coverage --ament-cmake-args <more-args>

Escaping characters (like quotes) could be a pain

While this could be realized as a "verb alias" I do see a couple of downsides / limitations to it:

Making the argparse infrastructure aware of these requires first parsing some arguments, then using those to find additional configuration files declaring aliases, and then add those to the argparse structure (in order to show up in --help etc.). This approach sounds rather complicated and especially runtime-complex to me (e.g. considering completion needs to do the same).

The alias approach limits each "configuration snippet" to be used separately. Thinking about what kind of "configuration snippets" could be useful would include things like:

coverage
memory sanitizer
debug / release (with different optimization options as well as directories)
arguments for cross compilation

That being said I would rather like see these kind of "configuration snippets" as mixins. So it should be able to choose multiple (assuming they don't collide / contradict each other) at the same time. So e.g. "memory sanitizer" together with "debug" or "coverage" together with "release" (not really good examples but I guess it clarifies the idea).
Those "mixins" could be contributed in a similar way as the .meta files in the colcon-metadata-repository and then easily shared and used by all users interested in them.

@dirk-thomas If I understand correctly, what you are proposing would look something like:

There exists a project similar to colcon-metadata-repository, let's call it colcon/colcon-mixin-repository

Register the mixins from the repository:

colcon mixins add my-mixins https://raw.githubusercontent.com/colcon/colcon-mixin-repository/master/index.yaml

Update mixins:

colcon mixins update my-mixins

They are now available in colcon build:

$ colcon build --help
...
Mixin arguments:
  --with-coverage    Equivalent to --ament-cmake-args _DCMAKE_...
  --debug-build      Equivalent to --cmake-args -DCMAKE_BUILD_TYPE=Debug
  --compile-aarch64  Equivalent to --cmake-force-configure, --cmake-args ...
...

And the .mixin file could be something like:
{
    "build": {
        "with-coverage": [ "--ament-cmake-args -DCMAKE_...."],
        "debug-build": ["--cmake-args -DCMAKE_BUILD_TYPE=Debug"],
        "compile-aarch64": [
            "--cmake-force-configure",
            "--cmake-args ..."
        ]
    }
}

If I understand correctly, what you are proposing would look something like:

Exactly - thanks for the more concrete summary :+1:

They are now available in colcon build:

I would probably lean toward colcon build --mixin with-coverage debug-build (so making the mixin names parameters of an actual --mixin argparse option. That would give you all the freedom for naming the mixins without the chance of colliding with other options in the future.
I am just not sure yet how all these aspects should play together in the bigger picture: metadata, defaults, mixins, profiles (like in catkin-tools), etc. :thinking:

Please see the new package colcon-mixin and the corresponding data repository colcon-mixin-repository which has a few PRs with some proposed mixins.
Any feedback on this is appreciated.

@dirk-thomas Thanks! I've created this PR which can close this issue


R.swift

Description

Added R.swift to the project (this process includes a run script). Note that when you add new resources you'll need to run the project to generate the references, not just build.
Updated all "stringly typed" resources except for Strings, since those are all localized in PR #61.
Updated the ReadMe with a blurb about R.swift and a reminder to run bundle install when getting started. (I'll be happy to update with anything else y'all think should be added!)

Let me know if you have any questions! This isn't necessary, but will help with localization, adds extra type safety, and it's just nice, y'know?

Note that when you add new resources you'll need to run the project to generate the references, not just build.

@iosjillian Are you sure that's true? The Run Script Build Phase should be done before we compile sources right?

(also, why the hell haven't I used R.swift before, this is awesome)

@subdigital I agree that's how it should work, but in practice it seems to be a little finicky. I just tested it out, and looks like building twice works if building once doesn't detect the change ¯_(ツ)_/¯


Notify Cluster Level Critical Events and CrashLoopBackOff Events in pods

This PR addresses #129 and #106,

alerts on CrashLoopBackOff events occurring in pods ( when pods are being watched )
alerts on cluster level critical events like

NodeNotReady
NodeReady
NodeRebooted (by default)

removes New() func from event pkg to enhance simplicity
removes action filed from notify function in all handlers to enhance simplicity
retrieves namespace value and name from event key, if empty.
modified msteam_test.go suitably to test functionalities.
minor bug fixes
fixing typos

Preview :
CrashLoopBacKOff when Pods are Being Watched

Cluster Level Critical Events (Configured by default)

Thoughts and Comments..?

I would like to get it reviewed and merge it.
@jbianquetti-nami @jjo and @tylerauerbeck do share your views.

Thanks @jbianquetti-nami, hope we could merge this PR as @jjo approves it.

@jbianquetti-nami and @jjo,
I have updated the implementation to make pkg event look better and to support future development.
do have a look and let me know your comments.

Any updates on this..??

Remider Ping
Could this be reviewed and merged..?

This would be great! I want this.

FYI, These features are now avalilable with Botkube  (0.9.0)
People in need can make use of it. :+1:

@mkmik rebased this PR, can this be reviewed and merged?

Yes!

bors r+

it's becoming clear that the current handler interface is not good; I'll continue your change and formalize the fact that the handlers receive an event


Support for openrouter API

It would be really great if you add support for this api operator, as it allows to use most of llms available so far. openrouter.ai

https://openrouter.ai/docs/quick-start
in the docs there's an option for using openai's api
you can change "model" : "blahblah" in your profile.js to
"model": {
  "api": "openai",
  "url": "https://openrouter.ai/api/v1",
  "model": "????"
},

Thanks for response


calledOnContract matcher requires provider that support call history

I'm trying to use calledOnContractWith in a simple test:
const calc = (await deployContract(owner,
      FixedRatesCalculatorArtifact,
      [toWei("999"), toWei("1000")])) as FixedRatesCalculator;
    expect('setRates').to.be.calledOnContractWith(calc,[toWei("999"), toWei("1000")]);

I'm getting error:
Error: calledOnContract matcher requires provider that support call history
      at Object.ensure (node_modules/@ethereum-waffle/chai/dist/cjs/matchers/calledOnContract/utils.js:6:15)
      at Object.validateMockProvider (node_modules/@ethereum-waffle/chai/dist/cjs/matchers/calledOnContract/calledOnContractValidators.js:13:13)
      at Proxy.<anonymous> (node_modules/@ethereum-waffle/chai/dist/cjs/matchers/calledOnContract/calledOnContractWith.js:9:38)
      at Proxy.methodWrapper (node_modules/chai/lib/chai/utils/addMethod.js:57:25)

Trying to console.log here:

gives me:

deps:
"@nomiclabs/hardhat-ethers": "^2.0.2",
    "@nomiclabs/hardhat-truffle5": "^2.0.0",
    "@nomiclabs/hardhat-waffle": "^2.0.1",
     "@typechain/hardhat": "^2.1.0",
    "@types/mocha": "^8.2.2",
    "@types/node": "^15.0.3",
    "chai": "^4.3.4",
    "ethereum-waffle": "^3.2.0",
    "hardhat": "^2.4.1"

Hey @ppedziwiatr did you manage to fix that? I have the same issue trying to use this chai matcher

Hey @ppedziwiatr did you manage to fix that? I have the same issue trying to use this chai matcher

damn, that was quite a long time ago..not remember exactly, but probably not..

Any updates on this issue? It still happens

Currently, the ethereum-waffle package on its own supports the call history for Ganache providers.
In order to make this matcher work with Hardhat provider, you need to be using Waffle plugin supported by Hardhat which adds some plumbing in order to make the call history possible.
https://hardhat.org/plugins/nomiclabs-hardhat-waffle


zathura: update

Motivation for this change
Prompted by https://github.com/NixOS/nixpkgs/issues/36468, requires meson 0.45
Things done

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

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

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

@GrahamcOfBorg build zathura

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: zathura
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: girara
Partial log (click to expand)
/nix/store/5c74da2lnbqky6pr4a73vbq36hsxg9jy-girara-0.2.9

Failure on x86_64-darwin (full log)
Attempted: girara
Partial log (click to expand)
Project name: girara
Native C compiler: /nix/store/8b0gj3bmcy5bh1zcnhn0146199b3m5kb-clang-wrapper-5.0.1/bin/cc (clang 5.0.1 "clang version 5.0.1 (tags/RELEASE_501/final)")
Build machine cpu family: x86_64
Build machine cpu: x86_64

meson.build:33:0: ERROR: C library 'libm' not found

A full log can be found at /private/tmp/nix-build-girara-0.2.9.drv-0/girara-0.2.9/build/meson-logs/meson-log.txt
builder for '/nix/store/2ba6p4bqzd0aki78q1fjb8zajjyq5x3l-girara-0.2.9.drv' failed with exit code 1
error: build of '/nix/store/2ba6p4bqzd0aki78q1fjb8zajjyq5x3l-girara-0.2.9.drv' failed

Failure on aarch64-linux (full log)
Attempted: zathura
Partial log (click to expand)
   Compiling proc_macro v0.0.0 (file:///build/rustc-1.25.0-src/src/libproc_macro)
   Compiling rustc_const_math v0.0.0 (file:///build/rustc-1.25.0-src/src/librustc_const_math)
   Compiling syntax_ext v0.0.0 (file:///build/rustc-1.25.0-src/src/libsyntax_ext)
building of '/nix/store/0p4h4m63ki245n14vpk2xihn23lq1a4a-rustc-1.25.0.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/apcj2slll2axzpsnpyw7qxq0mymqdhly-cargo-0.26.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/qi8m0z84cdhfspfx4chzl5ffamky2pm6-librsvg-2.42.2.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/51ql8gdyzkbc3mik7nqmyzxxf38by52d-djvulibre-3.5.27.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/1zjdh94j73b440qh7kabrqh6ykv6z34y-zathura-djvu-0.2.8.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/f3367gzik1vyzvmm73r0gj1y7vgpsfk3-zathura-with-plugins-0.3.9.drv': 1 dependencies couldn't be built
error: build of '/nix/store/f3367gzik1vyzvmm73r0gj1y7vgpsfk3-zathura-with-plugins-0.3.9.drv' failed

Success on x86_64-linux (full log)
Attempted: girara
Partial log (click to expand)
-
-

0

100 65464  100 65464    0     0  65464      0  0:00:01 --:--:--  0:00:01 82656


Null object but with 100+ mods installed

Describe the bug

Null object reported by user with over 100 mods installed.
Code review to spot maybe where it occurs? I can't see it
        private void Update()
        {
            if (ZNet.instance == null || !(Time.time > lastUpdate)) return;
            if (ReturnHome())
            {
                dropoffTarget = GetNearestDropOffPoint();
                if (dropoffTarget == null)
                {
                    NeckroStatus = "Can't find a container";
                }
                else
                {
                    NeckroStatus = $"Moving toward {dropoffTarget.name}";
                    if (CloseToDropoffPoint())
                    {
                        DepositItems();
                    }
                }
            }
            else
            {
                LookForNearbyItems();
                PickupNearbyItems();
                //todo: loot dead gatherers
            }

            if (ShowMessages.Value
                && NeckroStatus != ""
                && Vector3.Distance(Player.m_localPlayer.transform.position, transform.position) < 5)
            {
                Chat.instance.SetNpcText(gameObject, Vector3.up, 5f, 2f, "", NeckroStatus, false);
            }

            lastUpdate = Time.time + UpdateDelay.Value;
        }

        private void LookForNearbyItems()
        {
            // get all nearby items
            Collider[] hitColliders = Physics.OverlapSphere(transform.position + Vector3.up, LookRadius.Value, autoPickupMask);
            if (hitColliders.Length < 1) return;
            // order items from closest to furthest, then take closest one
            Collider closest = hitColliders
                .OrderBy(col => Vector3.Distance(transform.position, col.transform.position))
                .FirstOrDefault();
            if (closest != null)
            {
                ItemDrop itemDrop = closest.GetComponentInParent<ItemDrop>();
                if (itemDrop != null)
                {
                    if (TryGetComponent(out MonsterAI monsterAI))
                    {
                        // move toward that item
                        NeckroStatus = $"Moving toward {itemDrop.m_itemData.m_shared.m_name}";
                        monsterAI.SetFollowTarget(itemDrop.gameObject);
                        return;
                    }
                }
            }
        }

        private void PickupNearbyItems()
        {
            List<string> itemNames = new();
            Collider[] hitColliders = Physics.OverlapSphere(transform.position + Vector3.up, PickupRadius.Value, autoPickupMask);
            foreach (var hitCollider in hitColliders)
            {
                ItemDrop itemDrop = hitCollider.GetComponentInParent<ItemDrop>();
                if (itemDrop != null)
                {
                    if (itemDrop.CanPickup())
                    {
                        itemNames.Add(itemDrop.m_itemData.m_shared.m_name);
                        StoreItem(itemDrop, container);
                    }
                }
            }

            NeckroStatus = itemNames.Count > 0
                ? $"Picking up {string.Join(", ", itemNames)}"
                : "Looking for items...";
        }

I think I found and fixed this. It was happening before the game properly loaded because
            if (ShowMessages.Value
                && NeckroStatus != ""
                && Vector3.Distance(Player.m_localPlayer.transform.position, transform.position) < 5)

did not check if localPlayer is null or not.


Added Run-Unit-Test to Cake build

Fixed link in README.md

This PR adds Unit test execution to the build pipeline.  I commented out the failing test.  I have a separate branch trying to fix those.

Please check the cake plugin, it seems that's not compatible with our version of cake.


Add a license to the repository

I recently came across your project qiskit-ibm-hackathon-2024 and I noticed that the repository github.com/kandaurovnet/qiskit-ibm-hackathon-2024 currently does not have a license specified.
Why Adding a License is Important?
As GitHub documents

Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you'll need to license it so that others are free to use, change, and distribute the software.

Would be possible to add a valid license to this repository? Probably something really OpenSource such as the Apache 2.0 license would fit really well.
Thanks!

Thanks for the note, done 👍

Thanks!


[UI]Finalise eslint and all commands

Eslint is added with all errors removed.
Lot of work is pending but I have managed to suppress the warnings.
CI is integrated for lint too.

@leecalcote Successfully integrated EsLint for UI:

Added CI command.
Added makefile command, need to update documentation that pleases run make run-ui-lint before committing changes.
Fixed all the errors, there were 200 errors remaining which were more of a labour work than actual logic hence I have converted them into warnings which may be solved by new-contributors and I will open a tracking issue for same.

Remaining :

Completing integration for Provider-UI.
I will integrate pre-commit-hook which will run lint command as soon as developers do  git commit _______

@leecalcote Is it good to be merged?

LGTM, That's quite a bit of cleaning though! Woof.. :+1:

Thanks for this makeover, @kush. No small bit of work. 🔨

@nveenjain For your reference

--fix will fix up all the lint errors until it is out of bound for
ESLint, hence fix is the best option for it.
Constant declaration and then changing its value is considered as bad
practice for a good developer.
A production open source project should be free from commented code. I
still dont understand point of having this much commented code, not only it
decreases code quality but also creates hurdle when new contributors get to
know the codebase.

On Tue, 7 Apr, 2020, 21:24 Lee Calcote<EMAIL_ADDRESS>wrote:

Thanks for this makeover, @KuSh https://github.com/KuSh. No small bit
of work. 🔨
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/layer5io/meshery/pull/797#issuecomment-610469450, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQMTLRA7ITMNLWPPERLLWTRLNEENANCNFSM4MBK4P5Q
.

@kushthedude, while I agree that --fix will fix all errors, but adding them in lint command is not required, eslint should report these errors and the developer can run eslint --fix on it. lint should not fix any error, it should just check for errors.
Because it may happen that someone pushes the code without running lint command, and in the CI no error will be seen. Since --fix option is applied. However the code would not have been change, it would just change on the CI server.
I agree that constant declarations are good, that's why I think that there we should use const instead of var (which is ES5 already).
Agreed that open source project should be free from irrelevant comments, that's why I think that the comments in ui/components/CustomToolbarSelect.js should also be removed.

Removing comment is totally labour work, I am working on a script to do the work for me. Meanwhile if you want to remove them from other go+js files, please be my guest.
--fix args is the best option, moreover there are 150+ errors of useless props and unused variable which I have turned them into warnings. Again, that is a pure labour work for which I will open a tracking issue so that all new contributors or existing may take up a file and refine it.

We should use --fix, most of the projects do.

yes @snitin315 , --fix should be used, but it should not be used while we lint, by lint, I mean run as part of test in CI job for the project, it should be used as a separate command, by the developer.
All the top projects related to JS directly use eslint command, --fix will result in extra errors.
It should be executed by the developer side and not during test.
For reference:-
https://github.com/facebook/react/blob/master/package.json#L105 (its a script that import eslint and doesn't use --fix option)
https://github.com/babel/babel/blob/master/Makefile#L112
https://github.com/webpack/webpack/blob/master/package.json#L134
https://github.com/graphql/graphql-js/blob/master/package.json#L31
--fix option can be run once offline and it will fix all the errors eslint can fix, and it won't be required again.

Well we can have two different scripts as well.
lint and lint:fix

Yes, that would be perfect.
As long as lint:fix doesn't runs as a part of tests, it would work, and in
some cases even help developers who will be able to fix eslint errors using
npm run lint:fix instead of specifying eslint path(from node modules or
from global installation) with --fix option.
On Tue, Apr 7, 2020, 11:44 PM Nitin Kumar<EMAIL_ADDRESS>wrote:

Well we can have two different scripts as well.
lint and lint:fix
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/layer5io/meshery/pull/797#issuecomment-610542058, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNVFRMNDZZPXDXUWB4UPYLRLNUQZANCNFSM4MBK4P5Q
.

I'm also thinking to integrate lint-staged and husky. What do you think?
I can create a PR if you agree.

Sounds good @snitin315, but I guess @kushthedude maybe already working on it as per https://github.com/layer5io/meshery/pull/797#issuecomment-609471616 please confirm.

I'm also thinking to integrate lint-staged and husky. What do you think?
I can create a PR if you agree.

You may go ahead once this PR is finalised, also try to integrate go-precommit if possible else no issues.

Yes, that would be perfect. As long as lint:fix doesn't runs as a part of tests, it would work, and in some cases even help developers who will be able to fix eslint errors using npm run lint:fix instead of specifying eslint path(from node modules or from global installation) with --fix option.
…

Comment to your point, developers won't be using npm run lint as we already makefile support. Make lint will do the thing for them including fixing the lints issues. Running the linter and then again running the fix command is obviously the pain in the back. Also, most of the packages you mentioned are services which are used by-products. Most end products integrate the fix with linter to save running another command and not to mention save resources.
A big project usually takes 3-5 minutes to run linter to check the rules, not wasting another 3-5 minutes for linter to fix the obvious indents & literals is not productive in my pov.

@leecalcote Please check if anything is remaining, I will open the tracking issues for the lint warnings once this gets merged.

I agree with @kushthedude.

Most end products integrate the fix with linter to save running another command and not to mention save resources.
@kushthedude, having eslint --fix will result in errors, as CI will never report any error that can be fixed by eslint. CI would fix it's own copy of the repository. If we are saving efforts of running a command that would be run once by developer while that could cause more errors in the repository, that would not be a good design...
All the products (including the tools used in JS) only use eslint.
For reference, all the JS end products in trending section on GitHub right now using eslint without --fix option
https://github.com/trekhleb/javascript-algorithms/blob/master/package.json#L7
https://github.com/RocketChat/Rocket.Chat/blob/develop/package.json#L29
https://github.com/jitsi/jitsi-meet/blob/master/package.json#L141

I think you don't understand the term.use of resources. At once you are concerned about the lint script and now you are concerened about the lint introduced in CI. Also FYI, there will be no errors as after merging of this @snitin315 will introduce the pre-commit hooks for lint which means before every git commit, Lint script will be run on local . I dont know where do you get yourself confused in this easy chain of command, it would be better if you read the my initial comment on this PR for flow of operations after this. If you still have any doubt, ping me I will help you understand.

Since this conversation with @nveenjain is going to nowhere and only resulting in more difference arguments from initial one.
@leecalcote can you please check the above code and flow of operations listed by me in initial comments? Let me know if there is anything missing or needs to be amend.

@nveenjain there will be no chances of having lint errors, if user have any they will be fixed before committing the changes.

My take is lint command should just check for the lint and it should not fix any errors.
As mentioned in https://github.com/layer5io/meshery/pull/797#issuecomment-610548249 and https://github.com/layer5io/meshery/pull/797#issuecomment-610511259
If we are relying solely on git hooks, to fix the eslint errors, then there should not be any reason to include lint in CI, as no one will be able to commit without eslint errors. git hooks can be skipped, and if they are, it should result in error anyhow if checking on CI,but it wouldn't in current premises. Most projects I pointed out also have pre-commit hooks, but linting step doesn't fix the errors automatically there too. Some do provide a separate command to let eslint auto-fix, but that is a separate command and not used either in git pre-commit or while testing.

You are asking for the following conf.
For CI - lint
For hook - lint:fix

Yeah, this is the way it should be. CI should never fix any error.

So what do you want, developers to commit the un-linted code and see the CI
check , oh my code is not linted and push the code again.
CI reinforcements of tests is for double check and maintaining the quality
of delivery to be made from next commit. Going your way, I should remove
the fix script and not setup hooks and let developers wait for CI to fail
and then again push the linted code.
On Wed, 8 Apr, 2020, 12:40 Naveen jain<EMAIL_ADDRESS>wrote:

My take is lint command should just check for the lint and it should not
fix any errors.
As mentioned in #797 (comment)
https://github.com/layer5io/meshery/pull/797#issuecomment-610548249 and #797
(comment)
https://github.com/layer5io/meshery/pull/797#issuecomment-610511259
If we are relying solely on git hooks, to fix the eslint errors, then
there should not be any reason to include lint in CI, as no one will be
able to commit without eslint errors. git hooks can be skipped, and if they
are, it should result in error anyhow if checking on CI,but it wouldn't in
current premises. Most projects I pointed out also have pre-commit hooks,
but linting step doesn't fix the errors automatically there too. Some do
provide a separate command to let eslint auto-fix, but that is a separate
command and not used either in git pre-commit or while testing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/layer5io/meshery/pull/797#issuecomment-610791090, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQMTLV6RD6OPYYZQ6HHF5DRLQPOZANCNFSM4MBK4P5Q
.

also eslint --fix does not work for all rules.

I will wait for @leecalcote now, it has been converted into an argument
from a PR review which is still ambiguous.
On Wed, 8 Apr, 2020, 12:52 Nitin Kumar<EMAIL_ADDRESS>wrote:

also eslint --fix does not work for all rules.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/layer5io/meshery/pull/797#issuecomment-610795542, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQMTLWRF7GQNJOTSTJQFTTRLQQ2DANCNFSM4MBK4P5Q
.

don't worry I will configure such that the changes will be staged.

@leecalcote Good to be merged ?

@leecalcote Good to be merged ?

I think so, yes. I've put this as a topic in today's community meeting. Could you socialize this update and what it means to contributing to the UI?

@leecalcote update ?

Given the amount of discussion generated and implications of this change, a verbal discussion is warranted, I think. Can we get this on the agenda of this week's developer meeting?
What do contributors updating the UI need to be aware of given the changes here? Are those considerations incorporated into CONTRIBUTING docs?

Given the amount of discussion generated and implications of this change, a verbal discussion is warranted, I think. Can we get this on the agenda of this week's developer meeting?
What do contributors updating the UI need to be aware of given the changes here? Are those considerations incorporated into CONTRIBUTING docs?

Sure! Contributors must be aware of the new rules we have incorporated of which one of the biggest & most ignored rule in our codebase in importing of unused variables & blank variable assignments.
Also, we have to update the docs to let contributors know about lint script so that CI doesn't fail on their Pull Request.
We can definitely have a discussion for this & then move ahead.


Call shaders out as individual objects accessible outside the toolkit

We need some representation of the shaders outside the core C++.
This means being able to instantiate them from the ObjC/Swift and Java/Kotlin levels.

We are still going to do this at the C++ level.  But not, for the moment, at the higher level interfaces (Swift, Java).


By default I get a 0.2 score match

Hello!
I trying to use this gem to find similar Car Makes, but I'm getting a result I don't understand:
If I have the make Citroen and I look for the make "Volkswagen" I get the "Citroen" make:
FuzzyMatch.new(['Citroen']).find("Volkswagen") -> Citroen
FuzzyMatch.new(['Citroen']).find_with_score("Volkswagen") -> ["Citroen", 0.13333333333333333, 0.19999999999999996]
How is this possible? Am I doing something wrong? How can I change the threshold?
Thanks!

As far as I understand, it searches the best match from the given list. As you only have one entry in that list (Citroen), it's automatically picked as best match. Put all car brands in that first list and it will probably work as you expect.

That is correct. What was bothering me was getting 0.13 instead of nil or 0. But I guess the "-en" was giving that scoring. Thank you @gr8bit


Additional vector tests

Have to merge https://github.com/earthlab/matplotcheck/pull/203 before this one.

Heya @nkorinek - not 100% sure whether this is a fix, but do you need to set the matplotlib backend to get these commented out tests to work? e.g., in test_vector.py at the top:
... # other imports
import matplotlib
matplotlib.use('Agg')

# awesome tests
...

@lwasser Alright I think I'm happy with how much of the code is tested now! Let me know what you think and if I need to look into adding anymore vector tests.

Heya @nkorinek - not 100% sure whether this is a fix, but do you need to set the matplotlib backend to get these commented out tests to work? e.g., in test_vector.py at the top:
... # other imports
import matplotlib
matplotlib.use('Agg')

# awesome tests
...

THANK YOU @mbjoseph !! so appreciative of your help!

Ok @lwasser , I went through and renamed variables you pointed out had confusing names, and hopefully clarified a lot of the confusion. I think this is ready for another review!

ok once CI finishes I will merge this!!


🐛 [BUG]: onConnect method in useHandleConnections does not fire even if handle id is explicitly specified

Is there an existing issue for this?

[X] I have searched the existing issues and this is a new bug.

Current Behavior
This has been discussed in https://github.com/bcakmakoglu/vue-flow/issues/1480. However, onConnect does not fire now.
Expected Behavior
onConnect should fire when connect happens.
Steps To Reproduce
git clone git@github.com:ljw20180420/vueFlowBug.git
cd vueFlowBug
npm run dev
Delete the initial connection by `backspace`. `onDisconnect` is fired and `console.log` is called.
Try to connect the edge back. `onConnect` is not fired.

onConnect from useVueFlow() works just fine. However, I have several types of nodes. I want to push the onConnect logic in the definition file of nodes, so that I do not need to determine node type by if or switch.
Relevant log output
Anything else?
No response

Works completely fine for me in a sandbox.
From what I can tell though you're just misunderstanding onConnect of useHandleConnections.
const conns = useHandleConnections({
    type: 'source',
    id: 's',
    onConnect: params => {
        console.log("onConnect", params);
		// You cannot attempt making connections here, this callback is not triggered for connections attempted but connections *made*
        // addEdges([
        //     {
        //         ...params,
        //         type: 'myEdgeType',
        //         updatable: true
        //     }
        // ])
    },
    onDisconnect: params => {
        console.log("onDisconnect", params);
    },
});

This is not fired when a connection is attempted but is fired when a connection is made, meaning the global onConnect event is for attempts and is fired before onConnect of useHandleConnections triggers, which is only triggered if a new edge is actually created that connects to that handle.


Add support for command HSCAN

Add support for the HSCAN command in DiceDB similar to the HSCAN command in Redis. Please refer to the following commit in Redis to understand the implementation specifics - source.
Write unit and integration tests for the command referring to the tests written in the Redis codebase 7.2.5. For integration tests, you can refer to the tests folder. Note: they have used TCL for the test suite, and we need to port that to our way of writing integration tests using the relevant helper methods. Please refer to our tests directory.
For the command, benchmark the code and measure the time taken and memory allocs using benchmem and try to keep them to the bare minimum.

I would like to work on this

@Saitharun279 Thanks for taking this up. assigned.

Hey @Saitharun279 , are you still working on this? Will be happy to pick this up!

Hey @Saitharun279, are you still working on this issue? If not, Can I pick this up?

Hey @iamskp11 , @anchalsinghrajput
im actively spending time on this issue, i would need some more to finish it as im new to golang

I see it open from long time. I can take it up if it's not making any progress.

I've created the PR for this command - #907

Unassigned my self
@manishrw please ask the moderators to assign this to you

@arpitbbhayani  can you assign this to me ??

Hello @manishrw,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

Hello @manishrw,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

@lucifercr07 Can we mark this as done? I think it keeps getting flagged for @arpitbbhayani

Closing, merged as part of https://github.com/DiceDB/dice/pull/907


Make sure subscriptions have nice JSON output

Some minor issues. And could you put a json ignore tag on deleted at?

lgtm


fix ErrorHandler unittest

Fixes #6175

Beginning pylint and unit tests.
See https://cmssdt.cern.ch/jenkins/job/DMWM-PR-test/579/ for details

Summary of pylint changes for pull request 6252:

Score for test/python/WMComponent_t/ErrorHandler_t/ErrorHandler_t.py decreased from 9.58 to 9.57

test/python/WMComponent_t/ErrorHandler_t/ErrorHandler_t.py got worse in pylint. Report follows:

Line 40 in ErrorHandlerTest R0902 Too many instance attributes (8/7)
Line 126 in ErrorHandlerTest.createWorkload W0613 Unused argument 'workloadName'
Line 126 in ErrorHandlerTest.createWorkload W0613 Unused argument 'emulator'
Line 134 in ErrorHandlerTest.createWorkload W0612 Unused variable 'rereco'
Line 196 in ErrorHandlerTest.createTestJobGroup W0612 Unused variable 'i'
Line 231 in ErrorHandlerTest.testA_Create W0612 Unused variable 'workload'
Line 285 in ErrorHandlerTest.testB_Submit W0612 Unused variable 'workload'
Line 319 in ErrorHandlerTest.testC_Jobs W0612 Unused variable 'workload'
Line 356 in ErrorHandlerTest.testD_Exhausted W0612 Unused variable 'workload'
Line 406 in ErrorHandlerTest.testE_FailJobs W0612 Unused variable 'workload'
Line 498 in ErrorHandlerTest.testZ_Profile W0101 Unreachable code
Line 498 in ErrorHandlerTest.testZ_Profile W0612 Unused variable 'cProfile'
Line 40 in ErrorHandlerTest R0904 Too many public methods (25/20)
Line 33 W0611 Unused import Report
Line 30 W0611 Unused import Configuration
plus 112 comments on code style

Unit test changes for pull request 6252:

WMComponent_t.ErrorHandler_t.ErrorHandler_t.ErrorHandlerTest:testA_Create changed from failure to success
WMCore_t.WorkQueue_t.Policy_t.Start_t.Block_t.BlockTestCase:testRunWhitelist changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testCloseWorkOpenBlocks changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testPriority changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testQueueChainingStatusUpdates changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testResubmissionWithParentsWorkflow changed from success to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testSiteStatus changed from failure to error
WMCore_t.WorkQueue_t.WorkQueue_t.WorkQueueTest:testTeams changed from failure to error

It cannot be that this fix would affect even WorkQueueTest:testTeams... I'll look at it tomorrow.

No, I think those are the recently unstable tests. You could clean up the pylint stuff.

When test changed from success/fail to error, it seem it most likely one of the unittest wasn't able to clean up the db.  (Hopefully patch Valentin is working on should remove that problem)
Yes, you should just ignore WorkQueue errors.

Sure! Pylint stuff cleaned up. Also marked the profilling test as integration.

Beginning pylint and unit tests.
See https://cmssdt.cern.ch/jenkins/job/DMWM-PR-test/580/ for details

No pylint warnings for pull request 6252:

Unit test changes for pull request 6252:

WMComponent_t.ErrorHandler_t.ErrorHandler_t.ErrorHandlerTest:testA_Create changed from failure to success
WMComponent_t.ErrorHandler_t.ErrorHandler_t.ErrorHandlerTest:testZ_Profile was deleted. Prior status was success
WMCore_t.JobSplitting_t.EventAwareLumiBased_t.EventAwareLumiBasedTest:testH_LumiCorrections was added. Status is success

@ticoann feel free to merge this request


Segment snap

Replaces #15306. This is the reviewed and amended version of that pull request by @manisandro.

Thanks!


Clarify what is sent between sensors and localisation

The topic names, message types, and contents of messages is not intuitive enough today. This should be refactored such that names, topics, and contents of messages are self-explanatory.

@torgeirgrini any updates on this?

The ESKF takes inn two nav_msgs/Odometry, one which holds the z value in meters from the pressure measurement, and one which holds the linear acceleration values from the DVL (pressureZ_topic and dvl_topic in parameters yaml-file). These values are all published in one topic from the DVL (auv/odom), https://github.com/vortexntnu/dvl1000_ros. The ESKF also listens to a topic from the IMU (imu/data_raw) https://github.com/vortexntnu/stim300.

Closing in favor of the new work on the EKF


How to create a custom metric function by mx.metric.np in python?

For example, if I need a metric of "error rate" or some other metrics like that in R api, how to make it?

You could use EvalMetric add pass it to the model.fit function with eval_metric parameter. You could see https://github.com/dmlc/mxnet/blob/master/python/mxnet/metric.py for more details.

The mx.metric.np function takes a numpy function as the first argument which is of the form callable(label, pred). It returns an EvalMetric object that should be passed to model.fit function with eval_metric argument.
See here and here for more details.

@jermainewang Still can't understand. I tried some but got wrong results. Could you please give an example how to write a callable metric like "err rate"?

@jermainewang Thx. I've figured it out.


Raster reprojection source resolution

Related to PR #4122
When reprojecting tiled-based raster sources, required source resolution is calculated precisely for each reprojected tile (in it's center) using ol.reproj.calculateSourceResolution.
The resolution to be used (zoom level) is then selected from the available resolutions on the tile grid using ol.tilegrid.TileGrid#getZForResolution, which by default finds the nearest resolution (and zoom level). (The zoom level is then constant for the whole reprojected tile.)
This sometimes results in magnification:

Some better method for resolution selection could be implemented to improve the visual quality by changing this.srcZ_ = sourceTileGrid.getZForResolution(sourceResolution); in ol.reproj.Tile to different algorithm.

Always-magnify approach produces very blurry results (ol.array.linearFindNearest(sourceTileGrid.getResolutions(), sourceResolution, 1);):

Always-shrink approach (ol.array.linearFindNearest(sourceTileGrid.getResolutions(), sourceResolution, -1);) sometimes works better:

, but more data have to be loaded and labels can be hard to read:

Alternatively, some new threshold value can be added to determine, when round the resolution up and when down (0.5 would be equal to the "closest").

These issues were created so we document the knowledge, but they are not active issues being worked on, so I'm going to close them.
Thanks for documenting them though @petrsloup they will be kept for posterity.


Activation URL expiration

Is there any settings or mechanisms to set expiration time for activation URL?

There is no actual expiry of the URL but the token which is used for the Activation URL, we can change it expiry trough
https://docs.djangoproject.com/en/3.1/ref/settings/#password-reset-timeout-days


[fix]: Use pascal casing for type names in structs generated by abigen

This fixes Issue #2129. Additionally, the versions of crates thiserror and anyhow where downgraded a couple of minor versions so that cargo check --all-features passes. The versions in the lock file used unstable features.

I have removed the changes to the lock file.

ty!


Missing fields

Hey there - just wanted to FYI that there are a few fields missing for Organizations

image_url
looks like metadata doesn't load properly
a few more I'm missing - will update

Hey @stevenschmatz , we're looking into this and will revert shortly !

Hey @stevenschmatz ! I wanted to circle back here. Were you able to pull SDK methods used / debug logs? Happy to look deeper into this.


(POC) execute puppet until idempotent

Sometimes it takes more than one run to reach desired state after install.

I've always wanted an execute_puppet_until_idempotent function.


[NetworkX-compatibility][Graph-construct]Maybe use a patch on immutable graph to implement arrow graph to dynamic graph [Proposal]

patch a non-CSR on original CSR (when arrow property to dynamic)
set dead/alive tomb when modify CSR.
when iterate edges or nodes, skip the dead nodes/edges. (check in the iterations implementation)

Note: the life-cycle of immutable graph and mutable graph should be consistent.

As we optimize the process with multi-threading by #1458, close this.


Upgrade ActionControllerSubscriber filtering for Rails 7 compatibility

Overview
When running the unit test suite against Rails version 7.0.0.rc1 on Ruby 2.7.x and Ruby 3.0.x, the following error is raised:

Error: NewRelic::Agent::Instrumentation::ActionControllerSubscriberTest#test_records_filtered_request_params_in_txn:  Expected: "[FILTERED]" Actual: "secret"
Test Line: test/new_relic/agent/instrumentation/rails/action_controller_subscriber.rb:289

This indicates a change in Rails 7 that breaks the mechanism the agent uses to filter secret information from request params within transactions.
Prerequisites

Have Ruby 2.7.5 and 3.0.3 installed (for help installing Ruby versions, we often use rbenv)
Create a branch off of test/rails-7-upgrade

To run the failed file: bundle exec rake "test:env[rails70]" "file=test/new_relic/agent/instrumentation/action_controller_subscriber_test.rb"
To run the failed test:
bundle exec ruby test/new_relic/agent/instrumentation/rails/action_controller_subscriber.rb -n /test_records_filtered_request_params_in_txn/
T-Shirt Size
Small (1 day - 4 days)

@tannalynn and I resolved this error on December 15, 2021. The work is included in #878


Restructure Router Folder for Improved URL Structure

Issue Description:
The current structure of our router folder could benefit from a more organized and understandable layout. We aim to reorganize it by creating a Next.js route group for the 'overview' section, which will contain the following routes:

overview
destinations
sources

Scope of Work:
Create a new route group named 'overview' within the router folder.
Inside the 'overview' route group, add routes for 'overview,' 'destinations,' and 'sources.'
Ensure that the routes are configured correctly, matching their respective components or page files.
Update the navigation links and any references to these URLs to reflect the new structure.
Ensure that all existing functionality and data retrieval are maintained during this restructuring.
Test the updated structure to confirm that it works as intended.
Skills Needed:

Proficiency in Next.js routing and folder structure.
Knowledge of JavaScript and web development.
Experience with route handling and navigation.

Expected Outcome:
The restructuring of the router folder will result in a more logical and organized URL structure, making it easier for developers and users to understand and navigate our project. This improved structure should contribute to a better overall user experience and maintain the integrity of our existing functionality.
Note: Adapt this issue to the specific needs and technologies used in your project. Be sure to provide more details and context in the actual issue description when creating it in your repository.

@alonkeyval I would like to work on it, Please assign this to me

@Kritik-J Good luck!


Update targeted content documentation

Revise usage wording

Closing this. Was just using it to show James how previews and editing work.


Special Case for 10.7: New BrowserHax Usable ala TubeHax DNS

I would like to propose 2 changes to Part 1 the guide.

Because there is a new Browserhax that works for 10.6 and 10.7. 10.6 can use the new BrowserHax by using Yellows8's Bypass method, as that wasn't patched until 10.7.

9.9.0 - 10.5.0: Follow this guide as written.

should be changed to

9.9.0 - 10.6.0: Follow this guide as written.

As for 10.7, in many cases, users rarely use the 3DS Internet Browser, and since this is often the case the update nag may not have been triggered yet, it's probable that users with 10.7 could run the new BrowserHax if they enable the old TubeHax DNS on their internet connections before proceeding to scan the BrowserHax QR code, followed by using the new MenuHax 3.0 to install the new MenuHax, and then removing the TubeHax DNS before proceeding with the guide. (To prevent future issues with blocking the update servers and what not in the event of a softbrick)
How this should be phrased is up to you, but I actually can confirm this works as a viable entrypoint for free homebrew access on 10.7, as I myself just yesterday helped my friend downgrade from 10.7 this way.

Oh, one more tidbit: It's also important that you mention that if the user does get the nag, than they will have to seek alternative entrypoints, since there's really no way to stop that nag once you get it the first time.

jaxrogers2 mentioned in another ticket that as far as browser goes, 10.7 is considered the same as 11.0 and so blocking the update servers is not necessary,  https://3dbrew.org/wiki/Internet_Browser doesn't list any browser changes from -32 to -33.

Fixed


Use go modules

This PR modifies to use go modules instead of vendors to manage dependent libraries, and use GitHub Actions as CI.
Release steps in CI will be added in the next PR.
Closes #46

lgtm pretty much the same I did locally 👍
Why did you remove wercker.yml though ?

Why did you remove wercker.yml though ?

I've deleted that file in this PR because I'll change the release step in the next PR to also run in GitHub Actions.


auth: isUser/Builder/Admin refactor

Description
Introduce isUser isBuilder isAdmin helper function on WorkspaceType to avoid referring to particular role and in particular role === "builder" || role === "admin". Also introduces isOnlyUser isOnlyBuilder isOnlyAdmin to test if a WorkspaceType has exactly this role.
The use of assertNever will make adding a new role in the future much safer.
Attempted to remove as many reference to actual roles in the code as possible
Risk
Touches auth logic. Risk of error is low but impact of error is high.

cc @dust-tt/engineering-team please use these functions instead of testing the actual owner.role values :pray:


Not working with Ionic 3

kindly check following post & update for Ionic 3
https://forum.ionicframework.com/t/cannot-find-name-animationmodule/84483?u=mubasshir

I updated mine to ionic3... I had to do this:
run this:
$ ionic plugin add ionic-plugin-keyboard
$ npm install --save @ionic-native/keyboard

add this line:
import { Keyboard } from '@ionic-native/keyboard';

inject it into the constructor:
constructor(public evts: Events, private keyboard: Keyboard) {}

ngOnInit:
 ngOnInit() {
    /**
     * Hide the wizard buttons when the keyboard is open
     */
    this.keyboard.onKeyboardShow().subscribe(() => {
      this.hideWizard = true;
    });
    this.keyboard.onKeyboardHide().subscribe(() => {
      this.hideWizard = false;
    })
  }

Untested at the moment.


(docs)(DOCUMENT-809) Fix typos in PDB client tools docs.

Fix a typo causing errors in an example, and fix a spelling error in and clarify a related note.

Test PASSed

CLA signed by all contributors.


Adding name to TODOs

One of the TODO from previous PR review was to add names to TODOs, so here they are :)
cc @G-Harmon

Rebased to resolve conflicts with https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress/pull/3


[widget/29783]- chartBuilderWidget created to build charts using highcharts library

chartBuilderWidget created to build charts using highcharts library
https://pmdb.fortinet.com/ProjectManagement/editprojects.php?id=29783

Moved to gitlab

Moved to gitlab hence closing the PR


Add support for KIWI Door Locks

Description:
Added support for the KIWI Door lock platform (https://kiwi.ki).
Pull request in home-assistant.github.io with documentation (if applicable): https://github.com/home-assistant/home-assistant.github.io/pull/5381
Example entry for configuration.yaml (if applicable):
lock:
  - platform: kiwi
    username<EMAIL_ADDRESS>    password: supersecretpassword

Checklist:

[x] The code change is tested and works locally.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

Successor of #12304

https://github.com/c7h/kiwiki_client/issues/1 should be addressed upstream and the requirement updated.


Stacktrace related features do not work when a localized version of .Net is used

AxoCover needs to parse the stack trace of errors for a number of features. If a non-English version of .Net is used on the machine, the English words in the stack trace (at, file, line) are replaced by localized versions, in some cases additional punctuation e.g. : is also used.
As the tests might require the locale to set to certain values, the likely solution will be to write a smarter parser which can identify the method name, the file path and the line number even if the rest of the stacktrace contains localized data.

Fixed in <IP_ADDRESS>.


App Name
Strike
App Website
strike.me
Other notes
Strike now interprets the lightning parameter on BIP21 URIs and attempts a Lightning payment when present. It does not generate BIP21 URIs with lightning parameter when requesting BTC though.

Fixed in #72


add legacy interfaces

Motivation
Add the original Seaport 1.1 interfaces for Consideration and Zone.

Solution

Codecov Report
Base: 65.45% // Head: 99.95% // Increases project coverage by +34.50% :tada:

Coverage data is based on head (83b08bf) compared to base (4b2c048).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #941       +/-   ##
===========================================
+ Coverage   65.45%   99.95%   +34.50%
===========================================
  Files         108       47       -61
  Lines        4443     2429     -2014
  Branches      561      351      -210
===========================================
- Hits         2908     2428      -480
+ Misses       1508        0     -1508
+ Partials       27        1       -26

Flag
Coverage Δ

foundry
?

production
100.00% <ø> (ø)

reference
99.91% <ø> (ø)

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

Impacted Files
Coverage Δ

reference/ReferenceConsideration.sol
96.87% <0.00%> (-0.19%)
:arrow_down:

contracts/lib/Executor.sol
100.00% <0.00%> (ø)

contracts/lib/Assertions.sol
100.00% <0.00%> (ø)

contracts/lib/AmountDeriver.sol
100.00% <0.00%> (ø)

contracts/lib/OrderCombiner.sol
100.00% <0.00%> (ø)

contracts/lib/CounterManager.sol
100.00% <0.00%> (ø)

contracts/lib/OrderFulfiller.sol
100.00% <0.00%> (ø)

contracts/lib/ZoneInteraction.sol
100.00% <0.00%> (ø)

contracts/lib/TokenTransferrer.sol
100.00% <0.00%> (ø)

contracts/lib/CriteriaResolution.sol
100.00% <0.00%> (ø)

... and 80 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fix TensorType to return new TensorTypes for shapes instead of TensorType instances

This ensures that TensorType is never actually instantiated and instead new TensorType subclasses are created (and cached) for each shape.
This is a stepping stone to a fully generic TensorType where the dtype and shape are modeled into the type itself, but it appears that won't be easily realized until we can depend on Python 3.11.
Importantly, this adds unit tests to ensure if we can move to a proper generic that behavior will remain the same.
Fixes #219

Hold on merging this. Trying to figure out what stopped working on 3.7 and 3.8.


Cray Shasta support for Charm++ 6.10.x ?

Hi, I was wondering whether you have plans to add support for Shasta on the previous Charm++ version 6.10.x.
Context:
I have noticed support has been added through PRs #3497 and #3499 and is available in 7.0.0.
However, there are issues with the Molecular Dynamics code NAMD, which uses Charm++.
The latest NAMD version, 2.14, only builds with Charm++ 6.x, while it crashes with 7.0.0 due to what seem API changes in Charm++. Development versions of NAMD also seem not to have support for 7.0.0 yet.
Thanks in advance, Marco

That should be possible, I'll investigate and see if we can put out a point release for 6.10.x to add support there.
Separately, the development version of NAMD (both master and devel) at https://gitlab.com/tcbgUIUC/namd should work with 7.0.0 and the current main of Charm++ as far as I know. If you're having issues building that, then there's probably some bug that we need to fix. Can you provide more details about whatever error you're seeing with the development build?

Thanks for the feedback @rbuch!
I do have a colleague who is looking into patching 6.10.x for Shasta, I might join to this conversation when he's happy with his solution.
Regarding issues in building with Charm 7.0.0, note I was using NAMD release 2.14, not master/devel.
In this context, I did get errors that seemed related to API changes in Charm, for instance:
src/NamdCentLB.C:597:24: error: 'struct BaseLB::LDStats' has no member named 'n_objs'
  597 |   for (j=0; j < stats->n_objs; j++) {

Thanks for the feedback @rbuch! I do have a colleague who is looking into patching 6.10.x for Shasta, I might join to this conversation when he's happy with his solution.
Regarding issues in building with Charm 7.0.0, note I was using NAMD release 2.14, not master/devel. In this context, I did get errors that seemed related to API changes in Charm, for instance:
src/NamdCentLB.C:597:24: error: 'struct BaseLB::LDStats' has no member named 'n_objs'
  597 |   for (j=0; j < stats->n_objs; j++) {

Note how I am using Spack to install NAMD, Charm and their dependencies.
[edit]: I am getting the same errors also when trying to build NAMD version 2.15a1, and the master branch (as of today, 8 December)

Ah, okay, I misunderstood, then. It's expected that 2.14 and the current alpha of 2.15 won't build with 7.0.0, upcoming releases of NAMD should, however.
I'm working on creating a 6.10.3 release to add Shasta support, I'll update this issue when I have a candidate solution for that.

I've made a branch (https://github.com/halfflat/charm/tree/shasta-on-6.10.2) which pulls in the #3032,  #3497 and #3499 PRs onto v6.10.2, resolving conflicts and removing, as much as I noticed, any 7.0.0-specific dependencies. I've only confirmed that the mpi-crayshatsa and ofi-cratshasta targets build.
Would it be useful to submit this as a PR?

I've made a branch (https://github.com/halfflat/charm/tree/shasta-on-6.10.2) which pulls in the #3032, #3497 and #3499 PRs onto v6.10.2, resolving conflicts and removing, as much as I noticed, any 7.0.0-specific code. I've only confirmed that the mpi-crayshatsa and ofi-crayshasta targets build.
Would it be useful to submit this as a PR?

Your branch looks good and should be usable for your purposes, but it doesn't work for the CMake-based build (using ./buildcmake). It's not the default in 6.10.x, so it's not critical to have, but I'd like to have it working for the 6.10.3 release. That's where most of the complexity of backporting the Shasta support lies since that part has to be disentangled from the rest of the changes to the CMake build. That's what I'm working on right now, but until I finish that and put out the 6.10.3 release, you can use your branch.

Thanks for taking a look at it! The other thing I was hoping to add in a separate patch is an option to make +ofi_runtime_tcp on by default, so that we don't have to have people add it at invocation time. What do you think?


Update Rollbar JS snippet from 1.1 to 1.4

https://github.com/segment-integrations/analytics.js-integration-rollbar/blob/master/lib/index.js#L36
The current version of Rollbar we're loading is V1.1 via the snippet above. We should update that to 1.4, the latest version to take advantage of Bug Fixes and Improvements.
via Jeff Sinclar, Atlassian
Rollbar JS documentation
Rollbar GH repo

fixed in https://github.com/segment-integrations/analytics.js-integration-rollbar/pull/4


Change name from Drop App to Boxwise and add icons

See #26. I have searched for all occurences of the name and changed. Furthermore I added all versions of icons for all devices

Woot! Looks great!

✨ 🥊 🤓 ✨