Add tests for textlab api client

Short description

This PR for HIX score representation on page edit
Proposed changes

Tests for:

The text normalization function that is applied before sending text to the TextLab API
HIX score is requested and saved when the page translation is updated
HIX score is not updated when hix is disabled on region level
HIX score is not updated when hix is enabled on page level but hix_ignore flag is set to "on"
HIX score is not updated when hix is enabled on page level and page content is empty
HIX score is not updated when hix is enabled on page level and page content is not updated
HIX score is requested but response 400 received. Hix score is not updated

Related issues

Relates to: #2582

Pull Request Review Guidelines

One of new tests is failing. I think it would be better to fix it on CMS side. When TextLab API returns response with not a successful HTTP code (e.g. 400 like in test), it should ignore any value in the response body, even a valid one, like {"formulaHix": 15.48920568}
Could someone experienced please help with this? I am not sure how I can fix it in code...

Giving this high priority as per request from the tech meeting (any issues regarding HIX). Not sure this changes much here and it is only about testing the existing functionality anyway, so don't feel pressured to reschedule your work-life-balance just to get this out a day or two earlier.

Thank you @seluianova for your comments and suggestions!
Ready for final review round now

@MariaKabanova I have merged the new mock_server fixture https://github.com/digitalfabrik/integreat-cms/pull/2748, could you please update your tests to use it?

@MariaKabanova the new mock_server fixture has been merged https://github.com/digitalfabrik/integreat-cms/pull/2748, could you please update your tests to use it?

@seluianova thank you for your suggestions!
I updated my code respectively


Admin interface and asset pipeline

It looks like the admin UI doesn't reference correct images in production. As a result, none of the images are working. For example, on my box, CMS admin references the following image:
assets/comfortable_mexican_sofa/icon_regular.gif
However, due to asset pipeline in place, it should be something like this:
assets/comfortable_mexican_sofa/icon_regular-5a2f87ff91d5c3635c724a1a98721379.gif

That's really strange. I have an app in front of me running Rails 3.2 and it's fine. You're right that url for images doesn't have the hash but they load just fine. Sprockets is smart enough to deal with serving assets without cache busters.

I just checked
http://host.host/assets/image-41709047c17b65a5c7d6393dc446ecf1.gif

is also accessible without cache buster:
http://host.host/assets/image.gif

This is on Rails 3.2.1 with default asset pipeline stuff. So, unless there's some setting that I'm unaware of, it really should work.


Feature Request: Breadcrumb view on notes

I really like using Excalibrain to help me organize and "make sense" of my notes and I like how Excalibrain automatically infers relationships by which note links to which other note. I would like to take this a little bit further and show breadcrumbs (from a customizable root "index" page) at the top of my notes. It might look something like this:

Note: the above comes from the breadcrumbs plugin, but I like excalibrain because of how it handles relationships and because I like it's visual view
In my mind the breadcrumb shown would be the shortest path by default (although other options could be added as well)

Second this


rearranging layers off when lots of layers

🐛 Bug
When there are so many layers that the layers list starts showing a scrollbar on the side if you scroll down and then start trying to rearrange the layers everything goes wrong because that scrolling has not been taken into account in the geometry calculations. This needs to be fixed.

This has now been fixed in #536


[PE-D][Tester D] Inconsistent error message for index based commands

Description
The error message for a delete command with invalid index should be the same for an index which is below range as one which is above the range (as both are out of range)
Steps to Reproduce

Enter the command deletet 0 (which is an invalid index)
An error showing "Invalid command format" is displayed as attached in the first screenshot
Enter the command deletet n (which is more than the available length of tasks, ie n > taskList.size())
An error showing "The task index provided is invalid" gets displayed as attached in the second screenshot

Expected behaviour
The error message should be the same (task index provided is invalid) for both commands.
Actual behaviour
The error message saying "Invalid command format" is displayed, despite the general structure of the command being the same.
Operating System: macOS

Labels: severity.Low type.FunctionalityBug
original: nicleejy/ped#6

#196


Elaborate description with Sphinx cross-references is converted to field list.

The following example is of a PEP 257 multi-line docstring with a summary line and an "elaborate description" paragraph that contains Sphinx cross-references in the "elaborate description".
The docstring does not contain any docstring sections and (thus) no reST field list. This is because the class implements a series of abstract classes from collections.abc and doesn't have any attributes of its own.
class A:
    pass

class B:
    """Let's write a cross-reference to the above :class:`A`.

    Implements the following abstract class text text text text text text
    more text :class:`collections.abc.Set` text text text text text text
    :class:`frozenset` trailing text text text text text text text text
    :class:`collections.abc.Hashable` text text text text text text text text.
    """

When running docformatter 1.7.1 on the example it offers to:

Remove the text preceding the first cross-reference (possibly aiming to convert the :class: roles into a field list).
Introduce a space between the role and the opening backtick, turning :class:`title <link>`  into :class: `title <link>` . (This change would break the cross-references).

@@ -9,10 +9,10 @@
 class B:
     """Let's write a cross-reference to the above :class:`A`.

-    Implements the following abstract class text text text text text text
-    more text :class:`collections.abc.Set` text text text text text text
-    :class:`frozenset` trailing text text text text text text text text
-    :class:`collections.abc.Hashable` text text text text text text text text.
+    Implements the following abstract class text text text text text text more text
+    :class: `collections.abc.Set` text text text text text text
+    :class: `frozenset` trailing text text text text text text text text
+    :class: `collections.abc.Hashable` text text text text text text text text.
     """

Notice that if the docstring did have a docstring section docformatter would format it correctly, the following example works as expected:
class A:
    pass

class B:
    """Let's write a cross-reference to the above :class:`A`.

    Implements the following abstract class text text text text text text
    more text :class:`collections.abc.Set` text text text text text text
    :class:`frozenset` trailing text text text text text text text text
    :class:`collections.abc.Hashable` text text text text text text text text.

    Args:
        an_arg (str): Explains the arg.
    """

Using docformatter 1.7.1 with the following settings in pyproject.toml:
[tool.docformatter]
black = true
wrap-descriptions = 88
wrap-summaries = 88

A screenshot to help visualize the desired result:

v1.7.2-rc4 fixes this.

Closing this issue to #231.


Info on hub.docker.com still outdated

My comment in #15 didn't get noticed, I open a new issue.
Your repo on Docker Hub is not an automated build, you have to update the README manually.
Here you find more infos about automated builds. Seems it isn't possible to convert an existing repo, there is an open issue on Docker: https://github.com/docker/hub-feedback/issues/794
I don't want to be the one who always complains, so I'll propose some changes to the README.

Sounds like one needs to create a PR updating https://github.com/docker-library/docs/tree/master/rakudo-star
This can be semi-automated via adding an update.sh in this repo and letting @docker-library-bot commit here, cf https://github.com/Perl/docker-perl/pull/24#issuecomment-439660780

Now that 2019.03 is on Dockerhub, why is the README still not updated?

That'd be because nobody has made a PR to https://github.com/docker-library/docs/tree/master/rakudo-star :smile:
To be clear, giving @docker-library-bot commit bits here would not do anything with README.md -- the format in https://github.com/docker-library/docs/tree/master/rakudo-star is different (and templated so that all official images have a consistent image description format).
The approach we take with images maintained under https://github.com/docker-library is to make the README.md inside the repository just a stub that points to Docker Hub as the canonical source (see https://github.com/docker-library/golang#readme, for example), which helps us avoid duplicated documentation effort.
Some other images prefer to keep the documentation on Docker Hub explicitly slim and link elsewhere for documentation (either to a markdown file in GitHub or better yet to actual upstream documentation content so the documentation for the image lives within the proper upstream documentation directly).

Let's see if I can take care of this...  But I don't have the permissions
in Docker Hub, so it might be for nothing...

I have permission, and it's not required. But I think that an official maintainer has to make this PR.

It doesn't require any permissions of any kind -- we just need someone to take a look at https://github.com/docker-library/docs/blob/master/rakudo-star/content.md and provide a PR to that repository updating it as desired (which we then typically ask one of the image maintainers to sign-off on whether they approve of the changes).

Even more outdated now...

https://github.com/docker-library/docs/pull/1704

I've updated the info that I could find how to update. If stuff's still wrong, please open a merge request against docker-library/docs.


Stop smashing module names in OpenRPC to lowercase

This enables Mocks, reference apps, etc. to know the case-sensitive module names in each SDK.

This change also exists in #20, so this can be closed, I think.

To be addressed as part of a future non-patch release.


Game freezes at the start of voting

The voting options appear on the moderator screen, but the player screens just say "Submission Received" without showing voting options. The clock doesn't move, but the timer is still active and gives an almost-out-of-time warning beneath the Submission Received message, and the round will eventually finish without voting taking place.

Actually, it reads Round Finished on the player screen, but the moderator screen remains stuck at the start of voting.


Auto update deleted everything

Expected Behavior
Open Insomnia, find your usual workspace.
Actual Behavior
I opened Insomnia, which updated automatically (I didn't configure this), found confusing screens with confusing text and confusing options for logging in and storing things in some place or location, I chose location and found an empty workspace. When re-importing base collections and inserting login tokens, Insomnia displays an unhelpful error message.
Reproduction Steps
No response
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information

Insomnia Version
8.6.0
What operating system are you using?
Windows
Operating System Version
Windows 10.
Installation method
Download form insomnia.rest.
Last Known Working Insomnia version
No response

This message (which we are improving in 9.x in a few weeks) indicates that you are running a request without properly valuing an environment variable? Are all the environments variables properly valued?


_page.json return empty JSON object

Version
v2.4.0
Reproduction link
https://brotli.pro/benefits.json
Steps to reproduce
Add .json to any SSR pages
Eg: /apples ---> /apples.json
What is expected ?
Nothing ¯_(ツ)_/¯
but.. it could be nice to return specific data as JSON object
What is actually happening?
Return empty JSON Object : {}
Additional comments?
Bug or maybe a future awesome feature :thinking:
Shopify do the same with /orders  ----> /orders.json and it's awesome for debugging

This bug report is available on Nuxt community (#c9010)

THanks for reporting! It's not related to pages though but generally to 404 requests (Depending on the extension/data type).
it's a feature of https://github.com/nuxt/serve-placeholder to reduce workload for 404 requests so they don't go through the whole Nuxt SSR cycle, e.g. for robots.txt, json, images and so on.


Fix #327 set default row of gradio webui to 1 and drop empty/blank row

Fix #327 .
Here are the changes:

set the default number of row of dataFrame of launch_gradio_widget to 1
First replace all blank/empty input rows with np.nan which then could be dropped by the following np.dropna

Happy to take advice.😀 @lvwerra

Awesome, thanks @Raibows! Would you mind running make style && make quality to make the code quality checks happy?

Awesome, thanks @Raibows! Would you mind running make style && make quality to make the code quality checks happy?

I have runned make style && make quality to reformat the codes. But the github auto checks remained failed status. I guess maybe the difference versions of black caused it. I use python 3.8.10 with black 21.6b0.
Do you have any advice on it? Thanks.

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

Yes, indeed strange, it changed a few files it shouldn't have. I am using black==22.8.0. If that doesn't work I think just reverting the changes on the tokenizer and file_utils files should fix it.

@lvwerra I have reverted these changes. Now it only formats the gradio.py. Please check it.


Misc feedback addressed

addressing some more feedback from the review
Ping @dubee, @Harwayne

One last outstanding issue is:
https://github.com/knative/eventing-sources/pull/148/files#r243751345
So, instead of hard-coding the image (currently it is sjwoodman...), we wanna make that flexible and add an env - var .
I am not exactly 100% how than ko will resolve this,  @dubee, @evankanderson


[tracing] Propagate TraceID to the backend. Create a new setupEnv span. Fix span hierarchy

This PR tackles three main issues:

Propagate TraceID to the backend: this change enables Datadog APM to link the SDK traces with the backend traces and logs
Use a dedicated span for the setup actions: this change traces the setup actions performed by every test suite and links the setup span to the suite span

TODO:

[x] Fix span hierarchy: Actions performed inside each test case are linked to the suite span instead of the test span. The test span created in the beforeEach hook needs to be activated before the test code runs.

Looking good! The hierarchy of spans is maintained till the backend 👌
One downside with the final refactor is that we lost the parent Span, and now we have a bunch of top-level spans that belong to the same suite but we don't have a way to point to "all of them".

I will look at it! Thanks @sgirones


How to load data for a RootContainer supplied to Router on server side?

I pass a RootContainer with a Relay.Route supplied to it in the isomorphic-relay-router. This root container contains other RootContainers with different Relay.Routes in the component supplied to it. For a complete server side rendering I would like all the data for the RootContainer supplied to router and RootContainers loaded by the component in the supplied RootContainer to be loaded server side.
I read somewhere in the comments that IsomorphicRelay.Renderer should be used in place of the default Relay.Renderer. I can replace the RootContainers with isomorphic renderers. Will it solve the problem? The renderer needs an environment as argument which is different server and client side. How can I effectively use the same renderer while passing in different environments? The problem is particularly serious on server side. I can't create a global variable. So there should be a way to pass the environment created on renderOnServer.js to the IsomorphicRenderer I use in place of RootContainer. this.context.relay is undefined when passed as environment to the renderer.

Why do you need multiple RootContainers/Renderers in the first place?

Because I don't fetch data for all components from a single viewer query properly traversing the graph. Rather I directly query node for data req of those components by passing the nodeId in the following way:
'use strict';

import Relay, {
  Route,
} from 'react-relay';

export default class xyzRoute extends Route {
  static routeParams = {
    xyzId : ''
  };
  static queries = {
    viewer: (Component) => Relay.QL`query {
      node(id : $xyzId) {
        ${Component.getFragment('viewer')}
      }
    }`
  };
  static routeName = 'xyzRoute';
}

Rather I directly query node for data req of those components by passing the nodeId

But you can do it without multiple RootContainers/Renderers.

Even then, if say I use
<Route path="/" component={HomeScreen} queries={ViewerQueries} prepareParams={(params) => {return {...params}}} >
data is rendered on server. However, if I use
<Route path="/" component={HomeScreenContainer} prepareParams={(params) => {return {...params}}} >
and pass a Route equivalent of ViewerQueries to the container, data is fetched from the client.
So, are you trying to suggest that I should not use containers/ renderers at all apart from apart from one call to IsomorphicRelay.Rederer made in renderOnServer.js?

The reason I use the current pattern is because I dont have to care about the entire graph and keep track of properly calling getFragment amongst parent and children components. I get the flexibility to load containers on demand in any existing component without having to worry about how data will flow down from parents.

So, are you trying to suggest that I should not use containers/ renderers at all apart from one call to IsomorphicRelay.Rederer made in renderOnServer.js?

You should never render Rederer or RootContainer yourself when using isomorphic-relay-router. See the ToDo example in the isomorphic-relay-router repository. Also see the documentation for react-router-relay about how to correctly configure routes.


More as a suggestion: button(s)

Hello! Thank you for your work on projects and sharing! I am wondering, why physical control was removed in this version? Web control is good and all, but - would be convenient still able control without. Was there a technical reason not putting button code from previous analog input version to this project? Thank You!

Simply because I didn't need it :) Feel free to add it back in, it would be
easy enough.
On Fri, 21 Oct 2022, 12:33 Juris Perkons, @.***> wrote:

Hello! Thank you for your work on projects and sharing! I am wondering,
why physical control was removed in this version? Web control is good and
all, but - would be convenient still able control without. Was there a
technical reason not putting button code from previous analog input version
to this project? Thank You!
—
Reply to this email directly, view it on GitHub
https://github.com/s-marley/ESP32-INMP441-Matrix-VU/issues/12, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACSGWSJLGQOM4YYVAKAMZW3WEJ5SNANCNFSM6AAAAAARLCSDNI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Supply Reconciler with TaskStatusProvider in constructor and remove from arguments in start method

To ensure that task statuses are all coming from a single source of truth, this alters the Reconciler interface so that the start() method no longer accepts a list of TaskStatus protos. Instead, it is expected that the implementing class will accept a TaskStatusProvider in its constructor, which it will consult to fetch a collection of all task statuses currently known by the scheduler. To this end, the StateStore interface now extends the TaskStatusProvider interface with its getTaskStatuses() method. All default implementations of these interfaces now reflect the new semantics.

@mrbrowning:  Tests failing?  Also this PR will need to bump build.gradle version.

@gabrielhartmann Tests are passing.

@mrbrowning:  Unit test failing.

@mrbrowning:  I this for INFINITY-321 ?

@mesosphere-ci: retest this please


improve buffered/seeked detection

native "playing"  triggers when readyState is 3 and, in some browsers, whenever it seems to feel like. It should be more correct to use "canplaythrough" to detect when a buffer or seek is completed.

@bwallberg added wip multi-engine (currently only Shaka) demo app to help testing this change. I'll add the last bits once other things are out of the way.

(build works locally, need to look into what's problematic in actions)


add conversion btw bigint <-> number

https://scryptworkspace.slack.com/archives/CLSHPUZC3/p1673377206206569
Also add an example here https://scrypt.io/scrypt-ts/getting-started/how-to-write-a-contract#array-types

Maybe like these?
https://stackoverflow.com/questions/53970655/how-to-convert-bigint-to-number-in-javascript
https://stackoverflow.com/questions/56097821/i-am-trying-to-convert-a-javascript-number-type-to-a-bigint-to-be-passed-to-a-po


CLOUDSTACK-9026: Modifying testpath for adding missing parameter

Adding service_offering creation in testpath_storage_migration.py testpath which is missing right now

Testcase result:
Test migrate Volume (root and data disk) ... === TestName: test_01_migrate_root_and_data_disk_nonlive | Status : SUCCESS ===
ok

Ran 1 test in 1688.400s
OK

LGTM  based on test results!!
Test migrate Volume (root and data disk) ... === TestName: test_01_migrate_root_and_data_disk_nonlive | Status : SUCCESS ===
ok

Ran 1 test in 1778.920s
OK

did cod walk thought. Looks good to me .


feat(thanos): add needed configuration and resources to deploy Thanos

This PR integrates the thanos module with the kube-prometheus-stack and it goes hand-in-hand with this PR in the thanos module. It deploys the configuration and resources needed to deploy a Thanos sidecar with Prometheus and then export the metrics to an S3 bucket for persistence.
All these configurations are applied conditionally when a variable  metrics_archives is passed on module call. This also means that the kube-prometheus-stack module must depend on the thanos module in the case that we deploy the latter.
The code is mainly adapted to an AWS deployment but is easily adaptable to other deployments, the only thing that needs changing is the bucket configuration (on AWS we use IAM roles and Kubernetes ServiceAccounts to allow pods to connect to the S3 bucket but on other services we might need API and Secret Keys).
Example module call:
module "monitoring" {
  source = "git::https://github.com/camptocamp/devops-stack-module-kube-prometheus-stack//eks"

  cluster_name     = module.eks.cluster_name
  argocd_namespace = local.argocd_namespace
  base_domain      = module.eks.base_domain
  cluster_issuer   = local.cluster_issuer

  metrics_archives = module.thanos.metrics_archives

  prometheus = {
    oidc = module.oidc.oidc
  }
  alertmanager = {
    oidc = module.oidc.oidc
  }
  grafana = {
    enable = false
    additional_data_sources = true
  }

  depends_on = [module.argocd_bootstrap, module.thanos]
}

I added 2 commits today that added some outputs to the module to say which components are activated. This useful in this case to then conditionally modify the configmap of the helloworld start page and only show the links for the applications that are actually deployed.


Support merging ARCHE resources

It's plausible that an external database provides data suggesting a few resources should be merged in the ARCHE (as they share same id). This should be supported.
Example https://arche-dev.acdh-dev.oeaw.ac.at/browser/search/words=Schopenhauer&payload=false&order=titleasc&limit=10&page=1

Implemented something along the way and definitely there in v1.0.0


Add support for kafka schema registry ACL

Hi. Would it be possible to add support for kafka schema registry ACL in the operator?
https://api.aiven.io/doc/#tag/Service:_Kafka/operation/ServiceSchemaRegistryAclAdd

Hey! Thanks for the request. Added to the backlog.

Hey, @christoffer-eide! 👋
It is now implemented and will be released soon.


#309 dl select - Issue fixed for arrow up down select

Thank you for your contribution to the repo. Before submitting this PR, please make sure:

[ ] Your code builds clean without any errors or warnings
[ ] You are using approved terminology
[ ] You have added unit tests
[ ] You have updated documentation
[ ] You have tested your changes

Please provide a description of the changes proposed in the pull request and reference any related issues in the repository.
Please indicate if this PR contains:

[ ] A bug fix
[ ] A feature request
[ ] Breaking changes
[ ] An enhancement

Stale or Non relevant PR


Changing network attachments should kick off a rolling update

In #1021, we fixed the updater to replace any tasks that need a new set of endpoints. We need to do the same thing with network attachments.
This is harder than with endpoints because we don't have a stable network attachment object to compare between the task and the service (the network attachments on the task are added by the allocator). We may want to tweak the API to make it easier to detect changes in network attachments, if that's still possible.
cc @aluzzardi @mrjana @stevvooe

We will need to revert #1024 when this is fixed.
cc @dongluochen

This is harder than with endpoints because we don't have a stable network attachment object to compare between the task and the service (the network attachments on the task are added by the allocator). We may want to tweak the API to make it easier to detect changes in network attachments, if that's still possible.

Could you elaborate more?
So the logic lives in IsTaskDirty https://github.com/docker/swarmkit/blob/master/manager/orchestrator/task.go#L65
In TaskSpec, we have NetworkAttachmentConfig which contains target (the network ID [or name?])
In Task, we have NetworkAttachment, which contains Network, which contains the ID and the Name.
Could we compare those together to figure out if an update is necessary?

Could we compare those together to figure out if an update is necessary?

Yes, in theory we can. What I meant was that it's not a matter of just doing a reflect.DeepEqual.

These are different data types
Not sure we want to assume the same order of networks between the Task and the TaskSpec (it looks like the current implementation preserves this order, but it seems like a questionable assumption to make)
The allocator may add the ingress network to NetworkAttachment even though it's not specified in the spec. Knowing whether the ingress network should or shouldn't be in NetworkAttachment involves some networking business logic around things like host publish mode.

So it's theoretically solvable, but it involves IsTaskDirty needing to know an unfortunate amount about how the allocator works.
I'd suggest defining a function in the allocator that checks if the task's network attachments are up to date, and calling that from IsTaskDirty. It can reuse the isIngressNetworkNeeded function.

Note that isIngressNetworkNeeded is exported in #2049.


GPUGridAggregator: use fp64arithmetic module instead of fp64

For #

Background

Bump luma.gl dep to beta.2
GPUGridAggregator: use fp64arithmetic module instead of fp64

Change List

GPUAggregator: use fp64arithmetic instead of fp64

Coverage decreased (-2.4%) to 80.722% when pulling 5c5f983cdff0c6c61185fd78d28ca6f8295f3d7f on fp64arithmetic into 88b2c0a6bf8afc7eaaa7995ed37c61714524e9f8 on master.


Trim redirects (round 1)

I wrote a tool to check link clicks on each source URL in the redirection file. This PR looks at the first 500 redirect entries and trims any entry that has zero page views for the last 90 days. Also attaching a tab-separated values file showing link clicks.
The diff doesn't seem to be any good, but any redirect source_path links with 0 hits were deleted from the redirection file (295 entries).
clicks.txt

Closing in favor of #21772.


main to release-0.10

Merging the latest doc updates and e2e tests back to release-0.10.

Hold for a while. I'll push some documents updated today.


[159] Create EvaluationCriteria model & migration

Main tasks
#159

Added missing models for phase
Modified existing models for evaluation_form and user
Added factories for agency, challenge, evaluation_form, phase, and user due to required associations with evaluation_criteria


fix ddns support

Fixes: #328

I'm probably going to merge this sooner rather than later as I'd like to cut a new release.. but a note would be helpful @sadysnaat :-D

I'm probably going to merge this sooner rather than later as I'd like to cut a new release.. but a note would be helpful @sadysnaat :-D

@thebsdbox Issue logged at #328


Create an indexed list component

An indexed list component needs to be added to our component system. Currently, the investigations directory page employs this component.
For example:

The initial version of the indexed list component has been implemented into the prototype.
Additional improvements to the component will be made when it's migrated to wds-react.
PR containing this implementation coming later today.


Attachment RG scope causes terraform error

Tried to use an RG scope for an attachment.
I set the resource_groups_scope with one resource group name in the array. This was done after the SCC instance with a profile attachment for "AI Security Guardrails 2.0" has been deployed (originally using [] for the RG scope). When trying to update the deployment with the new RG scope, I got an error on apply (plan was successful):
2024/09/06 18:11:48 Terraform apply | Terraform will perform the following actions:
 2024/09/06 18:11:48 Terraform apply |
 2024/09/06 18:11:48 Terraform apply |   # module.create_profile_attachment["AI Security Guardrails 2.0"].ibm_scc_profile_attachment.scc_profile_attachment will be updated in-place
 2024/09/06 18:11:48 Terraform apply |   ~ resource "ibm_scc_profile_attachment" "scc_profile_attachment" {
 2024/09/06 18:11:48 Terraform apply |         id                    = "42f*****94/7e0*****f13ea/38-****6d"
 2024/09/06 18:11:48 Terraform apply |         name                  = "1 daily full account attachment"
 2024/09/06 18:11:48 Terraform apply |       ~ schedule              = "daily" -> "every_30_days"
 2024/09/06 18:11:48 Terraform apply |       ~ status                = "disabled" -> "enabled"
 2024/09/06 18:11:48 Terraform apply |         # (12 unchanged attributes hidden)
 2024/09/06 18:11:48 Terraform apply |
 2024/09/06 18:11:48 Terraform apply |       + scope {
 2024/09/06 18:11:48 Terraform apply |           + environment = "ibm-cloud"
 2024/09/06 18:11:48 Terraform apply |
 2024/09/06 18:11:48 Terraform apply |           + properties {
 2024/09/06 18:11:48 Terraform apply |               + name  = "scope_type"
 2024/09/06 18:11:48 Terraform apply |               + value = "account.resource_group"
 2024/09/06 18:11:48 Terraform apply |             }
 2024/09/06 18:11:48 Terraform apply |           + properties {
 2024/09/06 18:11:48 Terraform apply |               + name  = "scope_id"
 2024/09/06 18:11:48 Terraform apply |               + value = "06****6f1"
 2024/09/06 18:11:48 Terraform apply |             }
 2024/09/06 18:11:48 Terraform apply |         }
 2024/09/06 18:11:48 Terraform apply |
 2024/09/06 18:11:48 Terraform apply |         # (31 unchanged blocks hidden)
 2024/09/06 18:11:48 Terraform apply |     }
 2024/09/06 18:11:48 Terraform apply |
 2024/09/06 18:11:48 Terraform apply | Plan: 0 to add, 1 to change, 0 to destroy.
......
2024/09/06 18:11:56 Terraform apply | module.create_profile_attachment["AI Security Guardrails 2.0"].ibm_scc_profile_attachment.scc_profile_attachment: Modifying... [id=42f*****94/7e0*****f13ea/38-****6d]

Error: ReplaceProfileAttachmentWithContext failed Necessary attachment parameters are not available to create or update attachment.

So I tried to change the RG scope back to [] but then somehow the schematics state got the module.create_profile_attachment["AI Security Guardrails 2.0"].ibm_scc_profile_attachment.scc_profile_attachment resource stuck with a non-empty value that it cannot refresh and I cannot even undeploy the config:
2024/09/06 21:16:31 Terraform refresh | module.create_profile_attachment["AI Security Guardrails 2.0"].ibm_scc_profile_attachment.scc_profile_attachment: Refreshing state... [id=42f*****94/7e0*****f13ea/38-****6d]
 2024/09/06 21:16:33 Terraform refresh | Error: Error setting scope: scope.0.properties.2.value: '' expected type 'string', got unconvertible type '[]interface {}', value: '[]'
 2024/09/06 21:16:33 Terraform refresh |
 2024/09/06 21:16:33 Terraform refresh |   with module.create_profile_attachment["AI Security Guardrails 2.0"].ibm_scc_profile_attachment.scc_profile_attachment,
 2024/09/06 21:16:33 Terraform refresh |   on .terraform/modules/create_profile_attachment/modules/attachment/main.tf line 64, in resource "ibm_scc_profile_attachment" "scc_profile_attachment":

Affected modules

Terraform CLI and Terraform provider versions

Terraform version:
Provider version:

Terraform output

Debug output

Expected behavior

Actual behavior

Steps to reproduce (including links and screen captures)

Run terraform apply

Anything else

By submitting this issue, you agree to follow our Code of Conduct

A variation of this problem also happens in the following scenario:

Deploy the DA with a profile attachment (e.g. ["AI Security Guardrails 2.0"]) with default value for RG scope (i.e. [])
Once SCC is deployed, go to SCC instance and modify the scope on the created attachment by adding some RG exclusions (I have more than 3, the number may need to be sufficiently large to trigger the error), but keep the main scope as "account".
Try to undeploy the DA - it fails on resource refresh

I get an error indicating that there is an issue in the provider itself when it tries to read/map the scope parameters and gets the new values from the RG exclusion entries:
2024/09/11 18:32:31 Terraform refresh | Error: Error setting scope: scope.0.properties.2.value: ''
expected type 'string', got unconvertible type '[]interface {}', value:
'[map[scope_id:a1***39 scope_type:account.resource_group]
map[scope_id:5b***09 scope_type:account.resource_group]
map[scope_id:8e***f3 scope_type:account.resource_group]
map[scope_id:ea***cc scope_type:account.resource_group]
map[scope_id:07***f4 scope_type:account.resource_group]
map[scope_id:5d***51 scope_type:account.resource_group]
map[scope_id:70***18 scope_type:account.resource_group]]'
 2024/09/11 18:32:31 Terraform refresh |
 2024/09/11 18:32:31 Terraform refresh |   with module.create_profile_attachment["AI Security Guardrails 2.0"].ibm_scc_profile_attachment.scc_profile_attachment,
 2024/09/11 18:32:31 Terraform refresh |   on .terraform/modules/create_profile_attachment/modules/attachment/main.tf line 64, in resource "ibm_scc_profile_attachment" "scc_profile_attachment":
 2024/09/11 18:32:31 Terraform refresh |   64: resource "ibm_scc_profile_attachment" "scc_profile_attachment" {

It looks like any change to the attachment in SCC after deployment will cause the scope to get updated with [] as exclusion list and it will make the schematics state effectively invalid because now it cannot be refreshed - that [] value will always cause a read error.
Then the SCC DA cannot be undeployed or its inputs updated, the only way out is to clean up schematics workspace and delete the DA.

@jor2 - the case that you submitted above is a different issue. The error you show in the output indicates that you did not supply a parameter that is required, but no default value is in the profile. This is not the same as the  scope read error above.

@jor2 - the case that you submitted above is a different issue. The error you show in the output indicates that you did not supply a parameter that is required, but no default value is in the profile. This is not the same as the scope read error above.

@in-1911 are you still able to reproduce this error? I wasn't able to.


Implementation of new config subcommands

Implement:
https://github.com/bundler/bundler/issues/4600

@denniss can you fix the rubocop feedback reported in travis please 😄

@indirect Can you take a peek at this? I started this in response to https://github.com/bundler/bundler/issues/4600 . I used the existing config_spec.rb as a starting point and to pass the implementation of the new command (currently called config2 and the spec is in config2_spec.rb).

ping @indirect

Changed the specs to not pass --local by default. Also fixed the mistake you found @indirect

Currently new implementation is aliased as config2. I'd like to remove the existing config command and renamed config2 to config if you guys think this looks okay.

Since this is a breaking change, we can merge it to master behind a feature flag that switches the new implementation on. Then, after we ship 2.0 and the feature flag is always on, we can delete the old implementation. 👍

@indirect @segiddins While working through merge conflight, I was wondering: If the same key exist for environment variable (`ENV['BUNDLE_BAR']) and global (~/.bundle/config) which has higher precedence? Currently environment variable has higher precedence. Is this correct? Does it matter?

Currently environment variable has higher precedence. Is this correct? Does it matter?
yes, and yes

@denniss what's the status of this PR?

I won't be able to touch this for another 2 weeks. Busy with life at the
moment. Mich apologies.
On Tue, Aug 29, 2017 at 7:38 AM Samuel Giddins<EMAIL_ADDRESS>wrote:

@denniss https://github.com/denniss what's the status of this PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bundler/bundler/pull/5507#issuecomment-325684956, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAXiZulV9z5YJjo_8xdt4NvlNVy--udeks5sdCJKgaJpZM4MWEQh
.

https://github.com/bundler/bundler/pull/5981 is an alternative to this PR

Superseded by #5981


Syncthing process priority

The UI should allow reprioritizing the syncthing process so that it does not interfere with UI responsiveness.
Also should support setting the maximum number of threads to spawn with the GOMAXPROCS environment variable

I have no clue what you mean with reprioritising the syncthing process. It just starts as a background child process of the syncthing-macosx bundle and there is no interfere with UI responsiveness.
Currently it is not possible to pass environment variables to the child process.

I meant something equivalent to spawning with the command "nice -n 20 syncthing" so that other processes get priority. Syncthing doesn't as of now cause issues with UI responsiveness per se, but it does seem to slow down performing other computationally expensive tasks on the machine, when sync should probably be the least important thing going on.

Yeah now I understand. You mean in context of Operating System UI responsiveness. The NSTask class has a qualityOfService property which is used for this purpose instead of chaining in a nice call.
Note to self:
https://developer.apple.com/reference/foundation/nstask/1415794-qualityofservice?language=objc
https://developer.apple.com/library/content/documentation/Performance/Conceptual/power_efficiency_guidelines_osx/PrioritizeWorkAtTheTaskLevel.html


Auto corrected by following Lint Ruby Style/SafeNavigation

Auto corrected by following Lint Ruby Style/SafeNavigation
Click here to configure it on awesomecode.io

Coverage remained the same at 96.207% when pulling ffa09e7cc4680b4d258fe80590c5b52d31e9ee23 on awesomecode-lint-ruby-style-safenavigation-47733 into bb9f383db2c3a34c61abe59643f7213772eaa77b on master.

Coverage remained the same at 96.207% when pulling ffa09e7cc4680b4d258fe80590c5b52d31e9ee23 on awesomecode-lint-ruby-style-safenavigation-47733 into bb9f383db2c3a34c61abe59643f7213772eaa77b on master.


Fix Sprockets deprecation warning with v3 and v4 support

No need to use register_engine method as we specify all the the others for Sprockets v4 support. But since gem still allows Sprockets 3 we need to support it and use the register_engine method. This follows the Sprockets upgrade guidelines although I'm unaware if other changes are necessary. I'm able to contribute more with some help/advice.

@TannerRogalsky I submitted this due to #23 not updating to run against passing tests. But also realized the change was just for Sprockets v4 and this gem supports v3 and up so I updated the code to account for what is documented for supporting both versions.

@javierjulio Thank you! I'm just heading out but I look forward to reviewing and merging this this evening.

This was published in v0.9.1. Thanks again, @javierjulio!


Update repositories.txt

Closing as duplicate of https://github.com/arduino/library-registry/pull/1406


Camera trigger now working on pins 5,6

I've been testing the camera trigger and haven't got it working on Pins 5&6 of the FMU (TRIG_PINS = 56). I've also tried the setting TRIG_PINS = 34 which works fine.
I'm wondering if there was a bug introduced somewhere because the default pins are in fact 5,6.
@birchera Do you guys have the same issue?

Tested on master

Does it work if you stop the trigger app and restart it again via the console? (with pins 5,6)

@mhkabir No, I tried all possible things.

@mhkabir On which pins have you been using it?

BTW, this is using the PWM interface (TRIG_INTERFACE = 2)

I've been using it on 1,2 in GPIO mode. I had previously run into an issue where it would clash with the fmu driver and cause issues. Restarting the trigger app, or starting fmu in mode_gpio beforehand worked. For 5,6 the fmu driver should start in mode_pwm4 leaving 5,6 free. Cross check rcS just in case it isn't for you.

It works for us. As @mhkabir mentioned you need to start fmu driver in pwm4 mode. Since it runs on 3&4 for you it is likely an issue related to that.

@birchera I've checked that as well, FMU is started in mode pwm4. I even killed fmu and cam trigger and started them manually again, same story.

When you trigger on 3&4 I think you overwrite commands from the fmu driver and they might interfere. I remember we had some issues setting it up differently, but can't quite remember. Let me quickly dive into some old PRs.

@birchera Thanks, that would be great!

We still use the exact same setup as on current master.
What hardware do you use? We have it running on a pixracer, so v4.

@birchera I'm trying with pixhawk

@birchera Ok, I got one step further. The reason why it worked on pins 34 was because the fmu was put into mode pwm4. In short, the camera trigger only works on those pins which are also configured by the fmu. So now I started fmu in mode pwm (all 6 outputs) and then I was able to use the camera trigger on pins 56. However, I don't think this is the way it was designed to work, right?

When you trigger on 3&4 I think you overwrite commands from the fmu driver and they might interfere.

No I don't think that is how it should be. But when we had the pixhawk, we always used the IO pins to trigger. We never tested the fmu ones. Would that be possible for you? With the IO present, some things are set up differently, so it is hard to guess what goes wrong.

@birchera How are you using the IO pins for triggering? I wouldn't even know what setting that would be and the documentation on the dev guide only talks about AUX pins.

@LorenzMeier Do you as the unquestioned FMU expert have a shotgun idea about what might be going wrong?
To put it in a nutshell: Triggering via the camera trigger app only works if the pins used for triggering are included in the bitmask used by the FMU.
Is there something the FMU does which is not done in the camera trigger app which is needed to output pwm to pins?

Oh, I meant the AUX pins. Sorry, quite some time I worked with the pixhawk.

Closing in favour of https://github.com/PX4/Firmware/issues/6961.


Issue connecting to reader

Describe the bug
On a first install of the app(example-app), the app doesn't connect to the reader. It just errors out eventually with "Timed out waiting for connection token. But it does work if I reopen the app.
To Reproduce
Steps to reproduce the behavior:

run example-app
accept the permissions
wait for the sdk to initialize
click on discover readers
pick a reader
Wait till the error pops up.

Expected behavior
The reader should connect. It seems like the sdk/app doesn't attempt at getting a connection token at all so it can't connect to the reader.
Screenshots
If applicable, add screenshots to help explain your problem.
Stripe Terminal React Native SDK version

^0.0.1-beta.20`
this issue does not happen on ^0.0.1-beta.19`

Smartphone (please complete the following information):

Device: Pixel 6a or a Android Tablet
OS: Android
Browser [e.g. stock browser, safari]
Version 13/14

Additional context
Add any other context about the problem here.

I'm experiencing the same issue. Reader failing to connect after initially installing the app, then working after re-opening. Downgrading to 0.0.1-beta.19 fixes the issue, and it seems they are aware of it

Hi,
When we downgraded to 0.0.1-beta.19 , we saw a similar problem (I don't know whether it is related or not).

Build app
Fresh install of app (if app exists, delete it first)
Go to Tap to Pay button
Android - it shows a spinner at the Tap to Pay button; need to terminate app to use
iOS - similar, but it returns to the Tap to Pay button after a few minutes, after which it can be used

We are reluctant to release this version as new users will think the app is not working.
Any ideas?

beta.21 was just released and should address this issue. Can you give it a try and let us know?

I upgraded from 0.0.1-beta.20 to 0.0.1-beta.21 but have the same issue with in Android 14. However, after the first install, it works as expected.

I updated to 0.0.1-beta.21 and tested on iOS 18 and Android 11 and everything works as expected.

I updated to 0.0.1-beta.21 and tested on iOS 18 and Android 11 and everything works as expected.

@tzecheng are you still running into issues on the latest release?

@tzecheng are you still running into issues on the latest release?

Hi @nazli-stripe , will be testing in the next few days.

@tzecheng are you still running into issues on the latest release?

Hi @nazli-stripe , will be testing in the next few days.

Hi @nazli-stripe ,
Have upgraded to 0.0.1-beta.22.  Tested on iOS 17.6.1 and Android 12.  The problem reported earlier on Android spinner and iOS delay is no longer there.


'feature' not in batch.keys() in loss_superpixels_average

Hello, I preprocess with SAN and find that the script do not save xxx_lidarseg.npz, features=[] actually, and the collate function does not include 'feature' key to batch dict. How to generate features for superpoints?

Sorry, I may have accidentally deleted pretrain.dataloader_nuscenes_ov, I've added it back now. Please let me know if you encounter any issues.

Thanks! I have another question with task settings, does the model learn open-vocabulary semantics on pretraining stage or annotation-free stage? Is pretrain is only for backbone warmup?

It learns semantics in both stages, with the first stage focusing on scene understanding and the second stage on scene perception. So pre-training not only warmup parameters but also endows our models with scene understanding and transfer learning capabilities.

Great Work! Now I can start the pretrain stage and will reach you if meet further issues. Thanks a lot.


Upload skitt's DevConf 2021 talk to SubM Youtube

Upload @skitt's outstanding, demo-heavy Submariner talk to Submariner's Youtube. Link to the Other Resources website section.

Please wait until the talk has been presented at DevConf, I wanted to premiere it there.

Please wait until the talk has been presented at DevConf, I wanted to premiere it there.

Ah I didn't realize DevConf hadn't happened yet. Right, makes sense. 👍

Ah I didn't realize DevConf hadn't happened yet. Right, makes sense. 👍

Once that’s done, I will upload a non-DevConf-specific edit of the video to our YouTube channel.

DevConf is done, so this is unblocked I think (of course @skitt cycles also pending).
If you make a version without a DevConf intro, maybe we can also use that for Red Hat Summit (https://github.com/submariner-io/submariner/issues/1104)?

Once that’s done, I will upload a non-DevConf-specific edit of the video to our YouTube channel.

DevConf is done, so this is unblocked I think (of course @skitt cycles also pending).
If you make a version without a DevConf intro, maybe we can also use that for Red Hat Summit (submariner-io/submariner#1104)?

Yup, when I find some tuits I’ll prepare a version with Submariner branding only for the channel, and another for RHS.

FWIW, here is the YouTube link for the DevConf talk: https://youtu.be/-HE9iq34Zj8

I addressed this in this PR https://github.com/submariner-io/submariner-website/pull/502


Pr docs component

mhevery/qwik#2 contains some suggested typo fixes

@jimt Thank you for your improvments. They have been integrated.


Bump env images for automated tests

Problem
Currently https://github.com/hashgraph/hedera-smart-contracts/blob/main/.github/workflows/test-workflow.yml#L10 has a set of outdated images versions for consensus and mirror node images
Solution
Update the version to ensure tests are running again the most recent version.
Run tests against previewnet and testnet also
Alternatives
No response

Update

RELAY_IMAGE_TAG: 0.27.1
NETWORK_NODE_IMAGE_TAG: 0.40.0-alpha.1
HAVEGED_IMAGE_TAG: 0.40.0-alpha.1
MIRROR_IMAGE_TAG: 0.83.0

@Nana-EC I updated the image tags as you provided but it seems that all the CI automated tests kept on failing at the Start the local node job.
After a while of performing some manual CI testing on my forked repo, I figured that if the image tags specified under the workflow/test-workflow.yml#L10 do not match with the corresponding hedera local node's docker images, the job is unable to start hedera local node, resulting in the failure of the tests.
Here are the docker image tags hedera local node uses,
minio/minio                                          latest       57da0b94503d   6 days ago      292MB
postgres                                             14-alpine    cb57a91a2ecc   4 weeks ago     241MB
ghcr.io/hashgraph/hedera-json-rpc-relay              0.23.3       6828ccbcb7d6   2 months ago    888MB
gcr.io/hedera-registry/main-network-node             0.38.0       c7e52dede5e9   2 months ago    625MB
gcr.io/hedera-registry/network-node-haveged          0.38.0       47ed4499ecf2   2 months ago    66.2MB
gcr.io/mirrornode/hedera-mirror-rest                 0.81.0-rc1   8c003437adb9   2 months ago    325MB
gcr.io/mirrornode/hedera-mirror-grpc                 0.81.0-rc1   7bb6dd5b991f   2 months ago    368MB
gcr.io/mirrornode/hedera-mirror-web3                 0.81.0-rc1   6a287904da8e   2 months ago    377MB
gcr.io/mirrornode/hedera-mirror-importer             0.81.0-rc1   285ab3adbc9b   2 months ago    407MB
gcr.io/mirrornode/hedera-mirror-monitor              0.81.0-rc1   0eae14804546   2 months ago    342MB
gcr.io/hedera-registry/hedera-mirror-node-explorer   0.2.0        55db0133fdfa   4 months ago    155MB
grafana/grafana                                      8.5.16       80539339ec31   5 months ago    312MB
prom/prometheus                                      v2.41.0      5b45069f212c   6 months ago    225MB
gcr.io/hedera-registry/uploader-mirror               0.7.0        9b74704c84cb   11 months ago   209MB
envoyproxy/envoy                                     v1.22.0      f4559f8bf83b   15 months ago   118MB

They still use<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>Now this suggests that we should open a new issue on the hedera local node repo to have them upgrade the image tags before we can proceed further on this issue.
Here is the CI tests on my forked repo for the reference: https://github.com/quiet-node/hedera-smart-contracts/actions/runs/5583422083/jobs/10203717190#step:6:16073


Managed Node Groups with Launch Template using Spot Instances: Taints

I have issues
I'm submitting a...

[ ] bug report
[ ] feature request
[x] support request - read the FAQ first!
[ ] kudos, thank you, warm fuzzy

What is the current behavior?
Creating a Managed Node Group does allow using Spot Instances and setting additional k8s labels on the node, but doesn't seem to allow specifying taints using kubelet_extra_args.
If this is a bug, how to reproduce? Please include a code sample if relevant.
working from the example: https://github.com/terraform-aws-modules/terraform-aws-eks/tree/master/examples/launch_templates_with_managed_node_groups
Adding kubelet_extra_args to the template_file
data "template_file" "nginx" {
  template = file("${path.module}/templates/userdata.sh.tpl")

  vars = {
    cluster_name        = local.cluster_name
    endpoint            = module.eks.cluster_endpoint
    cluster_auth_base64 = module.eks.cluster_certificate_authority_data

    bootstrap_extra_args = ""
    kubelet_extra_args   = "--node-labels=node.kubernetes.io/lifecycle=spot,group=nginx,role=ingress-controllers --register-with-taints=dedicated=ingress-controllers:NoSchedule"
  }
}

resource "aws_launch_template" "nginx" {
  name_prefix             = "eks-nginx-"
  description            = "NGINX Launch-Template"
  update_default_version = true

  block_device_mappings {
    device_name = "/dev/xvda"

    ebs {
      volume_size           = 10
      volume_type           = "gp2"
      delete_on_termination = true
    }
  }

  key_name = "cabrinha-mng-test"

  monitoring {
    enabled = true
  }

  network_interfaces {
    associate_public_ip_address = false
    delete_on_termination       = true
    security_groups             = [
      module.eks.cluster_primary_security_group_id,
      module.eks.cluster_security_group_id,
      module.eks.worker_security_group_id,
    ]
  }

  user_data = base64encode(
    data.template_file.nginx.rendered,
  )

  # Supplying custom tags to EKS instances is another use-case for LaunchTemplates
  tag_specifications {
    resource_type = "instance"

    tags = {
      Name = "${local.cluster_name}-nginx"
    }
  }

  # Supplying custom tags to EKS instances root volumes is another use-case for LaunchTemplates. (doesnt add tags to dynamically provisioned volumes via PVC tho)
  tag_specifications {
    resource_type = "volume"

    tags = {
      Name = "${local.cluster_name}-nginx"
    }
  }

  # Tag the LT itself
  tags = {
    Name = "${local.cluster_name}-nginx"
  }

  lifecycle {
    create_before_destroy = true
  }
}

module "eks" {
 ...

  node_groups = {
    nginx = {
      capacity_type    = "SPOT"
      desired_capacity = 3
      max_capacity     = 3
      min_capacity     = 3

      launch_template_id      = aws_launch_template.nginx.id
      launch_template_version = aws_launch_template.nginx.default_version

      instance_types = [
        "c3.2xlarge",
        "c4.xlarge",
        "c4.2xlarge",
        "c5.2xlarge",
        "c5.xlarge",
        "c5.4xlarge",
        "m3.xlarge",
        "m3.2xlarge",
        "m4.2xlarge",
        "m5.4xlarge",
        "m5a.xlarge",
        "m5d.4xlarge",
        "r3.large",
        "r4.2xlarge",
        "r5.xlarge",
        "r5.2xlarge",
        "r5.4xlarge",
        "t3a.xlarge",
        "t3a.2xlarge",
        "t3.2xlarge",
      ]
    }
  }
}

This results in NodeCreationFailure with Instances failed to join the kubernetes cluster in the AWS console.
What's the expected behavior?
Is there any way to using managed node groups, with spot instances, with taints?
Are you able to fix this problem and submit a PR? Link here if you have already.
Environment details

Affected module version:
OS: macOS 10.15.7
Terraform version: 0.12.30

Any other relevant info
https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1211

should be possibk with https://github.com/terraform-aws-modules/terraform-aws-eks/pull/1138

should be possible with #1138

Would you mind adding an example that uses managed node groups, spot instances, labels and taints all together? It'd be super helpful.

@ArchiFleKs do I need to use a launch template in order to apply taints to managed node groups instances?
It seems I can't override this parameter on a per-node-group basis: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/modules/node_groups/locals.tf#L16
Other parameters are being overridden successfully, like "root_volume_size" works fine.
    prometheus = {
      desired_capacity   = var.prometheus_mng_desired_capacity
      max_capacity       = var.prometheus_mng_max_capacity
      min_capacity       = var.prometheus_mng_min_capacity
      instance_types     = local.spot_instance_types
      capacity_type      = var.prometheus_mng_capacity_type
      root_volume_type   = var.prometheus_mng_root_volume_type
      root_volume_size   = var.prometheus_mng_root_volume_size
      kubelet_extra_args = "--register-with-taints=dedicated=prometheus:NoSchedule"
      additional_tags    = var.prometheus_mng_additional_tags
      k8s_labels         = {
        "role" = "worker"
        "group" = "prometheus"
      }
    }

@cabrinha what do you mean on a per node group basis ?
Your config seems right yes. What is happening ?
Pre user data is node working because user data is merge with official AMI. I think there is discussion about this in the PR comment.

@cabrinha what do you mean on a per node group basis ?

node_groups = {
  prometheus = {
    kubelet_extra_args = "--register-with-taints=dedicated=prometheus:NoSchedule"
  }
  nginx = {
    kubelet_extra_args = "--register-with-taints=dedicated=nginx:NoSchedule"
  }
}

Your config seems right yes. What is happening ?
--node-labels is the only option rendering into --kubelet-extra-args. I don't see --register-with-taints in there.

Pre user data is node working because user data is merge with official AMI. I think there is discussion about this in the PR comment.

This explains why it's not working: https://github.com/terraform-aws-modules/terraform-aws-eks/pull/1138#issuecomment-823531632

I just tested with master and the following configuration:
  node_groups = {
    "default-${local.aws_region}a" = {
      ami_type = "AL2_ARM_64"
      desired_capacity = 1
      max_capacity     = 3
      min_capacity     = 1
      instance_types    = ["t4g.large"]
      subnets          = [dependency.vpc.outputs.private_subnets[0]]
      disk_size        = 20
    }

    "default-${local.aws_region}b" = {
      ami_type = "AL2_ARM_64"
      desired_capacity = 1
      max_capacity     = 3
      min_capacity     = 1
      instance_types    = ["t4g.large"]
      subnets          = [dependency.vpc.outputs.private_subnets[1]]
      disk_size        = 20
    }

    "default-${local.aws_region}c" = {
      ami_type = "AL2_ARM_64"
      create_launch_template        = true
      desired_capacity = 1
      max_capacity     = 3
      min_capacity     = 1
      instance_types    = ["t4g.large"]
      subnets          = [dependency.vpc.outputs.private_subnets[2]]
      kubelet_extra_args = "--node-labels=role=private --register-with-taints=dedicated=private:NoSchedule"
      disk_size        = 20
    }
  }

It is working as expected


Const correctness in LittlevGL

I noted today, when using const appropriately in my own code that LittlevGL wasn't very 'const correct'.
https://isocpp.org/wiki/faq/const-correctness
It would be good to start using const as appropriate on new code and updating existing code to use it.
In embedded systems using const can really help the compiler optimize the code in addition to the other readability and developer friendly gains it provides.

for instance:
v_obj_t * lv_obj_create(lv_obj_t * parent, lv_obj_t *copy);
should probably be
v_obj_t * lv_obj_create(lv_obj_t * parent, const lv_obj_t * const copy);
that is, lv_obl_create never changes the pointer to copy and never modifies that structure pointed to by copy

Hi,
I tried to consciously place the const tags but I forget it in create functions.
However, I never thought that lv_obj_t * const copy or const lv_obj_t * const copy might have relevance as the key thing is the data pointed by the pointer won't changed (indicated byconst lv_obj_t * copy).

Hi,

Hi,
IMHO Hydra has a point as a matter of principle.
In the first place, it would make for easier understanding of the behaviour of the function,
Secondly, it would allow for constant declarations of objects (in flash for example, even though that may not be currently supported) to be used as templates for copying instead of needing to obtain them from read/write memory.

Hi,
To store data in flash only const lv_obj_t * copy is required to show data the pointed data is constant. I totally agree with it, this approach should be followed everywhere.
I have concerns in regard to  const lv_obj_t * const copy (second const). Can you mention some cases where it is useful? Or do you think it also improves "readability"?

Hi,
I agree, the "second" const is largely meaningless when a pointer is passed as a function parameter.

Great! @hydra, what do you think?
If you find forgotten consts in the code, please mention them here.

for me, any improvement in const usage is welcomed.  the sooner you apply it the easier it will be to maintain in the future for the library and the users of it.

Hi,
void lv_obj_align(lv_obj_t * obj,lv_obj_t * base, lv_align_t align, lv_coord_t x_mod, lv_coord_t y_mod);

Note the missing space after first comma.
All the lv_x_get_x functions which take lv_obj_t * arguments ?
I may be wrong, but it seems to me that correcting all instances may not be a trivial matter.

Hi,
You are right near all lv_x_get_x functions can be updated! Thank you!
lv_obj_align is also correct!

Hi,
I added consts to all:

lv_.._create()
lv_..._get_...()
and other places (e.g. lv_obj_align)

Probably still you will find some places where const can be added but I think we covered the bulk of it.
Hence I close this issue!
Thank you for the contribution!


Update to handle PR merge for better spec/test compliance on py-ipfs-api repo

With recent updates/fixes to the py-ipfs-api repo, a list is no longer returned.  Without this PR, if a user chooses to install the latest py-ipfs-api repo, a traceback will result within the mediachain-client during ingest as follows:
[....]
  File "/Users/.../site-packages/mediachain/writer/writer.py", line 83, in write_dataset
    raw, local_assets)
  File "/Users/.../site-packages/mediachain/writer/writer.py", line 97, in submit_translator_output
    raw_ref = self.store_raw(raw_content)
  File "/Users/.../site-packages/mediachain/writer/writer.py", line 168, in store_raw
    ref = store.put(raw_content)
  File "/Users/.../site-packages/mediachain/datastore/ipfs.py", line 59, in put
    header = result.pop(0)
KeyError: 0

I've attempted to maintain backwards compatibility with the old behavior (py-ipfs-api <= 0.2.3) and still work with the new and improved py-ipfs-api repo behavior.

Awesome, thanks @joshisa 😄


feat: rx_offset to use with upconverters

Adds rx_offset setting which allows to extend the receive range of the k5 with the use of external upconverter.
This functionality is more flexible then currently available features in different firmwares, as it allow to set frequency of the upconverter in kHz which allows better adjustment for possible frequency deviation introduced by the upconverter (which is often the case) and thus supports any upconverter.
@egzumer please let me know what you think. :)

Tested myself and works really well. Channels are saved with proper frequency. Other frequency band switching works as before.
TODO: Fix to allow lower frequencies in spectrum as well (uses different set of constraints).

Closing this one, as this feature seems to be directed towards specific usage and not a lot of people will use it.


Document functions imported from dependencies

The docs need a page listing all functions imported from lodash & fecha (etc), and the top-level names that they reside within.
Ideally that could be generated by build tooling...

Dependencies are clearly listed in package.json

I didn't mean "list dependencies".
I meant list all the specific functions bundled into the release, e.g. _.isEmpty().
And list them on a new docs page.


ast: avoid intermediate wires/assigns when lowering to AST_MEMINIT

Before this commit, every initial assignment to a memory generated
two wires and four assigns in a process. For unknown reasons (I did
not investigate), large amounts of assigns cause quadratic slowdown
later in the AST frontend, in processAst/removeSignalFromCaseTree.
As a consequence, common and reasonable Verilog code, such as:
reg [`WIDTH:0] mem [0:`DEPTH];
integer i; initial for (i = 0; i <= `DEPTH; i++) mem[i] = 0;

took extremely long time to be processed; around 80 s for a 8-wide,
8192-deep memory.
After this commit, initial assignments where address and/or data are
constant (after generate) do not incur the cost of intermediate
wires; expressions like mem[i+1]=i^(i<<1) are considered constant.
This results in speedups of orders of magnitude for common memory
sizes; it now takes merely 0.4 s to process a 8-wide, 8192-deep
memory, and only 5.8 s to process a 8-wide, 131072-deep one.
As a bonus, this change also results in nontrivial speedups later
in the synthesis pipeline, since pass sequencing issues meant that
all of these intermediate wires were subject to transformations such
as width reduction, even though they existed solely to be constant
folded away in memory_collect.

I fixed the failing tests, and I'm reasonably confident this change is correct now.

Thanks!


Fix Unit system

Describe the bug
I'm having a lot of bugs dealing with units. In some place I need to use pixels as units, while in others, I don't.

try creating a universal unit that you can convert everything to and from. like rem in css will be converted too and from pixels based on screen size. take a look at mozilla docs for stuff like rem to get some ideas

There is a universal-unit-like-thingy that is 1u = 10px (u as in unit), which is being used in the Camera::ScreenToWorldPos ()and Camera::WorldToScreenPos() methods. I realized that just the camera doesn't use that unit system properly.

what seems to be the issue with the camera in particular? it shouldnt make a difference if you convert it back and forth properly

@Sable-20 Well that is the issue. My brain is running on like -100IQ so I'm sure I messed up the math somewhere.

Fixed


Update bundled copy of compat-5.3, or maybe stop bundling it

Thanks you very much.

Thank you a lot.


Feature: Toggle

I didn't see any way to toggle Neovim mode on and off.  That's important to me since some operations don't translate easily to Windows, like clipboard copy and paste, select all, etc.

In meantime you can use insert mode, all neovim keybindings are disabled except <C-r> and <C-a> while in insert mode.
I'm assuming you're using wsl option, yeah? Clipboard is actually easy fixable for wsl interop, i'll look sometime soon into it.

Hey, does ctrl-c work to copy in insert mode for you? In my case it exits insert mode and does not copy. Tried to turn of "Use Ctrl Keys For Insert Mode" but it wouldnt help.
Im on windows to and not using wsl.
Any suggestions?

@KuenstlicheIntelligenz
add to your keybindings.json
			{
				"command": "-vscode-neovim.escape",
				"key": "ctrl+c",
			}

this will unbind ctrl+c from the escape key
Also ctrl+insert / shift+insert are working for copy & paste

I would like to see this too

Why close this? This is a useful feature to be able to toggle between vim keybinds and standard vsCode keybinds.

Is there any new? I think this is a very useful feature to be implemented. In the Vim extension it's possible to do that by typing ctrl+shift+p followed by toggle vim mode.

I find I myself mostly using actual vim more because switching key modes back and forth all the time is cumbersome and I'm too old to learn vscode key bindings or to not constantly try to use vim bindings whenever I type in an editor. I hope this does happen though, any improvements that reduce the number of times that I have to switch keybindings is a good thing.

I'd like this feature as well. As a vim beginner, it's comforting to quickly go back to VSCode mode for a few actions you are uncomfortable with or haven't learned yet.

I'll comment to add my support for this feature

https://github.com/vscode-neovim/vscode-neovim/pull/1033


📖 Food for thought regarding the burred sidebar advice

Prior to this project supporting the blurred sidebar, I had already implemented it in my own macos desktop app.  Like you I started with the suggestion from this comment.
However, the source code that is in that comment really isn't the right way to do it. Mucking around with contentView and its position in the view hierarchy is not the right way to do it.
I added a comment to that issue that uses a more traditional AppKit-way of doing things.
Now, I know that this project can't really do much in terms of providing Swift code... however, I do feel like it would be worth considering what advice is shared for this code. Note that I'm not saying my code is "the right way" or "the only way"... just that the current suggestion isn't really idiomatic Swift code. Just some food for thought.

@edwardaux feel free to open a PR with this documentation update.


Splunk HEC config

:rocket: deployment of nhsuk/gp-redirect succeeded (http://gp-redirect-pr-34.dev.beta.nhschoices.net)

Done in #33


Image Circle

Icon Request

Icon name: Image Circle
Tags of this icon:
Use case: Image uploading
Screenshots of similar icons:

Can you add more details to this issue? I still can't figure out what you need based on the information above.

Here is an example: https://api.iconify.design/majesticons:image-circle.svg


[CS2103T-T09-2] PetCode

Target User:
Coordinators of pet sale who need a contact list of both clients, deliverers and suppliers. These coordinators run their business online and get used to typing. Such people need to maintain a contact list of clients, deliverers, and suppliers.
Value Proposition:
Our app will record the needs of clients, current unsold pets from suppliers, and deliverers’ details. It will automatically match the best-fit pet to a client’s needs.

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (d343154) compared to base (77a32bf).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #105   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add Libre FM integration

There are two ways to submit scrobbling:

Deprecated Last.fm Submissions Protocol v1.2.1.
Modern Scrobbling 2.0 REST API (changes).

Nuvola currently uses Scrobbling 2.0 API for Last.fm. It used to work also for Libre.fm, but it stopped working around 2014-06-28 and was not included in Nuvola 3 for that reason.
As of 2018-03-04, Scrobbling 2.0 API still does not work for Libre.fm, so it is necessary to use the deprecated API :-1:

WIP: https://github.com/tiliado/nuvolaruntime/tree/librefm
Submission server: http://turtle.libre.fm/
Example: rb_audioscrobbler_nowplaying, rb_audioscrobbler_submit_queue
Libre.fm Test profile

Original ticket
Nuvola Player 2 provides Libre FM integration (see screenshot below). It would be great to have this feature in Nuvola Player 3 too.
Two users have voted for this feature on Trello board:

Laurenţiu Lozan (laureniulozan)
Mark Rich (markrich1)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Ticket updated with current status.

Released with Nuvola 4.16.0, more info: Nuvola 4.16 Brings Libre.FM Scrobbling, Ivoox Service, and more


What is more useful Assert-Throw behavior?

Assert throw will pass if any exception is thrown, but often we need to refine what exception we expected and what were it's properties. Which parameter is more useful to be provided by position? The type or the message?
# filter on message
{ throw [InvalidOperationException]"This is wrong!" } | Assert-Throw '*wrong*'

# filter on type
{ throw [InvalidOperationException]"This is wrong!" } | Assert-Throw ([InvalidOperationException])

I'd say string first, but no strong opinion.

I'd like to see both behaviors possible. You could filter on type primarily as this is similar to the pattern we use with try/catch. A second parameter should be available for filtering by message and further parameters for other exception properties.

In the end I did not make any of the paramater positional.
@mattmcnabb I just released it in 0.7.0. Please help me test it.


Roll engine 9bfa4f53cdbe..739b2dd4b271 (3 commits)

git@github.com:flutter/engine.git/compare/9bfa4f53cdbe...739b2dd4b271
git log 9bfa4f53cdbe..739b2dd4b271 --no-merges --oneline
2019-08-07<EMAIL_ADDRESS>Roll fuchsia/sdk/core/linux-amd64 from 9sR9P... to v5rSi... (flutter/engine#10678)
2019-08-07<EMAIL_ADDRESS>Roll fuchsia/sdk/core/mac-amd64 from eB-F0... to 14j-v... (flutter/engine#10676)
2019-08-07<EMAIL_ADDRESS>Roll src/third_party/skia ab961e9db1dd..c13305320fd1 (2 commits) (flutter/engine#10677)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (jimgraham@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


Docs - Freestyle, custom, etc.?

How do we want to document these modules? The design system and Ember addon(s) should all be documented in a similar fashion; in the past we've used ember-freestyle, but we also have a history of building "custom" apps that show off the functionality. This should probably be decided before we get too far into this project so that we can add "building documentation" as one of the requirements for a PR.

We're going to use ember-freestyle to create documentation similar to the existing knoxville-utilities-board/ember-nrg-ui project.


Look for fetchPriority instead of importance

In https://github.com/sitespeedio/coach-core/blob/aa2654879533af3ec0381acaf9e7f0b1bfe84c30/lib/dom/performance/largestContentfulPaint.js#L44C1-L49 The Coach will take 5 points if the LCP element is an img and it misses the importance="high" attribute.
According to https://web.dev/fetch-priority/#history, this attribute is now fetchPriority:

Fetch Priority was first experimented with in Chrome as an origin trial in 2018 and then again in 2021 using the importance attribute. At that time it was known as Priority Hints. The interface has since changed to fetchpriority for HTML and priority for JavaScript's Fetch API as part of the web standards process. To reduce confusion we now refer to this API as Fetch Priority.

I've tried adding both attributes to get a perfect score there, but I think doesn't work in recent versions of Chrome as it already moved to fetchPriority (testing manually in the JS console, markup for lcp_image is <img importance="high" fetchpriority="high" src=...):
lcp_image.importance
undefined
lcp_image.fetchPriority
'high'

Thanks I'll have look before the next release.


Update afx-extension-module-structure_1.cpp - inaccurate initialisation of AFX_EXTENSION_MODULE structure

The first two parameters of the structure AFX_EXTENSION_MODULE are BOOL and HMODULE. So initialisation with = { NULL, NULL } is inaccurate: first NULL is FALSE (or 0 due to BOOL is defined as int). In fact this expression cannot be transformed to modern C++ equivalent = { nullptr, nullptr }.
struct AFX_EXTENSION_MODULE
{
BOOL bInitialized;
HMODULE hModule;
HMODULE hResource;
CRuntimeClass* pFirstSharedClass;
COleObjectFactory* pFirstSharedFactory;
};

LGTM. Thanks!


[1.16] extreme reactors ores not added to ore laser recipes

DO NOT REPORT AN ISSUE IF YOU HAVEN'T TESTED THE ISSUE WITH THE LATEST VERSION IN CURSEFORGE
Industrial Foregoing Version:
1.16.5-<IP_ADDRESS>-fbef27c
Titanium Version:
1.16.5-<IP_ADDRESS>
Crashlog If Applicable (Upload to pastebin/gist):
https://pastebin.com/jAWbTtwV

Same case with Uraninite from Powah. (<IP_ADDRESS>)

did you successfully add Extreme Reactor Recipes to the drill yet?

in case a dev fins this and wants to know the issue
the serializer returns null

The integration is there since the start, the ore needs to have the item tag too for it to work


Annotations event listener

Is there a way to add an event listener like "onchange" to the annotations when accessing them using let annotationData = await page.getAnnotations();? I have been attempting to do so, but haven't been successful.

It's quite difficult to know exactly what you're asking about, but you might be able to achieve what you need by adding a onSetModified callback-function to the annotationStorage-instance since that's invoked every time form-data changes; see https://github.com/mozilla/pdf.js/blob/73d650af3e88037c03f89aecdadf4824ac99f2a7/src/display/annotation_storage.js#L35-L39

Unfortunately it's very difficult to help here since it seems that you've focused more on a particular solution, rather than describing your actual "problem" in sufficient detail.
When opening an issue, please provide all of the information requested in https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md including a clear and concise description of the problem.

I am sorry yo didnt understand wath i am asking, i will say it  different way,
I am sorry for any confusion. Let me rephrase it for clarity.
I have a PDF file that contains input fields. After some research, I discovered that I can access these input fields using the page.getAnnotations() function. This function provides an object that contains all the input fields, including their types and content.
I have successfully implemented a feature that allows users to interact with the PDF by displaying the input annotations, enabling them to write on the fields, as you can see next code.
`async setupAnnotationss(page, viewport) {
let annotationData = await page.getAnnotations();
  const pdf_canvas = document.getElementById('pdf-canvas');
  // Canvas offset
  const canvas_offset = pdf_canvas.getBoundingClientRect();
  // Canvas height
  const canvas_height = pdf_canvas.height;
  // Canvas width
  const canvas_width = pdf_canvas.width;
  // CSS for annotation layer
  const annotationLayer = document.getElementById('annotation-layer');
  annotationLayer.style.left = canvas_offset.left + 'px';
  annotationLayer.style.top = canvas_offset.top + 'px';
  annotationLayer.style.height = canvas_height + 'px';
  annotationLayer.style.width = canvas_width + 'px';

  // //Renderizar las nuevas anotaciones
  pdfjsLib.AnnotationLayer.render({
    viewport: viewport.clone({ dontFlip: true }),
    div: annotationLayer,
    annotations: annotationData,
    page: page,
    event: onclick,
  });
},`

However, I'm currently working on adding an event listener to each annotation. The purpose of this event listener is to identify which values are being changed by the user. Furthermore, I aim to provide the users with additional options based on these changes, enhancing their experience with the PDF.


Feat/close native snackbar 🚀

Description 📄

Add: close button on snackbar
Platforms 📲

[ ] Web
[x] Mobile

Type of change 🔍

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How Has This Been Tested? 🧪

[x] Unit Test
[x] Snapshot Test

Checklist: 🔍

[x] My code follows the contribution guide of this project Contributing Guide
[x] Layout matches design prototype: FIGMA
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Screenshots 📸

https://user-images.githubusercontent.com/39800209/172072157-8fb7a45f-d2e5-481d-99b1-6f09e71a7ac9.mov

Before
After

success
informative
attention

@MasterTeus The fact that the close button was not implemented on the mobile component is because it is not expected to exist on the mobile version.

And about the hideIcon @luispiresgympass, the mobile has this behavior when the icon prop is not passed, maybe it is interesting to check if the hideIcon prop is used in the web context and which are the cases that it is necessary. Maybe it makes sense to remove the hideIcon to have that same behavior of the Mobile, once it seems to do not have any Snackbar behavior that uses the hideIcon prop.

I talked to Yoga design asking about having the close button close behavior for the mobile snackbar, but at the moment we're not going to have this behavior.
But I would like to thank you for your contribution to Yoga @MasterTeus. If the need arises to have the close behavior with the close button, we will use your PR ❤


Bump 0.5.0-rc1

Signed-off-by: Nana-EC<EMAIL_ADDRESS>Description:
Bump 0.5.0-rc1
Related issue(s):
Fixes #
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Codecov Report

Merging #396 (740e88a) into release/0.5 (c91245f) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           release/0.5     #396   +/-   ##
============================================
  Coverage        73.55%   73.55%
============================================
  Files               10       10
  Lines              832      832
  Branches           136      136
============================================
  Hits               612      612
  Misses             172      172
  Partials            48       48

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c91245f...740e88a. Read the comment docs.


chore(main): release audit 1.35.1

:robot: I have created a release beep boop
1.35.1 (2023-04-07)
Bug Fixes

pnpm graph gen issue (de15efa)
support pnpm lockfile v6 (eb88694)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/sandworm-hq/sandworm-audit/releases/tag/audit-v1.35.1 :sunflower:


Added Scientific Calculator

Description
Hello Sir,
I have added my Scientific Calculator PR in this repo. Please take a look at my PR.
Related Issue

Closes #4

Type of Change
Please check the type of change that applies to your PR:

[ ]  Bug Fix
[ ] New Feature
[ ] Enhancement (improvements, refactoring, etc.)
[ ] Documentation Update
[X] Other (please specify): New Project

Checklist
Before submitting your pull request, please ensure you've completed the following:

[X] I have read the CONTRIBUTING.md document and followed the contribution guidelines.
[X] My code follows the project's coding standards.
[X] I have added or updated the necessary documentation (if applicable).
[X] My changes do not introduce any new linting or test errors.
[X] All new and existing tests have passed.
[X] I have reviewed my code to ensure its quality.

Screenshots (if applicable)

Additional Information
Please review my PR under APERTRE
Author's Note

@debarshee2004 I have added my PR to this repo .Please take a review & if possible pls Merge it under APERTRE.

Well done @apu52 . Best of luck and happy coding.

@debarshee2004 Thank you for merging the PR. Can you please also add the labels of APERTRE in this PR


implement access interface of ProjectApi

I have write two simple test and remove the comment.

@keylorsdu: Thanks for the update. It looks like a merge went wrong. I suggest you to squash all commits into one commit and check the diff that there are no unnecessary changes. Then you can force-push to your branch in order to update this pull request.


It seems that the text rendering engine has been changed in version 1.66

Usually, I set the value of editor.fontweight as bold to activate the fake bold function of text rendering engine. It works well in version 1.65. However, the behavior of editor has changed in version 1.66. Two images are listed below to demonstrate my problem intuitively.
The first image corresponding to version 1.65.

The second image corresponding to version 1.66.

It seems that the text rendering engine of version 1.65 tend to stretch the width rather than increase the font weight like version 1.66. I prefer the former. Besides, I need the updates in version 1.66 such as Local History . Is it possible to select the old text rendering engine in version 1.66.

Does the issue repro with https://vscode.dev/ under similar font settings ?

Does the issue repro with https://vscode.dev/ under similar font settings ?
I try reproducing the issue with https://vscode.dev/, however I can't find the method to switch the version of the web vscode. Would you mind tell me how to reset the version to 1.65 on the web vscode? With the same font settings, it looks like below. I can't understand the tag needs version info you have added, because I have recorded the version information both in issue title and initial description.

Thanks for the detailed repro steps, it helps! merging to https://github.com/microsoft/vscode/issues/146399. Please subscribe to that issue for updates.


force germline workflows to produce genotyped vcf

This PR removes the emit_reference_confidence input for germline workflows, defaulting it to NONE. If the input value was not set to NONE the output vcf would not be a genotyped VCF but a genome VCF(gVCF). This causes issues with downstream steps.
@dufeiyu, should I also change the pipelines/aml_trio_cle.cwl and pipelines/amle_trio_cle_gathered.cwl workflows?

We have the pipelines/germline_exome_gvcf.cwl and pipelines/germline_wgs_gvcf.cwl workflows. They can produce the gvcf files. They run the alignment workflow and produce gvcf files. They do not make a genotyped vcf.
Currently, we do not have a workflow that can produce gvcf files and a final genotyped vcf.


Image embeddings extraction example

Hi all 👋🏻! Is there any simple embedding extraction example? I'm interested in something super simple and basic.

Load a single image from the local path.
Load model.
Run the model to extract embeddings.

I would be very grateful for any help. Kind regards.

#2

Closing and keeping track in #53.


Added statistics calculator for Annotation Tools

Context
Refactored the stats calculation code for Annotation Tools and added a way to create and initialize new calculator with custom statistics.

Changes

Added new class BasicStatsCalculator, which has the default stats such as max, mean , stdDev..  used by the annotation tools instead of using callbacks.
Made RectangleROITool statistics calculation match the other tools. (Using pointInShapeCallback instead of 3 'for')

Testing
stackAnnotationTools example.

Checklist
PR

[] My Pull Request title is descriptive, accurate and follows the
semantic-release format and guidelines.

Code

[] My code has been well-documented (function documentation, inline comments,
etc.)

[] I have run the yarn build:update-api to update the API documentation, and have
committed the changes to this PR. (Read more here https://www.cornerstonejs.org/docs/contribute/update-api)

Public Documentation Updates

[] The documentation page has been updated as necessary for any public API
additions or removals.

Tested Environment

[] "OS:
[] "Node version:
[] "Browser:

@sedghi Hey, I've been working on annotation tools and I added the feature to custom the text shown by the tool. So we can add custom text and also custom statistics calculator by the tool configuration.
So now we can set our custom text and calculator when adding the tool into the toolgroup with it's configuration or also by setToolConfiguration method.
I've created a new example aswell (stackAnnotationToolsSpecificConfiguration)


Report not adding to the PR console

Hi
We have upgraded to the latest version 1.6.1
But this is not adding the aggregated value to the pr.
it is just saying below even thought there are some coverage changes in the pr.

Using Java17
Any help would be appreciated.
Thanks in advance

It is showing this,
Run<EMAIL_ADDRESS>Event is pull_request
base sha: aceb8b21d602b8bcf2d5d86700ca8583dab633a0
head sha: a5f79c717702d4b7f7b91990bcafa126583bf703
and not showing any coverage info on the pr

Team,
Any update on this?

We are working on fixing some issue associated with this, but I am a bit confused on the scenario above.

Is this a multi module project?
Is the JaCoCo report available in the mentioned path?
If it is present, could you check the .xml to see if it's a valid report? We have an issue where if the <report /> is empty, then we show NaN as the coverage.
You could try running the action with debug: true to get more information.


docs: updates contributor nickname

Updates the old Even Stensberg's nickname "ev1stensberg" to "evenstensberg"

Thanks!


[Bug] New Export PR WIll skip Export-DbaLogin tests

it has regex and i wouldnt have time to fix. can someone else please look once the PR has come in? it's not caused by the changes in this PR, the entire integration tests were commented out from an earlier PR.

@sqllensman or @joshcorr  - same as before 😅  can either of you you take a look at this? thanks so much

I will grab this one.


[graphiql] visiblePlugin errors @graphiql/plugin-explorer v0.3.0

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When upgrading from v0.2.0 to v0.3.0 of @graphiql/plugin-explorer when using visiblePlugin={explorer} an error is encountered on initial render:
Cannot read properties of null (reading 'getValue')
Presumably this is because the state has not been set yet?
Expected Behavior
The explorer plugin is loaded as the visible plugin on initial load
Steps To Reproduce
Minimal replication: https://codesandbox.io/s/heuristic-rubin-cyny3d?file=/src/App.tsx

Load the replication and see the error
Comment out visiblePlugin={explorer} and confirm the error is resolved
Click the explore icon in the menu and verify the explore plugin is loaded

Environment
No response
Anything else?
No response

@benedfit thanks for reporting - close! this has to do with the presence of the editor instance. patch incoming :)

@benedfit thanks to your codesandbox, i can confirm that<EMAIL_ADDRESS>fixes this bug!

@benedfit see:
https://codesandbox.io/s/wispy-field-y6gpvh?file=/src/App.tsx
also, be sure to instantiate the plugin outside the react component unless you need to, there are instructions in the changelog

noting for others in need of this patch - there was a bug with @changesets/cli and it was accidentally released as<EMAIL_ADDRESS>we will be deprecating this version, and hope to release this as<EMAIL_ADDRESS>as intended. we are going to patch changesets temporarily until they decide how to handle this case


Making sure HPX_WITH_ASYNC_MPI is reported properly

Fixes #5921

Thanks for fixing the issue :partying_face:
I tested your branch and it worked on my machine


Exposed some method and info through map model.

This PR exposes some internal through map model in order to avoid consuming them globally. Related to https://github.com/CartoDB/cartodb/issues/11846
cc @xavijam @alonsogarciapablo

Merging! 👏


Error: crypto.getRandomValues must be defined

https://github.com/paulmillr/noble-ed25519#usage

I have the same problem; the link above does not explain much. I am running it on Node 18.

@rdzidziguri which words, exactly, you don't understand from the link above?

For node.js <= 18 and React Native, additional polyfills are needed

@paulmillr, I scrolled down, and it is there, but it would be better if you put those right under the statement with explicit text for each ENV. There was confusion right after that statement, followed by the code I misinterpreted thinking it was the one for the earlier node.

@rdzidziguri do you think 2 is better than 1?


Environment Variables in Startup Scripts

I'm currently working on a project that requires that I use an environment variables in my CT template to determine which configuration to pull. I discovered that what is preventing this from working is the lack of these environment variables when CT is running as a daemon. (When ran manually it uses my running environment and pulls the variables just fine, just not as a daemon.)
My question is, would it be possible to add a parameter to the class/module for supplying the startup scripts with additional environment variables? This would be especially helpful as I would be able to supply this in hiera from facts and would simplify a lot of work on my end!
Also, if I sound wildly insane asking this, please feel free to enlighten me on how to accomplish what I am attempting to do. I'm not a seasoned linux vet and still have lots to learn. :)
Thanks!

I ended up using the same trick from my other issue (#54) to get something working, though this is somewhat clunky:
consul_template::extra_options: |
  '-template /path/to/my/template.ctmpl:/path/to/my/output.out'
  export FACT=%{::myfact}

It works (the daemon now sees the envvar), but it's not pretty so support for this would be highly appreciated! :) (If I have time even I will clone/edit/pr this change... )

Hi,
Thanks for in the insight into your use case - I'm pleased that you found a way to squeeze data in through extra_options as I'm currently not minded to incorporate support for env variables into the module since it'll mean updating all the different init scripts.
Always happy to receive a PR for such things, of course :) I'll close this for now.

I understand! I may be able to work on this and submit a PR for you. My concern would be my ability to test outside of the sysv and systemd templates but we'll see!
Thanks again!


Fix sometimes net.bridge.bridge-nf-call-iptables is disable

Fix sometimes net.bridge.bridge-nf-call-iptables is disable
if modinfo_br_netfilter.rc == 0
it will skip Enable bridge-nf-call tables

I've already got an identical PR: https://github.com/kubernetes-incubator/kubespray/pull/2067

@manics  ok

will merge with #2067


test: cover supported node versions with travis

I think this might be the best way to get full coverage in travis. @cclauss @joaocgreis

Sure.  We can work this.  A lot of this was done on https://github.com/refack/GYP

While you are in here, can you please change F72 on line 39 to F7 so that we add the __flake8 F70x tests to our scans?  I know that we do not have any F70x issues today but putting this in place would catch any new occurrences.

please change F72 on line 39 to F7
gibberish! but done

Do you understand why Node 6 fails?  Is it worth fixing?

yes, it will turn magically green when #1808 is merged


save function of standard lineplot should include the gene in its name

Currently only the last plot is saved, but ideally all of them are saved. Easy fix is to add the gene name in the loop of standard_lineplot creation in e.g. average_expression_per_cluster

Remains to be tested....


some related references for the write up

https://journals.sagepub.com/doi/10.1177/2158244020915900
https://www.mdpi.com/2411-5134/3/3/44/htm
seen here: https://twitter.com/brembs/status/1268520881170649089

Hase and Pearson 2020 has been cited in this commit https://github.com/mxochicale/the2020/commit/e61ef72795a97c7ec56598496737bf8f439a7591#diff-c6d83a61b46609bcd42889f3810278c6


refactor: 💡 move from master branch to main

PR Checklist
Please check if your PR fulfills the following requirements:

[ x ] The commit message follows our guidelines: CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ x ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ x ] Refactoring (no functional changes, no api changes)
[ x ] Build related changes
[ ] CI related changes
[ x ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?
The repository has been migrated from using master branch to the new default main branch.
However, some docs have not been updated and the CI is still based on master
Issue Number: N/A
What is the new behavior?
Docs are updated to refer to main and CI uses main as the trunk branch.
Does this PR introduce a breaking change?
[ ] Yes
[ x ] No

Other information

Commit message should be chore: move from master branch to main, instead of refactor: (...).

I'll change it with the squash