text:
two concurrent video feeds, mask rendering degrades and almost stops after 10 min..

over about 10-15minutes, the masking (with landmarks, no points) of my two concurrent, different video feeds goes from immediately reactive to slower and slower to the point it barely reacts. I've included two snippets of the performance (10 sec clip or so). It looks like getImageData ( think within extractFaces?) starts to drag from under 50ms to over 250ms. This happens on both a Mac laptop and a Mac iphone x. Any thoughts/ideas for how to address?
-my canvas is 435x256 and the method containing the draw function is invoked asynchronously
-my video is hidden, and is 640x480
if (canvasOverlayBuff && canvasOverlayBuff.width > 0) {
      canvasOverlayBuff.width = 435;
      canvasOverlayBuff.height = 256;

      const drawObj = new self.window.faceapi.draw.DrawFaceLandmarks(
        lastLandmarks[`${mode}Video${pId}`]?.landmarks,
        {
          drawLines: true,
          drawPoints: false,
        }
      ).draw(canvasOverlayBuff);
      console.log("faces drawn ");

I figured out my issue(s). 1. I was invoking setTimeout multiple times within useEffect. 2. I wasn't clearing the Timeout
fix use setInterval, store the id in state, and clear it == AWESOME performance
here's the code if this helps others:
let [intervalId, setIntervalId] = useState(null);

  useEffect(() => {
    if (participants) {
      if (!intervalId) {
        intervalId = setInterval(function () {
          pullAndPostFrameTimer(mode, anonymousParticipants);
        }, 100);  // now that I'm using setInterval, and correctly,  I can really knock this render number way down
      }
    }
    return function cleanup() {
      clearInterval(intervalId);
    };
  }),
    [participants];
  return <div />;


text:
Uncaught (in promise) Error: toNetInput - expected media to be of type HTMLVideoElement

Hi, my name is Ezequiel and I am a student therefore I am new to programming. I am trying to make a system with face-api that recognizes a face on the webcam and compares it with that of an image. But when I try to print by console const detections = await faceapi.detectSingleFace(video.current) it returns the following result:

My code:
import React from 'react';
import * as faceapi from 'face-api.js';
import {useRef, useEffect} from 'react';

function IdBiometrica(){

  const video = useRef()

  useEffect(() => {
    const getUserMedia = async () => {
      try {
        const stream = await navigator.mediaDevices.getUserMedia({video: true});
        video.current.srcObject = stream;
      } catch (err) {
        console.log(err);
      }
    };
    getUserMedia();
  }, []);

  Promise.all([
    faceapi.nets.ssdMobilenetv1.loadFromUri('/models'),
    faceapi.nets.tinyFaceDetector.loadFromUri('/models'),
    faceapi.nets.faceRecognitionNet.loadFromUri('/models'),
    faceapi.nets.faceLandmark68Net.loadFromUri('/models')

  ]).then(recognition())

  function recognition(){
    setInterval(async () => {
      const detections = await faceapi.detectSingleFace(video.current)
      console.log(detections)
    }, 10000)
  }
      return(
        <div>
          <video ref={video} id='video' width="480" height="240" autoPlay={true} muted></video>
        </div>
      )
  }

  export default IdBiometrica

This is an app component created with Create-React-App.
I don't understand why throw an error but after throwing a correct result.
Does anyone have any idea of what the problem is?
Thanks for help!

Following the API documentation, the detectSingleFace method is expecting a TMediaElement type. I have the same issue by using react-webcam and capturing the reference of the component with useRef.
https://justadudewhohacks.github.io/face-api.js/docs/globals.html#tmediaelement
You might consider to use a DOM query selector just like the example in the High Level Api section of the face-api readme.
https://github.com/justadudewhohacks/face-api.js/#high-level-api

source: gharchive/issue

authors: eze-villegas randy-aguirre

license: MIT

license_type: permissive

license_source: github-api


text:
Stable

Doneness:

[X] Build is okay - I made sure that this change is building successfully.
[X] No Bugs - I made sure that this change is working properly as expected. It doesn't have any bugs that you are aware of.
[X] Branching - If this is not a hotfix, I am making this request against develop branch

:white_check_mark: Build Titanium-Web-Proxy 3.0.212 completed (commit https://github.com/justcoding121/Titanium-Web-Proxy/commit/5b7a8f43c5 by @honfika)

source: gharchive/pull-request

license: mit

license_source: bigquery


text:
feat(pie-input): DSW-0 Proof of Concept - IGNORE

Proof of concepts for using content slots and assistive text in pie-input
Assistive Text props
<pie-input assistiveText="Some informative text"></pie-input>

<pie-input
    assistiveText="Please enter a value with 4-8 characters"
    assistiveTextState="error">
</pie-input>

<pie-input
    assistiveText="A success message!"
    assistiveTextState="success">
</pie-input>

Content slots
<pie-input>
    <icon-search slot="leading"></icon-search>
    <icon-calendar slot="trailing"></icon-calendar>
</pie-input>

<pie-input>
    $
    <icon-calendar slot="trailing"></icon-calendar>
</pie-input>

Combination of assistive text and content slots
<pie-input
    assistiveText="Please enter a value with 4-8 characters"
    assistiveTextState="error">
    <icon-search slot="leading"></icon-search>
    <icon-calendar slot="trailing"></icon-calendar>
</pie-input>

/snapit

/snapit

/snapit

repo: justeattakeaway/pie


text:
🛑 qBittorrent is down

In 8eca7d1, qBittorrent (https://bt.justforlxz.com) was down:

HTTP code: 530
Response time: 121 ms

Resolved: qBittorrent is back up in 93eda73 after 18 minutes.


text:
Feature/better types

Refactor the codebase to get better types flowing throughout, and add lint check to the CI for making sure mypy is satisfied.
Changes

[x] Add helpful error when using GCS paths without GCS libraries installed
[x] Fix issue where GCS would print a client error immediately when importing Pathy
[x] Autoformat and Lint check the codebase (sh tools/lint.sh / sh tools/format.sh)
[x] Simplify GCS/File bucket client type names (e.g. ClientBucketGCS -> BucketGCS, ClientBlobFS -> BlobFS)
[x] Consolidate the base pathy code in base.py removing api.py and client.py (needed to avoid circular imports)

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

repo: justindujardin/pathy


text:
Rails 4.2 deprecation on column_for

Similar to #1080, but I was advised to open a new issue. I'm using:

Rails 4.2.0.rc3
Formtastic 3.1.2

Formtastic is not explicitly configured, but is only used by ActiveAdmin (git HEAD, the beta of 1.0; revision f51d96dddb).
When I run my RSpec suite, I see the following deprecation warning (five or six times):

DEPRECATION WARNING: #column_for_attribute will return a null object for non-existent columns in Rails 5. Use #has_attribute? if you need to check for an attribute's existence. (called from maxlength at /usr/local/Cellar/rbenv/0.4.0/versions/2.1.5/lib/ruby/gems/2.1.0/gems/formtastic-3.1.2/lib/formtastic/inputs/base/stringish.rb:27)

It looks to me like the trouble is at lib/formtastic/inputs/base/database.rb, line 7, where there's a call to the column_for_attribute method that's not wrapped in ActiveSupport::Deprecation.silence.

Just pushed new gem 3.1.3 with this patch in it FYI

Great, thanks so much!

authors: cpence justinfrench

repo: justinfrench/formtastic


text:
Add JustList: Salvadorcoin

JustList URL: https://salvadorcoin.org/Salvadorcoin.json
JustList Name: Salvadorcoin
Link to the official homepage of the JustList manager: https://salvadorcoin.org

Sorry, your issue will be closed as you did not submit your information in the correct format.

authors: jeffwami salvadorcoin

repo: justswaporg/justlists


text:
添加JustList: {JustList name}

提交之前请删除下面的话:
如果您没按照要求提交正确的JustList样式，您的issue将会被删除
您提交的JustList json格式必须满足下面链接中定义的例子格式
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
检查清单

[ ] 我已知晓此issue不是提交token而是提交JustList
[ ] 我已经测试粘贴JustList URL到justswap.org的添加列表中并能够正常展示.
[ ] 我已知晓提交的issue不能确保通过并且提交的JustList不确保能在jsutlists网站中显示.

请提供以下的信息
JustList的json URL必须以HTTPS开头.
JustList URL:
JustList 名称:
JustList 提交者的网站或主页:

Sorry, your issue will be closed as you did not submit your information in the correct format.Please resubmit.


text:
Add+JustList:+{JustList+name}

Before submission deletes this line:
THIS IS NOT A TOKEN LISTING REQUEST FORM. IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/blob/main/example.justlists.ts
Checklist

[ ] I understand that this is not the place to request a token listing.
[ ] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[ ] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

Please submit the correct information, invalid information will cause the issue to close


text:
SemanticPass: Call sa_MemberExpression in sa_CallExpression

This is basically the same thing as #561, just for MemberExpression. This concludes refactoring of sa_CallExpression, which now doesn’t contain various symbol-manipulating and symbol-checking code that doesn’t belong there and relies fully on sa_Variable and sa_MemberExpression to handle this.
A nice side effect of the change is fixing several incorrect error messages.
Part of work on #419.

@bkutil
The tests fail because of insufficient coverage, will figure out what to do with that (but it’s strange, this is refactoring and it removes lines).

Rebased to fix a small conflict, tests magically went green.
@bkutil, could you have a look?

+1

Fixed the commit message, will merge on green.

authors: bkutil dmajda

repo: juttle/juttle


text:
🛑 SALUD SOCIAL is down

In e6abb94, SALUD SOCIAL (https://saludsocial.tonoip.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SALUD SOCIAL is back up in 966537b.

repo: jveyes/upptime


text:
🛑 TITO API - QA is down

In c6cc46c, TITO API - QA (https://api-qa.titoapp.org/ping) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TITO API - QA is back up in 04b8250.

repo: jvillenaVS/tito


text:
Getting " One or more errors occurred" while opening GUI

Expected Behavior
Ui should have been loaded
Current Behavior

Steps to Reproduce (for bugs)
Your Environment

Module version used:2.1.5
Operating System and PowerShell version:Windows 10 / 7

Same error here, this time on both Windows and Linux Docker.

Same error here as well, using Windows.

Hey, wanted to chime in again and say that I got this error again. I was able to fix it without reinstalling by setting the theme to "light" in the jvSettings.json settings file. For some reason it was set to null. I'm assuming since it's set to null it can't choose a theme to go with and gets locked up. Hope this helps.

repo: jvlflame/Javinizer


text:
Poetry pyproject.toml wheel dependencies fails to generate

Having the following pyproject.toml file
[tool.poetry]
name = "example"
version = "0.1.0"
description = ""
readme = "README.md"
authors = []

[tool.poetry.dependencies]
python = "3.9.10"
torch = [
  {markers = "platform_machine == 'aarch64'", url = "https://download.pytorch.org/whl/torch-1.12.1-cp39-cp39-manylinux2014_aarch64.whl" },
  {markers = "platform_machine == 'x86_64'", url = "https://download.pytorch.org/whl/cpu/torch-1.12.1%2Bcpu-cp39-cp39-linux_x86_64.whl" },
]

[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

and the following poetry.lock file
# This file is automatically @generated by Poetry 1.4.0 and should not be changed by hand.

[[package]]
name = "torch"
version = "1.12.1"
description = "Tensors and Dynamic neural networks in Python with strong GPU acceleration"
category = "main"
optional = false
python-versions = ">=3.7.0"
files = [
    {file = "torch-1.12.1-cp39-cp39-manylinux2014_aarch64.whl", hash = "sha256:6cf6f54b43c0c30335428195589bd00e764a6d27f3b9ba637aaa8c11aaf93073"},
]

[package.dependencies]
typing-extensions = "*"

[package.source]
type = "url"
url = "https://download.pytorch.org/whl/torch-1.12.1-cp39-cp39-manylinux2014_aarch64.whl"

[[package]]
name = "torch"
version = "1.12.1+cpu"
description = "Tensors and Dynamic neural networks in Python with strong GPU acceleration"
category = "main"
optional = false
python-versions = ">=3.7.0"
files = [
    {file = "torch-1.12.1%2Bcpu-cp39-cp39-linux_x86_64.whl", hash = "sha256:870bc47b880fb0488ea5b665bf76fc8df76a55a5cd48917501bf4597e1af6b2e"},
]

[package.dependencies]
typing-extensions = "*"

[package.source]
type = "url"
url = "https://download.pytorch.org/whl/cpu/torch-1.12.1%2Bcpu-cp39-cp39-linux_x86_64.whl"
[[package]]
name = "typing-extensions"
version = "4.5.0"
description = "Backported and Experimental Type Hints for Python 3.7+"
category = "main"
optional = false
python-versions = ">=3.7"
files = [
    {file = "typing_extensions-4.5.0-py3-none-any.whl", hash = "sha256:fb33085c39dd998ac16d1431ebc293a8b3eedd00fd4a32de0ff79002c19511b4"},
    {file = "typing_extensions-4.5.0.tar.gz", hash = "sha256:5cb5f4a79139d699607b3ef622a1dedafa84e115ab0024e0d9c044a9479ca7cb"},
]

[metadata]
lock-version = "2.0"
python-versions = "3.9.10"
content-hash = "b7d2a1b2bf6dddd0bb2fa76dc0a38338509d62e901e7daec4839b316a015fe69"

with the following BUILD.bazel file
load(
    "@jvolkman_rules_pycross//pycross:defs.bzl",
    "pycross_lock_file",
    "pycross_poetry_lock_model",
    "pycross_target_environment",
)

_linux_x86_64 = [
    "@platforms//os:linux",
    "@platforms//cpu:x86_64",
]

pycross_target_environment(
    name = "python_linux_x86_64",
    abis = ["cp39"],
    platforms = [
        "linux_x86_64",
        "manylinux2014_x86_64",
    ] + [
        "manylinux_2_%s_x86_64" % str(i)
        for i in range(17, 25)
    ],
    python_compatible_with = _linux_x86_64,
    version = "3.9.10",
    visibility = ["//visibility:public"],
)

pycross_poetry_lock_model(
    name = "predict_lock_model",
    poetry_lock_file = "poetry.lock",
    poetry_project_file = "pyproject.toml",
)

pycross_lock_file(
    name = "predict_lock",
    out = "predict_lock.bzl",
    lock_model_file = ":predict_lock_model",
    target_environments = [
        ":python_linux_x86_64",
    ],
)

and running
bazel build //predict:predict_lock

results in the following error
INFO: Invocation ID: efb054fe-51cd-4e9f-a8ff-a1a6a3681f81
INFO: Analyzed target //predict:predict_lock (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: /workspaces/data-platform/predict/BUILD.bazel:34:26: Action predict/predict_lock_model.json failed: (Exit 1): poetry_translator failed: error executing command (from target //predict:predict_lock_model) bazel-out/aarch64-opt-exec-2B5CBBC6/bin/external/jvolkman_rules_pycross/pycross/private/tools/poetry_translator --poetry-project-file predict/pyproject.toml --poetry-lock-file predict/poetry.lock ... (remaining 2 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
Traceback (most recent call last):
  File "/home/devcontainer/bazel/output_base/sandbox/processwrapper-sandbox/9/execroot/data_platform/bazel-out/aarch64-opt-exec-2B5CBBC6/bin/external/jvolkman_rules_pycross/pycross/private/tools/poetry_translator.runfiles/jvolkman_rules_pycross/pycross/private/tools/poetry_translator.py", line 298, in <module>
    app.run(main, flags_parser=parse_flags)
  File "/home/devcontainer/bazel/output_base/sandbox/processwrapper-sandbox/9/execroot/data_platform/bazel-out/aarch64-opt-exec-2B5CBBC6/bin/external/jvolkman_rules_pycross/pycross/private/tools/poetry_translator.runfiles/rules_pycross_pypi_deps_absl_py/site-packages/absl/app.py", line 308, in run
    _run_main(main, args)
  File "/home/devcontainer/bazel/output_base/sandbox/processwrapper-sandbox/9/execroot/data_platform/bazel-out/aarch64-opt-exec-2B5CBBC6/bin/external/jvolkman_rules_pycross/pycross/private/tools/poetry_translator.runfiles/rules_pycross_pypi_deps_absl_py/site-packages/absl/app.py", line 254, in _run_main
    sys.exit(main(argv))
  File "/home/devcontainer/bazel/output_base/sandbox/processwrapper-sandbox/9/execroot/data_platform/bazel-out/aarch64-opt-exec-2B5CBBC6/bin/external/jvolkman_rules_pycross/pycross/private/tools/poetry_translator.runfiles/jvolkman_rules_pycross/pycross/private/tools/poetry_translator.py", line 258, in main
    lock_set = translate(args.poetry_project_file, args.poetry_lock_file)
  File "/home/devcontainer/bazel/output_base/sandbox/processwrapper-sandbox/9/execroot/data_platform/bazel-out/aarch64-opt-exec-2B5CBBC6/bin/external/jvolkman_rules_pycross/pycross/private/tools/poetry_translator.runfiles/jvolkman_rules_pycross/pycross/private/tools/poetry_translator.py", line 133, in translate
    pinned_package_specs[pin] = parse_constraint(pin_info["version"])
TypeError: list indices must be integers or slices, not str
Target //predict:predict_lock failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 0.288s, Critical Path: 0.16s
INFO: 2 processes: 2 internal.
FAILED: Build did NOT complete successfully

Reading the error message and reading the code it looks like the poetry_translator.py doesn't like two things:

Currently it's being passed a list instead of a string / dict
If it's passed a dict it requires the dict to contain the version key

Thanks. I haven't tried to reproduce the issue, but just looking at the error and what you've provided I'm guessing that I don't handle this syntax:
torch = [
  {markers = "platform_machine == 'aarch64'", url = "https://download.pytorch.org/whl/torch-1.12.1-cp39-cp39-manylinux2014_aarch64.whl" },
  {markers = "platform_machine == 'x86_64'", url = "https://download.pytorch.org/whl/cpu/torch-1.12.1%2Bcpu-cp39-cp39-linux_x86_64.whl" },
]

The translation step assumes the simpler format, e.g. torch = "=1.2.1". I'll have to take a closer look to see if this more complex form can be supported.

I am having the same issue with a dependency defined as:
tensorflow = [
    {version = "2.16.1", platform="linux", extras=["and-cuda"]},
    {version = "2.16.1", platform="darwin"},
]

authors: jvolkman mvgijssel wingsofovnia


text:
Cropped images are sometimes 1 pixel too small

smartcrop --width 100 --height 400 %1 %~n1_out%~x1
When I run this command on kitty.jpg from the test suite, the output image is 99x400.

I assume this happens because of the skewed aspect ratio of the requested crop, I've encountered a similar "missing pixel" problem when cropping in Photoshop. Is there a way to force exact dimensions for the output?

Hey @wave-dash thanks for the detailed report. I don't think this is the correct repo though. Can you please report it against https://github.com/jwagner/smartcrop-cli ? Looks like a rounding error somewhere. I don't have time to go digging for it right now but I should get to it eventually. :)

Sure thing, sorry about that. This repo seemed more active, and I figured the code for the two would be mostly the same.

I actually have a similar problem using smartcrop-sharp. When passing it options like this:
const { topCrop } = await smartcrop.crop(imageFile, {
            minScale: 1.0,
            width: 3,
            height: 2,
        });

OR
const { topCrop } = await smartcrop.crop(imageFile, {
            minScale: 1.0,
            width: 4000,
            height: 2666,
        });

It always returns a height of 2656 instead. I think the issues are here:
https://github.com/jwagner/smartcrop.js/blob/de2d1438b1f46490452f8e8b196974b19b0b0dcf/smartcrop.js#L120-L121
https://github.com/jwagner/smartcrop.js/blob/de2d1438b1f46490452f8e8b196974b19b0b0dcf/smartcrop.js#L147-L148
In the first pair of lines, I believe you are scaling down the dimensions for the downsampled image (for processing ease, I'm assuming). But since it's floored, once you scale back up in the second pair of lines, it won't be at the correct width, especially if the initial wasn't a multiple of 256.
To prove the above example in pseudocode,
prescale = 0.064
downsampledCropHeight = floor(2666 * 0.064) = 170
finalCropHeight = floor(170 / 0.064) = 2656

I don't know what the solution should be. You could force based on aspect ratio. But as an end user, I guess I can just use the x and y of the crop, and force the dimensions myself.
Just letting you know where I think the issue lies.

authors: jwagner kamiyo wave-dash


text:
Modify the HTML template to handle more data

Expand the HTML template to account for more profile data
Modify the HTML template to account for multiple projects

Issue parameters have been met.


text:
Open maximized window directly maximized

Which operating system does the issue occur on?
ArchLinux
If on linux, are you using X11 or Wayland?
At the time of opening this bug, X11.
With startup_mode set to Maximized, new Alacritty instance doesn't open directly maximized but instead open first at the size it would with the default windowed value, and then after a quick flash resize to its Maximized size.
Could it instead open directly at its Maximized size instead, and avoid this flashing effect to user?

I'm not 100% sure about it, but it seems like it's possible, at least from by quick testing. I don't know any caveats of this approach though.

It turned out that Maximized couldn't be worked around even more on X11 to achieve the behavior you've mentioned, since X11 doesn't support starting window in maximized mode (we're maximizing it during run time). I was initially confused by awesomewm, which started alacritty in a wrong way (like below all other windows + maximized), however forcing it to start everything in floating mode and then setting maximized was resulting in nothing with my patch, and in a behavior you've mentioned on master.

@Porkepix Which WM are you using?

After some testing, I can notice the issue with KDE/Plasma. I could do some record and look frame by frame and you clearly see the transition when I spawn a new alacritty window above another one.
I didn't do record with other window managers, but with only my eyes I didn't see anything as noticeable with Gnome (both Xorg and Wayland), XFCE, Budgie or Cinnamon.
I can also check with a record and frame by frame inspection for those if you wish to.

I don't think it's possible to spawn a window with X that is directly mapped as maximized, though there might be some ways to work around this.
Spawning the window at monitor coordinates 0x0 with the width/height of the entire monitor and then calling maximized after it has been mapped might make it possible to achieve this without any flickering, but I'm not sure if that would be worth it. I'm also not certain how all the different WMs behave when a window is maximized, since i3 does not have this concept.
I don't think this is going to change anytime soon though. If your WM has an option to spawn a window as maximized, that's probably your best bet.

authors: Porkepix chrisduerr kchibisov

repo: jwilm/alacritty


text:
Ignore casing of algorithm

I am have to connect to a third party source for JWTs which transmits the algorithm as "Ed25519". This does not match the expected value in Ruby "ED25519". To remedy this:

Ignore casing of algorithm
Preserve original algorithm casing during encode/decode

There might be something wrong with how the gem handles the Ed25519 cases (https://github.com/jwt/ruby-jwt/issues/334).
In general i think that making the algorithms case insensitive is maybe not a good idea. The RFCs clearly states what the values are expected to be (https://tools.ietf.org/html/rfc7518#page-9).

The RFCs clearly states what the values are expected to be (https://tools.ietf.org/html/rfc7518#page-9).

The RFC does not say anything about case sensitivity. It's reasonable to expect that there will case insensitive JWT implementations in the wild. Perhaps we can always encode to correct casing (uppercase), but decode irrespective of case?

@anakinj I've raised PR #406 which is specific to "Ed25519". That PR includes examples of how other libs are using "Ed25519" (lowercase "d"). Please kindly merge either this PR or #406 .

I agree that that the parameter given in the decode method could be case insensitive.
Just to compare the OpenSSL API is case insensitive and allows both uppercase and lowercase:
OpenSSL::Digest.new('SHA512') == OpenSSL::Digest.new('sha512')
=> true

Im fine with either just doing the change in #406 or then make some adjustments to this that the alg value in the token do not change but the encode and decode methods understands the algorithm in any given case

OK, I've updated this PR to show what it would look like to add casing coercion (e.g. "hs256" becomes "HS256" when encoding). There are still some failing specs related to unsupported case. If you like this implementation I will fix the failing specs over the weekend.

Thank you for your contribution.

authors: anakinj johnnyshields

repo: jwt/ruby-jwt


text:
🛑 le Zata is down

In d7f8107, le Zata (http://zata.free.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: le Zata is back up in 7cbc197.

repo: jyhem/upptime-jyhem


text:
🛑 le Zata is down

In 5e89d1b, le Zata (http://zata.free.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: le Zata is back up in 9d7a5df.


text:
🛑 le Zata is down

In e6901eb, le Zata (http://zata.free.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: le Zata is back up in 159900a.


text:
🛑 le Zata is down

In c847220, le Zata (http://zata.free.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: le Zata is back up in 9eb4e9b after 11 minutes.


text:
fix: do not find wrapper for contains when call hideThese()

https://jsfiddle.net/feipigzi/62k3998L/

What the issue you are trying to fix? Could you provide a jsfiddle showing the error scenario?

@staabm https://jsfiddle.net/feipigzi/62k3998L/

Could you elaborate a bit further. I am not sure this is a bug right now.

closing, because no feedback. feel free to discuss your issue further.

authors: staabm zhenyong

repo: jzaefferer/jquery-validation


text:
LALR instead of SLR for initializing LR(0) partitions.

Currently, langcc appears to use SLR followsets for initializing the partitions in the LR(0) NFA.
It looks to me like LALR followsets could be used instead.
Of course, calculating LALR followsets is more tricky than the standard followsets, but
LPG is a LALR(k) parser generator written in C++ and maybe adopting its approach wouldn't be too difficult.
I think it would be really interesting to see how big of an effect this could have on the size of the final tables.

Because langcc appears to be abandoned, I'm going to close this issue.

repo: jzimmerman/langcc


text:
Add support for a screen rotation

Currently portrait orientation is supported. Could you add support for a landscape screen orientation too?

Library contains only view, not a view controller. Right now view does not handle resizes, but I think support can be added easily. I'll try today.

@kronik added ability to resize view in version 0.1.1


text:
How to insert/merge multi-level block?

Hi, I am trying to insert a multi-level level block to an original yaml file:
original:
apiVersion: test
kind: test
metadata:
  name: test
  namespace: test
spec:
  infrastructureTemplate:
    apiVersion: test
    kind: test
    name: test
  kubeadmConfigSpec:
    clusterConfiguration:
      apiServer:
        extraArgs:
          cloud-provider: external

the patch file would be:
spec:
metadata:
  name: test
  namespace: test
spec:
  kubeadmConfigSpec:
    clusterConfiguration:
      imageRepository: test
      kubernetesVersion: test
        - etcd:
            local:
              dataDir: test
              imageRepository: test
              imageTag: test

the combination would be:

apiVersion: test
kind: test
metadata:
  name: test
  namespace: test
spec:
  infrastructureTemplate:
    apiVersion: test
    kind: test
    name: test
  kubeadmConfigSpec:
    clusterConfiguration:
      imageRepository: test
      kubernetesVersion: test
        - etcd:
            local:
              dataDir: test
              imageRepository: test
              imageTag: test
      apiServer:
        extraArgs:
          cloud-provider: external

But I tried overlay method but it doesn't work with a multi-level insert. Can I get some guidance on how to do this? Thanks!

Hi @jiatongw,
The overlay package is exactly what you're looking for! Although it seems like you have invalid yaml in your example, more specifically, the block:
...
clusterConfiguration:
      imageRepository: test
      kubernetesVersion: test
        - etcd:
            local:
              dataDir: test
              imageRepository: test
              imageTag: test
...

Is invalid at the - etcd line. This array item needs to be in an array but is currently in a map.
I have added <some-key> as the container for the array item but otherwise, this is an example of using the overlay package to achieve what you've described: https://get-ytt.io/#gist:https://gist.github.com/ewrenn8/e61a6234ea175eec7958be76dc2ebfea.

@ewrenn8 I think the second example is what I am look for. Thanks!
There is another question: in my real case, the metadata.name and metadata.namespace are variables. So I think maybe I can use apiVersion and kind to match?
Is #@overlay/match by=overlay.subset({"apiVersion":"test"}, {"kind": test}) a valid one?

Just tested using the interactive playground.. it is not valid. overlay.subset takes only one argument. Is there a way to match by kind and apiversion?

Hey @jiatongw, you could do #@overlay/match by=overlay.subset({"apiVersion":"test", "kind": test})

given that yall sorted out two questions, im going to close this issue.

authors: cppforlife ewrenn8 jiatongw


text:
c-api导出优化

#if defined(_MSC_VER)
#ifdef __cplusplus
#define SherpaNcnn_EXPORT   extern "C" _declspec(dllexport)
#else
#define SherpaNcnn_EXPORT
#endif
#else
#ifdef __cplusplus
#define SherpaNcnn_EXPORT extern "C"
#else
#define SherpaNcnn_EXPORT
#endif
#endif
适配一下msvc

@zhou881117
Thanks for your contribution! https://github.com/k2-fsa/sherpa-ncnn/pull/190 is an updated version of this PR.
Closing via #190


text:
Request support for PowerPC (ppc64le) CPU

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

k3s is supposed to support IoT devices, but it appears that PowerPC-based devices are excluded.
Describe the solution you'd like

Support for PowerPC-based (ppc64le) devices is desired.
Describe alternatives you've considered

Both minikube and kind support PowerPC but having a more lightweight solution would be desirable.
Additional context

Backporting

[ ] Needs backporting to older releases

We do not currently have access to any PPC hardware on which to build or test K3s.

Understood.

authors: brandond crystalattice


text:
[emby] New chart

Signed-off-by: Nicholas Wilde ncwilde43@gmail.com
Description of the change Emby
Benefits
New chart
Possible drawbacks
None
Applicable issues
None
Additional information
Checklist

[X] Chart version bumped in Chart.yaml according to semver.
[X] Title of the PR starts with chart name (e.g. [home-assistant])
[X] Variables are documented in the README.md (this can be done with using our helm-docs wrapper ./hack/gen-helm-docs.sh stable <chart>)

Incubator is meant for long lived testing of a chart with pretty non-standard config. This looks as if it's fine being release as stable.


text:
operators hive-operator (1.1.13)

Signed-off-by: Devan Goodwin dgoodwin@redhat.com
Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

authors: dgoodwin framework-automation


text:
operators azure-service-operator (1.0.28631)

Signed-off-by: Christian Muirhead christian.muirhead@microsoft.com
Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

authors: babbageclunk framework-automation


text:
operators [O] hazelcast-jet-enterprise-operator (0.6.0)

Signed-off-by: devOpsHelm devopshelm@hazelcast.com
Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

/merge possible

/merge possible

/merge possible

authors: devOpsHelm framework-automation


text:
Remove sh-specific redirections.

The "<<<" are not available in dash, used by deb-based OSes. Replaced it with "echo" and "|" which achieves same effect.
Reviewed-by: Chun-Feng (David) Liu cfliu@google.com

/test-all

/test-all

Pull Request Test Coverage Report for Build 3677226919

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.05%) to 25.33%

Files with Coverage Reduction
New Missed Lines
%

controllers/sriovnetwork_controller.go
2
67.0%

Totals

Change from base Build 3631034070:
0.05%

Covered Lines:
1902

Relevant Lines:
7509

💛  - Coveralls

I don't seem to have merge power. It looks like all tests passed

/lgtm

authors: SchSeba adrianchiris coveralls iancoolidge


text:
Implement a CassandraTask for moving single-token nodes

What this PR does:
This PR implements a CassandraTask for moving single-token nodes.
Which issue(s) this PR fixes:
Fixes #441
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CHANGELOG.md updated (not required for documentation PRs)
[ ] CLA Signed:  DataStax CLA

Note to reviewers: I'd like to introduce the bare functionality first, then introduce later on some extra functionality such as:

Available disk size pre-checks;
Automatic token computation.


text:
Prometheus scrape errors: invalid metric name or label names

What did you do?
I deployed a K8ssandraCluster with Prometheus metrics enabled (see below) using the k8ssandra-operator.
Three of the four targets of the cass-servicemonitors throw scrape errors like this one:
invalid metric name or label names: {__name__="mcac_hints_hints_created.10.244.3.158.7000_total", cassandra_datastax_com_cluster="k8ssandra", cassandra_datastax_com_datacenter="dc1", cluster="k8ssandra", container="cassandra", dc="dc1", endpoint="prometheus", exported_instance="10.244.4.231", instance="10.244.4.231:9103", job="k8ssandra-dc1-all-pods-service", mcac="org.apache.cassandra.metrics.hints_service.hints_created.10.244.3.158.7000", mcac_filtered="true", namespace="cassandra", pod="k8ssandra-dc1-default-sts-0", rack="default", service="k8ssandra-dc1-all-pods-service"}

Is there something I can do about it? Is something wrong with my K8ssandraCluster?
Did you expect to see some different?
No scrape errors.
Environment

K8ssandra Operator version:
Image:         docker.io/k8ssandra/k8ssandra-operator:v1.6.0
Image ID:      docker.io/k8ssandra/k8ssandra-operator@sha256:f74057380f4c18ea45c0c76f12e7eb74730209f232703cdfec5739514a16a4c3

Kubernetes version information:
# kubectl version --output=yaml
clientVersion:
  buildDate: "2023-03-15T13:37:18Z"
  compiler: gc
  gitCommit: ef70d260f3d036fc22b30538576bbf6b36329995
  gitTreeState: clean
  gitVersion: v1.24.12
  goVersion: go1.19.7
  major: "1"
  minor: "24"
  platform: linux/amd64
kustomizeVersion: v4.5.4
serverVersion:
  buildDate: "2023-03-15T13:30:13Z"
  compiler: gc
  gitCommit: ef70d260f3d036fc22b30538576bbf6b36329995
  gitTreeState: clean
  gitVersion: v1.24.12
  goVersion: go1.19.7
  major: "1"
  minor: "24"
  platform: linux/amd64

Kubernetes cluster kind:
bare metal, kubeadm

Manifests:
apiVersion: k8ssandra.io/v1alpha1
kind: K8ssandraCluster
metadata:
  name: k8ssandra
spec:
  auth: false
  cassandra:
    config:
      jvmOptions:
        heap_initial_size: 4G
        heap_max_size: 4G
    datacenters:
      - metadata:
          name: dc1
        resources:
          requests:
            cpu: 500m
            memory: 5Gi
          limits:
            cpu: 2
            memory: 10Gi
        size: 4
        storageConfig:
          cassandraDataVolumeClaimSpec:
            storageClassName: local-path
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 5Gi
        telemetry:
          prometheus:
            commonLabels:
              release: kube-prometheus-stack
            enabled: true
    serverVersion: "4.0.7"
  reaper:
    autoScheduling:
      enabled: true
    telemetry:
      prometheus:
        commonLabels:
          release: kube-prometheus-stack
        enabled: true

You can scrape the metrics from the newer endpoint (port 9000) and not the old MCAC endpoint.

I am not sure how to do that. I changed port: prometheus manually to port: metrics in the k8ssandra-dc1-cass-servicemonitor created by the k8ssandra-operator and now I get the following error for all four instances/targets (only with different IP addresses):
Get "http://10.244.3.13:9000/metrics": dial tcp 10.244.3.13:9000: connect: connection refused

This is the service monitor (without the metricRelabelings):
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  annotations:
    k8ssandra.io/resource-hash: 5Y3cOLV0h3fw65WeQJCqYrohwZOccOGyCEp2JtG4kck=
  creationTimestamp: "2023-02-07T08:54:53Z"
  generation: 17
  labels:
    app.kubernetes.io/component: telemetry
    app.kubernetes.io/created-by: k8ssandracluster-controller
    app.kubernetes.io/managed-by: k8ssandra-operator
    app.kubernetes.io/part-of: k8ssandra
    k8ssandra.io/cluster-name: k8ssandra
    k8ssandra.io/cluster-namespace: cassandra
    k8ssandra.io/datacenter: dc1
    release: kube-prometheus-stack
  name: k8ssandra-dc1-cass-servicemonitor
  namespace: cassandra
  ownerReferences:
  - apiVersion: cassandra.datastax.com/v1beta1
    blockOwnerDeletion: true
    controller: true
    kind: CassandraDatacenter
    name: dc1
    uid: 71069af5-86ab-4ec5-8990-267024a9a34f
  resourceVersion: "359652657"
  uid: 195fad2d-b188-467a-bd0f-1743c9feac18
spec:
  endpoints:
  - bearerTokenSecret:
      key: ""
    interval: 15s
    metricRelabelings: [...]
    path: /metrics
    port: metrics
    scheme: http
    scrapeTimeout: 15s
  namespaceSelector:
    matchNames:
    - cassandra
  selector:
    matchExpressions:
    - key: cassandra.datastax.com/cluster
      operator: In
      values:
      - k8ssandra
    - key: cassandra.datastax.com/datacenter
      operator: In
      values:
      - dc1
    matchLabels:
      app.kubernetes.io/managed-by: cass-operator
      cassandra.datastax.com/prom-metrics: "true"
  targetLabels:
  - cassandra.datastax.com/cluster
  - cassandra.datastax.com/datacenter

And this is the service:
apiVersion: v1
items:
- apiVersion: v1
  kind: Service
  metadata:
    annotations:
      cassandra.datastax.com/resource-hash: dzNfK3eQ1eF02rAs6/3sxVa119CotM6e/XqsvKBhUMo=
    creationTimestamp: "2023-02-07T08:48:59Z"
    labels:
      app.kubernetes.io/created-by: cass-operator
      app.kubernetes.io/instance: cassandra-k8ssandra
      app.kubernetes.io/managed-by: cass-operator
      app.kubernetes.io/name: cassandra
      app.kubernetes.io/version: 4.0.7
      cassandra.datastax.com/cluster: k8ssandra
      cassandra.datastax.com/datacenter: dc1
      cassandra.datastax.com/prom-metrics: "true"
    name: k8ssandra-dc1-all-pods-service
    namespace: cassandra
    ownerReferences:
    - apiVersion: cassandra.datastax.com/v1beta1
      blockOwnerDeletion: true
      controller: true
      kind: CassandraDatacenter
      name: dc1
      uid: 71069af5-86ab-4ec5-8990-267024a9a34f
    resourceVersion: "323576073"
    uid: 7c970480-d7f8-4cc7-bd22-e256b5cf4e94
  spec:
    clusterIP: None
    clusterIPs:
    - None
    internalTrafficPolicy: Cluster
    ipFamilies:
    - IPv4
    ipFamilyPolicy: SingleStack
    ports:
    - name: native
      port: 9042
      protocol: TCP
      targetPort: 9042
    - name: mgmt-api
      port: 8080
      protocol: TCP
      targetPort: 8080
    - name: prometheus
      port: 9103
      protocol: TCP
      targetPort: 9103
    - name: metrics
      port: 9000
      protocol: TCP
      targetPort: 9000
    publishNotReadyAddresses: true
    selector:
      cassandra.datastax.com/cluster: k8ssandra
      cassandra.datastax.com/datacenter: dc1
    sessionAffinity: None
    type: ClusterIP
  status:
    loadBalancer: {}
kind: List
metadata:
  resourceVersion: ""

Querying the prometheus endpoint from inside the cassandra container works:
# kubectl --namespace cassandra exec pod/k8ssandra-dc1-default-sts-0 --container cassandra -- curl -IsS http://localhost:9000/metrics
HTTP/1.1 200 OK
Content-Type: text/plain; version=0.0.4; charset=utf-8
Content-Length: 29237744
Connection: keep-alive

And I verified that the containerPort is exposed:
    - containerPort: 9000
      name: metrics
      protocol: TCP

@burmanm Is my K8ssandraCluster wrong or why is it querying the MCAC endpoint when I have configured:
        telemetry:
          prometheus:
            enabled: true

Hey, try the following:
telemetry:
  prometheus:
    enabled: true
  mcac:
    enabled: false

@burmanm Thank you very much for the support!
I disabled mcac as suggested and the service monitor looks different now (for example the metricRelabelings are gone). But I still get the following scrape error:
Get "http://10.244.1.127:9000/metrics": dial tcp 10.244.1.127:9000: connect: connection refused

The service monitor now looks like this:
spec:
  endpoints:
    - bearerTokenSecret:
        key: ""
      interval: 15s
      path: /metrics
      port: metrics
      scheme: http
      scrapeTimeout: 15s
  namespaceSelector:
    matchNames:
      - cassandra
  selector:
    matchExpressions:
      - key: cassandra.datastax.com/cluster
        operator: In
        values:
          - k8ssandra
      - key: cassandra.datastax.com/datacenter
        operator: In
        values:
          - dc1
    matchLabels:
      app.kubernetes.io/managed-by: cass-operator
      cassandra.datastax.com/prom-metrics: "true"
  targetLabels:
    - cassandra.datastax.com/cluster
    - cassandra.datastax.com/datacenter

It looks like a bug. TBH, the initial issue with mcac enabled looks like one as well.
Let me reproduce these and see what we can do.

I think it's just because of this: https://github.com/k8ssandra/k8ssandra-operator/blame/dc852e456324bfb3017701ef9b8b473fcf54c68e/pkg/telemetry/cassandra_agent/cassandra_agent_config.go#L29
It's forced to bound to 127.0.0.1, it's not going to be available with the PodIP. I quickly tested with cass-operator to verify it, with default installation the metrics are available, but if you deploy a ConfigMap with the following properties:
kind: ConfigMap
apiVersion: v1
metadata:
  name: my-metrics-config
  namespace: cass-operator
data:
  metrics-collector.yaml: |
    endpoint:
      address: "127.0.0.1"
      port: 9000

It's no longer available through PodIP (like it shouldn't be).

I think you can simply override this behavior with the following K8ssandraCluster:
telemetry:
  prometheus:
    enabled: true
  mcac:
    enabled: false
  cassandra:
    endpoint:
      address: "0.0.0.0"

I'm able to reproduce the initial issue:

We're missing a relabeling rule to replace the dots in the hints metrics it seems.

@burmanm, I guess we should make 0.0.0.0 the default endpoint in k8ssandra-operator unless overridden, right?

We don't need to set that value (or any endpoint configs) at all in k8ssandra-operator I'd say.

I think you can simply override this behavior with the following K8ssandraCluster:
telemetry:
  prometheus:
    enabled: true
  mcac:
    enabled: false
  cassandra:
    endpoint:
      address: "0.0.0.0"

That solved the issue. Thank you very much!

@burmanm we need to add these data in the k8ssandra-cluster statefulset. so that our prometheus scrap metrices from these k8ssandra pods. Is there any way to override this spec from k8ssandra-cluster.yaml?
template:
metadata:
annotations:
prometheus.io/path: /metrics
prometheus.io/port: "9000"
prometheus.io/scrape: "true"

To be clear do you want these annotations on the statefulets or the pods created by the statefulsets?

authors: adejanovski bradfordcp burmanm elchenberg msr1132


text:
Move functionality from RecipientLoader to its own class

Once PR #962 is merged, move functionality from RecipientLoader to its own class(es). That way both testing and changing the method to perform the work off the main thread later will be much easier.
The fact that the loader is registering content observers make this a bit more complicated. So this should probably not done by a beginner.

This loader is used to display a dropdown only, so the information it displays is very short-lived and the user would not expect it to be updated while leaving the app. Consequently, content observers are not really a necessary feature for this particular loader, and we could just remove it.

I guess it would be nice to be updated. You could realize a recipient is missing a key, go to OpenKeychain to add the key, then come back to K-9 Mail's compose screen and see the updated recipient box.

reminder to also change the loading in RecipientPresenter to load in an asynctask rather than with the loader hack.

authors: Valodim cketti


text:
update providers to add 2 of the domains offered by Mailo

Updated app/autodiscovery/providersxml/src/main/res/xml/providers.xml to add details for Mailo.com.

Mistake in the domains section - sorry.


text:
adds Pursuit search to the completion

changes the completion API from complete stub to complete stub (File|Project|Pursuit) where File and Project do the same for now and Pursuit fetches completion results from Pursuit

@epost Some reviewing would be appreciated. Since everything is synchronous this does block for the entire HTTP request. Maybe we should consider asynchronous options for our new protocol?

repo: kRITZCREEK/psc-ide


text:
Error when using a plugin

Hi
I encounter the following issue when trying to run a test that uses a plugin (https://github.com/GSLabDev/pepper-box).
Error in rconfigure() method java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
        java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
        java.lang.ClassNotFoundException: com.gslab.pepper.config.plaintext.PlainTextConfigElement (no security manager: RMI class loader disabled)
Error in rconfigure() method java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
        java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
        java.lang.ClassNotFoundException: com.gslab.pepper.config.plaintext.PlainTextConfigElement (no security manager: RMI class loader disabled)
Remote engines have been started

Could you please advise on this, and how I can fix this.
Thanks for the great work!

@nysthee I was quite busy last week, I would check it during weekend.

Hi solved it by making sure plugins are on all the nodes. It was ignorance from my side.

Hi @nysthee,
I am getting the same exception when trying to execute my load testing on the slave nodes. I have copied the pepper-box.jar on all the nodes to location lib/ext initially (later to lib/ as well in addition to the one in lib/ext), but I still get the same ClassNotFoundException. I understand the problem you faced was 2 years ago, however, any pointers on this will help a lot. Thanks.

authors: kaarolch nysthee pritukam

repo: kaarolch/kubernetes-jmeter


text:
Add network policy for kabanero and tekton-pipelines namespaces

Fixes #265
The routes to the Kabanero CLI and Landing page, as well as the Tekton dashboard, do not work reliably.  OpenShift will sometimes report that the pods are not running or the network is not accessible.
The OpenShift Service Mesh Member Role is watching the kabanero and tekton-pipelines namespaces.  It's watching kabanero so that appsody applications deployed there with serverless capabilities will function, and watching tekton-pipelines so that the github webhook sink will function.  The service mesh assumes that if a namespace is in the member role, that all traffic in and out will come thru istio and therefore traditional routes do not work reliably.
The solution was to add a network policy that allows all traffic to these namespaces.  This configuration is similar to what Kabanero had been using in OKD 3.11 and Istio 1.1.7.
I've also changed the subscription for the Serverless operator to use the redhat-catalog, since version 1.1.0 is available there now.

Fixes kabanero-io/kabanero-foundation#126

repo: kabanero-io/kabanero-operator


text:
Using FlowRouter.getParam as template-wide variable

I have a route that's roughly like this:
posts/:postId/
What's the best way to reference the postId for the whole post.html template? I'd like to be able to do this:
var postId = FlowRouter.getParam('postId');
Template.post.helpers({
    post: function(){
        return posts.findOne({_id: postId});
    }
});

But the postId variable comes back undefined. I thought this could be related to bug #95, but I don't have getParam inside onCreated, so it's a little different.
For now, I can declare the postId in each of the helpers, but it's redundant, and I use it almost a dozen times, not very DRY.

You need put var postId = FlowRouter.getParam('postId'); inside the helper itself.

I was hoping to avoid that so I could reuse the variable in several helpers and events, for example:
author: function(){
    return authors.findOne({posts: {$in: postId}});
}

Is there a better way to get the postId/context? Should I be pulling the context from the template, and using that to find related docs?

I almost forgot another thing, I would like to subscribe to a collection with the postId as an argument.

May be you are looking to pass FR context as data to a template. So, check this: https://kadira.io/blog/meteor/introducing-blaze-plus-the-next-generation-of-blaze

I close this because this is a question. Feel free to discuss.

Very interesting, I'll have to take a deeper look into blaze plus. Is it a drop-in replacement for blaze (as in remove blaze, add blaze plus, works like blaze plus the other functionality)?

authors: JulianKingman arunoda

repo: kadirahq/flow-router


text:
Option to not unsubscribe subscriptions with composeWithTracker

Right now, I'm using ReactMeteorData mixin with https://github.com/kadirahq/subs-manager
Caching subscriptions is crucial to my app so everything is always instant.
In this article, you noted that subscriptions are automatically unsubscribed after container unmount:
https://voice.kadira.io/using-meteor-data-and-react-with-meteor-1-3-13cb0935dedb#.oq8bos4u3
Is there (or can there be) an option to not unsubscribe subscriptions on unmount? I believe if there was, I wouldn't need subs-manager anymore?
Cheers,
Mark

@markoshust This is just like ReactMeteorData.(Since it runs a tracker) There is no built in way to do that.
You need to use subs-manager.

Ok no prob -- thanks

authors: arunoda markoshust

repo: kadirahq/react-komposer


text:
BE: KC: Expose Kafka Connect validation errors in the UI

What changes did you make? (Give an overview)
Closes https://github.com/kafbat/kafka-ui/issues/681
Example:

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[x] Manually (please, describe, if necessary)
[x] Unit checks
[x] Integration checks
[x] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

A picture of a cute animal (not mandatory but encouraged)

@Haarolean Are the current test failures a known problem?

@yeikel yeah it's a flaky one

@yeikel thank you!

authors: Haarolean yeikel

repo: kafbat/kafka-ui


text:
Failed consuming messages: failed to lookup address information: nodename nor servname provided, or not known

Repo example does not work on MacOS or Docker.
cargo run --example example-consume

Fails with:
Failed consuming messages: failed to lookup address information: nodename nor servname provided, or not known

~/Downloads/kafka-rust-master$ rustc --version
rustc 1.38.0 (625451e37 2019-09-23)
~/Downloads/kafka-rust-master$ cargo --version
cargo 1.38.0 (23ef9a4ef 2019-08-20)

Docker-Compose for Kafka
---
version: '2'
services:
  zookeeper:
    image: confluentinc/cp-zookeeper:5.3.1
    hostname: zookeeper
    ports:
      - '2181:2181'
    environment:
      ZOOKEEPER_CLIENT_PORT: 2181

  kafka:
    image: confluentinc/cp-enterprise-kafka:5.3.1
    hostname: kafka
    ports:
      - '9092:9092'
    depends_on:
      - zookeeper
    environment:
      KAFKA_BROKER_ID: 1
      KAFKA_ZOOKEEPER_CONNECT: zookeeper:2181
      KAFKA_ADVERTISED_LISTENERS: LISTENER_BOB://kafka:9092
      KAFKA_ADVERTISED_HOST_NAME: kafka
      KAFKA_AUTO_CREATE_TOPICS_ENABLE: "false"
      CONFLUENT_METRICS_ENABLE: 'false'
      CONFLUENT_SUPPORT_CUSTOMER_ID: 'anonymous'
      KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: LISTENER_BOB:PLAINTEXT
      KAFKA_INTER_BROKER_LISTENER_NAME: LISTENER_BOB
      KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR: 1

Config issue with Kafka / Docker.  Fixed.

This is old, but the OP didn't offer the fix.
To anyone who sees this later and needs to know the correct way, add the following to the docker-compose config:
    ports:
      - "127.0.0.1:29092:29092"
     environment:
      KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://kafka:9092,PLAINTEXT_HOST://localhost:29092
      KAFKA_LISTENER_SECURITY_PROTOCOL_MAP: PLAINTEXT:PLAINTEXT,PLAINTEXT_HOST:PLAINTEXT

Good find! I will add this to the compose config :+1:

Good find! Thank you! 🎉

authors: admwrd stephenlb

repo: kafka-rust/kafka-rust


text:
02.1 Feature importance voting and pre-assessment of features.ipynb  Can‘t run successfully

I am sorry to trouble u that this part of code in file 02.1 can't run successfully. Hope for your early reply. Thanks!

Thank you very much for your warning.
The Xverse library is not a current library and unfortunately, it crashes above python 3.6. This error you are getting is related to version conflict.
I just tried the codes. While Python3.6.6 does not have any problems, unfortunately, it does not work in newer versions (I tried 3.8, 3.9 and 3.10).
In this context, if you are having problems, please try Python 3.6.
If you do not want to change the installation on your computer, you can use a virtual machine or colab. A useful link for colab: https://www.datasciencelearner.com/change-python-version-in-google-colab-steps/
Thank you
Kahraman

Thank you very much, Kahraman. You really helped me.
Your article has greatly inspired me, and I am looking forward to having more discussions with you in the future.
Thank you
Kangli Niu

You're welcome, Kangli.
I am glad that my article was useful to you. If there are any questions, I am always willing to help. Hoping to exchange more ideas in the future.
Thank you
Kahraman

@kahramankostas
Dear Sir,
I meet the same problem when I ran the code of 02.1;
The python version is 3.6.6;
could you give me some advice that I can deal with it?

The problem, as you have noticed, is that the use of the Kfold function in sklearn has changed.
In the new version the usage is as follows:
"kfold = sklearn.model_selection.KFold(n_splits=fold, shuffle=True, random_state=int(rnd*100))" s
I will update the code in this way.
Thanks for the warning

Dear Sir，
I used pip install pandas==1.35， but there is no version with 1.3.5 for python 3.6.X；
and， I  also checked the “https://www.lfd.uci.edu/~gohlke/pythonlibs/”；

pandas==1.3.5 depends on python 3.7 or more，
therefore， the requirements.txt is right?
and when I ran the code “from sklearn.metrics import balanced_accuracy_score”， it reports an error that  there is no module with balanced_accuracy_source.
Look for your reply.

It gives problems in xverse for newer versions of Python. If you are using 3.6, you don't need to specify the version, you shouldn't have any problems.

If you get the error in the screenshot, you should:
The problem is due to the updating of the sklearn functions, if you make the following changes on line 131 of the _voting.py file, you will not have any problems in newer versions of Python.
rfe = RFE(clf, self.no_of_features) #old-from #replace this line with the following
rfe = RFE(estimator=clf,n_features_to_select=self.no_of_features) # new-to # new line
balanced_accuracy_score error looks interesting.
the following link may help. but if you provide more information (e.g. ss) I can help too.
https://stackoverflow.com/questions/55111886/cannot-import-name-balanced-accuracy-score-from-scikit-learn

I forked the xverse module and fixed the bugs caused by the panda and sklearn updates.
If you use my version in the requirements.txt you should have no problems.
If you want to install it manually, you can install it as follows:
pip install git+https://github.com/kahramankostas/XuniVerse

Can i run this project in colab ?? i try it but colab run on notbook

谢谢来信，已收到！祝好：）

@AhmedmostafaElabdli1  If you share your error screenshots, I will help as much as I can.


text:
Error：Must provide radosgw admin access key

ceph version 12.2.2 (cf0baeeeeba3b47f9427c6c97e2144b094b7e5ba) luminous (stable)

EERROR：

you must add admin access for you exist user, or create another and than add to them admin access by next command:
radosgw-admin caps add --uid="<admin_uid>" --caps="users=*"


text:
spike: QC board

This card is to track experiments with the QC board in order to boot a Kairos image.

While we are able to modify the efi.bin now and provide different boot efi files we cannot modify the partitions in any meaningful way and that blocks any kind of kairos real implementation on the device.

grub can be added but it wont see any usb devices which we could boot off the installation process
systemd-boot can be tweaked to provide different entries, including chainloading the grub efi file and efi shell but again, we cannot use that to boot from external devices
cant partition the device in any meaningful way, its hardcoded and even changing manually the partitions.xml and forcing it to format the system, the partitions dont appear anywhere
we can generate a fake system.img with our partitions and files on them but we cna only flash that to the single system partition, which creates a broken system partition with more partitions on it but those are innaccessible or empty.

The idea would be, as we cannot change the partitions during flahing the device, to have grub chainload the grub on a usb install media, so the agent could run the install as normal and create the proper partitions. Then the efi image would be a modified one that has grub which either loads the installer if a usb media is inserted or chainloads the active/passive images grub as normal kairos but we cannot control that, seems like during efi boot the usbs are not powered.
What we would need to continue:

a way to control the partition schema OR a way of flashing our own image into the system directly, not to a single partition
a way of booting off usb sticks

authors: Itxaka mudler

repo: kairos-io/kairos


text:
Ads Getting Through

Cannot replicate this. Are you sure the website is not whitelisted?

Yeah I'm sure, it's really strange. I just did it again and all of those ads popped up.. :/

Until I can replicate this I'm afraid I can't fix it. Will leave this open if someone has the same issue.
Please note that the test won't work anyway currently with ads blocked. I will look into that.

Just installed Nope, and I'm having this issue too on beta.speedtest.net

@vasuvasu What version are you suing? I still can't replicate this... See in the screenshot what's being blocked and compare to what you see in your browser.

I'm guessing it's regional, different ad servers are used depending on where you are located / the IP is located.

@SpacePuppeh Oh, that would make a lot of sense.

Are you using 40-50k rules? If not, adding more block lists and deduplicating them may help prevent things like this, or would any unused/rarely used rules make it slower?

authors: SpacePuppeh kaishin vasuvasu

repo: kaishin/Nope


text:
SDカード読み込みを実装する

rom置き場

最初から実装するのしんどい気もする。ビルド生成物にバイナリ仕込む....か?

include_byteマクロやばすぎる

これはHALで動作確認済

repo: kamiyaowl/rust-nes-emulator


text:
Upgrade openshift/api to release-4.15 branch

https://github.com/openshift/api/tree/release-4.15
Pull request type

[x] Dependency upgrade

Test Plan

[x] :zap: CI

#1987

@viveksinghggits @pavannd1 Please DO NOT merge yet, it is not complete. I'd like to include an upgrade for Openshift's client-go module as well in the same PR.
Nevertheless, PTAL and LMK if there are any concerns.
Also, what is the plan for upgrading Openshift going forward if automatic upgrades don't work reliably?

Also, this includes a couple of minor upgrades to k8s dependencies. Those can be pushed separately in case we need to revert this change.

repo: kanisterio/kanister


text:
KAS-3992: Add shortlist for publication-flows

Adds the shortlist service and necessary dispatcher config

Added the https change in v0.1.0. Will fix this branch & next branch later.

authors: ValenberghsSven sergiofenoll

repo: kanselarij-vlaanderen/app-kaleidos


text:
Detect when copied and original variable is used

I have the following code which I extracted from a test:
		for _, req := range testRequests {
			failingReq := req // <----- here
			failingReq.ExpectBody = test.ErrorCode(keppel.ErrTooManyRequests)
			failingReq.ExpectStatus = http.StatusTooManyRequests
			failingReq.Check(t, h)

			s.Clock.StepBy(time.Second)
			req.Check(t, h)
		}

req gets copied and modified and both are used. I think the linter should ignore this or at least add an option to ignore it.

@SuperSandro2000
There is the ignore-alias option. Have you tried it?"
linters:
  disable-all: true
  enable:
    - copyloopvar

linters-settings:
  copyloopvar:
    ignore-alias: true

repo: karamaru-alpha/copyloopvar


text:
🛑 car4-qa is down

In 3896879, car4-qa (https://car4-qa.ridecell.us) was down:

HTTP code: 0
Response time: 0 ms

Resolved: car4-qa is back up in e92cfde.

repo: karankale/upptime-test


text:
Sending P2sh is encountered with an mandatory-script-verify-flag-failed (Signature is found in scriptCode) error

Hi
Code
def import_w(index: int = 0) -> HDWallet:
    hdwallet: HDWallet = HDWallet(symbol=BTCTEST).from_mnemonic(
        "olympic tip enforce tool orchard major spy defense wink maid company book")
    # Get Bitcoin HDWallet from entropy
    hdwallet.clean_derivation()
    hdwallet.from_index(44, hardened=True)
    hdwallet.from_index(0, hardened=True)
    hdwallet.from_index(0, hardened=True)
    hdwallet.from_index(0)
    hdwallet.from_index(index)
    return hdwallet

def main():
    # always remember to setup the network
    setup('testnet')
    w = import_w(1)
    r = import_w(0)
    #
    sender = PrivateKey(wif=w.wif())
    receiver = PrivateKey(wif=r.wif())

    txin = TxInput("9aab6944ad5d771cd780f1f4c8bb714cbf76137bbeed0253406d6a640f04bbd5", 1)

    rec_public = receiver.get_public_key().to_hex()
    redeem_script = Script([rec_public, 'OP_CHECKSIG'])
    txout = TxOutput(2076777, redeem_script.to_p2sh_script_pub_key())

    tx = Transaction([txin], [txout])
    sender_address = P2pkhAddress(sender.get_public_key().get_address().to_string())
    sig = sender.sign_input(tx, 0, sender_address.to_script_pub_key())
    # print(sig)

    # get public key as hex
    pk = sender.get_public_key()
    pk = pk.to_hex()
    # print (pk)

    # set the scriptSig (unlocking script)
    txin.script_sig = Script([sig, pk])
    signed_tx = tx.serialize()
    print(signed_tx)

Why does the script below give me a different address? Shouldn't it be the same?
    setup('testnet')
    w1 = import_w(0) # From the previous code
    print(w1.p2sh_address())  # 2MxnaH4QGVz34aVHQDtYbqRVJapAuk6BTBW
    pk = PrivateKey.from_wif(wif=w1.wif())
    ps = pk.get_public_key().get_address().to_script_pub_key()
    p2sh = P2shAddress(script=ps)  # 2MxnaH4QGVz34aVHQDtYbqRVJapAuk6BTBW  // same

    rec_public = pk.get_public_key().to_hex()
    redeem_script = Script([rec_public, 'OP_CHECKSIG'])
    # redeem_script.to_p2sh_script_pub_key()

    address = keys.P2shAddress.from_script(redeem_script)
    print('address: ', address.to_string())  # 2N7uZgvLwjTBteicco18NSx91g2XGiQAixZ << different address)

In the transaction, I wanted to send it to the 2MxnaH4QGVz34aVHQDtYbqRVJapAuk6BTBW but
in the last one it was sent to this 2N7uZgvLwjTBteicco18NSx91g2XGiQAixZ
Thank you, sorry, I'm a newbie

Address 2MxnaH4QGVz34aVHQDtYbqRVJapAuk6BTBW is for a P2PKH wrapped in P2SH -> P2SH(P2PKH)
i.e. that is what  .to_script_pub_key() returns!
Address 2MxnaH4QGVz34aVHQDtYbqRVJapAuk6BTBW is for a P2PK wrapped in P2SH -> P2SH(P2PK)
Note that both P2PKH and P2PK are standard output types and thus can (and in most cases should) be used directly (not wrapped in P2SH, which will complicate spending). I typically use P2PK for demonstrating P2SH only because it is a small and easy to understand script -- not because I needed to.

authors: MohsenHaydari karask

repo: karask/python-bitcoin-utils


text:
multi-search broken since the recent update

Hi,
I assume this comes from the recent update of the tag system (which is awesome!). But now the search bar in the upper right corner seems to be broken:

The dedicated search below the Cocktails and the Ingredients tab still works as expected. Unfortunately, the logfile doesn't give much information:
bar-assistant-meilisearch-1 | [2024-07-08T10:03:24Z INFO  actix_web::middleware::logger] 172.22.0.1 "POST /multi-search HTTP/1.0" 200 6788 "https://core.einhorn.bar/cocktails" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36" 0.003851
bar-assistant-meilisearch-1 | [2024-07-08T10:03:24Z INFO  actix_web::middleware::logger] 172.22.0.1 "POST /multi-search HTTP/1.0" 400 456 "https://core.einhorn.bar/cocktails" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36" 0.000658

Works for me.
Have you tried clearing cache/cookies?

Been there, done that, even tried in a chrome incognito window with no cache/cookies present. Still "error 400" in the logfile and the mentioned display above. Also, the same on smartphone and bartender tablet.

Hi,
I'm experiencing the same issue as @frank42hh.
When I open the search on the top right, the browser console has the following output:
POST https://core.<mybar>.bar/search/multi-search 400 (Bad Request)
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:3
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:3
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:1
a @ instant-meilisearch.esm-a8c3febb.js:1
fetchWithTimeout @ instant-meilisearch.esm-a8c3febb.js:3
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:3
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:1
a @ instant-meilisearch.esm-a8c3febb.js:1
request @ instant-meilisearch.esm-a8c3febb.js:3
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:3
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:1
a @ instant-meilisearch.esm-a8c3febb.js:1
post @ instant-meilisearch.esm-a8c3febb.js:3
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:3
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:1
a @ instant-meilisearch.esm-a8c3febb.js:1
multiSearch @ instant-meilisearch.esm-a8c3febb.js:3
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:4
h @ instant-meilisearch.esm-a8c3febb.js:4
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:4
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:4
F @ instant-meilisearch.esm-a8c3febb.js:4
multiSearch @ instant-meilisearch.esm-a8c3febb.js:4
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:4
h @ instant-meilisearch.esm-a8c3febb.js:4
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:4
d @ instant-meilisearch.esm-a8c3febb.js:4
Promise.then
o @ instant-meilisearch.esm-a8c3febb.js:4
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:4
F @ instant-meilisearch.esm-a8c3febb.js:4
search @ instant-meilisearch.esm-a8c3febb.js:4
ce._search @ index-7584ce78.js:74
ce.searchOnlyWithDerivedHelpers @ index-7584ce78.js:74
s.search @ index-7584ce78.js:89
(anonymous) @ index-7584ce78.js:89
(anonymous) @ index-7584ce78.js:53
Promise.then
n @ index-7584ce78.js:53
value @ index-7584ce78.js:89
(anonymous) @ index-7584ce78.js:101
Promise.then
Pa @ index-7584ce78.js:13
mounted @ index-7584ce78.js:101
(anonymous) @ index-7584ce78.js:13
Hr @ index-7584ce78.js:13
Yt @ index-7584ce78.js:13
t.__weh.t.__weh @ index-7584ce78.js:13
_o @ index-7584ce78.js:13
Vh @ index-7584ce78.js:13
Promise.then
Wh @ index-7584ce78.js:13
Xo @ index-7584ce78.js:13
(anonymous) @ index-7584ce78.js:13
Tu @ index-7584ce78.js:9
Nr @ index-7584ce78.js:9
set @ index-7584ce78.js:9
(anonymous) @ AuthLayout-90124203.js:1
Ze.r.<computed>.r.<computed> @ index-7584ce78.js:17
Hr @ index-7584ce78.js:13
Yt @ index-7584ce78.js:13
r @ index-7584ce78.js:17

MeiliSearchApiError: Unknown field `attributesToSearchOn` inside `.queries[0]`: expected one of `indexUid`, `q`, `offset`, `limit`, `page`, `hitsPerPage`, `attributesToRetrieve`, `attributesToCrop`, `cropLength`, `attributesToHighlight`, `showMatchesPosition`, `filter`, `sort`, `facets`, `highlightPreTag`, `highlightPostTag`, `cropMarker`, `matchingStrategy`
    at instant-meilisearch.esm-a8c3febb.js:1:7412
    at Generator.next (<anonymous>)
    at d (instant-meilisearch.esm-a8c3febb.js:1:6152)
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:4
h @ instant-meilisearch.esm-a8c3febb.js:4
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:4
h @ instant-meilisearch.esm-a8c3febb.js:4
Promise.then
o @ instant-meilisearch.esm-a8c3febb.js:4
d @ instant-meilisearch.esm-a8c3febb.js:4
Promise.then
o @ instant-meilisearch.esm-a8c3febb.js:4
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:4
F @ instant-meilisearch.esm-a8c3febb.js:4
search @ instant-meilisearch.esm-a8c3febb.js:4
ce._search @ index-7584ce78.js:74
ce.searchOnlyWithDerivedHelpers @ index-7584ce78.js:74
s.search @ index-7584ce78.js:89
(anonymous) @ index-7584ce78.js:89
(anonymous) @ index-7584ce78.js:53
Promise.then
n @ index-7584ce78.js:53
value @ index-7584ce78.js:89
(anonymous) @ index-7584ce78.js:101
Promise.then
Pa @ index-7584ce78.js:13
mounted @ index-7584ce78.js:101
(anonymous) @ index-7584ce78.js:13
Hr @ index-7584ce78.js:13
Yt @ index-7584ce78.js:13
t.__weh.t.__weh @ index-7584ce78.js:13
_o @ index-7584ce78.js:13
Vh @ index-7584ce78.js:13
Promise.then
Wh @ index-7584ce78.js:13
Xo @ index-7584ce78.js:13
(anonymous) @ index-7584ce78.js:13
Tu @ index-7584ce78.js:9
Nr @ index-7584ce78.js:9
set @ index-7584ce78.js:9
(anonymous) @ AuthLayout-90124203.js:1
Ze.r.<computed>.r.<computed> @ index-7584ce78.js:17
Hr @ index-7584ce78.js:13
Yt @ index-7584ce78.js:13
r @ index-7584ce78.js:17

Uncaught (in promise) Error: MeiliSearchApiError: Unknown field `attributesToSearchOn` inside `.queries[0]`: expected one of `indexUid`, `q`, `offset`, `limit`, `page`, `hitsPerPage`, `attributesToRetrieve`, `attributesToCrop`, `cropLength`, `attributesToHighlight`, `showMatchesPosition`, `filter`, `sort`, `facets`, `highlightPreTag`, `highlightPostTag`, `cropMarker`, `matchingStrategy`
    at Proxy.<anonymous> (instant-meilisearch.esm-a8c3febb.js:4:14802)
    at h (instant-meilisearch.esm-a8c3febb.js:4:3626)
    at Object.throw (instant-meilisearch.esm-a8c3febb.js:4:2909)
    at h (instant-meilisearch.esm-a8c3febb.js:4:2540)
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:4
h @ instant-meilisearch.esm-a8c3febb.js:4
(anonymous) @ instant-meilisearch.esm-a8c3febb.js:4
h @ instant-meilisearch.esm-a8c3febb.js:4
Promise.catch
ce._search @ index-7584ce78.js:74
ce.searchOnlyWithDerivedHelpers @ index-7584ce78.js:74
s.search @ index-7584ce78.js:89
(anonymous) @ index-7584ce78.js:89
(anonymous) @ index-7584ce78.js:53
Promise.then
n @ index-7584ce78.js:53
value @ index-7584ce78.js:89
(anonymous) @ index-7584ce78.js:101
Promise.then
Pa @ index-7584ce78.js:13
mounted @ index-7584ce78.js:101
(anonymous) @ index-7584ce78.js:13
Hr @ index-7584ce78.js:13
Yt @ index-7584ce78.js:13
t.__weh.t.__weh @ index-7584ce78.js:13
_o @ index-7584ce78.js:13
Vh @ index-7584ce78.js:13
Promise.then
Wh @ index-7584ce78.js:13
Xo @ index-7584ce78.js:13
(anonymous) @ index-7584ce78.js:13
Tu @ index-7584ce78.js:9
Nr @ index-7584ce78.js:9
set @ index-7584ce78.js:9
(anonymous) @ AuthLayout-90124203.js:1
Ze.r.<computed>.r.<computed> @ index-7584ce78.js:17
Hr @ index-7584ce78.js:13
Yt @ index-7584ce78.js:13
r @ index-7584ce78.js:17

Running Salt Rim v 2.15.0, Bar Assistant v 3.17.0 and Mellisearch 1.1.1

It's a pretty old meilisearch version so I'm guessing its probably related to that. You could try updating to a newer one like 1.8

It's a pretty old meilisearch version
Yep, I know... it's still from the first release of the docker-compose image which I'm using. I'm not very experienced with docker yet, so I might or might not have sufficient practice to do that.
I already attempted to upgrade meilisearch before, but that went rogue - I didn't save error logs from that but the upgrade howto from the meilisearch homepage didn't work and restarting it with a clean database didn't work either, so I reverted back to the snapshot again.
I'll try again next week and will try to report more detailed.

Hi again,
sorry to ask stupid docker questions, but as said, I'm not yet experienced enough to get alle the details of running something in a container ;-)
I managed to delete the meilisearch volume and recreated it with meilisearch:v1.8 now. The container starts up everything as expected, and the logfile says (amongst other things) this:
bar-assistant-meilisearch-1    | 2024-07-30T13:44:28.590872Z  INFO index_scheduler::batch: document indexing done indexing_result=DocumentAdditionResult { indexed_documents: 231, number_of_documents: 231 }

bar-assistant-meilisearch-1    | 2024-07-30T13:44:28.598748Z  INFO index_scheduler: A batch of tasks was successfully completed with 1 successful tasks and 0 failed tasks.

I think this means that meilisearch is running, but then, when I try to open the multi-search, I still get an error, but another one:
bar-assistant-meilisearch-1    | 2024-07-30T13:45:46.450343Z  WARN HTTP request{method=POST host="127.0.0.1:7700" route=/multi-search query_parameters= user_agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 status_code=403 error=The provided API key is invalid.}: tracing_actix_web::middleware: Error encountered while processing the incoming HTTP request: ResponseError { code: 403, message: "The provided API key is invalid.", error_code: "invalid_api_key", error_type: "auth", error_link: "https://docs.meilisearch.com/errors#invalid_api_key" }
bar-assistant-meilisearch-1    | 2024-07-30T13:45:46.452109Z  INFO HTTP request{method=POST host="127.0.0.1:7700" route=/multi-search query_parameters= user_agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 status_code=403 error=The provided API key is invalid.}: meilisearch: close time.busy=1.23ms time.idle=2.60ms

I only changed the meilisearch version, I didn't touch the MEILI_MASTER_KEY entry in .env or the MEILISEARCH_KEY entries in the docker-compose file, so I'm quite clueless where to search for the origin of this error.
A query against meilisearch from commandline works fine as well:
# curl -X GET 'http://localhost:7700/indexes' -H 'Authorization: Bearer <heres_my_master_key>'

{"results":[{"uid":"cocktails","createdAt":"2024-07-30T13:22:36.602925352Z","updatedAt":"2024-07-30T13:44:27.971867251Z","primaryKey":"id"},{"uid":"ingredients","createdAt":"2024-07-30T13:22:36.629758866Z","updatedAt":"2024-07-30T13:44:28.585761937Z","primaryKey":"id"}],"offset":0,"limit":20,"total":2}

So what did I break this time?

Update: I just happened to notice that after removing the cache data of the site, the search works again. Is it possible that the API connection to meilisearch is somehow cached on client side? Sorry for the confusion but I honestly didn't think of the possibility that something that is cached in the browser would survive a shift-reload.
On a side note: while the search itself is working again, the thumbnail images of the recipes are not displayed within the search results. Does someone happen to have an idea about that?

API keys are saved per bar, clearing the cache or re-selecting bar usually helps.
Missing thumbnails should have some errors in network logs, or in API container logs.
What you can try is docker compose exec bar-assistant php artisan bar:refresh-search --clear and see if it helps.

Hi,
thanks for the hint, but that didn't solve the problem.
According to the Developer Tools Console, this happens:
AuthLayout-90124203.js:1 Mixed Content: The page at 'https://core.einhorn.bar/' was loaded over HTTPS, but requested an insecure element 'http://localhost/bar/api/images/125/thumb'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html

and
GET http://localhost/bar/api/images/127/thumb net::ERR_CONNECTION_REFUSED

I have no idea why it seems to request the cocktail thumbnails over http://localhost/ - the correct URL should be https://core.einhorn.bar/bar/api/images/125/thumb , which works.
(and yes, this time I remembered to clean my browser cache before testing :-))

That's weird, how does your .env look, seems like maybe APP_URL is wrongly set up

authors: OFlannigan frank42hh karlomikus zhdenny

repo: karlomikus/vue-salt-rim


text:
🛑 Habilitación is down

In 321983f, Habilitación (https://catalogo-vpfe-hab.dian.gov.co/User/Login) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Habilitación is back up in a0f2200 after 11 minutes.


text:
time to archive

time to deprecate the npm package

Can you provide the rationale for deprecating the package?

Phantom ja was never a browser that any user was using. It totally lacks any UI. It was a early version of things like puppeteer that did not exist at that time and was/is based on a early version of webkit
Also the development of phantom ja has stopped. And the phantomjs-prebuilt package that you depends on is also deprecated

authors: jginsburgn jimmywarting

repo: karma-runner/karma-phantomjs-launcher


text:
browserify error

Chrome 58.0.3029 (Windows 7 0.0.0) ERROR
Uncaught Error: Cannot find module '../util/root'
at C:/Users/BAGGAR~1/AppData/Local/Temp/90918cb8ed733bfe3627b234589ffcab.browserify:1
browserify on command line on that file works fine but it gives error while loading the file with karma with preprocessor set to 'browserify' for that file.

Can you give more information here about your karma config/setup?

No additional information since over six months ago. Closing.

authors: EzraBrooks bhawanaa wesleycho

repo: karma-runner/karma


text:
Karma@1.7.1 on npm does not match 1.7.1 source on GitHub

Expected behaviour
npm install karma@1.7.1  using https://registry.npmjs.org/ should have the same package.json dependencies as the karma-1.71.zip.
Actual behaviour
$ npm view karma@1.7.1 dist.tarball
https://registry.npmjs.org/karma/-/karma-1.7.1.tgz
$ curl -o karma-1.7.1-npm.com.tgz https://registry.npmjs.org/karma/-/karma-1.7.1.tgz
And then inspecting the tgz file it shows package.json dependencies with lodash: ^3.8.0 instead of ^4.x.y.
Environment Details
$ node --version
v6.11.1
$ npm --version
3.10.10
Steps to reproduce the behaviour
As above.
Is this a problem in publishing to registry.npmjs.org?

Yes, the npm distribution is somehow messed up.
The github source package.json
https://github.com/karma-runner/karma/blob/master/package.json
has
"version": "1.7.0",
and dependencies including:
 "lodash": "^4.17.4",
But the npm distro has package.json with
version 1.7.1
and dependencies including:
"lodash": "^3.8.0",
How can we fix this?

I think the problem here is that the 1.7.1 branch is not merged into HEAD

I renamed this issue to make it more general, as there are other issues caused by this failed deployment.

karma 1.7.1 is correct on npm. 1.7.1 was released with "old" lodash@3 because moving to 4 is breaking change. master contains multiple breaking changes, so I  cut a release for 1.7.1 which only contains this commit. The branch 1.7.1 is incorrect now as master was never supposed to be merged into it, only the tag is correct.

@dignifiedquire can you clean up the fact there are multiple tags for 1.7.1 then - and not containing the same source code - https://github.com/karma-runner/karma/compare/v1.7.1...1.7.1

@wilsonge thank you for pointing that out, should be fixed now and tags correct

Thanks :)

authors: EzraBrooks dignifiedquire johnjbarton kmashint wilsonge


text:
adopter onboarding for Li Auto

What type of PR is this?
/kind documentation

What this PR does / why we need it:
adopter onboarding for Li Auto
Which issue(s) this PR fixes:
Parts of #74
Special notes for your reviewer:

Welcome ~

authors: samzong zhzhuang-zju

repo: karmada-io/website


text:
Update README.md

This project aims to achieve the same performance as llm.c and making the resulting code maintainable, e.g., turning the While loops generated from c2rust into For loops, which enables the parallelization through the rayon library.

cool! :)

authors: karpathy yijunyu


text:
Class kartik\switchinput\SwitchInput not found

i am new to yii2, i have integrated this widget as instructed in doc but it i have this error "Class kartik\switchinput\SwitchInput not found". i am using yii2 advanced template and the extension is placed on root vendor folder. where do i fix the path for this extension? please help. Thanks!!!

Install composer require kartik-v/yii2-widgets "*"

use kartik\switchinput\SwitchInput;

authors: a-M-i-T pievealessandro sorinpohontu


text:
How to call a Detail Activity

How to Call a CustumerDetail, for update and delete?
override fun onBindViewHolder(baseHolder: RecyclerView.ViewHolder, basePosition: Int) {
super.onBindViewHolder(baseHolder, basePosition)
val position = baseHolder.adapterPosition
when (getItemViewType(basePosition)) {
VIEW_TYPE_ITEM -> {
val holder = baseHolder as CustomerViewHolder
val item = items[position] as Customer
val binding = holder.binding
binding.customer = item
if (!binding.root.hasOnClickListeners()) {
binding.root.setOnClickListener {
// val clickedPosition = holder.adapterPosition
// val clickedItem = items[clickedPosition] as Customer
}
}
}
}
}

Hello @blfernandez
There is no Customer Detail Activity in Sample app.
You can surely add one, by passing the customer object (POJO) to new CutsomerDetailActivity / CustomerDetailFragment and display customer details

Ready


text:
Quarto FollowUp

Make Ben's requested changes from PR https://github.com/kaskada-ai/kaskada/pull/799

[ ] Consider improving the CI flow
[ ] Add an _extensions README.md
[ ] Move Slack-Join URL to a variable
[ ] Attempt to move index text to separate files
[ ] Add a _scripts README.md
[ ] Re-add comments to the bluesky example
[ ] Convert the reddit example to qmd
[ ] Adjust spacing of docstrings for aliases
[ ] Create Issue/PR to on include-code-files extension to support start & end tags
[ ] Add a comment to the commented-out fields
[ ] Refactor the card template to not require design-styles.css
[ ] Move announcement text to a variable

repo: kaskada-ai/kaskada


text:
Kata Containers 1.7.2

Version bump no changes

/test

authors: bergwolf egernst

repo: kata-containers/agent


text:
Adding: Firecracker Client API Support

Adding the firecracker client API support.  This is in preparation of firecracker support in Kata containers.
This includes the swagger definition, auto generated code and the vendoring of packages required by this code.
This does not include the actual implementation of the hypervisor interface which will be done in subsequent commit.

What's the relationship between this package and the FC client offered by aws team (https://github.com/firecracker-microvm/firecracker-go-sdk)? Is the official one missing some key functionality for us to use?

What's the relationship between this package and the FC client offered by aws team (https://github.com/firecracker-microvm/firecracker-go-sdk)? Is the official one missing some key functionality for us to use?

I have same question with @bergwolf , can we just vendor firecracker client and re-use it?

We could just exclude the licence checks from the auto-generated virtcontainers/pkg/fireclient package by updating:

https://github.com/kata-containers/tests/blob/master/.ci/static-checks.sh#L355

Closing this in favor of https://github.com/kata-containers/runtime/pull/1044
This directly vendors the firecracker-go-dsk

authors: WeiZhang555 bergwolf jodh-intel mcastelino

repo: kata-containers/runtime


text:
cli: Backtrace on SIGUSR1

Rework the signal handling code to backtrace on receipt of SIGUSR1
but continue to run.
Added some basic tests for the signal handling code.
Fixes #241.
Signed-off-by: James O. D. Hunt james.o.hunt@intel.com

Ping @bergwolf, @sboeuf.

Updated branch to only backtrace on SIGUSR1 when debug enabled at @sboeuf's suggestion.


text:
ReferenceError: WaveSurfer is not defined

Hello,
I have noticed that a new version of wavesurfer.js has appeared in the src folder of github, so I downloaded it and started using it. But I get an error.
Error message in Firefox Console: ReferenceError: WaveSurfer is not defined
Code to produce the error:
<script src="js/wavesurfer.js"></script>
	var wavesurfer = WaveSurfer.create({
    container: container_id,
    waveColor: 'violet',
    progressColor: 'purple',
    scrollParent: true,
    plugins: [
    	WaveSurfer.regions.create({})
    ]
});

Operating System: Win10 Prof.
Browser: FireFox 70.0 32bit
Any help is appreciated.
best regards
Jim

hi Jim, you should download the latest release (https://github.com/katspaugh/wavesurfer.js/archive/3.2.0.zip), unpack it and follow these instructions to create a proper wavesurfer.js file: https://github.com/katspaugh/wavesurfer.js#development
npm install
npm run build

or use a CDN like unpckg or cdnjs.

Hi Thijs,
I followed your instructions and now wavesurfer.js-3.2.0 is working.
Thank you very much.
best regards
Jim
At 2019-10-29 19:30:31, "Thijs Triemstra" notifications@github.com wrote:
hi Jim, you should download the latest release (https://github.com/katspaugh/wavesurfer.js/archive/3.2.0.zip), unpack it and follow these instructions to create a proper wavesurfer.js file: https://github.com/katspaugh/wavesurfer.js#development
npm install
npm run build
or use a CDN like unpckg or cdnjs.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


text:
Exception At Address: 0x7084DE82 Module: (pawnraknet.DLL)

20.45-RakNet插件崩溃日志.txt
I've put together the error output from the console, and the log of the crash.

It looks like you incorrectly use BS_ReadValue in your script.

authors: WeiduXx katursis


text:
Enhanced RxBus

Nice repo! Also really simple and easy approach to achieve Pub-Sub pattern in RxBus.
would you consider enhancing the example with smth like https://github.com/apptik/rxHub ?
I would be more than happy to provide a PR.

hey @djodjoni ! thanks for the pointer. honestly, i want to keep this examples as lean and crazy simple as possible. rxHub looks pretty cool but i want to stick with a drop dead Subject for this example (just so everyone understand the working better)
Cheers and thanks!

authors: djodjoni kaushikgopal

repo: kaushikgopal/RxJava-Android-Samples


text:
MS prefix

Why do you use MS prefix everywhere?
Is this repo sponsored by Microsoft? ;-)

:P Movie Search ™

authors: dawidhyzy kaushikgopal

repo: kaushikgopal/movies-usf


text:
マークダウンから作成日時を削除する

そこだけアップデートされてしまうので。

3e7d5d238aa4d97abc99abf40b31b6d2fc21654e

表示上問題なさそうなのでクローズ

repo: kawaguti/ScrumFestMapViewer


text:
Viết lại các hàm của fca trên promise & tương thích với kb2abot (helpers/fca.js)

Cơ chế nhắn tin mới sẽ là 1 hàng chờ, hàm mới trong thư viện sắp tới sẽ bỏ vào, base sẽ đẩy ra mỗi 100 milisecond
-> Chuẩn bị cho kb2abot-api

or just wait for fb.js, totally based on promise <(")

All

@BadAimWeeb when?

idk

V3 added (util/fca.js)

authors: BadAimWeeb Hieu299 khoakomlem


text:
Only use service clients from narrative-utils

There's a few that are hacked together in this repo that shouldn't be.

Can't completely do this right now, at least not for the dynamic service clients. Those use a configuration in narrative-utils to hit the service wizard, which is hard-coded to CI.
The other service clients should be doable, though.

repo: kbaseIncubator/dashboard-redesign


text:
tests: fix clap_app! doctest

I need these changes to get all of the tests to pass on Linux.

Changes Unknown when pulling e635658dad391f642bdc6b8da6891a36d26d9b9d on pkgw:pr-testfix into ** on kbknapp:master**.

Thanks! @homu r+

:pushpin: Commit e635658 has been approved by kbknapp

:zap: Test exempted - status

authors: coveralls homu kbknapp pkgw

repo: kbknapp/clap-rs


text:
Implement much convenient controller syntax

New syntax for creating controllers:
Paloma.controller('Users', {
  index: function(){
    alert("do something");
  },

  show: function(){
    alert("do something");
  }
});

Syntax for inheritance:
Paloma.controller('Admins < Users', {
  index: function(){
    alert("do something");
  }
});

Implemented on version 5.0.0

repo: kbparagua/paloma