I have set deadLetterSink.uri for the Broker, but it still says that deadLetterSink is not set

Describe the bug
"Failed to send event to dead letter sink topic=knative-messaging-kafka.knative-eventing.my-sequence-demo1-kn-sequence-0 partition=0 offset=16","logger_name":"dev.knative.eventing.kafka.broker.dispatcher.impl.RecordDispatcherImpl","thread_name":"vert.x-worker-thread-19","level":"ERROR","level_value":40000,"stack_trace":"io.vertx.core.impl.NoStackTraceThrowable: No dead letter sink set\n","topic":"knative-messaging-kafka.knative-eventing.my-sequence-demo1-kn-sequence-0","partition":0,"offset":16}

Expected behavior
deadLetterSink.uri should receive data
To Reproduce
Knative release version
1.7
Additional context
broker yaml:
apiVersion: eventing.knative.dev/v1
kind: Broker
metadata:
  annotations:
    eventing.knative.dev/broker.class: Kafka
    eventing.knative.dev/creator: system:admin
    eventing.knative.dev/lastModifier: system:admin
    kafka.eventing.knative.dev/external.topic: my-knative-kafka-demo-topic
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"eventing.knative.dev/v1","kind":"Broker","metadata":{"annotations":{"eventing.knative.dev/broker.class":"Kafka","kafka.eventing.knative.dev/external.topic":"my-knative-kafka-demo-topic"},"name":"my-kafka-broker2","namespace":"knative-eventing"},"spec":{"config":{"apiVersion":"v1","kind":"ConfigMap","name":"kafka-broker-config","namespace":"knative-eventing"},"delivery":{"deadLetterSink":{"uri":"http://<IP_ADDRESS>:5104/handle-fail"}}}}
  creationTimestamp: "2022-09-19T07:47:10Z"
  finalizers:
  - brokers.eventing.knative.dev
  generation: 4
  managedFields:
  - apiVersion: eventing.knative.dev/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:finalizers:
          .: {}
          v:"brokers.eventing.knative.dev": {}
    manager: kafka-controller
    operation: Update
    time: "2022-09-19T07:47:10Z"
  - apiVersion: eventing.knative.dev/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:eventing.knative.dev/broker.class: {}
          f:kafka.eventing.knative.dev/external.topic: {}
          f:kubectl.kubernetes.io/last-applied-configuration: {}
      f:spec:
        .: {}
        f:config:
          .: {}
          f:apiVersion: {}
          f:kind: {}
          f:name: {}
          f:namespace: {}
        f:delivery:
          .: {}
          f:deadLetterSink: {}
    manager: kubectl-client-side-apply
    operation: Update
    time: "2022-09-20T01:37:16Z"
  - apiVersion: eventing.knative.dev/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:spec:
        f:delivery:
          f:deadLetterSink:
            f:uri: {}
    manager: kn.exe
    operation: Update
    time: "2022-09-20T02:01:06Z"
  - apiVersion: eventing.knative.dev/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:status:
        .: {}
        f:address:
          .: {}
          f:url: {}
        f:annotations:
          .: {}
          f:bootstrap.servers: {}
          f:default.topic.partitions: {}
          f:default.topic.replication.factor: {}
        f:conditions: {}
        f:deadLetterSinkUri: {}
        f:observedGeneration: {}
    manager: kafka-controller
    operation: Update
    subresource: status
    time: "2022-09-20T02:13:04Z"
  name: my-kafka-broker2
  namespace: knative-eventing
  resourceVersion: "864447"
  uid: c9ad6d1d-e255-4ea4-b909-7db83b0c5bca
spec:
  config:
    apiVersion: v1
    kind: ConfigMap
    name: kafka-broker-config
    namespace: knative-eventing
  delivery:
    deadLetterSink:
      uri: http://<IP_ADDRESS>:5104/handle-fail
status:
  address:
    url: http://kafka-broker-ingress.knative-eventing.svc.cluster.local/knative-eventing/my-kafka-broker2
  annotations:
    bootstrap.servers: <IP_ADDRESS>:9092
    default.topic.partitions: "1"
    default.topic.replication.factor: "1"
  conditions:
  - lastTransitionTime: "2022-09-19T07:47:52Z"
    status: "True"
    type: Addressable
  - lastTransitionTime: "2022-09-19T07:47:51Z"
    reason: Config map knative-eventing/kafka-broker-brokers-triggers updated
    status: "True"
    type: ConfigMapUpdated
  - lastTransitionTime: "2022-09-19T07:47:10Z"
    status: "True"
    type: ConfigParsed
  - lastTransitionTime: "2022-09-19T07:47:10Z"
    status: "True"
    type: DataPlaneAvailable
  - lastTransitionTime: "2022-09-20T02:13:04Z"
    status: "True"
    type: ProbeSucceeded
  - lastTransitionTime: "2022-09-20T02:13:04Z"
    status: "True"
    type: Ready
  - lastTransitionTime: "2022-09-19T07:47:51Z"
    reason: Topic my-knative-kafka-demo-topic created
    status: "True"
    type: TopicReady
  deadLetterSinkUri: http://<IP_ADDRESS>:5104/handle-fail
  observedGeneration: 4

trigger yaml:
apiVersion: eventing.knative.dev/v1
kind: Trigger
metadata:
  annotations:
    eventing.knative.dev/creator: system:admin
    eventing.knative.dev/lastModifier: system:admin
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"eventing.knative.dev/v1","kind":"Trigger","metadata":{"annotations":{},"name":"my-kafka-trigger-demo1","namespace":"knative-eventing"},"spec":{"broker":"my-kafka-broker2","subscriber":{"ref":{"apiVersion":"flows.knative.dev/v1","kind":"Sequence","name":"my-sequence-demo1"}}}}
  creationTimestamp: "2022-09-19T10:23:40Z"
  finalizers:
  - kafka.triggers.eventing.knative.dev
  generation: 2
  labels:
    eventing.knative.dev/broker: my-kafka-broker2
  managedFields:
  - apiVersion: eventing.knative.dev/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:finalizers:
          .: {}
          v:"kafka.triggers.eventing.knative.dev": {}
    manager: kafka-controller
    operation: Update
    time: "2022-09-19T10:23:40Z"
  - apiVersion: eventing.knative.dev/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .: {}
          f:kubectl.kubernetes.io/last-applied-configuration: {}
      f:spec:
        .: {}
        f:broker: {}
        f:subscriber:
          .: {}
          f:ref:
            .: {}
            f:apiVersion: {}
            f:kind: {}
            f:name: {}
    manager: kubectl-client-side-apply
    operation: Update
    time: "2022-09-19T10:59:40Z"
  - apiVersion: eventing.knative.dev/v1
    fieldsType: FieldsV1
    fieldsV1:
      f:status:
        .: {}
        f:conditions: {}
        f:deadLetterSinkUri: {}
        f:observedGeneration: {}
        f:subscriberUri: {}
    manager: kafka-controller
    operation: Update
    subresource: status
    time: "2022-09-20T02:13:04Z"
  name: my-kafka-trigger-demo1
  namespace: knative-eventing
  resourceVersion: "864448"
  uid: b1740f60-e442-429a-8b56-97f1cad6ab43
spec:
  broker: my-kafka-broker2
  filter: {}
  subscriber:
    ref:
      apiVersion: flows.knative.dev/v1
      kind: Sequence
      name: my-sequence-demo1
      namespace: knative-eventing
status:
  conditions:
  - lastTransitionTime: "2022-09-20T02:13:04Z"
    status: "True"
    type: BrokerReady
  - lastTransitionTime: "2022-09-20T01:37:16Z"
    status: "True"
    type: DeadLetterSinkResolved
  - lastTransitionTime: "2022-09-19T10:23:40Z"
    status: "True"
    type: DependencyReady
  - lastTransitionTime: "2022-09-20T02:13:04Z"
    status: "True"
    type: Ready
  - lastTransitionTime: "2022-09-19T10:23:40Z"
    message: 'Subscriber will receive events with the delivery order: UNORDERED'
    reason: SubscriberResolved
    status: "True"
    type: SubscriberResolved
  - lastTransitionTime: "2022-09-19T10:23:40Z"
    status: "True"
    type: SubscriptionReady
  deadLetterSinkUri: http://<IP_ADDRESS>:5104/handle-fail
  observedGeneration: 2
  subscriberUri: http://my-sequence-demo1-kn-sequence-0-kn-channel.knative-eventing.svc.cluster.local

Hi @qzwzqty, thanks for opening this issue!
That log line is referring to your sequence that is referenced by the trigger subscriber:
 # ...
  subscriber:
    ref:
      apiVersion: flows.knative.dev/v1
      kind: Sequence
      name: my-sequence-demo1
      namespace: knative-eventing

can you please post the definition of the sequence? and possibly also related KafkaChannels associated with the sequence (the Sequence API creates Channels for delivery and routing events)?

@pierDipi I know how to configure the sequence's deadLetterSink.
apiVersion: flows.knative.dev/v1
kind: Sequence
metadata:
  name: my-sequence-demo1
  namespace: knative-eventing
spec:
  channelTemplate:
    apiVersion: messaging.knative.dev/v1beta1
    kind: KafkaChannel
  steps:
    - uri: http://<IP_ADDRESS>:5104/test1
      delivery:
        deadLetterSink:
          uri: http://<IP_ADDRESS>:5104/handle-fail
    - uri: http://<IP_ADDRESS>:5104/test2
      delivery:
        deadLetterSink:
          uri: http://<IP_ADDRESS>:5104/handle-fail
    - uri: http://<IP_ADDRESS>:5104/test3
      delivery:
        deadLetterSink:
          uri: http://<IP_ADDRESS>:5104/handle-fail
  reply:
    ref:
      kind: Broker
      apiVersion: eventing.knative.dev/v1
      name: default-kafka

Can change the default to trigger or broker's deadLetterSink?

No, you have to do it manually

@pierDipi OK, Thanks


ci: set only image name as lowercase, leave image tag untouched

Change image name to lowercase but leave the optional tag untouched
Signed-off-by: Paolo Chila<EMAIL_ADDRESS>

@Raffy23 what's your take on this?
IMO we are now fixing the fix for the fix of "uppercase names in Docker image names", which we seem to be preventing in keptn-service-template-go anyway:

I would prefer to not fix this issue, but revert to the original implementation (which was changed with this PR):
https://github.com/keptn/gh-automation/pull/15/files

We can revert to the previous implementation, until we find a better way of normalizing tags. I'm currently not sure what kind of unintended behavior is introduced by this change (e.g.: A registry with a port will probably not work anymore). But if we do, we also have to document somewhere that GitHub accounts with any uppercase letters can not use this action + any other action that depends on it ...

Reverting to the old behavior of not checking the input would break configurations that use
        TAGS: |
            ghcr.io/${{ github.repository_owner }}/${{ env.IMAGE }}:${{ env.VERSION }}
            ghcr.io/${{ github.repository_owner }}/${{ env.IMAGE }}:${{ env.VERSION }}.${{ env.DATETIME }}

which would require us to change the README.
Also, I just looked at service-template, we will also break it there, because I only tested it with upper case service name, but not repository/organization owner :(
          TAGS: |
            ghcr.io/${{ github.repository_owner }}/${{ env.IMAGE }}:${{ env.VERSION }}

I digged a little bit deeper, and found a Troubleshooting guide of build-push-action, which provides another example of fixing this:
- name: Sanitize repo slug
  uses: actions/github-script@v4
  id: repo_slug
  with:
    result-encoding: string
    script: return 'ghcr.io/${{ github.repository }}'.toLowerCase()

- name: Build and push
  uses: docker/build-push-action@v2
  with:
    context: .
    push: true
    tags: ${{ steps.repo_slug.outputs.result }}:latest

Nevertheless, I'm seeing many problems appear with uppercased names on GitHub repos vs. GHCR, therefore I'm willing to accept this PR for now (it doesn't make it worse, it improves the 99% case/golden path, it just doesn't solve all edge cases).
I will provide an issue in keptn-service-template-go to handle upper-case owner names better.


git: 2.27.0 -> 2.28.0

Motivation for this change
Git 2.28 adds several new features. Announcement<EMAIL_ADDRESS>Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build gitFull

Pushed as d42bcde652ed0f19c04c71cc2d70e7d395739b38.


[Dialog] Dialog does throw Error in v0.15.0.beta.1

I copy the Simple dialog to my meteor-1.3.1 app source. Errors as follows:
Missing class properties    transform.
Somebody also met the error here?

Please follow the issue template properly

@hobartwang - please google "Missing class properties transform meteor', and come back if you still have a problem, and can demonstrate the issue is with Material-UI.

Ok,thanks


Better details on pool and queues in the logs

Better details on pools and queues in the log. How full is full? Are these configurable?
WARN [2015-10-22 05:10:18,227] pool-8-thread-1 - io.cyanite.engine.queue queue is full

This could be related to the issue with clojure.lang.ExceptionInfo: invalid carbon line: NaN metric spamming the worker pool.

Hi @jshook,
This will soon be added to the documentation and I will provide better defaults for the queue sizes.
I added hints as to what values to use there:
https://github.com/pyr/cyanite/issues/121#issuecomment-145795928

this issue is made irrelevant by #174


From UI users can delete  output or clusterOutput which are in use in flow or clusterflow in logging

On master-head, 5da52c0

Created a logging output, output1
Created a flow using the output, called flow1
Later issue a delete from UI to delete the output1 which is in use in flow1.
UI deleted the output1, now flow1 is active with a non-existent output, output1

The same behavior also exists in clusteroutputs and clusterflows.
Expected behavior:
We need to prevent deleting in use output and clusteroutput.

Instead of preventing delete, we should highlight if a flow references an output that doesn't exist.
We should use the same UI as we have for when looking for services that don't exist.
Trying to prevent the delete could be load intensive if there are lots of flows to check if a specific output or clusteroutput so let's highlight the reference to an orphaned object.

Instead of preventing delete, we should highlight if a flow references an output that doesn't exist.
We should use the same UI as we have for when looking for services that don't exist.
Trying to prevent the delete could be load intensive if there are lots of flows to check if a specific output or clusteroutput so let's highlight the reference to an orphaned object.

Verified on 2.5-head, commit id 3d62d5d

Created a logging output, output1
Created a flow using the output, called flow1
Later issue a delete from UI to delete the output1 which is in use in flow1.
UI deleted the output1, now flow1 is active with a non-existent output, output1

With the fix, if users hover the mouse over the output1 in flow's detail page, users can see the info message that the output object doesn't exist.

Repeated the test for clusterflow, clusteroutput

Verified on 2.5-head, commit id 3d62d5d

Created a logging output, output1
Created a flow using the output, called flow1
Later issue a delete from UI to delete the output1 which is in use in flow1.
UI deleted the output1, now flow1 is active with a non-existent output, output1

With the fix, if users hover the mouse over the output1 in flow's detail page, users can see the info message that the output object doesn't exist.

Repeated the test for clusterflow, clusteroutput


dump-config task is using the wrong secret

Describe the bug
When a dump-config tekton task is run, it is unable to start since it is trying to read the wrong secret. It is reading peribolos-$(params.INSTALLATION-ID) instead of $(params.SECRET_NAME).
To Reproduce
Steps to reproduce the behavior:

Install the app on in a new organization
Check the logs of the dump-config TaskRun

Expected behavior
It should read the correct secret.

/assign

Bug resolved.
/close


-keep-parent is default for move?

In
drive move -id id 'path'
the file remains in "My Drive", i.e. does a "-keep-parent".
Am I misunderstanding anything?

Hello @bjohas, thank you for creating this issue and great to see you here in 2018. @lbsx welcome to drive and thanks for the input.
@bjohas my apologies am reiterating stuff you already know about but, drive move requires a src and destination, in your case --id would be the source, 'path' would be the destination.
-keep-parent ensures that a file/folder can exist in more than one parent folder e.g
if my file is in b1/b2
drive move --keep-parent --id <id> b1/b2/foo txy

at the end, the target file will exist in both b1/b2 and txy

Also, is there a way of creating a file in a folder, without this folder existing locally?

drive new --folder folderpath

Also, is it possible to specify the target folder by id?

The current command is not expressive enough for this, it just uses a path.
Hope this helps.

@odeke-em, and many thanks for answering my many questions about your excellent  piece of software, as well as my apologies for not reading the docs properly!
I'll try this out, and will report back - many thanks!

Hello again,
For me, "drive list test_folder" works, but if I say
drive move -id ABC 'test_folder'
I get this error: move: ABC: dest: '/test_folder/test_folder' remote path doesn't exist.
However, the file is moved.
Strangely, for a newly created file, the file only appears in 'test_folder' (i.e. My Drive/test_folder). However, If move the file again:
drive move -id ABC 'test_folder/test'
the file is now in both test_folder and test_folder/test (without using -keep-parent).
Is this all as expected?


In the process of generating kernel, you may be forget to use BN and Relu activate function, as descibed in paper.

kernel = self.span_mapping(self.reduce_mapping(self.o_mapping(input)))
after self.reduce_mapping(), need use activate function.

Hi, thanks for indicating this issue you are completely right. Let me fix this issue fast.


[RFC] Question about 3-layer FL

Hello,
I am trying to do some work with Meta-FL and have some questions about how this might work with plato. I was informed by my supervisor that you had mentioned in a presentation of Plato that 3-layer federated learning is supported. I am new to FL, and I am trying to figure out if that is through the cross-silo options or has to do with institutions. In either case, I feel there is some lack of documentation. Any clarification would be greatly appreciated!
Thanks
-Justin

You can use the sample configuration file to run a training session of three-layer federated learning:
./run -c configs/MNIST/fedavg_cross_silo_lenet5.yml
Configurable parameters of three-layer federated learning can be found at:
https://platodocs.netlify.app/configuration.html


Refactor ProcedureCache to support get_by_hash

We should change ProcedureCache into a real struct. One reason for this is that we'd want to be able to look up procedures by two things: procedure ID and procedure MAST root.
The interface could look something like:
impl ProcedureCache {

    pub fn insert(&mut self, proc: Procedure) {
        todo!()
    }

    pub fn get_by_id(&self, id: ProcedureId) -> Option<&Procedure> {
        todo!()
    }

    pub fn get_by_hash(&self, root: RpoDigest) -> Option<&Procedure> {
        todo!()
    }

   pub fn contains_id(&self, id: ProcedureId) -> bool {
        todo!()
    }

    pub fn contains_hash(&self, root: RpoDigest) -> bool {
        todo!()
    }

   pub fn values(&self) -> btree_map::Values {
       todo!()
   }
}

This let us support call.<MAST root> instruction - thought, we'd probably also need to update how Callset works as well.
Please see #895 for more context.

Closed by #911.


Maistra 2.4

Initial sync of Maistra proxy 2.4 with istio upstream 1.16.

Need to update WORKSPACE ENVOY_SHA
Need to add vendor folder.

Redundant.


Is a generic newtype possible?

Is it possible to create a generic newtype with nutype? When I do, let's say:
use nutype::nutype;

#[nutype(validate(predicate = |v| !v.is_empty()))]
struct NonEmptyVec<T>(Vec<T>);

I get:
 --> src/main.rs:4:27
  |
4 | struct NonEmptyVec<T>(Vec<T>);
  |                           ^ not found in this scope
  |
help: you might be missing a type parameter
  |
4 | struct NonEmptyVec<T><T>(Vec<T>);
  |                   +++

Hi @atezet
It's not possible at the moment.
But I have this in mind and want to make it possible in the future.

I already like using the library as-is a lot, but definitely looking forward to that! Thanks

@atezet Btw, if you need only non empty vector, I recommend taking a look at nonempty: https://github.com/cloudhead/nonempty

Thanks for the suggestion! We tried that at first, and iirc it worked for the cases where we needed a vector, but we also need IndexMap and some others. Unfortunately nonempty only supports Vec, even though its name would suggest otherwise.
I also suggested just using nutype and fixing the type of the stored values, but my colleague went ahead and implemented a newtype wrapping a generic Iterator for now.
Would love to see this to be possible with nutype or nonempty.

The basics implementation to support generics is merged in https://github.com/greyblake/nutype/pull/135
There some corner cases that need to be addressed before a new version can be published, see generics label.
@atezet If would appreciate if you can try the current implementation out and let me know if there something else missing!

Hey there, I just briefly checked out the interface (no time to check the code), and my example works as expected! I think your observations regarding support for trait bounds and auto derives are very correct. It would be cool if something like (there are better predicates to do this):
#[nutype(validate(predicate = |i| i.into_iter().count() != 0))]
struct NonEmpty<T: IntoIterator>(T);

would work as well, but that should be covered by #142

@atezet Hi, thanks for the feedback!

@atezet I just finished the work with generics and published  0.4.3-beta.1.  Let me know if that works for you.
I am planning to release 0.4.3 in a week.

@atezet So in 0.4.3 it's possible to use generics and to set type bounds.
However, to properly implement your use case it would require setting type bounds with where clause (this one is not supported yet):
#[nutype(
    validate(predicate = |c| c.into_iter().next().is_some()),
)]
struct NonEmpty<C>(C)
where
    for<'a> &'a C: IntoIterator;

The problem here is that we need to set the &C: IntoIterator boundary, but within <C> it's only possible to set the boundary on C, (not &C).
As a workaround, it's possible to clone. But of course it's not optimal from the performance perspective:
#[nutype(
    validate(predicate = |c| c.clone().into_iter().next().is_some())
)]
struct NonEmpty<C: Clone + IntoIterator>(C);

@atezet I've found a good solution for you.
We can introduce a helping IsEmpty trait and with that workaround limitation without  cloning:
use nutype::nutype;

trait IsEmpty {
    fn is_empty(&self) -> bool;
}

impl<T> IsEmpty for T
where
    for<'a> &'a T: IntoIterator,
{
    fn is_empty(&self) -> bool {
        self.into_iter().next().is_none()
    }
}

#[nutype(
    validate(predicate = |c| !c.is_empty()),
)]
struct NonEmpty<C: IsEmpty>(C);

fn main() {
    let number_vector = NonEmpty::try_new(vec![1, 2, 3]).unwrap();

    let chars: std::collections::BTreeSet<char> = "abc".chars().collect();
    let char_set = NonEmpty::try_new(chars).unwrap();
}

Hi @greyblake. Sorry for not replying earlier. We're in a final sprint before the code is audited, so I've some quite busy times and will look at using your solution in the next phase. Thanks for putting in the work, I think it looks quite clean already! I really like what nutype can do for typesafe type driven development with minimal boilerplate

@atezet No worries! Good luck with the sprint!
Looking forward for any feedback from you, if you'll have any.


ASC-1042 Enable multiple system actions

This commit modifies the match for the 'system' gating action. Any
action that begins with the string 'system' will be matched. This is
done to allow multiple variants of the system action to be defined in CI
in order to segment jobs.
Issue: ASC-1042

Thank you for submitting a pull request to this project!
Once all check jobs have passed and the pull request has received a
sufficient number of reviews, the repository's gate jobs can be triggered by
adding a comment of :shipit: to this pull request.
When the gate jobs have completed successfully, this pull request will get
merged automatically.


text-wrap: balance

text-wrap: balance
http://dev.w3.org/csswg/css-text-4/#valdef-text-wrap-balance
http://blogs.adobe.com/webplatform/2013/01/30/balancing-text-for-better-readability/

This issue was imported from Google Moderator
Moderator votes: +3
Issue added by medmunds on 2015-03-31
To vote this issue up or down, simply include +1 or -1 in your comment.

Covered by #1064?

Yup.


Add hollows_hunter

hollows_hunter is a process analysis tool that can be used to recognize and dump malicious implants such as shellcodes, hooks, etc:
https://github.com/hasherezade/hollows_hunter

It's there. :)


[1846] add change age range link

Context
Course age range
Changes proposed in this pull request
Add the "change" link
Guidance to review
🚢

 Edit 'Age Range' - (MCFE)


Docker build does not use Proxy from Docker Daemon

Hi,
i have set a proxy for the docker daemon in my systemd start file, this works well, i can search and pull from the puplic index
But if i try to build a Dockerfile, the proxy setting is not used, i need to set the proxy in the Dockerfile, but this is not a good idea as it is not portable.
docker 0.11.1 and 1.0.0
regards f0

closing as dup of https://github.com/docker/docker/issues/4962


chore(Dependencies) : update scalikejdbc-streams from 3.5.0 to 4.3.1

About this PR
📦 Updates org.scalikejdbc:scalikejdbc-streams from 3.5.0 to 4.3.1 ⚠
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalikejdbc", artifactId = "scalikejdbc-streams" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalikejdbc", artifactId = "scalikejdbc-streams" }
}]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #752.


specification not printing in alphabetical order

This is the output that is produced when a yaml file is created using Jackson ObjectMapper's mapper.writer.
As you can see, the messages key is below and the schemas key is above. Nevertheless, if I put this in the asyncapi parser, there won't be any errors. Yet, isn't it lovely to have it generally in a standard asyncapi specification? (messages key to be above  and schemas key to be below).
If someone can look at this, it would be wonderful, this is not just related to messages and schemas.. there also had some ordering problems in different keys as well. The reason I'm assuming this is where the variables declare order .. (attached an image). As you can see schemas variable has been declared above the messages variable.  or it would be the case in modelwriter(attached an image). but I'm not certain.

**variable declare order**

**model writer**
thank you

In the most recent version of this library, the ordering of properties in the output should be based on the order they are defined in the specification.  If that is not happening then it's a bug.  This applies for standard ordering of properties listed in the specification, not collections of entities. For collections, the ordering should be preserved based on the input file.

In the most recent version of this library, the ordering of properties in the output should be based on the order they are defined in the specification. If that is not happening then it's a bug. This applies for standard ordering of properties listed in the specification, not collections of entities. For collections, the ordering should be preserved based on the input file.

Hello @EricWittmann ,
As you can see even if I try to set message prior to schema using a setter, it doesn't print in the order what I am setting it. Is this wrong?

@EricWittmann  Yeah yeah I got it


Cluster-Autoscaler: Write status to configmap

This change is

/approve
/lgtm

@k8s-bot test this please

/lgtm

!!! 'gofmt -s' needs to be run on the following files:
./cluster-autoscaler/core/static_autoscaler.go

/approve
/lgtm


add log tailing to logfetch tool

@tpetr @wsorenson
This will add the ability to tail logs for a request, task, or request/deploy when the --tail option is specified with a logfile path (ie. 'logs/access.log'). It will also take the -g grep option and pas that through to the api as well.
If --tail isn't specified the tool will download and grep as before.

what happens then a request churns through tasks (i.e. OOM kill / misc. failure / bounce / deploy)? right now we won't pick up new tasks -- if we're cool with that, we need to make it very clear in the docs

i'd almost prefer to have a 2nd entrypoint (logtail) instead of the --tail arg, which completely changes the functionality of the program

I've made logtail it's own entrypoint and reworked the threading a bit, we were using -t for the taskId already so for right now I made -l the logfile name to tail

re: https://github.com/HubSpot/Singularity/pull/383#issuecomment-69087139 -- totally overlooked -t being for task id, right

Tailing should be all set now, I've trimmed the arguments down to just the IDs, logfile, and grep string (along with the base uri/conf file stuff). I left the logfile arg as giving an error message if it is not set.


Eyedropper: noticeable latency after clicking the icon

Bug Description
Discovered in bug-bash.
From Will:

noticeable, confusing ~1s latency after clicking the eye dropper and before the color overlay appears — a loading indicator/spinner would help!

Expected Behaviour

Steps to Reproduce

Screenshots

Additional Context

Plugin Version:
WordPress Version:
Operating System:
Browser:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Verified in QA (spinner appearing)


[api-docs] Corrects slash command name regex (lowercase only)

A new commit was made into the api-docs repo. This issue was created automatically. Need to review if we made any change to the library for this commit.
https://github.com/discord/discord-api-docs/commit/becdeec4ada23282fdc1b83139436c1e030324d8

Done


https://www.jplist.org/ does not seem to be working

I cannot get into https://www.jplist.org/. The browser and Kaspersky keep telling me there is an error with the encrypted connection.
Do others have the same problem?

The response I get is
This site can’t provide a secure connection
jplist.org sent an invalid response.


add full screen support for IE and fix full screen event bug for Firefox

为 IE 加上全屏支持；
修复 Firefox 无法触发 fullscreen / fullscreen_cancel 事件的 bug。

后者的原因是 Firefox 不支持给元素绑定 fullscreenchange 事件，仅支持给 document 绑定。

Merged, thanks!

两位，打扰一下，为啥有两个msfullscreenchange注册？大小写不同会照成问题吗？
https://github.com/MoePlayer/DPlayer/commit/a6f10f35b5f7cf0665568d6bfa2f7ec895770b14#diff-848f04249cd3c530a0380222f7b06b67R43
https://github.com/MoePlayer/DPlayer/commit/a6f10f35b5f7cf0665568d6bfa2f7ec895770b14#diff-848f04249cd3c530a0380222f7b06b67R44

@kn007 As far as I've tested in IE 11, the events seems to be spelled as msfullscreenchange.
And IE10 doesn't support the event.

谢谢~了解了

@kn007 IE 11 和 IE 以下的版本大小写不同

https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/dev-guides/dn265028(v%3Dvs.85)
Microsoft doesn't mention the fullscreen API until IE11.
Does IE10 really support the fullscreen API?

@Copay 嗯，那可能是我记错了。不是 IE 11 和 IE 10 的区别，是 IE 11 的小版本或者 Windows 版本的区别，网络上表示大写能用小写不能用，和小写能用大写不能用的人都有。

warning  'fullEle' is never reassigned. Use 'const' instead  prefer-const
warning  Expected space(s) after "if"                        keyword-spacing
warning  Missing space before opening brace                  space-before-blocks
warning  Expected space(s) after "if"                        keyword-spacing
warning  Missing space before opening brace                  space-before-blocks
warning  Missing semicolon                                   semi
warning  Expected space(s) after "if"                        keyword-spacing
warning  Missing space before opening brace                  space-before-blocks
warning  Missing space before opening brace                  space-before-blocks

hmm，很多细节模式没处理


OrbitControl plugin - Zoom is not working on Firefox

OS: Windows 10.1709 (64 bits)
Browser: Firefox 59.0.2 (64 bits)
ClayGL: 1.2.0
First, thanks for your great library!
I have an issue with orbit control:
Zoom does'nt work on Firefox. I found this error in console but don't know if it's related: Error: WebGL warning: texImage2D: Alpha-premult and y-flip are deprecated for non-DOM-Element uploads.
Note: Zoom works on Chrome 😮

You're right. Zoom event changed.

The wheel event is fired when a wheel button of a pointing device (usually a mouse) is rotated. This event replaces the non-standard deprecated mousewheel event.


error at the node bot.js

Looks like your auth.json perhaps doesn't have the token in quotes?

how do I fix it?

Add quotes around your token in auth.json?

agreed


Make capsule colliders climb stairs

The function for step detection doesn't work for capsule (or sphere) colliders. The downard cast on ledges won't return floor collision normals because of the rounded bottom of the collider shape, which is the expected behaviour. Checking surface normals could be a solution, but currently the function raycasting the collision points does not hit the floor surface in this scenario for some reason.

Progress in 0ec3554. Capsule colliders now detect the floor surface of steps that are not too shallow, but short steps prove to be a problem, due to the height of the collision point still being higher than the maximum allowd height, for some odd reason.

I finally figured out that the shape radius has to be added on top of the max allowed height, which makes stepping work properly for capsules and spheres. Snapping down stairs now also work. 4b88e76


CosmosDB REST API not working as expected

Link to article:
https://docs.microsoft.com/en-us/rest/api/cosmos-db-resource-provider/databaseaccounts/onlineregion
Problem:
I'm using cosmos db and I'm using REST API mentioned above to add a secondary region to replicate data globally. I'm sure my request parameters are valid, but I received an error:
{
    "code": "BadRequest",
    "message": "onlineRegion capability not enabled for database account tosicosmosdrtest.\r\nActivityId: ad5bd779-6905-4fcc-ab95-3e871fd379ad, Microsoft.Azure.Documents.Common/<IP_ADDRESS>"
}

I'm wondering why this API doesn't behave as expected? And if I have any misunderstanding, this API is not used to create a secondary region, is there any way to create a secondary region programmatically(but not in Azure portal)?

By creating a secondary region manually and monitoring browser's developer tool, I have found there is a PUT request to https://management.azure.com/subscriptions/my-sub-id/resourceGroups/my-rg/providers/Microsoft.DocumentDB/databaseAccounts/tosicosmosdrtest/?api-version=2015-04-08, the request body is:
{
   "location":"East US",
   "kind":"GlobalDocumentDB",
   "tags":{
      "defaultExperience":"DocumentDB"
   },
   "properties":{
      "databaseAccountOfferType":"Standard",
      "consistencyPolicy":{
         "defaultConsistencyLevel":"Session",
         "maxIntervalInSeconds":5,
         "maxStalenessPrefix":100
      },
      "locations":[
         {
            "id":"tosicosmosdrtest-eastus",
            "failoverPriority":0,
            "locationName":"East US",
            "provisioningState":"Succeeded"
         },
         {
            "id":"tosicosmosdrtest-westus",
            "failoverPriority":1,
            "locationName":"West US",
            "provisioningState":"Succeeded"
         },
         {
            "id":"tosicosmosdrtest-eastus2",
            "failoverPriority":2,
            "locationName":"East US 2"
         }
      ],
      "ipRangeFilter":"",
      "enableAutomaticFailover":false,
      "isVirtualNetworkFilterEnabled":false,
      "virtualNetworkRules":[

      ]
   }
}

I think it is the really API endpoint to create a replication database.


Extend rust.vim's Cargo command with add

I did some experimenting and came up with this:

Cargo reload reloads the cargo for lsp
Cargo add runs add and afterwards reloads cargo
Cargo * will behave like rust.vim's Cargo command.

Not sure if this fits in here, maybe in a stripped down version, as this depends on rust.vim for the non add or reload commands.
Put it in .config/nvim/after/ftplugin/rust.lua
vim.api.nvim_buf_add_user_command(0, "Cargo", function(env)
    local cmd = env.args:match("^(%S+)")
    io.stdout:setvbuf 'no'

    if cmd == "add" then
        local file = assert(io.popen('cargo ' .. env.args .. ' 2>&1', 'r'))
        file:flush() -- > important to prevent receiving partial output
        local output = file:read('*all')
        print(output)
        require'lspconfig'["rust_analyzer"].commands["CargoReload"][1]()
    elseif cmd == "reload" then
        require'lspconfig'["rust_analyzer"].commands["CargoReload"][1]()
    else
        vim.cmd('call cargo#cmd("' .. env.args .. '")')
    end
end, {nargs = "+", force = true});

Yeah not sure if it's in the scope of this plugin, atleast wouldn't wanna depend on some other plugin

Yeah, just a general Idea, as a lot of people use cargo edit to manage their dependencies, and running cargo add does not reload rust-analyzer.


Fixing dead link

@bowdenk7,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Error during make of gateway-connector

Make spits out a couple of errors, how to handle? I've tried both https://github.com/TheThingsNetwork/paho.mqtt.embedded-c and https://github.com/eclipse/paho.mqtt.embedded-c
root@gateway:/home/ubuntu/ttn-gateway-connector# make
mkdir -p obj/
cc -fPIC -Wall -g -O2 -Isrc -I../paho.mqtt.embedded-c-1.0.0/MQTTClient-C/src -I../paho.mqtt.embedded-c-1.0.0/MQTTPacket/src -Isrc/github.com/gogo/protobuf/protobuf -Isrc/github.com/TheThingsNetwork -DMQTT_TASK  -I../paho.mqtt.embedded-c-1.0.0/MQTTClient-C/src/linux -c src/connector.c -o obj/connector.o
In file included from src/network.h:7:0,
from src/connector.c:5:
../paho.mqtt.embedded-c-1.0.0/MQTTClient-C/src/MQTTClient.h:22:10: error: empty filename in #include
#include "" //Platform specific implementation header file
^
../paho.mqtt.embedded-c-1.0.0/MQTTClient-C/src/MQTTClient.h:32:15: error: unknown type name ‘Timer’
void NewTimer(Timer*);
^
../paho.mqtt.embedded-c-1.0.0/MQTTClient-C/src/MQTTClient.h:67:26: error: unknown type name ‘Network’
void MQTTClient(Client*, Network*, unsigned int, unsigned char*, size_t, unsigned char*, size_t);
^
../paho.mqtt.embedded-c-1.0.0/MQTTClient-C/src/MQTTClient.h:87:5: error: unknown type name ‘Network’
Network* ipstack;
^
../paho.mqtt.embedded-c-1.0.0/MQTTClient-C/src/MQTTClient.h:88:5: error: unknown type name ‘Timer’
Timer ping_timer;
^
In file included from src/network.h:11:0,
from src/connector.c:5:
src/session.h:10:3: error: unknown type name ‘Network’
Network network;
^
src/session.h:11:3: error: unknown type name ‘MQTTClient’
MQTTClient client;
...
int MQTTSubscribe (Client*, const char*, enum QoS, messageHandler);
^
src/connector.c:113:9: error: too many arguments to function ‘MQTTSubscribe’
err = MQTTSubscribe(&session->client, session->downlink_topic, QOS_DOWN,
^
In file included from src/network.h:7:0,
from src/connector.c:5:

After rebase all worked again. :)


[BUG] Login icon doesn't not matches theme

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When i toggle between dark and light modes the login icon remains same
Expected Behavior
When i toggle between dark and light modes the colour of the login icon also toggles
Reproduction steps
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots

Logs
No response
Browsers
No response
OS
No response

@krishnaacharyaa I would like to work on this. can u please assign this to me.

@EshaalakshmiDS any updates?

@krishnaacharyaa sorry for the delay, submitting PR by tomorrow EOD.

Yes please @EshaalakshmiDS

can i work on this


windows::Error is not Send or Sync

The windows::Error type is not Send or Sync. This means that a windows::Result<T> is not Send or Sync either, even if T is. This is a pain both for async code, and for integrating with common error-handling frameworks like eyre and anyhow. It is possible to work around both of these issues, but they make the API considerably less ergonomic.
It looks like the problem is that Error may contain a bindings::windows::win32::winrt::IRestrictedErrorInfo. It is not clear from the documentation whether this type is supposed to by thread-safe. Could it at least be made Send? That would help with the async issue, and then by wrapping it in a Mutex you could make windows::Error Sync as well.

See also https://github.com/microsoft/windows-rs/issues/424#issuecomment-766528167

Sorry for the delay. I had a look at the implementation. Yes, it can be both Send and Sync.
Does ErrorCode also need Send and Sync or just Error? ErrorCode seems to work across threads without explicitly being Send and Sync.

ErrorCode is automatically Send + Sync because it doesn't contain any types that are not Send + Sync.

ErrorCode is already Send and Sync, isn't it? It's just a wrapper around a u32 so the compiler will automatically implement both. You only need to implement them manually for types containing raw pointers or other special types.

Thanks for confirming! I'll get a PR out shortly.

Here you go: https://github.com/microsoft/windows-rs/pull/601


[CT-1339] [Feature] dbt exposures should support metrics

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
As a dbt user, I want to be able to use metrics in my exposures. For example, if I have a dashboard, I should be able to add it as an exposure in my DAG, and show that it uses certain models and metrics. This is especially useful once I can directly query those metrics via the Semantic Layer.
Describe alternatives you've considered
I've tried adding metrics in my project under the ref'd models in the exposure definition (i.e. using the metric(...) syntax used to define dependencies in derived metrics), but the metrics don't appear in the lineage graph after the project compiles.
Who will this benefit?
Exposures are a great way to 'extend the DAG' and should support models and metrics. I want to see where my metrics are used and how:

for overall awareness about their usage and utility
to ensure any upstream changes I make don't have negative consequences downstream.

This will benefit organizations adopting dbt metrics, especially those querying them via the Semantic Layer.
Are you interested in contributing this feature?
I'm happy to give feedback and help user test the functionality!
Anything else?
No response

thanks @cafzal!

@jtcohen6 Any update on triaging/fixing this? Users can't use use metrics with exposures until it's fixed.

@cafzal Sorry, missed this! We could have a much longer conversation about what it means to consume a metric in an exposure. For now, I'm aligned with this being a thing that should be possible; it's what's consistent & expected.
@MichelleArk took a look, it should be fairly straightforward to implement: https://github.com/dbt-labs/dbt-core/pull/6342


[BUG] Shopware-pwa override paste the component in the wrong folder

Should paste the components in /src/components/... instead of /components/...

I'm closing. The issue was caused by a mismatched CLI version.


Create script to generate Flame Graphs

This script facilitates instrumentation (currently only via dtrace) and generation of Flame Graphs.

I've added a link to the repo containing the needed Perl scripts. Along the way, I've fixed another bug.


🐛 Fixed error messages not fitting on narrow screens

Longer error messages may not fit on one row on more narrow screens, so I changed errorMaxLines in OBTextFormField's TextFormField to default to 3 (to allow for slightly smaller screens, and maybe longer errors in other languages). See image below.

Aha! Big improvement. We were wondering how to do this and totally missed this. Thank you.


Allow course pages to be navigated to from other pages

Either allow redirection from the Advanced Course Search page or Choose Classes page, or maybe both

Feature added with this commit https://github.com/anderm18/HASSPathways/commit/942b39d80f5d8fa09579e25a9087f9277d062ecf


Is sudo capability needed?

Sorry to trouble you again, but is the ability to do sudo without password used for anything?
I have a fork and can remove myself, but was wondering if you have a specific use case or not.
Thanks if you have time to answer :D

@brianlmerritt In general, user should set a password for your account. I assumed that user uses this Dockerfile to build the development environment for prototype. So, it is structured this way to simplify the procedure. I' ll update at a later date.

Not a problem, just interested.


Plots to vizualize

What are the axis in the plots shown in the README file?
How can we achieve it?

The result plots are saved in the log directory.


[Bug]: Modal widget with expanded borders, on deploy, overlaps with the application page tabs

Is there an existing issue for this?

[X] I have searched the existing issues

Description
On increasing the size of a modal widget, and deploying the app which has a number of pages, the UI of modal widget seems to overlap with the Pages.
Steps To Reproduce

Drag and drop a modal widget on one of the pages of an application, with about 7 / 8 pages already
Increase its height such that it reaches its max height to the top of the canvas.
Add a button to the canvas, and ensure that on click of this button the modal widget is invoked.
Deploy the application

You can see that the modal widget overlaps the Pages tabs on top of the screen.
The behavior on Prod is different.

Public Sample App
No response
Version
Release

Duplicate of #14849


Error in pom.xml

@phillipuniverse
Plugin execution not covered by lifecycle configuration: io.github.phillipuniverse:githook-maven-plugin:1.0.5:install (execution: default, phase: initialize) on adding the below plugin
        <plugin>
            <groupId>io.github.phillipuniverse</groupId>
            <artifactId>githook-maven-plugin</artifactId>
            <version>1.0.5</version>
            <executions>
                <execution>
                    <goals>
                        <goal>install</goal>
                    </goals>
                    <configuration>
                        <hooks>
                            <pre-commit>
                                echo running validation build
                                exec mvn clean install
                            </pre-commit>
                        </hooks>
                    </configuration>
                </execution>
            </executions>
        </plugin>

Worked after adding below lines
'pre-commit-hook
install'

@krishnapollu what version of Maven were you on (mvn -v)? I want to look into this a bit more and potentially update the readme.
Also, generally speaking I would not recommend binding to install as you have less guarantees for the commit hook to run. For instance, if someone runs mvn package then the commit hook would not be executed.

I don't have mvn installed globally on my machine, but from Eclipse -> Window -> Preferences -> Maven -> Installation I see
3.6.1 / <IP_ADDRESS>90716-1623 (EMBEDDED)

I don't have mvn installed globally on my machine, but from Eclipse -> Window -> Preferences -> Maven -> Installation I see
3.6.1 / <IP_ADDRESS>90716-1623 (EMBEDDED)


⚠ PrivateHD has degraded performance

In b1ccd43, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2365 ms

Resolved: PrivateHD performance has improved in 42833c9.


Fix example code in README.md

The current snippet is not formatted and looks like JavaScript code.

Thanks again. Really helps to make this shine.


kie-issues#398: Implement flag to allow self-signed certificates when using CORS Proxy for Git requests

Closes https://github.com/kiegroup/kie-issues/issues/398

Hi @thiagoelg,
Thank you for the fix. Unfortunately, it looks broken again as mentioned in https://github.com/lima-vm/lima/issues/1742. I noticed that PR checks started to fail (e.g. https://github.com/kiegroup/kie-tools/pull/1926). Could you please take a look again at how it can be fixed? Thanks in advance!

Hi @thiagoelg, Thank you for this. Unfortunately, it looks QEMU is broken again as mentioned in lima-vm/lima#1742. I noticed that PR checks started to fail (e.g. #1926). Could you please take a look again at how it can be fixed? Thanks in advance!

Well, you can ignore my previous comment. I figured out that the third workaround mentioned in https://github.com/lima-vm/lima/issues/1742 and will be opening PR for the fix soon.

Thanks @zdrapela! Feel free to let me know if I can help with anything.
This issue kind of sucks and there's not much we can do about it beyond applying these workarounds and waiting for an official fix. :confused:


Data Entry: Shadows Wisps in 1-01 do acid damage instead of void

The Shadows Wisps in 1-01 do acid damage instead of void damage with their strikes.

Cannot reproduce.

Yeah, I just double-checked it myself. Sorry for the trouble. Must have been looking at the wrong instance.


Places Autocomplete - Able to preventDefault when selecting a location

I'm using the Places Autocomplete directive. It's sitting inside a form, and when a user starts typing an address, then selects the address and hit's enter on the keyboard, the form is submitting. If the user just selects the location, then clicks out of the field, everything works correctly.
Is there a way to preventDefault the submit since most users are a use to hitting return once they select an address in the typeahead?

I would like this too!
Thanks

You can add another listener to the input field and when it is enter key(13), just simply return false.
It's out of scope question, I think.

I think it'd be better if the default behavior is set to this. Even novice internet users use arrow keys / enter to navigate through dropdown items nowadays.


Clarify handling of Non-converged runs

Clarifying the rules. We believe that runs which don't converge should be counted as infinite runtime when computing the Olympic Score for MLPerf.

SWG:
We clarify that this is everyone's understanding and that this should be codified in the rules.


Do not cycle through options when edges are hit via keyboard navigation.

cf. https://github.com/ipython/ipywidgets/issues/562
cc: @jasongrout @blink1073 @SylvainCorlay

Thanks!


What does the depth predicted by the model mean?

Is the depth predicted by the model absolute depth or relative depth? Why do the predicted values correspond to smaller numbers for points that are further away and larger numbers for points that are closer? Can I obtain the actual distance from a point to the camera plane using the predicted depth? What method can I use to achieve this?

The model predicts inverse depth (1 / depth). Therefore, smaller prediction corresponds to larger depth.


Support for Gauge32 and closing transport thread used in SNMP to avoid java.lang.OutOfMemoryError: unable to create new native thread

Purpose

Support for Gauge32 and closing transport thread used in SNMP to avoid java.lang.OutOfMemoryError: unable to create new native thread

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: PratikSingal:x: Pratik SingalPratik Singal seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: PratikSingal:x: Pratik SingalPratik Singal seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


ARROW-9234: [GLib][CUDA] Add support for dictionary memo on reading record batch from buffer

This is a follow up task for https://github.com/apache/arrow/pull/7263 .

@github-actions crossbow submit -g linux

+1


404 on certain branch URI's

Category
Bug
What is the current behavior?
I'm not sure how to reproduce it. The issue is that two of our five branches fails to be uploaded and be correctly connected to our branch URI.
For example, the branch 'develop' should be found at mygitbook.com/v/develop. In my case, I have a branch 'develop', that doesn't show up at that URI. The curious thing is that this changed a couple of days ago and worked previously.
Worth noting is that my main branch (develop) is indeed built and uploaded correctly and can be accessed from the root URI (mygitbook.com), though not from the specific URI. Another branch RC cannot be found anywhere. The three other branches work correctly.
Example at https://docs.starcounter.io/
What is the desired behavior?
All branches that are built should be available from the following URI: mygitbook.com/v/mybranch.
Additional information
It has GitHub synching to the following repo: https://github.com/Starcounter/Docs.
All branches are building correctly.
We recently changed the main branch from <IP_ADDRESS>34 to Develop. All branches above <IP_ADDRESS>34 are the ones that do not work (RC and Develop).

The following error shows on the two branches that break:

CC @AaronO

It's now working again. I don't know what fixed it. Closing the issue for now.


c++11/14/17/20/23的新特性代码案例

c++11/14/17/20/23的新特性代码案例，包含lambda匿名函数，右值引用，auto，coroutine库，synchronization库等。
https://github.com/0voice/cpp_new_features

In order to asses your issue, we need the following information:

What is the issue you have?

Please describe the steps to reproduce the issue. Can you provide a small but working code example?

What is the expected behavior?

And what is the actual behavior instead?

Which compiler and operating system are you using? Is it a supported compiler?

Did you use a released version of the library or the version from the develop branch?

If you experience a compilation error: can you compile and run the unit tests?


port

how about add port configuration?

Port support is not found yet. I'll add it as soon as possible. Thanks your feedback.

Hi @jackslowfuck , I added port support for PDOx. You can check the documentation.
Thanks :)


config: add exclude labels for tars

Fix the problem of inconsistency between tars and tide, which will cause tars to perform redundant merge master operations and fail to complete the merge, this wastes a lot of CI resources.

/merge


Show friendly name instead of attribute in info_entities

Is your feature request related to a problem? Please describe.
I have a sensor with possible attribute values of dry, very_comfortable, comfortable, ok_but_humid, somewhat_uncomfortable, quite_uncomfortable, extremely_uncomfortable, severely_high, which is what is displayed in the info_entities area of room card. Instead I would like to display the more human readable friendly names without the underscores.
Have you tried if it is already a feature? Have you checked the wiki?
yes
Describe the solution you'd like
option to make show_state to show friendly name
Describe alternatives you've considered
n/a
Additional context
currently the attribute is displayed (highlighted in purple) I would like to display the friendly name (highlighted in green)

friendly_name is an attribute so if you pass it like this
info_entities
  - entity: sensor.example
    attribute: friendly_name

That should give the result you want.
Could you please try this?

Hi,
I'm not sure if I use correct terms for what I want to achieve, using the snippet from your post instead of state I get the name of the sensor so I guess friendly_name is not what I was after

Ah you are right.  Back to the drawing board

It's this hacs integration https://github.com/dolezsa/thermal_comfort

Cool integration! I think its not possible yet since there is a pull request open to use this in templates: https://github.com/home-assistant/core/pull/65743 and https://github.com/PiotrMachowski/Home-Assistant-custom-components-Custom-Templates/tree/master. But I will try to figure out on how to do it.


Raise BrowserNotFound if Chrome and Edge binary are not found.

Also added specs for EdgeFinder.
Fixes #144.

I have only tested this on Windows. Still need to test it with the rake tasks on Linux and macOS.

LGTM

Tested this on Linux and it works as expected. Merging!


No default package after rowan installed

Login to a freshly rowanized stone.
Go to classes browser, Dictionaries pane, create new Dictionary, define a class.
Get walkback:
a UserDefinedError occurred (error 2318), reason:halt, No package named nil found

I was wrong about the problem - apparently the category needs to match an existing package name, so the problem was that no package was selected.
It does get an error when I attempt to create a new package, with no default project.
No error occurs when I attempt to add a package with an existing name, but nothing bad seems to happen..
I don't see a way that given a package, you can figure out what project it's in.

don't know if this is a jadeite or rowan issue or just a "to be fixed in pyrite" ... @ericwinger can you figure this out?

As you can tell, there was some confusion when I filed this.
The nil isn't the problem... When you attempt to create a class where the category is nil (or any invalid package name), you should detect that and give a nice dialog saying "Invalid category name (nil): you must set category to a valid package name"

That is code that is executed by Rowan in the server and this is a use case for some sort of GsInteraction ... probably an #inform: (which should be logging a message when in non-interactive session) followed by the #error: ... this can be put in for Alpha1.1, but in Alpha1.1 you'll get the same behavior -- until pyrite maps interactions to dialog boxes ... labeling as First Release and assigning to me , since I have to put the interaction code in place ...

looks like it is fixed


Feature Request: Nearby Bluetooth Devices

It would be great if the Bluetooth evidence source included nearby (i.e. active but not connected) bluetooth devices like the "Nearby WiFi Network" evidence source does, and then allow rules to be triggered based on whether a particular device is "nearby".
Use case: I want to create a rule+action that will automatically connect to a bluetooth headset whenever it is turned on in the vicinity of my mac (can't believe Apple doesn't provide this capability within the Bluetooth preference pane).
See also #326

Is it appropriate to +1 this request?
I recall that MarcoPolo supported bluetooth detection that did not require connecting (which is so stupidly complex with a Mac and iPhone that I might as well just manually do the things I want ControlPlane to do for me), but merely the presence of a specific Bluetooth device. This was so long ago that the device in question was a Blackberry!

I agree that this would be nice. I'm interested in connecting to a Bluetooth PAN (my phone) when there's otherwise no network access available (so far so good)... and reestablishing the connection if I move too far away and then return.
This last part is difficult without setting CP to deliberately bounce between contexts (so as to connect to PAN on both departure and arrival).

Chiming in a little later to say still would be nice.


Upgrade dependency on dw1000 crate

The Travis build displays as pending here, but if I click on the link, I see that it has been completed successfully. Merging.


Header

Reads the header of a NetCDF v3.x file

Changes Unknown when pulling 117443e7af83c81d393069563d97575093aeabaa on development into ** on master**.

Changes Unknown when pulling 11e4a684ce9bd7beea895d64b92f4f8ea6b87c4d on development into ** on master**.

Changes Unknown when pulling a4d5bbae083b84c1a7a150dd183868a3737dc265 on development into ** on master**.

Changes Unknown when pulling<PHONE_NUMBER>55b322bdafc66f4285f63a973ce2dd on development into ** on master**.

I would put methods related to types like evalType in the type.js file.

Changes Unknown when pulling 2b96889fd7ec28384dca3659a8634cea85f226ff on development into ** on master**.

Changes Unknown when pulling 2b96889fd7ec28384dca3659a8634cea85f226ff on development into ** on master**.

Changes Unknown when pulling 24a8f2b9d416789558d53709b5620f7aaedc9b60 on development into ** on master**.


Bug: SP_CLASSINSTALL_HEADER implements Debug only on 64 bits target

Which crate is this about?
windows
Crate version
0.30.0
Summary
#[cfg(any(target_arch = "aarch64", target_arch = "x86_64"))]
impl ::core::fmt::Debug for SP_CLASSINSTALL_HEADER {
    fn fmt(&self, f: &mut ::core::fmt::Formatter<'_>) -> ::core::fmt::Result {
        f.debug_struct("SP_CLASSINSTALL_HEADER").field("cbSize", &self.cbSize).field("InstallFunction", &self.InstallFunction).finish()
    }
}

This impl is gated on 64 bit and is not replicated for 32 bit.
Expected behavior
I expected the 32 bit version to implement Debug too
Actual behavior
The 32 bit version does not implement Debug
Additional comments
https://github.com/microsoft/windows-rs/blob/5e37e9fe2d6ce72069d11d5adf7fa106b172bfcb/crates/libs/windows/src/Windows/Win32/Devices/DeviceAndDriverInstallation/mod.rs#L9215

You'll notice the x86 form of this struct has a packed representation. Rust has pretty severe restrictions for what can be done with packed structs so the windows crate avoids emitting the Debug trait (and a few others) in such cases. Since the x64 form of this struct has no specific packing metadata, the windows crate can emit the Debug trait for that flavor.
https://github.com/rust-lang/rust/issues/82523

This means the windows crate cannot be compiled for i686-pc-windows-msvc with the feature Win32_Devices_DeviceAndDriverInstallation.
The CI does not do its tests or checks with the --all-features flag so it cannot catch this right now, it probably should:
cargo check --all-features --target=i686-pc-windows-msvc -p windows
   Compiling proc-macro2 v1.0.32
   Compiling unicode-xid v0.2.2
   Compiling syn v1.0.81
   Compiling windows_reader v0.30.0 (/home/alexis/repos/windows-rs/crates/libs/reader)
   Compiling windows_quote v0.30.0 (/home/alexis/repos/windows-rs/crates/libs/quote)
   Compiling windows_i686_msvc v0.30.0 (/home/alexis/repos/windows-rs/crates/targets/i686_msvc)
   Compiling quote v1.0.10
    Checking windows_gen v0.30.0 (/home/alexis/repos/windows-rs/crates/libs/gen)
   Compiling windows_macros v0.30.0 (/home/alexis/repos/windows-rs/crates/libs/macros)
    Checking windows v0.30.0 (/home/alexis/repos/windows-rs/crates/libs/windows)
 error[E0277]: `SP_CLASSINSTALL_HEADER` doesn't implement `std::fmt::Debug`
     --> crates/libs/windows/src/Windows/Win32/Devices/DeviceAndDriverInstallation/mod.rs:11877:84
      |
11877 | ...eld("ClassInstallHeader", &self.ClassInstallHeader).field("PowerMessageWake", &self.PowerMessageWake).finish()
      |                              ^^^^^^^^^^^^^^^^^^^^^^^^ `SP_CLASSINSTALL_HEADER` cannot be formatted using `{:?}`
      |
      = help: the trait `std::fmt::Debug` is not implemented for `SP_CLASSINSTALL_HEADER`
      = note: add `#[derive(Debug)]` to `SP_CLASSINSTALL_HEADER` or manually `impl std::fmt::Debug for SP_CLASSINSTALL_HEADER`
      = note: required for the cast to the object type `dyn std::fmt::Debug`

error[E0277]: `SP_CLASSINSTALL_HEADER` doesn't implement `std::fmt::Debug`
     --> crates/libs/windows/src/Windows/Win32/Devices/DeviceAndDriverInstallation/mod.rs:12400:80
      |
12400 | ...eld("ClassInstallHeader", &self.ClassInstallHeader).field("Title", &self.Title).field("Instructions", &self.Instructions).field("ListL...
      |                              ^^^^^^^^^^^^^^^^^^^^^^^^ `SP_CLASSINSTALL_HEADER` cannot be formatted using `{:?}`
      |
      = help: the trait `std::fmt::Debug` is not implemented for `SP_CLASSINSTALL_HEADER`
      = note: add `#[derive(Debug)]` to `SP_CLASSINSTALL_HEADER` or manually `impl std::fmt::Debug for SP_CLASSINSTALL_HEADER`
      = note: required for the cast to the object type `dyn std::fmt::Debug`

error[E0277]: `SP_CLASSINSTALL_HEADER` doesn't implement `std::fmt::Debug`
     --> crates/libs/windows/src/Windows/Win32/Devices/DeviceAndDriverInstallation/mod.rs:12518:82
      |
12518 | ...eld("ClassInstallHeader", &self.ClassInstallHeader).field("ChmFile", &self.ChmFile).field("HtmlTroubleShooter", &self.HtmlTroubleShoot...
      |                              ^^^^^^^^^^^^^^^^^^^^^^^^ `SP_CLASSINSTALL_HEADER` cannot be formatted using `{:?}`
      |
      = help: the trait `std::fmt::Debug` is not implemented for `SP_CLASSINSTALL_HEADER`
      = note: add `#[derive(Debug)]` to `SP_CLASSINSTALL_HEADER` or manually `impl std::fmt::Debug for SP_CLASSINSTALL_HEADER`
      = note: required for the cast to the object type `dyn std::fmt::Debug`

error[E0277]: `DBOBJECT` doesn't implement `std::fmt::Debug`
     --> crates/libs/windows/src/Windows/Win32/System/Search/mod.rs:30023:56
      |
30023 |         f.debug_struct("SSVARIANT_0_0").field("dbobj", &self.dbobj).field("pUnk", &self.pUnk).finish()
      |                                                        ^^^^^^^^^^^ `DBOBJECT` cannot be formatted using `{:?}`
      |
      = help: the trait `std::fmt::Debug` is not implemented for `DBOBJECT`
      = note: add `#[derive(Debug)]` to `DBOBJECT` or manually `impl std::fmt::Debug for DBOBJECT`
      = note: required for the cast to the object type `dyn std::fmt::Debug`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `windows` due to 4 previous errors

Tested on commit c30b98520638bfd0869f1456f102ca9bf080ace1

Unfortunately, testing all features of the windows crate exhausts the available memory on the GitHub build VMs. @yoshuawuyts is looking into a workaround.
Is there a minimal set of features that reproduces the problem on x86 builds?

I think the features Win32_Devices_DeviceAndDriverInstallation and Win32_System_Search are affected

Minimal repro (requires x86):
cargo check -p windows --features Win32_Foundation,Win32_Devices_DeviceAndDriverInstallation

All done - thanks for reporting.

0.32.0 has now been published and includes this change.


Please upgrade server to 2.7.4

Please upgrade server to 2.7.4, Thank you very much! Nice Job!

+1 Dashboard also need to be updated to 1.2.0


t.navigateTo broken

Bug report
t.navigateTo singe page app does not open
t.navigateTo single page app opens the page
When i updated to 0.20.5 from 0.19.2 t.navigateTo functionality stopped working correctly
I'm not specifying url on test or fixture. I'm navigating from the test implementation
Example await t.navigateTo('desktop.ttqa4.xyz/register')

operating system: OSX
testcafe version: 0.20.5
node.js version: 6.5

Rolling back to 0.19.2 fixes it, but i'm losing meta features

Hi @emildimitrov, try to specify protocol in the links specified in the navigateTo action.

Hi @AndreyBelym with and without protocol its the same. Since 0.19.2 this functionality is broken. I tried all the releases since then

If this is helpful the runner shows a blank white screen after the waiting for the page and fails on finding elements on the page, but if untill the runner is waiting i refresh the url test gets executed properly

Thanks a lot @LavrovArtem

Related to https://github.com/DevExpress/testcafe-hammerhead/issues/1702

Fixed in https://github.com/DevExpress/testcafe-hammerhead/commit/6ff79ed73b6efa4e3cb8dd76d7ddceb2ed09f862


what does chain-state-db-size-mb mean?max size is mem size?

In config.ini,there is opt chain-state-db-size-mb,which max size is mem size,so if my pc's men is 8G,and chain-state-db-size-mb max size is 8G,when the state dir is above 8G ,what happened?Is there anyway to break this up limit of state dir?

Would enable mongodb-plugin will help to reduce chain-state-db-size?

chain-state-db-size-mb is the max size of the shared_memory database for storing the state. It should be configured to be less than machine memory. Configuring large size might result in memory swap and performance reduction.

As you say,what happened if chain-state-db-size-mb increase more than machine memory?eos crush?or not crush,but can not store new data?

it will possibly causes memory swap and serious performance reduction.

if it happens,eos can not store data and work normally.
if set chain-state-db-size-mb less than mem size(8G),some day it increase above limit,it crush.
it is bug or there is some way to reslove it?

For the time being, the solution is to run nodeos on a machine with more memory.  This solves the problem for quite a long time, as AMD EPYC systems are available today that can accommodate 4TB of RAM.
Note that on some platforms, with some kernel settings, nodeos will crash if the chain state exceeds available physical RAM.  It attempts to lock memory, and if that operation fails, some platforms will terminate the process.

As you say,if my pc's mem is low ,someday eos must be crush.
So ,that is a serious  bug in eos?

That’s not a bug, it’s just the way certain OSes with certain kernel options handle memory overconsumption. nodeos can’t change OS behavior.

But actually,most people's mem is about 8G,when state_db size increase above it ,eos must crush,it can not work normally at all.

Nodes handling large chains need to run on high-ram dedicated servers, not typical PCs. This is not unusual; servers exist to run jobs that PCs are poor at.

this means that the EOS cannot support large data volume applicaiton???.... since in the end, the state_db will reach the limit......   is there any plan to swap to another DB engine? like put some data onto mongodb instead??     I agree that this is actually serious problem.... as a lot of application requires much more space than 1TB, or 4TB.

But even though the high-ram server, we still face the crush result once the ram used up.  Is there a solution like state data persistence in hard disk storage?

Common causes for ram exceeding 64 GB:

Abusing filter-on. * is not intended for production use. See the Mongo plugin for an alternative.
Storing data that contracts don’t need in rows. See demux for an alternative. See also the Mongo plugin.

Key point to remember: data can be stored in action data without causing nodeos to consume ram, as long as that data isn’t stored in rows or included by the history plugin. Both mongo and demux can safely index large data stored this way.

The history_plugin + "filter-on: *" option causes memory full problem.
Consider mongo_db_plugin + mongo db + api server.

Pity it seems still not solved yet in 2022!


Deployment script in Azure CLI 2.0?

Is there an equivalent to azure site deploymentscript in Azure CLI 2.0? (Ref. Custom deployment script)

No, but it's simpler to just use kuduscript directly. Install it using npm install -g kuduscript, and then run kuduscript.


Geo: pricing plan questions contain bad assumptions

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework
Not applicable
Amplify APIs
Not applicable
Amplify Categories
No response
Environment information

$ amplify --version
5.2.2-geo.2

Describe the bug
I'm not tracking anything in my app, just showing a map.
The following choices determine the pricing plan for Geo resources. Learn more at https://aws.amazon.com/location/pricing/
? Are you tracking commercial assets for your business in your app?
❯ No, I only need to track consumers personal mobile devices
  Yes, I track commercial assets (For example, any mobile object that is tracked
 by a company in support of its business)

Expected behavior
A default option where I indicate that I'm not using tracking. The current default says that I'm tracking "consumers [sic; should be possessive] personal mobile devices" and I'm definitely not.
Reproduction steps
amplify init
amplify add geo
# walk through steps until you get to the pricing question

Code Snippet
No response
Log output
No response
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response

Thanks, transferring to CLI for @phani-srikar to make the changes.


Automate smoke test on GCE

In order to improve deis' quality on various providers, we'd like to have a way to test deis on GCE in an automated fashion.
What I'd like to see is:

provision a 3 node cluster on GCE
run the smoke test script after provisioning is complete.

I'll probably take a stab at reviving some of the work that others have done with Terraform for the provisioning bit.

You may want to talk to @econnell  about this, as he has been working on Terraform recently :)

You bet @bacongobbler. @econnell is there a place I can go to check out your work/understand your progress in that domain?

This is not something we'll be able to get to fixing for the LTS release, and provisioning Deis v2 is done through installing a vanilla kubernetes cluster so I'm going to go ahead and close this.


apiservice-kicker 100% CPU usage

Fresh install of microk8s (snap 1.21/edge) on PI4 (8GB), Ubuntu 21.04.
I noticed that apiservice-kickeris is taking 100% cpu on two nodes of a three node cluster.
The cluster isn't doing anything yet, I'm new to kubernetes and don't know where to look...
Any help appreciated.
inspection-report-20210430_132345.tar.gz
Saw the same issue on snap 1.21/stable

Hi @matonb, I cannot see anything wrong in your setup. I will need your help to figure out what may be causing this.
The apiservice-kicker [1] is a loop that runs every 3 seconds. In the loop there are a few tasks performed. Some of these tasks are "feature-flagged" via lock files found under /var/snap/microk8s/current/var/lock. Could you share the output of ls -l  /var/snap/microk8s/current/var/lock? We will need to run each tasks from the command line to see if some task gets stuck in an infinite loop.
[1] https://github.com/ubuntu/microk8s/blob/master/microk8s-resources/wrappers/apiservice-kicker

@ktsakalozos Here's the ouput:
ls -l /var/snap/microk8s/current/var/lock
total 0
-rw-r--r-- 1 root root     0 May  3 12:21 cni-loaded
-rw-rw---- 1 root microk8s 0 May  3 12:18 ha-cluster
-rw-rw---- 1 root microk8s 0 May  3 12:18 lite.lock
-rw-rw---- 1 root microk8s 0 May  3 12:18 no-etcd
-rw-rw---- 1 root microk8s 0 May  3 12:18 no-flanneld

Ok, we will need to go though the tasks in [1] one by one and see if any of them is causing this behavior.
Let's first disable the re-issuing of certificates on network changes, to do so edit /var/snap/microk8s/current/arg/kube-apiserver and append a line like --advertise-address=<IP_ADDRESS>, then restart microk8s with microk8s.stop; microk8s.start.
[1] https://github.com/ubuntu/microk8s/blob/master/microk8s-resources/wrappers/apiservice-kicker

Added to the top of the file:
head /var/snap/microk8s/current/args/kube-apiserver -n4
--advertise-address=<IP_ADDRESS>
--cert-dir=${SNAP_DATA}/certs
--service-cluster-ip-range=<IP_ADDRESS>/24
--authorization-mode=AlwaysAllow

microk8s restarted:
sudo su -
microk8s stop ; microk8s start

@matonb when you do a sudo microk8s.stop does the apiservice-kicker stop? I wonder if there is a leftover process.

@ktsakalozos
There's one apiservice-kicker process left running (100%) after I stop microk8s

On a node showing this behaviour (pid 131252 stuck at 100%):
ps -ef | grep kicker
root        1781       1  0 03:02 ?        00:00:40 /bin/bash /snap/microk8s/2175/apiservice-kicker
root      131252    1781 99 05:03 ?        04:11:53 /bin/bash /snap/microk8s/2175/apiservice-kicker
matonb    213917  211135  0 09:15 pts/0    00:00:00 grep --color=auto kicker
matonb@pi011:~$ sudo strace -f -p 1781
strace: Process 1781 attached
wait4(-1, ^Cstrace: Process 1781 detached
 <detached ...>

matonb@pi011:~$ sudo strace -f -p 131252
strace: Process 131252 attached

Can't terminate strace on stuck process, had to kill strace
sudo strace -f -p 131252
strace: Process 131252 attached
^C^C^C^CKilled

Same result here. PI4 8GB running Ubuntu 21.04 for a few weeks. I've even got two apiservice-kickers running after microk8s stop. Not in any practical use yet, but about to get started.
$ ps aux|grep apiservice|grep -v grep
root     2118288 99.4  0.0   9128   704 ?        R    May01 28377:11 /bin/bash /snap/microk8s/2175/apiservice-kicker
root     2870911 98.5  0.0   9260   752 ?        R    May18 3995:13 /bin/bash /snap/microk8s/2215/apiservice-kicker

$ uptime
 12:37:03 up 20 days, 20:17,  4 users,  load average: 2.00, 2.14, 2.78

$ date
Fri May 21 12:37:04 UTC 2021

$ sudo strace -f -p 2118288
strace: Process 2118288 attached

$ sudo strace -f -p 2118288
strace: Process 2118288 attached
^C^C^C^C^C^C^CKilled

$ sudo strace -f -p 2870911
strace: Process 2870911 attached
^C^C^C^C^CKilled

$ lsb_release -r
Release:        21.04

$ snap info microk8s|grep installed
installed:          v1.21.1             (2215) 168MB classic

this https://github.com/ubuntu/microk8s/issues/1775#issuecomment-734218451
seems to help. I'm still testing

this https://github.com/ubuntu/microk8s/issues/1775#issuecomment-734218451
seems to help. I'm still testing

This did not work for me. Have since changed systemd's journal storage to volatile (based on recommendations in another thread and Ubuntu's docs) and watching for performance issues.

And the hanging apiservice-kicker process is back at 100%. I suppose I could try to replace the SD media with USB connected SSD's, but it kind of defeats the purpose of running a cluster on pis'.

SSD's won't fix the problem, that's what I'm running with on my PI's.
I think the issue is network related, I've got a few other projects on an not had chance to look into this much.

@matonb and @nord73 there's also recently reported issue where users see this.
https://github.com/ubuntu/microk8s/issues/2280#issuecomment-851365650  based on their investigation moving the journald to volatile, improve disk storage and disabling metrics server seems to do the trick.

@balchua No metrics server here, and volatila storage for journald, so only storage performance left of those to consider. But as I mentioned earlier, taking built-in micro SD storage (even fast ones) out of the equation makes the idea of a pi cluster moot for most.

Still seeing this issue with v1.22.0.

I also ran into this problem. PI4 8GB / Ubuntu 21.04 / usb ssd

I also ran into this problem.  PI4 8GB / Ubuntu 21.04 / usb ssd

I've got the same issue Pi4 4GB / Ubuntu / Ubuntu 21.04 / sd card

I'm also seeing this - 4 x Pi 4 4GB running Ubuntu 21.04, microk8s 1.21.
Here's a screenshot of glances on one of the nodes.

I'm also seeing this - 4 x Pi 4 8GB. But now I see 2 processes stuck at 100%

I have the same issues as everyone else here. Running Ubuntu 21.10 on RPI 4/8GB, each booted off an SSD drive.
microk8s was installed using this command: sudo snap install microk8s --classic --channel=1.21. I have installed the metrics-server today, but prior to that, it wasn't running and the apiservice-kicker process was pegged at 100%. I will try installing debian and see if it fixes the issue or not.

Is there an easy way to make that script modifiable in any way? I could try to debug on my end, but as it is part of the snap it is on a read only FS. Horrible idea!

I got the same issue, apiservice-kicker using ~80% and systemd-udevd was also taking a high load of the CPU on a raspberry pi 400 - using ubuntu 21.10 server.
After having installed linux-modules-extra-raspi, CPU went down to something more expected/normal.
hope it helps a few

I am wondering why nobody has bothered to look into this yest from canonical ?  Its still an issue....

Hi @JoshuaDodds
This is in fact not ignored or abandoned by the MicroK8s team. Our testing concluded that it was an issue with the apiservice kicker using ethtool to check whether the vxlan.calico interface had a checksum offloading calculation enabled or disabled.
This has been removed in newer versions. Starting from MicroK8s 1.24, we are now using the configuration offered by Calico to properly disable the check instead of relying on the old behaviour, which would not cause the 100% CPU usage lockup.
In light of this, we have not seen the issue come up recently, but it is sometimes hard to follow up and we sometimes miss some updaes. Given that it has been a year since the issue was reported, I don't know if the original reporter can weigh in and check whether the are getting the same problem on 1.24+.

Hi @neoaggelos ,
Much thanks for your quick response.  I have been following this issue since inception and somehow missed this update.  This is good news to hear that you believe that you have found the root cause of the issue.  I will assist when i have time by upgrading to 1.24 and re-enabling the api-kicker to test how it behaves.  I will report back with my findings.
Thanks again for the quick response to my comment!


Is there an offical tensorflow version of soft nms?

Hi,
Thanks for shaing your code. I want to ask is there an offical tensorflow version of soft nms. If I use a self-written cpu version of soft nms, like yours, will it greatly reduce the efficiency of the program? Thanks.

Yes - https://www.tensorflow.org/versions/r1.15/api_docs/python/tf/image/non_max_suppression_with_scores
if you set the 'soft_nms_sigma' variable to > 0 it will apply Gaussian Soft NMS on the candidate boxes and scores


fix: do not allow to pass A&B custom options to backend.run()

Yes, it's the simpler workaround I think. I chose to get the parameters dynamically from the processor function, so we don't have to maintain a string list of the parameters that could become out of sync. I didn't know if it was better to do it in the init or in the .run(), but at least here it runs this code only when needed.


can't select sonoff switches as devices in automation

my sonoff switches show up as entities (under configuration) but not as devices. therefore in automation they can be used as triggers but not as actions. Switching via Lovelace UI works fine. any suggestions?

I have the same issue. Please help !

In automations, you do not use them as devices.  For example, if it is a light, click toggle.light, and you can select your switch. I had the same issue; it's not very clear at first.

Thanks hewwoworld, it works!
BTW my zigbee devices do show up as devices under actions. That apparently confused me. Thanks again.


Change from queries to mutations

How to display the mutations or the queries from a Change Introspection? (from a flat HTML version)
I found this issue was closed, but I don't really understand how to make it happen: https://github.com/APIs-guru/graphql-voyager/issues/15
Thanks!

@elenigen Do you mean online demo https://apis.guru/graphql-voyager/ or NPM package?

@elenigen If you use NPM, can you please check that you are using v1.0.0-rc.26?

Sorry, I just noticed that we can actually simply change the root item from the menu :

I believe I was focusing too much on the displayOptions.rootType feature.  I thought it could be initialized only when the Voyager page is loaded, but in the end, it's dynamic.
🤦♂
Thanks anyway for your help!

Coming way after last comment but I totally missed the chevron as well
Wouldn't it make much more sense to have a an abstract "Root" which then contains "Query", "Mutation" and Subscription" (and henceforth for their endpoints) ?
This way we wouldn't need the chevron menu as much and would be able to search any endpoint in the search bar


Added dropEyeFromFrame rule as requested in issue #20.

Simple implementation of issue #20.
Needs some typo corrections.

Testing locally everything looks good. Sometimes the eyes of ender glitch in the block though, could this be easily fixed by offsetting the position to the top of the end portal frame block?


[4099] enable service domain redirect in prod

Context
We've added and tested code to redirect education.gov.uk to service.gov.uk. This works in qa, review apps and staging.
Changes proposed in this pull request
Enable the redirect in prod.
Guidance to review
Please consider whether any other configuration needs to be updated for this. I've added www.register-trainee-teachers.service.gov.uk to the sign-in and sign-out sections of the DFE Sign-In configuration, please also validate those changes if you can.
Important business

[ ] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[ ] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml

 Enable education -> service domain redirect in prod


No recoil not working

I updated everything and the cheat works perfectly but no recoil does not work at all, is there a way to fix that? Btw sorry for making so many issues :(

You probably didn't update held entity or baseprojectile then.

Will try doing that

no both those are updated but it still doesnt work

also console sometimes says "Failed to Execute scatter read" but the cheat still works, only recoil doesnt.

The recoil properties field also needs updating.

its up to date, its 0x2F0

do I need to update the class above recoil properties?

My fork that was just merged should all be updated properly, have a look at the SDK changes and you can try to figure out what you missed.

hey, yeah I did and it works now, in Item ID I accidently put 10 instead of 20. Tysm for the help


Both C++ and Python implementation of games necessary for some algorithms?

Discussed in https://github.com/deepmind/open_spiel/discussions/975

Originally posted by regenbogenfrosch December 10, 2022
Hello all open_spiel developers
Thank you very much for releasing this wonderful project!
I am just new to RL and open_spiel in general and have some questions that might sound easy for you:
I am currently using open_spiel in my university work, and trying to understand RL for my project.
I have rewritten the "Tower Of Hanoi" problem as a k-general sum single player game in the C++ code part of open_spiel as described in the tutorial. And it works. Random plays run very well until the TerminalState is reached, at least for small problem sizes.
I also managed successfully to run the Q-Learning and SARSA learning algorithm (from one of the examples file adapted) and those algorithms also converge to the solution.
Now I want to test the "real" RL algorithms, as DQN, A2C and EVA. Unfortunately, I have found examples for using these algorithms only in the python directory of open_spiel.
Now, my silly question: does this mean, I have to rewrite my "myHanoi.cc" Code for my game completely new (and identical) in python (for example: myHanoi.py)? Or is it possible to use my written game and just load it from the C++ code directory somehow?
Sorry, for the silly sounding question, but I missed that somehow in the documentation.
Anyways, this is a cool framework, thanks again.
Best Regards
Frank

I answered there, closing this. Thanks for raising it again here.


Patch/contribution

Codecov Report

Merging #107 (823b6a3) into main (7fd92b3) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #107   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          139       139
=========================================
  Hits           139       139

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 7fd92b3...823b6a3. Read the comment docs.


Leaseweb api always returns 400, but not when using libdns example

What's the best way to debug when the leaseweb api returns a 400 bad request error? Would it be possible to return/log the error details that Leaseweb returns in the response body?
When I compile the https://github.com/libdns/leaseweb example code with my api key the request are done succesfully, but when using through caddy with tls  { dns leaseweb API_KEY } it seems all requests fail with a 400.:
ERR ts=1 logger=tls.obtain msg=will retry error=[*.mydomain.com] Obtain: [*.mydomain.com] solving challenges: presenting for challenge: adding temporary record for zone "mydomain.com.": Received StatusCode 400 from Leaseweb API. (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/x/y) (ca=https://acme-staging-v02.api.letsencrypt.org/directory) attempt=3 retrying_in=120 elapsed=186 max_duration=259200

To be clear, the tls request is for a wildcard domain hence the *.mydomain.com

Hey, sorry I missed this issue. I'm not actively using caddy+leaseweb anymore, and there never was a lot of interest. Never had to do actual maintaining.
This also was my only real golang stint, but the approach you came up with was very similar to mine if I recall correctly.
Thanks for documenting, I will put it in the README.md if you're okay with that.

Awesome.
Seem like xcaddy build --with github.com/caddy-dns/leaseweb && ./caddy run is now working with leaseweb configured as provider:
some-domain.example.org:8443 {
	tls {
		dns leaseweb "<api-key>"
	}
	respond "Hello, world!"
}


Stream max-lifetime feature moving to server-side & test flakiness

@moh-osman3 Has been working on https://github.com/f5/otel-arrow-adapter/pull/211 which was in-flight when this repository migration began. @lquerel had asked for the mechanism to be configurable on the server side, which made more sense to @moh-osman3 and me after we studied the problem further. @moh-osman3 will rebase that work into this repository.
Meanwhile, there is one flaky test that I will ignore to move forward with the migration.

Failure is seen in #4.
=== RUN   TestStreamGracefulShutdown
panic: test timed out after 10m0s

goroutine 5200 [running]:
testing.(*M).startAlarm.func1()
	/opt/hostedtoolcache/go/1.19.12/x64/src/testing/testing.go:2036 +0x8e
created by time.goFunc
	/opt/hostedtoolcache/go/1.19.12/x64/src/time/sleep.go:176 +0x32

goroutine 1 [chan receive, 9 minutes]:
testing.(*T).Run(0xc0004b0000, {0xf7deba?, 0x518865?}, 0xfc1370)
	/opt/hostedtoolcache/go/1.19.12/x64/src/testing/testing.go:1494 +0x37a
testing.runTests.func1(0xc0001fdb60?)
	/opt/hostedtoolcache/go/1.19.12/x64/src/testing/testing.go:1846 +0x6e
testing.tRunner(0xc0004b0000, 0xc00045fcd8)
	/opt/hostedtoolcache/go/1.19.12/x64/src/testing/testing.go:1446 +0x10b
testing.runTests(0xc0001ebf40?, {0x1851380, 0x11, 0x11}, {0x7f2c9b1375b8?, 0x40?, 0x1861940?})
	/opt/hostedtoolcache/go/1.19.12/x64/src/testing/testing.go:1844 +0x456
testing.(*M).Run(0xc0001ebf40)
	/opt/hostedtoolcache/go/1.19.12/x64/src/testing/testing.go:1726 +0x5d9
main.main()
	_testmain.go:79 +0x1aa

goroutine 4816 [select, 9 minutes]:
github.com/open-telemetry/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow.(*healthyTestChannel).onRecv.func1()
	/home/runner/work/otel-arrow/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow/common_test.go:195 +0x9a
reflect.Value.call({0xe03100?, 0xc0006c2480?, 0xc00056ba00?}, {0xf690dd, 0x4}, {0x18933f8, 0x0, 0x40f45f?})
	/opt/hostedtoolcache/go/1.19.12/x64/src/reflect/value.go:584 +0x8c5
reflect.Value.Call({0xe03100?, 0xc0006c2480?, 0x0?}, {0x18933f8?, 0x4d8816?, 0xe51f00?})
	/opt/hostedtoolcache/go/1.19.12/x64/src/reflect/value.go:368 +0xbc
github.com/golang/mock/gomock.(*Call).DoAndReturn.func1({0x0, 0x0, 0xc0004e86a0?})
	/home/runner/go/pkg/mod/github.com/golang/mock@v1.6.0/gomock/call.go:132 +0x485
github.com/golang/mock/gomock.(*Controller).Call(0xc010b0aa50, {0xee4ce0, 0xc0004e86a0}, {0xf69261, 0x4}, {0x0, 0x0, 0x0})
	/home/runner/go/pkg/mod/github.com/golang/mock@v1.6.0/gomock/controller.go:251 +0xf7
github.com/open-telemetry/otel-arrow/api/experimental/arrow/v1/mock.(*MockArrowStreamService_ArrowStreamClient).Recv(0xc0004e86a0)
	/home/runner/work/otel-arrow/otel-arrow/api/experimental/arrow/v1/mock/arrow_service_mock.go:129 +0x59
github.com/open-telemetry/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow.(*Stream).read(0xc0001da1b0, {0xc021050[280](https://github.com/open-telemetry/otel-arrow/actions/runs/5826962689/job/15802016892#step:5:281)?, 0x0?})
	/home/runner/work/otel-arrow/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow/stream.go:351 +0x35
github.com/open-telemetry/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow.(*Stream).run(0xc0001da1b0, {0x10f4358?, 0xc021050200?}, 0xc00d07b1b8, {0x0, 0x0, 0x0})
	/home/runner/work/otel-arrow/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow/stream.go:167 +0x246
github.com/open-telemetry/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow.(*streamTestCase).start.func1()
	/home/runner/work/otel-arrow/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow/stream_test.go:84 +0x95
created by github.com/open-telemetry/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow.(*streamTestCase).start
	/home/runner/work/otel-arrow/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow/stream_test.go:82 +0xb8

goroutine 4815 [chan receive, 9 minutes]:
github.com/open-telemetry/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow.(*streamTestCase).get(...)
	/home/runner/work/otel-arrow/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow/stream_test.go:119
github.com/open-telemetry/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow.TestStreamGracefulShutdown(0xc000378340?)
	/home/runner/work/otel-arrow/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow/stream_test.go:149 +0x33b
testing.tRunner(0xc0003784e0, 0xfc1370)
	/opt/hostedtoolcache/go/1.19.12/x64/src/testing/testing.go:1446 +0x10b
created by testing.(*T).Run
	/opt/hostedtoolcache/go/1.19.12/x64/src/testing/testing.go:1493 +0x35f
FAIL	github.com/open-telemetry/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow	600.106s
?   	github.com/open-telemetry/otel-arrow/collector/gen/exporter/otlpexporter/internal/arrow/grpcmock	[no test files]

See @moh-osman3's investigation in https://github.com/grpc/grpc-go/issues/6504


bug: show content button position conflict

Show contents button is conflicting with the folder path . Sometime looks ugly.

Taking this up

Hello, can this task be assigned to me,
How I am going to tackle this situation:-

I'll make that button positioning absolute alongside keeping it easily accessible for the user.
I have also encountered this same issue with, the user always has to scroll to the top of the page when they want to click on it.

@sharabhh I think it was already set to absolute positioning when I opened the code, and when I ran the code locally, it worked well in my environment without overlapping.

@parthjadhao but on scroll it moves upward atleast in the current production code

@sharabhh, the Show button is rendered when the Sidebar component is rendered. In the screenshot below, you can see that it is already set to relative positioning.

In the code of the Sidebar component shown below, you can see that the Show content is already declared.

I believe it's moving upward because its parent element is also moving upward, but I am not completely sure why.

@sharabhh, the Show button is rendered when the Sidebar component is rendered. In the screenshot below, you can see that it is already set to relative positioning.
In the code of the Sidebar component shown below, you can see that the Show content is already declared.
I believe it's moving upward because its parent element is also moving upward, but I am not completely sure why.
by the way in you locally hosted project is showcontent button is overlapping or rendering perfectly like mine

Yes exactly, just saw it in the code. It is moving according to the parent due to relative position. So if we want to make it stick individually we need to either take it out of that file entirely to another higher level file or maybe find a way to make it sticky in a way that it can work from there without going behind top navbar

For now, the maintainer has asked to simply fix the issue of overlapping. If they want the button to be sticky, you can inquire further, but for now, I am submitting a pull request to resolve the bug.