Error on forward message

Description
Hello! I'm getting the following error when trying to forward a message
rror: 2021-06-28T05:27:53.391Z Cannot read property '_serialized' of undefined - TypeError: Cannot read property '_serialized' of undefined     at forwardMessages (/opt/wppconnect-server/src/controller/deviceController.js:327:23)     at processTicksAndRejections (internal/process/task_queues.js:97:5) error: 2021-06-28T05:28:00.496Z message is missing critical data needed to download the file. - Error: message is missing critical data needed to download the file.     at Whatsapp.<anonymous> (/opt/wppconnect-server/node_modules/@wppconnect-team/wppconnect/dist/api/whatsapp.js:319:35)     at step (/opt/wppconnect-server/node_modules/@wppconnect-team/wppconnect/dist/api/whatsapp.js:64:23)     at Object.next (/opt/wppconnect-server/node_modules/@wppconnect-team/wppconnect/dist/api/whatsapp.js:45:53)     at /opt/wppconnect-server/node_modules/@wppconnect-team/wppconnect/dist/api/whatsapp.js:39:71     at new Promise (<anonymous>)     at __awaiter (/opt/wppconnect-server/node_modules/@wppconnect-team/wppconnect/dist/api/whatsapp.js:35:12)     at Whatsapp.decryptFile (/opt/wppconnect-server/node_modules/@wppconnect-team/wppconnect/dist/api/whatsapp.js:311:16)     at getMediaByMessage (/opt/wppconnect-server/src/controller/sessionController.js:217:33)     at processTicksAndRejections (internal/process/task_queues.js:97:5) error: 2021-06-28T05:28:01.719Z message is missing critical data needed to download the file. - Error: message is missing critical data needed to download the file.     at Whatsapp.<anonymous> (/opt/wppconnect-server/node_modules/@wppconnect-team/wppconnect/dist/api/whatsapp.js:319:35)     at step (/opt/wppconnect-server/node_modules/@wppconnect-team/wppconnect/dist/api/whatsapp.js:64:23)     at Object.next (/opt/wppconnect-server/node_modules/@wppconnect-team/wppconnect/dist/api/whatsapp.js:45:53)     at /opt/wppconnect-server/node_modules/@wppconnect-team/wppconnect/dist/api/whatsapp.js:39:71     at new Promise (<anonymous>)     at __awaiter (/opt/wppconnect-server/node_modules/@wppconnect-team/wppconnect/dist/api/whatsapp.js:35:12)     at Whatsapp.decryptFile (/opt/wppconnect-server/node_modules/@wppconnect-team/wppconnect/dist/api/whatsapp.js:311:16)     at getMediaByMessage (/opt/wppconnect-server/src/controller/sessionController.js:217:33)     at processTicksAndRejections (internal/process/task_queues.js:97:5) error: 2021-06-28T05:28:23.495Z Cannot read property '_serialized' of undefined - TypeError: Cannot read property '_serialized' of undefined     at forwardMessages (/opt/wppconnect-server/src/controller/deviceController.js:327:23)     at processTicksAndRejections (internal/process/task_queues.js:97:5) error: 2021-06-28T05:45:57.974Z Cannot read property '_serialized' of undefined - TypeError: Cannot read property '_serialized' of undefined     at forwardMessages (/opt/wppconnect-server/src/controller/deviceController.js:327:23)     at processTicksAndRejections (internal/process/task_queues.js:97:5) error: 2021-06-28T05:45:58.176Z Cannot read property '_serialized' of undefined - TypeError: Cannot read property '_serialized' of undefined     at forwardMessages (/opt/wppconnect-server/src/controller/deviceController.js:327:23)     at processTicksAndRejections (internal/process/task_queues.js:97:5) error: 2021-06-28T05:58:15.774Z Cannot read property '_serialized' of undefined - TypeError: Cannot read property '_serialized' of undefined     at forwardMessages (/opt/wppconnect-server/src/controller/deviceController.js:327:23)     at runMicrotasks (<anonymous>)     at processTicksAndRejections (internal/process/task_queues.js:97:5)
Another problem with this method is when i try to forward big files like 80MB+, the webhook crashed for some reason and i need to restart the server to get it work.

bug fixed


Atom mapping

fixing issues with atom mapping when not using vacuum phase simulations

This PR:

Automatically renders atom-mappings for all simulated legs (which should be identical) automatically when relative simulations are run
Uses oemol object, rather than string when running the topology proposal, which is more robust
Moves to a more robust dictionary object for storing atom mappings


Fix typos in comments

Fix a few misspellings.
Add missing doc comments.
@mbhinder @variadico

LGTM!


Allow to manually add modules for DllPlugin

@ctrlplusb
I think we must enhance the dll's vendor by allowing to manually include modules.
The main purpose is to be able to manually add modules in the dll to reduce re-compilation times of the client bundle.

Related to enten/tension#9
Commits 0c137387, 89a7b5a8 and aeeac540 add that enhancement in tension
With this enhancement I reduce by 50% the re-compilation times of my client bundle by manually add core-js polyfill files (imported by babel-polyfill) and intl /react-intl translation files.

Context
I encountered huge re-compilation times caused by usage of babel-polyfill and react-intl (and intl).
The current modules detection (which will be passed to the DllPlugin) can't (and shouldn't) caught all imports which may be include in the dll.
So we need an option to manually add modules in the dll to reduce re-compilation times.
Proposal
I suggest a new devVendorDLL's option (in config/private/project.js) called includes.
This option receive an array of files path patterns. These patterns will be resolved (only if it contains joker "*" char, else it's not a pattern but just a file path) and merge to modules paths in buildVendorDLL().
Use case example
devVendorDLL: {
  enabled: true,
  // ...
  includes: [
    'fbjs',
    'intl/locale-data/jsonp/*.js'
  ]
}

In the example above:

fbjs will not be resolved because it's not a file path pattern
intl/locale-data/jsonp/*.js will be resolved

So, the includes declarations above will be resolved into:
[
  "fbjs",
  "intl/locale-data/jsonp/af.js",
  "intl/locale-data/jsonp/af.-NA.s",
  "intl/locale-data/jsonp/af.-ZA.s",
   // ...
]

Some amazing insights and advice here @enten - you are super helpful yet again.  I really appreciate you taking the time to post this issue.

We could use something similar to how msbtr's react-boilerplate uses the DLL Plugin.
https://github.com/mxstbr/react-boilerplate/blob/master/internals/config.js
https://github.com/mxstbr/react-boilerplate/blob/master/internals/webpack/webpack.dll.babel.js
Everything for the DLL's is pulled via what's in the package.json and additional includes that you manually add, such as core-js

My plan is to to tackle the aforementioned DLL modification today.

Awesome @strues - just saw this now.  Looks like a great move!
Always up for anything that is simpler and/or less magical. :)

PoC is working. Allows both inclusion / exclusion. Also removes a lot of vendorDLL code.

Staged.


Add options argument to ProvidePlugin

Brings finer control over exactly what resources will be affected by ProvidePlugin.
For instance, I might only want to provide window.jQuery to a single module, and have it evaluate to undefined everywhere else.

Please add an test...


Handle multiple comma separated actions.

Parser configuration
parse('github')
Text to parse
Fixes #1,#2
Current Behavior
{ actions:
   [ { raw: 'Fixes #1',
       action: 'Fixes',
       slug: undefined,
       prefix: '#',
       issue: '1' } ],
  refs: [ { raw: '#2', slug: undefined, prefix: '#', issue: '2' } ],
  duplicates: [],
  mentions: [] }

Expected behavior
Should return 2 actions instead of 1 action and 1 ref.

I don't think so. In a GitHub PR if you add Fixes #1,#2, when merging the PR only #1 will be closed.
So GitHub in such case GitHub applied the Fixes keyword only to the first one.
See https://github.com/pvdlg/test-sr/pull/10. If you hover your cursor above the Fixes GitHub will show a popup saying only #10 will be closed.

Hmm makes sense.
I guess this could be something GitHub could look into?
IMO Fixes #1,#2 is more concise and apt as opposed to Fixes #1 Fixes #2
What do you think?

The syntax to close multiple issues is explicitly mentioned in the GitHub doc: https://help.github.com/articles/closing-issues-using-keywords/#closing-multiple-issues.
So I guess this is intentional and thought through. So I don't think GitHub would change it.
Regarding issue-parser the objective is to exactly mimic GitHub so one can find out from the description of a PR what issue was or will be closed on merge. So independently of opinions and preferences about the syntax, the reference is how GitHub (or GitLab, Bitbucket) parse issues/PRs.
As the behavior is expected I'll close the issue.


Actual and expected values are swapped

When a test fails, the actual and expected values are swapped.
E.g., try using this (wrong) implementation for sieve:
: primes \ n -- a
  drop [1]
;

The output is:
    Actual:    « [1]»
    Expected:  «1»

@axtens is this something you can fix?

You'll have to give me more context. As defined, you've created a word that purports to find a number of the stack and replace it with an array. And in the body of the definition you drop the number and then push a single-element array containing 1 in its 0-th element.

And bin/run-no-docker sieve passes everything. Are you asking for a test that will fail?

"must fail"
    [1]
    ( 1 primes )
    equal?

must fail  ... FAIL
Actual:    « []»
Expected:  « [1]»

So not sure what you're asking

It's probably an issue on my side, sorry!


Plan v5 Release

[ ] Update Node support
[ ] https://github.com/ember-cli/ember-cli-terser/pull/319

Going to close this as we are not using ember-cli-terser anymore at work.


fix the wrong age default value in docs

In scheduler.py
default_schedule = {
        'priority': 0,
        'retries': 3,
        'exetime': 0,
        'age': -1,
        'itag': None,
    }

default age value is -1.
and in on_old_request
elif schedule_age >= 0 and schedule_age + (old_task.get('lastcrawltime', 0) or 0) < now:
            restart = True

age=0 means always recrawl.
The document  says,

age - the term of validity of the task. The page would be regarded as not modified during the term. default: 0(never recrawl)

that is wrong.

Yes, I changed the strategy without updated the documentation, thank you.


Request: New setting to pass the actual Init Image resolution to custom ComfyUI workflow

This issue is based on discussion #242 👍🏻
When using a custom workflow to create an image upscale workflow, then using the Generation tab to upscale an image via Init Image, it seems Swarm doesn't send the image's actual resolution to the workflow, instead it sends over a resized resolution.
In the discussion topic example above, the test image I've been using is 1152x869 (an SDXL 4:3 image created by Swarm). When this image is sent to Init Image and then to the custom workflow, by clicking Generate, the debug logs report the image as being only 658x512. Using a 1024x1024 image as the Init Image doesn't work either. It reports the resolution as 512x512. This doesn't happen if you upload the image directly to the Load Image node in the editor and use the custom workflow directly to upscale.
This issue is especially annoying when you have created the image using one of the supplied aspect ratios in Swarm, yet this isn't passed to the custom workflow you want to use. Is it caused because I was using the larger SDXL sizes?
Is it possible fix this issue or perhaps add a setting in Swarm to send the actual image resolution of the Init Image to the custom workflow?
Many thanks,
James

This is a perfect demonstration of why there's automatic resizing btw:
the test image I've been using is 1152x869 (an SDXL 4:3 image created by Swarm)
If that image was sent in raw (unresized), it'd be erroneous - all images must have pixel sizes as a multiple of 8 to encode properly in the VAE, which of course 869 is not. At best you get it silently rounded away in the background, or at worst you get a fatal error and the workflow can't process at all, depending on which nodes follow.

Ahhh apologies...I meant 1152x896, my bad! 😬
As I mentioned in my original post, I also tried it with the default SDXL image size of 1024x1024. When Swarm sent this Init Image to the custom workflow it resizes it down to 512x512, for some reason.

With the new SwarmInputImage node, you can take a custom image input, and choose whether or not to autoresize it with the auto_resize toggler on the node


No module named util

I had try many ways to install baselines,however they didn't work.mujoco-py has been installed,I wonder know why there is such mistake.Please share some solutions ,thanks a lot!!!
baselines$ pip install -e .
Obtaining file:///home/zlj/%E4%B8%8B%E8%BD%BD/baselines
Requirement already satisfied: gym[atari,classic_control,mujoco,robotics] in /usr/local/lib/python2.7/dist-packages (from baselines==0.1.5)
gym 0.9.5 does not provide the extra 'robotics'
Requirement already satisfied: scipy in /usr/local/lib/python2.7/dist-packages (from baselines==0.1.5)
Requirement already satisfied: tqdm in /usr/local/lib/python2.7/dist-packages (from baselines==0.1.5)
Requirement already satisfied: joblib in /usr/local/lib/python2.7/dist-packages (from baselines==0.1.5)
Requirement already satisfied: zmq in /usr/local/lib/python2.7/dist-packages (from baselines==0.1.5)
Requirement already satisfied: dill in /usr/local/lib/python2.7/dist-packages (from baselines==0.1.5)
Requirement already satisfied: progressbar2 in /usr/local/lib/python2.7/dist-packages (from baselines==0.1.5)
Requirement already satisfied: mpi4py in /usr/local/lib/python2.7/dist-packages (from baselines==0.1.5)
Requirement already satisfied: cloudpickle in /usr/local/lib/python2.7/dist-packages (from baselines==0.1.5)
Requirement already satisfied: tensorflow>=1.4.0 in /usr/local/lib/python2.7/dist-packages (from baselines==0.1.5)
Requirement already satisfied: click in /usr/local/lib/python2.7/dist-packages (from baselines==0.1.5)
Requirement already satisfied: numpy>=1.10.4 in /usr/local/lib/python2.7/dist-packages (from gym[atari,classic_control,mujoco,robotics]->baselines==0.1.5)
Requirement already satisfied: requests>=2.0 in /usr/local/lib/python2.7/dist-packages (from gym[atari,classic_control,mujoco,robotics]->baselines==0.1.5)
Requirement already satisfied: six in /usr/local/lib/python2.7/dist-packages (from gym[atari,classic_control,mujoco,robotics]->baselines==0.1.5)
Requirement already satisfied: pyglet>=1.2.0 in /usr/local/lib/python2.7/dist-packages (from gym[atari,classic_control,mujoco,robotics]->baselines==0.1.5)
Requirement already satisfied: atari_py>=0.1.1 in /usr/local/lib/python2.7/dist-packages (from gym[atari,classic_control,mujoco,robotics]->baselines==0.1.5)
Requirement already satisfied: Pillow in /usr/local/lib/python2.7/dist-packages (from gym[atari,classic_control,mujoco,robotics]->baselines==0.1.5)
Requirement already satisfied: PyOpenGL in /usr/local/lib/python2.7/dist-packages (from gym[atari,classic_control,mujoco,robotics]->baselines==0.1.5)
Collecting mujoco_py>=1.50 (from gym[atari,classic_control,mujoco,robotics]->baselines==0.1.5)
Using cached mujoco-py-<IP_ADDRESS>.tar.gz
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-build-j8QcDU/mujoco-py/setup.py", line 2, in
import importlib.util
ImportError: No module named util
----------------------------------------

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-j8QcDU/mujoco-py/

I have the same problem! I only need Atari environment but I don't know how to install it...

Use python 3, do not use python2

As @qingzhouzhen pointed out, you need to use python3 (specifically, I have tested it with python3.5 and 3.6). For general package sanity, we recommend using a virtualenv (this will also prevent conflicts between python2 and 3 if you are mainly using former on your machine).
To create and activate the virtualenv, run the following commands:
    pip install virutalenv
    virtualenv env --python=python3
    . env/bin/activate

Whether python3 is being used in a current env can be tested by running python --version
After that, pip install -e . should succeed, and the installation can be tested using pytest runner as follows:
    pip install pytest
    pytest

Common installation problems include missing cmake, openmpi or (for ubuntu) zlib.
On mac os those can be installed via homebrew (https://brew.sh/) as follows:
    brew install cmake openmpi

On ubuntu:
    apt-get update && apt-get install cmake libopenmpi-dev zlib1g-dev

We'll include these instructions in the README as well.

I have a fork for python2 with tests passing here, but its ugly (I.e. forcing named arguments). I will keep it in-sync for a little while, but as python2.7 is EOL anyway its not worth doing a PR.


Problem: make release doesn't work

Solution: Edit Makefile so make release depends on make dist being done first
Note: make dist in turn depends on make clean being done first

Codecov Report

Merging #110 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #110   +/-   ##
=====================================
  Coverage      89%    89%
=====================================
  Files          15     15
  Lines         828    828
=====================================
  Hits          737    737
  Misses         91     91


Improvements in Nebula LLM

Description: Added improvements in Nebula LLM to perform auto-retry; more generation parameters supported. Conversation is no longer required to be passed in the LLM object. Examples are updated.
Issue: N/A
Dependencies: N/A
Tag maintainer: @baskaryan
Twitter handle: symbldotai

lgtm, thanks @toshish!


[BUG] The vGPU allocatable count for a node isn't updated after cluster creation

Describe the bug

When you create a RKE2 cluster from an upstream Rancher cluster it doesn't update the vGPU allocatable list node.status.allocatable after the cluster creation
To Reproduce
Steps to reproduce the behavior:

Create 4 vGPU profiles on a node
deploy a 3 node RKE2 cluster with that vGPU profile
Try to deploy out another 3 node RKE2 cluster and check allocatable

Expected behavior

The allocatable vGPU count should update
Support bundle

supportbundle_314d015f-bac6-449f-a676-14fd3732e576_2024-05-08T22-16-49Z.zip
Environment

Harvester ISO version: v1.3.0
Rancher version: v2.8-head
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): 2 node DL360

Additional context
Add any other context about the problem here.
This is the Harvester side bug for 10948

we should improve the device plugin pcidevices controller to monitor resource usage: https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/#monitoring-device-plugin-resources
additional changes may be needed in the harvester api to federate plugin info from all nodes for rancher to leverage

require-doc

doc: update vGPU doc and mention the feature is available after Rancher version xxx
release note: mention the feature is available after Rancher version xxx

Tested with Harvester v1.4.0-rc2 with Rancher versions

v2.8-68e5d43e449fcd3ef73baf1caee98da6f0104eed-head

v2.9-af2463ff43418024ff86cfd9304836b7074a924a-head

v2.10-fe30db77dab22d42b769c9d88d9410a8044c4066-head


chosenClass doesn't work

It changes class of the ghost element, not dragging element.
Example from readme:
http://jsbin.com/qotoximefo/edit?html,css,js,output

I do not understand what's the problem?

I want to style dragging (floating) element but chosenClass behaves exactly as ghostClass.

+1

+1
Applies the classes to the same div, there's no differentiation between the placeholder and the floating element.

+1 Trying to apply a zoom transform to the ghost element so that it matches the other elements in size. But instead it is applied to the chosen-class.

+1
And the link to the chosenClass demo doesn't really seem to work?
It's hard to understand precisely what is meant by chosen, and I don't feel like the demo explained it anymore than the docs did. This would be a class that gets applied to an item, and not it's ghost, while you're dragging it?

Did anyone find the solution??

the thing floating around isn't even a class for me, i can't find it...

the thing floating around isn't even a class for me, i can't find it...

the thing floating around isn't even a class for me, i can't find it...

You have to create it...

the main problem here is that to get the chosenClass even working you need to activate forceFallback: true...otherwise it creates a clone that isn't customizable

so you got it working??

Yes. These are my settings:
my app:
sortable = Sortable.create($( ".sortable" )[0], {
		tolerance: "pointer",
		containment: $("#container"),
		helper: "clone",
		revert: 200,
		revertDuration: 200,
		animation: 1000,
		forceFallback: true,
		scroll: $("#editbadges")[0],
		chosenClass: 'sortable-chosen',
		ghostClass: 'sortable-ghost',
		zIndex: 1,
		items: "> li",
		cursor: "move"
	});
	$( ".sortable" ).disableSelection();

then edits i made to the original sortable.js at line 586 (opacity):
_appendGhost: function () {
			if (!ghostEl) {
				var rect = dragEl.getBoundingClientRect(),
					css = _css(dragEl),
					options = this.options,
					ghostRect;

				ghostEl = dragEl.cloneNode(true);

				_toggleClass(ghostEl, options.ghostClass, false);
				_toggleClass(ghostEl, options.fallbackClass, true);
				_toggleClass(ghostEl, options.dragClass, true);

				_css(ghostEl, 'top', rect.top - parseInt(css.marginTop, 10));
				_css(ghostEl, 'left', rect.left - parseInt(css.marginLeft, 10));
				_css(ghostEl, 'width', rect.width);
				_css(ghostEl, 'height', rect.height);
				_css(ghostEl, 'opacity', '1'); // HERE
				_css(ghostEl, 'position', 'fixed');
				_css(ghostEl, 'zIndex', '100000');
				_css(ghostEl, 'pointerEvents', 'none');

				options.fallbackOnBody && document.body.appendChild(ghostEl) || rootEl.appendChild(ghostEl);

				// Fixing dimensions.
				ghostRect = ghostEl.getBoundingClientRect();
				_css(ghostEl, 'width', rect.width * 2 - ghostRect.width);
				_css(ghostEl, 'height', rect.height * 2 - ghostRect.height);
			}
		},

This in my style.css doesn't change much but it's also working somehow:
.sortable-chosen {
	opacity: 0.5;
	display: none;
}


TEAM" does not start, the site keeps loading.

Describe the bug
We have an IAM Identity Center account connected to an Active Directory. Users are created in Active Directory, and then AWS directly consumes that data.
When performing attribute mapping from the application created in IAM Identity Center for the "TEAM IDC APP" team, we are stuck on the Federated Sign-In screen without progressing or showing an error.
Upon further investigation, we have noticed that users who are directly assigned in the IAM Identity Center app for the "TEAM IDC APP" team do not have attributes; they only have a user ID. We understand that this is because IAM Identity Center, being connected to AD, retrieves user attributes and data in real-time from the Active Directory.
Is it possible to set up another attribute mapping using Okta, or utilize the user ID provided by IAM Identity Center?
I send some screenshot about what we have and what it´s happend.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@Artimen7 did you configure the attribute mapping for the TEAM application on Identity Center following the steps [here](- https://aws-samples.github.io/iam-identity-center-team/docs/deployment/configuration/idc.html#configure-attribute-mapping) ?

Hello,
Yes, we followed the steps and copied the attributes as is.
To give a little more context, we have two Okta locations, let's call them "Okta1" and "Okta2".
In the Okta1 integration, the Identity Center was integrated directly into Okta, so these attributes work perfectly and the TEAM is working.
In Okta2, the Identity Center is integrated into Active Directory, so the attributes are different (this is in the attached ticket) and I understand that the error is coming from there, as the attributes do not match, and it is trying to run TEAM.
PS: as additional information, we are reading the AWS document and linking to the available attributes, but when changing the "subject" of the application, it breaks and does not load TEAM. I don't know if it is possible to alter it in the code to match the AD attributes, but since we don't know what behavior may occur, we don't do it yet.


Release EgoCVR on Hugging Face

Hello @hummelth 🤗
I'm Niels and work as ML engineer at Hugging Face. I discovered your work through ECCV, congrats! I indexed
your paper page here: https://huggingface.co/papers/2407.16658. The paper page lets people discuss about your paper and lets them find artifacts about it (your dataset for instance) you can also claim the paper as yours which will show up on your public profile at HF.
Would you like to host the datasets on https://huggingface.co/datasets? I see you're using Google Drive for it. Hosting on Hugging Face will give you more visibility, and will also allow people to do:
from datasets import load_dataset

dataset = load_dataset("your-hf-org/ego-cvr")

If you're down, leaving a guide here: https://huggingface.co/docs/datasets/image_dataset. We also support Webdataset, useful for image/video datasets: https://huggingface.co/docs/datasets/en/loading#webdataset.
Besides that, there's the dataset viewer which allows people to quickly explore the first few rows of the data in the browser.
After uploaded, we can also link the datasets to the paper page (read here) so people can discover your work.
What do you think?
Kind regards,
Niels

Hey @NielsRogge,
Thanks for the suggestion. This is a great idea, and we will try to do this in the next 1-2 weeks. A quick question: since we have videos to be uploaded, I assume that we would need to use Webdataset rather than the image_dataset format that you have?

Yes I think webdataset might be the best format here, @mfarre (who works on video models at Hugging Face) has put together a script for uploading: https://github.com/mfarre/hf_pushvideo_dataset/blob/main/snippets.ipynb.
This was also leveraged for the FineVideo dataset, which can be explored here: https://huggingface.co/spaces/HuggingFaceFV/FineVideo-Explorer.


Option for changing component height

No possibility change component height. 40px is hardcoded value

Is it currently possible somehow please ?

Right now you can Just over right the CSS classes and change the height.

Right now you can Just overwrite the CSS classes and change the height.

Can u tell which classes i have to change to edit height? Already a Headache

For me it was the multiselect__tags, originally it was 40px (if you look at source code below)
https://github.com/shentao/vue-multiselect/blob/master/src/Multiselect.vue
::v-deep {
    .multiselect__tags {
        min-height: 100px !important;
    }
}

By changing this, the initial height of the input box becomes larger.
I'm using ::v-deep because I'm declaring this overrirde in a parent component, inside scoped style

For me the best way to do it was this
Note: play with changable lines that have * above to get best match
  .multiselect {
    width: 200px;
    min-height: unset;
    .multiselect__select /*arrow styles*// {
      // if select got too much height chage those
      padding-top: 12px;
      padding-bottom: 12px;
      height: 100%;
    }
    .multiselect__tags /*input warpper*/ {
      background: transparent;
      width: 100%;
      min-width: unset;
      display: flex;
      align-items: center;
      // *
      height: 50px;
      min-height: unset;
      padding-top: 0;
      justify-content: flex-start;
      // *
      padding-left: 12px;
      .multiselect__single,
      .multiselect__placeholder,
      .multiselect__input /*inside input, placeholder and search input */{
        background: transparent;
        margin: 0;
        padding: 0;
      }
    }
  }

Summary for what i did:
removed all static padding placements and rewrite it with flex-box to get more flexibility while changing the height of the input.
I also wanted to write the arrow style but it works for me right now

can i contribute here?

@vidhan63-soe thanks for your offer however you can edit the height via overriding the default CSS classes as discussed previously. There are thoughts around how we should change how the styling of the component should be done, and I believe this is part of that wider discussion.

#891 is closed,so is  there anything i can do as a full-stack developer here that might help


Emulate GeoCAT styling

Shinythemes 'darkly' is quite close, but may need to adjust CSS.

It should be different enough, but agree darkly is close, but may not be accessible complicant.

I think this is good enough so closing this one


Add nvidia to chicoma-cpu

This merge also updates the Omega submodule to latest develop, which is needed to be able to run the CTest utility on Chicoma (because of the need to specify an account).

Checklist

[ ] Testing comment in the PR documents testing used to verify the changes

Testing
I was able to build the Polaris spack environments and build and successfully run Omega with them on Chicoma-CPU with nvidia.  I needed to use the branch from https://github.com/E3SM-Project/mache/pull/185


Sorting tibble data_frames in View pane results in NAs

When Viewing a data_frame from (tidyverse package tibble, attempting to sort by a column in the View pane results in NAs. It does not change the values in the variable, just what is being populated in the View table.
library(tibble)
test = data_frame(x = sample(100, 26), y = sample(LETTERS, 26))
View(test)

and then try to sort by a column.
Version Info
Visual Studio Professional 2015 v. 14.0.25431.01 Update 3
RTVS: 1.1.30627.1321
SessionInfo
R version 3.4.1 (2017-06-30)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 7 x64 (build 7601) Service Pack 1
Matrix products: default
locale:
[1] LC_COLLATE=English_United States.1252 LC_CTYPE=English_United States.437
[3] LC_MONETARY=English_United States.1252 LC_NUMERIC=C
[5] LC_TIME=English_United States.1252
attached base packages:
[1] stats graphics grDevices utils datasets methods base
loaded via a namespace (and not attached):
[1] colorspace_1.3-2 scales_0.4.1 compiler_3.4.1 lazyeval_0.2.0
[5] plyr_1.8.4 gtable_0.2.0 tibble_1.3.3 Rcpp_0.12.12
[9] ggplot2_2.2.1 grid_3.4.1 rtvs_<IP_ADDRESS> rlang_0.1.1
[13] munsell_0.4.3

Related #3771

https://github.com/Microsoft/RTVS/commit/235d2372fc802648005bd71d2291feaf7c2f84f4


[feature request] Can we preload Anyline model

Can we preload Anyline model with Inspire-pack

mark


Add validation of http method through fig/http-message-util

Add validation of http method through fig/http-message-util

OK I realize from the the tests that custom methods are intended to be allowed, although that sounds a bit strange, I'll remove my PR if this is the intention of the package (anyone confirms) ?

Custom methods are perfectly valid and widely used, so yeah, dropping support for them is not.a good idea. 🙂


Add display mode to page

Are you requesting a feature, reporting a bug or ask a question?
Requesting a feature.
What is the current behavior?
Cannot set mode to "display" on page.
What is the expected behavior?
Be able to control mode at page level.
How would you reproduce the current behavior (if this is a bug)?
Provide the test code and the tested page URL (if applicable)
Tested page URL:
Test code
your_code_here

Specify your

browser:
browser version:
surveyjs platform (angular or react or jquery or knockout or vue):
surveyjs version:

@rogereriksen Could you please describe your scenario, why do you need this functionality?
There is already question.readOnly : boolean (default false) property. You may set it to a question. Why do you need it on the page level?
Thank you,
Andrew

Planning to set up a solution where I can have case manager/agent read all responses with view only on first pages and then do some kind of management/evaluation on pages only visible to that role.

@rogereriksen Ok, I have just added it into our TODO list.
Unfortunately, it is not as easy as it seems. There is a Panel/Page concepts. So the readOnly should be on the Panel level as well. Additionally, at the current moment Question doesn't know about Panel or Page it belongs to. It has to be introduced as well.
I mean, it may take some time since we are busy with some other tasks at the current moment. But eventually, we will introduce this functionality.
Thank you,
Andrew

@rogereriksen It has been implemented. Here is the example
Thank you,
Andrew


Select2 elements loses focus on tab. It should focus on next (select2) element.

Go to https://adminlte.io/themes/AdminLTE/pages/forms/advanced.html.
Try focusing on a select2 element, then press tab.
You will see that the focus is not on the next input element.
I am not sure if the problem is with select2 itself or usage of it in admin-lte.
It seems that select2 is not keyboard friendly. I found other select plugin selectize, which is more keyboard friendly.

Related: https://github.com/select2/select2/issues/4971

This is a Select2 issue there is a fix for this.
$('select').on("select2:close", function () { $(this).focus(); });

The other problem with the Tab is  if you do a search then click tab the input will not have the new value, you have to click on Enter... I have to find a solution for this

Hi, check this fix
https://github.com/select2/select2/pull/4427/commits/294e7e664d95eafb7f41264c2b87412ad9aa48fc

@lenamtl, how do I get the fix??

You can manually edit the file since the pull request is not done yet...
I have not test it yet.
SO make a backup first then do some tests

I think this problem is still present


Won't install via pip

Using python 2.7:
; virtualenv erlastic-broken
New python executable in erlastic-broken/bin/python2.7
Also creating executable in erlastic-broken/bin/python
Installing setuptools, pip, wheel...done.
; ./erlastic-broken/bin/pip install basho-erlastic
Collecting basho-erlastic
  Using cached basho-erlastic-2.1.0.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 20, in <module>
      File "/private/tmp/pip-build-nB7_vU/basho-erlastic/setup.py", line 5, in <module>
        from erlastic import __version__ as version
      File "erlastic/__init__.py", line 6, in <module>
        from erlastic.codec import ErlangTermDecoder, ErlangTermEncoder
      File "erlastic/codec.py", line 4, in <module>
        import six
    ImportError: No module named six

python 3.5 gives a similar output.

Fixed in da4f1cf51d6b72de79431e38c67f1f36b0bfbc3f


WIREFRAMES: Build report: user notification outside the report modal

As a user, when I am working in another part of the UI, I want to be notified when the build report is complete and ready to view.
Need to address:

How is the user notified when working in another part of the UI?
How is the user notified when on the Pipeline screen?

Ideas:

Email notification
Alert within ALM UI (can this be dismissed/ directly linked to report)

@jryhanyc - I'd like to close this issue and resolve this through the Notification design process since this affects more than Bayesian.  Ok to close this?

sounds good @catrobson

Closing, as will be handled as part of https://github.com/fabric8io/fabric8-ux/issues/408


 It looks like it's a style checker?

yup! many other node frameworks also use it to fix common issues:
https://codeclimate.com/github/expressjs/express/issues

I see. I looked though it yesterday and a lot of the issues are that there are similar code between our example apps, which of course makes sense, as they are examples. Each example app is stand alone and so is going to have duplicate code. It doesn't seems like Code Climate is going to work for our project layout.


format  when  if  switch exists

VSCode Version: Code 1.8.1 (ee428b0eead68bf0fb99ab5fdc4439be227b6281, 2016-12-19T14:42:49.304Z)
OS Version: Darwin x64 15.5.0
Extensions:

Extension
Author
Version

beautify
HookyQR
0.7.3

crane
HvyIndustries
0.2.2

format-php
Kasik96
1.1.2

theme-setimonokai
SmukkeKim
0.0.1

alignment
annsk
0.3.0

path-intellisense
christian-kohler
1.2.0

vscode-html-css
ecmel
0.0.32

Theme-Trepid
enkrypt
0.0.1

text-transform
florianloch
0.1.0

auto-rename-tag
formulahendry
0.0.11

vscode-phpfmt
guodf
0.0.4

theme-material-theme
jprestidge
1.0.1

theme-chromodynamics
lei
1.0.8

Theme-MaterialKit
ms-vscode
0.1.1

vscode-icons
robertohuertasm
4.3.0

clang-format
xaver
1.0.0

Steps to Reproduce:

@yuxing1994 Issue summary and description is not complete. Can you please provide

What is the issue
How to reproduce it
If possible some samples

Thanks


Use it with Svelte

It would be amazing to use this in a Svelte project.

That's a great idea. I'll work on it!


Create btc45

btc45

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @bobowang2333, @nflaig, @beyondacm, @toursonlk, @minhthanh521308, @fred2khk, @fns123456


12/22 PM Publishing

"paramster" to "parameter" in line 4203

Docs Build status updates of commit 83cf345:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-7.0.0/release-notes-azureps.md
:bulb:Suggestion
View (azps-7.0.0)
Details

docs-conceptual/azps-7.0.0/release-notes-azureps.md

Line 100, Column 152: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'string' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Create distributable TileSet

To create proper tutorials and examples, a custom TileSet image is required.  This is so it can be distributed without worrying about licence and credit.
A 320x320 pixel image is required, consisting of 100 tiles (10x10 grid), each 32x32pixels with no spacing in-between.  Not all of them have to be filled, and this image may be added to at a later stage.
The following should be included:

Grass
Dirt
Sand
Path
Rock (single and a collection)
Tree(s)
Water
House
Transitions (left-to-right, right-to-left, top-to-bottom, left-top corner both ways, etc)

Grass to water
Grass to dirt
Sand to dirt
Sand to grass
Sand to water

Pushing back due to time constraints, will use a basic tileset for now, and this will be used to make the tutorials and examples look good in the furture


Why build clang/llvm rather than from debian pkg?

Building and installing clang...
Cloning into '/src/prod/tools/linux/third-party/../../../../..//deps/third-party/src/clang'...

Are there special features in your clang/llvm/other third-party deps source? Or can we switch to quickly pulling down the pre-built apt-get install clang-5.0 lldb-5.0 from http://apt.llvm.org/ ?
Perhaps can we move to submodules so to formalize/make explicit the dependency on these git branches? e.g. https://github.com/Microsoft/service-fabric/issues/53

See my comments in #55. If you notice in src/prod/tools/Linux/third-party/clang.sh we actually don't pull from upstream clang. We have some necessary fixes to clang that aren't present in the pre-built packages you get from apt-get.

Building from source -- especially for clang is really annoying, and I think it's a contribution barrier for first timers. Note that you only have to build once so the long build time only affects clean builds. Still really annoying. I've been trying vto figure out a good solution to distribute pre-built binaries with out modifications.. but haven't found a satisfactory solution. I think clang is the only one that really takes a long time to build, and we are working on getting our patch into the upstream, so once that happens this might be less of an issue.

I do like the idea of moving to submodules to make our dependencies more explicit. I don't think the script is very robust. I'll see if I can think about any serious concerns with that module and open up conversation on your other issue!

Thanks for the answers. I'm sorry - I normally write issues as I think of questions but try to answer them myself before pressing "Create". I saw the branches. Yeah I'm seeing the clang build time issue. I'll have a look at building some intermediate docker images via CI and submit some PRs back so you can build them + host them yourself.  I'll close this ticket.

@drnic  Not a problem! I am really grateful to see where things are confusing, and where people are having trouble.  It isn't always clear as someone who is already familiar with the system, and does not hit those roadblocks.
We actually were hosting a docker image prebuilt with clang, but we removed it due to potential licensing issues, in addition to that, some people were expressing concern that it could be hard to contribute fixes / modify the 3rd party dependencies if they were prebuilt into the container.  So for example, if you wanted to modify code relating to our integration of the "Babeltrace" dependency, you wouldn't have an easy way to do that.
Before working on the intermediate docker image / CI system, can you open a discussion / issue so we can make sure all the requirements are met? I'd hate to have you put in a bunch of work only to find out we can't use what you did because of a reason that wasn't initially clear (such as licensing issues)


entropy: rpi_pico: implement entropy driver for RP2350

Use get_rand_64() from Pico SDK for entropy.
This is somewhat based on #66764.

Do you have any answer to @yonsch's comment in your previous PR #66764 (comment)?

@yonsch is referring to the fact that RP2040 lacks a hardware random number generator
so it uses other sources as seed.
RP2350 has a hardware random number generator and uses
that in pico-sdk.


Revert "workflows/eval: Add the eval summary as a comment"

This reverts commit 38003ce53b4815bb1bc0250c3fd8de0da741faf9.
I am already overwhelmed with github notifications and this makes the situation even worse.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Ideally it should only output one comment and then modify it continuously. The position it appears should be relatively high so will not be folded by GitHub.

Ideally it should only output one comment and then modify it continuously. The position it appears should be relatively high so will not be folded by GitHub.

It only updates the last comment already. Still when I open a pull request, I will now always get a notification even if no human has responded to my PR.

I will now always get a notification even if no human has responded to my PR.

Yeah. Annoying.
Is there any way to have the bot post the eval results into the PR description / body, maybe replacing a special placeholder in the template?

Don't think github actions have currently permissions to do that.

gh pr edit <NUMBER>  --body "BODY" should work?

I will now always get a notification even if no human has responded to my PR.

Yeah. Annoying.
Is there any way to have the bot post the eval results into the PR description / body, maybe replacing a special placeholder in the template?

Don't think github actions have currently permissions to do that.

gh pr edit <NUMBER> --body "BODY" should work?

Ok. Maybe you can try this in a follow up pull request.

I will now always get a notification even if no human has responded to my PR.

Yeah. Annoying.
Is there any way to have the bot post the eval results into the PR description / body, maybe replacing a special placeholder in the template?

It's possible https://github.com/NixOS/nixpkgs/commit/eff1eee5df763b8d61bcfb1212e1b88a50c42ca1
Demo https://github.com/azuwis/nixpkgs/pull/10

Are you still receiving notifications about those edits or do those happen "silently"?

No notifications.
For reference https://stackoverflow.com/questions/38986589/does-github-send-a-notification-when-an-issue-comment-is-edited

No, you do not get a notification if a comment, issue title, or description is edited or even deleted.

@mention should also get no notifications for edits, according to this:

Per my experiments, if edit a comment to add a @mention, the mentioned user will receive the notification, but only once, regardless of how many edits are done afterward and whether they are @mentioned or not.

Perhaps we can create a commit status instead, I think that's also what ofborg does: https://docs.github.com/en/rest/commits/statuses?apiVersion=2022-11-28#create-a-commit-status

I've made a version that add the eval summary to the Things done lists of the PR template https://github.com/NixOS/nixpkgs/compare/master...azuwis:nixpkgs:push-rnzsmkkzkums, example:

25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.
Eval summary

package: added 0, removed 0, changed 61
rebuild: linux 0, darwin 61

Demo https://github.com/azuwis/nixpkgs/pull/15
I think it's pretty elegant, no notifications, occupy only a little space.
Before opening a PR, I'd like to know what you think.

@azuwis I'm not a huge fan, because at least in a lot of my PRs I completely remove the checkmarks and rewrite appropriate ones myself, and I don't really want CI to mess with that, especially when rebuild count is irrelevant anyways. Also it just seems conceptually wrong, the comment is user-written and not meant for CI output. I'm also concerned on what happens when a user updates the description around the same time as CI, that seems reconcilable, but that shouldn't even be a concern imo.

The data is already available in the summary page for the eval jobs, so arguably a commit status... would not be any more visible than that?

It takes two button presses to get to the summary page (the first one gets you to the details page, and then finding where the summary is is not obvious), while with a commit status it would be a single click that can lead to any page. And people are already used to that from ofborg.

Perhaps we can create a commit status instead, I think that's also what ofborg does: https://docs.github.com/en/rest/commits/statuses?apiVersion=2022-11-28#create-a-commit-status

Good idea, implemented in https://github.com/NixOS/nixpkgs/pull/361973


Add What's New In DevTools (Chrome 80)

Target Live Date: 2019-12-05

[ ] This has been reviewed and approved by @kaycebasques
[ ] I have run npm test locally and all tests pass.
[x] I have added the appropriate type-something label.
[ ] I've staged the site and manually verified that my content displays correctly.

Whoops!
There were 2 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/12/devtools.md#L23 - Common typo found: 'behaviour' Should it be 'behavior'? Please use American spellings. See: https://developers.google.com/style/spelling
src/content/en/updates/2019/12/devtools.md#L94 - Common typo found: 'behaviour' Should it be 'behavior'? Please use American spellings. See: https://developers.google.com/style/spelling

Whoops!
There were 1 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/12/devtools.md#L93 - Common typo found: 'behaviour' Should it be 'behavior'? Please use American spellings. See: https://developers.google.com/style/spelling

Whoops!
There were 14 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/12/webassembly.md#L84 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2019/12/webassembly.md#L54 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L58 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L62 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L30 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L35 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L43 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L48 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L50 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L53 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L54 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L66 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L76 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L78 - Line must be at most 100 characters

Whoops!
There were 14 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/12/webassembly.md#L84 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2019/12/webassembly.md#L54 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L58 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L62 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L30 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L35 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L43 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L48 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L50 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L53 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L54 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L66 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L76 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L78 - Line must be at most 100 characters

Whoops!
There were 15 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/12/devtools.md#L29 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L84 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2019/12/webassembly.md#L54 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L58 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L62 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L30 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L35 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L43 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L48 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L50 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L53 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L54 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L66 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L76 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L78 - Line must be at most 100 characters

Whoops!
There were 16 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/12/devtools.md#L29 - Line must be at most 100 characters
src/content/en/updates/2019/12/devtools.md#L50 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L86 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2019/12/webassembly.md#L55 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L59 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L63 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L30 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L35 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L43 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L48 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L50 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L53 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L55 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L67 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L77 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L79 - Line must be at most 100 characters

Whoops!
There were 16 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/12/devtools.md#L29 - Line must be at most 100 characters
src/content/en/updates/2019/12/devtools.md#L50 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L86 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2019/12/webassembly.md#L55 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L59 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L63 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L30 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L35 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L43 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L48 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L50 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L53 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L55 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L67 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L77 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L79 - Line must be at most 100 characters

Whoops!
There were 26 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2019/12/devtools.md#L29 - Line must be at most 100 characters
src/content/en/updates/2019/12/devtools.md#L50 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L86 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2019/12/webassembly.md#L55 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L59 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L63 - Common typo found: 'm32' Should it be 'Chrome XX'? Do not use 'M' or 'milestone'
src/content/en/updates/2019/12/webassembly.md#L30 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L35 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L43 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L48 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L50 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L53 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L55 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L67 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L77 - Line must be at most 100 characters
src/content/en/updates/2019/12/webassembly.md#L79 - Line must be at most 100 characters
src/content/en/updates/_shared/discover.md#L225 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/_shared/discover.md#L71 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L96 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L97 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L104 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L105 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L109 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L115 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L115 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L79 - Line must be at most 100 characters

:tada: This has been pushed live to https://developers.google.com/web/

:tada: This has been pushed live to https://developers.google.com/web/

Where though? I was expecting https://developers.google.com/web/updates/2019/12/devtools but that's a 404.

Never mind, it's live now.


add data

I'm going to figure out where to put my .csv file

All_Crops_FinalProj.csv
my csv

[ ] create python code for final
[ ] get a copy of the code output to turn in
[ ] get link to GitHub and submit


CSS files by URL

In testing Solid Bootstrap, it'd be really nice to be able to include the Bootstrap CSS in the output. Two natural interfaces:

Button for adding CSS by URL
import the CSS URL in main.ts. Several build processes support this, and the CSS is already available from NPM and via skypack so this would be especially convenient.

Happy to discuss/brainstorm further, here or in Discord, but wanted to write down this request, having needed it a couple times this week.

Does something like https://playground.solidjs.com/?hash=-147837099&version=1.2.6 work for you?

Ah, yes, that does work pretty well. The above e.g. import would be nicer, but only slightly, so not a priority.
Thanks!

I had an idea the other day. Maybe we could have some sort of settings popup page (initially Wordle made me think of it but in retrospective, every sandbox has that).
On the model of Codepen, we could have two text areas, one for inserting stuff in the head of the webview and one for adding stuff at the end of the body.
The issue is that I wonder if there are any security issues...

This works now: https://playground.solidjs.com/anonymous/6d4825f2-8531-4588-8d34-c1383b9b4591


[WIP] Adding in-cluster Prometheus monitoring

Will be only enabled for OpenShift4 clusters
Signed-off-by: Lalatendu Mohanty<EMAIL_ADDRESS>

@LalatenduMohanty this all looks reasonable to me. still WIP b/c you're doing some testing?

Am I correct we should close this as it doesn't actually work until 4.3?

/close


[CLI] - Created a template for a documentation website (Resolves #4)

[CLI] - Created a template for a documentation website (Resolves #4)
Still need support for Algolia search in the template.
Includes support for:

GitHub link
Discord Link
Sponsor Link
Pub API docs link
Contributors list
Global navigation menu
Table of Contents per page
Toggle between light and dark mode

Added working CLI tests for the docs template generation.
Source code includes the following template sections:
/packages/template_docs -> the source of truth for the docs template, in a runnable state

/packages/static_shock_cli/templates/docs -> the docs template with mustache variables for Mason

/packages/static_shock_cli/lib/templates/docs.bundle -> the final bundled docs template that's inflated at runtime

Future templates will need the same pieces as above.
The process for updating a template is as follows:

Alter the runnable template (e.g., /packages/template_docs) until it behaves as intended.
Copy the runnable source files (e.g., /packages/template_docs) to the template source (e.g., /packages/static_shock_cli/templates/docs). Replace all hard-coded values with mustache variables. Replace all Jinja brackets with escaped versions: {{#mustacheCase}} stuff {{/mustacheCase}}
Run mason bundle to create a new bundle from the template source. Move that bundle into /packages/static_shock_cli/lib/templates/.

FYI @angelosilvestre


Why must df_prior and df_post have the same lengths?

I was interested in trying this package out, but immediately got an error ValueError: Lengths must match to compare because my df_prior and df_post have different lengths. What is the rationale behind the length assertion? If I were to compare data in production vs. new data, the new data would always have more rows than the data in production (since new data = latest data + old production data).

I am unable to replicate your issue, have just tried it with df_prior and df_post containing different number of rows and it functions as expected. Might you have a reproducible example to share? Does any columns contain a list type?

Closing issue as no further updates / reproducible example.


docs: extend scrollMargin description

As discussed here https://github.com/TanStack/virtual/discussions/856#discussioncomment-10955571 I would like to update the docs for the scrollMargin argument, so other people will understand better how to properly use it.
My changes only include update for virtualizer.md file

@Wordllban thanks!


Pull Request Template Creation

I am writing to express my interest in contributing to your repository by creating a pull request template.
I believe that having a standardized template will help streamline the contribution process, ensuring that all necessary information is included and making it easier for maintainers to review and merge pull requests.
Could you please assign me the issue under gssoc24? I am excited about the opportunity to contribute to your project and help improve the workflow for all contributors.

I would like to work on this issue. Please assign it to me.

It is already done


Demo Extension : Application product type

This product type should create a application service when added to a project.
Product types should include

Include product and order questions
Service outputs from the provisioning process
Optionally use a service details page override

Went with just maintaining this as a product category for now. Not sure we really need to build out a demo product type for application right now. Closing this for now.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.2 to before v5.15",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=80f3afd72bd4149c57daf852905476b43bb47647",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f9a470db2736b01538ad193c316eb3f26be37d58"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "80f3afd72bd4149c57daf852905476b43bb47647",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "f9a470db2736b01538ad193c316eb3f26be37d58",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "misc: fastrpc: Add missing lock before accessing find_vma()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15 by commit f9a470db2736b01538ad193c316eb3f26be37d58, it was introduced in version v5.2 by commit 80f3afd72bd4149c57daf852905476b43bb47647. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1002150


Add option to disable the volk target

At the moment, the volk target is always created by CMake. However, when VOLK_PULL_IN_VULKAN is OFF, the target is not complete and will not build unless path to Vulkan headers is explicitly added. When VOLK_PULL_IN_VULKAN is OFF, the application most likely only needs the volk_headers target and has to explicitly remove volk from build.
It would be very helpful if there was an option to only define the volk_headers target, e.g. VOLK_HEADERS_ONLY

Something like VOLK_HEADERS_ONLY would make sense as a CMake option. Feel free to contribute a PR!


sap.m.Input description broken (in 1.48.8)

OpenUI5 version: 1.48.8
Browser/version (+device/version): Chrome/61.0 (64Bit)
Any other tested browsers/devices(OK/FAIL): Firefox 55.0.3 (Fail)
Source: <Input value="{tabFinancialModel>planned}" description="{tabFinancialViewModel>/inputCurrency}" />
Steps to reproduce the problem:

I have description on an sap.m.Input bound to a model value in a table cell
If I use version 1.46.12 I see "EUR" behind field, 1.48.8 nothing

What is the expected result?
Expect to see value of inputCurrency as in Version 1.46.12
What happens instead?
Blank after input field
Any other information? (attach screenshot if possible)
See two screenshots, only change is different openUI5 version in index.html.

@fschulten Please modify this example to illustrate the problematic settings -https://jsbin.com/tududiselu/edit?html,output
The example used the latest OpenUI5 and bindProperty of the Input control to apply values from different named models.

I am closing this one as there is no activity in the thread. Feel free to open a new thread linking this issue, if you want to continue the discussion


Enable renovate for gardener/ops-toolbelt

/kind enhancement
What this PR does / why we need it:
With this PR gardener/ops-toolbelt will be watched by renovate 🤖
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

/lgtm
/approve


Add melody refinements

Improved error messages (clarity, fewer silent failures)
/stopsong no longer required to switch to a new melody

/melody with an active melody transitions at end of current song

Additional defensive programming to stop corner cases

Paranoid checking of all pointers
Additional constraints checking on start
Tighter control that songs and current_index are always kept valid (or disabled)
Retry (missed note) logic improvements:
correct wraparound for 0 index retry
retry_count tracking to constrain log spam in error cases
auto-advances to next song if a song fails 8 times, terminates melody if 15 retries w/out success

Melodies now end when sitting (and thus camping, eliminates some corner cases and surprises)

Please take a look when you have time.  I went a little OCD and touched a lot of it to make it as solid as possible (we bards use it a lot), there are just a few rare corner cases that I wanted to improve with some light refactoring of some patches.
The primary intentional changes are above.  I think the majority of bards will appreciate the retry limits (8 is sufficiently generous in my experience).  The melody terminating when sitting could annoy someone, but I couldn't think of a use case where a bard would sit and need to auto-resume melody (versus looting which is common).

Thanks for approving! Just let me know if you want any (now or future) changes, I'm happy to help out with maintaining melody when useful.
I just pushed a trivial second commit to add /mel as an alias.  I'm fine with reverting or modifying it.
Thanks!  Sherra (on DIscord)

Np i'll merge it in when I bring the dev branch in to main


Added Fedora support

Added detection for Fedora linux, as it is similar/equal to RedHat and CentOS.
"Works on my machine".

Awesome! You saved my day.

Thank you @leyrer-ibm for this PR. I created a PR based on yours and tested it. I did so to resolve the conflicts that showed up. Thank you for contributing! 👍 PR#114


Shall we bump version to 0.5.1 or 0.6  for the latest update?

@wu-h , there is just one minor change since 0.5.1. I think we can wait for more changes before creating 0.5.2


Add announcement list

Improve communications by providing an opt-in email list for security and release notifications. Requested by many people who don't have time to follow social media or other noisier channels. This list is only for Bitcoin Core security/release announcements.

Nice, Concept ACK!

ACK, looks good to me

awesome ACK

utACK


kubeshark deployment DOSes kube-apiserver if k8s audit events enabled

We just successfully killed our k8s control plane nodes by deploying the kubeshark. The kubeshark deployment created thousands of k8s audit events thus DOSed the kube api servers which leaded to control plane nodes memory exhaustion. We use audit policy from the k8s documentation https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/.
How can we protect against such events?
I could remove the kubeshark namespace from the audit policy file but is there any more general solution to protect the kube api server and node against audit events DOS?
I analyzed k8s audit events in our ELK before and during the crash and it seems I'm not able to identify any common DOS events which could be filtered-out in the audit-policy.yaml file.
Currently we're gonna to set the

memory limits on kube-apiserver pods so that the kubeshark doesnt't kill the node;
limit hub, sniffer and tracer pods;
target specific namespace.

@MMquant thanks for reporting this. We are actively looking into this and will report back our findings.

Hi @MMquant
I've tried to verify this on our test environment in EKS cluster. (5 t3.large nodes, ~100 pods)

This graph shows a number of audit log events in the cluster.
I installed Kubeshark at 7:30.
There was a little spike in a number of events at this point which stabilized after Kubeshark made its initial discovery. After that, no anomalies in the number of events were detected.
Also, there is no visible additional load on the Kubernetes API server.
We did similar tests before on a cluster with 100 nodes and ~1000 pods and didn't find any issues.
This doesn't prove that there are no such issues though.
Maybe EKS does not have that verbose audit policy, dunno.
Please provide more details on your setup.

Is it cloud, on-prem, some test env with kind/minikube/etc
Number of nodes and approximate number of pods
Nodes resources (CPU, RAM, storage)
Exact audit policy used

Also maybe ELK can provide some details on anomalies? You wrote that no common "DDOS" events were found, but maybe you can provide at least the difference in the count of events before Kubeshark and after.
E.g. average count before Kubeshark was 1k events/s and after Kubeshark was installed - 10k events/s.
That would help us to identify the magnitude of the issue at least.

Is it cloud, on-prem, some test env with kind/minikube/etc

The k8s cluster is deployed on-prem on proxmox. 3 master nodes, 3 worker nodes.

Number of nodes and approximate number of pods

±150

Nodes resources (CPU, RAM, storage)

maple@ubuntu:tk8s-mon$ k top nodes
NAME                               CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%
tk8sm01   423m         10%    4086Mi          53%
tk8sm02   316m         7%     3477Mi          45%
tk8sm03   252m         6%     3216Mi          42%
tk8sw01   381m         4%     11859Mi         37%
tk8sw02   671m         8%     8623Mi          27%
tk8sw03   1051m        13%    18054Mi         56%

Exact audit policy used

https://falco.org/docs/install-operate/third-party/learning/#falco-with-multiple-sources
ELK event count screenshot from opensearch

You can see that normal event rate[5m] is around 6k-7k. When the kubeshark was deployed the rate jumped to 13k.
The empty bars are kube-apiserver crashes. We needed to temporarily disable auditing in the kube-apiserver.yaml so that we would be able to uninstall the kubeshark helm release.
Additionally see the screenshots from Grafana
kubeshark daemonset memory load

kube-apiserver memory load

At the moment we are gonna to test following

upgrade nodes to use cgroup v2
limit the kube-apiserver memory resources so that next time at least the node itself survive
limit the kubeshark memory resources according to the guide https://docs.kubeshark.co/en/performance
scope the kubeshark to specific namespace

You are right that the audit policy definition has huge impact on the amount of the events generated. The one we are using is pretty verbose as it's needed for analysis by Falco.

Thx for the info @MMquant
To confirm if Kubeshark itself generates those events, can you please exclude Kubeshark service account from auditing?
If you installed Kubeshark in the default namespace, this can be done with the rule:
  - level: None
    userGroups: ["system:serviceaccounts"]
    users: ["system:serviceaccount:default:kubeshark-service-account"]

Hi @corest ,
we have just tested the rule and it seems that the rule indeed filtered-out the "DOS events".
However we are concurrently facing another issue with kubeshark which we don't know if it's related to this events issue.
Kubeshark containers are in crashLoopBackoff state
Defaulted container "sniffer" out of: sniffer, tracer
{"level":"debug","time":"2024-02-27T09:24:01Z","message":"packet-capture flag is deprecated!"}
2024-02-27T09:24:01Z INF main.go:75 > Starting worker...
2024-02-27T09:24:01Z INF misc/data.go:25 > Set the data directory to: data-dir=/app/data
2024-02-27T09:24:01Z INF kubernetes/memory/limit.go:47 > Memory limit is set to limit=8301034833169294539
2024-02-27T09:24:01Z INF main.go:106 > Starting worker...
2024-02-27T09:24:01Z WRN kubernetes/resolver/resolver.go:126 > Failed reading the name resolution history dump: error="open /app/data/name_resolution_history.json: no such file or directory" path=/app/data/name_resolution_history.json
2024-02-27T09:24:01Z INF main.go:126 > Linux kernel: version=4.18.0-513.11.1.el8_9.x86_64
2024-02-27T09:24:01Z INF utils/kernel/loader.go:80 > Downloading kernel module: dst=/app/kernel_modules/pf_ring.ko url=https://api.kubeshark.co/kernel-modules/4.18.0-513.11.1.el8_9.x86_64/pf_ring.ko
2024-02-27T09:24:01Z INF kubernetes/resolver/target.go:115 > Targeted pod: ......-01-0
2024-02-27T09:24:01Z INF kubernetes/resolver/target.go:115 > Targeted pod: .......-02-0
2024-02-27T09:24:01Z INF kubernetes/resolver/target.go:115 > Targeted pod: ....dsr7k
2024-02-27T09:24:01Z INF kubernetes/resolver/target.go:115 > Targeted pod: linux-tools
2024-02-27T09:24:02Z WRN main.go:131 > error="bad response code: 404"
2024-02-27T09:24:02Z INF assemblers/tcp_streams_map.go:75 > Using 1000 ms as the close timed out TCP stream channels interval
2024-02-27T09:24:02Z WRN source/tcp_packet_source.go:88 > Can't use PF_RING socket error="pfring NewRing error: address family not supported by protocol"
2024-02-27T09:24:02Z INF source/tcp_packet_source.go:103 > Using AF_PACKET socket as the capture source
2024-02-27T09:24:02Z INF server/server.go:62 > Starting the server... port=30001

@MMquant https://github.com/MMquant The logs don't show a problem. Do you
still experience the containers failing?
Also, one log line implies you're using an older version.
It will be good to test out one of the recent versions (e.g. the latest
one).
On Tue, Feb 27, 2024 at 1:36 AM Petr Javorik @.***>
wrote:

Hi @corest https://github.com/corest ,
we have just tested the rule and it seems that the rule indeed
filtered-out the "DOS events".
However we are concurrently facing another issue with kubeshark which we
don't know if it's related to this events issue.
Kubeshark containers are in crashLoopBackoff state
Defaulted container "sniffer" out of: sniffer, tracer
{"level":"debug","time":"2024-02-27T09:24:01Z","message":"packet-capture flag is deprecated!"}
2024-02-27T09:24:01Z INF main.go:75 > Starting worker...
2024-02-27T09:24:01Z INF misc/data.go:25 > Set the data directory to: data-dir=/app/data
2024-02-27T09:24:01Z INF kubernetes/memory/limit.go:47 > Memory limit is set to limit=8301034833169294539
2024-02-27T09:24:01Z INF main.go:106 > Starting worker...
2024-02-27T09:24:01Z WRN kubernetes/resolver/resolver.go:126 > Failed reading the name resolution history dump: error="open /app/data/name_resolution_history.json: no such file or directory" path=/app/data/name_resolution_history.json
2024-02-27T09:24:01Z INF main.go:126 > Linux kernel: version=4.18.0-513.11.1.el8_9.x86_64
2024-02-27T09:24:01Z INF utils/kernel/loader.go:80 > Downloading kernel module: dst=/app/kernel_modules/pf_ring.ko url=https://api.kubeshark.co/kernel-modules/4.18.0-513.11.1.el8_9.x86_64/pf_ring.ko
2024-02-27T09:24:01Z https://api.kubeshark.co/kernel-modules/4.18.0-513.11.1.el8_9.x86_64/pf_ring.ko2024-02-27T09:24:01Z INF kubernetes/resolver/target.go:115 > Targeted pod: ......-01-0
2024-02-27T09:24:01Z INF kubernetes/resolver/target.go:115 > Targeted pod: .......-02-0
2024-02-27T09:24:01Z INF kubernetes/resolver/target.go:115 > Targeted pod: ....dsr7k
2024-02-27T09:24:01Z INF kubernetes/resolver/target.go:115 > Targeted pod: linux-tools
2024-02-27T09:24:02Z WRN main.go:131 > error="bad response code: 404"
2024-02-27T09:24:02Z INF assemblers/tcp_streams_map.go:75 > Using 1000 ms as the close timed out TCP stream channels interval
2024-02-27T09:24:02Z WRN source/tcp_packet_source.go:88 > Can't use PF_RING socket error="pfring NewRing error: address family not supported by protocol"
2024-02-27T09:24:02Z INF source/tcp_packet_source.go:103 > Using AF_PACKET socket as the capture source
2024-02-27T09:24:02Z INF server/server.go:62 > Starting the server... port=30001
—
Reply to this email directly, view it on GitHub
https://github.com/kubeshark/kubeshark/issues/1500#issuecomment-1966144381,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPGA2JN2QUG4IJ2GIMI7ULYVWSK7AVCNFSM6AAAAABDSVNNBKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRWGE2DIMZYGE
.
You are receiving this because you commented.Message ID:
@.***>

@corest I think we can close this issue can't we?
@alongir The logs I posted have been sorted out by our devops team. Moreover I wouldn't discuss that log error in this issue as I think these things are not related.

@MMquant we will keep this opened for now as I have few things to work on:

Create environment with extensive audit policy + falco to replicate your issue.
Find why Kubeshark generates so many events
Update docs on our side regarding excluding Kubeshar from audit events.

Recreated cluster with 3 nodes and audit policy provided by Falco
Installed Falco, some workloads. Left cluster for 1h. Average rate of audit events - 345 events/minute
Installed Kubeshark and enabled scripts to have some activity. Left for 1h. Average rage of audit events increased to 352 events/minute

Overall in 1h Kubeshark service account generated ~300 events and that is expected and normal.
Also there was no additional visible load on Kubernetes API generated.
So for the case of this issue I think the reason behind high volume of events is very specific to cluster setup and can't be fixed on Kubeshark side as for now.
Last thing for this issue - I'll add section here https://docs.kubeshark.co/en/troubleshooting on how to exclude kubeshark audit events from monitoring
FYI @alongir

Done


Real Time audio recording examples missing

Excuse me, I am working about Digital Signal Processing specifically Modulation and I want to record my voice in real time but I don't know how do that. I tried to look for something in "AudioIO.jl" about my problem but nothing. Could you make some examples about how record audio in real time please ?
PD: My OS: Windows 8         and a VM: Ubuntu 14.0.4

I just started playing with the package myself, no idea if this is the correct way to record from the input, but it works for me. I'd appreciate input from anyone familiar with the module (@ssfrr, @wherrera10, @JayKickliter, @goretkin).
using AudioIO

# Record for 11 seconds
secs = 11

type RecordingRenderer <: AudioIO.AudioRenderer
    active::Bool
    storage::Array{Float32}
    idx::Int

    function RecordingRenderer(length_s::Int)
        new(false, zeros(Float32, 44100 * length_s), 1)
    end
end
typealias RecordingNode AudioIO.AudioNode{RecordingRenderer}

idx = 1
import AudioIO.render
function render(node::RecordingRenderer, device_input::AudioIO.AudioBuf, info::AudioIO.DeviceInfo)
    len = 1024
    idx = node.idx
    node.storage[idx : idx + len - 1] = device_input
    node.idx += len
    return device_input .* false
end

myNode = RecordingNode(secs)
println("Start recording")
AudioIO.play(myNode); sleep(secs); stop(myNode)

println("Plot recording")
using UnicodePlots
display(lineplot(1:length(myNode.renderer.storage), myNode.renderer.storage, width = 50))

println("Start playback")
sleep(1)
player = ArrayPlayer(myNode.renderer.storage)
play(player)
sleep(secs)

output...
Start recording
INFO: Initializing PortAudio. Expect errors as we scan devices
INFO: Scheduling PortAudio Render Task...
INFO: PortAudio Render Task Running...
Plot recording
         ┌─────────────────────────────────────────────────────────┐
    0.26 │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢀⢀⠀⠀⠀⠀⠀⠀⠀⠀⡆⠀⠀⠀⠀│
         │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⢸⠀⠀⠀⠀⠀⡀⠀⠀⡇⠀⠀⠀⠀│
         │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⣿⡆⢠⠀⠀⢠⣷⠀⠀⡇⢸⠀⠀⠀│
         │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⣸⣿⡇⣾⣇⣴⢸⣿⡆⡇⡇⢸⠀⠀⠀│
         │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣇⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⣿⣿⣷⣿⣿⣿⢸⣿⡇⡇⡇⢸⠀⡀⠀│
         │⢀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⣿⡄⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⣿⣿⣿⣿⣿⣿⣿⣿⣇⡇⡇⢸⠀⡇⠀│
         │⣸⡆⠀⠀⠀⠀⠀⠀⢀⣀⣴⣿⣤⣿⣷⣇⡀⣄⠀⢰⠀⠀⠀⠀⠀⢀⠀⠀⠀⢰⣆⠀⠀⢠⣾⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷⣷⢸⣾⣧⡆│
         │⣿⣿⣶⣦⠤⠤⠤⠤⢼⣿⣿⣿⣿⣿⣿⣿⣿⣿⣷⣾⡤⠤⠤⠤⠤⢼⣧⠤⡤⢼⣿⣶⣶⣾⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣾⣿⣿⡇│
         │⢻⡏⠀⠀⠀⠀⠀⠀⢸⡟⠿⣿⣿⣿⣿⡟⠋⠟⠁⢸⠀⠀⠀⠀⠀⠘⠁⠀⠀⢸⠟⠀⠀⠸⢿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡿⢹⣿⣿⠇│
         │⠈⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠉⠀⣿⠋⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⣿⣿⣿⣿⣿⣿⣿⣿⣿⡏⡇⢸⠁⡇⠀│
         │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⡏⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⣿⣿⣿⣿⣿⣿⢹⣿⡇⡇⡇⢸⠀⠁⠀│
         │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠈⣿⣿⡟⣿⡟⢹⢸⣿⡇⡇⡇⢸⠀⠀⠀│
         │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⣿⡇⢹⠁⠈⢸⣿⠀⡇⡇⢸⠀⠀⠀│
         │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⣿⠃⠈⠀⠀⠀⡟⠀⠃⡇⢸⠀⠀⠀│
   -0.25 │⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⢸⠁⠀⠀⠀⠀⠀⠀⠀⠀⠇⢸⠀⠀⠀│
         └─────────────────────────────────────────────────────────┘
         0                                             490000
Start playback

That is a very nice plot!
A fork of AudioIO which I've created uses more simple functions, as in read and write.  An example:
-- coding: utf-8 --
Examples for Julia AudioIO module
using AudioIO
using WAV
CHUNKSIZE = 40960
FORMAT = AudioIO.paInt16
CHANNELS = 2
SRATE = 44100
RECORD_SECONDS = 20
"""
choose the devices for 2 channel IO
"""
function choose_input_output()
devices = get_audio_devices()
indev = -1
outdev = -1
for aud in devices
println("$(aud.device_index) $(aud.name)")
if (aud.max_input_channels == CHANNELS) & (indev == -1 )
indev = aud.device_index
end
if(aud.max_output_channels == CHANNELS) & (outdev == -1)
outdev = aud.device_index
end
end
if indev == -1
info("Appropriate input device not found.")
elseif outdev == -1
info("Appropriate output device not found.")
else
info("Using input device ", bytestring(devices[indev + 1].name),
", number ", devices[indev + 1].device_index,
" and output device ", bytestring(devices[outdev + 1].name),
", number ", devices[outdev + 1].device_index)
end
return indev, outdev
end
"""
read from input
"""
function record_audio(devnum, seconds)
instream = AudioIO.open_read(devnum, CHANNELS, SRATE, CHUNKSIZE)
bufsize = seconds * SRATE * CHANNELS
buf = AudioIO.read(instream, bufsize)
AudioIO.Pa_CloseStream(instream.stream)
buf
end
"""
write to WAV file
"""
function write_as_WAV(buffer, filename="temp.WAV")
fio = open(filename, "w")
WAV.wavwrite(deinterlace_stereo(buffer), fio, Fs=SRATE)
end
"""
interlaced to noninterlaced stereo data
"""
function deinterlace_stereo(buffer)
reshape([buffer[1:2:end]; buffer[2:2:end]],
(floor(Int, length(buffer)/2), 2))
end
INS, OUTS = choose_input_output()
println("Starting recording...")
BUF = record_audio(INS, RECORD_SECONDS)
println("Finished reading from device number $INS")
println("Recording volume was $(mean(abs(BUF))*(100/16783))% of max")
write_as_WAV(BUF)
println("Finished writing to WAV file.")

Nice, I hadn't looked deep enough in to your fork then. But both our previous examples record and then play back. Not really suitable for the original question of real time processing.
Here is an example of processing the incoming audio in real time using Reactive.jl (@shashi) and plotting a naive level meter.
using AudioIO, Reactive

# Set up recording node
#
type RecordingRenderer <: AudioIO.AudioRenderer
    function RecordingRenderer()
        new()
    end
end
typealias RecordingNode AudioIO.AudioNode{RecordingRenderer}

x = Input(convert(Float32, 0.0))
import AudioIO.render
function render(node::RecordingRenderer, device_input::AudioIO.AudioBuf, info::AudioIO.DeviceInfo)
    push!(x, mean(abs(device_input)))
    return device_input .* false
end

# Basic processing
#
SMA(N::Int, buffer = Float32[]) =
 x -> begin
        push!(buffer, x)
        if length(buffer) == N+1 shift!(buffer) end
        round(Int, mean(buffer))
      end
moving_average = SMA(5)

# Run processing
#
myNode = RecordingNode()
println("Start recording")
AudioIO.play(myNode)

t_int = 1/20
solidglyph="█"
hist_vals = zeros(Float32, 4)

for t in 1:t_int:30
    print("\u1b[1G")
    print("\u1b[K")
    val = moving_average(1000*value(x))
    print(string(val, "  |", repeat(solidglyph, val)))
    sleep(t_int)
end
stop(myNode)

Output
INFO: Scheduling PortAudio Render Task...
INFO: PortAudio Render Task Running...
8  |████████

super cool, and I'm glad to see more audio-focused folks using Julia these days! There's currently an AudioInput node defined in nodes.jl that you should be able to pipe to speakers just with play(AudioInput()) (watch out for feedback!)
One cool way to implement this would be an EnvelopeFollower node that could take any other node as input, so you could do EnvelopeFollower(AudioInput()) or EnvelopeFollower(SomeOtherNode())

I think PR #57 addresses this issue.


Jazz up sample scene 'CanvasShadow'

Describe the problem
The scene might be a little hard to read for new users, also it is generally not much to look at and the documentation is missing
Describe the solution you'd like
Cleaning up the scene, apply descriptive panels and add a doc.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

#148


isWXAppInstalled always returns false

I installed the module, added the url scheme to xcode's info url types.
  WeChat.registerApp("wx81bfaa7ead2e5f7d", function (resultOne) {
            console.log(resultOne)
            WeChat.isWXAppInstalled(function (resultTwo) {
                console.log(resultTwo)
            })
        })

resultOne is null, resultTwo is false.
iPhone 6, WeChat 6.3.6, RN 0.14.2, RN-wechat 1.1.1
Any other configuration is required?

Nope, but this seems to be a bug from WeChat iOS SDK, let me reproduce this later, thanks for your report.

@yorkie  is this fixed in 1.1.2 ?

Sorry, I'm still not able to have enough time to take this issue. Perhaps I will take a look this night :-)

fixed.
for iOS9, put these in info.plist
<key>LSApplicationQueriesSchemes</key>
  <array>
    <string>weixin</string>
    <string>wechat</string>
  </array>


Move Dashboard page to the GOV.UK Design System

Description
This adds the dashboard index view in the GOV.UK Design System.
As the like for like implementation didn't really work with both the draft and force published editions taking up half the page
each, i've largely copied the design in Carlos' prototype.
Screenshot

Trello card
https://trello.com/c/1gMHaPpS/19-dashboard-page
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
Follow these steps if you are doing a Rails upgrade.

@davidgisbey
Looks great!
Few comments and suggestions:

Add some more space between the force-published title and the table above (govuk-!-margin-bottom-9 or govuk-!-margin-top-9)
Question: Should it be View? Or should it be Edit for Drafts and Review for force-published?
Recommendation: In the user research, we got feedback about the Guidance taking too much space. Here is a design suggestion with the guidance in the footer instead:

https://gds-wh.herokuapp.com/v2/dashboard/?prototypeVersion=v2
Password: wh1t3h@11

I'm going to hold off on merging the design guidance into the footer because it would take substantial work and i think footers should probably be consistent across the application. We could change this in future but i think it needs more thinking/research and is out of scope for the transition work.

This looks great. Just wondering what happens if there are no documents under the "My draft document" heading


samples: net: http: Remove Arduino-101 config from server

There is not enough memory to run the HTTP server sample
application in Arduino-101 so remove the config file.
Jira: ZEP-2157
Signed-off-by: Jukka Rissanen<EMAIL_ADDRESS>

So that means HTTP can't run on Arduino101? If I want to build  web server on  arduino101 ,what should I do.


small fix: update the POST /ent ex. req with a mapped model key

loved the example(s)
just a small doc change.
just ran cloned and ran this locally, but saw the POST /ent example wasn't referencing a valid model.

Will this be merged?


Rename RequestOptions to DigitalTwinsRequestOptions

We got this feedback during the Java ADT review and it is applicable over here, too

As long as we are talking about consistency, I think we should make the ModelData -> DigitalTwinsModelData  and ModelProperties -> DigitalTwinsModelProperties changes here as well.
The ADT team is not going to make this change in their preview swagger but they have agreed to make the change in the GA swagger.

Any changes in readme, samples/readme, change history?

Samples are up to date since I did a refactor, I'll update the samples readme since they wouldn't get refactored automatically, and sure I'll add this all to the changelog


Ability to facet by delimiter (e.g. comma separated fields)

E.g. if a field contains "Tags,With,Commas" be able to facet them in the same way as _facet_array= lets you facet ["Tags", "With", "Commas"]

Part of #551


Camera hangs up unexpectedly

Hi all, I am using PiCamera 1.12 for creating day timelapse, here is the code:
https://github.com/BruXy/time-lapse-utils/blob/master/snapshot.py
However, after almost a month of continuous usage, I have realized that camera hangs up (yesterday twice) and I need to kill the process with SIGTERM and restart RaspberryPi to be able to use the camera again.
When I tested with pdb, the process hang at  the initialization with picamera.PiCamera() as camera:. The CPU load remained normal (strace raspivid stopped on a futex syscall, but I did not save the output).
I did some brief system check like dmesg, /var/log/messages, but I did not find anything relevant.
I am worried, that it will happen again. Is there any option to check camera state or enable some debug mode to see what it going on?
Regards,
BruXy

Since the report of issue the situation did not happen again. Actually, I am not sure if this was happening for version 1.12, because during problem debugging I probably did pip upgrade.

I have exactly the same problem with version 1.13. Occasionally the camera hangs and when I try to debug it hang at the initialization.

I have exactly the same problem with version 1.13. Occasionally the camera hangs and when I try to debug it hang at the initialization.


maven package should run npm install

Often we forget that a new dependency has been added.  Therefore the build should ensure that the node modules are all installed.

https://mrhanlon.com/posts/using-npm-bower-and-grunt-with-maven/
possibly ...

Hello!
I'm doing something similar for the webpack build  (waltz-ng/pom.xml) - it feels a bit hacky - but seems to be the best way.
     <plugin>
                <!-- Build the front end -->
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>exec-maven-plugin</artifactId>
                <version>1.4.0</version>
                <executions>
                    <execution>
                        <phase>prepare-package</phase>
                        <goals>
                            <goal>exec</goal>
                        </goals>
                    </execution>
                </executions>
                <configuration>
                    <executable>npm</executable>
                    <arguments>
                        <argument>run</argument>
                        <argument>build</argument>
                    </arguments>
                    <environmentVariables>
                        <BUILD_ENV>prod</BUILD_ENV>
                    </environmentVariables>
                    <workingDirectory>../waltz-ng</workingDirectory>
                </configuration>
            </plugin>

/dw