[geotrans] add new port

I can't see the details on the failed check, not authorized.  I only tested on Linux x64 on my end.

I can't see the details on the failed check, not authorized. I only tested on Linux x64 on my end.

The CI build is failing because the the CI build only passes for x64-linux. I can see that geotrans is also available for Windows -- would you be able to get this port to work for the Windows triplets?

The CI build is failing because the the CI build only passes for x64-linux. I can see that geotrans is also available for Windows -- would you be able to get this port to work for the Windows triplets?

I'll have a look. I thought that the code in the downloads was identical, only the Linux package is src+shared objects, while the Windows package is src+DLL's.

two port ?
it is necessary to isolate the Assembly on the platform
Windows Developer | 149 MB | win_dev.zip
http://earth-info.nga.mil/GandG/geotrans/geotrans3.7/win_dev.zip
Linux Developer | 144 MB | linux_dev.tgz

and personally I have problems with access to site
without a proxy from another country could not go

@grdowns Can you let give me access to the failure screen, or let me know why it failed?  I tested on Windows x86, x64 and Linux x64.

two port ?
it is necessary to isolate the Assembly on the platform
Windows Developer | 149 MB | win_dev.zip
http://earth-info.nga.mil/GandG/geotrans/geotrans3.7/win_dev.zip
Linux Developer | 144 MB | linux_dev.tgz

The code is the same in both, one has Linux binaries, the other has Windows.

Thank you for adding this library, it is looking good so far.  Could you add a comment near the URL just pointing out that despite having Linux in the file name the source code is the same for all architectures?  Tests are passing on all architectures except for the uwp triplets on windows.

install-x64-uwp-dbg-out.log
Here is the log file for x64-uwp.  Doing a quick scan it looks like the failures can probably all be fixed with _CRT_SECURE_NO_WARNINGS.

Thanks for contributing, geotrans builds for all triplets in our CI system 👍


[Feature Request]: Dedicated Blog Section in Mockly

Is your feature request related to a problem? Please describe.
Currently, Mockly lacks a blog section where contributors can share updates, tutorials, and tips about the application. Having a blog within the app would improve user engagement, keep users informed, and showcase insights or usage guides directly on the platform.
Describe the solution you'd like
I would like to add a dedicated blog section in Mockly, where blog posts are stored in markdown files inside a content folder within the repository. The Next.js app should read these markdown files, render them as HTML, and display them under a "Blog" route, allowing users to access posts directly on the Mockly website.
Describe alternatives you've considered
Using an external blogging platform like Medium or Dev.to to publish articles about Mockly, but hosting a blog directly on Mockly offers greater control and a seamless user experience.
Additional context

Use a static approach to fetch markdown content from the content folder.
Enable support for markdown rendering with syntax highlighting for code snippets.
The blog posts should support metadata like title, date, and author.

Tasks:

[ ] Set up a content folder:

Create a content folder at the root of the project to hold markdown files for each blog post.
Each markdown file should follow a consistent naming convention and metadata structure (e.g., title, date, author).

[ ] Create a blog page:

Set up a route in Next.js (e.g., /blog) that lists all blog posts.
Each post should link to its own dedicated page displaying the full content.

[ ] Markdown rendering setup:

Use a library like remark or next-mdx-remote to parse and render markdown files as HTML.

[ ] Test the blog section:

Ensure that markdown content displays correctly and that metadata renders as expected.
Test mobile and desktop views for optimal readability.

[ ] Update documentation:

Add instructions on how to create and add blog posts in markdown format.
Document the metadata structure required for new posts.

Optional Sections:

Priority: Medium
Are you willing to contribute to this feature? Yes
Does this feature require any third-party libraries or changes in existing ones? Likely remark or next-mdx-remote for markdown parsing.

Update: Mockly Now Supports Blog
Feel free to contribute to writing blogs.


Compilation error cupy-rocm with Radeon Mobile Graphics (AMD)

Description
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/cupy/cuda/compiler.py", line 686, in compile
    nvrtc.compileProgram(self.ptr, options)
  File "cupy_backends/cuda/libs/nvrtc.pyx", line 154, in cupy_backends.cuda.libs.nvrtc.compileProgram
  File "cupy_backends/cuda/libs/nvrtc.pyx", line 166, in cupy_backends.cuda.libs.nvrtc.compileProgram
  File "cupy_backends/cuda/libs/nvrtc.pyx", line 84, in cupy_backends.cuda.libs.nvrtc.check_status
cupy_backends.cuda.libs.nvrtc.NVRTCError: HIPRTC_ERROR_COMPILATION (6)

To Reproduce
python autozoom.py --in ./images/doublestrike.jpg --out ./autozoom.mp4

From https://github.com/sniklaus/3d-ken-burns
Installation
None
Environment
OS                        : Linux-6.2.9-arch1-1-x86_64-with-glibc2.37
Python Version            : 3.10.10
CuPy Version              : 11.3.0
CuPy Platform             : AMD ROCm
NumPy Version             : 1.24.2
SciPy Version             : 1.10.1
Cython Build Version      : 0.29.33
Cython Runtime Version    : 0.29.33
CUDA Root                 : /opt/rocm
hipcc PATH                : /opt/rocm/bin/hipcc
CUDA Build Version        : 50422804
CUDA Driver Version       : 50422804
CUDA Runtime Version      : 50422804
cuBLAS Version            : (available)
cuFFT Version             : 10021
cuRAND Version            : 201009
cuSOLVER Version          : (3, 20, 0)
cuSPARSE Version          : (available)
NVRTC Version             : (9, 0)
Thrust Version            : 101600
CUB Build Version         : 201012
Jitify Build Version      : None
cuDNN Build Version       : None
cuDNN Version             : None
NCCL Build Version        : 21304
NCCL Runtime Version      : 21304
cuTENSOR Version          : None
cuSPARSELt Build Version  : None
Device 0 Name             : AMD Radeon Graphics
Device 0 Arch             : gfx90c:xnack-
Device 0 PCI Bus ID       : 0000:07:00.0

Additional Information
I've installed python-cupy-rocm in Arch linux.
I am overriding the version of the graphics card with HSA_OVERRIDE_GFX_VERSION=9.0.0 because it seems that the integrated GPU on laptops are not officially supported.

@amathews-amd
Do you have any clue about this? :)
Thanks!

See https://github.com/RadeonOpenCompute/ROCm/issues/1714#issuecomment-1128327143
If the gpu is not officially supported, the ROCm stack is not build up, or tested on this GPU. While some non-supported hardware sometimes just tends to work, continued functionality is not guaranteed, and there is no mechanism to request for help.
cc: @AdrianAbeyta


chore: added coverage generation stage in ci

Title
Added Coverage generation stage in CI
Description of what's changing
This step would be necessary to include the coverage badges in the README.md
What else might be impacted?
None
Which issue does this PR relate to?
#25
Checklist
[x] Tests are written and maintain or improve code coverage
[x] I've tested this in my application using yarn link (if applicable)
[x] You consent to and are confident this change can be released with no regression

The artifacts are generated as part of the build process. Can I use the links of these artifacts directly in the readme for #19

@christyjacob4 that looks like a good solution to me. But will defer to @skodamarthi for final approval as she is much more up to speed on this than me.

Hi @reubenae a potential problem with this approach is that there is no way to reference the artifacts from the readme since their URLs are not fixed. I'm looking around for solutions but the suggestion is to use codecov or Coveralls

@skodamarthi Yeap sure. if nothing works we could go with the coveralls approach

Shall I add support for coveralls in this PR ?

References :
https://dev.to/dxnchima/integrating-circleci-with-coveralls-for-your-next-node-project-hi1
https://medium.com/@ollelauribostr/start-measuring-coverage-with-jest-travis-ci-and-coveralls-1867928aca42
https://medium.com/@okunladekayode/how-i-integrated-coveralls-with-my-nodejs-project-95e88b78ae68
I have added support for coveralls
Few action items from the repo owners

Setup COVERALLS_REPO_TOKEN as an env variable in circleci
Log into coveralls and add coveralls to this repo.

This is the end result.

Let me know once doe @skodamarthi

@christyjacob4 I have done the steps. Do I also need to create coverall.yml file and add the environment var to it?

@skodamarthi  yes you need to create a .coveralls.yml file locally as well repo_token: <YOUR_REPO_TOKEN>
Else you will be unable to push your code  because the husky pre-push hook runs npm test && npm run test:coverage
and npm run test:coverage requires coveralls.
What I can do here, is to only run npm test in the pre-commit hook.
Then we wouldn't need .coveralls.yml locally

@christyjacob4 Sounds good! I believe this PR can be merged now without any additional changes. Right?

Yes @skodamarthi  we're good to go 👍


Dot-notation for records

This PR adds support for code like [#foo].tag in a search section.
There is an issue that prevents it from working in an action section (scans should not generate proposals if a dependent variable is covered by some instance of GenerateId provider that hasn't been accepted yet), but I'll work on this in subsequent PR.
Let me know if there is anything you'd like me to change in the code.

This change is

@joshuafcole @cmontella do either of you have any objections to this? I think I was the main opponent, but I'm not strongly opposed - more just a slight unease.

I think it'll make code a little harder to read in some cases, but it seems like a natural thing to want to do. I don't have any specific concerns though, so I think it's fine to allow this.

Oh, if you don't want this, I'll be fine without it :)
My reasoning was It seemed intuitive that if
foo = [#some-record]
foo.attribute

then
[#some-record].attribute

is expected to work too. But I admit that it may be far-fetched to apply this traditional reasoning to eve.
Especially since my initial use-case was based on incorrect assumption that without this PR there is no way to simplify following code:
[#foo bar]
(not bar)

But I've learned about
[#foo not(bar)]

since then.

The big use case here is for inline queries in maths, e.g.
[#person age < 18].height / [#teacher not(#professor)].height
In principle it sounds like a good thing to support, but every time I write
an example of it I find it relatively hard to read. This is actually
something I was advocating for internally earlier, but after trying it out
with the logical syntax extension here, I'm not so sure. I can't think of a
particularly better syntax either. There's an argument to be made that we
should support it anyway for orthogonal completeness, but it doesn't seem
super compelling to me. I'd say I'm about a 2/10 against this. If you feel
more strongly that we should have it I'm okay with that.
On Tue, Jan 10, 2017 at 1:59 PM Ravil Bayramgalin<EMAIL_ADDRESS>wrote:

Oh, if you don't want this, I'll be fine without it :)
My reasoning was It seemed intuitive that if
foo = [#some-record]
foo.attribute
then
[#some-record].attribute
is expected to work too. But I admit that it may be far-fetched to apply
this traditional reasoning to eve.
Especially since my initial use-case was based on incorrect assumption
that without this PR there is no way to simplify following code:
[#foo bar]
(not bar)
But I've learned about
[#foo not(bar)]
since then.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/witheve/Eve/pull/722#issuecomment-271711197, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AATKDrC4Khwbn4Pvx7aaaHZHVw9uV2vGks5rQ_8kgaJpZM4LccJY
.

Please correct me if I'm wrong in my following assumptions. It seems like the core team does not have strong arguments against this PR, but does have a minor gut feeling against it. And the team is ok to merge it if one person (who wrote the PR and is outside of the core team) strongly desires it. Is this correct?
In my opinion, seems like there are better ways to make the decision.

A gut feeling of the whole core team should be enough to stop the PR.
Community feedback could be gathered if the team is undecided/split. It'll hopefully provide an additional information that could be used by the team to make the final decision.
If there is no proponent of PR on the team, then the burden of conviction lies on an outside person (that could include initiating a gathering of community feedback by that person). Until the team is convinced that a PR is' a good idea, it shouldn't be merged. A simple reason to close the PR from the core team like "not convinced it will help" is sufficient.

What do you think?

@brainopia I think it's a minor enough change that we should just allow it and see how it works. Like you said, it makes sens, and as josh said, it we might want it just as an option for completeness. I say let's merge it and see how it goes.

@cmontella It should go the other way around. Anything we do that affects the actual language should be justified. That doesn't mean we won't eventually find a good reason for this, but we don't currently have one and its use does make things harder to read. As @brainopia the gut feeling is this probably shouldn't happen. I opened it up because @joshuafcole has previously expressed a desire for it, but he's lukewarm on it at best.
Let's close this for now. If someone comes up with a compelling justification for it, we'll revisit.

@ibdknox Sounds good to me, thanks for making a decision :+1:

@ibdknox by the way, I have another question.
Would you please check two first commits in the PR and tell me if you're interested in merging them.
There are no changes in semantics/syntax, but in my opinion, it is a slight improvement of parser by removing a couple of redundant abstractions.

Scratch my question. It's irrelevant now :)


Pool.DB.Sqlite: Close the database before attempting to wipe it

Relates to #1224.
Overview

If there was an error running db migrations, ensure that the database is closed before taking further action.

Comments

I have tested on Windows Server 2016 using cardano-wallet-core-2019.12.23-test-unit.exe --match /Cardano.Pool.DB.Sqlite/

The build from this branch passes the tests.
The build from master branch also passes the tests

bors r+

bors r+

bors retry


Role permissions inconsistency

About Role permissions,

shared model uses protobuf expression snake_case "can_add_asset_qty"
Iroha uses UpperCamel "CanAddAssetQuantity"
Stateful validator uses UpperCamel expression.

So in my understandings, maybe CreateRole transaction from shared model cannot work?
What are your thoughts on that? If something wrong with me, please correct.
UPDATE:

Link to internal(old fashioned) model:
https://github.com/hyperledger/iroha/blob/develop/irohad/model/permissions.hpp

Link to shared model: https://github.com/hyperledger/iroha/blob/develop/shared_model/builders/protobuf/transaction.hpp#L213

that was fixed partially in https://github.com/hyperledger/iroha/commit/999a1c710dda7936d3cb78b158c536a6ab714232
@l4l can you check if other issues persist (I mean those that are mentioned above by @motxx)

The first issue is still here, though it will work in new one anyway
And I'm not really got the second issue. Which permission are you speaking of?
https://github.com/hyperledger/iroha/blob/0f1d5b522f1e7ed2485f1cd806c96a9a74806912/schema/commands.proto#L38-L41

Fixed in #921 and some of the following prs


port lineage for datasets from legacy app with dagre-d3 implementation

Coverage remained the same at 0.0% when pulling 219da90d6744f5e029a43f2defe346d56de99db5 on theseyi:linkedin into 7eee9ecf398c3c2f624199e53138dcfd445aa04a on linkedin:linkedin.

Great Job :)


How to correctly count duplicates?

For the summaries.analysis.Analyzer, I'm working on a tool that should be detecting duplicates in the training data.
This rather trivial looking problem does pose some challenges in dealing with resulting duplicates, however:

Duplicate data has to be held as a copy in memory, since we are not guaranteed that each sample has a unique identifier (especially not if it is an actual accidental duplicate); adding our own uuids, however, might mean additional passes through the data. Hash functions can have collisions, and are generally not much different from hashing it with a dictionary, anyways.
When encountering a duplicate, it might happen that more complex scenarios appear that prohibit easy clean-up:

Sample A appears in the same form in different splits (training and validation). Does this count as a single duplicate, or two?
As a follow-up, it is also unclear which one of the samples should be kept if we de-duplicate datasets. Should it be the one in the training set (meaning discarding the validation sample), or vice versa? Or should both be dropped?
Alternatively, as an example, assume that sample A has the same reference text as sample B. In addition, A also has the same summary text as C. Again the question of counting duplicates and choosing deletions remains, but different this time, since B and C might be fully distinct, making this an even less obvious choice (or rather, less arbitrary).

A preliminary way might be to simply count samples multiple times for multiple problems, especially when considering that this might not be a very frequent problem.

For Cleaner (#41), this can be chosen with different functionalities. The default (and currently only function that is supported) is adding every encountered reference and summary, and not adding any future sample that contains a previously seen text.


Adding the maxDegreeOfParallelism property to the Spring Code

… spring code base.
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run java - cosmos - tests


Settings - Splash Settings

Production CT
Chrome 51.0 and Firefox 47

@ZakMooney Can you sort this, that's the ng-show thing remember.

Also, the Save button doesn't work.


cached find() result is not updated after re-render

In short: if I put find() result into interm variable it is not updated after wrapper is re-rendered. Meanwhile fresh call to find returns actual element.
Having really simple component:
const List = ({ options = [] }) =>
    <>
       {options.map((i, index) => {i})}
    </>

it('updates first item on updating options', () => {
	const options = [1];
	const wrapper = shallow(<List options={options} />);
	const first = wrapper.find('span').slice(0, 1);
	expect(first.props().children).toEqual(1);
	wrapper.setProps({ options: [2] });
	expect(wrapper.find('span').slice(0, 1).props().children).toEqual(2);
	expect(first.props().children).toEqual(2);
})

Current behavior
Test fails at last statement. Pre-last(with new find() call) passes.
Expected behavior
Both cached wrapper and call to find() returns the same Wrapper instance
Your environment
Windows 10, Node 8.12.0
API

[x] shallow
[ ] mount
[ ] render

Version

library
version

enzyme
3.9.0

react
16.8.6

react-dom
16.8.6

react-test-renderer
16.8.6

adapter (below)
1.13.1

Adapter

[x] enzyme-adapter-react-16
[ ] enzyme-adapter-react-16.3
[ ] enzyme-adapter-react-16.2
[ ] enzyme-adapter-react-16.1
[ ] enzyme-adapter-react-15
[ ] enzyme-adapter-react-15.4
[ ] enzyme-adapter-react-14
[ ] enzyme-adapter-react-13
[ ] enzyme-adapter-react-helper
[ ] others ( )

as far as I understand, there is nothing like BOM's "live collection". So after re-render occurs each previous find() may be outdated(say some elements does not exist in tree anymore). And there is no easy solution to update all those collection from within Enzyme's wrapper. Is it correct reasoning?
So find() result better never being stored into intermediate variable to avoid such a cases. Right?

This is intended behavior in enzyme v3 - see https://github.com/airbnb/enzyme/blob/master/docs/guides/migration-from-2-to-3.md#element-referential-identity-is-no-longer-preserved.
So yes, exactly - everything must be re-found from the root if anything has changed.

I suppose link should be pointing to https://github.com/airbnb/enzyme/blob/master/docs/guides/migration-from-2-to-3.md#calling-props-after-a-state-change
right?


[Bug]: 1 node(s) had taint {eks.amazonaws.com/compute-type: fargate}, that the pod didn't tolerate.

Welcome to Amazon EKS Blueprints!

[X] Yes, I've searched similar issues on GitHub and didn't find any.

Amazon EKS Blueprints Release version
https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/feat/custom-coredns/examples/fargate-serverless/main.tf
What is your environment, configuration and the example used?
data "aws_eks_addon_version" "latest" {
  for_each = local.cluster_addons

  addon_name         = try(each.key, null)
  kubernetes_version = data.aws_eks_cluster.this.version
  most_recent        = true
}
output "data_aws_eks_addon_versions" { value = data.aws_eks_addon_version.latest }

locals {
  cluster_addons = merge(
    {
      coredns    = {}
      kube-proxy = {}
      vpc-cni = {
        enable_pod_eni = true
      }
      # aws-ebs-csi-driver = {
      #   resolve_conflicts = "OVERWRITE"
      # }
    },
  )
}

# resource "aws_eks_addon" "aws_eks_addons" {
#   for_each = var.fargate_create || var.eks_managed_node_groups_create ? local.cluster_addons : {}

#   cluster_name = data.aws_eks_cluster.this.id
#   addon_name   = try(each.value.name, each.key)

#   addon_version            = lookup(each.value, "addon_version", data.aws_eks_addon_version.latest[each.key].version)
#   resolve_conflicts        = lookup(each.value, "resolve_conflicts", null)
#   service_account_role_arn = lookup(each.value, "service_account_role_arn", null)
#   preserve                 = lookup(each.value, "preserve ", null)

#   lifecycle {
#     ignore_changes = [
#       modified_at
#     ]
#   }

#   depends_on = [
#     module.fargate_profiles,
#     module.eks_managed_node_groups,
#   ]
# }
# output "aws_eks_addons" { value = aws_eks_addon.aws_eks_addons }

module "eks_blueprints_kubernetes_addons" {
  count = var.fargate_create || var.eks_managed_node_groups_create ? 1 : 0

  # source = "git::ssh://git@github.com/aws-ia/terraform-aws-eks-blueprints.git//modules/kubernetes-addons?ref=v4.0.6"
  source = "git::ssh://git@github.com/aws-ia/terraform-aws-eks-blueprints.git//modules/kubernetes-addons?ref=feat/custom-coredns"

  eks_cluster_id = data.aws_eks_cluster.this.id

  enable_amazon_eks_vpc_cni = true
  amazon_eks_vpc_cni_config = {
    addon_version     = data.aws_eks_addon_version.latest["vpc-cni"].version
    resolve_conflicts = "OVERWRITE"
  }

  enable_amazon_eks_kube_proxy = true
  amazon_eks_kube_proxy_config = {
    addon_version     = data.aws_eks_addon_version.latest["kube-proxy"].version
    resolve_conflicts = "OVERWRITE"
  }

  enable_amazon_eks_coredns = true
  coredns_use_managed_addon = var.fargate_create ? false : true
  coredns_helm_config = {
    # Sets the correct annotations to ensure the Fargate provisioner is used and not the EC2 provisioner
    compute_type       = var.fargate_create ? "fargate" : "ec2"
    kubernetes_version = data.aws_eks_cluster.this.version
  }

  depends_on = [
    # CoreDNS provided by EKS needs to be updated before applying self-managed CoreDNS Helm addon
    null_resource.modify_kube_dns
  ]
}
output "eks_blueprints_kubernetes_addons" { value = module.eks_blueprints_kubernetes_addons }

#---------------------------------------------------------------
# Modifying CoreDNS for Fargate
#---------------------------------------------------------------

locals {
  kubeconfig = yamlencode({
    apiVersion      = "v1"
    kind            = "Config"
    current-context = "terraform"
    clusters = [{
      name = data.aws_eks_cluster.this.id
      cluster = {
        certificate-authority-data = data.aws_eks_cluster.this.certificate_authority.0.data
        server                     = data.aws_eks_cluster.this.endpoint
      }
    }]
    contexts = [{
      name = "terraform"
      context = {
        cluster = data.aws_eks_cluster.this.id
        user    = "terraform"
      }
    }]
    users = [{
      name = "terraform"
      user = {
        token = data.aws_eks_cluster_auth.this.token
      }
    }]
  })
}

# Separate resource so that this is only ever executed once
resource "null_resource" "remove_default_coredns_deployment" {
  count = var.fargate_create ? 1 : 0

  triggers = {}

  provisioner "local-exec" {
    interpreter = ["/bin/bash", "-c"]
    environment = {
      KUBECONFIG = base64encode(local.kubeconfig)
    }

    # We are removing the deployment provided by the EKS service and replacing it through the self-managed CoreDNS Helm addon
    # However, we are maintaing the existing kube-dns service and annotating it for Helm to assume control
    command = <<-EOT
      kubectl --namespace kube-system delete deployment coredns --kubeconfig <(echo $KUBECONFIG | base64 --decode) | true
    EOT
  }
}
output "null_resource_remove_default_coredns_deployment" { value = null_resource.remove_default_coredns_deployment }

resource "null_resource" "modify_kube_dns" {
  count = var.fargate_create ? 1 : 0

  triggers = {}

  provisioner "local-exec" {
    interpreter = ["/bin/bash", "-c"]
    environment = {
      KUBECONFIG = base64encode(local.kubeconfig)
    }

    # We are maintaing the existing kube-dns service and annotating it for Helm to assume control
    command = <<-EOT
      echo "Setting implicit dependency on ${module.fargate_profiles["kube-system"].fargate_profile_arn}"
      kubectl --namespace kube-system annotate --overwrite service kube-dns meta.helm.sh/release-name=coredns --kubeconfig <(echo $KUBECONFIG | base64 --decode)
      kubectl --namespace kube-system annotate --overwrite service kube-dns meta.helm.sh/release-namespace=kube-system --kubeconfig <(echo $KUBECONFIG | base64 --decode)
      kubectl --namespace kube-system label --overwrite service kube-dns app.kubernetes.io/managed-by=Helm --kubeconfig <(echo $KUBECONFIG | base64 --decode)
    EOT
  }

  depends_on = [
    null_resource.remove_default_coredns_deployment
  ]
}
output "null_resource_modify_kube_dns" { value = null_resource.modify_kube_dns }

pod describe
kind: Pod
apiVersion: v1
metadata:
  name: coredns-7cb88d5df4-mjfq6
  generateName: coredns-7cb88d5df4-
  namespace: kube-system
  uid: 5dc91b63-ce7d-4d61-99d9-a39b509b595e
  resourceVersion: "23047"
  creationTimestamp: "2022-05-19T11:42:21Z"
  labels:
    app.kubernetes.io/instance: coredns
    app.kubernetes.io/name: coredns
    k8s-app: coredns
    pod-template-hash: 7cb88d5df4
  annotations:
    checksum/config: d7cc36048e256a36a02850eb7b5d0e4cbf1c68b087a22be2c7a4eee0f90999fa
    kubectl.kubernetes.io/restartedAt: "2022-05-19T12:42:21+01:00"
    kubernetes.io/psp: eks.privileged
    scheduler.alpha.kubernetes.io/critical-pod: ""
    scheduler.alpha.kubernetes.io/tolerations: '[{"key":"CriticalAddonsOnly", "operator":"Exists"}]'
  ownerReferences:
  - apiVersion: apps/v1
    kind: ReplicaSet
    name: coredns-7cb88d5df4
    uid: 65e1edec-9ba6-4349-906a-21a9d6eb6d5e
    controller: true
    blockOwnerDeletion: true
spec:
  volumes:
  - name: config-volume
    configMap:
      name: coredns-coredns
      items:
      - key: Corefile
        path: Corefile
      defaultMode: 420
  - name: kube-api-access-vtvxd
    projected:
      sources:
      - serviceAccountToken:
          expirationSeconds: 3607
          path: token
      - configMap:
          name: kube-root-ca.crt
          items:
          - key: ca.crt
            path: ca.crt
      - downwardAPI:
          items:
          - path: namespace
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
      defaultMode: 420
  containers:
  - name: coredns
    image:<PHONE_NUMBER>52.dkr.ecr.us-east-1.amazonaws.com/eks/coredns:v1.8.7-eksbuild.1
    args:
    - -conf
    - /etc/coredns/Corefile
    ports:
    - name: udp-53
      containerPort: 53
      protocol: UDP
    - name: tcp-53
      containerPort: 53
      protocol: TCP
    resources:
      limits:
        cpu: 100m
        memory: 128Mi
      requests:
        cpu: 100m
        memory: 128Mi
    volumeMounts:
    - name: config-volume
      mountPath: /etc/coredns
    - name: kube-api-access-vtvxd
      readOnly: true
      mountPath: /var/run/secrets/kubernetes.io/serviceaccount
    livenessProbe:
      httpGet:
        path: /health
        port: 8080
        scheme: HTTP
      initialDelaySeconds: 60
      timeoutSeconds: 5
      periodSeconds: 10
      successThreshold: 1
      failureThreshold: 5
    readinessProbe:
      httpGet:
        path: /ready
        port: 8181
        scheme: HTTP
      initialDelaySeconds: 30
      timeoutSeconds: 5
      periodSeconds: 10
      successThreshold: 1
      failureThreshold: 5
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    imagePullPolicy: IfNotPresent
  restartPolicy: Always
  terminationGracePeriodSeconds: 30
  dnsPolicy: Default
  serviceAccountName: coredns-coredns
  serviceAccount: coredns-coredns
  securityContext: {}
  schedulerName: default-scheduler
  tolerations:
  - key: node.kubernetes.io/not-ready
    operator: Exists
    effect: NoExecute
    tolerationSeconds: 300
  - key: node.kubernetes.io/unreachable
    operator: Exists
    effect: NoExecute
    tolerationSeconds: 300
  priority: 0
  enableServiceLinks: true
  preemptionPolicy: PreemptLowerPriority
status:
  phase: Pending
  conditions:
  - type: PodScheduled
    status: "False"
    lastProbeTime: null
    lastTransitionTime: "2022-05-19T11:42:21Z"
    reason: Unschedulable
    message: no nodes available to schedule pods
  qosClass: Guaranteed

coredns deployment
kind: Deployment
apiVersion: apps/v1
metadata:
  name: coredns
  namespace: kube-system
  uid: ab4dc1a3-1176-4877-ad21-ad6353431b29
  resourceVersion: "21130"
  generation: 2
  creationTimestamp: "2022-05-19T10:02:46Z"
  labels:
    app.kubernetes.io/instance: coredns
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: coredns
    app.kubernetes.io/version: 1.9.2
    helm.sh/chart: coredns-1.19.3
    k8s-app: coredns
    kubernetes.io/cluster-service: "true"
    kubernetes.io/name: CoreDNS
  annotations:
    deployment.kubernetes.io/revision: "2"
    eks.amazonaws.com/compute-type: fargate
    meta.helm.sh/release-name: coredns
    meta.helm.sh/release-namespace: kube-system
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/instance: coredns
      app.kubernetes.io/name: coredns
      k8s-app: coredns
  template:
    metadata:
      creationTimestamp: null
      labels:
        app.kubernetes.io/instance: coredns
        app.kubernetes.io/name: coredns
        k8s-app: coredns
      annotations:
        checksum/config: d7cc36048e256a36a02850eb7b5d0e4cbf1c68b087a22be2c7a4eee0f90999fa
        eks.amazonaws.com/compute-type: fargate
        kubectl.kubernetes.io/restartedAt: "2022-05-19T12:32:11+01:00"
        scheduler.alpha.kubernetes.io/critical-pod: ""
        scheduler.alpha.kubernetes.io/tolerations: '[{"key":"CriticalAddonsOnly", "operator":"Exists"}]'
    spec:
      volumes:
      - name: config-volume
        configMap:
          name: coredns-coredns
          items:
          - key: Corefile
            path: Corefile
          defaultMode: 420
      containers:
      - name: coredns
        image:<PHONE_NUMBER>52.dkr.ecr.us-east-1.amazonaws.com/eks/coredns:v1.8.7-eksbuild.1
        args:
        - -conf
        - /etc/coredns/Corefile
        ports:
        - name: udp-53
          containerPort: 53
          protocol: UDP
        - name: tcp-53
          containerPort: 53
          protocol: TCP
        resources:
          limits:
            cpu: 100m
            memory: 128Mi
          requests:
            cpu: 100m
            memory: 128Mi
        volumeMounts:
        - name: config-volume
          mountPath: /etc/coredns
        livenessProbe:
          httpGet:
            path: /health
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 60
          timeoutSeconds: 5
          periodSeconds: 10
          successThreshold: 1
          failureThreshold: 5
        readinessProbe:
          httpGet:
            path: /ready
            port: 8181
            scheme: HTTP
          initialDelaySeconds: 30
          timeoutSeconds: 5
          periodSeconds: 10
          successThreshold: 1
          failureThreshold: 5
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        imagePullPolicy: IfNotPresent
      restartPolicy: Always
      terminationGracePeriodSeconds: 30
      dnsPolicy: Default
      serviceAccountName: coredns-coredns
      serviceAccount: coredns-coredns
      securityContext: {}
      schedulerName: default-scheduler
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: 1
      maxSurge: 25%
  revisionHistoryLimit: 10
  progressDeadlineSeconds: 600
status:
  observedGeneration: 2
  replicas: 1
  updatedReplicas: 1
  unavailableReplicas: 1
  conditions:
  - type: Available
    status: "True"
    lastUpdateTime: "2022-05-19T10:02:46Z"
    lastTransitionTime: "2022-05-19T10:02:46Z"
    reason: MinimumReplicasAvailable
    message: Deployment has minimum availability.
  - type: Progressing
    status: "True"
    lastUpdateTime: "2022-05-19T11:32:11Z"
    lastTransitionTime: "2022-05-19T11:32:11Z"
    reason: ReplicaSetUpdated
    message: ReplicaSet "coredns-5b49b57cd4" is progressing.

What did you do and What did you see instead?
I'm seeing messages like
14m         Warning   FailedScheduling    pod/coredns-84d95c48b5-c5m4q    no nodes available to schedule pods
29m         Warning   FailedScheduling    pod/coredns-84d95c48b5-c5m4q    0/1 nodes are available: 1 node(s) had taint {eks.amazonaws.com/compute-type: fargate}, that the pod didn't tolerate.

Additional Information
using @bryantbiggs branch `feat/custom-coredns`

Thank you for the issue @FernandoMiguel. We will look into this and get back to you.

Did this happen on a new cluster deployment? If you delete the pending pod, does the new pod pulled succeed?

@bryantbiggs this was a few weeks ago when I was testing your branch... i dont recall if this was on a brand new cluster or mid test deployment , sorry.
i had quite a bit of trouble to get coredns to work so i tried a few things, and dont recall exactly how this happened.
eventually gave up and went back to our old method.
now that 4.0.8 is merged, i'll see if i can test this again

Hey @FernandoMiguel - this appears to be working in the example so I am going to close for now. If the CoreDNS pod fails to launch when first creating the cluster using the example, please try deleting the pod - this usually resolves the stuck pod pending status. If you have any further questions or details please feel free to respond here and we can re-open or file a new issue. Thanks!


Auto-cast Class.new(Parent) to T.class_of(Parent)

Motivation
Change the ClassNew rewriter to auto-cast the result of Class.new(Parent) into a T.class_of(Parent).
Right now, the associated type to Class.new(Parent) is always Class:
x = Class.new(Parent)
T.reveal_type(x) # => Class

This is problematic when trying to call things defined in Parent:
class Parent
  def foo; end
end

Class.new(Parent).new.foo # error: Method foo does not exist on Object

To be able to call foo, one has to manually cast the result:
T.cast(Class.new(Parent), T.class_of(Parent)).new.foo # ok

We can be a bit smarter and always rewrite Class.new(<ConstantLiteral>) to use a cast so this works out of the box:
x = Class.new(Parent)
T.reveal_type(x) # => T.class_of(Parent)
x.new.foo # ok

Since it's rewritten as this:
x = T.cast(Class.new(Parent), T.class_of(Parent))
T.reveal_type(x) # => T.class_of(Parent)
x.new.foo # ok

Test plan
See included automated tests.
cc. @egiurleo

I have generally tried avoiding rewriter passes that generate cast instructions, as there are restrictions on where T.cast is allowed to appear, and it is hard to detect whether we are currently in a position where T.cast is allowed.
# typed: true

class Parent; end

class A
  def initialize
    @x = Class.new(Parent) {}
  end
end

# typed: true

class Parent; end

class A
  def initialize
    if T.unsafe(nil)
      @x = Class.new(Parent) {}
    else
      @x = nil
    end
  end
end

# typed: strict

class Parent; end

class Class
  T::Sig::WithoutRuntime.sig do
    type_parameters(:Klass)
      .params(klass: T.all(Class, T.type_parameter(:Klass)))
      .returns(T.all(Class, T.type_parameter(:Klass)))
  end
  def self.new(klass)
    raise
  end
end

class A
  extend T::Sig

  sig {void}
  def initialize
    x = Class.new(Parent) {}
  end
end

Also: I notice that some of your location information is not great. For example, if you add a ^ hover assertion in any of those tests, you'll notice that instead of showing
sig {params(superclass: Class).returns(Class)}
def initialize (overload.1)(superclass=…); end

it shows something like
```
sig do
  params(
    klass: T.untyped
  )
  .returns(Runtime object representing type: T.class_of(Parent)
end
def self.class_of(klass); end
```

---

Type syntax to declare the type of a class's singleton class.

which shows that it found the synthesized call to T.class_of on hover instead of the call to new. If you set the synthetic loc to something with zero length (see the copyWithZeroLength helper) it will instruct LSP to ignore the thing on hover.
And as one last point: maybe we should simply fix this not by using T.cast + desugar, but by adding an RBI definition for Class.new similar to the sig shown above?

Closing as this as been fixed more elegantly in #6589.


Fix/uniformize page typing

Hey @yakovmeister ,
Thanks for the lib!
Leaving you this PR as it fixes some issue I came across while using it

thanks for stopping by, I'll review this changes.


Add scaling for shapes and test it

This PR adds a scale feature to the shapes currently supported by Joy library.
For the rectangle, the lower left coordinates is fixed but we could change this to make the center fixed.
Addresses this issue

@nikochiko @Sudha247 please review this. I have doubts about the float and integer conversion and scaling for a line. Thank you

Hi @nikochiko , please review this. This PR also solves the recently opened issue 47

@nikochiko Please review this

@kushalpokharel, can you make a separate PR with the diff that fixes #47? More PRs depend on it and needn't be tied to the scaling patch. Thanks!

Thanks for the changes! @kushalpokharel


Added proposal check

obsolete functionality, due to update in package the error object structure has been updated as well.


Enable vitest workspaces

Currently it works already when running inside of the solid-urql folder in isolation but not from the root


Added a chart for Percona Server

I needed a Percona Server chart, so I created one, based off of the MySQL chart since the docker images work essentially the same.

I signed it!

Howdy! Does anyone need anything from me to get this moving through the process?


/subjects/queued endpoint doesn't have links for subjects

I'm not sure if this is a feature or a bug, but I'm seeing a difference between the subjects returned by a query like /api/subjects?page_size=30&workflow_id=2368 and /api/subjects/queued?page_size=30&workflow_id=2368. The response to the second query doesn't have subject.links for any of the returned subjects.
Not a big deal at the moment, but I noticed it while running some Diagnosis London code that looks up linked subject sets to display metadata (eg. volume title) next to each subject, similar to the group metadata in Operation War Diary or Science Gossip.

Right - we're using a different serializer to streamline the response on this end point for subject selection. We could take some additional param context that would include the links in the serialized repsonse. What links do you need, just the subject_set ones?


Improve exceptions for incorrect usage of "CliCommand"

Fixes #11
I made a simple draft creating the exceptions in the DotMake.CommandLine.Shared project. What do you think of them?
Please review the naming and messages I made.

Should the EnsureValidityForCommand() method be public so users can pre-validate a class in code or should it be kept as a private class used exclusively for internal validation?

I don't think we need custom exception classes for this as in your PR but error messages is now more clear:
public static CliCommandBuilder Get(Type definitionType)
{
    if (!RegisteredDefinitionTypes.TryGetValue(definitionType, out var commandBuilder))
    {
        if (definitionType.GetCustomAttribute<CliCommandAttribute>() == null)
            throw new Exception($"The class '{definitionType.Name}' should have [CliCommand] attribute.");

        var parentWithoutAttribute = definitionType.RecurseWhileNotNull(t => t.DeclaringType)
            .FirstOrDefault(t => t.GetCustomAttribute<CliCommandAttribute>() == null);
        if (parentWithoutAttribute != null) //nested
            throw new Exception($"The parent class '{parentWithoutAttribute.Name}' of nested class '{definitionType.Name}' should have [CliCommand] attribute.");

        throw new Exception($"A registered command builder is not found for '{definitionType.Name}'. " +
                            $"Please ensure the source generator is running and generating a command builder for your definition class.");
    }

    return commandBuilder;
}


Select HTML tag using CSS selectors

What
It would be great if I can select specific HTML code block using CSS selectors.
For example, h1 will select all the HTML tag.
Selecting
Hello World
,
VSCode
, e.t.c.
Where
When pressing ctrl + f, a button with CSS icon will appear next to the other buttons. And if pressing the button, there should be an input box for putting CSS selector.
Why
Selecting HTML tags are too hard as the end tag might be on any line and different on how the code is formatted.
Thank you.

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!


💡 Feature Request - Accelerator doesn't update all values across all parameter files (eg mgrp prefix/ law resource-id)

Describe the solution you'd like
In the accelerator some parameters are set in the parameter files, but not all. eg log analytics workspace name. also some naming conventions are not set/ updatable.
not bad as you can edit parameter files in your code, however it shows that some values (eg mgrp prefix / law resource id) are used and defined in multiple parameter files. this works contraproductive
Describe alternatives you've considered
one parameter file, or referencing others to build parameters based on previous deployment steps to simplify configuration
Additional context
As discussed with Jack, Contact me on my MSFT teams, Im willing to help in this development/testing

Hi @jtracey93 and @oZakari
I noticed that eg. the LAW subscriptionID and name is not updated in the resource ID parameter ("parLogAnalyticsWorkspaceResourceId")  in several files such as Policy Assignments and DiagSettings parameter files.

Hi @bram-boer,
Could you share which version of the ALZ PowerShell Module you are using?  You can use Get-InstalledModule ALZ -AllVersions.
For the subscription ID not getting replaced, are you seeing the management group subscription ID not getting replaced correctly within subPlacementall.parameters.all.json as well?

The resource groups should incorporate the prefix you provide when prompted. However, the resources within those resource groups currently have alz as the prefix by default. Is that what you're looking to have changed?

@bram-boer can you come back to @oZakari here please?


Github.context.payload fails JSON.parse if payload has newlines

https://github.com/slackapi/slack-github-action/blob/d5d276d7ae0f38f29322b80da9baf985cc80f8b1/index.js#L35
When the commit message has new lines, such as a squash merge, the JSON.parse will fail.
I suggest using JSON.stringify on the github.context.payload to make it properly encode it.
// Get the JSON webhook payload for the event that triggered the workflow
payload = JSON.stringify(github.context.payload, null, '\n');

At the very least the message might not read as well as the actual commit message, but it will actually send and not fail the action.

Actually nevermind. One of my engineers just informed me that we are passing a payload and not using the default context.
Sorry for bothering you.


Labs1-6

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Add labs 1-6
What did you learn from the changes you have made?
I have learn a lot of different approaches, technicks and tricks to proccess recommendation models, NLP, picture.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Any kind of AI generation , but course does't cover it.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Preproccesing took a lot of time to figure out why and how martrix transformed.
How were these changes tested?
Manuall comparing the evaluation metrics.
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

Reviewed and marked as completed


Question: How can i show full posts on the homepage

Hi, how are you. This theme looks great. But i want to build a micro+link+photo blog with it. So i want to know how i can display full posts on the homepage. Thank you

Hello! @stephenajulu
Thanks for showing interest in the theme.
As the description says, it is a text-focussed theme, hence I had intentionally kept only the permalink to the post on the homepage.
The code below is responsible for rendering the permalink. Shall you wish to display whole posts here you can just put {{ .Content }} to render the full content of the post. Here is how Hugo renders a single post.
https://github.com/invinciblycool/lekh/blob/56aa828fc157892572576a2ddbec81f14d4fab69/layouts/index.html#L36
I hope this answers your question, if not please feel free to comment.

Thank you very much

You have been a huge help @invinciblycool  thank you. Started working on turning your theme into a microblog following your advice.

Glad to be of help!


UI: things not sorted in the UI

variables list in the script editor
dashboard list in the Save As... dashboard option from data explorer
~buckets list in save as task from data explorer~ 15769
List if Notification Endpoints
List of Notification Rules
List of Checks

this would be sooooo nice

stale

not stale


Create docker-compose.yml

add docker-compose.yml file so it works with docker.

Approved; I'll merge both after the other PR is adjusted 👍


feat: add submodules along env token for repo with or without submodules

This is another try for repos with or without submodules.
If the code is executed by multiple repositories, some of which may not have submodules, use the if conditional statement to conditionally include the submodules parameter based on whether the repository has submodules or not.
TOKEN environment variable specified in the env section will not affect repositories that do not need to clone submodules.

Eagerly waiting to test this. :small_airplane:

What is the difference between the two approaches/env vars used (pr-analysis and build are both completely different)

I have synced now both pr-analysis and build.

This is another try for repos with or without submodules.
If the code is executed by multiple repositories, some of which may not have submodules, use the if conditional statement to conditionally include the submodules parameter based on whether the repository has submodules or not.
TOKEN environment variable specified in the env section will not affect repositories that do not need to clone submodules.

Eagerly waiting to test this. small_airplane

Apart from the token everything else is working now. I have tested the code by ESR app generator (with submodules) and Reval integration (without submodule) service. Both of them are gradle repo.


DO NOT MERGERT - fix-integration-test

Signed-off-by: Xian Chaobo<EMAIL_ADDRESS>

ping @aluzzardi @abronan @vieux
I have found that file cmd can not be found in dockerswarm/swarm-test-env.
impot / export / save integration test use file cmd to check tar file.
Have any good idea to solve this?

@jimmyxian it's my fault I'm going to correct this asap !!!

@vieux :)

replaced by #1349
Thanks a lot @jimmyxian for investigating :)


Guard Installation guide for Kubernetes Clusters built with Kubespray

Hello @tamalsaha ,
Please have a look at this doco. I have tried to make it a little detailed so that it is easier to consume even for a newbie.
Cheers,
Vikas

Fantastic work @vikas027 ! I have added some minor cleanup.


Custom tattoo

@fabricecaruso  Hi again!
Custom .PNG tattoo doesn't recognize .PNG file
I chose the userdata/system folder for my .PNG
In batocera.conf it appeared as mame.bezel.tattoo_file=/userdata/system and the game stays without bezel
I manually added the logo  /userdata/system/logo.png and just like that it appeared,
but after restart it goes back to /userdata/system

The tatoo thing is not related to ES... ( it's just a menu entry for BATOCERA, writing in the conf file )
It's managed by Batocera.linux.
So I can't help.
Please close this & maybe repost to batocera.linux repo


Build failure with Xcode 8.3.3, MacOS 10.12.5

Description
Followed the instructions here to re-install XVim but when I run make it fails with error 65.
Operation
After setting up a new self-signed certificate, issued
sudo codesign -f -s XcodeSigner /Applications/Xcode.app

and then make, when I run make it fails with error 65.
Followed the answer of issues#1058
Remove support for "IDEPlaygroundEditor".
Delete reference of "IDEPlaygroundEditor+XVim.h" and "IDEPlaygroundEditor+Xvim.m",
then  comment the reference code in "XVim/XVimHookManager.m".

and then make, but when I run make it also fails with error 65.
Expected behaviour
XVim installed and working in Xcode
Environments

MacOS Version [  10.12.5  ]
Xcode Version [  8.3.3  ]
XVim branch and revision [ master 4ac2725]
Keyboard Language [ English ]
Input source language [ English ]

Crash log (if any)
CompileC build/XVim.build/Release/XVim.build/Objects-normal/x86_64/IDEPlaygroundEditor+XVim.o XVim/IDEPlaygroundEditor+XVim.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
cd /Users/gongyidong/workspace/ios/XVim
export LANG=en_US.US-ASCII
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x objective-c -arch x86_64 -fmessage-length=125 -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -fcolor-diagnostics -std=gnu99 -fobjc-arc -gmodules -Wno-trigraphs -fpascal-strings -Os -Wno-missing-field-initializers -Wmissing-prototypes -Wno-implicit-atomic-properties -Wno-arc-repeated-use-of-weak -Wduplicate-method-match -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wno-empty-body -Wuninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wno-bool-conversion -Wenum-conversion -Wsign-compare -Wshorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector -Wno-strict-selector-match -Wno-undeclared-selector -Wno-deprecated-implementations -DXVIM_XCODE_VERSION=5 -DXVIM_XCODE8=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -mmacosx-version-min=10.7 -g -Wsign-conversion -Wno-infinite-recursion -IXcodeClasses/Xcode8 -IXcodeClasses/Xcode4 -IXVim -I/Users/gongyidong/workspace/ios/XVim/build/Release/include -I/Users/gongyidong/workspace/ios/XVim/build/XVim.build/Release/XVim.build/DerivedSources/x86_64 -I/Users/gongyidong/workspace/ios/XVim/build/XVim.build/Release/XVim.build/DerivedSources -F/Users/gongyidong/workspace/ios/XVim/build/Release -F/Applications/Xcode.app/Contents/Developer/../Frameworks -F/Applications/Xcode.app/Contents/Developer/../PlugIns -F/Applications/Xcode.app/Contents/Developer/../SharedFrameworks -include /Users/gongyidong/workspace/ios/XVim/build/SharedPrecompiledHeaders/XVim-Prefix-elexydpllzrbhtdrnipiabdnwnvz/XVim-Prefix.pch -MMD -MT dependencies -MF /Users/gongyidong/workspace/ios/XVim/build/XVim.build/Release/XVim.build/Objects-normal/x86_64/IDEPlaygroundEditor+XVim.d --serialize-diagnostics /Users/gongyidong/workspace/ios/XVim/build/XVim.build/Release/XVim.build/Objects-normal/x86_64/IDEPlaygroundEditor+XVim.dia -c /Users/gongyidong/workspace/ios/XVim/XVim/IDEPlaygroundEditor+XVim.m -o /Users/gongyidong/workspace/ios/XVim/build/XVim.build/Release/XVim.build/Objects-normal/x86_64/IDEPlaygroundEditor+XVim.o
clang: error: no such file or directory: '/Users/gongyidong/workspace/ios/XVim/XVim/IDEPlaygroundEditor+XVim.m'
clang: error: no input files
** BUILD FAILED **
The following build commands failed:
CompileC build/XVim.build/Release/XVim.build/Objects-normal/x86_64/IDEPlaygroundEditor+XVim.o XVim/IDEPlaygroundEditor+XVim.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
make: *** [release] Error 65

XVim build failure with Xcode 8.3.3, MacOS 10.12.5

I was getting this issue when building XVim from the master branch. I just tried again with the develop branch and it worked, and I have XVim in my XCode 8.3.3

I also got a (somewhat different) build failure:

PBXCp build/Release/XVim.xcplugin /Users/rzemer/Library/Application\ Support/Developer/Shared/Xcode/Plug-ins/XVim.xcplugin
cd /Users/rzemer/tools/XVim
builtin-copy -exclude .DS_Store -exclude CVS -exclude .svn -exclude .git -exclude .hg -strip-debug-symbols -strip-tool /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/strip -resolve-src-symlinks /Users/rzemer/tools/XVim/build/Release/XVim.xcplugin /Users/rzemer/Library/Application\ Support/Developer/Shared/Xcode/Plug-ins
** BUILD FAILED **
The following build commands failed:
Ld build/Release/XVim.xcplugin/Contents/MacOS/XVim normal x86_64
GenerateDSYMFile build/Release/XVim.xcplugin.dSYM build/Release/XVim.xcplugin/Contents/MacOS/XVim
(2 failures)
make: *** [release] Error 65
xcode V8.3.3
MacOS: 10.12.5 (16F73)

I have solve this error with add IDEPlaygroundEditor.h and IDEPlaygroundEditor.m

Can confirm it works for Version 8.3.3 (8E3004b) if you build from the develop branch

解决此问题的办法是：检出develop分支，而不是master分支，按照readme文件重新安装

Just link to IDEPlaygroundEditor instead of removing it
Open build phases and look at "link binary with libraries"


Add list primitives from Quartic speedups paper

implement the following primitives from https://arxiv.org/abs/2406.19378

SortInPlace
SymmetricDifference
HasDuplicates

part of #1348

@tanujkhattar ptal


username_atttibute supported for HTTP but not for Transport

Hi -
HTTP honours username_attribute parameter and picks CN as the username attribute (see output below). Whereas in Transport, it always expect DN. Is this by design? Why is this inconsistent while HTTP accepts CN and DN, whereas accepts only DN?
Thanks.
Jalaja
When asking questions, please provide the following information:

Search Guard and Elasticsearch version
SG - 6-6.1.1-20.1
ES - 6-1-1

Search Guard configuration files

bash-4.2# cat sg_config.yml

searchguard:
  dynamic:
    authc:
     clientcert_auth_domain:
        http_enabled: true
        transport_enabled: true
        order: 1
        http_authenticator:
          type: clientcert
          config:
            username_attribute: cn #optional, if omitted DN becomes username
          challenge: false
        authentication_backend:
          type: noop

Good catch, i put it as a feature request to our backlog

Cool Thanks 👍

Will label this as a bug since REST and transport should behave the same. Issue has been created, should be fixed in the next SG version.

Scheduled for SG 24.

Will be released with SG 24 expected next week.


Couldn't find any nodes satisfying the request.

Hey, so I'm trying to setup all my products and just to test them I set them to $0 and tried purchasing one I successfully purchased one and it automatically setup the server, but when I tried again I got this error which is the one in the title
Error: Couldn't find any nodes satisfying the request.

This is covered in the FAQ and is not a bug.


EntityManager: Implement singleton pattern, use global injection (minor BC break)

As per the article, since Doctrine is moving to modern static interface, let's start immediately with EntityManager.
This PR introduces:

Singleton pattern - Why should anyone track the instance? Let EntityManager do it itself!
Global injection - Parameters are boring, this is easier.

Targets 2.5 as this should be introduced ASAP - preferably in the next bugfix version.
TODO:

[ ] Fix tests.

Closing, since we missed the timeframe for merging this stuff.
Feel free to reopen on April 1st next year 😂


How do you ensure QAF is thread safe when running Parallel execution?i meant the Data Retrieved from Excel,driver etc...

QAF Version

Note: only the latest version is supported

Steps To Reproduce
1.
2.
3.

Expected behavior
Actual behavior
Is the issue reproducible on runner?

[x] QAS
[ ] Maven
[ ] Gradle
[x] Ant
[ ] Eclipse

Test case sample

Please, share the test case (as small as possible) which shows the issue

Are you facing any issue while running in parallel? If so please provide details and steps to reproduce.
This is not right place for questions or discussion. Please post your questions and/or discussions in qaf users group or stackoverflow with qaf tag.

closing inactive issue. Please post your questions in users group if required further help.


[CLOSED] Log effective resource limits for every jail_code call; also, fix build

We are curious whether async jail_code calls on Celery workers
have different resource limit configurations than synchronous
calls on LMS/Studio. We suspect it may be different
because codejail is configured via a Django Middleware, which
may not be initialized for Celery workers.

https://github.com/edx/edx-platform/pull/25532
https://openedx.atlassian.net/browse/TNL-7649
https://openedx.atlassian.net/browse/CR-2862

Closed in favor of https://github.com/edx/codejail/pull/103


review of spanish README (development branch)

As commented in PR #259 I'm creating the PR on the development brach.
Here is the original comment:
I reviewed the README-es.adoc to make it more natural for native spanish users and fixing some spelling mistakes.
A part from this changes I also added the missing sections from the main readme:

Adding Images
Updating HubPress

:+1:
Thank you so much!


from lxml import etree ImportError: DLL load failed: The specified procedure could not be found. (Windows+ Anaconda)

I am facing this issue upon running:
python labelImg.py
Traceback (most recent call last):
File "labelImg.py", line 43, in
from libs.labelFile import LabelFile, LabelFileError, LabelFileFormat
File "C:\labelImage\libs\labelFile.py", line 10, in
from libs.pascal_voc_io import PascalVocWriter
File "C:\labelImage\libs\pascal_voc_io.py", line 6, in
from lxml import etree
ImportError: DLL load failed: The specified procedure could not be found.

OS: Windows 10 Enterprise
PyQt version: 5.6.0

This helped me to address the issue:
https://stackoverflow.com/questions/54075542/lxml-installed-with-conda-importerror-dll-load-failed-the-specified-procedur


Simplify s[:] to s where s is a slice

Found using https://go-critic.github.io/overview#unslice-ref

@gdbelvin, it's not a good CI linter yet, more like an audit tool that requires manual use.
Some checks can be integrated into gometalinter and golangci-lint in future, but we're not there yet.

Well thanks for the contributions and tool improvements.


Postgres Flexible Server: Document that sync_commit_cancel_wait custom GUC is broken

Azure Flexible Server adds a custom setting sync_commit_cancel_wait that is of type integer but had Disabled as value:
postgres=> SELECT name, vartype, setting FROM pg_settings WHERE name = 'sync_commit_cancel_wait';
          name           | vartype | setting
-------------------------+---------+----------
 sync_commit_cancel_wait | integer | Disabled
(1 Zeile)

This breaks tooling that tries to parse integer parameters, as, well, integer, e.g. Postgres Exporter:
panic: Error converting setting "sync_commit_cancel_wait" value "Disabled" to float: strconv.ParseFloat: parsing "Disabled": invalid syntax

It would be good to document this bug, or best, to get it fixed. I've reported it privately last fall to a Microsoft/Citus employee, but I don't think there's a public bug tracker?

I'm not sure what the correct page is, but if Microsoft claims to offer Postgres as a Service, but then introduces some code changes that break the system catalogue conventions, I think those changes should be documented somewhere, maybe on an entirely new page like "Bugs we introduced ourselves that you should know about" or so.

@mbanck - Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can update the document accordingly.

I'm not sure what the correct page is, but if Microsoft claims to offer Postgres as a Service, but then introduces some code changes that break the system catalogue conventions, I think those changes should be documented somewhere, maybe on an entirely new page like "Bugs we introduced ourselves that you should know about" or so.

 It's frustrating to say the least

Looks like this was fixed now in Flexible Server, this GUC is no longer in pg_settings it seems, and the value now is -1:
=> SELECT name, vartype, setting FROM pg_settings WHERE name = 'sync_commit_cancel_wait';
 name | vartype | setting
------+---------+---------
(0 Zeilen)

=> SHOW sync_commit_cancel_wait;
 sync_commit_cancel_wait
-------------------------
 -1
(1 Zeile)

=>


No 'version' key in the manifest file

Cloned the latest repo and tried custom integration for Vaillant (VRC 700)
Found following in the log files (non-breaking warning):
2021-04-01 17:02:02 WARNING (MainThread) [homeassistant.loader] You are using a custom integration vaillant which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2021-04-01 17:02:02 WARNING (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'vaillant'. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of 'vaillant'

I'm about to release a new version, could you check with the last beta before the release ? https://github.com/thomasgermain/vaillant-component/releases/tag/1.5.0b6

Used the new integration beta version. Warning has disappeared.


Request: Support for RecyclerView.

This is a great library. Are there any plans to support RecyclerView?

RecyclerViews have a different method of interaction.
I haven't put in much time, but based on some quick searches, the approach I take in this library isn't really suited for RecyclerViews.
Combined with my current lack of time, it's unlikely that I'll support RecyclerViews.
I did find this link, which seems to suggest that more recent versions of the support library have basic swipe to dismiss functionality built in for RecyclerViews.
http://stackoverflow.com/questions/27293960/swipe-to-dismiss-for-recyclerview

Thanks for the update. I ended up implementing my own Adapter using RecyclerView's OnItemTouch Class. I'm closing this issue.


Remove redundant closure

Type T which implement FnOnce() should be directly moved into a box.

Thanks!


Collisions with other trait method

Thank for this amazing package, i am having an issue
Trait method activity has not been applied, because there are collisions with other trait methods on App\User
if a model uses both traits LogsActivity and CausesActivity it throws the error.
I can implement my own but is their a different solution?
Thanks

i figured out the way around this using php traits conflict handling.
if we have a user model and want to log activity on user model and we also want it to be the causer
use CausesActivity, LogsActivity {
LogsActivity::activity insteadof CausesActivity;
CausesActivity::activity as log;
}
now we have 2 available methods, activity and log.
Thanks.
Not closing the issue because this doesn't work by default

Thanks for posting your solution. Closing this for now and will fix the collision in the next major version of the package.


Keep place when editing

Original report on BitBucket by Taina Jääskeläinen.

When the user does some code changes (adds a code, deletes a code, or in TL adds a translation for a code or edits a translation):

After clicking on ‘Save’ the system returns the user to the top of the code list
If the code list is long, the user may need to scroll back to where they were many times

This is annoying, e.g., for translators who are translating CVs with many terms.
Can the system be made to keep place in the list after the user has saved?

Not really important at this point, will be reopened if some users complain about this issue. Closing for now


[FLINK-26955] Add CRD compatibility check to maven build

Add automated CRD compatibility check logic to the maven build comparing against the 1.0.0 release.
Manually verified + unit tests added for the cases covered by the checker

cc @bgeng777 @morhidi

Thanks @gyfora for the PR. Having such a tool overall is a great idea, it'll force us to think twice before introducing any changes to the CRD. I second @tweise's suggestion to agree formally on a few bullets that we add to the CRD checker, e.g.: https://www.faun.dev/c/stories/dineshparvathaneni/kubernetes-crd-versioning-for-operator-developers/

+1 LGTM, as we understand more about CRD version compatibility we should add/modify the rules here. Nice job!


Allow a test to specify a training data filter to prevent over fitting thresholds to previous incidents

Currently, there's a limitation with using anomalies whereby if you have an incident in your training data it'll be reflected in how your thresholds are calculated. This can lead to a situation whereby an incident occurs and then reoccurs within x days and is not flagged as it "looks" similar to the previous incident which is now influencing threholds. See below for an example of this in an hour_of_day seasonal freshness graph.

Jun 30th you can see an incident occurs and we get a linearly increasing delta in current time to last load time as no new data comes in. You can see the same issue occur on Jul 5th. However it's now considered within the threshold.
Note: The periodic bumps daily are expected (hence why hour_of_day is used for this to take them into account).
Describe the solution you'd like
I think there's two possible approaches.

Would be having some way to retrospectively tag something as an incident. In theory you could do this with an incident seed file with a start and finish time of an incident but this is kinda clunky as it involves a PR being merged into dbt every time you want to remove an incident from training data. Maybe this is a good approach?
Would be to apply prior knowledge at the time of test config which adds out of bounds thresholds for training data. e.g. a min and max tolerance. Anything outside that tolerance would be ignored when calculating thresholds, but included when looking at the detection periods.  I would envisage this would work with the following yaml being added to anomaly test config

training_thresholds:
    min_value: <when training any value < this will be ignored>
    max_value: <when training any value > this will be ignored>

One might ask well if you can apply that knowledge of the thresholds should you be doing an anomaly test in the first place or simply a static threshold test? I think it's still fair to do an anomaly test as it'll allow tighter tolerances during during normally consistent periods.
Describe alternatives you've considered
See option 1 above.
Would you be willing to contribute this feature?
More than happy to work on this, keen for feedback on the options though and a discussion first as I imagine this is an area that elementary may have already discussed internally.

Hi @mossyyy,
Definitely something we have discussed, @oravi could elaborate on it.
Until he does - for this specific use case I would recommend you to add where_expression that filters out these few anomalous hours in your training set.
When you add a where_expression to a test Elementary would "reset" the metrics (as this is a change to the underlying dataset) and will recalculate the metrics without the excluded rows.

Hi @mossyyy !
This is now available with the anomaly_exclude_metrics parameter:
https://docs.elementary-data.com/data-tests/anomaly-detection-configuration/anomaly-exclude-metrics
Cheers,
Itamar


Need to make Theme configuration more explicit

On Shesha when we navigate to the Themes configuration it is not quite explicit enough that the expected behaviour is that we modify on the left and see the results on the right.
Here are some changes we can apply to this screen to make it more clear to users:

Have bolder titles on the left and right panels. eg: 'Theming Parameters' and add supporting info/tool-tip
Include a small description below parameters that says "You can modify the values by selecting the colour block"
Making the Properties panel full height so that it looks more like a properties panel. Currently the results section is too dominant and you might not notice the parameters panel is customisable.

https://starter-adminportal-test.shesha.dev/settings/theme

@AlexanderSlavchovUX about the 3rd point, do you mean that the parameters panel should always span from the bottom of the header to the very bottom of the viewport?

Hey @James-Baloyi
For now can we start by just ensuring that the parameters panel is full length to the bottom. Please don't make any changes to the margin at the top so that it remains consistent with the results screen.
I think once it stretches to the bottom of the screen it will really help separate these two. :)


[Regression] Broken pipe when uploading binaries

New Regression Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Regression Information

Breaking version: [e.g. 2.107.0]
Last working version: [e.g. 2.105.2]

Regression Description
We're using fastlane to deploy iOS apps on CI server. We have proxy set up on CI server, I'm not sure about the root cause but we're not able to upload binaries with DAV option on, via this proxy. I noticed that in fastlane 2.106.0 (https://github.com/fastlane/fastlane/pull/13404) DAV is by default turned on, it makes our CI server not able to upload binaries. Is it possible to revert the default behavior so it's consistent with previous versions?

ENV["DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS"] = "-t Signiant"

@allenhsu Does @robmaceachern solution solve your issue?

@joshdholtz yes thanks @robmaceachern

@robmaceachern Thanks so much for answering that issue! ❤

@robmaceachern Why does this work as a solution (besides that is reverting back to the old state)? Should we add this to some documentation somewhere?

@janpio I'm not sure exactly why it was failing in this case but the issue description mentions DAV being disabled via a network proxy. I think each protocol has their own failure modes depending on local network/firewall settings. It looks like there is already a bit of documentation here but it could be improved to show all the available protocol options (DAV, Signiant, and (I think) Aspera).
Some other potential improvements I can think of:

Figure out some way to verify network conditions are suitable for the selected protocol before attempting upload and provide better error messaging.
Auto-retry with alternate protocol if we can detect a firewall-related failure.
Promote the preferred Pilot protocol configuration to a regular parameter (instead of an environment variable).


--full-refresh doesn't work in dev

Fixed here: https://github.com/fishtown-analytics/dbt/pull/350


Only check for crashed content if crash_check is true.

good catch, could you rename the commit to start with "fps:" so we know what it relates to. Once thats done I'll merge it

Done.


#3427 fixing distributer event propagation in remote execution plane

fixes #3427

fixed with https://github.com/keptn/keptn/pull/3660


Support lists of models

This PR allows routes to be annotated with:
@router.get("/things")
def get_things() -> list[Thing]:
    ...

Fixes #240

As noted in #240, this may not be an ideal solution; for example, each iterated call to self._migrate_response() creates a new ResponseInfo instance, which is immediately discarded because only its .body is needed.
It's possible that the conversion work could be done by a helper method, so that it's not self._migrate_response() that's getting called.
Please let me know if this is even desirable work, and if you'd like to see an improvement in the design here. :+1:

I want to test one or two additional items before this merges (if it's a desirable change); I'm particularly interested in this use case:
class Thing(BaseModel):
    ...

class TopLevel(BaseModel):
    things: list[Thing]  # <-- Will this get converted?

I anticipate that returning a JSON array (instead of an object) may be a niche use case, but I bumped into that while preparing a rough-cut tech demo to present in my workplace, which is how I got to this PR.

Hmm, this doesn't address the more common case that I described above. I think that responding with JSON arrays may be too niche a use case to incorporate into cadwyn.
If you think this PR is valuable, you're welcome to merge it. However, I recommend closing.
I'll work to submit a PR that allows nested objects to be converted, which is far and away the more common case that I expect to use at work. However, I'll open an issue first to document the target work.


added docs

you could also add the example folder
see webauthn example

The example folder would be this variance wallet


change "add to marketplace" text on button on your cards

make it so this changes wether the card is/isnt for sale


Bump nodejs buildpack

This adds support for specifying the npm version in package.json, among other things.
https://github.com/heroku/heroku-buildpack-nodejs/compare/fae41898...1ebb095a

LGTM

LGTM


Issue Flocker Volume Documentation

This is a...

[ ] Feature Request
[X] Bug Report

Problem:
Volume options seen at https://kubernetes.io/docs/concepts/storage/volumes/#flocker are still offering flocker.
The project hasent seen any forward movement: https://github.com/ClusterHQ/flocker
The companys website has been down for a while: https://clusterhq.com/
...probably because they arent around any more: https://news.ycombinator.com/item?id=13239032
...attempts to follow the most recent documentation always fail. the docs can be seen here: https://flocker.readthedocs.io/en/latest/kubernetes-integration/install-client.html#installing-on-ubuntu-16-04-64-bit
the instructions reference an AWS s3 bucket that seemingly doesnt exist..., perhaps someone forgot to pay the AWS bill... or perhaps there is no company to pay the bill.
Here is the s3 bucket: https://clusterhq-archive.s3.amazonaws.com

root@f5f690ee5c2f:~# add-apt-repository -y "deb https://clusterhq-archive.s3.amazonaws.com/ubuntu/$(lsb_release --release --short)/\$(ARCH) /"
Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease
Ign:5 https://clusterhq-archive.s3.amazonaws.com/ubuntu/16.04/amd64  InRelease
Err:6 https://clusterhq-archive.s3.amazonaws.com/ubuntu/16.04/amd64  Release
  404  Not Found [IP: <IP_ADDRESS> 443]
Reading package lists... Done
E: The repository 'https://clusterhq-archive.s3.amazonaws.com/ubuntu/16.04/amd64  Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@f5f690ee5c2f:~#

Proposed Solution:
Its pretty obvious that the flocker solution doesnt work, or isnt a readily available viable option for most people. I cannot seem to get past the initial install phase. Has anyone tried flocker lately? I believe it is misleading to offer it as an option.
I propose removal of flocker references in the documentation
Page to Update:
https://kubernetes.io/docs/concepts/storage/volumes/#flocker

Also, I see there are dead links in the example documentation, seen here: https://github.com/kubernetes/examples/blame/master/staging/volumes/flocker/README.md#L18


[Feature Request] Reduce Permissions for Amplify App

Currently the Amplify App uses a managed policy AdministratorAccess for its role
This is not best practice and will be an issue for any type of audit.
I realise that the Amplify App should not run in the management account, so the blast radius of this issue is reduced.
Still the usage of this managed policy is highly discouraged and violates the principle of least privilege.
Can you pinpoint the necessary permissions needed for operating Amplify?

iam identity center read access
iam identity center access for assigning/removing permission sets
notifications
probably repository access
IAM read access
....

im sure there are many more permissions necessary. but i don't think that amplify should be able to create IAM roles or interact with storage services like S3 and RDS.
https://github.com/aws-samples/iam-identity-center-team/blob/35ad5a7f43e84ed945d3d72d583ccc115eb9bc1d/deployment/template.yml#L42:L61

fix #132


Buttons/toolbar regression

getting this trying to look at a Service in My Services:
[----] I, [2016-08-12T06:50:31.543221 #26455:25e345c] INFO -- : Started POST "/service/tree_select/?id=s-10r13" for ::1 at 2016-08-12 06:50:31 -0700
[----] I, [2016-08-12T06:50:31.562150 #26455:25e345c] INFO -- : Processing by ServiceController#tree_select as JS
[----] I, [2016-08-12T06:50:31.562262 #26455:25e345c] INFO -- : Parameters: {"id"=>"s-10r13"}
[----] F, [2016-08-12T06:50:31.641131 #26455:25e345c] FATAL -- : Error caught: [NoMethodError] undefined method is_available?' for #<Service:0x007fbb2a046d88> /home/dclarizio/.rvm/gems/ruby-2.2.3/gems/activemodel-5.0.0/lib/active_model/attribute_methods.rb:433:inmethod_missing'
/home/dclarizio/dev/manageiq/app/helpers/application_helper/button/generic_feature_button.rb:13:in rescue in skip?' /home/dclarizio/dev/manageiq/app/helpers/application_helper/button/generic_feature_button.rb:10:inskip?'

@PanSpagetka, @romanblanco : please, fix this asap
thx!

Seems the service does not have supports now is_available you are faster than @durandom

@PanSpagetka @martinpovolny so far from my investigation, I know:

problem is with service_reconfigure button (https://github.com/ManageIQ/manageiq/pull/10194)
problem is, that the button does not support is_available?(:reconfigure), neither supports_reconfigure?, but uses the different way -- validate_reconfigure


Prototype adding URL guidance

What
Prototype where URL guidance for pages on the NHS website could sit in the NHS digital service manual.
Why
So the approved URL guidance for the NHS website can be published and adopted by teams publishing content on the NHS website.
Related to
URL standards for the NHS website (NHS.UK) #265
Tasks

[ ] Create a prototype to visualise where the approved URL guidance draft content can sit within the NHS digital service manual.

Started to prototype how we could add URL guidance into the service manual information architecture. Current thinking is on the review 2 environment: https://nhsuk-service-manual-review-wa-2-dev-uks.azurewebsites.net/guidance-by-topic/URLs/
First iteration is to create a new “Guidance by topic” section which contains “Accessibility” and “URL” guidance. I’ll continue to fill the URL guidance with the draft guidance which was approved at the last DSWG.
Once the inclusive content user research concludes, we can explore getting this proposed approach to adding URL guidance tested with real service manual users


Rename Strings to Constants

Either rename String to Constants and store both links and localized string etc. Or create a new file called Constants to store the urls.
See comment: https://github.com/rnystrom/GitHawk/pull/494#discussion_r143076287

Slightly off topic, @BasThomas what's the hacktoberfest label?

@rnystrom: #507
https://hacktoberfest.digitalocean.com


r-18 mode doesn't work.

r-18 mode doesn't work.
R-18mode = true
Download to normal image

more info please?


Feature: "exists:" prefix

https://optifine.readthedocs.io/syntax.html#exists
Partially fixes https://github.com/SHsuperCM/CITResewn/issues/204

Apologies for the extended delay, I am not currently accepting new PRs as I revamp the project for version 2 (PR #510). The feature will be added after the fact.


export 'XhrFactory' was not found in '@angular/common' in Angular 11 application

In angular 11.2.8 version,
Followed instructions as in @jscutlery/cypress-angular -
https://github.com/jscutlery/test-utils/tree/main/packages/cypress-angular
ng add @jscutlery/cypress-angular
ng g @jscutlery/cypress-angular:setup-ct --project cypress-angular
It did all setup required to execute test.
then,
npx cypress open-ct - it was throwing an error -
ERROR in ./node_modules/<EMAIL_ADDRESS>1448:15-25
"export 'XhrFactory' was not found in '@angular/common'
<EMAIL_ADDRESS><EMAIL_ADDRESS> @ ./src/sample.cy-spec.ts
 @ ./node_modules/<EMAIL_ADDRESS><EMAIL_ADDRESS>
Package.json

{
  "name": "ang2-conduit",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build --prod  --base-href ./ && cp CNAME dist/CNAME",
    "test": "ng test",
    "lint": "ng lint --force",
    "e2e": "ng e2e",
    "postinstall": "ngcc"
  },
  "pre-commit": [
    "lint"
  ],
  "private": true,
  "dependencies": {
    "@angular/animations": "11.2.8",
    "@angular/common": "^11.2.8",
    "@angular/compiler": "11.2.8",
    "@angular/core": "11.2.8",
    "@angular/forms": "11.2.8",
    "@angular/platform-browser": "11.2.8",
    "@angular/platform-browser-dynamic": "11.2.8",
    "@angular/router": "11.2.8",
    "@jscutlery/cypress-angular": "^0.3.0",
    "core-js": "^2.4.1",
    "marked": "^0.3.9",
    "rxjs": "^6.4.0",
    "tslib": "^2.0.0",
    "zone.js": "~0.11.3"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.1102.7",
    "@angular/cli": "^11.2.7",
    "@angular/compiler-cli": "11.2.8",
    "@angular/language-service": "11.2.8",
    "@jscutlery/cypress-mount": "^0.9.1",
    "@types/jasmine": "~3.6.0",
    "@types/jasminewd2": "~2.0.2",
    "@types/node": "^12.11.1",
    "codelyzer": "^6.0.1",
    "cypress": "^7.3.0",
    "html-webpack-plugin": "^4.5.2",
    "jasmine-core": "~3.6.0",
    "jasmine-spec-reporter": "~5.0.0",
    "karma": "~5.0.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "~3.0.2",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "^1.5.0",
    "pre-commit": "^1.2.2",
    "ts-node": "~4.1.0",
    "tslint": "~6.1.0",
    "typescript": "4.1.5"
  }
}

Installing @jscutlery/cypress-mount version 0.8.0 fixed the issue.
Thanks

Thx @Sathish787 for your feedback.
Did you have to upgrade or downgrade to 0.8? latest version is 0.10.0. Did you try it?

Cypress-angular was installing cypress-mount version 0.9.1 at that time  and manually uninstalled 0.9.1 version and installed 0.8.0 version


Bad distorted picture using the in-painting example provided

I noticed the exactly identical issue to this one in runwayml and I'm asking if there is something that we are missing.
I also tried to adapt the Python code from here mentioned also here but without any luck.
I just receive some weird runtime errors like:
Given groups=1, weight of size [320, 9, 3, 3], expected input[2, 4, 64, 64] to have 9 channels, but got 4 channels instead

Someone has some suggestion on how can I use the in-painting correctly?

The same distortion happens with huggingface/diffusers and I could notice that the example code of this repository was originally converted from here if I'm not seeing wrong, perhaps there are some issue regarding the area outside the mask?
I also tried with a full black mask and this causes distortion and quality losses on the photo as well, especially on people faces, another mention about this issue could be found here.
I also tried updating the code with the one provided by Runwayaml without success 😢

Another update here, after many research and infinite tries I just understood that is not an issue with this crate itself.
I'm using SD 1.5 and in my code I just added a post-processing step in order to mix the original untouched image within the result decoded from VAE and the original mask (not downscaled) and I get a better result.
By the way, the output from VAE also differs in saturation and brightness and a slightly difference between the inpainted area and the original image is noticeable.
I'm guessing that the encode-decode process from VAE make the image to loses their original properties.
An idea that I'll try for sure is dilating a bit the original mask in order to keep other border information from the decoded latent and then blend the luminosity of the latent and the original image (if someone know how I can achieve this in Rust would be awesome); with this trick I think that I could achieve a better result.
For what matters, to me the inpainting process with Diffusers is just not usable for processing images with people faces, the distortion is fairly aggressive.

Same issue here. I have a custom model that works perfectly on Automatic111 but not when I use it with diffusers.
Even if a use a mask, it still modifies all the faces and other small details all over the image.

Even if a use a mask, it still modifies all the faces and other small details all over the image.

That's a normal behavior as the VAE process the full image latent, including the area outside the mask.
In order to achieve a good result you should re-mask the original untouched area mixing with the inpainted area, blending the image and matching the new colors histogram.
I'll close this issue as is not an issue with this crate itself, actually is not an issue at all, processed image should be post-processed as Automatic111 and other tools does 😄


Groupcreateprop

Add support for datasets created with compact and contiguous layouts.

The changes with H5D_CONTIGUOUS and H5D_COMPACT work fine.
The creationProperties field also works, except in the case of the root group. Because the root group of a domain is created when the domain is created, the body of the request has to be checked for creationProperties at domain creation time. So as written, there's no way to set the creation properties for the root group.
I was able to have the root group inherit a creation property list sent at file creation by adding this after line 1121 in  domain_sn.py
if body and "group" in body and "creationProperties" in body["group"]:
    group_json["creationProperties"] = (body["group"])["creationProperties"]

Good catch about the root group property list.  I've checked in your suggested change.


Updated readme

Coverage remained the same at 66.667% when pulling 8cde9cb0847be7ed3d7f3cf2e62ef60e28839fd6 on pancho111203:master into e7d43bc284b453ac520092fd7b7ddcfd8bd94a6d on eclipsesource:master.


coolingPerTick function adds temperature instead of subtracting

According to the coolingPerTick function, the temperature gets added to how much a fission reactor cools per tick, which means the hotter the biome is, the faster it cools down. Is this intentional?

Since Minecraft biome temperatures range from -0.7 - 2.0, the current implementation breaks reactors in a biome with a temperature of 0 (Frozen River, Frozen Ocean, Snowy Plains, Ice Spikes), and reactors cool less for biomes with a temperature less than 0 (Frozen Peaks, Jagged Peaks, Snowy Taiga, Snowy Slopes, Grove). Source: https://minecraft.wiki/w/Biome#List_of_biome_climates


Swarm Mode Issue Doc Update

Expands upon and hopefully clarifies issues with Docker Swarm mode & Element OS interoperability.

Hi,
you write that

NetApp has provided feedback to the Docker team

Could you please point me to the feature request or issue? I've searched in the moby issues but found nothing related to this so I'm wondering about this statement.

I know that this subject has been raised with Docker directly through our corporate partner channels, but I’m not sure if any public issues were generated as a result of those discussions.


onChange cell getting issue.

const onChange = useCallback((d: Sheet[]) => {
d[0]["data"][1][1]={"ct": {"fa": "General","t": "g"},"m": "Nameofthescript","v": "Name of the script","bg": "#858a7e","ht": "0",};
console.info(d[0]["data"]);
}, []);
return ;
Please can suggest the example for onChange event for each cell. I couldn't find on it.
above one is failing while I set the cell value.

Please can you share the article on rows and column updates example.

https://ruilisi.github.io/fortune-sheet-docs/guide/api.html#overview, API is avaible via the ref of Workbook

import React, { useRef, useState, useEffect, useCallback } from "react";
import ReactDOM from 'react-dom';
import "./styles.css";
import { Workbook } from "@fortune-sheet/react";
import<EMAIL_ADDRESS>import { produce } from "immer";
import { ComponentMeta, ComponentStory } from "@storybook/react";
import { Sheet } from "@fortune-sheet/core";
export default {
component: Workbook,
} as ComponentMeta;
const settings =  [
{
name: "Terminal",
id: 0,
status: 1,
defaultRowHeight: 20,
scrollLeft: 0,
column: 25,
row: 20,
config: {rowlen: {"0": 50}},
celldata: [ {"r": 0,"c": 0,"v": {ct: {fa: "General", t: "g"},m:"Nameofthescript",v:"Name of the script","bg": "#858a7e","ht":"0"},},
{"r": 0,"c": 1,"v": {ct: {fa: "General", t: "g"},m:"BuyRate",v:"Buy Rate","bg": "#00ff00","ht":"0"},},
{"r": 0,"c": 2,"v": {ct: {fa: "General", t: "g"},m:"Quantity",v:"Quantity","bg": "#00ff00","ht":"0"},}
]
}
];
const App = () => {
const [sheets, setSheets] = useState(settings);
const onChange = useCallback((d: Sheet[]) => {
setSheets(d);
}, []);
return ;
};
export default App;
above code failing with semi colon issue
export default {
component: Workbook,
} as ComponentMeta;
Please can you guide what went wrong with

Maybe you should delete ',' at
.
In addition, this error is not related to this project.

Thanks, please can you provide js example. We have only typescript examples. It will be helpful


2022 speakers page speaker images & removed MC & speakers img console error fix

added new speakers & updated speakers on speaker page


Supports tablet

This shouldn't have been false, my fault. Will need to deploy a new version.

This is cool but one really low hanging fruit would be to detect tablets and increase the density to 3 or 4-up in the grid.

Agreed.


Default value is a custom function

Is there a way form me to do something like sql:"default:<my_function>"?

Nevermind, the issue was I needed to specify that it is a primary key and the type of it to match the function as well.


text mask display wrong

hello,
I'm using jquery.inputmask on text field and for unknown reason it display wrong in some mobile devices.
this is the imput line
<input type="text" id="dueDate" name="dueDate" class="form-control" tabindex="2" autocomplete='off' />
and this is the mask implement
$("#dueDate").inputmask("99/99", {       "placeholder": "MM/YY"     });
the attached image shows the problem: the text 12/18 shown as 12/81

apprechiate any help.

@gol1980 ,
Which version of the inputmask do you use?

@RobinHerbots
Version: 2.2.2


Linked my own blog2md migration script

I wrote a migration script to convert wordpress and blogger export data for hugo. Linked it here for interested users.

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

PR for doc changes need to go to https://github.com/gohugoio/hugoDocs.

This PR needs to be closed @palanirja.

As PR to hugodocs was merged, deleting this as requested.


Change/Feature Request -  Azure Compute Gallery should have standalone product documentation pages

"Azure Compute Gallery" deserves to have standalone product documentation pages rather then being part of Virtual Machine documentation. Compute Galley is also used by other Azure service (Azure Batch) end even though it is closely linked to VMs it deserves to have standalone documentation.
Many important aspects usually documented in "Concepts" sections, like for example Disaster Recovery, is not explicitly documented for the Compute Gallery.

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

ID: f1852dc6-3d2f-7edb-3234-3acee53b2b54
Version Independent ID: ae78ea1f-2819-7101-f621-699b81f9457b
Content: Overview of Azure Compute Gallery - Azure Virtual Machines
Content Source: articles/virtual-machines/azure-compute-gallery.md
Service: virtual-machines
Sub-service: gallery
GitHub Login: @cynthn
Microsoft Alias: cynthn

@zojovano
Thanks for your feedback! We will investigate and update as appropriate.

@zojovano
I'm going to assign this to the document author so they can take a look at it accordingly.
@cynthn
Can you please check and add your comments on this doc update request as applicable.

#please-close Thank you for your feedback. We are doing a review of the documentation and will take this feedback into consideration as we make changes :)


Add visual cue to the icon when its effect is about to elapse

Like a pulse animation (fading off and in rapidly in succession).

Done.


Use upload indicators API

https://learn.microsoft.com/en-us/azure/sentinel/connect-threat-intelligence-upload-api
https://learn.microsoft.com/en-us/azure/sentinel/upload-indicators-api

Fixed in https://github.com/cudeso/misp2sentinel/commit/ffde3d9b132c33929e28675ca4abc7b22f96558c#diff-4d7c51b1efe9043e44439a949dfd92e5827321b34082903477fd04876edb7552


Update README.md

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

[ ] Refactor
[ ] Feature
[ ] Bug Fix
[ ] Optimization
[x] Documentation Update

Description
Featured Covered in this PR

[ ] Task 1
[ ] Task 2

Related Tickets & Documents

Related Issue #
Closes #

Screenshots, Recordings
Please replace this line with instructions on how to test your changes, or any screenshots or recording you can attach here.
Tested Feature??

[ ] In Real Device.
[ ] In Emulator

Thanks @ayato91 , this is only readme update


Redeem and Unstake flow update to include merkle patricia proof verification for RedemptionIntentHash

Following are the changes needed:

In OpenSTValue.confirmRedemptionIntent function
Remove the following parameter:

bytes32 _redemptionIntentHash

Add the following parameter:

uint256 _blockHeight
bytes _rlpParentNodes

No restriction of onlyRegistrar, caller can be any account

Implement verification of redemptionIntentHash storage proof.

ref: MOSA-68

Resolved by #163.


make it clearer what values.yaml after feedback

I have gist for my minikube setup - https://gist.github.com/ryandawsonuk/d30db8fb0cec1933c5276b2b4c64ac86 - we should try to make this clearer in the README or work it into the documentation


ngFor in slides with loop="true"

Short description of the problem:
When slides are in loop mode updating an ngFor inside the slides causes the ng-repeat not to update sometimes, this i think is due to the cloned slides that make the loop mode work.
What behavior are you expecting?
ngFor to update in all slides in loop mode
Steps to reproduce:

create slides in content
loop = true
update ngFor in slide you will swipe to.

Which Ionic Version? 1.x or 2.x
2x

Hey @stellasoft-will ! Would you mind making a Plunker (here is a template: http://plnkr.co/edit/TW20lftdc5s622pcJPkp?p=info) that we can use to reproduce your issue? Thanks!

I'm not able to reproduce this. If you are still seeing this issue please create a new issue with more information. Either a plunker that reproduces the problem or some code that demonstrates the issue. Thanks! :smile: