0.0.24 crashes when creating Policy Fragment with LIP

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version
Terraform v1.2.8
Affected Resource(s)

pingfederate_v0.0.24

Terraform Configuration Files

resource "pingfederate_authentication_policy_fragment" "first_factor" {
  name        = "FirstFactor"
  description = "Used for CIAM - First Factor"
  inputs {
    id = pingfederate_authentication_policy_contract.fragment_subject.id
  }
  outputs {
    id = pingfederate_authentication_policy_contract.facile_default.id
  }

  root_node {
    action {
      type = "AUTHN_SOURCE"
      authentication_source {
        type = "IDP_ADAPTER"
        source_ref {
          id = pingfederate_idp_adapter.ciam_html_form.id
        }
      }
      attribute_rules {
        items {
          attribute_name = "policy.action"
          condition = "EQUALS_CASE_INSENSITIVE"
          expected_value = "identity.registration"
          result = "Register"
        }
        fallback_to_success = true
      }
    }
    children {
      action {
        type    = "DONE"
        context = "Fail"
      }
    }
    children {
      action {
        type    = "LOCAL_IDENTITY_MAPPING"
        context = "Register"
        local_identity_ref {
          id = "regIdentityProfile"
        }
        outbound_attribute_mapping {
            attribute_contract_fulfillment {
              key_name = "ImmutableID"
              source {
                  type = "LOCAL_IDENTITY_PROFILE"
                  id = "regIdentityProfile"
              }
              value = "ImmutableID"
            }
            attribute_contract_fulfillment {
              key_name = "mail"
              source {
                  type = "LOCAL_IDENTITY_PROFILE"
                  id = "regIdentityProfile"
              }
              value = "email"
            }
            attribute_contract_fulfillment {
              key_name = "firstName"
              source {
                  type = "LOCAL_IDENTITY_PROFILE"
                  id = "regIdentityProfile"
              }
              value = "firstName"
            }
            attribute_contract_fulfillment {
              key_name = "lastName"
              source {
                  type = "LOCAL_IDENTITY_PROFILE"
                  id = "regIdentityProfile"
              }
              value = "lastName"
            }
            attribute_contract_fulfillment {
              key_name = "subject"
              source {
                  type = "LOCAL_IDENTITY_PROFILE"
                  id = "regIdentityProfile"
              }
              value = "username"
            }
            attribute_contract_fulfillment {
              key_name = "SAML_AUTHN_CTX"
              source {
                  type = "LOCAL_IDENTITY_PROFILE"
                  id = "regIdentityProfile"
              }
              value = "registration"
            }
            issuance_criteria {}
          }
        }
      }
    }

  }

Debug Output
https://gist.github.com/cprice-ping/cae93f775adf0e3e291f50ce7c873440
Panic Output
https://gist.github.com/cprice-ping/54b1604d6ebb7177176297e905476a44
Expected Behavior
Not crashing
Actual Behavior
Provide crashes when adding the Fragment
Steps to Reproduce

Create resource for Fragment with LOCAL_IDENTITY_PROFILE
terraform apply

Important Factoids
N/A
References

#0000

hi @cprice-ping
The empty issuance_criteria {} you have is whats causing the issue, ill add a fix and for this shortly but you will be able to work around it without the empty issuance criteria.

Thanks for the quick workaround - things are not crashing without that line.
Removing it produces regular TF errors about the resource definition -- I'm working though the complexity of these PF APIs (and translating all the Postman that I currently do).

yeah the API can be a bit of a beast, I know a few clients who will run the pf container locally configure the resources (manually) but then import them to help get the TF config.

I do it with this -- https://facile.pingidentity.cloud -- it's a NodeJS app that does Postman, fires of a Helm chart that's a wrapper around the ping-devops chart that has a whole bunch more Postman and things end up wired.
It's built to handle Nothing --> Something, but doesn't handle change like TF does -- that's why I'm converting it all into HCL with the help of your provider

I think you have another bug in this piece (maybe on Policy as well) - in Postman, you don't have to define anything in the inbound_mapping if this is not a Registration action:
"inboundMapping": {
                        "attributeSources": [],
                        "attributeContractFulfillment": {},
                        "issuanceCriteria": {
                            "conditionalCriteria": []
                        }
                    },

The Provider fails this either if it's omitted or if you construct as above.
I'm getting around it like this
      action {
        type    = "LOCAL_IDENTITY_MAPPING"
        context = "Register"
        local_identity_ref {
          id = "regIdentityProfile"
        }
        inbound_mapping {
          attribute_contract_fulfillment {
            key_name = "username"
            source {
              type = "NO_MAPPING"
            }
          }
        }

I don't know yet if this breaks the Policy when it fires (Policy API is worse than Fragments)

hi @cprice-ping do you have a full example of the resource your creating with the inboundMapping (postman or hcl)?

Sure -- Here's the Postman body to /authenticationPolicies/fragments:
https://gist.github.com/cprice-ping/7c4c6b36344e3c723e8ae7e595b9816e
And the HCL I'm using to replicate the same:
https://gist.github.com/cprice-ping/87798ded05cd837bfd4d6a051150d88f

hey @cprice-ping any chance i can get the config for all the other referenced (idp adapter, local identity profile, policy contracts etc) resources - i have no real way of creating the policy without them. 🙏

It's a touch more complicated - I think you're missing LIPs in the Provider, so I have a k8s Job that runs a Postman collection to add those bits.
I can add you to the repo that has the entire config set (PingOne \ PF \ Helm \ k8s) that I'm working on (Note: this is my first attempt at TF - I'm sure there's better ways that I haven't gotten to yet)

Yeah i noticed the missing resource (can you raise a new issue to support it) as this one is getting abit bloated.
I was able to deploy a super stripped down version of the policy fragement with my local dev provider version:

resource "pingfederate_authentication_policy_fragment" "first_factor" {
  name        = "FirstFactor"
  description = "Used for CIAM - First Factor"
  inputs {
    id = pingfederate_authentication_policy_contract.example.id
  }
  outputs {
    id = pingfederate_authentication_policy_contract.example2.id
  }

  root_node {
    action {
      type = "AUTHN_SOURCE"
      authentication_source {
        type = "IDP_ADAPTER"
        source_ref {
          id = pingfederate_idp_adapter.example.id
        }
      }
      attribute_rules {
        items {
          attribute_name = "policy.action"
          condition      = "EQUALS_CASE_INSENSITIVE"
          expected_value = "identity.registration"
          result         = "Register"
        }
        fallback_to_success = true
      }
    }
    children {
      action {
        type    = "DONE"
        context = "Fail"
      }
    }
    children {
      action {
        type    = "LOCAL_IDENTITY_MAPPING"
        context = "Register"
        local_identity_ref {
          id = "JJDMGnVqbexJbii0"
        }
        inbound_mapping {
        }
        outbound_attribute_mapping {
          attribute_contract_fulfillment {
            key_name = "subject"
            source {
              type = "LOCAL_IDENTITY_PROFILE"
              id   = "JJDMGnVqbexJbii0"
            }
            value = "foo"
          }
        }
      }
    }
    children {
      action {
        type    = "LOCAL_IDENTITY_MAPPING"
        context = "Success"
        local_identity_ref {
          id = "JJDMGnVqbexJbii0"
        }
        inbound_mapping {
          attribute_contract_fulfillment {
            key_name = "pf.local.identity.unique.id"
            source {
              type = "ADAPTER"
              id   = pingfederate_idp_adapter.example.id
            }
            value = "username"
          }
        }
        outbound_attribute_mapping {
          attribute_contract_fulfillment {
            key_name = "subject"
            source {
              type = "LOCAL_IDENTITY_PROFILE"
              id   = "JJDMGnVqbexJbii0"
            }
            value = "foo"
          }
        }
      }
    }
  }
}

which produced:
{
      "id": "FirstFactor",
      "name": "First_Factor",
      "description": "Used for Customer First Factor",
      "rootNode": {
        "action": {
          "type": "AUTHN_SOURCE",
          "authenticationSource": {
            "type": "IDP_ADAPTER",
            "sourceRef": {
              "id": "example",
              "location": "https://localhost:9999/pf-admin-api/v1/idp/adapters/example"
            }
          },
          "attributeRules": {
            "items": [
              {
                "attributeName": "policy.action",
                "condition": "EQUALS_CASE_INSENSITIVE",
                "expectedValue": "identity.registration",
                "result": "Register"
              }
            ],
            "fallbackToSuccess": true
          }
        },
        "children": [
          {
            "action": {
              "type": "DONE",
              "context": "Fail"
            }
          },
          {
            "action": {
              "type": "LOCAL_IDENTITY_MAPPING",
              "context": "Register",
              "localIdentityRef": {
                "id": "JJDMGnVqbexJbii0",
                "location": "https://localhost:9999/pf-admin-api/v1/localIdentity/identityProfiles/JJDMGnVqbexJbii0"
              },
              "inboundMapping": {
                "attributeSources": [],
                "attributeContractFulfillment": {},
                "issuanceCriteria": {
                  "conditionalCriteria": []
                }
              },
              "outboundAttributeMapping": {
                "attributeSources": [],
                "attributeContractFulfillment": {
                  "subject": {
                    "source": {
                      "type": "LOCAL_IDENTITY_PROFILE",
                      "id": "JJDMGnVqbexJbii0"
                    },
                    "value": "foo"
                  }
                },
                "issuanceCriteria": {
                  "conditionalCriteria": []
                }
              }
            }
          },
          {
            "action": {
              "type": "LOCAL_IDENTITY_MAPPING",
              "context": "Success",
              "localIdentityRef": {
                "id": "JJDMGnVqbexJbii0",
                "location": "https://localhost:9999/pf-admin-api/v1/localIdentity/identityProfiles/JJDMGnVqbexJbii0"
              },
              "inboundMapping": {
                "attributeSources": [],
                "attributeContractFulfillment": {
                  "pf.local.identity.unique.id": {
                    "source": {
                      "type": "ADAPTER",
                      "id": "example"
                    },
                    "value": "username"
                  }
                },
                "issuanceCriteria": {
                  "conditionalCriteria": []
                }
              },
              "outboundAttributeMapping": {
                "attributeSources": [],
                "attributeContractFulfillment": {
                  "subject": {
                    "source": {
                      "type": "ADAPTER",
                      "id": "example"
                    },
                    "value": "sub"
                  }
                },
                "issuanceCriteria": {
                  "conditionalCriteria": []
                }
              }
            }
          }
        ]
      },
      "inputs": {
        "id": "bekG2cjWnDT4nx4w",
        "location": "https://localhost:9999/pf-admin-api/v1/authenticationPolicyContracts/bekG2cjWnDT4nx4w"
      },
      "outputs": {
        "id": "p5VXoc0W9v78c8Vq",
        "location": "https://localhost:9999/pf-admin-api/v1/authenticationPolicyContracts/p5VXoc0W9v78c8Vq"
      }
    },
    {
      "id": "GrqI8SCfZMwXOkhiKdKWKygNW",
      "name": "FirstFactor",
      "description": "Used for CIAM - First Factor",
      "rootNode": {
        "action": {
          "type": "AUTHN_SOURCE",
          "authenticationSource": {
            "type": "IDP_ADAPTER",
            "sourceRef": {
              "id": "example",
              "location": "https://localhost:9999/pf-admin-api/v1/idp/adapters/example"
            }
          },
          "attributeRules": {
            "items": [
              {
                "attributeName": "policy.action",
                "condition": "EQUALS_CASE_INSENSITIVE",
                "expectedValue": "identity.registration",
                "result": "Register"
              }
            ],
            "fallbackToSuccess": true
          }
        },
        "children": [
          {
            "action": {
              "type": "DONE",
              "context": "Fail"
            }
          },
          {
            "action": {
              "type": "LOCAL_IDENTITY_MAPPING",
              "context": "Register",
              "localIdentityRef": {
                "id": "JJDMGnVqbexJbii0",
                "location": "https://localhost:9999/pf-admin-api/v1/localIdentity/identityProfiles/JJDMGnVqbexJbii0"
              },
              "inboundMapping": {
                "attributeSources": [],
                "attributeContractFulfillment": {},
                "issuanceCriteria": {
                  "conditionalCriteria": []
                }
              },
              "outboundAttributeMapping": {
                "attributeSources": [],
                "attributeContractFulfillment": {
                  "subject": {
                    "source": {
                      "type": "LOCAL_IDENTITY_PROFILE",
                      "id": "JJDMGnVqbexJbii0"
                    },
                    "value": "foo"
                  }
                },
                "issuanceCriteria": {
                  "conditionalCriteria": []
                }
              }
            }
          },
          {
            "action": {
              "type": "LOCAL_IDENTITY_MAPPING",
              "context": "Success",
              "localIdentityRef": {
                "id": "JJDMGnVqbexJbii0",
                "location": "https://localhost:9999/pf-admin-api/v1/localIdentity/identityProfiles/JJDMGnVqbexJbii0"
              },
              "inboundMapping": {
                "attributeSources": [],
                "attributeContractFulfillment": {
                  "pf.local.identity.unique.id": {
                    "source": {
                      "type": "ADAPTER",
                      "id": "example"
                    },
                    "value": "username"
                  }
                },
                "issuanceCriteria": {
                  "conditionalCriteria": []
                }
              },
              "outboundAttributeMapping": {
                "attributeSources": [],
                "attributeContractFulfillment": {
                  "subject": {
                    "source": {
                      "type": "LOCAL_IDENTITY_PROFILE",
                      "id": "JJDMGnVqbexJbii0"
                    },
                    "value": "foo"
                  }
                },
                "issuanceCriteria": {
                  "conditionalCriteria": []
                }
              }
            }
          }
        ]
      },
      "inputs": {
        "id": "bekG2cjWnDT4nx4w",
        "location": "https://localhost:9999/pf-admin-api/v1/authenticationPolicyContracts/bekG2cjWnDT4nx4w"
      },
      "outputs": {
        "id": "p5VXoc0W9v78c8Vq",
        "location": "https://localhost:9999/pf-admin-api/v1/authenticationPolicyContracts/p5VXoc0W9v78c8Vq"
      }
    }

notice the empty inbound mapping

When I do that, I get this error:
cprice@cprice-r Facile-PingFed % terraform apply --auto-approve
╷
│ Error: Insufficient attribute_contract_fulfillment blocks
│
│   on facile-pingfed-policy.tf line 198, in resource "pingfederate_authentication_policy_fragment" "first_factor":
│  198:         inbound_mapping {}
│
│ At least 1 "attribute_contract_fulfillment" blocks are required.

I'll have to do a better comparison to see what I've got mis-stated in the resource
I have a running list of things that aren't in your Provider - I'm getting around it with the k8s jobs I push in to run Postman. I didn't want to flood you with Issues :) There's an issues.md in the root of my repo

you would need to be a running a local dev build of the provider for it to work, its a change of behaviour that will be in the next release.


Encode Java types natively

Currently, several Java types in SemanticDB have weird encodings

primitive types: scala/Int#, scala/Double#, ...
array types: scala/Array#
wildcards: type ref with symbol local_wildcard

See spec https://github.com/scalameta/scalameta/blob/master/semanticdb/semanticdb3/semanticdb3.md#java-type
A core principle of Scalameta is to encode things for what they are so it might be an improvement to introduce native SemanticDB encodings for those types

primitive types: PrimitiveType(primitive: Primitive)
array types: ArrayType(tpe: Type)
wildcard types: WildcardType(tpe: Type, lower: Type, upper: Type)

I'm not 100% convinced this is still worth it, so it needs further validation. The biggest problem I can think of is: what do we in Scala? We have primarily two options:

Do the same in Java and Scala where possible. This has the benefit of consistency but the cost increasing the surface of the Scala type system.
Keep the current Scala encoding unchanged. This has the benefit of having Scala signatures resemble closer to the Scala compiler at the cost of higher inconsistency between Java and Scala.

@olafurpg I looked into this ticket, and I agree that it seems like a significant change that's not necessarily a crystal clear win. While I'm not against experimentation (and I'm certainly fond of conceptual purity, which this ticket advocates for), the cost of the experiment seems pretty high.
Concretely: I would prefer to keep the current Scala encoding unchanged (so that both Java and Scala represent their language features natively). Unfortunately, this means that unless we significantly improve the diff facilities in our expect tests, we're going to see a lot of spurious discrepancies (which is unacceptable, in my opinion). While I could certainly go ahead and introduce new types just for fun, spending several hours on diff facilities doesn't sound like fun (I did that way too much in Rsc, so at this point this kind of work isn't very enjoyable for me).
Therefore, since this ticket doesn't look like a blocker for our Rsc work, I'll be unassigning it from myself for the time being. Eventually, we'll start working on Java interop in Rsc, so it is likely that I won't be able to escape this fate, but for now I'd like to delay these fun times :)
To make sure we don't miss any blockers, I'll assign this ticket to you. If this ticket is also not on the critical path for your current work, please feel free to unassign - both from yourself and the 4.0.0-RC1 milestone.

You know, I could give it a try if we stop emitting SymbolInformation for Java compilation units in semanticdb-scalac (https://github.com/scalameta/scalameta/issues/1737). Then semanticdb-javac becomes the only source of truth, and we don't need to reconcile it with what Scalac thinks of Java types.

After sleeping on this and chatting with @olafurpg, I'm inclined to unassign this ticket from 4.0.0-RC1.
This is a big change coming up at the 11th hour of the release, so it better be really important like the static inner class symbol format change. However, it just isn't, since it doesn't fix any blockers for our use cases, and it doesn't add any fundamental capabilities.

I agree with you @xeno-by that this change does not carry it's weight. I propose we close the ticket as "wontfix".

Let's keep this open for the time being. I suggest that when I'm back from vacation we revisit the Scalameta roadmap and then trim the tickets appropriately, not limiting ourselves to just this one.


Custom breadcrumb titles (text and parameters)

Is it possible to create breadcrumb names which are combination of props.params and text? For instance for a path like 'history/:serialNum' creating a breadcrumb in this format History(:serialNum)?

+1

So apparently this is possible but I think the documentation could use some work.
I'm not associated with the project, just another appreciative consumer. :)
Looks like you can decorate routes that have params with prettifyParam={(param)=>'History (' + param + ')'}
https://github.com/svenanders/react-breadcrumbs/blob/master/index.jsx#L142

Yeah... I should really create better docs... 👍

You can also use the displayName() function documented in #96 :)


Can you make a sora (diffusion transformer) tutorial similar to llama2.c?

Can you make a sora (diffusion transformer) tutorial similar to llama2.c?
@karpathy As the title says I would like to ask you to create a teaching project with training and inference functions.

You might want to start here: https://keras.io/examples/generative/ddpm/


Restructure landing page

In https://github.com/mesh-adaptation/docs/issues/52#issuecomment-2522774720_ we agreed to make https://mesh-adaptation.github.io/ a static landing page that would link to https://mesh-adaptation.github.io/docs, which are now automatically built and deployed. So we need to update https://mesh-adaptation.github.io/ accordingly.
So the website tree would then look something like
https://mesh-adaptation.github.io/
    ├─ docs/
    │  ├─ animate
    │  ├─ goalie
    │  ├─ movement
    │  └─ UM2N
    ├─ papers
    └─ ...

Or docs/papers etc.

@jwallwork23 in https://github.com/mesh-adaptation/mesh-adaptation.github.io/commit/ffc784bd451cde89e8986fe078446f4596e22223 I left everything as it is but just redirected all links to the new build at https://mesh-adaptation.github.io/docs/ now, so that we'd have working references etc.

@jwallwork23 in mesh-adaptation/mesh-adaptation.github.io@ffc784b I left everything as it is but just redirected all links to the new build at https://mesh-adaptation.github.io/docs/ now, so that we'd have working references etc.

Nice - that works for the time being.
For the landing page it'd be great to have four clickable boxes with the name of the package and its logo in it, where clicking is a link the appropriate part of the docs. Of course, we don't currently have any logos, so just the letter "A", "G", M", or "U" would be sufficient for now.


Update Get-CsOnlineUser.md

Updates for TPM 2.6.2

Docs Build status updates of commit 64af0a0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineUser.md
:white_check_mark:Succeeded
View (skype-ps)

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

Docs Build status updates of commit 5b9d336:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineUser.md
:bulb:Suggestion
View (skype-ps)
Details

skype/skype-ps/skype/Get-CsOnlineUser.md

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'some-xml-string' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

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

Docs Build status updates of commit 5b9d336:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineUser.md
:bulb:Suggestion
View (skype-ps)
Details

skype/skype-ps/skype/Get-CsOnlineUser.md

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'some-xml-string' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

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

@dariomws @tseward @get-itips

Docs Build status updates of commit 031fda4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineUser.md
:bulb:Suggestion
View (skype-ps)
Details

skype/skype-ps/skype/Get-CsOnlineUser.md

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'some-xml-string' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

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

Docs Build status updates of commit 0a6ecb4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Get-CsOnlineUser.md
:bulb:Suggestion
View (skype-ps)
Details

skype/skype-ps/skype/Get-CsOnlineUser.md

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'some-xml-string' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

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

Please move this information before the examples section and after the last sentence of the description, here:

I am ok once @dariomws suggestions are applied.

@isrumnon Please update the changes.


No every example (shows some instead, plus typo in wrong example)

Our every example is actually for some and has a typo:
https://www.prisma.io/docs/reference/api-reference/prisma-client-reference#get-all-user-records-where-all-posts-are-published-and-a-least-one-related-post-mentions-prisma

The every and some examples have been reused, and I think, in this case, we could cut on the scope for the example snippets.


Support ts-rest

Description
Generate handlers out of a ts-rest contract
import { fromTsRest } from '@mswjs/source/ts-rest'

fromTsRest(input)

I'm not sure if this issue should be on the Source repo or the ts-rest one. I'm taking the lead of the one for trpc.

Hi, @spence-novata. That's a good suggestion! But it belongs in a community package. As I mention in the docs, Source isn't designed to include all the integrations for possible API libraries. I want to encourage people creating their own packages and publishing those. Let me know if Source can expose something to make community packages easier.


arkade: 0.8.18 -> 0.8.19

Description of changes

https://github.com/alexellis/arkade/releases/tag/0.8.19
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 167173 run on aarch64-darwin 1

1 package built:

arkade


Bot occasionally fails to connect

It throws this error:
wss://gateway-1.discord.gg/3
[2016-03-28 13:42:37] [fail] WebSocket Connection Unknown - "" /3 0 websocketpp.transport:9 Timer Expired
[2016-03-28 13:42:37] [info] Error getting remote endpoint: system:9 (Bad file descriptor)
[2016-03-28 13:42:37] [error] handle_connect error: Timer Expired
[2016-03-28 13:42:37] [info] asio async_shutdown error: asio.ssl:336462100 (uninitialized)

Looks like it's trying to connect to an invalid gateway?

Possibly. Recently, I haven't seen gateway URLs that looks like this. It could've just been a weird artifact of pre-API endpoints.

aidoboy why do you add a issue to your own repository?

Because someone else might have useful input.

I think this one was an issue on Discord's end.


Upgrade AjaxControlToolkit dll from version 3.0.20820.0 to 16.1

I need to upgrade my ajaxcontroltoolkit dll versioned - 3.0.20820 with the latest version 16.1
Below are couple of controls/class, for which I am facing issue:

CollapsiblePanelExtender: property used: CollapsedCssClass & ExpandedCssClass

PasswordStrength: property used: Strength

CalendarExtender: property used: CalendarMode & Enum - CalendarModeType

Q. What can we use instead of above properties as they are not available in version - 16.1?

Hi @harshal-a ,
I checked the AJAX Control Toolkit v3.0.20820 and did not find any property you mentioned.
Would you please provide a link to that release?

Hi,
I do not have the link for that release. Below is the code snippet for your reference we have:
Public CollapsiblePanel As New AjaxControlToolkit.CollapsiblePanelExtender()
CollapsiblePanel.CollapsedCssClass = "cssclassname"
CollapsiblePanel.ExpandedCssClass = "cssclassname"
Similarly, for other classes/controls we have used their respective properties.
Thanks,
Harshal A.

Ok, maybe you can attach a DLL that you are using?

Sorry, I can't do that, The dll is on client machine and we are not allowed to do so.

@harshal-a
This is a screenshot of an assembly structure taken from a DLL that I downloaded from the official release at CodePlex:

I don't see any property that you mentioned.

Dll file type is not supported here.
Please refer the screen image with highlighted properties.

Dll file type is not supported here.

Please try uploading as a ZIP archive.

AjaxControlToolkit.zip
Oops, my bad.

@harshal-a
Thank you for providing this assembly.
It seems to be a custom build based on version 3.0.20820 of the toolkit.

There is only one property that can be replaced by the property of the same functionality in v 16.1:
CalendarExtender.CalendarMode can be replaced with CalendarExtender.DefaultView and corresponding enum is CalendarDefaultView.

There are no direct replacement for the rest of the properties you mentioned, so you have to write custom code to achieve the same functionality as you had before.


docs: update structure

introduce new documentation structure https://github.com/inveniosoftware/cookiecutter-invenio-module/issues/56
document user perspective
document signals (if not done)
document example app (if not done)

Document:

[ ] example application (what is the app demonstrating - the templates, error pages, menu, ...)
[ ] configuration (in particular BASE_TEMPLATE, ...)
[ ] usage guide:

[ ] menu/breadcrumb system and endpoints.
[ ] default bundles and what they provide
[ ] templates and their blocks + macros

End-user perspective:

What does the module provide, and how do I make simple changes (e.g. change logo etc).


link is not yet supported at line for default installation

Description
I receive an error "Error parsing markdown. Content: link is not yet supported at line: 117, column: 1" when editing the About page.
Steps to reproduce
Install TinaCMS via npx/yarn.
Expected result
The markdown should be fully rendered in the content view and you should be able to edit the markdown in the TinaCMS editor.
Actual result
You should see a red box in the TinaCMS content editor and you should see markdown markup as the content view.
Environment
Tinacms Package Versions

├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>

Tools

Tool
Version

Chrome
107.0.5304.110

macOS Ventura
13.0.1

node
19.0.1

npm
8.19.2

Can you narrow it down to a certain markdown file that's failing for you? If so, would you be able to provide the file?
From the error, It seems that you have a Markdown link nested in another element that isn't yet supported in Tina

@jamespohalloran It's the default about.md file that comes with the TinaCMS starter template: my-tina-app/content/pages/about.md. The issue is that it's the default behavior of a default file.
The about.md markdown is below:
---
title: "About"
blocks:
  - body: "## What is this?\n\nThis is a [TinaCMS](https://tina.io)-enabled Next.js app, so you can edit your content on a live page. In this project the Tina file-based CMS is used via GraphQL: it's powered by a schema that *you* define. It not only serves content from Markdown files in your repository, but it also generates TinaCMS forms for you automatically ✨.\n\n### Scope\n\n*   Run this project locally using local content within this repository.\n*   Connect to Tina Cloud to benefit from its GraphQL Content API.\n*   Deploy the site to visually edit your site.\n*   Invite collaborators.\n\n## Requirements\n\n*   Git\n*   [Node.js Active LTS](https://nodejs.org/en/about/releases/)\n*   Yarn\n\n## Fork this repository\n\n⚠⚠ Start by **forking** the repository and then pull it down to your computer. ⚠⚠\n\n## Install\n\n> ℹ This project uses `yarn` as a package manager, if `yarn` isn't installed on your machine, open a terminal and run `npm install -g yarn`\n\nInstall the project's dependencies:\n\n```\nyarn install\n```\n\n> ⚠ If you'd like to use `npm` beware that there is no `package-lock.json` so we can't guarantee the dependencies are the same for you.\n\n## Run the project locally\n\nTo run the local development server:\n\n```\nyarn dev\n```\n\nThis command starts the GraphQL server and the Next.js application in development mode. It also regenerates your schema types for TypeScript and GraphQL so changes to your `.tina` config are reflected immediately.\n\nOne of the most interesting aspects of the Tina Cloud Content API is that it doesn't actually require anything from the Cloud to work locally. Since Tina is by default a Git-backed CMS, everything can be run from your local filesystem via the CLI. :sunglasses:\n\nThis is ideal for development workflows and the API is identical to the one used in the cloud, so once you're ready to deploy your application you won't face any challenges there.\n\nOpen [`http://localhost:3000`](http://localhost:3000) in your browser to see your file-based content being loaded from the GraphQL API.\n\n## Edit content locally\n\nWe need to define some local environment variables in order to edit content with Tina.\n\nCopy `.env.example` to `.env`:\n\n```sh\ncp .env.example .env\n\n```\n\n`NEXT_PUBLIC_USE_LOCAL_CLIENT` should be set to `1`, other values can be ignored for now.\n\nRestart your server and visit [`http://localhost:3000/`](http://localhost:3000/`), and click \"enter edit mode\" in the top right hand corner, the same page is displayed but you can notice a pencil icon at the bottom left corner.\n\nClick to open Tina's sidebar which displays a form with fields you can edit and see update live on the page.\nSince we're working locally, saving results in changes to your local filesystem.\n\nFrom here, you're ready to start building your own project, to read a little bit about how this project is structured, and how to modify it to make it your own,\nread the [folder structure](#starter-structure) section below.\n\nWhen you're ready to deploy your site, read on about how you can connect to Tina Cloud and make authenticated changes via our Cloud API.\n\n> **NOTE:** In this project there are two way to enter edit mode. You can click the \"enter edit mode button\" or visit [`/admin`](http://localhost/admin). You can also disable the edit button by setting `NEXT_PUBLIC_SHOW_EDIT_BTN=0` in `.env`\n\n## Connect to Tina Cloud\n\nWhile the fully-local development workflow is the recommended way for developers to work,\nyou'll obviously want other editors and collaborators to be able to make changes on a hosted website with authentication.\n\n> ℹ Changes in edit mode show up on your home page after your site finishes a rebuild.\n\n## Register your local application with Tina Cloud\n\n1.  Visit [auth.tina.io](https://auth.tina.io/register), create an organization, and sign in. Make a note of your organization name.\n2.  Create a Tina Cloud app which connects to the GitHub repository you've just forked. Once your app is created, click on the app to get to the app settings and copy the client ID.\n\n## Connect your local project with Tina Cloud\n\nIn the `env.local` file set:\n\n*   `NEXT_PUBLIC_USE_LOCAL_CLIENT` to `0`.\n*   `NEXT_PUBLIC_ORGANIZATION_NAME` to your Tina Cloud organization name\n*   `NEXT_PUBLIC_TINA_CLIENT_ID` to the Client ID displayed in your Tina Cloud App.\n*   `NEXT_PUBLIC_SHOW_EDIT_BTN` to `0` or `1`, `0` means there is no \"enter edit mode\" and you will have to visit [`/admin`](http://localhost/admin) to enter edit mode.\n\nRestart your server and run `yarn dev` again.\n\nOpen [`http://localhost:3000/`](http://localhost:3000/`) and click \"enter edit mode\"\n\n![](/uploads/tina-cloud-authorization.png \"\")\n\nThis time a modal asks you to authenticate through Tina Cloud. Upon success, your edits will be sent to the cloud server (and subsequently to GitHub).\n\n#### Edit content\n\nMake some edits through the sidebar and click save.\nChanges are saved in your GitHub repository.\n\nNow that Tina Cloud editing is working correctly, we can deploy the site so that other team members can make edits too.\n\n> ℹ Gotcha: since your changes are being synced directly to Github, you'll notice that when your in non-\"edit\" mode your page still receive the unedited data from your local filesystem. This is mostly fine since editing with Tina Cloud is designed for hosted environments. But beware that changes to your schema may result in a mismatch between the Tina Cloud API and your local client.\n\n## Deploy\n\n### Vercel\n\n[![Deploy with Vercel](https://vercel.com/button \"\")](https://vercel.com/new/)\n\nConnect to your GitHub repository and set the same environment variables as the ones in your `env.local` file:\n\n```\nNEXT_PUBLIC_ORGANIZATION_NAME= <YOUR_ORGANIZATION>\nNEXT_PUBLIC_TINA_CLIENT_ID= <YOUR_CLIENT_ID>\n```\n\n![](/uploads/vercel-congratulations.png \"\")\n\n\U0001F389 Congratulations, your site is now live!\n\nYou can test that everything is configured correctly by navigating to `[your deployment URL]/`, click \"edit this site\",\nlog in to Tina Cloud, and making some edits. Your changes should be saved to your GitHub repository.\n\n### Netlify\n\n[![Deploy to Netlify](https://www.netlify.com/img/deploy/button.svg \"\")](https://app.netlify.com/start/)\n\nConnect to your GitHub repository, then:\n\n*   set the **build command** to `yarn build`,\n*   set the **publish directory**. To `.next/` .\n\n![](/uploads/netlify-build-settings.png \"\")\n\nClick on **advanced** to add the same environment variables as the ones in your `env.local` file:\n\n```\nNEXT_PUBLIC_ORGANIZATION_NAME= <YOUR_ORGANIZATION>\nNEXT_PUBLIC_TINA_CLIENT_ID= <YOUR_CLIENT_ID>\n```\n\n![](/uploads/netlify-advanced-build-settings.png \"\")\n\nCopy-paste your Organization ID and Client ID.\n\nOnce you're done, click \"Deploy site\".\n\nInstall the [\"Next on Netlify\" plugin](https://www.netlify.com/blog/2020/12/07/announcing-one-click-install-next.js-build-plugin-on-netlify/)\nin order to take advantage of server-side rendering and Next.js preview features.\n\nTrigger a new deploy for changes to take effect.\n\nYou can test that everything is configured correctly by navigating to `[your deployment URL]/`, click \"edit this site\",\nlog in to Tina Cloud, and making some edits. Your changes should be saved to your GitHub repository.\n\n***\n\n## Starter structure\n\nTina Cloud Starter is a [Next.js](https://nextjs.org) application. The file-based routing happens through the `pages` directory. To edit this site, navigate to the `/admin` route. This will cause you to go into edit mode where Tina is loaded. Tina is only loaded in edit mode so it will not effect the production bundle size.\n\n### `.tina/schema.ts`\n\nThis is where your schema is defined, when you make changes here you'll notice that the generated GraphQL API changes too. It's a good idea to run your GraphQL server while editing so you can see any breakages.\n\n> Tip: Visit the GraphQL GUI at `http://localhost:4001/altair` so you can see how changes to the schema are updated in GraphQL.\n\n### `pages/[filename].tsx`\n\nThis page can be seen at `http://localhost:3000/`, it loads the content from a markdown file which can be found in this repository at `/content/pages/home.md`. You can edit this page at by navigating to `http://localhost:3000/admin`.\n\nHead over to the [reference](/docs/tinacms-reference/) documentation to learn more about [defining a schema](/docs/schema/) or [querying with GraphQL](/docs/graphql/)\n\n### `pages/posts/[filename].tsx`\n\nThe posts are stored in the `content/posts` directory of this repository, and their routes are built with `getStaticPaths` dynamically at build time.\n\n### The `content` folder\n\nHere's where your actual content lives, you can control how content is stored from the `defineSchema` function, by default we use `markdown`.\n\n### `components`\n\nMost of the components in this project are very basic and are for demonstration purposes, feel free to replace them with something of your own!\n\n### `pages/_app.js`\n\nThe `_app.js` file is a feature in Next.js that allows you to wrap all of your routes in some specific logic which will be applied to every page. We're using it to wrap your site content in TinaCMS context. We do this so when data passes through, we can *hydrate* it so that it's editable in real time. You may notice that it's being loaded dynamically based on something called `EditState`, when you're in edit mode we'll load `TinaCMS` and all that it provides. When you're not in edit mode Tina stays out of the way so your builds stay lean.\n\nBy default we've toggle the `showEditButton` to `true`. You'll likely want to remove that option as it'll show for visitors to your site.\n\n### `pages/posts/[filename].tsx`\n\nThe posts are stored in the `content/posts` directory of this repository, and their routes are built with `getStaticPaths` dynamically at build time. You'll notice a couple of helper functions like `getStaticPropsForTina` and `staticRequest`. These are helper functions to make sure you're returning data from the local GraphQL server in a shape that Tina understands. Feel free to bring your own http client if you'd like. Read more about these helpers in the [Next.JS APIs documentation](/docs/tinacms-context/)\n\n### Creating your own pages\n\nFor now, TinaCMS works best when you:\n\n1.  Use `getStaticProps` for data\n2.  Return data from `getStaticProps` with `data`, `query`, and `variables` properties.\n3.  Wrap your `_app.js` in TinaCMS dynamically.\n\nAfter that, you're on your own. Go build something and share it with us on [Twitter](https://twitter.com/tina_cms).\nTo browse the docs and query our GraphQL API, run `yarn dev` in your Tina project and go to `http://localhost:4001/altair`.\n\n## Getting Help\n\nTina Cloud is in public alpha, you might face issues, to provide feedback or get help with any challenges you may have:\n\n*   Read the [Tina Cloud documentation](https://tina.io/docs/tina-cloud/).\n*   [Join our Discord](https://discord.gg/zumN63Ybpf).\n*   Visit the [community forum](https://community.tinacms.org/) to ask questions.\n*   Reach out to us on Twitter at [@tina\\_cms](https://twitter.com/tina_cms).\n*   [Email<EMAIL_ADDRESS>to schedule a call with our team and share more about your context and what you're trying to achieve.\n*   Get support through the chat widget on the Tina Cloud Dashboard\n\n## LICENSE\n\nLicensed under the [Apache 2.0 license](./LICENSE).\n"
    color: default
    _template: content
---


Marketplace implementation addresses

TOOL-2814
Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR introduces support for ZKSync implementations in the contract deployment process, enhancing the CustomContractForm to handle MarketplaceV3 deployments specifically for ZKSync chains.
Detailed summary

Added ZKSYNC_IMPLEMENTATIONS to define MarketplaceV3 addresses for specific chain IDs.
Updated CustomContractForm to conditionally deploy MarketplaceV3 only if the wallet chain is not a ZKSync chain.
Integrated ZKSYNC_IMPLEMENTATIONS into the deployment logic to fetch the appropriate implementation contract based on the chain ID.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Merge activity

Dec 20, 12:00 PM EST: The merge label 'merge-queue' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


Return variable dependency properties in the "get variables" API response

#2138  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nickgraz and the rest of your teammates on  Graphite


Update for breaking changes in command status

Mainly update for TimerStatus -> Status.

lgtm. perhaps you can wait for my big PR to save me from a rebase ><

I just merged mine. You need to rebase (hopefully just the go.mod file need to refresh)


Info, Labels and buttons icons property

Hello @GeraudBourdin , I have a question:
this can work for labels "icon" property? Or buttons "icons" etc?
if possible a example will'b great. :)
Thanks for this module.

hi Nuno,
I didn't found icon property for labels nor buttons UI elements. May be you meant image property for button element, right ?
Unfortunately, svgView as the name says it is a basic View not an image. As Button element need a string path or a blob you could simply do this like this :

and in your controller file :
var imageButton = svgView.createView({
image: "android.svg",
width: '50',
height: '50',
top: 0,
left: 0,
backgroundColor:'pink'
});
var blob = imageButton.toImage().media;
$.buttonSvg.setImage(blob);
i've just tried it, and it works. Don't know if it efficient enough but that a quick workaround.
Did i answered your question ?

@GeraudBourdin My bad, yes that answer my question, I will do some tests.
Thank you very much  for you quick answer :)

I've just made a readme.md for a quick doc. And i added this answer to it. Hope this will help :)


mjsxj09cm cam Streaming

I finally get my mjsxj09cm into HB. The current plug-in version inputs camera power on/off control and led. But not streaming. Is that possible enable video streaming?

Streaming would be possible but I cannot do it by myself since this is quite a complicated topic and I do not have the knowledge. Hence if someone with expertise could do that then it would be great!
For now unfortunately this is not possible.


Data streams are reconnecting with Hubble UI replicas set higher than 1

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Related to https://github.com/cilium/hubble-ui/issues/833, there no visibility on that issue since April. Setting the hubble.ui.replicas to a value higher than 1, breaks the Hubble UI frontend.

No response
Cilium Users Document

[ ] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hey we happen to have similar issue, as a workaround we have reduced the replica of hubble-ui replicas to 1 (previously it was 2)
cilium version : 1.14.12
Below hubble UI logs seen during the time of error in the UI "Data streams are reconnecting..."
`

2024-07-22 16:01:00
time="2024-07-22T14:01:00Z" level=error msg="first tick failed" channelId=6790d51...dcf0 component=StatusChecker error="context canceled" handler=ControlStream

2024-07-22 16:01:00

2024-07-22 16:01:02

2024-07-22 16:01:02

`

can you please help check on the root casue of this issue?
since its still a temporary workaround to reduce the hubble-ui replicas to 1

/nostale

Any updates on this issue?

I've noticed the same error during a connectivity test:
📋 Test Report [cilium-test-1]
❌ 1/54 tests failed (1/507 actions), 51 tests skipped, 0 scenarios skipped:
Test [check-log-errors]:
  ❌ check-log-errors/no-errors-in-logs/sandbox/kube-system/hubble-ui-56899d94c9-4qbrq (backend)
  [-] Scenario [check-log-errors/no-errors-in-logs]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-6rgw8 (cilium-agent)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-6rgw8 (config)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-6rgw8 (mount-cgroup)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-6rgw8 (apply-sysctl-overwrites)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-6rgw8 (mount-bpf-fs)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-6rgw8 (wait-for-node-init)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-6rgw8 (clean-cilium-state)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-6rgw8 (install-cni-binaries)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-node-init-bzgnh (node-init)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-node-init-zghrt (node-init)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-operator-d89b54ff7-cxvkr (cilium-operator)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-operator-d89b54ff7-xmzxd (cilium-operator)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-v8xzn (cilium-agent)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-v8xzn (config)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-v8xzn (mount-cgroup)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-v8xzn (apply-sysctl-overwrites)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-v8xzn (mount-bpf-fs)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-v8xzn (wait-for-node-init)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-v8xzn (clean-cilium-state)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/cilium-v8xzn (install-cni-binaries)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/hubble-relay-757c44c877-jdjcd (hubble-relay)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/hubble-ui-56899d94c9-4qbrq (frontend)]
  [.] Action [check-log-errors/no-errors-in-logs/sandbox/kube-system/hubble-ui-56899d94c9-4qbrq (backend)]
  ❌ Found 2 logs in sandbox/kube-system/hubble-ui-56899d94c9-4qbrq (backend) matching list of errors that must be investigated:
time="2024-11-21T07:48:45Z" level=error msg="failed to send server status notification: channel closed\n" channelId=543f0fb503af4d97 component=APIServer handler=ControlStream (1 occurrences)
time="2024-11-21T07:48:45Z" level=error msg="first tick failed" channelId=543f0fb503af4d97 component=StatusChecker error="context canceled" handler=ControlStream (1 occurrences)
```

Only one replica for the UI component.


assign clusters to clusterclaims

A ClusterClaim resource is created by a user when they want to claim a cluster from a ClusterPool. The ClusterClaim must be in the same namespace as the ClusterPool. When a cluster has been assigned to the ClusterClaim, the namespace field in the status will be filled out with the namespace where the ClusterDeployment for the cluster resides, and the NotReady condition will be set to False.
When reconciling a ClusterPool, the clusterpool controller will check for ClusterClaims that reference the ClusterPool and that do not have a cluster assigned. If there are ready clusters, the controller will set the .status.namespace field to the namespace of one of the ready clusters. If there are not enough ready clusters to fulfill all claims, the controller will prioritize the oldest claims. If a claim is not assigned a cluster, the NotReady condition will be set to True on the claim with a reason of NoClusters.
The clusterclaim controller has been added to handle reconciling ClusterClaims that have been assigned a cluster. For a claim with an assignment, the controller will check the ClusterDeployment to ensure that the cluster has not been assigned to a different claim. If it has, the the .status.namespace field of the ClusterClaim will be cleared. If the ClusterDeployment has not been associated with any claim, then the controller will update the ClusterDeployment to associated it with the ClusterClaim, completing the cluster assignment. When the ClusterClaim is deleted, the controller will delete the ClusterDeployment assigned  to the claim.
https://issues.redhat.com/browse/CO-1012

/hold
This builds on https://github.com/openshift/hive/pull/1060.

#1060 has merged.
/hold cance;l

#1060 has merged.
/hold cancel

Addressed code review feedback.

Moved the .status.namespace field of ClusterClaim to .spec.namespace. This preserves the cluster assignment if the ClusterClaim loses its status, say due to a restore from backup.
Changed terminology around cluster assignment. When the clusterpool controller sets the .spec.namespace field of a ClusterClaim, that is "assigning" the cluster to the ClusterClaim. When the clusterclaim controller sets the .spec.clusterPoolRef.claimName field of a ClusterDeployment, that is "claiming" the cluster.

/lgtm


Refactor of the Table component

Fixes #619
Summary

user can select charts with many records in the table

Details

Move charts checkboxes above table with survey results
Move charts above table with survey results
Adjust style of the charts container to fix gap between chart and table containers
Add dynamic rendering of the charts and table of the survey results

Test Plan (required)

yarn start
click show me more
select Fever or Behavioral

Suggestion
I think that show me more view is overloaded with 2 charts and survey results table. I would suggest conditional rendering based on user selection. If user select fever chart, we can hide table to make view let over loaded with content. Open for dialog!
Final Checklist

[x] For CoronaTracker, did you bump the version in package.json?

Update the second decimal for a major change
Update the third decimal for a minor change
Numbers can go past 9, e.g. 1.0.9 => 1.0.10
For more info, read about Semantic Versioning

[x] Did you add any new tests as necessary?
[x] Is your PR rebased off the most current master?
[x] Have you squashed all commits? (can be done at merge)
[x] Did you use yarn not npm? (important!)
[x] Did you use Material-UI wherever possible?
[x] Did you run yarn lint on the code?
[x] Did you run all of your most recent changes locally to make sure everything is working?

I like that suggestion! So perhaps going forward when you click "Show me More" you get the table by default, but can select either table, fever chart, or behavioral chart and display only one at a time?

I like that suggestion! So perhaps going forward when you click "Show me More" you get the table by default, but can select either table, fever chart, or behavioral chart and display only one at a time?

Yes, exactly.

Add dynamic rendering:


Traceroute

I think it would be in incredibly help to have Trace route in the tools section.
Originally posted by @tmcb82 in https://github.com/isontheline/pro.webssh.net/discussions/271

+1!

For @isontheline work :

http://opensource.apple.com/source/network_cmds/network_cmds-77/traceroute.tproj/

+1 on this, here's a good example from the HE Network Tools:

Their tool is capable of running IPv4 and IPv6 traceroutes for those cases when you enter a domain name instead of an IP on the input field.

Thank you @TCB13 👍
Traceroute implementation is not trivial but I bring up this issue in order to plan the roadmap

Thank you @TCB13 👍
Traceroute implementation is not trivial but I bring up this issue in order to plan the roadmap

Yes, I'm well aware of that, I just wanted to share the HE screenshot as their app is really quite nice.

I agree, nice and clear design
I hope I will be able to implement it "soon"

A "simple" traceroute is now available inside the latest beta release : https://testflight.apple.com/join/QSrBK59z


filters.api.ip_list_in_use (Code: 10031)

Seems to be an issue where the ip list cannot be deleted. Cloudflare seems to think it is used in a rule somewhere, but I have checked all rules and it is not being used.
I have tried using the API directly to delete the list, using crowdsec-cloudflare-bouncer -d, deleting in the web interface, all to no avail. Always get the same error. I have also checked all my zones rules via the API and the list is not referenced anywhere.
It seems others have faced a similar issue as reported in the cloudflare community:
https://community.cloudflare.com/t/cant-delete-the-ip-list-filters-api-ip-list-in-use/501307

We had this before and the user had to contact cloudflare support as there is a long standing bug on their end. If I recall it was something like if you delete a zone when a list is in use it will become permanently in use.
We use the same API as you manually called so if you cannot see it then there no much we can do other than ask you to contact cloudflare support.

Cloudflare support do nothing about that...
They don't care at all... It's like those list are mostly unsupported...
And since few weeks I have so much rate limit...
It was working fine in 2022, but recently.... useless... as updating your list every hour is not very effective...

Yeah, I agree. In our experience they dont seem to want to support it as the suggestion we have on "fixes" have been to move to workers which is rather limited and can easily fall into a paid plan.

Unfortunate news. I guess this bouncer is essentially useless for me as the list has reached 10k items and whenever the bouncer runs everything seems to work, but nothing is actually ever updated. For example, I've used the exclude "ssh" items, but the list remains at 10k even though a lot of decisions should have been removed.  So it seems the list is no longer updating.
I've emailed cloudflare support, but I'm not expecting much with a free account :slightly_frowning_face:
time="02-05-2023 10:39:01" level=info msg="Starting crowdsec-cloudflare-bouncer v0.2.1-6b30687c25027607083926cb2112dd06e04dae59"
time="02-05-2023 10:39:01" level=info msg="Using API key auth"
time="02-05-2023 10:39:01" level=debug msg="req-api: GET http://crowdsec:8080/v1/decisions/stream?scenarios_not_containing=ssh&scopes=ip%2Crange%2Cas%2Ccountry&startup=true"
time="02-05-2023 10:39:02" level=info msg="using existing  ip list crowdsec_block 9axxxxxxxx" account_id=ffxxxxxxxxx
time="02-05-2023 10:39:02" level=debug msg="resp-api: http 200"
time="02-05-2023 10:39:02" level=debug msg="[headers] Content-Type : [application/json; charset=utf-8]"
time="02-05-2023 10:39:02" level=debug msg="[headers] Date : [Tue, 02 May 2023 14:39:02 GMT]"
time="02-05-2023 10:39:02" level=debug msg="Response: HTTP/1.1 200 OK\r\nTransfer-Encoding: chunked\r\nContent-Type: application/json; charset=utf-8\r\nDate: Tue, 02 May 2023 14:39:02 GMT\r\n\r\n4f270c\r\n{\"deleted\":  6MB of JSON response
time="02-05-2023 10:39:02" level=info msg="found existing rule for block action" account_id=ffxxxxxxxxx zone_id=2dxxxxxxxxxxxx
time="02-05-2023 10:39:02" level=debug msg="ip list setup complete" account_id=ffxxxxxxxxx
time="02-05-2023 10:39:02" level=info msg="skipping rule creation for block" account_id=ffxxxxxxxxx zone_id=2dxxxxxxxxxxxx
time="02-05-2023 10:39:02" level=info msg="setup of firewall rules complete" account_id=ffxxxxxxxxx
time="02-05-2023 10:39:02" level=debug msg="collecting decisions from LAPI" account_id=ffxxxxxxxxx
time="02-05-2023 10:39:02" level=debug msg="found new decision with value=<IP_ADDRESS>, scope=Ip, type=ban" account_id=ffxxxxxxxxx
.... continue 1000s lines of new decisions
.... 1000s of lines of expired decisions

Cloudflare support was able to do something that allowed me to delete the list. Not sure what as there were no rules, filters, etc that I could find that were using the list.


Version 1.4.0 rc updates to bazel and protobuf comments

Merge accumulated 1.4.0 updates.
by consensus in WG mtg

FYI, started a "prerelease" for 1.4.0 so the URLs in the Bazel rules work: https://github.com/p4lang/p4runtime/releases/tag/v1.4.0

FYI, started a "prerelease" for 1.4.0 so the URLs in the Bazel rules work: https://github.com/p4lang/p4runtime/releases/tag/v1.4.0

@smolkaj Once you create a tag (in this case v1.4.0) in the Git upstream, you are never supposed to mutate that tag (i.e., mutate the commit referenced by that tag, which is currently f50fef914398498fa97434b4b0183a6b5f74fc3f). That's pretty much a golden rule, and it can break things if you do (e.g., Go modules - it's very much a pain to repair properly and can only be done by releasing a new greater version). Did you mean to create that tag already? Marking the Github release as a "pre-release" doesn't make a difference here, because the tag is still created the same way.
If f50fef914398498fa97434b4b0183a6b5f74fc3f was the intended commit for the v1.4.0 tag all along, please ignore, but it doesn't seem to be the case, given the existence of this PR. The only way to fix it without breaking anything would be to leave the v1.4.0 tag alone now, and release v1.4.1 with all the necessary extra changes.

Thanks for catching that. IIUC, you are saying that tags should always be immutable?
Would simply deleting the tag again address your concerns? Presumably no one has started using it quite yet :)

Thanks for catching that. IIUC, you are saying that tags should always be immutable?
Would simply deleting the tag again address your concerns? Presumably no one has started using it quite yet :)

No deleting the tag doesn't work.
The tag would already have been cache by https://proxy.golang.org/ (presumably right after you created it). See how it is already in the Go documentation: https://pkg.go.dev/github.com/p4lang/p4runtime?tab=versions
Mutating the tag, deleting the tag, deleting the tag in order to recreate it later (which is essentially the same as mutating it) can all create issues for downstream modules (again in the case of Golang) because of conflicts with https://sum.golang.org/
Even outside of Golang specifically, mutating a tag can create issues for software that depends on the project. Some processes which observe a tag that has changed, or release assets that have changed, can fail as it gets reported as a supply chain attack.
The only solution is to move on to v1.4.1 without changing v1.4.0.

Thanks for elaborating, Antonin, I was not aware of that.
SG regarding moving to v1.4.1.


Parallelize download and upload operations during tests

This PR adds logic to parallelize download and upload operations of E2E binaries during tests using errgroup. This is identical to the change made in #7186.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve

/cherry-pick release-0.20

/cherry-pick release-0.19


[COMMENTS] Quotient groups and modular integers

The inline glossary is super useful! Now I know the definitions of complicated terms I'm not familiar with just by hovering over the word! You must be mart :)

Testing math $x^2$ and
$$\frac{x}{2}$$

The inline glossary is super useful! Now I know the definitions of complicated terms I'm not familiar with just by hovering over the word! You must be mart :)

That's true! You should do it too!! I get confused on your blog..


Increase spacing on review screen

@nonprofittechy can you advise on what specifically needed to change here

top margin, so that it is easier to visually tell that the headings indicate separate content.

This was fixed by the accordion blocks


Kotlin DSL for Gradle dependency information mat-card should use 'implementation' as Gradle

What are you trying to do?
Just a cosmetic fix on mat-cards (I got this term by inspecting the source page)

What feature or behavior is this required for?
People that want to import dependencies with Gradle/Kotlin DSL should know that the new recommended way is the implementation keyword, same as Gradle.

compile is not supposed to be used anymore : https://docs.gradle.org/current/userguide/java_library_plugin.html#sec:java_library_separation

How could we solve this issue? (Not knowing is okay!)
By modifying the tip card

Anything else?
Yes, a screenshot is attached !

sorry found it  #72 & #74


Simpler assignment of the optimize alg

Was trying to get recurrent-memory example to work, turns out I had an out of date version of theanets installed (the one you get with pip install isn't compatible with that example). While I was troubleshooting I noticed this small change. I also had to comment out climate.enable_default_logging() as I get an error UnsupportedOperation: fileno (I'm running this on Windows). The climate module seems to be mostly working other than that once I installed http://www.lfd.uci.edu/~gohlke/pythonlibs/#curses.

It looks like this change will ignore the optimize keyword argument that's passed directly to the itertrain() method. self.kwargs is a fallback in case nothing is passed directly.
You could update this change by retaining the original line 305 and then replacing 306-308 with your suggested line -- or you could even do:
optimize = optimize or self.kwargs.get('optimize', 'rmsprop')

Also, good to know that climate is working on Windows!
I am planning on releasing a new version of theanets next week, after this week's paper deadlines are over. :)


fix: #51 - fix "topMost" meta

delay the moment where Topmost is set
do a null check on browser

Thanks !
I rebased !52 (feturing #45), so it is ready to merge.


Regarding Input/Output Format

Hi there, What will be the IO format of each question? Like there will be any particular format of IO for checking the code against test cases or we can take input in any format as we want?

We've provided various sample inputs and outputs for each question. So the input and output format that we will be following to test your code would follow the same sample format.


Add syntax highlight for my template language

(Original issue 818 created by plan_rich on 2012-10-22T17:22:19.097719+00:00)
As I would like to have nice syntax highlight for my new template language here is the code.
It would be nice to have some feedback or including into the core, so that I can build some awesome docs here in bitbucket.
Edit: this is the new repo: https://bitbucket.org/plan_rich/kaa-pygments/overview

(Original issue was assigned to tshatch)
(Original issue 818 last updated on 2014-05-17T01:22:23.671563+00:00)
(Issue automaticaly closed due to status in Bitbucket: wontfix)

(Original comment by tshatch on 2012-11-06T16:02:27.920311+00:00)
It's a bit difficult for me to understand the lexer due to indentation, I'll look at it and reformat for 1.61.

(Original comment by plan_rich on 2012-11-28T14:32:47.597466+00:00)
I changed the indentation as it is in the documentation for 'creating a lexer'. hopes this helps!

(Original comment by tshatch on 2014-05-17T01:22:23.690816+00:00)
Sorry for the extreme delay, but the repo link 404's.  Please reopen if you are still interested.


Introduce Freezing fee

Freezing TXs now have to include SlashAmountPenatly amount of fee
for each Freeze output they have. This amount will be refunded to them
if they are not slashed for the duration of their validation cycle.
Part of #2554

There are bunch of races between spending the penalty deposit with changes in last commit, but the rest of the changes are stable enough to be reviewed.

Fixes #2622

First commit:
* `SlashAmountPenatly` (commit message): Typo

* I still need to process the details, but the idea looks pretty good;

* I don't see the genesis block being modified though ?

* 2nd commit: 👌

* 3rd commit: ❤ ❤ ❤ ❤

* 4th commit: 👌
  -5th to 7th commit: Lots of change... And not doing it for Genesis is a code smell. Still need to process it though.
  8th, 9th: Not sure this is the right way to go. Let's have a quick chat.

The problem with genesis is that there are no inputs for the freeze outputs. So, checking for "fees" in genesis does not really make sense. We could deduct the penalty amount from their frozen outputs tho, just to keep the supply the same.

Rebased and in desperate need of some reviews.

Problem with our current approach is obviously visible in testnet, bring up the wallet for VAL2 and you can see that it thinks it still has a frozen UTXO. But it was slashed, so that UTXO is no longer avaible and we have no record the refund UTXO.

Needs a rebase.

Needs a rebase.

Rebased

I merged some new code in to https://github.com/bosagora/agora/pull/2597/commits/e7a6f4758f0e62b3cf798a732f300284211b7c23 , please take a look.
Melting TX is now forced to spend atleast some part of the penalty deposit.

I merged some new code in to e7a6f47 , please take a look.
Melting TX is now forced to spend atleast some part of the penalty deposit.

I think this is better now. Will re run ci as a couple failed but probably not related.


Tiddle Title UTF8 Support?

Hello everybody
When I used the TiddlySpace,I type the title in my native language that is in UTF8.
However,It always occurs error when I type in something not just pure ANSI code....
I do love TiddlySpace,so I thought that is important to support UTF8 title.
Thanks a lot:D

Can you let us know some or all of the following so we can chase this down:

The browser you are using.
The name of a tiddler and space where you tried this and it didn't work, so we can look in the logs.
Whether you were editing within tiddlywiki directly, or the takenote web application.
Time and Date of you attempts.

UTF8 is supposed to work, so that it is not means that something somewhere in the stack is not right.

the title is: 吉他木頭
browser: firefox 9 and later
My TiddlySpace is http://johnteee.tiddlyspace.com/tiddlers.wiki
When I type this title in a new tiddle,it never save in the remote host,and always displays error messages.
I've tried many versions of firefox,and they don't work currectly.
However,Chrome and Opera and IE are always ok anyway...
Whatever~the problem appears,and there's way to solve it:P
Thank you:D

I found that it's my fault....Adblock block something,and make UTF8 doesn't work
Thank you so much !


Threadpool arguments arent documented here (nor does the command has an help with this information)

sos.threadpool has no auto documentation of the options (ex: -ti, -wi).
At the very least this web page should document the options.

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

ID: 8e01c075-7a07-5850-d462-706675b545f1
Version Independent ID: 0dd6c661-01a1-592c-ea53-8427412ff8d0
Content: SOS.dll (SOS Debugging Extension) - .NET Framework
Content Source: docs/framework/tools/sos-dll-sos-debugging-extension.md
Product: dotnet-framework
GitHub Login: @gewarren
Microsoft Alias: gewarren

Would it be helpful to link to this page? https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/-tp

tp does not seems to be a sos.dll command. People debugging on lldb uses threadpool.
See my initial comment. soshelp threadpool does not document the possible arguments.
According to source code "-ti" and "-wi" are optional arguments...

(lldb) soshelp threadpool
-------------------------------------------------------------------------------
ThreadPool

This command lists basic information about the ThreadPool, including the number
of work requests in the queue, number of completion port threads, and number of
timers.


Create Sample, Tissue, Animal, and Experiment objects

Create the objects for Sample, Tissue, Animal, and Experiments.

Sample
-
id PK int
animal_id int FK >- Animal.id
tissue_id int FK >- Tissue.id
name string
date date
researcher string

Tissue
-
id PK int
name string

Animal
-
id PK int
name string
infusate_compound_id int FK >- Compound.id
infusate_labeled_atom string
infusate_labeled_count int
infusion_rate float
infusate_concentration float
state string
experiment_id int FK >- Experiment.id

Experiment
-
id PK int
name string
description string

Questions for all (or at least @lparsons ):

Any concern/problem with swapping the term 'study' for 'experiment'? ('Study' is used by Metabolights repository and ISA model.   Another alternative might be 'bioproject', though I prefer study.
So, we are committing ourself to capturing a Study/Experiment with every animal/sample file? [foreign key will be required]. Also, an Animal will only be associated with 1 experiment/study, not more than one. [just clarifying; I think this is fine].

@jcmatese good questions.

Fine by me, I also prefer study over bioproject.
Yes, I think we can require a study name be included for each import. Yes, the design does mean an Animal can only be a part of one study.

@lparsons @fkang-pu Are we going to go with 'infusate' or 'tracer' for the animal attributes (five attribute-related prefixes)?  Did the researchers have a definitive preference?

@jcmatese @lparsons I am flexible with table/column names, but prefer to use ISA model if possible. I think if's good for the researchers in a long run. Michael Neinast prefers to use "tracer" instead of "infusate". For "Animal" table, I am also ok with using "Source" (ISA model). It's better to model Animal/Experiment as many to many relationships. The lab can group the samples before MS runs or re-group them later (e.g. for publications). If you want to save time for digging out details, I have notes in my Excel file (shared in Google drive on March 11) for animal/sample attributes based on Michael's comments. We should also decide column name(s) for a user (researcher/userid/primary_contact/performer), which may save a little bit time for changing them later.

@fkang-pu Some nice points, I'm good with using ISA naming conventions when it fits and doesn't make things to generic. A many to many relationship could certainly work for the Animal/Experiment relationship, and @jcmatese brought it up too, so I'll go ahead and make that change unless there is some dissent. Can you provide a link to the Google drive file you're referring to? I'll use that to update some of these names and get the issue updated. Thanks!

@lparsons two files: 1) Michale's pptx file revised on March 10: https://docs.google.com/presentation/d/1SUkGiPg0yX4QT6p9gAalOUo0tyyAaRzI/edit#slide=id.p1
2) my notes in Excel worksheets (study_source_sample_tables_v1, study_source_sample_tables_v2) with columns as Michael suggested: https://docs.google.com/spreadsheets/d/16_Mye49DwSfeZaYISCJqNrQyANy5-eu8/edit#gid=2137748225
My excel file is easier to go through if you download it and open in Excel.

I am actually fine the way it is (Animal).  My thinking:

Since we aren't actually modeling a full graph, with protocols, like source->protocol->treated sample->protocol->extracted_samples etc., and
we are pushing the protocol-derived attributes into the animal ("source"), and
we are hardcoding everything for this specific experiment design,

Therefore, I don't think it is worth calling it "Source" [may actually be a mischaracterization, as that animal has already been protocol-derived for weeks].

Thanks @fkang-pu I did want to comment that the example datafile in #19  and you notes do call out the following attributes that I would have added

genotype [string]
body_weight [float]

Fan's notes also include:
species [is this strictly necessary, since we appear to be hardcoding this for mouse?]
time of infusion start [is this strictly necessary?]

I guess we could always add them and make them nullable?

@jcmatese Michael's slide lists all data fields you mentioned. Some examples are listed  in "obob" 3b serum analysis file (top 5 rows for animal descriptions).  Not sure if the lab also use rats.

@jcmatese After reading your comments, I agree it's more appropriate to use "Animal" as table name for this project.

Just noting that the model currently has a single Tracer for an Animal , but the example file referenced by #19 has notes like "Infusion was actually 6 labeled tracers:  Histidine, Lysine, Methionine, Phenylalanine, Threonine, Tryptophan".  May need to consult with researchers as to how prevalent this is, and if we need to capture it from the start.

Just noting that the last 2 lines of the example file referenced by #19 have BLANK for all the sample attributes (Animal and Sample).  Initially I was considering making some attributes nullable to accommodate this, but there I also a note that "It could be excluded from database".  It is one thing to make a BLANK/mull tracer.  It is something self to have a blank/null Animal.  Wit the model as-is, we would likely have to exclude these from the database (or dummy data for Animal placeholder).

Just noting that many lines of the example file referenced by #19 have a Infusate/Tracer compound of "C16:0", which is not on any compound list we have been provided previously, and might violate our Compound-foreign-key assumptions or HMDB dbxrefs.


[bn] Localization of cluster-architect.md

localized cluster-architect.md in bangla
fixes #45729

/assign @asem-hamid
Can you proceed with this?

/label tide/merge-method-squash


[Bug] C++ exception with description "ibv_modify_qp failed (errno 19) (Ib failure: No such device)" thrown in the test body.

Hi, I am using mscclp to do cross node communication. But I got error as following. Please help me out.

Are you using IB or RoCE for cross node communication? Can you run ibstat and put the output here?

Thank you for your swift response. This is what ibstat got.
CA 'mlx5_0'
	CA type: MT4125
	Number of ports: 1
	Firmware version: 22.38.1900
	Hardware version: 0
	Node GUID: 0x946dae0300907832
	System image GUID: 0x946dae0300907832
	Port 1:
		State: Active
		Physical state: LinkUp
		Rate: 100
		Base lid: 0
		LMC: 0
		SM lid: 0
		Capability mask: 0x00010000
		Port GUID: 0x0000000000000000
		Link layer: Ethernet
CA 'mlx5_1'
	CA type: MT4125
	Number of ports: 1
	Firmware version: 22.38.1900
	Hardware version: 0
	Node GUID: 0x946dae0300907833
	System image GUID: 0x946dae0300907832
	Port 1:
		State: Active
		Physical state: LinkUp
		Rate: 100
		Base lid: 0
		LMC: 0
		SM lid: 0
		Capability mask: 0x00010000
		Port GUID: 0x0000000000000000
		Link layer: Ethernet
CA 'mlx5_2'
	CA type: MT4125
	Number of ports: 1
	Firmware version: 22.38.1900
	Hardware version: 0
	Node GUID: 0x946dae0300906062
	System image GUID: 0x946dae0300906062
	Port 1:
		State: Active
		Physical state: LinkUp
		Rate: 100
		Base lid: 0
		LMC: 0
		SM lid: 0
		Capability mask: 0x00010000
		Port GUID: 0x0000000000000000
		Link layer: Ethernet
CA 'mlx5_3'
	CA type: MT4125
	Number of ports: 1
	Firmware version: 22.38.1900
	Hardware version: 0
	Node GUID: 0x946dae0300906063
	System image GUID: 0x946dae0300906062
	Port 1:
		State: Active
		Physical state: LinkUp
		Rate: 100
		Base lid: 0
		LMC: 0
		SM lid: 0
		Capability mask: 0x00010000
		Port GUID: 0x0000000000000000
		Link layer: Ethernet
CA 'mlx5_4'
	CA type: MT4123
	Number of ports: 1
	Firmware version: 20.38.1900
	Hardware version: 0
	Node GUID: 0xe8ebd3030058998c
	System image GUID: 0xe8ebd3030058998c
	Port 1:
		State: Active
		Physical state: LinkUp
		Rate: 100
		Base lid: 0
		LMC: 0
		SM lid: 0
		Capability mask: 0x00010000
		Port GUID: 0x0000000000000000
		Link layer: Ethernet
CA 'mlx5_5'
	CA type: MT4123
	Number of ports: 1
	Firmware version: 20.38.1900
	Hardware version: 0
	Node GUID: 0xe8ebd3030058998d
	System image GUID: 0xe8ebd3030058998c
	Port 1:
		State: Active
		Physical state: LinkUp
		Rate: 100
		Base lid: 0
		LMC: 0
		SM lid: 0
		Capability mask: 0x00010000
		Port GUID: 0x0000000000000000
		Link layer: Ethernet
CA 'mlx5_6'
	CA type: MT4123
	Number of ports: 1
	Firmware version: 20.38.1900
	Hardware version: 0
	Node GUID: 0xe8ebd303005899bc
	System image GUID: 0xe8ebd303005899bc
	Port 1:
		State: Active
		Physical state: LinkUp
		Rate: 100
		Base lid: 0
		LMC: 0
		SM lid: 0
		Capability mask: 0x00010000
		Port GUID: 0x0000000000000000
		Link layer: Ethernet
CA 'mlx5_7'
	CA type: MT4123
	Number of ports: 1
	Firmware version: 20.38.1900
	Hardware version: 0
	Node GUID: 0xe8ebd303005899bd
	System image GUID: 0xe8ebd303005899bc
	Port 1:
		State: Active
		Physical state: LinkUp
		Rate: 100
		Base lid: 0
		LMC: 0
		SM lid: 0
		Capability mask: 0x00010000
		Port GUID: 0x0000000000000000
		Link layer: Ethernet

@Binyang2014
ibv_rc_pingpong is okay.

So I change gid index to 7. Mscclpp is still not working.

set-hldy-nlp-llm-inference08:165895:165895 [0] MSCCLPP INFO TcpBootstrap : Using eth0:<IP_ADDRESS><0>
set-hldy-nlp-llm-inference08:165895:165895 [0] MSCCLPP INFO TcpBootstrap : Using eth0:<IP_ADDRESS><0>
set-hldy-nlp-llm-inference08:165895:165895 [0] MSCCLPP INFO rank 0 nranks 2 - connecting to <IP_ADDRESS><54879>
devAttr.phys_port_cnt: 1
devAttr.phys_port_cnt: 1
Port: 1
IbQpInfo: lid: 0 port: 1 linkLayer: 2 qpn: 30029 spn: 0 mtu: 3 iid:<PHONE_NUMBER>164402688 is_grh: 1

unknown file: Failure
C++ exception with description "ibv_modify_qp failed (errno 19) (Ib failure: No such device)" thrown in the test body.

unknown file: Failure
C++ exception with description "ibv_modify_qp failed in IbQp::rtr (errno 19) (Ib failure: No such device)" thrown in the test body.

I figured it out. I have to change this line too.

We only run the unit tests in InfiniBand environment, which gid index is 0. For RoCE, seems we need a way to find the GID index, or let user pass the GID index via env variable.

@Binyang2014 Passing the GID index via env variable is what NCCL does.

@Binyang2014
I write a kernel for both cross node and within node communication.
__device__ void allGatherSendPlan(CommPlanKernelParams p) {
  int warpSize = 32;
  int warpIdx = threadIdx.x / warpSize;
  int laneIdx = threadIdx.x % warpSize;
  if (warpIdx < p.ep_world_size) {
    int remoteRank = warpIdx;
    auto smChan = p.smChans[remoteRank];
    smChan.put<4>(
        p.my_rank * p.ep_world_size * p.num_stages * sizeof(int),
        0,
        p.ep_world_size * p.num_stages * sizeof(int),
        laneIdx,
        warpSize);
    if (laneIdx == 0) {
      smChan.signal();
      smChan.wait();
    }
  }
  __syncthreads();
}

It works well when there are not cross node communication. But If I have one GPU per Node, I got a an illegal memory access was encountered.
Does the put, signal and wait work when doing cross node communication?

For cross node communication, pls use proxy channel, sm channel only for intra node communication.  Here is the doc for proxy channel setup: https://microsoft.github.io/mscclpp/getting-started/tutorials/initialization.html#initialize-communication-with-c-api, and a sample code for how to use the proxy channel: https://github.com/microsoft/mscclpp/blob/3e7801b1a8eb89f975c5e26c088e812e58601242/test/mscclpp-test/allgather_test.cu#L30-L50

Thank you for your help. I finally made it work. Close this issue.


[AdaptiveCards- Designer - Card Structure]: Ensures elements with an ARIA role that require parent roles are contained by them (.acd-tree-item[role="treeitem"])

Target Platforms
Other
SDK Version
1.5
Application Name
Adaptive Cards
Problem Description
Test Environment:
URL: https://adaptivecards.io/
OS Version: 22H2(OS Build 25247.1000)
Browser Version: Version 110.0.1543.0 (Official build) dev (64-bit)
Tool: Accessibility Insight For Web
Repro Steps:

Open the URL above with valid credential.
Navigate to 'Designer' link and press the enter key to activate it.
Navigate to 'Card Structure' button and press the tab key.
Run accessibility insight for web and observe the issue.

Actual Result:
Elements with an ARIA role that require parent roles are not contained by them.
Expected Result:
Ensures elements with an ARIA role that require parent roles are contained by them
User Experience:
It will impact the screen reader user if the screen reader does not convey the message to the user.
Element path:
li[aria-level="\31 "] > .acd-tree-item[role="treeitem"]
Snippet:

How to fix:
Fix any of the following:
Required ARIA parents role not present: group, tree
MAS Reference:
https://microsoft.sharepoint.com/:w:/r/sites/accessibility/_layouts/15/Doc.aspx?sourcedoc={9C514377-76E5-4CFE-8300-DA3079D3CDC3}&file=MAS 1.3.1 – Info and Relationships.docx&action=default&mobileredirect=true&share=IQF3Q1Gc5Xb-TIMA2jB5083DAcWOZyaXcx7TtNeRlXM4uHk
"Have feedback to share on Bugs ? Please help fill Trusted Tester Bug Feedback (office.com) “.
Screenshots

Card JSON
NA

Sample Code Language
No response
Sample Code
No response

Hi @anna-dingler,
As this issue is still repro, so could you please let us know is there any future plan to fix this issue?

Closing this issue since it is a duplicate of https://github.com/microsoft/AdaptiveCards/issues/7288

Adding A11yTTValidated tag as per the comment above,


chore: Merge non-breaking features from v2

Fixes #384

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

11 of 11 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 92.564%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
8739

Relevant Lines:
9441

💛  - Coveralls


Improve behavior when ngrok is already started

Current behavior:
If ngrok is already started, it won't be started even if the expected port is not listened to.
Expected behavior:

If the ngrok account accepts multiple sessions and ngrok doesn't listen to the expected port, the startup should start ngrok with the expected port.
If the ngrok account doesn't accept multiple sessions and ngrok doesn't listen to the expected port, the startup should fail.

I left related comment in MR https://github.com/kilmajster/ngrok-spring-boot-starter/pull/55#issuecomment-830650433

The feature request is still valid: the user account could be checked in order to provide a more expected behavior.
But I didn't find a public api for the account.


Error livy

Hello Team,
Under livy_server, after created a session, i tried to get the session status but i get status =error  and the msg is:
Authentication failed, URL: https://152101lp38.csh-dijon.cnamts.fr:9393/kms/v1/?op=GETDELEGATIONTOKEN&doAs=tdp_user&renewer=rm%2F152101lp38.csh-dijon.cnamts.fr%40CNAMTS.DEV&user.name=livy, status: 403, message: Forbidden","\tat org.apache.hadoop.security.authentication.client.AuthenticatedURL.extractToken(AuthenticatedURL.java:401)","\tat org.apache.hadoop.security.authentication.client.PseudoAuthenticator.authenticate(PseudoAuthenticator.java:74)","\tat org.apache.hadoop.security.token.delegation.web.DelegationTokenAuthenticator.authenticate(DelegationTokenAuthenticator.java:147)","\tat org.apache.hadoop.security.authentication.client.KerberosAuthenticator.authenticate(KerberosAuthenticator.java:213)","\t... 49 more","2023-03-01 14:43:00,239 INFO util.ShutdownHookManager: Shutdown hook called","2023-03-01 14:43:00,240 INFO util.ShutdownHookManager:
the error mentions the kerberos ticket, however, I do have a valid kerberos ticket, did I miss something please?
Thank you in advance

How do you perform the HTTP request ? Do you use curl ? If you use curl, do you use the --negociate option ?

i use the command as mentioned in the README
Create a session :
curl -k -u : --negotiate -X POST https://livy_server:8998/sessions
-d '{"kind": "pyspark"}' -H 'Content-Type: application/json'
Get the state session
curl -k -u : --negotiate -X GET https://livy_server:8998/sessions

Do have the proxyuser for livy in kms-site.xml?
hadoop.kms.proxyuser.livy.groups: ''
hadoop.kms.proxyuser.livy.hosts: ''

I added this two lines and now i have state dead this is all the message:
{"from":0,"total":2,"sessions":[{"id":0,"name":null,"appId":null,"owner":"livy","proxyUser":"livy","state":"dead","kind":"pyspark","appInfo":{"driverLogUrl":null,"sparkUiUrl":null},"log":["\tat java.security.AccessController.doPrivileged(Native Method)","\tat javax.security.auth.Subject.doAs(Subject.java:422)","\tat org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1729)","\tat org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:172)","\tat org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:217)","\tat org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:137)","\tat org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)","2023-03-06 19:04:30,194 INFO util.ShutdownHookManager: Shutdown hook called","2023-03-06 19:04:30,194 INFO util.ShutdownHookManager: Deleting directory /tmp/spark-7dd347a1-18b9-419a-b15b-ec33d0f463ae","\nYARN Diagnostics: "]},{"id":1,"name":null,"appId":null,"owner":"spark","proxyUser":"spark","state":"error","kind":"pyspark","appInfo":{"driverLogUrl":null,"sparkUiUrl":null},"log":["\tat java.security.AccessController.doPrivileged(Native Method)","\tat javax.security.auth.Subject.doAs(Subject.java:422)","\tat org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1729)","\tat org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:172)","\tat org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:217)","\tat org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:137)","\tat org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)","2023-03-06 19:08:26,769 INFO util.ShutdownHookManager: Shutdown hook called","2023-03-06 19:08:26,770 INFO util.ShutdownHookManager: Deleting directory /tmp/spark-3dd23288-2bb3-47c9-8b28-ddf7918d10c2","\nYARN Diagnostics: "]}]}

Do pyspark command work without livy?

yes pyspark work fine

I suppose that ranger-kms has been restarted after the kms-site update.
The log does not give too much information. All I see is the permission error.
Could you do this command on a "dead" session which is initiated by tdp_user ?
curl --negotiate -u : "https://livy_server:8998/sessions/session_id/log" | python -m json.tool

I tried with your command i saw a problem access to to the directory /user under hdfs. So i added this to hdfs-site.xml

dfs.permissions
false

and when i retest i get this message
"Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/jersey/api/client/config/ClientConfig. It appears that the timeline client failed to initiate because an incompatible dependency in classpath. If timeline service is optional to this client, try to work around by setting yarn.timeline-service.enabled to false in client configuration.",
I tried to add spark.hadoop.yarn.timeline-service.enabled false to spark-defaults.conf, but that change nothing.

livy.zip
I attached the files here

You must configure the correct ranger policies for the user to have access to hdfs.
By the way, the livy.conf is not updated with the lastet modification which helps to interfact with Hive. Please update your git repo and redeploy.

What did you do to get this error "Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/jersey/api/client/config/ClientConfig. It appears that the timeline client failed to initiate because an incompatible dependency in classpath. If timeline service is optional to this client, try to work around by setting yarn.timeline-service.enabled to false in client configuration.",
Do you restart services after changement the configuration?
Could you redo all step with the tdp_user?
It will be easier for me to follow if you post the command and the result/error at the same time.

It's the same commands always:
sudo su - tdp_user
kinit -ki
Create a session
curl -k -u : --negotiate -X POST https:/livy_server:8998/sessions
-d '{"kind": "pyspark"}' -H 'Content-Type: application/json'
Get the session status (wait until it is "idle")
curl -k -u : --negotiate -X GET https://livy_server:8998/sessions
Submit a snippet of code to the session
curl -k -u : --negotiate -X POST https://edge-01.tdp:8998/sessions/0/statements
-d '{"code": "1 + 1"}' -H 'Content-Type: application/json'
Get the statement result
curl -k -u : --negotiate -X GET https://livy-server:8998/sessions/0/statements/0
and i tried with livy user and with another users but is the same result
and after each modification, i restart the services.


Cleanup example code

Eliminated all warnings and did a minor refactor and cleanup.

Looks good to me. Does as it says on the tin.


Disable Styles and only bundle scss

Hi!
First of all I want to say thank you! Your plugin works great. The bundling is perfect.
I am using plugin-rollup-vue and since I am bundling the scss already with your plugin, I don't need styles at all. Do you have a clue on how to achieve this and disable the style-handling?
Thanks in advance.
Anton

Do you mean you don't want output the CSS file? Example in README should achieve this by default.

Hi @weizhenye, thanks for the reply. I tried the example number two (Using with rollup-plugin-vue) but the CSS was still inlined in the JS code of my components. I only want the bundled scss and no css at all in the esm-module.
Should I provide an example?

Inlined CSS in JS is created by rollup-plugin-vue with option { css: true }, you can set it to false and add another plugin to handle CSS files.
import commonjs from 'rollup-plugin-commonjs';
import vue from 'rollup-plugin-vue';
import bundleScss from 'rollup-plugin-bundle-scss';
import css from 'rollup-plugin-css-only';

export default {
  // ...
  plugins: [
    commonjs(),
    bundleScss(),
    vue({ css: false }),
    css({ output: false }),
  ],
};

Thank you, @weizhenye. This worked and solved the problem.
Thanks and have a great day!


Permissions

Please describe the changes this PR makes and why it should be merged:

not broken, unlike #2128
less complicated than #2126

Semantic versioning classification:

[ ] This PR changes the library's interface (methods or parameters added)

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

This is breaking for no reason, and returns an inconsistent type that isn't what you show in jsdocs...

I don't know if I agree with this being less complicated than my solution.

Return type is a derp. As for complexity and breaking changes, I see no reason why a simple bitwise operation shouldn't be better than loops and filters; return type is just a side effect of simplifying the operation.

Idk, this still doesn't seem to work. Try calling (new DiscordJS.Permissions(40)).missing(new DiscordJS.Permissions(86016))

Still doesn't work, try (new DiscordJS.Permissions(4096)).missing(new DiscordJS.Permissions(16384)). It says that 4096 is missing, although it's the only permission present. 🤔

As I understand it, this method is intended to determine the permissions that the instance is missing from the permissions provided.  My understanding is supported by the fact that the current method does exactly that.  Constructing an instance with only permissions for SEND_TTS_MESSAGES (4096) would therefore be missing permissions for EMBED_LINKS (16384).

That's correct, but your implementation doesn't do that. (new DiscordJS.Permissions(4096)).missing(new DiscordJS.Permissions(16384)) returns an instance of Permissions with a bitfield value of 4096, or rather "SEND_TTS_MESSAGES".


Migrate event with schedule to base page

Who's it for?
Us.
Problem to be solved
Moving from the article template to the base page so it can use all components consistently across the whole site.
Done when

Components available to include in Prismic

out of scope
Page redesign, ie design enhancements that aren't urgent but 'nice to have'
Components

[ ] Event schedule

Other components should be covered by events already migrated to base page https://github.com/wellcometrust/wellcomecollection.org/issues/3022

@pollecuttn this has already been done. I think @Heesoomoon might want to make some design changes at some point but it currently looks like this:

@pollecuttn @gestchild
We should consider following

Support multiple images
Update date & time format (as part of #3008)
Revisit how we display ticketing type info and location
Update event format label
Remove 'dates'
Ability for the content team to customise 'Need to know' info

I'm putting this back in to do for page migration in light of @Heesoomoon's comments