Deploying Cass-operator and CassandraDataCenter on Power architecture

Hi Team , We are working on deploying cass-operator(v1.14.0) and CassandraDataCenter on Power architecture. We are able to deploy the operator successfully, while deploying the CassandraDataCenter the pod with 0th index terminates repeatedly while the pods with 1st and 2nd index are running fine.
We have installed the operator using Helm chart.
NAME                                  READY   STATUS        RESTARTS   AGE
pod/cass-operator-6fb8dffdb6-hl5nm    1/1     Running       0          4h38m
pod/instana-cassandra-default-sts-0   1/2     Terminating   0          19s
pod/instana-cassandra-default-sts-1   2/2     Running       0          4h37m
pod/instana-cassandra-default-sts-2   2/2     Running       0          4h37m

NAME                                                TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)
        AGE
service/cass-operator-webhook-service               ClusterIP   <IP_ADDRESS>   <none>        443/TCP
        4h38m
service/instana-cassandra-additional-seed-service   ClusterIP   None            <none>        <none>
        4h37m
service/instana-cassandra-all-pods-service          ClusterIP   None            <none>        9042/TCP,8080/TCP,9103/TCP,9000/TCP            4h37m
service/instana-cassandra-service                   ClusterIP   None            <none>        9042/TCP,9142/TCP,8080/TCP,9103/TCP,9000/TCP   4h37m
service/instana-seed-service                        ClusterIP   None            <none>        <none>
        4h37m

NAME                            READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/cass-operator   1/1     1            1           4h38m

NAME                                       DESIRED   CURRENT   READY   AGE
replicaset.apps/cass-operator-6fb8dffdb6   1         1         1       4h38m

NAME                                             READY   AGE
statefulset.apps/instana-cassandra-default-sts   2/3     4h37m

Any pointers regarding this will be helpful, Thank you.

There should be some sort of indication from Kubernetes what caused the termination of a pod. We have no special handling for killing a pod (especially with index 0).
Other than that, it would require rolling restart / decommission to start deleting pods. But in those cases, the order would be different.
I recommend checking the logs of containers to identify if there's a reason why Cassandra is failing, or if Kubernetes has reasons to delete the pod otherwise (like rescheduling).

The cassandra container's log could tell if the /drain endpoint was called (it's a shutdown hook for the pod) or if the shutdown came from other source. If it's the shutdown hook, then something should indicate why it was shutdown.
Did cass-operator logs have any indications? If it did kill the pod, it should log why.

I checked the cass-operator logs and found this error for the 0th index pod:
2023-08-23T11:18:34.200Z INFO client::callNodeMgmtEndpoint {"controller": "cassandradatacenter_controller", "controllerGroup": "cassandra.datastax.com", "controllerKind": "CassandraDatacenter", "CassandraDatacenter": {"name":"cassandra","namespace":"k8ssandra"}, "namespace": "k8ssandra", "name": "cassandra", "reconcileID": "cb182f6e-a759-4ad2-811b-1e9ec3812cba"}
2023-08-23T11:18:34.200Z DEBUG events Starting Cassandra for pod cassandra-default-sts-0 {"type": "Normal", "object": {"kind":"CassandraDatacenter","namespace":"k8ssandra","name":"cassandra","uid":"21cca51b-d70f-47a3-8086-0ef3416cf6a4","apiVersion":"cassandra.datastax.com/v1beta1","resourceVersion":"2114359"}, "reason": "StartingCassandra"}
2023-08-23T11:18:34.215Z INFO Failed to start pod cassandra-default-sts-0, deleting it {"controller": "cassandradatacenter_controller", "controllerGroup": "cassandra.datastax.com", "controllerKind": "CassandraDatacenter", "CassandraDatacenter": {"name":"cassandra","namespace":"k8ssandra"}, "namespace": "k8ssandra", "name": "cassandra", "reconcileID": "cb182f6e-a759-4ad2-811b-1e9ec3812cba", "reason": "StartingCassandra", "eventType": "Warning"}
2023-08-23T11:18:34.215Z ERROR controllers.CassandraDatacenter calculateReconciliationActions returned an error {"cassandradatacenter": "k8ssandra/cassandra", "requestNamespace": "k8ssandra", "requestName": "cassandra", "loopID": "94017e6a-a0ad-4314-a6e3-add6a7b32302", "error": "Post \"http://<IP_ADDRESS>:8080/api/v0/lifecycle/start\": dial tcp <IP_ADDRESS>:8080: connect: connection refused"}
github.com/k8ssandra/cass-operator/controllers/cassandra.(*CassandraDatacenterReconciler).Reconcile
/workspace/controllers/cassandra/cassandradatacenter_controller.go:145
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:121
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:320
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:234
2023-08-23T11:18:34.215Z INFO Post "http://<IP_ADDRESS>:8080/api/v0/lifecycle/start": dial tcp <IP_ADDRESS>:8080: connect: connection refused {"controller": "cassandradatacenter_controller", "controllerGroup": "cassandra.datastax.com", "controllerKind": "CassandraDatacenter", "CassandraDatacenter": {"name":"cassandra","namespace":"k8ssandra"}, "namespace": "k8ssandra", "name": "cassandra", "reconcileID": "cb182f6e-a759-4ad2-811b-1e9ec3812cba", "reason": "ReconcileFailed", "eventType": "Warning"}
2023-08-23T11:18:34.215Z INFO controllers.CassandraDatacenter Reconcile loop completed {"cassandradatacenter": "k8ssandra/cassandra", "requestNamespace": "k8ssandra", "requestName": "cassandra", "loopID": "94017e6a-a0ad-4314-a6e3-add6a7b32302", "duration": 0.018262743}
2023-08-23T11:18:34.215Z ERROR Reconciler error {"controller": "cassandradatacenter_controller", "controllerGroup": "cassandra.datastax.com", "controllerKind": "CassandraDatacenter", "CassandraDatacenter": {"name":"cassandra","namespace":"k8ssandra"}, "namespace": "k8ssandra", "name": "cassandra", "reconcileID": "cb182f6e-a759-4ad2-811b-1e9ec3812cba", "error": "Post \"http://<IP_ADDRESS>:8080/api/v0/lifecycle/start\": dial tcp <IP_ADDRESS>:8080: connect: connection refused"}

There is the reason:
2023-08-23T11:18:34.215Z INFO Post "http://<IP_ADDRESS>:8080/api/v0/lifecycle/start": dial tcp <IP_ADDRESS>:8080: connect: connection refused

The management-api could not be contacted for some reason (perhaps the cassandra-container logs would tell something, that includes management-api logs, server-system-logger container is the Cassandra itself).


[MAINTAINERS] new non-code maintainers

Signed-off-by: Sally MacFarlane<EMAIL_ADDRESS>I propose adding Helen George and Matt Nelson to Besu non-code maintainers. They have started helping manage, categorize bugs and other Github issues for Besu, as well as collaborating with the existing maintainers to help coordinate the development and roadmap planning of Besu.
Becoming non-code maintainers, they will be able to label bugs and close relevant tickets, helping to keep the project tidy.
Voting ends two weeks from today.
For more information on this process see the Becoming a non-code Maintainer section in the MAINTAINERS.md file.

So to be clear, my proposal is that instead of this processes PMs that need access are vouched by a maintainer they work with, and then access is granted. No voting, it's the reputation of the maintainer that is sufficient "social proof" for membership.
Removing access is similarly simple, a maintainer shares that the contributor is no longer in the role needing access and access is removed after confirming (or after reasonable effort to confirm has been performed) with the contributor being removed.

Closing this in favor of a lightweight process for modifying the membership of the non-code contributors group


Pulse  - layout filter and chart issues

Description
There are some design issues as for screenshots.
Steps to reproduce

Login by user
Resize the window for half screen
Press Pulse in action box for Resource Limits VM, go to all the tabs

Actual result
Dimensions cross the chart. Filter and chart in the same line. The tooltip is cut.
Expected result
Filters are in separate line. Each chart is on a separate line. Dimensions don't cross the chart. The tooltip isn't cut.
Connected requirement IDs
REQ_PLS_006, REQ_PLS_011, REQ_PLS_016, REQ_PLS_007, REQ_PLS_019
Screenshots

TO TEST:
REQ_PLS_024
REQ_PLS_010
REQ_PLS_003

To test: REQ_PLS_006, REQ_PLS_011, REQ_PLS_016, REQ_PLS_007, REQ_PLS_019

Lack:1
Drop-down NIC on the separate line in Network when Safari is fullscreen
Actual result: Drop-down NIC on the separate line in Network when Safari is fullscreen
Expected result: Drop-down NIC in line with other filters in Network when Safari is fullscreen

@dron8552 Is it possible to fix?

Yes, it is possible, but it will take a lot of time. @ershovaelena should I fix it?

@dron8552 @evgeniiamokhova Fail is moved to a separate task #1594. This issue can be resolved.


Client Allocation Request for: qjkx

Client Allocation Questions
Core Information

Name: qjkx
Website / Social Media: qjxk, (qjxk, qjkx)
Region: Africa
DataCap Requested: 32 GiB
Addresses to be Notarized: qjkx
Notary Requested: Irene Young

This user’s identity has been verified through filplus.storage


Commented debug in update_file not to slow down process of updating

I have 1200+ files and don't like clicking "Space" so many times while all my files are listed like this:
update_file on ZagranPastXmyid.md
update_file on ZhaKh.md
update_file on ZoyaAboutMish014.md

If you don't want to see debug output, then don't set 'nvim_debug' to disable debug output.


Remove DataWithContent

Description
Remove DataWithContent
Issue reference
#1409
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test

End-to-end tests failed.

this is expected because e2e test apps refers to old proto client. this will be succeeded once we merge this pr.


Google Cloud API Client initialization inconsistent

Story
Rubyist knows to use Google Data Store API. Rubyist wants to learn Google Vision API and the samples use different Google Cloud API Client initialization. Confusion begins.
Issue
Initialization is inconsistent between these two samples. The issue may exist in other samples within the Ruby space.
DataStore uses
require "gcloud"
gcloud = Gcloud.new
datastore = gcloud.datastore
Vision uses
require "google/cloud"
gcloud = Google::Cloud.new
vision = gcloud.vision
Issue exists in the following locations:
appengine/datastore/app.rb
appengine/pubsub/app.rb
appengine/pubsub/spec/pubsub_spec.rb
bigquery/shakespeare.rb
datastore/sample.rb
logging/spec/sample_spec.rb
logging/sample.rb
pubsub/sample.rb
Possible Solution
Use the same initialization in all Ruby samples.

Duplicate of #55
Fix pending in #65


Fix nil porinter panic in npc/namespace.go

The *coreapi.Namespace in struct ns may be set to nil in func deleteNamespace before func deletePod called，it will cause a pinic when deletePod use the namespace pointer.
I use a new map to store the lables of namespace, when the pointer is set to nil, it can avoid panic and work well.
DEBU: 2020/07/23 11:09:37.920737 EVENT DeletePod {"metadata":{"creationTimestamp":"2020-07-23T08:30:24Z","deletionGracePeriodSeconds":0,"deletionTimestamp":"2020-07-23T11:09:31Z","generateName":"bp-s2-745c79479b-","labels":{"App":"f43f2b4120f7e4adbb88ede557c74ec35","Blueprint":"bbp-s2","Service":"bp-s2","app":"bp-s2","flowid":"57","pod-template-hash":"745c79479b","version":"v1"},"name":"bp-s2-745c79479b-kq66f","namespace":"f43f2b4120f7e4adbb88ede557c74ec35","resourceVersion":"27784263","selfLink":"/api/v1/namespaces/f43f2b4120f7e4adbb88ede557c74ec35/pods/bp-s2-745c79479b-kq66f","uid":"9eb3ec80-d600-4d07-837f-7662cd6a3e0a"},"spec":{"affinity":{},"containers":[{"image":"harbor.cloud2go.cn/cloudtogo/network-multitool","imagePullPolicy":"Always","name":"bp-s2","ports":[{"containerPort":80,"name":"p80","protocol":"TCP"}],"readinessProbe":{"failureThreshold":3,"initialDelaySeconds":1,"periodSeconds":5,"successThreshold":1,"tcpSocket":{"port":80},"timeoutSeconds":1},"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"FallbackToLogsOnError"}],"dnsConfig":{"options":[{"name":"ndots","value":"1"}]},"dnsPolicy":"ClusterFirst","nodeName":"n1.env.lab.io","restartPolicy":"Always","schedulerName":"default-scheduler","securityContext":{},"serviceAccount":"default","serviceAccountName":"default","terminationGracePeriodSeconds":0},"status":{"conditions":[{"lastProbeTime":null,"lastTransitionTime":"2020-07-23T08:30:24Z","status":"True","type":"Initialized"},{"lastProbeTime":null,"lastTransitionTime":"2020-07-23T08:31:48Z","status":"True","type":"Ready"},{"lastProbeTime":null,"lastTransitionTime":"2020-07-23T08:31:48Z","status":"True","type":"ContainersReady"},{"lastProbeTime":null,"lastTransitionTime":"2020-07-23T08:30:24Z","status":"True","type":"PodScheduled"}],"hostIP":"<IP_ADDRESS>","phase":"Running","podIP":"<IP_ADDRESS>","qosClass":"BestEffort","startTime":"2020-07-23T08:30:24Z"}}
INFO: 2020/07/23 11:09:37.939904 deleting entry <IP_ADDRESS> from weave-Cz*b([u5~[;?3vXY}8w6UH?f3 of 9eb3ec80-d600-4d07-837f-7662cd6a3e0a
INFO: 2020/07/23 11:09:37.939958 deleting entry <IP_ADDRESS> from weave-5$otwpJo/[g4!?%N8=f+9t=Au of 9eb3ec80-d600-4d07-837f-7662cd6a3e0a
INFO: 2020/07/23 11:09:37.939981 deleting entry <IP_ADDRESS> from weave-vfZR:H<EMAIL_ADDRESS>of 9eb3ec80-d600-4d07-837f-7662cd6a3e0a
INFO: 2020/07/23 11:09:37.940007 deleted entry <IP_ADDRESS> from weave-vfZR:H<EMAIL_ADDRESS>of 9eb3ec80-d600-4d07-837f-7662cd6a3e0a
ERROR: logging before flag.Parse: E0723 11:09:37.946420    1331 runtime.go:66] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
/go/src/github.com/weaveworks/weave/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:72
/go/src/github.com/weaveworks/weave/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:65
/go/src/github.com/weaveworks/weave/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:51
/usr/local/go/src/runtime/panic.go:679
/usr/local/go/src/runtime/panic.go:199
/usr/local/go/src/runtime/signal_unix.go:394
/go/src/github.com/weaveworks/weave/npc/namespace.go:336
/go/src/github.com/weaveworks/weave/npc/controller.go:144
/go/src/github.com/weaveworks/weave/npc/controller.go:106
/go/src/github.com/weaveworks/weave/npc/controller.go:143
/go/src/github.com/weaveworks/weave/prog/weave-npc/main.go:287
/go/src/github.com/weaveworks/weave/vendor/k8s.io/client-go/tools/cache/controller.go:209
/go/src/github.com/weaveworks/weave/vendor/k8s.io/client-go/tools/cache/controller.go:320
/go/src/github.com/weaveworks/weave/vendor/k8s.io/client-go/tools/cache/delta_fifo.go:444
/go/src/github.com/weaveworks/weave/vendor/k8s.io/client-go/tools/cache/controller.go:150
/go/src/github.com/weaveworks/weave/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133
/go/src/github.com/weaveworks/weave/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134
/go/src/github.com/weaveworks/weave/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88
/go/src/github.com/weaveworks/weave/vendor/k8s.io/client-go/tools/cache/controller.go:124
/usr/local/go/src/runtime/asm_amd64.s:1357

What exactly gets set to nil?  Where?
It's probably a good idea to file the problem as an issue, with this PR referring to it, in case there are different ways to solve it.

Oh, and thanks for the PR.

Do I still need to open an issue and provide more info?

My previous comment stands, yes.

Thanks for making all those changes - it's a bit more than I had thought (sorry!).
I'm just looking at fixing up the merge conflicts which came in with #3726

Merge conflicts resolved at https://github.com/weaveworks/weave/compare/master...fix-nil-ns-pointer


input-switch implementation

You did it @samkyatham!
Thank you for signing the Anthem Opensource Software CLA.


Save lastOverElement between move actions (closes #137)

\cc @inikulin @AlexanderMoskovkin

test fail

FPR

lgtm

@AndreyBelym, some other fixes was merged and github can't merge this PR now. Please rebase to the master branch

lgtm
@VasilyStrelyaev please check the strings

\r-

FPR

Lgtm

lgtm


can't deploy solutions, assertion error obj._schema == schema

When i try to deploy a soultion (network)
I get this assertion error

fixed at: https://github.com/threefoldtech/jumpscaleX_libs/commit/502d2777b56fb9ea7cc35205cfe5a1f70366183a


[C++] Add an API to allow writing RowGroups based on their size rather than num_rows

The current API allows writing RowGroups with specified numbers of rows, however does not allow writing RowGroups with specified size. In order to write RowGroups of specified size we need to write rows in chunks while checking the total_bytes_written after each chunk is written. This is currently impossible because the call to NextColumn() closes the current column writer.
Reporter: Anatoli Shein
Assignee: Deepak Majeti / @majetideepak
PRs and other links:

GitHub Pull Request #484

Note: This issue was originally created as PARQUET-1372. Please see the migration documentation for further details.

Uwe Korn / @xhochy:
Issue resolved by pull request 484
https://github.com/apache/parquet-cpp/pull/484

Anatoli Shein:
@renato2099, thanks! So the current plan is to make each row group approximately the given size without going over, while each row group should also have at least one record.

Renato Javier Marroquín Mogrovejo / @renato2099:
This is a very useful feature indeed [~anatoli.shein] !
Just one quick clarification question, are you planning to implement fixed row group sizes? i.e., all of them having for example 8MB? If so, how are you planning to deal with record boundaries? Cutting them off? or making each row group size approximately what was configured? Thanks!


Extract forward/backward core computation bits outside of torch autograd context for easy reuse

Summary

Extract forward/backward core computation bits outside of torch autograd context for easy reuse. This is beneficial for lightning thunder integration and the reuse of kernel in other context.
Doubled checked the speed and memory usage, within variance range, no degradation

Testing Done

Hardware Type:
[x] run make test to ensure correctness
[x] run make checkstyle to ensure code style
[x] run make test-convergence to ensure convergence

cc @t-vi LGTM


refactor: attempt to rename grpc so v is trailing

WIP
Imports are broken at the moment, it seems that it wants us to refer to each imported reference fully (ie xyz/block/ftl/schema/v1/schema.Ref rather than schema.Ref

I think I've figured out what the import rules are. If you have two packages:
xyz.block.ftl.console.v1
xyz.block.ftl.schema.v1

Ad you're trying to use  xyz.block.ftl.schema.v1.Schema in the console proto, you'd need to reference it like so:
schema.v1.Schema

That is, it will look for a common relative root.

Doing this while https://github.com/TBD54566975/ftl/pull/3417 is open is just going to cause more pain. I'll wait for that to come in and redo these changes

This has been fixed in main already now. closing this


USB Driver for El Cap has dependency on CodeBender

When you install the USB driver for El Cap, it shows page relating to CodeBender walkthrough and then fails when you try to continue.

This will be fine anyway - just hit okay and then complete the process and
it will still work.
On Tue, Sep 27, 2016 at 8:27 AM Linda Nichols<EMAIL_ADDRESS>wrote:

When you install the USB driver for El Cap, it shows page relating to
CodeBender walkthrough and then fails when you try to continue.
[image: screen shot 2016-09-26 at 3 20 17 pm]
https://cloud.githubusercontent.com/assets/1610195/18854072/ce54fd3e-8416-11e6-9c08-74b8cd64c10c.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Makeblock-official/mbot_nodebots/issues/18, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAHRo3aVTPyb5E9AULAADnkNljG05ccWks5quEa5gaJpZM4KHD_a
.


Analysis and troubleshooting on patroni going to recovery mode on load test

Describe the task
During the process of camunda load testing #2489, when the load test was performed with 5000 assessments with 20 VUs(virtual users) in DEV environment, it has been consistently observed for every load test (until workers were adjusted to reduce the amount of parallel requests) that the database was temporarily going to recovery mode for few seconds and then coming back up and stable after that.
Error observed in workers :
Private Zenhub Image
How to replicate the issue:
To replicate the issue in DEV environment, run the load test with 5000 iterations and 20 VUs. As the worker configurations are updated to stabilize the load on DB now, before running the load test, update the min replicas for workers to 4 or a higher value.
To install K6 and run load test, follow the wiki: https://github.com/bcgov/SIMS/wiki/Load-testing
Points which came from discussion when this error was observed
There was a point which came up in a discussion regarding the type of user that we use to connect database from all the applications(API, Workers, Queue Consumers) that we use superuser instead of a regular user. Need to investigate if that is a possible root cause.
Acceptance Criteria

[ ] Perform analysis to find the root cause and solution of the error where database goes to recovery mode temporarily
[ ] Timebox the effort. Implementation of solution if time permits otherwise have a separate ticket for that.

Additional context

Add any other context about the task here.
Or here

https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-managing-connections#postgres-connection-limits
as part of the connection limits to the superuser it is retricted to 15 and the database users 100. The change from the superuser to database user in the load test gives the below results

The red box notes the load test run assigning the superuser connection for the postgres and the orange one denotes the run that happened assigning the database user connection. Clearly not once the database went to recovery mode. The suggestion is changing the connection parameters in API, db-migrations-job, load-test-gateway, queue-consumers, and workers to database user than the super user.
In our case the database user does not have proper grants to access the tables and sequences in the database. So please run the below grants for the proper connection of the data to the database schema.


runtime crash with "Numeric"

var c:Numeric =233
var b:Numeric =1.0
print c+b

In this simple case it could be detected by the compiler but in the general case it should be handled somehow. If it crashes or throws a runtime exception it means the Numeric type is useless and dangerous.

The plan is to support operator overloading to implement Int + Float and others, in order to get the desired behavior at an acceptable performance level.
Until then, I recommend not using explicitly the Numeric static type if you don't need it, the Numeric limitations should not affect the direct use of Float and Int. You probably already noticed, in the given example simply removing the two :Numeric types will result in the expected static error to be displayed. But if you do need to use Numeric, use it with the Numeric-safe (but slower) methods add, sub, etc.

On Wed, Nov 22, 2017 at 02:36:09PM +0000, Alexis Laferrière wrote:

The plan is to support operator overloading to implement Int + Float and others, in order to get the desired behavior at an acceptable performance level.

just curious - is it similar like in Ruby where 2+3 is syntactic sugar for 2.+(3) (integer.methodcall+(arg))? In that case I would think it could be easily "redefined" by the programmer as needed? I was also thinking on complex numbers and whatever else might become useful at some point.

Until then, I recommend not using explicitly the Numeric static type if you don't need it, the Numeric limitations should not affect the direct use of Float and Int. You probably already noticed, in the given example simply removing the two :Numeric types will result in the expected static error to be displayed. But if you do need to use Numeric, use it with the Numeric-safe (but slower) methods add, sub, etc.

thanks for the hint, never knew about the numeric-safe variants.


Parallel main matrix

Run main build multiple OS and Python versions
- 3.6 and 3.9 as min/max supported version.
- Windows, macOS and Linux
- Cache python site-packages on Windows for install speed
- On Linux/macOS just cache pip wheels

We can expand the build to run in parallel on Linux + Windows (and even macOS) + different python versions.

I think it might be worth supporting macOS over lots of different Python versions, since I think discrepancies are far more likely to occur between OSes than Python's minor versions.  I think perhaps 2 py versions x 3 OSes seems reasonable?  Also for some reason our original build CI run is permanently marked as 'expected' for this PR - perhaps GH is just confused by the fact that we changed it...
Also we could perhaps do more strict checks between merging PRs and the code being released - I think the PyPI action is the wrong place, but perhaps we could run a bigger matrix each time master is committed to?

We could cache the python location (though probably not for all 6 runs without being close to 5GB limit)
https://medium.com/ai2-blog/python-caching-in-github-actions-e9452698e98d

Perhaps if we did this just for Windows to improve the speed?  I think too much caching could lead to us missing things that only happen on fresh python installs...

I don't have permission to see where build is set as a required checks for PRs to master.
macOS 3.9 is really slow to install numpy when not cached, we'll have to keep submitting PRs to stop the caches expiring :D

In a total of 3 runs I've had a doc test timeout on macOS 3.6 once and another time on macOS 3.9 :/

I don't have permission to see where build is set as a required checks for PRs to master.

It's in the security settings I think (which might only be accessible to me).  If the issue is just getting this PR merged, then I can bypass the protection on a per-PR basis.  I figured it was probably good practice to protect the master branch like this, although if it's more annoyance than it's worth then I'm happy to just reset the setting...

Do we need to do pip install wheel?

Ooh possibly - this does seem to work, but it's probably worth not using any legacy things for future proofing.

In a total of 3 runs I've had a doc test timeout on macOS 3.6 once and another time on macOS 3.9
And now one on Windows :disappointed:

Hmmm.  Perhaps we could increase the timeout as part of #175?

/rebase

Both mac runs had errors, I suspect it doesn't like the number of simultaneous connections
 >>> README.md:140: python ./run-wheatley 238915467 --method "Plain Bob Major" -I 1.0
RETURN CODE: 1
OUTPUT:
Traceback (most recent call last):
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/site-packages/urllib3/connection.py", line 159, in _new_conn
    conn = connection.create_connection(
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/site-packages/urllib3/util/connection.py", line 84, in create_connection
    raise err
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/site-packages/urllib3/util/connection.py", line 74, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 61] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/site-packages/urllib3/connectionpool.py", line 670, in urlopen
    httplib_response = self._make_request(
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/site-packages/urllib3/connectionpool.py", line 392, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/http/client.py", line 1253, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/http/client.py", line 1299, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/http/client.py", line 1248, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/http/client.py", line 1008, in _send_output
    self.send(msg)
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/http/client.py", line 948, in send
    self.connect()
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/site-packages/urllib3/connection.py", line 187, in connect
    conn = self._new_conn()
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/site-packages/urllib3/connection.py", line 171, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x109ff1100>: Failed to establish a new connection: [Errno 61] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/site-packages/requests/adapters.py", line 439, in send
    resp = conn.urlopen(
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/site-packages/urllib3/connectionpool.py", line 724, in urlopen
    retries = retries.increment(
  File "/Users/runner/hostedtoolcache/Python/3.9.4/x64/lib/python3.9/site-packages/urllib3/util/retry.py", line 439, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='methods.ringing.org', port=80): Max retries exceeded with url: /cgi-bin/simple.pl?title=Plain+Bob+Major&fields=title%7Cpn%7Cstage (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x109ff1100>: Failed to establish a new connection: [Errno 61] Connection refused'))

Hmm, I'm tempted to just drop the macOS runs for now as we don't have someone who can debug them

Hmm, I'm tempted to just drop the macOS runs for now as we don't have someone who can debug them

I agree - I don't think we should drop support for macOS completely but the minority of users use the CLI version and a minority of those use macOS so I don't think it's a particularly big deal.  At any rate, macOS and Linux tend to generally work the same since they're both ultimately Unix systems.
Ironically, I suspect that at least 80% of Wheatley's users are running it on Linux without knowing it (i.e. Wheatley itself is running on the RR servers) so I think Ubuntu and Windows should cover nearly everyone.

To be clear it just meant don't add macOS runs to this matrix, which is the previous situation where they just ran on Linux.
I think you might need to bypass checks to merge this and then edit the required checks afterwards?

Yep I can merge without the checks finishing.  I'll do that now.


BaseURL should be an optional parameter to the generate command

It's not uncommon for OpenAPI descriptions to not specify their server endpoints. This not only generates an odd warning:
warn: Kiota.Builder.KiotaBuilder[0]
      OpenAPI warning: #/ - Multiple servers entries were found in the OpenAPI description. Only the first one will be used. The root URL can be set manually with the request adapter

But it generates a client with a bad default base URL. It appears that it is setting it to the URL of the file, minus the file. For example, if I use https://api.apis.guru/v2/specs/funtranslations.com/starwars/2.3/swagger.json, it sets base URL to https://api.apis.guru/v2/specs/funtranslations.com/starwars/2.3. If I use https://funtranslations.com/yaml/funtranslations.starwars.yaml, it set it to https://funtranslations.com/yaml. Note these are the same API with identical descriptions (all other code generated by these two are identical).
The warning is odd because the are no servers entries, not multiple!
Proposal
While I realize developers can set the base URL in code, that's a step I shouldn't have to take. I propose adding an optional parameter so I can specify the default base URL. Something like:
kiota generate --base-url https://api.funtranslations.com/translate/

I also tried this by downloading their description using kiota and then generating from the local file:
kiota download apisguru::funtranslations.com:starwars
kiota generate -l CSharp -c TranslatorClient -d .\output\result.json -o ./Client

It set the base url like this:
RequestAdapter.BaseUrl = "https://api.funtranslations.com/C:/Source/temp/kiota/funtranslations/dotnet/src/output/result.jso";

This might actually be a conversion issue + preference
the description contains that
swagger: "2.0"
schemes:
  - https
  - http
host: api.funtranslations.com

which probably translates in the object model to
servers:
  - http://api.funtranslations.com
  - https://api.funtranslations.com

When performing that validation we should probably dedupe servers that are identical for everything besides the scheme and get rid of the HTTP one for obvious privacy reasons.

opened a pull request to address that. #2547
additionally, this particular API is impacted by this bug in the OpenAPI.net lib https://github.com/microsoft/OpenAPI.NET/pull/1213


Support for non-tiled GeoJSON and TopoJSON sources

This adds support for non-tiled, standalone GeoJSON and TopoJSON sources, by using the excellent geojson-vt library to cut these into tiles (appropriately simplified per zoom level) on the fly, client-side. This makes it much easier to use arbitrary data with Tangram!
In addition, the name and function of data sources is simplified: instead of having GeoJSONTiles and TopoJSONTiles source types, these are simplified to GeoJSON and TopoJSON. When creating the source, the URL is examined to see if it contains a tile template ({x}, {y}, and {z} parameters). If it does contain a tile template, a standard tiled data source is created. If the URL does not contain a tile template, an client-side-tiling source using geojson-vt is automatically created instead.
Example of shortened source type name:
    # creates a server-tiled data source (URL tile template is present)
    osm:
        type: GeoJSON
        url:  http://vector.mapzen.com/osm/all/{z}/{x}/{y}.json
    # creates a client-tiled data source (no URL tile template)
    counties:
        type: TopoJSON
        url: https://gist.githubusercontent.com/mbostock/4090846/raw/c899e3d4f3353924e495667c842f54a07090cfab/us.json

The bundled demo has been updated to use the shorter, unified source type names, but the older ones still work for backwards compatibility.
Here's a US counties TopoJSON (via one of Mike Bostock's examples), as a non-tiled source:

cc @meetar @sensescape @nvkelso out of interest
cc @blair1618 @tallytalwar @patriciogonzalezvivo on backwards compatible "API" change (accepting older GeoJSONTiles/TopoJSONTiles source names in addition to new unified ones).

@meetar @patriciogonzalezvivo after this is merged, let's update demos and docs to use the unified source type names, though the older ones will continue to work.

OMG this is huge. :+1: :tada: :open_mouth:

@bcamper We're champing at the bit over here, can we merge this?

I want to take a look at a few more things... hold your horses :)
On Tuesday, June 30, 2015, Peter Richardson<EMAIL_ADDRESS>wrote:

@bcamper https://github.com/bcamper We're champing at the bit over
here, can we merge this?
—
Reply to this email directly or view it on GitHub
https://github.com/tangrams/tangram/pull/160#issuecomment-117327586.

:horse_racing: :dash: :checkered_flag: :trophy:

split data sources into separate files?
remove Y flipping from internal tile coords?
open branch/PR to update docs (simplified GeoJSON/TopoJSON source type naming in addition to non-tiled sources)


Domain layer component should not be used in Data layer component

I have seen that you have used Domain layer components in Data layer
as per clean architecture Data layer component should not be used in Data layer component

@narendrakothamire  Data layer resides one level above than Domain (that is core layer in clean architecture) so it's ok to use models and other classes from lower layer in above layer/s.
Clean approach only says that you can't do reverse, for example :
you can't use Data entities in Domain layer because it ruins boundaries.

@MikeHerasimov You can't use Data entities in Domain layer because it ruins boundaries.
Domain layer has used data entities as well.
Presentation can have domain layer things and Domain can have data layer things
but not reverse -As per my knlwg

@narendrakothamire "Domain layer has used data entities as well." I'm not sure about this, can you provide some links?
Domain can't have data layer things because Data layer is above Domain.
In clean architecture we have
Domain -> Data -> Presentation
As I said earlier Domain layer is our core layer.

as far as I see you thought that Domain is our middle layer, it can be confusing at first because this layer has data from Data layer, but not directly.
In clean it is done by repository pattern.
I don't know where you started you Clean Architecture learning, you may want to take a look at some articles in section 6 (I'm just to lazy to copy all of them)
https://blog.aritraroy.in/what-my-2-years-of-android-development-have-taught-me-the-hard-way-52b495ba5c51#.w3idnlv2m

I knw clean architecture very well
U look this link from where this lib code has been taken
https://github.com/android10/Android-CleanArchitecture

I alredy saw this repo and all articles related to it.
you know clean architecture very well but claim that "Domain can have data layer things"

@MikeHerasimov is right on this. Data layer is an implementation layer (of the repository interfaces in the Domain layer). This is the same pattern followed in the  https://github.com/android10/Android-CleanArchitecture link provided by @narendrakothamire.


Client is enabled even if approval request is failed and default scopes are removed from Keycloak

API Services Portal Issue
API gateway deletes the default scopes from Keycloak
ENV

[ ] DEV
[x ] TEST
[ ] PROD

TESTCASE
Same issuer as mentioned in https://github.com/bcgov/api-services-portal/issues/136
Process: Developer requesting for API

Client is created with default scopes

Process: Approver approving the request
Q 1: Request approval failed when approver selected the available scope

Q 2: Client enabled even if approval failed

Q 3:  request approved when only empty 'Roles' is selected but this lead to removal of default scopes for client

default scopes are removed

EXPECTED

Assign selected scope to the client with default scopes
Client not enabled when approval process is failed

ACTUAL
1 Removes the default scopes
2 Does not assign the selected scope
3 Approval request is failed (https://github.com/bcgov/api-services-portal/issues/136)
4 Client is enabled even if approval is failed

Current behaviour is that the Portal assumes it is managing all Scopes for the clients that it creates.. so any Scope the client has that the Portal is not expecting, gets deleted.  The reasoning behind this was to avoid having two administration points for Clients created by the Portal.
There is a bug here though, in that the approved operation should either fully succeed or fully fail, rather than now where the Client is in a partial state of "Enabled with no Scopes assigned".


Relationship

How to make this relationship?
https://miragejs.com/repl/v2/aed73f33fc
HELPPP PLEASEEE

I looked at this for a little while but I can't see what the problem is. I will try to reproduce the issue outside of the REPL.

There are tests for similar relationships without issue. I suspect there's something wrong with the REPL.

How to make this relationship?
https://miragejs.com/repl/v2/aed73f33fc
HELPPP PLEASEEE

Have you been able to reproduce this issue in code, i.e., outside of the Mirage REPL?


Runtime crash due to build time configuration inconsistency/bug (CUDA 10.1)

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Arch Linux x86_64
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): source
TensorFlow version: 1.13.1 (equivalently affects 2.0.0-alpha0)
Python version: 3.7.3
Installed using virtualenv? pip? conda?: native system install
Bazel version (if compiling from source): 0.22.0
GCC/Compiler version (if compiling from source): GCC 8.3.0
CUDA/cuDNN version: 10.1
GPU model and memory: any

Describe the problem
At configuration time, TensorFlow checks if given CUDA version is indeed available by inspecting SONAMEs of libs. Then it links to the closest version available on the system. At runtime, however, it has stored the plain version number as a string (in stream_executor/dso_loader.cc), given to it at configuration time, and tries to load those libraries exactly instead -  not the ones it actually build/linked against. Normally, this will not be such a problem, however, it is inconsistent and in the case of CUDA 10.1, of course, results in a crash. CUDA 10.1 libraries ship as filenames lib*.so.<IP_ADDRESS>, but some are labelled with SONAME lib*.so.10.1 and others are labelled SONAME lib*.so.10. This results in either a build error or runtime error depending on how tensorflow was configured, but in any case, it prevents TensorFlow from working.
Provide the exact sequence of commands / steps that you executed before running into the problem
$ ./build.sh
  export PYTHON_BIN_PATH=/usr/bin/python
  export USE_DEFAULT_PYTHON_LIB_PATH=1
  export TF_NEED_JEMALLOC=1
  export TF_NEED_KAFKA=0
  export TF_NEED_OPENCL_SYCL=0
  export TF_NEED_AWS=0
  export TF_NEED_GCP=0
  export TF_NEED_HDFS=0
  export TF_NEED_S3=0
  export TF_ENABLE_XLA=1
  export TF_NEED_GDR=0
  export TF_NEED_VERBS=0
  export TF_NEED_OPENCL=0
  export TF_NEED_MPI=0
  export TF_NEED_TENSORRT=0
  export TF_NEED_NGRAPH=0
  export TF_NEED_IGNITE=0
  export TF_NEED_ROCM=0
  export TF_SET_ANDROID_WORKSPACE=0
  export TF_DOWNLOAD_CLANG=0
  export TF_NCCL_VERSION=2.4
  export NCCL_INSTALL_PATH=/usr
  export TF_IGNORE_MAX_BAZEL_VERSION=1
  export CC_OPT_FLAGS="-march=haswell"
  export TF_NEED_CUDA=1
  export GCC_HOST_COMPILER_PATH=/usr/bin/gcc
  export HOST_CXX_COMPILER_PATH=/usr/bin/gcc
  export TF_CUDA_CLANG=0
  export CUDA_TOOLKIT_PATH=/opt/cuda
  export TF_CUDA_VERSION=10.1
  export CUDNN_INSTALL_PATH=/usr/lib
  export TF_CUDNN_VERSION=7
  export TF_CUDA_COMPUTE_CAPABILITIES=3.5,3.7,5.0,5.2,5.3,6.0,6.1,6.2,7.0,7.2,7.5
  ./configure
  bazel \
    build --config=opt \
      //tensorflow:libtensorflow.so \
      //tensorflow:libtensorflow_cc.so \
      //tensorflow:install_headers \
      //tensorflow/tools/pip_package:build_pip_package
  bazel-bin/tensorflow/tools/pip_package/build_pip_package "${srcdir}"/tmpcudaopt

# BUILD ERROR:
ERROR: Skipping '//tensorflow/tools/pip_package:build_pip_package': error loading package 'tensorflow/tools/pip_package': in /build/tensorflow/tensorflow/tensorflow.bzl: Encountered error while reading extension file 'cuda/build_defs.bzl': no such package '@local_config_cuda//cuda': Traceback (most recent call last):
	File "/build/tensorflow/third_party/gpus/cuda_configure.bzl", line 1502
		_create_local_cuda_repository(repository_ctx)
	File "/build/tensorflow/third_party/gpus/cuda_configure.bzl", line 1266, in _create_local_cuda_repository
		_find_libs(repository_ctx, cuda_config)
	File "/build/tensorflow/third_party/gpus/cuda_configure.bzl", line 859, in _find_libs
		_find_cuda_lib("cublas", repository_ctx, cpu_value, c..., ...)
	File "/build/tensorflow/third_party/gpus/cuda_configure.bzl", line 773, in _find_cuda_lib
		find_lib(repository_ctx, [("%s/%s%s" % (bas...], ...)))
	File "/build/tensorflow/third_party/gpus/cuda_configure.bzl", line 747, in find_lib
		auto_configure_fail(("None of the libraries match th...)))
	File "/build/tensorflow/third_party/gpus/cuda_configure.bzl", line 341, in auto_configure_fail
		fail(("\n%sCuda Configuration Error:%...)))

Cuda Configuration Error: None of the libraries match their SONAME: /opt/cuda/lib64/libcublas.so.10.1

# $ ./tensorflow_test.py
#!/usr/bin/env python

import tensorflow as tf
mnist = tf.keras.datasets.mnist

(x_train, y_train),(x_test, y_test) = mnist.load_data()
x_train, x_test = x_train / 255.0, x_test / 255.0

model = tf.keras.models.Sequential([
  tf.keras.layers.Flatten(input_shape=(28, 28)),
  tf.keras.layers.Dense(512, activation=tf.nn.relu),
  tf.keras.layers.Dropout(0.2),
  tf.keras.layers.Dense(10, activation=tf.nn.softmax)
])
model.compile(optimizer='adam',
              loss='sparse_categorical_crossentropy',
              metrics=['accuracy'])

model.fit(x_train, y_train, epochs=5)
val = model.evaluate(x_test, y_test)
print('Result is:\n{}'.format(val[0]))
print('Success!')

# RUNTIME ERROR:
2019-04-23 23:51:16.393767: I tensorflow/stream_executor/dso_loader.cc:142] Couldn't open CUDA library libcublas.so.10.1. LD_LIBRARY_PATH:
2019-04-23 23:51:16.393797: F tensorflow/stream_executor/lib/statusor.cc:34] Attempting to fetch value instead of handling error Failed precondition: could not dlopen DSO: libcublas.so.10.1; dlerror: libcublas.so.10.1: cannot open shared object file: No such file or directory
[1]    4805 abort (core dumped)  ./tensorflow_test.py

Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
The following patch allows a workaround for CUDA 10.1 and specific affected libs:
diff --git a/tensorflow/stream_executor/dso_loader.cc b/tensorflow/stream_executor/dso_loader.cc
index 6dda5d6315..4df1d0dcfc 100644
--- a/tensorflow/stream_executor/dso_loader.cc
+++ b/tensorflow/stream_executor/dso_loader.cc
@@ -46,7 +46,7 @@ string GetCudnnVersion() { return TF_CUDNN_VERSION; }

 /* static */ port::Status DsoLoader::GetCublasDsoHandle(void** dso_handle) {
   return GetDsoHandle(FindDsoPath(port::Env::Default()->FormatLibraryFileName(
-                                      "cublas", GetCudaVersion()),
+                                      "cublas", "10"),
                                   GetCudaLibraryDirPath()),
                       dso_handle);
 }
@@ -63,14 +63,14 @@ string GetCudnnVersion() { return TF_CUDNN_VERSION; }

 /* static */ port::Status DsoLoader::GetCufftDsoHandle(void** dso_handle) {
   return GetDsoHandle(FindDsoPath(port::Env::Default()->FormatLibraryFileName(
-                                      "cufft", GetCudaVersion()),
+                                      "cufft", "10"),
                                   GetCudaLibraryDirPath()),
                       dso_handle);
 }

 /* static */ port::Status DsoLoader::GetCurandDsoHandle(void** dso_handle) {
   return GetDsoHandle(FindDsoPath(port::Env::Default()->FormatLibraryFileName(
-                                      "curand", GetCudaVersion()),
+                                      "curand", "10"),
                                   GetCudaLibraryDirPath()),
                       dso_handle);
 }
diff --git a/third_party/gpus/cuda_configure.bzl b/third_party/gpus/cuda_configure.bzl
index 8aa5b89cdd..7ed4bb8b45 100644
--- a/third_party/gpus/cuda_configure.bzl
+++ b/third_party/gpus/cuda_configure.bzl
@@ -842,7 +842,7 @@ def _find_libs(repository_ctx, cuda_config):
               repository_ctx,
               cpu_value,
               cuda_config.cuda_toolkit_path,
-              cuda_config.cuda_version,
+              '',
           ),
       "cusolver":
           _find_cuda_lib(
@@ -850,7 +850,7 @@ def _find_libs(repository_ctx, cuda_config):
               repository_ctx,
               cpu_value,
               cuda_config.cuda_toolkit_path,
-              cuda_config.cuda_version,
+              '',
           ),
       "curand":
           _find_cuda_lib(
@@ -858,7 +858,7 @@ def _find_libs(repository_ctx, cuda_config):
               repository_ctx,
               cpu_value,
               cuda_config.cuda_toolkit_path,
-              cuda_config.cuda_version,
+              '',
           ),
       "cufft":
           _find_cuda_lib(
@@ -866,7 +866,7 @@ def _find_libs(repository_ctx, cuda_config):
               repository_ctx,
               cpu_value,
               cuda_config.cuda_toolkit_path,
-              cuda_config.cuda_version,
+              '',
           ),
       "cudnn":
           _find_cuda_lib(

I would also like to mention that the following #26230 also suffers from the same problem. It tried to avoid it, but it only defers it. It allows to give TF_CUDA_VERSION and TF_CUDA_LIB_VERSION strings at configuration time, but ultimately, this will result in the same bug as not all CUDA libraries have (or are guaranteed to have) the same version.

ping @svenstaro

I think this should mostly be fixed already with the dso_loader.cc code changed to GetCudaLibVersion() in the appropriate places. I say mostly because there was a bug that will be fixed in PR #28021.

@chsahit Just had a quick look. I don't agree. Also, specifically GetCudaLibVersion() is just postponing the issue, since it relies on the fact a single config time supplied constant can describe a possibly multitude of lib versions. Also, it seems there is a disconnect between config time and runtime library version determination, if I read the code correctly. I think lib versions must be determined once, either only at config time or only at runtime. They should also not fully rely on a user supplied constant and be determined per required lib - as it is done at config time, except currently it's hardcoded. Instead, it should be allowed to find appropriate versions and the result propagated for each to common generated header.

CUDA libraries come with different versions in their name.

cuDNN, NCCL, TensorRT use major only.
CUDA runtime uses major.minor.
cuSPARSE, cuFFT, cuBLAS etc used major.minor up to 10.0, and just major starting with v10.1

CudaVersion() matches the second one (major.minor).
CudaLibVersion() matches the last one (major.minor up to v10.0, major starting with v10.1).
The value of CudaVersion() and CudaLibVersion() is determined during the CUDA repository configuration and is written into a header file.
Does that clear things up?
I'm closing this issue. Feel free to reopen if PR #28021 doesn't fix the issue for you.

as of 04/29, I am still experience following issue build with cuda 10.1
System information
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: n/a
TensorFlow installed from (source or binary): source
TensorFlow version: master
Python version: 3.6.7
Installed using virtualenv? pip? conda?: system install to /usr
Bazel version (if compiling from source): 0.24.1
GCC/Compiler version (if compiling from source): GCC 7.3.0
CUDA/cuDNN version: 10.1/7.5.0
ERROR: /tensorflow/tensorflow/core/kernels/BUILD:1018:1: output 'tensorflow/core/kernels/_objs/diag_op_gpu/diag_op_gpu.cu.pic.o' was not created
ERROR: /tensorflow/tensorflow/core/kernels/BUILD:1018:1: not all outputs were created or valid
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 962.337s, Critical Path: 139.55s
INFO: 10586 processes: 10586 local.
FAILED: Build did NOT complete successfully


ManyManyThroughList::removeAll() doesn’t respect filters

Unlike DataList, HasManyList and ManyManyList, when using many-many-through ManyManyThroughList::removeAll() will discard all filters and remove everything:
// Works as expected, relation is removed for all items except those with IDs in the $processedIDs array
foreach ($venue->AccessOptions()->exclude(['ID' => $processedIDs]) as $option) {
    $venue->AccessOptions()->remove($option);
}

// Removes all related items, including those in the $processedIDs array
$venue->AccessOptions()->exclude(['ID' => $processedIDs])->removeAll();

Acceptance criteria

[ ] Calling removeAll on a filtered ManyManyThroughList only remove relations for items matching the filter.

PRs

#10295

Probably worth back porting all the way back to 4.9.

@maxime-rainville, I've done tests on my local and ran unit tests as well. I could merge if you don't have any other questions.

All happy


sc-6823 GDS UI : make the stepper component label responsive on a small screen

Scope of changes
sc-6823 GDS UI : make the stepper component label responsive on a small screen
Type of change

[x] bug fix
[ ] new feature
[ ] documentation
[ ] other (describe)

Acceptance criteria

Author checklist

[x] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[ ]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[x]   Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

Codecov Report
Base: 43.94% // Head: 39.39% // Decreases project coverage by -4.54% :warning:

Coverage data is based on head (f884758) compared to base (0d7b7f9).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #822      +/-   ##
==========================================
- Coverage   43.94%   39.39%   -4.55%
==========================================
  Files         612      156     -456
  Lines       22792     2452   -20340
  Branches     1385      624     -761
==========================================
- Hits        10016      966    -9050
+ Misses      11471     1310   -10161
+ Partials     1305      176    -1129

Flag
Coverage Δ

unittests
39.39% <ø> (-4.55%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...rc/components/SectionStatus/SavedSectionStatus.tsx

...omponents/TestnetProgress/CertificateStepLabel.tsx

...src/modules/dashboard/certificate/registration.tsx

web/gds-user-ui/src/constants/trisa-base-url.ts

.../trisacrypto/directory/pkg/gds/admin/v2/options.go

.../CertificateSection/CertificateSection.stories.tsx

...er-ui/src/components/TravelRuleProviders/index.tsx

...mponents/NameIdentifier/NameIdentifier.stories.tsx

...user-ui/src/components/Section/SearchDirectory.tsx

...ds-user-ui/src/components/NameIdentifier/index.tsx

... and 447 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Can you share the evaluation procedure? Thanks!

Can you share the evaluation procedure? Thanks!

has the same question.can give me some advices?


Update whitepaper-azure-b2b-power-bi.md

updated the document for more gender specific
There is also a user name "Lucy" on the page that we need to fix later once we have approved list of gender neutral name.

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

WTD: Proposing the changes as part to the write the docs gender inclusive subject

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

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


sample_real_and_fake_latents

Thanks for your great work! Sorry for my english
But line 428 in coach.py. It should add latent_avg of style gan ?
It's right or my mistake ?

Hi @baopmessi!
Indeed, when training with the --start_from_latent_avg flag the discriminator should receive the code with the addition of the average latent code.
From my experiments the current version of the repo produces the desired editing results, but I will run an experiment with the addition of the average latents and update the repo afterwards.
Thanks for pointing that out!

Looking forward to the results from you soon ! . By the way, results in your paper without addition of the average latent code.


Fixed #26169 -- Fixed tutorial reference in reusable apps tutorial.

mysite/templates was created in Tutorial 07, not in Tutorial 02.
Current Documentation:
You created mysite/templates in :doc:Tutorial 2 </intro/tutorial02>,
and polls/templates in :doc:Tutorial 3 </intro/tutorial03>.
Corrected Documentation:
You created mysite/templates in :doc:Tutorial 7 </intro/tutorial07>,
and polls/templates in :doc:Tutorial 3 </intro/tutorial03>.

merged in ad216381fcd7d3d62f1639f9998f5a965d8eaedb, thanks.


BUG: Heroku server error

Describe the bug
Heroku is returning error, and so the graph isn't showing.
To Reproduce
Just check it out in here :- https://activity-graph.herokuapp.com/graph?username=Ashutosh00710
Expected behavior
Return without any error
Screenshots

Desktop:-

OS: Ubuntu 20.04
Browser Firefox 94.0

Refer to: #55

Service is up again with different instance


[ALLUXIO-2995] Fixed unnecessary partial caching on positioned read

https://alluxio.atlassian.net/browse/ALLUXIO-2995
When partial caching is turned on, FileInStream incorrectly caches the entire block on positioned read, even if the block is already cached in the local worker. This affects the APIs that perform positioned read, including read with offset, readFully with offset, and seek.
This PR adds a check to perform partial caching only when needed.

Reopen this to branch 1.5
https://github.com/Alluxio/alluxio/pull/5902

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16416/Failed Tests: 4org.alluxio:alluxio-core-client-fs: 1alluxio.client.file.FileInStreamTest.seekBackwardToFileBeginningorg.alluxio:alluxio-tests: 3alluxio.client.RemoteReadIntegrationTest.skip[0]alluxio.client.RemoteReadIntegrationTest.skip[1]alluxio.client.UnderStorageReadIntegrationTest.skip
Test FAILed.


Add support for list default value

First of all, thanks for a great gem!
Here's my attempt at implementing #66.
I wasn't sure how strict to be about default value type. For now, I opted for giving the user scissors and hoping they won't run with them.
Hope you don't mind I butted in like that, @tleish! Not sure if you started to work on this or not.
closes: https://github.com/rails/kredis/issues/66

@mwsteb - I don't mind at all.  While my example  in #66 shows kredis_list, I want this with other (if not all) Kredis types.  I might suggest adding more default types to this PR, or removing closes: #66 from the PR comment so additional PRs can be added with default types.

Makes sense. Since it's not a lot of code and it's all related, I can do it all in this PR.
I'm not sure about some types:

Proxy - unclear what this type is exactly and how it's used and what a typical default value would be
Cycle - setting the default value can be achieved by manipulating the order of the list - eg. Kredis.cycle "mycycle", values: %i[ three one two ]. Is adding an additional default option worth it?
Slot(s) - seems a bit contrived to be using default value for this type, but maybe I just lack imagination :)

Proxy is a base class, so I don't think you need to worry about it.   I assume it's safe to skip defaults for the other types as well for now.

Superseded by #89


No “exports” main defined in @monogrid/gainmap-js

now that monogrid is in drei users experience issues with bundling environments like next-js.
https://discourse.threejs.org/t/trying-to-use-react-three-drei-in-next-js-error-no-exports-main-defined-in-monogrid-gainmap-js-package-json/63586
Server Error
Error: No “exports” main defined in<EMAIL_ADDRESS>This error happened while generating the page. Any console logs will be displayed in the terminal window.

is this solved by adding something like this?
  "exports": {
    ".": {
      "import": "./dist/decode.js",
      "main":  "./dist/decode.umd.js", <----------
      "types": "./dist/decode.d.ts"
    },
    "./encode": {
      "import": "./dist/encode.js",
      "main":  "./dist/encode.umd.js", <----------
      "types": "./dist/encode.d.ts"
    },
    "./libultrahdr": {
      "import": "./dist/libultrahdr.js",
      "main":  "./dist/libultrahdr.umd.js", <----------
      "types": "./dist/libultrahdr.d.ts"
    },
    "./worker": {
      "import": "./dist/worker.js",
      "main":  "./dist/worker.umd.js", <----------
      "types": "./dist/worker.d.ts"
    },
    "./worker-interface": {
      "import": "./dist/worker-interface.js",
      "main":  "./dist/worker-interface.umd.js", <----------
      "types": "./dist/worker-interface.d.ts"
    }
  },

I'm not sure what's the proper fix, I have no trouble bundling with vite

or maybe I need to name the files .mjs
[...]
  "exports": {
    ".": {
      "import": "./dist/decode.mjs",
      [...]
    }
[...]

:thinking:
I'm trying to reproduce the problem with  https://github.com/pmndrs/react-three-next

good idea! i hope this is just a fluke. esm exports package.json is so complicated, i would not know how to even publish a package nowadays.

See https://publint.dev/<EMAIL_ADDRESS>It should be (note the use of .cjs):
"main": "dist/decode.umd.cjs",
"module": "dist/decode.js",
"types": "dist/decode.d.ts",
"sideEffects": false,
"type": "module",
"exports": {
  ".": {
    "types": "./dist/decode.d.ts",
    "import": "./dist/decode.js",
    "default":  "./dist/decode.umd.cjs"
  },
  "./encode": {
    "types": "./dist/encode.d.ts",
    "import": "./dist/encode.js",
    "default":  "./dist/encode.umd.cjs"
  },
  "./libultrahdr": {
    "types": "./dist/libultrahdr.d.ts",
    "import": "./dist/libultrahdr.js",
    "default":  "./dist/libultrahdr.umd.cjs"
  },
  "./worker": {
    "types": "./dist/worker.d.ts",
    "import": "./dist/worker.js",
    "main":  "./dist/worker.umd.cjs"
  },
  "./worker-interface": {
    "types": "./dist/worker-interface.d.ts",
    "import": "./dist/worker-interface.js",
    "default":  "./dist/worker-interface.umd.js"
  }
},

Ok, I kinda trust you but I wasn't able to reproduce the problem with a clean https://github.com/pmndrs/react-three-next initialization with the "untouched" library

and a yarn build produced no error

@CodyJasonBennett can you confirm this would fix the problem? or point me to a reproducibility procedure? I'm the kind of guy that likes to avoids "blind fixes" if possible

The reason this issue occurred was because Node tried to resolve your package from a CJS entrypoint (Next.js server-side), but the package only specifies the import condition (ESM-only). Since Node 14, it reads from the exports field over main when present (module is a Webpack-only field).
The use of .cjs or .mjs overrides the type key which controls which resolver Node should use for .js extensions. So, for an ESM package with "type": "module", you can use .cjs to specify a CJS entrypoint, and anything ending with .js is assumed to be ESM.
I couldn't clone this repository to implement this fix myself, but was referred here due to a downstream issue when resolving with Next.js, presumably through their app directory which uses a different compiler than our Next.js integration tests. https://publint.dev exists and can be used locally via CLI to ensure your package satisfies Node's increasingly complicated API contract.

Okay then, I've opened #36 with the fix you proposed, will be merging soon

v3.0.5 is out https://publint.dev/<EMAIL_ADDRESS>seems fine, let me know if this solves this problem, thanks for the help!

I'm going to close this as no-one else reported a similar problem. If this problem resurfaces please feel free to open again, thanks everyone


Update AboutUs

Upload photos of group members
Indicate the different roles played and responsibilities held by each team member.

Siqi: Find and list functionalities
Vedant: Saving+loading
Yufei: Student model (add, edit, delete)
Mario: StudentScore model (add, edit, delete)
Edison: GradedComponent model (add, edit, delete)


assertion in void h264_model::update_state_for_model_key when recoding

I keep getting these:
recode: recode.cpp:1033: void h264_model::update_state_for_model_key(int, model_key): Assertion `symbol == (num_nonzeros == nonzeros_observed)' failed.
Aborted

when recoding x264 video, what is that ?

@danielrh https://s3.amazonaws.com/x265.org/video/BigBuckBunny_2000h264.mp4
root@555b1942b4df:~/avrecode# ./recode roundtrip /files/BigBuckBunny_2000h264.mp4 /files/recode.mp4
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/files/BigBuckBunny_2000h264.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 1
    compatible_brands: isomavc1
    creation_time   : 2014-08-25 21:09:31
  Duration: 00:00:10.00, start: 0.083333, bitrate: N/A
    Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 3840x2160, 2027 kb/s, 24 fps, 24 tbr, 24k tbn, 48 tbc (default)
    Metadata:
      creation_time   : 2014-08-25 21:09:31
      handler_name<EMAIL_ADDRESS>FINISHED QUEUING DECODE: 1
FINISHED QUEUING DECODE: 1
FINISHED QUEUING DECODE: 1
FINISHED QUEUING DECODE: 1
FINISHED QUEUING DECODE: 1
FINISHED QUEUING DECODE: 1
FINISHED QUEUING DECODE: 2
FINISHED QUEUING DECODE: 3
FINISHED QUEUING DECODE: 1
FINISHED QUEUING DECODE: 3
recode: recode.cpp:1033: void h264_model::update_state_for_model_key(int, model_key): Assertion `symbol == (num_nonzeros == nonzeros_observed)' failed.
Aborted

@danielr I got this problem too
192:avrecode christopherfarrel$ ./recode roundtrip test.mp4  recode.mp4
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'test.mp4':
Metadata:
major_brand     : mp42
minor_version   : 0
compatible_brands: isommp42
creation_time   : 2017-11-05 04:12:54
Duration: 00:02:17.30, start: 0.000000, bitrate: N/A
Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, bt709), 1280x720 [SAR 1:1 DAR 16:9], 1434 kb/s, 24 fps, 24 tbr, 90k tbn, 48 tbc (default)
Metadata:
creation_time   : 2017-11-05 04:12:54
handler_name    : ISO Media file produced by Google Inc. Created on: 11/04/2017.
Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 125 kb/s (default)
Metadata:
creation_time   : 2017-11-05 04:12:54
handler_name    : ISO Media file produced by Google Inc. Created on: 11/04/2017.
FINISHED QUEUING DECODE: 5
FINISHED QUEUING DECODE: 4
FINISHED QUEUING DECODE: 4
FINISHED QUEUING DECODE: 4
FINISHED QUEUING DECODE: 1
FINISHED QUEUING DECODE: 4
FINISHED QUEUING DECODE: 6
FINISHED QUEUING DECODE: 6
FINISHED QUEUING DECODE: 1
FINISHED QUEUING DECODE: 1
Assertion failed: (symbol == (num_nonzeros == nonzeros_observed)), function update_state_for_model_key, file recode.cpp, line 1033.
Abort trap: 6

@danielrh I got this same problem too ,are you fix the this now?

Aborted (core dumped)


Extension Debug Mode

Before filing a bug report for VS Code, it's best practice to first disable all extensions to ensure that an extension isn't causing the issue. The workflow for going through this process looks like the following:

Make a list of all of your disabled extensions.
Disable all extensions.
Verify bug.
Enable all extensions.
Go through list of your extensions that should be disabled and manually disable each one again.

Instead, it'd be nice to put enabled extensions into a temporarily disabled (debug) mode. The workflow would then look more like this:

Enable debug mode.
Verify bug.
Disable debug mode.

There's a Reload Window with Extensions Disabled command you can use to temporarily set all extensions to disabled. Reloading the window again will revert extensions to their previous state.

Perfect!


fix #952 doesn't fix the right issue!

fix(oidc): single logout https://github.com/AxaGuilDEv/react-oidc/pull/952
FIXES https://github.com/AxaGuilDEv/react-oidc/issues/944 AND https://github.com/AxaGuilDEv/react-oidc/issues/947
BUT NOT THIS ISSUE: (https://github.com/AxaGuilDEv/react-oidc/issues/948)
Originally posted by @guillaume-chervet in https://github.com/AxaGuilDEv/react-oidc/issues/948#issuecomment-1419628364

My bad. Conf needs monitor_session = true!


fix(migration): Use valid column type for MariaDB.

When running database migrations using a MariaDB backend, the migration
fails due to an issue related to
(https://code.djangoproject.com/ticket/2495).
Closes #1398

readthedocs.org only runs on Postgres so there is no intend to support other database backends. However since this change does not add any complexity I'm a +0 on this.

I need to think a bit more about this. It seems like a sane request, but seems odd South would generate a Postgres-specific migration. Is this an artifact of using old South?
The proper solution is probably an upgrade to Django 1.8, and a conversion to Django's new migration system.

@gregmuellegger, understood. We don't actually use MySQL any longer either, but I thought I'd see if you were interested in having this upstreamed in case someone else didn't have the option to not use MySQL.
@ericholscher based on the Django discussion I think it's an issue with MySQL, or at least the migration provider not working around the issue in MySQL. Perhaps @gregmuellegger #1420 change will resolve this issue (Though I won't be able to test that theory since I no longer have a MySQL database).

We are migrating over to Django 1.8 and the new migrations framework anyways. Maybe you could try out the new migrations on MySQL and see if they pass? I assume they do. So we should more wait on the Django 1.8 PR #1420 to get merged than including this temporary fix for MySQL.

#1420 has been merged. Closing out this pull request.


download content should allow for content-encoding conversion.

This is clearly a picofeed issue but I post it here too.
If a feed source publishes content in, say, ISO-8859-2, it should be possible to convert it to UTF-8 before miniflux displays it. Otherwise all we get is a bunch of question marks.

@stopped Any content that is fetched from a website by the grabber is automatically converted to UTF-8 for a long time now. I've the impression this ticket is kind of outdated.
Would you please close the ticket!

Closing this ticket, reopen if you stil having the issue. Thanks.


Migration storage in xtransfer

With PR59 merged, storage used to store resource id was removed, should clean the storage in migration script.

Also need to do migration with PR78 being merged

#78 already was merged, close this issue.


Defines the output of marked parser

I want to customize some of Marked's markdown.
For example i wanna add a class that will wrap code markdowns.
i can see that Marked is giving the option to customize the parser by implementing "render" object and add it to the options:
[https://marked.js.org/using_pro]
but i cant see an option to do that by using typedoc
i think it would be great if we can use it throw typedoc
maybe you can add a string in the Typedoc json file that refer to a js file that implement the render object.

You can do this by using a .js config file and specifying markedOptions: https://typedoc.org/guides/options/#markedoptions


Resolve ts stucks

What did you do?

TiDB cluster with 8.1 TiKV and 7.5 CDC
create kafka simple protocol changefeed
no workload running

What did you expect to see?
CDC resolved ts should be normal
What did you see instead?
CDC resolved ts stucks

Versions of the cluster
TiKV version
Release Version:   8.1.0
Git Commit Hash:   56613f7c3e28c02853cc51d15bc1b77f68b58be8
CDC version:
Release Version:  7.5
Git Commit Hash:  29dae6c0caaad7fe3f8d74ded151d2627253af01

/assign @asddongmen

It shows that the frontier consume a huge amount of cpu:

And log below can be found in the upstream TiKV:
> wc -l tikv-2024-05-08T15-09-29.950.log
 6186489 tikv-2024-05-08T15-09-29.950.log
> grep "cdc send event failed, full" tikv-2024-05-08T15-09-29.950.log | wc -l
 6186448

It seems that the issue arises because the number of tables and the resolvedTs value exceed the frontier's ability.

cc @hicqu This PR https://github.com/pingcap/tiflow/pull/10506 is needed cherry-pick to v7.5.2.

/severity major


Like

Describe the bug
"Like" feature appears not to work in latest version?
Information

Version of Medoo: 2.0.1
Type of Database :  MySQL
System : Linux:

Detail Code
It appears the LIKE functionality has stopped working in version 2.0.1.  Previously noted working correctly in 1.7.3.
As detailed here : https://medoo.in/api/where
I am using
$database->select("person", "id", [
	"city[~]" => "lon",
         "status" => 1
]);

the actual output of the query is
 WHERE (`city` LIKE 'lon') AND `person.status` = 1

(missing % signs)
Expected output
I would expect the final query to contain
"WHERE city LIKE '%lon%';

We tested it, and it indeed outputs as %lon% as expected.
What PHP version are you using?

Version 7.3.9;
However, I've done some more digging and realised that it is a hyphen sign that is causing issues.
I did simplify my example and I really shouldn't have. Apologies. The actual code that doesn't work in 2.0.3 but did in 1.7.3 is :
select("shift", "*", ["notes[~]" => "SSP-"]);

The hyphen breaks it. With the hyphen I lose the % symbols. Without the hyphen I get
%SSP%

The hyphen is one of the wildcard characters for LIKE, and it fixed it on v2.0.
For quoting SSP-, you may need to manually add % on the front and the end.


New package: Corgi v0.0.1

Registering package: Corgi
Repository: https://github.com/Scurrra/Corgi.jl
Created by: @Scurrra
Version: v0.0.1
Commit: 7151f8cf9db53841fe680670d4a6b160e8f2886b
Reviewed by: @Scurrra
Reference: https://github.com/Scurrra/Corgi.jl/commit/7151f8cf9db53841fe680670d4a6b160e8f2886b#commitcomment-121432280
Description: ML Algorithms from scratch in Julia

Hi @Scurrra, thanks for the contribution!
Could you explain a little better how your framework differs from established ones like MLJ.jl ?
At the moment it only seems to contain a few preprocessing utilities, with no docs or readme.

Hi @Scurrra, thanks for the contribution! Could you explain a little better how your framework differs from established ones like MLJ.jl ? At the moment it only seems to contain a few preprocessing utilities, with no docs or readme.

Hi @gdalle, Yes for now it only contains some preprocessing tools, but in next versions it will contain some very custom things I've not seen in other packages.
[noblock]

[noblock]
Could you explain one thing: I can't release package because of its name is to similar to packages Norg and Korg?
┌ Info: Name is not too similar to existing package names
│ meets_this_guideline = false
└ message = "Package name similar to 2 existing packages.\n 1. Similar to Korg. Damerau-Levenshtein distance 2 is at or below cutoff of 2.\n 2. Similar to Norg. Damerau-Levenshtein distance 2 is at or below cutoff of 2."
ERROR: LoadError: RegistryCI.AutoMerge.AutoMergeGuidelinesNotMet("The automerge guidelines were not met.")

Yes for now it only contains some preprocessing tools, but in next versions it will contain some very custom things I've not seen in other packages.

Thanks for your answer. I'm not sure this package is ready to be registered yet, maybe add a few more things to it beforehand? See the guidelines here.

I can't release package because of its name is to similar to packages Norg and Korg?

Exactly, that is expected behavior. Most Julia package registrations are automatic, and to prevent namespace pollution or accidental installation of wrong packages, a minimum distance between names is enforced. If this minimum distance check fails, a human has to merge the PR.
I personally don't have merge rights, I just happen to be invested in the Julia ML community, and so I took the liberty to ask for details :)

[noblock]
@gdalle , and one more question. Doesn't your comments block merging without "[noblock]" attribute?

@gdalle , and one more question. Doesn't your comments block merging without "[noblock]" attribute?

In theory it does, but since this PR has failed automatic merging it doesn't change anything (as far as I know) because a human would have to look at it anyway.

Oh, thanks for your help and interest anyway!
But I at least leave it in my comment [noblock]

In some cases you can change the package and relaunch the PR, leading the automatic tests to succeed. Then my comments would be problematic.
But here the name is a problem, and if you change the package name and re-register it will be a new PR anyway :)

The name really isn’t a problem. The distance check is 95% false positives. I agree though that the functionality and documentation isn’t quite ready yet for registering in General, and I’d leave a blocking comment based on that. But you can definitely retrigger registration once you add a little bit more content, keeping the same package name.


fix: ssl need to be update when secret has been changed

Please answer these questions before submitting a pull request

Why submit this pull request?

[x] Bugfix

[ ] New feature provided

[ ] Improve performance

[ ] Backport patches

Related issues
#324

@gxthrj Now we only verify that data are passed to the DP but the verifications of the use of these certificates are missing.

@gxthrj Now we only verify that data are passed to the DP but the verifications of the use of these certificates are missing.

Yes, you are right, I will add it.

Codecov Report

Merging #337 (7a49678) into master (8006297) will decrease coverage by 0.29%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #337      +/-   ##
==========================================
- Coverage   43.72%   43.43%   -0.30%
==========================================
  Files          40       39       -1
  Lines        3428     3442      +14
==========================================
- Hits         1499     1495       -4
- Misses       1761     1777      +16
- Partials      168      170       +2

Impacted Files
Coverage Δ

pkg/ingress/controller/secret.go
0.00% <0.00%> (ø)

pkg/apisix/cluster.go
28.44% <0.00%> (-5.97%)
:arrow_down:

test/e2e/e2e.go

pkg/apisix/resource.go
78.43% <0.00%> (+0.21%)
:arrow_up:

pkg/apisix/route.go
44.17% <0.00%> (+0.22%)
:arrow_up:

pkg/apisix/upstream.go
48.04% <0.00%> (+1.80%)
:arrow_up:

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 8006297...7a49678. Read the comment docs.


Simple Token example contract finalization

A new example contract has been created - https://github.com/EOSIO/eos/blob/dispatch2/contracts/simple.token/simple.token.cpp, however, it is not documented currently.
ACT:

Tests are implemented and passing
Contract is documented - description, example usage, code comments
ABI is implemented
README.md is implemented

Simple.token is deprecated in favor of eosio.token.


Code review

Depends on math-io/float64-exponent#1 and math-io/float64-from-words#1.

We should probably also rename this module as float64-frexp.

Updated deps.

Looks all well to me. One comment: I would refrain from using modules like const-ninf-float64 in example code. These modules hide native JS values, and without reading the source code it might not be clear for a third-party what these constants represent.

Point taken. Without comments, ninf and pinf are opaque. The main reason for using these modules is to distinguish from const-ninf-float32, etc. I suppose for the purposes of example code, using Number.POSITIVE_INFINITY, etc, for built-in constants is fine, but not so for underlying implementations where constant type matters and should be explicit.

Updated.


Standalone dashboard not being populated per the readme

This can be replicated using any of the following

preview-4
preview-5
preview-5 & PR-191

The steps were the same, from the StandaloneDashboard sample directory ( .\samples\StandaloneDashboard) do the following:

run the dashboard via docker
run the console app
view the dashboard @ http://localhost:18888/ and check the the logs, metrics and traces - all were empty

I've attached the logs of the 3 runs as files as their output is quite prolific but not wildly informative to my eyes.
preview-4-output.md
preview-5-output.md
preview-5-pr-191-output.md

You have to set the address of the otlp endpoint in the application:
https://github.com/dotnet/aspire-samples/tree/main/samples/StandaloneDashboard#configure-opentelemetry
cc @JamesNK

Thanks for the quick reply.
Isn't that provided out of the box?
https://github.com/dotnet/aspire-samples/blob/main/samples/StandaloneDashboard/ConsoleApp/appsettings.json#L7

Is the dashboard successfully running in docker with the ports exposed?

Closing as I had a user environment variable set for OTEL_EXPORTER_OTLP_ENDPOINT which is why no logs were appearing.
Thank you for your time, sorry to waste it.


Applied searchbox theme to the page selector.

commented here https://github.com/cedvdb/phone_form_field/issues/228#issuecomment-2027959908

should be fixed now here https://github.com/cedvdb/phone_form_field/blob/main/lib/src/country_selector_navigator.dart#L249