[pods] Delete the replaced pods

What type of PR is this?
/kind feature

What this PR does / why we need it:
Delete the Failed pods in a pod-group once a replacement pods are created.
Which issue(s) this PR fixes:

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

The Failed pods in a pod-group are deleted once a replacements pod are created.

/test all

/test all

/cc @alculquicondor

/cherry-pick release-0.6

@trasc please create a cherry-pick and highlight in the description any significant changes compared to this PR.

/kind bug


Add property to area to control overwrite mode (#1224)

With this property it is possible to control when user starts overwrite mode using Insert key

Thanks for the PR, have reviewed and will merge :-)


Set a specific (setting) parameter, starting from a factory preset

Hello, thanks for the library.
Let's say I want to set the BME280 in Forced mode, while all other settings I would take from the "indoor" preset.
How would I do that, is there an example? Only found examples about enabling one of the presets (Settings.ino) as is.
Thanks

Hello,
I'm glad to hear you're using the library! To set the BME280 in the forced mode while using the indoor preset for other settings, you can make use of the setSettings method. Here's an example of how you can achieve this:

Hello,
I'm glad to hear you're using the library! To set the BME280 in forced mode while using the indoor preset for other settings, you can make use of the setSettings method. Here's an example of how you can achieve this:
#include <Arduino.h>
#include <Bme280.h>

Bme280TwoWire sensor;

void setup() {
  Serial.begin(9600);
  Wire.begin(D2, D1);

  Serial.println();

  sensor.begin(Bme280TwoWireAddress::Primary);

  auto settings = Bme280Settings::indoor();  // Use indoor preset
  settings.mode = Bme280Mode::Forced;  // Modify mode
  sensor.setSettings(settings);  // Set settings
}

void loop() {}

Thanks!

(solved)

@FerGT50 You're welcome.


Projects List/Page

We need a page talking about notable projects.

I retired the CodeForPortland/projects repo in favor of keeping projects info in a projects folder in this repo. Working on improving this repo in general.

Looks good @ngoldman I really dropped the ball on this

@bcomnes no worries it's a group effort and we've had 100 other things happen since this


Update to reqwest 0.12

reqwest 0.12 is based on a lot of version="1" crates around http. Having an upgraded set of dependencies plus crates_io_api causes a lot of duplicate crates (with different versions).

This was done in https://github.com/theduke/crates-io-api/pull/72 .


mentionPattern does not match names that end in -

People who's names end in - can't be pinged.

After messing around a bit, I think this is due to the \b word boundary matching. As - is not a word character, a space can never match after it (word boundary requires word before and non-word after, or vice versa). You can still ping these people if you put a letter directly after the - in order to trigger the word boundary matching.
Pattern p = Pattern.compile("\\b(" + "Box-" + ")\\b", CASE_INSENSITIVE);
Matcher m = p.matcher("I'm Box-");

System.out.println(m.find());
// Prints "false"

Matcher m2 = p.matcher("I'm Box-x");
System.out.println(m2.find());
// Prints "true"

Wanna have the bug fixed quickly?
Visit Issue hunt...

The fix is not complete as it doesn’t handle when the username is at the end of the line. It also doesn’t handle the case when the dash is at the beginning of the line.

I think you can reproduce the behavior of \b but modify the “word” class to include dashes.
Something like ^|[^A-z-]USERNAME[^A-z-]|$ should do the trick.
I also firmly disagree that this is “untestable”. There should be at least a few tests that check stuff like:

Box- matches Box-
-Box matches -Box
cardboard-Box does not match -Box
Box-boy does not match Box-
Hello Box-! matches Box-

The actual code this is in

Btw using A-z for the character class was lazy phone typing and will include a few special characters like square brackets, which we probably don’t want.

@Askaholic  this pattern matches on just spaces

Actually so did Axel's

I think I was able to fix it


Twitter popup login does not work

I am not sure why issue #177 was closed. Twitter login still does now work.
Here's the error -
Refused to display 'https://api.twitter.com/oauth/authenticate?oauth_token=VRVdnwAAAAAA6-NZAAAFGHgZffG' in a frame because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self' https://tweetdeck.twitter.com https://tdapi-staging.smf1.twitter.com https://tdapi-staging.atla.twitter.com https://tweetdeck.localhost.twitter.com".

I think I have a similar issue. I got:
Refused to display 'https://accounts.google.com/o/oauth2/auth.....' in a frame because it set 'X-Frame-Options' to 'sameorigin'.

When I'm trying to authenticate a Google user. Seems that the issue is being thrown during acquireTokenSilent operation.
I configured my Azure B2C with both Multi-Tenant AD and Google, with AD authentication works fine.

@vladkosarev @jrebagliatti Is this issue still seen? I am able to login with twitter using the basic SUSI policy. Please let us know if this issue still persists.

Thanks @vladkosarev . We ended up implementing [hello.js|https://adodson.com/hello.js/] due to the limitation described above. I'll give a try to the new version of MSAL and let you know.
Thanks!


Android Release build crashes after upgrading to 0.64.2 (hermes enabled)

Ours is an Android only Application.
Description
We upgraded our App from 0.61.5 to 0.64.2(hermes enabled) and debug build seemed to work fine, while the release fails with the following error:
2021-07-02 14:14:34.946 29256-29467/com.flipkart.seller E/ReactNativeJS: TypeError: Cannot read property 'style' of undefined, js engine: hermes
2021-07-02 14:14:34.963 29256-29467/com.flipkart.seller E/ReactNativeJS: Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect.
          This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native., js engine: hermes
2021-07-02 14:14:35.047 29256-29469/com.flipkart.seller E/AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
    Process: com.flipkart.seller, PID: 29256
    com.facebook.react.common.JavascriptException: TypeError: Cannot read property 'style' of undefined, js engine: hermes, stack:
    anonymous@1:454110
    h@1:82260
    d@1:81930
    o@1:81558
    anonymous@1:451031
    h@1:82260
    d@1:81930
    o@1:81558
    get TextInput@1:103370
    anonymous@1:709972
    h@1:82260
    d@1:81930
    o@1:81558
    anonymous@1:684543
    h@1:82260
    d@1:81930
    o@1:81558
    anonymous@1:1000552
    h@1:82260
    d@1:81930
    o@1:81558
    anonymous@1:954864
    h@1:82260
    d@1:81930
    o@1:81558
    anonymous@1:953733
    h@1:82260
    d@1:81930
    o@1:81558
    anonymous@1:951784
    h@1:82260
    d@1:81930
    o@1:81558
    anonymous@1:731714
    h@1:82260
    d@1:81930
    o@1:81558
    anonymous@1:724156
    h@1:82260
    d@1:81930
    o@1:81558
    anonymous@1:606677
    h@1:82260
    d@1:81930
    o@1:81558
    anonymous@1:89062
    h@1:82260
    d@1:81930
    o@1:81558
    anonymous@1:88728
    h@1:82260
    d@1:81887
    o@1:81558
    global@1:81246

        at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(SourceFile:12)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.facebook.react.bridge.JavaMethodWrapper.invoke(SourceFile:18)
        at com.facebook.react.bridge.JavaModuleWrapper.invoke(SourceFile:2)
        at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
        at android.os.Handler.handleCallback(Handler.java:938)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(SourceFile:1)
        at android.os.Looper.loop(Looper.java:223)
        at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(SourceFile:8)
        at java.lang.Thread.run(Thread.java:923)

React Native version:
System:
    OS: macOS 10.15.7
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Memory: 90.14 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.22.1 - ~/.nvm/versions/node/v12.22.1/bin/node
    Yarn: Not Found
    npm: 7.18.1 - ~/.nvm/versions/node/v12.22.1/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK: Not Found
  IDEs:
    Android Studio: 4.2 AI-202.76<IP_ADDRESS>51085
    Xcode: 12.4/12D4e - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.10 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: ^17.0.1 => 17.0.1
    react-native: 0.64.2 => 0.64.2
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Upgrade the App from 0.61.5 to 0.64.2
Install release build with Hermes enabled

Expected Results
Expect the App to run fine without any errors (just like in Debug build)
Snack, code example, screenshot, or link to a repository:
NA

My Bad found a deprecated usage in node_modules. Hence closing this thread.


starknet_getStorageAt not working correctly with params as array (json-rpc 1.0 style)

Wrong order of params defined in models.rs for GetStorageInput. I'm on it on a side branch, but just in case somebody runs into this.
Works well if params defined as object, but some clients send an array (e.g. starknet.rs).

Closed via #99


Peer to peer code review

Please consider improving your README file by adding prerequisites. For example, in order to run this project, you need text editor, web browser, and github account.

Great job,👍 creating those codes. could you please close the empty lines In lines 188-190 in your HTML file, it will make your code cleaner.


Grouping mode and participantCapacity

Does this "Grouping mode" in policy recording bot works?
I'm setting the participantCapacity in ICall.AswerAsync, but it seems like it doesn't make any difference.

It takes a bit more work to get this feature to work. First, if there are multiple join requests for the same meeting hitting your bot instance, then the platform will invite multiple bots, as only the answer of any of the join requests contains info about the capacity the bot supports.
Then, subsequent participants joining and requiring the bot for the same policy a special request will be sent to the bot. This notification needs to be processed via your own code. You need to handle the request and generate an Accept response for the platform to know you've really accepted this new participant. The CommunicationClient is not doing all the work for you here.
The docs are pretty slim on this, but yeah... this is how it works.
If you need further assistance, let me kow.

Yes, this code should do the trick:
https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/c01a738af7ac1379e7e36fa62ed55beb87ef1476/Samples/V1.0Samples/LocalMediaSamples/PolicyRecordingBot/FrontEnd/Bot/CallHandler.cs#L228-L249
However, I'm not sure it really works and whether the event gets triggered properly using this way.
If it doesn't work as described, then there are still issues. I know that it works, when I circumvent the entire comms client and return the acceptJoinResponse manually from within my controller action.

It works, but I also had to update all packages (Microsoft.Graph...) to latest versions (I was a few releases late).
Thanks for help.


Showdown does not include License in Script

Using GNU IceCat and LibreJS, I am unable to load Showdown because it does not have a stylized license comment in it. Please add a comment of the format
/*
 * LICENSE HERE
 *
 *
 */

Note to developer, add this to the Gruntfile.jsin the config.uglify.options.banner property.


ARROW-9388: [C++] Division kernels

See https://issues.apache.org/jira/browse/ARROW-9388

This can't be merged yet. Divide by zero in the unchecked case causes SIGFPE process crash.
We should probably return null when dividing by zero, this is what Impala does
https://github.com/apache/impala/blob/b5805de3e65fd1c7154e4169b323bb38ddc54f4f/be/src/exprs/operators-ir.cc#L60
I'm curious what other database-type systems do

cc @pitrou

This will wait for 2.0.

But, yes, I'll take a look later.

We have this implemented with SIMD (which was tricky) on the Rust side.  We currently return a Result for division by zero.

Thanks for starting this. I'm going to pull this down and make some changes per my comments

@wesm Thanks a lot for your effort. Your changes look much more reasonable than mine.

This can't be merged yet. Divide by zero in the unchecked case causes SIGFPE process crash.
We should probably return null when dividing by zero, this is what Impala does
https://github.com/apache/impala/blob/b5805de3e65fd1c7154e4169b323bb38ddc54f4f/be/src/exprs/operators-ir.cc#L60
I'm curious what other database-type systems do

I made some initial investigations, and it shows that some systems return null upon divide by zero (e.g. Impala and Hive (https://stackoverflow.com/questions/41165708/hive-dividing-numbers-from-the-same-column)), while others returns an error (like MySQL (https://www.got-it.ai/solutions/sqlquerychat/sql-help/data-manipulation/mysql-divide-by-zero-error-querychat/) and SQL Server (https://stackoverflow.com/questions/23230041/how-to-protect-sql-statement-from-divide-by-zero-error/23230084))
Anyway, we should handle it, instead of letting the process crash.

Thanks for doing this. Could you please be sure to add this function to https://github.com/apache/arrow/blob/master/docs/source/cpp/compute.rst?

Done. Thanks for your kind reminder.

After more experiments, I find @bkietz is right, as the test case crashed on AMD64 Ubuntu 18.04 when dividing by floating point 0.
So I have accepted his suggestions (Thank you @bkietz ).

@pitrou if you're satisfied, could you please merge?

I think unchecked floating point division by zero should simply return an infinite, but we can leave that for a separate JIRA.

I think unchecked floating point division by zero should simply return an infinite, but we can leave that for a separate JIRA.

@pitrou Thanks for your feedback, and sorry I did not take care of this problem. I will fix it up in the follow up issue.


failed to run custom build command for torch-sys v0.10.0

Caused by:
process didn't exit successfully: D:\rust\neural_network\target\debug\build\torch-sys-c996c2fe36bdca56\build-script-build (exit code: 1)
--- stdout
cargo:rerun-if-env-changed=TORCH_CUDA_VERSION
cargo:rerun-if-env-changed=LIBTORCH
cargo:rustc-link-search=native=D:\rust\neural_network\target\debug\build\torch-sys-de25f5a53a39aac9\out\libtorch\libtorch\lib
cargo:rerun-if-env-changed=LIBTORCH_INCLUDE
cargo:rerun-if-env-changed=LIBTORCH_LIB
cargo:rerun-if-changed=libtch/torch_api.cpp
cargo:rerun-if-changed=libtch/torch_api.h
cargo:rerun-if-changed=libtch/torch_api_generated.cpp.h
cargo:rerun-if-changed=libtch/torch_api_generated.h
cargo:rerun-if-changed=libtch/stb_image_write.h
cargo:rerun-if-changed=libtch/stb_image_resize.h
cargo:rerun-if-changed=libtch/stb_image.h
TARGET = Some("x86_64-pc-windows-msvc")
OPT_LEVEL = Some("0")
HOST = Some("x86_64-pc-windows-msvc")
cargo:rerun-if-env-changed=CXX_x86_64-pc-windows-msvc
CXX_x86_64-pc-windows-msvc = None
cargo:rerun-if-env-changed=CXX_x86_64_pc_windows_msvc
CXX_x86_64_pc_windows_msvc = None
cargo:rerun-if-env-changed=HOST_CXX
HOST_CXX = None
cargo:rerun-if-env-changed=CXX
CXX = None
cargo:rerun-if-env-changed=CXXFLAGS_x86_64-pc-windows-msvc
CXXFLAGS_x86_64-pc-windows-msvc = None
cargo:rerun-if-env-changed=CXXFLAGS_x86_64_pc_windows_msvc
CXXFLAGS_x86_64_pc_windows_msvc = None
cargo:rerun-if-env-changed=HOST_CXXFLAGS
HOST_CXXFLAGS = None
cargo:rerun-if-env-changed=CXXFLAGS
CXXFLAGS = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
DEBUG = Some("true")
running: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\bin\HostX64\x64\cl.exe" "-nologo" "-MD" "-Z7" "-Brepro" "-I" "D:\rust\neural_network\target\debug\build\torch-sys-de25f5a53a39aac9\out\libtorch\libtorch\include" "-I" "D:\rust\neural_network\target\debug\build\torch-sys-de25f5a53a39aac9\out\libtorch\libtorch\include/torch/csrc/api/include" "-FoD:\rust\neural_network\target\debug\build\torch-sys-de25f5a53a39aac9\out\libtch/fake_cuda_dependency.o" "-c" "libtch/fake_cuda_dependency.cpp"
running: "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\bin\HostX64\x64\cl.exe" "-nologo" "-MD" "-Z7" "-Brepro" "-I" "D:\rust\neural_network\target\debug\build\torch-sys-de25f5a53a39aac9\out\libtorch\libtorch\include" "-I" "D:\rust\neural_network\target\debug\build\torch-sys-de25f5a53a39aac9\out\libtorch\libtorch\include/torch/csrc/api/include" "-FoD:\rust\neural_network\target\debug\build\torch-sys-de25f5a53a39aac9\out\libtch/torch_api.o" "-c" "libtch/torch_api.cpp"
fake_cuda_dependency.cpp
torch_api.cpp
libtch/torch_api.cpp(1): fatal error C1083: Cannot open include file: 'torch/csrc/autograd/engine.h': No such file or directory
exit code: 0
exit code: 2
--- stderr
error occurred: Command "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.29.30133\bin\HostX64\x64\cl.exe" "-nologo" "-MD" "-Z7" "-Brepro" "-I" "D:\rust\neural_network\target\debug\build\torch-sys-de25f5a53a39aac9\out\libtorch\libtorch\include" "-I" "D:\rust\neural_network\target\debug\build\torch-sys-de25f5a53a39aac9\out\libtorch\libtorch\include/torch/csrc/api/include" "-FoD:\rust\neural_network\target\debug\build\torch-sys-de25f5a53a39aac9\out\libtch/torch_api.o" "-c" "libtch/torch_api.cpp" with args "cl.exe" did
not execute successfully (status code exit code: 2).

Hello, I would like to ask if this problem is solved now, I also encountered the same problem in the current compilation.Thank you.

Hi, i managed to fix this issue. Turns out i have to manually download Nvidia cuda from the nvidia website, which fixes this problem, but now i have a different problem when i try to run of the basic examples in github i get this error
error: process didn't exit successfully: `target\debug\nnetwork.exe` (exit code: 0xc0000135, STATUS_DLL_NOT_FOUND)

It was an issue with enviroment variables.  if you've set them, try to restart your terminal/ editor.


Neumes not saving properly anymore

I thought this was fixed, but when horizontal episemas are inserted on anthing other than a punctum, the neume is saved as a punctum and not as a virga  or any other note.

Realized that this is not because of the episemas but happening for all neumes. This was not happening before so I'm going to retrace our steps to see what went wrong.

Fixed in b820847


Adapt namespace style to dotnet 6 style

Currently when i create a class it's start like this
using System;

namespace projectname.folder.subfolder
{

    public class NewOrderCommand
    {

    }
}

But the dotnet 6 styles has changed it and look so much cleaner, like this:
using System;

namespace projectname.folder.subfolder;

public class NewOrderCommand
{

}

Would be great if you can update this styles thanks!

Hi @LincolnTx I will take a look on your request and implement it in the next release for sure. Thank you for the head's up!

Hi @LincolnTx sorry for the late reply but you can find your request resolved in the 1.2.9 version.
Now you can create .net 6.0 projects and create classes, interfaces, records, structs, with the new .net6.0 convention.
Thank you for reporting this and making the extension even better. Regards


Crashing weave-net pod when adding node to k8 cluster without supplying network-CIDR

What you expected to happen?
To not have to supply a --pod-network-cidr=<IP_ADDRESS>/12 command when setting up a weave network when using kubeadm init.  For the weave-net pod to remain stable when adding a node to the cluster.
What happened?
When I setup a k8 cluster using kubeadm init --apiserver-advertise-address=<IP_ADDRESS> and add one node, the newly created weave-net pod enters a CrashLoop when setting up the 2nd container.  This does not allow the new node to exit the NotReady state.
The weave-net pod for the master node looks healthy and has 2/2 RUNNING the entire time.
How to reproduce it?
NOTE - The k8 master and node are Ubuntu 18.04 VMs running on an Ubuntu 19.10 box.

Tear down existing k8 cluster to get to square 1

drain and delete all nodes
kubeadm reset on all nodes and master
On master:  delete /etc/cni/net.d and $HOME/.kube/config folders.

On master - run kubeadm init --apiserver-advertise-address=<IP_ADDRESS>

Run commands the kubeadm says to run at the end to sset up the kubeconfig correctly (mkdir....)
Run kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n')" to deploy weave

Wait for all pods to correctly come online
Add one node to the cluster with join cmd in the kubeadm output from the master.
On master - run kubeadm get pods --all-namespaces

At this point you can monitor the pods being created.  If the issue occurs, the 2nd container in the newest weave-net pod will start crashing and not come online - which keeps the node in a NotReady state.
Anything else we need to know?
I have recreated this issue a few times now to debug - the reproduction rate is not 100% (I have had it happen to me about 4/5 times with the above steps.
NOTE - adding --pod-network-cidr=<IP_ADDRESS>/12 to my init command when creating the cluster - I have not had this issue 4/4.  I see all pods/containers create as expected.
I opened an issue with K8 thinking this was just a documentation issue (I did not see the CIDR command in the K8 setup docs or in the Weave docs.  Opening an issue here since we did not see a CIDR address supplied in the log files when reproducing this bug, but saw one once I got a working cluster up.
One time before trying Weave I setup a Calico network for my cluster, but kept seeing crashing pods with that, so I moved to Weave.
Versions:
KubeCtl:
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-01-18T23:30:10Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-01-18T23:22:30Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/amd64"}

Weave
Using Weaving CNI plugin for Kubernetes
Docker:
Client:
 Version:           18.09.7
 API version:       1.39
 Go version:        go1.10.1
 Git commit:        2d0083d
 Built:             Fri Aug 16 14:20:06 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.09.7
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.1
  Git commit:       2d0083d
  Built:            Wed Aug 14 19:41:23 2019
  OS/Arch:          linux/amd64
  Experimental:     false

uname -a
Linux kubemaster 5.3.0-26-generic #28~18.04.1-Ubuntu SMP Wed Dec 18 16:40:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Logs:
The kube-proxy output once I have setup the master (before adding the node that has the crashing net pod):
apiVersion: v1
data:
config.conf: |-
apiVersion: kubeproxy.config.k8s.io/v1alpha1
bindAddress: <IP_ADDRESS>
clientConnection:
acceptContentTypes: ""
burst: 0
contentType: ""
kubeconfig: /var/lib/kube-proxy/kubeconfig.conf
qps: 0
clusterCIDR: ""
configSyncPeriod: 0s
conntrack:
maxPerCore: null
min: null
tcpCloseWaitTimeout: null
tcpEstablishedTimeout: null
enableProfiling: false
healthzBindAddress: ""
hostnameOverride: ""
iptables:
masqueradeAll: false
masqueradeBit: null
minSyncPeriod: 0s
syncPeriod: 0s
ipvs:
excludeCIDRs: null
minSyncPeriod: 0s
scheduler: ""
strictARP: false
syncPeriod: 0s
kind: KubeProxyConfiguration
metricsBindAddress: ""
mode: ""
nodePortAddresses: null
oomScoreAdj: null
portRange: ""
udpIdleTimeout: 0s
winkernel:
enableDSR: false
networkName: ""
sourceVip: ""
kubeconfig.conf: |-
apiVersion: v1
kind: Config
clusters:
- cluster:
certificate-authority: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
server: https://<IP_ADDRESS>:6443
name: default
contexts:
- context:
cluster: default
namespace: default
user: default
name: default
current-context: default
users:
- name: default
user:
tokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
kind: ConfigMap
metadata:
creationTimestamp: "2020-01-24T01:15:43Z"
labels:
app: kube-proxy
name: kube-proxy
namespace: kube-system
resourceVersion: "238"
selfLink: /api/v1/namespaces/kube-system/configmaps/kube-proxy
uid: f12e3e4b-73b2-439e-8be9-7289d2bce49a

And the output once I added the one node and started seeing the crashing net pod:
apiVersion: v1
data:
config.conf: |-
apiVersion: kubeproxy.config.k8s.io/v1alpha1
bindAddress: <IP_ADDRESS>
clientConnection:
acceptContentTypes: ""
burst: 0
contentType: ""
kubeconfig: /var/lib/kube-proxy/kubeconfig.conf
qps: 0
clusterCIDR: ""
configSyncPeriod: 0s
conntrack:
maxPerCore: null
min: null
tcpCloseWaitTimeout: null
tcpEstablishedTimeout: null
enableProfiling: false
healthzBindAddress: ""
hostnameOverride: ""
iptables:
masqueradeAll: false
masqueradeBit: null
minSyncPeriod: 0s
syncPeriod: 0s
ipvs:
excludeCIDRs: null
minSyncPeriod: 0s
scheduler: ""
strictARP: false
syncPeriod: 0s
kind: KubeProxyConfiguration
metricsBindAddress: ""
mode: ""
nodePortAddresses: null
oomScoreAdj: null
portRange: ""
udpIdleTimeout: 0s
winkernel:
enableDSR: false
networkName: ""
sourceVip: ""
kubeconfig.conf: |-
apiVersion: v1
kind: Config
clusters:
- cluster:
certificate-authority: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
server: https://<IP_ADDRESS>:6443
name: default
contexts:
- context:
cluster: default
namespace: default
user: default
name: default
current-context: default
users:
- name: default
user:
tokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
kind: ConfigMap
metadata:
creationTimestamp: "2020-01-24T01:15:43Z"
labels:
app: kube-proxy
name: kube-proxy
namespace: kube-system
resourceVersion: "238"
selfLink: /api/v1/namespaces/kube-system/configmaps/kube-proxy
uid: f12e3e4b-73b2-439e-8be9-7289d2bce49a

And for a compare, here is the output after I add the one node when I supply the CIDR in the init command:
apiVersion: v1
data:
config.conf: |-
apiVersion: kubeproxy.config.k8s.io/v1alpha1
bindAddress: <IP_ADDRESS>
clientConnection:
acceptContentTypes: ""
burst: 0
contentType: ""
kubeconfig: /var/lib/kube-proxy/kubeconfig.conf
qps: 0
clusterCIDR: <IP_ADDRESS>/12
configSyncPeriod: 0s
conntrack:
maxPerCore: null
min: null
tcpCloseWaitTimeout: null
tcpEstablishedTimeout: null
enableProfiling: false
healthzBindAddress: ""
hostnameOverride: ""
iptables:
masqueradeAll: false
masqueradeBit: null
minSyncPeriod: 0s
syncPeriod: 0s
ipvs:
excludeCIDRs: null
minSyncPeriod: 0s
scheduler: ""
strictARP: false
syncPeriod: 0s
kind: KubeProxyConfiguration
metricsBindAddress: ""
mode: ""
nodePortAddresses: null
oomScoreAdj: null
portRange: ""
udpIdleTimeout: 0s
winkernel:
enableDSR: false
networkName: ""
sourceVip: ""
kubeconfig.conf: |-
apiVersion: v1
kind: Config
clusters:
- cluster:
certificate-authority: /var/run/secrets/kubernetes.io/serviceaccount/ca.crt
server: https://<IP_ADDRESS>:6443
name: default
contexts:
- context:
cluster: default
namespace: default
user: default
name: default
current-context: default
users:
- name: default
user:
tokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
kind: ConfigMap
metadata:
creationTimestamp: "2020-01-24T01:27:20Z"
labels:
app: kube-proxy
name: kube-proxy
namespace: kube-system
resourceVersion: "242"
selfLink: /api/v1/namespaces/kube-system/configmaps/kube-proxy
uid: 10ce9974-f193-4b5c-9efb-78c0317746d2

you need to debug and ensure kubernetes service IP <IP_ADDRESS> is accessible from the node

you can do:
kubectl get svc kubernetes
which should give you the IP / port of the kubernetes service.
telnet <ip> <port>
will then tell you if the node has connection to the service.

Thanks for the response.
I telnetted from node-1 to the kubernetes service telnet <IP_ADDRESS> 443 and telnet <IP_ADDRESS> 6443 and both attempts just sat there trying with no response.
443 is the port seen open when I use kubectl get svc kubernetes.

did it say the following?

Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS>.

if yes, the connection is fine.
this verifies that the node has connectivity.

if no, i have no immediate explanation what can cause that. do you have firewall rules enabled?

No, it just tried and never connected.  I only let it sit maybe less than 20 seconds - I think it would have connected by then if things were ok.
I have a firewall, but I don't think this would touch the firewall at all since the 10.x.x.x addresses are a virtual network hosted on my linux box which has my kube cluster running on it with 3 VMs.
Plus, all this works if I supply the CIDR command when running the initial init command.  So I don't need this fixed since I can just remake my cluster, supply the CIDR and have everything work.  Maybe a note can be added to the setup process that supplying the CIDR could help people who run into this - for whatever reason.

Maybe a note can be added to the setup process that supplying the CIDR could help people who run into this - for whatever reason.

if weavenet does not require a CIDR, but in some cases it does (other than https://www.weave.works/docs/net/latest/kubernetes/kube-addon/#-things-to-watch-out-for), then this is breaking a UX contract and is better to understand the reason.

Plus, all this works if I supply the CIDR command when running the initial init command.

When you specifiy CIDR for kubeadm init, it goes to the --cluster-cidr argument of kube-proxy (please see https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/). This would help kube-proxy to figure what is internal traffic and exntenal traffic.
If you dont specify CIDR, possibly traffic is getting masquraded (not masqurade not SNAT). And if traffic is not going through then it means wrong source IP address is perhaps picked and is unroutable.
This sounds similar to https://github.com/kubernetes/kubeadm/issues/102. Are you using host with multiple interafaces?

yes, the master node has multiple interfaces:

datapath: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1376
inet6 fe80::10b7:87ff:fe21:f821  prefixlen 64  scopeid 0x20
ether 12:b7:87:21:f8:21  txqueuelen 1000  (Ethernet)
RX packets 6788  bytes 498949 (498.9 KB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2603  bytes 226461 (226.4 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether 02:42:d5:e3:f5:16  txqueuelen 0  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
inet6 fe80::9bdb:ca2a:31ee:beba  prefixlen 64  scopeid 0x20
ether 08:00:27:ab:c8:91  txqueuelen 1000  (Ethernet)
RX packets 1119999  bytes 634571114 (634.5 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 395661  bytes 145955863 (145.9 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
enp0s8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
inet6 fe80::a00:27ff:fe61:3d37  prefixlen 64  scopeid 0x20
ether 08:00:27:61:3d:37  txqueuelen 1000  (Ethernet)
RX packets 3591560  bytes 337031073 (337.0 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 3193847  bytes<PHONE_NUMBER> (1.4 GB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet <IP_ADDRESS>  netmask <IP_ADDRESS>
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 195097965  bytes<PHONE_NUMBER>5 (28.9 GB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 195097965  bytes<PHONE_NUMBER>5 (28.9 GB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
vethwe-bridge: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1376
inet6 fe80::d083:e0ff:fe25:5337  prefixlen 64  scopeid 0x20
ether d2:83:e0:25:53:37  txqueuelen 0  (Ethernet)
RX packets 6385  bytes 558005 (558.0 KB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 4089  bytes 357758 (357.7 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
vethwe-datapath: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1376
inet6 fe80::d483:37ff:fee3:ef7d  prefixlen 64  scopeid 0x20
ether d6:83:37:e3:ef:7d  txqueuelen 0  (Ethernet)
RX packets 4089  bytes 357758 (357.7 KB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 6385  bytes 558005 (558.0 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
vethwepl7096ee8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1376
inet6 fe80::e434:64ff:febe:f8ea  prefixlen 64  scopeid 0x20
ether e6:34:64:be:f8:ea  txqueuelen 0  (Ethernet)
RX packets 659  bytes 55426 (55.4 KB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 746  bytes 207812 (207.8 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
vethweplecda175: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1376
inet6 fe80::583f:ecff:fe34:67c8  prefixlen 64  scopeid 0x20
ether 5a:3f:ec:34:67:c8  txqueuelen 0  (Ethernet)
RX packets 649  bytes 54957 (54.9 KB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 737  bytes 207364 (207.3 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
vxlan-6784: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 65535
inet6 fe80::4850:93ff:fe79:a9d0  prefixlen 64  scopeid 0x20
ether 4a:50:93:79:a9:d0  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

weave: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1376
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
inet6 fe80::48ee:bcff:fe1d:6319  prefixlen 64  scopeid 0x20
ether 4a:ee:bc:1d:63:19  txqueuelen 1000  (Ethernet)
RX packets 4836959  bytes 329922997 (329.9 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 5229000  bytes<PHONE_NUMBER> (1.4 GB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

And here are the interfaces for the Linux host which is hosting the Master and Worker nodes through VirtualBox:

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether 02:42:0b:d5:50:03  txqueuelen 0  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
inet6 fe80::153:d098:f582:d701  prefixlen 64  scopeid 0x20
ether 18:03:73:1e:27:a9  txqueuelen 1000  (Ethernet)
RX packets 3645726  bytes<PHONE_NUMBER> (3.2 GB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 1503963  bytes 196857989 (196.8 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet <IP_ADDRESS>  netmask <IP_ADDRESS>
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 27871  bytes 2507853 (2.5 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 27871  bytes 2507853 (2.5 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
vboxnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
inet6 fe80::800:27ff:fe00:0  prefixlen 64  scopeid 0x20
ether 0a:00:27:00:00:00  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 15743  bytes 1366878 (1.3 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

This also sounds like https://github.com/weaveworks/weave/issues/3363


feat: add multiframe example

Add support to multiframe dicom images to cornerstone
Add a new function convertMultiframeImageIds that expands a multiframe imageid to a list of imageids where each imageid corresponds to a frame, the imageid ending with frames/x, where x corresponds to the number of the frame .i.e
an imageid   /studies/StudyInstanceUID/series/SeriesInstanceUID/instances/SOPInstanceUID/frames/1 will be converted to

/studies/StudyInstanceUID/series/SeriesInstanceUID/instances/SOPInstanceUID/frames/1
/studies/StudyInstanceUID/series/SeriesInstanceUID/instances/SOPInstanceUID/frames/2
...
/studies/StudyInstanceUID/series/SeriesInstanceUID/instances/SOPInstanceUID/frames/n

Hello, did you check the https://www.cornerstonejs.org/live-examples/ after the merge process?

@ssokmen for some reason our ci webpack didn't catch that. We will fix it


process.env.API_KEY is undefined

Describe the bug
Following the https://docs.amplify.aws/cli/function#query, it used:
headers: {
  'x-api-key': process.env.API_KEY
}

To Reproduce
Steps to reproduce the behavior:

Create a graphql API
Add a model with @auth and give it { allow: public, provider: apiKey }
Create a function and specify that you want to access API from that function.
Console log process.env and you'll see that API_KEY is not there.

Expected behavior
Should API_KEY be there or not?
Code Snippet
Just follow steps above.
Screenshots
If applicable, add screenshots to help explain your problem.
What is Configured?
If applicable, please provide what is configured for Amplify CLI:

Which steps did you follow via Amplify CLI when configuring your resources.
Which resources do you have configured?

If applicable, please provide your aws-exports file:

const awsmobile = {
    "aws_project_region": "us-east-1",
    "aws_cognito_identity_pool_id": "us-east-1:xxx-xxxx-xxxx-xxxx-xxxxxxxx",
    "aws_cognito_region": "us-east-1",
    "aws_user_pools_id": "us-east-1_xxx",
    "aws_user_pools_web_client_id": "xxxx",
    "oauth": {}
};

If applicable, please provide your manual configuration example:

{
 Auth: {
     identityPoolId: 'XX-XXXX-X:XXXXXXXX-XXXX-1234-abcd-1234567890ab',
     region: 'XX-XXXX-X',
     identityPoolRegion: 'XX-XXXX-X',
     userPoolId: 'XX-XXXX-X_abcd1234',
     userPoolWebClientId: 'a1b2c3d4e5f6g7h8i9j0k1l2m3',
     mandatorySignIn: false,
     authenticationFlowType: 'USER_PASSWORD_AUTH',
     oauth: {
         domain: 'your_cognito_domain',
         scope: ['phone', 'email', 'profile', 'openid', 'aws.cognito.signin.user.admin'],
         redirectSignIn: 'http://localhost:3000/',
         redirectSignOut: 'http://localhost:3000/',
         responseType: 'code' // or 'token', note that REFRESH token will only be generated when the responseType is code
        }
    }
}

If applicable, provide more configuration data, for example for Amazon Cognito, run aws cognito-idp describe-user-pool --user-pool-id us-west-2_xxxxxx (Be sure to remove any sensitive data)

Environment

npx envinfo --system --binaries --browsers --npmPackages --npmGlobalPackages

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
I'm trying to do this:
// somewhere above
const { GraphQLClient } = require('graphql-request');

// inside handler
const client = new GraphQLClient(
  endpoint,
  {
    headers: {
      'x-api-key': process.env.API_KEY
    }
  }
);

You can turn on the debug mode to provide more info for us by setting window.LOG_LEVEL = 'DEBUG'; in your app.

I reproduced the bug, will work on a fix soon.

@aprilmintacpineda The fix for this has been released in CLI v 4.26.0. The environment variable will be populated in API_<YOUR_API_NAME>_GRAPHQLAPIKEYOUTPUT. I have a docs PR above to update the docs to the new env variable as well.


Demo is broken?

Looking at http://vectoross.io/demo/ doesn't actually show any graphs only place holders for graphs (at least in Chrome)...

@sitsofe which server running PCP are you trying to fetch metrics from?

Oh! I hadn't twigged it was "live" and needed to pull data from a real pcp server. Let me close this issue before anyone else notices...


add -i, --installer option. it change to another installer (fix #101)

npm-check -u fail (support ied / pnpm) #101
dylang/npm-check#101

this feature usage:
npm-check -u -i pnpm -> $ pnpm install

Interesting feature! I'm a fan of these alternate installers, it was fun to discover pnpm uses my observatory module.
I'll provide feedback in the code.


Windows 11 context menu support

Hi, can this library be used to show Windows Explorer context menu entries for Windows 11? (in the new Windows 11 way IExplorerCommand + app identity)
https://blogs.windows.com/windowsdeveloper/2021/07/19/extending-the-context-menu-and-share-dialog-in-windows-11/

Would like that as well

no this will not work you need to use IExplorerCommand + App identity that's how Microsoft have made it hopefully they change this


MingW12.1.0,Windows8.1 undefined reference to WaitOnAddress, WakeByAddressAll,WakeByAddressSingle

When i build the gperftools on Windows8.1, MingW12.1.0。There are some issues for
undefined reference to WaitOnAddress
undefined reference to WakeByAddressAll
undefined reference to WakeByAddressSingle
What can i do for this  .

Frankly I am not sure what to advice. Those functions should be available on your OS. Some perhaps something isn't right with mingw. Can you grep your headers to see if WaitOnAddress is available ? If it is in headers, which appears to be the case, then we'll need to check if perhaps we're not linking everything right. Then I'll need full log from your build.


bug/docx skip counting page number for blank page

Describe the bug
Page number was wrongly enumerated when there existed a blank page. For instance, page 1 and page 3 have contents, where page 2 is a blank page. The page number extracted from elements_to_json reads content from page 3 as page 2.
To Reproduce
elements_to_json(partition(filename="example-docs/handbook-872p.docx"),"handbook-872p.docx.json")
Expected behavior
A correct page number corresponded to the actual document's page number.
Screenshots

Environment Info
OS version:  macOS-13.4-arm64-arm-64bit
Python version:  3.8.15
unstructured version:  0.8.1
unstructured-inference version:  0.7.10
pytesseract version:  0.3.10
Torch version:  2.1.0
Detectron2 is not installed

[notice] A new release of pip is available: 23.2.1 -> 23.3.1
[notice] To update, run: pip install --upgrade pip

[notice] A new release of pip is available: 23.2.1 -> 23.3.1
[notice] To update, run: pip install --upgrade pip
PaddleOCR is not installed
Libmagic version:  ==> libmagic: stable 5.45 (bottled)
LibreOffice version:  ==> libreoffice: 7.6.2

Additional context
1.
The page numbers do not seem to update after the Table of Content. For example, below is the text from page 8 in the document, but is shown as page 2 in metadata. (It seem to be running as according to the footer's page number, but more investigation is needed.)

Not quite related to this issue, but do we consider trimming the text extracted?

This behavior is addressed in a PR of mine merged last week.
Unfortunately the new behavior in this case is to not report any page numbers at all, the reason being the handbook-872p.docx file contains no rendered page breaks. This could be because it was a conversion from the original.
In any case, I'm pretty sure I can get Word to pop those in there for us if you think that would be better. I expect it would make it a better example if end-users were likely to use it like that, but I've got the enough other test-files in there for unit-testing purposes.


Migrate cluster IDs to ClusterIdentity

Description
This PR refactors all components to identify clusters by their ClusterIdentity (which internally contains their ID and name) rather than the cluster ID.
This opens the possibility of using user-friendly names in both Kubernetes object names and log messages.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

[x] Unit tests
[x] E2E tests

/build

/test

/test

/test

/test

/test

/test

/test

/test

/test

/test

/test

/test

/test

/test

/test

/test

/test

/test

/merge


Fix minor bug. args in def u(self, group, bites)

This looks more like a break than a fix.
The intended (and generally preferred) behavior is for args to be a list, not a string

Well it was preventing any commands to work properly on my end (weird); however, I acknowledge your take on it from your perspective.

This was said already but, the args being a list is an intentional feature on chlib, making it a string would be counter productive to the entire point of it being a string.


Interface change request for Detached Content

How about changing the interface t_cose_sign_encode_start and t_cose_sign_encode_finish in dev branch?
This is close to #34 , but now we can ignore the backward compatibility on t_cose 2.0.
It will be much simpler, and easy to implement detached content Mac and Encrypt.
Before
enum t_cose_err_t
t_cose_sign_encode_start(struct t_cose_sign_sign_ctx *me,
                         bool                         payload_is_detached,
                         QCBOREncodeContext          *cbor_encode_ctx)
{
    ...
    if(!payload_is_detached) {
        QCBOREncode_BstrWrap(cbor_encode_ctx);
    }
}

enum t_cose_err_t
t_cose_sign_encode_finish(struct t_cose_sign_sign_ctx *me,
                          struct q_useful_buf_c        aad,
                          struct q_useful_buf_c        detached_payload,
                          QCBOREncodeContext          *cbor_encode_ctx)
{
    if(q_useful_buf_c_is_null(detached_payload)) {
        /* Payload is inline, not detached */
        QCBOREncode_CloseBstrWrap2(cbor_encode_ctx, false, &signed_payload);
    } else {
        signed_payload = detached_payload;
    }
    ...
}

enum t_cose_err_t
t_cose_sign_one_short()
{
    return_value = t_cose_sign_encode_start(me, payload_is_detached, &encode_context);
    if(payload_is_detached) {
        QCBOREncode_AddNULL(&encode_context);
    } else {
        QCBOREncode_AddEncoded(&encode_context, payload);
    }
    if(!payload_is_detached) {
        payload = NULL_Q_USEFUL_BUF_C;
    }
    return_value = t_cose_sign_encode_finish(me, aad, payload, &encode_context);
}

After
enum t_cose_err_t
t_cose_sign_one_short()
{
    /*
    COSE_Sign = [
        Headers,
        payload : bstr / nil,
        signatures : [+ COSE_Signature]
    ]
    */

    /* encode `[` and `Headers` */
    return_value = t_cose_sign_encode_start(me, &encode_context);

    /* encode payload */
    if(payload_is_detached) {
        QCBOREncode_AddNULL(&encode_context);
        //XXX: no need to execute       payload = NULL_Q_USEFUL_BUF_C;
    } else {
        QCBOREncode_BstrWrap(cbor_encode_ctx);
        QCBOREncode_AddEncoded(&encode_context, payload);
        QCBOREncode_CloseBstrWrap2(cbor_encode_ctx, false, &signed_payload);
    }

    /* encode (`signatures` or `signature`) and `]` */
    return_value = t_cose_sign_encode_finish(me, aad, payload, &encode_context);
}

Yes, the interface can change in t_cose 2.0, but we have to support the t_cose 1.0 interface in a backwards compatible mode.
Your change would make the internals of t_cose_sign simpler which is good, but it would also make the use of the two-step signing more complicated. Look at two_step_sign_example(). All the BstrWrap stuff that is in t_cose_sign_encode_start() and t_cose_sign_encode_finish() would have to be implemented by the caller making it harder to use the two-step option. Example code will help, but not completely simplify it. I also worry it will make the 1.0 compatibility more complicated.
How does this help with detached payload encrypt-then-sign? At some point there should be an encrypt-then-sign API in t_cose. It should work for detached and non-detached payloads. It would probably be the t_cose_message object/API/context.

With proposed interface the caller must call QCBOREncode_BstrWrap() and QCBOREncode_CloseBstrWrap2() on two-step signing. It is certainly harder because the caller may not know that the payload should be bstr-wrapped in COSE struct.
I'll modify the interface in my forked repository as a trial, so judge that the change is appropriate.

I have a pretty good idea what the calling code would look like.  I also can see how the t_cose 1.0 backwards compatibility mode can be handled too.
I'm still trying to understand the benefit of this change.
I know for sure that it will simplify the internals of t_cose.
Are there use cases where it will benefit the user of t_cose? So far it just seems like it makes it harder for the user.  In particular, does it make things easier for encrypt-then-sign with detached content?

Fixed by https://github.com/laurencelundblade/t_cose/commit/baa6001217e75ea9460b3b6ae23858e873d111f7


merge package template from Kronos-Tools/npm-package-template

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template
chore(engines): update<EMAIL_ADDRESS>from template

.travis.yml

chore(travis): merge from template .travis.yml

Coverage decreased (-0.3%) to 77.992% when pulling 1112c0a4f81c25cb82117463a29dae43e09f5775 on template-sync-1 into cacc5eb4147d5528959401644a86d69f5e62c822 on master.

Codecov Report

Merging #215 into master will decrease coverage by 0.39%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #215     +/-   ##
=========================================
- Coverage   83.92%   83.53%   -0.4%
=========================================
  Files           1        1
  Lines         168      164      -4
=========================================
- Hits          141      137      -4
  Misses         27       27

Impacted Files
Coverage Δ

src/module.js
83.53% <0%> (-0.4%)
:arrow_down:

Continue to review full report at Codecov.

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


Hotfix：multy node with redisson receive multy same message

tow hotfix:

#552 this pr is too long ago, I also make this hotfix.
In multi nodes, other nodes receive only one LEAVE msg on client disconnect, although the client had joined multi rooms.

I was having the same problem, but I solved it thanks to you!!

Thanks for contribution!


Add a function that uses a resolve callback

Currently, useExpired is a nice feature to have data that is always fast to load, the problem is even when a fetch starts in the background, you will never get the updated data unless it's requested again. With modern frontend frameworks, it's often simple to say that you have new data and want to update, so we should take in a parameter to support cases like this
import { useResolve } from 'storage-utils'

const [state, setState] = useState(null);

// I haven't settled on a name for this function
// useExpired is implied because it's the only situation
// where you have 2 values
useResolve(
  localStorage,
  'key',
  fetchMyData,
  convertMinutesToMilliseconds(10),
  setState
);

There may be an even more readable solution using reactive techniques, but this is a good first pass

:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Login issue

New issue when logging in:
selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"css selector","selector":"[name="email"]"}
  (Session info: headless chrome=100.0.4896.88)

Hi, maybe i've broke the API in the last update. I will check asap

Sorry for the late response but i'm very busy in this period.


Step 03 - Configure FDPs with the defined schemas and populate them

Aim is proof-of-concept, hence manual onboarding at L3 is sufficient for this cycle. Automation tools for onboarding at L3 is a 'could'.

End date: manually populating the metadata schemas is straightforward but can be laborious.


Comparison conditions for optimized key set predicate rendering is broken for embedded ids

Description

The row value comparison handling for the optimized keyset pagination handling currently produces broken SQL. When a order by for an embeddable is done, the RowValueComparisonFunction receives arguments like ['<', '(col1, col2)', '?'] which finally renders SQL like where (col1, col2) < (?). This is obviously wrong and produces an error. There should be a second question mark for the second column.
Now the problem is, that Hibernate can't render the parameter as (?,?) because it doesn't know the parameter type and can't infer it because we pass it to a function. We could try to treat the parameter so that it gets a proper type, but I'm not sure this will work across persistence providers.
If all that doesn't work, we have to tupleize i.e. flatten the value manually, although I am not sure how easy that would be.
In additon to that, the "normal" optimized key set pagination code also produces invalid JPQL when embeddables are involved. A query contains a condition like embedded < :param which doesn't work. We would have to tupleize/flatten that too I guess.

Actually, I just found out that embedded ids generally don't work with keyset pagination currently because of generating embedded < :param code which isn't supported by hibernate as you can see here: https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src/main/java/org/hibernate/hql/internal/ast/tree/BinaryLogicOperatorNode.java#L127

Actually, I just found out that embedded ids generally don't work with keyset pagination currently because of generating embedded < :param code which isn't supported by hibernate as you can see here: https://github.com/hibernate/hibernate-orm/blob/master/hibernate-core/src/main/java/org/hibernate/hql/internal/ast/tree/BinaryLogicOperatorNode.java#L127

So the generated query should split the expression into col1 < ? and col2 < 3? I by the way assume that this also applies for entities with a compound key using @IdClass?
Nevertheless, I really stopped using compound keys in Hibernate because it can break so many things so easily. And I always ended up having to map the same column to two mappings and tweak my mapping with JoinFormula's and insertable=false columns ¯_(ツ)_/¯

Yes it has to be split. I guess this applies to IdClasses as well however I'm not sure IdClass support is already that good to even hit the optimization. I'd expect the query generation fails for IdClasses right now.


Subject Alternative Names in cert generation

Quickfix: These changes are necessary to enable clients (e.g. in #711) to communicate with the deployed server.
related to #724

Codecov Report

Merging #725 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #725   +/-   ##
=======================================
  Coverage   53.25%   53.25%
=======================================
  Files          38       38
  Lines        3207     3207
=======================================
  Hits         1708     1708
  Misses       1208     1208
  Partials      291      291

Continue to review full report at Codecov.

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

What's the status of this PR?

This PR includes a few lines of changes such that @AMarcedone's grpc (Java) client can communicate with the deployed server without warning about a wrong IP. It should create a cert that can be used from inside docker-composer, kubernetes, and externally by using the server's IP.
I think the scripts need further cleanup but it would be good if this got merged so that the deployed server can be contacted not only from inside the kubernetes cluster.

The deployed server works for me atm (so the cert is well formed and accepted).

The deployed server works for me atm (so the cert is well formed and accepted).

Thanks for testing that and thanks for the review. I removed the comment about the script not working on Macs, made the san extension mandatory, and made the deployed servers address configurable. PTAL

LGTM! Thanks for the changes and the PR in general.


Preview API: provide hint for which files (not) to request a thumbnail

Is your feature request related to a problem? Please describe.
Clients targeting the Preview API have no way of telling in advance for which file types a preview can likely be expected to be available, making (repeated) requests for thumbnails that will never be returned.
Describe the solution you'd like
Ideally, a list of MIME types, for which the Preview API is likely capable of providing a preview, would be available as part of the capabilities endpoint.
Using that list, clients could then see if the MIME type of an item is in that list and only request thumbnails for those items for which this is the case.
Describe alternatives you've considered
Alternatively, whether or not a thumbnail is available for a file could be returned as a new WebDAV tag (f.ex. <oc:has-thumbnail>).
This approach is more flexible, f.ex. if creating a thumbnail for a file previously failed, the server could tell the client that no thumbnail is available - even though it's a "supported" format.
However, for this additional flexibility to be put to use, I imagine that the server implementation would need to be more complex and possibly lead to a much higher overhead than the proposed solution.
Related issues
https://github.com/owncloud/core/issues/31267

Also related:

https://github.com/owncloud/ocis/issues/1378


Work with a room object exported from RoomScanLiDAR application

Hello! I try to add a 3D Object of a room in actual size (.obj) exported from the RoomScanLiDAR application to my scene but it isn't appearing in the AR scene. I set both of the onLoadStart and onLoadEnd callbacks and they work as expected, which means that the object was successfully loaded. I have added an ambient light to the scene, and another 3d object was rendered as expected. What I am doing wrong?
ViroMaterials.createMaterials({
  test: {
    lightingModel: 'Blinn',
    diffuseColor: 'yellow',
    shininess: 0.5,
  },
});

<ViroARScene
        onTrackingUpdated={this._onInitialized}
      >
        <ViroAmbientLight color="#ffffff" />
        <ViroNode scale={[0.7, 0.7, 0.7]} position={[0, 0, -1]}>
          <ViroText
            text={this.state.text}
            scale={[0.7, 0.7, 0.7]}
            position={[0, 0, 0]}
            style={styles.helloWorldTextStyle}
          />
          <Viro3DObject
            source={require('./src/assets/3d/property-obj.obj')}
            materials={['test']}
            scale={[0.5, 0.5, 0.5]}
            type="OBJ"
            onLoadStart={() => {
              console.log('LoadStart');
            }}
            onLoadEnd={() => {
              console.log('LoadEnd');
            }}
          />
        </ViroNode>
      </ViroARScene>

UPDATE
I've tried to put a small Viro box and small custom object also in the scene and everything was rendered. I think that probably Viro doesn't work with point cloud objects. Is there maybe some way to convert the point cloud to a normal 3d object?

I'm not sure if I can reproduce this - can you help by seeing if you get the same behavior I'm seeing?
I do see an error in the console but it looks like everything is working to me.

Error: Asset not found: /Users/XXX/starter-kit/assets/vp.mtl for platform: null
    at getAbsoluteAssetRecord (/Users/XXXXX/starter-kit/node_modules/metro/src/Assets.js:110:11)
    at async getAsset (/Users/XXX/starter-kit/node_modules/metro/src/Assets.js:238:18)
    at async Server._processSingleAssetRequest (/Users/XXX/starter-kit/node_modules/metro/src/Server.js:326:20)
    at async Server._processRequest (/Users/XXX/starter-kit/node_modules/metro/src/Server.js:401:7)

closing for no response.


[REVIEW]

GitHub Profile Link
https://github.com/VasudevJaiswal

You continue to act inappropriately, I will not be reviewing your profile


feat: add transactions to nexus updates

Adds transactions to nexuses, similar to what was done to replicas.

bors try

bors merge


Streaming: Give role

Maybe state that yag has to have a role above the one its assigning since multiple people have asked about it.

https://github.com/buthed010203/yagpdb/commit/319c13c6d954d0974e9f7507c1270d9be6e900a6


added django 2.0 compatibility

Fixes https://github.com/groveco/django-sql-explorer/issues/309

Improved import lines to better accommodate new django.urls imports.
Added now-required on_delete arguments to migrations so that they match models.
Reordered travis install order to ensure that correct Django version is always installed.

By the way, this PR was crashing for me with:
    from explorer.views import (
  File "/home/stavros/.virtualenvs/babbage/lib/python3.5/site-packages/explorer/views.py", line 26, in <module>
    from explorer.forms import QueryForm
  File "/home/stavros/.virtualenvs/babbage/lib/python3.5/site-packages/explorer/forms.py", line 4, in <module>
    import app_settings
ImportError: No module named 'app_settings'

@skorokithakis see #312


Engine Refactor

Overview
This pull request extracts the storage concerns from the tsdb package and moves them in to the tsdb/engine/v1 package. This allows us to support multiple storage formats inside of InfluxDB and it allows us to incrementally migrate between them.
One consequence of this refactor is that the tsdb tests needed to be moved to their own tsdb_test package so that both the tsdb and engine/v1 packages could be imported without causing a circular dependency.
This engine refactor is being PR'd separately from the compression engine.

OK, I rebased from @otoolep's changes and everything seems to be in working order.

Nice refactoring.  LGTM :+1:


SignifydAPI does not provide a method to update investigation label

There's no method in the \Signifyd\Core\SignifydAPI to call the Update Investigate Label end point described here: https://signifyd.zendesk.com/hc/en-us/articles/206387737-Update-Investigation-Label.
A new method could be provided similar to updatePayment

I submitted pull request #6 to address this issue

I see you already implemented the missing method: I'll close this issue as well as pull request #6


Remove MockTcpTransport

Summary of the changes / Why this improves CrateDB
The MockTcpTransport had only a single use site left. We can replace
that with the Netty4Transport. Has the advantage that we cover more
production code.
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Could you please clarify one thing? I think the difference here is that now it won't be testing the worst possible scenario:

is a test only implementation that implements the networking layer in the worst possible way since it blocks and uses a thread per request model.

was MockTcpTransport not effective?

Could you please clarify one thing? I think the difference here is that now it won't be testing the worst possible scenario:

The commits in https://github.com/crate/crate/pull/11909 give a bit more context to the change. In particular https://github.com/crate/crate/pull/11909/commits/80c2f5cd32b80b531d38ae7a60405d722850e8f8 & https://github.com/crate/crate/pull/11909/commits/4e36638e2029f9417ea75ed66d2294d291058047
Given that the transport is no longer pluggable, we benefit more from testing the real thing than testing hypothetical worst possible implementations.


[Bug] Black screen

When I start the game and enter a map a strange black screen appears on the entire screen. happens on any map
Additional information:

Game Version:chromium, x86-64
Game Type::singleplayer

did you removed old beatrun before updating?
remove everything old (beatrun and vmaniprework folder if you have them) and install latest one from here

yes i removed

there was a black screen lua in "license" releases, we dont have it here, so I don't have why you have that error. Try joining our Discord server and asking for help there

how to enter the server, i dont know lol

https://beatrun.ru, there is a button for our discord and courses database


shim-shadowdom gets removed by pub build

Originally opened as dart-lang/sdk#19860
This issue was originally filed by<EMAIL_ADDRESS>
What steps will reproduce the problem?

Place a <link rel="stylesheet" href="something.css" shim-shadowdom> tag in the head section of a page.
Run pub build.
View the page from the build folder in for example Firefox.

What is the expected output? What do you see instead?
The new selectors, e.g. /deep/ should work but they don't. The pub build command replaces the link tag with a style tag that contains all the rules. However, shim-shadowdom is missing from the style element. If I put the attribute on the element manually, everything works as expected. But I think pub build should not remove this attribute if the original page contained it.
What version of the product are you using? On what operating system?
Windows 8 x64
Dart SDK 1.5.3
polymer 0.11.0+5
A minimal example:
index.html
    <!DOCTYPE html>

        <link rel="stylesheet" href="index.css" shim-shadowdom>
        <link rel="import" href="packages/polymer/polymer.html">

        <polymer-element name="my-element" noscript>
          <template>

Hello, World!

          </template>
        </polymer-element>

        <my-element></my-element>

index.css
    my-element /deep/ h1 {
      color: red;
    }
And the index.html file in the build folder contains this:

Instead of this:

And the h1 element appears black in Firefox instead of red.

 Comment by sigmundch

Thanks for filing this bug and for the short repro test case!
Indeed pub-build should not inline this css file, and in general should be more configurable so that it doesn't always do this (see issue dart-lang/polymer-dart#395 too)

Added this to the 1.6 milestone.
Removed Priority-Unassigned label.
Added Priority-Medium, Area-Pkg, Pkg-PolymerBuild, Triaged labels.

 Comment by jakemac53

Issue dart-lang/polymer-dart#166 has been merged into this issue.

 Comment by sigmundch

Added PolymerMilestone-Next label.

 Comment by sigmundch

Removed Polymer-P-1 label.
Added Polymer-Milestone-Next label.

 Comment by sigmundch

Removed Polymer-Milestone-Next label.

 Comment by sigmundch

Removed this from the 1.6 milestone.
Added Polymer-P-1 label.

 Comment by jakemac53

Fixed in dart-lang/sdk@45b7fa47eb85a62b1a1e436e9b22a1c6eb944c5f

Added Fixed label.

 Comment by jakemac53

Set owner to @jakemac53.
Added Started label.


YAAPT handles the case when only two consecutive frames are voiced.

pchip and spline interpolation methods failed, so linear interpolation is now used in this case.
I changed the version number to <IP_ADDRESS>, maybe not necessarily.

Ok, cool, thanks for the feedback.
I wonder if in this case where there are only two consecutive frames the interval could be considered a real "voiced frame" due its (probably) short duration.
But anyway, this is also dependent from the sample frequency and the spoken language, so the modifications are welcome.

Currently I'm in the middle of another project (sorry, I have to pay my bills somehow ;) ), but once I'm finished, I want to work back on AMFM_decompy v1.1. I have another AM-FM decompostion method to add, and nevertheless, the current code is already more than a year without updates.
Probably then I'll add your modifications to the main branch. But until then, I'll keep this v<IP_ADDRESS>.

Cool! Actually I have some more fixes already and I'll probably submit
another PR soon. Good luck with your another project. :-)
czw., 7 lip 2016, 19:20 użytkownik bjbschmitt<EMAIL_ADDRESS>napisał:

Currently I'm in the middle of another project (sorry, I have to pay my
bills somehow ;) ), but once I'm finished, I want to work back on
AMFM_decompy v1.1. I have another AM-FM decompostion method to add, and
nevertheless, the current code is already more than a year without updates.
Probably then I'll add your modifications to the main branch. But until
then, I'll keep this v<IP_ADDRESS>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bjbschmitt/AMFM_decompy/pull/1#issuecomment-231147005,
or mute the thread
https://github.com/notifications/unsubscribe/APgGnl27LanAsOJDAZ4eb_4XGU2aygKTks5qTTVIgaJpZM4JGGMm
.


View pending users in manage users

At the moment if someone tries to join your Dojo you have to accept them via an email link. It would be useful to have a list of pending users in the manage users section with the option to approve them in here.

Still "invites" to be displayed to be consider "pending" to be finished


500 internal Server Errror  ?state=2BD4u......

Hi Mohammad,
like in the Issue #40 I experience the same errors. As you stated I set the Breakpoint and saw, that there could be a Problem when the webpage is not in the "root" Directory.
My Webpage starts with following Url:

If no modifications to the Callback Path are made I get this Error:

I modified the Code this way:

Now it seems working fine:

I saw that I also can Modify StartupAuth.cs
app.UseMixedAuth(new MixedAuthOptions()
            {
                CallbackPath = new PathString("/AUDM/MixedAuth"),
                Provider = new MixedAuthProvider()
                {
                }
            }, cookieOptions);

Is this the correct way? Do I have to setup MixedAuth for my page in a different Way?
Regards Dumitru

Hi,
No need to modify the path, it will be auto resolved to include you application base path.
Most probably, you don't have the windows authentication section unlocked as described in the README which might cause a 500 error.
Thanks.

Hi Mohammad,
thanx for your reply. You were right. I changed the  IIS Express Configuration to

Now it works.
Regards Dumitru


Fixes in DateTimeIndex, Vector and Index related to working with empty indexes

There are quite a few changes, they all came to light when I was debugging my project. The tests are passing fine. Let me know if there is any problem.

Great! Could you also add test cases that would actually run these edge cases so that future contributors will readily know when something goes wrong?

@Phitherek are you still working on this?

@v0dro I'm sorry, I don't have much time right now but I remember about it and I will certainly write some tests for this when I find time.

@Phitherek have you had the time to write tests for this? I'd like to merge these fixes before the next release, which is due soon. Tests will also pave the way for discussion if the features you've introduced are in the spirit of the library as a whole.

@v0dro Sorry, I haven't found time yet... When are you planning to release the next version?

As soon as a few fixes that I'm waiting for are ready, which should be early next week. One spec per fix should be enough.

Outdated.


Tabular: Fixed crash on NaN labels in evaluate_predictions

Issue #, if available:
Description of changes:
Fixed crash when NaN labels are present in y_true during evaluate_predictions, now it properly shows the warning and drops the NaN rows.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-621-2 is done.
Docs are uploaded to http://autogluon-staging.s3-website-us-west-2.amazonaws.com/PR-621/2/index.html


range -> zmax/zmin doesn't work with DirectionalLight2D

Godot version
4.1.1.stable.official
System information
Godot v4.1.1.stable - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 Ti (NVIDIA; <IP_ADDRESS>34) - 12th Gen Intel(R) Core(TM) i5-12600K (16 Threads)
Issue description
the range->zmin/zmax options don't work in DirectionLight2D (though they do work in PointLight2D).  out of zrange nodes (including textures and polygon2Ds) are still effected by the light.
Steps to reproduce
Under a new Node2D, create two ploygon2D.  change the z index to -5 on one and 5 on the other.
Create a DirectionalLight2D.  set intensity to 0.8, blend mode to subtract, z max to 0.
the z=5 should stay white and the z=-5 should be dark, but instead both are dark.  A similar setup with point light works as expected.
Minimal reproduction project
bug test.zip

I'd argue bug since it's got the zmin/max properties and there is a consistent way to apply their use.
Also it inherits from light2D which has those properties documented.  https://docs.godotengine.org/en/stable/classes/class_light2d.html#class-light2d-property-range-z-max

Add support for it will need some effort, maybe we can add the directional light data into push_constant or add another field for directional light.

Related to https://github.com/godotengine/godot/issues/48757.

Still does not work in version 4.1.2 stable. It would be great if you could increase the priority on this ticket, as 2D global illumination is basically not usable.

Same bug in 4.3


The transfer amount is debited before the payment link is sent

Pre-condition:
The user is logged in
Steps:

Open the https://gooddev.netlify.com?paymentCode=47c177f8a19c734eca0a&reason=Vgf
Tap the "Send" button
Enter the recipient name and tap the "Next" button
Enter the amount and tap the "Next" button
Enter the message and tap the "Next" button
Tap the "Confirm" button
Pay attention to the amount on the top right

Device: iPhone X // iOS 12.4 // Safari
Dev env:
https://www.screencast.com/t/YSZyIOabusV

@AnastasiiaOdnoshevna that's the expected behaviour
once your press confirm the payment is made and balance is debited
the only thing i didnt see if it created the feed card for the TX, where you should be able to cancel

Checked on  eWallet environment
Reproduced on Android 8.1.0 // Huawei P20

Duplicate of #1034


Remove dependencie innecesary composer.json.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Dependency checker work only with composer 2, but demo application should work also on composer 1.


add web ui dashboard

add web based ui for access database

there is no web ui support well TLS now, skipped.


Change doc and source branch of image_transport_plugins in melodic

A melodic branch has been split off in image_transport_plugins due to a backported feature which is untested in previous eol distros.

Thanks @methylDragon !


[Bug] Inview not getting triggered when the targed is an svg path

1. Describe the bug
Basically when you try to target a path tag using the inView function, it doesn't work, but it works for other elements
2. IMPORTANT: Provide a CodeSandbox reproduction of the bug
https://codesandbox.io/s/pensive-marco-7cp3vs

I believe this is a browser limitation with the IntersectionObserver


Fix large strings

Fixes #4.

thanks a lot! I had to remove the 9999 string because Lua 5.1 took too much time (with the other ones it takes ~10 minutes to pass the tests)


Reshape the format to tables, add more detail comment for each library

Reshape the format to tables, add more detail comment for each library

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.


Fix an error when swagger type is object, but doesn't have the type attribute

I fixed an error that caused me some headache, but I still don't think it's completely right now.
If a swagger object has an array of strings as "required" attribute, it will result in a type that has "isRequired" set to true. That doesn't feel right.
Microsoft Reviewers: Open in CodeFlow

Sorry, I still need to fix the tests first

Okay... correct me if I'm wrong. It looks like the tests fail due to my fix. I think the snapshots where wrong.
this is the test error:
  ● Should resolve protected api

    expect(value).toMatchSnapshot()

    Received value does not match stored snapshot "Should resolve protected api 1".

    - Snapshot
    + Received

    @@ -17,20 +17,20 @@
      export type ConfigureRequestHandler = (agent: SuperAgentRequest) => SuperAgentRequest;

      export type CallbackHandler = (err: any, res ? : request.Response) => void;

      export type Authentication = {
    -     'token_type' ? : "bearer";
    -     'expiration_date' ? : {};
    -     'access_token' ? : string;
    -     'refresh_token' ? : string;
    -     'project_tokens' ? : {};
    +     'token_type': "bearer";
    +     'expiration_date': {};
    +     'access_token': string;
    +     'refresh_token': string;
    +     'project_tokens': {};
      };
...

and this is the corresponding swagger file:
"definitions": {
        "Authentication": {
            "required": [
                "token_type",
                "expiration_date",
                "access_token",
                "refresh_token",
                "project_tokens"
            ],
            "properties": {
                "token_type": {
                    "type": "string",
                    "description": "The API token type",
                    "enum": [
                        "bearer"
                    ]
                },
...

In my opinion that's correct. how can I update the snapshot?

Hi! You are right, the snapshots definitely look wrong!
Your fix looks good, so lets just get the snapshots updated, then we should be good to go 👍
I pushed a minor update to master that adds a simple updateSnapshots command to the repo. If you merge with latest master you can run npm run updateSnapshots
Thanks for fixing this!

All tests are green. We're good to go now.
Thank you for maintaining this repo!

Completed and published as 3.2.0. Thanks for helping out!


chore: release main

:robot: I have created a release beep boop
config: 0.3.0
0.3.0 (2023-12-16)
⚠ BREAKING CHANGES

mimic the regular error class interface

Bug Fixes

mimic the regular error class interface (a2501ce)

Documentation Changes

fix a typo (616a87b)

Dependencies

The following workspace dependencies were updated

dependencies

@rmtc/errors bumped from ^0.1.0 to ^0.2.0

create-toolchain: 0.1.2
0.1.2 (2023-12-16)
Bug Fixes

switch to the new error inferfaces (da2e5fb)

Dependencies

The following workspace dependencies were updated

dependencies

@rmtc/config bumped from ^0.2.0 to ^0.3.0
@rmtc/errors bumped from ^0.1.0 to ^0.2.0

errors: 0.2.0
0.2.0 (2023-12-16)
⚠ BREAKING CHANGES

mimic the regular error class interface

Bug Fixes

mimic the regular error class interface (a2501ce)

plugin: 0.2.0
0.2.0 (2023-12-16)
⚠ BREAKING CHANGES

run executables with node_modules paths

Bug Fixes

run executables with node_modules paths (3a13993)
switch to the new error inferfaces (da2e5fb)

Dependencies

The following workspace dependencies were updated

dependencies

@rmtc/config bumped from ^0.2.0 to ^0.3.0
@rmtc/errors bumped from ^0.1.0 to ^0.2.0

plugin-biome: 0.2.0
0.2.0 (2023-12-16)
⚠ BREAKING CHANGES

run executables with node_modules paths

Bug Fixes

run executables with node_modules paths (3a13993)

Dependencies

The following workspace dependencies were updated

dependencies

@rmtc/plugin bumped from ^0.1.2 to ^0.2.0

@rmtc/plugin-eslint: 0.1.3
Dependencies

The following workspace dependencies were updated

dependencies

@rmtc/plugin bumped from ^0.1.2 to ^0.2.0

plugin-mocha: 0.2.1
0.2.1 (2023-12-16)
Bug Fixes

switch to the new error inferfaces (da2e5fb)

Dependencies

The following workspace dependencies were updated

dependencies

@rmtc/config bumped from ^0.2.0 to ^0.3.0
@rmtc/plugin bumped from ^0.1.2 to ^0.2.0

@rmtc/plugin-npm-scripts: 0.2.2
Dependencies

The following workspace dependencies were updated

dependencies

@rmtc/plugin bumped from ^0.1.2 to ^0.2.0

@rmtc/plugin-types-in-jsdoc: 0.2.1
Dependencies

The following workspace dependencies were updated

dependencies

@rmtc/plugin bumped from ^0.1.2 to ^0.2.0

toolchain: 0.1.3
0.1.3 (2023-12-16)
Bug Fixes

switch to the new error inferfaces (da2e5fb)

Dependencies

The following workspace dependencies were updated

dependencies

@rmtc/config bumped from ^0.2.0 to ^0.3.0
@rmtc/errors bumped from ^0.1.0 to ^0.2.0
@rmtc/plugin bumped from ^0.1.2 to ^0.2.0

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/rowanmanning/toolchain/releases/tag/config-v0.3.0 :sunflower:

:robot: Release is at https://github.com/rowanmanning/toolchain/releases/tag/create-toolchain-v0.1.2 :sunflower:

:robot: Release is at https://github.com/rowanmanning/toolchain/releases/tag/errors-v0.2.0 :sunflower:

:robot: Release is at https://github.com/rowanmanning/toolchain/releases/tag/plugin-v0.2.0 :sunflower:

:robot: Release is at https://github.com/rowanmanning/toolchain/releases/tag/toolchain-v0.1.3 :sunflower:

:robot: Release is at https://github.com/rowanmanning/toolchain/releases/tag/plugin-biome-v0.2.0 :sunflower:

:robot: Release is at https://github.com/rowanmanning/toolchain/releases/tag/plugin-eslint-v0.1.3 :sunflower:

:robot: Release is at https://github.com/rowanmanning/toolchain/releases/tag/plugin-mocha-v0.2.1 :sunflower:

:robot: Release is at https://github.com/rowanmanning/toolchain/releases/tag/plugin-npm-scripts-v0.2.2 :sunflower:

:robot: Release is at https://github.com/rowanmanning/toolchain/releases/tag/plugin-types-in-jsdoc-v0.2.1 :sunflower:


Fix new methods in renamed AccountsAdapter to return correct type

Critical Changes
Changes
Issues Closed
Community Ideas Delivered
Features Intended for Future Release
Features for Elevate Customers
New Metadata
Deleted Metadata

It looks like there are some things that need to be fixed in Application also.  It looks like merge of the domain branch into the undeliverable branch did not catch everything.


Feature/reorganize ingredient data

Problem
the 4th task in Migrate old ingredients into new "objects dict" #57
Solution
Created a partners object to convert ingredients that should be moved into this object.
Wrote tests for _convert_to_objects
Type of change
Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

merged to staging/ and deleted feature/ branch, grateful for helps!


Only Phind and Bing are GPT-4 by default.


feat: add timeout option

Motivation

In our recent contribution to the open-source project, we focused on enhancing the robustness of the RPC handling mechanism within the cast CLI tool. The primary motivation for our changes was to improve the user experience by implementing a timeout feature for RPC requests, which addresses potential issues of hanging requests that can lead to frustration during usage. By introducing a configurable timeout, users can now have better control over their interactions with the RPC, ensuring that they receive timely feedback even in the event of network delays or server unresponsiveness. This enhancement not only optimizes performance but also aligns with best practices in software design, contributing to the overall reliability of the tool.

The solution implemented in our code change involves adding a timeout feature for RPC requests in the cast CLI tool. By introducing a timeout argument, users can specify the duration (in seconds) for which the CLI will wait for a response from the RPC server before aborting the request. This is achieved by leveraging the Duration type to set a timeout that prevents hanging requests, enhancing the overall user experience. The new feature is integrated seamlessly into the existing command-line argument parsing and request handling, ensuring backward compatibility while improving the responsiveness and reliability of the tool.

update the code !

there is some issue related to my github i reopen it with as new issue

Review the updated code!


Add support for user defined scalar functions

This PR adds support for user defined scalar functions.  See #7368.
@divega @roji - per the conversation in #2850 I have made some modifications and broken my changes into multiple PRs. This is the first part.
This PR contains the api used to define UDFs and the back end changes needed to execute them.
From my original code I have pulled out the EFFunction extension methods and the changes which converted the existing supported scalar methods from using IMethodTranslator to the new API.  Those changes will come in later PRs.

@pmiddleton,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@pmiddleton I'm going to start looking at this (thanks BTW!), can you rebase to latest dev?

@anpete I have rebased to latest dev.  I look forward to your feedback.
There is one implementation area specifically I am interested in your thoughts on.
As it stands with this PR there are two different paths which functions can take through the translation process.  All custom functions with be converted into DbFunctionExpression during Relinq query parsing and later to SqlFunctionExpression as the expression tree is walked.  Any built in functions will continue to be converted directly to SqlFunctionExpressions via IMethodCallTranslator during expression parsing.
The reason I went the DbFunctionExpression route is that it allows converting function calls which are a part of a from clause.  This will allow support of Table Value Functions as query sources.  (I have a POC of this working)
My original cut of this feature included converting all of the existing IMethodCallTranslator's to use the new DBFunction creation api defined in this PR.  The outstanding question I have is whether it is worth doing that conversion, and deprecating IMethodCallTranslator, in order to get the code down to a single function translation path.

@anpete - Have you had a chance to take a look at this PR yet?

@pmiddleton It is next on my todo list 😄

@pmiddleton Thanks for submitting this thorough PR! Some initial feedback/thoughts:

I don't think we need to add functions to Core. In our new architecture, it seems like these should be implemented in relational as annotations. Similarly, the Code First APIs can be realized using our provider extension method pattern.
In line with that, I think we can then have relational use these annotations to create and register handlers into our existing method call translator system.
So what we end up with is an easy way to create custom method translators via fluent API/annotations, but one that integrates with our existing translation system.

Let me know what you think.

I put things into Core to allow support in both relational and non-relational data sources.  Raven, Mongo, Hadoop all support some form of UDF.  Is better to try to come up with a shared solution for relational and non-relational in Core, or will that cause too many limitations for each system type that it is better to go with separate implementations?  I can see arguments both ways.

In regards to tying into the existing translation system.  That was the first approach I looked at and the problem I ran into was adding support for Table Value Functions.  The implementation became more straight forward when TVFs were translated into DbFunctionExpressions earlier in the translation process. You don't have to deal with trying to convert method calls in the MainBody and AdditionalFromClauses. That being said if we want to remove code from Core then this warrants another look as well.

Another question driving the translation timing is whether there are any advantages to knowing a function is translatable, vs needing client eval, earlier in the query transformation process.

What are your thoughts on the non-relational support?  Would that be something better left to a non-relational base layer vs Core?

I think we would go with separate implementations just for simplicity and because we don't really understand what we need for functions on those other providers. A related point is that in the PR DbFunction has a Schema property, but EF Core is very careful to keep this as a relational concept. I also think it will just greatly simplify the impl, without really taking away any of the benefits of the new APIs you are proposing.
I'm happy to help where I can if you hit any issues integrating with the current method translation extensibility. I think it would be fine to scope-out TVFs for this initial support, too.
Not really, either the method can be translated during SQL translation, or not. If not, we will compile the call into the tree directly, which is nice if the CLR method can have an impl. because it enables testing against im-memory. That looked to be what you were going for in DbFunctionUnwindingExpressionVisitor.

I will start take a look at these changes.
I might have to hit you up with questions on the annotations and the api extension point, but I'm sure I can find a good example in the codebase to follow.
I will start looking at the TVF tie in with From clauses to make sure we are not backing ourselves into a corner, but support for materializing non entity types is needed before the feature can be finished.

@anpete
I am working through migrating the code to live in the Relational project and converting the metadata classes to use annotations as discussed.  I am using the existing relational Sequence class as an example to follow for the metadata classes.
I don't understand why Sequence is internally serializing it's data before storing it in the model.  What advantage does that give vs just storing the sequence object directly?  Should this serialization approach be used for other items in Relational which store themselves in annotations on the model?
@ajcvickers  - you added the serialization code so can you help me understand why this was done?
Thanks!

@pmiddleton Basically so that the model can be serialized and then read back. Specifically, the model snapshot, used by migrations, is a serialized form of the model. However, if the code that creates the snapshot understands the annotation and can write appropriate C# code, then this is better and the annotation can be any type. I think we added this for Sequence, so it may be that sequences don't need to be stored like this anymore. Likewise, any new annotations need to be either ignored by the snapshot (if they don't impact anything migrations would do) or serialized either by being stored as a simple type (e.g. string) or by having special code that understands them.

@anpete - Quick question before I end up writing a bunch of code that I might  not need to.
As part of the udf setup process I have a convention which processes registered dbFunctions by setting up name, arguments, etc.  In my original code I added a new property to ConventionSet to handle conventions for database functions.  I don't see anything in the relational project for extending ConventionSet in this way.  Am I missing something?  I'm trying to avoid extending ConventionSet if I can :smiley:

@AndriySvyryd to respond to last question.

@pmiddleton You would need to add IModelAnnotationSetConvention in Core similarly to IEntityTypeAnnotationSetConvention and the implementation would filter on the annotation name like SqlServerMemoryOptimizedTablesConvention

@anpete I'm looking for your thoughts on the integration with the current method translation for UDFs.  I'm debating a design choice I made.
Currently classes which derive from RelationalCompositeMethodCallTranslator are loaded into DI as singletons.  In order to perform method translation RelationalCompositeMethodCallTranslator now needs the current model in order to have access to the UDF metadata stored in the annotations.
I ended up replacing IMethodCallTranslator on RelationalCompositeMethodCallTranslator with a new interface that has a translate method which takes the IModel as a parameter.  This works, but it involved creating a new interface which providers have to update their derived classes to use.
I'm debating if it would be better to switch RelationalCompositeMethodCallTranslator to have a Scoped lifetime and DI the IModel.  Thoughts?
I have everything up and running with the new approach.  I am currently in process of getting the remaining unit tests moved over and working.

Great to hear that you are making progress!
I'm actually OK with either approach. Another option would be to add the IModel parameter to IMethodCallTranslator.Translate itself.
cc @ajcvickers for input.

@pmiddleton @anpete I would probably err on the side of making the service scoped and having the IModel injected. It seems cleaner in this case. But I don't feel strongly.

@anpete
I am getting close to being done.  I have made my changes on a different branch and I think it makes more sense to do a new PR.  Does that work for you or would you prefer I try to rebase this one?

@pmiddleton New PR is fine.


Relations between documents

Hi all! I want to create relations between documents. Is there any way how to do this?

@motionrus What kind of relations do you want to have?

I want simple relations, between bbox, but this bbox made different images (documents)

I would recommend that you use meta field where you can type any string.

So, you can write something like this there:
<task_id:region_id>

+1 for relations that can be on different pages! :)