Update mod-operator.md

Removed extra spaces.
Added result =  to its syntax. Because writing just num1 Mod num2 will generate a compile error. And also to be consistent with other articles like Not operator, Or operator, etc.
Added vb language to code snippet.
Updated division by zero as the information wasn't complete. (Explained in following images)

This looks good, @Youssef1313. Thanks for making the additional change. I'll merge your PR now.


Receiving below mentioned error while running the code

int' object has no attribute 'getitem': TypeError
Traceback (most recent call last):
File "/var/task/lambda_function.py", line 40, in lambda_handler
invoking_event = json.loads(event["invokingEvent"])
TypeError: 'int' object has no attribute 'getitem'

Which rule is it?

Closing, no update.


Dynamic loss scaling

This PR aims to support "dynamic" loss scaling.
Loss scaling is already available with current Chainer, but it is "static" loss scaling. You have to select an appropriate loss scaling factor before training, hence becoming kind of hyper parameter.
With this PR, there is no need to select scaling factor in advance. The appropriate scaling factor is dynamically determined by just adding following line to your training script.
optimizer.loss_scaling('dynamic', interval=1000)

When "dynamic" loss scaling is enabled, whole grads of parameters are checked every iteration, more specifically after backward() and before update() to see if there are NaNs in the grads. Initially the scaling factor is set to 1 and it will be doubled every iteration as long as there is no NaN in the grads. Once NaN is detected in the grads, the scaling factor will get halved. After that, the scaling factor is slowly increased every iteration so that it gets doubled in the specified "interval".
"Static" loss scaling is also supported and can be used as follows.
optimizer.loss_scaling('static', loss_scale=100.0)

Considering compatibility, optimizer.use_loss_scale(100.0) is also available.

Thanks for the PR! I have an idea for simplifying the interface: making the mode inferred from the option specified by the user. For example, loss_scaling(interval=1000) means dynamic scaling with interval 1000, while loss_scaling(scale=100.0) means static scaling with scale 100.0. Another idea would be to separate the method for each mode, e.g. loss_scaling for dynamic one and static_loss_scaling for static one. I prefer the former for its simplicity.

Sorry for the late comment. I think we want an additional argument to loss_scaling(interval=1000), to specify its initial scale. How about loss_scaling(scale=100.0, interval=1000), i.e. it turns dynamic when interval is specified? I am not too familiar with this technique though and it might be less obvious if we'd want the dynamic behavior as the default behavior (you'd probably have to pass interval=None).

I've just updated the PR based on the off-line discussion yesterday.
Please review it again.

Thank you for your detailed feedback, @hvy. I did code refactoring and clean-up based on your feedback. Could you review it again?

Is it difficult to write tests for these APIs?

Please wait for a while. I'm now considering how to test this API..

I've added some basic tests for static/dynamic loss scaling to existing test scripts: test_optimizers.py and test_optimizers_by_linear_model.py.  Could you review it?

jenkins, test this please.

Jenkins CI test (for commit 054aa9257675257807a2b598b2eb635eb09eb5a6, target branch master) succeeded!

LGTM!


full upgrade

Solution

[x] Upgrade X64 to 2. 98 + introducing ARM64 2.94
[x] apply example_ynh

PR Status

[ ] Code finished.
[ ] Tested with Package_check.
[ ] Fix or enhancement tested.
[ ] Upgrade from last version tested.
[ ] Can be reviewed and tested.

Package_check results

tested on x64-64 and aarch64

There was an error about nodejs fiber during upgrade from previous 2.56, now solved

2.99

Nice work!
So we just need to apply https://github.com/YunoHost-Apps/wekan_ynh/pull/44#discussion_r304615471 and then I can take this for a manual test run.
After that we could merge to the testing branch (once https://github.com/YunoHost-Apps/wekan_ynh/issues/42 is done).

Nice work!
So we just need to apply #44 (comment) and then I can take this for a manual test run.
After that we could merge to the testing branch (once #42 is done).

Just launch a new CI-Test

I just ran (on Yunohost 3.6.4):
$ yunohost app install https://github.com/yalh76/wekan_ynh/tree/2.98 --debug
... ldap login, poke around, create some things ...
$ yunohost app remove wekan

It all went well :+1:

Soooo shall we yolomerge this ?

Yaaaaaaar :fire: :fire: :fire:

yes, we can


My scroll wheel is too fast

i try to scroll on other app, it just runs normally, but if i scroll on vsc, it runs to fast. Very very fast. it is annoying.

Do you have a editor.mouseWheelScrollSensitivity setting?
What platform and version?
/needsMoreInfo

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

To my knowledge there is a vscode built in scroll sensitivity setting + many other mouse settings. I'd check those out.
editor > mouseWheelScrollSensitivity

Do you have a editor.mouseWheelScrollSensitivity setting?
What platform and version?
/needsMoreInfo

is it?,

@dyaksaadi  Can you try configuring editor.mouseWheelSensitivity to a smaller value like 0.1?

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


"Dumbrăveni", "Furnica" are listed in the drop-down menu

Description:
When user writes "Dumbrăveni", "Furnica" the location appears in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Dumbrăveni"

Expected results
The location appears in the drop-down menu as "Sat Dumbrăveni, CONSTANȚA, (Dumbrăveni)"

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Furnica"

Expected results
The location appears in the drop-down menu as "Sat Furnica, CONSTANȚA, (Dumbrăveni)"


Bug: Failed to configure neovim: failed to download configuration: HTTP status 404

After configure gh auth login, still get 404 when downloading raw file from public repo

The URL needs to be full: github.com/username/repo/master/blob/file


BUG: eigen3 and hdf5 fixes for windows and R

PR Checklist

[X] No API changes were made (or the changes have been approved)
[X] No major design changes were made (or the changes have been approved)
[ ] Added test (or behavior not changed)
[ ] Updated API documentation (or API not changed)
[X] Added license to new files (if any)
[X] Added Python wrapping to new files (if any) as described in ITK Software Guide Section 9.5
[ ] Added ITK examples for all new major features (if any)

After a restart of a couple of the builds, they all now pass! :tada:
@muschellij2 thank you for your patience and persistence in getting this fixed. Also, thank you for maintaining ITKR -- an awesome package! :-)


iam-assumable-role assume_role_policy showing changes without actual changes

Description
We're running into an issue with the iam-assumable-role submodule showing changes for aws_iam_role resource assume_role_policy field when no changes exist. This seems to trigger multiple data resource reads too creating a lot of plan noise.
One thing I noticed is that the list of Principals is reversed between the data aws_iam_policy_document and the  resource "aws_iam_role" field. Could this be the issue?

[x] ✋ I have searched the open/closed issues and my issue is not listed.

⚠ Note
Before you submit an issue, please perform the following first:

Remove the local .terraform directory (! ONLY if state is stored remotely, which hopefully you are following that best practice!): rm -rf .terraform/
Re-initialize the project root to pull down modules: terraform init
Re-attempt your terraform plan or apply and check if the issue still persists

Versions

Module version 5.44.0

Terraform version:
v1.9.5

Provider version(s):

provider registry.terraform.io/hashicorp/aws v5.64.0
provider registry.terraform.io/hashicorp/cloudinit v2.3.4
provider registry.terraform.io/hashicorp/external v2.3.3
provider registry.terraform.io/hashicorp/helm v2.14.0
provider registry.terraform.io/hashicorp/null v3.2.2
provider registry.terraform.io/hashicorp/time v0.12.0
provider registry.terraform.io/hashicorp/tls v4.0.5

Reproduction Code [Required]
Steps to reproduce the behavior:
 No.
 Yes.

module "iam_assumable_role" {
  source  = "terraform-aws-modules/iam/aws//modules/iam-assumable-role"
  version = "5.44.0"

  trusted_role_arns = [
        "arn:aws:iam::${var.account_ids.account_one}:root",
        "arn:aws:iam::${var.account_id}:role/{{REDACTED}}",
        "arn:aws:iam::{{REDACTED}}:role/{{REDACTED}}"
      ]

  create_role = true

  role_path         = "/internal/team"
  role_name         = "platform"
  role_requires_mfa = false

  custom_role_policy_arns           = [
        "arn:aws:iam::aws:policy/AdministratorAccess"
      ]
  number_of_custom_role_policy_arns = 1
}

Expected behavior
No changes show for a plan when no changes exist.
Actual behavior
Changes show for assume_role_policy on the role and multiple data resources load but no real changes exists.
Terminal Output Screenshot(s)

Additional context
Example plan output
We use this module within one of our own modules. That's why the resources show an extra layer. My example removes this layer and still has the issue.
  # module.team_roles["platform"].module.iam_assumable_role.data.aws_caller_identity.current will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "aws_caller_identity" "current" {
      + account_id = (known after apply)
      + arn        = (known after apply)
      + id         = (known after apply)
      + user_id    = (known after apply)
    }

  # module.team_roles["platform"].module.iam_assumable_role.data.aws_iam_policy_document.assume_role[0] will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "aws_iam_policy_document" "assume_role" {
      + id            = (known after apply)
      + json          = (known after apply)
      + minified_json = (known after apply)

      + statement {
          + actions = [
              + "sts:AssumeRole",
              + "sts:TagSession",
            ]
          + effect  = "Allow"

          + principals {
              + identifiers = [
                  + "arn:aws:iam::{{REDACTED}}:role/{{REDACTED}}",
                  + "arn:aws:iam::{{REDACTED}}:role/{{REDACTED}}",
                  + "arn:aws:iam::{{REDACTED}}:root",
                ]
              + type        = "AWS"
            }
          + principals {
              + identifiers = []
              + type        = "Service"
            }
        }
    }

  # module.team_roles["platform"].module.iam_assumable_role.data.aws_partition.current will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "aws_partition" "current" {
      + dns_suffix         = (known after apply)
      + id                 = (known after apply)
      + partition          = (known after apply)
      + reverse_dns_prefix = (known after apply)
    }

  # module.team_roles["platform"].module.iam_assumable_role.aws_iam_role.this[0] will be updated in-place
  ~ resource "aws_iam_role" "this" {
      ~ assume_role_policy    = jsonencode(
            {
              - Statement = [
                  - {
                      - Action    = [
                          - "sts:TagSession",
                          - "sts:AssumeRole",
                        ]
                      - Effect    = "Allow"
                      - Principal = {
                          - AWS     = [
                              - "arn:aws:iam::{{REDACTED}}:root",
                              - "arn:aws:iam::{{REDACTED}}:role/{{REDACTED}},
                              - "arn:aws:iam::{{REDACTED}}:role/{{REDACTED}},
                            ]
                          - Service = []
                        }
                    },
                ]
              - Version   = "2012-10-17"
            }
        ) -> (known after apply)
        id                    = "platform"
        name                  = "platform"
        tags                  = {}
        # (11 unchanged attributes hidden)
    }

It seems like this issue may be pointing to the same problem: #495

I'm also encountering this same issue.


Push to GitHub repository error too many redirects or authentication replays

Hi,
When I trying to push to GitHub repository it didn’t work, shows an error too many redirects or authentication replays, do you know how can I solve the problem?
Thank you ~

Problem solved - need add personal access tokens
https://code.thebaselab.com/guides/version-control

Problem solved - need add personal access tokens
https://code.thebaselab.com/guides/version-control


How can I get all the records the server had sent for a subscription?

As we know, despite this being a very common scenario, Meteor doesn't support querying against a publication, in other words finding on the clients all the records that a particular subscription has returned.
I have a large collection on the server called content, and different filters against it on the server (e.g. content of various types, search fields etc.), with differently named pub/sub for each: content for the most recent items, content-portfolio for content that matches a company in the user's portfolio. Without subs-manager, when the route changes from one view to another, the server resets the publication and I can simply find on the client all the records that the server has published for that view by running
Content.find({})

However, after adding subs-manager, the entire Content collection apparently gets cached on the client, not just the subscription, and Content.find({}) in the contentPortfolio route returns the most recent items as well from the content subscription.
I only use subs-manager for the content subscription, and a regular this.subscribe('content-portfolio') for the portfolio-filtered subscription.
Since subs-manager manages subscriptions at a very low level, it would be great if there were a mechanism to isolate records coming from a specific subscription. That would be a super useful feature and it would solve a very real problem with Meteor core.

I think we all good here.


Clicking on the ellipsis on the pagination component results in no page being selected

If your'e using the pagination component and click on the ellipsis between a set of pages,
it deselects the current page and the pagination resets. The handleChange event is still being
triggered for a click on the ellipsis, but it is then being passed through with a null value.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Clicking on the ellipsis in the pagination component resets the component,  and deselects any
value.
Expected Behavior 🤔
Clicking on the ellipsis should do nothing.
Steps to Reproduce 🕹
Steps:

Go to the example page https://mui.com/components/pagination/
Click on the ellipsis
The component resets.

This is made more obvious if you move forward a few pages and then click the ellipsis.
Context 🔦
The pagination is broken. If my users click the ellipsis, then the page breaks because context
of the current page is lost.
Your Environment 🌎
I'm not running this locally, so I don't have the information at this time, I noticed it on
a junior web developer test submission, and then confirmed it on your own example site.
I'm running Chrome Version 94.0.4606.71

Hard refresh on the docs site and try again. Thanks @kykungz


Update smb.conf

windows 10 clients cannot connect with user/password, only guest.

Hi @adipose,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


Replace "ignored" with "enabled"

A test is disabled with config(ignored = true) at the moment. This word resembles the annotation from JUnit 4 and (the somewhat awkward) ignore syntax from ScalaTest. JUnit 5 switches to "disabled", while TestNG uses "enabled". If you look at APIs in general "enabled" is pretty common. "ignore" would make more sence, if it were a method. But if we don't focus on the action (ignoring) but on the value (enabled or not), we could use the more common word for this status.
I suggest that we replace "ignored" with "enabled". Any objections?

I think in this case, you could argue for either, so its changing it just based on someone's preference.

I think you're right, it is a matter of taste and not worth the change.


Sizing issue with width-* and width-adjacent-* combinations

When width-* and width-adjacent-* combinations are used with form-col columns, the column padding is not taken into account, causing columns to expand beyond the width of the parent container.
Solution:
Use sass variables for column padding per column type (column border won't be configurable). Then subtract padding total from the width-adjacent calculations.
Current recommendation / workaround is to use content-col instead, as content-col has no padding or border and therefore the issue doesn't occur. If padding is required, any container or spacing can be nested directly inside these columns.

Slightly embarrassing that the actual problem turned out to be box-sizing: border-box missing from the form-col class. content-col never had a problem due to zero padding and there is no table-col class. Columns do not have any border, so that is not an issue. *-col classes without a column width suffix are for use when a percentage width is not required or when some other measurement unit needs to be applied. This will all be fixed and tested with a new table-col class added also.

Fixed issue as above.


refactor: day25 使用 list comprehension 簡化 function part1

I think using generator expression is fine and have no needs to change to list comprehension


Update CI jobs for current k8s versions

Describe what this PR does
Version 1.18.x is currently out, and the k8s community does not maintain
versions 1.14 and 1.15 anymore. No need to test on versions that users
should not deploy.
See-also: Kubernetes Patch Releases
Is there anything that requires special attention
Pass the Kubernetes version as an environment variable to the job. This
configuration automatically generates two jobs, one for 1.17.5 and one
for 1.18.2.
This makes it easier to maintain the testing matrix and update it in the future.
Related issues
Fixes: #1023

Adding the do-not-merge label as Travis CI does not seem to display the jobs correctly. The feedback from the Tarvis build is not available in this PR either?

Removing the [DNM] label as the adding of Kubernetes 1.18.2 did not work. Humble also sent a PR for that, so maybe we should go the known-to-work approach instead.


not working with Xcode 7.1

Since Xcode 7.1 bundle version should be of maximum 3 numbers (even for pods inside projects) so your <IP_ADDRESS> fails when I try to upload to iTunesConnect

Luckily, SQLite moved to semantic versioning beginning with 3.9.0. We can therefore change the version number and add the two zeros manually to the archive name (because internally, SQLite is still using 3090200 as archive and directory name for the 3.9.2 release...).
I pushed a new version '3.9.2' but this version is not shown as the newest one by CocoaPods, because it is positioned before '<IP_ADDRESS>' in ascending sort order.
Until then, please try using the following in your Podfile:
pod 'sqlite3', '3.9.2', inhibit_warnings: true
Does this work for you?

Hi @casim, luckily, SQLite is now using 3 numbers. I uploaded a new version of the sqlite3 pod (3.10.0).
I am closing this now, because having pod 'sqlite3', inhibit_warnings: true in your Podfile works again when pushing applications to the app store.
Please report back if you experience any problems.


kogito-quarkus support

Description
Hi,
In my organization, we use quarkus 3.X for our corporative framework and we need kogito for certain business proceses.
But we have the problem that latest version pubished in maven-central (2.44.0.Alpha) doesn't support quarkus 3 due to jakarta packages.
When will you release any version with full support for  quarkus 3 and jakarta packages?
Thank you!
Implementation ideas
No response

@ricardozanini
Thank you so much!
Could you tell me when do you expect the CI to be fixed and the sofware to be released?

Following up on this. Is there any timeline for or release schedule for Kogito?

it's expected that we'll branch this week!

Hi!
We are also really looking forward to the stable version. How soon is it?)

Hello there,
any news on this matter?
Thank you very much for your work!

We are still working on the release, we are getting there! 😅

Hi, do you have an ETA for the release ok Kogito with Quarkus 3?

it's expected that we'll branch this week!

I think I must have misunderstood what this meant xD Any news?

https://lists.apache.org/thread/g164c2z9y82l3bprmpn132zdwjk2nds8

Hello. Is there news on this subject?

Hi there. any news on the Quarkus 3 compatibility?

we are likely to run RC3 this week, so expected to have something out soon.

I saw the release vote closed on Thursday and there is a couple action items but looks like we are close?

blockers were found by IPMC, we are working to have rc4 this week

Hey @porcelli do you have any news for us on this topic?

10.0.0 has been released! https://kie.apache.org/blog/kie_10_0_0_release


[trivial] make: change dir for btcd

Not changing dir leads to the go.* files being modified when calling
make btcd (and every other command that requires btcd).
In addition, seems like we must change dir and install in the same
command for the dir change to actually be effective (macOS).

heh i didn't realize this ended up looking so close to #3521

Replaced by https://github.com/lightningnetwork/lnd/pull/3521


/play end should just be /play

Rationale
The /play end suncommand should still be named the same, since it performs exactly the same as the old /play. Having it as subcommand creates confusion, since it isn't obvious that end refers to the main play command with the default and expected behavior.
Description
Rework the subcommand /play end into the old /play.
Addendum
I'm not sure whether the existence of subcommands implies that the parent command cannot be called standalone. If that's the case, I'd very much suggest the current subcommands be moved to a different parent command and keeping the /play command as is.

Okay, I just proposed this to be the solution to #148, so I think we can kill two birds with one stone here as I agree that we should keep the normal play command as simply /play.

What name should we give to this advanced play command? How about /splay for "super play"?

That's a good suggestion (although in my mind it was suggested from "special play"). Another alternative is "advanced play", so /aplay, /advplay or any other variant.

What name should we give to this advanced play command? How about /splay for "super play"?

I feel that using /splay would be inconsistent with other commands such as, for example, /forceskip. I wouldn't mind if this advanced play command had a longer name (like /superplay or /advancedplay), since Discord has an autocomplete function and we could just use tab-complete to access it.

@danrpinho I really like /superplay!


Instance of RequestHandlerInterface classes fail

class HomePage implements \Psr\Http\Server\RequestHandlerInterface  {
    public function handle(\Psr\Http\Message\ServerRequestInterface $request): \Psr\Http\Message\ResponseInterface
    {
        $response = new Response();
        $response->getBody()->write("Hello world!");
        return $response;
    }
}
$app->get('/', new HomePage());

and
$app->get('/a', new class implements \Psr\Http\Server\RequestHandlerInterface  {
    public function handle(\Psr\Http\Message\ServerRequestInterface $request): \Psr\Http\Message\ResponseInterface
    {
        $response = new Response();
        $response->getBody()->write("Hello world!");
        return $response;
    }
});

Should both work. Tested in Slim 4.x and I get a  {} is not resolvable RuntimeException in CallableResolver line 82.
https://i.19ft.com/590bcaba.png

Fixed by #2571


I seem unable to make a netconf request to set data in the startup datastore or copy to the startup datastore

Hi,
I am trying to copy data from Running to Startup or just event set data in Startup and seem unable to do either.
I dont know the exact NETCONF request for copying but I want to achieve something similar to the sysrepo function call
int sr_copy_config(sr_session_ctx_t *session, const char *module_name,
        sr_datastore_t src_datastore, sr_datastore_t dst_datastore);

i.e. copy all the config from Running to Startup for module x.
<rpc message-id="101"
	  xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
   <copy-config>
	 <target>
	   <running/>
	 </target>
	 <source>
	   <startup/>
	 </source>
   </copy-config>
 </rpc>

This does not work and I do not know how to set the module?
To set the data I have tried:
NETCONF request
<edit-config>
	<target>
		<startup/>
	</target>
	<config>
		<example xmlns="http://example.com/example">
			<name>Name 1</name>
		</example>
	</config>
</edit-config>

The YANG model is:
YANG model
module example {

  namespace "http://example.com/example";
  prefix example;

  import ietf-yang-types { prefix yang; }

  container example {
	leaf name { type string; }
  }
}

many thanks in advance,
Darren

Hi Darren, have you tried to look at the raw NETCONF protocol messages that are produced by some existing NETCONF client when you attempt to issue a copy-config? You can use the netopeer2-cli for this purpose.

Hi Darren,
your RPC message is wrong, it performs copy-config from startup to running, you wanted it the other way around. Also, edit-config operation does not support target startup, you have to edit some other datastore and then use copy-config.
Regards,
Michal


isLoading prop for Button

Description
It would be awesome if the Button component had the isLoading prop like the Button comp from the Chakra library which shows a spinner when the state is changed to true
const [isLoading, setIsLoading] = useState(false)

<Button isLoading={isLoading} />

Problem Statement
Its a very reasonable thing for the Button component to have because this form of feedback to the user is widely used.
Proposed Solution or API
This is obviously a very basic implementation and the button should be disabled until loading is finished so the user cannot spam the server.
Const Button = ({isLoading, children}) => {

return (
    <View>
        {isLoading ? <Spinner />  :  children}
    </View>
        )
}

Alternatives
the alternative would be to create my own button component
Additional Information
No response

Maybe you need this? https://docs.nativebase.io/button#h3-loading


Handle scalar elevation values in nc_specs

Fixes #279

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 81.414%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
3329

Relevant Lines:
4089

💛  - Coveralls

@huard It looks as though @Mayetea hasn't been on GitHub in some time. What do you want to do with this PR?


Add as Todo

I'm not seeing a way to add new messages as a TODO by default. That would be a useful feature instead of trying to type brackets and braces on a phone.  My use case I'm using speech to text on a smart watch so it's nearly impossible without manually switching back to the keyboard and digging through to find the characters..

hey @turbo2ltr sorry I didn't see this for almost 2 years, but I personally solve this with text replacement in my iOS keyboard to replace TODO with {{TODO}}. Will leave this open for now as a prefix option would be nice


 I have a question

感谢作者！我佩服的五体投地！
Thank you first of all, your framework is powerfull！！！
i’m chinese in chengdu ,my english is very poor,so my description must have many syntax error, but i very hope that you cloud read over my question,and give me a response,thank you very much, and happy new sheep year!!!!!
:)    :)    :)    :)    :)    :)    :)    :)    :)    :)    :)    :)    :)    :)    :)    :)    :)    :)
but,i have a question,
1.some method has two child method,one don,t have prefix “mas_”,and another has prefix “mas_”,
for exaple:
equal, mas_equal
offset,mas_offset
what does  “mas_” mean? why a method has another method with prefix “mas_”??
2.we add constraint use [view mas_makeConstraints:];   but sometimes i need add constraint between two views or even more,
for example,  i want this effect (views  add constraints not one view) if i use apple’s vfl,i can do it like this:
@“H:|-0-[view1]-10-[view2]-10-[view3]-10-[view4]-….-0-|”
3.there has some method named “and” “with”,i know their usage,but if i don’t use them,i could receive the save result,i fell “and” “with” is useless???
example:
make.redview.width.and.height.equalTo(self.view);
|| (the same?)
make.redview.width.height.equalTo(self.view);
4.what different in left/leftMargin  top/topMargin bottom/bottomMargin right/rightMargin ?
i have test ,but i find out they are same???
thank you!!!

Its considered good practice to prefix your method names if you are extending a built in class with a category

Please read the readme

Yes they have no effect its just semantic

https://github.com/Masonry/Masonry/pull/163


Stringify titles when creating toc entry from UI

This PR addresses #15689
Creating notebooks with titles starting with special characters or containing only number would crash the toc when updating the book.
This is not a final fix, I'll work next release to add more validations when reading the toc.

Pull Request Test Coverage Report for Build 929718567

2 of 4 (50.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 43.369%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/notebook/src/book/bookVersionHandler.ts
2
4
50.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/import/src/wizard/pages/fileConfigPage.ts
1
73.46%

Totals

Change from base Build 929633124:
0.0%

Covered Lines:
26602

Relevant Lines:
55739

💛  - Coveralls

@barbaravaldez Can you clarify with @tobarnes on whether always using single quotes here is going to be ok? I seem to recall seeing in his example that they were quoted with double quotes and it would be kind of annoying for users to have ADS changing the types of quote used.


API token no defined

Hi,
The issue should be fixed now. Please update your repo (git fetch).

Closing this now since the issue has been resolved.


Release 0.13.1 or 0.14.0?

Primarily, I think it would be nice to replace the sparse public entry points below...

...with the updated docs that came after the 0.13.0 release, as a 0.13.1:

However, there are enough new features as well that perhaps this warrants 0.14.0?

Added new content to README.md and the root docs.

https://github.com/georust/gdal/pull/296

Fixed a crash in Group::dimensions and MDArray::dimensions when no dimensions exist

https://github.com/georust/gdal/pull/303

Added a more ergonomic means of accessing GDAL version properties

https://github.com/georust/gdal/pull/305

Provided access to gdal-sys discriminant values in ResampleAlg enum.

https://github.com/georust/gdal/pull/309

Breaking RasterBand::set_no_data_value takes Option<f64> instead of f64 so that no no-data can be set.
Also makes it symmetric with RasterBand::no_data_value which returns Option<f64>.

https://github.com/georust/gdal/pull/308

Added quality-of-life features to CslStringList: len, is_empty, Debug and Iterator implementations.

https://github.com/georust/gdal/pull/311

Added ability to set color table for bands with palette color interpretation.
Added ability to create a color ramp (interpolated) color table.

https://github.com/georust/gdal/pull/314

@jdroenner polite bump? 😃

sooooo how about a new release this week? :see_no_evil:
Are there open PRs we want to merge first?

https://github.com/georust/gdal/pull/318/files maybe?

#318 maybe?

That would be nice, but I wouldn't hold back the release if major changes are required.


FSDP hybrid shard should checkpoint in a single node

Description & Motivation
https://github.com/pytorch/pytorch/pull/104810 adds the recommendation that the save APIs should be called in a single node (shard_group).
https://github.com/pytorch/pytorch/issues/102904#issuecomment-1862892480 Also talks about this
Our logic doesn't do this and runs this code in all ranks.
Additional context
Lit-gpt uses hybrid sharding in pretrain/tinyllama.py but full checkpointing. I believe this feature request is only relevant for sharded pointing. @awaelchli Did you try it? Does sharded hybrid checkpointing work?
cc @borda @awaelchli @carmocca

Yes we should fix this. I have never had the chance to test this I think. While yes we can temporarily fix this simply calling the saver only in node 0, in general hybrid shard can span an arbitrary number of devices. We would need to get the right process group from the device mesh, pass it to the saver too and only call the saver from these ranks.

The feature is so useful. Is it supported now?

Also interested in this along with async checkpointing.


Hide inner error sources

Hide the inner sources of errors from the API. Error enums contain variants and often contain a source field with the underlying error, along with other detailed information. This source error can be something like a serde_json::Error, a futures_channel::mpsc::TrySendError, and so on.
Instead, the cause of an error and the type of the error are hidden behind error types.
Motivation
Through these source fields we expose many of our dependencies' error types. As a result, we're exposing our dependencies through our public API. This results in us being unable to upgrade our dependencies to new major versions. If async-tungstenite upgrades from 0.11 to 0.12, then we can not upgrade it as the error type from version 0.11 is incompatible with the "same type" from version 0.12. By hiding our dependencies, we can upgrade to new major versions.
Additionally, as we're somewhat aiming for a stable 1.0 release, hiding our dependencies from the API is a necessity. If we expose dependencies in our public API then the project will slowly become out of date until we release a new major version.
API
An error has always, typically, looked like this:
/// Sending a command failed.
#[derive(Debug)]
#[non_exhaustive]
pub enum CommandError {
    /// Sending the payload over the WebSocket failed. This is indicative of a
    /// shutdown shard.
    Sending {
        /// Reason for the error.
        source: TrySendError<TungsteniteMessage>,
    },
    /// Serializing the payload as JSON failed.
    Serializing {
        /// Reason for the error.
        source: JsonError,
    },
    /// Shard's session is inactive because the shard hasn't been started.
    SessionInactive {
        /// Reason for the error.
        source: SessionInactiveError,
    },
}

Users can consume the error to know its type and the underlying cause (if available) by matching on it, like so:
match command_error {
    CommandError::Sending { source } => {
        println!("source error: {:?}", source);
    }
    CommandError::Serializing { .. } => {
        println!("invalid json");
    },
    _ => {},
}

The problem, like mentioned above, is that now the underlying error is in the public API. To solve that, we can design our enums like this:
/// Starting a shard and connecting to the gateway failed.
#[derive(Debug)]
pub struct ShardStartError {
    cause: Option<Box<dyn Error + Send + Sync>>,
    kind: ShardStartErrorType,
}

impl ShardStartError {
    /// Immutable reference to the type of error that occurred.
    #[must_use = "consuming the error and retrieving the type has no effect if left unused"]
    pub fn kind(&self) -> &ShardStartErrorType {
        &self.kind
    }

    /// Consume the error, returning the source error if there is any.
    #[must_use = "consuming the error and retrieving the cause has no effect if left unused"]
    pub fn into_cause(self) -> Option<Box<dyn Error + Send + Sync>> {
        self.cause
    }

    /// Consume the error, returning the owned error type and the source error.
    #[must_use = "consuming the error into its parts has no effect if left unused"]
    pub fn into_parts(self) -> (ShardStartErrorType, Option<Box<dyn Error + Send + Sync>>) {
        (self.kind, None)
    }
}

/// Type of [`ShardStartError`] that occurred.
#[derive(Debug)]
#[non_exhaustive]
pub enum ShardStartErrorType {
    /// Establishing a connection to the gateway failed.
    Establishing,
    /// Parsing the gateway URL provided by Discord to connect to the gateway
    /// failed due to an invalid URL.
    ParsingGatewayUrl {
        /// URL that couldn't be parsed.
        url: String,
    },
    /// Retrieving the gateway URL via the Twilight HTTP client failed.
    RetrievingGatewayUrl,
}

Note: std::error::Error and std::fmt::Display are implemented for LargeThresholdError.
There are a few details to note here:

when using LargeThresholdError::into_cause and LargeThresholdError::into_parts, the concrete type is not returned, but rather a trait object is;
LargeThresholdError::kind is used to retrieve the type of error that occurred, and this does not contain the underlying type but most often just empty variants;
in addition to std::error::Error::source which returns an immutable reference to the underlying error, into_cause and into_parts consume the error and return the owned underlying error.

Using this API can look like:
match shard_start_error.kind() {
    ShardStartErrorType::Establishing => {
        println!("failed to establish connection");
    }
    ShardStartErrorType::ParsingGatewayUrl { url } => {
        println!("couldn't parse url: {}", url);
    }
    _ => {}
}

If the underlying error type is required, then there are 3 options:

call std::error::Error::source on the error;
call ShardStartError::into_cause to retrieve the owned source error
call ShardStartError::into_parts to retrieve the owned source error and type of error

Case studies
hyper does something similar, but less powerful and even less committed to a public API.
Its error type also has the into_cause method, but instead of returning a type enum it contains methods returning booleans for determining the type of error:
https://docs.rs/hyper/0.14.2/hyper/struct.Error.html
futures-channel has a similar API to hyper with methods, but instead only exposes methods for determining the type of error:
https://docs.rs/futures-channel/0.3.12/futures_channel/mpsc/struct.SendError.html
serde_json's error type contains methods to retrieve information that's always available as well as methods to determine the underlying variant:
https://docs.rs/serde_json/1.0.61/serde_json/struct.Error.html
Unlike these examples, the proposed API includes a type enum for each error. This is so that additional information can be included for a specific variant, which isn't cleanly possible in these case studies.

Some small nits and questions, but overall looks good.

Addressed

Some small nits and questions, but overall looks good.

Addressed

Rebased

Rebased

Rebased due to https://github.com/twilight-rs/twilight/pull/693/files#diff-8ef9fa7054864686dcad0e3dd331976e5e130bb0da1b546a4c33376b0523e856L8-L9


Add mouse events support for all platforms

fixes #21

Any updates on this? Is it ready, should it be reviewed?

I think it's good, I've been using it for a while https://www.npmjs.com/package/@futpib/node-global-key-listener

Okay cool, I will remind @sancarn to give this another proper test and then merge and publish it asap. Thanks for the efforts :)

Any update here? would love to have mouse event support here without needing to include another package.

Apologies for the delay everyone...


404 error generating reports for endpoints Version 1.7.0

Bug description
Trying to generate a report for endpoint gives error 404 when it should be generated.
Expected behavior
You should generate the report without problems
Deployment method (select with an X)

[ ] Kubernetes
[x] Docker
[ ] setup.bash / legacy-setup.bash

Environment information

Operating System: [e.g. Ubuntu 18.04]
DefectDojo Commit Message: [use git show -s --format="[%ci] %h: %s [%d]"]

Screenshots (optional)

Can you try with 1.7.1, there was a bug in 1.7.0 around endpoints.

Can you try with 1.7.1, there was a bug in 1.7.0 around endpoints.

Great, let me check. Thanks

The same error 404 in version 1.7.1.

@Maffooch any thoughts?

Looks like the referenced PR fixed this.


Maxkaz/f3 pretrained

closes https://github.com/microsoft/seismic-deeplearning/issues/226

obsolete


Add TSI support for basic and local remote monitoring solution

Description and Motivation
...
Change type

[ ] Bug fix
[x] New feature
[ ] Enhancement
[ ] Breaking change (breaks backward compatibility)

Checklist:

[x] All tests passed
[x] The code follows the code style and conventions of this project
[x] The change requires a change to the documentation
[ ] I have updated the documentation accordingly

This change is

@zhang-hua do we need to update the docs with instructions for the new deployment options?

@ppathan @asdonald - what are the doc updates required from this?

Hey @dominicbetts! The doc updates are the ones we had discussed in the last sprint planning that are hopefully in progress :). Let me send you an e-mail and we can discuss there.


Fail build if readthedocs build of project fails

No idea how to do this, but we should not be releasing the project if the docs do not build successfully.

Where does ReadTheDocs build run?


Use 'axes' metadata to pick channel_axis

Reading OME_NGFF v0.3 data with https://github.com/ome/ome-zarr-py/pull/89 fails since we no-longer have 5 dimensions and the channel_axis isn't hard-coded.
This PR dynamically sets the channel_axis based on the axes metadata.
cc @joshmoore @constantinpape

Codecov Report

Merging #9 (aa355a4) into main (d7325e8) will decrease coverage by 8.08%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##             main       #9      +/-   ##
==========================================
- Coverage   89.14%   81.06%   -8.09%
==========================================
  Files           3        3
  Lines         129      132       +3
==========================================
- Hits          115      107       -8
- Misses         14       25      +11

Impacted Files
Coverage Δ

napari_ome_zarr/_reader.py
76.36% <33.33%> (-2.49%)
:arrow_down:

napari_ome_zarr/_tests/test_reader.py
86.11% <0.00%> (-12.50%)
:arrow_down:

Continue to review full report at Codecov.

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

I would also like to add axis_labels to the metadata.
The docs at
https://napari.org/tutorials/fundamentals/image.html#arguments-of-view-image-and-add-image
suggest that the "arguments of view_image and add_image" include:
axis_labels : list of str, optional
        Dimension names. by default they are labeled with sequential numbers

but trying to add this metadata["axis_labels"] = metadata["axes"] into this PR: fails with:
  File "/opt/anaconda3/envs/napari/lib/python3.9/site-packages/napari/components/viewer_model.py", line 856, in open
    self._add_layers_with_plugins(
  File "/opt/anaconda3/envs/napari/lib/python3.9/site-packages/napari/components/viewer_model.py", line 929, in _add_layers_with_plugins
    added.extend(self._add_layer_from_data(*_data))
  File "/opt/anaconda3/envs/napari/lib/python3.9/site-packages/napari/components/viewer_model.py", line 1008, in _add_layer_from_data
    raise TypeError(
TypeError: _add_layer_from_data received an unexpected keyword argument ('axis_labels') for layer type image

and looking at the code confirms that add_image doesn't support axis_labels.
Any idea if there's a way to support this? @tlambert03

Unfortunately not at the moment.  It's a problem.
The issue is that the axis labels are a viewer.dims property, not a layer property.  I can't find the issue at the moment, but we definitely need to be support something like this (Ive tried to do the same thing myself many times)

(The reason view_image supports it is because that creates the full viewer, not just a layer)

@tlambert03 Thanks for the feedback. It's not a big deal, just thought I might be missing something. Cheers.

@will-moore how does this PR relate to #8? Should I close #8 in favor of this one?

This PR needs the axes metadata to be set by ome-zarr-py as I suggested in your PR at https://github.com/ome/ome-zarr-py/pull/89#pullrequestreview-706214120
If we have that, then the napari plugin doesn't need so much code to look this up.

This PR needs the axes metadata to be set by ome-zarr-py as I suggested in your PR at ome/ome-zarr-py#89 (review)
If we have that, then the napari plugin doesn't need so much code to look this up.

Ok, so if I understand correctly if we add the suggestion you made in https://github.com/ome/ome-zarr-py/pull/89#pullrequestreview-706214120 we can just use this PR and #8 becomes obsolete?

Ok, I still get the TypeError: _add_layer_from_data received an unexpected keyword argument ('axis_labels') for layer type image issue when trying to open an image with this PR and the changes suggested in https://github.com/ome/ome-zarr-py/pull/89#pullrequestreview-706214120. Is this something you can fix here, @will-moore?

I was looking to add axis_labels in this PR (see discussion above) but haven't done, so I don't know where that's coming from. I'm not seeing that error myself.
Does the error go away without this PR?

I was looking to add axis_labels in this PR (see discussion above) but haven't done, so I don't know where that's coming from. I'm not seeing that error myself.

Ok, thanks for clarifying.

Does the error go away without this PR?

This error happens for me with the changes from https://github.com/ome/ome-zarr-py/pull/89#pullrequestreview-706214120; both on this branch and on #8.
I had a closer look now and it only happens for data without a channel axis, e.g.  for my example data: https://s3.embl.de/i2k-2020/ngff-example-data/v0.3/zyx.ome.zarr

Ah, thanks. I saw a slightly different error with that data: TypeError: add_image() got an unexpected keyword argument 'axes'.
It should be fixed with that commit.
I made some bigger changes as I though that passing the metadata directly from ome-zarr-py to napari is too closely coupled: any change in metadata from ome-zarr-py would break napari.

Yes, that fixes the issue with displaying data without a channel axis.
There is still one more issue: data in the 0.1 format version is not displayed correctly.
For example this is what I get when displaying https://s3.embassy.ebi.ac.uk/idr/zarr/v0.1/6001240.zarr/:

whereas it should look something like this:

My guess is that internally a normal, instead of a nested directory store is used, see also https://github.com/zarr-developers/zarr-python/issues/769

@constantinpape: agreed. I think cross v0.1/v0.2 support is waiting on zarr-python fixes.

ome-zarr 0.0.22 has been released with support for NGFF v0.3. Releasing this as v0.2.0.


[2201.4.x] Increase the timeout for ballerina-central requests

Purpose
Increase the timeout for ballerina-central requests due to continuous timeouts.
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

This fix is no longer necessary as Ballerina Central has resolved the issue.


forced play services versions to 10.2.1

Fixes [SYS-4545]
Creator

[ ] Build relevant tests if any apply
[ ] Ensure there are no new warnings
[ ] Upload an animated GIF showcasing the solution (if it applies)
[ ] Set a relevant reviewer

Reviewer

[ ] Run test and make sure all tests pass
[ ] Review function and form on iOS
[ ] Review function and form on Android
[ ] Review function and form on Web
[ ] Review new test logic

@redreceipt Can you elaborate a bit on these changes? What are they doing? Why did this change need to be made? Etc..

@IsaacHardy this fixes a Firebase lib conflict described here
https://stackoverflow.com/questions/46340333/unable-to-start-receiver-com-google-firebase-iid-firebaseinstanceidinternalrecei
From my vague understanding, the app is crashing because the older Firebase lib starts a service in the background which conflicts with Android 8.0.  It was set to Firebase-9.8.0 from ExpoKit. Updating to Firebase-10.2.1 has fixed issues for a lot of people but if that doesn't work, we could try the more complicated Android Intent fix in the described solution here:
https://stackoverflow.com/questions/51532059/android-gcm-wakefulbroadcastreceiver-startwakefulservice-crash-due-to-illegals
Lastly, if all that doesn't work we could roll back the build to SDK 25 (Android v7) but I don't remember why we had to upgrade it so that could cause adverse other adverse effects. Currently, we're on 26.

@redreceipt Why are we currently using firebase?

We’re not, react-native-maps is
On Oct 22, 2018, 4:42 PM -0400, Isaac Hardy<EMAIL_ADDRESS>wrote:

@redreceipt Why are we currently using firebase?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Are we using react-native-maps?

Might not be exactly react-native-maps but it's some React Native library that uses an old Firebase lib. ExpoKit imports a bunch of libraries that we probably don't use in our code but they do.


TypeScript (tsc) errors on MainFn signature

Hi,
While running tsc in strict mode, I recently got this error:
src/index.ts:29:5 - error TS2345: Argument of type 'MainFn<Forbid<Sources, "state">, Omit<Sinks, "state">>' is not assignable to parameter of type 'MatchingMain<{ dom: Driver<Stream<VNode>, MainDOMSource>; }, MainFn<Forbid<Sources, "state">, Omit<Sinks, "state">>>'.
  Type 'MainFn<Forbid<Sources, "state">, Omit<Sinks, "state">>' is not assignable to type 'Main & ((so: Sources<{ dom: Driver<Stream<VNode>, MainDOMSource>; }>) => Omit<Sinks, "state">)'.
    Type 'MainFn<Forbid<Sources, "state">, Omit<Sinks, "state">>' is not assignable to type '(so: Sources<{ dom: Driver<Stream<VNode>, MainDOMSource>; }>) => Omit<Sinks, "state">'.
      Types of parameters 'sources' and 'so' are incompatible.
        Type 'Sources<{ dom: Driver<Stream<VNode>, MainDOMSource>; }>' is not assignable to type 'Forbid<Sources, "state">'.
          Type 'Sources<{ dom: Driver<Stream<VNode>, MainDOMSource>; }>' is not assignable to type 'Omit<Sources, "state">'.
            Types of property 'dom' are incompatible.
              Type 'MainDOMSource' is not assignable to type 'DOMSource'.
                Types of property 'elements' are incompatible.
                  Type '() => MemoryStream<Element[]>' is not assignable to type '() => MemoryStream<string | Element[] | Document[] | HTMLBodyElement[]>'.

29 run(main, drivers)

Code to reproduce the issue:
The affected code is available here. Demo runs at https://typometer.netlify.com/.
I believe it's fairly close if not par with the latest documentation as far as defining types (sources / sinks) goes. But I'm fairly new to TypeScript and this is my pet project, so after spending a few hours fixing loads of type checking errors and narrowing it down to that single one, I'm in for some expert insights :)
Expected behavior:
Not having this huge beast of an error message :D
Actual behavior:
tsc not happy with my CycleJS types.
Versions of packages used:

@cycle/dom 22.0.0
@cycle/http 15.0.0
@cycle/isolate 4.1.0
@cycle/run 5.1.0
@cycle/state 1.0.0
see package.json

I am closing this, because there is already an issue (#847) and I've also finished a PR yesterday (#852), so expect this to be released in the next few days


📖 Fix version in docs

What this PR does / why we need it:
This PR updates the versions in the docs
Which issue(s) this PR fixes:
Fixes #55

/cc @kashifest
/cc @fmuyassarov

/test-v1a4-integration

/lgtm


Manual PMJ labeling

If I've understood correctly, it's necessary to go through all QCs for the sct_detect_pmj command only, I don't need to flag sessions for the sct_deepseg and sct_process_segmentation commands, isn't ?

Okay I see, thank you !

check your segmentations

Thank you, now I can close this issue


Display correct rubric based on duty

If an assignment is a duty based assignment and a student has a role that has a specific rubric, then that duty specific rubric should be displayed to the student rather than the regular teammate evaluation rubric.

The issue is updated and can be found in Rubrics tabe


Contrib folder not installed with RDkit pypi installation

The module rxnutils.pipeline.actions.reaction_mod doesn't seem to be importable if RDKit is installed from pypi with pip due to missing Contrib package.
This needs to be investigated.

We will make the actions dependent on the Contrib folder optional. The Contrib folder will be included in future versions of the RDKit pypi packages.


Is Closure 62 and Closure 63 duplicated bugs?

Hi,
I am checking the patch of Closure 62 and Closure 63. It seems they are identical bugs yet the commit-db shows they appear in different commits. Correct me if I am wrong. Thanks!

Hi @lisahua,
Thanks for pointing this out. The patches, and hence the bugs, are indeed identical. The corresponding issue-tracker ID (issue 487) appears in two different commits, which is the reason why the bug-mining workflow picked up both commits. It seems, however, that one of the commits is either coming from a branch, which was merged in, or part of a revert operation.
I am labeling this as a bug and will investigate further.
Thanks,
René


docs(helmrelease): typo

It could even make sense to rewrite the sentence to something like "If one or many of the spec.chart.spec.valuesFiles don't exist inside the chart, ... ", because I would expect, that it will fail in both cases, if one or many defined files are not present.
Is this assumption correct? What do you think?

Yes, they are applied in order, I would expect it to fail if any of the files listed are not present 👍

Thanks for the contribution @choeffer 🎉


FC009 does not recognize headers as a valid attribute for remote file.

FC009: Resource attribute not recognised: ./providers/default.rb:14
This fails even when calling foodcritic with a specific Chef version including that attribute, e.g. -c 11.16.4
providers/default.rb:14 =
remote_file "downloading datomic-#{node[:datomic][:version]} to #{local_file_path}" do
    path     local_file_path
    source   datomic_download_url
    headers  Hash.new('Basic' => "Basic #{encoded_credentials}")
    owner    username
    group    username
    checksum new_resource.checksum
    action   :create
  end

Works as expected after all the missing metadata was committed, closing.


Facility for rendering a partial template from a tag helper

Proposal
When creating a custom TagHelper it would be convenient to be able to render an existing partial view programatically and capture the rendered result in a string or an HtmlContent object inside the TagHelper.Process method.
For example, consider the following hypothetical custom TagHelper
`
    public class CustomTagHelper : TemplateRenderingTagHelper
    {

        [HtmlAttributeName("asp-for")]
        public ModelExpression DataModel { get; set; }

        public override Task Process(TagHelperContext context, TagHelperOutput output)
        {
            output.TagName = "div";
            var renderedContent = HtmlHelper.Partial("~/Views/Shared/path/to/Template.cshtml");
            output.Content.SetHtmlContent(renderedContent);
        }
    }`

This tag helper inherits from the hypothetical TemplateRenderingTagHelper abstract class, this class would look like this:
`public abstract TemplateRenderingTagHelper : TagHelper
{
      protected IHtmlHelper HtmlHelper { get; set; }
      public TemplateRenderingTagHelper()
      {
            //Get a IHtmlHelper instance
            HtmlHelper = BuildAnIHtmlHelper();
      }
}
 `

As you can see this class makes available the HtmlHelper property for its sub classes, the HtmlHelper.Partial (or PartialAsync) can then be used to generate a template.
Motivation
Even if it is possible to call @Html.RenderPartial directly from the view, it is cleaner to factor the rendering inside the TagHelper.Process method especially if the rendering requires some preprocessing.
Consider the following TagHelper.Process example:
`
...
[HtmlAttributeName("asp-for")]
public ModelExpression DataModel { get; set; }
...
public override Task Process(TagHelperContext context, TagHelperOutput output)
{
      // Preprocessing on the model
      var model = SomeProcessingOn(DataModel.Model);
      // Building a Custom ViewData Dictionary
      var ViewData = BuildCustomViewDataDictWithCustomizedMetadata();

      output.TagName = "div";
      var renderedContent = HtmlHelper.Partial("~/Views/Shared/path/to/Template.cshtml", model, ViewData)
      output.Content.SetHtmlContent(renderedContent);
}`

@MissaouiChedy ,
Actually, you can use an HtmlHelper from within a TagHelper also now, with no need for further features:

Add an IHtmlHelper argument to the constructor of your TagHelper, say: IHtmlHelper html, so that a fresh Html instance is injected when your TagHelper is created.
Store it in a private variable, say html. The injected TagHlper is "neutral", not specific for your View, so you have to "contextualize" it for the current View Viecontext as explained in the steps below
Add a property:

        [HtmlAttributeNotBound]
        [ViewContext]
        public ViewContext ViewContext { get; set; }

It will be automatically bound to your View ViewContext
4. In the TagHelper ProcessAsync method contextualize the HtmlHelper:
(html as IViewContextAware).Contextualize(ViewContext );

Done! Now you have a working HtmlHelper.

@frankabbruzzese
Yes in fact it works.
I tried previously to get an IHtmlHelper by using dependency injection, but I got an exception whenever I called one of its methods.
It turned out that I missed the contextualization part.


Update understand-vm-reboots.md

Added clarification of the real procedure in terms of recovery for unhealthy Host Nodes.

Thank you for your interest in contributing to our documentation. Unfortunately, the changes in this pull-request cannot be accepted because our Content group is migrating content for the "virtual-machines", "virtual-machines-scale-set", "container-instances", and "service-fabric" folders to a new repository: azure-compute-docs.
Short-term, if there are changes in this PR for other folders, you can move forward with those by removing the change(s) to all the above mentioned folders' content.
In the meantime, we are closing this PR and tagging it so that when the content is available in the new repo, we can follow up with the new location information.
#please-close
#label:"migrate-followup"

@dantecit0  We’re happy to share that contributions to virtual-machines are once again possible at azure-compute-docs. Please open a PR in the new repo to submit your changes. We appreciated your patience during this migration.


Model and texture overhaul

I'm planning to overhaul all the Mekanism textures again, with my upgraded blender skills.

woot!

nice

Merging with #2042 - with the new models will come dynamic models!


Address #36.

Does not raise an exception if the  tag is not present.
I have tested on >=15.1, 14.2, and 12.1X46. This fix also more closely
follows the fix in PyEZ which appears to be working correctly.

Resolves #36


Testing, please ignore. (jaosxh)

Please ignore.. Please DO NOT APPROVE THIS! (jaosxh)

Hi @helumanxa,
Thank you for contributing this pull request!
Please sign the Kaltura CLA so we can review and merge your contribution.
Learn more at http://bit.ly/KalturaContrib


DCOS-52237 Remove dcos-commons/tools/vagrant

Adding folks from the SDK team to double-check nobody uses it.


[$500] Copy to clipboard on the system message for paid expense copies negative amount

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.33-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4211589
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:

Open https://staging.new.expensify.com/
Log in under your HT account - A
Send an IOU with any amount to Account B that you have access to
Log in under account B
Navigate to the conversation with account A
Open IOU Report Conversation
Turn off the internet
Pay for the IOU
Copy the system payment message "paid {currency} {amount} elsewhere"
Paste the copied message into the Compose Box

Expected Result:
The system message must be copied without the "-" sign in front of the currency
Actual Result:
Copy to clipboard on the system message for paid expense copies negative amount
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/43996225/0d87cd86-e881-471b-9985-a8dfd34575e0

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0170b576c255476ae4
Upwork Job ID:<PHONE_NUMBER>992983552
Last Price Increase: 2024-01-30

Proposal
Please re-state the problem that we are trying to solve in this issue.
Copied "paid" report action contains a negative amount
What is the root cause of that problem?
Since the Paid action means the user pays money, not receives it, the IOU amount is set with a negative value in the originalMessage.IOUDetails. And we do not negate this value when copying the message to clipboard.
What changes do you think we should make in order to solve the problem?
When building the getIOUReportActionDisplayMessage, use -amount instead of amount:
const formattedAmount = CurrencyUtils.convertToDisplayString(-amount, currency) ?? '';

What alternative solutions did you explore? (Optional)

@grgia just waiting on you to confirm

@tienifr assigned!

Eugh, no Melvin comments either. 😭 Why do you make me do work Melvin.

Wow, I need to pay this. Sorry for the tardiness.

Payment Summary:

@tienifr paid $500 here.
@parasharrajat paid $500 via newDot payments.

$500 approved for @parasharrajat


Can't run from CLI

Got this error. Any idea?

@CoalaJoe Try loading main.lua?
Could also try compiling https://github.com/libretro/libretro-lutro and loading the test directory?
I've run into segfaults with the latest Lutro before as well.

Seems like lutro does not work on OSX

Yeah, I had been getting the Segfault irregularily on Linux as well. There was a HTTP request system that was merged that somewhat broke it sometimes for me when running the tests.

What a pitty. Development on Lutro looks pretty dead.

@CoalaJoe Let's tackle that over at https://github.com/libretro/libretro-lutro/issues/65


Missing refresh button?

I thought the PR view in the scm viewlet used to have a refresh button, but today I assigned a new PR to myself then was unable to get it to show up in the scm viewlet

Hmm, I'm still seeing a refresh button there. Could you also send a list of other extensions you have enabled? I'm wondering if there could be some collision of "when" clauses for which view it gets shown on

It reappeared noooo

I haven't been able to reproduce this - let me know if you see this again in the latest version of VSCode.


[WIP] Bezier fit to a spring

Example of tangents so calculated (blue lines at each half-frame), https://codepen.io/rs42/pen/JjzpPyP
Example of fit curve, https://codepen.io/rs42/pen/jOJZNPa
Example of a quick hand-written fit using 2 cubics, https://codepen.io/rs42/pen/JjzpPyP
Context: we'd like to fit a small # of beziers to the curve produced by a spring so we can use the spring in places that have bezier easing and no spring function.
My intuition is that this is more cubics than we actually need. Fiddling fit_to_bezpath will eventually destroy the result but does not seem to let me get a good result with fewer cubics as I might have hoped. Most likely I just screwed up ParamCurveFit, haven't used it before and I"m not completely confidet I understood it correctly.

ParamCurveFit doesn't seem to achieve better results for what we need here than hand-written fitting. Per discussion with @raphlinus will use the hand-fit curve, likely with some degree of automated adjustment. Closing this, will land in a new PR.

If you do want to continue exploring the curve fitting method, one thing to experiment with is the approach in the recent paper, [Bézier Spline Simplification Using Locally Integrated Error Metrics](https://cs.nyu.edu/~sw4429/files/paper/sa23-bezier.pdf).

If you do want to continue exploring the curve fitting method, one thing to experiment with is the approach in the recent paper, Bézier Spline Simplification Using Locally Integrated Error Metrics.

Oh ty. I suspect we may seek to MVP with handwritten so I will file an issue to capture that.


Ability to search for specific topics

What

Allow people to be able to search the NHSBSA Playbook for specific topics, instead of having to navigate via the pages for each discipline.

Why

As the NHSBSA Playbook grows in terms of content, finding what each person needs becomes more and more difficult. Allowing people to search for the topics they need quickly and easily is a must.

There is a common need from within the Design Community to be able to find the required information to be able to train and learn to do their roles - ultimately - this is what the NHSBSA Playbook was setup to do.
In terms of evidence, we know having ran workshops within the Design Community that people are not able to find the support they need, primarily because of the huge number of different areas that currently exist, but also because they can't find the answer to their specific question. When that happens, they either suffer in silence, or turn to their colleagues for help.

Anything else

NHS Design System - https://service-manual.nhs.uk/design-system
GOV Design System - https://design-system.service.gov.uk/
DfE Design Manual - https://design.education.gov.uk/

@StephenHill-NHSBSA This has been done within the research version of the playbook.
https://nhsbsa-playbook.netlify.app/sitemap
Would be straight forward to implement the same approach within the playbook.


Feature Request: Undo for "Snap to Portas"

Hi!
How about an undo function for "Draw Tool Options" "Snap to Portals"?
I just lost 15 minutes drawing.
Thank you!

That might actually be very possible. I wouldn't do a permanent undo, but as long as the tap is open, or you don't draw anything else this should be very easy to do.

I could have used this a few times.  Upon a quick look, window.plugin.drawTools.snapToPortals() could be modified to save the previous coordinates (lat-lngs) when they are updated.  E.g.,
        if (!newll.equals(ll)) {
          layer.prevLatLng = ll;  // Save old value in new adhoc attribute prevLatLng
          layer.setLatLng(new L.LatLng(newll.lat,newll.lng));
          changedCount++;
        } else {
          delete layer.prevLatLng; // or layer.prevLatLng = undefined;
        }

Do this similarly for layers that have multiple LatLngs.
Then, in an a window.plugin.drawTools.undoSnapToPortals(), do something like this:
window.plugin.drawTools.drawnItems.eachLayer(function(layer) {
   if (layer.prevLatLng) {
      layer.setLatLngs(layer.prevLatLng);
      delete layer.prevLatLng;
      changeCount++;
   } else if (layer.prevLatLngs) {
   ...
   }
  if(changedCount > 0) {
    runHooks('pluginDrawTools',{event:'layersSnappedToPortals'}); //or should we send 'layersEdited'? as that's effectively what's happened...
  }
  alert(...nice alert message here...);
  window.plugin.drawTools.save();
}


Unnecessary console.log after every action

Hi,
Every action leaves a "data" log in the console which clutters it up and makes it harder to debug. Is there any way to stop this?
It happens here in the debugger-ui (line 18311):
    function t(t) {
        var n = void 0;
        return t.data ? (n = t.data,
        n.id = t.id) : n = t,
        "DISCONNECTED" === n.type ? void r(t.id, void 0, !0) : (console.log("data", n),
        void e(n))
    }

Still has data log in latest version? I remember this to be in the older remotedev-app version. Try to update version & Re-run inject command.


[CPU] Lower matvec and other "degenerated" matmuls to a more appropriate Linalg representation

It seems like we are currently using linalg.matmul to represent any kind of dot product operation, including matvec and 1-D dot products. Linalg also has linalg.matvec and linalg.dot, which would be really helpful to differentiate these simpler (at least optimization wise) operations from the full matrix multiplication. All these operations require a complex and significantly different optimization strategy and we shouldn't be looking at which dimensions are 1 in a linalg.matmul to decide what to do. That would also help remove some of these annoying size 1 dims from the code since we can't do so from a linalg.matmul op.
Would it be possible to lower to them directly from StableHLO? These are a few examples that I see internally:
%63 = "stablehlo.dot"(%62, %16) {precision_config = [#stab     lehlo<precision DEFAULT>, #stablehlo<precision DEFAULT>]} : (tensor<1x256xf32>, tensor<256x40xf32>) -> tensor<1x40xf32>

%14 = "stablehlo.dot_general"(%10, %13) {dot_dimension_numbers = #stablehlo.dot<lhs_contracting_dimensions = [1], rhs_contracting_dimensions = [1]>, precision_config = [#stablehlo<precision DEFAULT>, #stablehlo<precision DEFAULT>]} : (tensor<20x144xf32>, tensor<1x144xf32>) -> tensor<20x1xf32>

%168 = "stablehlo.dot"(%arg45, %144#2) {precision_config = [#stablehlo<precision DEFAULT>, #stablehlo<precision DEFAULT>]} : (tensor<32xf64>, tensor<32x1xf64>) -> tensor<1xf64>

Thoughts?
@rsuderman, @jpienaar

Seems pretty fixable. Plan should be a StableHLOToStableHLO pattern that identifies MatVec operations and converts them to a standard form, then lowers them to linalg.matvec.


Write a step-by-step guide for using a board in an app

The current happy path has just enough info to create a board, but there's nothing there about how to fit into an app (like a web app). Let's write a guide for building a simple app from an existing board. Probably just plain HTML/CSS/JS or maybe with Lit/React.

We had a heap of demos from @Mearman and co - we could probably re-provsion some of them.
Btw - I think we will need two entry points:

I have a board, now scaffold an app
I have an app, how do I integrated breadboard

For the most part, we got them working with the latest release. Though with the significant progress in the UI components and editor, it's building them from a clean slate.
@alexandraM98 has been getting to grips with the UI components, and @TinaNikou has been rewriting our getting-started examples using the new grammar.
I've requisitioned some of @jamesjacko and @jig925's time also next week. So, together with the rest of the @breadboard-ai/exadev team, we should be able to put our heads together and think about a path forward.
The way you've handled the proxy in the critic is an interesting scenario that I'm just going to link here as a bookmark<EMAIL_ADDRESS>This also aligns a bit with https://github.com/breadboard-ai/breadboard/issues/722

I think the kit section of the happy path needs a little more work as it isn't immediately obvious where the kit fits into the existing code from previous steps. The example ptomptTemplate kit is also a little confusing on first use as the example code does nothing but return the string in the prompt. Maybe changing that example to something like:
const prompt = templates.promptTemplate({
    template: "The input reversed is {{text}}",
    text,
  });

I realize that the Happy Path is more about getting up and running with breadboard but using the promptTemplate and it only returning "Hello, !" is confusing for someone who is getting started, I think.

I think the kit section of the happy path needs a little more work as it isn't immediately obvious where the kit fits into the existing code from previous steps.

I agree! Ideally, I'd love to rewrite the happy path guide entirely to follow the beats outlined here:
https://github.com/breadboard-ai/breadboard/issues/509


Saving eth canopy height dataset fails

Saving eth canopy height dataset fails. This is due to a time axis with length 0, and a time coordinate with no values.

Fixed with same fix as #17


V4: Multiple signing keys

@brockallen need help with the EF mappings. Maybe we store the signing algorithm list as a space separated string instead of introducing an extra table...


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
6f24289 -> d366e67

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.21.8 -> v1.21.10

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.21.10
Compare Source
Bug Fixes

deps: update module github.com/ibm/platform-services-go-sdk to v0.50.1 (#651) (df3e66d)

v1.21.9
Compare Source
Bug Fixes

deps: update gomod (#650) (1835de4)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Sakura tree blossoms

The tree used space-colonization algorithm and will eventually grow a sakura flower represented as a bright purplish-pink circle

No problem man. I'm honored to do so

Wonderful!


Fix Issue 20147 - Enable comparison (==, >, >=, <=, <) between std.bigint.BigInt and floating point numbers

Split off as its own PR separate from #7151 because there is a single mathematically correct way to compare numbers without needing to consider rounding mode.

Good to go?

Yep


Error occurs in "Python Interactive" when "Run All Cells" for Data Science

Visual Studio Code - Insiders: 1.32.0-insider
python-insider: 2019.2.5135-alpha
python version: Python 3.7.2 64bit
Repro steps:
1.Git clone https://github.com/qubitron/pydemo
2.Open Anaconda Prompt window
3.Cd pydemo
4.Run py -3 setup.py
5.Open hello-stackoverflow folder inVSC
6.Set python environment to Anaconda
7.Click on "analysis.ipynb" file, make sure prompt to import Jupyter Notebook" popup
8.Click "Import". Wait for a moment, a file will be generated.
9.Select "Run All Cells"
Except result:
Python Interactive window opens and cells are run in the window

Actual result: null and .js can't be found and error message outputted.

Hey @zhouwangyang Sorry that you ran into this issue. Since I noticed that you are using the python extension insiders build. Could you please try installing the most recent version of that from here?
https://github.com/Microsoft/vscode-python/blob/master/CONTRIBUTING.md#development-build
We accidentally pushed a version that broke some of the data science features to our development build and I think that you might have one of those versions. I also tried your scenario myself (thanks for the detailed steps) and was able to start the Interactive Window and run the code cells.

Thank you for your valuable feedback @IanMatthewHuff , I have installed the python extension(2019.3.5370-alpha) as you provided and Data Science worked OK.

@zhouwangyang Glad that we got you unblocked, sorry about the bad version that we pushed.


[LiveComponent] Deferring loading components and the paradox of twig component exposeInTemplate eager loading

Hello,
I'm using live components in multiple projects and I'm facing an issue that I don't really understand and that is IMO contradictory in the behavior (and the documentation) of twig/live components.
The problem : having (not using !) heavy exposeInTemplates methods in live-components.
I have a component (list of products) that have multiple methods exposed and some of them are really heavy on call. The thing is, they are not necessarily called during my component rendering because of some condition on render (sometimes the filters are render, other times not). But as the documentation of twig component mentioned, the exposed methods are eagerly fetched resulting on them being called during initialization and render.
I see multiple issues related to that :

The exposed methods are always called at least once during component initialization, even if not called in render.
-> Is it possible to avoid that initialization call ?
The exposed methods are called x number of time during render (depending on the number of call in template). Using "computed.myMethod" does not change the behavior of being called at least twice (init + render).
I tried to defer the render of my component with the defer option, but it's irrelevant because of the methods being called during initialization, even if I dont call it on render. I mention this because it is written:

Behind the scenes, your component is created & mounted during the initial page load, but it isn't rendered. So keep your heavy work to methods in your component (e.g. getProducts()) that are only called when rendering.

which is IMO contradictory to the eager fetch.
For now I set up a workaround to avoid calling the heavy processes by checking a condition inside my component. But is that not a major issue to execute exposed code that might not be used in template ? Did I miss something big ?
Side-note: I could not use the "loading-template" option while deferring the component loading, also the documentation have some syntax error (after "Or override the loadingContent block:"), is it still WIP ?

Do you need to expose them ?
Any public method is accessible from the template if you need them, without this attribute (that indeed pre-compute the resultes to expose it in the context)
See the Alert component for exemple: https://<IP_ADDRESS>:8000/twig-component

Concerning the syntax error, could you suggest a correction ? (You can open a PR directly from the documentation page (top of the page just under the title)

Do you need to expose them ?
Any public method is accessible from the template if you need them, without this attribute (that indeed pre-compute the resultes to expose it in the context)
See the Alert component for exemple: https://ux.symfony.com/twig-component

ok. so that's what I didn't get. thanks for the precision.

Concerning the syntax error, could you suggest a correction ? (You can open a PR directly from the documentation page (top of the page just under the title)

Sorry but I couldn't figure how to set it up.


Add initialIsOpen prop

Hi,
Love RHF and I was happy to discover the existence of this DevTool!
Would it be possible to add an initlaIsOpen prop to have the devtools closed on startup and open it only when I need it? I didn't find any other way to do it.
I would be happy to make a PR to add this feature
Thank you!

Do I take this as a "ok to make a PR?"


Dispatch Errors on Main Thread

The other handlers are called by Starscream's delegate, but the auth
errors are called by NSUrlSession, which is on a background thread.
So, I've moved the logic into a dispatch_async on the main thread.
I decided to put it in the handleError method rather than outside it because
there are multiple places that need it and currently all of them are on the
background threads.
If later that's not true, then we should put the dispatch around the method
call in all 4 or so places it comes up.

This looks sensible, although I just committed some code that makes some changes to the bit you changed in this PR: https://github.com/pusher/pusher-websocket-swift/pull/34/commits/77bd1eaf8c588cb72002ea4b92f7ec4fbe499a0c
If you could rebase that would be great 👍

@psycotica0 have you had a chance to look at this with the changes?

No, sorry. Doesn't seem like a problem, I've just been tied up, sorry.

Awesome - thanks a lot! And no worries  👍


Nvim v0.10 warning

vim.treesitter.query.get_query() is deprecated, use vim.treesitter.query.get() instead. :help deprecated
This feature will be removed in Nvim version 0.10

Thanks for the warning! I don't think we are using tree-sitter though. Is your warning a general one or do you actually encounter that issue somewhere?


fix table isGroupsOnly evaluate

[x] Changes have been thoroughly tested to not break existing functionality.

the bot doing something funny


jsii overrides protocol documentation

jsii Overrides
The requirement is to enable users to override a jsii class's method in a
subclass they define in their native language.
For example, say I have a jsii TypeScript class:
export class Helloer {
  public helloee() {
    return "Jake";
  }

  public sayHello() {
    return `Hello, ${this.helloee()}!`
  }
}

In this example, lets say I want to be able to define a class in a native
language (.NET, Java, Python) which extends (derives) from Helloer and
overrides helloee(), returns a new value.
In java, it will look like this:
public class MyHello extends Helloer {
    public String helloee() {
        return "Fran";
    }
}

And now, anyone who uses MyHello would get:
MyHello obj = new MyHello();
obj.sayHello() // returns "Hello, Fran!"

This is what users expect, and this is what overrides are all about!
Overrides are supported for:

Methods
Properties (getters/setters)
Async Methods

Synchronous Overrides
The jsii kernel supports overrides at runtime in the following way:
When the jsii client issues a create
request,
it can include an overrides field, which may include a list of property/method
names that are overridden by the native class.
In the above example, the create call would look like this:
{ fqn: 'Helloer', overrides: [ { method: 'helloee' } ] }

You can attach a cookie with each override, which will be sent back to you
when the override is called. This cookie can be used to associate the override
with the native method. In Java, for example the cookie contains the method
signature.
If an override is specified for a method or property that doesn't exist (or is
private), this override will be ignored. This means that the jsii client can
simply pass all method/property names that are user-defined when the object is
created (see the Java
discoverOverrides
as an example).

The jsii kernel protocol is a request/response protocol over STDIO. The native client would
issue a request, the jsii kernel will execute it and return a response to the native client.
Continuing with our example, let's the client <=> kernel interaction when the
Java code above which calls obj.sayHello() is run (>> denotes request from
the native client to jsii runtime and << denotes response from the jsii
runtime to the native client).
First, we create the object with obj = new Helloer() via a create request
and receive a create response:
>> { api: "create", fqn: "Helloer", overrides: [ { method: "helloee", cookie: "<magic-string>" } ] }
<< { objref: "helloer@0001" }

Now, we call obj.sayHello() via an invoke request:
>> { api: "invoke", objref: "helloer@0001", method: "sayHello" }

Since the jsii implementation of sayHello calls this.helloee(), and it was
defined as overridden, the response will be a callback
response
which instructs the client to invoke the override.
<< { callback: { cbid: "<callback-1234>", cookie: "<magic-string>", invoke: { objref: "helloer@0001", method: "helloee" } } }

After the native helloee method was called, the runtime captures the return
value ("Fran") and issues a
complete request:
>> { complete: { cbid: "<callback-1234>", result: "Fran" } }

If an exception is thrown from the callback, the complete request will include an err field
instead of result, and the exception will be thrown in the jsii side.

This yields control back to the jsii code, which continues to execute, and the sayHello method
eventually returns it's result via an invoke response:
<< { result: "Hello, Fran!" }

A similar protocol will occur for property overrides (both getters and setters can be overridden by the native code).
Async Overrides
jsii also supports async methods and async overrides. This means that users are able to define a jsii
method that returns a Promise (or use the async keyword), and native code can subclass and override
such a method.

Async overrides are declared in create similarly to synchronous overrides.

When the jsii native client needs to invoke an async method, it issues a begin request which
returns a begin response.
The response will always contain a promiseid.

Then, the native client should issue a callbacks request
which returns a callbacks response
with an array of callbacks.
If the array is empty, this means there are no callbacks to invoke. If it includes callback invocations,
the native code should invoke each native callback and send a complete request
for each callback.

When all pending callbacks are completed, the native client should issue an end request
with the promiseid returned from the "begin" and the end response
will eventually include the result of the original async invocation.

Compliance Tests
The following compliance tests cover overrides:

asyncOverrides_callAsyncMethod
asyncOverrides_overrideAsyncMethod
asyncOverrides_overrideAsyncMethodByParentClass
asyncOverrides_overrideCallsSuper
asyncOverrides_twoOverrides
asyncOverrides_overrideThrows
syncOverrides
propertyOverrides_get_set
propertyOverrides_get_calls_super
propertyOverrides_set_calls_super
propertyOverrides_get_throws
propertyOverrides_set_throws
propertyOverrides_interfaces
syncOverrides_callsSuper
fail_syncOverrides_callsDoubleAsync_method
fail_syncOverrides_callsDoubleAsync_propertyGetter
fail_syncOverrides_callsDoubleAsync_propertySetter
doNotOverridePrivates_method_public
doNotOverridePrivates_method_private
doNotOverridePrivates_property_by_name_private
doNotOverridePrivates_property_by_name_public
doNotOverridePrivates_property_getter_public
doNotOverridePrivates_property_getter_private

Can you override a constructor? What do you pass in as the method in that case?

Can you override a constructor? What do you pass in as the method in that case?

No, the constructor cannot be virtually called.

Something that wasn't clear to me from this documentation, is how an override calling super() would work here.
From what I understand, if a subclass with an override calls super, then the parent class's invoke call to that function should Just Work (tm) and the JSII will be smart enough not to generate another callback asking for the overridden method to be called.
However, that wasn't clear to me, and I was originally looking for a mechanism to call the original method.


Upgrade mpfr to latest version 4

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender.

This looks good to me now.


(maint) Don't install beaker for spec tests in travis

Prior to this commit, the beaker gem and all its dependencies were
being installed just to run spec tests. Excluding beaker when running
spec tests should make things go faster because we won't have to
install so many gems.

The Travis CI specs should still fail, so this isn't ready for merge yet. But I'm curious to see which gems are installed excluding beaker and its dependencies in hopes that it will help narrow down the gem that's causing the spec failure (thanks for the idea @kylog!).

:+1:

This one's ready to go too!


Fix target of StateImplementationMixin_API

Fixes warning:
@Mixin target net/minecraft/block/state/BlockStateContainer$StateImplementation is public in mixins.common.api.json:mcp.block.state.StateImplementationMixin_API and should be specified in value
Already my eyes hurt to see this yellow string...

This should be added to the OCD list to be merged at a later time in bulk.


How about add a web UI for colly?

Just like pyspider, how about add a web UI for Colly which can help user to control their spider.

This is a great idea. I started to implement a web debugger: https://github.com/gocolly/colly/blob/389bc3c811e16f7bfba497d8dc6bf4f98a51c8fe/debug/webdebugger.go , but it's really basic and I'm still not sure if it is the right approach. Would you like to work on this topic?

First of all, we should use the separation of front and back ends;
secondly, jQuery is not a good way to build the front end, recommend Vue.js;
then,we call API which provided by Colly  in front end.

How about it?
By the way, where could I find the API document of Colly?

First of all, we should use the separation of front and back ends;

I agree, that's why I created a debug interface which can be used by the webdebugger.

secondly, jQuery is not a good way to build the front end, recommend Vue.js;

Also agreed, it was just a quick POC.

By the way, where could I find the API document of Colly?

https://godoc.org/github.com/gocolly/colly

Hi, I made a simple web ui long time ago (just omit the picture ), now I wanna to make it open source.
And I think it is a good fit for Colly's management page.

client is the VM which one colly deploy on.
project is all your colly project.
We only need to use your colly lib to make web api. What do you think? Listen to your opinions with humility.

If use wanna review the source code, I think we can put it into colly project.

UI looks nice and clean :+1: is there a place we can play with a demo?

UI looks nice and clean 👍 is there a place we can play with a demo?

wait a minute, I am making it and the I will push it to github.

@vosmith The project is https://github.com/hantmac/CollyFront, I named it CollyFront, if you mind it, I can rename it.☺😆

@hantmac awesome I'll check it out there!

great idea you will have a little doc or demo even brider to see the beast in action :) because I have a doubt about the implementation with go colly
thank you for all his


Error when executing the SQLSRV driver, it is not recognized in the php_info() and neither in practice in code

PHP version
8.1.18 FPM
PHP SQLSRV or PDO_SQLSRV version
PDO_SQLSRV: 5.11.0 - SQLSRV: 5.11.0
Microsoft ODBC Driver version
ODBC 18
SQL Server version
Microsoft SQL Server 2016
Client operating system
Linux - Ubuntu 20.04
Problem description
Install the necessary drivers as well as the ODBC ones, I added it in the php.ini, and it does not execute, nor does it recognize it in the php_info(), since I updated to the latest versions of these... before updating these drivers They worked normally... could you help me, to install and activate it? These extensions were installed with PECL.

find the error, it was that it does not recognize the driver, follow a script that I visualize in the documentation, and everything seems to work normally, thanks take care.


Add macOS CI

I think that it's a good idea to add a CI to make macOS builds. I've found CircleCI which says that it can build for macOS, but I havn't had a chance to test it.

Is CircleCi Travis's main "competitor " (for a lack of better word, since they are both free)? Since Travis is executing in the bash environment doesn't Travis cover the build for Linux and Mac (assuming no Mac specific commands)? More thoughts on this would be useful when you've tested things out, let us know. Thank you!

Travis can do macOS as well: https://docs.travis-ci.com/user/osx-ci-environment/

I was just looking at that now. I will do a test in one of my repos to see how it works.

All you need to do is tell it to use both macOS and Linux. I've created a pull request #97.

I've  created another pull request with only 1 commit. #98

Mac builds take a while to start building. Have a look at the build for #98. https://travis-ci.org/jprichardson/reload/builds/243761480. There is about 10 minutes spent waiting for the osx builds to start. I am going to see if using CircleCI would be faster.

Closed by #98

I'm almost thinking of backing out mac os building as it really slows the building process down.
See: https://github.com/travis-ci/travis-ci/issues/7304

I recommend removal. I can't think of a command on Linux that doesn't work on Mac. All my deployments are from Mac onto Linux. I added Mac to my ack-reload fork and am set to delete it as well for the long times. Farewell fellas, impressing me to see such big ticket items being tackled day after day.

@alallier What are we doing about this. Should we remove Mac CI support completely? Or maybe go with my original idea of using CIrcleCI? I've seen a couple of projects which use both Travis and Circle. Maybe we should do that.

Not sure we have no research on CircleCI but I over waiting for Travis Mac VMs to spin up, it just takes way too long, since they are a limited resource

@AckerApple What did you do about this?

Thanks for asking. I completely removed for two reasons (have not pushed to NPM yet):
#1 : Mac runs on the same "rails" as Linux so they 99.9% produce the same results
#2 : The travis cli tester waits forever to start and then when it says started it still has a ton of MAC startup commands processing
You fellas have been working hard on this project. I think I might jump back in with y'all. I would add what's already in my fork:
#1 If port is already taken the reload wants to use, offer cli prompt to go to next port
#2 A true NPM test with unit test cases (describe, it, assert)
#3 Remove express (I don't use "your" reload because of this)
Thanks for asking my opinion

Thanks for your comment @AckerApple but please keep the conversation limited to the topic of this issue. Personally I think it might just be worth removing MacOS building for now as we are really just linting now and that makes no difference when running on Linux vs MacOS. The only reason I would be hesitant is I am planning to write unit tests next for this and building on Mac then would make a difference. But for now we could consider removing MacOS and adding it back when unit testing is added (knowing the performance problems or looking at an alternative like CircleCI).
Do we have any idea if CircleCI's Mac building is way faster that Travis's? If it isn't it's not worth adding

@alallier . Seriously man? "Please keep the conversation limited to the topic of the issue".
Please keep being a Robot to a minimum and take these chances to be alive.
Whatever, I couldn't really read the rest when you act like Angular with comment control policing like we don't have time to be considerate to be humans.
And I don't have a filter. My fault.

If you have a new idea or suggestion please open an issue and we can discuss it there.


docker compose up fails - could not find 'jekyll-tabs'

Have you checked that your issue isn't already filed?

[X] I read through FAQ and searched through the past issues, none of which addressed my issue.
[X] Yes, I have checked that this issue isn't already filed.

Bug description
I cannot run 'docker compose up'
How to reproduce the bug

Clone the repo
Install all necessary dependencies using WSL2 - Ubuntu 22.04
sudo docker compose pull
sudo docker compose up

Error messages and logs
Attaching to jekyll-1
jekyll-1  | /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/resolver.rb:332:in `raise_not_found!': Could not find gem 'jekyll-tabs' in locally installed gems. (Bundler::GemNotFound)
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/resolver.rb:392:in `block in prepare_dependencies'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/resolver.rb:377:in `each'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/resolver.rb:377:in `map'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/resolver.rb:377:in `prepare_dependencies'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/resolver.rb:61:in `setup_solver'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/resolver.rb:28:in `start'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/definition.rb:626:in `start_resolution'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/definition.rb:311:in `resolve'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/definition.rb:579:in `materialize'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/definition.rb:203:in `specs'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/definition.rb:270:in `specs_for'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler/runtime.rb:18:in `setup'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/bundler-2.5.7/lib/bundler.rb:162:in `setup'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/jekyll-4.3.3/lib/jekyll/plugin_manager.rb:52:in `require_from_bundler'
jekyll-1  |     from /var/lib/gems/3.0.0/gems/jekyll-4.3.3/exe/jekyll:11:in `<top (required)>'
jekyll-1  |     from /usr/local/bin/jekyll:25:in `load'
jekyll-1  |     from /usr/local/bin/jekyll:25:in `<main>'```

### What operating system are you using?

Windows

### Where are you seeing the problem on?

Running locally with Docker

### More info

I had the same issues running the command on OSX.

Fixing #2384 also fixes this.