feat: Add RocketChat support

Hi i was added support for sending messages to RocketChat
related to https://github.com/argoproj-labs/argocd-notifications/issues/233

Codecov Report

Merging #1 (af619c6) into master (c1ebfd8) will decrease coverage by 1.21%.
The diff coverage is 25.80%.

@@            Coverage Diff             @@
##           master       #1      +/-   ##
==========================================
- Coverage   44.12%   42.90%   -1.22%
==========================================
  Files          17       18       +1
  Lines         834      895      +61
==========================================
+ Hits          368      384      +16
- Misses        378      421      +43
- Partials       88       90       +2

Impacted Files
Coverage Δ

pkg/services/slack.go
25.00% <0.00%> (ø)

pkg/services/rocketchat.go
25.92% <25.92%> (ø)

pkg/services/services.go
25.49% <28.57%> (+0.22%)
:arrow_up:

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 c1ebfd8...af619c6. Read the comment docs.

Hi @sergeyshevch
Would you add documentation, please?

@ryota-sakamoto I'm not sure about documentation in this repo. As I see there is only documentation in the main argocd-notifications-repo.
I will add it after this PR will be merged and i will add integration to the main repo

Hi @sergeyshevch
Would you add documentation, please?

We was discussed about it in Slack


GPU memory sizes unclear

It's unclear how much memory the GPUs built into the machines actually have. It would be better if you provided the total GPU memory size per VM size, as well as the GPU memory size per GPU. Not sure about the other articles -- the issue might apply there, too.

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

ID: abf13994-0a3b-dccf-71e3-a7f5e232f642
Version Independent ID: b8d87ac0-35ac-08ad-efa1-c6f68bca960a
Content: ND A100 v4-series - Azure Virtual Machines
Content Source: articles/virtual-machines/nda100-v4-series.md
Service: virtual-machines
Sub-service: sizes
GitHub Login: @sherrywangms
Microsoft Alias: sherrywang

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

@Karishma-Tiwari-MSFT please help assign to @mattrvegas the owner of this product.

@mattrvegas
Can you please check and add your comments on this doc update request as applicable.

@mattrvegas are you able to provide an update on this issue?

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close

#please-close

#please-close


Example Image doesn't make it clear that Release Date field requires date as well

The Example image showing how to test the Create Link with Title "The Good, the bad, and the ugly" gives the impression that when copied exactly it will create an entry in the database. However, once you click Create, it will give the error "The ReleaseDate field is required" since the date and time are both required. Simply, change the image to a screenshot of ReleasDate field filled with both date and time.

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

ID: 6719f08e-3bd7-dc1a-71df-f2ef9fbca9d8
Version Independent ID: 7096fdb3-612e-9e00-bd0b-8ea4886a09ce
Content: Add a model to a Razor Pages app in ASP.NET Core
Content Source: aspnetcore/tutorials/razor-pages/model.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@hkalia  I think I'll introduce the Date attribute sooner so you won't have to enter time.

Dup of #7665
Will fix in next release.


Error Python/Dask worker/scheduler

Hello everyone, I am using in my local network the 3 computers, being 2 for 'worker' and 1 computer the 'schedule', configuring the 'client' in python when executing the command:
###################
from dask.distributed import Client
client = Client ('My ip address: 8786')
###################
And the result is:
TypeError: descriptor 'tls_worker_cert' for 'Security' objects does not apply to 'Security' object
Has anyone ever experienced this?
I am using a python 3.7.3 and dask 1.2.2
Thank you for your help!

 What version of distributed, and are there any logs on the scheduler / worker?
What protocol are you passing to Client? tcp? (no protocol defaults to tcp) or tls?

*What version of distributed
1.27.0, latest
*any logs on the scheduler / worker?
I just have 2 files in a dask folder, purge.lock and global.lock, both empty
What protocol are you passing to Client?
TCP

Tks

The console with the client should have a longer traceback.
How'd you start the scheduler & workers?

*What version of distributed
1.27.0, latest
*any logs on the scheduler / worker?
I just have 2 files in a dask folder, purge.lock and global.lock, both
empty
What protocol are you passing to Client?
TCP
[image: image_dask]
https://user-images.githubusercontent.com/7399450/57942232-4f7d6400-78a7-11e9-985e-4a4ef957b491.png
Tks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/4812?email_source=notifications&email_token=AAKAOIQYBIVAEXXR6SHLW7DPV3MB7A5CNFSM4HNRBOEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVVHDCQ#issuecomment-493515146,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKAOIVGVXROJYDFDQNAVWLPV3MB7ANCNFSM4HNRBOEA
.

*The console with the client should have a longer traceback.
*How'd you start the scheduler & workers?
Using Anaconda Prompt Console.
http://distributed.dask.org/en/latest/setup.html, page "Setup Network"
Print of Anaconda command worker:

Print of Dask directory:

Print of Anaconda command scheduler:

Tks

*The console with the client should have a longer traceback.

Were you able to get this traceback?
Can you also try setting the log level to debug in case that has more information? https://distributed.dask.org/en/latest/configuration.html#user-wide-configuration (change the logging.distributed value from info to debug

Let us know if you can provide that info. This doesn't seem to be an issue with dask / distributed though.


3MF export

From elalish/manifold#626
Hi, it seems that the object id has to be at least 1, lib3mf cannot recognize things with id 0.
The _rels/.rels is mandatory, we can remove the thumbnail line if we don't want a thumbnail.

oh the object id thing is set by us, but maybe you can add a documentation about the id has to be non-zero

ok, thanks for the hints, I could even throw an error if id is zero and add a bit in docs.

Do you plan to fix them and release a version soon? If yes, I can wait for your release without having to use this ugly workaround:
  files[fileForRelThumbnail.name] = strToU8(
      // remove the thumbnail line
      fileForRelThumbnail.content.split('\n')
          .filter((line: string) => line.indexOf('thumbnail') == -1)
          .join('\n'));

oh, ok I see. You are currently removing the thumbnail from 3mf export... I thought you were adding the thumbnail :)
.. np, I can make a version today, tomorrow that allows export without thumbnail, and keeps the mandatory rel file.

Thanks. In order to make a thumbnail we need access to the canvas, but we are currently making the 3mf file in a worker. I am not familiar with js stuff so I just decided to remove the thumbnail :)

@pca006132 I created 0.5.0 version that handles ref differently.
instead of it being a static file thre is new class: FileForRelThumbnail that has getter for proeprties name and content,
but the content is generated based on sate (added files).
instad of just importing  fileForRelThumbnail,  import  anduse FileForRelThumbnail  class
const fileForRelThumbnail = new FileForRelThumbnail()
//...
fileForRelThumbnail.add3dModel('3D/3dmodel.model')
//.. if you have thumbnail, add it
fileForRelThumbnail.addThumbnail('Metadata/thumbnail.png')

this way only refs actually used will be present in _rels/.rels

Thanks. Updated in manifold now.


update(libsinsp): Enable position-independent code.

Set CMAKE_POSITION_INDEPENDENT_CODE in CompilerFlags.cmake. This fixes
/usr/bin/ld: libsinsp/libsinsp.a(logger.cpp.o): relocation R_X86_64_TPOFF32 against _ZN12_GLOBAL__N_16s_tbufE' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: libsinsp/libsinsp.a(sinsp.cpp.o): relocation R_X86_64_PC32 against symbol _ZTV15sinsp_exception' can not be used when making a shared object; recompile with -fPIC
when linking a PIC-enabled shared library with libsinsp here on Ubuntu.

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-ebpf

/area libscap

/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

@geraldcombs: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

8752d9e update(libsinsp): Enable position-independent code.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Hi @geraldcombs. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: geraldcombs
To complete the pull request process, please assign fededp after the PR has been reviewed.
You can assign the PR to them by writing /assign @fededp in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

This should be safe to enable everywhere, but I can add a CMake option, e.g. ENABLE_PIC if needed.

Hi @geraldcombs !
I think it is safe enough to just enable PIC without yet another option. I see no downsides.
Thank you for this PR!
/ok-to-test

My only concern is that PIC can affect performance of the application, see https://stackoverflow.com/questions/15861759/how-much-overhead-can-the-fpic-flag-add.
Perhaps we could add the option(ENABLE_PIC "" OFF) by default and only set PIC if the option is enabled?

Perhaps we could add the option(ENABLE_PIC "" OFF) by default and only set PIC if the option is enabled?

Done.

It might make sense to add an option for building shared libs instead of or in addition to this; they're position-independent by default. I can take a look at doing that if you'd like.

I think that would have a broader scope; perhaps it is better to talk about it with the community in the today community call?
IMO at the moment i'd avoid having the shared libs because we don't really have a stable API and neither tagged releases; but that's just my opinion.
I think @terylt is interested in shared libs too, right?  Perhaps he has some more info :)

I think it's great to have an option to build shared libraries, so I would support a flag to do so, and maybe even a make shared_install make static_installtype of options in the make.  I can see the value in having both.  We use the static libs quite a bit in some of our deployments in air gapped systems and compiling everything into the binary is really nice in those scenarios, but I can see use cases for shared as well.   We might want to adopt a naming convention for the.a` files in both cases..

Thanks for sharing @terylt !
I'd be interested in listening to @leogr too, perhaps there is any historical reason for not supporting shared lib?
In the end, i think a flag would be a safe addition in any case.

LGTM label has been added.  Git tree hash: cec0bb571a8475ecea8c5aa7bb65497c34f1f695

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, geraldcombs
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, geraldcombs, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Login form has no hooks

I spent a little time looking around to see how one might go about implementing a plugin to provide multi-factor authentication (as requested in #2434) or OpenID login (I have a WordPress plugin that consumes OpenID), for example. In the process, I could not find any way for plugins to add fields on the login form.
Perhaps YOURLS doesn't need quite as many hooks as WordPress has, but I do think at least one injection point (below username & password, but above the submit button) would be useful. A plugin implementing two-factor auth would add a field there asking for the TOTP code (for example); a plugin implementing OpenID as a consumer would add, say, "or" and a field for the user's OpenID URL.
Per usual, before I actually get into any code, I'd like to flesh out exactly what hooks are appropriate. We can copy WordPress's hook name login_form for the one at the bottom of the login form. It's also trivial to add a login_head hook in case plugins need to add tags in the header for CSS/JS that's needed only on the login page. Putting a login_footer hook might not be as useful…
Left to my own devices, I'd implement the first two (login_head and login_form) as a start.

Completely open to add as many hooks as needed, if needed, anywhere. Regarding the login form, yourls_login_screen() calls yourls_html_head( 'login' ); so you can inject anything in the head using the first parameter of yourls_html_head(), but having specific pre_login_form and post_login_form wrapping the login form itself cannot hurt.


xmrig-proxy: 6.15.1 -> 6.18.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/xmrig/xmrig-proxy/releases.
meta.description for xmrig-proxy is: "Monero (XMR) Stratum protocol proxy"
meta.homepage for xmrig-proxy is: "https://github.com/xmrig/xmrig-proxy"
meta.changelog for xmrig-proxy is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.18.0 with grep in /nix/store/8l9jzn33z6rpv5fbz2cnzhaagbjrhxby-xmrig-proxy-6.18.0
found 6.18.0 in filename of file in /nix/store/8l9jzn33z6rpv5fbz2cnzhaagbjrhxby-xmrig-proxy-6.18.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
xmrig-proxy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8l9jzn33z6rpv5fbz2cnzhaagbjrhxby-xmrig-proxy-6.18.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8l9jzn33z6rpv5fbz2cnzhaagbjrhxby-xmrig-proxy-6.18.0
ls -la /nix/store/8l9jzn33z6rpv5fbz2cnzhaagbjrhxby-xmrig-proxy-6.18.0/bin

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

1 package built:

xmrig-proxy

Maintainer pings
cc @aij for testing.

Result of nixpkgs-review pr 186912 run on x86_64-linux 1

1 package built:

xmrig-proxy


Topic creation appears fundamentally broken

I'm trying to create a new topic using the Terraform provider.
I have read the advisories about the topic configuration values that aren't editable after topic creation. However, it appears that you can't even edit those values when you create the topic, and that any of those overridden defaults that remain in your resource definition trigger subsequent updates that can never succeed.
As long as you don't want to change any configuration values, it seems that you can create a topic; as soon as you want to customize the configuration, however, things begin to break.
Here is a minimal Terraform program that illustrates this:
terraform {
  required_providers {
    confluent = {
      source  = "confluentinc/confluent"
      version = "1.8.0"
    }
  }
}

variable "kafka_cluster_id" {
  type        = string
}

# Must set all of the following environment variables:
# - CONFLUENT_CLOUD_API_KEY
# - CONFLUENT_CLOUD_API_SECRET
# - KAFKA_REST_ENDPOINT
# - KAFKA_API_KEY
# - KAFKA_API_SECRET
provider "confluent" {}

resource "confluent_kafka_topic" "testing-topic" {
  kafka_cluster {
    id = var.kafka_cluster_id
  }
  topic_name         = "testing-topic"
  partitions_count   = 6
  config = {
    "cleanup.policy" = "delete"
    # NOTE: This is overridden from the default value of 'producer'
    "compression.type" = "zstd"
    "connection.failed.authentication.delay.ms" = "5000"
    "default.replication.factor" = "3"
    "delete.retention.ms" = "86400000"
    "file.delete.delay.ms" = "60000"
    "flush.messages" = "9223372036854775807"
    "flush.ms" = "9223372036854775807"
    "group.max.session.timeout.ms" = "1200000"
    "index.interval.bytes" = "4096"
    "max.compaction.lag.ms" = "9223372036854775807"
    "max.message.bytes" = "2097164"
    "max.downconversion.enable" = "true"
    "message.format.version" = "3.0-IV1"
    "message.timestamp.difference.max.ms" = "9223372036854775807"
    "message.timestamp.type" = "CreateTime"
    "min.cleanable.dirty.ratio" = "0.5"
    "min.compaction.lag.ms" = "0"
    "min.insync.replicas" = "2"
    "offsets.retention.minutes" = "10080"
    "preallocate" = "false"
    "retention.bytes" = "-1"
    "retention.ms" = "604800000"
    "segment.bytes" = "104857600"
    "segment.index.bytes" = "10485760"
    "segment.jitter.ms" = "0"
    "segment.ms" = "604800000"
    "unclean.leader.election.enable" = "false"
  }
}

Some important things to note:

I'm specifying configuration values for pretty much all variables for a topic, including ones that are editable after topic creation, and ones that are not editable after topic creation.
Everything is the default value except for compression.type which has been changed to zstd from the default of producer.

Saved to a main.tf file, it can be run as follows:
CONFLUENT_CLOUD_API_KEY="..." \
CONFLUENT_CLOUD_API_SECRET="..." \
KAFKA_REST_ENDPOINT="..." \
KAFKA_API_KEY="..." \
KAFKA_API_SECRET="..." \
TF_VAR_kafka_cluster_id="lkc-XXXXX" \
terraform apply

Here is the output of that first terraform apply:
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # confluent_kafka_topic.testing-2 will be created
  + resource "confluent_kafka_topic" "testing-topic" {
      + config           = {
          + "cleanup.policy"                            = "delete"
          + "compression.type"                          = "zstd"
          + "connection.failed.authentication.delay.ms" = "5000"
          + "default.replication.factor"                = "3"
          + "delete.retention.ms"                       = "86400000"
          + "file.delete.delay.ms"                      = "60000"
          + "flush.messages"                            = "9223372036854775807"
          + "flush.ms"                                  = "9223372036854775807"
          + "group.max.session.timeout.ms"              = "1200000"
          + "index.interval.bytes"                      = "4096"
          + "max.compaction.lag.ms"                     = "9223372036854775807"
          + "max.downconversion.enable"                 = "true"
          + "max.message.bytes"                         = "2097164"
          + "message.format.version"                    = "3.0-IV1"
          + "message.timestamp.difference.max.ms"       = "9223372036854775807"
          + "message.timestamp.type"                    = "CreateTime"
          + "min.cleanable.dirty.ratio"                 = "0.5"
          + "min.compaction.lag.ms"                     = "0"
          + "min.insync.replicas"                       = "2"
          + "offsets.retention.minutes"                 = "10080"
          + "preallocate"                               = "false"
          + "retention.bytes"                           = "-1"
          + "retention.ms"                              = "604800000"
          + "segment.bytes"                             = "104857600"
          + "segment.index.bytes"                       = "10485760"
          + "segment.jitter.ms"                         = "0"
          + "segment.ms"                                = "604800000"
          + "unclean.leader.election.enable"            = "false"
        }
      + id               = (known after apply)
      + partitions_count = 4
      + topic_name       = "testing-topic"

      + kafka_cluster {
          + id = "lkc-XXXXXX"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

confluent_kafka_topic.testing-topic: Creating...
confluent_kafka_topic.testing-topic: Still creating... [10s elapsed]
confluent_kafka_topic.testing-topic: Creation complete after 11s [id=lkc-XXXXXX/testing-topic]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

The initial terraform apply run succeeds, but the configuration values are not honored. In particular, the topic is created with a compression.type of producer, not zstd, as was specified.
This can be seen in the Confluent Cloud SaaS UI as well as via the REST API:
{
  "kind": "KafkaTopicConfig",
  "metadata": {
    "self": "https://pkc-XXXXX.region.aws.confluent.cloud/kafka/v3/clusters/lkc-XXXXXX/topics/testing-topic/configs/compression.type",
    "resource_name": "crn:///kafka=lkc-XXXXXX/topic=testing-topic/config=compression.type"
  },
  "cluster_id": "lkc-XXXXXX",
  "name": "compression.type",
  "value": "producer",                          # <-- This should be "zstd"
  "is_read_only": true,
  "is_sensitive": false,
  "source": "DEFAULT_CONFIG",
  "synonyms": [
    {
      "name": "compression.type",
      "value": "producer",
      "source": "DEFAULT_CONFIG"
    }
  ],
  "topic_name": "testing-topic",
  "is_default": true
}

Subsequent terraform apply runs mark the topic resource as needing an update. All the updates are for the non-editable configuration values, even though they haven't changed their values.
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # confluent_kafka_topic.testing-topic will be updated in-place
  ~ resource "confluent_kafka_topic" "testing-topic" {
      ~ config           = {
          + "compression.type"                          = "zstd"
          + "connection.failed.authentication.delay.ms" = "5000"
          + "default.replication.factor"                = "3"
          + "file.delete.delay.ms"                      = "60000"
          + "flush.messages"                            = "9223372036854775807"
          + "flush.ms"                                  = "9223372036854775807"
          + "group.max.session.timeout.ms"              = "1200000"
          + "index.interval.bytes"                      = "4096"
          + "max.downconversion.enable"                 = "true"
          + "message.format.version"                    = "3.0-IV1"
          + "min.cleanable.dirty.ratio"                 = "0.5"
          + "offsets.retention.minutes"                 = "10080"
          + "preallocate"                               = "false"
          + "segment.index.bytes"                       = "10485760"
          + "segment.jitter.ms"                         = "0"
          + "unclean.leader.election.enable"            = "false"
            # (12 unchanged elements hidden)
        }
        id               = "lkc-XXXXXX/testing-topic"
        # (2 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

confluent_kafka_topic.testing-topic: Modifying... [id=lkc-XXXXXX/testing-topic]
╷
│ Error: error updating Kafka Topic "lkc-XXXXXX/testing-topic": "offsets.retention.minutes" topic setting is read-only and cannot be updated. Read https://registry.terraform.io/providers/confluentinc/confluent/latest/docs/resources/confluent_kafka_topic for more details.
│
│   with confluent_kafka_topic.testing-topic,
│   on main.tf line 32, in resource "confluent_kafka_topic" "testing-topic":
│   32: resource "confluent_kafka_topic" "testing-topic" {
│

Have I missed something fundamental here, or can you not use this provider to create topics with modified configurations?
Thanks :pray:

👋 thanks for creating this issue and writing such a detailed summary!
I think our docs are a little bit unclear and they don't specify which topic settings can be specified on CREATE and the assumption a reader might have is as long as the topic setting is listed in that table, one could override its value on CREATE which is not totally accurate.
To specifically answer your question, compression.type is a read-only topic setting that can't be overriden during CREATE or after. To make things a little bit worse, there're some gotchas with Kafka REST API and it returns 201 even though ideally it'd have returned 400 with a descriptive error messages like X topic setting can't be set on CREATE. There's an internal ticket FF-4417 to support custom values on CREATE / updates for compression.type.
The following list of setting topic can't set on CREATE either (FWIW most of them are marked editable: no in that table):

"connection.failed.authentication.delay.ms"
"default.replication.factor"
"file.delete.delay.ms"
"flush.messages"
"flush.ms"
"group.max.session.timeout.ms"
"index.interval.bytes"
"max.downconversion.enable"
"message.format.version"
"min.cleanable.dirty.ratio"
"offsets.retention.minutes"
"preallocate"
"segment.index.bytes"
"segment.jitter.ms"
"unclean.leader.election.enable"
"compression.type"

I'm specifying configuration values for pretty much all variables for a topic, including ones that are editable after topic creation, and ones that are not editable after topic creation.

However for others topic settings updates (on CREATE and after) are actually supported for editable topic settings: for example, you can try to use:
resource "confluent_kafka_topic" "orders" {
  kafka_cluster {
    id = "lkc-y62rg7"
  }
  topic_name    = "orders"

  # https://docs.confluent.io/cloud/current/clusters/broker-config.html#custom-topic-settings-for-all-cluster-types
  config = {
    # NOTE: This is overridden from the default value of 'delete'
    "cleanup.policy"   = "compact"
    # NOTE: Overriding segment.ms to the default value:
    "segment.ms"       = "604800000"
    # NOTE: Overriding retention.ms to a custom value:
    "retention.ms"     = "604800001"
  }
}

and then you could run terraform plan with:
$ terraform plan
confluent_kafka_topic.orders: Refreshing state... [id=lkc-y62rg7/orders]

No changes. Your infrastructure matches the configuration.

For readability I'd also recommend not to list topic settings unless you want them to be set to a custom value.
Let me know if it helps / makes sense at all!

cc @christophermaier ⬆

@linouk23 This is very much a documentation issue, then. Calling something a configuration value when it can't be changed at all, even at topic creation time, is needlessly confusing. If I see something described as "configuration", it is entirely reasonable to think that I can actually configure it.
I'm glad that work is underway to enable changing these values, but until that capability is ready, I don't see the use of the documentation even mentioning them, let alone going to such lengths to make distinctions between what a user can and cannot edit.

Thanks for the feedback @christophermaier! We're working on updating docs to split Editable column into Editable on Create and Editable after Create columns.

I don't see the use of the documentation even mentioning them, let alone going to such lengths to make distinctions between what a user can and cannot edit.

Do you think it'll helpful to delete topic settings that have No as a value for both Editable on Create and Editable after Create  columns?

Do you think it'll helpful to delete topic settings that have No as a value for both Editable on Create and Editable after Create columns?

@linouk23 That depends on what operators or users can do with that knowledge. Is there any benefit to knowing about an internal detail that you can't change? Maybe it's good information to know, in order to have a better understanding of how the system works, so you can better reason about things when you're trying to, say, debug something. Maybe it's not useful to know.
In any event, I don't think having that information in a section about configuration is useful, because it can't be configured.
(Creating separate columns in the documentation for Editable on Create and Editable after Create is a great idea, however!)

I'm closing this PR since we updated the docs, see https://docs.confluent.io/cloud/current/clusters/broker-config.html#custom-topic-settings-for-all-cluster-types-supported-by-kafka-rest-api-and-terraform-provider
We'll update TF docs accordingly in our next release of TF Provider.


Added feet (US survey)

Thank you for creating a useful package.
I have added ft (US survey), please check and merge if possible.
Best regards,

Codecov Report

Merging #15 (12623bb) into main (6f8218e) will decrease coverage by 0.24%.
The diff coverage is 60.00%.

@@             Coverage Diff             @@
##              main      #15      +/-   ##
===========================================
- Coverage   100.00%   99.75%   -0.25%
===========================================
  Files           24       24
  Lines          822      827       +5
===========================================
+ Hits           822      825       +3
- Misses           0        2       +2

Impacted Files
Coverage Δ

lib/properties/length.dart
98.03% <50.00%> (-1.97%)
:arrow_down:

lib/properties/area.dart
97.36% <66.66%> (-2.64%)
:arrow_down:

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 6f8218e...12623bb. Read the comment docs.

Hi @chuyentt  and thank you, it's all perfect to me. Only 2 tests are missing, see the getters_test.dart file. I'm sorry but we want to keep a 100% coverage. Then we are ready to merge

Thank you @chuyentt!


Please review my blog: "Enabling Webpack’s HMR In React — The Missing Manual"

"Enabling Webpack’s HMR In React — The Missing Manual" https://medium.com/@rajaraodv/232336dc0d96
If you have suggestions or corrections, please select the text and Medium will show a tooltip w/ a lock symbol. If you click on that tooltip, it will allow you to add "private" comments and I'll get notifications.
I plan to post this Saturday afternoon. *You can make suggestion anytime even after it's posted and I'll update the blog * 😃
@sokra @gaearon
Thanks,
Raja

I would like to note that React Hot Loader 1 is deprecated, and version 3 is very different in the configuration. I’d appreciate if you documented version 3 instead.
https://github.com/gaearon/react-hot-loader/pull/240
https://github.com/gaearon/react-hot-loader/pull/260

Got it. It looks like there is so much going on! Not sure when it will be ready but when it is, I will deprecate the current blog and point to a new one. Thanks @gaearon

It’s pretty stable at this point. The main reason I don’t release it as stable is because the docs are not ready 😉 . You can help with the docs: https://github.com/gaearon/react-hot-loader/pull/260.


#117 issue fix.Typo in reducer filename.

Rename the file /reactapp/src/context/Cart/order/reudcers.js to /reactapp/src/context/Cart/order/reducers.js

Hello, the import is also fixed.


secp256k1: 0.4.1 -> 0.5.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/bitcoin-core/secp256k1/releases.
meta.description for secp256k1 is: Optimized C library for EC operations on curve secp256k1
meta.homepage for secp256k1 is: https://github.com/bitcoin-core/secp256k1
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.5.0 with grep in /nix/store/gz8xg34w3ni93x4i2gwlwj7ynjj70nsy-secp256k1-0.5.0
found 0.5.0 in filename of file in /nix/store/gz8xg34w3ni93x4i2gwlwj7ynjj70nsy-secp256k1-0.5.0

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

45 total rebuild path(s)

45 package rebuild(s)

First fifty rebuilds by attrpath

echidna
electron-cash
electrum
electrum-grs
electrum-ltc
glow-lang
haskellPackages.haskoin-core
haskellPackages.haskoin-store-data
haskellPackages.secp256k1-haskell
jami
libbitcoin
libbitcoin-client
libbitcoin-explorer
libbitcoin-network
libbitcoin-protocol
opshin
python311Packages.bip-utils
python311Packages.bip32
python311Packages.coincurve
python311Packages.eth-account
python311Packages.eth-keyfile
python311Packages.eth-keys
python311Packages.ledger-bitcoin
python311Packages.pluthon
python311Packages.python-secp256k1-cardano
python311Packages.secp256k1
python311Packages.slither-analyzer
python311Packages.uplc
python311Packages.web3
python312Packages.bip-utils
python312Packages.bip32
python312Packages.coincurve
python312Packages.eth-account
python312Packages.eth-keyfile
python312Packages.eth-keys
python312Packages.ledger-bitcoin
python312Packages.secp256k1
python312Packages.slither-analyzer
python312Packages.web3
secp256k1
slither-analyzer
tests.pkg-config.defaultPkgConfigPackages.libsecp256k1
ton
zeronet-conservancy

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/f96a90834c5e2fb1fd9cebfba862c6d5a01f7601#secp256k1

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

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

1 package marked as broken and skipped:

echidna

3 packages failed to build:

electrum-ltc
electrum-ltc.dist
glow-lang

65 packages built:

electron-cash
electron-cash.dist
electrum
electrum-grs
electrum-grs.dist
electrum.dist
jami
libbitcoin
libbitcoin-client
libbitcoin-explorer
libbitcoin-network
libbitcoin-protocol
ocamlPackages.secp256k1
opshin
opshin.dist
python311Packages.bip-utils
python311Packages.bip-utils.dist
python311Packages.bip32
python311Packages.bip32.dist
python311Packages.coincurve
python311Packages.coincurve.dist
python311Packages.eth-account
python311Packages.eth-account.dist
python311Packages.eth-keyfile
python311Packages.eth-keyfile.dist
python311Packages.eth-keys
python311Packages.eth-keys.dist
python311Packages.ledger-bitcoin
python311Packages.ledger-bitcoin.dist
python311Packages.pluthon
python311Packages.pluthon.dist
python311Packages.python-secp256k1-cardano
python311Packages.python-secp256k1-cardano.dist
python311Packages.secp256k1
python311Packages.secp256k1.dist
slither-analyzer (python311Packages.slither-analyzer)
slither-analyzer.dist (python311Packages.slither-analyzer.dist)
python311Packages.uplc
python311Packages.uplc.dist
python311Packages.web3
python311Packages.web3.dist
python312Packages.bip-utils
python312Packages.bip-utils.dist
python312Packages.bip32
python312Packages.bip32.dist
python312Packages.coincurve
python312Packages.coincurve.dist
python312Packages.eth-account
python312Packages.eth-account.dist
python312Packages.eth-keyfile
python312Packages.eth-keyfile.dist
python312Packages.eth-keys
python312Packages.eth-keys.dist
python312Packages.ledger-bitcoin
python312Packages.ledger-bitcoin.dist
python312Packages.secp256k1
python312Packages.secp256k1.dist
python312Packages.slither-analyzer
python312Packages.slither-analyzer.dist
python312Packages.web3
python312Packages.web3.dist
secp256k1
ton
ton.dev
zeronet-conservancy

Maintainer pings

1 package marked as broken and skipped:

echidna

1 package failed to build:

glow-lang

73 packages built:

electron-cash
electron-cash.dist
electrum
electrum-grs
electrum-grs.dist
electrum-ltc
electrum-ltc.dist
electrum.dist
haskellPackages.haskoin-core
haskellPackages.haskoin-core.doc
haskellPackages.haskoin-store-data
haskellPackages.haskoin-store-data.doc
haskellPackages.secp256k1-haskell
haskellPackages.secp256k1-haskell.doc
jami
libbitcoin
libbitcoin-client
libbitcoin-explorer
libbitcoin-network
libbitcoin-protocol
opshin
opshin.dist
python311Packages.bip-utils
python311Packages.bip-utils.dist
python311Packages.bip32
python311Packages.bip32.dist
python311Packages.coincurve
python311Packages.coincurve.dist
python311Packages.eth-account
python311Packages.eth-account.dist
python311Packages.eth-keyfile
python311Packages.eth-keyfile.dist
python311Packages.eth-keys
python311Packages.eth-keys.dist
python311Packages.ledger-bitcoin
python311Packages.ledger-bitcoin.dist
python311Packages.pluthon
python311Packages.pluthon.dist
python311Packages.python-secp256k1-cardano
python311Packages.python-secp256k1-cardano.dist
python311Packages.secp256k1
python311Packages.secp256k1.dist
slither-analyzer (python311Packages.slither-analyzer)
slither-analyzer.dist (python311Packages.slither-analyzer.dist)
python311Packages.uplc
python311Packages.uplc.dist
python311Packages.web3
python311Packages.web3.dist
python312Packages.bip-utils
python312Packages.bip-utils.dist
python312Packages.bip32
python312Packages.bip32.dist
python312Packages.coincurve
python312Packages.coincurve.dist
python312Packages.eth-account
python312Packages.eth-account.dist
python312Packages.eth-keyfile
python312Packages.eth-keyfile.dist
python312Packages.eth-keys
python312Packages.eth-keys.dist
python312Packages.ledger-bitcoin
python312Packages.ledger-bitcoin.dist
python312Packages.secp256k1
python312Packages.secp256k1.dist
python312Packages.slither-analyzer
python312Packages.slither-analyzer.dist
python312Packages.web3
python312Packages.web3.dist
secp256k1
tests.pkg-config.defaultPkgConfigPackages.libsecp256k1
ton
ton.dev
zeronet-conservancy

glow-lang is broken on hydra


Update main release and alignment

Overall Review of Changes:
Tidy up and improve alot of the content
latest ansible-lint configuration
new workflow setup (enabling easier changes if required)
new readme layout
Issue Fixes:
#314
#315
#317
Enhancements:
Lint updates
improved links to content and documention
many controls updated and improved
How has this been tested?:
Manually

workflow expected to fail as legacy files no longer present
more PRs to follow to ensure workflow and process works as expected


Package vs module for go advisories

Hello,
I noticed that for some go vulnerabilities, the vulnerability references a go package,
and not a go module.
For example, GHSA-pmw9-567p-68pc references the package github.com/cloudflare/cfrpki/cmd/octorpki, while the associated go module is github.com/cloudflare/cfrpki.
Note that some advisories reference both package and module, such as https://github.com/advisories/GHSA-74fp-r6jw-h4mp.
This is a bit troublesome, as go.mod files reference modules, so we need to find the module that contains a package
in order to know if a module is vulnerable.
Moreover, if a vulnerability references a package (inside a module), it is possible for the package to be later shadowed
by a module of the same name. In this case, the vulnerability would reference the wrong module.
From basic queries on the proxy.golang.org, it seems that about 20% of go packages referenced in (reviewed) advisories reference a non-existing module (which is most likely a package inside a module). This concerns 1010 advisories in total.
Do you think this is an issue that should be acted upon ?

This is indeed an issue. Any comment from maintainers/github forthcoming?


updated pg dependency to 4.5.5

as described in https://github.com/dmitriiabramov/node-sql-migrations/issues/1

thank you!


feat: remove jaeger datasource

:tada: This PR is included in version 0.2.0-alpha.19 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Kit's improved drawing app

now with :100:% less + :)

@EternalFootman Ahh! another problem.  There's no day in the title.  That's why this still isn't showing up.  Doublecheck for any other errors when you fix that- I may have missed them.
If I'm offline, feel free to work with your partner to get this merged up.

@eah13 Ahh! indeed. Apologies. Fixed now.


Change terminology in copier question for clarity

We got some feedback that the question "What is your python module name?" could be better phrased as "What is your python package name?" (Perhaps with some added hint text saying something like "you'll use import  to import your package", to provide some more clarity.
We also got feedback that the regex warning for project and module names exceeds the 80 character limit on some terminals, and Copier won't wrap to the next line. So we should try to find a way to shorten the error message.

Don't forget to update the documentation as well: https://lincc-ppt.readthedocs.io/en/latest/source/new_project.html


Node 10

It has a better support for ES modules.
Blocked by Yarn. Isn't time to switch back to npm?

yep


Broken backwards compatibility in docopt 0.6.86 and later versions

Hey!
When releasing new version of one of our cli's (ethabi), I noticed that backwards compatibility was broken in version 0.6.86.
The following code:

pub const ETHABI: &'static str = r#"
Ethereum ABI coder.
  Copyright 2016-2017 Parity Technologies (UK) Limited

Usage:
    ethabi encode params [-v <type> <param>]... [-l | --lenient]
"#;

#[derive(Debug, RustcDecodable)]
struct Args {
	cmd_encode: bool,
	cmd_params: bool,
	arg_param: Vec<String>,
	arg_type: Vec<String>,
	flag_lenient: bool,
}

let command = "ethabi encode params -v bool 1 -v string gavofyork -v bool 0".split(" ");
let args: Args = Docopt::new(ETHABI)
  .and_then(|d| d.argv(command).decode())
  .unwrap_or_else(|e| e.exit());

assert_eq(args.arg_param.len(), args.arg_type.len(), "{:?} {:?}", args.arg_param, args.arg_type);

Works fine in version 0.6.85, but after upgrading to 0.6.86, 0.7 or 0.8 it fails with:
assertion failed: `(left == right)` (left: `1`, right: `5`): ["bool"] ["1", "string", "gavofyork", "bool", "0"]'

Direct link to our broken code: https://github.com/paritytech/ethabi/blob/release_1.2/cli/src/main.rs#L24

From looking at the diff between 0.6.85 and 0.6.86, the only change is a fix to this bug: https://github.com/docopt/docopt.rs/issues/195 So it looks like that caused a regression elsewhere.
I'm not inclined to revert the fix to that bug. I'd rather treat this as a separate bug. I'm not sure when I'll have time to look at it.

Sure, it's not urgent, cause 0.6.85 still works perfectly fine. I will take a stab at fixing this when I have more time.


GCODE output is empty

This is a fresh install, and the gcode files just contain
;Generated from just_in_case.tmp.1719745022467.stl (hash: c984a5cf3c8d6d334d1c4b62464525414c446935)
; BEGIN DISPLAYLAYERPROGRESS SETTINGS
; DisplayLayerProgress_layerIndicatorProcessed = true
; END   DISPLAYLAYERPROGRESS SETTINGS

I've tried a few files with the same result.

Here's my config.ini
# generated by PrusaSlicer 2.8.0+win64 on 2024-06-30 at 10:32:37 UTC
arc_fitting = disabled
autoemit_temperature_commands = 1
avoid_crossing_curled_overhangs = 0
avoid_crossing_perimeters = 1
avoid_crossing_perimeters_max_detour = 0
bed_custom_model =
bed_custom_texture =
bed_shape = 5x0,215x0,215x220,5x220
bed_temperature = 50
before_layer_gcode = ;BEFORE_LAYER_CHANGE\nG92 E0\n;{layer_z}\n\n
between_objects_gcode =
binary_gcode = 0
bottom_fill_pattern = rectilinear
bottom_solid_layers = 2
bottom_solid_min_thickness = 0
bridge_acceleration = 250
bridge_angle = 0
bridge_fan_speed = 100
bridge_flow_ratio = 0.95
bridge_speed = 25
brim_separation = 0
brim_type = outer_only
brim_width = 0
chamber_minimal_temperature = 0
chamber_temperature = 0
color_change_gcode = M600
colorprint_heights =
compatible_printers_condition_cummulative = nozzle_diameter[0]==0.4;printer_notes=~/.*PRINTER_VENDOR_CREALITY.*/
complete_objects = 0
cooling = 1
cooling_tube_length = 5
cooling_tube_retraction = 91.5
default_acceleration = 500
default_filament_profile = "Generic PLA @CREALITY"
default_print_profile = "0.16 mm OPTIMAL (0.4 mm nozzle) @CREALITY"
deretract_speed = 40
disable_fan_first_layers = 1
dont_support_bridges = 1
draft_shield = disabled
duplicate_distance = 6
elefant_foot_compensation = 0.1
enable_dynamic_fan_speeds = 0
enable_dynamic_overhang_speeds = 0
end_filament_gcode = "; Filament-specific end gcode \n;END gcode for filament\n"
end_gcode = M400 ; Syncronise planner\n{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+2, max_print_height)} F600 ; Move print head up{endif}\nG1 X5 Y{print_bed_max[1]*0.85} F{travel_speed*60} ; present print\nM140 S0 ; turn off heatbed\nM104 S0 ; turn off temperature\nM107 ; turn off fan\nM84 X Y E ; disable motors
external_perimeter_acceleration = 0
external_perimeter_extrusion_width = 0.42
external_perimeter_speed = 25
external_perimeters_first = 0
extra_loading_move = -2
extra_perimeters = 1
extra_perimeters_on_overhangs = 1
extruder_clearance_height = 25
extruder_clearance_radius = 55
extruder_colour = #FCE94F
extruder_offset = 0x0
extrusion_axis = E
extrusion_multiplier = 1
extrusion_width = 0.44
fan_always_on = 0
fan_below_layer_time = 100
filament_colour = #42BDD8
filament_cooling_final_speed = 3.4
filament_cooling_initial_speed = 2.2
filament_cooling_moves = 4
filament_cost = 20
filament_density = 1.24
filament_deretract_speed = nil
filament_diameter = 1.75
filament_infill_max_crossing_speed = 0
filament_infill_max_speed = 0
filament_load_time = 0
filament_loading_speed = 28
filament_loading_speed_start = 3
filament_max_volumetric_speed = 15
filament_minimal_purge_on_wipe_tower = 15
filament_multitool_ramming = 0
filament_multitool_ramming_flow = 10
filament_multitool_ramming_volume = 10
filament_notes = ""
filament_purge_multiplier = 100%
filament_ramming_parameters = "120 100 6.6 6.8 7.2 7.6 7.9 8.2 8.7 9.4 9.9 10.0| 0.05 6.6 0.45 6.8 0.95 7.8 1.45 8.3 1.95 9.7 2.45 10 2.95 7.6 3.45 7.6 3.95 7.6 4.45 7.6 4.95 7.6"
filament_retract_before_travel = nil
filament_retract_before_wipe = nil
filament_retract_layer_change = nil
filament_retract_length = nil
filament_retract_length_toolchange = nil
filament_retract_lift = nil
filament_retract_lift_above = nil
filament_retract_lift_below = nil
filament_retract_restart_extra = nil
filament_retract_restart_extra_toolchange = nil
filament_retract_speed = nil
filament_settings_id = PLA
filament_shrinkage_compensation_xy = 0%
filament_shrinkage_compensation_z = 0%
filament_soluble = 0
filament_spool_weight = 0
filament_stamping_distance = 0
filament_stamping_loading_speed = 20
filament_toolchange_delay = 0
filament_travel_lift_before_obstacle = nil
filament_travel_max_lift = nil
filament_travel_ramping_lift = nil
filament_travel_slope = nil
filament_type = PLA
filament_unload_time = 0
filament_unloading_speed = 90
filament_unloading_speed_start = 100
filament_vendor = Creality
filament_wipe = nil
fill_angle = 45
fill_density = 15%
fill_pattern = 3dhoneycomb
first_layer_acceleration = 0
first_layer_acceleration_over_raft = 0
first_layer_bed_temperature = 50
first_layer_extrusion_width = 0.42
first_layer_height = 0.2
first_layer_speed = 20
first_layer_speed_over_raft = 30
first_layer_temperature = 210
full_fan_speed_layer = 0
fuzzy_skin = none
fuzzy_skin_point_dist = 0.8
fuzzy_skin_thickness = 0.3
gap_fill_enabled = 1
gap_fill_speed = 30
gcode_comments = 1
gcode_flavor = marlin2
gcode_label_objects = firmware
gcode_resolution = 0.025
gcode_substitutions =
high_current_on_filament_swap = 0
host_type = prusalink
idle_temperature = 150
infill_acceleration = 0
infill_anchor = 600%
infill_anchor_max = 50
infill_every_layers = 1
infill_extruder = 1
infill_extrusion_width = 0.44
infill_first = 0
infill_overlap = 23%
infill_speed = 50
inherits_cummulative = "0.20 mm NORMAL (0.4 mm nozzle) @CREALITY";"Creality PLA @CREALITY";"Creality Ender-3 V2 (0.4 mm nozzle)"
interface_shells = 0
ironing = 0
ironing_flowrate = 10%
ironing_spacing = 0.1
ironing_speed = 20
ironing_type = top
layer_gcode = ;AFTER_LAYER_CHANGE\n;{layer_z}
layer_height = 0.2
machine_limits_usage = emit_to_gcode
machine_max_acceleration_e = 5000
machine_max_acceleration_extruding = 500
machine_max_acceleration_retracting = 1000
machine_max_acceleration_travel = 500
machine_max_acceleration_x = 500
machine_max_acceleration_y = 500
machine_max_acceleration_z = 100
machine_max_feedrate_e = 60
machine_max_feedrate_x = 500
machine_max_feedrate_y = 500
machine_max_feedrate_z = 10
machine_max_jerk_e = 5
machine_max_jerk_x = 8
machine_max_jerk_y = 8
machine_max_jerk_z = 0.4
machine_min_extruding_rate = 0
machine_min_travel_rate = 0
max_fan_speed = 100
max_layer_height = 0.32
max_print_height = 250
max_print_speed = 100
max_volumetric_extrusion_rate_slope_negative = 0
max_volumetric_extrusion_rate_slope_positive = 0
max_volumetric_speed = 0
min_bead_width = 85%
min_fan_speed = 0
min_feature_size = 25%
min_layer_height = 0.06
min_print_speed = 15
min_skirt_length = 20
mmu_segmented_region_interlocking_depth = 0
mmu_segmented_region_max_width = 0
multimaterial_purging = 140
notes =
nozzle_diameter = 0.4
only_one_perimeter_first_layer = 0
only_retract_when_crossing_perimeters = 0
ooze_prevention = 0
output_filename_format = [input_filename_base] [timestamp].gcode
overhang_fan_speed_0 = 0
overhang_fan_speed_1 = 0
overhang_fan_speed_2 = 0
overhang_fan_speed_3 = 0
overhang_speed_0 = 15
overhang_speed_1 = 15
overhang_speed_2 = 20
overhang_speed_3 = 25
overhangs = 1
parking_pos_retraction = 92
pause_print_gcode = M25 ; pause print
perimeter_acceleration = 0
perimeter_extruder = 1
perimeter_extrusion_width = 0.44
perimeter_generator = arachne
perimeter_speed = 40
perimeters = 2
physical_printer_settings_id =
post_process =
prefer_clockwise_movements = 0
print_host =
print_settings_id = Leonard
printer_model = ENDER3V2
printer_notes = Don't remove the following keywords! These keywords are used in the "compatible printer" condition of the print and filament profiles to link the particular print and filament profiles to this printer profile.\nPRINTER_VENDOR_CREALITY\nPRINTER_MODEL_ENDER3V2\nPRINTER_HAS_BOWDEN
printer_settings_id = Leonard
printer_technology = FFF
printer_variant = 0.4
printer_vendor =
printhost_apikey =
printhost_cafile =
raft_contact_distance = 0.1
raft_expansion = 0.5
raft_first_layer_density = 50%
raft_first_layer_expansion = 0
raft_layers = 0
remaining_times = 1
resolution = 0.025
retract_before_travel = 2
retract_before_wipe = 70%
retract_layer_change = 1
retract_length = 5
retract_length_toolchange = 1
retract_lift = 0
retract_lift_above = 0.2
retract_lift_below = 0
retract_restart_extra = 0
retract_restart_extra_toolchange = 0
retract_speed = 60
seam_position = nearest
silent_mode = 0
single_extruder_multi_material = 0
single_extruder_multi_material_priming = 0
skirt_distance = 1
skirt_height = 1
skirts = 1
slice_closing_radius = 0.005
slicing_mode = regular
slowdown_below_layer_time = 20
small_perimeter_speed = 25
solid_infill_acceleration = 0
solid_infill_below_area = 0
solid_infill_every_layers = 0
solid_infill_extruder = 1
solid_infill_extrusion_width = 0.44
solid_infill_speed = 40
spiral_vase = 0
staggered_inner_seams = 1
standby_temperature_delta = -5
start_filament_gcode = "; Filament gcode\n"
start_gcode = G90 ; use absolute coordinates\nM83 ; extruder relative mode\nM104 S{is_nil(idle_temperature[0]) ? 100 : idle_temperature[0]} ; set temporary nozzle temp to prevent oozing during homing\nM140 S{first_layer_bed_temperature[0]} ; set final bed temp\nG28 ; home all axis\nG1 Z1 F240\nG1 X2.0 Y10 F3000\nM190 S{first_layer_bed_temperature[0]} ; wait for bed temp to stabilize\nM109 S{first_layer_temperature[0]} ; set and wait for nozzle temp to stabilize\n;G1 Z0.28 F240\n;G92 E0\n;G1 X2.0 Y140 E10 F1500 ; prime the nozzle\n;G1 X2.3 Y140 F5000\n;G92 E0\n;G1 X2.3 Y10 E10 F1200 ; prime the nozzle\nG92 E0
support_material = 1
support_material_angle = 0
support_material_auto = 0
support_material_bottom_contact_distance = 0
support_material_bottom_interface_layers = -1
support_material_buildplate_only = 0
support_material_closing_radius = 2
support_material_contact_distance = 0.2
support_material_enforce_layers = 0
support_material_extruder = 0
support_material_extrusion_width = 0.36
support_material_interface_contact_loops = 0
support_material_interface_extruder = 0
support_material_interface_layers = 2
support_material_interface_pattern = rectilinear
support_material_interface_spacing = 0.2
support_material_interface_speed = 100%
support_material_pattern = rectilinear
support_material_spacing = 5
support_material_speed = 40
support_material_style = snug
support_material_synchronize_layers = 0
support_material_threshold = 20
support_material_with_sheath = 0
support_material_xy_spacing = 60%
support_tree_angle = 40
support_tree_angle_slow = 25
support_tree_branch_diameter = 2
support_tree_branch_diameter_angle = 5
support_tree_branch_diameter_double_wall = 3
support_tree_branch_distance = 1
support_tree_tip_diameter = 0.8
support_tree_top_rate = 15%
temperature = 210
template_custom_gcode =
thick_bridges = 1
thin_walls = 1
thumbnails = 512x512/PNG
thumbnails_format = PNG
toolchange_gcode =
top_fill_pattern = rectilinear
top_infill_extrusion_width = 0.4
top_one_perimeter_type = none
top_solid_infill_acceleration = 0
top_solid_infill_speed = 30
top_solid_layers = 3
top_solid_min_thickness = 0
travel_acceleration = 0
travel_lift_before_obstacle = 0
travel_max_lift = 0
travel_ramping_lift = 0
travel_slope = 0
travel_speed = 150
travel_speed_z = 0
use_firmware_retraction = 0
use_relative_e_distances = 1
use_volumetric_e = 0
variable_layer_height = 1
wall_distribution_count = 1
wall_transition_angle = 10
wall_transition_filter_deviation = 25%
wall_transition_length = 100%
wipe = 1
wipe_into_infill = 0
wipe_into_objects = 0
wipe_tower = 0
wipe_tower_acceleration = 0
wipe_tower_bridging = 10
wipe_tower_brim_width = 2
wipe_tower_cone_angle = 0
wipe_tower_extra_flow = 100%
wipe_tower_extra_spacing = 100%
wipe_tower_extruder = 0
wipe_tower_no_sparse_layers = 0
wipe_tower_rotation_angle = 0
wipe_tower_width = 60
wipe_tower_x = 170
wipe_tower_y = 140
wiping_volumes_matrix = 0
wiping_volumes_use_custom_matrix = 0
xy_size_compensation = 0
z_offset = 0

Same issue here, with even more sparse .gcode output. I confirmed the source .stl slices fine, produces sane .gcode and prints, directly in PrusaSlicer with the same profile. Below is what the Internal Slicer generates (literally just these 2 lines):
;Generated from 58mm net pot to 30mm starter plug adapter (3).tmp.1719924499127.stl (hash: 60a0ad417d214c5bd8998733d4cd6e790bfacf6c)
Here's my PrusaSlicer .ini file. Printer is a Crealty Ender 3:

arc_fitting = disabled
autoemit_temperature_commands = 1
avoid_crossing_curled_overhangs = 0
avoid_crossing_perimeters = 0
avoid_crossing_perimeters_max_detour = 0
bed_custom_model =
bed_custom_texture =
bed_shape = 0x0,235x0,235x235,0x235
bed_temperature = 52
before_layer_gcode =
between_objects_gcode =
binary_gcode = 0
bottom_fill_pattern = monotonic
bottom_solid_layers = 3
bottom_solid_min_thickness = 0
bridge_acceleration = 0
bridge_angle = 0
bridge_fan_speed = 100
bridge_flow_ratio = 1
bridge_speed = 60
brim_separation = 0
brim_type = no_brim
brim_width = 0
chamber_minimal_temperature = 0
chamber_temperature = 0
color_change_gcode = M600
colorprint_heights =
complete_objects = 0
cooling = 1
cooling_tube_length = 5
cooling_tube_retraction = 91.5
default_acceleration = 0
default_filament_profile =
default_print_profile =
deretract_speed = 0
disable_fan_first_layers = 3
dont_support_bridges = 1
draft_shield = disabled
duplicate_distance = 6
elefant_foot_compensation = 0
enable_dynamic_fan_speeds = 0
enable_dynamic_overhang_speeds = 0
end_filament_gcode = "; Filament-specific end gcode \n;END gcode for filament\n"
end_gcode = M104 S0 ; turn off temperature\nG28 X0  ; home X axis\nM84     ; disable motors\n
external_perimeter_acceleration = 0
external_perimeter_extrusion_width = 0.45
external_perimeter_speed = 50%
external_perimeters_first = 0
extra_loading_move = -2
extra_perimeters = 1
extra_perimeters_on_overhangs = 0
extruder_clearance_height = 20
extruder_clearance_radius = 20
extruder_colour = ""
extruder_offset = 0x0
extrusion_axis = E
extrusion_multiplier = 1
extrusion_width = 0.45
fan_always_on = 0
fan_below_layer_time = 60
filament_colour = #29B2B2
filament_cooling_final_speed = 3.4
filament_cooling_initial_speed = 2.2
filament_cooling_moves = 4
filament_cost = 18
filament_density = 0
filament_deretract_speed = nil
filament_diameter = 1.75
filament_infill_max_crossing_speed = 0
filament_infill_max_speed = 0
filament_load_time = 0
filament_loading_speed = 28
filament_loading_speed_start = 3
filament_max_volumetric_speed = 0
filament_minimal_purge_on_wipe_tower = 15
filament_multitool_ramming = 0
filament_multitool_ramming_flow = 10
filament_multitool_ramming_volume = 10
filament_notes = ""
filament_purge_multiplier = 100%
filament_ramming_parameters = "120 100 6.6 6.8 7.2 7.6 7.9 8.2 8.7 9.4 9.9 10.0| 0.05 6.6 0.45 6.8 0.95 7.8 1.45 8.3 1.95 9.7 2.45 10 2.95 7.6 3.45 7.6 3.95 7.6 4.45 7.6 4.95 7.6"
filament_retract_before_travel = nil
filament_retract_before_wipe = nil
filament_retract_layer_change = nil
filament_retract_length = nil
filament_retract_length_toolchange = nil
filament_retract_lift = nil
filament_retract_lift_above = nil
filament_retract_lift_below = nil
filament_retract_restart_extra = nil
filament_retract_restart_extra_toolchange = nil
filament_retract_speed = nil
filament_settings_id = "Crealty Ender 3"
filament_shrinkage_compensation_xy = 0%
filament_shrinkage_compensation_z = 0%
filament_soluble = 0
filament_spool_weight = 1000
filament_stamping_distance = 0
filament_stamping_loading_speed = 20
filament_toolchange_delay = 0
filament_travel_lift_before_obstacle = nil
filament_travel_max_lift = nil
filament_travel_ramping_lift = nil
filament_travel_slope = nil
filament_type = PLA
filament_unload_time = 0
filament_unloading_speed = 90
filament_unloading_speed_start = 100
filament_vendor = (Unknown)
filament_wipe = nil
fill_angle = 45
fill_density = 20%
fill_pattern = stars
first_layer_acceleration = 0
first_layer_acceleration_over_raft = 0
first_layer_bed_temperature = 52
first_layer_extrusion_width = 0.42
first_layer_height = 0.35
first_layer_speed = 60
first_layer_speed_over_raft = 30
first_layer_temperature = 205
full_fan_speed_layer = 0
fuzzy_skin = none
fuzzy_skin_point_dist = 0.8
fuzzy_skin_thickness = 0.3
gap_fill_enabled = 1
gap_fill_speed = 20
gcode_comments = 0
gcode_flavor = marlin2
gcode_label_objects = disabled
gcode_resolution = 0.0125
gcode_substitutions =
high_current_on_filament_swap = 0
host_type = prusalink
idle_temperature = nil
infill_acceleration = 0
infill_anchor = 600%
infill_anchor_max = 50
infill_every_layers = 1
infill_extruder = 1
infill_extrusion_width = 0.45
infill_first = 0
infill_overlap = 25%
infill_speed = 100
interface_shells = 0
ironing = 0
ironing_flowrate = 15%
ironing_spacing = 0.1
ironing_speed = 15
ironing_type = top
layer_gcode =
layer_height = 0.3
machine_limits_usage = time_estimate_only
machine_max_acceleration_e = 10000,5000
machine_max_acceleration_extruding = 1500,1250
machine_max_acceleration_retracting = 1500,1250
machine_max_acceleration_travel = 1500,1250
machine_max_acceleration_x = 9000,1000
machine_max_acceleration_y = 9000,1000
machine_max_acceleration_z = 500,200
machine_max_feedrate_e = 120,120
machine_max_feedrate_x = 500,200
machine_max_feedrate_y = 500,200
machine_max_feedrate_z = 12,12
machine_max_jerk_e = 2.5,2.5
machine_max_jerk_x = 10,10
machine_max_jerk_y = 10,10
machine_max_jerk_z = 0.2,0.4
machine_min_extruding_rate = 0,0
machine_min_travel_rate = 0,0
max_fan_speed = 100
max_layer_height = 0
max_print_height = 200
max_print_speed = 80
max_volumetric_extrusion_rate_slope_negative = 0
max_volumetric_extrusion_rate_slope_positive = 0
max_volumetric_speed = 0
min_bead_width = 85%
min_fan_speed = 35
min_feature_size = 25%
min_layer_height = 0.07
min_print_speed = 10
min_skirt_length = 0
mmu_segmented_region_interlocking_depth = 0
mmu_segmented_region_max_width = 0
multimaterial_purging = 140
notes =
nozzle_diameter = 0.4
only_one_perimeter_first_layer = 0
only_retract_when_crossing_perimeters = 0
ooze_prevention = 0
output_filename_format = [input_filename_base].gcode
overhang_fan_speed_0 = 0
overhang_fan_speed_1 = 0
overhang_fan_speed_2 = 0
overhang_fan_speed_3 = 0
overhang_speed_0 = 15
overhang_speed_1 = 15
overhang_speed_2 = 20
overhang_speed_3 = 25
overhangs = 1
parking_pos_retraction = 92
pause_print_gcode = M601
perimeter_acceleration = 0
perimeter_extruder = 1
perimeter_extrusion_width = 0.45
perimeter_generator = arachne
perimeter_speed = 120
perimeters = 3
physical_printer_settings_id =
post_process =
prefer_clockwise_movements = 0
print_host =
print_settings_id = Crealty Ender 3
printer_model =
printer_notes =
printer_settings_id = Crealty Ender 3
printer_technology = FFF
printer_variant =
printer_vendor =
printhost_apikey =
printhost_cafile =
raft_contact_distance = 0.1
raft_expansion = 1.5
raft_first_layer_density = 90%
raft_first_layer_expansion = 3
raft_layers = 0
remaining_times = 0
resolution = 0
retract_before_travel = 2
retract_before_wipe = 0%
retract_layer_change = 0
retract_length = 2
retract_length_toolchange = 10
retract_lift = 0
retract_lift_above = 0
retract_lift_below = 0
retract_restart_extra = 0
retract_restart_extra_toolchange = 0
retract_speed = 40
seam_position = aligned
silent_mode = 1
single_extruder_multi_material = 0
single_extruder_multi_material_priming = 1
skirt_distance = 6
skirt_height = 1
skirts = 0
slice_closing_radius = 0.049
slicing_mode = regular
slowdown_below_layer_time = 5
small_perimeter_speed = 50%
solid_infill_acceleration = 0
solid_infill_below_area = 70
solid_infill_every_layers = 0
solid_infill_extruder = 1
solid_infill_extrusion_width = 0.45
solid_infill_speed = 70%
spiral_vase = 0
staggered_inner_seams = 0
standby_temperature_delta = -5
start_filament_gcode = "; Filament gcode\n"
start_gcode = G28 ; home all axes\nG1 Z5 F5000 ; lift nozzle\n
support_material = 0
support_material_angle = 0
support_material_auto = 1
support_material_bottom_contact_distance = 0
support_material_bottom_interface_layers = -1
support_material_buildplate_only = 0
support_material_closing_radius = 2
support_material_contact_distance = 0.2
support_material_enforce_layers = 0
support_material_extruder = 1
support_material_extrusion_width = 0.35
support_material_interface_contact_loops = 0
support_material_interface_extruder = 1
support_material_interface_layers = 3
support_material_interface_pattern = rectilinear
support_material_interface_spacing = 0
support_material_interface_speed = 100%
support_material_pattern = rectilinear
support_material_spacing = 2.5
support_material_speed = 60
support_material_style = grid
support_material_synchronize_layers = 0
support_material_threshold = 0
support_material_with_sheath = 1
support_material_xy_spacing = 50%
support_tree_angle = 40
support_tree_angle_slow = 25
support_tree_branch_diameter = 2
support_tree_branch_diameter_angle = 5
support_tree_branch_diameter_double_wall = 3
support_tree_branch_distance = 1
support_tree_tip_diameter = 0.8
support_tree_top_rate = 15%
temperature = 205
template_custom_gcode =
thick_bridges = 1
thin_walls = 1
thumbnails =
thumbnails_format = PNG
toolchange_gcode =
top_fill_pattern = monotonic
top_infill_extrusion_width = 0.4
top_one_perimeter_type = none
top_solid_infill_acceleration = 0
top_solid_infill_speed = 75%
top_solid_layers = 3
top_solid_min_thickness = 0
travel_acceleration = 0
travel_lift_before_obstacle = 0
travel_max_lift = 0
travel_ramping_lift = 0
travel_slope = 0
travel_speed = 130
travel_speed_z = 0
use_firmware_retraction = 0
use_relative_e_distances = 0
use_volumetric_e = 0
variable_layer_height = 1
wall_distribution_count = 1
wall_transition_angle = 10
wall_transition_filter_deviation = 25%
wall_transition_length = 100%
wipe = 0
wipe_into_infill = 0
wipe_into_objects = 0
wipe_tower = 0
wipe_tower_acceleration = 0
wipe_tower_bridging = 10
wipe_tower_brim_width = 2
wipe_tower_cone_angle = 0
wipe_tower_extra_flow = 100%
wipe_tower_extra_spacing = 100%
wipe_tower_extruder = 0
wipe_tower_no_sparse_layers = 0
wipe_tower_rotation_angle = 0
wipe_tower_width = 60
wipe_tower_x = 180
wipe_tower_y = 140
wiping_volumes_matrix = 0
wiping_volumes_use_custom_matrix = 0
xy_size_compensation = 0
z_offset = 0

Post the log of the plugin, i had the same issue and it was just a missing library

@Edevige Any idea which dependency was missing? I'd be happy to help diagnose what's going on and try to further automate the installation process.
@jbishop129 @non-bin Could you try to slice a new file again and then download the OctoPrint log files?

OctoPrint Settings Menu -> System Info -> Download Systeminfo Bundle

@Garr-Garr it was libgtk-3, unfortunately i can't post my log to help you further.
Thank you for this project

yup, an apt install libgtk3.0-cil fixed it. Thanks!

yup, an apt install libgtk3.0-cil fixed it. Thanks!

Thank you for the update! Do you know which OctoPi version you're running? I think some newer versions must have that preinstalled since I haven't ran into this issue yet, but the systeminfo bundle would give me a better understanding:

OctoPrint Settings Menu -> System Info -> Download Systeminfo Bundle

env.plugins.pi_support.model: Raspberry Pi 4 Model B Rev 1.5
env.plugins.pi_support.octopi_camera_stack: webcamd
env.plugins.pi_support.octopi_version: 1.0.0
env.plugins.pi_support.octopiuptodate_build: 1.0.0-1.10.3-20241105092907
env.plugins.pi_support.octopiuptodate_build_short: 2<IP_ADDRESS>907
env.plugins.pi_support.throttle_check_enabled: True
env.plugins.pi_support.throttle_check_functional: True
env.plugins.pi_support.throttle_state: 0x0
env.python.pip: 22.3
env.python.version: 3.9.2
env.python.virtualenv: True
octoprint.last_safe_mode.date: 2024-09-06T19:20:34Z
octoprint.last_safe_mode.reason: settings
octoprint.safe_mode: False
octoprint.version: 1.10.3
systeminfo.generated: 2024-09-11T19:56:05Z
systeminfo.generator: zipapi


New release

Hey guys,
Could you please push a new release of the latest version to NPM? Last one is from the 12th of August.
Thanks!

Done: https://github.com/marmelab/admin-on-rest/releases/tag/v0.4.0

Yay! 🎉


[Path] Speed up bin generation when there are many files

Closes #2846, I presume.
\c @indirect

@homu r+ rollup

:pushpin: Commit faf7b5a has been approved by indirect

:hourglass: Testing commit faf7b5a with merge b3b14b6...

:sunny: Test successful - status


changes for sidecar env in operator manifests

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature Enhancement
[ ] Test Automation
[ ] Code Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Community Operator listing
[x] Other (please describe): Sidecar env changes

What is the current behavior?

Current behavior we have instruction in KC to add sidecar env

What is the new behavior?

Added sidecar env in operator manifests which would be helpful for customer doing airgap installation. Current change will help customers to edit values of those env's

How risky is this change?

[ ] Small, isolated change
[x] Medium, requires regression testing
[ ] Large, requires functional and regression testing

getting following error after applying : generated/installer/ibm-spectrum-scale-csi-operator.yaml Error from server (BadRequest): error when creating "sidecar/ibm-spectrum-scale-csi-operator.yaml": Deployment in version "v1" cannot be handled as a Deployment: strict decoding error: unknown field "spec.template.spec.containers[0].env[8].vale"

Issue resolved with latest change.


Wooden Slabs not being pulled when using Filter module

Using 1.9.3 of the mod and have noticed that when I have a High Filter Module 3 (haven't tested with other tiers) wooden slabs of varying kinds do not seem to be pulled through to the container even though they are in the allowed list. Other items in the list are being pulled through correctly but none of the wooden slabs I've tested are getting pulled.
If I put a container with no filter they get pushed out to that without a problem.
Stone and cobblestone slabs appear to be working fine when using a filter module.

I've actually just run into the same issue with White Sand too, which comes from the mod Oh The Biomes You'll Go. Don't think it's directly related to the mod though since at least some of the wooden slabs I tested with were vanilla variants.

So I'm not sure why but after a server restart this seems to have resolved itself. I ran into an issue where I couldn't get anything at all to move to a chest with a filter setup for the items to be allowed so I thought I'd try restarting and then that filter started working so I tested the others and they seem to be working now too.


fix: set content-carousel hero images to stretch with object-fit

I've been using a -SNAPSHOT with these changes for days -- looks good :+1:


Loosing Connections

Hi,
I'm facing some weird connection issues.
My setup is the following:

1 devicee behind an LTE router: clientA
1 server on some cloud service A clientB
1 server on some other cloud service B: server (runs innernet-server)

server has ufw configured:
26346                         ALLOW       Anywhere
Anywhere                   ALLOW       <IP_ADDRESS>/16
Anywhere                   ALLOW       <IP_ADDRESS>/8
51820                         ALLOW       Anywhere
Anywhere                   ALLOW       <IP_ADDRESS>/16
51820/udp                  ALLOW       Anywhere
26346 (v6)                  ALLOW       Anywhere (v6)
51820 (v6)                  ALLOW       Anywhere (v6)
51820/udp (v6)           ALLOW       Anywhere (v6)

<IP_ADDRESS>/16 is my innernet network.
clientB (innernet client) and server (innernet server) can see each other all the time.
But clientA is loosing the connection once about every 12 hours and can't seem to reconnect.
innernet fetch <network> also does not help
When I do the following steps on server:

ufw disable
innernet fech
ufw enable

The connection between clientA and server can be reestablished.
The connection will stay active for some time (usually multiple hours) until its getting lost again.
I suspect that the LTE router changes access points often. Could this be the case here?
What has this to do with my ufw config?
Any help or ideas to debug this are appreciated.

Out of curiosity, does doing innernet down <network> && innernet up <network> make any difference compared to innernet fetch <network>?
Also, it might be worth checking some basic things like the output of ip route before and after the connection seems to be working.

Wireguard has a "PersistentKeepalive" feature.  That's helped me a lot in my wireguard configs in the past (pre-innernet).  Like adding a line like "PersistentKeepalive = 25" at the end of my wireguard conf file, in the [Peer] section, worked.  That sends a KeepAlive packet every 25 seconds, ensuring the tunnel never gets closed of in any intermediary router.  These KeepAlive packets are small, amounting to only like 8MB in a month, for 1 client.
Your (behind-an-LTE-connection) client switching IP addresses would seemingly not matter, as wireguard (I can't speak for the magic which innernet additionally performs) can gracefully and transparently handle such changes.


focusedView is wrong when a webview is showing

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

VS Code Version: 1.82.3
OS Version: macOS 13.5

Steps to Reproduce:

add ${focusedView} to window.title (or inspect context keys and find focusedView)
open a webview in the sidebar. for example, the Copilot Labs extension
focusedView doesn't get reset when focusing on other things until you focus a different view. closing the sidebar, focusing an editor, etc. do not clear it.

cc @meganrogge

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.83.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

focusing an editor now says Text Editor. As for the webview case, I can consider fixing that.

actually, focusing a web view like a mardown document preview shows the correct thing for the focused view for me. Could you pls create a gif? I think this is working as designed


Storyboard

Hey there,
Just a quick question, I haven't tried to run the code yet but was wondering if this would work with Storyboard as well? I don't see any initWithCoder overrides, so I thought I'll ask.
Thanks

It certainly should. You might enjoy @Remki's work in #13.


Custom Operators: Documentation

It misses custom operators documentation. Where could we add it ?

(sorry I add theses issues really fast, just to don't forget them)


BLE Library - new iBeacon advertising server data issue on iPhone

I'm using Arduino IDE and I have imported only changes related to iBeacon by simply coping and overwriting BLEAdvertising.* BLEBeacon.* and BLEUUID.h inside Arduino libs.
Doing this way it compiles without any problem.
I used this code for server side iBeacons advertising:
https://pastebin.com/HYyGT5K2
Reading data with nRF Connect on iPhone it does not seems to be working as aspected.
After some info exchange we suspected the problem should be in iPhone data reading.
But may be there should be something else in arduino libs.
It should be interesting to understand where the issue can be using origina esp environment with an iPhone (do someone can tell me if I can install esp development environment without conflicts with the arduino one ?)
Here's raw data view in nRF Connect

Just a suggestion, but iPhone requires iBeacons to transmit all advertising packets on a minimum interval of 100ms and a maximum interval of 100ms.  We are kind of hard coded, it appears to me, at 32ms min and 64ms max.
I don't know if it really matters.

Im looking for tester with iPhone to test ideas i have about iBeacon who is willing to contact on private (IRC or email).

I'm at<EMAIL_ADDRESS> I have iPhone and iPad.
And ESP32 of course.

Let me know -I have those techs
Email<EMAIL_ADDRESS>Skype giaras
Inviato da iPhone

Il giorno 06 apr 2018, alle ore 13:45, chegewara<EMAIL_ADDRESS>ha scritto:
Im looking for tester with iPhone to test ideas i have about iBeacon who is willing to contact on private (IRC or email).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@chegewara - Do you still need help?

Sure, more tests = more ideas = better results.

What to do?

Ok, i will try to prepare bin file and post here asap.

Ita a first version, i hope its last ;)
Because github doesnt allow to upload bin files ive added .txt, you know what to do.
iBeacon_v1.bin.txt

https://github.com/beaconinside/awesome-beacon
Can i ask someone to test this app with iPhone and tell me if iBeacon created with it can be recognized?
https://play.google.com/store/apps/details?id=net.alea.beaconsimulator


Ensure mocks are created after proto update

Codecov Report

Merging #17 (cb564ef) into master (13c8520) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #17   +/-   ##
======================================
  Coverage    7.26%   7.26%
======================================
  Files           4       4
  Lines         234     234
======================================
  Hits           17      17
  Misses        216     216
  Partials        1       1

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 13c8520...cb564ef. Read the comment docs.


200 1 0 build fixes

Closes https://github.com/Esri/arcgis-maps-sdk-swift-toolkit/issues/200
This fixes the build, handling the removal of ObservableObject conformance by Map and Scene.  It adds a data model, one for Map-based objects and one for Scene.  Is the pattern used correct?  Is there a better way?

@philium - I'm interested in your opinion on the pattern here in regards to the data models and map/scene support.  This is related to https://devtopia.esri.com/runtime/swift/issues/3174.  Thanks!

A few thoughts:

The geo model property of each should be immutable
The utility of such a class will be fairly limited since it only stores a map. If anything else is needed (graphics overlay, portal, etc.), then a custom class will be needed
Because the implementation is so simple and straightforward, I would argue that it doesn't pull its own weight and therefore shouldn't be included as part of the toolkit. Instead, it should be in the Examples app itself.
Due to the standalone nature of samples, even if the classes were part of the toolkit's public API, I don't think that the samples app could use them. Does the same principle (keeping them as self-contained as possible) apply to toolkit examples?

@philium Thanks for the feedback.  A similar change will have to happen in the Swift Examples app.  Did you have a thought on how that would work?

The utility of such a class will be fairly limited since it only stores a map. If anything else is needed (graphics overlay, portal, etc.), then a custom class will be needed

I could create a model inside each example, but that would just duplicate a bunch of code.  I'm open to suggestions.

I could create a model inside each example, but that would just duplicate a bunch of code. I'm open to suggestions.

It would need to be in many places, but without doc it is what, seven lines of code? That's what I mean by it doesn't pull its own weight. It is so trivial to implement in the samples app (or in each example for that matter) that it isn't worth adding the public API of the toolkit. Anything new public API should be tested and needs to be maintained. I just don't think this meets the bar for inclusion.

@dfeinzimer I moved the data models to the Examples app, per @philium's recommendation; I did have to add a data model to the OverviewMap component which needed it.

@mhdostal - instead of the 2 classes, can't we just have one generic:
class GeoViewModel<T: GeoModel>: ObservableObject {
    let geoModel: T

    init(geoModel: T) {
        self.geoModel = geoModel
    }
}

And then have type aliases for the two geo model subclasses:
typealias MapViewModel = GeoViewModel<Map>
typealias SceneViewModel = GeoViewModel<Scene>


Fix capitalization of GitHub in translations

Spotted this while trying out the GitHub excellent web hook templates in the portal.

:heart:

Thank you for your contribution @niik 👍


fix: remove flex style from link

SUMMARY:
fix: remove flex style from link
GITHUB ISSUE (Open Source Contributors)
JIRA TASK (Eightfold Employees Only):
CHANGE TYPE:

[ ] Bugfix Pull Request
[ ] Feature Pull Request

TEST COVERAGE:

[ ] Tests for this change already exist
[ ] I have added unittests for this change

TEST PLAN:

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@33e516c). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #380   +/-   ##
=======================================
  Coverage        ?   89.35%
=======================================
  Files           ?      484
  Lines           ?    13071
  Branches        ?     4393
=======================================
  Hits            ?    11679
  Misses          ?     1370
  Partials        ?       22

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.


feat: Generate completions during build process

This commit adds a build.rs which generates completion files for Bash,
Elvish, Fish, and zsh shells. In order to accomplish this, the
build_cli command was moved into a separate module: cli. The CI
build script was also modified to package the four scripts into the
outputted build artifact.
One downside of pre-generating the completion scripts is that it won't
be able to take user-specified profiles, as those are dependent on each
system. That would require custom generations, and would probably no
longer able to be auto-generated with clap.
Note: I have not actually tested out the CI script yet. I would recommend doing that before merging this.
Fixes #53

@DSpeckhals nice to see we are close to have some decent packaging for various distro.
I think we should wait for #4  to be implemented before merging this.

It would also be good to update to do the update to clapv3 beforehand.
The way completion files are generated changed a bit with their v3 release, as there's now a dedicated crate for this functionality.

This MR is old and has conflicts. Is @DSpeckhals willing to pick this back up?

I think this can be closed as "done", as there's now a subcommand to generate auto-completions at all :)
(Maybe it was there before, but I didn't see them^^).
Moving them to the correct location in the system is indeed the distro packager's job

For the record, Arch has had those for quite some time now.


Pass server variables to internal request

In my API implementation I am trying to return some URLs generated with Laravel's route() helper. The problem is that Dispatcher does not pass server variables from actual request into the internal request and links generated with route() are quite random (pointing to http://localhost for example).
Is this ok to pass all actual server variables instead of the empty array? It would solve my problem.

I can't see it being an issue.

We'll wait and see what happens though. Cheers. :+1:

It shines when you are trying to use server variables or things like route() at internal request level. It solves my issue. Thanks. :)


[feature-request] Add charge-lnd by accumulator

Discussed in https://github.com/raspiblitz/raspiblitz/discussions/3955

Originally posted by DoktorWhat June 20, 2021
https://github.com/accumulator/charge-lnd
Description:
This script matches your open Lightning channels against a number of customizable criteria and applies channel fees based on the matching policy.

So the idea would be to crteate a bonus script like ./config.scripts/bonus.charge-lnd.sh that is based on bonus.template.sh (just without the need for a webui) that installs https://github.com/accumulator/charge-lnd in bitcoin user home with a config setup like:
echo "
[discourage-routing-out-of-balance]
chan.max_ratio = 0.1
chan.min_capacity = 250000
strategy = static
base_fee_msat = 2000
fee_ppm = 690

[encourage-routing-to-balance]
chan.min_ratio = 0.9
chan.min_capacity = 250000
strategy = static
base_fee_msat = 1000
fee_ppm = 21

[default-proportional]
chan.max_ratio = 0.9
chan.min_ratio = 0.1
chan.min_capacity = 250000
strategy = proportional
min_fee_ppm = 21
max_fee_ppm = 210
base_fee_msat = 2000
" >> /home/bitcoin/charge-lnd/charge.config

line="0 */6 * * * /home/bitcoin/charge-lnd/bin/charge-lnd -c /home/bitcoin/charge-lnd/charge.config"
(crontab -u $(whoami) -l; echo "$line" ) | crontab -u $(whoami) -

running it as a service.

PR #4594 ready to be tested & merged for v1.11.1rc1


Feature request: Add current download speed to progress bar

Hello, It would make easier to understand how fast i'm actually downloading.
We could also use something like https://github.com/dustin/go-humanize to make the downloaded size ,total size and speed more readable.
Let me know what you think.

@luckcolors Thanks your feedback!
Probably I implemented you want features at v0.1.0. Could you try this one?
Thanks.


Add metrics to track progress of replication from cloud.

Since a metric like replication lag in bytes is not possible from cloud, a metric that can be used to track replication progress from cloud can be the point of time up to which the local replica has caught up from the cloud replica. Below are considerations for implementing such a metric.
There are two options to emit metrics for recovery/vcr-replication progress

Progress is reported by the VCR that is the recovery source.
Progress is reported by the storage node itself that is recovering.

Progress Reported By Vcr
When a VCR gets a replica metadata request, then it can look at the token to see the lastUpdateTime (which needs to be added to the CloudFindToken) in the incoming token, and can add it to a metric called partition_<partitionid_datanodeid>_catchup_point. This metric is the time up to which the remote is caught up from the VCR.
A major assumption here is that one storage node recovers/replicates from only one VCR node. If there is a possibility of one storage node replicating from multiple VCR nodes (which basically doesn't make sense, since the source of data is same for all VCRs), then it will not be possible to determine which VCR node has most up to date progress. Since such a possibility is not expected, this assumption is expected to hold true.
A major issue with approach is that there will be no way to know when to drop the metrics from a VCR node. Since this happens in the request path, a VCR node will never be able to drop the metrics. Due to this issue, the next approach is a better approach to report progress.
Progress Reported by the Storage Node
Just like a storage node emits metrics for replicationLagInBytes, it can also emit metrics for replicationCatchupTime (time up to which a replica has caught up). The response of replica metadata exchange consists of an ordered list of MessageInfo, representing the metadata of a blob. The operation time of the last MessageInfo, can be used as the point in time up to which the local replica has caught up from cloud replica. While this information can be obtained for both replication from cloud as well as from store, it makes more sense to track this only for replication from cloud, because there will be three peer store replicas for a local replica, and it is difficult to determine how to merge the three catch up timestamps to get accurate information about catch up point (there can be a remote store peer replica, which is new, and is still catching up with the existing replicas. It will be far behind the other replicas). With the assumption that there will be only one cloud replica per local replica in a store, this approach can be used to track progress of replication from cloud, and hence progress of disaster recovery.
Due to the reasons above, approach 2 (progress reported by the storage node), is used to get the recovery progress metric.

Will merge once the build passes.
The PR description is very thorough - recommend adding it to the github project wiki if there's an appropriate place for it.

Codecov Report

Merging #1456 into master will decrease coverage by 0.02%.
The diff coverage is 88.00%.

@@             Coverage Diff              @@
##             master    #1456      +/-   ##
============================================
- Coverage     73.74%   73.71%   -0.03%
- Complexity     8102     8106       +4
============================================
  Files           569      569
  Lines         44465    44488      +23
  Branches       5622     5624       +2
============================================
+ Hits          32790    32794       +4
- Misses        10031    10042      +11
- Partials       1644     1652       +8

Impacted Files
Coverage Δ
Complexity Δ

...m/github/ambry/replication/ReplicationMetrics.java
91.17% <82.35%> (+0.07%)
52.00 <5.00> (+6.00)

...ry/replication/CloudToStoreReplicationManager.java
63.57% <100.00%> (+0.73%)
11.00 <0.00> (ø)

...va/com/github/ambry/replication/ReplicaThread.java
85.42% <100.00%> (-0.05%)
106.00 <0.00> (ø)

.../com/github/ambry/network/BlockingChannelInfo.java
80.95% <0.00%> (-3.18%)
16.00% <0.00%> (ø%)

...github/ambry/rest/AsyncRequestResponseHandler.java
87.87% <0.00%> (-2.36%)
21.00% <0.00%> (ø%)

...in/java/com/github/ambry/store/BlobStoreStats.java
69.21% <0.00%> (-1.66%)
101.00% <0.00%> (-2.00%)

.../java/com/github/ambry/router/DeleteOperation.java
93.75% <0.00%> (-1.39%)
45.00% <0.00%> (-1.00%)

...a/com/github/ambry/clustermap/ClusterMapUtils.java
92.57% <0.00%> (-0.50%)
48.00% <0.00%> (ø%)

.../main/java/com/github/ambry/store/HardDeleter.java
77.20% <0.00%> (-0.29%)
48.00% <0.00%> (-1.00%)

... and 3 more

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 d083432...d2367ca. Read the comment docs.


emit added for DELE and RMD command

we may need a acknowledge  of dele and rmd, for other purpose in my case in need it for S3 bucket update.

Thanks for the pull request!
Could we get a read me update to add these events too? It’s definitely important to keep track of the potential events that are available in the docs.


How do I make the opponent play an animation when bf hits a note?

Describe your problem here.
I am trying to make a bullet note mechanic and I want to make the opponent play a shooting animation like hank accelerant did.
I made bf play has dodging animaton when he hits a bullet note, but I am having trouble with the opponents animation
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

Use the same function but with 'dad' instead

opponentNoteHit

bf hits a note

triggerEvent('Play Animation', '< your animation name >', 'dad')

function goodNoteHit(noteType)
if noteType == note:String then
characterPlayAnim('dad', anim:String, forced:Bool = false);
end
end

function goodNoteHit(noteType)
    if noteType == 'Your_Note' then
        characterPlayAnim('dad', 'Your_Anim', false);
    end
end

function goodNoteHit(noteType)
    if noteType == 'Your_Note' then
        characterPlayAnim('dad', 'Your_Anim', false);
    end
end

You'd actually want to change false to true


#[reflect(ignore)] on enum variant is not supported without an error

On 0.9/main.
For enums
    #[derive(Reflect, InspectorOptions)]
    enum Test {
        #[reflect(ignore)]
        Variant(#[reflect(ignore)] f32),
    }

#[reflect(ignore)] on enum fields is supported, but not for enum variants.
But since the attributes are not even looked at in the derive macro, we don't get an error message.
bevy_reflect_derive should parse the attributes on variants, and error if it finds an unsupported reflect attribute.
Alternatively we an implement ignoring variants if we want that, but I don't know of a use case right now.

This would be fixed as part of https://github.com/bevyengine/bevy/pull/6297


FBI 2.4.8

Please help me, with me does not work FBI to 11.3 FW. When will work?

For it to work all you have to do is:

Sell your 11.3 3ds

Buy a 11.2 (or below) 3ds.

Follow 3ds.guide

???

Profit

You are using this incorrectly; you need a certain level of access in order to install titles, and basic homebrew (via the homebrew launcher) does not meet these requirements.

Me homebrew works on 11.3 but we do not like the FBI and I can not install CIA file.

Wait for a new kernel exploit or some other method of gaining additional access.