Localization resources (*..resx) are named incorrectly if corresponding class has namespace other then default namespace(.NET Core 3.0 release)

ConsoleApp_Core3.zip
Steps to reproduce
Build and run attached application.
dotnet build ConsoleApp_Core3.csproj
bin\Debug\netcoreapp3.0\ConsoleApp_Core3.exe

Project file
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" Sdk="Microsoft.NET.Sdk.WindowsDesktop">

  <PropertyGroup>
    <UseWindowsForms>True</UseWindowsForms>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp3.0</TargetFramework>
  </PropertyGroup>

</Project>

Directory contents:
/
-ConsoleApp_Core3.csproj
-BaseComponent.cs
-Program.cs
-TestComponent.cs
-TestComponent.Designer.cs
-TestComponent.de.resx
-TestComponent.resx

Expected  behavior
program output should include:
Text: en-US
Text: de-DE

Actual behavior
program output include:
Text: en-US
Text: en-US

To make it work correctly the following lines have to be inserted in project file:
  <ItemGroup>
    <EmbeddedResource Update="TestComponent.de.resx">
      <DependentUpon>TestComponent.cs</DependentUpon>
    </EmbeddedResource>
  </ItemGroup>

Environment data
dotnet --version output:
3.0.100

Closed per #4853 merging into master with #4884


Bug: kubeproxy was trying to acces K8s apiserver through LB URL after removing the LB

Current Behaviour
The InputManifest contained some control-plane nodes and two static nodes. One static node was used as a worker node in the K8s cluster, and another one was used as a LoadBalancer. The worker node couldn't start any pod because the systemd-resolved service wasn't running there.
We removed the LoadBalancer from the InputManifest. Then we started the systemd-resolved service on the worker node. After the start, the first pods on the worker node were created (kube-proxy and node-local), however, the Cilium agent on that worker node kept on restarting, because it couldn't connect to the Kubernetes apiserver. These logs were in the kube-proxy pod of that worker node.
E0214 12:29:32.000604       1 node.go:152] Failed to retrieve node info: Get "https://lb-syd.worldofpotter.eu:6443/api/v1/nodes/syd01-1": x509: certificate is valid for control01-hetzner-hel1-iqpc8bt-1, kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, loadbalancer.worldofpotter.eu, not lb-syd.worldofpotter.eu
E0214 12:30:11.396240       1 reflector.go:140] vendor/k8s.io/client-go/informers/factory.go:150: Failed to watch *v1.Node: failed to list *v1.Node: Get "https://lb-syd.worldofpotter.eu:6443/api/v1/nodes?fieldSelector=metadata.name%3Dsyd01-1&limit=500&resourceVersion=0": x509: certificate is valid for control03-hetzner-nbg1-z88etn3-1, kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, loadbalancer.worldofpotter.eu, not lb-syd.worldofpotter.eu

To me, it looks like the kube-proxy still tried to connect to the Kubernetes apiserver through the LoadBalancer URL, even though the LoadBalancer was removed.
Expected Behaviour
A healed worker node should recognize that the LoadBalancer isn't in use anymore, and most importantly it should be able to connect to the Kubernetes apiserver.
Steps To Reproduce

Create an InputManifest with two static nodes. One as a K8s worker and another one as a LoadBalancer. The number and type of the K8s master nodes shouldn't matter, but FYI, we had 3 dynamic master nodes.
Make sure the systemd-resolved service isn't running on the static worker node.
Build the cluster.
Remove the static LoadBalancer from the InputManifest
Start the systemd-resolved service on the static worker node.
Check logs of the kube-proxy pod running on that worker node.

My findings on this issue.
After a cluster is created and the control plane apiendpoint changes (adding loadbalancer configuration / removing loadbalancer) kube-eleven is not patching kube-proxy configmap with the new apiEndpoint:
kubectl -n kube-system get cm kube-proxy -o yaml

apiVersion: v1
data:
  config.conf: |-

    . . . [TRIMMED]

  kubeconfig.conf: |-
    apiVersion: v1
    kind: Config
    clusters:
    - cluster:
        certificate-authority: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
        server: https://API_ENDPOINT_ADDRESS:6443 # <----- Value over here
      name: default
    contexts:
    - context:
        cluster: default
        namespace: default
        user: default
      name: default
    current-context: default
    users:
    - name: default
      user:
        tokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
kind: ConfigMap
metadata:
  labels:
    app: kube-proxy
  name: kube-proxy
  namespace: kube-system
  resourceVersion: "235"
  uid: 38ac488d-8dcb-4fb6-a78b-62d479232394

To fix this manually, I had to update the apiEndpoint in the config map, and rollout restart kube-proxy.


Local raw block device using persistent volume source

Feature Description

One-line feature description (can be used as a release note): Make local raw block devices (non-networked) available for consumption via a Persistent Volume Source
Primary contact (assignee): @erinboyd, @screeley44, @mtanino
Responsible SIGs: @kubernetes/sig-storage-feature-requests @kubernetes/sig-apps-feature-requests
Design proposal link (community repo): https://github.com/kubernetes/community/pull/805
Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
@msau42
@jsafrane
Approver (likely from SIG/area to which feature belongs):
@saad-ali
Feature target (which target equals to which milestone):

Alpha release target (x.y): 1.8
Beta release target (x.y): 1.9
Stable release target (x.y): 1.10

@idvoretskyi Could you assign me to this feature too?

Hi Erin, the feature you're working on is not specific to local storage right? There is work specific to the local storage plugin that I am coordinating.  Just want to make sure that it doesn't conflict with the work you're doing.

@mtanino it seems to be not possible before you'll join Kubernetes organization - https://github.com/kubernetes/community/blob/master/community-membership.md. Sorry, It's a GitHub restriction.

@idvoretskyi Thank you for the explanation.  I'll try to send membership request.

@erinboyd I have the same question as @msau42, is this specific to local block or this is about block support in general?

@erinboyd I just saw this.  What is required from SIG-Apps?

Copying comment from https://github.com/kubernetes/features/issues/350:
Both Nutanix and Rook are pursuing Flex volumes, which will be out-of-tree and do not need to be tracked for the release.
I will keep both these feature bugs active for 1.8 until code freeze--in the unlikely case we need to fall back to in-tree volume plugin. At code freeze, we will close both of these issues and remove them from tracking for 1.8.

for sig-apps it is mostly testing w/ databases + raw block storage to see if we see the intended benefits?

@danpaik @erictune
I agree on above.
@erinboyd
Anything else?

I'm sure SIG-Apps has the necessary experience to advise on how to adapt existing database examples/charts to use the new volume type.  Looking at MySQL, it looks like it won't be trivial: you need a separate step to initialize the block device, vs serving from it.
I agree that raw block access might pose some security issues, but I'm not sure SIG-Apps has the necessary expertise to evaluate security.

@etune I don't think it will be a big win for most OSS storage applications, but it will offer a migration path for users with custom or legacy applications to move their workloads onto Kuberentes.

None of Postgres, Cassandra, MongoDB, Couchbase, CouchDB, Riak, ElasticSearch, Solr, Kafka, Redis,or HDFS, or HBase support the use raw block devices.
Of the RDBMS systems that do (MySQL or Maria with InnoDB, Oracle, and DB2), I've only seen interest in MySQL and Maria.
Of the DFSes that use it, they are all meant to run with local raw block devices. The IOPS caps for remote storage might not be practical for the most prevalent use cases.

@danpaik For InnoDB what is the optimization we hope to achieve?

Are we just trying to remove the filesystem overhead?
Are we trying to disable double buffering? If so, we need to map the configured page size to the disk sector size. Note that, for ext4 (data=journaled) you can probably disable double buffering if the InnoDB page size is 4k without using a raw block device.

I don't think having a helm chart that disables double buffering will necessarily be safe (or portable) as there is an underlying dependency on the page size representing an atomically writable disk sector. The sector size will be cloud provider specific, and it is currently not surfaced in any way. We should just use manifests for the purposes of testing InnoDB in this configuration, and I would propose using Sysbench for an evaluation of the measured performance.

This did not make it in to 1.8, design was complete. Implementation will be punted to 1.8

@saad-ali to 1.8 or 1.9? If 1.9, let's update the milestone.

Moved to 1.9

Updated milestone above as well!

@erictune Not sure how I missed your comments from August (cough cough), my apologies. Thank you for the insight and we will find the appropriate expertise then for the database related questions. 👍

@erinboyd :wave: Please open a documentation PR and add a link to the tracking spreadsheet. Thanks in advance!

@erinboyd Bump for docs ☝
/cc @idvoretskyi

done: https://github.com/kubernetes/website/pull/6486
On Tue, Nov 28, 2017 at 5:03 PM, Zach Corleissen<EMAIL_ADDRESS>wrote:

@erinboyd https://github.com/erinboyd Bump for docs ☝
/cc @idvoretskyi https://github.com/idvoretskyi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/features/issues/351#issuecomment-347706501,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADLTZ_qv5WiWSiq_SFKARkM20TIZxw3iks5s7J9kgaJpZM4OV1Tr
.

@erinboyd, @screeley44, @mtanino @saad-ali
Any plans for this in 1.11?
If so, can you please ensure the feature is up-to-date with the appropriate:

Description
Milestone
Assignee(s)
Labels:

stage/{alpha,beta,stable}
sig/*
kind/feature

cc @idvoretskyi

@jberkus @justaugustus - not sure what else is required at this time, but existing docs do exist for this feature
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#raw-block-volume-support

feature and docs update: no additional docs are required for release 1.11

Moving block volumes to beta slipped. Moving to 1.12.

Working on https://github.com/kubernetes/kubernetes/pull/65117 to add e2e tests for block volume.
We might need a criteria to make this feature to beta. @saad-ali

E2E tests automatically running in CI should definitely be a blocker for beta.

Thank you for your comment. I will keep working on it. @msau42
Also, I would appreciate it if you could share a list of blockers for beta here, in order to make it easier for us to work together for this feature. (Or should each issue be added directory to 1.12 tracking spreadsheet?) @wongma7

@mkimuram I'm not aware of any blockers for beta but yeah let's list them here, imo the tracking spreadsheet is long enough already :). Please, if anybody is aware of other blockers for beta, especially any changes we need to make to the API, let me know, as I'm picking this task up with, tbh, minimal knowledge about how the alpha phase has gone

@wongma7 Thank you!

@erinboyd @screeley44 @kubernetes/sig-storage-feature-requests --
This feature was removed from the previous milestone, so we'd like to check in and see if there are any plans for this in Kubernetes 1.12.
If so, please ensure that this issue is up-to-date with ALL of the following information:

One-line feature description (can be used as a release note):
Primary contact (assignee):
Responsible SIGs:
Design proposal link (community repo):
Link to e2e and/or unit tests:
Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
Approver (likely from SIG/area to which feature belongs):
Feature target (which target equals to which milestone):

Alpha release target (x.y)
Beta release target (x.y)
Stable release target (x.y)

Set the following:

Description
Assignee(s)
Labels:

stage/{alpha,beta,stable}
sig/*
kind/feature

Please note that the Features Freeze is July 31st, after which any incomplete Feature issues will require an Exception request to be accepted into the milestone.
In addition, please be aware of the following relevant deadlines:

Docs deadline (open placeholder PRs): 8/21
Test case freeze: 8/28

Please make sure all PRs for features have relevant release notes included as well.
Happy shipping!
/cc @justaugustus @kacole2 @robertsandoval @rajendar38

@erinboyd @screeley44 --
Feature Freeze is today. Are we planning on graduating this feature in Kubernetes 1.12?
If so, can you make sure everything is up-to-date, so I can include it on the 1.12 Feature tracking spreadsheet?

@justaugustus we are planning on moving this from alpha to beta in 1.12, what are you asking to update?

@childsb -- just confirming. I hadn't heard anything regarding this since the 1.11 release cycle.
I've added it to the 1.12 tracking sheet. :)

Hey there! @erinboyd I'm the wrangler for the Docs this release. Is there any chance I could have you open up a docs PR against the release-1.12 branch as a placeholder? That gives us more confidence in the feature shipping in this release and gives me something to work with when we start doing reviews/edits. Thanks! If this feature does not require docs, could you please update the features tracking spreadsheet to reflect it?

@screeley44 @mtanino Bump for docs ☝

@zparnold , placeholder/WIP PR created here: https://github.com/kubernetes/website/pull/10100 .

Thank you!

@childsb @wongma7 --
Any update on docs status for this feature? Are we still planning to land it for 1.12?
At this point, code freeze is upon us, and docs are due on 9/7 (2 days).
If we don't here anything back regarding this feature ASAP, we'll need to remove it from the milestone.
cc: @zparnold @jimangel @tfogo

@childsb @wongma7 @erinboyd @screeley44 -- Removing this from the milestone as we haven't heard anything back from you.
/milestone clear

Hi @childsb @wongma7
This enhancement has been tracked before and slated for 1.13 graduation to stable according to the post, however, it's not on the milestone and I'm unsure if this made beta for 1.12. Any plans for this to graduate stages in Kubernetes 1.13? This release is targeted to be more ‘stable’ and will have an aggressive timeline. Please only include this enhancement if there is a high level of confidence it will meet the following deadlines:

Docs (open placeholder PRs): 11/8
Code Slush: 11/9
Code Freeze Begins: 11/15
Docs Complete and Reviewed: 11/27

Please take a moment to update the milestones on your original post for future tracking and ping @kacole2 if it needs to be included in the 1.13 Enhancements Tracking Sheet.
Thanks!

@kacole2 this missed 1.12 and is planned for 1.13.. i added the 1.13 milestone

@childsb what work if left in k/k for this feature to go to GA in 1.13?  Is there a list of pending PRs (code, tests and docs) that we can track on our end?

@AishSundar the k/k PR for code and tests is here https://github.com/kubernetes/kubernetes/pull/65829 (needs API review). docs have not been started

@wongma7 I rebased this docs PR to dev-1.13 and reopened it for you. Are you okay to use that PR for the docs for this? https://github.com/kubernetes/website/pull/10100

@tfogo yes, thanks! will be working on it shortly, k/k pr is awaiting approval

Hi @childsb @wongma7 -I'm an enhancements shadow checking in on this issue - sounds like progress is being made - as an FYI code slush is 11/9 and Code freeze is 11/15 - any concerns about making those dates

@wongma7 there hasn't been any progress on https://github.com/kubernetes/kubernetes/pull/65829 for about 7 days. Do we feel confident it's going to merge by tomorrow since that's the beginning of code slush?

@kacole2 @claurence yes, just needs final review from approvers. brought it up in meeting today and they will be looking at it.

@wongma7 I see the PR kubernetes/kubernetes#65829 is actively under review. Please let us know if there is a potential of this slipping 5pm Code freeze tomorrow. Thanks

@AishSundar It likely will slip to next week as it requires lots of approvals. Tests  went green and there are a few last items.

I think this can still make it in today if https://github.com/kubernetes/kubernetes/pull/71100 merges soon

This seems super tight to me. Will watch both PRs today

Hey @erinboyd @childsb @msau42 👋 I'm the v1.14 docs release lead.
Does this enhancement require any new docs (or modifications)?
Just a friendly reminder we're looking for a PR against k/website (branch dev-1.14) due by Friday, March 1. It would be great if it's the start of the full documentation, but even a placeholder PR is acceptable. Let me know if you have any questions!

This feature is remaining beta in 1.14. There are no plans to update docs.

/milestone clear
@msau42 if this landed as beta in v1.13, and is staying beta in v1.14, I'm not sure we as the release team need to be tracking it, please add back if I'm wrong

correct

Hello @msau42 @erinboyd , I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet. This will also require a KEP to be included.
Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.

This is remaining beta in 1.15

Hi @msau42 , I'm the 1.16 Enhancement Lead/Shadow.  Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet. If not's graduating, I will remove it from the milestone and change the tracked label.
Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.
As a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements.
Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.
Thank you.

This feature is remaining beta for 1.16

Hello @msau42, 1.17 Enhancement Shadow here! 🙂
I wanted to reach out to see if this enhancement will be graduating to stable in 1.17?

Please let me know so that this enhancement can be added to 1.17 tracking sheet.
Thank you!
🔔Friendly Reminder
The current release schedule is

Monday, September 23 - Release Cycle Begins
Tuesday, October 15, EOD PST - Enhancements Freeze
Thursday, November 14, EOD PST - Code Freeze
Tuesday, November 19 - Docs must be completed and reviewed
Monday, December 9 - Kubernetes 1.17.0 Released

A Kubernetes Enhancement Proposal (KEP) must meet the following criteria before Enhancement Freeze to be accepted into the release

PR is merged in
In an implementable state
Include test plan and graduation criteria
All relevant k/k PRs should be listed in this issue

Thank you.

We're aiming at GA in 1.17. Created KEP for the feature: https://github.com/kubernetes/enhancements/pull/1288 (it was designed before KEP was a thing).
Remaining work is tracked here: https://github.com/orgs/kubernetes-csi/projects/4

Thanks @jsafrane

/milestone v1.17

/stage stable

One more thing, @jsafrane -- We're only 5 days away from the Enhancements Freeze (Tuesday, October 15, EOD PST). Another friendly reminder that to be able to graduate this in the 1.17 release, KEP must have graduation criteria defined, in an implementable state, and merged in. Thank you!

Hello @msau42 I'm one of the v1.17 docs shadows.
Does this enhancement for (or the work planned for v1.17) require any new docs (or modifications to existing docs)? If not, can you please update the 1.17 Enhancement Tracker Sheet (or let me know and I'll do so)
If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.17) due by Friday, November 8th, it can just be a placeholder PR at this time. Let me know if you have any questions!

@msau42
Since we're approaching Docs placeholder PR deadline on Nov 8th. Please try to get one in against k/website dev-1.17 branch.

/assign @jsafrane

Doc changes: https://github.com/kubernetes/website/pull/17399

Test report with today's sources on GCE
I performed tests required by KEP:

Test that the pods are moved to another nodes and data is retained when the node is drained.

All 37 pods of 37 Deployments were killed on the original node and moved to other nodes, with their content preserved. Symlinks on the original node were cleaned.

Test that the data is retained when kubelet restarts while the pods are running.

No issue at all.

Test that the data is retained when the node reboots. For pods that were moved to another nodes during the outage, test that the newly started node cleaned up their devices.

The pods entered Error state and were restarted after reboot. All pods were restarted on the same node as before. Kubelet was able to find all devices and run the pods after reboot.

Test setup:

3 node cluster, each node could handle 37 pods (otherwise dd and md5sum was terribly slow). It's not much, I could bump nr. of CPUs if required.
GCE PD was used.
Each volume pre-filled with dd if=/dev/urandom and storing its md5sum.
Each pod did md5sum /dev/test-disk every now and then, e.g. during node drain, reboot and so on to simulate some load (read-only, but at least something...)

Hi @msau42 and @jsafrane
I am one of the Enhancements Shadows for the 1.17 Release Team. We are very near to Code Freeze (Nov 14th) for this release cycle. Just checking in about the progress of this enhancement. I don't see any kubernetes/kubernetes PRs related to this enhancement, can you please link them here?
Thank you in advance 😄

This PR is needed: https://github.com/kubernetes/kubernetes/pull/84784

Hi @jsafrane and @msau42 -- tomorrow is code freeze for the 1.17 release cycle. It looks like the k/k PRs have not yet been merged. We're flagging as At Risk in the 1.17 Enhancement Tracking Sheet.
Do you think they will be merged by the EoD of the 14th (Thursday)? After that point, only release-blocking issues and PRs will be allowed in the milestone with an exception.
Thank you!

We are removing this feature from 1.17 and pushing it to 1.18
We want to align moving both this (in-tree) and CSI raw block (https://github.com/kubernetes/enhancements/issues/565) to GA at the same time. If CSI raw block GA slips past 1.18, we can reconsider moving this to GA independently.
/milestone v1.18

@saad-ali Thank you for the update, we will remove from the tracking sheet!

Hello @saad-ali
Are you still planning on graduating this with #565? For your awareness, the enhancement freeze will be January 28th and the code freeze will be March 5th!

/assign @jsafrane
who is planning to work on this for 1.18

@jsafrane @msau42 I assume the comment above means we should we track this for 1.18? Thanks!

Hey @jsafrane @msau42 -
Seth here, Docs shadow on the 1.18 release team.
Does this enhancement work planned for 1.18 require any new docs or modifications to existing docs?
If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)
If doc updates are required, reminder that the placeholder PRs against k/website (branch dev-1.18) are due by Friday, Feb 28th.
Let me know if you have any questions!

Hello @msau42 kube-proxy-9t6v6,
Just a friendly reminder that code freeze for 1.18 is March 05, 2020.
As we track toward code freeze, please list out/link to any PRs you are working on toward graduating this enhancement!

Hello @msau42 @jsafrane
We're getting close to code freeze next week, 05 March 2020
Can you please share any PRs that are in flight for this so that we can properly track the issue? This includes both k/k PRs and placeholder PRs against k/website (branch dev-1.18), which are due by Friday, Feb 28th.

Doc PR: https://github.com/kubernetes/website/pull/19338

We track all issues/PR for GA in this board: https://github.com/orgs/kubernetes-csi/projects/4

Hey there @erinboyd, @screeley44 , @mtanino  -- 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?
In order to have this part of the release:

The KEP PR must be merged in an implementable state
The KEP must have test plans
The KEP must have graduation criteria.

The current release schedule is:

Monday, April 13: Week 1 - Release cycle begins
Tuesday, May 19: Week 6 - Enhancements Freeze
Thursday, June 25: Week 11 - Code Freeze
Thursday, July 9: Week 14 - Docs must be completed and reviewed
Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released
Thursday, August 20: Week 19 - Release Retrospective

If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍
Thanks!

/close
(closing this since the KEP has been implemented)

/milestone clear

/milestone v1.18
(since the enhancement graduated to Stable in 1.18 release cycle)


Created C String to CPP String.py

Description
Made solution for C String to C++ String (in Python)
Issue No.- #283
Checklist

[x] Yes, this task assigned to me.
[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] My Filename is in camelCase format
[x] I have added Problem statement, Problem link in file.

add problem statement and problem link in file as a comment

Done!


inspirational quote added

Added the option to be told an inspirational quote

Okay I'll see what I can do

Okay it now uses a library I found on PyPI


All training log files

Hi, Thanks for your excellent work! Could you please release the log files for shufflenetv2_1.0x and shufflenetv2_0.5x? Thank you so much!

Hi @frank-xwang ,
Attached please find the ShuffleNetV2(0.5x, 1.0x) log files here.
Hope that helps with your reproduction.
ShuffleNetV2_1.0x.log
ShuffleNetV2_0.5x.log

Thank you so much!


Release 1.22.0

Description

Checklist

[ ] My changes follow the contributing guidelines of this project.
[ ] I have performed a self-review of my code.
[ ] I have made corresponding changes to the documentation.
[ ] I have added tests that prove my fix is effective or that my changes work.
[ ] New and existing unit tests pass locally with my changes.

coverage: 94.198%. remained the same
when pulling a8ae9c5a0bf5f526404a37b050931916ccd61fa8 on release/1.22.0
into 73b0f663c2c473fa5a0517315c658bac7cb0b3f4 on main.


Only one active declaration per person

Terminate (change status to terminated) all active declarations linked to specific person_id in case new declaration created:
*active declarations:

status in ('active', 'pending_verification')
is_active = true

Fixed


ENH 2451: skip conditionals

Reference Issues or PRs

What does this implement/fix?
Put a x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[ ] Did you test the pull request locally?
[ ] Did you add new tests?

Any other comments?
This PR is related to the issue stated in ENH #2451:  https://github.com/nebari-dev/nebari/issues/2451
I have added a job to the integration test related github actions. This job acts as a mediary for a boolean environment variable and a conditional statement added to integration test job at it's top level. This was made so that a user with a fork of nebari who do not have access to the credentials for the cloud resources the job needs.
This method was chosen for the following reasons:

In testing, booleans on the step level did not prevent a failing of attempting to access the credentials.
In testing, environment variables could not be used to do a boolean on the job at large.
A flag that was not branch specific was requested by a few users (not stated in ticket) and this solution could provide this.
This avoids adding "push:" statements to the YAML (as opposed to using ignore-branches) which will keep the workflow inherently manual or on a cron job as dictated thus far.

@BrianCashProf can you resolve the pre-commit errors?


Feature request: support creating folders when saving files in Remote Development mode

When saving a file using Remote Development/SSH in VSCode, the save file dialog has no way to create a directory in the desired path if it doesn't exist. This is unlike saving a file locally, where macOS/Windows/Linux's native file picker allows creating folders.
For example:

install the Remote Development pack
ssh to a development machine
create a new file
choose File -> Save
in the "Save As" dialog, enter a path that contains a directory that doesn't exist yet

Current: the dialog just shows "Please enter a path that exists":

There's no button/option to create directories, and I would need to cancel the save, manually create directories, then save again.
Desired: the dialog should offer the user a button/prompt to create the directories that don't exist

I can't remember if this is owned by @alexr00 or @bpasero

duplicate of https://github.com/microsoft/vscode/issues/71425


i need help can you guys give me full steps what to do

i tried everything but it just says i am sorry theres a bug maybe i didsomething wrong downloading i didnt understand the tutorial can you guys give me full steps on downloading

Please describe in details and provide information about:

which version you've downloaded
what options you've chosen from the login screen after launching run.bat
any other behaviours you have noticed

I will close it for now, feel free to reopen it.


webkitgtk3-javascriptcore <IP_ADDRESS>

webkitgtk3-javascriptcore-<IP_ADDRESS> (Jens Petersen<EMAIL_ADDRESS>@juhp) is out of bounds for:

[ ] jsaddle-<IP_ADDRESS> (>=<IP_ADDRESS> && < 0.14). Jens Petersen<EMAIL_ADDRESS>@juhp. @ghcjs

jsaddle.git supports it now so I guess @hamishmack will make a release sooner or later, maybe together with the next leksah release which should hopefully then build in Stackage NIghtly? :-)

Issue closed in the GHC 8 release. If packages have been removed temporarily, please sent a pull request to update build-constraints.yaml (search for GHC 8 or BLOCKED).


Add -warn-long-expression-type-checking= frontend option.

Generates a warning for any expression that takes longer than <limit>
milliseconds to type check. This compliments the existing
-warn-long-function-body=<limit> option.

@swift-ci Please smoke test


SMS MFA Documentation

We need documentation about how to set up the SMS Authenticator. https://medium.com/@bkamaraj/implementing-mfa-using-sms-otp-in-keycloak-0444d1468ec1 is also worth a link.

We already have documentation here: https://github.com/netzbegruenung/keycloak-mfa-plugins/blob/main/sms-authenticator/README.md

True, I forgot about that. We should then either move it to the docs directory or alternatively move the files from there to the relevant plugin subdirectories.


Lap4 se 141

Summary:
This pull request is for updates to the high-fidelity styles, enhancing the visual consistency and aesthetics across the project.
Changes Made:
Refined hi-fi styles, including updates to color schemes, typography, and component layouts.
Made adjustments to padding, margins, and spacing for improved layout consistency.
Incorporated preliminary design feedback and updates.
Notes:
Waiting for further design specifications and feedback to make additional style adjustments.
This PR is actually finished with the styling tasks according to the current design requirements. (Will create new ticket when updated style comes out).

Reviewed and approved.


Add @xylar as a maintainer

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

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

@conda-forge-admin, please rerender

@ocefpaf, I mostly just want to get #1 merged but I figure you can use a hand here (as with so many other feedstocks).

@ocefpaf, if you would merge this, I would greatly appreciate it.  Thanks as always!

Thanks again!

Thanks again!

Thank you for taking yet on another package :smile:


使用SAM进行分割没有反应

我按照这个“https://labelstud.io/blog/get-started-using-segment-anything/#announcing-an-update-to-the-segment-anything-label-studio-backend”
网页的教程进行操作。在label-studio的项目的设置中，models选项里显示是与后端保持connected，但是在打标签的界面使用auto-detect和指定标签进行分割，SAM模型似乎没有加载。

前端启动的部分终端内容：
qin@user-Super-Server:~/Projects/label-studio-ml-backend/label_studio_ml/examples/segment_anything_model$ docker run -it -p 8080:8080     -v /mnt/data/GTAV-dataset/label-studio/mydata:/label-studio/data     --env LABEL_STUDIO_LOCAL_FILES_SERVING_ENABLED=true     --env LABEL_STUDIO_LOCAL_FILES_DOCUMENT_ROOT=/label-studio/data/images     heartexlabs/label-studio:latestst
=> Database and media directory: /label-studio/data
=> Static URL is set to: /static/
=> Database and media directory: /label-studio/data
=> Static URL is set to: /static/
Read environment variables from: /label-studio/data/.env
get 'SECRET_KEY' casted as '<class 'str'>' with default ''
[Tracing] Create new propagation context: {'trace_id': 'f3545253661b4b6a95d3dd2326a691df', 'span_id': '8c1ccf6744101799', 'parent_span_id': None, 'dynamic_sampling_context': None}
Starting new HTTPS connection (1): pypi.org:443
https://pypi.org:443 "GET /pypi/label-studio/json HTTP/1.1" 200 32193
Performing system checks...

System check identified no issues (1 silenced).
June 22, 2024 - 01:21:25
Django version 3.2.25, using settings 'core.settings.label_studio'
Starting development server at http://<IP_ADDRESS>:8080/
Quit the server with CONTROL-C.
[2024-06-22 01:21:27,192] [django.server::log_message::161] [INFO] "GET / HTTP/1.1" 302 0
[2024-06-22 01:21:27,192] [django.server::log_message::161] [INFO] "GET / HTTP/1.1" 302 0
[2024-06-22 01:21:27,274] [django.server::log_message::161] [INFO] "GET /user/login/ HTTP/1.1" 200 5402
[2024-06-22 01:21:27,274] [django.server::log_message::161] [INFO] "GET /user/login/ HTTP/1.1" 200 5402
[2024-06-22 01:21:27,403] [django.server::log_message::161] [INFO] "GET /static/css/main.05101f5b0b98.css HTTP/1.1" 200 15255
[2024-06-22 01:21:27,403] [django.server::log_message::161] [INFO] "GET /static/css/main.05101f5b0b98.css HTTP/1.1" 200 15255
[2024-06-22 01:21:27,404] [django.server::log_message::161] [INFO] "GET /react-app/main.css?v=779ee9 HTTP/1.1" 200 79666
[2024-06-22 01:21:27,404] [django.server::log_message::161] [INFO] "GET /react-app/main.css?v=779ee9 HTTP/1.1" 200 79666
[2024-06-22 01:21:27,555] [django.server::log_message::161] [INFO] "GET /static/css/login.8194c7aa01b8.css HTTP/1.1" 200 6270
[2024-06-22 01:21:27,555] [django.server::log_message::161] [INFO] "GET /static/css/login.8194c7aa01b8.css HTTP/1.1" 200 6270
[2024-06-22 01:21:28,003] [django.server::log_message::161] [INFO] "GET /static/images/heidi-tip.2e3228516929.svg HTTP/1.1" 200 39408

docker-compose.yml文件内容：
version: "3.8"

services:
  segment_anything_model:
    container_name: segment_anything_model
    image: heartexlabs/label-studio-ml-backend:sam-master
    build:
      context: .
      shm_size: '4gb'
      args:
        TEST_ENV: ${TEST_ENV}
    deploy:
      resources:
        limits:
            memory: 8G
        reservations:
            memory: 4G
            devices:
              - driver: nvidia
                count: 4
                capabilities: [gpu]
    environment:
      # specify these parameters if you want to use basic auth for the model server
      - BASIC_AUTH_USER=
      - BASIC_AUTH_PASS=
      # Change this to your model name: MobileSAM or SAM
      - SAM_CHOICE=SAM
      - LOG_LEVEL=DEBUG
      # Enable this to use the GPU
      - NVIDIA_VISIBLE_DEVICES=all
      # specify the number of workers and threads for the model server
      - WORKERS=1
      - THREADS=8
      # specify the model directory (likely you don't need to change this)
      - MODEL_DIR=/data/models

      # Specify the Label Studio URL and API key to access
      # uploaded, local storage and cloud storage files.
      # Do not use 'localhost' as it does not work within Docker containers.
      # Use prefix 'http://' or 'https://' for the URL always.
      # Determine the actual IP using 'ifconfig' (Linux/Mac) or 'ipconfig' (Windows).
      - LABEL_STUDIO_HOST=http://<IP_ADDRESS>:8080
      - LABEL_STUDIO_ACCESS_TOKEN=33a83f670a8112732928385b48e3778991dfe8fc

    ports:
      - 9090:9090
    volumes:
      - "./data/server:/data"

后端启动的终端部分内容：
qin@user-Super-Server:~/Projects/label-studio-ml-backend/label_studio_ml/examples/segment_anything_model$ docker compose up
WARN[0000] The "TEST_ENV" variable is not set. Defaulting to a blank string.
WARN[0000] /home/qin/Projects/label-studio-ml-backend/label_studio_ml/examples/segment_anything_model/docker-compose.yml: `version` is obsolete
[+] Running 1/0
 ✔ Container segment_anything_model  Recreated                                                                          0.0s
Attaching to segment_anything_model
segment_anything_model  | [2024-06-22 01:23:13 +0000] [7] [INFO] Starting gunicorn 22.0.0
segment_anything_model  | [2024-06-22 01:23:13 +0000] [7] [INFO] Listening at: http://<IP_ADDRESS>:9090 (7)
segment_anything_model  | [2024-06-22 01:23:13 +0000] [7] [INFO] Using worker: gthread
segment_anything_model  | [2024-06-22 01:23:13 +0000] [9] [INFO] Booting worker with pid: 9
segment_anything_model  | /usr/local/lib/python3.8/site-packages/pydantic/_internal/_config.py:334: UserWarning: Valid config keys have changed in V2:
segment_anything_model  | * 'allow_population_by_field_name' has been renamed to 'populate_by_name'
segment_anything_model  |   warnings.warn(message, UserWarning)
segment_anything_model  | /usr/local/lib/python3.8/site-packages/pydantic/_internal/_fields.py:160: UserWarning: Field "model_version" has conflict with protected namespace "model_".
segment_anything_model  |
segment_anything_model  | You may be able to resolve this warning by setting `model_config['protected_namespaces'] = ()`.
segment_anything_model  |   warnings.warn(
segment_anything_model  | [2024-06-22 01:23:16,542] [DEBUG] [sam_predictor::__init__::36] Using device cuda
segment_anything_model  | [2024-06-22 01:23:16,658] [INFO] [sam_predictor::__init__::59] Using SAM checkpoint /app/models/sam_vit_h_4b8939.pth
segment_anything_model  | [2024-06-22 01:23:23,142] [DEBUG] [label_studio_ml.api::log_request_info::179] Request headers: Host: localhost:9090
segment_anything_model  | Connection: keep-alive
segment_anything_model  | Sec-Ch-Ua: "Not/A)Brand";v="8", "Chromium";v="126", "Google Chrome";v="126"
segment_anything_model  | Sec-Ch-Ua-Mobile: ?0
segment_anything_model  | Sec-Ch-Ua-Platform: "Windows"
segment_anything_model  | Upgrade-Insecure-Requests: 1
segment_anything_model  | User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
segment_anything_model  | Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
segment_anything_model  | Sec-Fetch-Site: none
segment_anything_model  | Sec-Fetch-Mode: navigate
segment_anything_model  | Sec-Fetch-User: ?1
segment_anything_model  | Sec-Fetch-Dest: document
segment_anything_model  | Accept-Encoding: gzip, deflate, br, zstd
segment_anything_model  | Accept-Language: zh-CN,zh;q=0.9,en;q=0.8
segment_anything_model  | Cookie: username-localhost-8889="2|1:0|10:1717632496|23:username-localhost-8889|44:ZmNjNDg4MjIxYTYxNDY1OTk0MjAyYmQ2MzkyMTUxMTg=|7d348a24c93e522e230fc4c67f5b41b34e909f8f6d66b6206604c66402179093"; _xsrf=2|45ff2730|f32db1ad66796843e679f4ffd3540700|1717632496; _ga=GA1.1.2108444228.1718887086; _gid=GA1.1.1282437830.1719018689; _gat_gtag_UA_129877673_1=1; csrftoken=O9ruc2t2NChdmlMHGkY2jYA5vb6KRqA6Jeov6gihCetYJyGZHMLymGswsWQ5oOBB; _ga_Z4KXEBY4VP=GS1.1.17190186<IP_ADDRESS>90193<IP_ADDRESS>; sessionid=.eJxVT8tuhCAU_RfWanheBpfd9xvM5QJKx8BENOkj_fdqOptZnnfODztyYCMTAUQCBz2RDr2mKHu0ivqQpDOkHJH1rGN1m7Hkb9xzLdPjzkbRsRXbPq11zuWEVjgunDJicDcAJXTHJjz2ZTpa3Kb_KfbCeaR7LJcQPrDMdaBa9i374bIMT7UN7zXE9e3pfSlYsC1nWvnkkvEioQEExTXY4AA8KeIEynkrUCbk8SS00UoovKFF6bUmKThcpS22dj2Ln4-8fbFRK8k5__0Dp3xb0A:1sKpSe:YwUnI9C2m24wi1OH6BzsIQ2hGaqL54CVuj6R7QpxLZY
segment_anything_model  |
segment_anything_model  |
segment_anything_model  | [2024-06-22 01:23:23,142] [DEBUG] [label_studio_ml.api::log_request_info::180] Request body: b''
segment_anything_model  | [2024-06-22 01:23:23,143] [DEBUG] [label_studio_ml.api::log_response_info::185] Response status: 200 OK
segment_anything_model  | [2024-06-22 01:23:23,143] [DEBUG] [label_studio_ml.api::log_response_info::186] Response headers: Content-Type: application/json
segment_anything_model  | Content-Length: 45

我不清楚是哪里出现了问题，有人能帮忙解答吗，感谢！

按照教程格式修改了Labeling Interface，选中auto-detect和KeyPointLabel后可以有效分割


[cpr] update to 1.11.1

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[x] The "supports" clause reflects platforms that may be fixed by this new version.
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

@COM8

Thanks for the update!


golangci-lint: 1.51.0 -> 1.51.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/golangci/golangci-lint/releases.
meta.description for golangci-lint is: Fast linters Runner for Go
meta.homepage for golangci-lint is: https://golangci-lint.run/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.51.1 with grep in /nix/store/qxm243adp67s49363377w84cjaarlfsz-golangci-lint-1.51.1
found 1.51.1 in filename of file in /nix/store/qxm243adp67s49363377w84cjaarlfsz-golangci-lint-1.51.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
golangci-lint
vimPlugins.vim-go

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qxm243adp67s49363377w84cjaarlfsz-golangci-lint-1.51.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A golangci-lint https://github.com/r-ryantm/nixpkgs/archive/ca4904aa828daf954587cbda85902e24252a0390.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qxm243adp67s49363377w84cjaarlfsz-golangci-lint-1.51.1
ls -la /nix/store/qxm243adp67s49363377w84cjaarlfsz-golangci-lint-1.51.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

golangci-lint
vimPlugins.vim-go

Maintainer pings
cc @anpryl @manveru @Mic92 for testing.

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

2 packages built:

golangci-lint
vimPlugins.vim-go

@ofborg build vimPlugins.vim-go


Manage secrets

💡 Summary
Move all sensitive data -- in particular, CELERY_BROKER_URL -- into the secrets raft.
Motivation and context
We shouldn’t store any sensitive data in source control. Additionally, we want a layer of abstraction between these containers and the set of credentials. This makes for better secret management.

I think the path forward may be to define a Flower configuration in admiral.yml.


Improved event sequencing and dispatching

In https://github.com/hyperledger/firefly/issues/493#issuecomment-1035538293 we found  we missed an event due to the dispatcher skipping past events:
[2022-02-10T20:32:14.213Z] DEBUG Dispatcher event state: readahead=0 candidates=5 matched=5 inflight=0 queued=0 dispatched=5 dispatchable=0 lastAck=37559 nacks=0 highest=37559 pid=1 role=ed[d2ff7b72-504d-40dd-ab3e-e325c2b7a5d9] sub=3cf508e4-21a7-4f00-8ad0-a6d08a0703d0/default:perf_54c7faaf-ad...
[2022-02-10T20:32:14.366Z] DEBUG Dispatcher event state: readahead=0 candidates=1 matched=0 inflight=0 queued=0 dispatched=0 dispatchable=0 lastAck=0 nacks=0 highest=37595 pid=1 role=ed[d2ff7b72-504d-40dd-ab3e-e325c2b7a5d9] sub=3cf508e4-21a7-4f00-8ad0-a6d08a0703d0/default:perf_54c7faaf-ad...

The root cause here is we are writing events concurrently in many goroutines, using different DB transactions - so it's not possible to detect the order of those via a separate DB listener.
In this issue we will track the solution.

After lots of thinking on variations to the below (depending on how we manage connections, and who's in charge of generating the sequence numbers) - it felt like it comes to down to three main options (having pre-ruled out blocking V1.0 for the introduction of NATS/Redis or other similar persistent queue technology as a pre-req of running core):
1) Have a single go routine writing to the DB, to ensure the commits are clear

Pros:

No change to event detection logic

Cons:

The DB transactions are separate, so it's hard to work out which to do first - emit the event, or complete the updates in the DB that the event relates to
SQLite cannot handle multiple concurrent DB connections, so (with SQLite at least) you cannot block the main business logic routine waiting for the flush of the event

2) Update event detector to block until any gaps are filled

Pros:

No change to event emission logic

Cons:

If there is ever a case that we have a gap legitimately - such as a DB rollback - we need a recovery procedure

Possibly a variation on (1) - have a single Event Queue that is responsible for writing events to the database. Any place in the code that needs to write an event does it through this queue. Its AddEvent method would take an Event and also a callback which can contain arbitrary database logic. These events would be written to the database in the order they are queued, and each event would be written transactionally with the other logic supplied.
This would allow callers to include the database operation that marks a thing "done" alongside the event itself (such as moving a message to "confirmed"). If there's a crash or restart, things that weren't completed should be parsed again and it should pick up where it left off.

Hmm but moving the event queue to another thread will introduce other issues. Some callbacks, such as TokensTransferred, rely on all processing to be done successfully and synchronously before the connector event is ack'd. Moving the event logic out of that flow means the ack may get sent prematurely - you could lose the event if you crash after acking but before the event queue is flushed.

Guess the sender could block waiting on the event queue to process its event though. So the sender does as much upfront database logic as it can, then ends any database transaction, then submits the final step(s) to the Event Queue along with the Event, and blocks until that item is processed.

Another option: It's possible this could be handled at the database plugin level - for instance, Postgres should be able to enforce it with table-level locks within transactions that insert events. But unsure if pushing it to the database is the right answer here?

While we don't want to put too many restrictions on the database implementation in a general sense, I think it could be valid to say that the event storage in particular must be able to sequence things reliably (and that storage can be a database with locks, or a true event queue like Redis). Just one angle to consider.

Ok, this is really helpful.
I'm thinking about the laws of physics of events (things that would be true even if we were using a separate event system) - one thing has to logically happen "first" in an at-least-once delivery context.
So the trade-off on the design is between:
a) Guaranteeing the order is going to be the same for all consumers of the event
b) Losing the event in the case of a crash scenario, without repeating the action
c) Emitting the event before the thing the event relates to, is flushed to the DB
d) Delaying the event stream
I assert that (b) is most worrying, and then (c) is the most painful for applications to develop around.
So I'd like to focus on a solution that compromises most on (a) and (d).
Thinking it through, I believe (2) is actually the right approach - with a sufficiently long delay to handle gaps in the stream.

sufficiently long delay

picking this number is the real trick 😉

Yeah - understood. I've added a commit here: https://github.com/hyperledger/firefly/pull/501/commits/27637e470f9d8509da8c31bab00949dbd7eb798f
The number picked there is 30secs. This means in the case of a database rollback, we might stall the transaction stream for 30seconds. I was thinking we can add rollback detection and emission over a channel to this code to negatively fill gaps - if that becomes a problem. Because the sequence is something we return on inserts.

I agree with the risk analysis, btw. Seems like we're solving both (b) and (c) with database transactions, in both the current code and any proposed solutions (ie the event and the thing it references are committed in the same database transaction). That will actually require a re-think if we move to another eventing system, right?
So the proposed solution strongly enforces that the seq assigned by the database is increasing in a contiguous manner, and pauses for 30 sec if it ever skips. I know that's generally true, but I still have some qualms about this approach... and I wonder how it would stack up against a database locking solution. In both cases we're putting a rule on how the database layer behaves, and we're blocking for some amount of time during parallel inserts to ensure strong ordering. Feels a bit like a lock by another name 🤔

Look forward to discussing it a bit more with a whiteboard tomorrow.

That will actually require a re-think if we move to another eventing system, right?

Yeah - that's definitely not lost on me - and potentially it means an analysis of each place we emit an event, and splitting DB transactions up. I'd like to find something that lets us have an acceptable approach for now, and address that later.

Maybe we can try a test with an EXCLUSIVE table lock on the events table being added to any transaction that inserts into the events table, as another data point on the journey.

... although even with that, I'm not sure we're guaranteed of consecutive sequences - if we let the database allocate the sequence - so that might combine with sequence allocation in a leader-elected / singleton FireFly runtime.

It is possible to build gapless assignment by using exclusive locking of a table containing a counter; but this solution is much more expensive than sequence objects, especially if many transactions need sequence numbers concurrently.

And a good blog, that confirms the understanding and trade-offs discussed throughout here (including an example of what "using exclusive locking of a table containing a counter" looks like):
https://www.cybertec-postgresql.com/en/gaps-in-sequences-postgresql/

a test with an EXCLUSIVE table lock on the events table being added to any transaction that inserts into the events table

Yea, this is exactly what I was thinking. Seems like the other notes confirm this would generate a stable sequence at the expense of performance, which I think is what we're trying to achieve in this case.

ok - we had a positive run with the code that expects gapless sequences under normal operation, and tries to cope with them via delay.
I'm stashing that in this branch: https://github.com/kaleido-io/firefly/tree/gapless-sequences
Then let's give an EXCLUSIVE table lock a go, as a way to not rely on a gapless sequence - rather just what the DB intents to supply which is a sequence that increases (post commit).

Created this commit for the exclusive lock test: https://github.com/kaleido-io/firefly/commit/1d3cc7d1de4f9bb61b9701595c92d1f076363f17

Yeah, good distinction that the locking solution blocks the writers instead of the reader.
I'm still hung up on the first solution because it introduces a tight binding between the application code and the implementation details of the database sequencer, and because it still carries a small risk of (b) due to the "give up after X seconds" clause.
My impression is that the locking solution brings the (b) risk to zero, but at the expense of much lower write performance during high write load.
Probably getting into hand-wavy territory here though without measuring it.


[CodeQuality] Fix flipped check condition only remove property when unused on NarrowUnusedSetUpDefinedPropertyRector

see https://github.com/rectorphp/rector-phpunit/pull/388#pullrequestreview-2411971619

it seems covered at https://github.com/rectorphp/rector-phpunit/commit/f24bef525133df61ef556e34965f45625c8215c6


Timer concurrency logic

As discussed, this redoes the timer management to (hopefully) remove all race conditions.

The timer object is only allocated when starting replication, and disposed when exiting it.
When disposing, we wait until callbacks have completed (this is a bit tricky to do asynchronously on netstandard2.0, but I think it's OK). This means that we can never have timer callbacks running when StartReplication has returned.
A race condition may still make a feedback packet arrive at PG after replication has completed. I have done a check, and PG doesn't mind if a feedback message is received in idle state (outside of replication), so we should be good.
The above also means that we don't need to suspend the timer when cancelling replication.
Finally, it's worth noting that if SendFeedback gets stuck (because of a network partition), StartReplication will wait. As far as I can tell, this isn't a problem - we should already have timeouts in place for this case, and there's nothing special with this scenario compared to SendFeedback blocking anywhere else.

/cc @Brar and @vonzshik for an extra pair of eyes for this concurrency-sensitive business

Merged via c781f9de4f26d67c27f269ebb6b82f1c7ea8791e


[Event Request] New Function CallReportCopyPurchaseDocument  – Action "CopyDocument"

[Event Request] New Function CallReportCopyPurchaseDocument  – Action "CopyDocument"
Can we please have a new function CallReportCopyPurchaseDocument with Handled Pattern for the action "CopyDocument" of the purchase document pages.
Pages:
•	Page 49 "Purchase Quote"
•	Page 50 "Purchase Order"
•	Page 51 "Purchase Invoice"
•	Page 52 "Purchase Credit Memo"
•	Page 509 "Blanket Purchase Order"
•	Page 6640 "Purchase Return Order"
Alternatively, you could also include the handled patterns in every call.
We need the changes because the reports cannot be customized.
Can you please have a look at the tooltips of the actions, some of them talk about sales document.
    // >>>>>>>>
    procedure CallReportCopyPurchaseDocument(var PurchhaseHeader: Record "Purchase Header")
    var
        CopyPurchDoc: Report „Copy Purchase Document“;
        IsHandled: Boolean;
    begin
        OnBeforeCallReportCopyPurchaseDocument(PurchhaseHeader, IsHandled);
        if IsHandled then begin
            CopyPurchDoc.SetPurchHeader(PurchhaseHeader);
            CopyPurchDoc.RunModal();
            Clear(CopyPurchDoc);
        end;
    end;

    [IntegrationEvent(false, false)]
    local procedure OnBeforeCallReportCopyPurchaseDocument(var PurchhaseHeader: Record "Purchase Header"; var IsHandled: Boolean)
    begin
    end;
   // <<<<<<<<

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


WIP: Improve unordered-containers API docs.

This integrates the content from #249 into the module docs themselves instead of having a separate Tutorial module.
Changes:

Improve top level module docs
Include examples for all functions
Call out complexity separately from function summary

@sjakobi wdyt about this compared to having separate external docs / tutorial modules?

@sjakobi made some changes to formatting and added some comments as you suggested.

What's the motivation for shuffling around the complexity annotations though. Doesn't that make the documentation much longer?

The complexity of the function isn't the most important thing about the docs, and it feels kinda weird for the docs which describe what the functions do to start with O(something). This also leaves space for commentary on the complexity (see 'HashSet.size' docs) while keeping the formatting consistent. It does make the docs longer, but I don't think optimizing for doc length over organization is the right trade-off.

Also, switch from bold to emphasis for the complexity clause on the functions at the bottom of the docs. I personally prefer the emphasis instead of bold because it doesn't compete with the function names for attention.

What's the motivation for shuffling around the complexity annotations though. Doesn't that make the documentation much longer?

The complexity of the function isn't the most important thing about the docs, and it feels kinda weird for the docs which describe what the functions do to start with O(something). This also leaves space for commentary on the complexity (see 'HashSet.size' docs) while keeping the formatting consistent. It does make the docs longer, but I don't think optimizing for doc length over organization is the right trade-off.

I haven't really made up my mind about it, but I'd prefer to discuss it separately, i.e. not as a part of this PR.

Also, switch from bold to emphasis for the complexity clause on the functions at the bottom of the docs. I personally prefer the emphasis instead of bold because it doesn't compete with the function names for attention.

Which bold complexity clauses does this refer to?

I haven't really made up my mind about it, but I'd prefer to discuss it separately, i.e. not as a part of this PR.

Sure, I can move them back to being inline.

Which bold complexity clauses does this refer to?

Complexity: O(n)
vs.
Complexity: O(n)

I'm a bit torn. I agree with much of your rationale, but I don't we want the u-c Haddocks to become an "introduction to Haskell". Would it make sense to put a full example with very little explanation in the module intro? Maybe. I'm sure we don't want to get into "how to enable extensions in GHCi". That's just far out of scope here.

@treeowl how's this?

@sjakobi should I do the HashMap docs in this PR as well or a follow-up?

@sjakobi should I do the HashMap docs in this PR as well or a follow-up?

Let's make a decision on HashSet first.

Done. ptal!

Nearly done, IMHO! Great job!

Sorry for the delay, updated typeclass references. If there's nothing else I can squash and merge.

jk, linknig to "Data.Eq.Eq" isn't valid :/

jk, linknig to "Data.Eq.Eq" isn't valid :/

It should be 'Data.Eq.Eq' I think, with single quotes or alternatively backticks. I'll take another look tomorrow.

jk, linknig to "Data.Eq.Eq" isn't valid :/

It should be 'Data.Eq.Eq' I think, with single quotes or alternatively backticks. I'll take another look tomorrow.

Note that haddock might still produce a warning since the identifier is not in scope. But it should be able to produce the correct link anyway.
Also, please in include Hashable: 'Data.Hashable.Hashable'.

@treeowl Could you please review?
@m-renaud If you need help with the final touches to the markup, I can prepare a PR against yours.

@treeowl Could you please review?

Any @emilypi, too!? :)

I'll have time this weekend @sjakobi 😄

I'll have time this weekend. Eq and Ord linked properly but Hashable didn't for some reason :/

@sjakobi at least locally I can't get Hashable to link, any suggestions?

@sjakobi at least locally I can't get Hashable to link, any suggestions?

It actually works for me when I build the documentation with cabal haddock --enable-documentation.
What command did you use? I suspect you maybe just didn't build the haddocks for hashable too.

For sure, thanks for the thorough review! I'll squash the commits and wait for the others to review before merging :)

@treeowl, @emilypi I'd hate to see this PR languish. Could you please review?
If there are no reviews, I'll merge this on Monday (2020-07-20) or soon after.

Thanks again, @m-renaud! :)

No problem! Should I do the same for HashMap next?

Should I do the same for HashMap next?

IMHO, yes please! :)
I'd feel more comfortable if @treeowl and @emilypi would signal their approval too though.


Allow to extend agent communication from external crates

Fixed and reopened #719
This PR will open communication data structures to allow external crates to implement custom Agents for their purposes. For example wasi worker implementation which provides ~2x faster execution for wasm target https://github.com/dunnock/wasi-worker.
After opening structures it will be possible to implement custom trait for Agent with Reach=Public to allow custom initialization, also it will allow to provide custom implementation for Responder trait. It should be enough to have custom Agent implementation to be able to communicate with main yew application. Example https://github.com/dunnock/wasi-worker/blob/master/examples/yewworker/src/main.rs

Looks good!


Revert "Variable was being enclosed in an array in comparison example"

Reverts yiisoft/yii2#9147

As far as I see, the original code is correct: http://www.yiiframework.com/doc-2.0/yii-di-container.html#get()-detail

Perhaps the example should be adjusted to
$engine = $container->get('app\components\SearchEngine', [$apiKey, ['type' => 1]]);

Resolved by commit 77c1fcf. I think this example will not produce any confusion now.


Tooltips on button hover

The buttons in the design system were created ahead of the tool tip.
We need to go back and add in a tooltip as a label for the hover/focus styles.
https://www.figma.com/file/bMhG3KyrJF8vIAODgmbeqT/Design-System?node-id=3438%3A125786
Acceptance Criteria

buttons have a tooltip that appears on hover for square button and icon button types
label text matches what screen reader reaches

After working on this I believe that we should not do this ticket at all. Here's the reasons for why I think this should be done outside of the button component

Having a tooltip displayed on Icon buttons or buttons without text would be very useful. However, it would be redundant for button's tooltip to display the text that is already displayed in the button.

This is not straight-forward implement for every edge case.
a. Buttons may have children which aren't just text (like icons). We'd need to find the aria-label instead of the text content
b. This gets more complicated if the button has an abstract number of nested children. Although unlikely that it would have more than one nested span, we still would have to traverse those children to grab any/all text that is displayed or aria-labels to display to the user.

If we still wanted to do this but not have the button infer the text to display from its children, we could pass in a separate tooltip label as a prop to the button. This API feels clunky though since we could just use the <Tooltip /> component and keep the <Button /> API simpler.

It's easier to apply a tooltip to a button on a case-by-case basis. Not all buttons need tooltips, and in the events that they do it would be easier to wrap the button with the <Tooltip /> component that can be styled for any use case. This should be "opt-in" behavior rather than having every button display this redundant behavior.

@barklund what do you think? IMO we should not add this to the Button component.

I definitely agree with all that. We can just use the tooltip component where applicable. We'd need to control placement anyway, as it will vary with the button. No need to make the button API more complex when wrapping in another component is so straightforward.

Okay cool! @BrittanyIRL should we close this ticket?

yup! thanks for the discovery here!


optifinePackages: init

Motivation for this change
Since old versions of this game are still played a lot because of their mod support, we want all versions supported by upstream available in nixpkgs.
I was unfortunately not able to find a version list to write an update script, but I think this should be fine. Updates are rather infrequent anyway, especially for older versions.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] 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.

cc @legendofmiracles @sikmir might you be interested in reviewing this?


Making a Variable Optional

Is there a way to define a variable in a template - but if no value if provided for it - allow to be be blank?

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

ID: dd7e0bd3-1f7d-d7b6-cc72-5ef63c31b46a
Version Independent ID: dae87abd-b73d-9120-bcdb-6097d4b40f2a
Content: Variables - Azure Pipelines
Content Source: docs/pipelines/process/variables.md
Product: devops
Technology: devops-cicd
GitHub Login: @steved0x
Microsoft Alias: sdanie

Thanks for your question. It looks like your question isn't an issue with the documentation, but an issue or question specific to your implementation or a bug in the product itself.
For help with a specific task, here are a couple of options where you might consider asking your question:

Azure DevOps on Stack Overflow
Azure DevOps Support Bot

If you've encountered an issue with the product itself, to make sure it gets in front of the right people, please submit your bug here.
If you have an idea for improving the product, please submit your idea here.


Unable to generate declaration files d.ts

Hi guys,
I have problem with generating .d.ts files. tsc won't generate them for me, even though I have declaration: true in tsconfig.json.
I tried following 5 cases:

having no include or files section - in this case, tsc complained about overwriting existing d.ts files in output. It is similar to this issue https://github.com/Microsoft/TypeScript/issues/16749
having no include or files section and outputDir in exclude
having no include or files section and specifying declarationDir (and also having it in exclude)
having includes section
having files section

except the first case, which at least showed error, none of other 4 cases showed any error, neither or produced d.ts files as expected.

TypeScript Version:  2.0.10, 2.4.2, 2.6.2, next, I haven't tried on any other
tsconfig.json Code
{
    "compilerOptions": {
        "noImplicitAny": true,
        "module": "commonjs",
        "target": "es5",
        "emitDecoratorMetadata": true,
        "experimentalDecorators": true,
        "declaration": true,
        "moduleResolution": "node",
        "outDir": "./dist",
        "declarationDir": "./dec",
        "noEmitOnError": false
    },
    "include": [
      "src/index.ts"
    ],
    "exclude": [
      "node_modules",
      "tests"
    ]
}

(You can also have a look on my repo, it is really small one: https://github.com/klinki/HumanizeDuration.ts/tree/separate-languages )
Expected behavior:
.d.ts files should be generated when declaration: true is in tsconfig.json
Actual behavior:
It is not generated.

I can not see this locally. if you believe this is a compiler bug and not a configuration issue, please provide a minimal reproduction of the issue.
c:\test\20302\HumanizeDuration.ts>git log -2
commit 676c3182dd16e4f17486acf8d147c94cefff12c9 (HEAD -> master, origin/master, origin/HEAD)
Author: Nightapes<EMAIL_ADDRESS>Date:   Mon Aug 22 20:34:10 2016 +0200

    docs(README): add build status

commit 64f3764cceb53cc784cf4d44303bb88f8398f8b6
Author: Nightapes<EMAIL_ADDRESS>Date:   Mon Aug 22 20:28:38 2016 +0200

    docs(CONTRIBUTING): add CONTRIBUTING.md

c:\test\20302\HumanizeDuration.ts>git status
On branch master
Your branch is up-to-date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

        modified:   tsconfig.json

no changes added to commit (use "git add" and/or "git commit -a")

c:\test\20302\HumanizeDuration.ts>type tsconfig.json
{
    "compilerOptions": {
        "noImplicitAny": true,
        "module": "commonjs",
        "target": "es5",
        "emitDecoratorMetadata": true,
        "experimentalDecorators": true,
        "inlineSourceMap": true,
        "inlineSources": true,
        "declaration": true,
        "moduleResolution": "node"
    },
    "files": [
        //"typings/main.d.ts",
        "humanize-duration-ts.ts",
        "./src/humanize-duration.interface.ts",
        "./src/humanize-duration.lang.ts",
        "./src/humanize-duration.ts",
        "./tests/humanize-duration.spec.ts"
    ]
}

c:\test\20302\HumanizeDuration.ts>tsc --v
Version 2.7.0-dev.20171122

c:\test\20302\HumanizeDuration.ts>tsc --p tsconfig.json

c:\test\20302\HumanizeDuration.ts>dir *.d.ts
 Volume in drive C is OSDisk
 Volume Serial Number is 9E6D-383F

 Directory of c:\test\20302\HumanizeDuration.ts

11/28/2017  10:26 AM               141 humanize-duration-ts.d.ts
               1 File(s)            141 bytes
               0 Dir(s)   6,888,452,096 bytes free

c:\test\20302\HumanizeDuration.ts>dir src\*.d.ts
 Volume in drive C is OSDisk
 Volume Serial Number is 9E6D-383F

 Directory of c:\test\20302\HumanizeDuration.ts\src

11/28/2017  10:26 AM               685 humanize-duration.d.ts
11/28/2017  10:26 AM               740 humanize-duration.interface.d.ts
11/28/2017  10:26 AM               379 humanize-duration.lang.d.ts
               3 File(s)          1,804 bytes
               0 Dir(s)   6,888,448,000 bytes free

sorry, it wasn't in master, but in separate-languages branch which was on the link. For convenience, I just merged it into master.

c:\test\20302\HumanizeDuration.ts>git remote -v
origin  https://github.com/klinki/HumanizeDuration.ts.git (fetch)
origin  https://github.com/klinki/HumanizeDuration.ts.git (push)

c:\test\20302\HumanizeDuration.ts>git pull
Already up-to-date.

c:\test\20302\HumanizeDuration.ts>git status
On branch master
Your branch is up-to-date with 'origin/master'.

nothing to commit, working tree clean

c:\test\20302\HumanizeDuration.ts>tsc --v
Version 2.7.0-dev.20171122

c:\test\20302\HumanizeDuration.ts>tsc  --listEmittedFiles
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/humanize-duration.interface.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/humanize-duration.interface.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/humanize-duration.lang.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/humanize-duration.lang.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/en.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/en.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/humanize-duration.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/humanize-duration.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/ar.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/ar.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/ca.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/ca.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/cs_CZ.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/cs_CZ.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/da.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/da.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/de.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/de.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/es.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/es.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/fi.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/fi.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/fr.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/fr.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/gr.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/gr.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/hu.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/hu.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/id.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/id.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/it.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/it.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/ja.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/ja.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/ko.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/ko.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/lt.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/lt.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/ms.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/ms.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/nl.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/nl.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/no.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/no.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/pl.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/pl.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/pt.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/pt.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/ru.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/ru.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/sv.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/sv.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/tr.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/tr.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/uk.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/uk.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/vi.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/vi.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/zh_CN.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/zh_CN.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/zh_TW.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/zh_TW.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/index.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/lang/index.d.ts
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/index.js
TSFILE: c:/test/20302/HumanizeDuration.ts/dist/index.d.ts

hmm that's strange, it works on my second computer which is running Windows...
I will test it again on work computer.

I'm closing it, because it works now. Unfortunately I updated system meanwhile, so this could change the environment and I cannot reproduce it now.


AA Add Timeline View

Description
This fixes #issueNumber.

How to test the feature:

[ ]
[ ]

Checklist - did you ...

Test your changes with

[ ] REACT_APP_COUNTRY=rbd yarn start
[ ] REACT_APP_COUNTRY=cambodia yarn start
[ ] REACT_APP_COUNTRY=mozambique yarn start
[ ] Add / update necessary tests?
[ ] Add / update outdated documentation?

Screenshot/video of feature:

Two small things:

window 1 and window 2 should display the same data
the AA view should initialize to the global view as it did before


Choose between flow or Typescript parser

The babylon parser loads the flow plugin by default: https://github.com/oliviertassinari/i18n-extract/blob/093abee3d3b1e0e11769441ed606baa86e64b391/src/extractFromCode.js#L51
We use typescript in our codebase so we got a error while running the script. Can we add an option to choose between flow or typescript?

@mathieuletyrant I believe Babel 7 now supports TypeScript. We can try to use the Flow plugin alongside the TypeScript plugging. If it doesn't work, I guess we need to provide an option to chose between the two.

I tried to migrate to Babel 7 with @babel/parser instead of babylon with flow & typescript plugins and I got this error :

I think we must provide an option to choose between the two.

I think we must provide an option to choose between the two.

@mathieuletyrant You are right, we can't https://github.com/babel/babel/blob/9d244ae66b6561b5d031bdb4e4eaacd043dcbbb7/packages/babel-parser/src/plugin-utils.js#L69, we need an option 👍.


Please help me. I can't run it

I try to run the evilginx2 it keep saying
Make: go : No such file or directory
Make : ××× ( makefile:8: build) error 127
Please  need help to run it please.
Help me you can write me here or email<EMAIL_ADDRESS>Or telegram or WhatsApp<PHONE_NUMBER>
Please someone should please help me.
Thanks

It have to do with your go installation make sure go is upto date

The go is upto date.  Go1.18.2 latest version l have.  Please if you have
private mail l can communicate so you help me out please
On Saturday, May 21, 2022, Manmade404 @.***> wrote:

It have to do with your go installation make sure go is upto date
—
Reply to this email directly, view it on GitHub
https://github.com/kgretzky/evilginx2/issues/780#issuecomment-1133649412,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXRFW5X36LNVEEZSHVQJB6LVLD3ZXANCNFSM5WN3F6MA
.
You are receiving this because you authored the thread.Message ID:
@.***>

You can reach out to the developer on icq @mrgretzky he helped me once

It's looking for go, and telling you there's no such file or directory.
Try typing whereis go at the command line and posting the output here.

You can reach out to the developer on icq @Mrgretzky he helped me once

you need to be ban. Why are you referring people to your scamming scheme? Does that ID look like the developer to you? You need to stop it else you will get ban.

have you tried screaming at it?

I try to run the evilginx2 it keep saying
Make: go : No such file or directory
Make : ××× ( makefile:8: build) error 127
Please need help to run it please.
Help me you can write me here or email<EMAIL_ADDRESS>Or telegram @ciabnm
Please someone should please help me.
Thank


Update sweetalert2

Looks good, thanks @andreeib . Also tried looking at the failing test, but can't seem to find out the reason why it fails...


Type checker

This is probably on the scale of "very hard"

https://github.com/kaleidawave/ezno/

Enzo isn't far enough along yet to really be considered. We will most likely be using a snapshotted TSC until STC becomes stable enough.

Closing this for now, we've moved away from TS.


fix: remove FixedSizeArena

Which issue does this PR close?
Closes #762
Rationale for this change
The FixedSizeArena is just a demo whose correctness and unit tests are missing, and it may make people confusing. So let's remove it.

What changes are included in this PR?
Remove the FixedSizeArena.

Are there any user-facing changes?
None.

How does this change test
No need to test.

Codecov Report

Merging #772 (36bd6e6) into main (50471c0) will decrease coverage by 0.08%.
The diff coverage is 100.00%.

:exclamation: Current head 36bd6e6 differs from pull request most recent head 961a386. Consider uploading reports for the commit 961a386 to get more accurate results

@@            Coverage Diff             @@
##             main     #772      +/-   ##
==========================================
- Coverage   68.48%   68.41%   -0.08%
==========================================
  Files         296      295       -1
  Lines       46648    46592      -56
==========================================
- Hits        31947    31876      -71
- Misses      14701    14716      +15

Impacted Files
Coverage Δ

components/arena/src/lib.rs
100.00% <ø> (ø)

analytic_engine/src/instance/read.rs
77.85% <100.00%> (-0.31%)
:arrow_down:

analytic_engine/src/row_iter/mod.rs
100.00% <100.00%> (ø)

... and 8 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Test with random cross attention

Hi, this is great work!
I wanted to test having arbitrary mask, but cannot get it to work. I was wondering if this is the right / wrong way to do it? I tried it with the code below, but with mask_mod2 I get
../aten/src/ATen/native/cuda/IndexKernel.cu:93: operator(): block: [1841,0,0], thread: [32,0,0] Assertion -sizes[i] <= index && index < sizes[i] && "index out of bounds" failed.
.
.
.
... lib/python3.11/site-packages/torch/_ops.py:1116, in OpOverloadPacket.call(self, *args, **kwargs)
1114 if self._has_torchbind_op_overload and _must_dispatch_in_python(args, kwargs):
1115     return _call_overload_packet_from_python(self, args, kwargs)
-> 1116 return self._op(*args, **(kwargs or {}))
RuntimeError: CUDA error: device-side assert triggered
Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.
===> example code:
import torch

from torch.nn.attention.flex_attention import (
    create_mask,
    create_block_mask
)

q = torch.randn([1, 1, 162, 16])
k = torch.randn([1, 1, 5248, 16])
v = torch.randn([1, 1, 5248, 16])

zrand1 = torch.randint(0, 2, [k.shape[2]], device="cuda")
def mask_mod1(b, h, q_idx, kv_idx):
    return zrand1[kv_idx] > 0

zrand2 = torch.randint(0, 2, [q.shape[2], k.shape[2]], device="cuda")
def mask_mod2(b, h, q_idx, kv_idx):
    return zrand2[q_idx, kv_idx] > 0

mask_test1 = create_mask(mask_mod1, None, None, q.shape[2], v.shape[2], "cuda")
mask_test2 = create_mask(mask_mod2, None, None, q.shape[2], v.shape[2], "cuda")

# seems to work ...
block_mask1 = create_block_mask(mask_mod1, B=None, H=None, Q_LEN=q.shape[2], KV_LEN=v.shape[2])

# does not work :-(
block_mask = create_block_mask(mask_mod2, B=None, H=None, Q_LEN=q.shape[2], KV_LEN=v.shape[2])

sequence length was not multiple of 128


Add default groups configuration

@crobby @accorvin  WDYT?

@crobby @accorvin WDYT?

Hoping to try this today.
Once we have this in, does it become mandatory that when setting up the IdP stuff in OSD that the auth that gets set up has these groups?  ie:  How broken would QE be if we don't get them this info ahead of time?

How broken would QE be if we don't get them this info ahead of time?

They wouldn't be able to login to JH, so pretty broken.
Quick fix for them, before they have the right groups etc in place, can be to just se the modified label to true and leave the groups empty - that would make it work like it works in upstream ODH

/lgtm


fixed wrong behaviour of nearest date search

This is hotfix for not correctly working of search of the nearest date in list of selectable days.
What is wrong: mCalendar is initialised with current time and date, date is later changed to requested date obtained from newInstance(). Time of mCalendar (hour, min, sec, milllis) leaves unaffected. And this mCalendar variable is compared with values from selectableDays array. When selectableDays are rounded to midnight (and this is our case), mCalendar with actual date is after midday wrongly set to +1 day (because of smaller diff between time of mCalendar and start of tomorrow). All compared dates have to be rounded to midnight.
This is probably same issue as https://github.com/wdullaer/MaterialDateTimePicker/issues/200
Thank you!

Good catch.
I was just refactoring this code to implement a new feature.
I'll just implement the rounding to midnight, to save you the hassle of having to rebase.
Btw: it would have saved you some effort if you'd just let trimToMidnight() take a Calendar object rather than a Date


I need help

I'm a novice programmer and I want to use GMapsFX for a project in Eclipse.
I don't understand how to use this API, can someone write some steps to setup a new project?
I know it is probably very simple but I would be gratefull for an explanation.
Thanks,
dragoBerto

MainApp.java contains what is basically a sample project to get started with. I have no idea how Eclipse works, but you should be able to add the jar file to a new project and get started using the examples in there.
https://github.com/rterp/GMapsFX/blob/master/GMapsFX/src/main/java/com/lynden/gmapsfx/MainApp.java

Ok but there's no .jar file to download for 2.0.9 release, where can I find it?
If I install the .jar file with Maven will I be able to launch the MainApp?
Thanks for your time,
dragoBerto


Porting StorageClass to Dashboard from Ember

rancher/dashboard#2185
Notes:

I'm not sure if my provisioner type for custom is correct. Ember didn't function at all for custom. Mine does save and can be retrieved but I'm not sure how I'd verify further.
The view page is just the edit page in view mode

Custom is poorly labeled but that field is "taggable" in Ember so you type the name you want into the dropdown (and then it does work).  So you need the same thing, or a separate field if you choose custom to enter what the provisioner name is.

Reclaim Policy and Binding mode show up as radios with no default selected.

  We don't necessarily have to do these now (or at all) since you can still use them with "custom", but there should be an intentional decision one way or the other.

Custom is poorly labeled but that field is "taggable" in Ember so you type the name you want into the dropdown (and then it does work).  So you need the same thing, or a separate field if you choose custom to enter what the provisioner name is.

Reclaim Policy and Binding mode show up as radios with no default selected.

  We don't necessarily have to do these now (or at all) since you can still use them with "custom", but there should be an intentional decision one way or the other.

  We don't necessarily have to do these now (or at all) since you can still use them with "custom", but there should be an intentional decision one way or the other.

@vincent99 Who do we need to talk to to make this decision? Neil or Denise?

I made custom taggable and the necessary changes to support that.
I gave reclaim and binding default values.

Let me know who I should read out to and I'll get an answer on the provisioners behind the feature flag.

We'll add a separate issue for providers hidden by the unsupported-storage-providers flag.


Segfault on long operations chain of Vix.Vips.Operation.rank/4.

Opening an issue here to reflect https://github.com/elixir-image/image/issues/125.
A repeatable test case (at least on my M1 Max MacBook Pro 64Gb) is:
# The test image
{:ok, {_code, _headers, data}} = :httpc.request('https://raw.githubusercontent.com/elixir-image/image/main/test/support/images/tulips.png')
tulips = :erlang.list_to_binary(data)
{:ok, image} = Vix.Vips.Image.new_from_buffer(tulips)
mask = Vix.Vips.Operation.invert!(image[-1])
dilated = Enum.reduce(1..500, mask, fn _i, acc -> Vix.Vips.Operation.rank!(acc, 3, 3, 8) end)
Vix.Vips.Image.write_to_binary(dilated)

You should be able to just copy/paste the script above and I expect you will see a segfault a the write_to_binary/1 call.
CC: @ramyma

Hey @kipcole9. Thanks for creating the small case to test.
I'll check and get back to you.

Looks like upstream issue https://github.com/libvips/libvips/issues/3832. Waiting for the confirmation.


EVM-360 Invalid state root error on v0.7.1-alpha2

Description
In block builder, header timestamp was not set and transition was created with timestamp 0 before any tx writing.
Because of that opcode TIMESTAMP = 0x42 (opTimstamp) returned different results when tx is executed while building and verifying proposal
Changes include

[x] Bugfix (non-breaking change that solves an issue)
[ ] Hotfix (change that solves an urgent issue, and requires immediate attention)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Breaking changes
Please complete this section if any breaking changes have been made, otherwise delete it
Checklist

[x] I have assigned this PR to myself
[x] I have added at least 1 reviewer
[x] I have added the relevant labels
[ ] I have updated the official documentation
[ ] I have added sufficient documentation in code

Testing

[x] I have tested this code with the official test suite
[x] I have tested this code manually

Could you please be more descriptive in the PR description about the solution? it is only describing the problem scope.


Postgres generateChangeLog includeSchema

Environment
Liquibase Version: 4.8.0
Liquibase Integration & Version: <Pick one: CLI, maven, gradle, spring boot, servlet, etc.> CLI
Liquibase Extension(s) & Version: n/a
Database Vendor & Version: Postgresql 12.4
Operating System Type & Version: Amazon Aurora
Description
I am trying to generate DDL from the postgres database using Liquibase.  I would like the schema to be suppressed in the output.  However, when I run:
liquibase --changeLogFile=./ddl-build/changelog.etl1.new.sql --includeSchema=false --schemas=wetl generateChangeLog
I get oracle as schema, such as:
CREATE TABLE "oracle"."activity_defn"
I don't know where this "oracle" is coming from, I am pointing to a schema called "wetl".
Steps To Reproduce
This is the liquibase command I have run:
liquibase --changeLogFile=./ddl-build/changelog.etl1.new.sql --includeSchema=false --schemas=wetl generateChangeLog
Actual Behavior
Object owner called "oracle" gets appended to the objects when I generate the changelog and set includeSchema=false
Example: CREATE TABLE "oracle"."activity_defn"
Expected/Desired Behavior
There should be no object owner in the changelog output when includeSchema is set to false.
Example: CREATE TABLE "activity_defn"
Screenshots (if appropriate)
n/a
Additional Context
n/a

@jennymitch I am curious, what happens when you set includeSchema = true? Or when you drop the Schema specific commands? I am curious because the default should be includeSchema = false, so my first guess it that isn't actually what is causing the odd owner to be added. Do you get the same result when you just run liquibase --changeLogFile=./ddl-build/changelog.etl1.new.sql generateChangeLog?

Yes, I get the same result when I do not include the “includeSchema” option, as it does default to false.
When I set it to true, I get the true schema name.  For example:
Create table “wetl”.”apps”……
I am not sure what you mean by “drop the Schema specific commands”?  Please elaborate.
Thanks,
Jennifer
From: kataggart @.>
Sent: Thursday, April 21, 2022 12:41 PM
To: liquibase/liquibase @.>
Cc: Jennifer Mitchell @.>; Mention @.>
Subject: [Marketing] Re: [liquibase/liquibase] Postgres generateChangeLog includeSchema (Issue #2776)
@jennymitchhttps://urldefense.com/v3/__https:/github.com/jennymitch__;!!GszH2LQudD4GjA!nmQQ4LnHEtUsUvLadIHOmG_Jx6tMPbFuoBPmlQN0UvaqPuIS4vqSPmptaHHGxquezchTV9QiRFE43UR-W6ctkSpiE29mRw$ I am curious, what happens when you set includeSchema = true? Or when you drop the Schema specific commands? I am curious because the default should be includeSchema = false, so my first guess it that isn't actually what is causing the odd owner to be added. Do you get the same result when you just run liquibase --changeLogFile=./ddl-build/changelog.etl1.new.sql generateChangeLog?
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/liquibase/liquibase/issues/2776*issuecomment-1105624315__;Iw!!GszH2LQudD4GjA!nmQQ4LnHEtUsUvLadIHOmG_Jx6tMPbFuoBPmlQN0UvaqPuIS4vqSPmptaHHGxquezchTV9QiRFE43UR-W6ctkSrEn9nB3Q$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AY2GCVX5I25WBIRW2HZDF2LVGGOKVANCNFSM5T43P3RQ__;!!GszH2LQudD4GjA!nmQQ4LnHEtUsUvLadIHOmG_Jx6tMPbFuoBPmlQN0UvaqPuIS4vqSPmptaHHGxquezchTV9QiRFE43UR-W6ctkSph_toW4g$.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>All emails in this message string and any attachments are the confidential information of CSG Systems International, Inc. (CSG), or its affiliates and subsidiaries, and may contain privileged and/or confidential material. If you are not an intended recipient, please delete it immediately and notify the sender; unintended recipients are not authorized to read or otherwise use the information contained herein.

@jennymitch that is exactly what I meant :) Was interested in what results you got when you just ran liquibase --changeLogFile=./ddl-build/changelog.etl1.new.sql generateChangeLog
When you do that, you are getting
CREATE TABLE "oracle"."activity_defn"
But when you run `iquibase --changeLogFile=./ddl-build/changelog.etl1.new.sql --includeSchema=false --schemas=wetl generateChangeLog' you are getting
Create table “wetl”.”apps"
Am I getting that correct?
Thanks!

Yes, that is correct.
From: kataggart @.>
Sent: Thursday, April 21, 2022 1:31 PM
To: liquibase/liquibase @.>
Cc: Jennifer Mitchell @.>; Mention @.>
Subject: [Marketing] Re: [liquibase/liquibase] Postgres generateChangeLog includeSchema (Issue #2776)
@jennymitchhttps://urldefense.com/v3/__https:/github.com/jennymitch__;!!GszH2LQudD4GjA!lZmQPS-5ZrkRnHYtOOpT7UnDJoDv9iqgMesXv3tKj-RLiuf6DoQOC32_iuoL4qvMpCO2YpOy9aV0vhvB8maYV7X2uRh0ew$ that is exactly what I meant :) Was interested in what results you got when you just ran liquibase --changeLogFile=./ddl-build/changelog.etl1.new.sql generateChangeLog
When you do that, you are getting
CREATE TABLE "oracle"."activity_defn"
But when you run `iquibase --changeLogFile=./ddl-build/changelog.etl1.new.sql --includeSchema=false --schemas=wetl generateChangeLog' you are getting
Create table “wetl”.”apps"
Am I getting that correct?
Thanks!
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/liquibase/liquibase/issues/2776*issuecomment-1105672554__;Iw!!GszH2LQudD4GjA!lZmQPS-5ZrkRnHYtOOpT7UnDJoDv9iqgMesXv3tKj-RLiuf6DoQOC32_iuoL4qvMpCO2YpOy9aV0vhvB8maYV7WGQk8vWA$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AY2GCVS7NYSNR5XAOVBIY7TVGGUINANCNFSM5T43P3RQ__;!!GszH2LQudD4GjA!lZmQPS-5ZrkRnHYtOOpT7UnDJoDv9iqgMesXv3tKj-RLiuf6DoQOC32_iuoL4qvMpCO2YpOy9aV0vhvB8maYV7VIMuIlFw$.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>All emails in this message string and any attachments are the confidential information of CSG Systems International, Inc. (CSG), or its affiliates and subsidiaries, and may contain privileged and/or confidential material. If you are not an intended recipient, please delete it immediately and notify the sender; unintended recipients are not authorized to read or otherwise use the information contained herein.


Fix: #16 Bugfix power shell encoding

Fix: #16
See commits for details.

Hi, where did you get the codePages list? Is it an extensive list?
In my case I have tested and it did not work because my Charset.defaultCharset().name() is "UTF-8" and not the expected "utf-8". I have made an small fix that compares using always lowercase in both senses.

The list is from Microsoft: https://msdn.microsoft.com/de-de/library/windows/desktop/dd317756(v=vs.85).aspx Should cover all common Charsets supported by Powershell.
That is correct, lowercase makes sense here. If the Charset.defaultCharset().name() is still not in the list it should use no value which results in "cmd.exe /c chcp >> null & powershell.exe -NoExit -Command -...".
This does keep the wrong default codepage with possibly corrupted Characters but the rest will still work as it does without my PR.
Another solution might be to force UTF-8 here, but I do not like this attempt. If UTF-8 is required by any user, he should set the Charset.defaultCharset().name() to utf-8.

Ok I accept and I will make some small adjustements for a future 1.8 version
Thank you for your help