Resolve CSS import URLs

Original Discussion: https://www.pika.dev/npm/snowpack/discuss/197
/cc @idan, @jan-dh, @FredKSchott, @jwondrusch, @nickolay
Right now, we only resolve import URLs in JS. We should use that same logic on CSS import URLs as well.
// Supported (In any JS file)
import 'antd/dist/antd.css';

// Not Supported (In CSS files)
@import 'antd/dist/antd.css';

To start, we're going to try to implement this without Webpack's ~ operator. That means that Snowpack will never handle @import 'foo/bar.css' as a relative URL, even though the browser would. Relative URLs must be imported via @import './foo/bar.css'.

As @nikolay pointed out, @importis part of the css spec, so no real extra plugin needed.  The postcss-import plugin 's purpose is mostly this:

One of the most useful features preprocessors offer is the ability to organize your CSS into multiple files and combine them at build time by processing @import statements in advance, instead of in the browser.

There's a pretty good section on using with preprocessors in the Tailwindcss docs

In my PR for the documentation I tried to explain what's lacking in the snowpack at the moment: @import 'foo.css' will try to import foo.css in public/. Expected functionality includes:

Importing CSS files relative to the current file
Importing styles from other installed packages (@import 'antd/dist/antd.css'; should import the file in 'node_modules/antd/dist/antd.css')

To piggyback on @jan-dh's comment, while I had been figuring out the issue with TailwindCSS and the pseudo-selector classes using @apply, I had tried using postcss-import.
It didn't solve the issue, but it did work in terms of being able to define root or path in the postcss plugin settings and have the files be read correctly.
I haven't dug into the snowpack source too much to know whether it's a more prudent path to add a setting to snowpack to indicate a root for css @imports or to update the docs.  If it's the latter, I could probably put together a quick PR for that.

Another example that should be fixed as a part of this, if possible (or broken out):
@font-face {
  font-family: 'Framework7 Icons';
  font-style: normal;
  font-weight: 400;
  src: url("../fonts/Framework7Icons-Regular.eot");
  src: url("../fonts/Framework7Icons-Regular.woff2") format("woff2"),
       url("../fonts/Framework7Icons-Regular.woff") format("woff"),
       url("../fonts/Framework7Icons-Regular.ttf") format("truetype");
}

From: https://www.pika.dev/npm/snowpack/discuss/408

docs have been updated, so I think we're safe to close

The docs currently point to this issue, so it definitely shouldn't be closed!
Webpack automatically parses CSS @imports and bundles them together. Since the documentation currently points to this issue as "not yet supported natively", it seems the plan is for snowpack to also do something similar.

Ah, thank you! My issue cleanup was over ambitious :)
We could probably clarify the docs a bit more, but for anyone coming here the current status is:

Snowpack supports @import statements today, so as long as your browser supports them
but, unlike other import statements it's resolved purely by URL in the browser, and not by local file path at build time
If you want to resolve imports at build time, use postcss (see the docs linked above)
Webpack automatically parses and bundles these together today

Update: Cleaned up the docs to make it more clear that Snowpack will match native CSS import syntax by default (where @import "foo/bar.css" === @import "./foo/bar.css") and that imports by package name are supported via a PostCSS plugin.
https://www.snowpack.dev/#css-%40import-support
We also have a PR to add native support for this here: https://github.com/pikapkg/snowpack/pull/803

Are there any working examples of how precisely to set this up. I read that snowpack won't import from node_modules and that people have tried postcss-import without success (my case too)?

Same. I have no idea what any of this means... I just want to import my fonts for my project T_T

I've found this to work
// src/components/Foo.jsx
import './Foo-style.css';
...

// in src/components/Foo-style.css
.is-bar {
  background-image: url('/_dist_/components/Foo/img/bar.svg');
}

But... that seems not ideal. I'd expect to be able to do:
// in src/components/Foo-style.css
.is-bar {
  background-image: url('./img/bar.svg');
}

I've found this to work
// src/components/Foo.jsx
import './Foo-style.css';
...

// in src/components/Foo-style.css
.is-bar {
  background-image: url('/_dist_/components/Foo/img/bar.svg');
}

But... that seems not ideal. I'd expect to be able to do:
// in src/components/Foo-style.css
.is-bar {
  background-image: url('./img/bar.svg');
}

Creating a clean repo using @snowpack/app-template-svelte-typescript I have a similar issue.
In my App.svelte I can do this fine inside the <script> section and it works
import 'xp.css/dist/XP.css';
If I try it as an @import inside my main sass file:
@import "~xp.css/dist/XP.css" can't be resolved
If I do @import "node_modules/xp.css/dist/XP.css" to loads, but it fails to find references such as fonts (which sounds like the same issue @ludwignagelhus is having?)


Migrate to Node 18.X

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

I was using nuxt-security package for nuxt 3 for adding CSP headers and have node 18. It works good on local but while running on azure pipelines it fails stating "[error] Error while requiring module nuxt-security: Error: Cannot find module 'C:/Data/Agent/_work/68/s/nuxt-security'"
If there is some other package which can help us to continue please let me know!
Also how it is working okay on local and not on azure pipelines? if there is some solution please let me know!

Interesting case. Maybe @pi0 will be able to help with that? Is it a known Nitro issue on Azure Pipelines?

Can you please provide more info about your pipelines configuration? Usually you should be able to configure Node.js version for building phase.

Can you please provide more info about your pipelines configuration? Usually you should be able to configure Node.js version for building phase.

I can configure node version in my pipeline but the issue is as node 16 is deprecated, we have many other dependencies too which are also having issue with node 16. So when I try to run it with node 16 it gives other error.
Better it is to make it work with node 18 but the issue is that it works good and install package of nuxt-security with node 18 on local but not on azure pipeline

Ah sorry i thought issue is with using Node 18 in pipelines you are definitely better to use 18 and we will solve any issues if there are 👍🏼
@Baroshem Any reason nuxt-security not supporting Node 18? What is purpose of this issue that you originally created?

Looks like we are also having issues with Node 16 in our own CI pipeline.

Looks like we are also having issues with Node 16 in our own CI pipeline.

Can you please elaborate on the issue which you are facing on your CI pipeline, is it same as I am facing it?

Looks like we are also having issues with Node 16 in our own CI pipeline.

Can you please elaborate on the issue which you are facing on your CI pipeline, is it same as I am facing it?

Our pipeline fails because Nuxt 3.8.2 requires globby 14, which only supports Node 18+
Responsible commit was https://github.com/nuxt/nuxt/commit/94b16be9c93c3219c73c790b92111302ea42bfb6
In short Nuxt 3.8.2+ does not support Node 16 anymore
Upgrading CI to Node 18 solves the issue.
So our issue looks different from yours


Title screen

press any key at first to make player spawn
redo all the art and add  pumpkines ( pumpkin trampolines )
disable retry level on title screen
hide hp
Floating start game
maybe add rain

Related to #20 #21


Add PWMOutputDevice.pulse method

...which simply calls blink with different default arguments

This may seem a bit trivial, but it means you can just do:
from gpiozero import PWMLED
from signal import pause

led = PWMLED(21)
led.pulse()
pause()

Argument-order is exactly the same as the existing PWMOutputDevice.blink method.

Looks good! Could it cope without on_time and off_time though? Mind you, I can imagine cases you might want it to stay on or stay off between pulses. Yeah, that makes sense.
@waveform80 anything you'd change about this?

My only concern about this is API bloat (it adds a method to a base class, and there's already a method which accomplishes its goals, albeit without default parameters). I'll defer to @bennuttall's judgement on where to draw the line on such things though.
It's also worth noting we already limit which methods appear in the concrete API docs (see the method lists in https://raw.githubusercontent.com/RPi-Distro/python-gpiozero/master/docs/api_output.rst) and hence this method wouldn't automatically appear unless added to the PWMLED list (it will automatically appear in the generic classes docs though as they don't limit which methods appear on the assumption that they're "advanced").

Ok I'll think about it.

Hmmm, maybe it would be worth adding pulse() just to the PWMLED class then, rather than the base PWMOutputDevice?
My initial thinking was that pulse() was kind-of-like an analogue-equivalent of the digital blink() method.

To be honest, that could already be written with PWMLED's blink using red.blink(0, 0, 1, 1) out something similar - no need for that while loop :-)

Hmmm, red.pulse() or red.blink(0, 0, 1, 1)... I certainly know which I'd find easier! ;-)

I think if we were to add a pulse method, it should set on_time and off_time to 0 and only allow configuration of fade_in and fade_out, otherwise it's exactly the same as blink, just with default params, the first two of which you'd have to provide anyway, e.g:
led.pulse(0, 0, 2, 2)

or you'd have to use named parameters:
led.pulse(fade_in=2, fade_out=2)

Whereas with in_time and out_time not configurable, it would just be:
led.pulse(2, 2)

If you need to pulse but leave on or off for any amount of time, just use blink.
I was unsure, but I'm warming to the idea now.

Fair enough. I guess the other option would be to re-order the arguments of pulse to pulse(fade_in_time, fade_out_time,  on_time, off_time, n, background) but that's probably just too confusing, so I'm happy to remove the on_time and off_time parameters, and delegate any more advanced usage to the blink method.
What's the consensus about leaving the method in the base PWMOutputDevice class, or moving it to just the PWMLED class?

Yeah definitely confusing.
I'm up for merging with my suggestion thrown in. @waveform80, ok?
May as well leave on PWMOutputDevice.

All sounds good to me (i.e. leave it on PWMOutputDevice, remove on_time, off_time)

Looks like TrafficLights doesn't have pulse. I'll look into it.

Just for fun*, try this with a buzzer:
>>> buzzer = PWMOutputDevice()
>>> buzzer.pulse()

for values of fun = my ears hurt

Looks like TrafficLights doesn't have pulse. I'll look into it.

Yeah, you'll need to add pulse to LEDBoard too. I was going to add that to the PR at the same time as removing on_time and off_time, but you beat me to it ;-)

I like pulse. Makes blink look boring.


Encrypted rootfs release

Gather all tests that were implemented while working on Encrypted rootfs based on TPM

After rebasing changes from this PR are added in https://github.com/Dasharo/open-source-firmware-validation/pull/212


Add Cycles Piano Cover by Symphoniac

Song Name
Cycles Piano Cover
Artist Name
Symphoniac
Source
Youtube
Youtube Link
GUSuy73XnD8
Direct File Link
No response
Song ID
8
Start Offset [ms]
9425
Extra
Created from Auto Nong.
Created for level: 278956

accept


snow ball background

Fixes Issue🛠

Closes #1011
Description👨💻

We aim to enhance the user interface by adding text that is composed of particles. When a user hovers over this text, the particles should scatter, creating a visually engaging effect. This feature will add an interactive and dynamic element to our page.
Type of Change📄

[X] New feature (non-breaking change which adds functionality)

Checklist✅

[X] I am an Open Source contributor
[X] I have performed a self-review of my code
[X] My code follows the style guidelines of this project
[X] I have commented on my code, particularly in hard-to-understand areas

Screenshots/GIF📷

https://github.com/Rakesh9100/Beautiify/assets/113046759/44694f7d-ab6b-46ee-83e6-e2aeecfae608

Delete the files and commits related to Snow Ball Background from this PR, don't create a new PR @Skb08


Fixed websocket handshake failure if server is running on "ws://localhos...

Fixed websocket handshake failure if server is running on "ws://localhost:8080"
below are shown actuall handshake messages:
GET / HTTP/1.1
Upgrade: websocket
Connection: Upgrade
Sec-WebSocket-Key: qA5FUwqKwq7RShm2iMzxew==
Host: localhost:8080
Sec-WebSocket-Origin: http://localhost:8080
Sec-WebSocket-Protocol: wamp.2.json,wamp.2.msgpack
Sec-WebSocket-Version: 13
HTTP/1.1 200 OK
Content-Type: text/html; charset=UTF-8
Content-Length: 117
Wamp RouterThis server provides
a wamp router on path
on investigation noticed that:
URI.create("ws://localhost:8080").getPath() returns empty string
the current code expects it to return "/"

Looks ok from my side! Thanks!


Add Level 1

Basic stuff:

Whiskey comes down
Player can shoot and move
Lives are a thing
Player can die
End of level does something (idk)

Dissolved into other issues


[Router] - Set response code 404 when executing 'RouteNotFound' Route

When a use defined route is not found, the Dispatcher must set 404 status code on the Response object, so the user of the Dispatcher does not need to worry about this.

Resolved.


perf: making render blazing ⚡

⚡

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


TETP-274 | Bug fix for Map not rendering without default values

Description :sparkles:
Map was rendering as gray block due to missing center and zoom values.
Issues :bug:
https://helsinkisolutionoffice.atlassian.net/browse/TETP-274
Testing :alembic:
See that the map works on '/postings' endpoint

API branch is deployed to platta: https://kesaseteli-pr2017.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

YOUTH branch is deployed to platta: https://youth-pr2017.dev.hel.ninja :rocket::rocket::rocket:

EMPLOYER branch is deployed to platta: https://kesaseteli-pr2017.dev.hel.ninja :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://handler-pr2017.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://handler-pr2017.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://kesaseteli-pr2017.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://youth-pr2017.dev.hel.ninja :laughing::tada::tada::tada:


feat: upgrade lru-cache (drops node <6)

There is no changelog I can find. This is just a rewrite. Options appear to be the same.
https://github.com/isaacs/node-lru-cache/commits/master

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Initial size of panes/position of splitbar is not always correct

Sometimes the splitbar is positioned such that the leftmost pane has size zero.
Here is a Plunker showing the issue.  In this case it's combined with Angular bootstrap-ui's tabset and tab tags, but I've seen it without using these (couldn't manage to reproduce that simpler case just now though -- couldn't remember the combination of layout that caused it).
http://plnkr.co/wBoCHdMd3VNPYryE1URy
Notice that the leftmost splitbar is all the way to the left, even though there are min-size and size set for the div.
If you click on the splitbar and move it one pixel to the right, it will snap into place.
Debugging this a bit, it seems that tElement[0].offsetWidth is zero (the parent element's size) for some reason.  I'm not that familiar with how/when layout sets this value.

Closing this, as the initial issue seems to have been fixed.  Using #100 to track the window resizing issue.  Thanks!


[MT] Delete Student Group Functionality

Designed by Fiona - Review with her when complete

Add a delete button to the "Edit Student Group" modal.
Pressing the delete button should pop open the Warning Modal (already exists) to alert user that they are deleting a student group.
Make a DELETE request to student groups if the user presses "Yes" when deleting on the Warning Modal

https://www.figma.com/file/O2igPzMS1fZPzjmOxlo6Mc/TLP-Wireframes?node-id=3868%3A110261

/cib delete-student-group-functionality

Branch 159-delete-student-group-functionality created!


Add GPU-deterministic back-prop for fused softmax/cross-entropy ops

SYSTEM INFORMATION

TensorFlow version (you are using): 2.2.0-rc2
Are you willing to contribute it: Yes (please assign it to me)

CURRENT BEHAVIOR
The back-prop of tf.nn.softmax_cross_entropy_with_logits and tf.nn.sparse_softmax_cross_entropy_with_logits is non-deterministic on GPUs.
WILL THIS CHANGE THE CURRENT API?
No. Assuming the deterministic back-prop kernels are slower than the current non-deterministic ones, then the deterministic operation will be selectable using the preferred mechanism at the time. At the time of writing, that mechanism is to set the environment variable TF_DETERMINISTIC_OPS to "1" or "true".
WHO WILL BENEFIT FROM THIS FEATURE?
Determinism, for both training and inference, is becoming increasingly important as deep learning systems are moved into production, not only because of regulatory requirements of some markets but also, more broadly, because of the massive potential performance advantages of training with determinism; determinism accelerates and facilitates debug, experimentation (including hyper-parameter tuning and active learning), and regression testing.
With TF_DETERMINISTIC_OPS now enabling deterministic functionality of cuDNN convolution, bias addition, max-pooling, and CTC loss, many deep learning models will train deterministically on GPUs. Softmax and cross entropy are both foundational functions in deep learning, and are combined to ensure performance and numerical stability. Enabling these fused ops to function deterministically will enhance the ability for TensorFlow to be used for various production systems.
This current issue comes out of Issue 9 in the tensorflow-determinism project, which is focused on making the SequenceToSequece model of OpenNMT-tf train deterministically.
UNIT TESTS
What follows are essentially production-ready TensorFlow unit tests that currently fail, but that will pass when this feature is implemented correctly. Depending on the implementation, the parameter-space covered by the tests (e.g. "batch" dimensionality) may need to be broadened for coverage. The tests can be seen running (and failing) on TensorFlow version 2.2.0-rc2 in this colab.
import tensorflow as tf
import numpy as np

class DeterministicTest(tf.test.TestCase):

  def _randomInts(self, shape, high, dtype):
    return tf.constant(
        np.random.randint(low=0, high=high, size=shape).astype(dtype))

  def _randomFloats(self, shape, dtype, normalized_rows=False):
    a = (2 * np.random.random_sample(shape) - 1).astype(dtype)

    if normalized_rows:

      def normalize(row):
        return row / row.sum()

      a = np.apply_along_axis(normalize, 1, a)

    return tf.constant(a)

  def _testDeterministicGradients(self, exclusive_labels):
    with self.session(force_gpu=True):
      batch_size = 1024
      classes_count = 1000
      logits_shape = (batch_size, classes_count)
      logits_dtype = np.float32
      logits = self._randomFloats(logits_shape, logits_dtype)
      if exclusive_labels:
        labels_shape = (batch_size)
        labels_dtype = np.int32
        labels = self._randomInts(labels_shape, classes_count, labels_dtype)
      else:
        labels_shape = logits_shape
        labels_dtype = logits_dtype
        labels = self._randomFloats(labels_shape, labels_dtype,
                                    normalized_rows=True)
      output_shape = (batch_size)
      output_dtype = logits_dtype

      def gradients(local_seed):
        np.random.seed(local_seed)
        upstream_gradients = self._randomFloats(output_shape, output_dtype)
        with tf.GradientTape(persistent=True) as tape:
          tape.watch(logits)
          if exclusive_labels:
            tested_op = tf.nn.sparse_softmax_cross_entropy_with_logits
          else:
            tested_op = tf.nn.softmax_cross_entropy_with_logits
          op_output = tested_op(labels=labels, logits=logits)
          gradient_injector_output = op_output * upstream_gradients
        return tape.gradient(gradient_injector_output, logits)

      repeat_count = 5
      for seed in range(repeat_count):
        result_a = gradients(seed)
        result_b = gradients(seed)
        self.assertAllEqual(result_a, result_b)

  def testExclusiveLabelsDeterministicGradients(self):
    self._testDeterministicGradients(exclusive_labels=True)

  def testDistributionLabelsDeterministicGradients(self):
    self._testDeterministicGradients(exclusive_labels=False)

if __name__ == '__main__':
  tf.test.main()

POSSIBLE SOLUTION APPROACHES
The ultimate solution will be to fix this at the CUDA level by creating deterministic kernels that are exactly functionally equivalent to the existing non-deterministic kernels. I'll soon be upstreaming a solution like this for tf.image.resize with method=ResizeMethod.BILINEAR; see PR 39243.
It could also be possible to create a temporary solution at the Python level by combining existing deterministic ops. See deterministic tf.nn.bias_add as an example. Assuming that tf.nn.softmax operates deterministically (I have not tested that), then this could be followed by an arithmetically robust implementation of cross-entropy (e.g. streaming log-sum-exp). There would, of course, be a performance cost (1/2 speed) compared to a fused softmax and cross-entopy.
ASSIGNMENT
I'm willing and able to implement this feature, but I might not be able to get to it for quite a while. I'm happy for someone else to implement it, but please let me know if you start actively working on it (and I will do the same), so that we can avoid duplicating effort.

I just added two sections to my original comment: POSSIBLE SOLUTION APPROACHES and ASSIGNMENT.

Work-around info: use non-fused softmax and cross-entropy. For example, select the activation on the final Dense keras layer to be softmax and then select tf.keras.losses.categorical_crossentropy for the loss function.

@duncanriach Thanks for helping me resolve my issue (yesterday on the tensorflow-determinism repo) that revolved around this very problem.
The (cleanest) CUDA solution approach you outline is probably out of scope for me.
However, I believe I am able (and would be happy to) implement a temporary python-side solution.
Checking some assumptions before jumping out there and starting work on this:

would you be fine with me taking this on?
this would essentially be a special case in the body of tf.nn.softmax_cross_entropy_with_logits and tf.nn.sparse_softmax_cross_entropy_with_logits that becomes active if and only if TF_DETERMINISTIC_OPS environment variable is set?
to work around this, it should be possible to follow what tf.keras does in the non-fused case you mention as workaround above. Seems to come down to computing tf.nn.softmax and then following implementation of tf.keras.backend.categorical_crossentropy(from_logits=False) (lines 4636 - 4641) Does that sound correct? I'll make sure functionality is retained as per the unit tests.

would you be fine with me taking this on?

Absolutely. I expect that you'll do a great job of it.

this would essentially be a special case in the body of tf.nn.softmax_cross_entropy_with_logits and tf.nn.sparse_softmax_cross_entropy_with_logits that is active if and only if TF_DETERMINISTIC_OPS environment variable is set?

Yes, please refer to how I did this for tf.nn.bias_add and follow that patten.

Seems to come down to computing tf.nn.softmax.

I think you can/should just use tf.nn.softmax directly.

and then following implementation of tf.keras.backend.categorical_crossentropy(from_logits=False)

I think you can/should just use tf.keras.losses.categorical_crossentropy(from_logits=False) and tf.keras.losses.sparse_categorical_crossentropy(from_logits=False) directly also. I don't fully remember what the issue with arithmetic robustness was (and the need to consider streaming log-sum-exp). That might only be something to consider when implementing the final CUDA solution.

I'll make sure functionality is retained as per the unit tests.

Please use the test code in my original comment on this issue.
Reference how I organized the determinism tests for tf.nn.bias_add in tensorflow/python/kernel_tests/: the existing test moved into bias_op_base.py and then included in bias_op_test.py and then the deterministic test cases add in bias_op_deterministic_test.py.
You'll need to find the existing op test and where the gradient is tests (sometimes it's in a different file) and then appropriately add in the deterministic tests.
Review the changes in PR 31465, including the change to tensorflow/tools/pip_package/BUILD.

Another option is for you to begin by adding a patch to tensorflow-determinism (applied with tfd.patch()). This could be released almost immediately (in version 0.4) for application to stock TensorFlow 2.2 (and even earlier versions). Then either you or I could take that solution and upstream it into stock TensorFlow for release in version 2.3 or 2.4 (depending on how long the review process takes).
The advantage of this approach is that it allows almost immediate release and utility along with the ability to focus on getting the implementation correct before dealing with the process of getting it correctly integrated into, and released via, stock TensorFlow.

@duncanriach I like the suggested option to start from tensorflow-determinism as it would get this shipped to users at earliest.
I'll start on it there and once we have confidence the fix works upstreaming it should be much more straightforward.
Thanks for the guidance, really appreciate it!

Note that PR 47925, which has been merged and will be present in TensorFlow version 2.6 onwards, causes TensorFlow to throw tf.errors.UnimplementedError when TF_DETERMINISTIC_OPS is set to "true" or "1" (when determinism is expected) and the softmax/cross-entropy ops are used in such a way that truly random noise will be injected into the model's functionality.
This exception-throwing functionality can currently be disabled by setting TF_DISABLE_SPARSE_SOFTMAX_XENT_WITH_LOGITS_OP_DETERMINISM_EXCEPTIONS to "true" or "1" in case you're using a work-around (such as the one described here) that relies on the existing GPU-op functionality being exposed and usable.
This move to implement d9m-unimplemented exception throwing is orchestrated under this determinism RFC.

Note that PR 50070 has been merged and will be present in TF 2.7.  Deterministic functionality for both tf.nn.softmax_cross_entropy_with_logits and tf.nn.sparse_softmax_cross_entropy_with_logits (and the Keras layers that utilize them) can be enabled using tf.config.experimental.enable_deterministic_ops(True).


radarr: <IP_ADDRESS>46 -> <IP_ADDRESS>82

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for radarr is: Usenet/BitTorrent movie downloader
meta.homepage for radarr is: https://radarr.video/
meta.changelog for radarr is: https://github.com/Radarr/Radarr/releases/tag/v<IP_ADDRESS>82
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found <IP_ADDRESS>82 with grep in /nix/store/1almn9fc5rfmh4pk8753m8wa49m4vgbz-radarr-<IP_ADDRESS>82
found <IP_ADDRESS>82 in filename of file in /nix/store/1almn9fc5rfmh4pk8753m8wa49m4vgbz-radarr-<IP_ADDRESS>82

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

radarr

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1almn9fc5rfmh4pk8753m8wa49m4vgbz-radarr-<IP_ADDRESS>82 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A radarr https://github.com/r-ryantm/nixpkgs/archive/e3617db49dedee4c346fe87088dc9816b85d3181.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e3617db49dedee4c346fe87088dc9816b85d3181#radarr

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1almn9fc5rfmh4pk8753m8wa49m4vgbz-radarr-<IP_ADDRESS>82
ls -la /nix/store/1almn9fc5rfmh4pk8753m8wa49m4vgbz-radarr-<IP_ADDRESS>82/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

radarr

Maintainer pings
cc @edwtjo @purcell for testing.

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

1 package built:

radarr


Where to find argv.json?

Where do I find argv.json for vscodium on a linux machine? I'm unable to activate the plugin and am getting the message:
View container 'remote' requires 'enabledApiProposals: ["contribViewsRemote"]' to be added to 'Remote'.

Hi @gothicVI you can Press f1 and run Preferences: Configure Runtime Arguments command, the file is in ~/.vscode-oss/argv.json

Thanks so much! Also thanks for this extension!
Works like a charm so far!


File transfer optimization 1 WSFTP

Is your feature request related to a problem? Please describe.
The current file upload/download is slow, the download and upload progress is unknown, and it is not possible to support resumable transfers, etc.
Describe the solution you'd like
The current file upload and download are slow, the download and upload progress is unknown, and it is not possible to support resumable transfers, etc.
Describe alternatives you've considered
Refer to the WSFTP scheme and modify the file transmission scheme between the app and node nodes
Additional context
Add any other context or screenshots about the feature request here.

Between app <-> nodes, consider Facebook / wdt mode for file transfer
Support breakpoint resume and progress bar display
Suspend the task for now


chore(issues): reduce time for issues to be marked stale and then closed

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[x] Links to related issues (if applicable)
[x] Tests for the changes have been added/updated (if applicable)
[x] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[x] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@maggiehays We may want to communicate this change more widely.
Otherwise, LGTM.

👍 I'll be sure to call it out in our release notes + Slack announcements


tf.global_variables_initializer() throws missing attribute error in Docker container

When running the lab.ipynb with the docker image(udacity/carnd-tensorflow-lab), tf.global_variables_initializer throws missing attribute error. However, replacing it with tf.initialize_all_variables works.
I see that the change was done with the following commit:
update TensorFlow Variable initialization function commit f9c43461a9cd3d671d8ca445b53c9ed5cee237d1
Does that mean the tensorflow version in the docker image is old and does not supports global_variables_initializer?

I've now updated the repo to refer to the Term 1 Starter Kit so that we only need to keep this updated in one place - thanks for the note!


I just dont need navigationcontroller for slide menu

How can i use side menu without using navigationcontroller...  here i need only one button.. how can i deal with this.. i tried for that i need  your confirmation weather it can be done or not..

There's no good reason to avoid a navigation controller. Just embed your controller in the NavigationController and you're done.

@sreeji44 you can embed your UIViewController in UISideMenuNavigationController and just hide navigation bar in viewDidLoad method


Fixed Issue #69

Involve renaming the "resources" directory to "Resources": this is required for the tool to function on Unix-like operating systems, as they have case-sensitive paths (unlike Windows, which doesn't care).
Note, directory renames are known to be particularly prone to causing merge conflicts, hence me not auto-pulling this change; if you have made changes to SlicerCART/src/resources/UI/SlicerCART.ui this is likely to effect you!

This will close #69


Update Ransomware.py

this tool is best

Bhiya shi hai
On Thu, Feb 16, 2023, 12:25 PM AKASH BLACK HAT @.***>
wrote:

Merged #2 https://github.com/akashblackhat/Ransomware.py/pull/2 into
main.
—
Reply to this email directly, view it on GitHub
https://github.com/akashblackhat/Ransomware.py/pull/2#event-8533788024,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A537XQFJP6P7JZLATYEGVBTWXXI53ANCNFSM6AAAAAAU5LHAFY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add ios scheme target

Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change. If you're changing visual properties, consider including before/after screenshots (and runnable code snippets to reproduce them).
Related Issues
#14648
Tests
I added the following tests:
Replace this with a list of the tests that you added as part of this PR. A change in behaviour with no test covering it
will likely get reverted accidentally sooner or later. PRs must include tests for all changed/updated/fixed behaviors. See Test Coverage.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

@izambasiron are you planning to continue working on this?

I need help with applying changes for a real iOS device. Currently this change only works on ios simulator.


Camera streams stop or are very laggy in Home Assistant v2024.11

I have two Reolink cameras in HA ( model CX410 and Reolink video doorbell POE). Until version 2024.10 they worked flawless using RTSPtoWeb-WebRTC.
Now since version  2024.11 camerastreams are very laggy or just stop. I removed the build-in go2rtc integration from the default_config but no luck.
In a second attempt I removed RTSPtoWeb-WebRTC and only ran the build-in go2rtc integration but no luck.
In can’t see any abnormality in the logs.

It's pretty hard to fix something like that without being able to repeat it.
I admit RTSPtoWeb can work with Reolink cameras better than go2rtc.
Reolink cameras are known for their glitchy RTSP protocol.
I wonder if anyone has managed to work with it without glitches.
Need to try it on my glitchy Reolink camera.

Thx voor your reply.
What I don’t understand is that i removed go2rtc from the default_config. So the integration is removed from HA core. But I still get those bad streams. When I go back the the previous version of HA it works as it should be.

If the time bar works (white) in the video player - you are watching an HLS stream. If the bar is off (gray) - you are watching WebRTC.

The time bar is white but according to the RTSPWebRTC-Webrtc integration i'm watching WebRTC.
HLS stream is very laggy but my videostream is fast so i assume i'm watching WebRTC

Time bar for WebRTC always disabled. So you not watching WebRTC.


enable fixture and pip caching

What current issue(s) does this address, or what feature is it adding?
Resolve #510
How did you solve this problem?
enable caching
How did you make sure your solution works?
not, pushing here will tell me if travis agrees
Are there any special changes in the code that we should be aware of?
no
Please check the following, if applicable:

[ ] Did you add any tests?
[ ] Did you run make lint?
[ ] Did you run make test?
[X] Are you making a PR to a feature branch or development rather than master?
[ ] Did you add an entry to CHANGELOG.rst? (if not, please do)

Coverage decreased (-0.006%) to 80.159% when pulling 8d4d2cf588bc3a6023a204159430a52ea3e68e3c on ixje:enable_caching into 5879319c3215ab37153325ff2e5b268746907343 on CityOfZion:master.


Fix scrollToTop blanking

Problem
When scrolling to top using the status bar tap in iOS, we see some blanks even in the top performing devices.
Possible solution
FlatList does not remove the first elements of the screen, this could compromise memory but solve this problem.

Hey!
Any chance that this can be solved? This is the only issue preventing us from migrate to it on iOS

Hey!
Any chance that this can be solved? This is the only issue preventing us from migrate to it on iOS

hi @naqvitalha! is this one planned to be solved?

You can give a unique type to first few items to prevent them from unmounting.
Example:
getItemType={(item, index)=> {
   if(index < 5) { return index + 1; }
}}

Pass this prop to FlashList

I am also experiencing the same and have a hard time resolving this...

I am also wondering how to fix the issue with blank space when scrollToTop is triggered.

In FlatList, I resolved this by providing the getItemLayout prop. I think for this lib, you have to provide the estimatedItemSize .


Request to sync 'dennyreiter/mychevy' repo from upstream

Hi @dennyreiter,
This isn't a critical issue. Wanted to take the time and say thank you for creating this. :)
I installed this integration yesterday, and now leading to timeouts after a day.
The upstream sdague/mychevy@81e8225bc692cf12bfa41b32e9bd07d2d84e7a14 seems to address the same; but dennyreiter/mychevy fork is little behind.
Thanks again!

Interesting, I haven't seen any timeouts, but I'll get this updated.  Thanks!

Hmm, sorry, it's late and I've been working all night. So this is in the mychevy package, not the integration.  My manifest calls for version 2.1.1 to be used, which I think is what is specified in the latest HA release.  What HA version are you running?

I've synced with sdague, but the mychevy repository was just a fork to integrate the gas attributes into the package used by the integration.  The package is included in Home Assistant and should be up to date.


Upgrade actions versions

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


To add CONTRIBUTING_GUIDELINES file.

Describe the bug/feature
It'll help newbies like me to get familiar with the basics of contributing factors. I'll be attaching cheat sheets for every stuffs too.
To Reproduce
Steps to reproduce the behavior:

Expected behavior
It'll be a markdown file with clear, concise, and relevant info.
Logs
If applicable, add logs to help explain your problem (e.g. the error message and/or exception traceback).
Environment (please complete the following information):

OS:
Browser:

Additional context
Add any other context about the problem here.

Describe the bug/feature
It'll help newbies like me to get familiar with the basics of contributing factors. I'll be attaching cheat sheets for every stuffs too.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It'll be a markdown file with clear, concise, and relevant info.
Logs
If applicable, add logs to help explain your problem (e.g. the error message and/or exception traceback).
Environment (please complete the following information):

OS:
Browser:

Additional context
Add any other context about the problem here.

It would be very helpful. I am assigning you this issue. Make sure you complete it in 4 days.

Thanks a lot.
On it boss!!


Low Hashrate.

Hello, I installed the latest firmware on Arduino and connected via i2c to Wemos d1 mini. As a result, they give out a smaller hashrate than via USB. What could be the problem?

Use this https://github.com/vaclavhorejsi/arduino-DuinoCoin instead ricaun´s DuinoCoin library

I've had the same issue. The problem was resolved using code from this link. https://github.com/JK-Rolling/DuinoCoinI2C . The slave code for all boards is the Attiny85 code. I've tried on Arduino Uno and Arduino Pro Mini boards and it works. And I've used vaclavhorejsi's DuinoCoin library files. Hope this helps. It worked for me.


Azure.Storage.Blobs.Models.AccessTier Struct has additional values

Hello!  I'm referencing this doc while developing an application that will upload, download and delete blobs from a container.  I need to make sure I'm implementing sane options so that our applications don't do needless, costly things (such as deleting blobs from the Archive tier before they are old enough to avoid the early deletion charge).  I've needed to familiarize myself with the Azure.Storage.Blobs.Models.AccessTier struct.  The issue I'm having is that the struct has several members (the ones prefixed with P) that are not mentioned in this document, which only covers Hot, Cool and Archive.  I've seen some of these values mentioned when talking about disks, but not blobs.  Are these related to Premium Blobs?  If these values don't apply, as this documentation seems to suggest, then why are they in the struct?  Am I safe simply ignoring them in my use case?

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

ID: 392e90a0-af77-999e-39a1-78f09ffe0d06
Version Independent ID: 411ca9a3-4370-f9ca-f14c-5385e13d9075
Content: Hot, Cool, and Archive access tiers for blob data - Azure Storage
Content Source: articles/storage/blobs/access-tiers-overview.md
Service: storage
Sub-service: blobs
GitHub Login: @tamram
Microsoft Alias: tamram

@ronwarner Thanks for the question! We are investigating and will update you shortly.

@ronwarner Thanks for the feedback! Your feedback has been shared with the content owner for further review.

@ronwarner - the values that begin with P apply to premium page blobs only. If you are using block blobs or append blobs, you can ignore those other values.


Restored to default Laravel .gitignore, and added some customizations

Sorry, but this PR isn't very helpful in its current form. The rules we have have been worked out by people over time to suit how this collection is set up. For example the OS- and editor-specific rules go in Global templates. If you have specific changes you'd like to make, then please explain what needs changing specifically.

I've no idea why the default rules from Laravel was discarded from the current Laravel.gitignore. For example, /vendor should definitely be there, as the directory and its content should be provided via composer install. For reference, CakePHP.gitignore has /vendors and /config.

And apparently Laravel.gitignore hasn't been "worked out by people over time," has its history has only one entry. In other words, I'd insist that the current version is far from complete.

I'm aware of the history of the Laravel template - in fact it's been relatively active. There was once a different template in its place, and then we had separate templates for different versions of Laravel and then the Laravel4 template was renamed to this, which is why the history looks deceptively short.

Right, apologies for missing that.


not an issue : immer does not work with native js types right?

As under the hood, immer uses proxies, I was wondering if it was working with native js types (say number).

Immer only proxies plain objects and arrays.
The following snippet is where that logic lives:
https://github.com/mweststrate/immer/blob/004bb7f4471f3dae3c93ba5f06608de3be06e4e3/src/immer.js#L52-L68

Here are the unit tests for using produce with a primitive base state.
https://github.com/mweststrate/immer/blob/004bb7f4471f3dae3c93ba5f06608de3be06e4e3/__tests__/base.js#L1149-L1171

Side note: There are some minor bugs when calling produce with a base state of certain types. #233

That 's the best answer I ever had in a long time. Thanks


Batch experimental design

Issue #, if available: #35
Description of changes: Adds a batch method specific to experimental design.
I suspect modifying the model in the candidate point calculator is controversial so discussion is welcome. I decided to do this rather than other approaches as in many use cases (pretty much all using GPs) this way is valid.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Updated with feedback from Javier

Codecov Report

Merging #52 into develop will increase coverage by 0.2%.
The diff coverage is 93.33%.

@@            Coverage Diff             @@
##           develop      #52     +/-   ##
==========================================
+ Coverage     81.2%   81.41%   +0.2%
==========================================
  Files           62       63      +1
  Lines         1532     1560     +28
  Branches       154      157      +3
==========================================
+ Hits          1244     1270     +26
- Misses         253      254      +1
- Partials        35       36      +1

Impacted Files
Coverage Δ

emukit/core/optimization/acquisition_optimizer.py
86.36% <ø> (ø)
:arrow_up:

...al_design/model_based/batch_experimental_design.py
100% <100%> (ø)

...tal_design/model_based/experimental_design_loop.py
90.47% <71.42%> (-9.53%)
:arrow_down:

Continue to review full report at Codecov.

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

@javiergonzalezh I can move the GreedyCandidatePointCalculator to core if you think that's a better place?

Updated with Andrei's comments and moved GreedyBatchPointCalculator to core


Add a connect_nonbuilder_signals test.

@piegamesde I'm making this a PR because woab::connect_signal_handler is your addition and I'm not sure how exactly it's supposed to be used. I also want to replace it with a BuilderSingalConnector based syntax to support tag and inhibit and whatever else we'll add to it in the future.
So - is this the correct way to use it? To split the same signal to multiple actors? Or is its purpose to connect to the same actor signals that are not originated in the builder?

The only difference is that I make the call within started and that I'm not restricted to widgets. For widgets, I of course prefer the usual API.
let new = gio::SimpleAction::new("new", None);
woab::connect_signal_handler::<Self, _, _>(&new, "activate", "NewDocument", ctx);
application.add_action(&new);
application.set_accels_for_action("app.new", &["<Primary>N"]);

The make_signal_handler method has to be connected manually to the object. This can be used in the following two edge cases:

One wants to recover from a potential failure
One needs access to the SignalHandlerId. This is required to inhibit or de-register signal handlers later on.

Btw I was planning to make a PR with documentation+tests+examples anyways, the next time I find some time.

Ideally I would like to make this work with BuilderSingalConnector:
let new = gio::SimpleAction::new("new", None);
let save = gio::SimpleAction::new("save", None);
SignalType::connector().route_to(ctx)
    .connect(&new, "activate", "NewDocument")
    .connect(&save, "activate", "SaveDocument");

Because then we can get tagging (is tagging needed for actions? It's still useful for manually connected widgets...) and inhibit (do actions use inhibit?). Tagging is easy:
let new = gio::SimpleAction::new("new", None);
let save = gio::SimpleAction::new("save", None);
SignalType::connector().tag(my_tag).route_to(ctx)
    .connect(&new, "activate", "NewDocument")
    .connect(&save, "activate", "SaveDocument");

But inhibit can get weird - you have to specify the inhibit and match on the signals before the list of connect calls:
let new = gio::SimpleAction::new("new", None);
let save = gio::SimpleAction::new("save", None);
SignalType::connector()
    .inhibit(|signal| match signal {
        NewDocument => gtk::Inhibit(true),
        SaveDocument => gtk::Inhibit(false),
    })
    .route_to(ctx)
    .connect(&new, "activate", "NewDocument")
    .connect(&save, "activate", "SaveDocument");

Of course, since we are connecting each signal separately I could do this instead:
let new = gio::SimpleAction::new("new", None);
let save = gio::SimpleAction::new("save", None);
SignalType::connector().route_to(ctx)
    .connect(&new, "activate", "NewDocument", |_| gtk::Inhibit(true))
    .connect(&save, "activate", "SaveDocument", |_| gtk::Inhibit(false));

But then if you want to actually use the signal you'd have to match again:
let new = gio::SimpleAction::new("new", None);
let save = gio::SimpleAction::new("save", None);
SignalType::connector().route_to(ctx)
    .connect(&new, "activate", "NewDocument", |signal| match signal {
        SignalType::NewDocument(arg1, arg2) => ...,
        _ => panic!("wrong signal type"),

    })
    .connect(&save, "activate", "SaveDocument", |_| gtk::Inhibit(false));

Then again - considering how actions don't use inhibit (since there is no "default" behavior), we should be fine with the original connector().inhibit() syntax.

do actions use inhibit?

I've had a look at it, and as far as I can tell the callbacks don't return anything, so no. I generally like the new syntax, but what I'm worried about is how to access the SignalHandlerId from the connected signal.

How about we let the signal router return the closure, and then you register it yourself in the action?
let new = gio::SimpleAction::new("new", None);
let save = gio::SimpleAction::new("save", None);
let signal_router = SignalType::connector().route_to(ctx);
let new_document_handler_id = new.connect_local("activate", signal_router.handler("NewDocument").unwrap());
let save_document_handler_id = save.connect_local("activate", signal_router.handler("SaveDocument").unwrap());

@piegamesde I changed the test to use actions instead of widgets. Does it seem right now?
Initially I disconnected the signal for action2, but that broke the stream for action1 so I had to change it to block_signal. I think this is because we are using two streams (maybe underneath Actix unites them or something?), and maybe once I change it to the router syntax I suggested it would use a single stream we should be able to disconnect signals.


Feature request: drop abstract from exported references

I imagine most users of this great software export references so they can cite them. For this purpose, the abstract is superfluous takes a lot of space, making it harder to read the .bib file. The abstract also pollutes any version control the file may be under.
Would it be possible to add a checkbox to exclude abstracts from exports, please?

whoops - missed that. Thanks.


API Package distribution

This package should be independent from Laravel.
Anyone who wants to use full or just a part of features should be able to do that.
I would like to split it as following:

Core - package that contains all our core features like Repositories, Traits, Dtos, Basic interface - all that would be required without even single course solution. Using this pack may be also useful to create new laravel project intependent from LMS.
Course - package contains all features of courses and learning - all that will be available with configurable endpoints. Also here we'll have any integrations with Users, that may be assigned to specific course.
Authentication - package used for authentication - if someone wants to have their own auth system, there will be not issue with our solution, but if you want to have users, login, social login, profiles out of the box, that will be available for you.
Discussions - package that may be used for implement forum and all discussions according ANY model (including course, social action ect.)
Rewards - package used for gain and spent points, also for generate certificates and any other rewards that may be required
Plans - package used for plan courses in specific collections. It may be education path, it may be course access levels
Repository - package used for create repositories of contents (User generated content, admin uploaded contents) - may be similar to wordpress media
Marketing - push notifications, emails, ect.
Stats - package for statistics

All those package will have endpoints and Controllers that may be used, and will be enabled by default, but in any case user will be able to create their own solutions simply created by services by DI.
Endpoints will be published and editable outside vendor.


SPK Type 9 Support

I now have an example of spice kernel type 9, SOHO spice kernels available here:
https://soho.nascom.nasa.gov/data/ancillary/orbit/spice/
Are of spice kernel type 9:
https://naif.jpl.nasa.gov/pub/naif/toolkit_docs/FORTRAN/req/spk.html#Type 9: Lagrange Interpolation --- Unequal Time Steps

This looks like a simple extension of type 12/13. Should only require an implementation of a lagrange interpolation function and mostly copy-paste of type 12.


如何设置保存7天的数据量

Issue Description
Do you want to request a feature or report a bug?
如何设置保存7天的数据量
文档上的https://n9e.didiyun.com/zh/docs/operation/tsdb/ 里说的每看懂~~~~

What is the current behavior?
What is the expected behavior?
Context / What is the motivation / use case for changing the behavior?
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context.)

你上报的数据本来就没够2天吧.....

@UlricQin sorry, my mistake


Co-Editing Features

Allow for two coders to edit the same code and in real-time, but separately.

see https://code.visualstudio.com/blogs/2017/11/15/live-share


Fatal error while parsing orders in FullfilmentServer

Following code:
`$service = new Services\FulfillmentService(array(
'credentials' => $credentials,
'authorization' => $userToken
));
$request = new Types\GetOrdersRestRequest();
$request->limit = '1000';
$response = $service->getOrders($request);results in this error message:c:\xampp\php64\php -f updateEbayOrders.php
PHP Catchable fatal error:  Argument 1 passed to DTS\eBaySDK\Fulfillment\Types\OrderFulfillmentStatus::__construct() must be of the type array, string given, called in C:\Users\Besitzer\Documents\eclipse\cli-worker\Classes\DTS\eBaySDK\Types\BaseType.php on line 676 and defined in C:\Users\Besitzer\Documents\eclipse\cli-worker\Classes\DTS\eBaySDK\Fulfillment\Types\OrderFulfillmentStatus.php on line 27
Catchable fatal error: Argument 1 passed to DTS\eBaySDK\Fulfillment\Types\OrderFulfillmentStatus::__construct() must be of the type array, string given, called in C:\Users\Besitzer\Documents\eclipse\cli-worker\Classes\DTS\eBaySDK\Types\BaseType.php on line 676 and defined in C:\Users\Besitzer\Documents\eclipse\cli-worker\Classes\DTS\eBaySDK\Fulfillment\Types\OrderFulfillmentStatus.php on line 27There error is the same for both Windows runtimes I tried: PHP 7.0.6 x86 and PHP 5.6.30 x64. When enabling the debug, the returning JSON looks perfectly normal. I only found 2 different kind of entries for OrderFulfillmentStatus:"orderFulfillmentStatus": "FULFILLED"
"orderFulfillmentStatus": "NOT_STARTED"`
I have downloaded the ZIP installation of the 8.0.0 release.

Is possible for you to provide a copy of the JSON response so that I can look into this issue?

I can't attach the file publicity, since it contains actual live data. Can I someone send that file/text privately?

Understandable. It's OK I can re-create the issue without it. I think I've tracked down the cause to be this line https://github.com/davidtsadler/ebay-sdk-php/blob/master/src/Fulfillment/Types/Order.php#L85
As an ugly hack you may wish to change it to
'type' => 'string'

I think I understand what it's supposed to prevent, but just chaning the file doesn't prevent the error to be thrown. Do I need to run some script or prune some cache before the change takes effect?

You're correct about changing https://github.com/davidtsadler/ebay-sdk-php/blob/master/src/Fulfillment/Types/FulfillmentStartInstruction.php#L41 as well so thanks for spotting that. I'll make sure it gets fixed along with the other fields.
Not sure at the moment about the refund error. Chances are one of the classes is missing the property from it's definition. The problem is that these classes are generated automatically from information provided by eBay. I'll need to check that information to see if it's correct. I have problems in the past when eBay's WSDLs was missing various fields.

Is there any expectation of some soon testable code that can load the FullfillmentService API? I thought I could substitute the API using the SoldList from the TradingService, but it uses shortend (as in cut off by the ! sign) orderIds and calling it OrderLineItemID and it contains the lineItemId not all. Since I having some existing order tables from using Amazon API, I was counting on those fields as useable unique keys.

I'm afraid that I don't have an ETA at the moment. I will try and look at this issue over the next few days. I've been busy in my free time so I haven't been able to devote as much time as I would have liked.

Thanks for answering it. Knowing I have to find something myself is sufficient to know. At least I just stumbled over the getOrders() in der TradingService which does work adapting from the 11-get-my-ebay-selling.php example. It also uses the less troublesome authentification, since those oAuth tokens are seriously underperforming in useability, since it would be hard to daily generate a new one to begin with...

There's a 9.0.0 release that hopefully fixes the issue with the orderFulfillmentStatus and fulfillmentInstructionsType properties.
I'm still looking into why it thinks the refunds property doesn't exists. As far as I can tell from the eBay documentation there is only the one refunds property and the SDK should already be handling it.

The 13.0.0 release now ignores any properties that the SDK is not aware of. This may resolve this issue.


test: update test expectations

@whimboo @juliandescottes I have removed the expectations blocked on the cache behavior but they do not pass yet. Is there anything that has not landed still or is there another issue?

It looks like it is the CSS caching issue as well?

It looks like it is the CSS caching issue as well?

Yes exactly I need to rebase my PR to update the tests, same issue with the stylesheet cache

I am not 100% it is about CSS so I marked them as FAIL with a note to investigate

The coop font one fails because of a race condition, but I think we should fix it in the test? The others are stylesheet issues, I prepared a PR for this at #12709 but it will probably clash with yours


Cleanup, formatting, tests

remove @author
cleanup some formatting
make the Misc test suite run and pass (wasn't running before)
test the mediumint question from issue #37

@srdante do you mind taking a quick look through this?


Module configuration

Currently module configuration is done in a hard coded way. The actual initial input should be able to configure the modules as required for the module.
For this we need metadata from the DBMS to see common ways how different DBMS-s specify the operation parameters. This will be found out in the issue #40.

Done #74


Survey parsing

@ryan-hays I updated survey_scores to be more question-based and updated survey_results as well. Please test them out and if all looks good I'll merge this PR.


[bug] no SetDefault use panic

Not registered globally with SetDefault
Writing it this way would just panic
v, err := query.
		Use(w.data.DB(ctx)).
		User.
		WithContext(ctx).
		Where(query.WebAPI.Nmae.Eq(name), query.WebAPI.Age.Eq(age)).
		First()

query.WebAPI is nil
Is this the expected behaviour, and why can't the query be initialised at the time of generation?
Does direct initialisation have any impact?
Dealing with db and tag I understand that objects can be initialized?

gen demo

gen demo
This is not the result I want, dependency inversion instead of setting global sharing

@songzhibin97 This is expected. And the query can not be initialized at the time of generation, because the configuration of online, test, and local environments are different. Even using different databases, such as testing SQLite and online MYSQL.
The configuration of code generation is generally consistent with the local environment.

@songzhibin97 This is expected. And the query can not be initialized at the time of generation, because the configuration of online, test, and local environments are different. Even using different databases, such as testing SQLite and online MYSQL. The configuration of code generation is generally consistent with the local environment.

I tried to modify him and found that when there is an associated relationship for coupling, is it possible to disconnect according to the context, so that you can enjoy this use even when not using SetDefault

@songzhibin97 This is expected. And the query can not be initialized at the time of generation, because the configuration of online, test, and local environments are different. Even using different databases, such as testing SQLite and online MYSQL. The configuration of code generation is generally consistent with the local environment.

You can read my description, I'm not not giving him the db, I just like to enjoy not pre-registering the global db with SetDefault, but also use the method query.X.eq() normally, instead of the null pointer

@songzhibin97 do not set the WithDefaultQuery mode

There are two correct ways to use it.
1.


Sentinel cannot select db!

Describe the bug
from aioredis.sentinel import Sentinel
sentinel = Sentinel([('localhost', 36380), ('localhost', 36381), ('localhost', 36382)],  sentinel_kwargs={'db': 1})
master = sentinel.master_for('mymaster')
await master.set('Tuffy', 'this is redis')
slave = sentinel.slave_for('mymaster')
print(await slave.get('Tuffy'))

To Reproduce
1.I would like to add a key to redis DB1 .
2.I was able to switch DB for the Sentinel cluster using Another Redis Desktop Manager, but could not select DB for aioredis connection
Expected behavior
aioredis.exceptions.ResponseError: unknown command SELECT, with args beginning with: 1,
Logs/tracebacks
No logs.

Python Version
$ python --version
3.9.12

aioredis Version
$ python -m pip show aioredis
2.0.1

Additional context
No response
Code of Conduct

[X] I agree to follow the aio-libs Code of Conduct

It works for me to use the following code:
from aioredis.sentinel import Sentinel
sentinel = Sentinel([('localhost', 36380), ('localhost', 36381), ('localhost', 36382)],  sentinel_kwargs={'db': 1})
master = sentinel.master_for('mymaster')
await master.execute_command("SELECT", "1")
await master.set('Tuffy', 'this is redis')
slave = sentinel.slave_for('mymaster')
print(await slave.get('Tuffy'))


billing: implement billing services

This PR adds the new services to the go-github client: Billing Services
https://docs.github.com/en/rest/reference/billing
Fixes: https://github.com/google/go-github/issues/1788
/cc @gmlewis

Thank you, @wesleimp !
Merging.


Added Steamworks socket

Uses Steamworks to create P2P connections through Steam socket services.

@Moddingdudes the dependencies folder should be a submodule instead


Contribute our recommended settings as defaults

We have a set of recommended settings that ensure the LSP will have all of its features enabled.
I think we should contribute those as configuration defaults, so that people automatically get the complete experience. And then they can turn off if they don't want something.
Note: let's first double-check that using the configuration default does indeed turn on features like formatOnSave and formatOnType.

Sounds good. Feel free to put up a PR.


Add lockup update to longer duration

add support for migrating lockups from shorter duration(example 7days) to longer duration(14days) without unlocking

Duplicate of #711


configService.get returns string

Issue type:

[ ] question
[x] bug report
[ ] feature request
[ ] documentation issue

nestjs-config version
0.6.3
@nestjs/common+core or other package versions

@nestjs/common: 7.6.11
@nestjs/core: 7.6.11

Excepted behavior
Given the following .env.local file,
KEY1=3000
KEY2=false

When performing this:
const confValue = this.configService.get<number>("KEY1", 5000);

then confValue's type should be a number. At least that's what the get method's signature suggests and that's great.
Actual behavior or outcome (for issue)
However, when doing:
const confValue = this.configService.get<number>("KEY1", 5000);

... then confValue is actually a string, which is confirmed by typeof confValue
... which gets worse when dealing with booleans:
const confValue = this.configService.get<boolean>("KEY2", false);
if (confValue) {
  // truthy expression which always returns true:  if "false" => true
}

Thanks for your help !
Replication/Example
@Module({
  imports: [
    ConfigModule.forRoot({ envFilePath: ['.env.local'], cache: true })
  ],
  controllers: [ ],
  providers: [MyManager],
})
export class AppModule { }

@Injectable()
export class MyManager {

    @Inject()
    private configService: ConfigService;

    public async doStuff(): Promise<void> {
        const confValue1 = this.configService.get<number>("KEY1", 5000);
        const confValue2 = this.configService.get<boolean>("KEY2", false);
    }
}

nestjs-config version
0.6.3

but nestjs-config never had this version. Maybe you're talking about @nestjs/config?
$ npm info nestjs-config versions
[
  '1.0.0',        '1.0.1',        '1.1.0',
  '1.2.0',        '1.2.1',        '1.2.2',
  '1.2.3',        '1.2.4',        '1.2.5',
  '1.2.6',        '1.2.7',        '1.2.8',
  '1.2.9-alpha',  '1.2.9',        '1.3.0',
  '1.3.2',        '1.3.21',       '1.4.0',
  '1.4.1',        '1.4.2',        '1.4.3',
  '1.4.4',        '1.4.5',        '1.4.6',
  '1.4.7',        '1.4.8',        '2.0.0-beta',
  '2.0.0-beta.1', '2.0.0-beta.2', '2.0.0-beta.3'
]


Fix the offset calculation in oi2cr for LR35902

The rows and columns were incorrectly transposed in oi2cr.
The second byte is on the second row, the third byte on the third row and so on.
The seventeenth byte (offset 16) can be found on the first row, but on the second bit position within the column groups.

LGTM, thanks for your contribution!


Where are the 3rd party library installation instructions [jquery]

I was trying beta.28 and I think I got jquery installed just by doing npm install jquery --save.  Today I upgraded to the latest @angular/cli and my app says Cannot find module 'jquery'.  What is the way to get jquery running with the latest version?

https://www.gurustop.net/blog/2016/11/18/3821/jquery-angular2-angularcli-how-to


GraphQL error: failed to update account/script/transaction

Describe the bug
GraphQL error: failed to update account: rpc error: code = Aborted desc = Aborted due to cross-transaction contention. This occurs when multiple transactions attempt to access the same data, requiring Firestore to abort at least one in order to enforce serializability.
https://sentry.io/organizations/dapperlabs/issues/3460085293/?project=6391677
105 events in last 24 hrs by 8 users (717 events in last 30 days)
same error logged in playground-api sentry dashboard (5.3k events in the last 24 hrs by 0? users)
https://sentry.io/organizations/dapperlabs/issues/3459151908/?project=6391677
1.4k events in last 24 hrs by 45 users (37k events in last 30 days)
To Reproduce
Steps to reproduce the behavior:

send multiple script/transaction/account deployment requests at once
autosave script/transaction template on draft update

Expected behavior

transactions do not contend with each other

Additional context

issue may have been addressed in https://github.com/onflow/flow-playground/pull/302
monitor sentry to see if events have reduced

issue addressed in latest release


Optionally enable the ecr credential helper plugin

This allows optionally enabling https://github.com/awslabs/amazon-ecr-credential-helper as mentioned in #676 . This plugin's cache should write to the appropriate home folder and should be shared between builds as it's not in the ephemeral DOCKER_HOME. That's my desired behavior, but I'm not 100% sure that's what everyone would want. I think this has the benefit over the ECR plugin of both maintaining a cache between builds and also working against any ECR repo you have access to without having to pre-populate the appropriate registry IDs. I should note I've had a little bit of trouble with this plugin's interactions with docker-compose, but that was years ago. I believe the docker project has resolved those issues with how it calls credential helpers at this point. This worked with the docker and docker-compose plugins for me in testing.
Overview:

Installs the credential helper no matter the plugin setting. The binary won't do anything when it's not used and it's only 8mb and some change.
Writes an empty {} config.yaml in the temp DOCKER_HOME so it can be modified later by various things if necessary.
Follows the standard

Known issues:
I have almost no Windows knowledge. I'm hoping to get some feedback on this general pattern before attempting to get this working in Windows at well.
I'm not sure if this is better off being made into a more general plugin and then incorporated into this stack via git submodules or not? I opted to bake it right in.
This configuration also precludes any other docker auth, like dockerhub. To make that work it would need to configure the credHelpers object to only work on certain configured ECR URLs. That would probably be best done in a separate plugin that was incorporated and configured via a git submodule? We currently only use ECR as an authenticated repo, so this meets that need.

disclaimer: I'm not super familiar with docker credential stores or helpers, so some of this comment might be naive.
This is great, thanks for starting the discussion. Automatically using the instance credentials when accessing ECR seems like a great usability win.

Installs the credential helper no matter the plugin setting

:+1:

I think this has the benefit over the ECR plugin of both maintaining a cache between builds

Could you describe the caching in more detail? What will be cached across builds, the credentials?

I'm not sure if this is better off being made into a more general plugin and then incorporated into this stack via git submodules or not? I opted to bake it right in.
This configuration also precludes any other docker auth, like dockerhub. To make that work it would need to configure the credHelpers object to only work on certain configured ECR URLs. That would probably be best done in a separate plugin that was incorporated and configured via a git submodule? We currently only use ECR as an authenticated repo, so this meets that need.

Given the new rate limits being imposed on unauthenticated docker hub pulls as of yesterday, I think it'd be a shame to make it impossible to authenticate to docker hub.
I guess that means credHelpers are our best bet, but we'd need a way to specify the specific registries that will use ecr-login :thinking:
I'd want to run this idea by some colleagues before we commit to it, but what if we added a new ENV var to the existing ecr-login plugin that looks something like this: BUILDKITE_PLUGIN_ECR_CREDHELPER_REGISTRIES="aws_account_id1.dkr.ecr.region.amazonaws.com,aws_account_id2.dkr.ecr.region.amazonaws.com"?
That'd be useful for folks who use the ecr plugin directly. For folks using it via the elastic stack though, it'd mean setting the new ENV in an environment hook. Similar to the existing elastic stack docs. It's a shame wild card credHelpers aren't possible (like *.amazonaws.com).
Would that work for your team? I know it doesn't align with this comment :(

I think this has the benefit over the ECR plugin of both maintaining a cache between builds and also working against any ECR repo you have access to without having to pre-populate the appropriate registry IDs


updater: Delete Ubuntu's repository upon bzr errors

By deleting an Ubuntu repository that may be in a bad state,
Clair will eventually be able to perform the update, instead of retrying
naively.
Fixes #169

LGTM

LGTM


Master to Live for index change on Skype.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/docs-conceptual/index.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Keyboard shortcut to open the Source Control panel on the sidebar

Before installing GitLens I used the keyboard shortcut Ctrl+Shift+G to open the Source Control panel on the sidebar, after installing GitLens it seems like it takes over that shortcut.
What's the keyboard shortcut to open the Source Control panel on the sidebar using GitLens?

And just after posting the question found the solution hovering over the Source Control icon on the sidebar: Ctrl+Shift+G G


Examine Ruby memory use

See
https://www.joyfulbikeshedding.com/blog/2019-03-14-what-causes-ruby-memory-bloat.html#is-fragmentation-at-the-ruby-heap-pages-level-the-cause-of-memory-bloating

In the short term, investigate using
MALLOC_ARENA_MAX=2.

The "Joyful Bikeshedding" is, as far as I can tell, the best analysis.  Many people thought it was fragmentation, but with additional analysis, it appears that the real problem is slightly different.
That said, others have also noticed that setting MALLOC_ARENA_MAX=2 is helpful for Ruby:
https://www.speedshop.co/2017/12/04/malloc-doubles-ruby-memory.html
https://github.com/heroku/heroku-buildpack-ruby/issues/751
https://www.mikeperham.com/2018/04/25/taming-rails-memory-bloat/
Experimentation reveals no serious problems in setting this environment variable for our situation.

I continue to monitor.  I see no serious problems.  The memory use is somewhat less - it's not trivial, but it looks like we have a better margin.

I've continued to monitor.  MALLOC_ARENA_MAX=2 is a significant improvement.  Our 7-day average is 53%, and the max is 96% (at over 100% we start swapping).  While swapping doesn't shut us down, a single setting that makes it rare is a good thing.
So I'm closing this issue.  Further improvements would be welcome, but right now we should move on to other things.


es6.js externs for Reflect.construct specifies incorrect type for parameter "argList"

https://github.com/google/closure-compiler/blob/v20190909/externs/es6.js#L1580
/**
 * @param {function(new: ?, ...?)} targetConstructorFn
 * @param {!Array<?>} argList
 * @param {function(new: TARGET, ...?)=} opt_newTargetConstructorFn
 * @return {TARGET}
 * @template TARGET
 * @see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Reflect/construct
 */
Reflect.construct = function(targetConstructorFn, argList, opt_newTargetConstructorFn) {};

The type of the param argList is {!Array<?>} but should be {!IArrayLike<?>}.
A work-around is to use Array.from, but this should be unnecessary. For example
/**
 * @param {function(new: TARGET, ...?)} SuperCtor
 * @param {function(TARGET)} callback
 * @return {function(new: TARGET, ...?)}
 * @template TARGET
 */
function decorate(SuperCtor, callback) {
    return function DerivedCtor() {
        var target = Reflect.construct(SuperCtor, Array.from(arguments), DerivedCtor);
        callback(target);
        return target;
    };
}

Without Array.from the following is emitted by Closure Compiler

WARNING - actual parameter 2 of Reflect.construct does not match formal parameter
found   : Arguments
required: Array<?>
var target = Reflect.construct(SuperCtor, arguments, DerivedCtor);

Ref: https://www.ecma-international.org/ecma-262/6.0/#sec-reflect.construct
Ref: https://www.ecma-international.org/ecma-262/10.0/#sec-reflect.construct

26.1.2 Reflect.construct ( target, argumentsList [ , newTarget ] )
When the construct function is called with arguments target, argumentsList, and newTarget, the following steps are taken:

If IsConstructor(target) is false, throw a TypeError exception.
If newTarget is not present, set newTarget to target.
Else if IsConstructor(newTarget) is false, throw a TypeError exception.
Let args be ? CreateListFromArrayLike(argumentsList).
Return ? Construct(target, args, newTarget).

Internal issue created http://b/141855687

Internal issue created http://b/141855687

Good catch!  Would you like to open a PR for the fix?

Seems like accepting the arguments object is the common failure case here.
How would you feel about allowing only {!Array|!Arguments}?

Allowing only {!Array|!Arguments} would fix my issue; I don't foresee any other use case.


Typo in CASE statement

Thanks for putting together this cheatsheet! 👍

Likely that second WHEN should be a THEN

@dsmdavid Good catch!  Thanks UI updated it.


Jaeger templates: removed agent/collector host:port and UI configurat…

…ion, as the defaults provided by the operator should be used
This PR builds upon https://github.com/Maistra/istio-operator/pull/245 (patch for 1.0) to:

Remove the collector's agent host:port - so the operator will by default use load balanced gRPC
Remove the UI configuration, as this default configuration is provided by the operator, and in the next release we will want to override the docs URL with the productised docs.
Enable the agent image to be overridden as with other images
Enable annotations to be specified on the agent (consistency issue between two templates)

cc @pavolloffay @jpkrohling

Could you please add the jira id to the commit?

@rcernich sorry forgot :)

no worries


Add unit tests and e2e tests for watch

Watch is a continous process so e2e tests for this can be tricky
@tkral recommends the following steps for watch e2e tests

Start watch in a separate process
Make some code change on the watched source
Grep for filesystem events from watch logs
Terminate the process

The UTs can also be tricky as it involves :

files and folders
filesystemnotifier

You could refer to tests written for TestWaitForBuildToFinish for writing unit tests for watch: https://github.com/redhat-developer/odo/blob/master/pkg/occlient/occlient_test.go#L2334


[FEATURE] Adding Readme for each spring-boot-starter integration and also adding the starter to each and every model page in the documentation

Is your feature request related to a problem? Please describe.
It becomes very hard for a complete beginner to read all the documentation especially for a person who needs to complete their project or something within a particular time
Describe the solution you'd like
So to make it easy i think we should be adding the thing that there are spring boot starters and quarkus integrations available for us in each model page
I am requesting/proposing this since i had problems when i first used Langchain4j since I was in the lower version
I had many problems fixing this I fixed it only when i actively participated in the discussions of pull requests
I think any person in a hurry can use it with just the dependency and we can also add the readme file to github or just mention the properties they can choose and what all options they have
Describe alternatives you've considered
Once after adding the dependency code snippet in the model page we can add the parameters and types possible or else we can redirect them to github and add readme to each integration
Additional context
I just wrote my code for the configuration of google gemini ai integration for pull request and thought it would be helpful for newbies or people using just for their projects but not really interested in exploring since i personally faced the problem myself :)

@Suhas-Koheda totally agree, would you like to help us with this? 🙏

@Suhas-Koheda good luck with exams! :)
Yes, documentation is written in markdown, we use Docusaurus.
Documentation files are located here and hosted here: https://docs.langchain4j.dev/
Once the documentation is updated, https://github.com/langchain4j/langchain4j/actions/workflows/docs.yaml can be run to publish new docu version on https://docs.langchain4j.dev/
We can start with adding "Spring Boot Starter" sections to every documentaiton page of an integration that has SB starter implemented. As you suggested, it should contain a maven dependency of the SB starter, supported properties and an example of using it.

@Suhas-Koheda thanks a lot in advance! I've assigned you.
Happy Monday as well :)

@Suhas-Koheda - let's get your PR in the spring-boot repo updated and then we can build the doc for it

Yeah sure!


[WIP] Add benchmark scaffolding

Per https://github.com/mapbox/node-cpp-skel/issues/25

[x] Add single run test
[x] Add batch run test
[x] Try out process.memoryUsage(). Thinking about what info is useful here
[x] Add sleep option for mocking when threads are busy, but aren't doing much work
[x] Add more heavy-duty benchmarks per https://github.com/mapbox/node-cpp-skel/issues/30#issuecomment-253306888

Per chat with @springmeyer:

Can we write a test that proves memory optimization?
node module-ify @springmeyer 's libnew lib for tracking of memory allocations
Document how to profile (using Activity Monitor). The skel isn't doing heavy operations, but might be possible to profile during batch bench run.

cc @mapsam @springmeyer

Current coverage is 98.73% (diff: 100%)

Merging #29 into master will not change coverage

@@             master        #29   diff @@
==========================================
  Files             2          2
  Lines            79         79
  Methods          13         13
  Messages          0          0
  Branches          0          0
==========================================
  Hits             78         78
  Misses            1          1
  Partials          0          0

Powered by Codecov. Last update b4051a4...a3cd6ba

@GretaCB https://github.com/mapbox/node-cpp-skel/pull/29/commits/cf913b8adde27d14531644ce4d9b8961b408ffc9 adds a very expensive usage of std::map (because it invokes lots of memory allocation internally in the map, searching of the map, and string comparisons). Now with:
~/projects/node-cpp-skel[bench]$ time node test/bench/bench-batch.js  --iterations 10 --concurrency 10

real	0m3.491s
user	0m11.704s
sys	0m0.535s

I get my CPU usage spiking to > 500%. Running node test/bench/bench-batch.js  --iterations 100 --concurrency 10 to keep it going long enough to easily attach in activity monitor gives a callstack 98% idle in the main event loop (as expected if the threads are doing all the work) and with 99.9-100% of the threads reporting busy doing work (:tada:):

per chat with @GretaCB - next I'm going to take a look at profiling and tuning a few things in the PR. In particular I'll look at the impl of the mutex lock and make sure there is enough work being done in the async function that locks the global such that we are properly demonstrating (e.g. providing an example you can profile) the kind of thread contention programmers should avoid.

In particular I'll look at the impl of the mutex lock and make sure there is enough work being done in the async function that locks the global such that we are properly demonstrating (e.g. providing an example you can profile) the kind of thread contention programmers should avoid.

Done in https://github.com/mapbox/node-cpp-skel/commit/fb1fca8ee7ddfe6660fb6147dfa8f1bb955500a5. Now the contentiousThreads demo is properly awful. It can be tested like:
node test/bench/bench-batch.js --iterations 50 --concurrency 10 --mode contentiousThreads
Benchmark speed: 15 runs/s (runs:50 ms:3245 )
Benchmark iterations: 50 concurrency: 10 mode: contentiousThreads

If you bump up --iterations to 500 and profile in Activity Monitor.app you'll see the main loop is idle. This is expected because it is only dispatching work to the threads. The threads however are all busy in psynch_mutexwait (waiting for a locked mutex) as more time is spent waiting than doing the expensive work. This is because one thread will grab a lock, do work, all others will wait, another will grab the released lock, do work, all other threads will wait. This is all too common and the reason you don't want to use mutex locks. This is the profiling output of this non-ideal situation:

When locks are unavoidable in real-world applications, we would hope that the % of time spent in psynch_mutexwait would be very small rather than very big. The real-world optimization would be to either rewrite the code to avoid needing locks or at least to rewrite the code to hold onto a lock for less time (scope the lock more).

Just looked back at this branch. It's got some great stuff that I think we should merge soon and keep iterating on. My one reservation before merging I'm slightly uncomfortable with how we are mixing best practice/simple/hello-world style code with new code demonstrating both advanced and non-ideal scenarios. I think we should split things apart before merging such that:

src/hello_world.hpp and src/hello_world.cpp contain only simple hello world style code: only binding a single standalone function (this is what you would copy if you just want to start writing a module fast and use the skel as a base)
src/async_<name>.hpp and ``src/async_.cppandsrc/async_.readme.md` that demonstrate common async scenarios in code and have a readme talking about what about them to care about them (good and bad). (This is what you'd profile, and poke at within skel, to learn about the nuances of node async performance).

@GretaCB I just returned here to reflect on next steps. I feel like a good approach would be to split this work into 2 phases:
phase 1
Land a first PR that:

[ ] Adds a ./bench folder
[ ] Adds two benchmark scripts to cover the two performance focused functions currently in master:

[ ] ./bench/hello_async.bench.js
[ ] ./bench/hello_object_async.test.js

[ ] These scripts could be based on a simplified version of the test/bench/bench-batch.js currently in this PR
[ ]  Very simple docs added to the README on how to run the benchmark and a comment that it is not realworld yet since the code does not do much, but that the idea is for developers using skel to adapt it and run it to monitor the performance of the code they add.

^^ this gets the key structure in place to make it easy and fast to start benchmarks for any module that uses skel. This is a great first step.
phase 2
We could revisit adding examples of performance scenarios. However I feel like this is a really advanced topic most suitable outside of node-cpp-skel. The skel is complex enough currently without diving deep on performance. But given performance is critical it would be great to cover it and benefit from the skel structure. So, here is an idea. Instead of building into the skel directly, we could:

Fork skel, and remove lots of unneeded code and docs (like the sync examples)
Add back key async performance scenarios
Add docs for this
Then link to this fork as an example of a skel implementation
The fork would be a separate "performance deep dive example using node-cpp-skel"

@GretaCB  now that Phase 1 is done in #61 - how about closing this ticket? Phase 2 remains but I feel like my idea is not concrete enough to warrant a ticket. I'm feeling really good with what we have and don't see a major need to ticket more work here. Rather we'll apply node-cpp-skel, learn perf issues, and then - at that time - have ideas of things to build back, or add to the docs.

Closing this. What we have are:

Benchmark scripts: https://github.com/mapbox/node-cpp-skel/tree/master/bench
Benchmarking docs: https://github.com/mapbox/node-cpp-skel/blob/master/docs/benchmarking.md
Future performance questions to answer like #143


use charmed-kubeflow-workflows/build_and_publish_rock.yaml in CI

Merging this PR without review because new workflows cannot be tested until a version of that workflow is in main.  This CI and repo are not yet in production use so mistakes wont have severe consequences.  This will have a final review later before it is used in production


Yaml written by ImageUpdateAutomation cannot be reconciled when using variables

I have a deployment with an image that I want to be updated automatically. Everything works when I use a flat yaml file (no variables, everything explicit). The new images get recognized and the file is overwritten to reflect the new tag.
But when I start using variables in the file after one image update the file can no longer be reconciled because the format seems to be wrong.
Note:
.Values.name = qa
Deployment file:
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: frontend
    namespace: {{ .Values.name }}
  name: frontend
spec:
  replicas: 1
  selector:
    matchLabels:
      app: frontend
  template:
    metadata:
      labels:
        app: frontend
    spec:
      containers:
      - image: registry.local/gui/gui:0.0.1-1690901017 # {"$imagepolicy": "qa:frontend-policy"}
        imagePullPolicy: Always

Deployment file after update:
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: frontend
    namespace: {? {.Values.name: ''} : ''}
  name: frontend
spec:
  replicas: 1
  selector:
    matchLabels:
      app: frontend
  template:
    metadata:
      labels:
        app: frontend
    spec:
      containers:
      - image: registry.local/gui/gui:0.0.1-1690902238 # {"$imagepolicy": "qa:frontend-policy"}
        imagePullPolicy: Always

Policy:
apiVersion: image.toolkit.fluxcd.io/v1beta2
kind: ImagePolicy
metadata:
  name:  frontend-policy
  namespace: {{ .Values.name }}
spec:
  imageRepositoryRef:
    name: frontend-repo
    namespace: {{ .Values.name }}
  filterTags:
    pattern: '^[0-9\.]+-(?P<ts>[0-9]+)'
    extract: '$ts'
  policy:
    numerical:
      order: asc

Repo:
apiVersion: image.toolkit.fluxcd.io/v1beta2
kind: ImageRepository
metadata:
  name: frontend-repo
  namespace: {{ .Values.name }}
spec:
  image: registry.local/gui/gui
  interval: 5m
  secretRef:
    name: proxyregsecret

Flux the errors with "converting yaml to json values".
Any ideas? I still want to use variables in my yaml files.

Flux doesn't handle templates in manifests like namespace: {{ .Values.name }}. This looks like Helm templates so what you would need to do is wrap these manifests in a Helm chart.

So we worked around it by putting the image and version number in a value.yml of the Helm chart and referencing the Helm chart. Structure as in the docs:
├── src
└── chart
    ├── templates
    ├── values.yaml
    └── values-prod.yaml

Is that an acceptable way to do it? If yes, I would close this ticket.

The marker should go on the HelmRelease, example here https://fluxcd.io/flux/guides/image-update/#configure-image-update-for-custom-resources

We referenced the value file like this:
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  ...
spec:
  chart:
    spec:
      chart: somechart
      sourceRef:
        kind: GitRepository
        name: flux-system
      valuesFiles:
      - someChartDir/values.yaml
      reconcileStrategy: Revision
  upgrade:
    cleanupOnFail: true
  interval: 10m0s
{{- end }}

Is that also ok?

Aparently. Thanks for the answers!


Gemini-pro from openrouter have context length of 91k but getting error

openai.BadRequestError: Error code: 400 - {'error': {'message': "This model's maximum context length is 8192 tokens, however you requested 8977 tokens (8977 in your prompt; 0 for the completion). Please reduce your prompt; or completion length.", 'type': 'invalid_request_error', 'param': None, 'code': None}}
I am using routellm _ openrouter and this is the error I am getting when using google's gemini pro

Hi there! So this is caused by the OpenAI embedding call, which unfortunately has a maximum context length - I would suggest using the bert model instead, which doesn't require an embedding call.


API issue.

Currently setup for ETC. On the hourly stats the poolHashRate seems to be incorrect when it hits 300 million.
{
  "stats": [
    {
      "poolHashRate": 0.0,
      "connectedMiners": 0,
      "created": "2017-10-30T02:00:00"
    },
    {
      "poolHashRate": 0.0,
      "connectedMiners": 1,
      "created": "2017-10-30T03:00:00"
    },
    {
      "poolHashRate": 0.0,
      "connectedMiners": 1,
      "created": "2017-10-30T04:00:00"
    },
    {
      "poolHashRate": 0.0,
      "connectedMiners": 1,
      "created": "2017-10-30T05:00:00"
    },
    {
      "poolHashRate": 210937280.0,
      "connectedMiners": 2,
      "created": "2017-10-30T06:00:00"
    },
    {
      "poolHashRate": 252204576.0,
      "connectedMiners": 2,
      "created": "2017-10-30T07:00:00"
    },
    {
      "poolHashRate": 267447680.0,
      "connectedMiners": 2,
      "created": "2017-10-30T08:00:00"
    },
    {
      "poolHashRate": 269532768.0,
      "connectedMiners": 2,
      "created": "2017-10-30T09:00:00"
    },
    {
      "poolHashRate": 257787168.0,
      "connectedMiners": 2,
      "created": "2017-10-30T10:00:00"
    },
    {
      "poolHashRate": 231941776.0,
      "connectedMiners": 2,
      "created": "2017-10-30T11:00:00"
    },
    {
      "poolHashRate": 268492480.0,
      "connectedMiners": 2,
      "created": "2017-10-30T12:00:00"
    },
    {
      "poolHashRate": 264365072.0,
      "connectedMiners": 2,
      "created": "2017-10-30T13:00:00"
    },
    {
      "poolHashRate": 259825152.0,
      "connectedMiners": 2,
      "created": "2017-10-30T14:00:00"
    },
    {
      "poolHashRate": 2.692994E+08,
      "connectedMiners": 2,
      "created": "2017-10-30T15:00:00"
    },
    {
      "poolHashRate": 295922240.0,
      "connectedMiners": 2,
      "created": "2017-10-30T16:00:00"
    },
    {
      "poolHashRate": 2.680819E+08,
      "connectedMiners": 2,
      "created": "2017-10-30T17:00:00"
    },
    {
      "poolHashRate": 2.891924E+08,
      "connectedMiners": 2,
      "created": "2017-10-30T18:00:00"
    }
  ]
}

It does show correct in the pools output:
 "donationsPercent": 0.1,
      "poolStats": {
        "connectedMiners": 2,
        "poolHashRate": 311678850

Also why are the miner specific stats ascending and the all the other output is descending times?
Miner stats:
      "poolId": "etc1",
      "miner": "0x24a0dc797d584f13b92ffcee41449b0f4e6427e6",
      "hashrate": 311678850,
      "workerHashrates": {
        "ferrari": 256070373,
        "lambo": 55608478
      },
      "created": "2017-10-30T18:20:00.0171145Z"
    },
    {
      "poolId": "etc1",
      "miner": "0x24a0dc797d584f13b92ffcee41449b0f4e6427e6",
      "hashrate": 255308473,
      "workerHashrates": {
        "lambo": 43238294,
        "ferrari": 212070179
      },
      "created": "2017-10-30T18:10:00.0135562Z"

Hourly stats:
  "stats": [
    {
      "poolHashRate": 0.0,
      "connectedMiners": 0,
      "created": "2017-10-30T02:00:00"
    },
    {
      "poolHashRate": 0.0,
      "connectedMiners": 1,
      "created": "2017-10-30T03:00:00"

The hashrate values over 300M are not a bug. The values are simply represented in scientific notation which is perfectly legal in JSON and accepted by all compliant parsers.


Show doubles as doubles even if the decimal part is zero.

Does this issue occur when all extensions are disabled?: Yes

Version: 1.84.2 (user setup)
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:51:52.184Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Steps to Reproduce:
Add $double = 10.0 to watch.
Seriously I was wondering why the heck is_int($foo) was returning false when the watch was clearly showing that $foo was 13.

If the variable is a double just show the decimal part.

This is up to the debug extension, please file on whichever debug extension you're using


feat: Generate Google.Cloud.CloudControlsPartner.V1Beta

This does not publish the library yet, as the documentation is not available.
PiperOrigin-RevId: 609026905

(Oh, sorry, I merged this as if it was from Owlbot)

Fine by me :)


Some modifications - mostly refactoring.

The first commit implements the comments I've made on https://github.com/xenserver/xenadmin/pull/2926, the other two are some additional tidy up since I was in the area. Commits best reviewed separately.

Hmm, ok I'll move the tail commits to a master PR.

Moved extra commits to https://github.com/xenserver/xenadmin/pull/2931