Deployment error

What did you do?
we are using kube-prometheus and just did an upgrade (old version was around 300 days). In the upgrade process we bumped most of the versions to latest and added a pvc. We have 2 AKS clusters (QA and PROD). Exact same setup different node count. We did a kubectl delete -f manifests and then an apply on the new manifest files. The QA upgrade went fine everyting started right away. The prod upgrade didn't. Prometheus-k8s-0 is in a restart loop (83 times in the last 8 hours). Prometheus-k8s-1 and alertmanager-main-2 is in a creating/terminating loop. (
Did you expect to see some different?
All pods should be ready and not in loop state.
Environment
AKS

Prometheus Operator version:
quay.io/coreos/prometheus-operator:v0.30.1

Kubernetes version information:
kubectl version

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.3", GitCommit:"5e53fd6bc17c0dec8434817e69b04a25d8ae0ff0", GitTreeState:"clean", BuildDate:"2019-06-07T09:55:27Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
AKS

Manifests:

local k = import 'ksonnet/ksonnet.beta.3/k.libsonnet';  // https://github.com/ksonnet/ksonnet-lib/blob/master/ksonnet.beta.3/k.libsonnet - imports k8s.libsonnet
// * https://github.com/ksonnet/ksonnet-lib/blob/master/ksonnet.beta.3/k8s.libsonnet defines things such as "persistentVolumeClaim:: {"
//
local pvc = k.core.v1.persistentVolumeClaim;  // https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.11/#persistentvolumeclaim-v1-core (defines variable named 'spec' of type 'PersistentVolumeClaimSpec')

local kp =
  (import 'kube-prometheus/kube-prometheus.libsonnet') +
  // Uncomment the following imports to enable its patches
  // (import 'kube-prometheus/kube-prometheus-anti-affinity.libsonnet') +
  // (import 'kube-prometheus/kube-prometheus-managed-cluster.libsonnet') +
  // (import 'kube-prometheus/kube-prometheus-node-ports.libsonnet') +
  {
    _config+:: {
      namespace: 'monitoring',

      versions+:: {
        prometheusOperator: "v0.30.1",
        prometheusConfigReloader: "v0.30.1",
        prometheus: "v2.10.0",
        nodeExporter: "v0.18.1",
      },
    },

  prometheus+:: {
      prometheus+: {
        spec+: {  // https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#prometheusspec
          // If a value isn't specified for 'retention', then by default the '--storage.tsdb.retention=24h' arg will be passed to prometheus by prometheus-operator.
          // The possible values for a prometheus <duration> are:
          //  * https://github.com/prometheus/common/blob/c7de230/model/time.go#L178 specifies "^([0-9]+)(y|w|d|h|m|s|ms)$" (years weeks days hours minutes seconds milliseconds)
          retention: '30d',

          // Reference info: https://github.com/coreos/prometheus-operator/blob/master/Documentation/user-guides/storage.md
          // By default (if the following 'storage.volumeClaimTemplate' isn't created), prometheus will be created with an EmptyDir for the 'prometheus-k8s-db' volume (for the prom tsdb).
          // This 'storage.volumeClaimTemplate' causes the following to be automatically created (via dynamic provisioning) for each prometheus pod:
          //  * PersistentVolumeClaim (and a corresponding PersistentVolume)
          //  * the actual volume (per the StorageClassName specified below)
          storage: {  // https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#storagespec
            volumeClaimTemplate:  // (same link as above where the 'pvc' variable is defined)
              pvc.new() +  // http://g.bryan.dev.hepti.center/core/v1/persistentVolumeClaim/#core.v1.persistentVolumeClaim.new

              pvc.mixin.spec.withAccessModes('ReadWriteOnce') +

              // https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.11/#resourcerequirements-v1-core (defines 'requests'),
              // and https://kubernetes.io/docs/concepts/policy/resource-quotas/#storage-resource-quota (defines 'requests.storage')
              pvc.mixin.spec.resources.withRequests({ storage: '100Gi' }) +

              // A StorageClass of the following name (which can be seen via `kubectl get storageclass` from a node in the given K8s cluster) must exist prior to kube-prometheus being deployed.
              pvc.mixin.spec.withStorageClassName('default'),

            // The following 'selector' is only needed if you're using manual storage provisioning (https://github.com/coreos/prometheus-operator/blob/master/Documentation/user-guides/storage.md#manual-storage-provisioning).
            // And note that this is not supported/allowed by AWS - uncommenting the following 'selector' line (when deploying kube-prometheus to a K8s cluster in AWS) will cause the pvc to be stuck in the Pending status and have the following error:
            //  * 'Failed to provision volume with StorageClass "ssd": claim.Spec.Selector is not supported for dynamic provisioning on AWS'
            //pvc.mixin.spec.selector.withMatchLabels({}),
          },  // storage
        },  // spec
      },  // prometheus
    },  // prometheusspec

  };

{ ['00namespace-' + name]: kp.kubePrometheus[name] for name in std.objectFields(kp.kubePrometheus) } +
{ ['0prometheus-operator-' + name]: kp.prometheusOperator[name] for name in std.objectFields(kp.prometheusOperator) } +
{ ['node-exporter-' + name]: kp.nodeExporter[name] for name in std.objectFields(kp.nodeExporter) } +
{ ['kube-state-metrics-' + name]: kp.kubeStateMetrics[name] for name in std.objectFields(kp.kubeStateMetrics) } +
{ ['alertmanager-' + name]: kp.alertmanager[name] for name in std.objectFields(kp.alertmanager) } +
{ ['prometheus-' + name]: kp.prometheus[name] for name in std.objectFields(kp.prometheus) } +
{ ['prometheus-adapter-' + name]: kp.prometheusAdapter[name] for name in std.objectFields(kp.prometheusAdapter) }

Prometheus Operator Logs:

E0614 12:12:08.926810       1 operator.go:321] Sync "monitoring/main" failed: synchronizing governing service failed: updating service object failed: Operation cannot be fulfilled on services "alertmanager-operated": the object has be │
│ en modified; please apply your changes to the latest version and try again

Prometheus Logs:

This is from prometheus-config-reloader
ts=2019-06-14T12:01:41.431103954Z caller=main.go:35 msg="Starting prometheus-config-reloader version '0.22.2'."                                                                                │
│ level=info ts=2019-06-14T12:01:41.629023506Z caller=reloader.go:77 msg="started watching config file for changes" in=/etc/prometheus/config/prometheus.yaml out=/etc/prometheus/config_out/prometheus.env.yaml                             │
│ level=info ts=2019-06-14T12:01:41.968827096Z caller=reloader.go:182 msg="Prometheus reload triggered" cfg_in=/etc/prometheus/config/prometheus.yaml cfg_out=/etc/prometheus/config_out/prometheus.env.yaml rule_dir=                       │
│ hash file: open /etc/prometheus/config/prometheus.yaml: no such file or directory

From rules-config-reloader
failed to watch file "/var/log/pods/9a11d814-8de0-11e9-b29b-0a58ac1f0ec1/rules-configmap-reloader/0.log": no space left on device

Anything else we need to know?:

failed to watch file "/var/log/pods/9a11d814-8de0-11e9-b29b-0a58ac1f0ec1/rules-configmap-reloader/0.log": no space left on device

This looks bad, but at the same time doesn't seem like it's the prometheus operator's fault. This seems like your host doesn't have any space for the emptyDir volume.

Just checked all nodes, and none is under diskpressure or running low on disk. Tried deleting the manifests and applying them again, and can't get "no space left on device erorr" again. All the other errors are still present.

Your fixed may have worked for you but I've struggled with this a couple of times. Leaving this note to help others and perhaps I'll stumble on it in 6 months when I do another EKS upgrade and this resurfaces: The node this pod is living on has somehow corrupted, whether via memory leak or otherwise ( maybe https://github.com/moby/moby/issues/29638 ?) . Regardless, terminating the node that this pod is attempting to run on and firing a new one up has fixing the issue on a couple occasions.

Seems like the issue is not directly related to kube-prometheus, but it is an issue with a cloud provider infrastructure.


chore: bdd-nh-1588673804 to 0.0.1

chore: Promote bdd-nh-1588673804 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Not working for keyboard shortcuts

Error Notification "command 'extension.vscode-git-automator.pushLocalCommits' not found"

Issue Type: Performance
Extension Name: sqltools
Extension Version: 0.21.0
OS Version: Windows_NT x64 10.0.17763
VSCode version: 1.38.1

:warning: Make sure to attach this file from your home-directory:
:warning:C:\Users\Nirzaf\mtxr.sqltools-unresponsive.cpuprofile.txt
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

@nirzaf  This issue is not from this extension. Closing.


include init action in LogMonitor

include init action in LogMonitor

don't slice away init from items$
use canRevert$ to disable both the Reset and Revert buttons
prevent reverting or resetting the init action
style the init (first) action to reflect that it cannot by undone

Net effect: the ng store init action is logged and permanently remains
the first log entry in the monitor, and both Reset and Revert operations
are always disabled for the init action.

I force-pushed a rebased rendition with a proper commit message.

I ended up having to revert this PR. Styling didn't quite work and there was a problem in the template (missing a closing tag). Let's revisit after we get testing infrastructure in place.

Ugh. That'll teach me to do PRs in the morning. There's a missing quote on line 59. :(


Investigating about DelayedRender component in fluent

there is a component named DelayedRender that use in several components, it seems to make some delay to the inner child of it get render, but there is some confusion about working of this component that should be clear to be able to implement it in Bit

This issue is not valid anymore.


Allow for non default port grafana instances for get_snapshot_by_key

Changed the hard-coded port value in Snapshots.get_snapshot_by_key, this will allow for non default port deployment compatibility.

( Added a missing reference to Snapshots in the additional fixup commit )


ci: Add a new run-script workflow

Overview
The existing run-cluster.yaml script is quite opinionated on certain things:

the entrypoint script must be a python script
it must be invoked as a standalone script (i.e., no running modules via python -m module.sub_module)
ray job submit ... is a hard-coded step in the workflow

These things make the run-cluster workflow nice for more opinionated workflows. However, a more generic script which is not as opinionated will allow us to run a wider variety of commands (e.g., custom bash scripts which can submit jobs in the way it wants to).
This PR introduces a new workflow, run-script, which provides this interface.
Usage
You can pass in any arbitrary command as the input. Even try ls -las.
A more useful command to pass in would be ci/entrypoints/tpcds.sh (i.e., gh workflow run run-script.yaml --ref refactor/run-cluster -f entrypoint="ci/entrypoints/tpcds.sh".
(As a shortcut, instead of running the above command manually, you can just run scripts/run-tpcds-benchmarking.sh instead, which runs that exact command).
Limitations

cluster-profiles not yet implemented (small deliverables!)
only runs medium-x86; will expand to more in a follow-up PR
currently only runs latest released version of daft; will update to run a specific wheel

Example of a successful run:
https://github.com/Eventual-Inc/Daft/actions/runs/12323937114


upsample_nearest2d

If I set this opset_version to version 12, how do I change upsample_nearest2d，can you tell me?

What operators do you want support for from version 12?


Failure in Make progress in Step 2

When I tried to build the project as directed, it reaches approximately 57% on the terminal before I get errors that prevent completion of the build. I've attached a text document that has the terminal entries for the build.
Terminal Errors.txt

How to search device?
please


[FEATURE] Text Entered by User Should be Line breaked as it is he entered

Description
I observed that text entered by user is not coming as it is rather it is compressing . It's a backend and frontend Work that is taking the user data with line break and then sending it while fetching should be taken as it is.
I want to fix this issue.
Please assign me this issue as a GSSOC'23 Contributor.

Screenshots
No response
Additional information
No response

@narayan954 Waiting for this issue to be assigned to me !!

goo ahead!


Packaging updates

Fixes #4
Uses Poetry instead of setuptools

One concern: Apparently support for minimum Python versions only landed in Pip 9 (2016-11-02) and Setuptools 24.2.0 (2016-07-20).
Even Debian Stretch has these versions... but Ubuntu Xenial doesn't. Given that Xenial is EOL and drops security updates in less than a month, I'm personally comfortable moving ahead with this.

Can we split this into separate PRs that do various bits? E.g. I don't like burying the reformatting with black into a PR about packaging (especially if we squash merge this we then can't ignore the commit for git blame).

Would you be comfortable with a rebase and merge? Each commit is pretty self-contained as is.

Would you be comfortable with a rebase and merge? Each commit is pretty self-contained as is.

That should be fine too! 👍 It's just useful to have the reformatting(s) separate!

Awesome. Going for it and publishing updated package to PyPI


Simple UX

As potential future MobyMask extension power user, I want to suggest making UX as straightforward as possible.
Allowing users to report scammers in 1 click will be a huge UX advantage over the Twitter-native experience.
(Counted 10 clicks to report this scammer acc:)
UI drafts:

I agree, I'd mocked up something similar like this:

We actually have a group working on making a browser extension for reporting, this could be a nice way to do it.
Here is an invite link to our discord. It's good for one use, I hope you're the first person to claim it! I believe some phishers are trying to gain membership now. Please reply if you do use it so I trust whoever joins :)

@danfinlay thanks for the link! Just joined the server :)


Update Random Doubles

Wiki Berry and the like are so good in doubles that Gluttony is worth it for them, even without Belly Drum. Simple, on the other hand, is actually a detriment without any setup moves. Also, there are no Pokemon with both Marvel Scale and Psycho Shift, so I'll assume that's an error caused by copy/pasting from Magic Guard.

There's already an if statement for Simple.

Huh, must've missed that somehow. I added that in there because someone told me they'd gotten a Bibarel with Simple but no setup, but they didn't have a replay, so it might not have actually happened, or if it did it wasn't recent.

Aw shoot I mixed up which kind of merge did what.


[E2E] Java 13 support

"It's silly that I have only two options for Java."
§ What are you looking for? "Major versions. We are on like 13 right now."

The Azure Functions runtime supports JRE 1.8, also behind a few versions.
https://github.com/Azure/azure-functions-java-worker


MAINT: remove support for Python 3.7 (hence NumPy 1.16)

We should be dropping Python 3.7 with the next release (1.8), hence NumPy 1.16 will not be supported and we will move to NumPy 1.17.3.
This PR touches the setup.py, pyproject.toml, CI, some other smaller things and some documentation.
Related to recent discussions and linked to #14649. Also in accordance with NEP29 (NumPy already dropped support for 3.7 on main). And see here for official Python support. There will be just 1 year of support of 3.7 for the next release if we don't migrate now.
I think I touched everything with these 2 PRs. Just not sure about the Dockerfile.

Note:
In the process, I tried to update to ubuntu:20.04 instead of 18.04 in a few workflows, but it causes a warning FAILED scipy/stats/tests/test_continuous_basic.py::test_cont_basic[500-200-ncf-arg74]
scipy/integrate/quadpack.py:400: in quad
    warnings.warn(msg, IntegrationWarning, stacklevel=2)
E   scipy.integrate.quadpack.IntegrationWarning: The occurrence of roundoff error is detected, which prevents
E     the requested tolerance from being achieved.  The error may be
E     underestimated.

and also a different value in a doctest
File "build/testenv/lib/python3.8/site-packages/scipy/optimize/optimize.py", line 994, in check_grad
Failed example:
    check_grad(func, grad, [1.5, -1.5])
Expected:
    2.9802322387695312e-08
Got:
    4.2146848510894035e-08

I always get the ncf quadpack error on my computer.

I always get the ncf quadpack error on my computer.

Interesting, maybe something to look at after that. Or if you know a simple fix we can also do this now.

I haven't thought about a fix. Previously I had assumed it must be a very specific thing, but it sounds it's at least a little more widespread. Note that this is my Windows machine, not Ubuntu.

Platform-specific failures are always good to fix; if you see them locally while CI is green, it usually means others see them too.

Platform-specific failures are always good to fix; if you see them locally while CI is green, it usually means others see them too.

Ok, then I can re-update the CI to use 20.04 to make the CI fail. It will just not work for wheel_optimized_gcc48 as GCC version is not correct then. And I guess we don't want to change this, or do we?

Ok, then I can re-update the CI to use 20.04 to make the CI fail.

This is green now, so I'd leave that for a separate follow-up PR.

It will just not work for wheel_optimized_gcc48 as GCC version is not correct then. And I guess we don't want to change this, or do we?

We should bump the lowest GCC version, but last time we tried there was an issue on the scipy-wheels repo, so best not to do it in this PR.

Also once this is merged, scipy-wheels should be updated to match. Do you want to do that @tupui?

Ok great then! I will look at bumping GCC as soon as this merges. For the other bug, @mdhaber do you have time to take a look since you can reproduce?

It's all green, so let's give it a go - merged.

Also once this is merged, scipy-wheels should be updated to match. Do you want to do that @tupui?

Sure, glad to learn how and help with that.

@tupui Before I can think about the ncf issue I need to be able to work with SciPy master. This PR forced me to upgrade to Python 3.8 and now I get a DLL load error when I try to import any scipy subpackage; please gee gh-11062.


repeat={true} doesnt trigger onProgress

Hello! Thanks for the awesome library!
I've noticed that by having repeat={true} does not trigger onProgress. Is this intentional?
My current code is the following:
<Video source={{uri: this.props.video_src}}   // Can be a URL or a local file.
  rate={1.0}                     // 0 is paused, 1 is normal.
  volume={1.0}                   // 0 is muted, 1 is normal.
  muted={this.state.muted}                  // Mutes the audio entirely.
  paused={false}                 // Pauses playback entirely.
  resizeMode="cover"             // Fill the whole screen at aspect ratio.
  repeat={true}                  // Repeat forever.
  playInBackground={false}       // Audio continues to play when app entering background.
  playWhenInactive={false}       // [iOS] Video continues to play when control or notification center are shown.
  progressUpdateInterval={250.0} // [iOS] Interval to fire onProgress (default to ~250ms)
  onLoadStart={this._videoLoadStart}   // Callback when video starts to load
  onLoad={this._videoLoadEnd}      // Callback when video loads
  onProgress={this._setVideoProgress}      // Callback every ~250ms with currentTime
  onEnd={this._setVideoEnd}             // Callback when playback finishes

...

Why this troubles me is that Im having a countdown that count down how many seconds there still are in the video. This is reset when the video ends but when it repeats itself, the onProgress does not actually trigger which makes my code only work once but not after that.

Hmm, onProgress is being called for me, even when repeat=true
Are you still having this problem with v1.0.0?

Oh this should perhaps have been closed. I realized that my old nexus 4 was the culprit. That phone didnt trigger the onProgress. After testing it out on other phones, ths onProgress triggers correctly


Implement  .createDelegated() for ComputeCredential and ImpersonatedCredentials

FR to implement [createDelegated()]](https://googleapis.dev/java/google-auth-library/latest/com/google/auth/oauth2/ServiceAccountCredentials.html#createDelegated-java.lang.String-)   mechansm for other credential types.
Currently, only ServiceAccount credentials implements that api that allows domain-wide delegation.
This FR is to allow the other credentials to also implement it via its ServiceAccoutnSigner interface

ComputeEngineCredential.createDelegated()
ImpersonatedCredentials.createDelegated()

As an exmaple implementation, In the following article,  i've used the signer interface of these credential types to provide the equivalent createDelegated() feature

Easy GSuites Domain-Wide Delegation (DwD) in Java

Following...
Our org will disallow using SA Key soon. It would be great if our APP's SA can just impersonate domain-wide delegation SA.
It might be a more common case now as using SA key is discouraged as it does introduce security risks?


Can't load 32bit DLL

Hi Guys,
I am working on flutter windows app. I've no problem when i load win x64 DLL but 32bit dll throw me 193 error.
Please suggest any solution, the dll is for Zkteco attendance machine and no 64 dll was provided.
Thanks.

Dart SDK version: 2.17.1 (stable) (Tue May 17 17:58:21 2022 +0000) on "windows_x64"
final dll = DynamicLibrary.open("zkemkeeper.dll");
[ERROR:flutter/lib/ui/ui_dart_state.cc(198)] Unhandled Exception: Invalid argument(s): Failed to load dynamic library 'zkemkeeper.dll': error code 193
#0 _open (dart:ffi-patch/ffi_dynamic_library_patch.dart:12:43)
https://github.com/dart-lang/samples/pull/1 new DynamicLibrary.open (dart:ffi-patch/ffi_dynamic_library_patch.dart:23:12)
https://github.com/dart-lang/samples/pull/2 main
package:mgx/main.dart:11
https://github.com/dart-lang/samples/pull/3 _runMainZoned.. (dart:ui/hooks.dart:130:25)
https://github.com/dart-lang/samples/pull/4 _rootRun (dart:async/zone.dart:1426:13)
https://github.com/dart-lang/samples/issues/5 _CustomZone.run (dart:async/zone.dart:1328:19)
https://github.com/dart-lang/samples/issues/6 _runZoned (dart:async/zone.dart:1861:10)
https://github.com/dart-lang/samples/issues/7 runZonedGuarded (dart:async/zone.dart:1849:12)
https://github.com/dart-lang/samples/pull/8 _runMainZoned. (dart:ui/hooks.dart:126:5)

It is not possible to load a 32 bit DLL in a 64 bit executable.

Thanks for you reply, i'll try it.


Clean up Pad idle qubits at your own risk

Summary
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

23 of 24 (95.83%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 51.198%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_provider/transpiler/passes/scheduling/block_base_padder.py
20
21
95.24%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
3354

Relevant Lines:
6551

💛  - Coveralls

Hi @taalexander , please let me and @kt474 know what you'd like to do with this PR. It's been open for a few months and has accumulated some conflicts. Do you still want this to be reviewed? If so, please provide details about the changes.

Closing for now, feel free to reopen if still necessary


[Material You] Menus

This is a tracking issue for the following Material You components: Menus
Specification

Kamino closed and cloned this issue to Awesome-Freya/freya-material


Translation Feature Flooding Chatlog

Whenver a certain string of message is said, translation is trying to pick it up and starts a loop of it. I have a few examples of this occurring in game since 5.35 has dropped.
Here's one example of the bug when my FC member goes "T-T" in chat and starts immediately flooding the chat:
Here's another example of the translation feature bugging out. This was during the Bozjan Southern Front raid where someone shouted out their hallway was clear (C) and it proceeded to bug out the translation feature:

The only two ways I have seem to resolve this issue are:

Disable the program entirely in Dalamuld

Let it flood for approximately a minute before it stops, which the macro (I need for raid) is lost in the flood.

I have this problem too, any solution?


Support default domain

Since the referer is not always present, I propose a default domain configuration that is more reliable for reconstructing the absolute URL.

would it be better if uses Astro's site as a default instead?

Oh my bad! I forgot this is universal module.

would it be better if uses Astro's site as a default instead?

It can be an alternative source 👍🏻


Uninitialized Constant Spree::ReviewSetting (NameError) in Rails 7

Got the following error after upgrading the system to Rail 7
~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/bundler/gems/spree_reviews-c3069ddb8026/lib/spree_reviews/engine.rb:13:in `block in <class:Engine>': uninitialized constant Spree::ReviewSetting (NameError)

      Spree::Reviews::Config = Spree::ReviewSetting.new
                                    ^^^^^^^^^^^^^^^
Did you mean?  Spree::Reviews
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:32:in `instance_exec'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:32:in `run'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:61:in `block in run_initializers'
	from ~/.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:228:in `block in tsort_each'
	from ~/.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
	from ~/.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:422:in `block (2 levels) in each_strongly_connected_component_from'
	from ~/.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:431:in `each_strongly_connected_component_from'
	from ~/.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:421:in `block in each_strongly_connected_component_from'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:50:in `each'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:50:in `tsort_each_child'
	from ~/.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:415:in `call'
	from ~.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:415:in `each_strongly_connected_component_from'
	from ~/.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:349:in `block in each_strongly_connected_component'
	from ~/.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:347:in `each'
	from ~/.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:347:in `call'
	from ~/.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:347:in `each_strongly_connected_component'
	from ~/.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:226:in `tsort_each'
	from ~/.rbenv/versions/3.2.2/lib/ruby/3.2.0/tsort.rb:205:in `tsort_each'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/initializable.rb:60:in `run_initializers'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/application.rb:372:in `initialize!'
	from ~Development/Mobolet/mobolet_server/config/environment.rb:5:in `<top (required)>'
	from <internal:~/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
	from <internal:~/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/polyglot-0.3.5/lib/polyglot.rb:65:in `require'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/zeitwerk-2.6.11/lib/zeitwerk/kernel.rb:38:in `require'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/application.rb:348:in `require_environment!'
	from ~benv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/command/actions.rb:28:in `require_environment!'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/command/actions.rb:15:in `require_application_and_environment!'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/generate/generate_command.rb:21:in `perform'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/thor-1.2.2/lib/thor/command.rb:27:in `run'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/thor-1.2.2/lib/thor/invocation.rb:127:in `invoke_command'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/thor-1.2.2/lib/thor.rb:392:in `dispatch'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/command/base.rb:87:in `perform'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/command.rb:48:in `invoke'
	from ~/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/commands.rb:18:in `<top (required)>'
	from <internal:~/rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
	from <internal:~/.rbenv/versions/3.2.2/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:38:in `require'
	from bin/rails:8:in `<main>'

Seems resolved in the latest version for Spree 4.5 support.


refactor _copy_files_to_new_dir to always delete tmp directories

We currently avoid temp directories in rasa train commands by making sure that each of the different functions in training delete all temporary files upon exiting. However this isn’t super scalable, as we would also have to do the same for rasa data, rasa interactive, rata test, etc. commands. Instead we should refactor the method that actually creates these directories.
From @federicotdn:

The problem comes from the usage of function _copy_files_to_new_dir in rasa/data.py. The function you mentioned, get_core_nlu_directories, uses this function, and other do as well.

A call to these functions in data.py implies creating a temp directory and returning some path relative to it. The definitive solution to the problem would be making _copy_files_to_new_dir return a context manager and then change all uses of the functions in data.py to enter/exit the context manager appropriately.

A valid way to do this would be changing _copy_files_to_new_dir to return a TempDirectoryPath (once https://github.com/RasaHQ/rasa/pull/3887 is merged), and then slowly change the rest of the codebase to use the return value as a context manager. TempDirectoryPath can also be used as a regular string, so nothing should break after changing this.

I am probably tackling this here https://github.com/orgs/RasaHQ/projects/25. So please wait with this issue @federicotdn

I think we still have to do this for interactive learning. train should be fixed

I'll close this as it didn't come up again and we can just re-open it in case it becomes a problem again.

Reopening this due to this forum thread

Any solution to this?

@wochinge I think the forum issue that re-opened this one was resolved by this one right? does it still make sense to keep this one?

Hm, good point, I'm not sure. It does say "on my server" and the logs of their action server look like they could come from docker-compose

Fine to close this with the model architecture revamp in my opinion.


Typo in README.md

I guess that the text "Visual Source Code" in README.md should be replaced with "VIsual Studio Code".

Thanks for pointing that out.


Issue with max_delta_step when using XGBRegressor with "count:poisson" as objective

When I use XGBRegressor (the sklearn wrapper) with "count:poisson" as objective, I obtained
XGBoostError: PoissonRegression: need to set max_delta_step
So I sat  max_delta_step to 0.7 as mentioned in the doc of parameters:
"max_delta_step is set to 0.7 by default in poisson regression (used to safeguard optimization)"
It works but the problem that I obtained poor performance and convergence comparing to the case when I use directly the API xgboost.train() and without setting value max_delta_step.
Could you have any idea about this huge difference of performance ? please
Thank you in advance

Interesting, I have no idea on what happens, perhaps what you can do is look into the routine that calls into xgb.train(since all calls of sklearn api redirects into it) and see what was the difference in terms of configurations parameters


Solver capabilities - elastic-plastic mechanical problem

Does the library is capable to solve an elastic-plastic (no contact) problem, where the hardening curve is given by a stress/strain relation? In particular I am interested in tensile and compression tests.

Yes, of course. Let us know if you need anything!


Add yaml file for a new plugin for mixing-security-realm

Description

Plugin hosting request: https://issues.jenkins-ci.org/browse/HOSTING-997
Repository link: https://github.com/jenkinsci/mixing-security-realm-plugin
@wenjunxiao  - me, to get permission
Submitter checklist for adding or changing permissions

Always

[x] Add link to plugin/component Git repository in description above

For a newly hosted plugin only

[x] Add link to resolved HOSTING issue in description above

For a new permissions file only

[x] Make sure the file is created in permissions/ directory
[x] artifactId (pom.xml) is used for name (permissions YAML file).
[x] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[x] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[x] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
[x] All newly added users have logged in to Artifactory at least once

Reviewer checklist (not for requesters!)

[ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
[ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
[ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
[ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

User name not known to Artifactory: promissing

User name not known to Artifactory: promissing

@slide This is my user name on https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=promissing,  isn't it the username of this website?

User name not known to Artifactory: promissing

@slide This is my user name on https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=promissing, isn't it the username of this website?

@wenjunxiao I believe that you need to login at least once to https://repo.jenkins-ci.org/ as that user in order for Artifactory to know that you are a user of that system.  We have over 100 000 users in the Jenkins accounts database and we only want to create accounts in repo.jenkins-ci.org when a user will need that account.

User name not known to Artifactory: promissing

@slide This is my user name on https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=promissing, isn't it the username of this website?

@wenjunxiao I believe that you need to login at least once to https://repo.jenkins-ci.org/ as that user in order for Artifactory to know that you are a user of that system. We have over 100 000 users in the Jenkins accounts database and we only want to create accounts in repo.jenkins-ci.org when a user will need that account.

Thanks!


Composable Component prop type not extended

Current Behavior
I have a composable component called Page
import { type GetProps,styled, YStack } from 'tamagui'

export const Page = styled(YStack, {
  name: 'Page',
  flex: 1,
})

export type PageProps = GetProps<typeof Page>

I am trying to give it props from YStack and the UI reacts to the props but the typescript doesn't

I have them imported in that file
import { Page, type PageProps } from "@acme/ui";

Expected Behavior
Page extends the prop type of YStack
Tamagui Version
1.79.9

Platform (Web, iOS, Android)
non-specific

Reproduction
https://github.com/psycho-baller/convo-topics

System Info
System:
    OS: macOS 14.0
    CPU: (10) arm64 Apple M1 Max
    Memory: 81.47 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.2.0 - ~/.asdf/installs/nodejs/21.2.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.13.0/bin/yarn
    npm: 10.2.3 - ~/.asdf/plugins/nodejs/shims/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 120.0.6099.109
    Firefox: 120.0
    Safari: 17.0
  npmPackages:
    @acme/eslint-config: workspace:^0.2.0 => 0.2.0
    @acme/prettier-config: workspace:^0.1.0 => 0.1.0
    @acme/tsconfig: workspace:^0.1.0 => 0.1.0
    @tamagui/animations-react-native: latest => 1.79.9
    @tamagui/build: latest => 1.79.9
    @tamagui/font-inter: latest => 1.79.9
    @tamagui/react-native-media-driver: latest => 1.79.9
    @tamagui/shorthands: latest => 1.79.9
    @tamagui/themes: latest => 1.79.9
    expo-font: ^11.6.0 => 11.6.0
    tamagui: latest => 1.79.9

This issue seems to be resolved when modules are deleted and reinstalled... Not all the time though. It's my first time working with so many overlapping packages in a monorepo.
I guess this issue isn't a Tamagui one, it's a monorepo one


[#37] isCuid(id) validates cuids

@IamManchanda Please review

Yes, that is the current structure of cuids. However, you should treat the structure of the id as a black-box from a validation/type checking perspective. If you ever decide you need to switch id solutions, you will need to do extra work if you enforce the id specification too strictly.


Something's fucky... It isn't liking my attr_reader/attr_accessor met…

…hods and I don't know why.
...I now know why. See next commit.

4.5 / 5 (-0.5 on Q3)
Great job on this, Chris. It's clear that you're building a strong understanding of this stuff.


Change angular router path for repositories and configurations

Is your feature request related to a problem? Please describe.
Related to the double active selection on the menu
Describe the solution you'd like
Make a refactor of the angular router path
1 - For repositories transform the url "/widgets/admin/repositories" to "/repositories"
2 - For configurations transform the url "/widgets/admin/configurations" to "/widget-configurations"
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
If possible provide visual sample and code impacts
NB: Specify label(s) in right panel to ease requests organization

Add missing label, it has some impacts on backend (API description)

@Juyoo : Milestone 2 or 3 ?

Milestone 2, it's already done, i'm just waiting for the for the merge of the PR #321

There are no impacts on backend API, this is just a refactoring of the internal angular routes.


Small performance optimization

Comparing a string against .Length == 0 is faster than  == string.Empty. See CA1820 about that.

Yes, this might be a bit faster, but it's in the scale of ns. In case of some extensive data operations, this would have large impact.
I'd prefer the verbosity of String.Empty in this case.
Thanks!


fix: invalid characters in the headers on Node 5.6.0

On Node 5.6.0, Karma stopped working with the following error message: "The header content contains invalid characters". It's caused by the fact that the dates put by Karma to the Expires headers contain the time zone name, which might look like 'Thu Jan 01 1970 02:00:00 GMT+0200 (Иксанија)' if a Cyrillic locale is used. While Node <5.6 allowed Cyrillics in the headers, the version 5.6.0 is much stricter. See the changelog https://github.com/nodejs/node/blob/v5.6.0/CHANGELOG.md

Thank you for your contribution. We detected an issue with your commit message though and would ask you kindly to fix it.

Commit: 61fd5087ff49f9557ed86191582159786b0c2741
Your commit message body contains a line that is longer than 80 characters

Guidelines are available at http://karma-runner.github.io/0.13/dev/git-commit-msg.html and please do not hesitate to ask if you have any questions.

This message was auto-generated by https://gitcop.com

Thank you for your contribution. We detected an issue with your commit message though and would ask you kindly to fix it.

Commit: 22fc370852c2f43f7a9bdaad84665a7c0655ded6
Your commit message body contains a line that is longer than 80 characters

Guidelines are available at http://karma-runner.github.io/0.13/dev/git-commit-msg.html and please do not hesitate to ask if you have any questions.

This message was auto-generated by https://gitcop.com

Is this bot broken? There is no lines longer then 80 characters in my commit message.

Thanks :octocat: you can ignore the bot, it sometimes isn't very clever :(

Could you release the version 0.13.20 in the very nearest future? :)

@thorn0 I'm trying to but I'm afraid it'll be 0.14 as there are some changes in master that I'd consider not a 100% non breaking.

Released as 0.13.20


Update options

How can I reload the options? For instance the color variable has been changed and I want to update the graph to display the new color.
This is just an example so which parameter that was updated could be any.

how exactly does the destroy work? I can only create new progress bar instead of grab the existing to destroy. So far, I'm successful in creating a second bar over the first, but can't get rid of the first. Ideally, I'd just grab the first one and reanimate it with the new value.

I was able to accomplish this instead by finding my current element and then clearing out the innerHTML and then creating a new progress bar in its place.


Experiment with typesafe nav

WHAT
WHY
HOW
Checklist :clipboard:

[ ] Add explicit visibility modifier and explicit return types for public declarations
[ ] Run spotless check
[ ] Run tests
[ ] Update metalava's signature text files

@BowerSteve FYI only - if we want to add early support for this we can, might flush out some bugs, or let us confirm that transition animations work.
Not urgent at all.


MessageType.clone() does not seem to clone repeated scalar field array

After cloning a message and pushing to a repeated field, the original field is modified as well.

MessageType.clone() clones correctly, but did return the input message instead of the cloned message.
Fixed in v1.0.1.


Fix Counter accepting rollover values less than or equal to zero, enf…

…orce >0 in Counter tests
Given n is defined as "number of counts before the counter resets (or one more than the maximum output value of the counter)", it makes sense that n must be strictly positive.

retest this please

retest this please


Condition route v3.1

What is the purpose of the change
Added multi-address and priority support
Brief changelog
Detailed design documentation is available here  https://github.com/apache/dubbo/issues/14344
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

My erroneous push resulted in several test commits, I will re-submit the pr here  https://github.com/apache/dubbo/pull/14356


Move the exception symbol one step up in the stack

Q
A

Bug fix?
yes

New feature?
no

BC breaks?
no

Deprecations?
no

Related tickets

Documentation
https://github.com/php-http/documentation/pull/118

License
MIT

While making screenshots for the documentation I noticed that the exception symbol was misplaced. Consider the screenshot below.
When an exception is thrown at the error plugin we should have the big red X next to it. Before this PR the symbol appeared first at the content_length plugin.

Thank you for merging


Updated client functionalities of job and service handling

Added client level functionalities to deploy single /multiple jobs, delete single / multiple jobs, check job status, get job logs and metadata, wait for job completion.

Added client level functionalities to deploy single /multiple services, delete single / multiple services, check service status, get service logs and metadata.

Added a null check for the job - started_at and stopped_at fields in the UI.

Discrepancies with respect to the commit files


wiki: restrict access permissions for the repository wikis

https://help.github.com/en/articles/changing-access-permissions-for-wikis
seems the wiki page is editable for anyone and there will be some interfering message every now and then. such as this one

what about restrict the access permissions for the repository's wikis
@rakyll @jbuberel @natefinch seems you have discussed it before in this issue https://github.com/golang/go/issues/13226

We already have a place with "official" docs and restricted access: the golang.org website. The point of the wiki being open is to have a place where non-project-members are allowed to freely add documents/links and share knowledge. It's still a curated archive (a few Go organization members are subscribed to wiki changes and usually bad edits are noticed and reverted quickly), but more open than a place where every change needs to be approved.
Since github wikis don't allow PRs, if we restrict access we'll have to take changes suggestions on the issue tracker, and a project member will have to apply the change (no PR means that I can't approve and commit a change by pressing a button: I have to manually edit the page to apply the suggested diff). It's not very convenient.

I agree.  There is nothing to do here.


[Go] googleai: revised plugin design

This illustrates the new plugin design:

Plugins are initialized with an Init function that holds
configuration.

All models and other entities are defined in Init.

Plugins have global state.

Configured values can be retrieved by top-level functions that
take strings as arguments.

We set up state initially and then look it up again later. Why not just return it?

I agree with you, but the JS folks are more comfortable with action-at-a-distance than we are. They want the convenience of not having to plumb the state through the program. I can see their point of view.


WSL 2.0.9 update breaks DNS resolution and prevents connectivity including pings and downloads

Windows Version
Microsoft Windows [version 10.0.22621.2715]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-1
Distro Version
Debian 11
Other Software
VSCode
Version: 1.85.0 (user setup)
Commit: af28b32d7e553898b2a91af498b1fb666fdebe0c
Date: 2023-12-06T20:48:09.019Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Repro Steps
Notice all DNS-related activities are not functioning, including:

Failure when running curl -m 5 -v https://microsoft.com.
Inability to download any packages or files.
Unsuccessful pings to known IP addresses, such as ping <IP_ADDRESS>.

Expected Behavior
WSL should resolve DNS requests and allow for standard internet connectivity for downloads and responses to pings to known IPs, consistent with pre-update functionality.
Actual Behavior
After the update to WSL version 2.0.9, the subsystem fails to resolve DNS requests. This issue is highlighted by the inability to use curl for downloads, connect to external services, or even ping external IP addresses, such as Google's public DNS at <IP_ADDRESS>. The issue persists even after updating to WSL version 2.0.14, with no rollback options available.
Please note i don't have VPN or Proxy enabled.
curl -m 5 -v https://microsoft.com
* Could not resolve host: microsoft.com
* Closing connection 0
curl: (6) Could not resolve host: microsoft.com

ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
From <IP_ADDRESS> icmp_seq=1 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=2 Destination Host Unreachable
From <IP_ADDRESS> icmp_seq=3 Destination Host Unreachable
(...)

Diagnostic Logs
No response

I've followed the workaround suggested in this comment on a similar issue and it appears to have resolved the DNS resolution problem for now.

Hi. Can you please collect networking logs by following the instructions below?
https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

Hi @chanpreetdhanjal I am having similar issues, here are the attached logs
WslLogs-2023-12-12_08-23-45.zip

Please follow the networking diagnostic script. https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues
It should create a folder like [WslNetworkingLogs-date_ver.zip]

Hi @chanpreetdhanjal sorry here are the network logs
WslNetworkingLogs-2023-12-14_08-00-13.zip

@lancechant thanks for attaching the logs.
It looks like the IP of the WSL NAT vNIC got deleted and now the vNIC has a different IP than what Linux expects (Linux will use as DNS server and default gateway an IP that is no longer on the vNIC, causing the loss of connectivity).
Can you please do the following to collect additional diagnostics?
Run ".\collect-networking-logs.ps1 -RestartWslReproMode".
Wait for the script to output "Log collection is running", then start WSL
Confirm the issue reproduces
Stop the script and attach the resulting zip archive
Also, please run the following commands in an admin powershell window and attach "hns_events.log" to the issue
$events = Get-WinEvent -ProviderName Microsoft-Windows-Host-Network-Service | Where-Object { $.TimeCreated -ge ((Get-Date) - (New-TimeSpan -Day 1)) }
($events | ForEach-Object { '{0},{1},{2},{3}' -f $.TimeCreated, $.Id, $.LevelDisplayName, $_.Message }) -join [environment]::NewLine | Out-File -FilePath "hns_events.log" -Append
Additionally, can you try setting networkingMode=mirrored in the wslconfig file and let us know if the issue still reproduces?
Thanks

@lancechant thanks for attaching the logs.
It looks like the IP of the WSL NAT vNIC got deleted and now the vNIC has a different IP than what Linux expects (Linux will use as DNS server and default gateway an IP that is no longer on the vNIC, causing the loss of connectivity).
Can you please do the following to collect additional diagnostics?
Run ".\collect-networking-logs.ps1 -RestartWslReproMode".
Wait for the script to output "Log collection is running", then start WSL
Confirm the issue reproduces
Stop the script and attach the resulting zip archive
Also, please run the following commands in an admin powershell window and attach "hns_events.log" to the issue
$events = Get-WinEvent -ProviderName Microsoft-Windows-Host-Network-Service | Where-Object { $_.TimeCreated -ge ((Get-Date) - (New-TimeSpan -Day 1)) }
($events | ForEach-Object { '{0},{1},{2},{3}' -f $_.TimeCreated, $_.Id, $_.LevelDisplayName, $_.Message }) -join [environment]::NewLine | Out-File -FilePath "hns_events.log" -Append
Additionally, can you try setting networkingMode=mirrored in the wslconfig file and let us know if the issue still reproduces?
Thanks

Hi @CatalinFetoiu the issue I had seems to be fixed in 2.0.14. Also if I am correct the networkingMode=mirrored isn't available on windows 10?

Here is how to fix the issue :
Press Windows + R on your keyboard :  and put "optionalfeatures"
Disable then enable the wsl feature .
Restart the machine and your problem will be resolved !


python311Packages.python-roborock: 0.32.0 -> 0.32.2

Diff: https://github.com/humbertogontijo/python-roborock/compare/refs/tags/v0.32.0...v0.32.2
Changelog: https://github.com/humbertogontijo/python-roborock/blob/v0.32.2/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 247296 run on x86_64-linux 1

1 package failed to build:

home-assistant-component-tests.roborock

4 packages built:

python310Packages.python-roborock
python310Packages.python-roborock.dist
python311Packages.python-roborock
python311Packages.python-roborock.dist

Result of nixpkgs-review pr 247296 run on aarch64-darwin 1

4 packages built:

python310Packages.python-roborock
python310Packages.python-roborock.dist
python311Packages.python-roborock
python311Packages.python-roborock.dist


Common Lisp implementation of Sudoku

Fairly direct translation of the C version. Output should be 1-1 exactly the same.
If you want/care I can add the MIT license header, though I don't know whether it matters.

Thank you! No need to worry about the license. I want to put all source code here on the public domain.


Bump aerospike-client from 5.1.11 to 6.0.1

@ijusti We have an open PR that bumps both clients (reactive and non-reactive) versions to 6.1.2.
#414
we are expecting to merge that soon.

@ijusti We have an open PR that bumps both clients (reactive and non-reactive) versions to 6.1.2.
#414 we are expecting to merge that soon.

Super. missed this PR.
Is there estimates for soon?))

@ijusti Nothing accurate at the moment.
I would guess next week or the one after that.
I want all reviewers to approve the PR if possible.


Some tests in TestPlatform.sln could be parallelized

I was hoping to improve the test execution time of all the tests by annotating.
[assembly: Parallelize(Workers = 0, Scope = ExecutionScope.ClassLevel)]
in test projects.
My plan is follows

Add Parallelize to AssemblyInfo.cs
Test with a 4 core processor run 3-6 times per test project
If any projects have problems add the [DoNotParallelize] attribute to the TestClass

This would improve build times on AzureDevOps Pipelines and decrease testing times using LiveTesting feature in Visual Studio.

I am currently doing a fair amount of changes in the acceptance tests, I can already see some time improvements there. Let’s wait with this change to see if it will be needed.
Probably all the tests that cross check the runners could be paralelized, as they already spawn new processes, and should be isolated.
On the other hand, they are pain to debug already, even without paralelization 😅

Let me know when you are ready for me to take up the challenge

I think you can start, but I would not sink too much time into it, how about you do a quick pass on it, and then we review it as a proof of concept? I am not sure if I will want to merge it and don't want to waste your time :)


Model/material unloading

model.destroy: destroys skinning texture and possibly deletes vertex/index buffers of a model. Mesh is reference-counted, so buffers are only deleted if all models with referencing mesh instances were deleted. That means all in-scene models + the "base" one (asset.resource) which is created when the model is parsed.
shader.destroy: now also removes this shader from the programlib cache to prevent retrieving broken shaders.
material.destroy: removes this material from the scene, decrements the reference counter, and possibly calls shader.destroy.
device.clearShaderCache: destroys all shaders.
asset.unload: now calls resource.destroy and also raises the "unload" event. Old function (without destroy and event) moved to unloadOld. Model component uses the event to remove the model from the scene. Memory is 100% freed from the model in this case, as we don't care about reference counting.
createShaderFromCode now uses the same cache as material shaders.
default material is moved to pc.Scene.defaultMaterial.

9561436f80ff846014fd444f692b6905afb3c3ed


chore: try to update Spring Version following #389

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

My bad, this PR changes nothing else than Camunda Version actually


This code cannot work with serverless plan!

Please provide us with the following information:

This issue is for a: (mark with an x)
- [x] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce
This code cannot run with serverless plan CosmosDB, because it doesn't support Provisioned Troughput
Any log messages given by the failure

"Setting offer throughput or autopilot on container is not supported for serverless accounts.\r\nActivityId: ****, Microsoft.Azure.Documents.Common/2.14.0, StatusCode: BadRequest"
Mention any other details that might be useful
It works fine if you modify User.java at line 8,
Original:
@Container(containerName = "myContainer", ru = "400")
Modified:
@Container(containerName = "myContainer")
This repository linked from QuickStart MS document and most user may use serverless plan for evaluation. So please correct it ASAP! (Write some guidance in README or update the code.)

Thanks! We'll be in touch soon.

I believe you are right that we should update this repository to not set a throughput amount when creating the container. This will fail for serverless accounts. I need to do some quick testing to make sure the default throughput (when not specified) for provisioned accounts isn't a very large number.

I have finished testing and have found that if you omit the RU parameter, it will work with both serverless and provisioned accounts. I also determined that the default RU for provisioned accounts is 400 which is acceptable. I will issue a PR to fix this issue. Thanks @hatasaki for reporting it!


[feat] health page - Modern infra (kubernetes)

More and more people are working on kubernetes and other similar technologies. It has become common practice to have a "dummy" or real Endpoint which will return the health status of your application.
once this endpoint is available, the underlying orchestration considers the service ready to work.
I would like to suggest implementing an empty or just Health page with endpoint "/healthz"
this way we can use this endpoint for our orchestration healthchecks.
Why '/healthz'?

Stackoverflow - nice explanation: https://stackoverflow.com/questions/43380939/where-does-the-convention-of-using-healthz-for-application-health-checks-come-f
Kubernetes documentation: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
Some more bits from another project discussion https://github.com/jupyterhub/jupyterhub/issues/2532

https://github.com/OpenZWave/Zwave2Mqtt#healt-check-endpoints


saying no active campaigns when i linked them allready and they are active

Hello o/
What exactly is your issue? It's hard to tell, there's not much description to it.

so wheni run it just tells me that there are no active campions and there are active campions for rust and i link my twitch and rust and all that and it keeps giving me the messge there are no active campions

it keeps this messge No active campaigns to mine drops for. Waiting for an active campaign..

but link it and all that

Please check out #208, #203 and #198, to see if the steps and explanations provided there could help resolve your issue.

I'm assuming this can be considered resolved now.


Correct some typos

Wed Oct 30 14:43:09 GMT 2019
This PR corrects some typos throughout the project - mainly in the docs directory.
There was one instance where the British spelling was used: recognised.  This was corrected to North American spelling: recognized.
Also, MacOS was changed to macOS.
Most of the others were for commonly misspelled words.  (Note - this was not corrected in init.example.el.) ;-)

Good catches! Thanks for your help!


OpenBCI Testing

ℹ Computer information

Platform OS (Windows 10):
Python Version: 3.7
Brain Interface Used (OpenBCI Cyton):

📝 Provide detailed reproduction steps (if any)

…Followed instructions on NTCS website about Imitating an EEG Stream using OpenBCI Cyton
…
…

✔ Expected result
EEG Data stream from Cyton
❌ Actual result
IndexError: list index out of range
Got this error after putting in the COM port
📷 Screenshots

Other Feedback:

Add instructions for installing Jupyter Notebooks with Miniconda and then how to open Jupyter notebooks
https://www.codecademy.com/articles/setting-up-jupyter-notebook

The instructions on NTCS website have no links to any OpenBCI documentation about how to get started.
Links to Getting Started:
https://docs.openbci.com/GettingStarted/GettingStartedLanding/

On further testing I found out that in the screenshot above, I was inputting 16 but the required parameter was the index therefore 0.
I was able to do further testing by the command line interface. I was unsuccessful in using Jupyter Notebooks, or the provided code like this one:
from eegnb.devices.eeg import EEG
define the name for the board you are using and call the EEG object
eeg = EEG(device='cyton')
start the stream
eeg.start()
Note: Cyton RED light OFF. No file generated.
from eegnb.devices.eeg import EEG
define the name for the board you are using and call the EEG object
eeg = EEG(
device='cyton',
serial_port='COM7'
)
start the stream
eeg.start()
Note: Cyton RED light turned ON for a second and then code quit. No saved file generated. Add the required parameter of 'fn' in the function.
Finally, I was able to get EEG stream from Cyton by using the command interface. Here there are 2 methods: One is to pass all the arguments in the command line or use the (-ip) flag and using the interactive system to select the device and experiment.
When putting in all arguments via appropriate flags:
The argument for experiment (-ex) would NOT work for

auditory-SSAEP orig
auditory-SSAEP onefreq
auditory-oddball orig
auditory-oddball diaconescu

As all of these arguments have a space required and cmd would give me errors like
Error: Got unexpected argument (onefreq)
Error: Unknown experiment 'auditory-SSAEP'
For these 2 experiments, Cyton RED light was OFF and NO data file generated:

visual-cue
visual-codeprose

I was able to record data successfully for:

visual-N170
visual-P300
visual-SSVEP

Note: All 3 data files were above 800KB
I also tried using the (-ip) flag and interact with the system. I had following results for each experiment:

visual-N170:                   Cyton RED light ON, No save file generated
visual-P300:                    Cyton RED light ON, No save file generated
visual-SSVEP:                  Cyton RED light ON, No save file generated
visual-cue:                      Cyton RED light OFF, Save file of 1KB genertaed. The file didn;t have any stored EEG data and seemed corrupted
visual-codeprose:            Cyton RED light OFF, No save file generated
auditory-SSAEP orig:       Cyton RED light ON, No save file generated
auditory-SSAEP onefreq: Cyton RED light ON, No save file generated
auditory-oddball orig:      Cyton RED light ON, No save file generated
auditory-oddball diaconescu:   Cyton RED light ON, No save file generated

It seems like there are many ways to record data mentioned in the EEG-Notebooks Page which might make things confusing for someone doing this for the first time. I really liked the (-ip) flag method as it felt more interactive but as mentioned above there were a few errors there with data collection.


Add example for CRBA codegen

@vpadois
This feature is for you and related to #1047

@vpadois
To make the example working, you have to install CppAD (release 20200000.2 from https://github.com/coin-or/CppAD) and also CppADCodeGen (release v2.3.0 from https://github.com/joaoleal/CppADCodeGen)

@jcarpent Thanks for this information. I have to put this on hold for a few days but I will come back to you ASAP.
Thanks again.

Hello,
I'm looking at this with @vpadois, and we were wondering if there is a way to access the symbolic model generated by cppadcg as shown here ? I cannot find a way to make it work with the your example.

You should at the code in the class helper and just change the code generator, from C to latex for instance.


pipreqs circumvents pip.ini; feature request: use pip.ini if it exists.

I'm behind a corporate proxy and use pip.ini to set the proxy. If i run pipreqs without the --proxy ... argument, it doesn't find the pypi repos. It would be very cool if pipreqs could use the proxy settings from pip.ini.

I also facing this problem, using the settings from pip.ini would be great.


Update Wombat Assets

Update wombat assets

Looks good to me, moving to design review before closing to make sure they look right.


MNT: add "doc/api/generated" to gitignore

I think that after PR #12043 , we need to update .gitignore to include doc/api/generated ? At least on my local computer, doc/api/generated/* showed up in my untracked files after building the docs locally.

edit: Sorry for using CI resources on this without checking first.

I might be wrong, but I think a better fix is to have those files generated in doc/generated/api by changing the toctree lines, e.g.: https://github.com/mne-tools/mne-python/blob/3b6a33954c1aeb2ee02db3e9840b1df00d8c3be3/doc/api/creating_from_arrays.rst?plain=1#L7-L13
to:
:toctree: ../generated/api

@drammock Any preference?

Also, @scott-huberty if you want to prevent CIs from running on a commit, you can put the flag [skip ci] or [ci skip] in your commit message.
Works also with:

[skip azp] or [azp skip] for Azure pipelines
[skip circle] or [circle skip] for CircleCIs

e.g. MNT: add "doc/api/generated" to gitignore [skip ci]

@mscheltienne Yes I think you're right, I just tested make clean locally and it does not remove the contents of doc/api/generated, since the make clean command is equivalent to:
rm -rf _build sg_execution_times.rst auto_examples auto_tutorials generated *.stc *.fif *.nii.gz

TBH I don't fully understand autodoc / autosummary, so I tried out a couple options:

change the toctree lines to :toctree: ../generated/ so that the stub files end up in the same place they used to go; I tried this and got 36 warnings saying things like

WARNING: duplicate object description of mne.write_trans, other instance in api/generated/mne.write_trans, use :noindex: for one of them

change the toctree lines to :toctree: ../generated/api/ as @mscheltienne suggests; still got 36 warnings.

In both cases I did an rm -r doc/api/generated/ first, so I think this means that the right approach is to leave the :toctree: lines as-is, and in addition to adding doc/api/generated/ to .gitignore, add it to doc/Makefile:clean
@larsoner does that sound correct to you?

I don't fully understand it either, but I think you build with those 2 toctrees directives in an unclean state and/or with remaining :toctree: generated in your API folder. Locally, I got a clean build (html-noplot) and an non-existent api/generated folder with:

:toctree: ../generated/api/: cbfab294a3833b8320f31a5a4892e78e84a6b593
:toctree: ../generated: 9c0f1580c2f1e75baf8924c799cb00361d680bf2

I think it does impact the URL of those pages, so if they were landing in :toctree: ../generated/, it would be best to keep it this way, else many links on the forum pointing to API pages are now going to be broken.

n addition to adding doc/api/generated/ to .gitignore, add it to doc/Makefile:clean

Yes this sounds likely to be correct, but I think anywhere we had generated before the recent move-doc-stuff PR now needs to be api/generated -- I would git grep generated doc/ or so on the commit before the PR landed to see what needs to change.

so if they were landing in :toctree: ../generated/, it would be best to keep it this way, else many links on the forum pointing to API pages are now going to be broken.

I hadn't thought about this. In principle we could redirect but it would be a lot of redirects to write (hundreds probably), one per public API entry. This makes me slightly more inclined to go back to generated/, but I'm torn because api/generated/ seems clearer naming-wise. FWIW in terms of namings I looked at a few:

pandas seems to use reference/api/*
SciPy and NumPy use reference/generated/*
matplotlib uses _as_gen/ which I don't think we should follow
scikit-learn uses modules/generated

I don't see a clear takeaway from this but figured I'd report it anyway for completeness.

I think the right way forward here is to put the api stubs back where they used to be and skip the changes to the Makefile and .gitignore. I've opened #12110 to do that, and marked it to close this when merged. @mscheltienne you were right, the reason I was getting "duplicate entry" warnings was that my find-and-replace had missed a couple cases of :toctree: generated that lacked the trailing slash. Once I fixed those it builds without error. I've made both you and @scott-huberty co-authors on the commit.
@larsoner I think in the end it's better to have the URLs remain stable at generated/ rather than changing to be something slightly more informative. I figure, folks don't usually type those URLs in by hand anyway.

Sounds good to me, thanks everyone!


ms5611: build on linux (navio2)

Minor ms5611 changes to get it building on linux. This driver could use a big cleanup/modernization.

Still working on NuttX.

There's no change to the actual driver code here.

Merging immediately to save a little bit of flash on fmu-v2.


⚠ HopeAlley has degraded performance

In 1b50c51, HopeAlley (https://hopealley.com) experienced degraded performance:

HTTP code: 200
Response time: 7861 ms

Resolved: HopeAlley performance has improved in 421292a after 6 minutes.


test_version_stable.py does not exist?

Hi,
in the file lm_eval/evaluator_utils.py in the function "find_test_root" on line 507, it is searching for a test_stable_version.py and it seems like this file is used to run the test, but this file does not exist in the current repository. What other file is the right file to be able to run tests using simple_evaluate?
Please let me know.
Thank you!

I solved this by passing check_integrity=False


how to use the generated_surface_scripts.py?

Hello, I have an problem about the node_transpiler，when I create a blend file only include geometry node, and I use the dev_script.py to convert node-graphs to python code, but noly get the  generated_surface_scripts.py file. how to use the  generated_surface_scripts.py and get some information like Figure.3 in your paper(eg. has some parameters like desinty?), could your kindly to teach me?

Hello,
To get randomized values included in the Python code, you can give any Value node an annotated name like 'Density ~ U(5,20)' and a corresponding np.random call should appear in the Python. It won't be quite the format shown - the code in the figure is somewhat compacted and illustrative.
If you want to run the genwrated_surface_script.py, just open it up in the blender scripting panel, select some object (like the default cube etc) to apply the geonodes ontop of, then click play to run the script in the UI. Or, you can look at some of our code examples like flower.py or simple_greenery.py to see what it looks like running headless

Thanks for your reply ,but I use the wsl don't have the UI,  how can I do to use the generate_surface_script.py？I use the command "$BLENDER -b empty.blend --python generated_surface_script.py " and  export warning:  File written by newer Blender binary (305.8), expect loss of data!


map_blocks fails with lazy loaded dask array

Hi,
I'm very excited about this package and I'm just familiarising myself to see where I can use it for my use cases. I followed the example in the documentation to apply a groupby to the datatree.  However, I did use dask because my dataset is too large to fit it into memory. I realised that my group_by function is not being applied to lazy loaded dask arrays.
Minimal example
import datatree
import xarray as xr
import pandas as pd
import dask
import numpy as np

def group_by(da, groupby_type="time.floor('1D')"):
    gb = da.groupby(groupby_type)
    mean = gb.mean()
    return mean

times = pd.date_range("2022-09-01","2022-09-03", freq="6H")

a=xr.Dataset({'x': ('time', np.random.randint(0,10,len(times)))}, coords={'time':times})
b=xr.Dataset({'x': ('time', dask.array.random.randint(0,10,len(times)))}, coords={'time':times})
dt=datatree.DataTree.from_dict({'first':a, 'second':b})

dt.map_blocks(group_by, kwargs={"groupby_type": "time.day"}, template=dt)

Please compare the results for the eager (a) and lazy (b) loaded datasets below:
DataTree('None', parent=None)
├── DataTree('first')
│       Dimensions:  (day: 3)
│       Coordinates:
│         * day      (day) int64 1 2 3
│       Data variables:
│           x        (day) float64 5.75 7.75 6.0
└── DataTree('second')
        Dimensions:  (time: 9)
        Coordinates:
          * time     (time) datetime64[ns] 2022-09-01 2022-09-01T06:00:00 ... 2022-09-03
        Data variables:
            x        (time) int64 dask.array<chunksize=(9,), meta=np.ndarray>

Any ideas what is going wrong?
This can likely be generalised for any map_blocks function:
def func(da):
    return da.mean('time')

b=xr.Dataset({'x': ('time', dask.array.random.randint(0,10,len(times)))})
dt=datatree.DataTree.from_dict({'second':b})

dt.map_blocks(func, template=dt)

DataTree('None', parent=None)
└── DataTree('second')
        Dimensions:  (time: 9)
        Dimensions without coordinates: time
        Data variables:
            x        (time) int64 dask.array<chunksize=(9,), meta=np.ndarray>

Versions
xarray: 2022.6.0
datatree: 0.0.9

There's something to fix here but can you try installing flox then dt.groupby(...).mean(method="blockwise")?

Closed and moved upstream https://github.com/pydata/xarray/issues/9504


Getting small checkbox on refreshing the product page.

Bug report
Title
Getting small checkbox on refreshing the product page.
Issue Description
Getting small checkbox on refreshing the product page.
Preconditions
1. framework Version.- master

Steps to reproduce
1. step1- Go to product page and refresh the page.

Expected result
Checkbox should not display on refreshing the page.
Actual result
Getting small checkbox on refreshing the product page.

Issue was due to html content of description field.


Change placeholder texts

If you guys want to go live soon, then it might be a good idea to start removing all the placeholder text
Originally posted by @timstokman in https://github.com/CollActionteam/clothing-loop/pull/153#discussion_r789858583

thank you for creating the issue! Will work on this once I get the content from the copywriter


I don't think react-native-email is working anymore!

Duplicate of https://github.com/tiaanduplessis/react-native-email/issues/9


Version Check

DO NOT MERGE

Obsolete - replaced by https://github.com/deeplearning4j/nd4j/pull/2016


Using System.Stack slows down Entitas functions

Hi,
I've noticed a performance issue that arises due to using System.Stack<T> in implementation of entitas.
Here is a screenshot from instruments that illustrates the problem:

As you can see Stack<T> uses RuntimeHelpers.IsReferenceOrContainsReferences function that takes 99% of its execution time (and in our case 2% of total frame time).  As far as I can see its usage is an attempt to optimize method in case of using structs, but I think it does more harm than good in most cases(it is important to note that microsoft implementation does not use this or similar check)
Here is the code of Stack<T>.Pop() from unity:
public T Pop()
    {
      int index = this._size - 1;
      T[] array = this._array;
      if ((uint) index >= (uint) array.Length)
        this.ThrowForEmptyStack();
      ++this._version;
      this._size = index;
      T obj = array[index];
      if (!RuntimeHelpers.IsReferenceOrContainsReferences<T>())
        return obj;
      array[index] = default (T);
      return obj;
    }

My suggestion would be to use either built-in or custom collection  that doesn't implement such checks as it will greatly improve Entitas performance.

Are you using .Net 4.x?

Are you using .Net 4.x?

The instruments screenshot is made with project build with 2018.1.9 with .net 4.x backend

This is one is made with 2018.3.4 with .net 4.x scripting backend

Did some research on why this method is even used in the Stack, it seems that this "optimization" is now included in dotnetcore and relies heavily on JIT compiler optimizing out this call. In ios UnityLand JIT is not a thing and it seems the proper way to address this is to get Unity to fix it.


Fix permission issue on VIC appliance

The job logs directory's permission is not changed by prepare script
because the everything is moved from /data to /storage/data on VIC
appliance.  This commit will make sure both cases the directory is
readable by user 10000:10000.
This PR also makes sure the config json of notary signer has 0644
permission.

Coverage decreased (-0.006%) to 64.526% when pulling 5ff07cf6191c03e733767f1148b5625c25a14070 on reasonerjt:fix-joblog-dir into 86dddf444a000fd3c8a7399fabbdbf474f34acb3 on vmware:master.


When creating account create account in Swift first.

When you try to create account with same suffix as already existed
before, Swift raises error. But SwAuth already created container for
this account in .auth which creates inconsistency.

I haven't worked with this stuff in quite some time. However, my curiosity has me: What error does Swift return in this situation? My first thought it that a PUT to an account that already exists would return success.

When I create account, delete that account and then try to create same (same name, same suffix) account, Swift returns 403 forbidden:
Apr 20 15:09:40 swift1 proxy-server: STDOUT: EXCEPTION IN handle: Traceback (most recent call last):#012  File "/usr/local/lib/python2.7/dist-packages/swauth-1.0.9.dev-py2.7.egg/swauth/middleware.py", line 465, in handle#012    return self.handle_request(req)(env, start_response)#012  File "/usr/local/lib/python2.7/dist-packages/swauth-1.0.9.dev-py2.7.egg/swauth/middleware.py", line 532, in handle_request#012    req.response = handler(req)#012  File "/usr/local/lib/python2.7/dist-packages/swauth-1.0.9.dev-py2.7.egg/swauth/middleware.py", line 776, in handle_put_account#012    'cluster: %s %s %s' % (path, resp.status, resp.reason))#012Exception: Could not create account on the Swift cluster: /v1/AUTH_test2 403 Forbidden#012: {'HTTP_REFERER': 'http://swift1.dev:8080/auth/', 'SCRIPT_NAME': '/auth/v2/test2', 'swift.proxy_access_log_made': True, 'REQUEST_METHOD': 'PUT', 'PATH_INFO': '', 'HTTP_ORIGIN': 'http://swift1.dev:8080', 'SERVER_PROTOCOL': 'HTTP/1.0', 'swift.account/v2': {'status': 404, 'container_count': 0, 'bytes': None, 'total_object_count': None, 'meta': {}, 'sysmeta': {}}, 'CONTENT_LENGTH': '0', 'HTTP_USER_AGENT': 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.118 Safari/537.36', 'HTTP_CONNECTION': 'keep-alive', 'eventlet.posthooks': [(<bound method Swauth.posthooklogger of <swauth.middleware.Swauth object at 0x2faead0>>, (<swift.common.swob.Request object at 0x2fc76d0>,), {})], 'SERVER_NAME': '<IP_ADDRESS>', 'REMOTE_ADDR': '<IP_ADDRESS>', 'eventlet.input': <eventlet.wsgi.Input object at 0x2fc7510>, 'HTTP_X_AUTH_ADMIN_KEY': 'tank', 'wsgi.url_scheme': 'http', 'SERVER_PORT': '8080', 'HTTP_X_AUTH_ADMIN_USER': '.super_admin', 'wsgi.input': <swift.common.utils.InputProxy object at 0x2fc7f10>, 'HTTP_HOST': 'swift1.dev:8080', 'swift.cache': <swift.common.memcached.MemcacheRing object at 0x3065710>, 'HTTP_X_ACCOUNT_SUFFIX': 'test2', 'wsgi.multithread': True, 'HTTP_ACCEPT': '/', 'wsgi.version': (1, 0), 'GATEWAY_INTERFACE': 'CGI/1.1', 'wsgi.run_once': False, 'wsgi.errors': <swift.common.utils.

Ah, that makes sense to me now, the whole "can't create an account recently deleted" thing. Thanks for satisfying my curiosity.


cmd/go: result of 'go build -o' is missing the executable bit, and the resulting file does not execute (despite adding +x)

Very likely this is an issue with my set up, but I cannot figure out what is going on.
What version of Go are you using (go version)?

$ go version
go version go1.12.9 darwin/amd64

Does this issue reproduce with the latest release?
Not sure about the tip, go1.12.9 is the latest available release on Homebrew for macOS.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/ahmetb/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/ahmetb/go"
GOPROXY=""
GORACE=""
GOROOT="/Users/ahmetb/.homebrew/Cellar/go/1.12.9/libexec"
GOTMPDIR=""
GOTOOLDIR="/Users/ahmetb/.homebrew/Cellar/go/1.12.9/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/ahmetb/workspace/run-latencies/cmd/probe/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/h7/n46zg3md4l57vzsgxcs355hw00dl55/T/go-build623969830=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
GOPATH unset, have a very simple program:
$ tree
.
├── go.mod
└── main.go

rm -rf  ~/go/bin/probe
go build -o ~/go/bin/probe .
stat ~/go/bin/probe

Observe the executable file is 0644/-rw-r--r--.
I don't think my shell somehow magically got some umask that's causing files to be marked as non-executable.
What did you expect to see?
The file created from go build -o should have +x bits set.
What did you see instead?
The resulting file from go build -o executable file is 0644/-rw-r--r--.

Really glad I found this post, just helped me and a buddy out :)

me also VERY glad i found this)


npm version 6.11.0 - 'find_dp0' is not recognized as an internal or external command,

Type: Bug
Enter Task Name:
Task         : npm
Task Version      : 1.156.1
Environment

Server - Azure Pipelines

Issue Description

I had a task that runs a custom npm commands. And worked perfect until the Hosted Agent (Hosted Windows 2019 with VS2019) upgrade the npm version from "6.10.3" to "6.11.0"
Task logs with error ("6.11.0")
##[section]Starting: ProgramasProjetosWebApp - npm build
==============================================================================
Task         : npm
Description  : Install and publish npm packages, or run an npm command. Supports npmjs.com and authenticated registries like Azure Artifacts.
Version      : 1.156.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/package/npm
==============================================================================
SYSTEMVSSCONNECTION exists true
SYSTEMVSSCONNECTION exists true
[command]C:\windows\system32\cmd.exe /D /S /C "C:\npm\prefix\npm.cmd --version"
6.11.0
[command]C:\windows\system32\cmd.exe /D /S /C "C:\npm\prefix\npm.cmd config list"
; cli configs
metrics-registry = "https://registry.npmjs.org/"
scope = ""
user-agent = "npm/6.11.0 node/v10.16.3 win32 x64"

; environment configs
cache = "C:\\npm\\cache"
prefix = "C:\\npm\\prefix"
userconfig = "d:\\a\\1\\npm\\31417.npmrc"

; builtin config undefined

; node bin location = C:\Program Files\nodejs\node.exe
; cwd = d:\a\1\s\src\ProgramasProjetos\ProgramasProjetosWebApp
; HOME = C:\Users\VssAdministrator
; "npm config ls -l" to show all defaults.

[command]C:\windows\system32\cmd.exe /D /S /C "C:\npm\prefix\npm.cmd run build-prod"
'find_dp0' is not recognized as an internal or external command,
operable program or batch file.
internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module 'd:\@angular\cli\bin\ng'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

><EMAIL_ADDRESS>build-prod d:\a\1\s\src\ProgramasProjetos\ProgramasProjetosWebApp
> ng build --prod --base-href=/programasprojetos/ --deploy-url=/programasprojetos/

##[section]Finishing: ProgramasProjetosWebApp - npm build

again, yesterday worked perfect, i did not change nothing, and today i got this problem.
Comparing both logs, i saw the diference, the npm version.

Hi,
Thanks for reaching out to us. It appears that the issue is with npm v6.11.0, there is a similar issue report here: https://npm.community/t/6-11-0-npm-looking-for-executable-packages-in-root-c/9574 . Additionally, it looks like npm has already released the fix for this in npm v6.11.1 based on the solution to the issue report.
Since this is not an issue with the task, i would suggest updating your npm version or downgrading it and trying again.
Please let me know if this fixes your issue.

I'm using the Hosted Agent (Hosted Windows 2019 with VS2019).
I added a task "Use Node 12.6" that user npm "6.9.0". This task runs, but the next one, continue using npm "6.11.0"
How i change de npm version on Hosted Agent (Hosted Windows 2019 with VS2019)?

@penihel while we make the fix to the hosted agents, can you please add a command line task before the npm task and run:
npm install -g<EMAIL_ADDRESS>npm run prepare - successful
This should update your npm globally and npm task should use 6.11.1. We have forwarded this issue to the team which manages hosted agents.

@shubham90 I tried to run these commands, but I get this:
##[section]Starting: Install NPM (temporary)
==============================================================================
Task         : Command line
Description  : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
Version      : 2.151.2
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
==============================================================================
Generating script.
========================== Starting Command Output ===========================
##[command]"C:\windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "d:\a\_temp\60c407c4-8434-461a-9633-f1bdf971a3a8.cmd""
C:\npm\prefix\npm -> C:\npm\prefix\node_modules\npm\bin\npm-cli.js
C:\npm\prefix\npx -> C:\npm\prefix\node_modules\npm\bin\npx-cli.js
+<EMAIL_ADDRESS>updated 2 packages in 29.556s
'npm-cli.js" install -g<EMAIL_ADDRESS>is not recognized as an internal or external command,
operable program or batch file.
##[error]Cmd.exe exited with code '9009'.
##[section]Finishing: Install NPM (temporary)


create a snapshot on sources that already have some history

Jumping into the discussion to add one suggestion/idea. Sorry if this was already discussed, I couldn't find it.
One complaint I hear from time to time is that you can't create a snapshot if the source has duplicates.
Imagine we have a source like

id
status
date

1
created
2024-01-01

1
processed
2024-02-01

It would be nice if the snapshot, in its first run, could read this source and be built like

id
status
date
dbt_valid_from
dbt_valid_to

1
created
2024-01-01
2024-01-01
2024-02-01

1
processed
2024-02-01
2024-02-01
null

We could have something similar to incremental models

If the snapshot does not exist in the platform (first run), create a history of the source's data, instead of trying to insert only
if the snapshot exists in the platform, then go the default way

It would only work for the timestamp strategy, because the snapshot must know what is older and what is newer.
Just an idea, maybe there are other ways to do it. But just because it is bad when we can't create a snapshot on sources that already have some history.
By the way, loved that snapshots are in the spotlight! 🧡
Originally posted by @bruno-szdl in https://github.com/dbt-labs/dbt-core/discussions/7018#discussioncomment-9706404

More thinking here -> https://github.com/dbt-labs/dbt-core/issues/3878


Model card specific features of Keras mixin don't work with JAX model converted to TF

Describe the bug
I need to investigate why JAX models converted to TF and then pushed using push_to_hub_keras don't have automatically generated sections in model card. The bare minimum should have model plot and training hyperparameters. Metrics aren't written if the history isn't kept. (which is normal for this case)
Also pinging @sayakpaul
Reproduction
Code is here: https://github.com/sayakpaul/maxim-tf/blob/main/convert_to_tf.py#L204
Logs
No response
System Info
Need to ask but is insignificant for this case.

@merveenoyan thanks for reporting it.
I did some investigations:

I created a simple model using the functional API.
I then used push_to_hub_keras() to host it on Hub.

Here's the Colab: https://colab.research.google.com/gist/sayakpaul/1bea35f00acaa9926d2beb744058de1c/scratchpad.ipynb.
We see the model plot in the corresponding model repository but not the other stuff you mentioned. I wonder why the model plot doesn't appear for the MAXIM model. I can initialize the MAXIM model and actually plot the model.
You can replicate it with the following code:
from huggingface_hub.keras_mixin import from_pretrained_keras
import tensorflow as tf

model = from_pretrained_keras("sayakpaul/S-3_denoising_sidd")
tf.keras.utils.plot_model(model)

But it takes an incredibly long amount of time to plot it. Probably that's the reason the model plot is not there in the model repository.

@sayakpaul I will debug it and let you know 🙂 I wonder why hyperparams aren't there though, let's see.


Quotes inside comments in TwineScript are buggy

Describe the bug.
Opening a quote inside a comment in a macro head, and closing that same quote outside the macro causes the parser (the regex prolly?) to include everything between those quotes and throw.
To Reproduce:
<<set $var to {
   one: 1 /* open a ' quote */
}>>
<<= 'somestring>>

or
<<if $var is {
  one: 1 /* open a ' quote - ignore the stoopid usage, just wanted to demo it with a container */
}>><</if>>
<<= 'somestring'>>

Expected behavior.
No errors >.<
Project details.

SugarCube Version: e.g., 2.34.1
Included Add-ons: -
Included Libraries: -
Compiler & Version: Twine 2.3.13

Desktop details.

OS & Version: Windows 10
Browser & Version: Chrome 88.0.4324.190 (Official Build) (64-bit)

Additional context.
Found while hunting the cause of the bug in Wendy's project. Made me find a bug in T3LT too. It's got the same bug, given that it uses the same regex for the macros, and adapts a lot of the lexer code for argument parsing... But I think it's solely a problem with the regex, judging by how the extension reacts to it... I'll look into it myself too.

Noice.

O wait... No close until publish?


updated Markdown formatting

Updated formatting of the README.md file to properly render the markdown labels and clean things up for readability.

Thanks!!


Pillage tower

Spark link
purpur
Expected behavior
Attack generated are not affected
Observed/Actual behavior
purpur Server plunder tower generation is affected, how should be adjusted
Steps/models to reproduce
Attack generation speed is slow
Purpur version
Attack generation speed is slow
Agreements

[X] I am running the latest version of Purpur available from https://purpurmc.org/downloads.
[X] I have searched for and ensured there isn't already an open issue regarding this.
[X] My version of Minecraft is supported by Purpur.

Other
I'm sorry to ask you a question in this way, but I really can't find where to ask the question. Sorry.

I'm sorry to ask you a question in this way, but I really can't find where to ask the question. Sorry.

I can't make heads from tails of this ticket. Join us on Discord for further discussion.