Update client-side-experiments-config.json

This pull requested modified the client-side experiments config file but it does not pass schema validation.
Please send a follow-up pull request to fix this file using the correct schema.

This pull requested modified the client-side experiments config file but it does not pass schema validation.
Please send a follow-up pull request to fix this file using the correct schema.

This pull requested modified the client-side experiments config file but it does not pass schema validation.
Please send a follow-up pull request to fix this file using the correct schema.

This pull requested modified the client-side experiments config file but it does not pass schema validation.
Please send a follow-up pull request to fix this file using the correct schema.

This pull requested modified the client-side experiments config file but it does not pass schema validation.
Please send a follow-up pull request to fix this file using the correct schema.


Unstable UI

Once you run it in VS ,the UI is really messed up. Please try to fix it,if you can

The customers are still waiting for the fix. When is it going to be fixed?


Support idp cert multi with string keys

I ran into issues while attempting to integrate with an ADFS IdP.
The issue was that when settings are initialized with a hash where keys are not symbols (ex. when loaded from a json file), Settings#get_idp_cert_multi is not able to retrieve the certificates.
It had been reported in this issue before: https://github.com/onelogin/ruby-saml/issues/409.
This PR proposes to fallback to string keys if symbol keys are not defined.

Coverage decreased (-0.004%) to 96.791% when pulling 5ec843ffdb069261633199f4717bedb941e7a229 on alxckn:support_idp_cert_multi_with_string_keys into 61d09d0b8773b2a95f65dc104f3ed0d07d26ac64 on onelogin:master.

👍 This looks good to merge

@alxckn this looks ok, however, I wonder if we should coerce the settings keys to be symbols when reading in the data.
@pitbulk would suggest to merge this as-is.


Two page spread doesn't work in fullscreen presentation mode

When using two-page spreads, and then changing to fullscreen presentation mode, it changes back to single pages for the fullscreen mode instead of showing the desired two-page spreads.
I have seen issue #11708, and the response is a claim that presentation mode is meant to be very simple and not have any extra functionality. If this is truly the case it is a poor choice. I think it is more likely that it just hasn't been implemented yet, and so I'm making a new issue here. For presentation mode, anyone using this software would expect to see the same pdf presented as before, but filling the screen, and without the toolbar at the top and without any of the browser chrome surrounding. The answer for issue #11708 says that you should just use the browser's full-screen mode, but this doesn't to my knowledge allow one to show the pdf full-screen without any toolbars visible. If this is more than a bug, and more of a feature request, then please consider it a feature request. Thanks!
Configuration:

Web browser and its version: Safari 15.1 or Firefox 98.0.1
Operating system and its version: macOS Monterey 12.0.1
PDF.js version: Any
Is a browser extension: No

Steps to reproduce the problem:

Open any multi-page pdf
Click the double arrow dropdown on the right side of the toolbar
Choose "odd spreads" or choose "even spreads". A view will be shown with two pages side by side.
Click "Switch to Presentation Mode" on the toolbar.
You are switched to fullscreen, but with just one page instead of a two-page spread.

What is the expected behavior? (add screenshot)
When clicking "presentation mode" you should still see the same view of the pdf as you were before entering presentation mode.
What went wrong? (add screenshot)
As above, only one page is shown in presentation mode, regardless of two page spread settings
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension): n/a.

The problem seems to appear again. It reproduces for me on Firefox 110.0 (64-bit), build id<PHONE_NUMBER>1806, Intel Mac OS Monterey 12.6.2

Same here, Windows 10, Firefox 112.0.2 (64-bit)

Also for me, Firefox 113.0.1 64 bit, M1 Pro MacOS


Workflow Java SDK Code Sample

Moving existing tracking issue for the java code sample into the quickstarts repo.
What content needs to be created or modified?
We need to create java code sample for the workflow Java SDK QuickStart. This issue defines the criteria needed in a java code sample. There is a separate issue for the QuickStart itself.
Main workflow java sdk docs issue here: #3567
Describe the solution you'd like
We'll need a java sample that exactly mimics the same structure as the existing workflow samples for .NET and python.
I'll reference the .NET sample for my examples below:

The java program.cs file should have the exact same steps as the .NET quickstart program.cs file. Even down to the number of items purchased, and the item chosen)
Activities, and workflows should match those in .NET quickstart. For example, for the java sdk we'd also want the same exact 4 activities, activity names, workflow etc.

Additional context
#3567
dapr/quickstarts#898
https://github.com/dapr/java-sdk/pull/880

@hhunter-ms  and @skyao I'm moving this issue into the quickstarts repo instead. @skyao could you assign this to yourself?

hi, @nyemade-uversky  I had submitted the PR of workflow quick start in java sdk and waiting for review and merge.
I will continue to prepare the content in dapr docs about dapr workflow with java sdk.

@skyao could you actually close this PR and reopen it in the quickstart repo instead? We'd like the code sample for wf to live in the same repo with the actual quickstart.

Completed


Allow AnimationPlayer To Be Put On a Separate Window

The AnimationPlayer would benefit from having more space. Can we make it occupy its own window by itself?

I think it is better to use the Q&A for questions. https://godotengine.org/qa/

It's a usability issue though in my opinion. It's way too small for anything other than very simple animation graphs.

I'm saying this because davidpgil opened about 6 issues in a row, most of which are questions (at least in their title).

I am asking these questions so they can spur issues that need resolving. Shall I change the wording and titles of my posts so they appear as suggestions or requests? I can do that. All of these issues I posted come from my post-mortem notes of a project I already completed.

Currently Godot do not support separate windows.
You can do live editing with the scene running, though.
And try to add more details to your idea, like a mockup of how it may look better since animation player may be modified on future versions, a single line does not say much.

@eon-s , yes I know Godot doesn't support this yet. This is why I am requesting it. Right now the only interface support allows reorganizing of the windows with the intention to occupy one screen. Right now, software like Adobe After Effects, Maya, etc already allows to make UI elements to be "tirn off" so their window can exist independently of the main interface window. If that isn't an obvious enough description, I can surely take the time to illustrate it with a mockup. @eon-s would you be the one implementing this in code?

No, I try to not break things around here :p
But after 3.0 the animation player may be renewed or with more options, I'm sure some ideas will be welcome by those who work on the UI part of the engine.

If someone asks for a detailed example of what this will look like I will do it. I know of the animation overhaul coming in 3.1 ... I think my suggestions would be more useful after the 3.0 release.

Closing in favor of related proposal: https://github.com/godotengine/godot-proposals/issues/28


Docs: There is no description as to the behaviour of the Match Conditions

You've listed the Match Conditions enum in the documentation, but you do not explain what the behaviour is for these conditions.
Similarly, the description is not available in the cosmosdb docs

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

ID: 0c1e5642-e4f7-202d-b3ef-871ee0ff66cb
Version Independent ID: aa8729ae-b13b-bcb7-b87b-85f956f4abf8
Content: azure.core.MatchConditions enum
Content Source: docs-ref-autogen/azure-core/azure.core.MatchConditions.yml
GitHub Login: @lmazuel
Microsoft Alias: lmazuel

@xiangyan99 can you take a look?

The exact behavior of MatchConditions may vary from service to service.
Given "cosmosdb docs" is mentioned here. I would assign this to cosmos owner.

@xiangyan99 the content is from Azure Core:

Content: azure.core.MatchConditions enum
Content Source: docs-ref-autogen/azure-core/azure.core.MatchConditions.yml

Yes. But the behavior may be different. e.g. in cosmos:
match_condition = kwargs.pop('match_condition', None)
    if match_condition == MatchConditions.IfNotModified:
        if_match = kwargs.pop('etag', None)
        if not if_match:
            raise ValueError("'match_condition' specified without 'etag'.")
    elif match_condition == MatchConditions.IfPresent:
        if_match = '*'
    elif match_condition == MatchConditions.IfModified:
        if_none_match = kwargs.pop('etag', None)
        if not if_none_match:
            raise ValueError("'match_condition' specified without 'etag'.")
    elif match_condition == MatchConditions.IfMissing:
        if_none_match = '*'
    elif match_condition is None:
        if 'etag' in kwargs:
            raise ValueError("'etag' specified without 'match_condition'.")
    else:
        raise TypeError("Invalid match condition: {}".format(match_condition))

I think it will be better to describe the behavior in the method that supports MatchCondition, your ideas?

The way I read it is the docs from Azure Core are not useful and CosmosDB doesn't even have docs.

If it helps you narrow down the issue, I started by looking at the docs for upsert-item. There it states:
etag str
An ETag value, or the wildcard character (*). Used to check if the resource has changed, and act according to the condition specified by the match_condition parameter.

match_condition MatchConditions
The match condition to use upon the etag.

Which is definitely not useful to understand which of the MatchConditions to use.
This is especially confusing as the main cosmosdb docs page on optimistic concurrency talks about if-match and if-none-match headers, which is a completely different API and behaviour (though, seeing the snippet above, this is merely a translation to those headers).

A quick look at the source file shows that this same language is used in four different methods: replace_item, upsert_item, create_item, and delete_item.
Ideally, this behaviour should be documented either in those methods, or in the MatchCondition enum. The MatchCondition that will bring about the default behaviour for each method should be specified in that method, (e.g. IfNotPresent for create_item is what I assume is the default behaviour), or what the default behaviour is when this keyword is not specified. It's difficult to work out what each option does, as it translates into headers that are then interpreted in different ways by the cosmos server, so tracing through the code doesn't get you anywhere.
Also, it's not clear from the docs (though exceptions do tell us) that the match_condition keyword is compulsory when the etag keyword is used (though not vice-versa).
Finally, an indication of what the expected behaviour is when the condition is not met would be helpful, so we know to catch the right sort of Exception and handle it.
Also, it would be helpful to indicate that you're


Print header with date and time

Hi @volkanceylan
I have added a printHeader option for print the header of each page with date and time of report

Thanks @Estrusco. Should we change it to something more clear like printDateTimeHeader etc?

Yes, of course

OK @volkanceylan I have done

@volkanceylan you can merge now?

Thanks @Estrusco , sorry i forgot about this


#24 rename package to roave/backward-compatibility-check

Fixes #24

Build failures were due to BC breaks indeed, so merging.


Reacts > How do you react?

How often do you use love reacts?
What friends' posts are you most likely to react to?
Is their a friend for whose posts you use a single react?

Hi. This seems an interesting thing to start with. I would like to work on this. Could you please assign me this issue so that I can start working on it. Thanks !

Sure!
Have a look at the data, and please share what you think you will be working upon, before starting to code.
This will save us time later.
I'm adding you as a collaborator, after which this issue can be assigned to you.

So, yeah! I had a look at the data. In the Likes part of the data, fb provides a JSON object of all my reactions on any post. For every post it shows the reaction (ie whether its a 'Like', 'wow', etc) and the timestamp and a string describing it.
eg: You liked Tony Kroos's post. :p
The challenge would be extracting names from this string as there is no fixed format of the sentence. It varies from post to post.  So, we could try to do the following things:

Show the counts of different reactions.
Show the variation of number of reactions over different time periods.
Show the names of friends whose posts we reacted to the most, or top 5. Something like that.

Any feedback would be great. And yes, I accepted the invitation for the collaborator.

Seems good for a first issue. We can increase upon this later on.


Update appveyor.yml

:white_check_mark: Build locaweb-servidores-sdk-dotnet 1.0.23 completed (commit https://github.com/guibranco/locaweb-servidores-sdk-dotnet/commit/6cb36ab896 by @guibranco)


No able to send a message to former host.

Subject: No able to send a message to former host.
Description:
After the hosting event I wanted to make a message to the host, but I'm not able to. It would be perfect, to be able to write also after the event, as there might be questions - for example if the guest forgot something.
Results:
Enable messages to hosts also after the event.
Backend version: develop-b947f0cb
Frontend version: develop-b947f0cb
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.4 Safari/605.1.15
Page: https://couchers.org/messages/request/10801
User: patnrada (12957)

This is intentional by the current request design... unless there are plans to change this in the new host request design? @aapeliv

Yes. I messaged this user on platform to tell them they can send a regular message


Missing nodeSelector or affinity options in chart

Description
We have both Graviton (ARM) and AMD (x866) nodes in our k8s clusters. The Zookeeper charts allow us to use nodeSelector to make sure Zookeeper pods only deploy to x86 nodes. This capability is missing in the Pravega Bookkeeper-Operator chart.
Importance
Blocker
Location
default values.yaml is missing the nodeSelector: {} and affinity: {} options, and the chart templates are missing the sections to add these options to the deployment.
Suggestions for an improvement
At a minimum, add the nodeSelector: {} option to the chart so it works just like the Pravega Zookeeper-Operator chart.
Reusing the values.yaml and chart template sections from the corresponding Pravega Zookeeper-Operator and Zookeeper charts should make the change simple.

In the Pravega Zookeeper-Operator, the default valuess.yaml includes a section for scheduling constraints:
'# Scheduling constraints
nodeSelector: {}
affinity: {}
tolerations: []
'# Pod annotations
annotations: {}
Which are processed in the template by templates/operator.yaml:
{{- if .Values.nodeSelector }}
nodeSelector:
{{ toYaml .Values.nodeSelector | indent 8 }}
{{- end }}
{{- if .Values.affinity }}
affinity:
{{ toYaml .Values.affinity | indent 8 }}
{{- end }}
{{- if .Values.tolerations }}
tolerations:
{{ toYaml .Values.tolerations | indent 8 }}
{{- end }}

My work around:
Cloned the operator
Added this at line 20 in templates/operator.yaml:
{{- if .Values.nodeSelector }}
nodeSelector:
{{ toYaml .Values.nodeSelector | indent 8 }}
{{- end }}
{{- if .Values.affinity }}
affinity:
{{ toYaml .Values.affinity | indent 8 }}
{{- end }}
{{- if .Values.tolerations }}
tolerations:
{{ toYaml .Values.tolerations | indent 8 }}
{{- end }}
Then added this to the end of values.yaml when installing
nodeSelector:
x86: "true"
This assigns bookkeeper-operator to deploy only to nodes that have the Kubernetes label "x86" set to "true".


Update SKUs for MySQL/Postgres & validate (limit) the database size parameter value

Azure MySQL/Postgres require some specific database sizes (e.g., 51200, 102400, 128000, ...), but our current template accepts arbitrary numeric values, which are rejected only after the deployment is started. We should add the "allowedValues" property to that param, to fail fast.

We also need to address the recent SKU name changes on Azure MySQL & PostgreSQL services.

Update: Azure MySQL and PostgreSQL are now GA. The latest api-version is "2017-12-01", and its documentation is available at places like this.

This is fixed in #68, so closing.


The file path output in the 'OUTPUT' window cannot be jumped directly

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

I looked at some output in the 'OUTPUT' window, such as eslint's error, but found that if the output inside the window contains the local file path, it is not recognized and cannot be jumped through cmd+click, I am not sure if this is a bug, if so, I can try to fix it
Steps to Reproduce:

Feel free to add an extension to eslint that is not installed
Trigger eslint

/duplicate https://github.com/microsoft/vscode/issues/163778

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Add vscode for csharp dev course

What does this PR do?
Add online course about the VisualStudioCode editor for the C# developer.
For resources
VSCode is a nimble editor that can do just about anything. In this session, we will set up and configure VSCode for use in C# development. Then we will use it to build, debug, and deploy a small .NET Core web application to Azure.
Along the way, we will go over a list of the top C#-focused plugins for VSCode. Whether you are just getting started with VSCode or you are used to VSCode but want to start building C# projects, this session will get you up to speed fast.
Why is this valuable (or not)?
Course is not existant in the ebooks repository.
How do we know it's really free?
It's a video on youtube
For book lists, is it a book? For course lists, is it a course? etc.
It's a course.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

not a course


Document test-case-selector flag for test cli command

Page link
No response
Description
kyverno/kyverno#3183 needs to be documented.
Expected behavior
A brief description and few examples about the flag under https://kyverno.io/docs/kyverno-cli/#test
Slack discussion
No response

Please change the label and assign this to me.


Add Dynamic Battery Support for Non-WWST Door Lock Devices

Check all that apply
Type of Change

[ ] WWST Certification Request

If this is your first time contributing code:

[ ] I have reviewed the README.md file
[ ] I have reviewed the CODE_OF_CONDUCT.md file
[ ] I have signed the CLA

[ ] I plan on entering a WWST Certification Request or have entered a request through the WWST Certification console at developer.smartthings.com

[ ] Bug fix
[x] New feature
[ ] Refactor

Checklist

[x] I have performed a self-review of my code
[x] I have commented my code in hard-to-understand areas
[ ] I have verified my changes by testing with a device or have communicated a plan for testing
[x] I am adding new behavior, such as adding a sub-driver, and have added and run new unit tests to cover the new behavior

Description of Change
Jira ticket showing mis-profiling of a bridged door lock: https://smartthings.atlassian.net/browse/MTR-821
Further, there is a general ticket on adding dynamic profiling to this driver: https://smartthings.atlassian.net/browse/CHAD-13948
This logic will permit dynamic profiling on the base-lock profile depending on the Power Source cluster, and will ignore devices with predefined fingerprints. This code may be mostly deprecated with the new door lock driver coming in, but this is a quick, temporary solution to this issue at hand.
Summary of Completed Tests
See unit tests

This looks good to me, but I was just thinking that one potential drawback with this approach is that each PR for new WWST device fingerprints would also have to include an update to the list of fingerprinted devices in do_configure. Maybe that is no big deal but I thought I'd mention it

Yeah @nickolas-deboom I agree, that's definitely a downside. Unfortunately, there's not really any better method in place of solving this issue atm. I figured we would inform Alissa of this in the next Risk Analysis meeting and then you and I can help monitor this as well until we put a better solution in place.

@nickolas-deboom I also think this example might get some more proactive desire to fix this situation in a larger way

And I just thought of this, but another point of note here is that there is a new and improved matter Lock driver coming soon, so this issue may be extremely temporary.

Those are good points, and I can't think of a better way to handle this either, so I think this is a good solution for now, especially given it might be temporary since there are improvements coming to this driver as you mentioned.

Also before merging, this change should be tested with both the new bridged the device as well as regression tested against an existing lock.

Yes, I agreee Cooper. I will add the dynamic battery profiling logic to those places as well. And I have already reached out on the affected ticket to get some testing with the new device.


[Mobile] Difficult to use attachments, code blocks and markup tables due to forced opening of context menu

EPAM AI DIAL chat version
0.7
What happened?
Context menu appears when you try to open and use attachments, code blocks or md-table buttons.
Expected result: do not display context menu in these cases.
Confidential information

[X] I confirm that do not share any confidential information

Verified on mobile device on staging env successfully
User message context menu or model response context menu is not opened if to click on buttons appear in code block, stages, MD table, attachments

Verified on sales+chrome mobile view sucecssfully


Pretty Nice!

Pretty nice scripts @evanx!
Your scripts will be shared in our next RedisWeekly!

oh cool - and thanks for saying say
actually i'll rewrite in Node later
problem today with Node for console apps right now using ES2016 for
async/await (i.e. Promises rather than callbacks), is that using Babel
transpiler naturally makes startup a bit slow
however ES2016 async/await has landed in V8, and will be coming to a future
version of Chrome hopefully in a matter of months
in the meantime, i'll do a Node version of this console app than can be
installed via npm
but ja. i'm very happy with the functionality at least of bash one :)
thanks for featuring it in RedisWeekly - great news
best
e
On 23 May 2016 at 10:28, Francois-Guillaume Ribreau <
<EMAIL_ADDRESS>wrote:

Pretty nice scripts @evanx https://github.com/evanx!
Your scripts will be shared in our next RedisWeekly
http://redisweekly.com!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/evanx/redis-scan-bash/issues/1


Moment does not get correct time when local time is wrong

When the computer have wrong time (not synchronized with standard internet time), momentjs is also return this wrong time. I used moment() and moment.utc() function, but all of them is same result. How can I get global time independently with local time?

You'll have to get the current timestamp from some external service and pass it to Moment. Moment.js is just a convenient, value-added API around the native Date functionality the JS environment provides, so it only knows what your computer knows.

Yes, I see.


ON CLUSTER doesn't work with hosts in multiple shards

The queries across the whole cluster don't work when a host has multiple shards:
DROP TABLE test ON CLUSTER 'cluster1'

click1	9000	371	An error occured before execution: Code: 371, e.displayText() = DB::Exception: There are two exactly the same ClickHouse instances click1:9000 in cluster cluster1, e.what() = DB::Exception	32	0

The host has this indeed three replicas of different shards:
SELECT *
  FROM system.clusters
 WHERE host_name = 'click1'

┌─cluster──┬─shard_num─┬─shard_weight─┬─replica_num─┬─host_name─┬─host_address─┬─port─┬─is_local─┬─user────┬─default_database─┐
│ cluster1 │        28 │            1 │           1 │ click1    │ <IP_ADDRESS>  │ 9000 │        0 │ default │ r0               │
│ cluster1 │        29 │            1 │           2 │ click1    │ <IP_ADDRESS>  │ 9000 │        0 │ default │ r1               │
│ cluster1 │        30 │            1 │           3 │ click1    │ <IP_ADDRESS>  │ 9000 │        0 │ default │ r2               │
└──────────┴───────────┴──────────────┴─────────────┴───────────┴──────────────┴──────┴──────────┴─────────┴──────────────────┘

There's really no reason for this check to exist, if you want to make sure it's not a configuration error, you should perhaps use host_name:port/default_database for uniqueness check?
cc @ludv1x

Hi!
Indeed, for the simplicity of the first distributed DDL version, I intentionally skipped implementation of the case when a server has several shards in different databases. I thought it is not the widespread case.
It is not complicated to add support of this case.

Ah I see, supporting this use case would be wonderful 👌

So my understanding is that only ALTER queries for replicated tables are problematic, since some require you to execute the query only on leader replica, and some require you to execute the query on any single replica.
For CREATE | ATTACH | DROP | DETACH it should be executed on distinct server instances regardless of how many shards do they have. For example in my case, I have 3 shards in databases r{0,1,2}, but if write:
DROP TABLE r0.test ON CLUSTER 'cluster1'

I expect r0.test to be dropped on all hosts, and I don't expect other replicas or shards to be affected.

We also have multiple shards and host a replica of each shard on every node, which basically makes ON CLUSTER requests unusable...

https://github.com/yandex/ClickHouse/blob/6aa2313decf619faf62c04c7bc8a7d6913831140/dbms/src/Interpreters/DDLWorker.cpp#L73

Can we expect this feature in nearby future?

We are also facing this issue. Does anyone knows any plans on the fix

Same issue. We have to truncate some tables periodically and it would be much more convenient if our apps wouldn't know anything about cluster shards and their tables - only cluster name.

I have finished a patch to support distributed ddl(currently, only delete/updatet/drop partition operations have been tested) on cross replication clusters。 distributed-alter-query。

Fixed in  #11508 & #11703


Cleaning up error checking for FSDP sharding strategies with fp32 precision

What does this PR do?
We should be able to train models w/ FSDP and a sharding strategy with precision fp32, we just need to make sure param_dtype is not fp32. This cleans up the ValueError checking for sharding strategies.
FSDP throws internal assertion errors when the sharding strategy isn't NO_SHARD and param_dtype is fp32 e.g.
Expects full precision but got torch.float32
  File "/workdisk/brandon/examples_fork/llm/main.py", line 180, in <module>
    main(cfg)
  File "/workdisk/brandon/examples_fork/llm/main.py", line 136, in main
    trainer = Trainer(
  File "/usr/lib/python3/dist-packages/composer/trainer/trainer.py", line 974, in __init__
    prepare_fsdp_module(model, optimizers, self.fsdp_config, precision)
  File "/usr/lib/python3/dist-packages/composer/trainer/dist_strategy.py", line 340, in prepare_fsdp_module
    fsdp_obj = FullyShardedDataParallel(
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/fully_sharded_data_parallel.py", line 1062, in __init__
    self._materialize_module(module, param_init_fn, device_from_device_id)
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/fully_sharded_data_parallel.py", line 1368, in _materialize_module
    param_init_fn(module)
  File "/usr/lib/python3/dist-packages/composer/trainer/dist_strategy.py", line 314, in _param_init_fn
    module.apply(obj.param_init_fn)
  File "/usr/lib/python3/dist-packages/torch/nn/modules/module.py", line 728, in apply
    module.apply(fn)
  File "/usr/lib/python3/dist-packages/torch/nn/modules/module.py", line 728, in apply
    module.apply(fn)
  File "/usr/lib/python3/dist-packages/torch/nn/modules/module.py", line 728, in apply
    module.apply(fn)
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/fully_sharded_data_parallel.py", line 1668, in apply
    with self._summon_full_params(recurse=False, writeback=True):
  File "/usr/lib/python3.10/contextlib.py", line 135, in __enter__
    return next(self.gen)
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/fully_sharded_data_parallel.py", line 2981, in _summon_full_params
    free_unsharded_flat_params = [handle.needs_unshard() for handle in self._handles]
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/fully_sharded_data_parallel.py", line 2981, in <listcomp>
    free_unsharded_flat_params = [handle.needs_unshard() for handle in self._handles]
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/flat_param.py", line 681, in needs_unshard
    unsharded_flat_param = self._get_padded_unsharded_flat_param()
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/flat_param.py", line 714, in _get_padded_unsharded_flat_param
    p_assert(
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/_utils.py", line 147, in p_assert
    traceback.print_stack()
Traceback (most recent call last):
  File "/workdisk/brandon/examples_fork/llm/main.py", line 180, in <module>
    main(cfg)
  File "/workdisk/brandon/examples_fork/llm/main.py", line 136, in main
    trainer = Trainer(
  File "/usr/lib/python3/dist-packages/composer/trainer/trainer.py", line 974, in __init__
    prepare_fsdp_module(model, optimizers, self.fsdp_config, precision)
  File "/usr/lib/python3/dist-packages/composer/trainer/dist_strategy.py", line 340, in prepare_fsdp_module
    fsdp_obj = FullyShardedDataParallel(
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/fully_sharded_data_parallel.py", line 1062, in __init__
    self._materialize_module(module, param_init_fn, device_from_device_id)
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/fully_sharded_data_parallel.py", line 1368, in _materialize_module
    param_init_fn(module)
  File "/usr/lib/python3/dist-packages/composer/trainer/dist_strategy.py", line 314, in _param_init_fn
    module.apply(obj.param_init_fn)
  File "/usr/lib/python3/dist-packages/torch/nn/modules/module.py", line 728, in apply
    module.apply(fn)
  File "/usr/lib/python3/dist-packages/torch/nn/modules/module.py", line 728, in apply
    module.apply(fn)
  File "/usr/lib/python3/dist-packages/torch/nn/modules/module.py", line 728, in apply
    module.apply(fn)
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/fully_sharded_data_parallel.py", line 1668, in apply
    with self._summon_full_params(recurse=False, writeback=True):
  File "/usr/lib/python3.10/contextlib.py", line 135, in __enter__
    return next(self.gen)
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/fully_sharded_data_parallel.py", line 2981, in _summon_full_params
    free_unsharded_flat_params = [handle.needs_unshard() for handle in self._handles]
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/fully_sharded_data_parallel.py", line 2981, in <listcomp>
    free_unsharded_flat_params = [handle.needs_unshard() for handle in self._handles]
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/flat_param.py", line 681, in needs_unshard
    unsharded_flat_param = self._get_padded_unsharded_flat_param()
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/flat_param.py", line 714, in _get_padded_unsharded_flat_param
    p_assert(
  File "/usr/lib/python3/dist-packages/torch/distributed/fsdp/_utils.py", line 149, in p_assert
    raise AssertionError
AssertionError

What issue(s) does this change relate to?
CO-1700
Before submitting

[ ] Have you read the contributor guidelines?
[ ] Is this change a documentation change or typo fix? If so, skip the rest of this checklist.
[ ] Was this change discussed/approved in a GitHub issue first? It is much more likely to be merged if so.
[ ] Did you update any related docs and document your change?
[ ] Did you update any related tests and add any new tests related to your change? (see testing)
[ x] Did you run the tests locally to make sure they pass?
[x ] Did you run pre-commit on your change? (see the pre-commit section of prerequisites)

@dakinggg it's a FSDP bug, it's noted here (and the fix is merged, they just never expected a user to pass in fp32 into mixed precision):
https://github.com/pytorch/pytorch/issues/90584
It just hasn't made its way into an official release yet.

Ahh, I see, we can use sharding with fp32, we just have to do that by leaving param_dtype=None until the pytorch bug makes its way to a release. Could you add a comment by this code (and create a JIRA for us to fix it) explaining that it is pytorch bug?

Tracking the issue until the next PyTorch release, CO-1708


Bug:

Describe the bug
Describe the bug
When running flutter run inside the /examples/ios directory, an error occurs:
lib/pages/login_page.dart:101:26: Error: Too few positional arguments: 1 required, 0 given.
            icon: QrImage(
                         ^
../../../.pub-cache/hosted/pub.dev/qr-3.0.1/lib/src/qr_image.dart:17:11: Context: Found this candidate, but the arguments don't match.
  factory QrImage(QrCode qrCode) {
          ^
Target kernel_snapshot failed: Exception

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileFlutterBuildDebug'.
> Process 'command '/opt/homebrew/Caskroom/flutter/3.13.9/flutter/bin/flutter'' finished with non-zero exit value 1

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2s

To Reproduce
Steps to reproduce the behavior:

Navigate to /examples/ios directory
Open ios emulator
Run flutter run
See error

Solved it temporarily by removing this code from login_page.dart
IconButton(
      tooltip: "QR Code",
      padding: const EdgeInsets.all(0),
      icon: QrImage(
        data: wallet.displayUri,
        version: QrVersions.auto,
        // foregroundColor: Colors.deepPurple.shade900,
        size: 200.0,
      ),
      iconSize: 200,
      onPressed: () =>
          Clipboard.setData(ClipboardData(text: wallet.displayUri)),
    ),


Update README.md

Damia Group Recruitment

Hey @marmelo
Having some trouble on pushing can you help? I think everything is ok :/

hey @afonsojramos
maybe I'm misreading something, what have you noted?

@AntWecki I was referring to the fact that consultancy companies are listed with what they do, instead of a proper description. But I am not sure what the standards are right now... @marmelo can you lend a hand?

Hi @afonsojramos, I am not being too picky with the description.
@AntWecki works at Damia, so I trust that he knows how is the company described best.

Thanks @AntWecki and @afonsojramos.


Any chance of updating this for the new SharpDX 3+?

It will be great!

This was done back on Jan 11th already, no?
https://github.com/praeclarum/NGraphics/commit/c25fb4fd05d1c35de26bf543cae9ec228423294a

Unfortunately, that version never got released (scratching head, don't know why).
I'm working on a 0.5 release that will include SDX 3.1.

Any update on the 0.5 release you mentioned?

@praeclarum bueller....?

Any update on for the 0.5 released?


CPLP-362: PortalDB EFCore classes initial commit

@wira-mms : Hi William, To start using EFCore I did run the scaffolding on the portal scheme and went through the generated entities and DBContext fixing what appeared to be missing. (The scaffolding didn't generate anything for the m<->n relationships so I had to add them manually). There are some 1-n relationships that make use of an additional table for the linkage that I didn't find out how to map directly (AgreementAssignedCompanyRole and AgreementAssignedDocumentTemplate) - maybe you know we could get rid of those awkward properties in class Agreement (without changing the database-scheme)?
Does EFCore require DBSets for Entities that are not explicitly meant to be manipulated directly as they represent tables linking the n<->m relationships (like DbSet)?

@ntruchsess I am not completely satisfied with the outcome. Too many things are configured in the context which should be moved to attributes on the entities themselves to make it more focused and readable. I will look into your relationship questions.


309 add tutorial for jit solver

Closes #309

Adds a scalar set for the matrix tests
Adds a tutorial for the JIT solver

Will revisit after we optimize JIT more to show more than one grid cell
Docs

We're currently processing your upload.  This comment will be updated when the results are available.


[BC] include endpoint in FEMM MeshSolution

This is a hot fix to get the correct time and angle data into the MeshSolution.
But I think it would be even better (long term) to use the original values in case they are not 'linspaced'.
We could also check the values and decide what data to use (i.e. original values or linspace equivalent values).


Domain activation is Failed - aliases distribution error

App Id: d163eh18wxq7or
Region: us-west-2
Step: Domain activation
Status: Failed
Issue/question
I'n not sure I have correct CNAME configured in my domain.  Doc implies (but never comes out and says) that it should be in cloudfront domain.  If this is true, that is hard to do.  The necessary DNS records are only visible on the Amplify console while the activation process is running.  As soon as it completes, succeed or fail, the link to show DNS records is disabled so you can't debug the situation, you can only try the activation again (and again...).

Error message
One or more aliases specified for the distribution includes an incorrectly configured DNS record that points to another CloudFront distribution. You must update the DNS record to correct the problem.
Additional information
I'm trying to publish into my custom blog: https://blog.bobhy.com (from Google Domains).
The requested cloudfront CNAME seems to change each time I try the activation, though the SSL challenge is stable.  This is the DNS info after the last attempt failed:

I fixed this myself, deleted and recreated the whole registration.
If you're reasons this latter,  I think Google Domains UI let me down.
When I pasted the verification verification domain into the DNS record,  I left off the trailing period.  Google helpfully autocompleted my own domain name and I didn't notice.   If you add the trailing period as provided by Amplify console, Google leaves the value as is and that works.


Hash function to implement Account Number and Password

Create a Hash function instead of the current if-else loop.

Are you talking about validating (as here: https://github.com/salman-bhai/E-Manager/blob/master/src/main.cpp#L124)?

I will do this, just tell me more details about this , where you want this change


Extracting the sample-level representation

We have to work on this, maybe adding some specific getters.
As far as I can tell now the sample-level representation can be extracted using model.correction_gmm.component_sample(n_sample=100). Can we add functionality to go from this to something like we have in Fig2? Happy to work on this if you point me at the code to make the batch level representations in multiDGD_paper

model.correction_gmm.component_sample() does not extract learned representations, but samples from the distribution describing the sample-level latent features. I created a pull request adding a method to the model called get_covariate_representation() which works the same way as get_representation().


Allow to override rollback implementation of the EntityPluginController.

When a exception FunctionNotSupportedException was thrown from the EntityPluginController
I'd like to call another function.

I know it's been a while but I think this is a valuable addition. Would you be available to rebase with master?
Also, since you want to do something when a specific exception was thrown, wouldn't it make more sense to do something like:
protected function handleFailure(\Exception $ex)
{
    $this->entityManager->getConnection()->rollback();
    $this->entityManager->close();
}

Thanks for this @hshn! And thank you @makasim for reviewing.
This will be included in 1.3.0


[TW#15302] Arduino BLE Client Notification Subscribe/Read Error

Hello,
In our work and testing over on the ESP Arduino repo, I've run into a debug line that's causing any reading of characteristics or their notifications to be ignored and I don't want them to. How can this be fixed? I'm trying to read from a known working peripheral when used with curieBLE or nRF connect.
E (51039) BT: bta_gattc_cmpl_cback unknown conn_id = 3, ignore data

hi @WALLTECH , please give me more log information to locate the problem.

Over the last week, the ESP-IDF BLE API changed and that required rework of our Arduino BLE libraries.  We have done that but are now suffering an inability to compile C++ applications because of an apparent problem in the latest toolchain (see #1032).  Unfortunately until we can compile C++ classes as described in that issue, we are going to be somewhat stuck in giving you more log diagnostics (I think).

Any update about this issue?


Remove version: bornova.numara version 3.15.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/bornova/numara-calculator/releases/download/v3.15.0/Numara-3.15.0.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 910)


fix: improve email validation in is-email-address method (#3132)

Resolves #{{TODO: #3132 }}.
Description

What is the purpose of this pull request?

This pull request:

Fixes the issue with the is-email-address method, ensuring it correctly validates invalid email addresses according to standard email validation rules.
Adds comprehensive test cases to handle edge cases and improve reliability.

Related Issues

Does this pull request have any related issues?

This pull request:

Resolves #3132

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

Before

After

Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.
[x] Added new test cases to ensure proper validation functionality.
[x] Verified that all existing tests pass without issues.

@stdlib-js/reviewers

Thank you for submitting this PR; however, it is not RFC 2822 compliant.


Carla: how to do the fault injection to camera (broken image, water drop, etc)

CARLA version: 0.9.11
Platform/OS: Ubuntu 18.04
Dear everyone,
These days I am trying to do some fault injection to see the performance of autonomous driving system in Carla. But I haven't found useful tutorials about how to inject faults into camera (e.g., water drops, noise model, broken images, etc). Does anyone know how to do this kind of fault injection?
Thank you very much and look forward to your feedback
Best Regards,

Hi @saina110, just as @brscholz mentioned you can add posprocessing materials to the cameras and then add in the constructor of the sensor AddPostProcessingMaterial(TEXT("Material'path/to/material'"));.
You could also postprocess the images on the client side and store/use them after the changes you apply.


Fix #7230: Allow sparse coo.toarray to handle nnz > 2**31

Fixes #7230. Don't know if there is a pending PR for this.
This changes only the type of nnz from template I to npy_int64.
I don't have the memory to test it with other data types but at least the following test with uint8 passes
In [1]: import scipy
In [2]: X = scipy.sparse.csr_matrix(np.ones((2**16, 1),dtype=np.uint8))
In [3]: X
Out[3]:
<65536x1 sparse matrix of type '<type 'numpy.uint8'>'
	with 65536 stored elements in Compressed Sparse Row format>

In [4]: (X*X[:2**15-1].T).toarray()
Out[4]:
array([[1, 1, 1, ..., 1, 1, 1],
       [1, 1, 1, ..., 1, 1, 1],
       [1, 1, 1, ..., 1, 1, 1],
       ...,
       [1, 1, 1, ..., 1, 1, 1],
       [1, 1, 1, ..., 1, 1, 1],
       [1, 1, 1, ..., 1, 1, 1]], dtype=uint8)

In [5]: (X*X[:2**15].T).toarray()
Out[5]:
array([[1, 1, 1, ..., 1, 1, 1],
       [1, 1, 1, ..., 1, 1, 1],
       [1, 1, 1, ..., 1, 1, 1],
       ...,
       [1, 1, 1, ..., 1, 1, 1],
       [1, 1, 1, ..., 1, 1, 1],
       [1, 1, 1, ..., 1, 1, 1]], dtype=uint8)

While running the same test with uint8 on 0.19.0 I ran out of memory. Has anything changed since then? Is it gh-7081?

gh-7081 means that the CSR toarray() method no longer triggers this bug. Can you test the fix with a coo_matrix instead?
You'll need to update generate_sparsetools.py as well, though I'm not as familiar with that system.
@pv, how would one indicate the type signature of the new coo_todense that requires an int64 argument regardless of the I type?

@perimosocordiae I see. I was suspecting that I might have to touch the gen API somewhere, but didn't quite know, where the appropriate files where. Thanks for pointing it out. It seems that generate_sparsetools generates wrappers for two index types npy_int32 and npy_int64, separately. Any change there for coo_todense and coo_matvec will have to written as a special case of mixing the two index types, since mixing I_types is not supported I believe.

That said, the following test with coo_matrix also passes, while again, I run out of memory on 0.19.0
In [1]: import scipy
In [2]: X = scipy.sparse.coo_matrix(np.ones((2**16, 1),dtype=np.uint8))
In [3]: Y = scipy.sparse.coo_matrix(np.ones((2**15+1, 1),dtype=np.uint8))
In [4]: (X*Y.T).toarray()
Out[4]:
array([[1, 1, 1, ..., 1, 1, 1],
       [1, 1, 1, ..., 1, 1, 1],
       [1, 1, 1, ..., 1, 1, 1],
       ...,
       [1, 1, 1, ..., 1, 1, 1],
       [1, 1, 1, ..., 1, 1, 1],
       [1, 1, 1, ..., 1, 1, 1]], dtype=uint8)

In [5]: np.count_nonzero(_) / 2.**31
Out[5]: 1.000030517578125

It seems like (X*Y.T).toarray() is converted to csr so the ValueError does not occur there at all. Whereas allocating a coo matrix of size 2**31 does hog the memory for me.
Anyway, m.row.dtype is int32 for me.
In [1]: import scipy
In [2]: X = scipy.sparse.coo_matrix(np.ones((2**29, 1),dtype=np.uint8))
In [3]: X.row.dtype
Out[3]: dtype('int32')
In [4]: X.col.dtype
Out[4]: dtype('int32')

Maybe somebody with bigger RAM could test this and if the problem persists (very likely), I would look into changing the generate_sparsetools accordingly.

Closing, as this is superseded by gh-7871.


Piping Sketch Events To API

I am incredibly sorry if I missed something where this is already possible, but;
For those of us using the BrowserWindow plugin (Electron for Sketch), we have a lot of dependencies related to the "on-window-close" event.
However if someone closes sketch (which will close the window), we cannot catch this event, which for me is causing a serious conflict.
If there was a way for you to pipe your own on-window-close (that's bound to Sketch.app) that we can use for an event listener, it would be really useful.
If this already exists, I apologize and will close the issue.

you should be able to add a listener to the Shutdown action and do your clean up here. But keep in mind that it might not always be called if Sketch is forced quit or something.


Fix ordering bug

If an empty request is sent to the /tags/order endpoint, all tags would get moved to secondary tags.
Sorry for lots of commits, I'm not used to StyleCI

@franzliedke but an empty array should be allowed to mean that there are no primary tags, all tags are secondary...?

@CDK2020 Are you still interested in completing this? If so, please take care of the requested change. :smile:

@franzliedke @CDK2020 has other responsibilities from RL at the moment. I guess we can safely assume he won't be able to conclude the PR.


Improving backward pass efficiency

This PR follows a conversation from last Thursday's meeting on potentially improving the efficiency of the backward pass. @nmansard mentioned that @jcarpent identified potential improvements. I am happy to test and look into some of these this week - under guidance and advice.
To start off, I checked the backward-pass (backwardPass, tryStep, computeGains) for missing noalias but could not find any. Second, I looked through the equations to identify left-hand side terms that could potentially be moved to row-major storage order. These are: K_, FxTVxx_p_, and FuTVxx_p_. A draft to change this is included in this PR - I am expressly looking for feedback whether this is an appropriate step and which other areas we could look into for performance improvement of the serial backward pass.
Initial results without vectorisation on the quadruped benchmark did not show any improvement.
With vectorisation enabled, using the all-robots benchmark, we observe a 13% reduction in time for the backward pass on Talos and a 17% reduction for Anymal. Full outputs are attached and summary table below. Note: Despite the reduction of ~20% in the backward pass benchmark of "all-robots", we only see a ~3.2% reduction in the computation time for a single DDP.solve iteration in "quadrupedal-gaits".

All experiments were run with EigenPy, Pinocchio, Crocoddyl compiled with "-O3 -march=native"/ENABLE_VECTORIZATION=ON. CPU set to use the performance governor (i7-10875H @ ~3.8GHz, 16MB cache). Multi-threading disabled.
ALL_ROBOTS_DEVEL.txt
ALL_ROBOTS_ROWMAJOR.txt
QUADRUPEDAL_DEVEL.txt
QUADRUPEDAL_ROWMAJOR.txt
Any advice or insights highly appreciated :-).

Very nice attempt. Seems this is the first milestone.
I also mentioned last time that vector contained in the structures were not correctly aligned in memory, mostly when using std::vector. This means that some stuff is not aligned for Pinocchio.
I would also suggest activating mavx2 (which for most platform is not active by default).

Thank you for the comments, I'll look into aligned vectors next. mavx2 was activated by default through march=native.

I've just added a commit that uses a aligned_vector container based on Pinocchio's and used it across all files (https://github.com/loco-3d/crocoddyl/pull/937/commits/d394eadcec685a0d18501c663cd4872eaa4abaf2). However, in the benchmarks this disimproved the benchmarks for all-robots (cf. attached). I'll revert the commit in the branch for now but would love your insights if I used this incorrectly. Should I only selectively add alignment for K, Quu, etc.?
ALL_ROBOTS_ROWMAJOR_NOT_ALIGNED.txt
ALL_ROBOTS_ROWMAJOR_ALIGNED.txt
.

@wxmerkt When watching to your timings, they do not seem to be stable. it is hard to say which one is better.

Could you also handle the BoxQP?

I have some separate improvements for BoxQP that I've been using for a while that give a significant boost for cases where constraints are active. I wanted to do this in a separate PR.
Changing to RowMajor will cause an API breaking change for BoxQP - I am happy with it but it won't be API or ABI compatible (or we can have internal temporaries that are being copied to). Would it be okay to break API/ABI for BoxQP (it's mostly internally)?

New numbers are in with Turbo-Boost=OFF, CPU-Governor=Performance - i.e. these are at 2.3 GHz, 16 MB Cache - top shows change between devel and moving to RowMajor in this PR, bottom row shows difference between RowMajor and RowMajor and aligned container (
d394ead):

Using RowMajor as above gives a speed boost of about 16% on a quadruped, 12% on a humanoid
Moving to aligned-vector containers does not result in a benefit (and would break API right now). This may be because the default alignment to 16 bytes isn't helpful for the odd sizes considered? Did I do something wrong?

I'll go ahead and address the comments above - otherwise, are there additional points to consider or debug for the backward pass?

I have some separate improvements for BoxQP that I've been using for a while that give a significant boost for cases where constraints are active. I wanted to do this in a separate PR.

Sounds a good idea. Looking forward for reviewing that PR :)

Changing to RowMajor will cause an API breaking change for BoxQP - I am happy with it but it won't be API or ABI compatible (or we can have internal temporaries that are being copied to). Would it be okay to break API/ABI for BoxQP (it's mostly internally)?

Yes, we can break the API if this leads to a computational benefit. What it is important for our users is to adding a deprecate procedure. We could discuss it when you create that PR.

I'll go ahead and address the comments above - otherwise, are there additional points to consider or debug for the backward pass?

Perhaps, we could improve the computational time by using triangularView of Hessian terms. @jcarpent -- is this could lead to a computation-time reduction? If so, could you provide a guidance in this topic?

This is the line in question: https://github.com/loco-3d/crocoddyl/blob/cbf81a329e3abaf4ce1b4a8fab1431f93cd9a5c8/src/core/solvers/ddp.cpp#L248
There is memory allocation. For quick fix, a tmp variable should be allocated once for all.

Thank you for noticing the heap allocation. I fixed this now. I spent some time on triangularView etc. but the improvements and changes have been hard to quantify. I believe we are now at the level where more time spent on optimisation is likely to outweigh the benefits and would consider this PR as complete.

Thanks @wxmerkt and @jcarpent for your efforts in this PR 👍🏽


Which options are supported  for the driver setting？

I command through "man 5 freeipmi.conf" , there is no options:
driver-type IPMIDRIVER
Specify the default driver type to use.

Hi there!
Thanks for reporting this. The available options are indeed not listed there. To see the available options, please see man 8 ipmi-sensors (also installed by FreeIPMI) instead. Look for the --driver-type=IPMIDRIVER option. The listed values for IPMIDRIVER are the same that you can use in the config file.
I forgot to mention this issue in the commit message, but I added a pointer to the example config in https://github.com/soundcloud/ipmi_exporter/commit/e2ddbbf31c3e4b4ef48e0103ad728528eaa55480, which I hope should take care of this. I will close this issue, but if you feel there is still something missing, please feel free to keep commenting on this issue.


Model combined.R does not sync some inputs

Running combined.R from a state where no Drive files have been synced fails on PC_delinted.csv being not found.

Copy authoritative versions of point_counts/data_ingest/output to Drive
Modify combined.R to add a drive_sync of point_counts/data_ingest/output/PC_delinted.csv

Assigning this to Mary, since she "owns" the point count data, for the first bullet:

Copy authoritative versions of point_counts/data_ingest/output to Drive.

(even Resilience_Data_Drive/COMB/point_counts does not exist yet)

The second bullet point is obsolete, since we decided to remove the drive_sync() from combined.R in favor of symlinks until we move to a project-wide convention (possible design criteria: minimize hard-coding of paths in source files, minimize huge downloads by individuals working on a chunk that does not require them).


Fix Undo/Redo not working in Bezier Animation Editor when moving keys

Fixes https://github.com/godotengine/godot/issues/97146, introduced by https://github.com/godotengine/godot/pull/96753
In the PR I was registering the animation refresh do and undo method call inside AnimationBezierTrackEdit::_bezier_track_insert_key_at_anim thinking it was the correct place to refresh once the track is moved.
This is incorrect since this method itself is called by the undo_redo.commit() registed back in gui_input. So I moved it to the ape call to gui_input, after all other undo_redo callbacks caused by a move are registered.

Thanks!


fix(prefixes): add pyr_ prefix to Refund object

POST /v1/refunds returns the following Refund object with an ID the has the prefix pyr_
{
  "id": "pyr_XXXXXXXXXXXXXXXX",
  "object": "refund",
  "amount": 322,
  "balance_transaction": "txn_XXXXXXXXXXXXXXXX",
  "charge": ["py_XXXXXXXXXXXXXXXX"],
  "created":<PHONE_NUMBER>,
  "currency": "usd",
  "metadata": {},
  "payment_intent": ["pi_XXXXXXXXXXXXXXXX"],
  "reason": null,
  "receipt_number": null,
  "source_transfer_reversal": null,
  "status": "pending",
  "transfer_reversal": null
}

This pyr_ is not a defined ID for Refund objects in the src/ids.rs file, resulting in an error when fetching this object from Stripe. I cannot find documentation that points to this prefix (as with most Stripe prefixes), but I'm guessing it denotes a refund (r) from a PaymentIntent charge (py), which is the case in my situation.

Merged, thank you for your contribution! :)

Could we release this as 0.15.1? I'd also like to explore not requiring IDs to end with predetermined prefixes, since it seems highly variable what prefixes are given to IDs based on the usecase.


asking workflow to begin I get "message stopped"

Describe the bug
When I tell my team to build something, I immediately get 'Message Stopped' error
To Reproduce

I created the software development team in the demo app exactly
Setup my OpenAI API key per the video
I tell the system to 'build me a to-do list app'
I get the Message Stopped error.

Expected behavior
Messages in the window telling the supervisor to get to work.
Screenshots
If applicable, add screenshots to help explain your problem.
Flow
I'm a newbie, so I expect that I missed something and this is my fault.
Setup

Installation [e.g. docker, npx flowise start, pnpm start]
flowise/1.8.1 darwin-x64 node-v20.14.0
2.3 GHz Quad-Core Intel Core i5 Mac running Sonoma 14.5
Browser Chrome

Additional context
I searched for 'Flowise error "message stopped" but found nothing. I deleted the flow and started over based on how that fixed another error someone was having, but that did not help.

Check this https://github.com/FlowiseAI/Flowise/issues/2557#issuecomment-2148208490

moving to #2557

Chat_model Agents.json
can anyone check this model ,the supervisor calls the worker ,the worker doesnt respond


natOutgoing / SNAT not working for HA single-stack ipv6 bpf cluster running on dual-stack host

Using tigera operator, can't seem to get SNAT working for pod egress.
Expected Behavior
SNAT should work for egress to external services not running on cluster nodes.
Current Behavior
SNATing is not occurring during egress with source address showing the pod ip for traffic leaving the cluster.
Possible Solution
None identified.
Steps to Reproduce (for bugs)

provision HA single-stack ipv6 kubernetes cluster (via kubeadm) on dual-stack host and one non-cluster dual-stack host for control plane endpoint load balancing (and other services) in same ipv6 local-link network/subnet
install tigera operator via https://raw.githubusercontent.com/projectcalico/calico/v3.27.2/manifests/tigera-operator.yaml
install calico via the following installation manifest:

apiVersion: operator.tigera.io/v1
kind: Installation
metadata:
  name: default
spec:
  calicoNetwork:
    ipPools:
    - blockSize: 122
      cidr: fd00::10:244:0:0/108
      disableBGPExport: true
      encapsulation: VXLANCrossSubnet
      natOutgoing: Enabled
      nodeSelector: all()
    linuxDataplane: BPF
    nodeAddressAutodetectionV4: {}
    nodeAddressAutodetectionV6:
      kubernetes: NodeInternalIP
  typhaMetricsPort: 9093

create pod (any image that can issue icmp6): kubectl run -it -n calico-system --rm debug --image=mbentley/bind-tools --restart=Never -- sh
make note of assigned pod ip:

~ $ ip -6 a | grep 'inet6'
    inet6 ::1/128 scope host
    inet6 fd00::10:244:c:e7c4/128 scope global
    inet6 fe80::40a6:6eff:fe18:4ef0/64 scope link

start icmp6 to non-cluster host: ping -6 k8s-lb
monitor icmp6 traffic on non-cluster host: tcpdump -i any icmp6
observe source address arriving on icmp6 requests:

22:14:19.967367 eth0  In  IP6 fd00::10:244:c:e7c4 > k8s-lb: ICMP6, echo request, id 19912, seq 20, length 64
22:14:19.967422 eth0  Out IP6 k8s-lb > fd00::10:244:c:e7c4: ICMP6, echo reply, id 19912, seq 20, length 64

Context
Response traffic to requests originating from the cluster are unroutable as external services shouldn't need custom routes for pod ip cidr(s) with functioning SNAT and MASQ on the cluster node for egress traffic.
Your Environment

Calico Cluster Version: v3.27.2
Calico Cluster Type: typha,kdd,k8s,operator,bgp,kubeadm
Orchestrator version: Kubernetes v1.29.2
Operating System and version: Ubuntu 22.04.4 LTS

Additional Calico Installation Details

IPPools (created by tigera operator)

kubectl get ippools -o yaml
apiVersion: v1
items:
- apiVersion: crd.projectcalico.org/v1
  kind: IPPool
  metadata:
    annotations:
      projectcalico.org/metadata: '{"uid":"0e80d820-cc28-498f-ae7f-735d7e9dbacf","creationTimestamp":"2024-03-20T20:19:26Z"}'
    creationTimestamp: "2024-03-20T20:19:26Z"
    generation: 1
    name: default-ipv4-ippool
    resourceVersion: "923"
    uid: 7c4a7359-0be7-48d6-ada6-33783010ea28
  spec:
    allowedUses:
    - Workload
    - Tunnel
    blockSize: 26
    cidr: <IP_ADDRESS>/16
    ipipMode: Never
    natOutgoing: true
    nodeSelector: all()
    vxlanMode: Never
- apiVersion: crd.projectcalico.org/v1
  kind: IPPool
  metadata:
    annotations:
      projectcalico.org/metadata: '{"uid":"0649f662-66e1-45df-bf90-8ee9a8bfd988","creationTimestamp":"2024-03-20T20:19:26Z"}'
    creationTimestamp: "2024-03-20T20:19:26Z"
    generation: 1
    name: default-ipv6-ippool
    resourceVersion: "924"
    uid: 282d7d8e-a5a9-4050-bd9f-0045379442cb
  spec:
    allowedUses:
    - Workload
    - Tunnel
    blockSize: 122
    cidr: fd00::10:244:0:0/108
    disableBGPExport: true
    ipipMode: Never
    natOutgoing: true
    nodeSelector: all()
    vxlanMode: CrossSubnet
kind: List
metadata:
  resourceVersion: ""

FelixConfiguration

apiVersion: v1
items:
- apiVersion: crd.projectcalico.org/v1
  kind: FelixConfiguration
  metadata:
    annotations:
      projectcalico.org/metadata: '{"uid":"a8003704-d53d-47ce-9c29-1937f3e5e420","generation":2,"creationTimestamp":"2024-03-20T20:19:18Z","managedFields":[{"manager":"operator","operation":"Update","apiVersion":"crd.projectcalico.org/v1","time":"2024-03-20T20:19:18Z","fieldsType":"FieldsV1","fieldsV1":{"f:spec":{".":{},"f:bpfLogLevel":{},"f:healthPort":{},"f:vxlanVNI":{}}}},{"manager":"OpenAPI-Generator","operation":"Update","apiVersion":"crd.projectcalico.org/v1","time":"2024-03-20T20:19:19Z","fieldsType":"FieldsV1","fieldsV1":{"f:spec":{"f:policySyncPathPrefix":{},"f:prometheusMetricsEnabled":{},"f:serviceLoopPrevention":{}}}}]}'
    creationTimestamp: "2024-03-20T20:19:18Z"
    generation: 3
    name: default
    resourceVersion: "926"
    uid: a8003704-d53d-47ce-9c29-1937f3e5e420
  spec:
    bpfConnectTimeLoadBalancing: TCP
    bpfHostNetworkedNATWithoutCTLB: Enabled
    bpfLogLevel: ""
    floatingIPs: Disabled
    healthPort: 9099
    logSeverityScreen: Info
    policySyncPathPrefix: /var/run/nodeagent
    prometheusMetricsEnabled: true
    reportingInterval: 0s
    serviceLoopPrevention: Disabled
    vxlanVNI: 4096
kind: List
metadata:
  resourceVersion: ""

Additional Details (from node running icmp6 client pod)

describe calico-node pod

Name:                 calico-node-vxmtm
Namespace:            calico-system
Priority:<PHONE_NUMBER>
Priority Class Name:  system-node-critical
Service Account:      calico-node
Node:                 k8s-control-2/fd11::10:0:0:5
Start Time:           Wed, 20 Mar 2024 17:25:48 -0500
Labels:               app.kubernetes.io/name=calico-node
                      controller-revision-hash=558c45d59c
                      k8s-app=calico-node
                      pod-template-generation=2
Annotations:          hash.operator.tigera.io/cni-config: f2dea26b806eeb2a5867ba2b1d391bab0cc153a7
                      hash.operator.tigera.io/system: fdde45054a8ae4f629960ce37570929502e59449
                      tigera-operator.hash.operator.tigera.io/tigera-ca-private: c6784f1100cfddc78f4afeaaa3bea38d5caa9d9f
Status:               Running
IP:                   fd11::10:0:0:5
IPs:
  IP:           fd11::10:0:0:5
Controlled By:  DaemonSet/calico-node
Init Containers:
  flexvol-driver:
    Container ID:    containerd://5f0ddb8bd6efa47738e1cb19fb57168b91c029c26e0bd1e64edaec23ec708c52
    Image:           docker.io/calico/pod2daemon-flexvol:v3.27.2
    Image ID:        docker.io/calico/pod2daemon-flexvol@sha256:e9eaff6ec042d67398c25d1fc48f82511582993ec41f9541cabb03d0d59f9a6f
    Port:            <none>
    Host Port:       <none>
    SeccompProfile:  RuntimeDefault
    State:           Terminated
      Reason:        Completed
      Exit Code:     0
      Started:       Wed, 20 Mar 2024 17:25:49 -0500
      Finished:      Wed, 20 Mar 2024 17:25:49 -0500
    Ready:           True
    Restart Count:   0
    Environment:     <none>
    Mounts:
      /host/driver from flexvol-driver-host (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-hxnbm (ro)
  mount-bpffs:
    Container ID:    containerd://b7c2a3bda331ff279bf664369863226fdb30cc707b64742bdbb2cc095bcd614a
    Image:           docker.io/calico/node:v3.27.2
    Image ID:        docker.io/calico/node@sha256:0d00b1f4235652b370f3897803d7c8ef5a7059a081ab8d69ae02b7ca0cb0193b
    Port:            <none>
    Host Port:       <none>
    SeccompProfile:  RuntimeDefault
    Command:
      calico-node
      -init
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Wed, 20 Mar 2024 17:25:49 -0500
      Finished:     Wed, 20 Mar 2024 17:25:49 -0500
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /nodeproc from nodeproc (ro)
      /sys/fs from sys-fs (rw)
      /var/run/calico from var-run-calico (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-hxnbm (ro)
  install-cni:
    Container ID:    containerd://cfc8b47e7b5e33dc258ee110ea613771ef437ca4867f20eeea2386bdca5c2434
    Image:           docker.io/calico/cni:v3.27.2
    Image ID:        docker.io/calico/cni@sha256:d17e907f27956d82e978f4aee8c21f876230955f3fba51da621c7c49e71f2ece
    Port:            <none>
    Host Port:       <none>
    SeccompProfile:  RuntimeDefault
    Command:
      /opt/cni/bin/install
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Wed, 20 Mar 2024 17:25:50 -0500
      Finished:     Wed, 20 Mar 2024 17:25:50 -0500
    Ready:          True
    Restart Count:  0
    Environment:
      CNI_CONF_NAME:            10-calico.conflist
      SLEEP:                    false
      CNI_NET_DIR:              /etc/cni/net.d
      CNI_NETWORK_CONFIG:       <set to the key 'config' of config map 'cni-config'>  Optional: false
      KUBERNETES_SERVICE_HOST:  k8s-lb
      KUBERNETES_SERVICE_PORT:  6443
    Mounts:
      /host/etc/cni/net.d from cni-net-dir (rw)
      /host/opt/cni/bin from cni-bin-dir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-hxnbm (ro)
Containers:
  calico-node:
    Container ID:    containerd://634b4253af09096dcd58188f81cbe97e91d8b7e1f92426ed526cb7be20252108
    Image:           docker.io/calico/node:v3.27.2
    Image ID:        docker.io/calico/node@sha256:0d00b1f4235652b370f3897803d7c8ef5a7059a081ab8d69ae02b7ca0cb0193b
    Port:            <none>
    Host Port:       <none>
    SeccompProfile:  RuntimeDefault
    State:           Running
      Started:       Wed, 20 Mar 2024 17:25:51 -0500
    Ready:           True
    Restart Count:   0
    Liveness:        http-get http://localhost:9099/liveness delay=0s timeout=10s period=60s #success=1 #failure=3
    Readiness:       exec [/bin/calico-node -bird-ready -felix-ready] delay=0s timeout=10s period=30s #success=1 #failure=3
    Environment:
      DATASTORE_TYPE:                      kubernetes
      WAIT_FOR_DATASTORE:                  true
      CLUSTER_TYPE:                        k8s,operator,bgp
      CALICO_DISABLE_FILE_LOGGING:         false
      FELIX_DEFAULTENDPOINTTOHOSTACTION:   ACCEPT
      FELIX_HEALTHENABLED:                 true
      FELIX_HEALTHPORT:                    9099
      NODENAME:                             (v1:spec.nodeName)
      NAMESPACE:                           calico-system (v1:metadata.namespace)
      FELIX_TYPHAK8SNAMESPACE:             calico-system
      FELIX_TYPHAK8SSERVICENAME:           calico-typha
      FELIX_TYPHACAFILE:                   /etc/pki/tls/certs/tigera-ca-bundle.crt
      FELIX_TYPHACERTFILE:                 /node-certs/tls.crt
      FELIX_TYPHAKEYFILE:                  /node-certs/tls.key
      FIPS_MODE_ENABLED:                   false
      FELIX_TYPHACN:                       typha-server
      CALICO_MANAGE_CNI:                   true
      CALICO_IPV6POOL_CIDR:                fd00::10:244:0:0/108
      CALICO_IPV6POOL_VXLAN:               Never
      CALICO_IPV6POOL_BLOCK_SIZE:          122
      CALICO_IPV6POOL_NAT_OUTGOING:        true
      CALICO_IPV6POOL_NODE_SELECTOR:       all()
      CALICO_IPV6POOL_DISABLE_BGP_EXPORT:  true
      FELIX_BPFENABLED:                    true
      CALICO_NETWORKING_BACKEND:           bird
      IP:                                  none
      IP6:                                 autodetect
      IP6_AUTODETECTION_METHOD:            kubernetes-internal-ip
      FELIX_IPV6SUPPORT:                   true
      CALICO_ROUTER_ID:                    hash
      KUBERNETES_SERVICE_HOST:             k8s-lb
      KUBERNETES_SERVICE_PORT:             6443
    Mounts:
      /etc/pki/tls/cert.pem from tigera-ca-bundle (ro,path="ca-bundle.crt")
      /etc/pki/tls/certs from tigera-ca-bundle (ro)
      /host/etc/cni/net.d from cni-net-dir (rw)
      /lib/modules from lib-modules (ro)
      /node-certs from node-certs (ro)
      /run/xtables.lock from xtables-lock (rw)
      /sys/fs/bpf from bpffs (rw)
      /var/lib/calico from var-lib-calico (rw)
      /var/log/calico/cni from cni-log-dir (rw)
      /var/run/calico from var-run-calico (rw)
      /var/run/nodeagent from policysync (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-hxnbm (ro)
Conditions:
  Type                        Status
  PodReadyToStartContainers   True
  Initialized                 True
  Ready                       True
  ContainersReady             True
  PodScheduled                True
Volumes:
  lib-modules:
    Type:          HostPath (bare host directory volume)
    Path:          /lib/modules
    HostPathType:
  xtables-lock:
    Type:          HostPath (bare host directory volume)
    Path:          /run/xtables.lock
    HostPathType:  FileOrCreate
  policysync:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/nodeagent
    HostPathType:  DirectoryOrCreate
  tigera-ca-bundle:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      tigera-ca-bundle
    Optional:  false
  node-certs:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  node-certs
    Optional:    false
  var-run-calico:
    Type:          HostPath (bare host directory volume)
    Path:          /var/run/calico
    HostPathType:
  var-lib-calico:
    Type:          HostPath (bare host directory volume)
    Path:          /var/lib/calico
    HostPathType:
  sys-fs:
    Type:          HostPath (bare host directory volume)
    Path:          /sys/fs
    HostPathType:  DirectoryOrCreate
  bpffs:
    Type:          HostPath (bare host directory volume)
    Path:          /sys/fs/bpf
    HostPathType:  Directory
  nodeproc:
    Type:          HostPath (bare host directory volume)
    Path:          /proc
    HostPathType:
  cni-bin-dir:
    Type:          HostPath (bare host directory volume)
    Path:          /opt/cni/bin
    HostPathType:
  cni-net-dir:
    Type:          HostPath (bare host directory volume)
    Path:          /etc/cni/net.d
    HostPathType:
  cni-log-dir:
    Type:          HostPath (bare host directory volume)
    Path:          /var/log/calico/cni
    HostPathType:
  flexvol-driver-host:
    Type:          HostPath (bare host directory volume)
    Path:          /usr/libexec/kubernetes/kubelet-plugins/volume/exec/nodeagent~uds
    HostPathType:  DirectoryOrCreate
  kube-api-access-hxnbm:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              kubernetes.io/os=linux
Tolerations:                 :NoSchedule op=Exists
                             :NoExecute op=Exists
                             CriticalAddonsOnly op=Exists
                             node.kubernetes.io/disk-pressure:NoSchedule op=Exists
                             node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/network-unavailable:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists
                             node.kubernetes.io/pid-pressure:NoSchedule op=Exists
                             node.kubernetes.io/unreachable:NoExecute op=Exists
                             node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  26m                default-scheduler  Successfully assigned calico-system/calico-node-vxmtm to k8s-control-2
  Normal   Pulled     26m                kubelet            Container image "docker.io/calico/pod2daemon-flexvol:v3.27.2" already present on machine
  Normal   Created    26m                kubelet            Created container flexvol-driver
  Normal   Started    26m                kubelet            Started container flexvol-driver
  Normal   Pulled     26m                kubelet            Container image "docker.io/calico/node:v3.27.2" already present on machine
  Normal   Created    26m                kubelet            Created container mount-bpffs
  Normal   Started    26m                kubelet            Started container mount-bpffs
  Normal   Pulled     26m                kubelet            Container image "docker.io/calico/cni:v3.27.2" already present on machine
  Normal   Created    26m                kubelet            Created container install-cni
  Normal   Started    26m                kubelet            Started container install-cni
  Normal   Pulled     26m                kubelet            Container image "docker.io/calico/node:v3.27.2" already present on machine
  Normal   Created    26m                kubelet            Created container calico-node
  Normal   Started    26m                kubelet            Started container calico-node
  Warning  Unhealthy  26m (x2 over 26m)  kubelet            Readiness probe failed: calico/node is not ready: BIRD is not ready: Error querying BIRD: unable to connect to BIRDv4 socket: dial unix /var/run/calico/bird.ctl: connect: connection refused

calico-node -show-status

bird v4 status
+-------+-------------------+---------------+---------------------+---------------------+---------------------+
| READY |      VERSION      |    ROUTEID    |     SERVERTIME      |      LASTBOOT       |    LASTRECONFIG     |
+-------+-------------------+---------------+---------------------+---------------------+---------------------+
| true  | v0.3.3+birdv1.6.8 | <IP_ADDRESS> | 2024-03-20 20:41:45 | 2024-03-20 20:40:46 | 2024-03-20 20:40:46 |
+-------+-------------------+---------------+---------------------+---------------------+---------------------+

bird v4 BGP peers
+--------------+-----------+-------+-------+----------+
| PEER ADDRESS | PEER TYPE | STATE | SINCE | BGPSTATE |
+--------------+-----------+-------+-------+----------+
+--------------+-----------+-------+-------+----------+

bird v4 routes
+-------------+----------+-------+-------------+---------+
| DESTINATION | GATEWAY  | IFACE | LEARNEDFROM | PRIMARY |
+-------------+----------+-------+-------------+---------+
| <IP_ADDRESS>/0   | <IP_ADDRESS> | eth0  | kernel1     | *       |
| <IP_ADDRESS>/32 | N/A      | eth0  | kernel1     | *       |
| <IP_ADDRESS>/24 | N/A      | eth0  | direct1     | *       |
| <IP_ADDRESS>/32 | N/A      | eth0  | kernel1     | *       |
+-------------+----------+-------+-------------+---------+

bird v6 status
+-------+-------------------+---------------+---------------------+---------------------+---------------------+
| READY |      VERSION      |    ROUTEID    |     SERVERTIME      |      LASTBOOT       |    LASTRECONFIG     |
+-------+-------------------+---------------+---------------------+---------------------+---------------------+
| true  | v0.3.3+birdv1.6.8 | <IP_ADDRESS> | 2024-03-20 20:41:45 | 2024-03-20 20:40:46 | 2024-03-20 20:40:46 |
+-------+-------------------+---------------+---------------------+---------------------+---------------------+

bird v6 BGP peers
+----------------+-----------+-------+----------+-------------+
|  PEER ADDRESS  | PEER TYPE | STATE |  SINCE   |  BGPSTATE   |
+----------------+-----------+-------+----------+-------------+
| fd11::10:0:0:3 | Mesh      | up    | 20:40:48 | Established |
| fd11::10:0:0:4 | Mesh      | up    | 20:40:48 | Established |
+----------------+-----------+-------+----------+-------------+

bird v6 routes
+-------------------------+--------------------------+-----------------+-------------+---------+
|       DESTINATION       |         GATEWAY          |      IFACE      | LEARNEDFROM | PRIMARY |
+-------------------------+--------------------------+-----------------+-------------+---------+
| ::/0                    | fe80::215:5dff:fe01:8013 | eth0            | kernel1     | *       |
| fd00::10:244:c:e7c4/128 | N/A                      | cali9afddb189c7 | kernel1     | *       |
| fd00::10:244:c:e7c0/122 | N/A                      | blackhole       | static1     | *       |
| fd00::10:244:c:e7c0/122 | N/A                      | blackhole       | kernel1     |         |
| fd00::10:244:c:e7c0/128 | N/A                      | vxlan-v6.calico | direct1     | *       |
| fd00::10:244:c:e7c3/128 | N/A                      | calidbcba662e5c | kernel1     | *       |
| fd00::10:244:c:e7c2/128 | N/A                      | calid4bb1f604df | kernel1     | *       |
| fd00::10:244:2:e200/122 | fd11::10:0:0:4           | eth0            | kernel1     | *       |
| 2001:db8::1/128         | N/A                      | bpfin.cali      | kernel1     | *       |
| fd00::10:244:e:d680/122 | fd11::10:0:0:3           | eth0            | kernel1     | *       |
| fd00::10:96:0:a/128     | 2001:db8::1              | bpfin.cali      | kernel1     | *       |
| fd11::10:0:0:0/118      | N/A                      | eth0            | kernel1     | *       |
| fd11::10:0:0:5/128      | N/A                      | eth0            | direct1     | *       |
+-------------------------+--------------------------+-----------------+-------------+---------+

calico-node -bpf routes -6 dump

fd00::10:244:0:0/108: remote in-pool nat-out
fd00::10:244:2:e200/122: remote workload in-pool nat-out same-subnet tunneled nh fd11::10:0:0:4
fd00::10:244:2:e200/128: remote host in-pool nat-out same-subnet tunneled
fd00::10:244:c:e7c0/128: local host
fd00::10:244:c:e7c2/128: local workload in-pool nat-out same-subnet idx 3
fd00::10:244:c:e7c3/128: local workload in-pool nat-out same-subnet idx 7
fd00::10:244:c:e7c4/128: local workload in-pool nat-out same-subnet idx 8
fd00::10:244:e:d680/122: remote workload in-pool nat-out same-subnet tunneled nh fd11::10:0:0:3
fd00::10:244:e:d680/128: remote host in-pool nat-out same-subnet tunneled
fd11::10:0:0:3/128: remote host
fd11::10:0:0:4/128: remote host
fd11::10:0:0:5/128: local host

calico-node -bpf nat -6 dump

fd00::10:96:0:6fee port 5473 proto 6 id 0 count 2 local 1
        0:0      [fd11::10:0:0:5]:5473
        0:1      [fd11::10:0:0:3]:5473
fd00::10:96:0:1 port 443 proto 6 id 1 count 3 local 0
        1:0      [fd11::10:0:0:3]:6443
        1:1      [fd11::10:0:0:4]:6443
        1:2      [fd11::10:0:0:5]:6443
fd00::10:96:0:a port 53 proto 6 id 3 count 2 local 0
        3:0      [fd00::10:244:2:e206]:53
        3:1      [fd00::10:244:2:e207]:53
fd00::10:96:0:a port 53 proto 17 id 2 count 2 local 0
        2:0      [fd00::10:244:2:e206]:53
        2:1      [fd00::10:244:2:e207]:53
fd00::10:96:0:a port 9153 proto 6 id 4 count 2 local 0
        4:0      [fd00::10:244:2:e206]:9153
        4:1      [fd00::10:244:2:e207]:9153
fd00::10:96:0:4e0 port 443 proto 6 id 5 count 1 local 0
        5:0      [fd00::10:244:e:d683]:9443
fd00::10:96:0:5858 port 443 proto 6 id 6 count 2 local 1
        6:0      [fd00::10:244:c:e7c3]:5443
        6:1      [fd00::10:244:e:d684]:5443

Hopefully just something I am doing wrong...

Confirmed spec.calicoNetwork.linuxDataplane = iptables works as expected (SNAT + MASQ) with above config.  If anyone has any ideas related to potential incorrect tigera operator generated manifests / config would be happy to try that out!

Could you share ip6tables-save -c output from the node where your ping pod runs? What is k8s-lb IP?

Could you share ip6tables-save -c output from the node where your ping pod runs? What is k8s-lb IP?

Sure!
k8s-lb ip addr show eth0:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:15:5d:01:80:13 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fd11::10:0:0:2/118 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::215:5dff:fe01:8013/64 scope link
       valid_lft forever preferred_lft forever

k8s-control-2 ip6tables-save -c:
# Generated by ip6tables-save v1.8.7 on Fri Mar 22 23:49:09 2024
*mangle
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:KUBE-IPTABLES-HINT - [0:0]
:KUBE-KUBELET-CANARY - [0:0]
COMMIT
# Completed on Fri Mar 22 23:49:09 2024
# Generated by ip6tables-save v1.8.7 on Fri Mar 22 23:49:09 2024
*raw
:PREROUTING ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:cali-PREROUTING - [0:0]
:cali-untracked-flows - [0:0]
:cali-untracked-policy - [0:0]
[412952:143527437] -A PREROUTING -m comment --comment "cali:6gwbT8clXdHdC1b1" -j cali-PREROUTING
[0:0] -A cali-PREROUTING -m comment --comment "cali:7zj7wGmwqVLvW3HM" -m comment --comment "Jump to target for packets with Bypass mark" -g cali-untracked-policy
[410096:143112825] -A cali-PREROUTING -m comment --comment "cali:7eWd-Mfcvj2ajb5P" -m comment --comment "Mark traffic towards the host - it is TRACKed" -m addrtype --dst-type LOCAL -j MARK --set-xmark 0x1100000/0x1100000
[2856:414612] -A cali-PREROUTING -m comment --comment "cali:Ym3djp8aZ-csATbF" -m comment --comment "Check if forwarded traffic needs to be TRACKed" -m addrtype ! --dst-type LOCAL -g cali-untracked-flows
[0:0] -A cali-untracked-flows -i docker+ -m comment --comment "cali:4NvdONeom6EEzmfy" -m comment --comment "Track interface docker+" -j RETURN
[39:2440] -A cali-untracked-flows -m comment --comment "cali:VtS22xg7f6wFtQnT" -m comment --comment "MarkSeenSkipFIB Mark" -j RETURN
[0:0] -A cali-untracked-flows -m comment --comment "cali:pTuyY-99YpsSnNwE" -m comment --comment "MarkSeenFallThrough Mark" -j RETURN
[0:0] -A cali-untracked-flows -m comment --comment "cali:YQVCNgli2v3VOBUb" -m comment --comment "MarkSeenMASQ Mark" -j RETURN
[2777:408872] -A cali-untracked-flows -m comment --comment "cali:wFRbW8MsubpMXL-g" -m comment --comment "MarkSeenNATOutgoing Mark" -j RETURN
[40:3300] -A cali-untracked-flows -m comment --comment "cali:YVfeAHk7oTMmiVm5" -j NOTRACK
[0:0] -A cali-untracked-policy -m comment --comment "cali:GmTHf-cZvJXoOqUt" -j MARK --set-xmark 0x0/0x0
[0:0] -A cali-untracked-policy -m comment --comment "cali:QJsxuYT1xa6WFzwv" -j NOTRACK
COMMIT
# Completed on Fri Mar 22 23:49:09 2024
# Generated by ip6tables-save v1.8.7 on Fri Mar 22 23:49:09 2024
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:KUBE-KUBELET-CANARY - [0:0]
[301955:122068444] -A INPUT -m comment --comment "cali:zkuE8qdwsVpH6Kd2" -m comment --comment "Accept packets from flows that pre-date BPF." -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
[454:61469] -A INPUT -m comment --comment "cali:XQL0mC-L6wldZdgN" -m comment --comment "Drop packets from unknown flows." -j DROP
[2153:2062810] -A INPUT -i cali+ -m comment --comment "cali:pbFdTFCLcV-MVLSS" -j ACCEPT
[2:112] -A INPUT -i cali+ -m comment --comment "cali:u_TyW7ph8QsYnThE" -j DROP
[814:120205] -A FORWARD -m comment --comment "cali:umcmOn0WnTNOKJrp" -m comment --comment "Pre-approved by BPF programs."  -m conntrack --ctstate RELATED,ESTABLISHED -j MARK --set-xmark 0x8000000/0x8000000
COMMIT
# Completed on Fri Mar 22 23:49:09 2024
# Generated by ip6tables-save v1.8.7 on Fri Mar 22 23:49:09 2024
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:KUBE-KUBELET-CANARY - [0:0]
:cali-POSTROUTING - [0:0]
:cali-fip-snat - [0:0]
:cali-nat-outgoing - [0:0]
[4345:351743] -A POSTROUTING -m comment --comment "cali:O3lYWMrLQYEMJtB5" -j cali-POSTROUTING
[0:0] -A cali-POSTROUTING -m comment --comment "cali:ggLCSZ9_r9uXnHIo" -m comment --comment "BPF loopback SNAT" -j MASQUERADE --random-fully
[4345:351743] -A cali-POSTROUTING -m comment --comment "cali:THrmnLhAi3cxMLBO" -j cali-fip-snat
[4345:351743] -A cali-POSTROUTING -m comment --comment "cali:ez7mOi3T8N6rtIlJ" -j cali-nat-outgoing
[0:0] -A cali-POSTROUTING -o vxlan-v6.calico -m comment --comment "cali:i9aA9QlUgUVXqa4K" -m addrtype ! --src-type LOCAL --limit-iface-out -m addrtype --src-type LOCAL -j MASQUERADE --random-fully
[281:22480] -A cali-nat-outgoing -m comment --comment "cali:k9SjE1bWVYbIZgCm" -j MASQUERADE --random-fully
COMMIT
# Completed on Fri Mar 22 23:49:09 2024

note - this has been redeployed (should be same config), so you'll see different pod / ipam block assignments so here's the show-status as well:
bird v4 status
+-------+-------------------+---------------+---------------------+---------------------+---------------------+
| READY |      VERSION      |    ROUTEID    |     SERVERTIME      |      LASTBOOT       |    LASTRECONFIG     |
+-------+-------------------+---------------+---------------------+---------------------+---------------------+
| true  | v0.3.3+birdv1.6.8 | <IP_ADDRESS> | 2024-03-22 23:51:08 | 2024-03-22 23:42:59 | 2024-03-22 23:42:59 |
+-------+-------------------+---------------+---------------------+---------------------+---------------------+

bird v4 BGP peers
+--------------+-----------+-------+-------+----------+
| PEER ADDRESS | PEER TYPE | STATE | SINCE | BGPSTATE |
+--------------+-----------+-------+-------+----------+
+--------------+-----------+-------+-------+----------+

bird v4 routes
+-------------+----------+-------+-------------+---------+
| DESTINATION | GATEWAY  | IFACE | LEARNEDFROM | PRIMARY |
+-------------+----------+-------+-------------+---------+
| <IP_ADDRESS>/0   | <IP_ADDRESS> | eth0  | kernel1     | *       |
| <IP_ADDRESS>/32 | N/A      | eth0  | kernel1     | *       |
| <IP_ADDRESS>/24 | N/A      | eth0  | direct1     | *       |
| <IP_ADDRESS>/32 | N/A      | eth0  | kernel1     | *       |
+-------------+----------+-------+-------------+---------+

bird v6 status
+-------+-------------------+---------------+---------------------+---------------------+---------------------+
| READY |      VERSION      |    ROUTEID    |     SERVERTIME      |      LASTBOOT       |    LASTRECONFIG     |
+-------+-------------------+---------------+---------------------+---------------------+---------------------+
| true  | v0.3.3+birdv1.6.8 | <IP_ADDRESS> | 2024-03-22 23:51:08 | 2024-03-22 23:42:59 | 2024-03-22 23:42:59 |
+-------+-------------------+---------------+---------------------+---------------------+---------------------+

bird v6 BGP peers
+----------------+-----------+-------+----------+-------------+
|  PEER ADDRESS  | PEER TYPE | STATE |  SINCE   |  BGPSTATE   |
+----------------+-----------+-------+----------+-------------+
| fd11::10:0:0:3 | Mesh      | up    | 23:44:01 | Established |
| fd11::10:0:0:4 | Mesh      | up    | 23:43:29 | Established |
+----------------+-----------+-------+----------+-------------+

bird v6 routes
+-------------------------+--------------------------+-----------------+-------------+---------+
|       DESTINATION       |         GATEWAY          |      IFACE      | LEARNEDFROM | PRIMARY |
+-------------------------+--------------------------+-----------------+-------------+---------+
| ::/0                    | fe80::215:5dff:fe01:8013 | eth0            | kernel1     | *       |
| fd00::10:244:c:e7c5/128 | N/A                      | cali9afddb189c7 | kernel1     | *       |
| fd00::10:244:c:e7c4/128 | N/A                      | cali75db6953aa7 | kernel1     | *       |
| fd00::10:244:c:e7c0/122 | N/A                      | blackhole       | static1     | *       |
| fd00::10:244:c:e7c0/122 | N/A                      | blackhole       | kernel1     |         |
| fd00::10:244:c:e7c0/128 | N/A                      | vxlan-v6.calico | direct1     | *       |
| fd00::10:244:c:e7c3/128 | N/A                      | califde329b9f1d | kernel1     | *       |
| fd00::10:244:c:e7c2/128 | N/A                      | caliced6f8125e5 | kernel1     | *       |
| fd00::10:244:2:e200/122 | fd11::10:0:0:4           | eth0            | kernel1     | *       |
| fd00::10:96:0:c119/128  | 2001:db8::1              | bpfin.cali      | kernel1     | *       |
| 2001:db8::1/128         | N/A                      | bpfin.cali      | kernel1     | *       |
| fd00::10:244:e:d680/122 | fd11::10:0:0:3           | eth0            | kernel1     | *       |
| fd00::10:96:0:812d/128  | 2001:db8::1              | bpfin.cali      | kernel1     | *       |
| fd00::10:96:0:62ce/128  | 2001:db8::1              | bpfin.cali      | kernel1     | *       |
| fd00::10:96:0:1/128     | 2001:db8::1              | bpfin.cali      | kernel1     | *       |
| fd00::10:96:0:a/128     | 2001:db8::1              | bpfin.cali      | kernel1     | *       |
| fd11::10:0:0:0/118      | N/A                      | eth0            | kernel1     | *       |
| fd11::10:0:0:5/128      | N/A                      | eth0            | direct1     | *       |
+-------------------------+--------------------------+-----------------+-------------+---------+

@brentmjohnson I am able to reproduce this issue. But the issue is specific to ICMPv6. I tested tcp and it works. We will be fixing this soon. Thanks.

Thanks for confirming. In cluster DNS seemed to proxy as expected. I will validate for TCP / UDP. Let me know if you expect any other protocols may need specific testing.

The issue is only with ICMPv6.

I did identify one other issue / behavior in the current implementation in response forwarding of SNAT'ed requests.  I observed some fragmentation of response packets from the external service.  They looked like this in tcpdump on the node performing the SNAT'ing:
20:39:00.462276 IP6 k8s-lb > k8s-control-2: frag (1232|158)
20:39:03.918839 IP6 k8s-lb > k8s-control-2: frag (0|1232) http > 25373: Flags [.], seq 1:1201, ack 78, win 256, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 1200: HTTP: HTTP/1.1 200 OK

These appear to be dropped / not forwarded.  Is it expected ipv6 fragment forwarding should be handled in the ipv6 eBPF SNAT implementation? This is somewhat related to ICMPv6 as well as re RFC 2460 ICMP is used to notify the upstream in certain situations of fragment reassembly errors.

Thanks all, I will re-test once a dev image is available. Any feedback on expected level of support for forwarding of fragmented payloads?

@brentmjohnson calico/node:v3.27.3-3-g547edf833d4c should carry the fix. We just missed the 3.27.3 release, but this is essentially 3.27.3 + the fix. Let us know if it works for you and if it also fixed the fragmentation. If not, lets open another issue for that only :pray:

confirmed SNAT / MASQ of ICMP6 from pod network CIDR to external services in the node network CIDR works as expected now in calico/node:v3.27.3-3-g547edf833d4c

@brentmjohnson Thanks for confirming.


Errors running test on 11.3

2021-05-24 12:30:07,228 - WARNING - photosdb.py - 97 - WARNING: This module has only been tested with macOS versions [10.12, 10.13, 10.14, 10.15, 10.16, 11.0, 11.1, 11.2]: you have Darwin, OS version: 11.3
I updated and ran the tests on my M1 mini. Some errors seen. Log attached
testrun.txt

Thanks!  I'll take a look and see what I can figure out.  My machine running Big Sur has died so I don't have a way to test...will see if I can figure out what's going on then send you an update.

Looks like the exiftool process closed while osxphotos was trying to use it.  Can you try this to see if the test fails every time or if something weird happened on this particular run:
python3 -m pytest tests/test_template.py::test_exiftool_template

Running the individual test works and does not return any errors. However running all of the tests via "pytest" still results in error -
    command_str += (
        b"\n".join([c.encode("utf-8") for c in commands])
        + b"\n"
        + filename
        + b"\n"
        + b"-execute\n"
    )

    # send the command

  self._process.stdin.write(command_str)

E       ValueError: write to closed file
osxphotos/exiftool.py:288: ValueError
============================================================== warnings summary ==============================================================
tests/test_cli.py::test_osxphotos
tests/test_cli.py::test_osxphotos
/Users/nsankar/projects/osxphotos/.venv/lib/python3.9/site-packages/bitstring-3.1.7-py3.9.egg/bitstring.py:2: DeprecationWarning: invalid escape sequence \
-- Docs: https://docs.pytest.org/en/stable/warnings.html
========================================================== short test summary info ===========================================================
FAILED tests/test_template.py::test_exiftool_template - ValueError: write to closed file

I've managed to reproduce this but not sure yet why it's happening. I believe it's related to the fix for #449 and is a problem with test setup, not an actual problem with osxphotos. But still need to do more testing.

I've confirmed the functionality this test is testing actually works as expected.  The problem also seems to only occur when the following tests are run in order:

tests/test_cli.py
tests/test_exiftool.py
tests/test_template.py

The ExifTool module uses a singleton pattern and a module-level global variable to track state so I suspect one of these tests is somehow affecting the state.  All theses tests run fine if run in different order or individually.

So I think it would be ok to mark as 11.3 is supported as well and perhaps change the order of the tests might be ok.

I think I found & fixed the problem. I updated supported versions for 11.3 in release v0.42.26


ParsedDockerfile's parsing of FROM lines doesn't handle arguments

Given a Dockerfile with a line like:
FROM --platform=linux/amd64 openjdk:8u252-jre

you will get warnings in the log that look like:
09:06:07.355 [tc-okhttp-stream-748761773] ERROR com.github.dockerjava.api.async.ResultCallbackTemplate - Error during callback
com.github.dockerjava.api.exception.BadRequestException: {"message":"invalid reference format"}

	at com.github.dockerjava.okhttp.OkHttpInvocationBuilder.execute(OkHttpInvocationBuilder.java:283)
	at com.github.dockerjava.okhttp.OkHttpInvocationBuilder.lambda$executeAndStream$4(OkHttpInvocationBuilder.java:317)
	at java.lang.Thread.run(Thread.java:748)
09:06:07.355 [main] WARN org.testcontainers.images.builder.ImageFromDockerfile - Unable to pre-fetch an image (--platform=linux/amd64) depended upon by Dockerfile - image build will continue but may fail. Exception message was: {"message":"invalid reference format"}

because ParsedDockerfile's regex doesn't handle parameters.

Ah, thanks for reporting. I’ll work on a fix.