System.InvalidCastException when DataGrid's AutoGenerateColumns set to True

Steps to reproduce:

Create a DataGrid with AutoGenerateColumns set to True
Bind it to a collection of objects for which not all columns have column definitions defined explicitly

Expected result:
DataGrid successfully generates missing columns
Actual result:
System.InvalidCastException
HResult=0x80004002
Message=Unable to cast object of type 'System.Windows.Controls.DataGridColumnCollection' to type 'System.Windows.Controls.DataGrid'.
Source=FluentUI
StackTrace:
at FluentUI.FabricHelper.<>c.<OnTextColumnStyleChanged>b__3_0(Object s, NotifyCollectionChangedEventArgs eventArgs)
at System.Collections.ObjectModel.ObservableCollection`1.OnCollectionChanged(NotifyCollectionChangedEventArgs e)
(...)

In FabricHelper.cs line 69 event sender is casted to DataGrid. When DataGrid adds a column automatically, sender is actually a DataGridColumnCollection

can you see if branch https://github.com/adospace/fluent-ui-xaml/tree/fix-issue-4 is working for you?

Thanks, it works fine on this branch


docs: add d3 tree example

An obious and simple example.

Should we just include the result or the d3 code as well? Feels like a complete example would be good but messier. Maybe "both" - a separate example with d3 in action, a copy of the result in general examples page.


run goimports

It's easy enough to run goimports programatically (it's exposed as a package, not just an executable), so fzgen should just do it, rather than:
// if needed, fill in imports or run 'goimports'

Hi @josharian it does already programmatically run imports.Process from the golang.org/x/tools/imports package.
And I have a TODO In the code to remove that noisy comment you are referencing, but I am slightly worried about corner cases, which is why I haven’t removed it yet.
That said, no time like the present.
A general comment is thank you again for taking the time to file these quick issues based on your first impressions… Hopefully it will help smooth things out for others…

Hi @josharian, I am going to take the liberty of retitling this to be about the effectively misleading or at least not very useful comment.
The comment should be eliminated with PR #16.
Thanks again!


[WIP] Upgrade to controller-runtime v0.8.1 and Kubernetes v0.20.2

To support Rook v1.6 we need controller-runtime v0.8.x.
This in turn requires Kubernetes v0.20.2, which in turn requires support from operator-sdk.
There seem to be some breaking changes which we need to account for.

I imagine this PR is now partly done by #1022?

Changes included in #1141


Your domain won't resolve

It finally gets redirected to http://ww1.obsidian.garden/ which I'm assuming isn't the intended behavior.

In that case, you might want to not link to it from Github etc? Not sure. I think users of this project might be able to support some costs.

Thanks, I've removed it - this was only a side project and was given away for free. I'd never asked anyone to fund it, but I also don't have any duty to continue with it either.

Gotcha. I'm using it currently, and it is helping me a lot. Thank you for sharing this :)


add support to mp4 file get_batch with audio data.

Thanks for your great job. I tried this library with some mp4 files with get_batch method to decode specific video frames. This mp4 files have both video and audio data in it.   I suspect the library can not support this kind of mp4  files with both video and audio data. Would we support this scenario in plan?

Indeed I can reproduce the issue. So I will try to look into it.
Meanwhile, maybe you can workaround it by using video_reader.decode() if you are taking sub-clip of a video with evenly spaced frames you can use for example video_reader.decode("/path/to/file.mp4", compression_factor=0.25, start_frame=100, end_frame=200). Which would take 1 frame out of 4 (compression_factor=0.25) between frame 100 and 200.

Should be fixed in ac35dadc511f73eed3ec48a1b1b9699f3ac0ddd6


[GROSS HACK] Just seeing if Timidity can work

Am I checking in all of timidity?

This seems to "work" (it can play the file more or less) in dev mode but I guess the static assets (the wasm file) don't get moved (or something) in the prod build.

Okay. I just got them all moved into the demo directory in an ugly way. It works! You can drag in midi files. Visualizer/EQ/Volume does not work, but the basic idea is there.

Some notes I took while getting this working
building

# From https://emscripten.org/docs/getting_started/downloads.html

# Get the emsdk repo
git clone https://github.com/emscripten-core/emsdk.git

# Enter that directory
cd emsdk

# Fetch the latest version of the emsdk (not needed the first time you clone)
git pull

# Download and install the latest SDK tools.
./emsdk install latest

# Make the "latest" SDK "active" for the current user. (writes ~/.emscripten file)
./emsdk activate latest

# Activate PATH and other environment variables in the current terminal
source ./emsdk_env.sh

./node_modules/.bin/browserify -t brfs index.js -o bundle.js


fix: backport Black screen fix to beta branch

Description
Backporting #1820
Linked Issues/Tasks
Type of change
Bug fix
Tests
No test

If I understand correctly this also adds the fix from:

#1773
Which very nice IMHO, just wanted to have it mentioned for treaceability


Increate .travis.yml consistency between repos

aspnet/Universe#349
minimize dotnet setup time; no need for caching
build with --quiet

bfd2c36


Refactoring: Improve serialization performance

:scroll: Description
Improve performance by doing serialization in one step, see https://api.dart.dev/stable/2.17.0/dart-convert/JsonUtf8Encoder-class.html
#skip-changelog
:bulb: Motivation and Context
:green_heart: How did you test it?
This is covered by existing tests
:pencil: Checklist

[x] I reviewed submitted code
[x] I added tests to verify changes
[x] I updated the docs if needed
[x] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

Nice, @ueman some tests failed tho.


Installation fails on OS X

After sudo npm install grunt-iconizr terminal outputs me this errors:
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Darwin 14.4.0
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Work/Targi_Smaku/node_modules/grunt-iconizr/node_modules/iconizr/node_modules/svg-sprite/node_modules/phantom-sync/node_modules/phantom/node_modules/dnode/node_modules/weak
gyp ERR! node -v v0.12.3
gyp ERR! node-gyp -v v2.0.1
gyp ERR! not ok
npm ERR! Darwin 14.4.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.3
npm ERR! npm  v2.12.1
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the libxmljs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls libxmljs
npm ERR! There is likely additional logging output above.

I'm using:
OS X 10.10.4
npm 2.12.1
phantomjs 2.0.0
grunt 0.4.5
grunt-iconizr 0.2.3
npm-debug.log -> https://gist.githubusercontent.com/dawidk92/1d333f13d77a6c3ed9e6/raw/gistfile1.js

Hey @dawidk92,
this seems to be a long-term problem with the libxmljs dependency on the Mac, please see for example here for one of the issues regarding this. I don't know any fix, I'm sorry.
However, there's a new generation of node-iconizr respectively grunt-iconizr in the dev branch that doesn't have the libxmljs dependency anymore. Unfortunately, the new version is only poorly documented so far and I won't have the time to finally push it out of the door before August. You may give it a try, however.
Good luck and cheers,
Joschi

same issue here on Ubuntu with node v5.9.1 and npm 3.8.2

@jonasva Did you try the most recent version as decribed in the previous comment?


Get the telnet protocol working

It's already added to the configuration window, but doesn't work online.

Turns out it's not even implemented. Nothing happens after it sends 0x03.

Don't you have to send 0x03 0x04 ?

0x03 tells bnetd that you want to use the Telnet protocol. 0x04 tells bnetd that you want to disable echoing your input back. Although no custom servers properly handle 0x04 and BNETDocs is lacking in that area.
I have plans to refactor the documentation on the subject.

I see you are correct, I've changed my bot to just send only 0x03 byte.  It connects to emwar servers just fine without the 0x04.

Using emNet as a source of truth is asking for trouble. They only just barely implemented packet overflow protection. They still don't have UDP support, so clients that actually ask the server for its UDP code instead of always providing 0x74656e62 (bnet if you decode it as a string) will always have the plug icon (like BNRBot).

This issue should be reverified to see if it's still an issue. There have been changes to the way BNRBot handles Telnet/Chat protocols since the implemenation of Init 6 in #41.


Use elipsis on header bar for small device to make longer page titles fit

The layout might even also have to be broken down.


Debug output file should be settable in the configuration file

Debug output goes to stderr, or the file indicated by the COVERAGE_DEBUG_FILE environment variable.  It should also be settable in the configuration file.

This is implemented in commit 5f65d87b14245d4523bc866a75a16b6c55a7ce70

This is now released as part of coverage 7.1.0.


Upstream connect error or disconnect/reset before headers. reset reason: overflow

Bug description
One of my service return 503 status and the message upstream connect error or disconnect/reset before headers. reset reason: overflow
Expected behavior
Don't return  503 and respond normally.
Steps to reproduce the bug
I cannot reproduce this bug.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
istioctl version --remote
1.3.4

kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-15T19:18:23Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.12-eks-c500e1", GitCommit:"c500e11584c323151d6ab17526d1ed7461e45b0c", GitTreeState:"clean", BuildDate:"2019-10-22T03:11:52Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}

helm version
Client: &version.Version{SemVer:"v2.16.1", GitCommit:"bbdfe5e7803a12bbdf97e94cd847859890cf4050", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.16.1", GitCommit:"bbdfe5e7803a12bbdf97e94cd847859890cf4050", GitTreeState:"clean"}

How was Istio installed?
helm
Environment where bug was observed (cloud vendor, OS, etc)
AWS EKS
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.
This service worked in the production environment for three days and 503 problem suddenly appears. After delete the pod of istio-ingressgateway, the service can work agagin.

Does anyone know what caused the problem?

reset reason overflow generally indicates that circuit breaker has been triggered. Is this happening at higher concurrency?

@ramaraochavali Just very low concurrency, the incoming request data from grafana was displayed in 30 ops per second.

I can't find any helpful information, but I find istio-telemetry and istio-policy consume a lot of memory.

@zhulinwei care to share your findings on how you resolved this issue?

@zhulinwei care to share your findings on how you resolved this issue?

I can't do nothing but restart istio.

i see, @zhulinwei so you restarted all the components in istio and the affected pods with their sidecar prxies too? Did u run into the overflow issue again after restart?

Finally, I figured out whats happening in my environment, I am running istio 1.3.3 with eventhough global envoy circuit breaker setttings were
        "circuit_breakers": {           "thresholds": [             {               "priority": "DEFAULT",               "max_connections": 100000,               "max_pending_requests": 100000,               "max_requests": 100000             },             {               "priority": "HIGH",               "max_connections": 100000,               "max_pending_requests": 100000,               "max_requests": 100000             }           ]         },
These settings were overriden by Istio's destiantion rule which by default accroding to https://archive.istio.io/v1.3/docs/reference/config/networking/v1alpha3/destination-rule/#ConnectionPoolSettings-HTTPSettings
its 1024, which caused overflow errors. Updating these params will help if we are using Istio 1.3 or upgrading to 1.5 which has default of https://istio.io/docs/reference/config/networking/destination-rule/#ConnectionPoolSettings-HTTPSettings.


azure-cognitive-services-docker Key Phrase Extraction

The Key Phrase Extraction container returns a 500 error. Looking in the logs, azure-cognitive-services-docker
RequestUri='http://localhost:5000/text/analytics/v3.1/keyPhrases' RequestMethod='POST' RequestHeaders='{
"content-type": [
"application/json-patch+json"
],
"accept": [
"application/json"
],
"accept-encoding": [
"gzip, deflate, br"
],
"accept-language": [
"en-US,en;q=0.9"
],
"content-length": [
"347"
]
}' RequestRouting='/text/analytics/v3.1/keyPhrases' RequestId='6b3f405c-7204-4e0e-90e0-c685c62864a8' UnobservedTaskException='False' IsExternal='True' PodName='N/A'
info: Microsoft.CloudAI.Containers.Diagnostics.RequestCorrelationMiddleware[0]
RequestCorrelationMiddleware:ServiceOperation 2021-10-13T14:11:43 195.161 False  SubscriptionId='' RequestId='6b3f405c-7204-4e0e-90e0-c685c62864a8' Timestamp=''
fail: Microsoft.CloudAI.Containers.Diagnostics.ExceptionMiddlewareV2[0]
Specified argument was out of the range of valid values. (Parameter 'MaxDegreeOfParallelism') SubscriptionId='' RequestId='6b3f405c-7204-4e0e-90e0-c685c62864a8' Timestamp=''
The link in the DockerHub reference to raise an issue also goes to a 404: - https://github.com/Azure/azure-cognitive-services-docker

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

ID: 73a43800-f76a-f114-f4a2-ed18785b7c76
Version Independent ID: 172adee6-e47b-b68d-0687-2c9009052559
Content: Install and run Docker containers for the Text Analytics API - Azure Cognitive Services
Content Source: articles/cognitive-services/text-analytics/how-tos/text-analytics-how-to-install-containers.md
Service: cognitive-services
Sub-service: text-analytics
GitHub Login: @aahill
Microsoft Alias: aahi

Hi there - I am getting this when I am querying the endpoint. To reproduce, you can simply get the Swagger Ui up and POST any of the messages to the endpoint. This log is for
'/text/analytics/v3.1/keyPhrases'


[KOGITO-608] preliminary work for drools-model unfork

cool, the diff looks pretty small overall!

ok to test

jenkins test


add debug vs code config

PR Details

Description

Give a good explanation about this PR, including about the files you've changed.
Related Issue

Issue Title (PR_ID)
Steps to Reproduce

Write your steps here:

Sample
Of
Steps

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Duplicate of #31


How to use Neon deployed by docker-compose with autoscaling Kubernetes cluster deployed by kind?

I have now deployed a Neon cluster using docker-compose, and the node information is as follows:
# docker ps
CONTAINER ID   IMAGE                                              COMMAND                  CREATED          STATUS             PORTS                                              NAMES
e6ad7d839d55   docker-compose_compute                             "/shell/compute.sh"      45 minutes ago   Up 45 minutes      <IP_ADDRESS>:3080->3080/tcp, <IP_ADDRESS>:55433->55433/tcp   docker-compose_compute_1
ce312f9c47bc   neondatabase/neon:latest                           "/bin/sh -c '/usr/lo…"   46 minutes ago   Up 45 minutes      6400/tcp, <IP_ADDRESS>:9898->9898/tcp                   docker-compose_pageserver_1
d6c3aa8c81bc   neondatabase/neon:latest                           "/bin/sh -c 'safekee…"   46 minutes ago   Up 46 minutes      6400/tcp, 9898/tcp, <IP_ADDRESS>:7677->7676/tcp         docker-compose_safekeeper2_1
5d949edd0cfa   neondatabase/neon:latest                           "/bin/sh -c 'safekee…"   46 minutes ago   Up 45 minutes      6400/tcp, 9898/tcp, <IP_ADDRESS>:7676->7676/tcp         docker-compose_safekeeper1_1
f896b7535c2c   neondatabase/neon:latest                           "/bin/sh -c 'safekee…"   46 minutes ago   Up 45 minutes      6400/tcp, 9898/tcp, <IP_ADDRESS>:7678->7676/tcp         docker-compose_safekeeper3_1
7321a496e8a0   quay.io/minio/minio:RELEASE.2022-10-20T00-55-09Z   "/usr/bin/docker-ent…"   47 minutes ago   Up 46 minutes      <IP_ADDRESS>:9000-9001->9000-9001/tcp                   docker-compose_minio_1
4a16732eb4fb   neondatabase/neon:latest                           "storage_broker --li…"   47 minutes ago   Up 46 minutes      6400/tcp, 9898/tcp, <IP_ADDRESS>:50051->50051/tcp       docker-compose_storage_broker_1

It contains the following nodes:

compute * 1
pageserver * 1
safekeeper * 3
storage_broker * 1
MinIO * 1 (S3)

I can connect to PostgreSQL running in compute:
psql -h localhost -p 55433 -U cloud_admin postgres

At the same time, I also run an autoscaling Kubernetes cluster started by kind, which contains a series of nodes. The function implemented in it is to run an elastically scalable postgres14-disk-test-cxkmw, which runs in a NeonVM, through the virtual The machine hot-swappable function realizes vertical elastic scaling, and realizes horizontal elastic scaling through virtual machine migration. But only postgresql nodes are running in this cluster, running in NeonVM.
# kubectl get pods --all-namespaces -o wide
NAMESPACE            NAME                                         READY   STATUS    RESTARTS      AGE     IP           NODE                 NOMINATED NODE   READINESS GATES
cert-manager         cert-manager-5b8f9b9d96-5924t                1/1     Running   1 (92m ago)   7h9m    <IP_ADDRESS>   kind-worker2         <none>           <none>
cert-manager         cert-manager-cainjector-54f68bfb64-ndg9z     1/1     Running   6 (92m ago)   7h9m    <IP_ADDRESS>   kind-worker2         <none>           <none>
cert-manager         cert-manager-webhook-f6c8487d6-c6zvb         1/1     Running   6 (92m ago)   7h9m    <IP_ADDRESS>   kind-worker2         <none>           <none>
default              postgres14-disk-test-cxkmw                   1/1     Running   0             79m     <IP_ADDRESS>   kind-worker          <none>           <none>
kube-system          autoscale-scheduler-6c7495dcb9-84gcb         1/1     Running   1 (92m ago)   6h12m   <IP_ADDRESS>   kind-worker          <none>           <none>
kube-system          autoscaler-agent-5kg2r                       1/1     Running   1 (92m ago)   6h12m   <IP_ADDRESS>   kind-worker2         <none>           <none>
kube-system          autoscaler-agent-86w9c                       1/1     Running   1 (92m ago)   6h12m   <IP_ADDRESS>   kind-worker          <none>           <none>
kube-system          coredns-565d847f94-rk8j2                     1/1     Running   1 (92m ago)   7h9m    <IP_ADDRESS>   kind-control-plane   <none>           <none>
kube-system          coredns-565d847f94-tvpr2                     1/1     Running   1 (92m ago)   7h9m    <IP_ADDRESS>   kind-control-plane   <none>           <none>
kube-system          etcd-kind-control-plane                      1/1     Running   0             82m     <IP_ADDRESS>   kind-control-plane   <none>           <none>
kube-system          kindnet-48v92                                1/1     Running   1 (92m ago)   7h9m    <IP_ADDRESS>   kind-worker2         <none>           <none>
kube-system          kindnet-6m6pr                                1/1     Running   1 (92m ago)   7h9m    <IP_ADDRESS>   kind-worker          <none>           <none>
kube-system          kindnet-xxrfw                                1/1     Running   1 (92m ago)   7h9m    <IP_ADDRESS>   kind-control-plane   <none>           <none>
kube-system          kube-apiserver-kind-control-plane            1/1     Running   0             82m     <IP_ADDRESS>   kind-control-plane   <none>           <none>
kube-system          kube-controller-manager-kind-control-plane   1/1     Running   1 (92m ago)   7h9m    <IP_ADDRESS>   kind-control-plane   <none>           <none>
kube-system          kube-multus-ds-4k9kh                         1/1     Running   1 (92m ago)   6h13m   <IP_ADDRESS>   kind-worker2         <none>           <none>
kube-system          kube-multus-ds-7jbdd                         1/1     Running   1 (92m ago)   6h13m   <IP_ADDRESS>   kind-worker          <none>           <none>
kube-system          kube-multus-ds-bfsvv                         1/1     Running   1 (92m ago)   6h13m   <IP_ADDRESS>   kind-control-plane   <none>           <none>
kube-system          kube-proxy-9wxnc                             1/1     Running   1 (92m ago)   7h9m    <IP_ADDRESS>   kind-worker          <none>           <none>
kube-system          kube-proxy-dmkpk                             1/1     Running   1 (92m ago)   7h9m    <IP_ADDRESS>   kind-worker2         <none>           <none>
kube-system          kube-proxy-t7m95                             1/1     Running   1 (92m ago)   7h9m    <IP_ADDRESS>   kind-control-plane   <none>           <none>
kube-system          kube-scheduler-kind-control-plane            1/1     Running   1 (92m ago)   7h9m    <IP_ADDRESS>   kind-control-plane   <none>           <none>
kube-system          metrics-server-6644dbd5f9-gvsx6              1/1     Running   4 (92m ago)   7h8m    <IP_ADDRESS>   kind-worker          <none>           <none>
kube-system          whereabouts-gtwsn                            1/1     Running   1 (92m ago)   6h13m   <IP_ADDRESS>   kind-worker2         <none>           <none>
kube-system          whereabouts-psk4z                            1/1     Running   1 (92m ago)   6h13m   <IP_ADDRESS>   kind-worker          <none>           <none>
kube-system          whereabouts-qqx8g                            1/1     Running   1 (92m ago)   6h13m   <IP_ADDRESS>   kind-control-plane   <none>           <none>
local-path-storage   local-path-provisioner-7cf55d6b5d-wddfl      1/1     Running   4 (92m ago)   7h9m    <IP_ADDRESS>   kind-control-plane   <none>           <none>
neonvm-system        neonvm-controller-669c6f4c7-wst6d            2/2     Running   2 (92m ago)   6h12m   <IP_ADDRESS>   kind-worker2         <none>           <none>
neonvm-system        neonvm-device-plugin-5swjx                   1/1     Running   1 (92m ago)   6h12m   <IP_ADDRESS>   kind-worker          <none>           <none>
neonvm-system        neonvm-device-plugin-nvwhj                   1/1     Running   1 (92m ago)   6h12m   <IP_ADDRESS>   kind-worker2         <none>           <none>
neonvm-system        neonvm-device-plugin-vgsgv                   1/1     Running   1 (92m ago)   6h12m   <IP_ADDRESS>   kind-control-plane   <none>           <none>
neonvm-system        neonvm-vxlan-controller-cpq7t                1/1     Running   5 (81m ago)   6h12m   <IP_ADDRESS>   kind-control-plane   <none>           <none>
neonvm-system        neonvm-vxlan-controller-k9cmx                1/1     Running   5 (80m ago)   6h12m   <IP_ADDRESS>   kind-worker2         <none>           <none>
neonvm-system        neonvm-vxlan-controller-zfnbj                1/1     Running   5 (80m ago)   6h12m   <IP_ADDRESS>   kind-worker          <none>           <none>

How can I use the PostgreSQL node in Kubernetes as the computing node of the cluster, and use other storage layer nodes deployed by docker-compose as the storage node of the cluster?
Is there any relevant documentation that can help me?
Thanks~!

You should be able to create tenants using the HTTP control plane APIs and then you may access the database (see control_plane). For local developments, we recommend using the cargo neon utility instead of deploying everything by yourself.

@skyzh thanks for your help. I tried deploying with cargo neon. But the main problem I want to solve now is: how to configure the network topology so that the PostgreSQL nodes deployed in K8s can interact with the storage layer nodes (safekeeper, pageserver, minio) of cargo neon / docker-compose? Do I have to do service discovery manually? Is there any relevant case for my reference?

Is there any solution for neondata in kubernetes? Any helm chart any operator?

https://github.com/neondatabase/helm-charts?

@skyzh Thank you so much. This work is amazing.
At present, helm-charts does not seem to support the deployment of Safekeeper and Pageserver? Are there plans to support it in the future?

I don't think it's on the roadmap because we currently scale them manually.

Even scaling is manual but it will be helpful to install them via charts. Otherwise the instructions of manual + helm is going to be tough to understand.

Something in my mind is telling me I should start and create a chart myself. :^)


[BUG] - It is possible to get a UTxO stuck inside a contract due to the protocol parameters.

Internal/External
External   otherwise.
Area
Plutus    Related to Plutus Scripts (Alonzo).
Summary
It is possible to lock an UTxO into a smart contract until the protocol parameters change. The UTxO in question is large enough to send, i.e. below max tx size, but it can not be spent from a smart contract.
The error:
Command failed: transaction submit  Error: Error while submitting tx:
ShelleyTxValidationError ShelleyBasedEraAlonzo (ApplyTxError [
UtxowFailure (WrappedShelleyEraFailure (UtxoFailure (ExUnitsTooBigUTxO (
ExUnits {exUnitsMem = 10000000, exUnitsSteps =<PHONE_NUMBER>0})
(ExUnits {exUnitsMem = 11578150, exUnitsSteps =<PHONE_NUMBER>}))))])

The resulting UTxO is stuck until the protocol parameters are changed specifically:
"maxTxExecutionUnits": {
        "memory": 100000000,
        "steps":<PHONE_NUMBER>0
    },

As you can see in the error message the max memory units need to be increased to be able to spend this UTxO. The required mem unit is 11578150 and the max mem unit is 10000000.
This can happen to every smart contract and can not be known before validation. As of right now, it is possible to lock an UTxO inside any smart contract because there are too many NFTs / FTs on that UTxO.
From my test cases, it seems to occur with many policies, 20+, as I can spend 150+ NFTs from a single or few policy IDs.
Transaction information
Steps to reproduce
Steps to reproduce the behavior:

Compile any smart contract that can successfully validate a UTxO.
Mint 150+ Assets on 20+ different policies.
Send all 150+ assets into the smart contract with a known datum so it can be spent.
Attempt to spend the UTxO and view error.

Expected behavior
A UTxO that is below max tx size that can be sent into a contract should be able to be validated with the contract without a memory error.
System info (please complete the following information):

Ubuntu
20.04
cardano-cli 1.30.1 - linux-x86_64 - ghc-8.10
git rev 0fb43f4e3da8b225f4f86557aed90a183981a64f
cardano-node 1.30.1 - linux-x86_64 - ghc-8.10
git rev 0fb43f4e3da8b225f4f86557aed90a183981a64f

I can provide any additional details. This is my first bug report and I am a noob at it.

What's the whole uTXo look like?
I remember sending an NFT to my delegator have paying hell for it. I finally sent it off to a wallet though

a64d50155e2f46b303ada058e759f079a303b471360cfee012e3b30bbc209498     1        15955396 lovelace + 1 139e8d9190cd5a1213345a0099bedaa3ecf940b3e7675f4350e979da.Testing01 + 1 139e8d9190cd5a1213345a0099bedaa3ecf940b3e7675f4350e979da.Testing02 + 1 139e8d9190cd5a1213345a0099bedaa3ecf940b3e7675f4350e979da.Testing03 + 1 22935a6d855877721037306ce7a484d8e0c7e4220973d8cdb3dd4ddf.Testing01 + 1 22935a6d855877721037306ce7a484d8e0c7e4220973d8cdb3dd4ddf.Testing02 + 1 22935a6d855877721037306ce7a484d8e0c7e4220973d8cdb3dd4ddf.Testing03 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing01 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing02 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing03 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing04 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing05 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing06 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing07 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing08 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing09 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing10 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing11 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing12 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing13 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing14 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing15 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing16 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing17 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing18 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing19 + 1 257cd3b8b8883df0f0e0c676454099f250cae60d135743c69712dba4.Testing20 + 1 269a80b34d53654c78451a625f94198b59eef148c43d66acd35b5c1d.Testing01 + 1 269a80b34d53654c78451a625f94198b59eef148c43d66acd35b5c1d.Testing02 + 1 269a80b34d53654c78451a625f94198b59eef148c43d66acd35b5c1d.Testing03 + 1 269a80b34d53654c78451a625f94198b59eef148c43d66acd35b5c1d.Testing04 + 1 269a80b34d53654c78451a625f94198b59eef148c43d66acd35b5c1d.Testing05 + 1 26fcf86cc19e48ff4d6e1014c17cdee46c69763b68eb6e70b2b0ce09.Testing01 + 1 26fcf86cc19e48ff4d6e1014c17cdee46c69763b68eb6e70b2b0ce09.Testing02 + 1 26fcf86cc19e48ff4d6e1014c17cdee46c69763b68eb6e70b2b0ce09.Testing03 + 1 26fcf86cc19e48ff4d6e1014c17cdee46c69763b68eb6e70b2b0ce09.Testing04 + 1 26fcf86cc19e48ff4d6e1014c17cdee46c69763b68eb6e70b2b0ce09.Testing05 + 1 26fcf86cc19e48ff4d6e1014c17cdee46c69763b68eb6e70b2b0ce09.Testing06 + 1 26fcf86cc19e48ff4d6e1014c17cdee46c69763b68eb6e70b2b0ce09.Testing07 + 1 26fcf86cc19e48ff4d6e1014c17cdee46c69763b68eb6e70b2b0ce09.Testing08 + 1 26fcf86cc19e48ff4d6e1014c17cdee46c69763b68eb6e70b2b0ce09.Testing09 + 1 26fcf86cc19e48ff4d6e1014c17cdee46c69763b68eb6e70b2b0ce09.Testing10 + 1 27866b0bfb89cdbc54ee03ae42ba97b3a6c64969a1e61bc7c4a7e791.Testing01 + 1 27866b0bfb89cdbc54ee03ae42ba97b3a6c64969a1e61bc7c4a7e791.Testing02 + 1 27866b0bfb89cdbc54ee03ae42ba97b3a6c64969a1e61bc7c4a7e791.Testing03 + 1 28c69c3b549aa53363102ce63ef4d8ff1cfd835b900a49cc6803fbb8.Testing01 + 1 28c69c3b549aa53363102ce63ef4d8ff1cfd835b900a49cc6803fbb8.Testing02 + 1 28c69c3b549aa53363102ce63ef4d8ff1cfd835b900a49cc6803fbb8.Testing03 + 1 3e0103ea0886a4d5132d9326c1e7160d164f1dd320588d1dd364a289.Testing01 + 1 3e0103ea0886a4d5132d9326c1e7160d164f1dd320588d1dd364a289.Testing02 + 1 3e0103ea0886a4d5132d9326c1e7160d164f1dd320588d1dd364a289.Testing03 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing01 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing02 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing03 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing04 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing05 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing06 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing07 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing08 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing09 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing10 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing11 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing12 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing13 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing14 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing15 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing16 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing17 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing18 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing19 + 1 3fb9a380aeff00d0011ba24fed0f1d3489472ff90101347ce4dda0f2.Testing20 + 1 4967733d1e32e8298a31c9cefb9e5a7453c137fdcbee82ede7e4aade.Testing01 + 1 4967733d1e32e8298a31c9cefb9e5a7453c137fdcbee82ede7e4aade.Testing02 + 1 4967733d1e32e8298a31c9cefb9e5a7453c137fdcbee82ede7e4aade.Testing03 + 1 4a8cd34868088b2077315f51a0e398bd65bde1053b2f810b48768a90.Testing01 + 1 4a8cd34868088b2077315f51a0e398bd65bde1053b2f810b48768a90.Testing02 + 1 4a8cd34868088b2077315f51a0e398bd65bde1053b2f810b48768a90.Testing03 + 1 4a8cd34868088b2077315f51a0e398bd65bde1053b2f810b48768a90.Testing04 + 1 4a8cd34868088b2077315f51a0e398bd65bde1053b2f810b48768a90.Testing05 + 1 4a8cd34868088b2077315f51a0e398bd65bde1053b2f810b48768a90.Testing06 + 1 4a8cd34868088b2077315f51a0e398bd65bde1053b2f810b48768a90.Testing07 + 1 4a8cd34868088b2077315f51a0e398bd65bde1053b2f810b48768a90.Testing08 + 1 4a8cd34868088b2077315f51a0e398bd65bde1053b2f810b48768a90.Testing09 + 1 4a8cd34868088b2077315f51a0e398bd65bde1053b2f810b48768a90.Testing10 + 1 71b3aee548f59de27de520bc5dc2678da47f17dcebdbddb15c9944d0.Testing01 + 1 71b3aee548f59de27de520bc5dc2678da47f17dcebdbddb15c9944d0.Testing02 + 1 71b3aee548f59de27de520bc5dc2678da47f17dcebdbddb15c9944d0.Testing03 + 1 765e0e7ef5d451f33370aa596b3c7155c7bbc6a59db39d4220a92e66.Testing01 + 1 765e0e7ef5d451f33370aa596b3c7155c7bbc6a59db39d4220a92e66.Testing02 + 1 765e0e7ef5d451f33370aa596b3c7155c7bbc6a59db39d4220a92e66.Testing03 + 1<PHONE_NUMBER>1ab3cfef4402b5e48ba03ebdd248d0afffea68e23e04b3.Testing01 + 1<PHONE_NUMBER>1ab3cfef4402b5e48ba03ebdd248d0afffea68e23e04b3.Testing02 + 1<PHONE_NUMBER>1ab3cfef4402b5e48ba03ebdd248d0afffea68e23e04b3.Testing03 + 1<PHONE_NUMBER>1ab3cfef4402b5e48ba03ebdd248d0afffea68e23e04b3.Testing04 + 1<PHONE_NUMBER>1ab3cfef4402b5e48ba03ebdd248d0afffea68e23e04b3.Testing05 + 1 79dbf44bf8b1631097f9c395fae95d5128a5801e852eb33c16995ed0.Testing01 + 1 79dbf44bf8b1631097f9c395fae95d5128a5801e852eb33c16995ed0.Testing02 + 1 79dbf44bf8b1631097f9c395fae95d5128a5801e852eb33c16995ed0.Testing03 + 1 c51d3f1e0e53c060e64705bc50710159a52fc410b995250218aeadca.Testing01 + 1 c51d3f1e0e53c060e64705bc50710159a52fc410b995250218aeadca.Testing02 + 1 c51d3f1e0e53c060e64705bc50710159a52fc410b995250218aeadca.Testing03 + 1 db96d1a3a590119858bb996bf4f2e1edfb4bcda9b032d10a33662839.Testing01 + 1 db96d1a3a590119858bb996bf4f2e1edfb4bcda9b032d10a33662839.Testing02 + 1 db96d1a3a590119858bb996bf4f2e1edfb4bcda9b032d10a33662839.Testing03 + 1 db96d1a3a590119858bb996bf4f2e1edfb4bcda9b032d10a33662839.Testing04 + 1 db96d1a3a590119858bb996bf4f2e1edfb4bcda9b032d10a33662839.Testing05 + 1 db96d1a3a590119858bb996bf4f2e1edfb4bcda9b032d10a33662839.Testing06 + 1 db96d1a3a590119858bb996bf4f2e1edfb4bcda9b032d10a33662839.Testing07 + 1 db96d1a3a590119858bb996bf4f2e1edfb4bcda9b032d10a33662839.Testing08 + 1 db96d1a3a590119858bb996bf4f2e1edfb4bcda9b032d10a33662839.Testing09 + 1 db96d1a3a590119858bb996bf4f2e1edfb4bcda9b032d10a33662839.Testing10 + 1 dd6d1bf0fb7b267d5e2c35c298f3d7ba2e35c70dd25059dd3f2d6a85.Testing01 + 1 dd6d1bf0fb7b267d5e2c35c298f3d7ba2e35c70dd25059dd3f2d6a85.Testing02 + 1 dd6d1bf0fb7b267d5e2c35c298f3d7ba2e35c70dd25059dd3f2d6a85.Testing03 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing01 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing02 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing03 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing04 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing05 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing06 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing07 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing08 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing09 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing10 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing11 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing12 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing13 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing14 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing15 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing16 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing17 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing18 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing19 + 1 eaf3abad909f4931b74e0e5219d6a26bb3658d39fb5380ef168aec7e.Testing20 + 1 efd3173f8e7fb93af37641794b9634f140d562607619264fa89ca4e4.Testing01 + 1 efd3173f8e7fb93af37641794b9634f140d562607619264fa89ca4e4.Testing02 + 1 efd3173f8e7fb93af37641794b9634f140d562607619264fa89ca4e4.Testing03 + 1 efd3173f8e7fb93af37641794b9634f140d562607619264fa89ca4e4.Testing04 + 1 efd3173f8e7fb93af37641794b9634f140d562607619264fa89ca4e4.Testing05 + 1 efd3173f8e7fb93af37641794b9634f140d562607619264fa89ca4e4.Testing06 + 1 efd3173f8e7fb93af37641794b9634f140d562607619264fa89ca4e4.Testing07 + 1 efd3173f8e7fb93af37641794b9634f140d562607619264fa89ca4e4.Testing08 + 1 efd3173f8e7fb93af37641794b9634f140d562607619264fa89ca4e4.Testing09 + 1 efd3173f8e7fb93af37641794b9634f140d562607619264fa89ca4e4.Testing10 + 1 f6f6284e6813125424d4f571293bee92f13c407f4f208c1dd98d6127.Testing01 + 1 f6f6284e6813125424d4f571293bee92f13c407f4f208c1dd98d6127.Testing02 + 1 f6f6284e6813125424d4f571293bee92f13c407f4f208c1dd98d6127.Testing03 + 1 f6f6284e6813125424d4f571293bee92f13c407f4f208c1dd98d6127.Testing04 + 1 f6f6284e6813125424d4f571293bee92f13c407f4f208c1dd98d6127.Testing05 + 1 f6f6284e6813125424d4f571293bee92f13c407f4f208c1dd98d6127.Testing06 + 1 f6f6284e6813125424d4f571293bee92f13c407f4f208c1dd98d6127.Testing07 + 1 f6f6284e6813125424d4f571293bee92f13c407f4f208c1dd98d6127.Testing08 + 1 f6f6284e6813125424d4f571293bee92f13c407f4f208c1dd98d6127.Testing09 + 1 f6f6284e6813125424d4f571293bee92f13c407f4f208c1dd98d6127.Testing10 + TxOutDatumHash ScriptDataInAlonzoEra "5c290df1e9a743eee0ab8e8a2679e64f079db762352d0df2f36fd9ed24236800"

I am running an additional test to define the unique policy verse the unique asset boundary. I will update the thread with an image tomorrow.

Right, why isn't it checking to see if the UTxO will be out of bounds with the network parameters? When shuold that even happen, would it be possible to check if you will exceed maxTxExecutionUnits.memorry or maxTxExecutionUnits.steps like we can with predicting the fee?
Should that be up to the user to check or the transaction builders? Has anything actually gone wrong here, or is it the pace of the wallets to keep up?
Is it really a bug (I didn't read over the UTxO application theory) or should you be allowed to pack a UTxO like that , and let the network reclaim later on when it forces compliance by having the work broken up into smaller chunks to collect fees for its effort by requiring more transactions?
I don't know if this is a bug or a feature about UTxOs... super interesting to see!
You can get "unstuck" now by selectively sending a chunk of TXs, in whatever means makes sense for you, maybe selectively moving asset Testing0{n+1}, (where n=0), version out until you can do the large spend if that's what you desire.
I'm afraid that's all I can help you with if you need it.
I think this raises a question that  deserves an authoritative answer about whether this is a bug or a feature of the UTxO's seeming ability to offset cost to exist by being allowed to grow into a size that can be paid for later, perhaps by the single TX owners? Where does inspecting each Tx in the UTxO lay? If we just let the network remain fast and responsive by limiting UTxO size, maybe you can look at this as some kind of compression, that is perfectly legal in terms of the UTxO model, and its constraints, which allow it to be so versatile and compact, that it requires a size constraint to prevent attacks on the network, or individuals?
So should the network parameters be changed, or should users have to work within them? They each have consequences, one on ammeter user performance and the latter on overall performance.

On the vertical axis is the number of unique policy id and the horizontal is the number of unique assets. There exist a region where a UTxO can be spent and a region where it can not be spent.

Right, why isn't it checking to see if the UTxO will be out of bounds with the network parameters? When shuold that even happen, would it be possible to check if you will exceed maxTxExecutionUnits.memorry or maxTxExecutionUnits.steps like we can with predicting the fee?

That check only happens when spending a UTxO inside a smart contract not sending an UTxO into a smart contract. Validation only occurs at a singular point.

I don't know if this is a bug or a feature about UTxOs... super interesting to see!

This is a bug for sure. Any sendable UTxO should be able to be validated.

You can get "unstuck" now by selectively sending a chunk of TXs, in whatever means makes sense for you, maybe selectively moving asset Testing0{n+1}, (where n=0), version out until you can do the large spend if that's what you desire.

I think that it would have popped up immediately in automated testing or manual testing. You probably discovered a feature of why UTxO's have special abilities that at the moment look like immediate cost savings given. Yeah, we just have to read up on power of the UTxO model.

Depending on how they did this test. From my graph it is highly dependent upon which region they were testing in the policy verse asset parameter space. If the test was only concerned with low policy high assets then it would have worked.

Thank you for the insights. Surprised that can can't reduce the number of UTxOs... I was wrong about being able to help you. I hope you can get some eyes on this if it's that easy to vanish your ADA.

Thank you for the insights. Surprised that can can't reduce the number of UTxOs... I was wrong about being able to help you. I hope you can get some eyes on this if it's that easy to vanish your ADA.

Oh yeah, this is a huge issue if any DEX has any liquidity pools as large UTxOs it basically means that their DEX will freeze at some point, locking in the funds. Any NFT marketplace must have hard bounds on bundle sales. The only way to spend it is if IOG does an HFC event and increases the max mem units parameter.

If a Tx is sendable then it ought to be spendable. The only solution here is increasing maxTxExecutionUnits.memory parameter in the protocol parameters for the blockchain.
"maxTxExecutionUnits": {
        "memory": 100000000,
        "steps":<PHONE_NUMBER>0
    },

Okay, but let's hope not.

I don't think this is a bug, it is just unfortunate.
There was to be some way to prevent malicious or problematic scripts from using up all of a validators memory.
However, I think this hard limit vs a mechanism that requires higher fees is probably suboptimal because you can't pay to free locked expensive assets.

Are his assets really frozen on the blockchain without a protocol change? I am still confused about that.

Are his assets really frozen on the blockchain unless a protocol change or faux code smell bounty payout happens? I am still confused about that.

Yep completely frozen.
Look at the graph I provided. I found this because of sending 150 assets into a contract but this bug can be found by just sending 65 assets from 65 different policies into a smart contract. That UTxO will be stuck inside a contract. The UTxO maxes out the maxTxExecutionUnits.memory parameter. That parameter has to be increased for this UTxO to be spent.

I don't think this is a bug, it is just unfortunate.
There was to be some way to prevent malicious or problematic scripts from using up all of a validators memory.

If a transaction is sendable, it should be spendable. This is a bug.
It happens even with the alwayssucceed.hs contract from alonzo testnet and all that does it pass a True bool.
What malicious attack comes from passing a True value? How is sending a UTxO that is less than half the max UTxO size problematic?
This is extremely limiting in terms of what can be done with bundles of tokens and what an UTxO can represent. As of right now every NFT market has to cap bundle sales around 50 tokens.
If an UTxO represented a movie, royalties, the ownership of something, etc, where it was a bundle of tokens from unique policies then it is maxed out around 50 tokens. Kind of a joke in terms of what can be done with these contracts.

If a transaction is sendable, it should be spendable. This is a bug.

How would this be possible if the validator loops forever?
I think the current behavior is suboptimal. It should be easier to free these assets by paying more, but I think this will always be able to happen to some degree.

How would this be possible if the validator loops forever?

That would max out the maxTxExecutionUnits.steps I believe.
This is about having enough memory to store policy and asset name data.

That would max out the maxTxExecutionUnits.steps I believe.

Depends on the loop what it would max out first, memory or cpu.

That would max out the maxTxExecutionUnits.steps I believe.

Depends on the loop what it would max out first, memory or cpu.

Does it make sense to just increase the memory parameter to allow a max tx size to be spendable by the simplest contract possible?
It would still prevent infinite loops but allow a larger range of use cases of spendability.

Increase one but decrease the others, until there's a net zero effect. Memory's cheap, time isn't.

Does it make sense to just increase the memory parameter to allow a max tx size to be spendable by the simplest contract possible?

Probably. I have no idea why that specific memory limit was chosen. Since it is a nice simple number I assume it was arbitrary.

An arbitrary number that is too low and can not be changed without an HFC event. I wish we could just vote on this parameter and not have to wait on a centralized source to change it.

This is insane. We had a similar issue at https://www.jpg.store/collection/unsigned_algorithms where users had listed these NFTs at our script address, and were temporarily unable to get them out. Fortunately, these NFT's aren't above the memory limit, but they store so much data on chain that we had to increase our ExUnits for buy/unlist transactions for them to validate.

I am quoting George of APEX here, so while it's kind of hearsay, I thought you'd be happy to hear this:

Following extensive benchmarking, and developer feedback, we’re now starting to make gradual adjustments and have today submitted two initial changes.These changes are planned to take effect on the testnet on Thursday 25th November. Once tested, we anticipate subsequently applying these to the mainnet, taking effect on epoch 306, on Wednesday December 1, 2021 at 21:45:00 UTC.

I am quoting George of APEX here, so while it's kind of hearsay, I thought you'd be happy to hear this:

Following extensive benchmarking, and developer feedback, we’re now starting to make gradual adjustments and have today submitted two initial changes.These changes are planned to take effect on the testnet on Thursday 25th November. Once tested, we anticipate subsequently applying these to the mainnet, taking effect on epoch 306, on Wednesday December 1, 2021 at 21:45:00 UTC.

Yeah, I saw this too. It is a great step in the right direction but it will still leave many UTxOs stuck inside smart contracts. The increase from 10 M to 11.25 M is still not enough to unlock my case that is near 11.88 M. What it unlocks is the boundary between working and not working in the graph I made previously.

I recently saw a user hit the limits with as few as 8 --tx-in's on Stack Exchange 🤯 https://cardano.stackexchange.com/questions/6064/transaction-memory-and-cpu-usage-limits/6068#6068
I have a few suggestions for next steps here, knowing practically nothing about how this stuff works :P

Can we remove these limits entirely? Is there any reason why a user can't just pay more to execute a tx with higher mem/CPU requirements?

If 1) isn't possible, what is the reason for keeping the limits as low as they are currently?

Are there any efforts to optimize the Plutus compiler here? Surely adding a few more --tx-in's shouldn't blow up memory like this?

Closing this. If this is still relevant please reopen.

Go ahead and close this but it is still relevant. The memory parameter is extremely limiting and now all my contracts have to go through a stuck UTxO test to find where the limit is set for that contract. Imho even if the parameter increased by an order of magnitude this issue would still be relevant. There is no way to know when it will get stuck until it's already inside the contract.

Definitely still relevant. I've just unknowingly locked 220 fairly valuable assets in a contract with no way of retrieving them because it requires too many Execution units. RIP my 20k Ada


Question about CoVaR computation

Hi Tommaso,
Thanks for the amazing works, the toolbox is quite useful！
And I‘m really confused about the output of CROSS-SECTIONAL MEASURES. CoVaR computation requires the coefficients estimates through quantile regression, b = quantile_regression(y,x,a), how to get the estimation results of the coefficient "b"?
Best regards,
Guo

Hi @Liyang-Guo, sorry for the belated reply.
Please, take a look at: https://github.com/TommasoBelluzzo/SystemicRisk/blob/013aa57eecb902638814810570f86a8e51833d70/ScriptsModels/cross_sectional_metrics.m#L140


feat: make startup image configurable in settings.lua.

#1122

The doc in the comment seems still missing at: https://github.com/ayamir/nvimdots/wiki/Issues#change-dashboard-startup-image


Add Media Key Support

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Checked that your issue isn't already filed: https://github.com/GetStream/Winds/issues

Description
Would be fantastic to be able to play / pause podcasts with media keys
Steps to Reproduce

Open Winds
Play a Podcast
Keyboard play / pause to control audio

Expected behavior: Play or pause audio
Actual behavior: Nothing (YET)
Reproduces how often: 100%
Versions
Version 2.0.211 (2.0.211)

i really like this idea. should be pretty easy as well.

Would anyone from the community like to make this contribution? We'll send you an awesome Stream t-shirt!

Me, i'm working on this issue, I'll soon submit a PR.

Awesome :)
On Sun, May 27, 2018, 18:35 Leonardo Villela<EMAIL_ADDRESS>wrote:

Me, i'm working on this issue, I'll soon submit a PR.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GetStream/Winds/issues/290#issuecomment-392391790,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQMweL3hu-DZ_ktU-LHFB5iptzbFKN6ks5t20Y3gaJpZM4UK43J
.

@leonardovillela Hey! How's the PR coming along? Feel free to reach out if you have any questions about the codebase.

This feature has been added to v2.1! 🎉


Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

[X] I have checked for that this module doesn't already exist in the module indexes; or I'm proposing the module to be migrated from CARML/TFVM.

Bicep or Terraform?
Terraform
Module Classification?
Resource Module
Module Name
avm-res-batch-batchaccount
Module Details
AVM resource module for Batch Account
Do you want to be the owner of this module?
No
Module Owner's GitHub Username (handle)
No response
(Optional) Secondary Module Owner's GitHub Username (handle)
No response

Hi @bsantacruzms,
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what module ownership means:

Team Definitions & RACI
Shared Specification (Bicep & Terraform)
Module Support

Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
#RR

I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER

Hi @bsantacruzms,
Thanks for confirming that you wish to own this AVM module and understand the related requirements and responsibilities!
We just want to ask you to double check a few important things.
Please use the following values explicitly as provided in the module index page:

You must be the owner of the GitHub teams as outlined here.
Please check that your name has been updated in the module index page (this should happen shortly after you confirmed ownership).

You can now take ownership of this module and start improving it as needed! ✅ Happy coding! 🎉
Any further questions or clarifications needed, let us know!
Thanks,
The AVM Core Team

Reached out to @bsantacruzms to share an update here.

Closing as @bsantacruzms won't be proceeding forward on this for now and will re-open later as and when needed.

Closing as @bsantacruzms won't be proceeding forward on this for now and will re-open later as and when needed.

I am interested in taking ownership of this one

I am interested in taking ownership of this one

Requesting @prjelesi to advise on next steps

Hi @ethanjenkins1 ,
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what module ownership means:

Team Definitions & RACI
Shared Specification (Bicep & Terraform)
Module Support

Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
#RR

@ethanjenkins1 can you please respond?

I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER

Hi @ethanjenkins1 ,
Thanks for confirming that you wish to own this AVM module and understand the related requirements and responsibilities!
Before starting development, please ensure ALL the following requirements are met.
Please use the following values explicitly as provided in the module index page:

For your module:

ModuleName - for naming your module
TelemetryIdPrefix - for your module's telemetry

For your module's repository:

Repo name and folder path are defined in RepoURL
Create GitHub teams for module owners and contributors and grant them permissions as outlined here.
Grant permissions for the AVM core team and PG teams on your GitHub repo as described here.

Check if this module exists in the other IaC language. If so, collaborate with the other owner for consistency. 👍
You can now start the development of this module! ✅ Happy coding! 🎉
Please respond to this comment and request a review from the AVM core team once your module is ready to be published! Please include a link pointing to your PR, once available. 🙏
Any further questions or clarifications needed, let us know!
Thanks,
The AVM Core Team

Module is ready to be published but not sure on the next steps.

@ethanjenkins1 - We will put this under review and let you know the feedback.

I am still waiting on approval from legal

@PmeshramPM I am still pending legal review, is there a way to get action on this item?

@ethanjenkins1 - Reaching out to you in chat

Still pending legal review, they are trying to find someone in my org for the approval. I will be on DTO June 28th-July 12th


mode option to combine my module annotation or project

add mergeModulesMergeMode option to set mode module to combine modules by @module annotation.
it means you can set same @module name and all reflections will be combined by its declaration rather than project root
src/
├── index.ts         @module main
├── module1
│   └── index.ts     @module submodule
├── module2
│   └── index.ts     @module submodule
├── module3.ts       @module main
└── module4
    └── module4-1
        └── index.ts @module main

this goes ⬇

I made this pull request because I need this feature and feel typedoc-plugin-merge-modules  matches to this idea.
However I will understand this may be out of this plugins concept. I that case I will make this as a other plugin.

Osu. It very much makes sense to me to include such a functionality in this plugin. I haven't used the @module annotation yet. I'll probably have time later this week to take a look.

The code basically looks fine to me. I merged it into a feature branch and I will test it in the next days. I'll keep you posted.

I'm ready to publish a new release including your changes. Do you want to be mentioned in the credits section (Github, NPM)?

@krisztianb
Thank you so much for your work.
If you credit my name, @beijaflor is nice to me ( @sho-otani-icare is my current work account ).
Anyway I'm looking forward to new release and we'll use our current product ;)

I've just released version 2.1.0 including your contribution. Should you find any bugs, please report them in the issues section here on Github. Thank you.

@krisztianb
Just for F.Y.I.. I made example repository for my Japanese tach blog.
https://github.com/beijaflor/typedoc-plugin-merge-modules-example

To be honest I'm amazed about how many people are using this plugin. I created it, because I needed the "old" TypeDoc behaviour for one of my projects. Looks like a lot of other people are having the same issue.


Data returned by websocket is inconsistent with the data returned by request

longhorn ui
On volume details page:

"Recurring Snapshot and Backup Schedule" section:

Click Edit > Click New > Click Save > Click Edit > Click New > Click Save > Cycle

This bug appears randomly,The main reason is that websocket’s data is older than what’s in the request sometime.
The request address is /v1/volumes
The ws address is /v1/ws/1s/volumes

https://github.com/longhorn/longhorn-manager/pull/368 has added timestamp fields in the various resource and it should help the caller to know which status can be dropped if needed.

@smallteeths ^^

Done. Feel free to reopen if it happens again.


On UNIX systems try to store kernels in tmp dir

This change adds a new compiler definition HAVE_UNIX and uses P_tmpdir to store
the kernel files in a temporary location rather than the current working
directory.
There are two reasons why I think this would be a good addition: 1) it doesn't clutter my current working directory and 2) I cannot always write in my current working directory.

Cleaning house; closing pull request as a compromise wasn't reached.


Support filter combined with: userid + timeline

Currenty the filter just support timeline for normal map (without any filter), now need to support this case:
/?userid=1&timeline_start=xxx&timeline_end=xxx

The timeline related code is here:
https://github.com/Greenstand/node-mapnik-1/blob/c9d6fde8870a87392c5a98352c07bec440bac522/greenstand/sqls/SQLCase1Timeline.js#L31-L39


non nullable Shadow properties as Keys and Navigation property evaluates the PK before shadow props are set

The following is a trimmed down version of the issue I am seeing.
I am trying to push as much of the Data layer out of my model code and experience the following error when I use a non-nullable type as both a navigation key and PK.
The issue goes away as soon as I switch to a nullable type.
Exception message: Unable to track an entity of type 'b' because primary key property 'code' is null.
Stack trace:
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.NullableKeyIdentityMap`1.Add(InternalEntityEntry entry)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.StateManager.StartTracking(InternalEntityEntry entry)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.InternalEntityEntry.SetEntityState(EntityState oldState, EntityState newState, Boolean acceptChanges)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.InternalEntityEntry.SetEntityState(EntityState entityState, Boolean acceptChanges, Boolean forceStateWhenUnknownKey)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.EntityGraphAttacher.PaintAction(EntityEntryGraphNode node)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.EntityEntryGraphIterator.TraverseGraph(EntityEntryGraphNode node, Func`2 handleNode)
   at Microsoft.EntityFrameworkCore.ChangeTracking.Internal.EntityGraphAttacher.AttachGraph(InternalEntityEntry rootEntry, EntityState entityState, Boolean forceStateWhenUnknownKey)
   at Microsoft.EntityFrameworkCore.DbContext.SetEntityState(InternalEntityEntry entry, EntityState entityState)
   at Microsoft.EntityFrameworkCore.DbContext.SetEntityState[TEntity](TEntity entity, EntityState entityState)
   at Microsoft.EntityFrameworkCore.DbContext.Add[TEntity](TEntity entity)
   at ConsoleApp1.Program.Main(String[] args) in <redacted>Program.cs:line 12

Steps to reproduce
using Microsoft.EntityFrameworkCore;

namespace ConsoleApp1
{
    class Program
    {
        static void Main(string[] args)
        {
            var model = new b() { a = new a() { code = false}};
            using (var db = new Data())
            {
                db.Add(model);
            }
        }
        private class Data : DbContext
        {
            protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder) => optionsBuilder.UseInMemoryDatabase("test");

            protected override void OnModelCreating(ModelBuilder modelBuilder)
            {
                modelBuilder.Entity<a>().HasKey(a => new { a.code });
                modelBuilder.Entity<b>().HasOne(ab => ab.a).WithMany().HasForeignKey(nameof(a.code));
                modelBuilder.Entity<b>().HasKey(nameof(a.code));
            }
        }
        private class a
        {
           public bool code { get; set; }
        }
        private class b
        {
            public a a { get; set; }
        }
    }
}

Further technical details
EF Core version: 2.0.0
Database Provider: N/A
Operating system: Windows 10
IDE: Visual Studio 2017

@Tarig0 I am only able to reproduce this with bool keys, which are not common. Have you also seen this for other key types, such as ints or strings? If you have, can you update the repro code to use something other than a bool key?

The bit/bool is part of a composite key. I am able to function with "bool?"  Type. I will check with other types. But my guess is that I just found the outlier.

This appears to only effect the bool type. For my case the this is an isFlag that is part of the PK, so doesn't make sense for me to be required to change my model code.
As stated before I can get around this by switching to the nullable type, which has some advantages for model validation, and the error goes away.

Note for triage: On further investigation I think this is by-design. The code is adding a new entity (in this case a dependent in an FK-to-FK relationship) that is not using a generated key without setting the generated key value to anything. This is not supported. The reason the same code works for integer keys is that these are generated by convention. This means we are able to generate a temporary value to use for the key, which is later replaced by the propagated vale from the principal end.
There exists now some logic used by the change detector that could potentially allow us to support this case by deferring the tracking of the dependent until the principal has been tracked. However, I don't think we should try to do this for 2.1--this is an area where its easy for special cases to make a mess, so I think we need more bake time before enhancing the code in this way.

This code sample no longer throws an error.


Uncaught Exception: Command failed:<PHONE_NUMBER>

An uncaught exception was reported.
Info:
OS: win32
Arch: ia32
GPMDP Version: 3.0.0
Time: Thu Mar 10 2016 19:40:11 GMT-0800 (Pacific Standard Time)
Error:
Command failed:<PHONE_NUMBER>
Error: Command failed:<PHONE_NUMBER>
System.AggregateException: One or more errors occurred. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)
   at System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Squirrel.Utility.<LogIfThrows>d__4d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at Squirrel.FileDownloader.<DownloadFile>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAn
...Some of the stack is missing

This issue was created automatically inside the uncaughtException handler

You need to update to 3.0.1 you should get an udpate notification shortly


Fix invalid filenames

Hey, this looks like it solved the issue on my end.

Method cleanPath takes a path string and returns one where invalid characters are replaced with -
Wraps creation of File object referring to destination and the extraction in a try block, catches InvalidPathException.

I only tested that this worked for exporting my SMS attachments from the Files tab, where it worked just fine and exported all 20gbs of them. Did not test exporting by domain or search.

This might be a better way to handle it, up to you. Tries without any replacements, if there's an issue, does the replacements and logs it, if there's still an error, then throws an exception. Also realized drive letter isn't included until later, so no need to ignore first two characters.

Thank you very much!

No problem!


Improving performance of the placeholder list database

This pull request will eventually address #828
This first commit demonstrates, how the current implementation is performing poorly by adding a unit test, that fails.

So it turns out loading 100k placeholders takes only 836ms on WIndows, while it takes 4650ms on Mac.

After the changes it takes 143ms on Mac and 156ms on Windows to load 100k placeholder list from file.

The only remaining question now is - with Mac and Windows disk layout versions diverged, how do we bump them? Should we increment both by +1? I assume we only write migrations for windows layouts, as Mac is not yet being used?

@turbonaitis: I started reviewing this last week and got side-tracked. One thing that is difficult to know is how much is re-used code from the previous collection and how much is new. Is there any way you can share some code across the two collections?

I've compared the two files and it seems refactoring for them to be able to share a lot of code shouldn't be hard - I'll try to do that.

@derrickstolee I've refactored the code, so that both old and new database classes inherrit from the same base class. Please have another look.

@turbonaitis I am currently looking into sqlite and doing some performance and memory testing on a spike of using that.  I also queued a performance build on your changes here as well to see how it compares to sqlite.

I'm closing this PR because #1107 starts the conversion of the placeholder database to SQLite. In local testing we've found this has better read performance than the improvements in this PR as well as significantly better write performance. Thanks for pointing us in this direction @turbonaitis

@derrickstolee thanks for your thorough review! All of your suggestions, if implemented, would have made this code better! I'm also glad you're pointing out the value of programming to explicitly defined interfaces, something that was lacking before.
@jrbriggs looking forward to see the SQLite version implemented!


SSL_connect failed: unexpected eof while reading

Hi there,
I tried to establish connection using TLS to the redis cluster via predixy and it returns the following error
Could not connect to Redis at <IP_ADDRESS>:7617: SSL_connect failed: unexpected eof while reading
The command I run:-
redis-cli --tls --cacert /etc/redis/cert/ca.pem  --cert /etc/redis/cert/client.pem --key /etc/redis/cert/clientkey.pem -p 7617 --askpass
Whilst running the following establishes the connection with Role:unknown if TLS mode was enabled i.e. doesn't recognise cluster:-
redis-cli -p 7617 --askpass
If it wasn't a bug, I wonder when predixy will support TLS? and if there are other alternatives, have anyone tried envoy proxy with TLS required? and if there is anything I can do to help implementing TLS support, please let me know.
With thanks.
Zakaria.

TLS is not supported now

camellia-redis-proxy support tls_connect, you can try it. @InputOutputZ

camellia-redis-proxy support tls_connect, you can try it. @InputOutputZ

Thanks so much for letting me know, any further help would be too appreciated, please check this issue.
https://github.com/netease-im/camellia/issues/130


Build static lib too

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@xhochy ok to merge?

Thanks @xhochy!

The variants cannot be used at the same time as they would clobber eachother. Either the static one should depend on the shared one or there should be a run_constrained <0a0 on each other.

Shouldn't we test for include/aws/common/config.h? I see we don't do it in https://github.com/conda-forge/s2n-feedstock/blob/master/recipe/meta.yaml.

Shouldn't we test for include/aws/common/config.h? I see we don't do it in https://github.com/conda-forge/s2n-feedstock/blob/master/recipe/meta.yaml.

Yes, we should test for that in the main package.

I'm confused why now the run_exports is not working correctly 🤔

Closing as stale.


[BEAM-5915] Timeout http requests, if they got stuck, at dataflow job creation time

Please add a meaningful description for your change here

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.


Is there a health check of any kind on logspout??

I have logspout set to publish its logs to a port, and typically I can view its output by curling that port, however I am currently getting no response. If I restart the container, it will typically solve this problem, but I'm trying to find a root cause. Is there a way to health check an existing logspout container to see why it is not responding before I restart it??

Is there no response from docker logs CID?

There was a response from docker logs in the cases that I saw.

Also now watching this issue.  I'm seeing similar behavior.  Available and happy to help debug if you can suggest a place for me to start.

I've been having (probably) the same problem for about 2 weeks. I've been collecting data otherwise I would have submitted the issue sooner. I'm using gliderlabs/logspout as the image for a kubernetes v1.2.4 daemonset and it runs fine for some number of days before logs cease. There are no error messages, logspout just seems to stop working (though the container and processes stay running). I've got plenty of space left on papertrail, and if I restart the containers/pods logging resumes normally so I think we can rule out papertrail as the source problem.
I will try and leave the broken pod in the current broken state so I can collect more information from it or the node, please send me any requests for info you have.
When a container breaks, the most noticeable issue is that logs cease to be sent to papertrail. The container stays running. If I port forward to the pod so I can connect to the container's http server my curl command just waits and never outputs anything
kubectl port-forward logspout-papertrail-rsjok 9002:80

curl localhost:9002/logs # curl stays running, no output

The above commands work fine and output logs when I connect to a working logspout container.
I can log into the kubernetes node and strace the logspout pid:
root@gke-cluster-default-pool-4efa2519-rpot:~# strace -p 27341 -ff
Process 27341 attached with 7 threads - interrupt to quit
[pid 27348] futex(0xc82000d310, FUTEX_WAIT, 0, NULL <unfinished ...>
[pid 27351] epoll_wait(4,  <unfinished ...>
[pid 26309] restart_syscall(<... resuming interrupted call ...> <unfinished ...>
[pid 27352] futex(0xc8200d8590, FUTEX_WAIT, 0, NULL <unfinished ...>
[pid 27347] futex(0xc82000ce90, FUTEX_WAIT, 0, NULL <unfinished ...>
[pid 27341] futex(0xabbf90, FUTEX_WAIT, 0, NULL <unfinished ...>
[pid 27346] restart_syscall(<... resuming interrupted call ...> <unfinished ...>
[pid 26309] <... restart_syscall resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 26309] clock_gettime(CLOCK_MONOTONIC, {1525060, 176301571}) = 0
[pid 26309] futex(0xabb660, FUTEX_WAKE, 1) = 1
[pid 27346] <... restart_syscall resumed> ) = 0
[pid 26309] clock_gettime(CLOCK_MONOTONIC,  <unfinished ...>
[pid 27346] sched_yield( <unfinished ...>
[pid 26309] <... clock_gettime resumed> {1525060, 176491143}) = 0
[pid 27346] <... sched_yield resumed> ) = 0
[pid 26309] clock_gettime(CLOCK_REALTIME,  <unfinished ...>
[pid 27346] futex(0xabb5a0, FUTEX_WAKE, 1 <unfinished ...>
[pid 26309] <... clock_gettime resumed> {1468265339, 321153236}) = 0
[pid 27346] <... futex resumed> )       = 0
[pid 26309] futex(0xc8200d8590, FUTEX_WAKE, 1 <unfinished ...>
[pid 27346] clock_gettime(CLOCK_MONOTONIC,  <unfinished ...>
[pid 26309] <... futex resumed> )       = 1
[pid 27352] <... futex resumed> )       = 0
[pid 27346] <... clock_gettime resumed> {1525060, 176702791}) = 0
[pid 26309] clock_gettime(CLOCK_MONOTONIC,  <unfinished ...>
[pid 27352] select(0, NULL, NULL, NULL, {0, 100} <unfinished ...>
[pid 27346] clock_gettime(CLOCK_REALTIME,  <unfinished ...>
[pid 26309] <... clock_gettime resumed> {1525060, 176861054}) = 0
[pid 27346] <... clock_gettime resumed> {1468265339, 321421026}) = 0
[pid 26309] clock_gettime(CLOCK_MONOTONIC,  <unfinished ...>
[pid 27346] select(0, NULL, NULL, NULL, {0, 20} <unfinished ...>
...

logspout just seems to be polling and not noticing any log events.

The docker image ID of my current broken container is d36a70e7d3e0b189815821631e38065f638b4ce35c632fae74998ea1af2ab67a

Thats interesting. Do you notice any other issues around the time it stops shipping data?
We could/should probably add statsd support so we can pinpoint how much data/when things stop being shipped. I'd happily look at such a pr and merge it for our next release.

@josegonzalez No other issues around the time. This cluster is a low-traffic cluster so it should be pretty easy to tell if something is spiking or otherwise not working correctly.

In other words, I think this is an issue of basic functionality breaking, not a resource related edge case.

Are you using latest master or something else? We may have fixed your problem here https://github.com/gliderlabs/logspout/pull/191.

I've been using :latest and not :master - I'll switch and see if that fixes the problem thanks.

@josegonzalez So I've switched to docker master tag (image id: e3a7c3c77162f1fa920194aeb890e4f5ea073b66d9202e2b5db258eae6bef3ab) and I'm still having problems though they might be different. The end result is similar, logs are not getting from the containers to papertrail.
The behavior I'm seeing is a small number of containers' logs get through. As I'm writing this only one container's logs, from one host, are getting into papertrail. If I connect directly via http to the logspout container I see the same behavior.
I have recently returned to papertrail at my new job and I'm surprised to be having these issues. I never had a single problem with the now deprecated progrium/logspout container.

I switched back to progrium/logspout and the problems went away. I'll stop contributing to this thread since it's not directly related to the original topic. Sorry for hijacking it.

I am still seeing it intermittently unfortunately. Today I saw a new error though, I tried to curl to follow the log output of a container and got this response:
curl: (18) transfer closed with outstanding read data remaining
which was new. Restarting the logspout container fixed it though.
We are considering pursuing an alternate method of using logback to write logs directly to kafka due to these issues unfortunately :/

@chrishiestand interesting. gliderlabs/logspout is essentially progrium/logspout, except further along in development. I'm not personally sure when things "broke" in such a way that we'd no longer be handling those cases, but unfortunately test coverage isn't great.

I'm using logspout on marathon and having this would alleviate #215 for me (especially combined with #201 ) anyone interested in a bounty?

From struggling with suddenly missing logs for the past several weeks, I'm quite sure at least one of the causes is log rotation when using the json-file driver. we switched to journald logging driver for docker, and the issue went away.
@edude03 give the brodsky/logspout:latest fork a try until #201 is merged - it's essentially a build of #201, which I just rebased.

I'm hitting this issue when using logspout on kubernetes. I switched to UDP instead of TCP and the issue seems to have been mitigated some. It's gone from seeming to stop within 24 hours to having been up for a few days. I'm wondering if it's volume related since I don't normally hit this on quieter machines, but the kubernetes setup I'm using is much more active.
I had been using the syslog+tls scheme on the path passed in as an arg, and changed it to be syslog://

Seems like this issue has meandered a bit and looks like a few things are discussed here. I'm going to close this and those that are still having a specific issue, please open a dedicated issue for that.
Note: there is a known issue for log flows halting if using docker's --log-opt max-size= option

Related to #216.


Fix autocomplete embeddings refresh condition

Noticed that embeddings for autocomplete were not refreshing every 5 min.
Test plan
Added temporary logging to confirm
before:
embeddings for /projects/sourcegraph/cmd/frontend/backend/app.go are -3 minutes old

after:
embeddings for /Users/chriswarwick/projects/sourcegraph/cmd/frontend/backend/app.go are 1 minutes old

Very strange, difference calc should act in abs mode I think

Aligns with the  docs
https://date-fns.org/v2.30.0/docs/differenceInMinutes


#85 fixed

Pull Request Test Coverage Report for Build 763763383

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.08%) to 41.01%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ando/tools/generator/AnDOGenerator.py
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

ando/tools/generator/AnDOGenerator.py
1
0%

Totals

Change from base Build 760423547:
-0.08%

Covered Lines:
203

Relevant Lines:
495

💛  - Coveralls


Rotten Tomatoes support

It would be excellent to have RT supported!

Yes, it would be great, but I don't have enough resources. However, as this is an Open Source project, anyone can create pull request with this feature.


Improve Footer Responsiveness and Design

#590 Improve Footer Responsiveness and Design
This pull request updates the footer on the landing page to improve its responsiveness and overall design. Key changes made include:
Responsive Layout:
Refactored the footer structure using Flexbox to ensure it adapts to different screen sizes (mobile, tablet, desktop).
The footer sections now stack vertically on smaller screens and align horizontally on larger screens.
Visual Enhancements:
Updated font sizes for better readability across devices.
Improved styling of the subscribe form and social media icons for a cleaner look.
Added padding and margins to ensure proper spacing between elements.
Standardized color scheme and button styling for consistency with the rest of the page.
Accessibility:
Ensured that all links have sufficient color contrast for readability.
Improved layout for keyboard navigation and screen reader compatibility.
These changes provide a cleaner, more user-friendly, and visually appealing footer that works well across all devices.

@anuragverma108 please can you review.


Quiz mode can take in other commands

Quiz mode should not be able to take in other commands

What is translation is "End quiz" ?


Decent fakelag fix

So by using G::ChokeMap and checking if the target chokes more than we want lets say 6 ticks, we just ignore him, until he hits below 6 ticks then we shoot. Its decent but better than nothing

no?

this is a good idea, but a bad implementation :D

Hook fl_SimTime (whatever the netvar is), and when it changes, save a record for the player it changed on with relevant data (simtime, tickcount, bones, etc) and then target the most recent record within aimbot. (genius)


url.php

hai , im galuh boy from indonesia,
i may have question about file "url.php"
first:
what i know : the file will make the map having some line that using to draw our track position.
And what i want to ask is on first line that have $_SERVER function,
what that function is purposed ? why the program should need that ?
second :
the function of "mysql_escape_string" , i'm looking on mr.google
there is no such function like that, the function should be "mysql_real_escape_string"
so what was that "mysql_escape_string" suppose to mean ?
anyone please help ...
#sory for bad english (student)
regards, boy

This defines the scope of the cookie used to track the session information across multiple pageloads.  Since info is passed back and forth between php scripts, persistent information is stored in a cookie.  The line there says don't let the cookie persist after this session (so, it's not sitting around on your computer), and the $_SERVER directive really only means the cookie applies to just this directory...not another web directory on that server, like if you're me and you have multiple torque instances up (a test and a live one).  See here: https://secure.php.net/manual/en/function.session-set-cookie-params.php https://secure.php.net/manual/en/reserved.variables.server.php

It used to exist, but is now depreciated.  https://secure.php.net/manual/en/function.mysql-escape-string.php

@surfrock66 thx again buddy
for helping me :dango:


Allow nil for interfaces and models

Fixes #263.
class InterfaceInteraction < ActiveInteraction::Base
  interface :anything

  def execute
    anything
  end
end

InterfaceInteraction.run!(anything: nil)
# master
#   ActiveInteraction::NoDefaultError: anything
# gh-263
#   => nil

class ModelInteraction < ActiveInteraction::Base
  model :object

  def execute
    object
  end
end

ModelInteraction.run!(object: nil)
# master
#   ActiveInteraction::NoDefaultError: object
# gh-263
#   => nil

I'm not entirely clear on this. Why would we allow nil without a default being set?

Because nil is an appropriate value. If you have an interface filter with no methods, nil implements that interface. If you have a model filter for Object, nil is an Object.

Can I get a :shipit:?

:shipit:


[BEAM-9547] Add a few more DataFrame operations

Combining Series with & and |
Projecting multiple columns in __getitem__

R: @robertwb
Post-Commit Tests Status (on master branch)

Lang
SDK
Dataflow
Flink
Samza
Spark
Twister2

Go

---

---

---

Java

Python

---

---

XLang

---

---

---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website
Whitespace

Non-portable

Portable
---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Portable_Python PreCommit


fopen_s, _wfopen_s mode text is incorrect for short-lived / "temporary" file mode flag

The mode / modifier tables for fopen_s, _wfopen_s are not correct. It lists the same mode flag twice (lowercase 't') with different meanings:
mode modifier	Translation mode
t	Open in text (translated) mode.
mode modifier	Behavior
t	Specifies a file as temporary. If possible, it isn't flushed to disk.
Characters in mode string	Equivalent oflag value for _open/_sopen
t	_O_TEXT
t	_O_SHORTLIVED
't' (lowercase 't') is for 'text' mode; uppercase 'T' is for "temporary".
This is already correct on other pages:
https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/fopen-wfopen?view=msvc-170
https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/fsopen-wfsopen?view=msvc-170
But 'T' temporary is also misleading; see #4523 since 'T' actually maps to '_O_SHORTLIVED' while 'D' maps to '_O_TEMPORARY'.

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

ID: c5a2e737-afe6-a70d-8eb3-fe3a0aeda3e8
Version Independent ID: 3a9bdb00-1d09-1b08-3dc3-029a6a0b16a2
Content: fopen_s, _wfopen_s
Content Source: docs/c-runtime-library/reference/fopen-s-wfopen-s.md
Product: visual-cpp
Technology: cpp-ucrt
GitHub Login: @TylerMSFT
Microsoft Alias: twhitney

Fixed. Also did some work in conjunction with #4523. Will be live Monday afternoon.


verify_bundle_keys to not 'failfast'

Is your feature request related to a problem? Please describe.
https://github.com/Project-MONAI/model-zoo/blob/c4752051e315917089f098651e13776bac92630b/ci/verify_bundle.py#L121
currently the testing pipeline fails and reports on the first missing keyword for the config.
would be great to report as many as possible all the missing keywords in one test and save the developers' time...

do you have time to enhance this? @yiheng-wang-nv

Update: I will address this feature today


Assign input value (eg: UiPath Studio) , and replace the word with an…

…y other word by using Replace function
Task 24

SourceCode/2024/May 2024/saivenu/Task24/project.json
Main.xaml

Remove unused WriteLine activities and consider replacing them with tracepoints during debug.
Consider changing WriteLine to Log Message if needed for debugging purposes.

Variables

Ensure all variables follow the naming convention.
Check that variable names are unique and avoid duplicates.

Activities

Add more descriptive titles to activities like Assign, Write Line to make them easier to understand.

Dependency packages

Remove unused dependency packages (UiPath.Excel.Activities, UiPath.Mail.Activities, etc.) to improve process execution time.

Score: 4/5

SourceCode/2024/May 2024/saivenu/Task24/project.json
Main.xaml
WriteLine activity usage at Write Line: Write Line activity can be replaced with tracepoints during debug. They should be removed before publishing. Consider also changing WriteLine to Log Message if it is really needed for debugging purposes.
WriteLine activity usage at Write Line: Same comment as above.
Variable naming conventions
Variable str_ input does not respect the set pattern ^ (dt_) ?(A-Z|a-z) + (0-9)$ | out A-Za-zA-za-za0-9_: Make sure all the variables follow the naming convention.
Variable str_replace does not respect the set pattern ^ (dt_) ?(A-Z|a-z) + (0-9)$ | out A-Za-zA-za-za0-9_: Same comment as above.
Assign display name
Assign display name is defined many times. Current allowed threshold is 1. Code contains 2: Names of activities should give a clear indication of how they are being used. Default names are usually too generic. Please avoid duplicate names.
Write Line display name is defined many times. Current allowed threshold is 1. Code contains 2: Same comment as above.
Activity naming conventions
Activity Write Line has a default name.: Check if it could be easier to understand what the activity does by adding a more descriptive title.
Activity Assign has a default name.: Check if it could be easier to understand what the activity does by adding a more descriptive title.
Activity Write Line has a default name.: Same comment as above.
Activity Assign has a default name.: Same comment as above.
Dependency packages
Dependency package UiPath.Excel.Activities is not used.: Remove unused packages in order to improve process execution time.
Dependency package UiPath.Mail.Activities is not used.: Same comment as above.
Dependency package UiPath.System.Activities is not used.: Same comment as above.
Dependency package UiPath.Testing.Activities is not used.: Same comment as above.
Dependency package UiPath.UIAutomation.Activities is not used.: Same comment as above.
Score: 5/5
Note: The review is based on the provided information, and it does not contain any code suggestions.

SourceCode/2024/May 2024/saivenu/Task26/project.json
Main.xaml
Log Message not used in workflow Main.

This is an important finding! Log messages help us understand the flow of our process and are super helpful when debugging or maintaining the code.

Variable naming conventions
Variable int_randomNum does not respect the set pattern ^ (dt_) ?(A-Z|a-z) +(0-9)* $ |out A-Za-zA-Za-za0-9_*$.

Please make sure all your variables follow this naming convention. It's super important for readability and maintainability!

Message Box display names
Message Box display name is defined many times. Current allowed threshold is 1. Code contains 5.

Try to give each Message Box a more descriptive name that indicates what it's used for. Right now, they're all just "Message Box".

Activity naming conventions
Activity State Machine has a default name.

Can you give this activity a more descriptive title? It will make it easier to understand what the activity does.

Activity Assign has a default name.

Same thing! Can you give this activity a more descriptive title?

...and so on for all the repeated "Message Box" activities
Score: 5/5
Please address these issues and let me know when you're ready for another review!

@SAIMADDURI
Task – 24
Code verified.
Task – 26
Code verified.
Try to complete the pending tasks and commit it in github


AGPL3 is not detected on GitHub or GitLab

Are you experiencing an issue with...
shields.io
🐞 Description
My project has license AGPL3 but that’s not correctly detected. Applies to GitHub as well as GitLab (project moved recently).

GitHub: not identifiable by github
GitLab: Other

🔗 Link to the badge
https://img.shields.io/github/license/dboehmer/coocook.svg
https://img.shields.io/gitlab/v/license/coocook/coocook
💡 Possible Solution
No response

Hi.
If I call https://api.github.com/repos/dboehmer/coocook it says the license is
"license": {
  "key": "other",
  "name": "Other",
  "spdx_id": "NOASSERTION",
  "url": null,
  "node_id": "MDc6TGljZW5zZTA="
},

If I call https://gitlab.com/api/v4/projects/coocook%2Fcoocook?license=1 it says the license is
"license": {
  "key": "other",
  "name": "Other",
  "nickname": null,
  "html_url": "http://choosealicense.com/licenses/other/",
  "source_url": null
},

In the case of GitHub, it tries to auto-detect your license from the LICENSE file (more details https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository#detecting-a-license ). If you're using a well-known license and it is not auto-detected this is often due to some minor difference between the license file in your repo and the reference copies in https://github.com/licensee/licensee . Even really minor differences like whitespace can cause this. I'd imagine GitLab does something similar, but I've not looked into it.
In any case, the badges are reporting the values from the API responses correctly so this is an issue that will need to be resolved elsewhere. Thanks


"Instana" sensors and agents are affected, patches provided

Submission Template
Please provide the following information.

Vendor: IBM
Product Name: Instana
Version(s) affected: it's complicated
Status:  Fixed
Update Available:  Yes
Notes
References
Last Updated:  Date of last update

For questions about choice for status, please see the information below.

Unknown - Status unknown.  Default choice.
Affected - Reported to be affected by CVE-2021-44228.
Not Affected - Reported to NOT be affected by CVE-2021-44228 and no further action necessary.
Fixed - Patch and/or mitigations available (see provided links).
Under Investigation - Vendor investigating status.

This product has been added to the repository. Thank you.


What's the output of hostname -I | cut -d' ' -f1 and hostname -I

@VibroAxe

Do all the machines on your network have a public IP?
Is this machine inside your network, you can't have a cache box external to the network
Assuming this is an internal cache however:
For some reason LANCACHE_IP wasn't set when you ran the commands. My guess is you forgot the export line
docker rm lancache-dns

docker run --restart unless-stopped --name lancache-dns -p 53:53/udp -e USE_GENERIC_CACHE=true -e LANCACHE_IP=<IP_ADDRESS> lancachenet/lancache-dns:latest```
Should get you up and running

Do all the machines on your network have a public IP?
Is this machine inside your network, you can't have a cache box external to the network
Assuming this is an internal cache however:
For some reason LANCACHE_IP wasn't set when you ran the commands. My guess is you forgot the export line
docker stop lancache-dns
docker rm lancache-dns

docker run --restart unless-stopped --name lancache-dns -p 53:53/udp -e USE_GENERIC_CACHE=true -e LANCACHE_IP=<IP_ADDRESS> lancachenet/lancache-dns:latest

Should get you up and running

this helped me. Thanks

I had the same problem.
The log then said that 53:53/udp is already in use. This is also correct, from the Debian server itself.
How can I change this? It is an external server and has no internal network to the other server

@HerrSammyDE  I think the solution to your problem is to stop the dns server which Debian is running for you. Logically you only need one dns server, it's either this one or that one.
Also just because the symptom is the same (constant restarting) doesn't mean the cause is the same. Locking thread.


Outdir not working

Dear,
I used your script and I think there is a small bug when using the outdir argument.
You should add something like this in your main to create the folder, otherwise it gives an error, at least in my case
if not os.path.exists(args.outdir):        os.makedirs(args.outdir)

Sorry it took me so long to respond to this issue and thanks for pointing this out.

Thanks for pointing this out @LauraVP1994. The script has been updated


⚠ Bofrost.lu has degraded performance

In ba1b58a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 3873 ms

Resolved: Bofrost.lu performance has improved in 5035f96.


ESM: type: "module" in package.json?

If @floating-ui/dom is meant to be ESM, then shouldn't it have "type": "module" in package.json? Also an exports section?

I'd like for it to be but I want to make sure there are no issues with bundlers like webpack/create-react-app. I changed it back to a "legacy" type of ESM using a plain .js file + module field to ensure this, for now. Wondering what the best way to go about this is? See #2

I believe you can support both, see https://nodejs.org/api/packages.html#packagejson-and-file-extensions
// package.json
{
  "main": "./main-require.cjs",
  "exports": {
    "import": "./main-module.js",
    "require": "./main-require.cjs"
  },
  "type": "module"
}

Also, this looks interesting: https://antfu.me/posts/publish-esm-and-cjs

Will give that a go and manually test the package in CRA to make sure there are no issues! I know that Nuxt 3 requires this type of setup going forward, so definitely something to move toward. Evidently it seems like using .mjs is not the way to do it though due to the current issues with bundlers.

My 2 cents: I would go with an ESM default (so .js instead of .mjs) and provide an explicit require export with .cjs. Assuming that is compatible with CRA etc.