Can't vagrant up any more after upgrading Vagrant to 1.9.4

Today I'v upgraded from Vagrant 1.9.1 to 1.9.4 (by choco upgrade vagrant). Now then I try to vagrant up the boxcutter/ubuntu1610-desktop I get following error:
TL;DR
    default: Warning: Connection reset. Retrying...
==> default: Forcing shutdown of VM...
==> default: Destroying VM and associated drives...

Yesterday everything worked fine with  Vagrant 1.9.1
COMPLETE OUTPUT
λ vagrant up --provision
proxyconf...
vagrant-proxyconf plugin installed, looking for proxies...
http_proxy found, setting for VM
https_proxy found, setting for VM
no_proxy found, setting for VM
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: <IP_ADDRESS>:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:in `readpartial': An established connection was aborted by the software in your host machine. (Errno::ECONNABORTED)
        from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:54:in `block (2 levels) in negotiate!'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:52:in `loop'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:52:in `block in negotiate!'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:50:in `loop'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:50:in `negotiate!'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/server_version.rb:32:in `initialize'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/session.rb:84:in `new'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh/transport/session.rb:84:in `initialize'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.rb:233:in `new'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/net-ssh-4.1.0/lib/net/ssh.rb:233:in `start'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:397:in `block (2 levels) in connect'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in `block in timeout'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `block in catch'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `catch'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `catch'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in `timeout'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:371:in `block in connect'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/util/retryable.rb:17:in `retryable'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:370:in `connect'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:68:in `block in wait_for_ready'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:88:in `block in timeout'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `block in catch'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `catch'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:32:in `catch'
        from C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/timeout.rb:103:in `timeout'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/plugins/communicators/ssh/communicator.rb:46:in `wait_for_ready'
        from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.4/lib/vagrant/action/builtin/wait_for_communicator.rb:16:in `block in call'

HOST INFO

Windows 7 64 bit
Vagrant 1.9.4 (nothing works any more)
Virtualbox <IP_ADDRESS>229
VirtualBox.ExtensionPack <IP_ADDRESS>634
Vagrant and VirtualBox are installed through Chocolatey
cmder 1.3.0

Related? https://github.com/mitchellh/vagrant/issues/8519

hmmm ... I could try to update Vagrant 1.9.5 that possibly fixes above issue but I am a bit afraid that I will have to spend the rest of the day  rolling back everything :-/
I'll close this one anyway. If this issue appears undert 1.9.5 I'll reopen it.

Upgraded to Vagrant 1.9.5 today - works like a charm!


Video Background

What feature do you want to get added on the base engine?
Dear ShadowMario i've been waiting for the video background on this Game i hope you add an video background, Thank You
To test your sight, and reliability, please select the option of what should NOT be requested.
Useful feature

you failed the test

you failed the test

frfr


docs(timeoutWith): create documentation for the operator

Create documentation for timeoutWith operator, comparing it
to timeout operator, describing what fallback Observable is
needed for, showing example of usage and providing descriptions
for all parameters of the operator.
Related issue (if exists):
#2656

Coverage remained the same at 97.734% when pulling 198d5c167b549c02622990ecb1f32beae562566b on mpodlasin:timeout-with-docs into 80a5ea7050320b37cb723407cb3fdde2ab2cd6eb on ReactiveX:master.

Looks good to me, @mpodlasin , well done.


readme: fix faq entry for ^r search

Closes #423

These changes were made as part of b56ee542d619.  We didn't notice this PR before we merged that one, apologies for that.

And to be explicit: thanks for this docs patch, and apologies if the merge got some authorship metadata wrong.


Browser webcam

Thank you guys!!
I want to recognize face using browser's webcam, how to integrate that? Can you please let me know

Thanks! you can try opencv.js framework.
for example https://huningxin.github.io/opencv.js/samples/index.html

Thanks for quick reply,
will definitely try opencv framework


Log function

Is there a way to use a log function on decision variables? I've found this old issue, where I see it wasn't implemented yet in 2016. Is there any update now? See: https://github.com/SCIP-Interfaces/PySCIPOpt/issues/41
Thank you!

Hi, yes you can. In test_expr.py we build logarithmic expressions... a bit artificial though.

Oh great! Thank you for your very quick reply. Is there anything else I should do besides import the log or exp? Because I get an AssertionError.
I imported the expressions like this:
from pyscipopt import Model, quicksum, multidict, log, exp
And I wrote the objective function like this:
model.setObjective(quicksum((exp(z[i,p])) for i in C for p in P), "maximize")
Thanks!

oh, sorry
you can't have nonlinear objectives. You have to linearize it, using the so-called epigraphical representation (or something like that). That is:

add a new variable, objvar = model.addVar(name="objvar", type= "C", lb=None, ub=None)
use that constraint as the objective model.setObjective(objvar, "maximize")
and then add a constraint model.addCons(objvar <= quicksum((exp(z[i,p])) for i in C for p in P))

@fserra Does it make a difference with respect to performance whether the auxiliary constraint is a <= vs ==?

In principle, it could. So if your objective is concave and you add objvar <= obj, then this is a convex constraint, while objvar == obj is non-convex. Now, of course SCIP could detect this, but I am not sure right now if it is going to do that, so I would use <= as a rule of thumb.


Calling spawn is very slow at times

VSCode Version: Code 1.11.2 (6eaebe3b9c70406d67c97779468c324a7a95db0e, 2017-04-13T08:03:11.395Z)

Shell 1.4.6
Renderer 53.0.2785.143
Node 6.5.0

OS Version: Windows_NT ia32 6.1.7601
Extensions:

Extension
Author
Version

tslint
eg2
0.12.0

theme-material-theme
jprestidge
1.0.1

material-icon-theme
PKief
2.0.3

Steps to Reproduce:

Start VSCode.
Before the left side pane is fully loaded open a recent project.

If the window remains open often it will never open any projects.  Other times it stays a blank screen without any folders.  Also tested this by disabling all the extensions above.
This seems to be a problem with the updated 1.11.x code.  I didn't see this problem before.

@chrispyatfpng Can you run code with the --prof-startup flag and attach the profile here. Thanks

Attached are the profiles.
On Tue, Apr 18, 2017 at 3:35 AM, Johannes Rieken<EMAIL_ADDRESS>wrote:

@chrispyatfpng https://github.com/chrispyatfpng Can you run code with
the --prof-startup flag and attach the profile here. Thanks
—
You are receiving this because you were mentioned.
  Included a zip of the files just in case.
On Tue, Apr 18, 2017 at 9:47 AM, Johannes Rieken<EMAIL_ADDRESS>wrote:

@chrispyatfpng https://github.com/chrispyatfpng Please attach as files
because the comments gets cropped and also because there are two separate
files
—
You are receiving this because you were mentioned.
 Just huge, tho incomplete, comments

Okay.  Trying directly through github.
dac5_main.cpuprofile.txt
dac5_renderer.cpuprofile.txt

Thanks

Spawning child processes seems very slow on your system. We have often heard that is coming from eager AV software...

I will do some tests with the AV.  Knowing my system environment that could likely be the problem, and likely my problems are just coincidental with updating VSCode.  Thank you for the assistance!

@chrispyatfpng Did you find out anything? Does this still happen? Does this happen on every start?

I am experiencing the same issues. Although, node process message that debugger attached almost immediately, VS Codes takes a long time to connect. Additionally, sometimes the node process dies because of a Segmentation fault  too.

I'm not seeing the extreme slow response and freeze as I was before.  On occasion it is a little slow but that is common for apps on my older machine.  I should be receiving a new machine in the next month and I will report back with an update.

Closing this issue in favour of #56644, which also tracks slow startup issues on Windows.

Closing this issue in favour of #56644, which also tracks slow startup issues on Windows.


CMake build and test support for Darwin

This sequence of patches is a combination of a bunch of cherry-picks from LLVM.org to support building and running the test suite on Darwin using CMake, and some additional patches to get the Swift support also working with CMake on Darwin.

@swift-ci Please smoke test.

I should note, with this patch there are 6 failing tests and 6 tests with errors. The 6 failing tests also fail on LLVM.org with CMake builds (so no regression). The tests with errors are:
FAIL: test_dsym (functionalities/exec/TestExec.py) FAIL: test_dwarf (functionalities/exec/TestExec.py) FAIL: test_expr_dsym (lang/c/modules/TestCModules.py) FAIL: test_expr_dwarf (lang/c/modules/TestCModules.py) FAIL: test_expr_gmodules (lang/c/modules/TestCModules.py) FAIL: test_gmodules (functionalities/exec/TestExec.py) ERROR: testREPL (repl/lazy_reverse/TestLazyReverse.py) ERROR: testREPL (repl/pounwrapping/TestPOUnwrapping.py) ERROR: testREPL (repl/classes/TestREPLClasses.py) ERROR: testREPL (repl/type_lookup/TestREPLTypeLookup.py) ERROR: testREPL (repl/recursive_class/TestREPLRecursiveClass.py) ERROR: testREPL (repl/structs/TestREPLStructs.py) ERROR: [EXCEPTIONAL EXIT 11 (SIGSEGV)] test_swift_no_target_dsym (lang/swift/expression/no_calculator/TestSwiftNoProcess.py)

@swift-ci Please test

@swift-ci Please test

The macOS PR test failure is now also failing in master.  This is unrelated to Chris' change here.


[$500] Payment issue for #32539

This issue was never paid and the Upwork job closed, so creating this to get a new upwork job and facilitate payments for @shubham1206agra and @dukenv0307
https://github.com/Expensify/App/issues/32539
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~010f1d87f89b9d5093
Upwork Job ID:<PHONE_NUMBER>208180224
Last Price Increase: 2024-02-06

Offers sent to @dukenv0307 and @shubham1206agra for $500 for this, please accept and I'll pay you right away

@greg-schroeder Accepted


Added buffer support to Node

Using System.Dynamic instead of json.net as that's what edgejs operates upon, which helps to maintain type info.
resolves #814

Is this only an issue for http bindings? I.e. are you saying it works as expected already for a queue output? I believe I have some existing tests verifying that Buffers work for other binding types.

@mathewc Haven't looked into other bindings, but yeah it fails for http.  I'll look around for the queue buffer tests you're talking about

@mathewc The queue tests that you are referring to test that a byte[] input is converted to a Buffer in node (which is great :D).  This issue is about how returned buffers are handled if they are nested in objects, since we serialize all objects & non-byte arrays to strings before passing to binding.

@mamaso I ask here because I'm not sure where else to ask. I've been stuck by this problem, I've ported a thumbnailer code into azure functions (works great!), but the response is converted into base64. I only need to send a Buffer with a declared content type (in this case "image/jpeg" or "image/png"), it is always sent as a base64 string, all the caching and storage of thumbnails is done by another service, I don't want to store anything, just pure http in/out.
If there's anything I can do to help, please tell me, I understand this would be a common usage for many people.

@kshmir Yep, it's an important use case that we don't support yet.  When this fix is released Buffers will be correctly treated as binary content and not converted to base64 strings.
Until this fix is released (hopefully in less than a week), your best option would be to port the thumbnailer code to C# if possible, it doesn't have issues with binary content.

@fabiocav @mathewc Rebased on top of the branch to get in Fabio's changes so things might look a bit funky.

Merged as part of https://github.com/Azure/azure-webjobs-sdk-script/pull/1002


Godot zip / extracted file does not contain " Mono " file in "GodotSharp" file #10239

Tested versions
Godot 4.3 stable mono
System information
Godot v4.3.stable.mono - Windows 10.0.22631 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 4060 Laptop GPU (NVIDIA; <IP_ADDRESS>03) - AMD Ryzen 7 7735HS with Radeon Graphics (16 Threads)
Issue description
I just downloaded Godot Engine 4.3 .NET (mono version) and it doesn't contain "Mono" file in "GodotSharp" file. it only contains Tools and Api files
Steps to reproduce

Minimal reproduction project (MRP)

(https://github.com/godotengine/godot-docs/issues/10239)

That's not a bug. Godot 4 and newer does not have a mono folder because despite the name not changing, mono is not used for C# anymore, .NET is.


Add wallet max balance

New .env variable LNBITS_MAX_WALLET_BALANCE_SAT can limit the maximum balance for each wallet and throw an error if the wallet attempts to create a new invoice.
Example: LNBITS_MAX_WALLET_BALANCE_SAT=1000000

Not into main please. We use dev for development


add emulator e2e tests

Add a e2e test that uses the emulator and does not rely on any GPU.
I wanted a quick way to run the emulator pod and I realize that we probably want to use this for CI eventually.

/cc @sairameshv can you review this?

@kannon92 does the test run as expected for you? I am getting a timeout.
Waiting for the pod to be ready, err: exit status 1
output: error: no matching resources found

Retrying...
Waiting for the pod to be ready, err: exit status 1
output: error: no matching resources found

Retrying...
Waiting for the pod to be ready, err: exit status 1
output: error: no matching resources found

Retrying...
Waiting for the pod to be ready, err: exit status 1
output: error: no matching resources found

Retrying...
Waiting for the pod to be ready, err: exit status 1
output: error: no matching resources found

Retrying...
Waiting for the pod to be ready, err: exit status 1
output: error: no matching resources found

Retrying...
Waiting for the pod to be ready, err: exit status 1
output: error: no matching resources found

Retrying...
Waiting for the pod to be ready, err: exit status 1
output: error: no matching resources found

Retrying...
  STEP: building the manager(Operator) image @ 09/17/24 11:39:05.715
  running: make docker-build IMG=quay.io/amalvank/instaslicev2-controller:latest
  STEP: loading the manager(Operator) image on Kind @ 09/17/24 11:40:25.659
  running: kind load docker-image quay.io/amalvank/instaslicev2-controller:latest --name kind
  STEP: installing CRDs @ 09/17/24 11:40:44.397
  running: make install
  STEP: deploying the controller-manager @ 09/17/24 11:40:46.337
  running: make deploy-emulated IMG=quay.io/amalvank/instaslicev2-controller:latest
  STEP: validating that the controller-manager pod is running as expected @ 09/17/24 11:40:48.945
Waiting for the pod to be ready, err: exit status 1
output: error: timed out waiting for the condition on pods/instaslice-operator-controller-manager-75d79c8b77-rqzmn

Retrying...
  [FAILED] in [It] - /go/pkg/mod/github.com/onsi/ginkgo/v2@v2.15.0/internal/node.go:463 @ 09/17/24 11:42:49.139
Deleting the cluster
• [FAILED] [301.760 seconds]
controller Operator [It] should run successfully
/instaslice-operator/test/e2e_emulator/e2e_test.go:70

  [FAILED] Timed out after 120.162s.
  Expected
      <bool>: false
  to be true
  In [It] at: /go/pkg/mod/github.com/onsi/ginkgo/v2@v2.15.0/internal/node.go:463 @ 09/17/24 11:42:49.139
------------------------------
S [SKIPPED] [0.000 seconds]
controller Operator [It] should apply the YAML and check if that instaslice resource exists
/instaslice-operator/test/e2e_emulator/e2e_test.go:107

  [SKIPPED] Spec skipped because an earlier spec in an ordered container failed
  In [It] at: /instaslice-operator/test/e2e_emulator/e2e_test.go:107 @ 09/17/24 11:42:50.915
------------------------------
S [SKIPPED] [0.000 seconds]
controller Operator [It] should apply the pod YAML with no requests and check the allocation in instaslice object
/instaslice-operator/test/e2e_emulator/e2e_test.go:118

  [SKIPPED] Spec skipped because an earlier spec in an ordered container failed
  In [It] at: /instaslice-operator/test/e2e_emulator/e2e_test.go:118 @ 09/17/24 11:42:50.915
------------------------------

Summarizing 1 Failure:
  [FAIL] controller Operator [It] should run successfully
/go/pkg/mod/github.com/onsi/ginkgo/v2@v2.15.0/internal/node.go:463

Ran 1 of 3 Specs in 301.761 seconds
FAIL! -- 0 Passed | 1 Failed | 0 Pending | 2 Skipped
--- FAIL: TestE2E (301.76s)
FAIL
FAIL    github.com/openshift/instaslice-operator/test/e2e_emulator      302.428s
FAIL
make: *** [test-e2e-emulator] Error 1

/close


Error: getaddrinfo ENOTFOUND

I'm running the following TypeScript code:
import * as nock from 'nock';
import * as rp from 'request-promise';
// ...
      const server = nock('https://fake.domain')
        .post('/endpoint', 'derp')
        .reply(200);
      await rp({
        method: 'POST',
        url: 'https://fake.domain/endpoint',
        body: 'derp',
      });
      server.done();

And getting the following error:
     RequestError: Error: getaddrinfo ENOTFOUND fake.domain fake.domain:443
      at new RequestError (node_modules/request-promise-core/lib/errors.js:14:15)
      at Request.plumbing.callback (node_modules/request-promise-core/lib/plumbing.js:87:29)
      at Request.RP$callback [as _callback] (node_modules/request-promise-core/lib/plumbing.js:46:31)
      at self.callback (node_modules/request/request.js:188:22)
      at Request.onRequestError (node_modules/request/request.js:884:8)
      at TLSSocket.socketErrorListener (_http_client.js:309:9)
      at connectErrorNT (net.js:1025:8)
      at _combinedTickCallback (internal/process/next_tick.js:80:11)
      at process._tickDomainCallback (internal/process/next_tick.js:128:9)

Instead I expected nock to intercept this and return a 200 response code.
I'm using the latest version of nock, request-promise, and Node.js v6.10.2.

Turns out calling nock.restore(); in a different file caused nock to not work here.  Removing that line fixed everything!

but why is it doing it? I'm trying to do a nock.restore(); in my beforeEach(); test setup. but as long as the restore() is there, tests will fail. remove it and the tests work as expected ... strange.


JBEHAVE-1133 ExamplesTableFactory shouldn't use custom default ResourceLoader-s

This change is the first step to removing custom default configuration objects (Keywords, ResourcesLoader-s and etc.).

It will help to support JBehave customization cases: configure once and use everywhere, less potential bugs related to customization
It may improve performance a bit (no duplicate object creations)

Is there any chance to review and merge the changes to the master so that they will be included in the upcoming JBehave 4.1 release?
I was needed to load story files from classpath and generate examples tables on runtime basing on DB data, but was not able to override default resource loader of examples tables. So the main reason of these changes is to eliminate existing shortcoming.

Hi, the scope of the PR is too big compared to the stated aim.   In particular, the fact it tries to inject the Configuration object in the components, instead of the individual dependencies.
Can you provide an example of how you'd need to have the resource loader configurable so we can try to satisfy it?

Hi, the original issue is not in resource loader configuration (in general, I implemented some types of resource loader for examples tables that load data from file system using some custom rules, from DB-s, from RESTful APIs). The original issue is that ExamplesTableFactory defines own custom resource loader:

https://github.com/jbehave/jbehave-core/blob/master/jbehave-core/src/main/java/org/jbehave/core/model/ExamplesTableFactory.java#L43
https://github.com/jbehave/jbehave-core/blob/master/jbehave-core/src/main/java/org/jbehave/core/model/ExamplesTableFactory.java#L51
https://github.com/jbehave/jbehave-core/blob/master/jbehave-core/src/main/java/org/jbehave/core/model/ExamplesTableFactory.java#L55

Removal of this custom resource loaders brings chains of changes in multiple classes that use the constructors with default loaders.
If you don't like the idea of Configuration injection in the components, I will refactor the changes.

Finally I've found time to redesign the solution.
@maurotalevi , could you please review the change?

@maurotalevi, could you please review the change?

@maurotalevi, could you please review the change?

@maurotalevi, could you please review the changes?

Merged. @maurotalevi , thank you!

New pull request: https://github.com/jbehave/jbehave-core/pull/152


Empty directories

Excuse me.I have ran data_preprocess.py,but I got empty directories in the directory 'recognition_train_img',like this

is that normal?

I recommend run single process to make sure there is no any running error, before you run multi-process mission.


Garbled characters appear upon long Chinese nickname

Thanks for your great work!
As the picture shows below, I played as IO and the other three are NPCs. When my nickname lenth is 2, its display is correct(in the later record). However when my nickname lenth is 10, garbled characters appear(in the earlier record).

Fixed in https://github.com/false-spring/gbfr-logs/releases/tag/0.0.9


Fix problems with read past end of dataset but within dimension length for vars with multiple unlimited dimensions

Fixes #1413
This PR also includes PR #1561 which also touches this section of code.

@WardF, could you please merge this soon? It's an important bug fix and I want these tests to be active for all the other PRs so we ensure that we're not breaking this fix. ;-)


Alternative methods to provide OIDC configuration

Hi,
I have noticed that the only way to provide the OIDC configuration (which some of is sensitive) is directly in the values file.
It would be good to be able to support loading this configuration from environment variables or files. If you are using a GitOps approach for managing your deployment of headlamp the current setup forces you into bad practice.
Is this a welcome change? If so I will make it.
Thanks,
Max Sargent

I did not read enough of the source, I have found the HEADLAMP_CONFIG_ prefix now, thanks.

Re-opening, this change will now be a request for:

Trivial change to the helm chart to support setting environment variables from a secret
Updating the koanf usage so that it can read the settings from a flat yaml file mounted at a pre-specified location

Thanks.

Thanks @maxsargentdev . We will look into this.


RAM usage

I'm not sure if it's only me, but I'm kinda concerned about the amount of ram it eats. I mean Intellij IDEA or Android Studio eats about 1-1.5k RAM while Chrome with lots of tabs opened also eats about 1k. This app, doing nothing fancy (like debugging, compiling, autocomplete and what not) eats constantly around 900MB.
macOS Sierra 10.12.4

Came here to open the same issue.
It was consuming 900MB also, but after upgrading through brew cask reinstall messenger dropped to around 200MB – which is acceptable but still a bit high compared with other messaging apps that consume less, like WhatsApp around 140MB.
macOS Sierra 10.12.4 (16E195)

Glad to hear that! I will try it later this day and confirm any changes

When you say 1k @PopTudor, are you taking about kilobytes? If so, you are gravely mistaken — Chrome uses at least a couple of hundred megabytes for it's supervisor "main" process and a lot more memory if you combine the memory usage of it's many "render" processes (Chrome and Safari uses a pool of separate processes, each with its own resource usage.)
This app uses a single-process webview, meaning that this app does not use additional processes to support the webview that loads messenger.com and in effect the sum of resource usage of this app (Messenger for Mac) needs to be compared to the sum of memory usage by Chrome or Safari.
For instance, here's the memory usage of Chrome on my machine:

If you sum the "Memory" column up, you get 2.6GB (2628MB)
Looking at this app's total memory usage, it's 360MB which includes the app itself + messenger.com in a webview:

So, not an issue, not a bug and incorrect assumptions about what is "normal" memory usage :)

@m4grio I tried it but with no effect :(
@rsms I was talking in MB since I have not seen any app uning 1 kilobyte of RAM. It might be an incorrect assumption but from my point of view it should not eat so much. For the comparison I installed another Messanger app called Goofy (no affiliation with them) and here is the result:

A couple of days ago it got to 1,8GB then I quit it. Don't get me wrong, I appreciate the effort and the software. Thank you!
As a guidance, I observed the memory starts to accumulate on scrolling up into the history and maybe it's not releasing previous resources. I don't know if you have control over that but it's a starting point :)


Animation unable to work with dynamic fillvalue values

When using dynamic fillvalue the arc does  not display correctly until animation is set to false even modifying the animation delay does not solve the problem

@TalelCS could you provide a video of what's happening if this happens again after updating to the latest 1.2.1 version? This should have been solved in that release https://github.com/shipt/segmented-arc-for-react-native/releases/tag/v1.2.1

Closing this issue due to inactivity, please create a new one if you experience this problem again. Thanks!


Datasource Autocompaction stuck 'Awaiting First Run'

Affected Version
0.22.1
Description
I'm opening a ticket after having no luck with my druidforum post: https://www.druidforum.org/t/datasource-autocompaction-awaiting-first-run/7087.
I’m trying to use Autocompaction to update a datasource segmentGranularity from ‘HOUR’ to ‘WEEK’. I’m testing with a small datasource (15mb / ~400,000 rows) which has many segments (5,000+).
I submit a compaction config like:
{
  "dataSource": "my_datasource",
  "taskPriority": 25,
  "inputSegmentSizeBytes": 419430400,
  "skipOffsetFromLatest": "P1M",
  "tuningConfig": {
    "partitionsSpec": {
      "type": "dynamic",
      "maxRowsPerSegment": 5000000
    },
    "type": "index_parallel",
    "forceGuaranteedRollup": false
  },
  "granularitySpec": {
    "segmentGranularity": "WEEK"
  }
}

Both the web console and curl against the api (e.g. curl get against /druid/coordinator/v1/config/compaction/ ) show that my compaction config has been set/accepted.
There are segments going back to 2021-05, so there are plenty of candidate segments to compact based on skipOffsetFromLatest.
There are 3 worker slots available and relevant compaction TaskSlot variables are: "compactionTaskSlotRatio" : 0.7, "maxCompactionTaskSlots" :<PHONE_NUMBER>

I’m expecting autocompaction to start compacting based on this config.
Instead, I find that in the unified-console, the dataSource Compaction column shows Awaiting first run and has been stuck like this for 24h+. Reviewing Coordinator logs, I don’t see any indication that compaction is even being attempted. No errors. If I grep “compact” in coordinator logs, nothing is returned except for a single line at startup indicating the coordinator is scheduling compaction tasks.
I made a branch in my fork with a docker-compose, ingestion spec, and compaction spec which seems to reproduce the issue. Steps:

run it: docker-compose up
submit the ingestion spec: curl -H 'Content-Type:application/json' -d<EMAIL_ADDRESS>-X POST http://localhost:8081/druid/indexer/v1/task
Let the datasource become fully available
submit the compaction spec: curl -H 'Content-Type:application/json' -d<EMAIL_ADDRESS>-X POST http://localhost:8081/druid/coordinator/v1/config/compaction

I have tried many tweaks to the compaction config (e.g. segmentGranularity to day instead of week) but haven't been able to get compaction to start. There do not seem to be any logs indicating autocompaction tasks are being created / attempted. We have also tried restarting our cluster (and restarting the docker-compose also does not resolve the issue).
If there are any more details I can provide, please let me know!

hey @gitmstoute, I had exactly the same problem with the same version.
To unblock the situation, I deleted an old database entry in druid_pendingsegments table that should not have remained:
druid_db=# select * from druid_pendingsegments;
-[ RECORD 1 ]-
id                         | xxx_2022-07-26T00:00:00.000Z_2022-07-26T01:00:00.000Z_2022-08-03T04:44:16.814Z_2427
datasource                 | xxx
created_date               | 2022-09-14T09:27:55.647Z
start                      | 2022-07-26T00:00:00.000Z
end                        | 2022-07-26T01:00:00.000Z
sequence_name              | index_kafka_xxx_44c72010954e750_0
sequence_prev_id           |
sequence_name_prev_id_sha1 | E6Exxx
payload                    | \xxxx
druid_db=# delete from druid_pendingsegments where id='xxx_2022-07-26T00:00:00.000Z_2022-07-26T01:00:00.000Z_2022-08-03T04:44:16.814Z_2427';

Thank you for the update @baaaaast! Sounds promising. I will investigate this and update!

exactly the same and also on the same version of druid: 0.22.1.

Thanks @linehrr I was starting to think I was going crazy.
@baaaaast even with the docker start scripts (should have an empty druid_pendingsegments table) I'm still unable to get autocompaction to kick off. Time is tight to keep investigating much further on my end.

it basically looks like this, and it's just stuck there forever.
coordinator logs look fine.
to me this looks like the segment compaction calculation/planning thread stuck.

2022-11-10T18:51:32,702 ERROR [Coordinator-Exec--0] org.apache.druid.server.coordinator.DruidCoordinator - Caught exception, ignoring so that schedule keeps going.: {class=org.apache.druid.server.coordinator.DruidCoordinator, exceptionType=class java.lang.RuntimeException, exceptionMessage=org.apache.druid.java.util.common.ISE: Error while killing pendingSegments of dataSource[Forecasting_geo] created until [2022-11-09T18:10:12.359Z]}

java.lang.RuntimeException: org.apache.druid.java.util.common.ISE: Error while killing pendingSegments of dataSource[Forecasting_geo] created until [2022-11-09T18:10:12.359Z]

    at org.apache.druid.client.indexing.HttpIndexingServiceClient.killPendingSegments(HttpIndexingServiceClient.java:415) ~[druid-server-0.22.1.jar:0.22.1]

    at org.apache.druid.server.coordinator.KillStalePendingSegments.run(KillStalePendingSegments.java:79) ~[druid-server-0.22.1.jar:0.22.1]

    at org.apache.druid.server.coordinator.DruidCoordinator$DutiesRunnable.run(DruidCoordinator.java:910) [druid-server-0.22.1.jar:0.22.1]

    at org.apache.druid.server.coordinator.DruidCoordinator$2.call(DruidCoordinator.java:720) [druid-server-0.22.1.jar:0.22.1]

    at org.apache.druid.server.coordinator.DruidCoordinator$2.call(DruidCoordinator.java:713) [druid-server-0.22.1.jar:0.22.1]

    at org.apache.druid.java.util.common.concurrent.ScheduledExecutors$4.run(ScheduledExecutors.java:163) [druid-core-0.22.1.jar:0.22.1]

    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_212]

    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_212]

    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_212]

    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [?:1.8.0_212]

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_212]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_212]

    at java.lang.Thread.run(Thread.java:748) [?:1.8.0_212]

Caused by: org.apache.druid.java.util.common.ISE: Error while killing pendingSegments of dataSource[Forecasting_geo] created until [2022-11-09T18:10:12.359Z]

    at org.apache.druid.client.indexing.HttpIndexingServiceClient.killPendingSegments(HttpIndexingServiceClient.java:403) ~[druid-server-0.22.1.jar:0.22.1]

this is something useful we just found.
we saw this error log on the coordinator, regarding error deleting pendingSegment of a datasource.
then we suspended the ingestion tasks and cleaned up the pendingSegment table.
after that coordinator is unblocked and start to issue the compaction tasks.
I think this is very related to the issue, hopefully this can provide some good clue during the investigation.

ok after we cleaned up the pendingsegment basically by removing the broken records in the table, coordinator is now functioning ok and scheduling the auto-compaction now.
so I do think there is a bug somewhere so that first some pending segments can't be killed for some reason and also if this happens, it will block coordinator from scheduling compaction.


Allow executing of a single test from a file

Investigate the possibility to pass test nr to executable if only a single test was requested to be run instead of the entire file.
This would mean a vscode setting for regex for parameter passed to executable along with test nr. I.e. test.exe -test 5 to only run 5th test in file. Or pass the actual test function name (same as in the UI) to the exe.
Choose between test nr or function name approach based on how the future testing API will work for vscode (are tests guaranteed to always have the same order in the file - i.e. not user orderable or hideable)
Then it's up to the exe to implement or ignore this.

For reference, Unity ships with fixtures to allow exactly this usecase (https://github.com/ThrowTheSwitch/Unity/tree/master/extras/fixture), the resulting binaries can then be called with -n test_name.

Thanks for the suggestion. Started switching to fixtures on my personal project and using that as test grounds for adding support for fixtures to this extension.
Future v0.0.7 will add support for fixtures by 2 new extension settings:

testExecutableArgs: to pass arguments to test exes when running them. Tests written with the fixture library don't report anything for a Pass by default, so can't tell if a test passed or was not run. Passing -v to tests fixes this and this setting could be used more broadly too.
testExecutableArgSingleCaseRegex: to tell the extension how to add the test case's name to the exe to only run that test case. With Unity fixtures would be set to -n $1 to replace $1 with the test's name, but who knows if there are other custom formats out there, so that could be supported too. If empty, the extension would default to current approach of running the entire test file when a single test case is run from the UI.


Helpers are clobbering the options in 2.0.0.rc

When using simple_form.en.yml in conjunction with the helper method label, the options hash gets modified. The label method seems to add the :placeholder key with no value to the options hash, which then stops the input method from using the locales.
I have found that passing options.dup to all the helpers stops this from happening.  It might be worth checking the other helper methods too.
# simple_form.en.yml
en:
  simple_form:
    placeholders:
      blog:
        name: 'type your name here'

<!-- _form.html.erb -->
<%= simple_form_for @blog  do |form| %>
  <%= render :custom_field,
    :locals => { :form => form, :options => {:label => 'bar'}} %>
<% end %>

<!-- _custom_field.html.erb -->
<%= form.label :name, options %>
<%= form.input :name, options %>
<%= form.hint :name, options %>
<%= form.full_error :name, options %>

Because there is no :placeholder key in the options hash, i would expect form.input to use locales placeholder, but it is not because the options hash gets filled up with empty values from the label method.
Is the correct solution to pass options.dup?
<%= form.label :name, options.dup %>
<%= form.input :name, options.dup %>

Thanks for reporting this issue. The label method should not modify the options hash. Which SimpleForm version are you using?

Thank you for the awesome gem.
I'm using version 2.0.0.rc
On 20/02/2012, at 7:04 PM, Rafael Mendonça<EMAIL_ADDRESS>wrote:

Thanks for reporting this issue. The label method should not modify the options hash. Which SimpleForm version are you using?

Reply to this email directly or view it on GitHub:
https://github.com/plataformatec/simple_form/issues/463#issuecomment-4066616

@rafaelfranca
Thank you it is working!


permission 'purpur.joinfullserver' is not checked on join.

Spark link
https://spark.lucko.me/DSRzKkf9x7
Expected behavior
The player with the permission "purpur.joinfullserver" can actually join the full server.
Observed/Actual behavior
I only have luckperms installed, just clean purpur server install with no configs changed. (Only thing changed is: max-players=1 in server.properties for testing purposes)
I have the luckperms permission set: purpur.joinfullserver for my user
lp user <user> permission set purpur.joinfullserver true
also tried adding the permission to my users group "default", no difference.
lp group default permission set purpur.joinfullserver true
I also tried creating a new group and adding the permission in there with no luck.
When running lp verbose record <user> and joining the server (with open slots otherwise "server full" kick), these permissions are te the only permissions starting with purpur. :
[LP] VB > thijsjeboygaming - purpur.debug.f3n - false
[LP] VB > thijsjeboygaming - purpur.portal.instant - false

See full verbose log export
When running lp verbose record <user> and joining the server when it is full, the verbose command outputs nothing.
So i presume that it does not check the purpur.joinfullserver permission on join?
When running lp user <user> permission check purpur.joinfullserver:
[LP] Permission information for purpur.joinfullserver:
[LP] - thijsjeboygaming has purpur.joinfullserver set to true in context global.
[LP] - thijsjeboygaming inherits purpur.joinfullserver set to true from default in context global.
[LP]
[LP] Permission check for purpur.joinfullserver:
[LP]     Result: true
[LP]     Processor: common.DirectProcessor
[LP]     Cause: 7847c8cb-0adb-4fcb-980b-a879536d6a0a has purpur.joinfullserver set to true in context global
[LP]     Context: None

I am running the latest 1.21.1 Purpur version, and I can't seem to find anything in the configs.
The user can join the full server if they have OP.
Steps/models to reproduce

Install the latest version of Purpur
Install the Luckperms plugin
Edit the server.properties file and set max-players=1 (assuming you have 2 accounts to test this with)
Use the Luckperms command: lp user <user> permission set purpur.joinfullserver true in console
Join the server with the account that does not have this permission first.
Join the server with the account that does have the permission as last.

You will see a The server is full! kick message on the account that has the purpur.joinfullserver = true permission.
Purpur version
version
[19:48:56 INFO]: Checking version, please wait...
[19:48:56 INFO]: Current Purpur Version: 1.21.1-2328-d49ca07 (MC: 1.21.1)*
* You are running the latest version

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.
[ ] I ticked all the boxes without actually reading them
[X] My version of Minecraft is supported by Purpur.

Other
Other people in the Discord server also have the same problem that I have described.
My initial message in the Discord server.
Message of a individual that also tested this.

Can confirm that it's still an issue on 1.21.3.
LuckPerms doesn't get around to loading the player's perms in time for the check to process. Will look into this more at a later date.


Add endpoint to download the agent binaries

Summary of the Pull Request
What is this about?
PR Checklist

[ ] Applies to work item: #xxx
[ ] CLA signed. If not, go over here and sign the CLI.
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

Codecov Report

Merging #2600 (264c675) into main (fb8a4e3) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #2600      +/-   ##
==========================================
- Coverage   24.80%   24.73%   -0.07%
==========================================
  Files         120      121       +1
  Lines       12475    12508      +33
==========================================
  Hits         3094     3094
- Misses       9381     9414      +33

Impacted Files
Coverage Δ

src/ApiService/ApiService/Functions/Tool.cs
0.00% <0.00%> (ø)

src/ApiService/ApiService/OneFuzzTypes/Enums.cs
30.98% <ø> (ø)

src/ApiService/ApiService/onefuzzlib/Containers.cs
60.68% <0.00%> (-6.49%)
:arrow_down:

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


Migration to aws-sdk-go-v2?

AWS SDK for Go (v1) is already in maintenance mode since July 31, 2024, and is moving towards end of life:
https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/
Are there any plans to migrate Terratest to aws-sdk-go-v2?

hey @artem-nefedov
Can you help test my PR #1451?
You can point to my fork by using the replace directive in your go.mod file.
go mod init github.com/wakeful/new-project
go mod edit -replace github.com/gruntwork-io/terratest<EMAIL_ADDRESS>go get<EMAIL_ADDRESS>

Seems done to me

The changes introduced in PR #1451 modify the signatures of exposed functions, which is a breaking change. As a result, this should have triggered a major version bump from 0.47.2 to 1.0.0, rather than a minor version bump to 0.48.0.
For example, the function NewEcsClientE in modules/aws/ecs.go previously returned *(aws/aws-sdk-go/service/)ecs.ECS. After this PR, it now returns *(aws-sdk-go-v2/service/)ecs.Client. This breaking change impacts compatibility and aligns with semantic versioning principles, which mandate a major version increment for such updates.

Hi @uchanchlani !  Thanks for the thoughtful feedback!
Terratest is still pre-1.0, and as such does not have backwards compatibility guarantees within its major version of 0.  We tend to use minor version bumps to indicate when things might break.  Gruntwork is, however, pushing to get all of the tools it maintains to 1.0 and begin enforcing such a backwards compatibility promise, although we are not there yet.  I/we apologize if this causes any inconvenience along the way, however we feel its important that we have a stable foundation that we can commit to for a long time before officially releasing 1.0.


Relative path in file field?

How can I use the combination of BetterBibTex and ZotFile to get an exported .bib with a relative path in the file field?
Settings

Edit -> Preferences -> Advanced -> Files And Folders -> Base Directory:
C:\Users\scott\OneDrive - Clean Power Research\ref\zotero\papers_added
Edit -> Preferences -> Better BibTex-> Automatic Export:
On Change
Edit -> Preferences -> Better BibTex->My Library => Collection:
ExportToBib
Tools -> ZotFile Preferences -> Location of Files:
C:\Users\scott\OneDrive - Clean Power Research\ref\zotero\papers_added\papers

In addition, when I first created the collection ExportToBib, I set its path to:
C:\Users\scott\OneDrive - Clean Power Research\ref\zotero\papers_added
(so that the .bib file would be exported to the directory above the pdfs)
Result
The file fields in C:\Users\scott\OneDrive - Clean Power Research\ref\zotero\papers_added\ExportToBib.bib are still absolute, for example:
@incollection{Beaudin17hmEnergyMgmtModelCmplx,
  title = {Home {{Energy Management Systems}}: {{A Review}} of {{Modelling}} and {{Complexity}}},
  shorttitle = {Home {{Energy Management Systems}}},
  booktitle = {Energy {{Solutions}} to {{Combat Global Warming}}},
  author = {Beaudin, Marc and Zareipour, Hamidreza},
  editor = {Zhang, XinRong and Dincer, Ibrahim},
  year = {2017},
  pages = {753--793},
  publisher = {{Springer International Publishing}},
  address = {{Cham}},
  doi = {10.1007/978-3-319-26950-4_35},
  abstract = {Innovations in the residential sector are required to reduce environmental impacts, as the sector is a contributor to greenhouse gas emissions. The increasing demand for electricity and the emergence of smart grids have presented new opportunities for home energy management systems (HEMS) in demand response markets. HEMS are demand response tools that shift and curtail demand to improve the energy consumption and production profile of a dwelling on behalf of a consumer. HEMS usually create optimal consumption and productions schedules by considering multiple objectives such as energy costs, environmental concerns, load profiles and consumer comfort. The existing literature has presented several methods, such as mathematical optimization, model predictive control and heuristic control, for creating efficient operation schedules and for making good consumption and production decisions. However, the effectiveness of the methods in the existing literature can be difficult to compare due to diversity in modelling parameters, such as appliance models, timing parameters and objectives. The present chapter provides a comparative analysis of the literature on HEMS, with a focus on modelling approaches and their impact on HEMS operations and outcomes. In particular, we discuss a set of HEMS challenges such as forecast uncertainty, modelling device heterogeneity, multi-objective scheduling, computational limitations, timing considerations and modelling consumer well-being. The presented work is organized to allow a reader to understand and compare the important considerations, approaches, nomenclature and results in prominent and new literary works without delving deeply into each one.},
  file = {C\:\\Users\\scott\\OneDrive - Clean Power Research\\ref\\zotero\\papers_added\\papers\\Beaudin17hmEnrgyMgmtModelCmplx.pdf},
  isbn = {978-3-319-26950-4},
  keywords = {Appliance models,Home energy management system,Home energy scheduling,Household device models,Net-zerohomes,Optimal residential energy management,Smart grid,Smart home},
  language = {en},
  series = {Lecture {{Notes}} in {{Energy}}}
}

Result I was hoping for
file fields like this:
file = {papers\\Beaudin17hmEnrgyMgmtModelCmplx.pdf},
Can this be done?

I submitted a bug report:  LTMWYT82-euc

You previously would have needed to set https://retorque.re/zotero-better-bibtex/installation/preferences/hidden-preferences/#relativefilepaths but build 536 should make that automatic for exports to the attachments base dir.

Can you try build 537?

It works.  Thanks.

Thanks for the confirmation


fixed crash on time picker and date picker click

closes #210
This pull request includes significant updates to the DatePickerManager and TimePickerManager classes in the calf-ui module for iOS. The changes focus on refactoring the code to improve the handling of date and time picker events by using NSObject delegates.
Refactoring for event handling:

calf-ui/src/iosMain/kotlin/com/mohamedrejeb/calf/ui/datepicker/DatePickerManager.kt: Replaced the use of method pointers and direct actions with an NSObject delegate to handle the date change events in the DatePickerManager class. [1] [2]
calf-ui/src/iosMain/kotlin/com/mohamedrejeb/calf/ui/timepicker/TimePickerManager.kt: Similarly, replaced the use of method pointers and direct actions with an NSObject delegate to handle the time change events in the TimePickerManager class.

Thanks for the great library 🚀


rename gcc-for-nvcc-source for scathgap-l4t-r35.x branch

gcc-for-nvcc: rename gcc-for-nvcc-source -> gcc-source-for-nvcc
to take advantage of the automatic license whitelisting buried in
base.bbclass that checks for PN starting with 'gcc-source-', and
avoid the issue mentioned in https://github.com/OE4T/meta-tegra/issues/1711.
Signed-off-by: Islam Hussein<EMAIL_ADDRESS>

Cherry picked the change from #1732


Global parameters for workflow templates

Hi I am trying to set up a workflow template that can accept global parameters from Argo Events.
When I create my workflow template using Hera I see the following:
metadata:
  name: train-template
  namespace: argo
  uid: 6d42116f-3c0f-473e-8f5e-d7c0015e034d
  resourceVersion: '91607583'
  generation: 1
  creationTimestamp: '2022-04-19T07:56:20Z'
  labels:
    workflows.argoproj.io/creator: system-serviceaccount-argo-default
  managedFields:
    - manager: argo
      operation: Update
      apiVersion: argoproj.io/v1alpha1
      time: '2022-04-19T07:56:20Z'
      fieldsType: FieldsV1
      fieldsV1:
        'f:metadata':
          'f:labels':
            .: {}
            'f:workflows.argoproj.io/creator': {}
        'f:spec': {}
spec:
  templates:
    - name: train-template
      inputs: {}
      outputs: {}
      metadata: {}
      dag:
        tasks:
          - name: echo-pvsystemid
            template: echo-pvsystemid
            arguments:
              parameters:
                - name: pvsystemid
                  value: '"this did not work"'
            continueOn: {}
      parallelism: 50
    - name: echo-pvsystemid
      inputs:
        parameters:
          - name: pvsystemid
            value: '"this did not work"'
      outputs: {}
      metadata: {}
      daemon: false
      script:
        name: echo-pvsystemid
        image: 'python:3.7'
        command:
          - python
        resources:
          limits:
            cpu: '1'
            memory: 4Gi
          requests:
            cpu: '1'
            memory: 4Gi
        imagePullPolicy: Always
        source: |
          import json
          pvsystemid = json.loads('''{{inputs.parameters.pvsystemid}}''')

          print(pvsystemid)
  entrypoint: train-template
  arguments: {}

Where there are no inputs for the train-template. Is there a way with Hera to specify a global input parameter?

Hi @lambertsbennett! Thanks for submitting the question. Also, thanks for writing a Medium blog that used Hera 🙂 do you mind sharing the Hera code you used? My guess is that pvsystemid is a parameter for a Python function and the value was set via the func_params field on a Task?

Yes exactly and no problem I'm a huge fan!
from hera.task import Task
from hera.workflow_template import WorkflowTemplate
from hera.workflow_template_service import WorkflowTemplateService

def echo_pvsystemid(pvsystemid: str):
    print(pvsystemid)

ws = WorkflowTemplateService(host='https://DOMAIN:2746', token=TOKEN, verify_ssl=False)
w = WorkflowTemplate('train-template', ws, namespace='argo')
echo = Task('echo-pvsystemid', echo_pvsystemid, [{'pvsystemid': 'Hello, world!'}])
w.add_tasks(echo)
w.create()

I've been able to pull off something very similar with YAML, but when I run this no matter what "Hello, world!" is printed and it ignores the parameter value obtained from the request body.
For completeness the Argo Events Sensor definition is here:
apiVersion: argoproj.io/v1alpha1
kind: Sensor
metadata:
  name: webhook
spec:
  template:
    serviceAccountName: argo
  dependencies:
    - name: train-trigger
      eventSourceName: webhook
      eventName: train
  triggers:
    - template:
        name: webhook-train-trigger
        k8s:
          operation: create
          source:
            resource:
              apiVersion: argoproj.io/v1alpha1
              kind: Workflow
              metadata:
                generateName: train-w-global-arg-
              spec:
                serviceAccountName: argo
                entrypoint: echo-pvsystemid
                arguments:
                  parameters:
                    - name: pvsystemid
                      value: hello
                templates:
                  - name: echo-pvsystemid
                    dag:
                      tasks:
                      - name: echo-pvsystemid
                        templateRef:
                          name: train-template
                          template: echo-pvsystemid
                      # - name: echo-random
                      #   templateRef:
                      #     name: train-template
                      #     template: echo-random
          parameters:
            - src:
                dependencyName: train-trigger
                dataKey: body.pvsystemid
              dest: spec.arguments.parameters.0.value

I have a hunch of what's going on. When parameters are created by Hera it sets a literal value on both the task parameters at the workflow level and at the template level, as can be seen here and here. The documentation of value says:
Value is the literal value to use for the parameter. If specified in the context of an input parameter, the value takes precedence over any passed values

Problem 1: the inputs should not have a value.
Now, your goal is to parametrize tasks based on global variables. These have a different access pattern, as documented here. The global ones are accessed via {{workflow.parameters.X}}.
Problem 2: Hera does not currently support global parameters, and it needs to support both global and local (as arguments).
I attempted the global parameter usage using a modified workflow of this Hera example. Here's the YAML:
metadata:
  name: delightful-dragon
  namespace: default
spec:
  arguments:
    parameters:
      - name: x
        value: '"hello hera"'
  entrypoint: hello
  templates:
  - name: hello
    dag:
      tasks:
        - name: t
          template: t
          arguments:
            parameters:
              - name: x
                value: "{{workflow.parameters.x}}"   # TODO: Hera needs to support specifying global parameters
    parallelism: 50
  - name: t
    inputs:
      parameters:
        - name: x  # TODO: Hera needs to remove the value/default of the input
    outputs: {}
    metadata: {}
    daemon: false
    script:
      name: t
      image: 'python:3.7'
      command:
        - python
      resources:
        limits:
          cpu: '1'
          memory: 1Gi
        requests:
          cpu: '1'
          memory: 1Gi
      source: |
        import json
        x = json.loads('''{{inputs.parameters.x}}''')

        print(x)

So, I am inclined to mark the two things above as enhancements. Thoughts?
I also wanted to ask: could the dest field on the even be modified so that it injects a different part of the template? For instance, instead of dest: spec.arguments.parameters.0.value, could that be dest: spec.templates.0.dag.tasks.0.arugments.parameters.0.value?

Thanks for the work on this! I agree that these would be nice enhancements. At least for coupling templates with the use of Argo Events it would be super useful.
To answer your question, I changed up the YAML to include those fields and ran it again and there seems to be no problem with pointing to that destination as a dest.
I'm a beginner when it comes to contributing to open source projects, but if I could help in any way with the implementation I'd be happy to!

seems to be no problem with pointing to that destination as a dest.

Ok, great! 🎉  So it works for now as a work-around?

I'm a beginner when it comes to contributing to open source projects, but if I could help in any way with the implementation I'd be happy to!

That would be amazing! Hera has a contribution guide that outlines how one can contribute 🙂 The more important question is:

do you feel like you have sufficient understanding from the above discussion to contribute this enhancement? If not, perhaps I can offer a bit more guidance on the code changes and whatnot in order to help move ahead with the change but you still make it? Remote pairing could work as well!

@flaviuvadan I'll read the contribution guide! In terms of understanding what needs to happen to implement the change I think I need to get more familiar with the code.
I would love any help getting started and hopefully that will get me up to speed that I could contribute more frequently! I will read through the codebase and work to understand the layout of the project.

Hello, I have se same problem, but with the output params, I wrote a wrapper for "Taks" in the meantime.
I'd like to contribute with this feature. Here my progress.
This's working for me, for now.
# imports required

class ValueFrom(BaseModel):
    default: Optional[str]
    parameter: Optional[str]
    path: Optional[str]

    def get_spec(self) -> IoArgoprojWorkflowV1alpha1ValueFrom:
        spec = IoArgoprojWorkflowV1alpha1ValueFrom()
        if self.path:
            setattr(spec, 'path', self.path)
        elif self.parameter:
            setattr(spec, 'parameter', self.parameter)
        if self.default:
            setattr(spec, 'default', self.default)

        return spec

class Parameter(BaseModel):

    name: str
    value: Optional[str]
    value_from: Optional[ValueFrom]
    default: Optional[str]

    @root_validator
    def check_value_or_value_from(cls, values):
        if not values.get('value') and not values.get('value_from'):
            raise ValueError('either value or value_from is required')
        if values.get('value') and values.get('value_from'):
            raise ValueError('only one value or value_from field required')
        return values

    def get_spec(self) -> IoArgoprojWorkflowV1alpha1Parameter:
        """Constructs the corresponding Argo parameters representation"""
        spec = IoArgoprojWorkflowV1alpha1Parameter(name=self.name)
        if self.value:
            setattr(spec, 'value', self.value)
        elif self.value_from:
            setattr(spec, 'value_from', self.value_from.get_spec())
        if self.default:
            setattr(spec, 'default', self.default)
        return spec

class MyTask(Task):

    def __init__(
            self,
            name: str,
            func: Callable,
            image: str,
            output_parameters: Optional[List[Parameter]]
    ):
        self.output_parameters = output_parameters
        super().__init__(name, func, image=image)

    def get_outputs(self) -> IoArgoprojWorkflowV1alpha1Outputs:
        """Assembles and returns the task outputs"""
        return IoArgoprojWorkflowV1alpha1Outputs(artifacts=self.argo_output_artifacts,
                                                 parameters=self.get_argo_output_parameters())

    def get_argo_output_parameters(self) -> List[IoArgoprojWorkflowV1alpha1Parameter]:
        """Assembles and returns a list of artifacts assembled from the Hera internal output artifact representation"""
        if not self.output_parameters:
            return []
        out_parameters = [o.get_spec() for o in self.output_parameters]
        return out_parameters if out_parameters else []

# Example function
def params():
    connector = ""

    def arguments(step, step5, secrets):
        with open('/step', 'w') as f:
            f.write(step)
        with open('/step5', 'w') as f:
            f.write(step5)
        with open('/secrets', 'w') as f:
            f.write(secrets)

    if connector == 'salinas':
        arguments('step_salinas', 'extractor', 'production-salinas-secrets')
    else:
        arguments('step_generic', 'sales', 'production-orders-secrets')

ws = WorkflowService(host=HOST, verify_ssl=False, token=TOKEN)
w = Workflow(name='origin', service=ws, namespace='argo')

parameters_task = MyTask(
    'parameters',
    params,
    image='python:alpine3.15',
    output_parameters=[
        Parameter(name='step', value_from=ValueFrom(path='/step')),
        Parameter(name='step5', value_from=ValueFrom(path='/step5')),
        Parameter(name='secrets', value_from=ValueFrom(path='/secrets')),
    ])

w.add_tasks(parameters_task)
w.create()


Updating arch diagram according to new scope

The scope of the project has changed and it does not modify ingresses, services, or deployments related to the target application. This PR reflects that change in the architecture diagram
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)

Thanks @tomkerkhove. I added #99 to track that work.


Relays Not Working with CNTools

Relay Nodes info don't display when node is running with CNTools.

Could you provide more information, please? Your node's configuration file, RTView configuration file, etc.

Sorry about that.
On 3 nodes, (2 relays and 1 producer) Im running 1.24.2 and I installed RTView 0.3.0 on a separate server...It looks like my blockproducer is fine but no data to coming from my relays.
Since I'm using CNTools an my immediate thought is that it's conflicting with topologyUpdater file, is this possible?
here is the bottom on my config file for one of the conflicting nodes: (yes, it's suppose to be 30001)
https://prnt.sc/w78zmf
Everything else in config file has been double checked and looks good to me.

Fixed it. My appologies!


Add Dutch (Belgium) version to Dutch Fuzzy Clock

Description
This PR adds a Belgian Dutch variation to the Dutch Fuzzy Clock.
The main difference with the existing Dutch version is that we say na instead of over.
Copilot

🤖 Generated by Copilot at 5bbf08c
Summary
🇧🇪🕒🗣

This pull request adds a new feature to the dutch_fuzzy_clock app, which allows users to display the time in a fuzzy way using the Dutch language as spoken in Belgium. It does this by adding a new language option and a new word dictionary in the apps/dutchfuzzyclock/dutch_fuzzy_clock.star file.

dutch_fuzzy_clock
now speaks Belgian Dutch too
a winter update

Walkthrough

Add support for Dutch language in Belgium in dutch_fuzzy_clock.star (link, link, link)

I have read the CLA Document and I hereby sign the CLA

LGTM. @remyblok ?

Yes. Looks good to me too!


gofmt -s

Thanks, to be merged as https://github.com/ory-am/hydra/pull/81/commits/ed4af602061214ff42a1f6c5a6c1eb9cff1acb57.


The callback address？

Thank you very much for making such a good tool. I can use my RSS reader to read my tumblr following blog now.
After using it for a while, I found that the service you provided was updated about three hours, perhaps because I was following too many blogs and many posts were not pushed.
I try to build this service on my own server, but I have a problem in step 0:
Tumblr requires a callback address and I don't know it.
On the other hand, I don't know where to set the frequency of updates?
Thank you for your creation and look forward to your answer.

Thanks, I'm glad you think it's useful :)

After using it for a while, I found that the service you provided was updated about three hours, perhaps because I was following too many blogs and many posts were not pushed.

tumblr2rss is pretty dumb, it just calls the Tumblr API and renders it as an RSS feed. tumblr2rss does have the drawback that it will only render the last 20 items in the feed. If your scraper is only scraping every 3 hours, and there are more than 20 posts in that period of time, they will not be included in the feed. tumblr2rss does have an intentionally undocumented feature that allows you to include more posts.  You can try adding ?length=<count> where <count> is a number <=100. Instead of the default, tumblr2rss will render that many posts in the feed.

I try to build this service on my own server, but I have a problem in step 0: Tumblr requires a callback address and I don't know it.

The callback address is the URL of the page that tumblr redirects the user to after they have registered. It's part of the OAuth authentication flow. You can read more about it here. tumblr2rss uses the /registered path for this purpose. So if you were hosting the server on foo.com, you would use http://foo.com/registered as the callback address.

On the other hand, I don't know where to set the frequency of updates?

The easiest way is to just increase the number of posts in the feed using ?length=... as described earlier.

I have tried it and it is very successful.
Thank you very much

Glad to hear it!


Add limit to OpsGenie message

OpsGenie API has a limit of 130 characters to a message.

@stuartnelson3 done. Let me know if you want me to squash the commits, or it's fine separated.

@stuartnelson3 I've rebased it from master to update logging to use the go-kit way. Also squashed it in 1 commit.


Document how to create xcconfig file for running devicelab tests locally on iOS

When I run an iOS devicelab test locally, it tells me to specify a xcconfig. We should document on https://github.com/flutter/flutter/tree/master/dev/devicelab how to create that file and where the required information can be found.
/cc @yjbanov

Do you have a preference for where to put such a document? I've used Wiki in the past, e.g.: https://github.com/flutter/flutter/wiki/Flutter-CLI-crash-reporting

The error message would provide a link to the wiki page.

I would have expected to find the information in the readme for device lab: https://github.com/flutter/flutter/blob/master/dev/devicelab/README.md
That one also tells me everything else I need to know about running a task.

We should also re-evaluate if we still need the xcconfig. Now that @xster added support for automatically selecting the correct certificates for signing it might no longer be needed...


OSPP: Implementation of Heterogeneous Multi-Edge Collaborative Neural Network Inference for High Mobility Scenarios

This PR is implementaion of https://github.com/kubeedge/ianvs/issues/100

@hsj576 might also want to take a look at this project implementation

/lgtm

This pull request contains 4 commits, which might make maintenance difficult, considering the number of contributors, pull requests, and their commits in KubeEdge Ianvs recently. In the final stage, @wyoung1 can squash the commits into one using rebase techniques.

Thank you for your suggestion, I have squashed all submissions into one.

/lgtm

/lgtm

lgtm

/approve


Link @drawable/recorder to com.simplemobiletools.voicerecorder

Adds support for Simple Voice Recorder

Hello! Cheers for your interest in contributing. Unfortunately, since Google Recorder and Simple Voice Recorder have different icons, @drawable/recorder shouldn’t be used for Simple Voice Recorder. A separate icon would be required. You are welcome to create such an icon and reopen this pull request or open a new one. Thanks again!


Issue #1528

Added job posting in Issue #1528

hi @Tatenda there seems to be a lot of unnecessary changes for the package-lock.json file. Could you remove those changes?

HI @jamessspanggg i reversed those changes after I was made aware of them.


feat(cli): show environment info in verbose mode

Motivation/Description of the PR

It would be more convenient to show environment info when running tests with verbose mode.

 Environment information:-

codeceptVersion:  "3.5.4"
nodeInfo:  18.16.0
osInfo:  macOS 13.5
cpuInfo:  (8) arm64 Apple M1 Pro
chromeInfo:  116.0.5845.179
edgeInfo:  116.0.1938.69
firefoxInfo:  Not Found
safariInfo:  16.6
helpers:  {
 "Playwright": {
  "url": "https://github.com",
  "show": false,
  "browser": "chromium",
  "waitForNavigation": "load",
  "waitForTimeout": 30000,
  "trace": false,
  "keepTraceForPassedTests": true
 },
 "CDPHelper": {
  "require": "./helpers/CDPHelper.ts"
 },
 "OpenAI": {
  "chunkSize": 8000
 },
 "ExpectHelper": {
  "require": "codeceptjs-expect"
 },
 "REST": {
  "endpoint": "https://reqres.in",
  "timeout": 20000
 },
 "AllureHelper": {
  "require": "./helpers/AllureHelper.ts"
 }
}
plugins:  {
 "screenshotOnFail": {
  "enabled": true
 },
 "tryTo": {
  "enabled": true
 },
 "retryFailedStep": {
  "enabled": true
 },
 "retryTo": {
  "enabled": true
 },
 "eachElement": {
  "enabled": true
 },
 "pauseOnFail": {}
}
***************************************
If you have questions ask them in our Slack: http://bit.ly/chat-codeceptjs
Or ask them on our discussion board: https://codecept.discourse.group/
Please copy environment info when you report issues on GitHub: https://github.com/Codeception/CodeceptJS/issues
***************************************
CodeceptJS v3.5.4 #StandWithUkraine

Type of change

[ ] :rocket: New functionality

Checklist:

[ ] Tests have been added
[ ] Documentation has been added (Run npm run docs)
[ ] Lint checking (Run npm run lint)
[ ] Local tests are passed (Run npm test)

Thanks, makes much sense!


feat: Basic implementation of traits

Description
Make the most basic test case for traits execute correctly. Although this review looks big, it's mostly test code.
Next step will be to refactor tests in resolver, so I can add more unit tests and move the errors from Def Collecter to Resolver.
PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

After this PR this noir programs work:
Execution of specialized for the specific type:
trait Default {
    fn default(x: Field, y: Field) -> Self;
    fn method2(x: Field) -> Field {
	x
    }
}

struct Foo {
    bar: Field,
    array: [Field; 2],
}

impl Default for Foo {
    fn default(x: Field,y: Field) -> Self {
        Self { bar: x, array: [x,y] }
    }

    fn method2(x: Field) -> Field {
	x * 3
    }
}

fn main(x: Field) {
    let first = Foo::method2(x);
    assert(first == 3 * x);
}

Execution of trait provided default implementation
trait Default {
    fn default(x: Field, y: Field) -> Self;
    fn method2(x: Field) -> Field {
	x
    }
}

struct Foo {
    bar: Field,
    array: [Field; 2],
}

impl Default for Foo {
    fn default(x: Field,y: Field) -> Self {
        Self { bar: x, array: [x,y] }
    }
}

fn main(x: Field) {
    let first = Foo::method2(x);
    assert(first == x);
}

For more examples refer to tests added in this PR

@jfecher Have a nice weekend :)

Looks like you've got some import errors

Does this close https://github.com/noir-lang/noir/issues/527?

@yordanmadzhunkov would you like to take a jab at documenting this PR? https://github.com/noir-lang/docs/issues/359

Sure, we will document traits, but for now I prefer to focus on testing/bug fixing, before documentation.

@Savio-Sou we're avoiding documenting traits until they're complete. We don't want users to be thinking they're in the language yet. There's also a compiler warning when using them to alert users they're still in development. This PR is just one in a series since traits are a large feature we need to break up into many PRs.

Thanks for the clarification @jfecher!
Do we have a list of the intermediate Issues that'd get us to completion somewhere?
Would be great if you could help add a tasklist on https://github.com/noir-lang/noir/issues/527 if not. Feel free to edit the Issue directly!

@yordanmadzhunkov I'm documenting traits in the Noir docs. Will add you as a reviewer if you don't mind!

@yordanmadzhunkov I'm documenting traits in the Noir docs. Will add you as a reviewer if you don't mind!

Do it :)


ERROR: Failed to initialize driver for device. Intel HD 2500

Tested versions
Godot_v4.3-stable_win64.exe
System information
Device name	AHQ-PC Processor	Intel(R) Core(TM) i3-3210 CPU @ 3.20GHz   3.20 GHz Installed RAM	12.0 GB (11.9 GB usable) Device ID	23BFFD3F-DA76-487C-A217-0D7F0AA571DD Product ID	00331-10000-00001-AA787 System type	64-bit operating system, x64-based processor Pen and touch	No pen or touch input is available for this display
Issue description
PowerShell 7.5.0-preview.4
PS I:\godot> I:\godot\Godot_v4.3-stable_win64.exe
PS I:\godot> Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org
WARNING: Your video card drivers seem not to support the required OpenGL 3.3 version, switching to ANGLE.
     at: DisplayServerWindows (platform/windows/display_server_windows.cpp:6055)
OpenGL API OpenGL ES 3.0.0 (ANGLE 2.1.1 git hash: 468fcbe033fa) - Compatibility - Using Device: Google Inc. (Intel) - A)

Editing project: E:/games/hello
Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org
ERROR: Required extension VK_KHR_surface not found.
   at: (drivers/vulkan/rendering_context_driver_vulkan.cpp:153)
ERROR: Condition "err != OK" is true. Returning: err
   at: initialize (drivers/vulkan/rendering_context_driver_vulkan.cpp:594)
WARNING: Your video card drivers seem not to support Vulkan, switching to Direct3D 12.
     at: DisplayServerWindows (platform/windows/display_server_windows.cpp:5985)
ERROR: D3D12CreateDevice failed with error 0x887a0004.
   at: (drivers/d3d12/rendering_device_driver_d3d12.cpp:6302)
ERROR: Condition "err != OK" is true. Returning: ERR_CANT_CREATE
   at: initialize (drivers/d3d12/rendering_device_driver_d3d12.cpp:6670)
ERROR: Failed to initialize driver for device.
   at: (servers/rendering/rendering_device.cpp:5372)

================================================================
CrashHandlerException: Program crashed with signal 11
Engine version: Godot Engine v4.3.stable.official (77dcf97d82cbfe4e4615475fa52ca03da645dbd8)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] error(-1): no debug info in PE/COFF executable
[2] error(-1): no debug info in PE/COFF executable
[3] error(-1): no debug info in PE/COFF executable
[4] error(-1): no debug info in PE/COFF executable
[5] error(-1): no debug info in PE/COFF executable
[6] error(-1): no debug info in PE/COFF executable
[7] error(-1): no debug info in PE/COFF executable
[8] error(-1): no debug info in PE/COFF executable
[9] error(-1): no debug info in PE/COFF executable
[10] error(-1): no debug info in PE/COFF executable
[11] error(-1): no debug info in PE/COFF executable
[12] error(-1): no debug info in PE/COFF executable
[13] error(-1): no debug info in PE/COFF executable
[14] error(-1): no debug info in PE/COFF executable
[15] error(-1): no debug info in PE/COFF executable
[16] error(-1): no debug info in PE/COFF executable
[17] error(-1): no debug info in PE/COFF executable
[18] error(-1): no debug info in PE/COFF executable
[19] error(-1): no debug info in PE/COFF executable
[20] error(-1): no debug info in PE/COFF executable
[21] error(-1): no debug info in PE/COFF executable
[22] error(-1): no debug info in PE/COFF executable
-- END OF BACKTRACE --
================================================================

Steps to reproduce
na
Minimal reproduction project (MRP)
na

It looks like the project manager worked successfully for you, but crashes when running the project, is that right?

yes

WARNING: Your video card drivers seem not to support Vulkan, switching to Direct3D 12.

You are trying to open a project with "Forward+"/"Mobile" renderer which require either Vulkan or DX12, and neither is supported by your GPU. Try switch to "Compatibility" renderer.

Your video card drivers seem not to support the required OpenGL 3.3 version, switching to ANGLE.
Intel HD 2500 supports OpenGL 4 > OpenGL 3.3

OpenGL driver quality on ancient Intel GPU is awful and mostly unusable, so Godot use ANGLE over DX11 instead of OpenGL.

WARNING: Your video card drivers seem not to support Vulkan, switching to Direct3D 12.

You are trying to open a project with "Forward+"/"Mobile" renderer which require either Vulkan or DX12, and neither is supported by your GPU. Try switch to "Compatibility" renderer.

Your video card drivers seem not to support the required OpenGL 3.3 version, switching to ANGLE.
Intel HD 2500 supports OpenGL 4 > OpenGL 3.3

OpenGL driver quality on ancient Intel GPU is awful and mostly unusable, so Godot use ANGLE over DX11 instead of OpenGL.

Yep compatibility indeed worked
but I think HD 2500 has vulkan support? or am I missing something?

I don't think Intel HD 2500 supports Vulkan on Windows (maaaybe on Linux with Mesa, but with very limited support that probably wouldn't work well enough for Godot).
But the logs look like it's falling back to Direct3D 12, and then also failing at that:
WARNING: Your video card drivers seem not to support Vulkan, switching to Direct3D 12.
     at: DisplayServerWindows (platform/windows/display_server_windows.cpp:5985)
ERROR: D3D12CreateDevice failed with error 0x887a0004.
   at: (drivers/d3d12/rendering_device_driver_d3d12.cpp:6302)

I'm not sure Intel HD 2500 supports D3D12.

Thanks a lot of clarifying though. I guess I can just use the compatibility code as I'll be only making 2d games. For 3d games, I think I can utilize my 11th gen laptop?


Physical flow detail: Allow export from App screen

Should the Unused Specifications displayed on this page be also converted into a grid and allow export?


There is lack a feature in newest release version 5.13.1

The problem
In the newest version 5.13.1 there should be added collectionCondition ItemWithText() (provided by https://github.com/selenide/selenide/pull/1194) but there is no code in the jar for it. Maven was used to provide dependency
Details
If necessary, describe the problem you have been experiencing in more detail.
Tell us about your environment

**Selenide Version5.13.1:
Chrome\Firefox\IE Version:
Browser Driver Version:
Selenium Version:
OS Version:

Code To Reproduce Issue [ Good To Have ]
Please remember that with sample code it's easier to reproduce the bug.

@SeleniumTestAB it is in 5.14
see change log https://github.com/selenide/selenide/blob/master/CHANGELOG.md

@SeleniumTestAB it will be released in Selenide 5.14.0

@asolntsev then please update the release notes for 5.13.1. They are misleading

I don't see it. Where exactly do you see the misleading text?


The 'onclose' event handler is not implemented

I've noticed that if you assign an event handler to the dialog's "onclose" property (or attribute), it is not called on dialog close. I think this should be mentioned in the "Limitations" section.
On the other hand, I've made a custom version of the polyfill that supports the "onclose" property (not the attribute). What I've done is to add the following code in the dialogPolyfillInfo.close method:
    close: function(opt_returnValue) {
      ...
      // Call the "onclose" event handler
      if (typeof this.dialog_.onclose == 'function') {
        this.dialog_.onclose({
          type: 'close',
          bubbles: false,
          cancelable: false,
          composed: false,
          defaultPrevented: false,
          isTrusted: true,
          eventPhase: Event.AT_TARGET,
          target: this.dialog_,
          currentTarget: this.dialog_,
          returnValue: this.dialog_.returnValue
        });
      }

      // Triggering "close" event for any attached listeners on the <dialog>.
      ...

Feel free to use this as the starting point for a proper implementation.

This was fixed in #184


Store: only run the debug assertion against recordings (not blueprints)

I'd like to keep that assertion a bit longer, just in case. So for now just ignore blueprints, as they are problematic in that case.

Fixes #8389

In the same vein, the multi-chunk write warning should really be a debug instead.


Reland call state cleanup fix

@veblush

Believe I've fixed the bug, but adding @yashykt to verify.


Update webpack and other dependencies.

Newer versions of webpack and other dependencies don't seem to break anything.

Closing in favor of #11.

@gchallen +<EMAIL_ADDRESS>


Test: use StdlibUnittest in BridgeNonVerbatim

Convert tests in BridgeNonVerbatim.swift to use StdlibUnittest.
Also add a function that compares references in StdlibUnittest.

@swift-ci please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 4e5dbed41a8c6a51158f432f0cb22ecb9114c0cc
Test requested by - @dduan

@swift-ci please test OS X platform

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 4e5dbed41a8c6a51158f432f0cb22ecb9114c0cc
Test requested by - @dduan

@swift-ci please test OS X platform


Update internal docs

Description
This PR brings new internal docs for understanding the Faro internal architecture. This should help new joiners with understanding how Faro works.
Writing new transports and instrumentations docs will be provided in a separate PR.
Checklist

[x] Tests added
[x] Changelog updated
[x] Documentation updated

Updated with changes as per latest comments.


Makes createGlobalState API compatible with React's useState API

Description
This PR makes the createGlobalState function compatible with the React API. This means 2 things:

It allows using a function in setState, as in setState(prevState => prevState + 1)
It allows using a function in the initial state, as in createGlobalState(() => 0)

Also, as a side effect:

It improves the types when the initial value is passed or set as the generic argument, while relying on the React original type for the return (SetStateAction).
It fixes the current tests that were using an incorrect syntax and extends them to the new use cases and types.
Extends docs and fixes a minor grammar issue.

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as before)

Checklist

[x] Read the Contributing Guide
[x] Perform a code self-review
We mobbed this in our team at Spotify.
[x] Comment the code, particularly in hard-to-understand areas
[x] Add documentation
[x] Add hook's story at Storybook
[x] Cover changes with tests
[x] Ensure the test suite passes (yarn test)
[x] Provide 100% tests coverage
[x] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
[x] Make sure types are fine (yarn lint:types).

You better use method provided at src/misc/hookState.ts to have a single state resolution method.

There you go, thanks for the pointer @xobotyi !


Patches for local repository don't work

Describe the bug
While working on https://github.com/xmake-io/xmake-repo/pull/120 I was trying to make a patch for chipmunk2d, and it seems patches don't work for local repositories.
Expected behavior
That patches worked for local repositories as well
Error output
PS C:\Projets\Burgwar\BurgWar> xmake.exe -vD
checking for architecture ... x64
checking for Microsoft Visual Studio (x64) version ... 2019
checkinfo: cannot runv(unzip.exe -v), No such file or directory
finding concurrentqueue from xmake ..
finding libcurl from xmake ..
finding nlohmann_json from xmake ..
finding fmt from xmake ..
finding chipmunk2d from xmake ..
finding chipmunk2d from vcpkg ..
finding chipmunk2d from conan ..
finding chipmunk2d from pkg_config ..
finding chipmunk2d from system ..
finding stackwalker from xmake ..
finding stackwalker from vcpkg ..
finding stackwalker from conan ..
finding stackwalker from pkg_config ..
finding stackwalker from system ..
note: try installing these packages (pass -y to skip confirm)?
in test-repo:
  -> chipmunk2d 7.0.3
please input: y (y/n)
y
error: @programdir\actions\require\impl\actions\patch_sources.lua:84: patch(xmake-repo\packages\c\chipmunk2d\patches\7.0.3\android.patch): not found!

Related Environment
Please provide compiling and running environment information:

xmake version: xmake v2.3.8+202010172345
os: Windows 10 2004
target platform: Windows 10

Additional context
When committing the exact same files I used on my local repository to xmake-repo (see https://github.com/xmake-io/xmake-repo/pull/120/commits/b4fe789776054f4ad13a74462bbcb0ffb1748c48), there was no problem when patching, that's why I think the issue comes from local repositories.

I have fixed this problem. You can update to dev and try it again. xmake update -s dev

I can confirm it's fixed, thank you!


Why is the sass version locked to 1.7.2?

Why is the sass version locked to 1.7.2?
I think it would be beneficial to use never versions. Correct me if I am missing something.
I need the importing of CSS same as @LucaMele in #50
According to the docu of SASS-LANG the sass lib supports this since 1.11.0:
https://sass-lang.com/documentation/at-rules/import#importing-css

This would also allow us to include @use and @forward.
I'll look into making a PR to fix this.

You can use the runtime option to pass the sass implementation that you want. For example, you can install in your project<EMAIL_ADDRESS>and then when using rollup-plugin-sass pass the option:
sass({
  options: {
    runtime: require('sass')
  }
})

This way you can use rollup-plugin-sass with the sass version that your project is using.


Refactor move strategies

This PR involves some refactoring of things in move strategies. It is designed to make it easier to create new move strategies, without breaking any backward compatibility. It also reduces repeated code, and improves code quality (according to CodeClimate score).
One of the main things this introduces are the get_per_mover_ensembles and get_parameters  methods in strategies. Strategies are factories for movers. What the factory needs is to combine the type of mover with the initialization parameters for each mover instance to be created. The get_parameters method returns a list, one entry per mover, containing the parameters to initialize each mover, which makes the make_movers factory function very simple.
In particular, .get_parameters handles things like the idea that some parameters may be given once but repeated for all movers in the strategy (e.g., the engine for shooting movers). On the other hand, parameters may be given as either a single object to be broadcast to all instance or as a per-mover list (such as with shooting point selectors, which can vary depending on the mover).
This PR also involves some simplification by using collections objects, in particular defaultdict. There's a lot of code in OPS where we should be using collections, but aren't!

This is ready for review. In addition to stuff listed above, it also removes some of the path mover factories (the rest should be removed soon, as well, as should our other factory objects). These have been replaced by the move scheme/strategy approach.
It also fixes a problem we've been having in tests, because conda kept trying to upgrade Python from 3.5/6 to 3.7. (Soon we should drop 3.5 and add 3.7 support.)
There's a slight drop in test coverage. This is because I made well-covered code shorter. There are no new uncovered lines, just there are fewer lines overall!

Leaving this up for review for another 2 days. If no review by Saturday night, I'll merge it myself.

A small note: this also adds pytest as a requirement to run the test suite.

A small note: this also adds pytest as a requirement to run the test suite.

Technically, that happened as of #808. However, this might be the first PR with tests that required pytest. Currently we also still require nosetests (for the imports). As discussed in #756, the next stage in upgrading tests is to remove the nosetests import requirements.


slicec-cs Cleanup Pass 2

This PR performs some more cleanup in slicec-cs. No logic or function is altered by this PR, it just cleans and refactors.
It removes 54 lines of code (for a running total of 140 lines).
I'm only opening a PR to make sure CI passes. But if you want to review it, go for it!

I guess I merged just as you finished reviewing :)
It is somewhat of a Rust convention, because Rust lacks a ternary operator, and matching like this is more compact that a full if/else statement.

Neither is more correct than the other. For me, I only use this match convention if the branches are very simple, ie. if I would normally use a ternary operator.
if field.is_tagged() {
    encode_tagged_type
} else {
    encode_type
}

vs
match field.is_tagged() {
    true => encode_tagged_type,
    false => encode_type
}

, because Rust lacks a ternary operator

Rust if is an expression so there is no need for a ternary operator, in C the ternary operator is required because if is an statement.
I very match prefer if for checking true/false because it is more specific, when you see an if you know that is all it is doing.
Whatever we do we should be consistent, a few lines below in the PR we have:
let parameters = if return_type {
        operation.non_streamed_return_members()
    } else {
        operation.non_streamed_parameters()
    };

when you see an if you know that is all it is doing.

I used to be of the same opinion! But over time I've come to see it the other way :)
match bool can only have 2 possibilities.
Right underneath it you'll have an exhaustive list of the two paths it can take. There's no other sane outcome here.
And I can see the single condition being tested, up front, right after the match.
An if statement can invite intermediate checks: if foo {} else if unrelated_thing {} else {},
so there could be more than 2 possible paths. And the conditions being checked can be completely unrelated.
With match, all the branches are indented to the same level, with no break in between.
This makes it easy to see where the check starts and ends:
match thing {
    true => something,
    false => something_else,
}

With if, there's a dedented line in-between, breaking it up.
In the middle of lots of code (like in slicec-cs), this makes it just a little harder to see what's going on.
if thing {
    something
} else {
    something_else
}

You can grep through our repos, we use it in a handful of places in slicec, the language server, and obviously slicec-cs:
true =>|false =>

Or, searching on GitHub: https://github.com/search?q=true+%3D>+language%3ARust&type=code&l=Rust
There's no definitive rule on when to use it, it's just style and preference.
I only use it when the true/false are very short. If the cases need more than one line, I use if/else instead.
I don't have a reason for this. It's just what I've done shrugs.

Despite my small novel:
I don't actually care!
I just wanted to convey what eventually made me switch sides.
If you want to update everything to use if/else, that's genuinely fine by me!
Because I think the most important thing, is that we're consistent.
There's all kinds of things like this in slicec-cs, hence why I've started cleaning it.
I'm just doing the larger refactorings first before going through and looking at what looks weird or inconsistent!


AWS deployments: Add EFS to osparc.io and sim4life.io

          # OPS:

Add EFS to osparc.io and sim4life.io AWS deployments
Originally posted by @matusdrobuliak66 in https://github.com/ITISFoundation/osparc-simcore/issues/6441#issuecomment-2429383200
### Tasks
- [ ] sim4life: https://git.speag.com/oSparc/osparc-ops-deployment-configuration/-/merge_requests/1023
- [ ] nih: https://git.speag.com/oSparc/osparc-ops-deployment-configuration/-/merge_requests/1024

Close once PRs in Task List are merged and applied

it's done ;--)


Update secondary button style in Verify seed phrase screen and a few others

After #3843
List of screens mentioned in https://github.com/AlphaWallet/alpha-wallet-ios/issues/3819#issuecomment-1023288063
Requires ButtonsBar to support a new, vertical layout (or some variant of ButtonsBar that does that since it's unlikely it will ever have more than 2 buttons a vertical configuration)

Original:
@colourfreak could we one for that?

Maybe the same (or different) style for the "Import from iCloud…" button too when importing:

Before we do this, I do consider a global change of the green color. What do you think? @JamesSmartCell @hboon @vladyslav-iosdev @seabornlee @justindg @eviltofu

Before we do this, I do consider a global change of the green color. What do you think? @JamesSmartCell @hboon @vladyslav-iosdev @seabornlee @justindg @eviltofu

Do we have dark and light mode versions of the button colour?

Import with Seed:
https://zpl.io/Z09qdgG
Import with Keystore
https://zpl.io/9qkN9ye
Import with Private Key
https://zpl.io/Dlkp8ng
Backup
https://zpl.io/VxvqDAW

@colourfreak thanks!

Should the primary button be on top? @hboon @colourfreak

Just for this screen, yes. Not generally. Keep this as a separate PR from changing colors?

Just for this screen, yes. Not generally. Keep this as a separate PR from changing colors?

The Color change is in #3838. This is for the follow up #3819

Great. Thanks.


improve the performances

I removed as much useless characters as possible in the source code:

This improve the compilation time by at least 0.2% since the parser now doesn't have to skip these characters
I'm pretty sure it also reduce the size of the final binary
It also improve the readability of the code. Personally I can see way more code on my screen

For  further improvement we could probably merge every files in one single big file.

Easter is over, closing.


improving user experience on installing Clusternet

What would you like to be added:
Why is this needed:

/assign


fix: soft calibration offset

Regarding the polarity of the calibration term - here are some values of the offsets from the BoW test.
Timestamp,Timestamp(utc_s),SerialNumber,OffsetValueDegC
2023-12-25_11:11:11,1600000,398804,-0.03876
2023-12-25_11:11:11,1600000,398804,-0.0590343
2023-01-11_13:15:33/,1673471733.9574752,399504,0.15164988416988404
2023-01-11_13:15:33/,1673471733.9574752,401239,0.09835451737451692

If the TSYS reads higher than the RBR it's being calibrated against, it will read a negative value

Yields the offsets:
{
    "423709": -0.06944950269506993,
    "423398": -0.1281154421201235,
    "423665": -0.11886492877309844,
    "423712": -0.04740188975872664,
    "423764": -0.07272016491273071
}

which we should add back to each reading to get the calibrated reading

Nice find! 🎉


Deathmatch is broken

[x] it redoes player state
[ ] the post countdown event fires again for it, which isn't ideal
[x] player spawns get changed to where they were before the deathmatch
[x] player's sometimes experience super lag when killed in the deathmatch.

This should be fixed as one 1.1.7, except for the countdown event, but that's not really incorrect behavior. Instead there should be more events.
#11


Set User-agent in all CLI requests

It turns out that Cloudflare blocks requests with a user-agent containing “Python-urllib”! (https://github.com/IATI/IATI-Standard-Website/issues/230), but it's ok if the User-agent is set to request.

Not to be Captain Hindsight, but have we asked the Kubernilla team if this is something they can adjust or fix on their end?
It's a great catch, but I feel bad having to mung our code to work around brain damage outside of our perimeter.

I understood it's automatic "feature" that can't be changed on Cloudflare, but now I see it can be adjusted. I could have explicitly asked, my bad.
At least we'll prevent from opening issues here like this https://github.com/IATI/IATI-Standard-Website/issues/230, complaining that Racetrack doesn't work with Cloudflare.

🥓