pcfdev box has issue connecting to broker running on another machine

I have a broker running with pcf-dev, and have created a postgres service instance. The app is bound to the postgres service instance. However, the application has error (followed)
Caused by: org.postgresql.util.PSQLException: Connection to <IP_ADDRESS>:32773 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
I’m able to use db client to connect to <IP_ADDRESS>:32773. So it seems the pcfdev box is having problem communicating with an external VM ie <IP_ADDRESS>.
I tried to login to the pcfdev box, but do not have the credentials.
Any tips?
Thanks

Hi Beth,
You need to add a security group to permit your app to make connections to your external DB service. By default, apps can only make connections to public IP addresses, the VM, and the host. See here for instructions. In your case, this should look something like:
cf create-security-group db <(echo '[{"protocol":"all","destination":"<IP_ADDRESS>"}]')
cf bind-running-security-group db
cf restart your-app

You can login to the VM to test connectivity with ssh<EMAIL_ADDRESS>(password: vcap). However, you may want to test connectivity from an app container (using cf ssh your-app) instead of the VM itself.
Hope this help!
Stephen

Stephen
Your suggestion solves the problem.  My micro-services are deployed and running. Mucho thanks.
-Beth


New Branches

Recently found this new branches: gview6 and gview6-STJ, both are NET8, but what are the differences? which one can I review? Also continue to maintain master (gview5, NET 4.7)
Regards
Carlos

Hi Carlos, i will change from gView 5 to gView 6 soon.
Thats why i also changed the name of the repository form gview5 to a version independent name "gview-gis".
The difference between the gview6 and gview6-STJ is, that i use System.Text.Json (STJ) an not Newtonsoft.Json.
But now i  just merged the changes back to the gview6 branch. gview6-STJ will deleted soon.
The main focus on the new release will be the UI for the gView Carto and gView Explorer UI. I will not use Windows Formas anymore. Its than all Blazor and running also in the web.
The main branch is here is still gview5
The gview5 branch is an will be the latest (and last) gview5
The gview6 branch is the current gview6 version.
I must do all the documentation stuff first, then the gview6 branch will merged to master.
Hope thats ok for you,
Regards
Jürgen
PS And yes everything will be .NET 8

Thanks in advance. I understand the idea.
meanwhile, in this brank I found this situation, trying to load an ArcGIS Feature Service, notice that the Extent object doesn't have a number, instead has NaN as string. So an error was generated. I'd made a custom JsonConverter to manage this returning Double.NaN but i'm not sure it's the best solution.

OK, step by step:
Execute gView.Web
Explorer
Web Services
Esri Geoservices
My Own AGS services
http://MYOWN/arcgis/rest/services/PETIGASCARIBEPRUEBA/PETIGASCARIBE/MapServer/layers?f=json&
Returns in many layers:
"extent":{"xmin":"NaN","ymin":"NaN","xmax":"NaN","ymax":"NaN","spatialReference":{"wkid":3116,"latestWkid":3116}}
And return a message like 'The JSON value could not be converted to System.Double
Means that cannot convert the string NaN to double.
I made a custom JsonConvert to avoid that.

It's a good solution?

Hi Carlos,
You already using gView6, nice :)
With Version and branch you are testing.
Form now on the current branch is gview6. Forget all other branches...
Numbers with NaN seems not work with System.Text.Json in advance.
I extended the JsonSerializerOptions with this:

static public class JsonSerializerOptionsExtensions
{
    static public JsonSerializerOptions AddServerDefaults(this JsonSerializerOptions options)
    {
        if (options.Converters != null)
        {
            options.Converters.Add(new Array2DConverter());
            options.Converters.Add(new DBNullConverter());
        }

        options.ReferenceHandler = ReferenceHandler.IgnoreCycles;

        // Allow "NaN" with numbers
        options.NumberHandling = JsonNumberHandling.AllowNamedFloatingPointLiterals;

        return options;
    }
}

now it seems to work. Pull the latest gview6 branch. Hope it works than for you


Abstracting away errors

The 3 operations: canStoreSecurely, write, and read are executed in wild environments.
How about allowing callbacks to be passed to each that would be executed if anything gets thrown?
Basically, this
boolean canStoreSecurely();
void write(String name, ByteString value);
Observable<ReadResult> read(String name);

would become
interface OnErrorListener {
  void onError(Throwable t);
}

boolean canStoreSecurely(@Nullable OnErrorListener onErrorListener);
void write(String name, ByteString value, @Nullable OnErrorListener onErrorListener);
Observable<ReadResult> read(String name, @Nullable OnErrorListener onErrorListener);

I think I'd prefer this passed into the factory/constructor instead of at each callsite?

What's the goal here? How does this change the behavior of Observable and Completable?

 Want to make that behavior optional..

Ah, right. I remember that thing. Second question still stands.

If an error callback is not set ⇒ throw the error down the stream
if an error callback is set ⇒ .doOnError(callback).onErrorResumeNext(/* something */)

Yeah, the behavior change is to attach error handling everywhere so you don't need to worry about it at every call site... Not that important for read() since it's a stream and those are easy to attach error handling to. It was important for write before we changed that to a Completable, so I guess it's not that important there anymore. canStoreSecurely() is still a pain to have to try/catch it. @oldergod and I are looking through our reports now to see if we can handle those ones differently and then maybe this error handling can just be turned into extension functions internal to the app.

Let's say we don't need that for now


mgmt, iotfirmwaredefense, add live tests

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run prepare-pipelines

/azp run java - iotfirmwaredefense - mgmt - tests

API change check
API changes are not detected in this pull request.


@W-16375669@  Automate updating of custom functions in migrated IP & DR

What does this PR do?
this replaces the old custom formula syntax to standard formula syntax for custom implementation.
for example :
REPLACE(targetString, replacementString). ===> FUNCTION(“CustomStringFunctions”, “replace”, targetString, replacementString).

Please write Unit test cases

added the unit tests

Please write Unit test cases

Added


Documentation inacurate

The documentation for the installation on OCP3 says
"controller-3.yml and controller-4.yml in the deploy/ocp3-operator/latest, stable, and v1.0.0 directories contain the recommended settings for OCP 3 and 4 respectively."
The path is incorrect, it's "deploy/nom-olm/latest, stable and v1.0.0"

Thank you for the issue! I'll try to get this fixed shortly


Docs are confusing

Hello again,
Probably related to my ealier submitted issue.
Tried
helm install stable/nginx-ingress --set rbac.create=false --set rbac.createRole=false --set rbac.createClusterRole=false
from
https://github.com/Azure/AKS/issues/346
but when I surf to the IP  I get
This site can’t be reached
<ip-address-here> took too long to respond.
Try:
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_TIMED_OUT
:(
I've tested with two clusters. This used to work some months back.
And as a last note, I think the docs need to be much more explicit about the different versions used because there are a lot of components involved here and things move fast. For instance, we have helm, kubectl, az, kubernetes, nginx-ingress. A lot of the time if one components gets bumped, another gets affected. Seen this too many times. :(

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

ID: ada58160-dc50-b977-d3bc-65f92406e16d
Version Independent ID: 5c596e04-fddb-effe-3b72-575f4df42d4e
Content: Configure ingress with Azure Kubernetes Service (AKS) cluster
Content Source: articles/aks/ingress.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Also, a lot of the times you get an error, find some snippet on Google, execute the command, without really knowing what you just did, then leaving your environment in a "messy" state. The docs should therefore always have some sort of reset instructions.

@iainfoulds would you be able to look into this one? Might be related to the other 2 you are working on from @spacecat

@MicahMcKittrick-MSFT These are quite different.
@spacecat I'll create a non-RBAC cluster and test. On an RBAC-enabled cluster, the instructions work correctly.
I'll look to add a note on how to remove a Helm deployment if you no longer wish to use. These aren't AKS specific, rather Helm management tasks. To list what's been installed by Helm:
helm list

The CHART column shows what component it is, such as nginx-ingress-0.22.1, as shown in the following example output:
 $ helm list
NAME           	REVISION	UPDATED                 	STATUS  	CHART               	NAMESPACE
rafting-sparrow	1       	Mon Jul 16 14:02:02 2018	DEPLOYED	nginx-ingress-0.22.1	kube-system

So delete the ingress controller:
helm delete rafting-sparrow

#in-progress

@spacecat I can't replicate this error, both a non-RBAC and RBAC-enabled cluster respond on the public IP address in the web browser. When you do a helm list, is the ingress controller shown? If you do kubectl get pods, do the pods show as in a Running state?

@iainfoulds I tried everything again (fresh cluster install) and now it works. I think I must have missed/skipped the Helm step a long the way.
For reference these are the steps that I needed to do in order for it to work:
1 https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough
1.1 Create resource group:
az group create --name test-cluster-02-rg --location westeurope

1.2 Create cluster (RBAC is enabled by default):
az aks create --resource-group test-cluster-02-rg --name test-cluster-02-cl --node-count 1 --generate-ssh-keys

1.3 Connect to the cluster:
az aks get-credentials --resource-group test-cluster-02-rg --name test-cluster-02-cl

2 https://docs.microsoft.com/en-us/azure/aks/kubernetes-helm
2.1 Create a service account:
nano helm-rbac.yml
kubectl create -f helm-rbac.yml

apiVersion: v1
kind: ServiceAccount
metadata:
name: tiller
namespace: kube-system
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
name: tiller
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:

kind: ServiceAccount
name: tiller
namespace: kube-system
2.2 Configure Helm:
helm init --service-account tiller

3 https://docs.microsoft.com/en-us/azure/aks/ingress
3.1 Install ingress controller:
helm install stable/nginx-ingress --namespace kube-system

3.2 Get the public IP address:
kubectl get service -l app=nginx-ingress --namespace kube-system

If I browse to the public IP address, I am routed to the NGINX ingress controllers default 404 page which previously did not work for me.
It's easy to miss the Helm service account part and I think it would be a good thing if you could add a highlighted side note or similar with a link (https://docs.microsoft.com/en-us/azure/aks/kubernetes-helm) on the Ingress and TLS docs page so you don't miss it. Also, in the Install an ingress controller part you could add a link to https://docs.microsoft.com/en-us/azure/aks/kubernetes-walkthrough. And that a cluster created following that walkthrough is RBAC-enabled by default. I believe that doesn't say anywhere.
You can close this now.
Thanks!

The document still doesn't work for me. I find commands from this fix the problem:
kubectl create serviceaccount --namespace kube-system tiller
kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'


Fails to build on Ubuntu 18

I'm trying to build revery-quick-start in my system but it fails while building reason-sdl2. Any guidance would be much appreciated. Here's the log:
info esy build 0.6.2 (using package.json)
info building reason-sdl2@2.10.3010@d41d8cd9
error: build failed with exit code: 1
  build log:
    # esy-build-package: building<EMAIL_ADDRESS>    # esy-build-package: pwd: /home/vijay/.esy/source/i/reason_sdl2__2.10.3010__dae8935c
    # esy-build-package: running: 'dune' 'build' '--root' '.'
    File "dune", line 1, characters 17-31:
    1 | (ignored_subdirs (node_modules))
                         ^^^^^^^^^^^^^^
    Warning: ignored_subdirs is deprecated in 1.6. Use dirs to specify visible
    directories or data_only_dirs for ignoring only dune files.
     js_of_ocaml bin_js/test_sdl2.bc.runtime.js
    warning: free variables in primitive code "caml_glGetString" (/home/vijay/.esy/3/b/reason_sdl2-2.10.3010-037a6d51/default/bin_js/../src/gl_stubs.js:23)
    vars: caml_js_to_string
    code providing caml_glGetString (/home/vijay/.esy/3/b/reason_sdl2-2.10.3010-037a6d51/default/bin_js/../src/gl_stubs.js:23) may miss dependencies: caml_js_to_string
             gcc src/sdl2_wrapper.o (exit 1)
    (cd /home/vijay/.esy/3/b/reason_sdl2-2.10.3010-037a6d51/default/src && /usr/bin/gcc -I /home/vijay/.esy/3____________________________________________________________________/i/ocaml-4.7.1004-a6ae015e/lib/ocaml -I /home/vijay/.esy/3____________________________________________________________________/i/opam__s__lwt-opam__c__4.4.0-185b2924/lib/lwt -I /home/vijay/.esy/3____________________________________________________________________/i/opam__s__ocamlfind-opam__c__1.8.1-3176721a/lib/bytes -I /home/vijay/.esy/3____________________________________________________________________/i/opam__s__result-opam__c__1.4-35a3271d/lib/result -I /home/vijay/.esy/3____________________________________________________________________/i/opam__s__seq-opam__c__base-37652505/lib/seq -I /home/vijay/.esy/3____________________________________________________________________/i/reason_gl_matrix-0.9.9306-c198df5b/lib/reglm -I /home/vijay/.esy/3____________________________________________________________________/i/esy_sdl2-2.0.10004-5d8a4274/include -I /home/vijay/.esy/source/i/reason_sdl2__2.10.3010__dae8935c/include -I /home/vijay/.esy/source/i/reason_sdl2__2.10.3010__dae8935c/src -fPIC -std=c++11 -g -o sdl2_wrapper.o -c sdl2_wrapper.cpp)
    sdl2_wrapper.cpp: In function 'value resdl_SDL_GetNativeWindow(value)':
    sdl2_wrapper.cpp:189:41: error: 'union SDL_SysWMinfo::<unnamed>' has no member named 'x11'
         pNativeWindow = (void *)wmInfo.info.x11.window;
                                             ^~~
    error: command failed: 'dune' 'build' '--root' '.' (exited with 1)
    esy-build-package: exiting with errors above...

  building<EMAIL_ADDRESS>esy: exiting due to errors above

This is due to you not having the development packages for XOrg/X11. Check out Revery's "Build and Run" for the required packages!


Can't get the .exe to work

I've just downloaded the files, and unpacked them.
I have the .exe open, with the addon I want selected, and I ended up editing the game path manually as I couldn't use Select Directory.
Everything is greyed out, and it's telling me that the bin64 path is incorrect. I've taken a snapshot: https://imgur.com/a/kfDNdPl

If you set the path to E:\Program Files\Guild Wars 2 (no bin64), it should work.

Thank you, that worked. Any idea why my buttons are greyed out rather than red?

Which buttons? The ones in the addon manager are all styled grey/blue if I recall correctly.

Ah, must be an older image I saw - the buttons were all red.


error checks when reading /proc/[pid]/exe don't account for kernel processes or docker permissions shenanigans

Right now, under Linux we check to see if we have a permission denied error when we resolve the symlink for exe:
https://github.com/elastic/elastic-agent-system-metrics/blob/8a02eaa6c02e7972cc8d0adc90c1c13db836e273/metric/system/process/process_linux_common.go#L209
We do this so we can skip any errors related to permissions issues. However, this doesn't work under two cases:

For kernel processes, the exe symlink is non-existent
Under docker, we'll get either Permission deined or file not found depending on the permissions docker is running with.

The permissions check in process_linux_common.go should check for both permission errors, and file not found errors.


Implement node_network_profile for default node pool

Describe your changes
Implements default_network_profile for the default node pool
Issue number
#524
Checklist before requesting a review

[X] The pr title can be used to describe what this pr did in CHANGELOG.md file
[X] I have executed pre-commit on my machine
[X] I have passed pr-check on my machine

Thanks for your cooperation!

@zioproto I see allowed_host_ports and application_security_group_ids in node_network_profile block, don't we need to add them in this pr?

The goal of this PR was to bring feature parity between the current extra extra_node_pool.tf and the default nodepool.
https://github.com/Azure/terraform-azurerm-aks/blob/dce8047210ab2e348792a11e759a4e7a73b38bfd/extra_node_pool.tf#L117-L123
If I implement allowed_host_ports I should add it in both places, maybe I can do that in a different PR ?
It would be easier to test, because I should extend also end to end tests to cover all those scenarios.


iOS issue after upgrading Xcode 13.2.1

Current behavior
/Users/mycom/Library/Developer/Xcode/DerivedData/limelite-fmzrscpebfdblueckvpunppvzdku/Build/Intermediates.noindex/PrecompiledHeaders/Compressor-Bridging-Header-xsfx0gcl0s08.dia:1:1: warning: Could not read serialized diagnostics file: error("Failed to open diagnostics file") (in target 'Compressor' from project 'Compressor')
Command PrecompileSwiftBridgingHeader failed with a nonzero exit code
Platform

[X] iOS

React Native Version
0.63.3
React Native Compressor Version
1.4.0
Reproducible Steps And Demo

@nomi9995 Could you check the errors above? I added node_modules/react-native-compressor/ios/Compress.xcodeproj to library and added libCompressor.a to Link biary with libraries.

@martsneld can you try to bridge the header by

and try again?

@nomi9995 I tried it several times. I created a blank .swift file and created a bridge. Then I dragged Compressor-Bridging-Header.h to Object-C Bridging Header.

@martsneld can you make a repro in the new GitHub repo and attach the link here so I can reproduce it on my side ad fix it. it is not reproducing on my side. I am testing the example folder in this package

@martsneld any update?

@nomi9995 Sorry for late response. no updates. I disabled this library for now. I will let you know if I have more questions when resuming this package.


Add SQL Bindings

can we add description for this PR?

@YunchuWang @vrdmr @gavin-aguiar This can be closed


App v2.3.1_v2 is blocking the network connection

What happened: After some time the app is blocking the network connection and other apps cant send data (the same bug is on 3 machines WIN10 cli, Win Server 2019 & Win Server 2009
What you expected to happen: running the app
How to reproduce it (as minimally and precisely as possible): running the app 2.3.1_v2

What are your environment parameters?

DeFi App Version: 2.3.1_v2
Operating System (OS): WIN10, WIN Server 2019, WIN Server 2009

Anything else we need to know?:

Hello @supervolot
Please send us some more screenshots and your log data so that we can better understand the problem.
https://github.com/DeFiCh/app/wiki/How-to-submit-issues-for-Defi-App

Hi @supervolot , the team has halted v2.3.1 at the moment due to some issues. I'll update you again when the team fixes it and is ready for release. In the mean time, could you send your app logs please?

defi_v2.3.1_log_14.03.2021.log

There are also "network errors" seems like the app have a lot ob bugs, perhaps you should update as fast as possible to 2.3.2

@supervolot Do you know if your machine has network connection? Maybe there's some firewall/anti virus that's blocking the network connection on your machine. The network errors on the logs are just warnings that the app cannot connect to the network

Sometimes i have the same error, i make a video.
HTTP over Browser failed
Wallet Balance failed
Ping ok
Sync ok
Close Wallet: All fine again.
http://mydeficha.in/video/lost_internet_http.mp4

Do you have a low bandwidth cap on your network? It seems that app is only synced to block 270k and not fully synced. During syncing state it would consume quite significant bandwidth, this might limit your other apps from using the same bandwidth.
Regardless, I don't think this is an issue on the node or defi app but more of an issue of the network. I can't really be sure. Alternatively you might want to try the Bitcoin Core (QT) client to see if the same network issues occur. https://bitcoin.org/en/download

I have the same problem, about 5 hours after opening the wallet (same effect when only the defid is running without wallet) the internet connection on Win10 drops.
From that moment on no RPC connections are possible neither to a bitcoin fullnode on the computer nor to the defi node.
Immediately after the definode was shut down everything works normally again.
In the logfiles there is nothing to find at the time, I will try to record the next interruption.

Do you have a low bandwidth cap on your network? It seems that app is only synced to block 270k and not fully synced. During syncing state it would consume quite significant bandwidth, this might limit your other apps from using the same bandwidth.
No, my Wallet is on testnet, Blockheight is correct.
I check the connections from defid.exe when the wallet and internet works:

Bitcoin Testnet or not? After connection is lost, all this Ports are closed, only 18555 visible.

when the error occurs, the ports above opened from defid.exe.

This error occurs only with enabled spv-support (spv=1 in defi.conf) Is this switch necessary to run a Masternode inside the Wallet?
Maybe its not a problem from the APP, its a problem of defid.exe (AIN/Node-Version)

Hi @supervolot , update v2.3.2 is out, this is a mandatory update.
Please read through the release notes before updating.
The above feature / issue is not included in this update yet, this comment is to notify you about the update.

Hi i have still the bug after the mandatory update (and no SPV=1) in the defi.conf

App_log_29.02.2021.log
Bin logs_29.03.2021.log

After the bug when i stopp the app and restart i get the message "corrupted block database detected" !!!

Hi @supervolot , thanks for the update, it's likely did not close the app properly.

The team is working on the Snapshot fix — to speed up synchronisation. Logs well received, please give us time to investigate.

Hi @supervolot , v2.3.3 is out. Please read through the release notes before updating. If you have not sync to 100%, there was a node issue on 05/04/2021 that may have cause the network error, everything is back online now, you may try the following:
Option 1 — Reset & Reindex (sync from 0%)

Settings > Reset & Reindex

Option 2 — Snapshot (sync from 90%+)

Settings > Reset & Reindex
Wait for app to start syncing
Ensure you’ve at least 27GB of extra space
Click on i located at bottom-left corner of app screen
Download Snapshot

Let me now your results, thank you for your patience.

If your issue persist, we can further discuss on the problem here Unable to start blockchain. We would like to keep same issues in one thread. Thank you for your patience.


OLS-1110 - Auxiliary task: Remove service image installation from konflux jobs

Removing the service image replacement from konflux jobs since now that we moved to a separate application, we no longer have access to the ols application's snapshot
Description

Type of change

[ ] Refactor
[ ] New feature
[x ] Bug fix - fixing konflux test jobs
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)
[ ] CI configuration change
[ ] Konflux configuration change

Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

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

Project coverage is 91.14%. Comparing base (e77efdf) to head (ca9245b).
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1898      +/-   ##
==========================================
- Coverage   93.47%   91.14%   -2.33%
==========================================
  Files          64       64
  Lines        2941     2868      -73
==========================================
- Hits         2749     2614     -135
- Misses        192      254      +62

see 9 files with indirect coverage changes

/retest

/test e2e-ols-cluster-4-15
/test e2e-ols-cluster-4-16
/test e2e-ols-cluster-4-17

/test integration

/test e2e-ols-cluster-4-15

/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"

/override "ci/prow/e2e-ols-cluster-4-15"

/approve
/lgtm

/lgtm
/approve

/test unit

/override "ci/prow/e2e-ols-cluster-4-17"

/test integration


chore: resolve all npm install warnings

Replaces listr with listr2 and updates mocha. npm install no longer
reports audit issues on install.
I am not confident about the listr changes, especially replacing the use of listr-input with inquirer. Unfortunately, those are all in the v8-update code and it does not seem to be covered by tests. Perhaps @targos can test it?

I added log-symbols to the dependencies. It looks like we were depending on it being installed by listr.
The functionality is not broken (I tried the major, minor and backport commands), but the prompt when there are conflicts is not displaying correctly. I think that listr2 and inquirer both try to rewrite the last terminal line and listr2 wins the fight. See https://asciinema.org/a/OqLKx8YqAxwZhi7U9yXD1ZOys

Should be fixed now: https://asciinema.org/a/sVGBhIpAMEtyjCmQoY9zMvDPe

Pinging recent reviewers in this repo who aren't targos or me: @aduh95 @richardlau @mhdawson @codebytere @tniessen


Breakup the genapi script into a separate package

Convert genapi.py into denvrgen.

Test individual functions
Extract each of the major spec components into standard names
Support generating API directories for various languages (e.g., typescript, go)

Consider just contributing to and using https://github.com/MarcoMuellner/openapi-python-generator.
Pros:

Should already address #7
Code is pretty easy to follow

Not too verbose
Organized how I'd probably breakup the apigen.py script anyway

Support both requests and httpx (and sync and async calls)
Uses pydantic (was considering anyway)

additional validation
type hints / conversions
aliasing out-of-the-box (e.g., to_snake)

Cons:

External dependency
Will require some slight modifications

Flag to use to_snake for method and field names.
Integration with our Auth and Config logic


cmdstan can fail to compile, depending on stan filename

Summary:
Stan models fail to compile when the stan model file has an unusual filename.
Description:
I noticed that my cmdstanr compilation was failing for some files with unusual, but valid, filenames. I think this is a problem with cmdstan, rather than cmdstanr. A couple of characters that are trouble seem to be + and (, but I'm sure there are others.
Reproducible Steps:
Copy these lines into two different files, one called test.stan and another called test (.stan.
(I think this will be a problem with any stan model; here's the one I used.)
Then try to compile both. test.stan works, test (.stan does not.
// generated with brms 2.13.3
functions {
}
data {
  int<lower=1> N;  // number of observations
  int Y[N];  // response variable
  int<lower=1> K;  // number of population-level effects
  matrix[N, K] X;  // population-level design matrix
  int prior_only;  // should the likelihood be ignored?
}
transformed data {
  int Kc = K - 1;
  matrix[N, Kc] Xc;  // centered version of X without an intercept
  vector[Kc] means_X;  // column means of X before centering
  for (i in 2:K) {
    means_X[i - 1] = mean(X[, i]);
    Xc[, i - 1] = X[, i] - means_X[i - 1];
  }
}
parameters {
  vector[Kc] b;  // population-level effects
  real Intercept;  // temporary intercept for centered predictors
}
transformed parameters {
}
model {
  // priors including all constants
  target += student_t_lpdf(Intercept | 3, 1.4, 2.5);
  // likelihood including all constants
  if (!prior_only) {
    target += poisson_log_glm_lpmf(Y | Xc, Intercept, b);
  }
}
generated quantities {
  // actual population-level intercept
  real b_Intercept = Intercept - dot_product(means_X, b);
}

In R:
cmdstanr::cmdstan_model("test.stan") # Runs
cmdstanr::cmdstan_model("test(.stan") # Fails with error below

Current Output:
  System command 'make' failed, exit status: 2, stderr (last 10 lines):
E>   533 |   stan_model* m = new stan_model(data_context, seed, msg_stream);
E>       |   ^~~~~~~~~~
E> /tmp/RtmpJf3PfS/model-4f974c9a990.hpp:533:15: error: ‘m’ was not declared in this scope; did you mean ‘tm’?
E>   533 |   stan_model* m = new stan_model(data_context, seed, msg_stream);
E>       |               ^
E>       |               tm
E> /tmp/RtmpJf3PfS/model-4f974c9a990.hpp:533:23: error: expected type-specifier before ‘stan_model’
E>   533 |   stan_model* m = new stan_model(data_context, seed, msg_stream);
E>       |                       ^~~~~~~~~~
E> make: *** [make/program:50: /tmp/RtmpJf3PfS/model-4f974c9a990] Error 1
Type .Last.error.trace to see where the error occured

Expected Output:
A valid, compiled stan model.
Additional Information:
I'm using cmdstanr::cmdstan_model to compile.
Current Version:
v2.23.0

It needs to be a legal Stan identifier when - is converted to _.
That means [a-zA-Z][_0-9a-zA-Z]*
This should be tested from the outside.

Stanc3 should test that and could either:

error early
replace special characters with _ or just remove them

If it helps, I rant into this issue by trying to name the stan file after a (sanitized) brms formula:
y - x1 + x2 + (1  x3).stan


Multiple Issues with Injected Connectors

Describe the bug
This list isn't by any means exhaustive, but I've noticed multiple issues with lesser-known wallets when connecting via wagmi that do not occur with wagmi 1.x
OKX Wallet

Once connected, disconnecting does not work

Trust Wallet

Attempting to connect results in an error

Link to Minimal Reproducible Example
https://stackblitz.com/edit/nextjs-apz8ps?file=app%2FProviders.tsx
Steps To Reproduce
With OKX Wallet - try to connect and disconnect
With trust wallet - try to connect
Wagmi Version
2.5.4
Viem Version
2.5.0
TypeScript Version
No response
Check existing issues

[X] I checked there isn't already an issue for the bug I encountered.

Anything else?
No response

Not sure if this is the same case with OKX Wallet, but looks like Trust Wallet doesn't implement removeListener, which is a required EIP-1193 event handling method. This would explain why it fails connecting here. This happens in v2 because we try to clean up some events that we didn't in v1.

@frankfka can you try wagmi@canary and see if it's fixed?

looks like Trust Wallet doesn't implement removeListener

I reported this in December, I'll reping them 🙈

@frankfka can you try wagmi@canary and see if it's fixed by 2a72214?

Nice! That worked for Trust, the OKX Disconnect issue is still there

What's the issue? Error message, etc. would be helpful.

What's the issue? Error message, etc. would be helpful.

There's no error, but disconnecting doesn't work:
https://github.com/wevm/wagmi/assets/31530056/e7b27ae2-1077-4424-babc-68e17f1f33e0

Works fine for me when connecting and disconnecting.
https://github.com/wevm/wagmi/assets/6759464/1c518697-039b-49a1-b11a-8c0a9bf236d7

Hmm that's odd.. I'm getting the behavior I sent in the stackblitz link

@frankfka this is happening for me as well w/injected. It fails in local and seems to be a wagmi.store issue. I'm not exactly sure what it is but it seems to happen more often non-deterministically when running several tabs with wagmi providers.
In production this never happens, or at least it never does after clearing cache and hard reloading hence why I think it's an issue with the local storage wagmi.store

Closing as fixed by https://github.com/wevm/wagmi/commit/2a72214a2901d6b6ddd39f80238aa0bd4db670a7 since I'm not able to reproduce.


HIVE-27209: Backport HIVE-24569 to branch-3: : LLAP daemon leaks file descriptors/log4j appenders

HIVE-24569: LLAP daemon leaks file descriptors/log4j appenders
Author: (Stamatis Zampetakis, reviewed by Jesus Camacho Rodriguez)
Closes apache/hive#1952

What changes were proposed in this pull request?

Based on ee4e1f3c3bdf8e644143f8039cbda55d97710461
But modified to exclude tests that require JUnit5 and minor changes in the constructor of
LLapRandomAccessFileAppender to account for the differences in the versions log4j.version.
Why are the changes needed?

This Backport was already done in branch-3.1 using this HIVE-24569 so we need to backport the same to branch-3.
Does this PR introduce any user-facing change?

How was this patch tested?

+1 LGTM

@vihangk1 and @sankarh Can you review this?

@guptanikhil007 Why test changes are not ported?

@sankarh This is ported from the original branch-3.1 cherry-pick not master.

https://github.com/apache/hive/pull/1952


HMR is not working under certain circumstances (difficult to pin point the exact context) / patching issue

Version
3.0.0-rc.1
Reproduction link
https://github.com/AlexandreBonaventure/vue-hmr-vfor-bug

Steps to reproduce
https://github.com/AlexandreBonaventure/vue-hmr-vfor-bug/blob/master/README.md
So with my team we've been noticing that in the last couple of vue/vite versions HMR was really not working anymore for us. Often times it gives cryptic errors in the console and difficult ro reproduce consistently. It is probably due to multiple reasons but I managed to isolate a bug at least. I had an insanely hard time to make a minimal repro out of it because it seems really flaky but on my machine this minimal repro is failing everytime.
So yeah, sorry you might see some stuff there that seems really randomly put but I swear, if you remove one single line the bug does not show anymore XD
Just this single bug makes HMR broken and unusable for us.
I can provide machine specific info if you guys can't reproduce.

Most likely caused by https://github.com/vuejs/vue-next/commit/5f61aa0f719cbd90182af1e27fad37b91c2c351e
What you can do now: specify vueCompilerOptioons: { hoistStatic: false } in your vite config.


map features master checkbox

Adds a master checkbox which selects/deselects all map features.
(closes #2904)

@bhousel review?

So, this code is awesome and does exactly what it was supposed to do... I really like what you did.
BUT, I thought about this some more and I'm going to add OpenStreetMap as a data layer here instead:

It makes more sense to me, post-#3001 layer refactor, and I want to reinforce the idea that OSM is just one of many layers that iD can support.
We have more projects now where people are starting to fork iD and swap out OSM for something else, and I think this signals to them conceptually the cleanest way to do it..


Adds Circe, Fetch and Monocle Libraries

Fixes https://github.com/scala-exercises/scala-exercises/issues/500
Fixes https://github.com/scala-exercises/scala-exercises/issues/497
Fixes https://github.com/scala-exercises/scala-exercises/issues/620
It includes libraries Circe, Monocle and Fetch.

Codecov Report

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

@@          Coverage Diff           @@
##           master    #630   +/-   ##
======================================
  Coverage    35.3%   35.3%
======================================
  Files          40      40
  Lines         946     946
  Branches       18      18
======================================
  Hits          334     334
  Misses        612     612

Continue to review full report at Codecov.

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


chore: Add missing create method to javadsl Graph

Motivation:
Add helper method for java dsl.
Result:
richer javadsl.

@pjfanning @mdedetrich Can we have this in 1.1.0-M1 release too ?


Missing "sort transactions by" in addresses with many transactions

When showing the transactions of an address we should allow the user to sort them by value or timestamp.

same issues as in #42


Issue #SC-963 chore: Update samza jobs for ingesting LOG events to druid

@anandp504 @sowmya-dixit @sunilpes Please review.

Please address the PR comments.

Changes has been made as specified.


This datetime string won't parse, and I have no idea why

>>> arrow.get('2016-03-01T07:45:12.6842351+00:00')
Traceback (most recent call last):
.
.
.
  File "/python_env/adt/lib/python3.5/site-packages/arrow/arrow.py", line 290, in __str__
    return self._datetime.isoformat()
ValueError: offset must be a timedelta strictly between -timedelta(hours=24) and timedelta(hours=24).

And yet this works fine (I just removed the right-most digit from the sub-seconds)
>>> arrow.get('2016-03-01T07:45:12.684235+00:00')
<Arrow [2016-03-01T07:45:12.684235+00:00]>

And so does this (the original string with one digit added to the sub-seconds):
>>> arrow.get('2016-03-01T07:45:12.68423510+00:00')
<Arrow [2016-03-01T07:45:12.684235+10:00]>

What's going on here?

FTR, I'm getting a different output:
>>> import arrow
>>> arrow.get('2016-03-01T07:45:12.6842351+00:00')
<Arrow [2016-03-01T07:45:12.000684+23:51]>
>>> arrow.get('2016-03-01T07:45:12.684235+00:00')
<Arrow [2016-03-01T07:45:12.684235+00:00]>
>>> arrow.get('2016-03-01T07:45:12.68423510+00:00')
Traceback (most recent call last):
  File "<input>", line 1, in <module>
    arrow.get('2016-03-01T07:45:12.68423510+00:00')
  File "/usr/lib/python2.7/site-packages/arrow/arrow.py", line 286, in __repr__
    return '<{0} [{1}]>'.format(self.__class__.__name__, self.__str__())
  File "/usr/lib/python2.7/site-packages/arrow/arrow.py", line 289, in __str__
    return self._datetime.isoformat()
ValueError: tzinfo.utcoffset() returned 1440; must be in -1439 .. 1439

Stepping thru the code, it appears that arrow.get() doesn't currently support strings that have more than 6 digits of sub-seconds.  However, it also doesn't raise any explicit errors when presented with these strings.  Instead, it treats the subsequent digits as the timezone offset.
To see this behavior, try running the last example that I presented in my first post:

arrow.get('2016-03-01T07:45:12.68423510+00:00')
<Arrow [2016-03-01T07:45:12.684235+10:00]>

Note that the resulting arrow object has an offset of 10, which is actually the last two digits of the sub-seconds.
Sometimes this results in errors, depending on what those remaining sub-second digits contain.  In any case, it's not likely what the caller wants, since those digits were not intended to be interpreted as a timezone offset.

I believe this is fixed in 0.9.0.
Please have a try.

Closing. Please reopen if it is still an issue


Add Group by and Having query support using Elasticsearch

Support for Groupby and Having queries should be enabled using elasticsearch

Fixed with Kundera -2.17 release.


unable to run the code

Hey Dorsk i hope your doing well ive tried to run the code but it always gives me a bug that looks something like this
from psutil import Process, process_iter, NoSuchProcess, ZombieProcess
ModuleNotFoundError: No module named 'psutil'
im pretty new into the github scene and it took me over an hour to figure out that all of this code runs on git bash lmao anyways if you have any resources for content that could help me to edit this code or be able to run id appreciate it i tried to email you but i couldnt find your email so sorry to bother you cheers!

 ModuleNotFoundError: No module named 'psutil'
Maybe you have to install this module
Try:
sudo pip install --upgrade psutil
I found the code from StackOverflow. Haven't tried.
If that doesn't work, try using python3.


Add isScratcher value to API

Uses my brand-new API! (It's so new, it doesn't even have a homepage yet... But it will once I set up express.static()!

Honestly I'd rather keep the logic for this on my vercel deployment - it would make things much faster.

Honestly I'd rather keep the logic for this on my vercel deployment - it would make things much faster.

Where is that? I couldn't find the user validation code.

Where is that? I couldn't find the user validation code.

https://github.com/webdev03/scratchinfo/blob/main/src/lib/getStatus.ts

Honestly I'd rather keep the logic for this on my vercel deployment - it would make things much faster. Maybe I should try node-html-parser and see how that goes again.

You can use my code. https://github.com/hello-smile6/isScratcher

I actually made one earlier.. but building game some "canvas" error

So, where is your authentication script? I couldn't find it.

Authentication is managed https://github.com/webdev03/scratchinfo/tree/main/src/routes/you/supa/scratchlight

#53


.NET Docs --> pin instrumentation versions to pre-1.4.x?

Hello @open-telemetry/dotnet-approvers - would like some of your guidance. Right now I'd like to stabilize the .NET docs w.r.t. packaging. Today, the code sample here is incorrect due to the changes to hosting: https://opentelemetry.io/docs/instrumentation/net/getting-started/#aspnet-core
But is it right to recommend this path, or use downgraded instrumentation and hosting packages to use a stable version of the base OTel package?

@CodeBlanch FYI.
We are going to have stable 1.4.0, along with Otel.Ext.Hosting stable pretty soon. (1-2 weeks or less).
We can wait for that (or the final RC before 1.4.0) and update all docs to use that ?

Unfortunately, no.
https://www.nuget.org/packages/OpenTelemetry/1.4.0-rc.3 was done ~5 days ago only (delayed), and if no issues found with this, we will be releasing stable. The general process is to give 2 weeks bake time after the last pre-release.
However, we can update the docs to use the rc.3 package - https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/examples/AspNetCore/Program.cs this should already be the working code example with rc3.


Improvements

Thanks for this module, I have the exact same use case.
As you pointed out in #1, it would be nice to have something a bit more "correct", so I copied in the documentation from the spec(s) and hacked up an implementation. It seems to work (at least for connections from node and chrome) and is about 20x faster. Review / suggestions welcome.
I mentioned it in the docs I added, but I think it would generally be wise to do some other checks to confirm that a given packet even looks like a client hello before using this module. I feel that those checks are out of scope though so I linked to another module (yes, of my authoring...) instead of including them here.
cc @jornane

Wow, awesome! I'll have a look through this as soon as I can and add you as a maintainer, if you like. :)

This is some stellar work! Maybe @jornane and @tellnes (author of sni-reader) would like to weigh in on this before merging?
I don't want to name squat and would be happy to add all you guys as collaborators / maintainers on npm, if you want to.

Hi @jessetane! Great work! I've quickly looked over your changes, you've done some serious cleaning.
I'll look into this in more detail shortly.

Ah I had not seen sni-reader! Search fail on my part... it looks like I may have duplicated some of @tellnes efforts... Maybe it is still worth having the standalone guts here?

@buschtoens thanks for adding me as a contributor, happy to help maintain here and on npm where my username should be the same.

I've went through your changes. It's good that the code no longer relies on regular expressions so simply find something that "looks like" a domain. However, your code lacks some checks that @tellnes sni-reader has. For example, it's possible to crash your code in the var sessionIdLength = data[pos]; line by having too few bytes in data.
As @jessetane mentioned in the documentation, this problem can be solved by checking the data first. But I think it's a bit dirty to have some of the checking in the sni-library and other checking in his own is-tls-client-hello-library.
Personally, I like @tellnes his approach better, where the library takes care of everything that's related to SNI-parsing, such as socket handling and validation. You can look at https://github.com/jornane/node-snip to see how I use sni-reader today.
I will leave the merge decision to @buschtoens.

@jornane thanks for the review. I still see the function of verifying the record and extracting the sni as separate things. And actually, if you look at the sni-reader source, you can see that these functions are split up internally:
https://github.com/tellnes/sni-reader/blob/master/index.js#L52-L74
https://github.com/tellnes/sni-reader/blob/master/index.js#L76-L172

It's definitely nice to have the sni-reader package that "does all the things", but having access to the little lego pieces is nice too (I don't need the stream handling stuff personally). Maybe not worth the effort, but maybe it would make sense to to compose sni-reader out of smaller modules?

@jornane also you are right about the sessionid length check - I added a commit to fix, thanks!

@buschtoens any objection to me going ahead and merging this?

@jessetane Nope, absolutely in favor! I also prefer the Lego approach. :wink:

This isn't really a feature addition or breaking change, but I think we can probably bump to 1.0.0 for release - if you add me on npm I can go ahead and publish as well.

You should already be added. :+1:

done and done, thanks!

Nah, thank you. :smile:

Hi. Thanks for mentioning me.
This implementation will still fail if the input is less bytes than where the SNI extension is found. That is the reason I'm handling the stream stuff in sni-reader. I'm first reading five bytes. The last two of them tells me how much more I need to read to be guaranteed to read enough.
Yes, the first data blob you receive from the stream api on the socket will probably include everything you need because it will probably be in the first tcp packet, but that is an implementation detail and not something the api guarantees.
Other that that, it looks great.


Debugger feature request - Display variables in tree format

This may be more than you want to do but maybe some day we can do this.

if you double-click on "ff" you'll get a full tree view of it, in gide.

Yes, I have been using that feature, not quite as good as getting all of your vars in a single tree but good enough.


Make HazelcastInstanceTest wait and verify new cluster member is shutdown

Pretty much the same fix as #5082 but with verifying the cluster member was shut down.
Hopefully it makes things more stable. I managed 100 JVM mode test runs without failure.

Nice work, thanks a lot @jamesnetherton!


Unable to complete kata

Having this problem in multiple katas. Both sample tests and final tests. I also see multiple users reporting this issue on the dashboard.

Even Test.expect(true) has red outline.

stderr is empty.

I have the same issue -- keep hitting "Attempt", it succeeds, but can't submit.

I also am having the same issue.

Same here
Tried reloading page, restarting browser, etc.

Same thing for me on the 2 different Katas I've tried in the last 30 mins.

Same here for every Kata done in the past 2 hours.

Looks like even preview.codewars.com is suffering from the same problem. I suspect it has to do with backend server problems.
Currently I'm watching the discourse and responding to new comments that talks about this issue. I hope @jhoffner will take care of the issue quickly :)

Same issue

Same here

same issue.

Same issue - happens on Linux and Windows, and on all browsers.

same issue

same here whether chrome or safari

same issue

I had thought there were some problems with my algorithm. I am not alone!

Same, please fix it ASAP.

same issue

username: wonderay
browser: chrome 57.0.2987.133
login: github

Happens here as well.
On macOS using Safari.

Same here

:(

same here :(

:(

Here also, Mac/Safari, Mac/Chrome, iPad/Safari, reload, log out, cache n cookie flush, etc

same here

Same for me!

+1

+1

Same Issue. - I am saving them all in Notepad until its fixed.

+1 - Same problem

Could it be Ably CDN ? Got warning message The Ably CDN URL you are using is deprecated because it does not contain a version number. Please see https://support.ably.io/solution/articles/3000063698 in the console. I'll install mockup proxy for verification.

Same problem with this kata: https://www.codewars.com/kata/collatz-conjecture-3n-plus-1/train/python
Time: 143ms Passed: 150 Failed: 0
Output window is bordered in red.
notify:
{success: true, data: null}
data:null
success:true
run:
result:{serverError: false, completed: false,…}
assertions:{passed: 4, failed: 0, hidden: {passed: 0, failed: 0}}
completed:false

+1 same here :(

+1

@clifflu: IIRC that was already happening in the past, so it shouldn't be the cause.

+1

+1

+1

+1

+1 - I'd really like to sign up and start the challenges! I can't get past the initial sign up test.

+1

+1

@lynmuldrow site is suffering from some problems. Try it again later.

+1 (happy Easter holidays)

+1

+1

+1

+1

+1

+1

+1

+1

+1

same :(

+1

same for me

Same issue, can't submit solution.

Well I guess, they can put a label : "URGENT NOT WORKING"

It is working again for me

It's now fixed! :D

I shouldn't have complain then. Good job! 👍

working for me as well :))

Thank you, @jhoffner!

[image: Inline images 1]
I am still experiencing problems. I don't think its fully restored yet ?
On 14 April 2017 at 16:06, Matthias Rahlf<EMAIL_ADDRESS>wrote:

Thank you, @jhoffner https://github.com/jhoffner!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Codewars/codewars.com/issues/893#issuecomment-294170028,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALVoKSAQi4k1NxG8O-IUTTLVm-npBISJks5rv4tugaJpZM4M9YBS
.

It was still happening for me but logging out and then logging back in again got it going.

@eastabrooka that looks like a different issue. May have been a server issue. Did you try to submit again?


Over segmentation of cells in samples with non-uniform cell geometry

Hi Baysor Team,
I am a new-ish user to the baysor tool and have a series of Xenium samples our group is trying to re-segment. After multiple iterations of config settings it seems that I have yet to find an optimal segmentation profile that dynamically handles diverse cell shapes. With that said, is there a setting I may have missed, or a proper way to handle segmentation in cases of non-uniformity? I have attached my config.toml below. (Note: the prior segmentation being referenced was generated via XeniumRanger).
Additionally, it appears my z_location is being removed from associated output files.
Thank you for your consideration.
`[data]
x = "x_location"
y = "y_location"
z = "z_location"
gene = "feature_name"
min_molecules_per_cell = 150
[segmentation]
prior_segmentation_confidence = 0.2
scale = 15
scale_std = "100%"
n_cells_init = 6456`

Hi @Riley-Grindle ,
That's a good question. scale_std, unfortunately, doesn't work as intended and in my tests its effect on the results was minor (if any). I'd try setting num. clusters to 10-15 and increase scale to be closer to the size of larger cells. Also, if your prior segmentation doesn't work well (which I assume because of confidence 0.2), you can switch to nuclei segmentation and set a higher confidence. It would help with undersegmentation.

Additionally, it appears my z_location is being removed from associated output files.

What about other columns? x/y_location and feature_name?

Disregard the last part of that query. The z_location is preserved in the transcript coordinates, and the cell/nuclei boundaries were never 3 dimensional to begin with.
Thank you for the suggestions! I will initiate a test run with some of these in mind and return with feedback.

Let me know how that works! If that helps, I'll add it to the documentation.

Do you have 3D data? If so, it's often impossible to create non-overlapping polygons in 2D.


Birth order and mother's maiden name

Is it possible to add birth order and mother's maiden name to the demographics of a patient?

Thank you for your prompt reply.
I'm trying to figure out how to add it to the patients.csv output.
Birth order should be represented with an integer (1-9), calculated from the date/time of the birth date/time

Hints to Implement
First, you would add the field to the CSV headers:
https://github.com/synthetichealth/synthea/blob/17e5584c2d95894dfafd6de323ccfabf5642c56f/src/main/java/org/mitre/synthea/export/CSVExporter.java#L291-L294
Next, you would add the data to each record:
https://github.com/synthetichealth/synthea/blob/17e5584c2d95894dfafd6de323ccfabf5642c56f/src/main/java/org/mitre/synthea/export/CSVExporter.java#L557-L624
The Problem
This should be fairly straight-forward for Mother's patient name: add Person.NAME_MOTHER to the list of exported fields.
Unfortunately, things get a little more complicated for birth order. That is because we do not simulate that level of detail, so each person does not have a birth order.
So, you have two choices.

Simulate birth order (the details of which are beyond the scope of this post)
Pick a birth order randomly from some non-uniform distribution.

Thank you!  This has been very helpful to solve the problem and to understand Synthea a lot more.


App is crashing when I navigate back to MenuViewController.

AI and AI player mode, app is crashing when I navigate back to MenuViewController. How to stop the AI action when the ViewController dismiss.

Hi @SuneelGunupudi - Sorry this has taken me such a long time to get around to, but better late than never!
I've fixed this now, in version 1.1.2.


Version 5.3.0 java.lang.ClassCastException: org.glassfish.json.JsonStringImpl cannot be cast to javax.json.JsonObject

Run scan against React project (Node).
Version used 5.3.0. CLI
Log file
[WARN] An unexpected error occurred during analysis of 'package.json' (Node.js Package Analyzer): org.glassfish.json.JsonStringImpl cannot be cast to javax.json.JsonObject
[ERROR]
java.lang.ClassCastException: org.glassfish.json.JsonStringImpl cannot be cast to javax.json.JsonObject
at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.processDependencies(NodePackageAnalyzer.java:287)
at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.analyzeDependency(NodePackageAnalyzer.java:262)
at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131)
at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88)
at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Can you provide a package.json/package-lock.json that causes this behavior?

Yes @jeremylong
sorry for the delay
package.zip

I'm unable to re-produce this.  I downloaded and unzipped the package.zip and then ran:
npm install --package-lock
dependency-check.sh -s . -o .

No errors occur. I'm using a mac and my java version:
java -version
openjdk version "1.8.0_212"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_212-b03)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.212-b03, mixed mode)

We might have a solution to this based on an answer on SO.

When will this fix be released?

Hey @jeremylong, do you have an ETA on Version 5.3.1?  Can we support you?

downgrading to 5.2.2 seems to resolve the problem.

Sorry for the delay - 5.3.1 was released today.

Did the 5.3.1 release fix it for anyone? Because I still seem to get it

@els-hansenj as I've stated above - I'm unable to reproduce this on my machine. Any chance you can provide a new example (package.json, package-lock.json), the version of Java being used, etc.?

Hi Jeremy,
I don't have a package-lock.json, maybe that is part of the problem? It does write this in the log "No lock file exists - this will result in false negatives; please run npm install --package-lock" but figured it wasn't that important
It's running on Jenkins (2.204.5) with the 5.1.1 version of the plugin and the 5.3.0/5.3.1 version of the dependency checker. It works fine with version 5.2.2 as noted earlier.
The JVM version is 1.8.0_211-b12
Let me know if you need more information
/Jacob
package.zip

I just ran into this issue with our Gradle project.
In one of our packages the build fails because of this error. When I then manually create a package.lock file with the npm install --package-lock-only command and run the dependency-check again it seems to pass the module and goes on without issue.
The thins is. We do not use npm but rather we use yarn. Our project generates a yarn.lock file.
Npm is doing some great work to get the same advantages as yarn but for the moment we still would like to use yarn. We might switch back to npm in the future but I thinks it's crucial for this module to also start supporting yarn.lock files

Hi @jeremylong , @Shuyinsama and @els-hansenj ,
I testen the Version 5.3.1 top and I ran n this issue too.
But with me it‘s the same as with @Shuyinsama : I use yarn and not npm. And the Error is different to the one reported in this ticket. @jeremylong I think this bug is solved.
@Shuyinsama we should open a feature request supporting yarn.lock. There is a node module which can convert a yarn.lock to a package-lock.json - maybe this can be used.

@sfxn the error in this post is exactly my error. Using 5.3.1
So no I don’t think this should be closed.
As for introducing a extra package. That would be weird. I could just add a extra dtep in our pipeline that would run npm install —package-lock-only
But i’d rsther prefer this plugin to support yarn

Hey Patrick, then it was a misunderstanding as your comment followed the one of Jacob who reported a different problem so I thought you had the same (new) Problem as Jacob.
Regarding yarn: there is already an open feature request 1416 for yarn and yes, I'd be happy too. I'm not that deep into npm and yarn, just supporting my team with the ci-servers (Jenkins) and secuity-checks we usually do for java projects; we want to adapt it for our angular project, so I ran into the "java.lang.ClassCastException" while adopting the checks - we had no previous projects unsing this plugin, so I cannot provide a comparison "it worked with 5.2.2 but not with 5.3.X"
I'm already out of office for today, so I'll check the plugin output tomorrow and will provider further information if I still can reproduce the problem or if I now have a new situation.
With 5.3.0 I got the ClassCastException, with 5.3.1 I ran into the "No lock file exists" which sounded to be a new/different problem.
Bastian

@sfxn No problem. We also run a multi-module project where we have 5 modules. One of which is a angular 7 application. This is also the module where this dependency fails.

5.3.2 same problem.

Any chance someone can provide a re-create? I'm not able to re-produce this error.

@jeremylong I made a sample project which loosely resembles our own project in terms of setup.
I have 2 Gradle modules one is a simple spring boot project generated with https://start.spring.io/
Then I added a second module generated with ng new command of @angular/cli.
We use the https://github.com/node-gradle/gradle-node-plugin plugin to download node and yarn locally and use that for installing. We have a yarn.lock and not a package-lock.json
Basically you can run the following command from the root directory
./gradlew eDC

or
./gradlew executeDependencyCheck

This will result in the following error:
Verifying dependencies for project dependency-check-node-issue
Checking for updates and analyzing dependencies for vulnerabilities

No lock file exists - this will result in false negatives; please run `npm install --package-lock`
An unexpected error occurred during analysis of '/Users/patrick/IdeaProjects/dependency-check-node-issue/sample-project-angular/package.json' (Node.js Package Analyzer): class org.glassfish.json.JsonStringImpl cannot be cast to class javax.json.JsonObject (org.glassfish.json.JsonStringImpl and javax.json.JsonObject are in unnamed module of loader org.gradle.internal.classloader.VisitableURLClassLoader @1073fe27)

java.lang.ClassCastException: class org.glassfish.json.JsonStringImpl cannot be cast to class javax.json.JsonObject (org.glassfish.json.JsonStringImpl and javax.json.JsonObject are in unnamed module of loader org.gradle.internal.classloader.VisitableURLClassLoader @1073fe27)
        at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.processDependencies(NodePackageAnalyzer.java:287)
        at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.analyzeDependency(NodePackageAnalyzer.java:262)
        at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131)
        at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88)
        at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:834)

Thanks @Shuyinsama

I have the exact same issue.  Dropping from 5.3.2 to 5.2.2 resolved it.

@Shuyinsama If I understand correctly, the error come from the fact you doesn't have a package-lock.json ?
Any npm-shrinkwrap.json maybe ?
In my opinion, your bug is, that dependency-check try to processDependencies, and need to stop before (if file doesn't exist) .
And FYI, dependency-check doesn't support yarn.lock for the moment, and some functionnalities from yarn can "break" npm (like using an alias).
Maybe someone have a package-lock.json (or npm-shrinkwrap.json) producing this errors ? So I can try ?
@jeremylong I'm here because of your update https://github.com/jeremylong/DependencyCheck/commit/8f1f5663e48d57cb77dd9af722a8ab62f6c808c6
Doing this, sometimes version will contains quotes ...

In my opinion, if the bug doesn't come from here, it's better to revert to jo.getString("version"); .
( I'm actually digging in the NodePackageAnalyzer, because of bugs with yarn, npm, alias, local submodules, generating package-lock.json from yarn.lock .... So, I think I can try to handle this, if linked with the NodePackageAnalyzer )

I use pnpm instead of npm, and I have pnpm-lock.yaml committed instead of package-lock.json.. Running into the same issue.

I use pnpm instead of npm, and I have pnpm-lock.yaml committed instead of package-lock.json.. Running into the same issue.

Only package-lock.json or npm-shrinkwrap.json is read. Else it use the package.json .

I use pnpm instead of npm, and I have pnpm-lock.yaml committed instead of package-lock.json.. Running into the same issue.

Only package-lock.json or npm-shrinkwrap.json is read. Else it use the package.json .

Thanks, I did a workaround by separating the OWASP dependency check from normal application build (which uses pnpm) and running npm install --package-lock --production specifically for the dep check step.

Hey, is there an estimated release date for 6.0.0? Apparently 5.4.0 was renamed to 6.0.0, right?

Sorry about the delay in getting 6.0.0 released.  There are still two breaking changes that I need to get implemented. Unfortunately, a different project is taking a bit longer than expected. I hope to be back to this shortly and finish the two breaking changes so we can get this patch released.

I get this error on a Java project. Weird. A part of the error -
Checking for updates and analyzing dependencies for vulnerabilities

No lock file exists - this will result in false negatives; please run `npm install --package-lock`
An unexpected error occurred during analysis of '/var/folders/fg/55xcrj215gs2n9gnpz4077y40000gq/T/dctemp8b096f47-b387-4847-96b1-aacc7ad56355/check5333087062372066136tmp/91/package/package.json' (Node.js Package Analyzer): class org.glassfish.json.JsonStringImpl cannot be cast to class javax.json.JsonObject (org.glassfish.json.JsonStringImpl and javax.json.JsonObject are in unnamed module of loader org.gradle.internal.classloader.VisitableURLClassLoader @36f4dc9e)

java.lang.ClassCastException: class org.glassfish.json.JsonStringImpl cannot be cast to class javax.json.JsonObject (org.glassfish.json.JsonStringImpl and javax.json.JsonObject are in unnamed module of loader org.gradle.internal.classloader.VisitableURLClassLoader @36f4dc9e)
        at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.processDependencies(NodePackageAnalyzer.java:287)
        at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.analyzeDependency(NodePackageAnalyzer.java:262)
        at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:131)
        at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88)
        at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
        at java.base/java.lang.Thread.run(Thread.java:832)

> Task :dependencyCheckAnalyze FAILED

FAILURE: Build failed with an exception.

Gotta dig in. Maybe disable the Node analyzer

How about don't make dependency check fall over if it errors like this? It shouldn't be this brittle


bump console version to v1.0.3 that remove pkg/errors

bump console version to v1.0.3 that remove pkg/errors from their vendoring
xref: https://github.com/containerd/console/issues/56
Signed-off-by: Zou Nengren<EMAIL_ADDRESS>

/cc @AkihiroSuda @estesp

CI is claiming that some go.sum changes weren't included
  These files were modified:

   M go.sum


Fix for fs2 snapshot update

Current coverage is 100.00%

Merging #77 into master will increase coverage by +0.20% as of 047e0da

@@            master     #77   diff @@
======================================
  Files           16      16
  Stmts          516     516
  Branches        56      56
  Methods          0       0
======================================
+ Hit            515     516     +1
  Partial          0       0
+ Missed           1       0     -1

Review entire Coverage Diff as of 047e0da

Powered by Codecov. Updated on successful CI builds.


DefaultChannelGroup has Executor, but relies on EventExecutor when closing channels

Hi,
DefaultChannelGroup has it's own Executor, although, when Channel is closed in DefaultChannelGroup::close, it relies on EventExecutor from the Channel itself.
I understand that it might be very well by design (since Channel already has it's own executor), just wanted to point it out (after finding a couple of issues that are related to closing the worker in parallel or out of order with channel group) that several people have stumbled on that :)
Do you think it'd be useful to shutdown Channel from the Executor that is owned by DefaultChannelGroup to make it a bit more obvious? I realise it's impossible to work around every case where user is not attentive enough tho.
Thank you.

@ifesdjeen the EventExecutor is only used to notify the ChannelGroupFuture. I will do a javadoc update to clarify it.

Yup, I know. It's just a bit counter-intuitive. I should've said that documenting it could be a better idea.

@ifesdjeen actually it is already in the javadocs:
Creates a new group with a generated name and the provided {@link EventExecutor} to notify the {@link ChannelGroupFuture}s.

Oh... somehow I have missed that. Sorry and thanks!


Tweak tests and update README for lodash 3.0 - closes #15

Don't Merge
This PR needs to be updated once<EMAIL_ADDRESS>is published.  The travis.yml will need to be updated to test that version.

Rock reviewed!


Add SNS SubscribeV1 for new pattern support

@Admiral-Piett There are a few of comments but totally looks good! I will start to modify my CreateTopic PR to merge with this branch 👍


Localize and translate the main menu

It is possible (and desirable) to translate the main application menu (menu.js).
The idea is:

create a new localize.js (or i18n.js, ...). No more than 20 LoC (lines of code);
create some new files: en.js, fr.js, de.js, ..., containing the key: value translations;
English will be the fallback language;
add the glue code (a few lines changes only in menu.js).

If this new feature can be accepted, I'm planning to submit a patch.
[edit]
https://github.com/sindresorhus/anatine/compare/master...claudioandre:i18n?expand=1

Thanks for the suggestions, but not something I'm interested in. This project is done.  Sorry. Would be better to fork and release it as a different app.


From bare-metal-to-Kubernetes

Great article explaining how Betabrand, a clothing company migrated its infrastructure from Rackspace to Kubernetes.!

interesting


Use fonts from u8g2

U8g2 has a pretty big collection of fonts. It would be great to have support for them in embedded-graphics. This issue is a tracking issue of sorts to define what should be done as a minimum first step towards u8g2 font support.
Any code that aims to close this issue should:

Reuse as much u8g2 tooling as possible
Treat the u8g2 repository as the source of truth for fonts (no mirrors, etc)
Create embedded-graphics compatible font maps like the .raw files here.

The first implementation will be non-ideal, but will show where things can be fixed or improved with more optimisations and tooling in the future.
CC also #28 for some desired future features.

I think this can be closed as outdated. See https://github.com/jamwaffles/embedded-graphics/issues/28#issuecomment-490886600 for more fresh solution.

I like to contribute and make more fonts available, since I like to use a bigger font in my personal project. However, I still have no clue where to start implementing a new font.
Can one of you please give me a clear explanation on what steps to take so I can start working on implementing new fonts.
@jamwaffles @puzrin

Hi, thank you for contributing! The fonts story is pretty poor right now, but the current bitmap fonts use a black and white font image (example) that's converted to a 1BPP (8 pixel values per byte) image using this Imagemagick command (untested, YMMV):
convert font.png -depth 1 gray:"font.raw"

You can then use the FontBuilder to build a font that samples characters from the image. I'd suggest looking at the existing fonts like Font6x8 for a starting point. Hope that helps!

@dutchmartin I'd suggest you to carefully inspect this project & spec https://github.com/littlevgl/lv_font_conv and use it's binary format. It implements storage level with care about all known issues in embedded.
Better thing can be only direct TTF rendering (but that increase RAM requirements significantly).

I'm gonna close this issue as it's pretty stale. @dutchmartin please open a PR or another issue if you need more help and I'll do what I can.

Please see https://github.com/jamwaffles/embedded-graphics/issues/28#issuecomment-524076670 for a possible future direction.


Adds note Search-AzGraph defaults to Subscriptions

Added a note about how Search-AzGraph defaults to Subscriptions in the default context.
Also, added a one-liner to make it search across all the subscriptions using PSDefaultParameterValues.

@DexterPOSH : Thanks for your contribution! The author, @DCtheGeek, has been notified to review your proposed change.

@jborsecnik : Thanks for your contribution! The author, @DCtheGeek, has been notified to review your proposed change.

@DCtheGeek Thank you.


How did you set up your outline's postition?

sorry i'm new to neovim, and i've searched through your nvim config but didn't find where is it set and encoutered error when derectly open nvim with your config.

Yeah, you should not just use my config. I did not make it to be used like that.
Just use LazyVim.
The outline positioning etc is done by edgy.nvim


fix incorrect results for group averaging with missing data

Description
This PR fixes an issue that leads to incorrect results for group averaging with missing data; the PR ensures that these data points receive no weight when averaging.

Closes #319

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

If applicable:

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass with my changes (locally and CI/CD build)
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have noted that this is a breaking change for a major release (fix or feature that would cause existing functionality to not work as expected)

Codecov Report

Merging #320 (428675f) into main (afd7a82) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #320   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           14        14
  Lines         1191      1201   +10
=========================================
+ Hits          1191      1201   +10

Impacted Files
Coverage Δ

xcdat/temporal.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Thanks for opening this PR. FYI, I realized I won't have time to review this until next week.


Regarding the MIT License

Hi, I was reviewing the license terms for this repository in order to use it for my project and noticed that it is distributed under the MIT License. However, I see that this project uses the SwissEphNet, which is licensed under the GPL-2.0.
The GPL-2.0 license requires that any derivative work must also be distributed under the GPL-2.0 license unless you have purchased a professional license from "Swiss Ephemeris" team. Could you please confirm whether the MIT license is appropriate for this repository?

Good observation
On Tue, Jul 9, 2024 at 2:21 PM Saravana Kumar @.***>
wrote:

Hi, I was reviewing the license terms for this repository in order to use
it for my project and noticed that it is distributed under the MIT License.
However, I see that this project uses the SwissEphNet, which is licensed
under the GPL-2.0.
The GPL-2.0 license requires that any derivative work must also be
distributed under the GPL-2.0 license unless you have purchased a
professional license from "Swiss Ephemeris" team. Could you please confirm
whether the MIT license is appropriate for this repository?
—
Reply to this email directly, view it on GitHub
https://github.com/VedAstro/VedAstro/issues/136, or unsubscribe
https://github.com/notifications/unsubscribe-auth/BC6RRIC3HXYU5MFP74EZP43ZLQZ2HAVCNFSM6AAAAABKTPEDW2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4TQOJZGE2TINY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Deprecation use of Reopening the Ember.Component super class

Bellow deprecation warning appears on console:
"Reopening the Ember.Component super class itself is deprecated. Consider alternatives such as installing event listeners on the document or add the customizations to specific subclasses. [deprecation id: ember.component.reopen]"

see https://github.com/simplabs/ember-test-selectors/issues/709, this has been fixed in v5.3.0 with a config option, and fully fixed in v6.0.0


Some new actions! :)

Oh awesome! I will have a look through later on and have a play, thank you @tallguyjenks - the YouTube one definitely looks super interest 💪

@eddiejaoude if you want to see it live I have the article, youtube, and GH activity all on my profile repo https://github.com/tallguyjenks/tallguyjenks

Thanks @tallguyjenks 👍

Stalebot lets keep this for now please 🤓

Not sure we want all these changes just yet. We can bring them in as we use them

@eddiejaoude still blocked? lol i have a few more actions too now there's so many good ones

hey @tallguyjenks I am blocked on other stuff and this one is slowly moving down my list 😢 . Oh feel free to append the new actions to this PR?

Since this PR has not been updated/discussed in a while, I am curious why didn't Stale bot interfere.

@tallguyjenks From the PR pattern I think you've made the PR to the wrong repo, this repo is about GitHub Actions and you've added stuff relevant to a github profile readme.
@eddiejaoude I think this PR can be closed 🙂

they were just example actions for others to grab and use, not something I meant to actually run on the repo. by itself, the things affecting the readme wouldn't function without the right HTML comments placed in the readme anyhow.

they were just example actions for others to grab and use, not something I meant to actually run on the repo. by itself, the things affecting the readme wouldn't function without the right HTML comments placed in the readme anyhow.

but they shouldn't be in .github/workflows any ways 😓


Add Sentinel Plugin Test To soul-plugin

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #819 (a126650) into master (8bb2e9b) will increase coverage by 0.16%.
The diff coverage is n/a.

Continue to review full report at Codecov.

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


various improvements

:tada: This PR is included in version 1.3.32 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add description to schema properties in codegen

[off-topic] Do you know how/if we can retrieve this description from the API?
I don't see it so far 😢

Originally posted by @fabien0102 in https://github.com/xataio/frontend-next/pull/753#discussion_r860616266

🙄 I'm not using the client-ts in the screenshot, I think the description is not exposed at the openapi level 😇
https://github.com/xataio/openapi/blob/dacf601a1723c944cad0fd8f60f8f20cdf252ecb/bundled/openapi.yaml#L3233-L3269

https://github.com/xataio/openapi/issues/129

Still good to also track it here 😄


Fix for index.md# Links

See "you might need to enable file sharing" link at /docker-for-mac/troubleshoot/#volume-mounting-requires-file-sharing-for-any-project-directories-outside-of-users on Netlify

The link to check is near https://deploy-preview-3981--docker-docs-vnext-engine.netlify.com/docker-for-mac/troubleshoot/#recreate-or-update-your-containers-after-beta-18-upgrade

@johndmulhausen LGTM, tested:
Anchor links ...

from non-index.md to index.md
from non-index to non-index
from index-to-index
from index to non-index

Thanks for the testing, y'all! :+1: Be on the lookout for any weird anchor link behavior.


inconvenience - no easy way to rebuild plugin dependencies

when upgrading node versions sbot cant run because plugin modules are compiled against my old version this is a pain 😅 maybe i'll come up with something before then but it would be nice if this was fixed

oh woops wrong repo my bad y'all 😅

for modules installed via sbot plugins.install, you could do cd ~/.ssb && npm rebuild that should do it.


Added casts properties to all models, re-ordered model properties

Should fix #916

Shouldn't this go to 1.2 since it's a bug fix?

1.2.1 I guess...

Rebased and tests do pass.

Rebased and tests do pass.

Still failing?

Hmm, leave it with me.

This actually fixes the tests too, since they weren't comparing integers.

:+1:


Add new admin rest service to change destination of config files

This enhancement adds a new REST call to the admion servers so that it is possible to switch the config document store to a different file location, or to change the connector to store the configuration documents in a completely different type of store.

The URL for the new connection is: .../open-metadata/admin-services/users/{userId}/stores/connection.  There is no validation for the userId but it is there as a placeholder so that a consuming product can link this into their security mechanisms

The connection is held in memory.  If the server is restarted it reverts to using the file store connector.

Another subtlety is that the file store connector uses a different file for each server.  This is switched automatically if the server name in the url changes.
If the connection/connector is overridden with the new API request then the same connector is used for all subsequent admin calls.  The connector can retrieve the server name from the OMAGServerConfig object.

To check the setting of the overridden connection use a GET ../open-metadata/admin-services/users/{userId}/stores/connection.  It returns either a connection object or a null if the default file-based connector is to be used.

Merged into master using pull request https://github.com/odpi/egeria/pull/288


Move non-payment-method-specific settings into dedicated "KOMOJU" tab

My ultimate goal right now is to make each KOMOJU payment method a separate WC gateway.
Currently, there is just one "KOMOJU" gateway that contains options for each actual payment method. This causes a handful of problems, including

poor interop with other plugins (e.g. payment gateway filtering plugins) and
confused customers, not knowing what a KOMOJU is.

This PR doesn't quite achieve the end-goal of one gateway per payment method. This PR just moves settings that would apply to all payment methods into a dedicated KOMOJU settings tab.

How to test

Follow the dev setup guide if you don't already have a WC store set up
Make sure you're using this branch
Go to your store settings
See the "Komoju" tag (in a future PR, we should change all "Komoju" texts to "KOMOJU")
Confirm that you can update your api key and other things from here

@FTLam11 can you help us review this PR, please?


Nodes getting cordoned and deleted as soon as they starts

Version
Karpenter Version: 0.20.0
Kubernetes Version:v1.22
Expected Behavior
Expected behaviour is to get pods scheduled on nodes
Actual Behavior
INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "f60dacd", "provisioner": "spot-karpenter-nodes-arm64", "launched-instance": "", "hostname": "", "type": "c6gd.medium", "zone": "ap-south-1a", "capacity-type": "spot"}
INFO	controller.interruption	deleted node from interruption message	{"commit": "f60dacd", "queue": "bms-eks-sit", "messageKind": "StateChangeKind", "node": "", "action": "CordonAndDrain"}
INFO	controller.termination	cordoned node	{"commit": "f60dacd", "node": ""}

INFO	controller.termination	deleted node	{"commit": "f60dacd", "node": ""}
Steps to Reproduce the Problem
Install Karpenter, Add provisioners and aws-node template
Resource Specs and Logs
--- apiVersion: karpenter.sh/v1alpha5 kind: Provisioner metadata:   name: spot-karpenter-nodes-arm64 spec:   annotations:     karpenter.sh/do-not-consolidate: "true"     karpenter.sh/do-not-evict: "true"   requirements:     - key: "kubernetes.io/arch"       operator: In       values: ["arm64"]     - key: "karpenter.sh/capacity-type"       operator: In       values: ["spot"]     - key: node.kubernetes.io/instance-type       operator: In       values:         - c6g.medium         - m6g.medium         - t4g.small         - c6g.large         - t4g.medium         - c6g.xlarge     - key: "topology.kubernetes.io/zone"       operator: In       values: ["ap-south-1a"]   taints:     - key: "arch"       value: "arm64test"       effect: "NoSchedule"   limits:     resources:       cpu: "100"       memory: 100Gi   providerRef:     name: default   ttlSecondsAfterEmpty: 500
--- apiVersion: karpenter.k8s.aws/v1alpha1 kind: AWSNodeTemplate metadata:   name: default spec:   subnetSelector:     karpenter.sh/discovery: <>   securityGroupSelector:     karpenter.sh/discovery: <>   blockDeviceMappings:     - deviceName: /dev/xvda       ebs:         volumeSize: 30Gi         volumeType: gp3         iops: 3000         encrypted: true         deleteOnTermination: true         throughput: 125   instanceProfile: <profile name created>
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

@Avani231194 Can you share the instance ID or the node name of the launched instance that is getting terminated? This instance ID should appear further up in the logs if you could share those.

@jonathan-innis  Thankyou for response.
Instance ID : i-03c6a154bacfb375f

@Avani231194 Looking at the logs internally, it looks like you are trying to create an encrypted device volume but do not have the permission to access the encryption keys, which is causing instance start to fail and the instance to go immediately into a terminating state.
Typically, encryption settings might be region/account-wide so can you check if EBS encryption is set by default in the region/on the account?

Hey @jonathan-innis
We do not have  EBS encryption set by default, not sure if Karpenter expects it.
 aws ec2 disable-ebs-encryption-by-default  {     "EbsEncryptionByDefault": false }
Also, I tried removing EBS Volume block from aws-node-template.yaml, but didn't help

Hmmm, do you have another instance ID after launching with the EBS encryption disabled. There may be a different error that is plaguing you now.

Hey @jonathan-innis
I tried again without EBS, but the issue seems to be same.
Instance ID : i-0ceccec5bb82fa390
Ref : AWSNodeTemplate.yaml
--- apiVersion: karpenter.k8s.aws/v1alpha1 kind: AWSNodeTemplate metadata:   name: default spec:   subnetSelector:     karpenter.sh/discovery: <CLUSTER NAME>   securityGroupSelector:     karpenter.sh/discovery: <CLUSTER NAME>
2022-12-21T04:03:08.761Z	INFO	controller.provisioner.cloudprovider	launched new instance	{"commit": "f60dacd", "provisioner": "spot-karpenter-nodes-arm64", "launched-instance": "i-0ceccec5bb82fa390", "hostname": "", "type": "c6gn.medium", "zone": "XXXXXX, "capacity-type": "spot"} 2022-12-21T04:03:10.091Z	INFO	controller.interruption	deleted node from interruption message	{"commit": "f60dacd", "queue": "bms-eks-sit", "messageKind": "StateChangeKind", "node": "ip-10-27-30-252.ap-south-1.compute.internal", "action": "CordonAndDrain"} 2022-12-21T04:03:10.135Z	INFO	controller.termination	cordoned node	{"commit": "f60dacd", "node": ""} 2022-12-21T04:03:10.289Z	INFO	controller.termination	deleted node	{"commit": "f60dacd", "node": ""}

Hi @jonathan-innis
One more thing that I found in CloudTrail logs is, the event "AttachNetworkInterface" is not getting triggered, or it is failing to attach an interface to pod.

Hey @jonathan-innis  We were able to launch nodes.
Standalone pods are getting scheduled, but  when added a side car going into crashloop backoff as sidecar is unable to run

Still looking into this one internally. Are you saying that you are no longer observing the issue?

@jonathan-innis  Yes, that issue seems to be resolved.
Other one that we are facing now is on one same node, some of the pod will go in running state and for the same application some will go in to crashloopbackoff

@Avani231194, that sounds like it may be unrelated to Karpenter since it's related to the container running successfully or erroring out. I'm going to close this since you say that you are no longer observing the issue.
Feel free to re-open if you begin observing it again.


docs: make ThemedImage example work out of the box

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[ ] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

It would be great if the simple examples are Copy@Pasteable to work. No big deal to look up the import statement for the missing useBaseUrl, but i think it would be handy to have it there.
Test Plan

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/
Related issues/PRs

thanks 👍


v0.8.3 release

Tetragon release checklist

[x] Check that there are no release blocker issues or release blocker pull requests.

ignoring https://github.com/cilium/tetragon/pull/496 this dockerfile is for building arm clang.

[x] Set RELEASE environment variable. For example, if you are releasing v0.8.1:
export RELEASE=v0.8.1

[x] Open a pull request to update the Helm chart version:
git checkout -b pr/prepare-$RELEASE
./contrib/update-helm-chart.sh $RELEASE
pushd install/kubernetes
./test.sh
popd
git add install/kubernetes/
git commit -s -m "Prepare for $RELEASE release"
git push origin HEAD

https://github.com/cilium/tetragon/pull/498

[x] Once the pull request gets merged, create a tag for the release:
git checkout main
git pull origin main
git tag -a $RELEASE -m "$RELEASE release" -s
git push origin $RELEASE

[x] Go to Image CI Releases workflow and wait for the release image build to finish.
- Get approval for your release build workflow from a Tetragon maintainer
- https://quay.io/repository/cilium/tetragon?tab=tags
- https://quay.io/repository/cilium/tetragon-operator?tab=tags

[x] When a tag is pushed, a GitHub Action job takes care of creating a new GitHub
draft release, building artifacts and attaching them to the draft release. Once
the draft is available in the releases page:

[x] Use the "Auto-generate release notes" button to generate the release notes.
[x] Review the release notes and click on "Publish Release" at the bottom.

[x] Publish Helm chart
- Follow cilium/charts RELEASE.md to publish the Helm chart: https://github.com/cilium/charts/pull/32
- Once the pull request is merged and the chart is published, go to cilium/charts GKE workflow and wait for the
CI run to pass.

completed. i'll follow up with https://github.com/cilium/tetragon/pull/489 to update README.md


Create zh_CN.lang

Thanks for contributing!
I added another string in a recent PR for formatting progress, would you mind localizing that as well?
https://github.com/timrwood/roost/pull/10/commits/6666faee00fc434d8ebfdd6f5a20651fd08c5eed#diff-722dccd83b1e6f06508263782c389560R9


Switch datasets type to a list of datasets

Following a suggestion from @julien-c to update the datasets tag in ModelCardData from Optional[Union[str, List[str]]] to Optional[List[str]] so we get a YAML block like
datasets:
  - "IMDB"

rather than
datasets: "IMDB"

The changes here are just changing the types and doc strings, and there isn't any checking of what the user passes. This is consistent with existing behaviour, but happy to add this check if we want to enforce this type on the user.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

just a note that we allow both string and array of string on the server side (it is validated there) but string is more for backward compat.
I think it's nicer UX if we always use array of string going forward

Thanks for opening a PR @davanstrien! Agree on using only 1 type.
What about metrics, tags and models ? (both in DatasetCardData and ModelCardData). I think we should align for consistency except if there is a specific reason why we would like to support them differently.

Thanks for opening a PR @davanstrien! Agree on using only 1 type. What about metrics, tags and models ? (both in DatasetCardData and ModelCardData). I think we should align for consistency except if there is a specific reason why we would like to support them differently.
EDIT: Too late 😄

Sorry! Can open a separate PR for this if you think it's nicer to make it consistent?

Oops i should have mentioned to wait for @Wauplin to approve, my bad
non-string array tags wouldn't be allowed server side anyways


Disallow ambiguous color descriptors in the light.turn_on schema

Description:
There are quite a lot of different ways to specify colors and making them mutally exclusive seems simpler than making rules of precedence.
Strictly speaking, this is a breaking change: previously you could have an XY and an RGB light in a group and make one light red and the other one blue with a single service call. I don't think losing that ability will be an issue. Also, profiles can no longer have their xy-value overwritten, only the brightness. Again – not a real loss.
The real breaking change is that it will now point out some configurations that have previously been ambiguous or redundant.
I have pooled color_temp with the color-setting ones because I think it should imply a white color.
The white_value is not included due to it being separate from all the others. In an RGBW light, the white_value affects the W while all the others affect the RGB.
Opinion can probably differ on the above points and I am prepared to adjust given some sensible arguments :)
Breaking change notice: The light platform will now refuse turn_on calls that specify redundant or ambiguous colors, such as using both color_name and color_rgb in the same call.
Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

I'm torn about color_temp and would like agitated feedback :)


Empty target .NETCoreApp3.0 in 4.2.0 nuget package.

Hello,
The System.Reactive Nuget package contains a target for .NETCoreApp3.0, but the target is empty.
Apparently MSBuild seems able to cope correctly with that and automatically switches to .NetStandard2.0 for .NETCoreApp3.0 projects.
However, our project use Nuget.Commands to restore Nuget packages as part of an update mechanism and as a .NETCoreApp3.0 target exists, it selects it instead of .NetStandard2.0 and fails to find System.Reactive.dll
Is it expected?

Indeed the system.reactive.4.2.0.nupkg is missing files in its netcoreapp3.0 directory, however, there are other directories with 3.0 content.

Ok, I think I understand now: The provided targets file switches between the  netcoreapp3.0 version in build or the netstandard version depending if we are running with WPF or not.
<Project>
  <PropertyGroup>
    <UseWindowsRxVersion Condition="'$(UseWpf)' == 'true' OR '$(UseWindowsForms)' == 'true'" >true</UseWindowsRxVersion>
    <UseWindowsRxVersion Condition="'$(UseWindowsRxVersion)' == '' " >false</UseWindowsRxVersion>
  </PropertyGroup>
  <ItemGroup>
    <Reference Condition="'$(UseWindowsRxVersion)' == 'true' "  Include="$(MSBuildThisFileDirectory)..\..\build\netcoreapp3.0\System.Reactive.dll" />
    <Reference Condition="'$(UseWindowsRxVersion)' != 'true' "  Include="$(MSBuildThisFileDirectory)..\..\lib\netstandard2.0\System.Reactive.dll" />

    <FrameworkReference Condition="'$(UseWindowsRxVersion)' == 'true' " Include="Microsoft.WindowsDesktop.App" />
  </ItemGroup>
</Project>

I understand the need, I'm pretty sure the only way to make that work is to use msbuild to restore.

Correct, this is a workaround for the lack of a way to differentiate between .NET Core 3 on Windows with the Desktop SDK vs .NET Core 3 without.
You do need to use either dotnet restore or msbuild /restore for it to work correctly.

Closing as resolved.