Division by zero

Hi,
the parameter w is not checked for range, so this line:
c = c * self.w / (1 - self.w)
can divide by zero.
How about an additional line in init:
assert self.w<=0<1
BTW: I find it hard to understand the meaning of the documentation of w without reading the original paper. I suppose w=0 (default) is the case for Gaussian distributions only and w=1 for equal distribution (in the presence of noise), right?

Thanks for catching the potential bug. I am kind of overwhelmed by other responsibilities but would like to fix this sometime in the future.
I would prefer raising a ValueError instead of an assert.
w is a measure of outliers, i.e. target points that do not belong to the target point cloud but exist due to noise in measurements. The paper makes the assumption that outliers can appear anywhere, hence they are modeled as a uniform distribution. w=0 means that there are no outliers in the data. w≈1.0 means that the entire point cloud is outliers.

Im closing this because the current code already throws a ValueError if w >= 1 therefore this case shouldn't happen.
See: https://github.com/siavashk/pycpd/blob/83ffd5ae14ec898f4415f34ed6fd183c34026804/pycpd/emregistration.py#L163-L165


How to set the container_name property for RabbitMQ Docker containers?

I am using the following code to create three RabbitMQ Docker containers and want to test their behavior as nodes. I would like to set the hostname property for the containers to easily identify and manage them.
var builder = DistributedApplication.CreateBuilder(args);

var rabbitMq = builder.AddRabbitMQContainer("EventBus");
rabbitMq.WithEnvironment("RABBITMQ_ERLANG_COOKIE", "secretcookie");
rabbitMq.WithVolumeMount("rabbitmq-node.config", "/etc/rabbitmq/rabbitmq.config");

var rabbitMq1 = builder.AddRabbitMQContainer("EventBus1");
rabbitMq1.WithEnvironment("RABBITMQ_ERLANG_COOKIE", "secretcookie");
rabbitMq1.WithVolumeMount("rabbitmq-node.config", "/etc/rabbitmq/rabbitmq.config");

var rabbitMq2 = builder.AddRabbitMQContainer("EventBus2");
rabbitMq2.WithEnvironment("RABBITMQ_ERLANG_COOKIE", "secretcookie");
rabbitMq2.WithVolumeMount("rabbitmq-node.config", "/etc/rabbitmq/rabbitmq.config");

How should I set the hostname property to facilitate testing and managing these RabbitMQ containers?
docker-compose.yml
version: '3.8'

services:
  rabbitmq-node1:
    image: "rabbitmq:3-management"
    container_name: "rabbitmq-node1"
    hostname: rabbitmq-node1
    ports:
      - "5672:5672"
      - "15672:15672"
    environment:
      RABBITMQ_ERLANG_COOKIE: "secretcookie"
    volumes:
      - ./rabbitmq-node1.config:/etc/rabbitmq/rabbitmq.config
    networks:
      - rabbitmq-cluster

  rabbitmq-node2:
    image: "rabbitmq:3-management"
    container_name: "rabbitmq-node2"
    hostname: rabbitmq-node2
    ports:
      - "5673:5672"
      - "15673:15672"
    environment:
      RABBITMQ_ERLANG_COOKIE: "secretcookie"
    volumes:
      - ./rabbitmq-node2.config:/etc/rabbitmq/rabbitmq.config
    networks:
      - rabbitmq-cluster

  rabbitmq-node3:
    image: "rabbitmq:3-management"
    container_name: "rabbitmq-node3"
    hostname: rabbitmq-node3
    ports:
      - "5674:5672"
      - "15674:15672"
    environment:
      RABBITMQ_ERLANG_COOKIE: "secretcookie"
    volumes:
      - ./rabbitmq-node3.config:/etc/rabbitmq/rabbitmq.config
    networks:
      - rabbitmq-cluster

networks:
  rabbitmq-cluster:
    driver: bridge

Dupe of https://github.com/dotnet/aspire/issues/949


Added Ben Sampica's roll for initiative under game mode

What type of PR is this? (check all applicable)

[X] 🚀 Added Name
[ ] ✨ Feature
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
I made a little Roll For Initiative game for my readme and thought I'd share.
Add Link of GitHub Profile
https://github.com/benjaminsampica/benjaminsampica

This looks so Good, I'm merging now,
P.S - Don't forget to leave a ⭐ if you found this helpful.
Thanks


code: 101, message: Unexpected packet Query received from client when updating many-to-many association

Not sure this is a bug or my own misunderstanding of gorm:
These models:
type HModel struct {
	ID        string `gorm:"primarykey"`
	CreatedAt time.Time
	UpdatedAt time.Time
	// DeletedAt DeletedAt `gorm:"index"`
}

type Visitor struct {
	HModel
	Email string `gorm:"unique" json:"email"`
	FirstName    string           `json:"first_name"`
	LastName     string           `json:"last_name"`
	Aliases []*Alias `gorm:"many2many:visitor_to_alias" json:"aliases"` // many:many
}

type Alias struct {
	Email     string `gorm:"primaryKey" json:"email"`
	FirstName string `json:"first_name"`
	LastName  string `json:"last_name"`
}

an implementation of adding an alias for a visitor like this:
func UpsertAliasForVisitor(db *gorm.DB, visitor *Visitor, alias *Alias) (err error) {
	err = db.Model(alias).Create(alias).Error
	if err != nil {
		return err
	}
	return db.Model(visitor).Association("Aliases").Append(alias)
}

Fails like such:
[6.709ms] [rows:0] INSERT INTO `aliases` (`email`,`first_name`,`last_name`) VALUES (?,?,?)
clickhouse-go: [send query] compression="lz4" ALTER TABLE `visitors` UPDATE `updated_at`=toDateTime('1705510846') WHERE `id` = '018d185e-3e35-7491-86d6-abbb58e64515'
clickhouse-go: [send data] compression="lz4"
clickhouse-go: [end of stream]
clickhouse-go: [send query] compression="lz4" INSERT INTO `aliases` (`email`,`first_name`,`last_name`) VALUES
clickhouse-go: [send data] compression="lz4"
clickhouse-go: [table columns]
clickhouse-go: [read data] compression="lz4". block: columns=3, rows=0

2024/01/17 11:00:46 /Users/thomashemphill/ubuntu-work/hulation/model/visitor.go:194
[1.576ms] [rows:0] INSERT INTO `aliases` (`email`,`first_name`,`last_name`) VALUES (?,?,?) ON CONFLICT DO NOTHING
clickhouse-go: [send query] compression="lz4" INSERT INTO `visitor_to_alias` (`visitor_id`,`alias_email`) VALUES
clickhouse-go: [send data] compression="lz4"
clickhouse-go: [exception] code: 101, message: Unexpected packet Query received from client
[clickhouse-std][conn=0][localhost:9000] PrepareContext error: code: 101, message: Unexpected packet Query received from client

2024/01/17 11:00:46 /Users/thomashemphill/ubuntu-work/hulation/model/visitor.go:194 code: 101, message: Unexpected packet Query received from client
[3.583ms] [rows:0] INSERT INTO `visitor_to_alias` (`visitor_id`,`alias_email`) VALUES (?,?) ON CONFLICT DO NOTHING

However, an implementation calling my own SQL works fine:
func UpsertAliasForVisitor(db *gorm.DB, visitor *Visitor, alias *Alias) (err error) {
	err = db.Model(alias).Create(alias).Error
	if err != nil {
		return err
	}

	return db.Transaction(func(tx *gorm.DB) (err error) {

		if err = tx.Exec("INSERT INTO `visitor_to_alias` (`visitor_id`,`alias_email`) VALUES (?,?)", visitor.ID, alias.Email).Error; err != nil {
			fmt.Printf("Error inserting into visitor_to_alias: %s", err.Error())
			log.Errorf("Error inserting into visitor_to_alias: %s", err.Error())

		}
		return
	})
}

Results:
2024/01/17 11:08:10 /Users/thomashemphill/ubuntu-work/hulation/model/model_test.go:109
[15.935ms] [rows:0] INSERT INTO `visitors` (`id`,`created_at`,`updated_at`,`email`,`ss_cookie`,`first_name`,`last_name`) VALUES (?,?,?,?,?,?,?)
    model_test.go:115: Insert ok.

Verified everything using the clickhouse client.
ClickHouse client version <IP_ADDRESS> (official build).
Connecting to localhost:9000 as user default.
Connected to ClickHouse server version 23.12.2.

My understanding is that the error:  code: 101, message: Unexpected packet Query received from client
Is likely when the same client is asked to start a new transaction while waiting on another to complete. My cursory glance at the source confirms this.
Notice that the clickhouse-go end of stream event never occurs in the first implementation. Is the gorm clickhouse driver not waiting for the first action to complete, or am i doing something wrong here?
related:
https://github.com/ClickHouse/clickhouse-go/issues/322
https://github.com/ClickHouse/clickhouse-go/issues/485

Further research indicates to me that Clickhouse does not even support constraints with foreign keys. It does not seem to be supported in their SQL spec.
See:
https://clickhouse.com/docs/en/sql-reference/statements/alter/constraint
https://stackoverflow.com/questions/66354832/how-can-i-use-functionality-of-primary-key-and-foreign-key-in-clickhouse
Take for instance this table:
type User struct {
	HModel
	Email     string  `gorm:"index"`
	Roles     []*Role `gorm:"many2many:user_roles;"`
	FirstName string
	LastName  string
	Role      string
}

...

type HModel struct {
	ID        string `gorm:"primarykey"`
	CreatedAt time.Time
	UpdatedAt time.Time
	// DeletedAt DeletedAt `gorm:"index"`
}

When doing a err = db.AutoMigrate(&User{}, &Role{}) the driver will attempt this:
ALTER TABLE `user_roles` ADD CONSTRAINT `fk_user_roles_role`
FOREIGN KEY (`role_id`,`role_type`) REFERENCES `roles`(`id`,`type`)

But, at least based on my very limited (a week worth of messing with Clickhouse) this SQL statement is just wrong.
For instance running it in clickhouse-client results in:
Syntax error: failed at position 63 ('FOREIGN'):

 ALTER TABLE `user_roles` ADD CONSTRAINT `fk_user_roles_role` FOREIGN KEY (`role_id`,`role_type`) REFERENCES `roles`(`id`,`type`)

Expected one of: CHECK, ASSUME

Maybe someone could shed light on this.
But - as far as i can tell - this driver is just basically broken.

I think the only reasonable way to do many-to-many in clickhouse would be to simply use the ReplacingMergeTree engine using TUPLE() as the ORDER BY
Anyone? thoughts?
Or please tell me I am missing something big here.


What are the problems with using Jax-RS instead of Cloud Endpoints on Google App Engine?

Thinking about using Jax for this, but my question is would I be giving up anything in terms of logging and metrics?
-Montana

"Jax" and "Jax-RS" are unrelated projects. This "Jax" is a machine-learning system; I think you were looking for the other "JAX-RS".


GettingStarted.md: Remove two "forced line breaks"

… and one superfluous example.  Also slightly enhance wording at some places.

Where are we with this PR? @piggz are all changes done and now OK for merge?

Done!


countdown clock v1

https://media.discordapp.net/attachments/756951813541986484/813872779983061012/Desktop_-_2.png?width=1080&height=768

Innovation    Insight sharing    7    17-Feb-2021    22:00    24-Feb-2021
Innovation    Proposal Submission    7    24-Feb-2021    22:00    3-Mar-2021
Innovation    Refine Proposals    7    3-Mar-2021    22:00    10-Mar-2021
Innovation    Finalize Proposals    7    10-Mar-2021    22:00    17-Mar-2021
Innovation    Review Proposals / Assess    7    17-Mar-2021    22:00    24-Mar-2021
Innovation    Assess QA    7    24-Mar-2021    22:00    31-Mar-2021
Governance    Register proposals + Voters    7    7-Apr-2021    19:00    14-Apr-2021
Governance    Snapshot    2    14-Apr-2021    19:00    16-Apr-2021
Governance    Voting    19    16-Apr-2021    19:00    5-May-2021
Governance    Tallying    2    5-May-2021    19:00    7-May-2021
Execution    Rewarding    2    14-May-2021        16-May-2021
Execution    Reporting    Every two weeks


WIP Preparation job

This PR separates the ingestion of data out of the aggregation and wholesale job.
Input data is now stored as a snapshot and used in the following jobs.

need snapshotId


Let anchors be styleable as buttons

Fixes https://github.com/ampproject/ampstart/issues/208

@sebastianbenz - can you review pls :)

will do


Error Code 0xc000007b while updating

Issue Type
Bug
Description
In VS Code Insider:
Search for and download update.
Click install update.
Click "restart for update".
This error shows up:

After clicking OK, VS Code starts with no errors, but has not installed the update.
VS Code Info
VS Code version: Code - Insiders 1.21.0-insider (ef42990520a856451ba5ad6fa1d299b0e0c185a2, 2018-02-12T05:14:21.574Z)
OS version: Windows_NT x64 10.0.10240
Version 1.21.0-insider
Commit ef42990520a856451ba5ad6fa1d299b0e0c185a2
Date 2018-02-12T05:14:21.574Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz (4 x 2712)

Memory (System)
15.93GB (11.28GB free)

Process Argv
C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe

Screen Reader
no

VM
0%

Reproduces without extensions

@tweakimp Please disable background updates with the following setting: "update.enableWindowsBackgroundUpdates": false
Please enable it back again mid next week and let me know if you still have the same problem.

So no updates for me for a week? :'( I'll do it though, for science!

@tweakimp Give it a try any time now, let me know how it goes.

It worked!

Sweet! Thanks @tweakimp!

Marking as verified. Running with background update for a while without problems.

Does this mean I can revoke the setting?

What do you mean? I thought this worked for you.

It did work and I can confirm that I was able to revoke the setting and it still works.


add notebook example for creating dataset for object detection and instance segmentation

I added a notebook tutorial to create a dataset for object detection and instance segmentation using VHR-10 dataset originally from chaozhong2010/VHR-10_dataset_coco
The notebook was created using colab and i convert it to jupyter environment

@haritsahm This looks amazing. What is your Hub slack handle by the way? (I want to give you a shout out :) )

@haritsahm This looks amazing. What is your Hub slack handle by the way? (I want to give you a shout out :) )

thank you! It's @haritsahm


[RC2] GC: Port recent telemetry changes

Port the following commits to RC2 branch:

f2b744a7f92e52fe40ec2e66bcb824bd3ac14cd9
059fc1896bbb11419e62e1351c50a2c23f1d3d1c
059fc1896bbb11419e62e1351c50a2c23f1d3d1c
68e6f921898cfa5b8210eb72304cdc89259c44de

@tyler-cai-microsoft head ups I'm porting #20185 here, I wanted to check for aliased dataStore synchronously for logging.


Array Parameter not recognising comma seperated integer items

I'm attempting to use the array parameter type with an items type of integer. Although when i then attempt to input values via the webUI to test the action. It returns an
"Failed to run action "value before comma" is not of type integer"
error message appears. It doesn't even actually call the action (not showing in history)
Input in web UI
85001,85002
I have tried the following and all return the same error
[85001,85001]
85001
Yaml config:
parameters:
   mid:
      type: "array"
      description: "ICSP MID for desired server. (Comma seperated)"
      required: true
      items:
        type: "integer"

Thanks for the report. Yes, I can confirm there is a problem of field type: "array" not converting item values to the type specified instead just sending them as strings.
Temporary workaround would be to remove items.type part from the parameter and convert them to integer inside the action. Proper routine for handling conversion of inner types would be a part of parameter form overhaul I've mention in #296.

I think @bigmstone fixed this in https://github.com/StackStorm/st2web/pull/360. I'll wait for him to confirm.


kyber network- set enable, verify all contracts were set, including proxy

currently proxy isn't tested upon set enable

already fixed.


ignore_fail doen't work with sequence tasks

Hello! This is the sample of pyproject.toml
[tool.poetry]
name = "poe_test"
version = "0.1"
description = ""
authors = ["John Smith<EMAIL_ADDRESS>
[tool.poetry.dependencies]
python = ">=3.8.1,<4.0"

[tool.poetry.group.dev.dependencies]
poethepoet = "^0.29.0"

[tool.poe.tasks]
task1 = "echo Task1"
task2_1 = "echo Task2_1"
task2_2 = "bash -c 'exit 1'"
task2_3 = "echo Task2_3"
task2 = ["task2_1", "task2_2", "task2_3"]
task3 = "echo Task3"
task4 = "echo Task4"
all.sequence = ["task1", "task2", "task3", "task4"]
all.ignore_fail = "return_non_zero"

[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

I run commands
poetry install --no-root
poetry run poe all

And i got this output

Poe => echo Task1
Task1
Poe => echo Task2_1
Task2_1
Poe => bash -c 'exit 1'
Poe => echo Task2_3
Task2_3
Error: Subtasks task2_2 returned non-zero exit status

Seems like a bug, why task3 and task4 aren't starting in this case? I set ignore_fail = "return_non_zero" for the task all.
If task1/task3/task4 would failed, the rest of the tasks will be started, but if task2 failed the next tasks aren't starting.
Poetry v1.8.4
poethepoet v0.29.0
Python3 v3.12.3
Ubuntu 24.04

Hi @ownik, thanks for the feedback. I hadn't thought about that edge case... it does seem like a bug.
I suppose the ideal behaviour would be that when task2 fails, it prints an error to indicate this and aborts task2 (as is the case already), but then it should catches the error and continue with the next subtask of all.
I'll see what I can do about it.

This issue is fixed in v0.30.0 🚀


Split the section about embed=true parameter of embedded Streamlit apps

Successor to #688
The embed=true query parameter has a noteworthy side effect, so its section should be separated.

TODO: While the updated content is correct for the upstream Streamlit, HF Spaces' patched Streamlit always disables scrolling even when being served without embed=true, so we have to investigate it before publishing this change.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

@osanseviero Sorry it has been stale for a long time. I fixed it and marked as ready.


rdoc for SoftLayer::ImageTemplate class documents two attributes (globalIdentifier and note) that aren't supported

(I originally posted this against to the portal forum but was directed to open it here...)
I am just pointing out a doc issue here... I am using the softlayer_api 3.0.2 Ruby gem. When I access the rdoc that got installed with gem, and looking at the doc for the SoftLayer::ImageTemplate class (.../softlayer_api-3.0.2/rdoc/SoftLayer/ImageTemplate.html), it documents five (5) Attributes, but two are not supported and when I try to access them I get:
undefined method `globalIdentifier' for #SoftLayer::ImageTemplate:0x9939078 (NoMethodError)
(or 'note' for the other Attribute that's not supported.) So basically the Attributes notes, global_id and name work; globalIdentifier and note do not work. I guess those two have been deprecated in favor of global_id and notes.
Really not a big deal just pointing out the rdoc discrepancy.

I think this is a more broad issue than just in the SoftLayer::ImageTemplate class. Basically anywhere where the sl_attr method is used with the second parameter ala:
sl_attr :global_id, 'globalIdentifier'
Then in addition to rdoc'g the first parameter (e.g., "global_id" in the above) as an attribute, it will rdoc the second as well as an attribute.

This kind of thing (from for example the SoftLayer::ImageTemplate class:
##
# :attr_reader:
# The notes, if any, that are attached to the template. Can be nil.
sl_attr :notes, "note"

causes rdoc to treat everything after "sl_attr" as an attribute. I think this will address this:
##
# :attr_reader: notes
# The notes, if any, that are attached to the template. Can be nil.
sl_attr :notes, "note"

But if it's somehow the intent that both "note" and "notes" are actually intended to be attributes then this is not the fix.
Can anyone comment on the intent here? I will submit a patch to fix up the rdoc defs here in the meantime, hoping that that's the way we want to go here...

Right its only the first that should be the attribute. Ive been testing and we need to do this for all the objects for all sl_attr and sl_dynamic_attr entries.

I think it should be this:
##
# :attr_reader: attr_label
sl_attr :attr_label, 'alt_attr_label'

#If the sl_dynamic_attr does not accept a parameter then its marked as attr_reader

##
# :attr_reader: dymanic_attr_label
sl_dynamic_attr :dynamic_attr_label do |param|
   #body
end

#If the sl_dynamic_attr does accept a parameter (such as Account.bare_metal_servers) then its marked as method

##
# :method: dymanic_attr_label
sl_dynamic_attr :dynamic_attr_label do |param|
   #body
end

I am not sure if all sl_dynamic_attr support the force_update parameter by default, but if they do then all of them should be marked as method  and not attr_reader and they probably all need to have the call-seq section added to show that it takes that parameter.

So on the sl_dynamic_attr given that these are actually attributes, I guess it depends on taste how we want to really doc this, if we want to leave it as :attr_reader: it doesnt seem to support :call-seq: but we can indent a block above the description as follows:
##
# :method: dymanic_attr_label
#   dynamic_attr_label(force_update=false)
#
# Description
sl_dynamic_attr :dynamic_attr_label do |param|
   #body
end

The two space indent causes the method to appear in a "code" block as it does in normal markdown.

@ju2wheels  - You wrote:

[...] we need to do this for all the objects for all sl_attr [...] entries.

For sure we should do this for any sl_attr that has the 2nd argument... Do you think we should specify the rdoc :attr_reader: modifier even for those that don't specify the 2nd argument, i.e., like this case?
##
# :attr_reader:
sl_attr :attr_label

I dont see a need to unless theres a case where its showing up different in the doc like the two arg one.

Also I notice that Datacenter.rb seems to have undocumented attributes. Is this on purpose or an oversight?
In Datacenter.rb:
sl_attr :name
sl_attr :long_name, "longName"

Oversight, if its there it should be doc'ed as usable.

@ju2wheels - I think I like the option where you specify the calling sequence directly on the :attr_reader: directive, what you called alternative 2, ala:
##
# :attr_reader: dynamic_attr_label(force_update=false)
#
# Description
sl_dynamic_attr :dynamic_attr_label do |param|
    # body
end

That comes out looking like this which I prefer:

Would you be ok with going that way?
Does every sl_dynamic_attr defined attribute support the force_update=false argument? I think from looking at DynamicAttribute.rb that they do. I only see it documented in some of the dynamic attribute cases though...

Yes all of them should support it, I tested it on a dynamic attribute that didnt have it doc'ed and it worked. Its hard to tell from the way the metaprogramming code was written but the getter it defines seems to consistently support that option.
Ill defer to Scott on the doc part for dynamic attrib, I could make the argument for either but given the implementation alt 2 makes the most sense.

@SLsthompson - Could I trouble you to weigh in here on a couple of things about how we want to document the attributes created via sl_dynamic_attr?

How to rdoc sl_dynamic_attr as attributes? I guess these are unusual in that they are attributes but they take this force_update=true|false optional argument. @ju2wheels made some suggestions as to how to handle this above. I favor just rdoc'g them with the :attr_reader: modifier specifying the full method call ala:
 ##
 # :attr_reader: dynamic_attr_label(force_update=false)
 #
 # Description
 sl_dynamic_attr :dynamic_attr_label do |param|
     # body
 end

This would show the rather unusual "dynamic_attr_label(force_update=false)" in the rdoc attributes section when almost always Ruby attributes would just show as "dynamic_attr_label".
But another way to go might be to just use the attribute name and somehow make reference to the notion of force_update in the description for the attribute ala:
    ##
    # :attr_reader: dynamic_attr_label
    #
    # Description would somehow mention that there's a force_update=true|false
    # argument.
    sl_dynamic_attr :dynamic_attr_label do |param|
        # body
   end

A potential benefit here is that the attribute's rdoc output might look more "normal".

Include force_update on all such sl_dynamic_attr attributes? Although as @ju2wheels notes, the force_update argument works on all sl_dynamic_attr attributes, it is only mentioned in the description for the ones where there is a 5 minute auto-refresh implemented. We are thinking that we should mention force_update for all sl_dynamic_attr attributes. What do you think?

I'd like, if nothing else for completeness sake, to deal with this now so I'm hoping you can give me some thoughts here.

Hmm... I thought I had added a comment but I don't see it now.
Please take my comments as a member of the community, not as a SoftLayer directive (or edict or whatever...)

If we are to document these as attributes (i.e. with :attr_reader) then I prefer the "oddness" of the top option to overburdening the description for ALL of them.
However, I find myself second guessing using "attr" in the name to begin with.  I mean what these really are are "getter" methods.  The advantage of documenting them with :attr_reader is that they show up as attributes in rdoc, but they're not REALLY Ruby attributes.  I'm kinda back and forth about whether documenting them as such is a good thing.

If you're going to expose the force update parameter for the getter then it should probably be done everywhere.
The other way you might handle this is by finding some way to flag the "getter" routines as being sl_dynamic_attr in the documentation then finding some where in the framework documentation to explain exactly what that means.

@SLsthompson:

How to doc the dynamic sl_dynamic_attr "attributes"?

However, I find myself second guessing using "attr" in the name to begin with. I mean what these really are are "getter" methods. The advantage of documenting them with :attr_reader is that they show up as attributes in rdoc, but they're not REALLY Ruby attributes. I'm kinda back and forth about whether documenting them as such is a good thing.

I consulted with one of our more senior Ruby devs and his inclination was to doc the sl_dynamic_attr things as methods. I am coming around to this position as well. And as methods it's not odd or confusing at all to have the force_update argument. And most of these occasions are documented that way right now, modulo a few which I will fix.
I think we should leave the sl_attr items as they are now, annotated as attributes via the :attr_reader: specifier.
So can we agree to:
a. Document sl_dynamic_attr items as methods (as they mostly are now); and
b. Document sl_attr items as attributes (:attr_reader:) (as they also mostly are now)
Sound OK?

force_update documented on all sl_dynamic_attr items?

If you're going to expose the force update parameter for the getter then it should probably be done everywhere.

For sure I think the force_update parameter should be documented on the methods where there is the "auto update every 5 minutes" scheme, but I think it might already be in those cases. I will verify that.
@ju2wheels said pretty much the same thing that we should document the force_update parameter everywhere so let me make an update accordingly.

For sure I think the force_update parameter should be documented on the methods where there is the "auto update every 5 minutes" scheme, but I think it might already be in those cases. I will verify that.

I dont think thats true for all of them. Its only in Account that there are dynamic attr entries that decide to update every 5 min if you dont specify force_update (why that was done I have no idea, but it seems to be one of the few oddball updates).

I think my pull request https://github.com/softlayer/softlayer-ruby/pull/98 is ready to go for this.

OK.  I will give the changes a quick look.  With the expanded Object Filter capability I'll start thinking about a 3.1 release.  Is there anything else you guys would like to get into that?

Im going to have the cleanup stuff pushed today (need to add changes based on comments and the result limit options) and the base class for the first half of basic Network Monitors (making some last tweaks to implementation). Thats all I have right now thats ready to go.


Locally testing use cases in a distributed setup

Need to test the use cases with multiple gateway nodes.
Tested use cases are updated in the internal spreadsheet [1] in sheet "Manual Testing - 2 nodes"
[1] PROJECT  Doc - Improvement for BE and burst related distributed throttling

12/06/2023 : Completed


Previous/next guide link not working properly

Sorry, I didn't get the issue. Why is it not working properly?

It's not a link, it says gobstones/Fundamentos de la Programación

Yes, it is not a link. But arrows are. What did you expected?

BTW, gobstones/Fundamentos de la programación is the name of the Path.

However, the gobstones string is a bit redundant, because it's already written next to the guide title.


- Generating module map file at `Pods/Target Support Files/device_info/device_info.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/device_info/device_info-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/device_info/device_info-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/device_info/device_info-dummy.m`
        - Installing target `emoji_picker` iOS 8.0
          - Generating module map file at `Pods/Target Support Files/emoji_picker/emoji_picker.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/emoji_picker/emoji_picker-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/emoji_picker/emoji_picker-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/emoji_picker/emoji_picker-dummy.m`
        - Installing target `facebook_app_events` iOS 9.0
          - Generating module map file at `Pods/Target Support Files/facebook_app_events/facebook_app_events.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/facebook_app_events/facebook_app_events-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/facebook_app_events/facebook_app_events-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/facebook_app_events/facebook_app_events-dummy.m`
        - Installing target `file_picker` iOS 8.0
          - Generating module map file at `Pods/Target Support Files/file_picker/file_picker.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/file_picker/file_picker-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/file_picker/file_picker-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/file_picker/file_picker-dummy.m`
        - Installing target `firebase_analytics` iOS 10.0
          - Generating module map file at `Pods/Target Support Files/firebase_analytics/firebase_analytics.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/firebase_analytics/firebase_analytics-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/firebase_analytics/firebase_analytics-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/firebase_analytics/firebase_analytics-dummy.m`
        - Installing target `firebase_auth` iOS 10.0
          - Generating module map file at `Pods/Target Support Files/firebase_auth/firebase_auth.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/firebase_auth/firebase_auth-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/firebase_auth/firebase_auth-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/firebase_auth/firebase_auth-dummy.m`
        - Installing target `firebase_core` iOS 10.0
          - Generating module map file at `Pods/Target Support Files/firebase_core/firebase_core.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/firebase_core/firebase_core-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/firebase_core/firebase_core-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/firebase_core/firebase_core-dummy.m`
        - Installing target `firebase_crashlytics` iOS 10.0
          - Generating module map file at `Pods/Target Support Files/firebase_crashlytics/firebase_crashlytics.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/firebase_crashlytics/firebase_crashlytics-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/firebase_crashlytics/firebase_crashlytics-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/firebase_crashlytics/firebase_crashlytics-dummy.m`
        - Installing target `firebase_database` iOS 10.0
          - Generating module map file at `Pods/Target Support Files/firebase_database/firebase_database.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/firebase_database/firebase_database-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/firebase_database/firebase_database-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/firebase_database/firebase_database-dummy.m`
        - Installing target `firebase_dynamic_links` iOS 10.0
          - Generating module map file at `Pods/Target Support Files/firebase_dynamic_links/firebase_dynamic_links.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/firebase_dynamic_links/firebase_dynamic_links-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/firebase_dynamic_links/firebase_dynamic_links-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/firebase_dynamic_links/firebase_dynamic_links-dummy.m`
        - Installing target `firebase_messaging` iOS 10.0
          - Generating module map file at `Pods/Target Support Files/firebase_messaging/firebase_messaging.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/firebase_messaging/firebase_messaging-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/firebase_messaging/firebase_messaging-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/firebase_messaging/firebase_messaging-dummy.m`
        - Installing target `firebase_remote_config` iOS 10.0
          - Generating module map file at `Pods/Target Support Files/firebase_remote_config/firebase_remote_config.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/firebase_remote_config/firebase_remote_config-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/firebase_remote_config/firebase_remote_config-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/firebase_remote_config/firebase_remote_config-dummy.m`
        - Installing target `firebase_storage` iOS 10.0
          - Generating module map file at `Pods/Target Support Files/firebase_storage/firebase_storage.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/firebase_storage/firebase_storage-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/firebase_storage/firebase_storage-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/firebase_storage/firebase_storage-dummy.m`
        - Installing target `flutter_keyboard_visibility` iOS 8.0
          - Generating module map file at `Pods/Target Support Files/flutter_keyboard_visibility/flutter_keyboard_visibility.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/flutter_keyboard_visibility/flutter_keyboard_visibility-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/flutter_keyboard_visibility/flutter_keyboard_visibility-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/flutter_keyboard_visibility/flutter_keyboard_visibility-dummy.m`
        - Installing target `flutter_sound` iOS 10.0
          - Generating module map file at `Pods/Target Support Files/flutter_sound/flutter_sound.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/flutter_sound/flutter_sound-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/flutter_sound/flutter_sound-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/flutter_sound/flutter_sound-dummy.m`
        - Installing target `fluttertoast` iOS 8.0
          - Generating module map file at `Pods/Target Support Files/fluttertoast/fluttertoast.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/fluttertoast/fluttertoast-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/fluttertoast/fluttertoast-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/fluttertoast/fluttertoast-dummy.m`
        - Installing target `gRPC-C++` iOS 8.0
          - Generating Info.plist file at `Pods/Target Support Files/gRPC-C++/ResourceBundle-gRPCCertificates-Cpp-gRPC-C++-Info.plist`
          - Generating module map file at `Pods/Target Support Files/gRPC-C++/gRPC-C++.modulemap`
          - Generating umbrella header at `Pods/Target Support Files/gRPC-C++/gRPC-C++-umbrella.h`
          - Generating Info.plist file at `Pods/Target Support Files/gRPC-C++/gRPC-C++-Info.plist`
          - Generating dummy source at `Pods/Target Support Files/gRPC-C++/gRPC-C++-dummy.m`
        - Installing target `gRPC-Core` iOS 8.0
          - Copying module map file to `Pods/Target Support Files/gRPC-Core/gRPC-Core.modulemap`
      CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only perfomed in repo update

    ――― MARKDOWN TEMPLATE ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――

    ### Command

    ```
    /usr/local/bin/pod install --verbose
    ```

    ### Report

    * What did you do?

    * What did you expect to happen?

    * What happened instead?

    ### Stack

    ```
       CocoaPods : 1.10.1
            Ruby : ruby 2.6.3p62 (2019-04-16 revision 67580) [universal.x86_64-darwin20]
        RubyGems : 3.0.3
            Host : macOS 11.2.3 (20D91)
           Xcode : 12.4 (12D4e)
             Git : git version 2.23.0
    Ruby lib dir : /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib
    Repositories : master - git - https://github.com/CocoaPods/Specs.git @ a0abf73604cb65bd66eb158d5aac5bc3366927b5

                   trunk - CDN - https://cdn.cocoapods.org/
    ```

    ### Plugins

    ```
    cocoapods-deintegrate : 1.0.4
    cocoapods-plugins     : 1.0.0
    cocoapods-search      : 1.0.0
    cocoapods-trunk       : 1.5.0
    cocoapods-try         : 1.2.0
    ```

    ### Podfile

    ```ruby
    # Uncomment this line to define a global platform for your project
    platform :ios, '10.0'

    # CocoaPods analytics sends network stats synchronously affecting flutter build latency.
    ENV['COCOAPODS_DISABLE_STATS'] = 'true'

    project 'Runner', {
      'Debug' => :debug,
      'Profile' => :release,
      'Release' => :release,
    }

    def flutter_root
      generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
      unless File.exist?(generated_xcode_build_settings_path)
        raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
      end

      File.foreach(generated_xcode_build_settings_path) do |line|
        matches = line.match(/FLUTTER_ROOT\=(.*)/)
        return matches[1].strip if matches
      end
      raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
    end

    require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

    flutter_ios_podfile_setup

    target 'Runner' do
      use_frameworks!
      use_modular_headers!

      flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
    end

    post_install do |installer|
      installer.pods_project.targets.each do |target|
        flutter_additional_ios_build_settings(target)
          target.build_configurations.each do |config|
                  config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= [
                    '$(inherited)',
                     'PERMISSION_EVENTS=0',
                     'PERMISSION_CONTACTS=0',
                    'PERMISSION_SPEECH_RECOGNIZER=0',
                     'PERMISSION_MEDIA_LIBRARY=0',
                     'PERMISSION_SENSORS=0'
                  ]
            end
      end
    end
    ```

    ### Error

    ```
    Errno::ENOENT - No such file or directory @ rb_sysopen - /Users/bhanukaisuru/Documents/REBORN/YELLO/user-app/ios/Pods/gRPC-Core/include/grpc/module.modulemap
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator/pod_target_installer.rb:962:in `read'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator/pod_target_installer.rb:962:in `read'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator/pod_target_installer.rb:962:in `block in create_module_map'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/user_interface.rb:145:in `message'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator/pod_target_installer.rb:961:in `create_module_map'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator/pod_target_installer.rb:78:in `block in install!'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/user_interface.rb:145:in `message'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator/pod_target_installer.rb:40:in `install!'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator.rb:115:in `block in install_pod_targets'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator.rb:112:in `map'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/pods_project_generator.rb:112:in `install_pod_targets'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/single_pods_project_generator.rb:32:in `block in install_all_pod_targets'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/user_interface.rb:145:in `message'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/single_pods_project_generator.rb:31:in `install_all_pod_targets'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer/xcode/single_pods_project_generator.rb:19:in `generate!'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:312:in `block in create_and_save_projects'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/user_interface.rb:64:in `section'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:307:in `create_and_save_projects'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:299:in `generate_pods_project'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:178:in `integrate'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/installer.rb:166:in `install!'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/command/install.rb:52:in `run'
    /Library/Ruby/Gems/2.6.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/lib/cocoapods/command.rb:52:in `run'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.1/bin/pod:55:in `<top (required)>'
    /usr/local/bin/pod:23:in `load'
    /usr/local/bin/pod:23:in `<main>'
    ```

    ――― TEMPLATE END ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――

    [!] Oh no, an error occurred.

    Search for existing GitHub issues similar to yours:
    https://github.com/CocoaPods/CocoaPods/search?q=No+such+file+or+directory+%40+rb_sysopen+-+%2FUsers%2Fbhanukaisuru%2FDocuments%2FREBORN%2FYELLO%2Fuser-app%2Fios%2FPods%2F
    gRPC-Core%2Finclude%2Fgrpc%2Fmodule.modulemap&type=Issues

    If none exists, create a ticket, with the template displayed above, on:
    https://github.com/CocoaPods/CocoaPods/issues/new

    Be sure to first read the contributing guide for details on how to properly submit a ticket:
    https://github.com/CocoaPods/CocoaPods/blob/master/CONTRIBUTING.md

    Don't forget to anonymize any private data!

    Looking for related issues on cocoapods/cocoapods...
    Found no similar issues. To create a new issue, please visit:
    https://github.com/cocoapods/cocoapods/issues/new

Error running pod install

The main error seems to be:
Errno::ENOENT - No such file or directory @ rb_sysopen - ios/Pods/gRPC-Core/include/grpc/module.modulemap
Can you confirm if you have gRPC-Core pod installed ?
Also, can you try rm -rf Pods/ and then pod install to see if it helps ?

@darshankawar I tried rm -rf Pods, NO LUCK.
How can I see gRPC-Core?

@bhanuka96 It's outside of Flutter framework. As mentioned in the error, it seems to be cocoapods issue than Flutter pods.
Follow below links as mentioned in the error to get help on your issue:
Search for existing GitHub issues similar to yours:
    https://github.com/CocoaPods/CocoaPods/search?q=No+such+file+or+directory+%40+rb_sysopen+-+%2FUsers%2Fbhanukaisuru%2FDocuments%2FREBORN%2FYELLO%2Fuser-app%2Fios%2FPods%2F
    gRPC-Core%2Finclude%2Fgrpc%2Fmodule.modulemap&type=Issues

    If none exists, create a ticket, with the template displayed above, on:
    https://github.com/CocoaPods/CocoaPods/issues/new

    Be sure to first read the contributing guide for details on how to properly submit a ticket:
    https://github.com/CocoaPods/CocoaPods/blob/master/CONTRIBUTING.md

    Don't forget to anonymize any private data!

    Looking for related issues on cocoapods/cocoapods...
    Found no similar issues. To create a new issue, please visit:
    https://github.com/cocoapods/cocoapods/issues/new

@darshankawar you mention issue also raise by me. 😢. btw I used old flutter version for that project.
flutterold --version
Flutter 1.22.6 • channel unknown • unknown source
Framework • revision 9b2d32b605 (9 weeks ago) • 2021-01-22 14:36:39 -0800
Engine • revision 2f0af37152
Tools • Dart 2.10.5
flutter --version
Flutter 2.0.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 4d7946a68d (8 days ago) • 2021-03-18 17:24:33 -0700
Engine • revision 3459eb2436
Tools • Dart 2.12.2

@bhanuka96
Actually that's my bad. I should've asked your first about flutter doctor -v. Try upgrading to latest and see if issue still persists or not.

I used 1.22.6 flutter SDK for this project. but FLUTTER_ROOT had 2.0 flutter SDK path in Generated.xcconfig. So, I renamed my flutter SDK folder. Now It's working


Add ACTIONS_ALLOW_UNSECURE_COMMANDS env variable

Workaround for unsecure commands.

Link to the workaround: https://github.com/cake-contrib/Cake.Recipe/issues/724


to test CI with features File Rest Parity and Identity SAS

Can one of the admins verify this patch?

the other pull request is rebased against the most recent changes, so this pr is not necessary


Add [your name] Markdown

Project Request

Proejct Request to Add [your name] markdown file and route

Field
Description

Name
Akshaya Krishna M

Email
<EMAIL_ADDRESS>

Github
AK-4-0-0-2

What do you what to contribute to:

[ ] HackFest GDSC Contributor
[ ] Hacktober Fest Contributor

please add your name to the issue title


Introduce custom markers to skip tests based on version

Try to use custom markers and special handling to skip tests that aren't
relevant to specific 3scale version.
Builtin skipif mark is better as there is no new code and no new
behavior, however... Having two imports (that must be ignored in checks)
and repeating still same conditions is pretty inconvenient. Furthermore
custom marks create standardized behavior that doesn't allow "creative"
conditions.

a thought to record... Question is whether until_version & after_version would be more handy

Closing for now, this was just a brainstorming kickoff how these markers should look like. (require|before)_version looks right approach (and due to easier use, code reduction and elimination of exceptions also better than builtin skipif). However the effort to rewrite all (and avoid merge conflicts) or introduce different style for newer tests isn't worth at this moment


Outlook Remove custom response header details

Removes details about the custom response header as there is a product issue that needs to be addressed.

Docs Build status updates of commit 7bec591:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/use-sso-in-event-based-activation.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8092d2c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/use-sso-in-event-based-activation.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


MainMenu: Fix layout to prevent vertical squishing of widgets.

Stylistic choices in a pull request are a bit spicy, but i'll allow it.


ADF Web copy connector

Added Web linked service/dataset/copy source.
Not bumping up nugget version as we still have one or two features need to be shipped in this sdk.

Hi @yitao-zhang, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (yitzhang). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@yitao-zhang Is this PR ready to merge?

Hi Mark,
Yes, it's ready to be merged. I didn't send the email waiting for the merge build to turn green and now it does :)
Thanks,
Yitao

@markcowl I'm bumping up the our nuget version and will release to Nuget.org


BAU-Display-Google-Apply-Pay-In-Services

This PR surfaces to the user whether a service has Apple Pay or Google Pay enabled at /gateway_accounts/:id.

Closes https://github.com/alphagov/pay-toolbox/issues/219


libvideo_decoder.so: undefined symbol: av_frame_unref

I am getting the following error when I try to load video using video_decoder.
-> % qlua test-frame.lua -v 1DCnIad1Y0w.mp4
Unable to connect X11 server (continuing with -nographics)
qlua: error loading module 'libvideo_decoder' from file './libvideo_decoder.so':
./libvideo_decoder.so: undefined symbol: av_frame_unref
stack traceback:
[C]: at 0x7fc4456649c0
[C]: at 0x7fc445439bd0
[C]: in function 'require'
What could be the issue? could you please help?

If you are getting this error, it means that you are making it with make NEWFFMPEG=1.
Try making it without NEWFFMPEG=1.


Update to Swift 5.0

Summary
Describe the goal of this PR. Mention any related Issue numbers.
Requirements (place an x in each [ ])

[x ] I've read and understood the Contributing Guidelines and have done my best effort to follow them.

[x ] I've read and agree to the Code of Conduct.

[ ] I've written tests to cover the new code and functionality included in this PR.

No functionality was changed from this PR. The test coverage has not been affected

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

@ste57 bump! :)

Perhaps it makes sense to add support for Swift 5.1 instead of 5.0?

Now done. Sorry for the delay. https://github.com/slackhq/PanModal/releases/tag/1.2.5
Will look into 5.1 now.


Make API return error before raising error again

This change makes it so any API clients can show the same error as what happens in the terminal where you run the API. Useful for various WebUIs to display more helpful error messages to users.
As an example, setting cfg_scale to 1 would return nothing as the response body when making HTTP requests. The terminal window would print AssertionError: CFG_Scale (-C) must be >1.0 together with a stack trace though, but only useful for whoever has access to the terminal window itself.
With this change, sending a request with cfg_scale set to 1, it now returns the following response body before closing the connection:
{"event": "error",
 "message": "CFG_Scale (-C) must be >1.0",
 "type": "AssertionError"}

It still raises the exception after printing it, so everything works as before (printing the exception in the terminal too) and in the future, catches can be made further up the stack if necessary.
This is probably the first piece of Python code I've ever written, so please let me know if I did something heroically wrong, as I have no idea about Python idioms.

For sure. It's much easier for me to bring in small fixes than big ones. I'll attend to it now.


Change grace period from duration to date

Can you change the grace period from duration (i.e. 30/60 days) to date (i.e. March/April 1st)? It's easier to understand when the features will be unavailable without Teams Premium.
https://learn.microsoft.com/en-us/microsoftteams/teams-add-on-licensing/licensing-enhance-teams#are-there-current-teams-features-that-will-move-to-teams-premium

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: c100aa6e-f8a3-053f-f5c6-d3e543dea5a0
Version Independent ID: c100aa6e-f8a3-053f-f5c6-d3e543dea5a0
Content: Microsoft Teams Premium licensing - Microsoft Teams
Content Source: Teams/teams-add-on-licensing/licensing-enhance-teams.md
Service: msteams
GitHub Login: @DaniEASmith
Microsoft Alias: danismith

@shtakeda We intentionally used the language of "30-day" and "60-day" because not all Teams Premium features will be releasing at the same time. Additionally, each vertical, like GCC, GCC High, and DoD, are releasing at different times. Lastly, although we have rough estimates of when specific features will release, there are instances when a feature release may be delayed. By using specific months or dates, we would be guaranteeing that features will release at that time. This is something that we won't do in our articles.

@DaniEASmith , thanks you for your comment. I understand the reason.


[boost-build] build failure for x64-windows but boost-build:x86-windows works

Operating system
Windows
Compiler
No response
Steps to reproduce the behavior

Have vcpkg.json file as below (I think only the boost packages matter in this context but included the original file here for full context).

{
  "name": "myProject",
  "version-string": "1.0.0",
  "dependencies": [
    "openssl",
    "boost-test",
    "boost-asio",
    "boost-chrono",
    "boost-interprocess",
    "boost-regex",
    "boost-system",
    "boost-thread",
    "curl"
  ],
  "overrides": [
  ],
  "builtin-baseline": "5bb5f3923a33d862b25c18fd4514e08c74c698e1"
}

Run command  C:\vcpkg\vcpkg.exe install --triplet x64-windows --x-install-root="C:/vcpkg/installed"  | Write-Host

Without vcpkg.json, one can use vcpkg install boost-build:x64-windows in vcpkg classic mode.

Failure logs
bootstrap-x64-windows-err.log
File Not Found

bootstrap-x64-windows-out.log
Building the B2 engine..
Call_If_Exists "bin\VCVARS32.BAT"
###
### Using 'msvc' toolset.
###

C:\vcpkg\packages\boost-build_x64-windows\tools\boost-build\src\engine>"cl" /nologo /MP /MT /TP /Feb2 /wd4996 /O2 /GL /EHsc   -DNDEBUG  builtins.cpp class.cpp command.cpp compile.cpp constants.cpp cwd.cpp debug.cpp debugger.cpp execcmd.cpp execnt.cpp execunix.cpp filent.cpp filesys.cpp fileunix.cpp frames.cpp function.cpp glob.cpp hash.cpp hcache.cpp hdrmacro.cpp headers.cpp jam.cpp jamgram.cpp lists.cpp make.cpp make1.cpp md5.cpp mem.cpp modules.cpp native.cpp object.cpp option.cpp output.cpp parse.cpp pathnt.cpp pathsys.cpp pathunix.cpp regexp.cpp rules.cpp scan.cpp search.cpp jam_strings.cpp startup.cpp subst.cpp sysinfo.cpp timestamp.cpp variable.cpp w32_getreg.cpp modules/order.cpp modules/path.cpp modules/property-set.cpp modules/regex.cpp modules/sequence.cpp modules/set.cpp /link kernel32.lib advapi32.lib user32.lib
builtins.cpp
class.cpp
command.cpp
compile.cpp
constants.cpp
cwd.cpp
debug.cpp
debugger.cpp
execcmd.cpp
execnt.cpp
execunix.cpp
filent.cpp
filesys.cpp
fileunix.cpp
frames.cpp
function.cpp
glob.cpp
hash.cpp
hcache.cpp
hdrmacro.cpp
headers.cpp
jam.cpp
jamgram.cpp
lists.cpp
make.cpp
make1.cpp
md5.cpp
mem.cpp
modules.cpp
native.cpp
object.cpp
option.cpp
output.cpp
parse.cpp
pathnt.cpp
pathsys.cpp
pathunix.cpp
regexp.cpp
rules.cpp
scan.cpp
search.cpp
jam_strings.cpp
startup.cpp
subst.cpp
sysinfo.cpp
timestamp.cpp
variable.cpp
w32_getreg.cpp
order.cpp
path.cpp
property-set.cpp
regex.cpp
sequence.cpp
set.cpp
LINK : fatal error LNK1104: cannot open file 'b2.exe'

C:\vcpkg\packages\boost-build_x64-windows\tools\boost-build\src\engine>dir *.exe
 Volume in drive C is BOOTCAMP
 Volume Serial Number is 0246-9FF7

 Directory of C:\vcpkg\packages\boost-build_x64-windows\tools\boost-build\src\engine

Failed to build the B2 engine.

Console Output (only console output for classic mode is posted, as it shows same error with manifest mode):
PS C:\> vcpkg install boost-build:x64-windows --triplet x64-windows
Computing installation plan...
warning: vcpkg appears to be in a Visual Studio prompt targeting x86 but installing for x64-windows. Consider using --triplet x86-windows or --triplet x86-uwp.
The following packages will be built and installed:
    boost-build[core]:x64-windows -> 1.82.0#1
Detecting compiler hash for triplet x64-windows...
Restored 0 package(s) from C:\Users\AlinaLi\AppData\Local\vcpkg\archives in 463 us. Use --debug to see more details.
Installing 1/1 boost-build:x64-windows...
Building boost-build[core]:x64-windows...
-- Using cached boostorg-build-boost-1.82.0.tar.gz.
-- Cleaning sources at C:/vcpkg/buildtrees/boost-build/src/ost-1.82.0-e88c66a4cd.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/vcpkg/downloads/boostorg-build-boost-1.82.0.tar.gz
-- Applying patch 0002-fix-get-version.patch
-- Applying patch 0003-fix-emscripten.patch
-- Applying patch 0004-workaround-MSVC-codegen-bug-in-17.5-on-ARM64.patch
-- Using source at C:/vcpkg/buildtrees/boost-build/src/ost-1.82.0-e88c66a4cd.clean
-- Using cached boost_LICENSE_1_0.txt.
-- Using cached boost-1.82.0-boostcpp.jam.
-- Installing: C:/vcpkg/packages/boost-build_x64-windows/share/boost-build/copyright
-- Bootstrapping...
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: C:/vcpkg/packages/boost-build_x64-windows/tools/boost-build/bootstrap.bat msvc
    Working Directory: C:/vcpkg/packages/boost-build_x64-windows/tools/boost-build
    Error code: 1
    See logs for more information:
      C:\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-out.log
      C:\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-err.log

Call Stack (most recent call first):
  ports/boost-build/portfile.cmake:65 (vcpkg_execute_required_process)
  scripts/ports.cmake:147 (include)

error: building boost-build:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
    https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+boost-build
You can submit a new issue at:
    https://github.com/microsoft/vcpkg/issues/new?title=[boost-build]+Build+error&body=Copy+issue+body+from+C%3A%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

Additional context
On May-12th, the build for boost-build:x64-windows is working with boost on classic mode, but today I tried with manifest mode and started encountering issues, and after some testing I discovered it is not building on classic mode as well. I have tried deleting vcpkg and re-cloning but have the same error.

The failure is at the bootstrapping step.
vcpkg also warns for Visual Studio targeting x86, but my Visual Studio is x64
the build for  boost-build:x86-windows works without any issues.

I tried vcpkg from older branches but I now still have the same problem. It might be due to my environment change as boost-build should be building from the same source code as before, but I have no idea what it might be, any help would be appreciated, thanks.

I can't reproduce this issue in my side. I think you could repair your VS first, then clone a new vcpkg repository and install boost-build:x64-windows again.

Hi @Cheney-W , I have tried uninstalling the unused Visual Studio 2019, leaving only Visual Studio 2022. I have also repaired the Visual Studio 2022, and cloned the new vcpkg, but the error persists.

@Cheney-W  The version of Visual Studio I was using was 17.6, and I also tried 17.6.1, and both had the same error as above. My co-worker mentioned that VS 17.5.5 worked for him, so I used that VS version instead, and now I can build vcpkg boost-build. I believe you might be able to reproduce the issue with the newest version of Visual Studio (17.6.1). I'm not sure if the error is from vcpkg, boost, or Visual Studio, although it does feel like a Visual Studio problem.

I'm sorry, but I still couldn't reproduce this issue. I was previously using VS2022 17.5.5, and now I have upgraded to VS2022 17.6.1. Then I re-cloned vcpkg and installed xx, and I was able to install it successfully.
Additionally, what's the results when you try the following steps:
1. Open x64 Native Tools Command Prompt for VS 2022
2. Pushd C:\vcpkg\packages\boost-build_x64-windows\tools\boost-build
3. Run bootstrap.bat

No worries. I actually never used x64 Native Tools Command Prompt for VS 2022 when installing vcpkg packages, and I only used PowerShell 7 or DeveloperShell for VS 2022, that might be the cause of the errors... I'll try when I have time, for now I'll use VS 17.5.5. In the main time I have some questions:

Since vcpkg is included in VS 2022 Ver 17.6, did you encounter any conflicts when re-cloning vcpkg?
Is x64 Native Tools Command Prompt for VS 2022 the recommended tool for running vcpkg?

Thanks for your reply!

Since vcpkg is included in VS 2022 Ver 17.6, did you encounter any conflicts when re-cloning and using vcpkg?

In general, conflicts are not expected to occur. The typical approach we use for vcpkg is to clone a vcpkg repository from GitHub to a local directory, such as E:\vcpkg. The files in this vcpkg folder are mostly identical to the ones on GitHub. Then, we open a regular PowerShell window in this folder and execute vcpkg-related commands.
The vcpkg that comes with 17.6 is installed in the ${VCINSTALLDIR}\vcpkg directory and does not require running bootstrap.bat. It already includes a fixed version of vcpkg.exe, which is automatically recognized only when you open Developer PowerShell for VS 2022. It won't be recognized in a regular PowerShell window.
When I mentioned re-cloning a vcpkg, I was referring to the general usage approach, where the installation commands are executed within this vcpkg folder. It is unrelated to the vcpkg installed through Visual Studio.

2. Is x64 Native Tools Command Prompt for VS 2022 the recommended tool for running vcpkg?

No, that's not the case.
After executing the vcpkg install command, vcpkg.exe runs the appropriate vcvarsall.bat script based on the triplet. Since you installed the x64-windows triplet, it means that the compilation environment uses vcvarsall_bat amd64, which is the same as the one used by the x64 Native Tools Command Prompt for VS 2022. So, I suggest that you use that command prompt for testing.

3. Which Windows platform are you using? Mine is Windows 10 on Intel mac using Windows bootcamp.

Mine:

There are currently some issues with the vcpkg installed through the VS Installer. Please refer to: https://github.com/microsoft/vcpkg/issues/31565.

#31565 is a different error.
Here:

    See logs for more information:
      C:\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-out.log
      C:\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-err.log

Nobody interested in these files?

@dg0yt, the user had put the content of two logs to issue report.
Failures:
LINK : fatal error LNK1104: cannot open file 'b2.exe'
@alinaliBQ. could you help maually check if b2 could be generated successfully? may be deleted by anti-software?

Open x64 native Tools command:
pushd C:\vcpkg\packages\boost-build_x64-windows\tools\boost-build\src\engine
Execute the following command and see if b2.exe generated.

cl /nologo /MP /MT /TP /Feb2 /wd4996 /O2 /GL /EHsc   -DNDEBUG  builtins.cpp class.cpp command.cpp compile.cpp constants.cpp cwd.cpp debug.cpp debugger.cpp execcmd.cpp execnt.cpp execunix.cpp filent.cpp filesys.cpp fileunix.cpp frames.cpp function.cpp glob.cpp hash.cpp hcache.cpp hdrmacro.cpp headers.cpp jam.cpp jamgram.cpp lists.cpp make.cpp make1.cpp md5.cpp mem.cpp modules.cpp native.cpp object.cpp option.cpp output.cpp parse.cpp pathnt.cpp pathsys.cpp pathunix.cpp regexp.cpp rules.cpp scan.cpp search.cpp jam_strings.cpp startup.cpp subst.cpp sysinfo.cpp timestamp.cpp variable.cpp w32_getreg.cpp modules/order.cpp modules/path.cpp modules/property-set.cpp modules/regex.cpp modules/sequence.cpp modules/set.cpp /link kernel32.lib advapi32.lib user32.lib

@PhoebeHui Oh my, you're correct. I just checked the anti-malware and indeed the b2 files were deleted by it.
With VS 17.6, I remember when building b2 with fresh vcpkg clone with regular Power Shell, the logs would say the build is successful but the b2 file has access denied error, and when I run the vcpkg install as administrator for the second time, the access denied error is gone, and instead we're back to the same error I originally posted. I previously thought the access denied error was due to me not running Power Shell as administrator, but it is very likely anti-malware related. However, it is very strange that I'm not encountering this problem with VS 17.5.5, and the anti-malware is only deleting b2 with VS 17.6, it might be due to the anti-malware settings or something... I'll check with IT for this one.

@alinaliBQ, it might be due to the anti-malware settings, thanks for your response!


Feat: add Event doubleClick and contextMenu

👀 PR includes

✨ Feature

[x] New feature

🎨 Enhance

[ ] Code style optimization
[ ] Refactoring
[ ] Change the UI
[ ] Improve performance.
[ ] Type optimization

🐛 Bugfix

[ ] Bug fix issue #0

🔧 Chore

[ ] Test case
[ ] Docs / demos update
[ ] CI / workflow
[ ] Other

📝 Description
add Event:

doubleClick
contextMenu

🖼 Screenshot

Before
After

❌
✅

🔗 Related issue link

增加contextMenu是为了解决什么场景？


fix worldsave when backup files are present

When backup files from other tools are present in the region folder
Minutor could hang infinitely while trying to calculate the world
border. This commit completely rewrites the Chunk number from region
file detection code.
This PullRequest closes issue #60

@mrkite : I know that this change is not necessary for normal operation, but it makes Minutor more robust to leftovers from other tools.
Just write a short comment if I should change something or you dislike parts of my changes.

Hi @mrkite are you still doing Minecraft related stuff?
I personally reduced it much in the last weeks... but I still use Minutor.

I'm not playing Minecraft anymore, but every few months I make sure Minutor is still working.  Sorry about taking so long to merge this.


Please document correct usage of accessibilityRole "link"

Description
Here's the current documentation for accessibilityRole="link":

link Used when the element should be treated as a link.

This... could be more helpful. It's arguably a tautology: it says the link role should be used in those cases where the link role should be used.
There are many examples (some given below) of inconsistent and sometimes contradictory ways this has been interpreted.
What is the problem?
This is a problem because people fill in their own common-sense opinion on how link roles should be used (possibly  influenced by non-equivalent experience of links on websites).
For example, I've encountered three different interpretations on how the link role should be used, all from seemingly authoritative sources:

Navigation between screens: The widely used react-navigation project has utilities like useLinkProps that apply accessiblityRole="link" to any element that navigates between screens - every element using these utilities that would do internal routing in a  web context will get the "link" role in Android and iOS.
All interactive inline text: The react-native-accessibility-engine project has a test "link-role-required" that requires any Text element with an onPress handler to have the role "link", regardless of what the press does. This appears to be interpreting "link" by presentation (interactive inline text) rather than the nature of the action.
Opening URLs in device browser: App accessibility consultants I've worked with in the past have advised that "link" should be used specifically for interactive elements that cause the app open and focus a web browser, and that "button" should be used for in-app navigation (regardless of element type). Here's an example of an accessibility consultancy giving this advice in the context of iOS:

Links open a URL in an external browser.  This the important distinction between buttons.  Only apply the trait of link when the users interaction with the control will take them out of your application and into Safari.

How can we address it?
There is one right answer as to how React Native's link accessibilityRole is intended to be used, based on the appropriate iOS and Android guidance for the underlying properties and traits that React Native applies internally to the native Android and iOS elements it controls.
The React Native accessibility docs should state it clearly. For example (assuming this one is correct):

link Interactive elements that load a web page in a device browser, switching focus away from this app

Why is it important?
There's clearly already diverging interpretations of how this role should be used, and it's a very commonly used role, so there is almost certainly already a lot of inconsistency on when elements are described as a "Link" in React Native apps in production.
Who needs this?
Ideally all React Native developers should be applying this accessibilityRole consistently and correctly.
When should this happen (use version numbers if needed)?
As soon as there's a clear consensus on what the correct usage is.

No it's not fixed, stay open please.

No it's not fixed, stay open please.


FI from CoreRT master

Based on Michal's suggestion I have attempted to FI the most recent CoreRT master bits into the R2R branch. This is my first stab at GitHub branch integration so please double-check I haven't messed it up.
Thanks
Tomas

@dotnet-bot Test Windows_NT and OSX10.12 please

He did but thanks for pointing it out anyway. Sadly it looks like the tests are still stuck.

@dotnet-bot Test Windows_NT and OSX10.12 please

@dotnet-bot Test this please


feat(gateway): support overriding Config's intents & token

Reusing the TLS context can result in dramatically reduced memory usage when running multiple shards, unfortunately it requires cloning an existing Config (which can be quite awkward). This PR allows reusing the TLS context when running a different set of intents per shard and/or running multple set of shards (multiple bots).
In the future, it would be nice to figure out an API where the TLS context can be shared not only inside twilight-gateway but also with twilight-http and third-party users' TLS clients.

Can you elaborate on the intended use case? I'm not sure I'm seeing it here

Can you elaborate on the intended use case? I'm not sure I'm seeing it here

To share the TLS context with all shards of a multi-bot gateway microservice event queue producer. Could also be useful for https://github.com/Gelbpunkt/gateway-proxy

This feature request is too niche to be worthwile the cognitive overhead of the methods. A better, general, dependency injection API that covers twilight-http, and users' own HTTP client should be created instead to support this feature.


Fix #2650: Support Customization with CADL input in DPG

@annelo-msft, i would like to confirm with you whether all those customization cases should be supported in CADL+DPG

Sidecar has to provide language-specific customizations, and I'm very skeptical about having a good way of customizing entities that exist only in C# code (multiple constructors, type conversions, etc.)

@annelo-msft, i would like to confirm with you whether all those customization cases should be supported in CADL+DPG.

@lirenhe, we have not closed on the customization story for DPG+CADL yet.  Closing on this story is not required for August MVP.  It is up to you whether you want to merge this PR or not, but if it's required for anything in the August MVP, then we are doing something incorrectly.

if it's required for anything in the August MVP, then we are doing something incorrectly.

It is required to workaround https://github.com/Azure/cadl-ranch/pull/49, which is a blocker for https://github.com/Azure/autorest.csharp/issues/2550.

It is required to workaround https://github.com/Azure/cadl-ranch/pull/49, which is a blocker for https://github.com/Azure/autorest.csharp/issues/2550.

That issue is for parity with DPG 1.0.  DPG 1.0 did not generate models, therefore we shouldn't need model customization to achieve parity with DPG 1.0.  So, something is incorrect.

That issue is for parity with DPG 1.0

Well, https://github.com/Azure/autorest.csharp/issues/2550 is not about parity in terms of API surface, it is about parity in terms of resiliency, meaning that "DPG 2.0 handles client generation from CADL when upgraded from v1 to v2 as good as DPG 1.0 handles client generation from swagger when upgraded from v1 to v2".

I disagree, but at the end of the day it doesn't matter what I think - please work with @lmazuel to clarify his intention for this test case and what the requirements for DGP 1.0 parity are.  Thanks!

Independent of whether or not this is needed for DPG 1.0 parity, I just chatted with @KrzysztofCwalina, and he would like to keep these customizations available for use in .NET SDKs.  We can slowly shift the customization balance to Cadl over time with the shift left effort, but this effort should not block DPG 2.0.  @lmazuel, @tg-msft, FYI.

This is high interest technical debt.  If we're going to keep it, I'd propose we never let anything GA using it (possibly adding analyzers to warn about it) and only allow it for short term Preview workarounds until the Cadl customization story adds any missing features.

I would be fine with having a system in place where all such customizations need to be approved explicitly. I don't agree with banning such customizations in GA libraries altogether. The main mission of our team is to ship great libraries and we need to have tools that allow arbitrary customizations.


Implement terminated event

Good opportunity to see if #52 fixes #42, as this test seems to fail reliably on github actions.
Tests pass locally.

Nvm this was actually just an issue with the close aseprite tests.


Add derive support for simple enums.

Only simple C-style enums are accepted.
Enums with fields, generics or where clauses are rejected.
The #[serde(rename)] attribute is respected.
Closes #12 .
As requested, the https://github.com/theduke/miniserde/tree/enum-benchmarks branch contains a little benchmark setup in the mini-bench directory, which is compiling 500 structs with 500 enums contained in those structs , and serializes them.
cd mini-bench; time $(cargo clean && cargo build --release --features=mini) && time $(cargo clean && cargo build --release --features=full)
The result is pretty conclusive. ;)
Miniserde: 31s
serde: 2m04s

Published in 0.1.12.


First pass on logo

Hey there, this a first rough pass on the logo. I put everything inside the .logos directory mostly because that's going to likely have to move elsewhere (webhost or dropbox or something) just so people pulling this module down aren't pulling down logos as well.
Let me know what you think, this was a pretty fast process.

Looks nice! Thank you, @qbunt. I'm going to host the logo on my personal website just so that it doesn't have to get download when people pull it as you said.


Unable to clone the repo ( Ss shared below)

while git clone repo to my ubuntu 18.04 using terminal

Please google this. There's nothing I can do about this.


WSL error 0x8007023e

CMD version
Microsoft Windows [Version 10.0.22621.1413]
Steps required to reproduce
wsl ---install
Copy of the terminal input
Ubuntu is already installed.
Launching Ubuntu...
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x8007023e
Error: 0x8007023e {Application Error}
The exception s (0x
Press any key to continue...

Expected behavior
Installing Ubuntu, and creating an account in the Terminal.
Strace output
Can't run Strace, as Ubuntu is not working.
Logs
WslLogs-2023-03-15_17-41-39.zip

I forgot to upload the image for it.
So here it is.

@OneBlue There we go!
followed the steps, this time :d!

Thanks @mikolertesx. Did you find any crash dumps while you were doing this ?

Thanks @mikolertesx. Did you find any crash dumps while you were doing this ?

If you mean the last section of the Git document, no, there are no Crash dumps, even after the regedit changes, and making wsl crash again!.
btw, what's happening is that it crashes whenever I try to install the distribution, so maybe that's before the crashes are even ready to be dumped 😭

Sending another message to keep this from getting closed 🗡

Thank you @mikolertesx. To root cause this we'd need to take a TDD trace of the service, so let's try that.
I just wrote instructions on how to do that, can you please follow the '12) Collect wslservice time travel debugging traces'
 section and share the result trace while reproducing the issue ?

Well, this is going to be a tough nut to crack, isn't it?

I'm getting a different error, ever since I went back to wsl 1, and upgraded to wsl 2, the error being "Error code: Wsl/Service/CreateVm/ConfigureNetworking/0x8007023e".

Comment to avoid this from being deleted.

Thanks @mikolertesx. Looking at the error message you got, it looks like the issue is probably somewhere in the host networking service.
Can you collect traces again when you get this error so we can have a deeper look ?

@OneBlue I can't use WinDBG, it doesn't stop recording so all recordings become corrupted.

Sorry for the misunderstanding, by traces, I meant /logs

WslLogs-2023-03-30_17-32-08.zip
I:
1.- Ran the file.
2.- Reproduced the issue by trying to upgrade to WSL version 2.
3.- Pressed enter.
4.- Sent this file to you through Github.
Here is the file, my helpful friend! :D.
reproduced the issue, then click enter for it to finish

Thanks for reporting this @mikolertesx.
Looking at the logs, this is an issue in HNS that should be fixed by now. Do you still see the error ?

@OneBlue Well, no, I couldn't fix the thing in time.
I had work to do, so I ended up reinstalling Windows 11, and I had to:

Pay for another Windows Key (Custom Built PC).
Lost access to VMWare Pro that had a 1-Machine key policy.
Let go of my Microsoft  Office 2021 Copy, which I paid and lost the serial key to.

All in all, I'm just glad no one else will have to go through the same issue.
I'm glad to hear this won't happen to the next guy xd.

Oh sorry to hear that.
Closing since the repro is gone.

Seems reasonable.
I need to look for someone to complain with xd.

For anyone dealing with this issue still ---------
I had the same issue and went through all steps listed here and here https://github.com/microsoft/WSL/issues/5508 with no changes. Right before i was going to reinstall windows i rememberd i hadn't installed Restoro on this computer yet. It works by scanning and replacing courrupted/deleted files in windows. So quick install, run and restart with Restoro and everthing is back to normal for me. Although i did use the paid version the free version should be able to do the same thing for anyone interested. I'm not affiliated with Restoro in anyway just think it could help some of the people dealing with this issue. It was 3 days of beating my head agaisnt the wall before this so i understand everyones pain! Good Luck! :)


Restructure documentation

Addressing one of the action items in #1125.
Suggestions welcome!

This is how the index looks like now

Also a couple of files that are not linked:
/Users/nube/ESMValTool/doc/sphinx/source/diag_scripts/index.rst: WARNING: document isn't included in any toctree
/Users/nube/ESMValTool/doc/sphinx/source/plot_scripts/index.rst: WARNING: document isn't included in any toctree

Also
../source/getting_started/git_repository.inc:148: WARNING: undefined label: writing (if the link has no caption the label must precede a section header)
../source/getting_started/git_repository.inc:148: WARNING: undefined label: tab_checklist (if the link has no caption the label must precede a section header)
../source/getting_started/git_repository.inc:166: WARNING: undefined label: std_diag (if the link has no caption the label must precede a section header)
../source/getting_started/git_repository.inc:167: WARNING: undefined label: std_recipe (if the link has no caption the label must precede a section header)
../source/getting_started/git_repository.inc:167: WARNING: undefined label: std_diag (if the link has no caption the label must precede a section header)

but this file will need to be thoroughly updated after we split, so it is not that important

another warning I totally missed:
doc/sphinx/source/getting_started/running.inc:13: WARNING: Unknown target name: "user config file".

but funny enough I am not getting @jvegasbsc 's warnings

I fixed the warnings (thanks for reporting!), except for git_repository.inc (these have to be fixed as the content is revised).
Merging now so we can start adding/editing the text.


Fix AlreadyLoggedIn isn't raised even if session is created

According to docstrings, AlreadyLoggedIn should be raised when session is created. But there's missing raise keyword in the code. This pull request fixes that.

Hello! I didn't even notice this error. Thanks for finding and fixing it.


Checkboxes can't be indented nor created with "- [ ]"

Identified three issues with the checkboxes.

Creating checkboxes similar to other markdown editors (e.g. GitHub, Obsidian, et cetera) with "- [ ]" does not work. If there is another way to create these checkboxes without the toolbar; I am unable to find it documented anywhere. Clashes with markdown UX expectations.
Unable to indent checkboxes with tab. When hovering over a checkbox line, tabbing seems to just change focus. Clashes with markdown UX expectations.
Pressing enter on an empty checkbox does not make it disappear, as is standard for markdown editors. Clashes with markdown UX expectations.

Reproduction recorded:

Please track this PR for Markdown support: https://github.com/superlistapp/super_editor/pull/1360
For the other two issues, can you please file separate tickets so that we can address individually? You can edit this ticket to become one of those two tickets.
When describing expectations, please be precise about what's happening now vs what exactly you think should happen.

I'm going to close this ticket due to inactivity. If you have specific, individual issues that you'd like for us to address, please file one ticket per issue, and please fully describe the actual vs desired behavior.


Automator: update<EMAIL_ADDRESS>dependency in<EMAIL_ADDRESS>

Generated by Automator - 2023-06-28T16:28:04+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio_release-1.17
40c2bd61997ff30c42dd6c08ac113fc4f20fd2cd
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-multicluster

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio_release-1.17
40c2bd61997ff30c42dd6c08ac113fc4f20fd2cd
link
unknown
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot


Update Apache Ant to latest version to avoid this CVE: https://nvd.nist.gov/vuln/detail/cve-2020-1945

Issue type
Other
Problem description
Update Apache Ant to latest version to avoid this CVE:
https://nvd.nist.gov/vuln/detail/cve-2020-1945
Context (optional)
No response

Never mind, looks like 1.10.13 is recent enough to avoid cve-2020-1945
https://github.com/gradle/gradle/blob/d8cad90101799383c990e394184f35a230bb544e/subprojects/distributions-dependencies/build.gradle.kts#L18

Please follow our security policy in the future. Instead of creating an issue, please submit all security bug reports to [security@gradle.com](mailto:security@gradle.com).


fix: universal packaging for node and browser

Webpack upgrade broke universal packaging. See https://github.com/webpack/webpack/issues/6525 and https://github.com/webpack/webpack/issues/6522
As current workaround I've added globalObject: 'this' to webpack.config
fixes #65

That's what is in the output of 4.0.5 version which seems to work.
I've done a quick check by running node -p -e "require('./dist/mobx-react-router.js')"
It fails for case when no globalObject is specified and works when globalObject: 'this'


Capabilites of DesktopWebDriverRequest not clonable

Description
The SessionContext clones the complete WebDriverRequest object after instantiation. In case of existing capabilities the following exception occues because the Capabililies object is not clonable.
org.apache.commons.lang3.SerializationException: IOException while reading or closing cloned object data
I've added a special handling of cloning capabilites in AbstractWebDriverRequest
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@gogro @martingrossmann I simplified cloning as intented to be implemted and by not using serialization anymore.


Segmentation faults when building using apple clang 11.0.3

When trying to build with latest clang 11.0.3 I get several segmentation faults and even out of memory errors:
clang: /usr/bin/clang
llvm-ar: /usr/bin/ar
Building with /Users/thilo/Documents/coseda/cppcoro/config.cake - Variant(release='optimised', platform='darwin', architecture='x64', compiler='clang')
Building with /Users/thilo/Documents/coseda/cppcoro/config.cake - Variant(release='debug', platform='darwin', architecture='x64', compiler='clang')
Compiling test/recursive_generator_tests.cpp
Compiling test/async_generator_tests.cpp
Compiling test/recursive_generator_tests.cpp
test/recursive_generator_tests.cpp:156:2: warning: control reaches end of non-void lambda [-Wreturn-type]
        };
        ^
test/recursive_generator_tests.cpp:160:11: note: in instantiation of function template specialization '_DOCTEST_ANON_FUNC_16()::(anonymous class)::operator()<(lambda at test/recursive_generator_tests.cpp:148:11)>' requested here
                return f(n, f);
                        ^
test/recursive_generator_tests.cpp:237:2: warning: control may reach end of non-void lambda [-Wreturn-type]
        };
        ^
test/recursive_generator_tests.cpp:239:14: note: in instantiation of function template specialization '_DOCTEST_ANON_FUNC_20()::(anonymous class)::operator()<(lambda at test/recursive_generator_tests.cpp:219:11) &>' requested here
        auto gen = f(0, f);
                    ^
test/recursive_generator_tests.cpp:297:2: warning: control may reach end of non-void lambda [-Wreturn-type]
        };
        ^
test/recursive_generator_tests.cpp:299:14: note: in instantiation of function template specialization '_DOCTEST_ANON_FUNC_22()::(anonymous class)::operator()<(lambda at test/recursive_generator_tests.cpp:252:11) &>' requested here
        auto gen = f(1, f);
                    ^
clang: error: unable to execute command: Segmentation fault: 11
clang: error: clang frontend command failed due to signal (use -v to see invocation)
Apple clang version 11.0.3 (clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin19.5.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
clang: note: diagnostic msg: PLEASE submit a bug report to http://developer.apple.com/bugreporter/ and include the crash backtrace, preprocessed source, and associated run script.
clang: note: diagnostic msg:
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg: /Users/thilo/Documents/coseda/cppcoro/recursive_generator_tests-ca7e05.cpp
clang: note: diagnostic msg: /Users/thilo/Documents/coseda/cppcoro/recursive_generator_tests-ca7e05.sh
clang: note: diagnostic msg: Crash backtrace is located in
clang: note: diagnostic msg: /Users/thilo/Library/Logs/DiagnosticReports/clang_<YYYY-MM-DD-HHMMSS>_<hostname>.crash
clang: note: diagnostic msg: (choose the .crash file that corresponds to your crash)
clang: note: diagnostic msg:

********************
/usr/bin/clang: failed with exit code 254
test/recursive_generator_tests.cpp:156:2: warning: control reaches end of non-void lambda [-Wreturn-type]
        };
        ^
test/recursive_generator_tests.cpp:160:11: note: in instantiation of function template specialization '_DOCTEST_ANON_FUNC_16()::(anonymous class)::operator()<(lambda at test/recursive_generator_tests.cpp:148:11)>' requested here
                return f(n, f);
                        ^
test/recursive_generator_tests.cpp:237:2: warning: control may reach end of non-void lambda [-Wreturn-type]
        };
        ^
test/recursive_generator_tests.cpp:239:14: note: in instantiation of function template specialization '_DOCTEST_ANON_FUNC_20()::(anonymous class)::operator()<(lambda at test/recursive_generator_tests.cpp:219:11) &>' requested here
        auto gen = f(0, f);
                    ^
test/recursive_generator_tests.cpp:297:2: warning: control may reach end of non-void lambda [-Wreturn-type]
        };
        ^
test/recursive_generator_tests.cpp:299:14: note: in instantiation of function template specialization '_DOCTEST_ANON_FUNC_22()::(anonymous class)::operator()<(lambda at test/recursive_generator_tests.cpp:252:11) &>' requested here
        auto gen = f(1, f);
                    ^
clang: error: unable to execute command: Segmentation fault: 11
clang: error: clang frontend command failed due to signal (use -v to see invocation)
Apple clang version 11.0.3 (clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin19.5.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin
clang: note: diagnostic msg: PLEASE submit a bug report to http://developer.apple.com/bugreporter/ and include the crash backtrace, preprocessed source, and associated run script.
clang: note: diagnostic msg:
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg: /Users/thilo/Documents/coseda/cppcoro/recursive_generator_tests-2a2f2d.cpp
clang: note: diagnostic msg: /Users/thilo/Documents/coseda/cppcoro/recursive_generator_tests-2a2f2d.sh
clang: note: diagnostic msg: Crash backtrace is located in
clang: note: diagnostic msg: /Users/thilo/Library/Logs/DiagnosticReports/clang_<YYYY-MM-DD-HHMMSS>_<hostname>.crash
clang: note: diagnostic msg: (choose the .crash file that corresponds to your crash)
clang: note: diagnostic msg:

********************
/usr/bin/clang: failed with exit code 254
^C/usr/bin/clang: failed with exit code -2
Build failed with 3 errors.
The following targets failed to build:
- build/darwin_x64_clang11.0.3_debug/test/obj/recursive_generator_tests.o
- build/darwin_x64_clang11.0.3_optimised/test/obj/recursive_generator_tests.o
- build/darwin_x64_clang11.0.3_optimised/test/obj/async_generator_tests.o
```

This was a known issue with Clang 9.0, on which I believe AppleClang 11 was based.
It has been fixed in upstream Clang 10 and so will hopefully be incorporated into the next release of AppleClang.
See https://bugs.llvm.org/show_bug.cgi?id=43492


Added Scroll to Top Button

PR Description 📜
The Button's CSS matches with that of the whole webpage
Clicking the button smoothly scrolls the user back to the top of the page.
Fixes https://github.com/ChromeGaming/Physi-c-Tech/issues/239

Mark the task you have completed ✅

[✅ ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[ ✅] I have performed a self-review of my own code or work.
[✅ ] My changes generates no new warnings.
[✅ ] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[ ✅] I have added screenshot for review.

## Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Hey @thevirengarg!
Please look into this pull request
Thank you


Make html files more readable

Html files are not readable, as their formatting is not ideal. Please reformat it to make it more readable:
http://stackoverflow.com/questions/29973357/how-do-you-format-code-in-visual-studio-code-vscode

There are still some not needed empty lines in Gallery.html file


Question about rendering results.

Thank you very much for your willingness to openly share the source code!
However, the rendering results i got were not like what you showed in paper. I saved the rendering rgb generated from
https://github.com/Lab-of-AI-and-Robotics/GS_ICP_SLAM/blob/bb6398fd1e95b78b4197400203934989b1517cff/mp_Mapper.py#L383. The rendering results contain many holes, and the average PSNR result only has 26.47 dB (room0).
Here is a example (frame_890) of the results:

The final metric results are as follows:

Hello!
Sorry for the late response.
GS-ICP SLAM is implemented in multiprocess manner, and optimization of the map is performed during tracking process.
So the number of map optimization iteration is not constant, depending on the performance of the GPU.
Therefore, the map quality can vary depending on the performance of the GPU.
The results reported in the paper are from experiments on the RTX 4090.
If your environment is different from ours, your map quality might different.