match failed when using #array or ##array instead of #[] and ##[]

Please verify the last 2 matches using karate version 0.9.4:
  Scenario: Match against #array and ##array
    And def response =
    """
    { rows:
      [
      { foo: true, bar: "bar" },
      { foo: false, bar: "bar2"}
      ]
    }
    """
    And def rowSchema =
    """
    {
      foo: "#boolean",
      bar: "#string"
    }
    """
    And match response == { rows: "#[] rowSchema" }
    And match response == { rows: "##[] rowSchema" }
    # the following assertions should also succeed:
    And match response == { rows: "#array rowSchema" }
    And match response == { rows: "##array rowSchema" }

@beloyar777 no, only #[] works. btw #[] foo is a short-cut for #[] #(foo) if you feel the docs need to be fixed, specify

Yes, please. Could you raise some awareness about the difference of #[] and #array and its usage in the documentation? That would be also helpful for all my colleagues!
I was reading the documentation about a month, but I've got the point only today.

#[] is an array (as expected)
#array is an array of JSON/js-like objects

Yesterday I had one more aha moment about string array looping. And it was not obvious at all after reading the whole documentation.
Only now I'm getting the feeling of understanding the whole concept of JSON array.
As I read karate documentation before and read the term JSON array... I just thought... oh, it's most likely an array inside of JSON: { foo: [] }. Now I see, that it's a completely different array. It's like [{ foo: "x"}, {foo: "y"}]...

@beloyar777 you have said a lot of things. please just submit a PR against the readme :)


fix: Add link to example contracts in the monorepo

Adds a link in the getting started - CLI page to the source code of the example contracts.
closes #2178
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[x] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[x] Every change is related to the PR description.
[x] I have linked this pull request to relevant issues (if any exist).

Something weird - admin-merged it


Needs a license file.

Hello,
I'd like to use your library in some homework to give to students. For that to be possible, it needs a clear license.
I'd really appreciate that!

Hey Bryan, that's awesome. I will confess the code is pretty dusty and is probably hiding some corpses, so keep me up to date as your students use it.

Awesome! Thank you so much!


Codec and LogAdapter

Two types that provide a slightly higher level interface to streambed.

So the first attempt to graft this onto streambed-patterns just created a mess in the Cargo manifest as the two have nothing in common.    Will propose a new crate instead called streambed-codec (I can characterise LogAdapter as a CommitLog + Codec.) This is closely tied to to streambed itself (while Ask has no treambed dependencies at all).


Calculated columns can't be used in time filters - Wrong data type

If a calculated column is used as a time column, an error occurs : the WHERE clause is not adapted.
How to reproduce the bug

Create a calculated column with DATETIME type and tick the "time column" checkbox
Create a chart and use this calculated column as time column
Filter on "Last week"
Run
See error

Expected results
The query should run without any problem
Actual results
An error occurs : Error: SYNTAX_ERROR: line 5:20: '>=' cannot be applied to date, varchar(26)
Screenshots
Config

Error

Cause

Environment
(please complete the following information):

browser type and version: Google Chrome Version 103.0.5060.53 (Official Build) (x86_64)
superset version: 1.5
python version: 3.9
node.js version: /
any feature flags active: /

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[X] I have reproduced the issue with at least the latest released version of superset.
[X] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Already present in the earlier versions of Superset

Working as Expected. Got the result that new calculated column passed to time column.
Screenshots:-

Loom video:-
https://www.loom.com/share/341e157f81c943f6ac5943e6a27c9be0

Sounds like we can close this. Thanks again for the help @ShaliniIruvuru !


Email verification

Find out if it's worth it to use some third party email verification service (https://neverbounce.com/ etc.) to verify user emails before they submit.
Even if they're bad, what do we do then - tell them the email is incorrect? If it's incorrect in the first place, it's incorrect for a reason - they don't know it most likely (considering our target demographic), and it'll be discouraging them from completing the request if we tell them to change it. I'll leave this here till I determine if it's better to just accept the occasional bounceback.

Nah


pip install gpflow is not working

Hello,
I created a freshly new virtual environment for GPFlow and trusted pip to solve all my troubles.
However, it installs Tensorflow 1.4, which is not compatible with tensorflow-probabilties 0.9
Could you lend a hand?
Thanks

in your virtual environment, can you type pip -V and paste the output here

Yes, sorry. Meant tensorflow 1.14.
pip -V output: pip 9.0.1 from /home/maldades/venv/gpflow/lib/python3.6/site-packages (python 3.6)
output of pip list after installing gpflow:
absl-py (0.9.0)
astor (0.8.1)
cloudpickle (1.3.0)
dataclasses (0.7)
decorator (4.4.2)
gast (0.2.2)
google-pasta (0.2.0)
gpflow (2.0.0)
grpcio (1.28.1)
h5py (2.10.0)
Keras-Applications (1.0.8)
Keras-Preprocessing (1.1.0)
Markdown (3.2.1)
multipledispatch (0.6.0)
numpy (1.18.2)
pip (9.0.1)
pkg-resources (0.0.0)
protobuf (3.11.3)
scipy (1.4.1)
setuptools (46.1.3)
six (1.14.0)
tabulate (0.8.7)
tensorboard (1.14.0)
tensorflow (1.14.0)
tensorflow-estimator (1.14.0)
tensorflow-probability (0.9.0)
termcolor (1.1.0)
Werkzeug (1.0.1)
wheel (0.34.2)
wrapt (1.12.1)
output while pip install gpflow:
pip install gpflow
Collecting gpflow
  Using cached https://files.pythonhosted.org/packages/26/58/6d23a0f47299782c96d0b769e5ce93e37fc1d6fdaee11280eb8cabed94a7/gpflow-2.0.0-py3-none-any.whl
Collecting numpy>=1.10.0 (from gpflow)
  Using cached https://files.pythonhosted.org/packages/07/08/a549ba8b061005bb629b76adc000f3caaaf881028b963c2e18f811c6edc1/numpy-1.18.2-cp36-cp36m-manylinux1_x86_64.whl
Collecting tabulate (from gpflow)
  Using cached https://files.pythonhosted.org/packages/c4/f4/770ae9385990f5a19a91431163d262182d3203662ea2b5739d0fcfc080f1/tabulate-0.8.7-py3-none-any.whl
Collecting gast<0.3,>=0.2.2 (from gpflow)
Collecting tensorflow-probability>=0.9 (from gpflow)
  Using cached https://files.pythonhosted.org/packages/9b/ed/f587d64127bbb85e539f06a2aace1240b7b5c6b4267bea94f232230551a5/tensorflow_probability-0.9.0-py2.py3-none-any.whl
Collecting scipy>=0.18.0 (from gpflow)
  Using cached https://files.pythonhosted.org/packages/dc/29/162476fd44203116e7980cfbd9352eef9db37c49445d1fec35509022f6aa/scipy-1.4.1-cp36-cp36m-manylinux1_x86_64.whl
Collecting dataclasses (from gpflow)
  Using cached https://files.pythonhosted.org/packages/e1/d2/6f02df2616fd4016075f60157c7a0452b38d8f7938ae94343911e0fb0b09/dataclasses-0.7-py3-none-any.whl
Collecting tensorflow (from gpflow)
  Using cached https://files.pythonhosted.org/packages/de/f0/96fb2e0412ae9692dbf400e5b04432885f677ad6241c088ccc5fe7724d69/tensorflow-1.14.0-cp36-cp36m-manylinux1_x86_64.whl
Collecting multipledispatch>=0.6 (from gpflow)
  Using cached https://files.pythonhosted.org/packages/89/79/429ecef45fd5e4504f7474d4c3c3c4668c267be3370e4c2fd33e61506833/multipledispatch-0.6.0-py3-none-any.whl
Collecting decorator (from tensorflow-probability>=0.9->gpflow)
  Using cached https://files.pythonhosted.org/packages/ed/1b/72a1821152d07cf1d8b6fce298aeb06a7eb90f4d6d41acec9861e7cc6df0/decorator-4.4.2-py2.py3-none-any.whl
Collecting six>=1.10.0 (from tensorflow-probability>=0.9->gpflow)
  Using cached https://files.pythonhosted.org/packages/65/eb/1f97cb97bfc2390a276969c6fae16075da282f5058082d4cb10c6c5c1dba/six-1.14.0-py2.py3-none-any.whl
Collecting cloudpickle>=1.2.2 (from tensorflow-probability>=0.9->gpflow)
  Using cached https://files.pythonhosted.org/packages/ea/0b/189cd3c19faf362ff2df5f301456c6cf8571ef6684644cfdfdbff293825c/cloudpickle-1.3.0-py2.py3-none-any.whl
Collecting grpcio>=1.8.6 (from tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/cf/7a/9744998129fce7e29c5f2d8b0f545913b7383e65d8366fc0ae98d11936af/grpcio-1.28.1.tar.gz
Collecting wheel>=0.26 (from tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/8c/23/848298cccf8e40f5bbb59009b32848a4c38f4e7f3364297ab3c3e2e2cd14/wheel-0.34.2-py2.py3-none-any.whl
Collecting tensorboard<1.15.0,>=1.14.0 (from tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/91/2d/2ed263449a078cd9c8a9ba50ebd50123adf1f8cfbea1492f9084169b89d9/tensorboard-1.14.0-py3-none-any.whl
Collecting tensorflow-estimator<1.15.0rc0,>=1.14.0rc0 (from tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/3c/d5/21860a5b11caf0678fbc8319341b0ae21a07156911132e0e71bffed0510d/tensorflow_estimator-1.14.0-py2.py3-none-any.whl
Collecting absl-py>=0.7.0 (from tensorflow->gpflow)
Collecting wrapt>=1.11.1 (from tensorflow->gpflow)
Collecting google-pasta>=0.1.6 (from tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/a3/de/c648ef6835192e6e2cc03f40b19eeda4382c49b5bafb43d88b931c4c74ac/google_pasta-0.2.0-py3-none-any.whl
Collecting keras-applications>=1.0.6 (from tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/71/e3/19762fdfc62877ae9102edf6342d71b28fbfd9dea3d2f96a882ce099b03f/Keras_Applications-1.0.8-py3-none-any.whl
Collecting keras-preprocessing>=1.0.5 (from tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/28/6a/8c1f62c37212d9fc441a7e26736df51ce6f0e38455816445471f10da4f0a/Keras_Preprocessing-1.1.0-py2.py3-none-any.whl
Collecting astor>=0.6.0 (from tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/c3/88/97eef84f48fa04fbd6750e62dcceafba6c63c81b7ac1420856c8dcc0a3f9/astor-0.8.1-py2.py3-none-any.whl
Collecting termcolor>=1.1.0 (from tensorflow->gpflow)
Collecting protobuf>=3.6.1 (from tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/57/02/5432412c162989260fab61fa65e0a490c1872739eb91a659896e4d554b26/protobuf-3.11.3-cp36-cp36m-manylinux1_x86_64.whl
Collecting werkzeug>=0.11.15 (from tensorboard<1.15.0,>=1.14.0->tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/cc/94/5f7079a0e00bd6863ef8f1da638721e9da21e5bacee597595b318f71d62e/Werkzeug-1.0.1-py2.py3-none-any.whl
Collecting setuptools>=41.0.0 (from tensorboard<1.15.0,>=1.14.0->tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/a0/df/635cdb901ee4a8a42ec68e480c49f85f4c59e8816effbf57d9e6ee8b3588/setuptools-46.1.3-py3-none-any.whl
Collecting markdown>=2.6.8 (from tensorboard<1.15.0,>=1.14.0->tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/ab/c4/ba46d44855e6eb1770a12edace5a165a0c6de13349f592b9036257f3c3d3/Markdown-3.2.1-py2.py3-none-any.whl
Collecting h5py (from keras-applications>=1.0.6->tensorflow->gpflow)
  Using cached https://files.pythonhosted.org/packages/60/06/cafdd44889200e5438b897388f3075b52a8ef01f28a17366d91de0fa2d05/h5py-2.10.0-cp36-cp36m-manylinux1_x86_64.whl
Building wheels for collected packages: grpcio
  Running setup.py bdist_wheel for grpcio ... error
  Complete output from command /home/maldades/venv/gpflow/bin/python3.6 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-ejwmvqts/grpcio/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /tmp/tmp27bkcf3ypip-wheel- --python-tag cp36:
  Found cython-generated files...
  usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: -c --help [cmd1 cmd2 ...]
     or: -c --help-commands
     or: -c cmd --help

  error: invalid command 'bdist_wheel'

  ----------------------------------------
  Failed building wheel for grpcio
  Running setup.py clean for grpcio
Failed to build grpcio
Installing collected packages: numpy, tabulate, gast, decorator, six, cloudpickle, tensorflow-probability, scipy, dataclasses, grpcio, wheel, absl-py, werkzeug, setuptools, markdown, protobuf, tensorboard, tensorflow-estimator, wrapt, google-pasta, h5py, keras-applications, keras-preprocessing, astor, termcolor, tensorflow, multipledispatch, gpflow
  Running setup.py install for grpcio ... done
  Found existing installation: setuptools 39.0.1
    Uninstalling setuptools-39.0.1:
      Successfully uninstalled setuptools-39.0.1
Successfully installed absl-py-0.9.0 astor-0.8.1 cloudpickle-1.3.0 dataclasses-0.7 decorator-4.4.2 gast-0.2.2 google-pasta-0.2.0 gpflow-2.0.0 grpcio-1.28.1 h5py-2.10.0 keras-applications-1.0.8 keras-preprocessing-1.1.0 markdown-3.2.1 multipledispatch-0.6.0 numpy-1.18.2 protobuf-3.11.3 scipy-1.4.1 setuptools-46.1.3 six-1.14.0 tabulate-0.8.7 tensorboard-1.14.0 tensorflow-1.14.0 tensorflow-estimator-1.14.0 tensorflow-probability-0.9.0 termcolor-1.1.0 werkzeug-1.0.1 wheel-0.34.2 wrapt-1.12.1

Hi @AlvaroRCueto, pip version 9.0.1 is out of date (it is from 2016!). Can you please try upgrading pip first: pip install -U pip - the latest version is 20.0.2. Once you've upgraded pip, pip install gpflow should work - so I'll close this issue for now, hope that makes sense to you. Of course if it still doesn't work for you after upgrading pip, please feel free to re-open this issue or make a new one!


Only works on low quality images

Hello, thanks for sharing your work, the results are impressive!
I've compared to other in-painting methods and this gives a very good result, the main issue is width should equal to height and small size 256*256 which is preventing from testing on real world images, can you add support for non square photos?

Thanks for you attention. I'm sorry that there is no plan to study inpainting on non-suqare photos in a short time


Fixed parsing of empty JSON arrays

Parsing failed when they had whitespace characters in them.
Updated test targets to swift 2.2
Fixes #9

The CI failure is due to the update to swift 2.2, I can revert the changes if you would like?

Thanks for the patch, I've fixed this in my own way. Regarding Swift 2.2, I'll accept a PR that also amends the Travis file to use Xcode 7.3 :)


Make Forms Responsive

Forms currently don't work very well on mobile devices (specifically iOS Safari).

Form fields are too small.
Too much spacing between fields

This has been fixed (for now). In the future should look at adding the form footer with nextField/prevField controls back for mobile.


Flex provisioner example.

Move the flex provisioner example from https://github.com/childsb/flex-provision

it won't build with the shared vendor dir after we merge it because they reshuffled client-go and apimachinery repos. Need to rebase on latest external-storage master and fix the errors. I can fix it after we merge

I made the two updates you requested.  As far as the build.....
It works from me building clean--
mkdir -p /opt/go/src/github.com/kubernetes-incubator/
git clone git@github.com:childsb/external-storage.git
cd /opt/go/src/github.com/kubernetes-incubator/external-storage/flex
make

Where are you building that fails because of the shared library?


Added 'X' button in QR Scanner.

Closes #2403

Ok. I'll update the strings usage. As for the "ic_close", I used it but it was shown in white color and thus not visible in the toolbar. Therefor I created new one from the default vector icons provided by MaterialDesign.

If I change it to ic_close it shows as black to me. It's used in the ActionSheetDialog and also appears black there. Could this be a theme-ing issue? Essentially the 'x' you checked in and the 'x' for ic_close are identical data except for sizing (same colour etc). Can you try it again and see if ic_close is indeed white?
Also - I don't mind if, when you create a new class you add your header to the top of the file (in fact, yep that's cool) but please remove your header from the inside of source files, it distracts from the source code maintenance. It's already clear who wrote it from the github logs.
Thanks,
James

Just want to add - in the upcoming dark mode patch, the toolbar icon colors will be fixed. I created new styles that will help with consistency. It might be better not to add new assets. I'll edit these files anyway once it's merged to master :)

Just want to add - in the upcoming dark mode patch, the toolbar icon colors will be fixed. I created new styles that will help with consistency. It might be better not to add new assets. I'll edit these files anyway once it's merged to master :)

So, go with ic_close to ensure it works with the dark mode.

I noticed a weird thing. If I use ic_close then sometimes it shows black and sometimes it shows white. After adding tint in the vector, its working correctly now.

Now it has broken the ActionSheetDialog 'x' which is now white Just leave it as is, and let's let @justindg's re-themeing fix this.

@asif-finimble bump

@JamesSmartCell, I have restored the ic_close to original. Can be merged now.


draw map layers in their correct order when using :with or :without

Hi.
Really enjoying play-clj via Nightmod with my daughter.
This small change makes sure map layers are drawn in the right order. (My path disappeared under the grass layer.)

Thanks!


Add leader task ArchiveStatusCleanup

Mutate archive status from PENDING to UNKNOWN if the job has completed more than N minutes ago and the agent disappeared.
This covers primarily 2 cases:

Agent crashing or partitioned from server after updating the final job status
Old agents that do not include the new logic to update archive status after archiving

Coverage increased (+0.09%) to 93.223% when pulling df17bd8a05dc6d700f23319643a8404110c271d0 on mprimi:GENIE-671-clean-pending-archive-status into f31a0a19f043cdc53e24767cc06c4716956d79f3 on Netflix:master.


Update challenges.ts

Title and Issue number

Title :
Issue No. :
Code Stack :
Close #<issue_no>

Checklist:

[] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md
[] I have updated the Index.html file for my contribution

You have created 3 Pull requests for one challenge and the files are split amkng 3 PRs
This is invalid. Everything should be in one PR.

You have created 3 Pull requests for one challenge and the files are split amkng 3 PRs
This is invalid. Everything should be in one PR.

How can i add three files in 1 pr? i am new sry

Create ine PR and then keep commiting in the sane branch. All new changes will appear automatically
If you want i can Reopen this PR. And then you can keep pushing/comitting in this "patch-1" branch and they will appear here

Yes Please and how can i commit to same pr can you share any doc or video?

Checkout to the branch from where you created the PR. And then simply commit and push.
I am opening this PR. This PR is created from your "patch-1" branch. Try pushing in this "patch-1" branch.


MAINT: lint: enable stacklevel warnings check

Reference issue
https://github.com/scipy/scipy/pull/19604#issuecomment-1836467622 @mdhaber
What does this implement/fix?

Enable rule B028 which checks that warnings have an explicit stacklevel which is not equal to 1.

Additional information
163 violations right now, will clean them up when I have time.

That's what I would have suggested. I'll take a quick look in a bit.

Although maybe private functions should be at least stacklevel=3?

Although maybe private functions should be at least stacklevel=3? Again I'll take a look shortly.

Agree private functions should be >2

I've had a go at making some changes to stacklevel=3 but I've probably missed a few places or included a few I shouldn't have.

thanks for the thorough review @mdhaber ! I've pushed in all of your suggested adjustments.


[Retro] TAG ENV at Kubecon CloudNativeCon NA 2023

This tracking issue is a used to collect async retro items from anyone attended Kubecon NA 2023.
Please use the following template:

KEEP DOING:
MORE OF:
START DOING:
STOP DOING:
LESS OF:
IDEAS:

We will discuss anything added to the issue in an upcoming TAG Meeting.

@leonardpahlke thanks for kicking off this thread!
KEEP DOING: Assembling list of sustainability related talks
MORE OF: Spread the word on how to add your talk to the green talks list. I missed it. Maybe we could add it to a kubecon reminder
START DOING: Maybe we arrange talks or demos for during the TAG meeting at KubeCon to pull people in

KEEP DOING: Being on stage at the keynotes to create visibility
MORE OF: Talks on the associated technology, such as Kepler
IDEAS: Get sponsors that have a green initiative to be identified as having one at their booth

IDEA: Sustainable cloud computing day 0 event next year?

KEEP DOING: plan a meetup and attend major conferences
MORE OF: informal get togethers
START DOING:

have a kiosk / project booth
plan the presence at major conferences earlier & make sure we communicate events not at the event but weeks before

STOP DOING: be desperate for contributors (ideally, contributing to the TAG should be more natural fit. We should continue highlighting, that we look for support and there are a lot of ways to contribute, but we don't need to message in every discussion that we are desperate for contributors)
LESS OF:
IDEAS:

conference checklist (#270)
subteam lead in WG comms to support with TAG ENV presence at events (see charter https://github.com/cncf/tag-env-sustainability/pull/247)

if you find a minute, could you comment your insights @catblade @nikimanoledaki @ams0 🙌

KEEP DOING:  State of the ecosystem talks, one chair/lead, one other member, lots of good conversations.
MORE OF: informal get-togethers, planned ahead, maybe small sponsored breakfast?
LESS OF:  nothing yet... we need more more more.

I know I was not asked but this topic is something that I care about a lot and advocate a lot for so my 2 cents:
KEEP DOING: List of sessions
MORE OF: open spaces session for sustainability, technical details
START DOING: TAG sustainability talks and get interest from the group who wants to participate and then people can submit/participate on rotating basis
LESS OF: general stuff about sustainability
IDEAS: Colocated event (I have already raised this to CNCF waiting for response and will update once I hear something)
so a colocated event, open spaces session, list of people in the TAG attending KubeCOn, Interested in speaking, more content creation around KubeCon, encourage people to submit more sustainable tech talks for Kubecon via slack.

KEEP DOING: Lists of sessions and advocating for the TAG! Specifically the keynote session introduced me to the TAG and made me look up the update session.

MORE OF: More promotion and mentions in and amongst other things from contributors would be great.

IDEAS: Is there any way we can get a sustainability track at KubeCon to quickly see the events? I will bring this up at the Comms WG. It would also be interesting to consider how we can get new people to the zero-day meet up when they don't even know of the TAG yet - i.e. they aren't checking normal comms channels yet!

IDEAS: Write a blog post or create social media content sharing the key learnings from KubeCon.


Rename hadoop_palo_path to hadoop_starrocks_path

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

Thanks for your contribution. @bjmek


ip,bytebuild: disable test suites.

Motivation for this change
ip and bytebuild are currently marked broken because of broken test suites.
Things done
Disabled tests and ran
nix-build --no-out-link -A haskellPackages.ip --arg config '{ allowBroken = true; }'
nix-build --no-out-link -A haskellPackages.bytebuild --arg config '{ allowBroken = true; }'
successfully.

Thanks!


Add description to each page

This is a reminder to add the respective description to each page, which will improve the SEO of the page. This is a minor change and of low priority. If anyone wants to help, PRs are welcome.

Hi, I am interested in resolving this issue. I would like to know if anyone else is already working on it?

Hi @rehmansheikh222, no one has mentioned wanting to work on this, so I believe no one is working on this issue yet.
I am assigning this to you, If you have any questions, feel free to ask. Someone from the team will help you (as soon as we can).

Hi @bjohansebas , thanks for letting me know. I am already working on this. Just I have some questions that I would like to clarify, does adding description to each page means every HTML file and by description, do you mean meta tags or something else.

Hi @rehmansheikh222, I mean adding it to each markdown file where the content is located. For example, on this page https://github.com/expressjs/expressjs.com/blob/gh-pages/en/starter/examples.md?plain=1#L1, you can find the following data:
---
layout: page
title: Express examples
menu: starter
lang: en
redirect_from: "/starter/examples.html"
---

...

It’s about adding the following option and providing an appropriate description for the page
---
layout: page
title: Express examples
menu: starter
lang: en
description: "A description"
redirect_from: "/starter/examples.html"
---

...

The blog posts already contain it in case you want to use them as a reference:
ref:

https://github.com/expressjs/expressjs.com/blob/gh-pages/_posts/2024-09-29-security-releases.md
https://github.com/expressjs/expressjs.com/blob/gh-pages/_posts/2024-10-15-v5-release.md

Okay got it, thanks

fixed by #1672


Request:Changing the endpoint swagger-ui.html

Hello,
thanks  fr the great work.
It would be nice to be able to change the endpoint served when using swagger-ui (swagger-ui.html) trhoug a property config or something like that.
Thanks

Closing this as a duplicate of #1080

You refer to this page from the duplicate one and refer to the original @dilipkrish. This issue is not still resolved.


Convert Kafka Chart values to lowercase

@viglesiasce small cleanup of the Kafka chart to:

use camelCase instead of CamelCase variable names (in fact, some of the values dont work without this fix, namely resources and zookeeper overrides)
Adds explanatory comments to the values.yaml file in the style often found in charts in the stable repo.

Small note: I have another outstanding PR for affinity rules which is also versioned at 0.2.4, so whichever PR gets merged second will need to have its version updated.

/ok-to-test


osra355 setting asterisk on mandatory fields

Some other possibilities for setting * against mandatory fields.

(Partner :name field) Set attribute “require” on input field. Use javascript to add the * onto the associated label. (This has been implemented for  elements only and would need to be extended for other types of input controls).
(Partner :region field) Set "required-field" class on the label which is associated with the mandatory input field.
(Partner :contact_details field) Set "required-group" on the form-group which is a parent of the mandatory input field.
Note that this has just been pushed up for comments, not for merging.

@robbiejackson I like the solution from http://blog.pothoven.net/2012/10/self-marking-required-fields-in-rails.html, which is the only one that would prevent things getting out of sync between the model validations and the views. I would prefer the original approach taken in the blog post of setting a CSS class on required labels rather than appending a asterisk directly, as this would give us more flexibility. I also wonder whether this solution would noticeably slow down form rendering since each label will have to additionally consult the model, though I suspect that the answer is "No".

@nik That was the previous solution I proposed - see pull request 285 (https://github.com/AgileVentures/osra/pull/285) but we agreed not to go down that route for the reasons stated in that pull request.

Thanks for reminding me! It's a shame that that solution did not work for all our use cases.

Will reopen when @robbiejackson returns or if someone takes over the task


broken example test recipe links

Hope this helps.  These links were broken.

[Current coverage][cc-pull] is 98.03%

Merging [#63][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master        #63   diff @@
==========================================
  Files            10         10
  Lines           204        204
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            200        200
  Misses            4          4
  Partials          0          0

Powered by Codecov. Last updated by [0e2b9a8...bbd4d95][cc-compare]
[cc-base-branch]: https://codecov.io/gh/poise/application/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/poise/application/compare/0e2b9a8f34a0033e8931d17123aacc25cd17d975...bbd4d95edaa4bbfe4486b77859e6c274ec79f6a7?src=pr
[cc-pull]: https://codecov.io/gh/poise/application/pull/63?src=pr

Thanks!


Cant monitor my own (sub)domain(s)

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
Hi guys,
Ive tested Uptime Kuma a couple of months ago with docker on my Synology NAS.
Recently, Ive started a couple of services, eg, plex, a public minecraft server. I would like to know if these services ever go down, so I have decided to install and use Uptime Kuma.
I can ping my devices fine but unfortunately my Uptime Kuma times out when I try to monitor them by URL.
Ive tested it on another device, same issue.. I also tested it on the demo from git, where it seems to work just fine.. so it must be something on my own network.. The network config in docker is bridged
Does any1 have any idea why i cant contact my own subdomains to monitor them, Id appreciate any help
Thank you
📝 Error Message(s) or Log
Just timeouts
🐻 Uptime-Kuma Version
1.21.2
💻 Operating System and Arch
Synology DSM7
🌐 Browser
Google Chrome
🐋 Docker Version
20.10.3-1308
🟩 NodeJS Version
14.20.1-1012

Login into docker container and check tracert to these services. By IP and by domain.
Also check ping to domains and see if IP addresses are translated properly.

Could be that you cannot loopback to your own ip address. Search for “hairpin NAT” - depending on your router it can just a simple setting, or it isnt possible at all.


feature(robot-server): protocol session events are published to notification server

Overview
ProtocolSession should send notifications of progress by publishing events to notification server.
Implementation
There is a big dilemma about implementing this ticket.
The ProtocolSession uses the RPC guts to run protocols. That means one way of doing this is to hook into a Broker and pipe events to notification server. This gives us parity with RPC's running of protocols.
A longer term solution would be to hook this into the protocol engine under development. This will definitely have to happen at some point.
Acceptance Criteria

[ ] each step in a protocol run over a ProtocolSession emits an event to notification server.
[ ] Models of protocol events are created in notification package .

Stale ticket, closing in favor of new tickets for this behavior when ready


Update rmb-peer with the latest envelope data

Description
rmb-relay v1.3.0 added a new optional relays field that is part of the Envelope to avoid chain updates delay: https://github.com/threefoldtech/rmb-rs/blob/v1.3.0/proto/types.proto#L75
This new field should have the current relays for the twin sending a request to a relay. It should be a list of relays in the format <hostname>, for example: relay.dev.grid.tf and relay.dev.02.grid.tf. neither protocol or port should be added (wss or :443).
Reference PR and Issue

verified:

the relays field is added to the challenge hash
tested an rmb call between:

zos node at version 3.10.5 that uses rmb-peer version 1.3.0
local client uses the latest rmb-sdk peer
and call succeeded


Prophet Logistic Growth

Thanks for this library. This really makes my workflow a lot easier !!
I am trying to fit a 'logistic' growth model using the Prophet and I'm passing the dataframe containing 'cap' and 'floor' columns to the metadata param. But while fitting the model, Prophet throws an error saying that for a logistic model, it expectcs 'cap' and 'floor' columns. How do i specify which columns in the dataframe should be used for 'cap' and 'floor' ?
When I looked at the code for ProphetEstimator fit function, only the 'time' column and 'y' column gets passed on to Prophet code, no additional columns are passed on.
def fit(self, X, y=None, time_col=TIME_COL, value_col=VALUE_COL, **fit_params):

        super().fit(X, y=y, time_col=time_col, value_col=value_col, **fit_params)

        if self.add_regressor_dict is None:
            fit_columns = [time_col, value_col]
        else:
            reg_cols = list(self.add_regressor_dict.keys())
            fit_columns = [time_col, value_col] + reg_cols

Is this a bug or is there a way to pass the 'cap' and 'floor' columns that I'm missing ?
I couldn't find an example on how to do this in the documentation.
Thanks !!

Hi Venkat, thank for bringing this up. You might be able to work around this by pretending 'cap' and 'floor' are regressors in one of your grid search candidates:

Add 'cap' and 'floor' columns to your dataframe, extending them into the future forecast period.
To your grid search candidates, add a hyperparameter set where 'cap' and 'floor' are regressors. You don't care about the result of this model; it's there only to make the columns available.

Let us know if this works.

Thanks for the response @al-bert.
I did try adding the cap and floor as regressor. But in that case, Prophet threw an error saying that the name 'cap' and 'floor' are reserved.
Below is what I tried initially.
df.columns

Index(['ts', 'y', 'cap', 'floor'], dtype='object')
model_components = ModelComponentsParam(
    seasonality = seasonality,
    growth={"growth_term": ["logistic"]},
)

when I run with the above configuration, I'm getting the below error:
ValueError: Capacities must be supplied for logistic growth in column "cap"

And then I added 'cap' and 'floor' as regressors, similar to the example given here. The cap and floor column values extend into the future as well.
regressors=dict(
    add_regressor_dict={
        "cap": {
            "prior_scale": 10.0,
            "mode": 'additive'
        },
         "floor": {
            "prior_scale": 10.0,
            "mode": 'additive'
        }
    }
)

model_components = ModelComponentsParam(
    seasonality = seasonality,
    growth={"growth_term": ["logistic"]},
    regressors=regressors,
)

and now this gives me the error that 'cap' is a reserved name.
ValueError: Name 'cap' is reserved.

Is this same as what you suggested, Albert ?

Hi Venkat, thanks for those details. Prophet recognizes 'cap' and 'floor' as special column names, but we do not. Perhaps you could try forking the code and add 'cap' and 'floor' to fit_columns?

Sure Albert, I'll give it a shot !!

I did manage to find a temporary work around for the cap/floor issue. I'm passing the 'cap' and 'floor' columns as regressors, same as how I have defined in the previous comment, but in the ProphetEstimator.fit function I'm filtering out 'cap' and 'floor' columns from where the regressors are added to the model.
def fit(self, X, y=None, time_col=TIME_COL, value_col=VALUE_COL, **fit_params):
        ..........
        ..........
        ..........
        # if extra regressors are given, we add them to temporal features data
        # This implementation assumes that the regressor(s) are provided in time series df, alongside target column.
        if self.add_regressor_dict is not None:
            for reg_col, reg_params in self.add_regressor_dict.items():
                if reg_col != 'cap' and reg_col != 'floor':      # ---> Remove 'cap' and 'floor' from the regressor list.
                    self.model.add_regressor(name=reg_col, **reg_params)`

This fix seems to work when I tested on my dataset. But this seems more like a temporary fix. I guess this should be better handled, like passing 'cap' and 'floor' column names via the MetadataParam configuration and these parameters should flow from there.
BTW, I don't see any contribution guidelines or public pull requests yet. Are you accepting any pull requests for now ?

Great to hear! We do plan to accept contributions and will provide guidelines to explain the process.

Contribution guidelines are available here: https://github.com/linkedin/greykite/blob/master/CONTRIBUTING.rst

Thanks Albert. Was bit busy with work, didn't get time to look into this.
When I look into fbprophet's forecaster.py, the reserved names are defined as below:
       reserved_names = [
            'trend', 'additive_terms', 'daily', 'weekly', 'yearly',
            'holidays', 'zeros', 'extra_regressors_additive', 'yhat',
            'extra_regressors_multiplicative', 'multiplicative_terms',
        ]
        rn_l = [n + '_lower' for n in reserved_names]
        rn_u = [n + '_upper' for n in reserved_names]
        reserved_names.extend(rn_l)
        reserved_names.extend(rn_u)
        reserved_names.extend([
            'ds', 'y', 'cap', 'floor', 'y_scaled', 'cap_scaled'])

So apart from the forecast output columns, [ 'ds', 'y', 'cap', 'floor', 'y_scaled', 'cap_scaled'] are the reserved names within fbprophet. Of these, 'ds' and 'y' are already taken care of.
If we have a solution, similar to the one that I had proposed earlier, would that work ?
I would pass the cap and floor as additional regressors in the model config and in the ProphetEstimator.fit function I filter out the columns that matches the reserved columns from being passed on as a regressor. This way the 'cap' and 'floor' columns gets passed on the to the model, but now prophet won't throw an error that the column name is reserved.
Model config
regressors=dict(
    add_regressor_dict={
        "cap": {
            "prior_scale": 10.0,
            "mode": 'additive'
        },
         "floor": {
            "prior_scale": 10.0,
            "mode": 'additive'
        }
    }
)

prophet_estimator.py
prophet_res_columns = ['cap', 'floor', 'y_scaled', 'cap_scaled']
....

def fit(self, X, y=None, time_col=TIME_COL, value_col=VALUE_COL, **fit_params):
        ..........
        ..........
        ..........
        # if extra regressors are given, we add them to temporal features data
        # This implementation assumes that the regressor(s) are provided in time series df, alongside target column.
        if self.add_regressor_dict is not None:
            for reg_col, reg_params in self.add_regressor_dict.items():
                 if reg_col not in prophet_res_columns :      # ---> Remove the reserved column names from the regressor list
                      self.model.add_regressor(name=reg_col, **reg_params)`

....

Let me know if this work-around makes sense ? If yes, then I can make the change and submit a pull request ?
Thanks !!

It's been a while now, but I tried the solution above and it worked for me.


Update Difficulty system

difficulty and world/game rules are two separate things. it does not depend on difficulty of the server.


Suddenly stops working beyond a certain number of samples

I found what I assume is a bug in perfanno when reading perf.data files that have more than ~14500 samples. When trying to load a perf.data that is beyond a certain size, it will never actually finish loading. The two images below are (ironically) perf data from perfanno reading a file with 14400 samples and a file with 14900 samples.
14400 samples

14900 samples

As the image suggests, the perfanno with the smaller file loaded in under a second. The other one, however, shows perf being run for a much shorter time, but without giving you annotated source code.

Hm, that is odd. I use the plugin with larger sample sizes than that so that shouldn't be the issue. It works fine even with the perf.data file gets huge (>10GB sometimes).
It would be helpful if I could reproduce the issue. What perf command did you use to record and on what version of perf? Does it already happen on a simple test program like this:
#include <iostream>

void foo(int i) {
    if (i % 10000) {
        std::cout << i << '\n';
    }
}

int main() {
    for (int i = 0;i < 1'000'000'000; ++i) {
        foo(i);
    }
}

The other thing which I find weird here is that in the second picture with more samples, perf seems to exit much earlier - perhaps it crashed or reported an error? Normally you should get a warning if perf exits with non-zero exit code, but perhaps there is something going wrong there. The command that the plugin runs to get the output from perf in the callgraph mode is the following:
perf report -g folded,0,caller,srcline,branch,count  --no-children --full-source-path --stdio

Does this produce any unusual output?

Running that perf command does error out with
Couldn't decompress data
0x132836 [0xffff]: failed to process type: 81 [Operation not permitted]
Error:
failed to process sample

I'm not sure why this happens, but if I run perf with no compression it works just fine, perfanno included. Annoying to have to keep these massive files in my system, but since it's either a perf or how perf is packaged in by my OS problem, I'll close the issue.
Thank you for the insight!


Changing 'retval' default value in firstContentOffset return method

When prepare is called in CalendarLayout it would scroll CalendarView by default to contentOffset = 0.
Therefore if I have a CalendarView with a ContentInset != 0 it will initially be scrolled to contentOffset = CGPoint(x: 0, y: 0) instead of being scroll to the start of the CalendarView (UICollectionView) which is at contentOffset = CGPoint(x: -contentInset.left, y: -contentInset.top).
This PR makes CalendarView scrolled by default to the start when prepare is called in CalendarLayout.

"When you introduce an inset, you change the range of the content offset. For example, setting the content inset to have a value of 10 for its top value allows the content offset’s y value to reach -10."
I've read it in https://www.objc.io/issues/3-views/scroll-view/
So the minimal value of the contentOffset is less than 0 when contentInset is >0

Hello @patchthecode , this change looks good to me and it would solve one issue I am facing in my app. Can you consider merging and releasing this? Thank you.


Page header should use contract date

Page header should use contract date
Revert @redhat-cloud-services/frontend-components version bump

https://issues.redhat.com/browse/HCS-144

Codecov Report

Merging #424 (c122f49) into main (dd8e391) will not change coverage.
The diff coverage is 0.00%.

:exclamation: Current head c122f49 differs from pull request most recent head 1aa51bc. Consider uploading reports for the commit 1aa51bc to get more accurate results

Additional details and impacted files

@@          Coverage Diff          @@
##            main    #424   +/-   ##
=====================================
  Coverage   4.57%   4.57%
=====================================
  Files         49      49
  Lines       1987    1987
  Branches     427     427
=====================================
  Hits          91      91
  Misses      1896    1896

Impacted Files
Coverage Δ

src/routes/components/page-heading/PageHeading.tsx
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


⚠ Bofrost.at has degraded performance

In 217125a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1577 ms

Resolved: Bofrost.at performance has improved in 9032b1c.


Guard propertyName in no-jquery-methods

In a large app I'm testing, the line this[this.someProp] was causing the no-jquery-methods rule to error out since node.object is a ThisExpression thus node.object.property.name was undefined.
In an example AST gist you can see this.
There is no point in continuing if propertyName is undefined since we base the blacklist off it. Added test cases.
@lynchbomb @chadhietala @scalvert

LG


Update prompt.txt to remove the restriction to english

I'm wondering if that line is needed at all? I used a prompt which said all input will be in English and then this
User
3 songs with awesome riffs
ChatGPT
{"media_id": ["Led Zeppelin - Whole Lotta Love", "AC/DC - Thunderstruck", "Guns N' Roses - Sweet Child o' Mine"], "media_type": "track"}
User
drie rocknummers met geweldige riffs
ChatGPT
{"media_id": ["Led Zeppelin - Whole Lotta Love", "AC/DC - Thunderstruck", "Guns N' Roses - Sweet Child o' Mine"], "media_type": "track"}
User
trois chansons rock avec des riffs géniaux
ChatGPT
{"media_id": ["Led Zeppelin - Whole Lotta Love", "AC/DC - Thunderstruck", "Guns N' Roses - Sweet Child o' Mine"], "media_type": "track"}
So three languages, same phrase (according to Google translate!) and same three responses when this was in the prompt "Note that the input query will be in English."

sounds valid to me!


Bumped turndown version

Since #14329 was throwing too many hygiene errors, I am just bumping the turndown version, which is the dependency that uses lodash (others are devDependencies)

(for context turndown is the package used to do all the HTML<->conversion in Notebooks which is what this test is testing)

@Charles-Gagnon @chlafreniere Oh woops, didn't expect the upgrade to have breaking changes. Should this be fixed by @cssuh then?

@abist let's chat more at DRI for options; I've asked my team to investigate.

Pull Request Test Coverage Report for Build 579779313

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 43.304%

Files with Coverage Reduction
New Missed Lines
%

src/sql/workbench/contrib/notebook/browser/turndownPluginGfm.ts
2
75.28%

extensions/import/src/wizard/pages/fileConfigPage.ts
3
72.99%

Totals

Change from base Build 579128829:
-0.01%

Covered Lines:
24990

Relevant Lines:
52893

💛  - Coveralls


Command line for Maven step, requires a manual Ctrl-C to Break. The output in the document needs to be updated.

** PLEASE ONLY USE THIS ISSUE TRACKER TO SUBMIT ISSUES WITH THE DOCKER LABS TUTORIAL CONTENT **

If you have a bug working with Docker itself, not related to these labs, please file the bug on the Docker repo *
If you would like general support figuring out how to do something with Docker, please use the Docker Slack channel. If you're not on that channel, sign up for the Docker Community and you'll get an invite. *
Or go to the Docker Forums *

Please provide the following information so we can assess the issue you're having
Which lab is it that you're having issues with?

Description

Steps to reproduce the issue, if relevant:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
(paste your output here)

Output of docker info:
(paste your output here)

Additional environment details (AWS, Docker for Mac, Docker for Windows, VirtualBox, physical, etc.):
At step to run: mvn -f docker-java-sample/pom.xml install -Pdocker
The output hanging at the [INFO] DOCKER> [hellojava:latest]: Waited on log out 'Hello World!' 506 ms, as the docker is running in the foreground. The document needs to mention this. It will require a Ctrl-C to break.

Which lab is this regarding?

Workshop, Docker for Java Developer
Sent from my Sony Xperia™ XZ smartphone
---- Mano Marks wrote ----
Which lab is this regarding?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/docker/labs/issues/242#issuecomment-294582057, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATKzd7oHX6vnQnTSXXHLGMJMVtwvjYAHks5rw8r3gaJpZM4M_gam.
WARNING - CONFIDENTIALITY NOTICE
This e-mail and any attachments may contain confidential and privileged
information.
Any use, disclosure, copying or dissemination of this information by a
person other than an intended recipient is not authorized and may be
illegal.
If you are not an intended recipient, please notify the sender
immediately by return e-mail, delete this e-mail and destroy any copies.
Thank you.

@arun-gupta


bittensor install

https://github.com/RogueTensor/bitagent_subnet/blob/main/README.md#get-running
I followed this, however bitcli isn't installed at this point, should I have installed it at the beginning?

It's btcli, not bitcli, only 1 "i" - HTH


bug: GCP use of default service account error when not defined

Describe the bug
https://aquasecurity.github.io/tfsec/v1.27.0/checks/google/compute/no-default-service-account/
no-default-service-account reports a critical error when no service account section is defined.
If service account is not specified then Terraform will create the instance without one configured. In this case the instance is not using the default service account, as it is using no service account at all.

To Reproduce
run tfsec with the following resource:
 resource "google_compute_instance" "default" {
   name         = "test"
   machine_type = "e2-medium"
   zone         = "us-central1-a"

   tags = ["foo", "bar"]

   boot_disk {
     initialize_params {
       image = "debian-cloud/debian-9"
     }
   }

   // Local SSD disk
   scratch_disk {
     interface = "SCSI"
   }

 }

Expected behavior
tfsec should not report an issue as there is no service account attached to the instance
System Info

tfsec version: v1.27.0
terraform version: v1.2.6
OS: darwin_arm64

Thanks for the report, fix incoming...


ci: create baseline and experimental test app pipelines

Description: Creates distinct test app profiles for end-to-end testing of baseline and new/experimental features in CI on Swift and Kotlin. Previously only a baseline configuration was run in CI which resulted in blindspots, especially with respect to upstream changes.
Risk Level: Low
Testing: Local & CI
Signed-off-by: Mike Schore<EMAIL_ADDRESS>

After talking with @goaway offline:

@goaway is going to open a GH issue that will track the future work for simplifying (removing) code from new CI example apps. We are going to remove some http filters, simplify apps' ViewControllers etc.
we are going to add some documentation that would explain what's the intent behind these new CI example apps and how they should be updated when somebody add a new feature to Envoy Mobile.
new CI example apps are going to be moved out of examples directory


Improve docs for updater signing CLI usage

The generate command wasn't mentioned in the docs, although it feels like quite an essential step in setting up the updater. This should help clear things up a bit.
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[x] Docs
[ ] New Binding issue #___
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[x] No

Checklist

[ ] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information

Thank you!


message send multiply numbers

is it possible to message send multiply numbers

Hi @lyarinet ,
There is no option in WhatsApp Business Cloud API to send messages to multiple phone numbers at one go, you have to do that one by one or through the loop.
Here is the WhatsApp API doc:
https://developers.facebook.com/docs/whatsapp/on-premises/reference/messages#sending-messages


 It also checks the arguments for play function

Thanks! I will wait for the PR.

Closing. Already implemented in https://github.com/thelinmichael/spotify-web-api-node/pull/190


Causes lock up:  History -> Recently closed windows -> [Window w/ 1028 Tabs]

When preforming this action with the addon enabled the window opens and the content does not load, but firefox's ram usage goes to the moon (16-20GB)
opening the browser with all these windows is not a problem with the addon enabled, only when doing it from history
after trying to restore this window 6 times with hangs and crashes i disabled this addon and it works no issues
This has been a issue for a while now, but i finally found the cause now that i will actually not open the window anymore and i can't just wait it out
note that firefox is set to only load active tabs when it is opened
System Info:

OS: kubuntu 22.04 (no snap packages installed)
Firefox: 125.0b6 (from Mozilla's website)

Hardware:

Ryzen 5 3600
32GB Ram (4x8GB; Micron Rev E)
RX 580 8GB
X470 Gaming Plus
Dual monitors

also causes memory leaks when running with multiple tabs


dtypes are inconsistent throughout rs.utils

We do not consistently use the same dtypes in functions within rs.utils. We should come up with a unified philosophy for how numpy dtypes are determined for returned values. I can think of at least three defensible possibilities:

Use input dtypes to decide return dtypes
Add a dtype=np.{float32, int32, ...} parameter to each function
Always return np.float32 or np.int32 as applicable.

I lean toward the last option, because it meshes best with the mtz standard, and I think it will lead to fewer edge cases and gotchas.

I agree with your take of prioritizing 32-bit dtypes where possible


Update how-to-networking-private-link-azure-cli.md (Typo "flexible se…

…rver"→"Flexible Server")
https://github.com/MicrosoftDocs/azure-databases-docs/blob/main/articles/mysql/flexible-server/how-to-networking-private-link-azure-cli.md #PingMSFTDocs

@SudheeshGH - related #10

Thanks, @hyoshioka0128!


chore(main): release 1.2.0

:robot: I have created a release beep boop
1.2.0 (2023-04-09)
Features

add more time function (f4d611a)
add some string functions (4320e3a)

Bug Fixes

review update (28ef8f9)

Styling

modify the code style (3f56cde)

Docs

make doc better (e7868e3)
make doc better (a46a6b3)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/WGrape/golib/releases/tag/v1.2.0 :sunflower:


gh-538 - Make REST API more RESTful and update to version 2.

Some questions regarding the change to the REST API in version 2:

I have added a custom media type to indicate to the REST client which version of the API their request has been executed against. I can remove this if we think it's not useful, or we could implement this differently (for example, by adding a custom header to the response)
I've added a additional endpoint (/latest) which redirects to the latest version of the API - is this useful?
At the moment, only one version of the API can be served up through Swagger - this needs to be configured by the application. Are there use cases where we would want to allow access to all versions of the API via Swagger?
Some methods have been changed to return Jersey Response objects - this allows for greater control over the object which is returned to the calling service (e.g. headers, status codes etc). Is it worth standardising this across the services so that all methods are treated the same?

/latest sounds useful
Yeah I think we will need to expose both versions in swagger.
Standardising the responses would be sensible, but only for the new version of the rest api.

Codecov Report

Merging #1036 into develop will increase coverage by 0.75%.
The diff coverage is 4.56%.

@@              Coverage Diff              @@
##             develop    #1036      +/-   ##
=============================================
+ Coverage      62.18%   62.93%   +0.75%
+ Complexity      1141     1039     -102
=============================================
  Files            528      504      -24
  Lines          15763    14715    -1048
  Branches        1831     1649     -182
=============================================
- Hits            9802     9261     -541
+ Misses          5191     4752     -439
+ Partials         770      702      -68

Impacted Files
Coverage Δ
Complexity Δ

...uk/gov/gchq/gaffer/rest/service/v1/JobService.java
0% <ø> (ø)
0 <0> (?)

...v/gchq/gaffer/rest/service/v1/ExamplesService.java
57.57% <ø> (ø)
0 <0> (?)

.../gchq/gaffer/rest/service/v1/OperationService.java
68.51% <ø> (ø)
0 <0> (?)

...fer/rest/service/v1/GraphConfigurationService.java
90.14% <ø> (ø)
0 <0> (?)

...n/java/uk/gov/gchq/gaffer/rest/SystemProperty.java
60% <ø> (ø)
0 <0> (ø)
:arrow_down:

...q/gaffer/rest/application/ApplicationConfigV2.java
0% <0%> (ø)
0 <0> (?)

...chq/gaffer/rest/service/v2/OperationServiceV2.java
0% <0%> (ø)
0 <0> (?)

.../gov/gchq/gaffer/rest/service/v2/JobServiceV2.java
0% <0%> (ø)
0 <0> (?)

...v/gchq/gaffer/rest/service/v2/StatusServiceV2.java
0% <0%> (ø)
0 <0> (?)

...r/rest/service/v2/GraphConfigurationServiceV2.java
0% <0%> (ø)
0 <0> (?)

... and 201 more

Continue to review full report at Codecov.

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


Mocking object function arguments using ->with() do not behave as expected.

I noticed that I cannot do the following to check that an object with the correct properties is passed to my mock object.
$mockArg = new stdClass();

Mockery::mock("My\Awesome\Object")
    ->shouldReceive("awesome")
    ->with($mockArg)
   ->once();

Instead I need to work around the issue with something like this.
$mockArg = new stdClass();

Mockery::mock("My\Awesome\Object")
    ->shouldReceive("awesome")
    ->with(Mockery::on(function($arg) use ($mockArg) {
        return $arg == $mockArg;
    }))
   ->once();

Php states comparing objects using '==' and/or '===' is the preferred practice (See: http://php.net/manual/en/language.oop5.object-comparison.php), so why does Mockery not support this type of comparison?  It seems fairly trivial to implement, I just want to make sure that there isn't a reason that I don't know about for this oversight.
Proposed Solution:
--- vendor/mockery/mockery/library/Mockery/Expectation.php  2016-01-21 16:42:29.000000000 -0800
+++ vendor/mockery/mockery/library/Mockery/Expectation.new.php  2016-01-21 16:41:47.000000000 -0800
@@ -327,6 +327,12 @@
                 return true;
             }
         }
+        if (is_object($expected) && is_object($actual)) {
+            $result = $actual == $expected;
+            if ($result) {
+                return true;
+            }
+        }
         if ($expected instanceof \Mockery\Matcher\MatcherAbstract) {
             return $expected->match($actual);
         }

This has come up a few times and is something we need to make a decision on. I don't like the current behaviour, but it's quite a big break in terms of backwards compatibility.
Previously raised here #328
It's mentioned in the issue we have for moving towards 1.0 #288

Seems like your solution here would be a good fit for 1.0.  Feel free to close this bug and attached PR after you figure out what you want to do for #288.
Thanks.

Closing this one, I'm going to maintain BC for now. I'm proposing to deprecate the MustBe matcher in #689.


How do you resovle a merge conflict with strategy theirs

This sentence is incomplete: "You can manually merge changes by selecting Merge, then entering the changes directly into the" Also, what do you do if you have over 1000 conflicts. How do you choose keep local or take remote for all conflicts if you already have a merge conflict? If there's no way, can you git pull with strategy=theirs using team explorer and a github repository?

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

ID: e2e2ddbb-512d-fe28-55c2-bfc4ff8aad73
Version Independent ID: 9b7770d7-7f5d-3cb7-c619-a5cd23b5da09
Content: Resolve Git merge conflicts
Content Source: docs/git/tutorial/merging.md
Service: unspecified
GitHub Login: @erickson-doug
Microsoft Alias: sdanie

@user135711 I'll fix that sentence, it depends on the merge tool you have configured in Visual Studio (or your Git settings)
I am finding out the answer to your other question about what to do if there are lots of merge conflicts and strategies to resolve.

@user135711 In Visual Studio there isn't currently a way to take "theirs/ours" for "All files". However you can do it from the command line, as described in this stack overflow post. If you think this is something we should add directly in Visual Studio, can file a feature request here. Thank you for your feedback.


One comment will generate two issues,it this a bug?

I like this tool very much, I use it in my personal blog.Thanks the authors.
But recently I had a problem. When someone commented on an article, there were two issues. So that comments can't be loaded into the blog.

Issues(https://github.com/yansheng836/yansheng836.github.io/issues) like this:

Blog: https://www.yansheng.xyz/article/faa5d14.html, can't loaded the comment, and the console show:

my config
<script src="https://utteranc.es/client.js"
        repo="yansheng836/yansheng836.github.io"
        issue-term="title"
        theme="github-light"
        crossorigin="anonymous"
        async>
</script>

Maybe this happened because of a bug in utterances.  This could also happen in the rare case that two people try to create the first post at the same time.
Does utterances have any feature to workaround this race condition?  Such a feature might help @yansheng836 avoid what happened to them.
An idea that comes to mind is some way for the repo owner to tell utterances to create an issue if it doesn't already exist.

What if someone creates the issue directly without using Uttranace? In this case, there could be multiple matching issue threads. When this happens, the comments should be merged when displaying and new comments through Uttranace should be posted in only one of the issues (perhaps oldest issue).

What if someone creates the issue directly without using Uttranace? In this case, there could be multiple matching issue threads.

Oh, great point.  I created a issue #348 to focus on that aspect so that this issue can focus on why two identical issues were created for you.

Actually, these two issues was generated by utterances-bot at the same time . The first one has no comment and the second one has a comment.
first:

second:

@yansheng836 Can you give a link to the post and issues also it this might help in figuring out what is happening.

In fact, I already have a link to that in my issue, please see https://github.com/utterance/utterances/issues/347#issue-648151769.
detailed
article link: https://www.yansheng.xyz/article/faa5d14.html
first issue(no comment): https://github.com/yansheng836/yansheng836.github.io/issues/15
second issue: https://github.com/yansheng836/yansheng836.github.io/issues/16

The best option would be, you be the first commenter or create the issue manually.

Alternatively, issue creation should be a part of build process for your static website. Each time you create a new article, build should create an issue for you


What model formats are supported by LLamaSharp

What model formats are supported by LLamaSharp？
What other formats are supported besides gguf?
Can the ggml format be supported？

LLamaSharp is a llama.cpp wrapper. It supports the models and formats described in llama.cpp documentation. See https://github.com/ggerganov/llama.cpp

Multimodal models are currently not supported, they will be supported in the near future.

Can the ggml format be supported?

ggml is no longer supported by llama.cpp itself, so we don't (can't) support it.


cloud_firestore : Batch commit not failing even though there is an error in one of the transactions

Describe the bug
While working on Flutter, I was writing a batch of transactions for creating documents on Firestore. The first transaction was valid, but the second transaction gave the error
`E/flutter ( 3848): [ERROR:flutter/lib/ui/ui_dart_state.cc(166)] Unhandled Exception: PlatformException(error, Invalid data. Document fields must not be empty, null)
E/flutter ( 3848): #0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:569:7)
E/flutter ( 3848): #1      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:159:18)
E/flutter ( 3848): <asynchronous suspension>
E/flutter ( 3848): #2      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:332:12)
E/flutter ( 3848): #3      MethodChannelWriteBatch.setData.<anonymous closure> (package:cloud_firestore_platform_interface/src/method_channel/method_channel_write_batch.dart:67:40)`

Now there is something missing the data that I have to fix. However, my batch commit did not catch the error and the first transaction was successful. I thought the point of batch transactions was to ensure integrity when there are multiple transactions. So if one transaction fails, I expect everything else to fail as well.
Is this an expected behaviour or am I missing something ? Can you please advice ?
To Reproduce
Steps to reproduce the behavior:
    final WriteBatch _batch = Firestore.instance.batch();
    String flag = '';

    final int timestamp = DateTime.now().millisecondsSinceEpoch;
// this transaction succeeds
    _batch.setData(
        Firestore.instance
            .collection('users')
            .document(uid)
            .collection('collection')
            .document('$uid$timestamp'),
        <String, dynamic>{'timestamp': timestamp});

// this transaction fails
    _batch.setData(
        Firestore.instance
            .collection('collection')
            .document('$uid$timestamp'),
        <Data that gives that error>);

    await _batch.commit().then((value) {
      flag = 'Submitted Successfully';
    }).catchError((dynamic onError) {
      print(onError.toString());
      flag = 'Submission Failed';
    });

    return flag;
  }

Expected behavior
I expect the whole batch transaction to back out as one of the transactions failed. I also expect the commit would catch the error.
Additional context
cloud_firestore: ^0.13.7
Flutter doctor
Run flutter doctor and paste the output below:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, 1.19.0-4.3.pre, on Linux, locale en_CA.UTF-8)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.0)
[✓] Connected device (3 available)

• No issues found!

Hi @vin-fandemand
Can you provide an example data that gives error
// this transaction fails
    _batch.setData(
        Firestore.instance
            .collection('collection')
            .document('$uid$timestamp'),
        <Data that gives that error>);

Code Sample
import 'package:cloud_firestore/cloud_firestore.dart';
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      title: 'Material App',
      theme: ThemeData.dark(),
      home: Home(),
    );
  }
}

class Home extends StatefulWidget {
  @override
  _HomeState createState() => _HomeState();
}

class _HomeState extends State<Home> {
  String flag;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Firestore Example'),
      ),
      body: Center(
        child: BookList(),
      ),
      floatingActionButton: FloatingActionButton(onPressed: () async {
        final WriteBatch _batch = Firestore.instance.batch();

        final int timestamp = DateTime.now().millisecondsSinceEpoch;
// this transaction succeeds
        _batch.setData(
            Firestore.instance
                .collection('users')
                .document('2020')
                .collection('collection')
                .document('20202 $timestamp'),
            <String, dynamic>{'timestamp': timestamp});

// this transaction fails
        _batch.setData(
            Firestore.instance
                .collection('collection')
                .document('2020 $timestamp'),
            <String, dynamic>{'timestamp': timestamp});

        await _batch.commit().then((value) {
          flag = 'Submitted Successfully';
        }).catchError((dynamic onError) {
          print(onError.toString());
          flag = 'Submission Failed';
        });
      }),
    );
  }
}

class BookList extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return StreamBuilder<QuerySnapshot>(
      stream: Firestore.instance.collection('books').snapshots(),
      builder: (BuildContext context, AsyncSnapshot<QuerySnapshot> snapshot) {
        if (snapshot.hasError) return new Text('Error: ${snapshot.error}');
        switch (snapshot.connectionState) {
          case ConnectionState.waiting:
            return new Text('Loading...');
          default:
            return new ListView(
              children:
                  snapshot.data.documents.map((DocumentSnapshot document) {
                return new ListTile(
                  title: new Text(document['title']),
                  subtitle: new Text(document['author']),
                );
              }).toList(),
            );
        }
      },
    );
  }
}

flutter doctor -v
[✓] Flutter (Channel dev, 1.20.0-7.1.pre, on Mac OS X 10.15.6 19G73, locale
    en-GB)
    • Flutter version 1.20.0-7.1.pre at /Users/taha/Code/flutter_dev
    • Framework revision 7736f3bc90 (6 days ago), 2020-07-10 16:33:05 -0700
    • Engine revision d48085141c
    • Dart version 2.9.0 (build 2.9.0-21.2.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version
    30.0.0)
    • Android SDK at /Users/taha/Code/sdk
    • Platform android-30, build-tools 30.0.0
    • ANDROID_HOME = /Users/taha/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google
      Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.47.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.12.2

[✓] Connected device (5 available)
    • SM M305F (mobile)      • 32003c30dc19668f          • android-arm64  •
      Android 10 (API 29)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios            •
      iOS 13.6
    • macOS (desktop)        • macos                     • darwin-x64     •
      Mac OS X 10.15.6 19G73
    • Web Server (web)       • web-server                • web-javascript •
      Flutter Tools
    • Chrome (web)           • chrome                    • web-javascript •
      Google Chrome 83.0.4103.116

• No issues found!

I am unable to recreate the issue. It is working as expected.

Hi @vin-fandemand
given your last message I feel safe to close this issue, if you disagree please write in the comments and I will reopen it.
Thank you


Admin URL finder mechanism

A mechanism for obtaining the admin edit URL for an arbitrary model instance, optionally applying permission checks.
url_finder = AdminURLFinder(request.user)
url_finder.get_edit_url(some_page)  # => "/admin/pages/123/edit/"
url_finder.get_edit_url(some_image)  # => "/admin/images/456/"
url_finder.get_edit_url(some_site)  # => None (user does not have edit permission for sites)

Handlers for new models can be registered via register_admin_url_finder:
class SprocketAdminURLFinder(ModelAdminURLFinder):
    edit_url_name = 'wagtailsprockets:edit'

register_admin_url_finder(Sprocket, SprocketAdminURLFinder)

I haven't added any documentation yet, as nothing is making use of AdminURLFinder yet (other than tests) - but the extended Site History report will make use of this, and it'll also be useful for things like "deleting this object will also delete the following..." prompts (#6129).

Do you think we could extend this to support other actions and use for the Admin API as well?

Sure! There's an open question there about how we handle different actions for the same model being registered in separate calls to register_admin_url_finder - e.g. wagtail.contrib.modeladmin will register itself as the edit view, but presumably won't provide an API endpoint so that will get registered separately - but we can cross that bridge when we come to it.

Merged in de549b428863e8d1cd58a0c1ce1ed46af4c9f749


darwin.js fails to find individual sim results, causing it to be stuck on gen 0

System information

Have I written custom code (as opposed to using zenbot vanilla): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 17:10
Zenbot version (commit ref, or version): Working in a8d3f72, failing after
Zenbot branch: unstable
NodeJS version: 10.5.0
Python version (when using a python script): na
Exact command to reproduce (include everything): node ./scripts/genetic_backtester/darwin.js --selector=gdax.BTC-USD --days=90 --period_length=15m --period=15m --markdown_buy_pct=0.0001 --markup_sell_pct=0.0001 --order_type=taker --floatScanWindow=true --currency_capital=3000 --asset_capital=0.000001 --ignoreLaunchFitness=true --generateLaunch=true --population_data=period15day90taker --noStatSave=false --use_strategies=ta_macd,wavetrend,ichimoku,ta_ultosc,ti_bollinger,ta_ppo --population=30
Did I make any changes to conf-sample.js?: no

Describe the problem
After commit a8d3f72, the darwin.js script fails to parse the results of individual simulations.  It does NOT appear to be a permissions issue, as the folder gets created appropriately, and contains the expected json output files.
darwin's behavior in this situation is to repeatedly run generation 0, since it is unable to parse/locate the results from that generation.
Source code / Error logs
No traceback.
The console output of the issue is a single line stating "Couldn't find simulationResults for #" for every sim instance in the generation.  The files DO exist.
There are 3 non travis-ci commits after the working a8d3f72 commit.  The most likely is commit bed3bb5

**- Have I written custom code: No

OS Platform and Distribution: Ubuntu 16:04
Zenbot version: e41a01b
Zenbot branch: unstable
NodeJS version: 10.5.0**

darwin.js fails to parse the JSON files created for each sim because the JSON files for the sims which cannot be found are missing lots of information and are not formatted correctly. Below, I will attach JSON files (as TXTs), sim_20.json & sim_32.json, created after two simulations in the same generation. sim_20.json is correctly formatted and has all the information about the sim, and therefore the "simulationResults for 20" were found. sim_32.json is formatted incorrectly and is missing information suggesting that sim 32 was not executed. Because of this, "simulationResults for 32" could not be found.
sim_20.txt
sim_32.txt
Note that both of those simulations were of the same generation which was completed, but for some reason sim 32 was not completed in proper. Also, unlike @tabbek, this issue only happens a few times per generation rather than for each simulation. The most times this error has occurred in one generation using the system, with which I am typing this comment, is 16 out of 150 simulations. On my other system, the issue happens for each simulation, and they are hardly being processed by my CPU meaning that a simulation might freeze forever.

I'm having the same issue... Anyone has the solution to this?


Kubernetes log viewer is extremely slow to load with larger log files

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
The log viewer in Kubernetes is very very slow to load on larger logs.
Expected Behavior
This is local so I do expect fast loading.  The file size is around 30,000 lines but I notice the unresponsive browser tab message at around 10000 lines and it takes around 1minute or more to load.   You might not think much of that until you see a php app I'm working on that loads the log for the app from Kubernetes in under 1s.
Actual Behavior
Sitting there for tens of seconds waiting for it to load.  The browser pops up an unresponsive tab dialog.
If you wait long enough it might load.
Steps to Reproduce
Create an app that spews a lot of log data.  Which can happen if an app has an issue or is misbehaving or doing a lot because it's a busy process.
Portainer logs or screenshots
No response
Portainer version
2.23.0
Portainer Edition
Business Edition (BE/EE) with 5NF / 3NF license
Platform and Version
Docker Desktop with Kubernetes 1.3x
OS and Architecture
Windows + WSL
Browser
Chrome
What command did you use to deploy Portainer?
Standard

Additional Information
You can use this project to quickly build a local image to test.
https://github.com/hookenz/quoter
It generates a lot of log data and with colour output so it's really stressing the log viewer component.
The same container viewed under Docker is quicker because they are only showing the last 100 lines by default.
But if you change the number of lines to 30000, then expect to wait a long time.  In the mean time the whole tab locks up and is unusable until it completes.  There is no feedback as to what it's doing.

@Nick-Portainer happy to give you a slack call and demo to show you how slow it is vs how fast it should be (comparing to the php code I have).

Hey @hookenz Thanks, I have raised this internally will chat with the team and let you know!


net: tcp: Fix net_buf leak in case of low available net_buf count

This net_buf leak happends when we are low on available net_buf
count. During TCP segment preparation we do allocate IP header
successfully, but we fail to allocate TCP header. In such case
pkt->frags is not NULL anymore (it contains IP header), but we
override it during TCP header allocation error path. This results
in net_buf containing IP header to never be deallocated, because
it does not belong to any net_pkt anymore.
Use net_pkt_frag_add() function to add tail for future net_pkt
deallocation, instead of assigning tail to pkt->frags pointer.
Fixes: c6407659f3e6 ("net: tcp: Add the frag back to caller allocated
net_pkt")
Signed-off-by: Marcin Niestroj<EMAIL_ADDRESS>

Codecov Report

Merging #9379 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master    #9379   +/-   ##
=======================================
  Coverage   52.52%   52.52%
=======================================
  Files         201      201
  Lines       25352    25352
  Branches     5299     5299
=======================================
  Hits        13316    13316
  Misses       9941     9941
  Partials     2095     2095

Impacted Files
Coverage Δ

subsys/net/ip/tcp.c
58.96% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[Bitmagic]  Update to 7.11.2

Describe the pull request

What does your PR fix?
Updates bitmagic to 7.11.2

Which triplets are supported/not supported? Have you updated the CI baseline?
As before, Yes

Does your PR follow the maintainer guide?

Yes

Thanks for the update!


Add handler for workflow_run.in_progress payloads

May be tangentially related to #169 - though unlikely given the area of code touched to fix the issue I was seeing

Behavior
Before the change?

      System.Text.Json.JsonException: The JSON value could not be converted to Octokit.Webhooks.Events.WorkflowRunEvent. Path: $ | LineNumber: 374 | BytePositionInLine: 1.
         at Octokit.Webhooks.Converter.WebhookConverter`1.Read(Utf8JsonReader& reader, Type typeToConvert, JsonSerializerOptions options)
         at System.Text.Json.Serialization.JsonConverter`1.TryRead(Utf8JsonReader& reader, Type typeToConvert, JsonSerializerOptions options, ReadStack& state, T& value)
         at System.Text.Json.Serialization.JsonConverter`1.ReadCore(Utf8JsonReader& reader, JsonSerializerOptions options, ReadStack& state)
         at System.Text.Json.JsonSerializer.ReadFromSpan[TValue](ReadOnlySpan`1 utf8Json, JsonTypeInfo jsonTypeInfo, Nullable`1 actualByteCount)
         at System.Text.Json.JsonSerializer.ReadFromSpan[TValue](ReadOnlySpan`1 json, JsonTypeInfo jsonTypeInfo)
         at System.Text.Json.JsonSerializer.Deserialize[TValue](String json, JsonSerializerOptions options)
         at Octokit.Webhooks.WebhookEventProcessor.DeserializeWebhookEvent(WebhookHeaders headers, String body)
         at Octokit.Webhooks.WebhookEventProcessor.ProcessWebhookAsync(IDictionary`2 headers, String body)
         at Octokit.Webhooks.AspNetCore.GitHubWebhookExtensions.<>c__DisplayClass0_0.<<MapGitHubWebhooks>b__0>d.MoveNext()
Octokit.Webhooks.WebhookEventProcessor: Error: Exception processing GitHub event.

Stepped through the code and it was falling out here, because it was only pulling back two types (in_progress being missing)
https://github.com/octokit/webhooks.net/blob/e87e42e7826f775c83d66082c0bbe9285aba60e7/src/Octokit.Webhooks/Converter/WebhookConverter.cs#L35-L39
Looks like the in_progress type was added fairly recently: https://github.com/octokit/webhooks/commit/3a19cc7a3731811fce7654755f0420904bed78dd
After the change?

It works :)
Other information

Not sure if I need to add any tests here? (Might need some pointers!)

Additional info
Pull request checklist

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[ ] Added the appropriate label for the given change

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

[ ] Yes (Please add the Type: Breaking change label)
[x] No

If Yes, what's the impact:

N/A

Pull request type

Please add the corresponding label for change this PR introduces:

Bugfix: Type: Bug
Feature/model/API additions: Type: Feature
Updates to docs or samples: Type: Documentation
Dependencies/code cleanup: Type: Maintenance

Do you have an example payload you can share?


LANG-781 Added methods to ObjectUtils class to check for null element…

I've created this pull request to refresh the issue LANG-781 as I faced a lack of methods to check nulls in array.

Any update on this?

Yes:

Thank you for the patch.
The Javadoc has some bogus text, like starting with "". You do not need that.
Do not use a for-each loop to traverse an array. This creates an iterator when none is needed. Use a normal for loop, which will not create the extra Iterator to GC. This matters when a libraries is used on the critical path and/or environments trying to do low/no GC.

@vanta It would be nice if you could update the pull request according to garys comments.
Thanks!

@garydgregory How bout firstNonNull method that exists since 2009 and uses for-each loop to iterate over array?

There is a discussion going on right now on the dev mailing list about for-each vs. for. Let's see how that plays out. See https://commons.apache.org/mail-lists.html

Thanks! :+1:
For each loop won the discussion, so I merged only the first commit.
@vanta Sorry for telling you to refactor to use a for loop.

@PascalSchumacher Nothing to sorry for :)


SetParent function was used instead of parent property during instantiation.

It removes warning when UI is instantiated.

Awesome

Thanks


Nuxt Fatal Error - Context is not available

Describe the bug
Error on yarn dev:
FATAL  Context is not available
at use (node_modules/unctx/dist/index.mjs:12:15)
at setup (node_modules/@unlighthouse/nuxt/dist/module.mjs:18:26)
at ModuleContainer.normalizedModule (node_modules/@nuxt/kit/dist/index.mjs:630:29)
at async ModuleContainer.addModule (node_modules/@nuxt/core/dist/core.js:239:20)
at async ModuleContainer.ready (node_modules/@nuxt/core/dist/core.js:51:7)
at async Nuxt._init (node_modules/@nuxt/core/dist/core.js:478:5)
Reproduction
No response
System Info
@nuxt/cli v2.15.8.

package.json devDependencies: "@unlighthouse/nuxt": "^0.4.2",

nuxt.config.js:

buildModules: [
    '@unlighthouse/nuxt',
  ],

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

v0.3.29 seems to be the last working version for Nuxt v2.

Thank you - pointing at the earlier version has resolved the issue.

Thanks for the issue guys, I'll leave this open to fix properly soon. Busy with another project atm

Thanks for the patience, fixed in 0.4.3

Getting a new fatal error in Nuxt 2:
 FATAL  Maximum call stack size exceeded                                                                                16:43:07

  at jiti (/node_modules/jiti/dist/jiti.js:1:247662)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/util.js:20:22
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/JSHandle.js:29:13
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/ElementHandle.js:29:17
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/util.js:20:22
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/JSHandle.js:29:13
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/ElementHandle.js:29:17
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/util.js:20:22
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/JSHandle.js:29:13
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/ElementHandle.js:29:17
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/util.js:20:22
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/JSHandle.js:29:13
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/ElementHandle.js:29:17
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/util.js:20:22
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/JSHandle.js:29:13
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/ElementHandle.js:29:17
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/util.js:20:22
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/JSHandle.js:29:13
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/ElementHandle.js:29:17
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/util.js:20:22
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/JSHandle.js:29:13
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/ElementHandle.js:29:17
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/util.js:20:22
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/JSHandle.js:29:13
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/ElementHandle.js:29:17
  at jiti (/node_modules/jiti/dist/jiti.js:1:247502)
  at /node_modules/puppeteer-core/lib/esm/puppeteer/common/util.js:20:22


flashrom: 1.1 -> 1.2

Motivation for this change
New upstream release.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build flashrom

@GrahamcOfBorg build flashrom
Testing the expanded platforms list.

@GrahamcOfBorg build flashrom
...and again now that I fixed the merge conflict

libflashrom should also now be suitable for upstream consumption by fwupd, cc @jtojnar.

@GrahamcOfBorg build flashrom

Does it build on aarch64 now? See https://github.com/NixOS/nixpkgs/pull/79906#issuecomment-585281029
Also the commit message should be fixed now that @r-ryantmʼs update was merged.

Huh, didn't realize I was beaten by the bot; strange it was merged days ago considering the release was only tagged and announced today.
Removed the pointless enableParallelBuilding line; let's see if it builds on AArch64 now, though I doubt it: @GrahamcOfBorg build flashrom

yep, still broken. Added a link to the upstream issue to track it at least.

aarch64-linux build is failing because unlike flashrom Makefile, meson.build doesn't feature any platform support checks. Compare:

https://github.com/flashrom/flashrom/blob/afc3ad64300bbcc14266e645beec897ef06df13d/Makefile#L413-L451
https://github.com/flashrom/flashrom/blob/324929c3d725ce264b2390525dbc9070f6029cc4/meson.build

We could disable pciutils for non-X86 architectures, which works around the issue:
{
  mesonFlags = [
    (lib.optional (!stdenv.isi686 && !stdenv.isx86_64) "-Dpciutils=false")
  ];
}

But it's probably better to invest effort into fixing this upstream.


modularize routing behavior

by exporting routes directly to respective index.js

in controllers directory, we have functions for logic mainly
in routers, we have our express pathing, and at the endpoints we export our controllers methods and use them according to paths


Stuck on Creating Canvas Player and occasionally on creating api

I am stuck on Creating CanvasPlayer Window. I left it in 1hr but still stuck. i am running a Fujitsu Lifebook U Series Netbook.

install VLC 3.0.20


Add Fred Pickel to ICPC, 2019 NAIPC repos

Fred Pickel<EMAIL_ADDRESS>GitID: fredpnh1947

Invited!


THEEDGE-2487

Description
This PR covers THEEDGE-2487.

It adds an aria-label of "Actions for group details view" to the top right Actions dropdown in the Group details view.
It changes the aria-label of the Group details page's system table toolbar kebab from "Actions" to "Actions for selected table items".

What is it?

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update

Checklist:

[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] I run npm run lint:js:fix to check that my code is properly formatted

Codecov Report
Base: 30.28% // Head: 30.53% // Increases project coverage by +0.24% :tada:

Coverage data is based on head (111deb5) compared to base (d6e61fb).
Patch coverage: 26.92% of modified lines in pull request are covered.

:exclamation: Current head 111deb5 differs from pull request most recent head 2692796. Consider uploading reports for the commit 2692796 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #555      +/-   ##
==========================================
+ Coverage   30.28%   30.53%   +0.24%
==========================================
  Files         126      126
  Lines        2704     2702       -2
  Branches      827      831       +4
==========================================
+ Hits          819      825       +6
+ Misses       1724     1723       -1
+ Partials      161      154       -7

Impacted Files
Coverage Δ

src/Routes/DeviceDetail/DeviceDetail.js
0.00% <ø> (ø)

src/Routes/Devices/DeviceTable.js
28.37% <0.00%> (ø)

src/Routes/GroupsDetail/GroupsDetail.js
40.69% <ø> (ø)

src/Routes/ImageManagerDetail/DetailsHeader.js
85.71% <ø> (ø)

src/components/general-table/ToolbarKebab.js
87.50% <0.00%> (ø)

src/Routes/Devices/RetryUpdatePopover.js
21.62% <29.16%> (+16.49%)
:arrow_up:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


AttributeError: module 'ctypes' has no attribute 'windll'

Describe the bug
cannot run python3 bjorn-detector.py without getting this error:
io@Neptune bjorn-detector % python bjorn-detector.py
Traceback (most recent call last):
File "bjorn-detector.py", line 3, in
from src import main
ImportError: No module named src
io@Neptune bjorn-detector %
To Reproduce
run through procedure on  M1 Max Macbook pro (MacOS 14.3 )

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

Expected behavior
to be able to run this on Mac,
Screenshots

Additional context
Add any other context about the problem here.

fixed.
https://github.com/JuanVilla424/bjorn-detector

much thanks- still not being found on the network. Think that's my issue though 😛

try scan ur network using a network scan and identify bjorn IP address by hostname

yea, not showing up- its a me issue lol.

Try this...
Hey Cybervikings ! 🤘🏻
I've noticed many of you are struggling with Bjorn "forgetting" its Wi-Fi networks whenever it connects to a new one... That's because of this f…..  "preconfigured" connection being a bit stubborn!
While I work on an update to fix this properly, and integrate full WiFi's management with priorities and potfiles import, here's a quick temporary solution that'll make your life easier:
1⃣ First, let's get rid of that annoying "preconfigured":
sudo nmcli connection delete "preconfigured"
sudo rm /etc/NetworkManager/system-connections/preconfigured.nmconnection
2⃣ Then, you have two cool ways to add your networks:
The Easy Way (scanning and connecting):
Scan available networks
nmcli device wifi list
Connect to your network
nmcli device wifi connect "YourWiFiName" password "YourPassword"
The Pro Way (manual setup with priorities - higher number = higher priority):
First, create and edit your network configuration file:
sudo vi /etc/NetworkManager/system-connections/YourWiFiName.nmconnection
Add this configuration (replace YourWiFiName and YourPassword):
[connection]
id=HomeWiFi
type=wifi
autoconnect=true
autoconnect-priority=20
[wifi]
mode=infrastructure
ssid=YourWiFiName
[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk=YourPassword
[ipv4]
method=auto
[ipv6]
method=auto
Finally, restart NetworkManager:
sudo systemctl restart NetworkManager
That's it! Now Bjorn will remember all your networks and automatically connect to the one with the highest priority when available.
Pro Tip: If you're using an iPhone hotspot, check "Maximize compatibility" option in your iPhone settings to force 2.4GHz connection if you're having issues.
Thanks to @infinition

solved #4


ARCH=powerpc allmodconfig kallsyms failure

The ARCH=powerpc allmodconfig build has been failure on mainline with clang-17 and newer for some time now:
https://github.com/ClangBuiltLinux/continuous-integration2/actions/runs/7100738175/job/19337864638
Inconsistent kallsyms data
Try "make KALLSYMS_EXTRA_PASS=1" as a workaround

I have been unable to reproduce this locally with either the kernel.org LLVM toolchains or the TuxMake docker.io/tuxmake/powerpc_clang-17 container across many runs. Is this an issue with caching or something?
We could try adding KALLSYMS_EXTRA_PASS=1 to the environment to workaround this but it appears that TuxSuite only supports KCONFIG_ALLCONFIG, rather than arbitrary environment variables.

I haven't seen this in some time.


Add interactivity shell issues.

I found when i create a interactivity shell, i need create tow process make it work, one auto-start process, one interactive process, but now status is not ok for that, beacuse if the user presses Ctrl+C during installation, the previous state should be successful!
like this:

Should be fixed