History: DynDNS Changes are not logged with details

It would be nice, if the DynDNS changes will also be logged with Details, like changes via WebUI and API.

Hello @Metrax
I don't have time to look at the code, but is the master branch giving more details now ?
Regards

@jbe-dw nope, no change at master for this issue. Its still an inconsistancy in handling RR changes.


Doesn't work

I have added the lua file in script folder, also added the game cupture in source but it still doesn't work.

See #1


Deleting not found file leads to crashing

'f' is not found file. Delele f and then compile the following code. Codon crashes.
test.py:
f = open('path')
f.write('data')
del f

Reproduce:
codon/codon-linux-x86_64/codon-deploy/bin/codon' run -release test.py
Crash message:
IOError: file path could not be opened

Raised from: std.internal.file.File.__init__:2
codon/codon-linux-x86_64/codon-deploy/lib/codon/stdlib/internal/file.codon:17:13
Aborted (core dumped)

Behavior on CPython(3.10.8):
Traceback (most recent call last):
  File "test.py", line 1, in <module>
    f = open('path')
FileNotFoundError: [Errno 2] No such file or directory: 'path'

Environment:
codon: v0.15.5 on Feb 6
Ubuntu 18.04

Hi @xiaxinmeng -- this is expected behavior; Codon throws an exception and aborts if it propagates out of the program (similar to C++ exceptions). Under the hood it calls abort().


[ISSUE] gatewayAddress Configuration cannot be configured

Describe the issue:
In the current configuration of the Camunda Platform Helm Chart for version 8.7 (Core), the gatewayAddress value is hardcoded in the ConfigMap templates:

[ConfigMap for Core](https://github.com/camunda/camunda-platform-helm/blob/18a83148cdb827ae6c91936e8c94e63528cb6ab0/charts/camunda-platform-alpha/templates/core/configmap.yaml#L274)
[Another reference in Core ConfigMap](https://github.com/camunda/camunda-platform-helm/blob/18a83148cdb827ae6c91936e8c94e63528cb6ab0/charts/camunda-platform-alpha/templates/core/configmap.yaml#L366)

For comparison, in version 8.6, similar hardcoded values exist in the following components' ConfigMaps:

[Operate ConfigMap](https://github.com/camunda/camunda-platform-helm/blob/18a83148cdb827ae6c91936e8c94e63528cb6ab0/charts/camunda-platform-8.6/templates/operate/configmap.yaml#L117)
[Tasklist ConfigMap](https://github.com/camunda/camunda-platform-helm/blob/18a83148cdb827ae6c91936e8c94e63528cb6ab0/charts/camunda-platform-8.6/templates/tasklist/configmap.yaml#L135)

This hardcoding makes the configuration incompatible with the documented OpenShift deployment procedure:

https://docs.camunda.io/docs/self-managed/setup/deploy/openshift/redhat-openshift/#using-openshift-routes
TLS encryption for services in OpenShift relies on Service Serving Certificates, which only include SAN values like <service>.<namespace>.svc.cluster.local and not the short service name (e.g., <service>).
As a result, connections to the gateway fail because the short name does not match the expected SAN.

To resolve this, the gatewayAddress value needs to be configurable, allowing compatibility with OpenShift’s TLS routing.
Related to P1 https://github.com/camunda/camunda-platform-helm/issues/2595

Actual behavior:

The gatewayAddress is hardcoded and does not support the configuration of a custom address.
This leads to connection failures for components attempting to connect to the Gateway when deployed in OpenShift with TLS routes.

Expected behavior:

The gatewayAddress should be configurable in the Helm values file, allowing users to specify the appropriate FQDN (e.g., <service>.<namespace>.svc.cluster.local).
Connections to the Gateway should succeed when deployed with OpenShift TLS Service.

How to reproduce:

Deploy the Camunda Platform Helm Chart in an OpenShift environment.
Configure OpenShift TLS Service as per [OpenShift documentation](https://docs.openshift.com/container-platform/4.17/security/certificates/service-serving-certificate.html).
Observe the connection failure due to the hardcoded gatewayAddress.

Logs:

Environment:

Platform: OpenShift (AWS)
Helm CLI version: e.g., 3.10.0
Chart version: 8.7.x
Values file:

Hi @leiicamundi I have more context now after exploring this issue a little bit.
The problem is only with tasklist. This env var for tasklist is now out of date: CAMUNDA_TASKLIST_ZEEBE_BROKERCONTACTPOINT
instead, you should use: CAMUNDA_TASKLIST_ZEEBE_GATEWAYADDRESS
Here is a full working values.yaml:
global:
  ingress:
    annotations:
      route.openshift.io/termination: edge
      route.openshift.io/destination-ca-certificate-secret: combined-tls-auto
    enabled: true
    className: openshift-default
    host: "combined.hamzatest.com"
    tls:
      enabled: true
      secretName: hamzatls
  identity:
    auth:
      publicIssuerUrl: "https://combined.hamzatest.com/auth/realms/camunda-platform"
      operate:
        redirectUrl: "https://combined.hamzatest.com/operate"
      tasklist:
        redirectUrl: "https://combined.hamzatest.com/tasklist"
      optimize:
        redirectUrl: "https://combined.hamzatest.com/optimize"
      webModeler:
        redirectUrl: "https://combined.hamzatest.com/modeler"
      console:
        redirectUrl: "https://combined.hamzatest.com/console"

identity:
  contextPath: "/identity"
  fullURL: "https://combined.hamzatest.com/identity"

operate:
  env:
    - name: CAMUNDA_OPERATE_ZEEBE_SECURE
      value: "true"
    - name: CAMUNDA_OPERATE_ZEEBE_BROKERCONTACTPOINT
      value: camunda-zeebe-gateway.hamza.svc.cluster.local:26500
    - name: CAMUNDA_OPERATE_ZEEBE_CERTIFICATEPATH
      value: /usr/local/operate/config/tls.crt
  extraVolumeMounts:
    - name: certificate
      mountPath: /usr/local/operate/config/tls.crt
      subPath: tls.crt
  extraVolumes:
    - name: certificate
      secret:
        secretName: zeebe-gateway-tls-auto
        items:
          - key: tls.crt
            path: tls.crt
  contextPath: "/operate"

optimize:
  contextPath: "/optimize"

tasklist:
  env:
    - name: CAMUNDA_TASKLIST_ZEEBE_SECURE
      value: "true"
    - name: CAMUNDA_TASKLIST_ZEEBE_CERTIFICATEPATH
      value: /usr/local/tasklist/config/tls.crt
    # - name: CAMUNDA_TASKLIST_ZEEBE_BROKERCONTACTPOINT
    #   value: camunda-zeebe-gateway.hamza.svc.cluster.local:26500
    - name: CAMUNDA_TASKLIST_ZEEBE_GATEWAYADDRESS
      value: camunda-zeebe-gateway.hamza.svc.cluster.local:26500
  extraVolumeMounts:
    - name: certificate
      mountPath: /usr/local/tasklist/config/tls.crt
      subPath: tls.crt
  extraVolumes:
    - name: certificate
      secret:
        secretName: zeebe-gateway-tls-auto
        items:
          - key: tls.crt
            path: tls.crt
        defaultMode: 420
  contextPath: "/tasklist"

console:
  contextPath: "/console"

connectors:
  enabled: true
  inbound:
    mode: oauth
  contextPath: "/connectors"
  env:
    - name: ZEEBE_CLIENT_BROKER_GATEWAY-ADDRESS
      value: "camunda-zeebe-gateway.hamza.svc.cluster.local:26500"
    - name: ZEEBE_CLIENT_SECURITY_PLAINTEXT
      value: "false"
    - name: CAMUNDA_CLIENT_ZEEBE_CACERTIFICATEPATH
      value: /usr/local/certificates/tls.crt
  extraVolumeMounts:
    - name: certificate
      mountPath: /usr/local/certificates/tls.crt
      subPath: tls.crt
  extraVolumes:
    - name: certificate
      secret:
        secretName: zeebe-gateway-tls-auto
        items:
          - key: tls.crt
            path: tls.crt
        defaultMode: 420

zeebeGateway:
  replicas: 1
  contextPath: "/zeebe"
  service:
    annotations:
      service.beta.openshift.io/serving-cert-secret-name: zeebe-gateway-tls-auto
  env:
    - name: ZEEBE_GATEWAY_SECURITY_ENABLED
      value: "true"
    - name: ZEEBE_GATEWAY_SECURITY_CERTIFICATECHAINPATH
      value: /usr/local/zeebe/config/tls.crt
    - name: ZEEBE_GATEWAY_SECURITY_PRIVATEKEYPATH
      value: /usr/local/zeebe/config/tls.key
    - name: ZEEBE_GATEWAY_CLUSTER_SECURITY_CERTIFICATECHAINPATH
      value: /usr/local/zeebe/config/tls.crt
    - name: ZEEBE_GATEWAY_CLUSTER_SECURITY_PRIVATEKEYPATH
      value: /usr/local/zeebe/config/tls.key
  extraVolumeMounts:
    - name: certificate
      mountPath: /usr/local/zeebe/config/tls.crt
      subPath: tls.crt
    - name: key
      mountPath: /usr/local/zeebe/config/tls.key
      subPath: tls.key
  extraVolumes:
    - name: certificate
      secret:
        secretName: zeebe-gateway-tls-auto
        items:
          - key: tls.crt
            path: tls.crt
        defaultMode: 420
    - name: key
      secret:
        secretName: zeebe-gateway-tls-auto
        items:
          - key: tls.key
            path: tls.key
        defaultMode: 420
  # contextPath: ""
  ingress:
    grpc:
      enabled: true
      className: openshift-default
      host: "zeebe-combined.hamzatest.com"
      tls:
        enabled: true
        secretName: hamzatls

zeebe:
  clusterSize: 1
  partitionCount: 1
  replicationFactor: 1

webModeler:
  enabled: true
  contextPath: "/modeler"
  image:
    pullSecrets:
      - name: registry-camunda-cloud
  restapi:
    mail:
      fromAddress<EMAIL_ADDRESS>
postgresql:
  enabled: true

The other option would be to modify the gateway address through the values.yaml but I don't see much value in that when you are already able to modify the other components correctly to connect to zeebe gateway


xcc/cmake: don't discard stderr; don't (ever!) use ERROR_QUIET

Remove ERROR_QUIET which is a bad idea 99.9% of the time. When any program makes the effort of using stderr, we really don't want to lose those error messages.
Using ERROR_QUIET in XCC is even worse because of how high maintenance XCC is; see another example in 4cba9e6d425e ("cmake: warn the user that the toolchain cache hides errors")
No one expects error messages to be silently discarded and especially not people not familiar with CMake (= most people); so hiding the following error stalled progress for a couple days:
Error: there is no Xtensa core registered as the default.

You need to either specify the name of a registered Xtensa core (with
the --xtensa-core option or the XTENSA_CORE environment variable) or
specify a different registry of Xtensa cores (with the --xtensa-system
option or the XTENSA_SYSTEM environment variable).

Executing the below command failed.  Are permissions set correctly?

Also capture stdout and print it on failure because you never know.
Indent the  ${CMAKE_C_COMPILER} --version line in the error message so CMake does not split that line.

Thanks for the prompt reviews! Two more and hopefully last PRs removing more ERROR_QUIET evil:

#66000
#66003

The first one is just a copy/paste of this one. They're both very small.


Hacktoberfest 2024 Add take action to auto assign contributors

This pull request introduces a new GitHub Actions workflow to automatically assign issues to contributors when they comment during the month of October. The workflow also logs when the action is skipped outside of October.
New GitHub Actions workflow:

.github/workflows/take.yml: Added a workflow named "Auto-assign issue to contributor" that triggers on issue comments. It includes two jobs:

assign: Assigns the issue to the contributor if the comment is made in October.
log_out_of_october: Logs a message indicating the action was skipped if the comment is made outside of October.

I think this might've been an accident. I can open a new PR or edit this current one to add the take action. This looks quite different from the take action

Looks like I can't edit it! I'm going to close this PR if that's okay with you @taniashiba ..and open a new one


Add storage -> rules in node ingress

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Ahmad Fahadh Ilyas 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.

replaced by https://github.com/ConsenSys/permissioning-smart-contracts/pull/265


Viewlet: header gets updated for each view within

Steps to Reproduce:

add a breakpoint here
open the debug view

=> the selectbox is created 4 times for each view within
I find that weird, I would only expect the header of a viewlet to change when there is a transition from 1 view to many views or vice versa. And I would possibly not expect this on first creation time of the view where its already known how many views are being added.

The issue here is panelViewet updates the title area whenever a split view is added.
However this is only needed for the explorer (as some actions can move to the title area).
So I have pushed a fix for this to be only done for the explorer viewlet
@sandy081 please reveiw

@isidorn View headers and title area are updated depending on the number of views. They are a pair and to be invoked together. I think moving updateTitleArea away from it makes it disconnected and broken.
updateHeaders does it smarty by checking if there is a single view or not. updateTitleArea should also do the same.
I would suggest to combine them into single method and do the updates?

@sandy081 thanks for feedback.
I think updateHeaders and updateTitleArea can not be moved to a single method since updateTitleArea needs to be called when transitioning in and out of single view mode and that is not the case with updateHeaders. Still I think I covered some of your concerns with the attached commit.
Feel free to change it if you do not like my approach.

@isidorn your argument makes sense. New change looks good to me.

@isidorn the SelectBox is created each time I open the debug view but never disposed it seems. There maybe more things leaking when switching views in the title area, I have not checked.

@bpasero yes that is because I am not caching my debug actions which I plan to tackle as part of this debt item https://github.com/Microsoft/vscode/issues/46867. However this is not related to the main issue thus closing this one


Remove obsolete //base:logging from unix/fcitx

Description
Remove obsolete //base:logging from unix/fcitx

Although I believe development has already shifted to Fcitx5 and fcitx is no longer maintained, I have included updates to follow the changes in Mozc's log-related headers, as well as patch modifications to support building with bazel.
Along with PR #63, I have confirmed that it is buildable.

test


Clerk provider not found

So I was testing vue-clerk in nuxt coz I wanna update the docs to add Nuxt installation guide, but somehow I got this error

Clerk provider not found

Facts:

Env is properly loaded
No visible installation error

Here's my setup:
// nuxt plugin
// vue-clerk.client.js

import { defineNuxtPlugin, useRuntimeConfig } from '#imports';
import { clerkPlugin } from 'vue-clerk';

export default defineNuxtPlugin({
	setup (nuxtApp) {
		const runtimeConfig = useRuntimeConfig();
		const clerkPublishableKey = runtimeConfig.public.clerkPublishableKey;

		console.log(clerkPublishableKey); // has value

		nuxtApp.vueApp.use(clerkPlugin, {
	      	publishableKey: clerkPublishableKey,
	    });
	},
});

// .env

CLERK_PUBLISHABLE_KEY=pk_test_c3dl...Rlax4 # reducted

// nuxt.config.js

...

runtimeConfig: {
 	public: {
    	clerkPublishableKey: process.env.CLERK_PUBLISHABLE_KEY,
  	},
},

plugins: [
	'~/plugins/vue-clerk.client.js',
]

...

Screenshot

Yo! You also need to add the clerk-js module to build.transpile. I have a Nuxt template actually if you want to check out - https://github.com/wobsoriano/nuxt-clerk-template

Yo! You also need to add the clerk-js module to build.transpile. I have a Nuxt template actually if you want to check out - wobsoriano/nuxt-clerk-template

Nice! Thanks @wobsoriano got it. Will review and update this issue, thanks!

When the vue-clerk/nuxt module? 😜

@Atinux soon! :)

Let me know if are still experiencing this issue! There's a Nuxt template for now - https://github.com/wobsoriano/nuxt-clerk-template


fix: removed count from random pet resource #97

Description
Removed count from random_pet resource
Motivation and Context
Changing the value of "recreate_asg_when_lc_changes" from true to false in module call causes cycle errors as random_pet resource is dependent on flag
Breaking Changes
No
How Has This Been Tested?
removed count from random_pet resource, called module with recreate_asg_when_lc_changes flag to true. Updated module call with flag set to false
tf 0.12.10

@antonbabenko Created this pr for cycle errors I was running into. Can you please take a look?

Hi @latikawadhwani !
Maybe closer to the end of the week. I am busy with other things before that.

I could not reproduce this issue using Terraform 0.14.7, so I am closing this issue.


Multiple .prototxt files

I have never used Caffe before. I want to convert [this model] https://github.com/ddtm/caffe/tree/grl/models/bvlc_alexnet) to TensorFlow. However, I found three .prototxt files under that folder. Namely, they are deploy.prototxt, solver.prototxt, and train_val.prototxt.
Then I tried to convert only one file followed by this error.
"Error encountered: Multiple top nodes are not supported."
How could I add those three files as input please?
Thank you in advance.

I suppose you should use deploy.prototxt as network structure  file and bvlc_alexnet.caffemodel for weights (http://dl.caffe.berkeleyvision.org/bvlc_alexnet.caffemodel).


cache node_modules for faster travis builds

Testing..not ready for review.

This change is

Ready for review - seems to shave at least a minute off CI times!

:thumbsup:, excited for the faster builds!


Missing module parameters

The output of a failure is limited to only the message, none of the parameters are displayed.
Is it possible to push the details of a module parameters?
Example below:
copy[]
src (or content) and dest are required

Thanks a lot for reporting this issue! This callback is still in active development and has no stable release yet, so a lot of things may not be working as expected.
That said a task failure should send an event that includes the task's parameters (so it should include src and content for the copy task). See https://github.com/DataDog/ansible-datadog-callback/blob/master/datadog_callback.py#L115.
What version of Ansible are you using, and are the parameters always missing ?

This would would be Ansible 1.7
Upgrading to 1.9 seems to have resolved this but opened another issue regarding SSL and the version of python 2.7.6 where I think the issue has been resolved in the latest 2.7 release which we'll need to move it at some point.
Given the above I will close this issue.
Thanks.


unconfirmed transactions

I was using electrum-dash 2.4.1 and could not send transactions using ubuntu 16.04.
I then followed instructions to upgrade to the latest version. I sent 0.2 dash successfully and followed that transaction up by sending a much larger amount that is now stuck in an unconfirmed status.
Block explorer is not showing the transaction ID either.
Please help!

Please let us know if this solution works with your situation https://github.com/dashpay/electrum-dash/issues/95#issuecomment-281944464 , or explain more about your situation, ex: which instruction? what OS?

Hi thelazier. Appreciate your attention on this issue but I'm not sure what other information I can provide.
I was sending Dash from address a to address b and it's stuck in an unconfirmed state in my electrum-dash and my coins are unavailable to me and the transaction ID is not showing up on the blockexplorer.
As per my first comment I am on ubuntu 16.04.
I raised a thread on reddit about this and it looks like I'm not the only one impacted:
https://www.reddit.com/r/dashpay/comments/5x6hhp/electrumdash_unconfirmed_transaction/
The solution you provided is for Windows.

Another solution , you can export private keys from electrum-dash into csv file and import them one by one into Dash Core via "importprivkey" command (you don't have to import every single key btw, just import the ones which are holding some funds).
I hope the team will release a working version soon.

Hi, the current Electrum Dash fork is maintained here: https://github.com/akhavr/electrum-dash
Please use that repo and report there if you have any issues.


confused trying to get artifact from a build

i am trying to figure out how to just like, get an artifact from a build (or is it a pipeline?) into my hands, and i am very confused as to how to do this.

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

ID: 861ce7a5-4fa4-55f1-2c97-46a9cc6a2f66
Version Independent ID: bdf954b9-9bbe-8b34-b674-71ad8153519d
Content: Publish and consume Pipeline artifacts in builds - Azure Pipelines
Content Source: docs/pipelines/artifacts/pipeline-artifacts.md
Product: devops
GitHub Login: @alexmullans
Microsoft Alias: amullans

@zvory sorry you feel this way. What do you have so far?
As this doc says, if the files you want to download are in a folder named say "some_folder", add this to the steps of your "azure-pipelines.yml" file:
steps:

task: PublishPipelineArtifact@0
inputs:
artifactName: 'artifactName'
targetPath: 'some_folder'

okay, i wanted to get the binary my pipeline was building, so i was specifying the file i wanted published. which meant when i tried to use this task, it was failing because you can only publish directories, and not files.
i should note that it's pretty unclear what this task does, Publish could mean anything here, when i tried this task it was because "all the other tasks didn't work, lets try this one, maybe this is what i want?"
everything works now, thanks

I was stuck on this also; I thought targetPath was the full path to a single file that I wanted to publish with the name artifactName. It would be useful if the docs said the targetPath is the name of the full directory to archive and publish.

We are currently making a change to Pipeline Artifacts which will allow you to specify the path to an individual file. In addition we support an .artifactignore (documentation). Its basically the same format as a .gitignore file and allows you to specify which files from the target path you want to upload.
By default we upload everything (except the .git folder), but with this you can prune what gets uploaded. I often do something like this:
!**/*
justthe
dirsthat
icareabout

We'll have a think about allowing you to specify multiple specific files to upload in the YAML definition itself. In theory it would be like an inline .artifactignore file where the !**/* is implied. Thanks for the feedback!

Where are the artifacts actually published? I just used the Publish Pipeline Artifact successfully on the first try. But there is no indication of where it ends up. If I go to the Artifacts tab of my Azure DevOps there is nothing there. I'm just prompted to connect to a feed. But I have no idea what that means.

But I have no idea what that means.

I mean, I know what the different types of feeds (Nuget, etc.) are, but none of them are relevant for the task I have at hand which is to publish and make available a file from my build.

I'm coming from CircleCI where the publish task is very similar, but in the build output there is a very clear link to the artifacts from the build. I don't see a similar type of link in the DevOps build.

Hi @mgwelch , sorry for the confusion here, it's good feedback for us though. Build Artifacts, Pipeline Artifacts, and Symbols aren't stored in "Azure Artifacts", that Artifacts tab is for consuming and publishing packages like NuGet, npm, Python, Maven, and Universal. Mitch can correct me if I'm wrong, but I believe Pipeline Artifacts are stored within the build itself, you can see how to see Build Artifacts here.

Yeah, the overloaded use of Artifacts is very confusing. I assumed there was a distinction between the two and did finally find the link. Thanks.

Very Odd. I found two links. The (now) very obvious Artifacts button on the top of the build page. That link contains all of the output I wanted.
But in the build summary progression I see an entry named: "Build artifacts published" with an artifact with the name I gave it. But clicking on that artifact brings up this file:
{"$id":"1","innerException":null,"message":"Artifact Documentation%20File was not found for build 2.","typeName":"Microsoft.TeamFoundation.Build.WebApi.ArtifactNotFoundException, Microsoft.TeamFoundation.Build2.WebApi","typeKey":"ArtifactNotFoundException","errorCode":0,"eventId":3000}

So I think my issue is resolved but the link in the summary progression is either broken or indicating some other issue

Hmm I'll get that looked at, thank you!


RFC: Discrete aparc/aseg segmentations - naming issues

Right now, we generate files with names like GLS005_ses-2_task-graphlocalizer_space-MNI152NLin2009cAsym_desc-aparcaseg_dseg.nii.gz. However, the contents of the segmentation are the same regardless of the task, because this is just the aseg/aparc resampled into standard space with the resolution of the BOLD, which is generally homogeneous.
Should we leverage res- here and minimize the number of different aparc/aseg conversions in standard spaces? (if all tasks have exactly the same shape & zooms, then generate just one conversion without res entity).

Do they always have the same shape and zooms?

(if all tasks have exactly the same shape & zooms, then generate just one conversion without res entity).

As I mentioned (see above) - no, they don't have to be matched. But it is the most common case.

Not only would this reduce duplication, but it would simplify figuring out which volumes are the same down the road.
For myself, I've definitely compared the aparc/aseg volumes manually to verify whether an ROI extraction, for instance, needs to use the respective segmentation for each run, or if I can just load the aparc for the first run and use that for the rest of the BOLD data.
If this is indeed always consistent for a combination of space and res, it might reduce some potential confusion.


curl insecure if ssl verification disabled

needs also casher update with handling of self-signed certs to be fully functional


instancio-quickcheck & docs misuse "property" term

The Instancio Quickcheck module documentation at https://www.instancio.org/user-guide/#quickcheck uses the phrases

The test case verifies that one of the properties of the Person type (in this case age property) should be a strictly positive number for any generated Person instance.

a custom property generation strategy can be provided:

the @Property annotation denotes an individual test case with the possibility to set the number of samples to generate for each property in question

the @ForAll annotation on test case method argument denotes the individual property to generate samples against

The test engine inspects all accessible instance methods of the test class to find out the candidates for the properties under test

That is, the Instancio Quickcheck module uses "property" synonymously with what Java calls a field or a component.
But this is not at all what "property" means in "property testing" or in the Haskell QuickCheck library that defined property testing or in the QuickCheck research paper the Instancio documentation appeals to or in https://www.schoolofhaskell.com/user/pbv/an-introduction-to-quickcheck-testing. The meaning of "property" here is closer to that of "fact" or "truth" or "invariant": "given some general input state, this general output state is guaranteed". For example, "the reversal of the reversal of an input is equal to the input" is a property that holds for all lists.
Applied to the examples from the Instancio user guide, replicated here for posterity:
@DisplayName("Test that each person has valid age")
@Property(samples = 100)
public void age(@ForAll Person p) {
    assertThat(i.age()).isGreaterThan(0);
}

@DisplayName("Test that each person has valid age")
@Property(samples = 100)
public void age(@ForAll("persons") Person p) {
    assertThat(i.age()).isGreaterThan(0);
}

public Arbitrary<Person> persons() {
    return Arbitrary
        .fromStream(Stream.generate(() -> Instancio
            .of(Person.class)
            .generate(Select.field(Person::age), gen -> gen.ints().min(1).max(150))
            .create()));
}

The "property" expressed is something like "a person's age is valid".
@ForAll seems redundant. @Property has already marked the case for property testing, which implies generated input for all of which the assertion must be satisfied. I recognize that in the second example @ForAll also selects a generation strategy but there is no clear reason this could not be solved by @Property or a counterpart to JUnit 5's @MethodSource.

"A person's age is valid" is a poorly expressed property -- what does age validity entail? Examples of more clearly expressed properties that relate to the user guide's second example are
public void age_is_not_negative(Person p) {}
public void age_does_not_exceed_150(Person p) {}

Unrelated to misusing the terminology, the second example also suffers from being tautological. It is plainly evident that if one generates an integer in the range [1 ; 150] then that integer is greater than 0. This weakness makes it much more difficult to understand what problem property testing solves and why Instancio's bid is useful. In fact, the second example can be trivially replicated with a plain JUnit 5 @ParametrizedTest and core Instancio (and it would still be tautological), i.e. instancio-quickcheck contributes nothing worthwhile.
Properties generally (always?) refer to behavior, not state, and thinking up meaningful and instructive behavior for a Person -- , which is probably just a POJO anyway -- is not easy for me. Even the example of "age ∈ [1 ; 150]" I could call into question: what is the age of a new-born baby? One could instead say something like "a person's full name starts with their given name, ends with their family name" but that statement would also be false in half the world. Rather than awkwardly shoehorn Person into these examples, https://www.schoolofhaskell.com/user/pbv/an-introduction-to-quickcheck-testing has multiple unfalsifiable and comprehensible examples of properties and property testing.

Would you be interested in submitting a PR?

Unfortunately my employment situation makes that difficult. This is only what I can easily do.

I'm also curious if you had a chance to use the quickcheck module and if you have any feedback on it as well?

Genuinely valuable feedback, I'm not sure. I don't have any projects where the approach is a particularly strong candidate, mainly academic interest. But I did whip up the following two implementations I believe to be morally equivalent:
final class ObjectMapperInstancioTest {

    private final ObjectMapper objectMapper = objectMapper();

    @Property(samples = 5)
    void ser_deser_roundtrips(Person input) throws JsonProcessingException {
        var s = objectMapper.writerFor(input.getClass()).writeValueAsString(input);
        var deser = objectMapper.readerFor(input.getClass()).readValue(s);
        assertThat(deser).isEqualTo(input);
    }
}

final class ObjectMapperJunitTest {

    private final ObjectMapper objectMapper = objectMapper();

    @ParameterizedTest
    @MethodSource("args")
    void ser_deser_roundtrips(Person input) throws JsonProcessingException {
        var s = objectMapper.writerFor(input.getClass()).writeValueAsString(input);
        var deser = objectMapper.readerFor(input.getClass()).readValue(s);
        assertThat(deser).isEqualTo(input);
    }

    public static Stream<Person> args() {
        return Instancio.of(Person.class).stream().limit(5);
    }
}

record Person(Name name, List<Address> addresses, List<ContactInfo> contactInfo) {}
record Name(String name) {}
record Address(String street, Country country) {}
record Country(String code) {}
interface ContactInfo {
    String get();
    record Phone(String phoneNumber) implements ContactInfo {
        @Override
        public String get() {
            return phoneNumber;
        }
    }
    record Email(String emailAddress) implements ContactInfo {
        @Override
        public String get() {
            return emailAddress;
        }
    }
}

When executed that looks like
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running example.ObjectMapperInstancioTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.273 s -- in example.ObjectMapperInstancioTest
[INFO] Running example.ObjectMapperJunitTest
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.099 s -- in example.ObjectMapperJunitTest

In this example, using serial execution, the execution time of @Property is substantially higher than that of @ParameterizedTest. However, at a hundred samples the overhead no longer dominates and @Property runs much faster than @ParameterizedTest. On the other hand, @ParameterizedTest is parallelizable and requires 1000 samples to reach the execution time of @Property under parallel execution. It is unfortunate the sample size is not reported in the output -- that misrepresents the amount of work the quickcheck module has to perform.
The quickcheck module makes it extremely easy and safe to perform this exact type of check. JUnit's parameterized test (JUnit 5 as well as JUnit 4) requires more ceremony that's more baroque, and at one point I accidentally changed only one of the three names that reference the parameter type and got a class cast exception. That's pretty cool.
As soon as I need to customize Instancio's behaviour, however, the playing field levels out. I can inject Settings with @WithSettings easily enough but there is no setting for printing out the seed, for example, and I don't have an InstancioApi<T> handle to invoke verbose() on. In the JUnit 5 @MethodSource implementation that's trivial, as it would be in a hypothetical ArbitraryGenerator<T> implementation. Customization also comes into play with subtype mapping, which is relevant for the ContactInfo interface -- it seems likely that it will frequently be necessary in practice to implement a generator.
@Property appears to Just Work™ with multiple parameters. @ParameterizedTest, in comparison, is very cumbersome with multiple parameters.

@commonquail thank you, I appreciate the feedback!
The quickcheck module is still labelled as "experimental" and is missing some essential features, such as reporting the seed, as you mentioned. Unfortunately, I haven't had much time to dedicate to it, as the core library already takes much of my time. I'm looking for other contributors to help drive it forward.
Additionally, there's the excellent jqwik library that has been around for a long time and offers similar functionality with more features. IMO, for instancio-quickcheck to justify its existence, it needs to provide something that jqwik doesn't. Here too, I'm looking for feedback from users to help drive it forward (or not).

@commonquail I updated the user guide. If you have any other feedback, please let me know.

That looks pretty good!


proficiency_choices order

under each classes/[index] there's an object called proficiency_choices which holds an array of proficiency objects. In every one of the classes the skill proficiencies is the first index of the array except for monk which is at index 2. I believe for consistency with the other classes it should be the first index. Also This is just a suggestion but maybe add a name attribute at each imdex to label the type of proficiency_choices it is (i.e. skills or instruments)

Gonna close this out following choice reform landing.


Add version: Henry++.simplewall version .3.6

\n\nAuto-updated by vedantmgoyal2009/winget-pkgs-automation
Microsoft Reviewers: Open in CodeFlow

Hey @jedieaston since you know this kind of stuff, would you be able to look at Simplewall's installer? Its not installing correctly when you use the /S switch, which wingetbot probably noticed too...
I DID make a issue over there but got yelled at that its Open Source and that i can fix it my self by submitting a PR... Which i obv can't when i don't know what i'm looking at.

Oh, I see. I thought it not writing to the ARP table was intentional, not that it literally wasn't installing at all. I'll take a peek.

Oh, I see. I thought it not writing to the ARP table was intentional, not that it literally wasn't installing at all. I'll take a peek.

Weeeell, it does "install", but its works more like extracting when the silent switch is included, if you run the installer in interactive mode everything works as expected, so yeah something is just wrong with their installer, which they don't like people pointing at 🤦♂

Their .nsi file isn't in that repo. Without that I can't figure out what's going on, but I'm guessing that they've set some of the properties to be set only if the GUI is rendered.
Maybe you should reopen that issue and ask them to post it.

Maybe you should reopen that issue and ask them to post it.

He probably can't because the issue was closed by the maintainer itself.

Well, darn. I'm not in a very "stirring stuff up" mood at the moment or I'd open another issue.
Since this PR is assigned, maybe we can get a validation override for the executable error? It is putting an executable in Program Files.

Their .nsi file isn't in that repo. Without that I can't figure out what's going on, but I'm guessing that they've set some of the properties to be set only if the GUI is rendered.

Is it this https://github.com/henrypp/builder/blob/master/setup_script.nsi?

Probably yes because this line exists in that... https://github.com/henrypp/builder/blob/master/setup_script.nsi#L185
I think he maintains one script for "all" his projects.

The start menu shortcuts and other areas we have trouble with all have IfSilent: Skip turned on. They might have a reason (maybe it interferes with their automatic updater?)

/azp run


Plex integration

Plex integration using Mantine's spotlight needs :

[ ] Asking for API key in add services component
[ ] Use the API key to list all the medias available on the Plex instance
[ ] Map those medias to the spotlight and make them openable
[ ] Add a keybind to open the search bar directly

Hi!
Can you tell me what i have to insert as "Plex Service url" ?
Regards!
Mike

Hi!
Can you tell me what i have to insert as "Plex Service url" ?
Regards!
Mike

Can you provide screenshots? I don't understand your question. Plex integration is not done yet if you are referring to that.

Ah ok... thanx for that info! I´m too fast! :)

It may be easier to integrate with tautulli instead of Plex as their API is a bit more friendly, and gives a lot more info.

I don't understand what can this plex integration do...could you pls give me some info? thanks

Reopening, as I implemented this working on #323 .
I suggest that we work on the Tautulli in a later release, as it does not share a common factor with this widget.

Hi, I am almost finished with this.
Can you confirm that the implementation is working for you?
You may use the branch or use the testing image: test-widget-media-server.
PLEASE NOTE:
Testing on development versions is at your own risk. Ensure that you have a proper backup, before switching your image.


Solid Router doesn't handle history.state correctly when using

When passing history state to <A> like this:
<A href={link()} state={sate()}>

the state is not available in the destination page/component. Calling history.state in the destination component's setup function or even within onMount will always return undefined. This seems to happen because @solidjs/router calls history.pushState after everything else in the navigation workflow happens.
I would imagine that updating the history would ideally be the very first step in the navigation workflow. This is to be consistent with the back/forward navigation triggered by popstate where the history is the very first thing to be updated. If the history is always updated first, then history.state will consistently be available to the page.

I think the issue is the router needs to support transitions, so it doesn't want to update the browser history until after that completes.
In the destination component, do you get a better result using the router's useLocation() state instead?
Alternatively, but perhaps not ideal, if you use a plain <a> tag then the url is updated first and the router only finds out about that afterward.

I agree with this. We should have state present as part of the transition exposed through our own primitives. I don't think there is a good decision either way if we can't tap into our Transitions.
Moving this to router repo as that is where it belongs.


Program stays in Alt Tab menu even when close to tray enabled.

I have the setting enabled to hide the program entirely, but it still appears in the Alt Tab menu and makes it difficult to tab between multiple programs. Any way to completely hide it and leave it running in the background?

Works perfectly. Thanks for the fast fix.


chore(risedevtool): use cdn to download kafka for recent versions

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Recent checks failing, I suspect is caused by this.

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

Documentation

[ ] My PR contains user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

It was reverted when introducing new kafka dl url: https://github.com/risingwavelabs/risingwave/pull/10391/files#diff-622ee11202b69f0dc6f728fea2db8846f2f3441cd3169d4174dbbfa93fbac8f2R8.

Back to normal after this PR.


travis_terminate: preserve previous return by default

the usual || travis_terminate idiom loses some information by not providing the old return value. Let's fix that.

What is the issue, exactly? travis_terminate ends the job immediately, and there is no information to preserve when the execution gets to it.


Build Fails on React Native 0.71.0 when fabric enabled

If fabric disabled it works fine after #497 but if i enable fabric this error appears again

If i remove MMKV it works in fabric without error

Does it also not work with RN MMKV 2.6.1?

@mrousavy yes

Same behavior after clean project during the build with fabric enabled.

@ievolution Did it work before clean with fabric?

@ievolution Did it work before clean with fabric?

Nope. The graddle sync is successful, but the build fails with the same error you have

I'm sorry, I can't reproduce this error.

@mrousavy Okay then i use it without fabric, thanks for the quick reply

@Titozzz can you reproduce this?

This is usually local cache issue

I'm sorry, I can't reproduce this error.

I create a simple repo, I have same problem with android build.
hope you can help.
https://github.com/sssajjad007/vendor

@sssajjad007 do you have the same error with fabric?

@sssajjad007 do you have the same error with fabric?

Yes

Yes

@sssajjad007 Please, Try it in RN 0.71.1 it might work, but I haven't tried it yet

This is usually local cache issue

@Titozzz  i cleared home gradle caches and app caches + removed node modules but it didn't help. Is there any chance the libraries might conflict with each other? Conflict with RNGH?
RNGH: ^2.9.0
react-native-mmkv: ^2.6.1
react-native: 0.71.1
Log after all cleans:

i created this repo on 71.1, but still have problem https://github.com/sssajjad007/vendor

@sssajjad007  me too

correct!
facing same issue  for the latest version of RN-0.71.1 with mmkv  same

yo, accidentally saw this problem and decided to check. Everything works fine for me, I attach a screenshot. Therefore, gentlemen, this is your local problem, perhaps a conflict with other dependencies or a cache.

package.json:
{
  "name": "fabric",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "lint": "eslint .",
    "start": "react-native start",
    "test": "jest"
  },
  "dependencies": {
    "@react-native-async-storage/async-storage": "^1.17.11",
    "@shopify/flash-list": "^1.4.0",
    "react": "18.2.0",
    "react-native": "0.71.1",
    "react-native-mmkv": "^2.6.1"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "@babel/preset-env": "^7.20.0",
    "@babel/runtime": "^7.20.0",
    "@react-native-community/eslint-config": "^3.0.0",
    "@tsconfig/react-native": "^2.0.2",
    "@types/jest": "^29.2.1",
    "@types/react": "^18.0.24",
    "@types/react-test-renderer": "^18.0.0",
    "babel-jest": "^29.2.1",
    "eslint": "^8.19.0",
    "jest": "^29.2.1",
    "metro-react-native-babel-preset": "0.73.7",
    "prettier": "^2.4.1",
    "react-test-renderer": "18.2.0",
    "reactotron-react-native": "^5.0.3",
    "typescript": "4.8.4"
  },
  "jest": {
    "preset": "react-native"
  }
}

yo, accidentally saw this problem and decided to check. Everything works fine for me, I attach a screenshot. Therefore, gentlemen, this is your local problem, perhaps a conflict with other dependencies or a cache.

package.json:
{
  "name": "fabric",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "lint": "eslint .",
    "start": "react-native start",
    "test": "jest"
  },
  "dependencies": {
    "@react-native-async-storage/async-storage": "^1.17.11",
    "@shopify/flash-list": "^1.4.0",
    "react": "18.2.0",
    "react-native": "0.71.1",
    "react-native-mmkv": "^2.6.1"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "@babel/preset-env": "^7.20.0",
    "@babel/runtime": "^7.20.0",
    "@react-native-community/eslint-config": "^3.0.0",
    "@tsconfig/react-native": "^2.0.2",
    "@types/jest": "^29.2.1",
    "@types/react": "^18.0.24",
    "@types/react-test-renderer": "^18.0.0",
    "babel-jest": "^29.2.1",
    "eslint": "^8.19.0",
    "jest": "^29.2.1",
    "metro-react-native-babel-preset": "0.73.7",
    "prettier": "^2.4.1",
    "react-test-renderer": "18.2.0",
    "reactotron-react-native": "^5.0.3",
    "typescript": "4.8.4"
  },
  "jest": {
    "preset": "react-native"
  }
}

@Yrsafam Wow cool! I think it conflicts with RNGH? can you use it with RNGH?

@Yrsafam , just saw you are using RN -0.71.1 with mmkv -"^2.6.1" , and your RN- app is running(correct!).
But, i'm getting link with using the current version of RN.

@devoren , yes, a similar error occurs when adding RNGH. In this case, it is difficult to say on whose side the problem is. Perhaps some class names really overlap and this should not be the case. Here you need to delve into the way to create a module based on the new react-native architecture. Unfortunately I don't have time for this right now

@98rahul , at the moment, the current version of react-native is 0.71.1. I suspect in your case it is easiest to upgrade to the latest version because perhaps the problem is in the area of responsibility of react-native, which has been fixed by the patch

@Yrsafam  using the latest version of RN-0.71.1 and running smoothly .
while on adding RN-mmkv -2.6.1 build fails error

@98rahul, There is too little input data. Is the project absolutely clean? Is there only one third-party dependency in the project in the form of react-native-mmkv? After experimenting with RNGH, after deleting the package, I could not restart the project until I cleared the cache through gradlew clean and deleted the android/app/.cxx folder

@Yrsafam  project  already built , moving with current version of RN-0.71.1,  from the official docs 0.71.1 as asyncstorage had been removed.
greetings -:)
issue been resolved .
just deleted the installed  ndk version mention in (android.build.gradle)  from the .....\AppData\Local\Android\Sdk\ndk\23.1.7779620
and start the run command.
ndk will ready -->> complete-->> finished.

Still facing this error (Error while merging dex archives) while compiling:

RN: 0.71.1
mmkv: 2.6.1
RNGH: 2.9.0

Cleaning Gradle (even deleting .gradle folder) doesn't help.
Compiling on fresh RN 0.71.1 only with mmkv working fine.

@dennisvk001 Yes, it conflicts with RNGH

After applying changes from #506 project compiled without any issues.

@dennisvk001 Yeah cool! Thanks for reminding me

After upgrading RN to v0.71.2 issue was resolved

This can help https://www.youtube.com/watch?v=iL-o8IJhwSQ&list=PLQhQEGkwKZUrempLnmxjt7ZCZJu1W3p2i&index=16


Metadata: Align entity name properties with CLR

resolves #1613

@rowanmiller Can you check the API review notes on this one? I thought we came to a different decision.

We decided to leave Name as-is and rename SimpleName to DisplayName and make it an extension method (though personally I don't think the extension method part is critical)

Thanks Rowan. I think it should be an extension method because then any implementation of the interface can use the same implementation.

@rowanmiller - Can you update #1613  or close it and file a new issue for this task?

@smitpatel - Closed. @anpete is going to be making that changes from the API review.


Revert "fix RequestCode overflowed issues:8868 (#8871)"

This reverts commit 327abe5d6eb0b74f48867821447e2f0718509a42.

Which Issue(s) This PR Fixes

Fixes #issue_id
Brief Description

How Did You Test This Change?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 47.56%. Comparing base (dd62ed0) to head (0859d05).

Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #8874      +/-   ##
=============================================
- Coverage      47.61%   47.56%   -0.06%
+ Complexity     11752    11733      -19
=============================================
  Files           1304     1304
  Lines          91043    91043
  Branches       11675    11675
=============================================
- Hits           43354    43302      -52
- Misses         42352    42395      +43
- Partials        5337     5346       +9

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


#361: fixed nightly build

Closes #361

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 59.759%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4662

Relevant Lines:
7511

💛  - Coveralls


[stable/jenkins] update plugins to latest version

What this PR does / why we need it:
This fixes a security vulnerability and ensures that Jenkins starts (at least today) without errors using the default plugins.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/lgtm


Reviewing stale branches

Little review cleanup makes sense:

https://github.com/HTPC-Manager/HTPC-Manager/tree/cardigan: The project is basically dead, so I suggest to remove the branch. When it is resurrected, the branch can be restored from base branches.
Kodi/VLC web player: https://github.com/HTPC-Manager/HTPC-Manager/compare/master2...HTPC-Manager:video_stream_temp
Much effort has gone into this one. As it's more than 6 years old, I just fear that used technologies are outdated, APIs changed etc. Would be interesting to test, but I think, if wanted, it is less work to start from scratch, using modern Kodi and/or VLC API, HTML5 etc, ignoring old browser support etc.
Fixes from the old master branch have been applied to master2 already, so that one can be removed.

So in short, I suggest to remove those three branches so that we have master2 only. An idea would be to create some sorts of dev branch, where we collect smaller commits for a while and release them after another review/testing on a regular basis, so that users don't see an update on every little change and e.g. the Docker container build server is not overloaded with rebuilds for a single little commit only 😄: https://github.com/linuxserver/docker-htpcmanager
Currently I aim to merge multiple PRs at once, when some more accumulated and having them open for review and testing for a while, so a salve of multiple commits work a little like a release 🙂.

Nice idea.  I agree with removing the cardigan and old master branches (the latter is confusing and we basically inherited it).
As for video_stream_temp, it sounds incredible, but on one hand it's too dated (our current code might not be compatible) and on the other hand it seems to be really big (code lines) as well as including code from other projects. I'm confident that the Kodi API is somewhat stable, but I don't think it's worth the effort unless you have the spare time. Certainly I don't :disappointed:

Okay, let's leave the video branch in place for now. Probably someone find the time to pick it up, even when just using it for spare parts to start this feature from scratch 🙂.

Old branches removed, and opened a PR + rebased the video player branch: #45
Was not too hard to resolve conflicts, pretty clean, of course no guarantee that the additional modules, the included library and the imports are Python 3 compatible, but it serves as basis to test and in case continue the effort that has been put into it.
I'll mark this issue hence as closed.


More battery information

Wouldn't it be good to add more detailed battery information on following lines ?
Defined in android.os.BatteryManager
BATTERY_STATUS_UNKNOWN (0x00000001)
BATTERY_STATUS_CHARGING (0x00000002)
BATTERY_STATUS_DISCHARGING (0x00000003)
BATTERY_STATUS_NOT_CHARGING (0x00000004)
BATTERY_STATUS_FULL (0x00000005)
With respect to health in battery information, the definition of value is as follows,
Defined in android.os.BatteryManager
BATTERY_HEALTH_UNKNOWN (0x00000001)
BATTERY_HEALTH_GOOD (0x00000002)
BATTERY_HEALTH_OVERHEAT (0x00000003)
BATTERY_HEALTH_DEAD (0x00000004)
BATTERY_HEALTH_OVER_VOLTAGE (0x00000005)
BATTERY_HEALTH_UNSPECIFIED_FAILURE(0x00000006)
BATTERY_HEALTH_COLD (0x00000007)

Part of bbc/hive_mind#173


Updates to API

Better exception handling

Adding ApiException that clients can throw with the data needed to be written in the response body
Handling ApiException as handled error
Keep general Exception handling, but wrapping the message into ApiException for proper response to the client

Adding BasicResource

BasicResource deals with API endpoints that are not reliant on Django ORM
BasicResource wraps dict object and makes it behave as regular object
Keeps the same interface as Resource object
The goal is for BasicResource to become abstract Resource in the future. And Resource will become DjangoResource

Response body for POST requests

Using JSONFormatter to output the resource into the response body on POST requests.

I like that we are surfacing the exception message, it's a much needed feature.  I am not crazy about losing the stack trace.  Logs are great, and it's good that the stack trace is going there.  However, especially from the front end of a web app, I've found it super helpful to have the stack trace next to the request that caused it.  This is especially true for un anticipated exceptions.

@arianamiri, about stack trace. We should never surface strack trace to the end-user stack. Besides, looking ugly, it gives client and end-user no benefit, it potentially can reveal information about our tech stack that can be exploited.
With that being said, I can add a check to add stack trace if we are running in debug mode.

@rue-mishakorablin i think that would be helpful

Aside from my comments, LGTM :+1:


V6 Performance Documentation and potential mem-leak

Issue description
This is intended as a feedback to the developers for the performance, as well as a potential bug I have found.
Documentation
I'm running the following setup on my Amazon Cloud:

My AWS Lightsail Instance with the 4 nodes uses an UBUNTU 20.4 TLS instance with the given size

Directly after starting my OT-Nodes, this is the memory consumption of the four nodes running on the machine
Attributes comma separated are:
Process ID, user , %mem , command

Each node takes roughly 153MB of RAM ( lets take 7.5% of 2048 MB)
Problem
I've been hammering my 4 nodes in 2 waves for roughly two hours.  I don't have memory monitoring activated, so I cannot show a diagram of them RAM usage yet.
After 2 hours of hammering jobs to those four nodes, my VM crashed.
I've analyzed the behaviour and saw the following:
CPU

It looks like the CPU usage has risen within 10 mins to 80%, within the next 10 mins to 100% and then crash the EC2 instance.
RAM
As I said, I don't have mem usage graph yet, as lightsail is not as good integrated into AWS yet, but I can see, that the memory consumption of each node rises from the starting 6-7% up to 20% within a timespan of a few hours.
This is the screenshot of the four nodes running for like 2 hours of constant publishing.
Process ID, user , %mem , command

Since neither database, nor blazegraph are running on the node, it looks like there is some memory problem within the OT-Node at the moment.
Do I analyze that correctly? Do you have another idea, what it could be?
If this is just regular behaviour, because the consumption is indeed intended to double across the usage then nevermind this ticket and just take it as a performance documentation :)
Expected behavior
The OT-Node RAM usage does not triple/quad in 2 hours, but stay constant
Actual behavior
Triples until my tiny machine runs OOM/CPU
Steps to reproduce the problem

Realize the architecture as mentioned above
Run 4 Nodes
Publish jobs each few seconds for a limited amount of time

Specifications

Node version: Latest v6.0.0-beta.1.23
Platform: Ubuntu 20.4 TLS
Node wallet: 0x03405Ce6eD71642EA50b0F6073c113f6Ea7149B6
Node libp2p identity: Many different, do you need them?

Contact details

Email: hansi1337 at gmail dot com
Discord: angrymob

Error logs
Disclaimer
Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to<EMAIL_ADDRESS>

The issue still persists with the latest 1.29 testnet version, thus I will migrate to the 20$ instance on AWS and check whether the memory leak is still persisting or will memory consumption will reach a plateau.

This issue is being closed as inactive due to the date of the last activity on it. However, we would love to see if you execute this test on latest code.
Thank you,
OriginTrail Team


Device label/ description should be improved

Currently the device description is very hard to notice, and is not visible on many parts like the device details screen. The device description should be more visible.

Have worked on this issue @ben-kaufman . For the cards components, I have designed them and placed them in design system page both for dark mode and light mode
Figma:
https://www.figma.com/design/m5eMFTKD391AiJAXaEzgxB/Bitcoin-Keeper?node-id=3132-4019&t=6LSw0Y7lq1yjdP6a-1
design system:
https://www.figma.com/design/m5eMFTKD391AiJAXaEzgxB/Bitcoin-Keeper?node-id=0-1&t=6LSw0Y7lq1yjdP6a-1
S.s:

I just have one question, Is this screen's new UI design alright? because if so I would have to make changes for all signers screens like this, it is better that I do it now otherwise things would get left out and mistakes will be repeated in app.
design screen:

I have made more Improvements/changes in the UI screens now please view @ben-kaufman , Also if this is right then let me know so I can make changes in all keys/signers screens along with their setting screens
Figma link:
https://www.figma.com/design/m5eMFTKD391AiJAXaEzgxB/Bitcoin-Keeper?node-id=3132-4019&t=FT0OBNt5Qi9LWrGc-1
s.s

Looks great 👍

I have edited all the signers/keys Screens now along with setting screens in the same design style as show above for both Dark and light mode now.
Figma Link:
https://www.figma.com/design/m5eMFTKD391AiJAXaEzgxB/Bitcoin-Keeper?node-id=3132-4019&t=FT0OBNt5Qi9LWrGc-1
S.s:

#5286 - Tapsigner's settings

Just to clarify, the design of the device tile should be updated in the same way to show description also in the Wallet creation and manage keys of the wallet.
Also in the sign transaction of a cold wallet, the list of devices will need to show the description. Attaching here screenshots of the relevant screens:

Verified this issue on keeper app v 1.3.1(429)


Spring AAD - Support webapp and resource-server in the same application

https://github.com/Azure/azure-sdk-for-java/issues/21005

Closing this issue, because it's duplicated with this one: https://github.com/Azure/azure-sdk-for-java/issues/19816


Identify model testing blockers

To make it easier to integrate model testing and validation as part of a CI pipeline, we need to identify current blockers / things which are not smooth.
Suggested setup:

Rasa project including action server

Things to do:

Validating training data
Testing NLU
Testing Core
e2e testing of the model

The docs should help on the single steps: https://rasa.com/docs/rasa/user-guide/evaluating-models/

@alwx Any news on this?

@wochinge not really, because I am currently busy with other issues.
But I will find the time, check it tomorrow, and update you.
Sorry for the delay.

Cool, thanks. Just important so that we can decide what to do here for our okr

@wochinge
So I spent some time today checking it again and remembering my previous experience.
Again, everything was relatively easy and straightforward, but maybe that's because I already know that the action server needs to be running and how some of the things work.

How was writing the end-to-end tests for you?

Honestly, the examples/formbot/tests/end-to-end-stories.md helped me more than the documentation: https://rasa.com/docs/rasa/user-guide/evaluating-models/#end-to-end-evaluation
But that's just me — I prefer learning by exploring examples. Anyway, the process of writing e2e tests is relatively easy and straightforward — the only thing I am thinking of is giving more examples in the documentation or just providing links to already existing ones.

Did you find enough documentation?

Yes, I think https://rasa.com/docs/rasa/user-guide/evaluating-models doc gives more than enough information.

How did end-to-end testing go with the action server? Did you start it before and then executed things?

I've forgotten to start it when I was executing tests for the first time, but then I saw an error and understood that the server needs to be running because otherwise actions cannot be executed. I guess it's more or less obvious for everyone who's writing code and running tests, and I am not sure if any explicit information needs to be added (especially considering the fact that it's very hard not to notice errors).

cc @TyDunn

@wochinge Thanks for the nudge. I have been thinking about and am now writing my thoughts down here: https://docs.google.com/document/d/1PNavef4M3WyA6drAT9KPStSx8FuUPvWcFICpKS0epZU/edit

@wochinge I have been thinking about this and will now record my thoughts. I will polish this scope and then ask for feedback from the squad later today: https://docs.google.com/document/d/1PNavef4M3WyA6drAT9KPStSx8FuUPvWcFICpKS0epZU/edit


Is it neccesary to configure discovery on client side when using a Kubernetes service?

If clients connect to server through a Kubernetes service, Is it neccesary to configure discovery on client side?

You cannot connect through a kubernetes service, as a Hazelcast client needs to connect to all cluster members not just a single one. There's a dummy client configuration which is ok with "one member" but not sure it'll work over a kubernetes service, never tried it.
That said, it also means clients cannot (are not supported) to run outside the kubernetes environment.

Perfect. Thank you very much for the prompt reply.

You're welcome, gonna close the issue :)


chore(deps): update terraform terraform-ibm-modules/secrets-manager/ibm to v1.18.5

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/secrets-manager/ibm (source)
module
patch
1.18.4 -> 1.18.5

Release Notes

terraform-ibm-modules/terraform-ibm-secrets-manager (terraform-ibm-modules/secrets-manager/ibm)
v1.18.5
Compare Source
Bug Fixes

deps: update terraform terraform-ibm-modules/event-notifications/ibm to v1.10.16 (#208) (bceafdb)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline


Don't export attributes that are namespace definitions

Description of the pull request:
Currently if you drop an xmlns:whatever in an element, the whatever portion will also show up as a regular attribute. This checks for the xmlns namespace and skips popping those out into the dom.
I've no idea why behavior would be different in a fiddle than run locally. Maybe something to do with jsfiddle declarations?
Fixes the following issues:
sort #2560
Is breaking:
Shouldn't be.
Reviewers:
Anyone familiar with xmlns?

It seems phantom is not a fan. Does anyone more familiar with the subject matter know if this is one of those things that different browsers do completely differently? The test passes in Chrome.


tests: mem_protect/userspace: exclude xenvm boards

This excludes xenvm and xenvm/xenvm/gicv3 platforms from userspace tests. The tests will run as long as the arch has CONFIG_ARCH_HAS_USERSPACE enabled. However, commit cb19bd4fc2541931beb0e1f157127f7a50a082d4 explicitly disabled CONFIG_USERSPACE for xenvm and xenvm/xenvm/gicv3 boards. This results in build errors as none of the userspace code is being built.

use #70129 instead.


Add lakefs instrumentation

Linked Issue
Closes #6216

I'm not in favour of a new Docker image for quickstart, sorry. This is for two reasons:

Quickstart should ideally be a "runway" for users to get up and running (and take off, to continue the analogy)—using a dedicated image is like a dead-end road. There are exceptions to this rule but they need to be a good one, not just to make it easier to instrument
If we use a dedicated image we need to explain to the user why, and that explanation is too thin to hold weight IMHO

I'm not in favour of a new Docker image for quickstart, sorry. This is for two reasons:

Quickstart should ideally be a "runway" for users to get up and running (and take off, to continue the analogy)—using a dedicated image is like a dead-end road. There are exceptions to this rule but they need to be a good one, not just to make it easier to instrument
If we use a dedicated image we need to explain to the user why, and that explanation is too thin to hold weight IMHO

Appreciate the feedback, please suggest an alternative for identifying execution as part of the quickstart guide

@nopcoder Please re-review quickstart refactor

Firstly: I think this is a positive change and a good direction 👍🏻
However grimacing I have some nits, as well as a blocker.
Potential blocker: This change will remove quickstart email capture
From a DevEx point of view I am 100 100 100 100 100 in favour of this, but last time I did it it caused ructions elsewhere ;)
We need to make it clear to all stakeholders (@iddoavn, @einato , @ozkatz et al) the impact and get agreement from them.
The solution here is to implement #6033 / #6204 first.
Nits
Pre-create the quickstart repo
Since we know they're running the quickstart, we should pre-create the quickstart sample repo
Sample repo instructions
These need updating for the new --quickstart flag
Startup Banner
The startup banner should reflect the startup mode; if the user is using --quickstart then echo the pre-baked creds to stdout and not direct them to complete the setup process at http://<IP_ADDRESS>:8000/setup
You already have this change but only in the docs, whereas it should be conditional and in the lakeFS output itself
i.e. instead the current startup banner:

     ██╗      █████╗ ██╗  ██╗███████╗███████╗███████╗
     ██║     ██╔══██╗██║ ██╔╝██╔════╝██╔════╝██╔════╝
     ██║     ███████║█████╔╝ █████╗  █████╗  ███████╗
     ██║     ██╔══██║██╔═██╗ ██╔══╝  ██╔══╝  ╚════██║
     ███████╗██║  ██║██║  ██╗███████╗██║     ███████║
     ╚══════╝╚═╝  ╚═╝╚═╝  ╚═╝╚══════╝╚═╝     ╚══════╝

│
│ If you're running lakeFS locally for the first time,
│     complete the setup process at http://<IP_ADDRESS>:8000/setup
│

│
│ For more information on how to use lakeFS,
│     check out the docs at https://docs.lakefs.io/quickstart/
│

│
│ For support or any other question,                            >(.＿.)<
│     join our Slack channel https://docs.lakefs.io/slack         (  )_
│

Should be this for quickstart:

     ██╗      █████╗ ██╗  ██╗███████╗███████╗███████╗
     ██║     ██╔══██╗██║ ██╔╝██╔════╝██╔════╝██╔════╝
     ██║     ███████║█████╔╝ █████╗  █████╗  ███████╗
     ██║     ██╔══██║██╔═██╗ ██╔══╝  ██╔══╝  ╚════██║
     ███████╗██║  ██║██║  ██╗███████╗██║     ███████║
     ╚══════╝╚═╝  ╚═╝╚═╝  ╚═╝╚══════╝╚═╝     ╚══════╝

│
│ You are running lakeFS in quickstart mode.
|   Login at http://<IP_ADDRESS>:8000/
│
|    Access Key ID    : AKIAIOSFOLQUICKSTART
│    Secret Access Key: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
│

│
│ For more information on how to use lakeFS,
│     check out the docs at https://docs.lakefs.io/quickstart/
│

│
│ For support or any other question,                            >(.＿.)<
│     join our Slack channel https://docs.lakefs.io/slack         (  )_
│

I realise that the creds are echoed earlier on as part of the bootup but from a DX point of view it's not obvious particularly when there is a user-facing dialog later on in the stdout

Thanks,
Regarding the blocker:
As you stated - this will be resolved in https://github.com/treeverse/lakeFS/issues/6033, so we can wait until that issue is resolved before merging this one - in that case there's no impact so there's nothing to discuss.
Nits:
Pre-create the quickstart repo
That's a good idea - but outside of this PR scope. We can open an issue for that if we want this feature
Startup Banner
Since we expected users running quickstart as part of the quickstart tutorial, we can assume they will continue to the next steps where we added the credentials.
Customizing the banner is a good idea, but I think the solution we have is good enough for now

I'd like both the nits addressed as part of this PR please. If we're implementing a --quickstart flag (which is a great idea) then it should behave as a proper quickstart, not a partial one nor rely on users to RTFM ;)

@rmoff Added the banner changes - but I have to insist on the sample repo creation. This PR should focus on the issue at hand which is providing a way to understand where lakefs is run from.
The quickstart flag was created out of necessity and not out of requirement. If we think we should add the creation of a sample repo as part of the "quickstart mode" we should discuss and do it as part of a designated context (issue)


Slow CTC beam search decoder

Current CTC beam search decoder runs on single CPU core. So it might be a bottleneck for speech recognition inference.

@bill-kalog : Hi, I'm interested in your approach, could you please explain more about it? How you can use this ctcdecode combine with OpenSeq2Seq because I think the ctc-decode in OpenSeq2Seq is already built for their models. Which flags or hyperparameters have you replaced to use this ctc-decode?

@ngochuyenluu, we already integrated Baidu beam search decoder in OpenSeq2Seq. That is the same decoder as in ctcdecode project. Please see https://nvidia.github.io/OpenSeq2Seq/html/speech-recognition.html#decoders for more details.

@vsl9 hello, can i use the baidu ctc decoder in training? and i also found that the baidu WarpCTC suppports gpu too, can we use it in this openSeq2Seq project?


Fix group merge phase not update the GroupExpression state which will merge other GroupExpression

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #5203
Problem Summary(Required) ：

In #5007, I add a function replaceBestExpression which update the low cost groupExpression of the group. but forget to update the state (low cost table, output property map) of the group expression, this will result in can not find the best plan in optimizer

[FE PR Coverage check]
:disappointed: fail : 7 / 12 (58.33%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/optimizer/GroupExpression.java
6
11
54.55%

:large_blue_circle:
com/starrocks/sql/optimizer/Memo.java
1
1
100.00%

please add UT

[FE PR Coverage check]
:disappointed: fail : 7 / 12 (58.33%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/sql/optimizer/GroupExpression.java
6
11
54.55%

:large_blue_circle:
com/starrocks/sql/optimizer/Memo.java
1
1
100.00%

@Mergifyio backport branch-2.2


Add pattern for YouTube Shorts

Update convertUrlToId to accept YouTube Shorts URI

Thank you for your contribution, but I'm working on rewrite of the package using youtube_player_iframe under-the-hood.
So, the change won't be necessary as the iframe package already supports shorts url.


fatal: '/hello' does not appear to be a git repository

Hello,
When I push data to my first test app, I get the following:
pygy@Albert ~/tmp/hello> git remote add dokku ssh://git@dokku.me:2222/hello
pygy@Albert ~/tmp/hello> git push dokku master
fatal: '/hello' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

A headless, empty repository has apparently been created, though (not sure if it is complete):
vagrant@dokku:/home/git$ ls hello
HEAD  branches  config  description  hooks  info  objects  refs

Thee files look legit, and the directories contain etheir nothing, empty folders, or sample hooks.
OS X 10.8. I'm using a Vagrant VM based on the provided Vagrantfile. Doku has been installed as described in the README. The public key has been succesfully uploaded.

i tried to address this here in the wiki. pl take a look.
https://github.com/debianmaster/Notes/wiki/Dokku-Auth-Setup

In the penultimate line what is "devmachine"?
s/not/now/ and s/devmachine/dev machine/ in the last sentence.
Otherwise it looks fine. Note that I'm not using dokku right now.


[Bug] When starting oracle-cdc with the specified "StartupOptions.latest()", it causes a significant difference between "currentScn" and "startScn".

Search before asking

[X] I searched in the issues and found nothing similar.

Flink version
flink-1.15.2
Flink CDC version
flink-connector-oracle-cdc-2.4.2
Database and its version
Oracle 12c 数据库
Minimal reproduce step
    SourceFunction<String> sourceFunction = OracleSource.<String>builder()
            .url(connectInfo.get("conn_url"))
            .hostname(connectInfo.get("conn_host_name"))
            .port(Integer.parseInt(connectInfo.get("conn_port")))
            .database(connectInfo.get("orc_cdb"))
            .schemaList(sourceSchema)
            .tableList(infoMap.get("source_table_list"))
            .username(connectInfo.get("conn_user_name"))
            .password(connectInfo.get("conn_password"))
            .startupOptions(StartupOptions.latest();)
            .debeziumProperties(prop)
            .deserializer(new JsonDebeziumDeserializationSchema())
            .build();

What did you expect to see?
The difference between "currentScn" and "startScn" is very small.
What did you see instead?
log display：
2024-01-17 16:45:49,249 INFO  io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource [] - Transaction 26001d00e0ef0100 was pending across snapshot boundary. Start SCN =<PHONE_NUMBER>45, snapshot SCN =<PHONE_NUMBER>35
2024-01-17 16:45:49,249 INFO  io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource [] - Transaction 560008002cc30600 was pending across snapshot boundary. Start SCN =<PHONE_NUMBER>55, snapshot SCN =<PHONE_NUMBER>35
2024-01-17 16:45:49,249 INFO  io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource [] - Transaction 380018006f330700 was pending across snapshot boundary. Start SCN =<PHONE_NUMBER>70, snapshot SCN =<PHONE_NUMBER>35
2024-01-17 16:45:49,249 INFO  io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource [] - Setting commit SCN to<PHONE_NUMBER>34 (snapshot SCN - 1) to ensure we don't double-emit events from pre-snapshot transactions.
2024-01-17 16:45:49,249 INFO  io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource [] - Resetting start SCN from<PHONE_NUMBER>35 (snapshot SCN) to<PHONE_NUMBER>21 (start of oldest complete pending transaction)
2024-01-17 16:45:53,244 DEBUG io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource [] - Using Top SCN calculation<PHONE_NUMBER>20 as end SCN. currentScn<PHONE_NUMBER>57, startScn<PHONE_NUMBER>20
2024-01-17 16:46:05,860 DEBUG io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor [] - Fetching results for SCN [166289160920,<PHONE_NUMBER>20]
2024-01-17 16:46:14,088 DEBUG io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor [] - Skipping event START (SCN<PHONE_NUMBER>23) because it is already encompassed by the initial snapshot
2024-01-17 16:46:14,088 DEBUG io.debezium.connector.oracle.logminer.processor.AbstractLogMinerEventProcessor [] - Skipping event COMMIT (SCN<PHONE_NUMBER>24) because it is already encompassed by the initial snapshot
Using Top SCN calculation<PHONE_NUMBER>20 as end SCN. currentScn<PHONE_NUMBER>57, startScn<PHONE_NUMBER>20
The difference between "currentScn" and "startScn" is 92,328,737, resulting in significant data latency.
Anything else?
no
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

Please use com.ververica.cdc.connectors.oracle.source.OracleSourceBuilder.OracleIncrementalSource

Closing this issue as it is no longer valid or requires additional information. If the issue still exists, please report it on Apache Jira under the project Flink, using the component tag Flink CDC. Thank you!


Uninitialized Read in WavpackSetConfiguration64()

uninit-config.wav.zip - contains fuzzed input
The parsing of the attached file uninit-config.wav leads to a read of an uninitialized location in memory. The uninitialized read can be uncovered using a tool such as Valgrind or MemorySanitizer. For example:
$ valgrind ./cli/wavpack uninit-config.wav
==21125== Memcheck, a memory error detector
==21125== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==21125== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==21125== Command: ./cli/wavpack uninit-config.wav
==21125==

 WAVPACK  Hybrid Lossless Audio Compressor  Linux Version 5.1.0
 Copyright (c) 1998 - 2019 David Bryant.  All Rights Reserved.

creating uninit-config.wv,==21125== Conditional jump or move depends on uninitialised value(s)
==21125==    at 0x425EEE: WavpackSetConfiguration64 (pack_utils.c:198)
==21125==    by 0x4137E8: ParseDsdiffHeaderConfig (dsdiff.c:318)
==21125==    by 0x408A94: pack_file (wavpack.c:1777)
==21125==    by 0x404AE2: main (wavpack.c:1273)

It appears that this is an uninitialized read of the field config->sample_rate on this line.

This is fixed now, thanks!


Azure OpenAI: 2023-06-01-preview update for image generation

(Description to be completed)

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.AI.OpenAI


Skip SSL Verification Mode

In the connection between Filebeat and ES im using the setting: ssl.verification_mode: "none"
How can I skip the SSL verification in your plugin? My Elastic instance is accessible via https but there is no right certificate available.

Hi @jensdon ,
Sorry for the very late response, I haven't been maintaining this repository as well as I should have lately. Have you been able to fix your issue?
Thanks,


Can Khadas Edge2 board be supported?

I modified the ARM-CL and tested it on the Khadas Vim3 Pro board. Now I want to utilize a more efficient CPU and GPU. Could I directly transplant my code to the Khadas Edge2 board?

Thank you! It is very helpful.  By the way, is there a way to include the NPU invocation of the Khadas Edge2 board in the existing ARM-CL?

Hi @zyujie-ioo
ACL only supports ARM CPUs and GPUs.
Hope this helps.

Okay, thanks. Do you know any compiler which supports executing the model using the CPU, GPU, and NPU of the Khadas Edge2 board? I checked ARM-NN, but there seemed to be no support for this board's NPU.

Hi @zyujie-ioo
For Linux you can use gcc > 6.3
For Android any recent version of the ndk will support armv8.2
Hope this helps.


Large datasets: Bitmaps, Jaccard distance with Roaringbitmaps

Following the approach here: https://umap-learn.readthedocs.io/en/latest/sparse.html; I'm sending UMAP a sparse float dataset, consisting only of 1.0 32-bit float values and zeroes, using Jaccard distance.
I'm finding myself at the limits with a big sparse matrix (25k x 175k, 1M non-zero values), fit() taking several hours and eating most of my RAM including with low_memory=True and LIL dataset input. (my needs in dataset size would be 75k x 400k, 13M values)
I was wondering if UMAP could be easily amenable to use Roaringbitmaps as input. It has great compression, on top of using 1 bit instead of 32. It also has fast vectorized operations for Jaccard distance with intersection_len / union_len.
I don't know if the iterations of UMAP necessitate to convert that dataset immediately to floats, but if it only needs the input dataset and to compute a distance Roaringbitmaps could help.
Would that be doable? Could someone who does not know much of the internals of UMAP but is ok in python hack a solution in minimal time?

What you really need is a fast approximate nearest neighbor computation. You can potentially use roaringbitmaps for that, and then UMAP does support being given the nearest neighbors (as knn_indices and knn_dists). Managing to plumb roaring bitmap into the internals (which really means plumbing it into pynndescent) would be a non-trivial project. But if you can use roaringbitmaps or another package that makes use of it for the nearest neighbor search then you can shortcut that whole stpe in UMAP.


Changes to pulseJobs documents collection during Job execution are reverted on document updates

Description
Hi,
will be nice if changes to document into pulseJobs collection are kept even if the updates occurs during execution of job.
For example if you update document filed "disabled" to true while job is running, on first update done by pulse library it will be reverted to its value at the begin of the execution.
I think that Pulse library internally before saving the document into pulseJobs has to read the actual state of job, or update only the fields actually the library needs to update (like lockedAt, progress, lastFinishedAt, ...)
What do you think about this enhancement?
Code example
No response
Additional context
No response

@tiberioalunni
Interesting, could you provide an example code that demonstrates this situation?


az configure doesn't check the validity of the arguments/values before configuring

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
CLI tells me rg isn't avail after I'd already explicitly configured it

To Reproduce

used az configure to set global rg

created appservice plan but ended up failing because rg isn't actually avail

Expected behavior
If the rg to be set at az configure isn't actually a valid rg, the tool should not plainly accept the value. It should first check the validity of the resource and return an error if it's not a valid rg. Else it would give a false impression that the configure has been successful and that the defaulted values are readily avail for use -- which is not in this case
Environment summary
CLI 2.10.1 on windows
Additional context

Another follow up Q...
Is there a way for folks to clear/delete any defaulted values in the CLI without going to the file and edit it?
I must be missing something but can't seem to find it either in doc or via intool help

add to S175

Hi @chenlomis, for the original post, this behavior is expected. Imagine these scenarios:
# The user sets the default resource group first
> az configure --default group=rg1

# Create the resource group
> az group create -l westus -n rg1

# Use the configured default resource group
> az vm list

If we enforce the validation in az configure, this scenario will fail at az configure because of the non-existing resource group.
Or
# The user sets the default resource group first
> az configure --default group=rg1

# Switch the active subscription
> az account set --subscription <subscription_id>

# Use the configured default resource group
> az vm list

There are 2 cases:

The old subscription has the resource group, but the new subscription doesn't. In this case, after switching the subscription, the configured default resource group becomes invalid (no way for CLI to detect that).
The old subscription doesn't have the resource group, but the new subscription does. The az configure command will fail at the beginning.

That's why the validation logic is not included in az configure, but is deferred to when an ARM command is actually executed.

For the second question, moving to a separate issue https://github.com/Azure/azure-cli/issues/14853.

The error could be something like "can't list vm in rg1 because you changed subscription".

This is difficult to achieve because the configuration is not bound to a subscription. In other words, all configurations apply to all subscriptions. So, it is difficult for Azure CLI to detect if the default resource group becomes invalid due to

subscription change, or
that the resource group is simply deleted by the user.

We can of course implement this but it requires big development efforts. The current config file is in ini format thus it is difficult to set complex properties:
[defaults]
group = rg1

If we switch to JSON, we can make the default resource group bound to a certain subscription, like
{
    "subscriptions": {
        "0b1f6471-1bf0-4dda-aec3-cb9272f09590": {
            "defaults": {
                "group": "rg1",
                "location": "westus"
            }
        },
        "bf664f93-b001-4dc8-a597-148bbc173cfd": {
            "defaults": {
                "group": "network-infra",
                "location": "eastus"
            }
        }
    }
}


Need to add "contains" filter operator in opensearch-dashboard gui

Hi Team,
We want to search the data based on contains operator filter, but in the below attachment's there was no contains operator.

But in below screen shot we have contains operator, for other application.

Can any one suggest us like how we search the data with contains filter in opensearch.
If this feature not available in opensearch, please let us know when it will available.
Thanks,
Anil

Catch All Triage - 1 2 3 4 5 6


Refactor the "Users Manipulation" docs page

This page: https://casdoor.org/docs/user/manipulation is very low-quality, not easy-to-follow wording, needs a total rewrite and put it to another place:

@leo220yuyaodog


Fix open redirect check for more cases

If redirect_to parameter has set value starting with \\example.com  redirect will be created with header Location: /\\example.com that will redirect to example.com domain.

How about a regex like [\\/]{2}?

I would avoid regex for this use case

As this part (context package) of code has no unit tests that would would allow creating context etc to test on this is not easy one to add one, especially for such small change

This still is not perfect solution as this would need to be actually context aware (like redirecting only to valid Gitea URLs etc) like stated in this FIXME comment:
https://github.com/go-gitea/gitea/blob/263ed09bbfebfbd7f53f2165c2175c2afab5a42d/routers/web/user/profile.go#L366
In future this should be fixed so I would avoid making changes just to be able to test small portion of this

I was unable to create a backport for 1.19. @lafriks, please send one manually. :tea:
go run ./contrib/backport 25143
...  // fix git conflicts if any
go run ./contrib/backport --continue


[Device Support Request] Tuya/MOES "Smart Brightness Thermometer" TS0222 _TYZB01_kvwjujy9

This device seems to be sort-of supported -- the measurements do come through ZHA. However, something in the communication goes wrong, and the device keeps resetting itself every few minutes as soon as it's part of the zigbee network.
Here's the device signature:
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0106",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0400"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    },
    "2": {
      "profile_id": 260,
      "device_type": "0x0302",
      "in_clusters": [
        "0x0402",
        "0x0405"
      ],
      "out_clusters": []
    }
  },
  "manufacturer": "_TYZB01_kvwjujy9",
  "model": "TS0222",
  "class": "zigpy.device.Device"
}

Which all seems fine (I think? weird that things like measurements are "in" clusters but zigbee always confuses me).  I can try to provide some logs of the comms right before the device resets.

You can taking one look on #961 there some users is trying getting it working and its looks like the time cluster is making the device leaving the network if its not getting OK response on it.
Great longs you have posted !!

  Thank you, sorry for the spam!

No problems but i think its better working together on the same device then its being easier getting it working and not need reinventing the wheel one more time or 2 ;-))
I have doing the same some time and the making one PR for one device and some one have doing the same some days before and getting it added so the work was for no.


Android build fails: Cannot find symbol this.setIntent(intent);

When i'm trying to build my project with the latest version i'm getting the follwing error:
:compileArmv7DebugJavaWithJavac/.../platforms/android/src/io/branch/BranchSDK.java:62: error: cannot find symbol         this.setIntent(intent);             ^   symbol: method setIntent(Intent)
Maybe this issue is connected with #82 ?

+1

Sorry team: https://github.com/BranchMetrics/Cordova-Ionic-PhoneGap-Deferred-Deep-Linking-SDK/pull/85

#85 fixed this and the android resume issue.  Great work!

Phew! Sorry about the delay in resolution :(


[Dependencies] How to remove lodash-es from final build

Version
4.2.3
Environment info
Environment Info:

  System:
    OS: macOS Mojave 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
  Binaries:
    Node: 11.0.0 - ~/.nvm/versions/node/v11.0.0/bin/node
    Yarn: Not Found
    npm: 6.9.0 - ~/.nvm/versions/node/v11.0.0/bin/npm
  Browsers:
    Chrome: 80.0.3987.132
    Firefox: Not Found
    Safari: 13.0.5
  npmPackages:
    @storybook/vue: ^5.0.3 => 5.0.3
    vue-vimeo-player: 0.0.9 => 0.0.9
  npmGlobalPackages:
    @vue/cli: 4.2.3

Steps to reproduce

Start new project
Run build task
Observe lodash-es in the dependencies - 493Kb

What is expected?
No dependencies of lodash-es
What is actually happening?
lodash-es included in the final build and takes 493Kb

I can't find any use of lodash-es in the app.

Thanks for submitting this issue! Due to our limited time, we ask you to include a reproduction link to a minimal full reproduction of your problem (for example in a GitHub repository) so we can find what is causing the issue. Thank you for your understanding!

Thanks for your response @sodatea, I'm not allowed to publish the private project event if it's a discovery project. But i will try to prepare separate.
And here is a how problem is looks like (look at lodash-es, it's in dependencies):

It's depended on by vuex-orm-localforage https://github.com/eldomagan/vuex-orm-localforage/blob/bc93d0e7a33c1d5c9ef153241137875e80b5e6da/package.json#L36

Thanks a lot @sodatea!


Latest Update Errors

Since updating to latest version.. I get the error "Type 'Validator' (aka 'Optional -> Bool') has no member 'isEmail'"
MY CODE
import UIKit
import SwiftValidators

class TestVC: UIViewController
{
    override func viewDidLoad()
    {
        super.viewDidLoad();

        let is_email = Validator.isEmail("nemoryoliver@gmail.com");

        print("is_email: \(is_email)");
    }
}

Sorry, I forgot to update the array on the docs. The Validator class is no more.
Use Validators instead

Hi bro.. Even changing the Validator to Validators gives another error. "Missing argument label 'nilResponse:' in call"
import UIKit
import SwiftValidators

class TestVC: UIViewController
{
    override func viewDidLoad()
    {
        super.viewDidLoad();

        let x = Validators.isEmail("nemoryoliver@gmail.com");

        print(x);
    }
}

See screenshot: http://imgur.com/a/H9If9

From version 4.0.0 there are no computed properties in the API. The Validators class now supports only static functions.
I have updated the documentation (16de371d69909c9cda4b7502aba4251ae4345fd9) to reflect those changes and pushed a minor version update 4.0.1 on Cocoapods.
The correct syntax to your case is the following
<EMAIL_ADDRESS>
Some other examples:
Validators.isEmail()(nil) // returns false
Validators.isEmail(nilResponse: true)(nil) // returns true

Awesome sir. Now I know how to use your new version. Thanks a lot for this great lib. It helps a lot!


Verify UAVCAN

@devbharat @boosfelm Here are the things that need to be verified:

That the compiler you have produces valid binaries for boot loader and application
That you have removed the capacitors Ben indicated
That firmware upgrade and enumeration work with QGC master (there is also now a checkbox to enable the bus)

With that we should have the confidence that things are operational.

gcc_4_8_3 produces valid binaries for boot loader and application. gcc_4_7_4 fails. We will cross validate more versions in the next days. same with firmware upgrade and enumeration with QGC master.
caps and resistors are removed.

Ok, we fixed this. It was a bad linker script plus differences in how the different boot loaders interpreted the param storage flash space.


IndexError: list index out of range

Hello, Currently, I have a problem with IndexError: list index out of range with IDR dataset. Do you have any idea about this?
Thank you in advance.
Kind Regards,
Phuc Nguyen Thai Vinh

Hello, Currently, I have a problem with IndexError: list index out of range with IDR dataset. Do you have any idea about this? Thank you in advance. Kind Regards, Phuc Nguyen Thai Vinh

Hi, I have the same problem when loading test dataloader. Did you tackle this error? Thank you in advance.

Are you creating your own cameras.npz file? If so, it needs to contain the six camera matrices ('scale_mat_...', 'scale_mat_inv_...', 'world_mat_...', 'world_mat_inv_...', 'camera_mat_...', and 'camera_mat_inv_...') for every image.


same naming as DRF

want to align this two projects

Thanks @theromis. This looks identical to https://github.com/dessibelle/sorl-thumbnail-serializer-field/pull/3 though, am I missing something? My comments and questions raised there still applies, and are still unresolved IMO.
I also do not see any references to url_prefix in the django-rest-framework code base, so it's unclear to me in what way this PR uses the same naming.
As I mentioned here HyperlinkedSorlImageField attempts to handle to_representation() transparently, in the regard that it attempts to find a sorl generated thumbnail and builds the URL from that. In case it fails, it should fallback to the default rest_framework.serializers.ImageField behaviour. This PR appears to break that by requiring request if I interpret the code correctly.
In large part I would say the solution is rather a special Storage class as suggested in https://github.com/tomchristie/django-rest-framework/pull/4577 that would handle e.g. the CDN use case. I may be wrong of course, in which case I would prefer a url_prefix kwarg which does not break the current behaviour of HyperlinkedSorlImageField, or perhaps even a specific subclass if such explicit dependence on request is in deed needed.

just figured out better way using storage to set "right" domain name, so closing this PR.
BTW: you referenced my PR to them :) I just thought I was closed this PR, sorry, I forgot to do that.


Change "grid-auto-rows: 400px" -> "grid-auto-rows: auto"

Hi there, thank you for this theme! I noticed that in gallery view, photos are be cropped to fit the max. height of their containing row (in this case 400px). This comes down to personal taste, but I'd prefer to see the whole photo every time, which this one-liner does quite nicely.

Yeah, that's better. Thank you @fshstk!

I've noticed that this commit reveals the bottom border of the anchor link when clickablePhotos = true. Also, the alignment between photos is lost. Take a look:

Thanks for pointing that out @arthurbailao!
Would either you or @fshstk be up for submitting a fix for this?