[AIRFLOW-3099] Don't ever warn about missing sections of config

Make sure you have checked all steps below.
Jira

[X] https://issues.apache.org/jira/browse/AIRFLOW-3099

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

Rather than looping through and setting each config variable
individually, and having to know which sections are optional and which
aren't, instead we can just call a single function on ConfigParser and
it will read the config from the dict, and more importantly here, never
error about missing sections - it will just create them as needed.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason: already covered by existing tests

Commits

[x] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

@chang you made a similar PR (#4002) - mind taking a look at this one too? It takes a completely different approach, but should mean there's no list to udpate.

Codecov Report

Merging #4028 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #4028      +/-   ##
=========================================
+ Coverage   75.79%   75.8%   +<.01%
=========================================
  Files         199     199
  Lines       15946   15936      -10
=========================================
- Hits        12087   12080       -7
+ Misses       3859    3856       -3

Impacted Files
Coverage Δ

airflow/bin/cli.py
65.01% <0%> (+0.53%)
:arrow_up:

airflow/jobs.py
82.13% <0%> (-0.36%)
:arrow_down:

airflow/models.py
91.67% <0%> (-0.05%)
:arrow_down:

Continue to review full report at Codecov.

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

One of the k8s test error'ed. I have re-started it.

Nice one @ashb


Updating state value tied to totalPages doesn't cause re-render of Pagination component

Category
[x ] Bug
Version
Please specify what version of the library you are using: [  1.19.0   ]
Expected / Desired Behavior / Question
Updating state value tied to totalPages property doesn't cause re-render of Pagination component
Observed Behavior
When passing a number from the property pane of an SPFx webpart to the totalPages property via state, the UI of the Pagination is not re-rendered, and if you click on the >> button it removes all the numbers.
Steps to Reproduce
Pass a number from the property pane of an SPFx webpart to the totalPages property via state, the UI of the Pagination is not re-rendered, and if you click on the >> button it removes all the numbers.

For anyone looking a solution without using the beta package, force the update changing the "key" of the element, like this:
<Element key={this.state.key} />
Then when you update the totalPages property:
this.setState({ key: Math.random() });
Taken from here. Not the best approach, but it works.

erickalves05 I've tried this, with no luck. I am updating totalPages from the property pane and adding it to state = { totalPages: this.props.totalPages, key: Math.random() } on the component then on componentDidUpdate I did as you said and checked this.props.totalPages !== prevProps.totalPages and setState({ totalPages: this.props.totalPages, key: this.state.key } The pagination component still refuses to re-render.


Unable to see JSON path on mouse over of JSON response field values

Expected Behavior
When the response is JSON, it should be possible to mouse over JSON field values, to find its equivalent JSON path expression.
Actual Behavior
When the response is JSON, it should be possible to mouse over JSON field values, to find its equivalent JSON path expression.
Reproduction Steps

Submit a HTTP request that returns JSON response
Mouse over json fields

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
2023.5.8
What operating system are you using?
macOS
Operating System Version
MacOS Ventura
Installation method
downloaded for macos
Last Known Working Insomnia version
No response

No, I'm able to filter the response. However, on mouseover of a field on the editor that contains the response, could we look at its equivalent path?


Support primary key have the capital letter

Make sure these boxes checked before submitting your pull request.

[] Do only one thing
[] No API-breaking changes
[] New code/logic commented & tested

For significant changes like big bug fixes, new features, please open an issue to make an agreement on an implementation design/plan first before starting it.
What did this pull request do?
if use postgresql, eg:
//Model
type Model struct {
	ID        uint      `gorm:"column:ID;primary_key"`
	CreatedAt time.Time `gorm:"column:create_time"`
}

insert data error:
pq: column name "id" not found

Should use scope.Quote

Should use Quote method


network: expose peer credentials on connection

This allows retrieving the pid/uid/gid from the connection if the
connection is made using a unix socket.
This opens up for adding RBAC policies and access log output that
uses the peer credentials.
Signed-off-by: Snow Pettersen<EMAIL_ADDRESS>Risk Level: Low
Testing: Integration test
Docs Changes: n/a
Release Notes: n/a
Step 1 of #6193

/retest


649 | test (Schema Bind): plugin-ts & wasm-as

@dOrgJelli Can/Should we add a formatter with our own configs so that we don't get our git changes polluted by default formatter of the devs?

Going to close these as they're a bit out of date, and we're adding more granular test cases within other PRs.


Using initialRegion instead of region

using initialRegion instead of region for react native maps

Hi, there is really no difference in using initialRegion and region. It can lead to problems when re rendering map because it will move user to initial position and that is usually not what we want. But feel free to use your version ;)

Any ideas then why it breaks the map on iOS?
On Oct 25, 2017 4:52 AM, "Tomasz Przybył"<EMAIL_ADDRESS>wrote:

Hi, there is really no difference in using initialRegion and region. It
can lead to problems when re rendering map because it will move user to
initial position and that is usually not what we want. But feel free to use
your version ;)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/venits/react-native-map-clustering/pull/16#issuecomment-339305009,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACVjbponJOTuQ5ZpNWwpnKkQwz9bFWPLks5svyEBgaJpZM4QFSuV
.


feat(fetch_secret): Enable retry on failed credentials fetching

What does this PR do?
Enable the retry of jobs on credential failures on gitlab jobs

Motivation
Don't see this again

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Update zio, zio-streams to 1.0.0-RC18-1

Updates

dev.zio:zio
dev.zio:zio-streams

from 1.0.0-RC17 to 1.0.0-RC18-1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

labels: library-update, semver-pre-release

A few code changes are needed to make this one work.
Also, a new version of https://github.com/zio/interop-reactive-streams built for RC18 is needed (should come soon).

Can be closed in favor of #458


New article --  Office versions and requirement sets

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/office-versions-and-requirement-sets.md
:white_check_mark:Succeeded

docs/images/office-version-number-ui.jpg
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

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


:CocCommand clangd.install

I'm following the "Quick Start" guide and have run into problems on the :CocCommand clangd.install step.  The guide claims coc-clangd will try to find clangd in my $PATH.  I know that clangd is not in my $PATH, but I see no output from :CocInstall coc-clangd that it looked and failed to find it.  I only see a single line with a green check that it installed into .config/coc/extensions/node_modules/coc-clangd.
When I run :CocCommand clangd.install to have it fetch the latest release, it returns [coc.nvim] Command: clangd.install not found.

You need to open C/C++ files to run :CocCommand clangd.install.

Did you check if it downloaded clangd?  It downloaded for me, and I think you're supposed to add the clangd path to your PATH and restart vim.  I gave up before I could get it working, because CentOS 7 won't run clangd 10 due to its glibc being too old.  I'd happily try an older release without that requirement, but 10.0 seems to be only release posted, not counting pre-releases.

Had same issue and updating my env variable PATH including the clangd fixed for me.

export PATH=$PATH:/home/rodhash/.config/coc/extensions/coc-clangd-data/install/10.0.0/clangd_10.0.0/bin

Also had to manually add the installation directory to my PATH. Not sure if this is intended behavior? If so, perhaps we should add it to the readme?

MWE for newbies (like me):

create Node project

dir01="$HOME/cocnvim_c"
mkdir $dir01 && cd $dir01
npm init # all default
npm i coc-clangd

Add $PATH

cd $HOME/.config/coc/extensions/coc-clangd-data/install/*/clang*/bin && echo $PWD && cd - # copy echo
vim ~/.bashrc  # add line: export PATH=$PATH:[paste echo]

test it:

echo $PATH
vim $dir01/main.c

Amend alternative to create a Node project (step 1 of my previous comment):
sudo npm i --global coc-clangd

I came up with the same problem, but I figured out why, just run :CocConfig, and it opens the config file: coc-settings.json, add clangd.path as folllows:
{
    "clangd.path": "/usr/local/opt/llvm/bin/clangd"
}

or if you installed clangd as coc suggests(:CocCommand clangd.install), the path should be something like this:
$HOME/.config/coc/extensions/coc-clangd-data/install/*/clang*/bin/clangd
make sure clangd is included in the path
as you can see, I use llvm, which already includes clangd, so I do not need to install clangd suggested by coc

Btw: if C/C++ file is NOT Vim-opened through terminal, the ~/.profile should have proper $PATH too: shell configuration files (like ~/.bashrc or /etc/profile) affect only the applications started from shell.


fix compile error

Summary
fix compile error
chip/efm32_leserial.c: In function 'efm32_restoreuartint': Error: chip/efm32_leserial.c:329:37: error: 'len' undeclared (first use in this function); did you mean 'ien'?
329 |   efm32_restoreuartint_nolock(priv, len);
|                                     ^~~
|                                     ien
Impact
efm32_leserial.c
Testing
ci

[Experimental Bot, please feedback here]
No, this PR does not fully meet the NuttX requirements. While it identifies a compile error fix, it lacks crucial information.
Here's what's missing:

Summary: Needs more detail. Why was len undeclared?  What was the root cause of the compile error? What exactly was changed to fix it?  Just stating "fix compile error" is insufficient.  Mention the affected functionality (e.g., serial driver).
Impact:  Saying efm32_leserial.c is affected is not enough. Answer all the impact questions specifically.  Does this fix introduce any user-facing changes?  Does it affect any particular boards?  Does it require documentation updates?  Most will likely be "NO", but you still need to state that explicitly.
Testing: "ci" is not adequate. Provide actual build and test logs before and after the change, demonstrating that the issue is resolved and no new issues are introduced. Specify the host and target environments used for testing (OS, architecture, board, configuration). Ideally,  show that the serial driver functions correctly after the fix.

Example of a better summary and testing section:
Summary:
This PR fixes a compile error in chip/efm32_leserial.c caused by the undeclared variable len within the efm32_restoreuartint function. This error occurred because len was used without being declared, likely intended to be the interrupt enable state.  The fix introduces a new variable uart_intstate to store the interrupt enable state and uses it correctly within efm32_restoreuartint and efm32_restoreuartint_nolock.  This resolves the compilation issue and restores the correct handling of serial port interrupts.
Impact:

Is new feature added? NO
Is existing feature changed? NO (bug fix)
Impact on user: NO
Impact on build: NO (fixes a broken build)
Impact on hardware: NO
Impact on documentation: NO
Impact on security: NO
Impact on compatibility: NO
Anything else to consider? NO

Testing:
Build Host: Linux, x86_64, GCC 9.4.0
Target: QEMU, ARM Cortex-M3, EFM32 Giant Gecko (sim)
Testing logs before change:
chip/efm32_leserial.c: In function 'efm32_restoreuartint':
chip/efm32_leserial.c:329:37: error: 'len' undeclared (first use in this function); did you mean 'ien'?
  329 |   efm32_restoreuartint_nolock(priv, len);
      |                                     ^~~
      |                                     ien
make: *** [<builtin>: chip/efm32_leserial.o] Error 1

Testing logs after change:
... (build output showing successful compilation) ...

nsh> help  # Verify serial console works
... (nsh help output)

@jerpelea this patch need cherry-pick to release branch too.


Unhelpful Documentation, Missing High Level Interface

Hi!
I really value your effort in trying to bring GOEA to python, but please, please, please go all the way. This whole library feels like someone did the hard things (programming the actual functionality) and then just abandoned it without giving users a chance to actually use it. As already was mentioned, the documentation is not helpful. I can't find a comprehensive explanation of the task that I want to achieve with this library.
My task is simple, I want to do a GO term enrichment analysis. From what I understand I should need three things to do that:

An iterable of gene identifiers (results)
An iterable of background gene identifiers (background)
Some Data structure that ties the gene identifiers to the desired ontology

A user friendly library should even hide the last point and let me choose it by specifying fitting criteria in a high-level interface.
Let me show how your library should work like with some python pseudocode:
results = [(a small number of HGNC identifiers]
background = [(a larger number of HGNC identifiers)]

from goatools import GOEnrichmentStudyNS

study = GOEnrichmentStudyNS(results, background, organism="human", ontology="GO", identifiers="hgnc")
df = study.do_analysis()

et voila, the final dfshould hold my GOEA results. Two lines, not counting the initialization of the iterables. Sadly, the user has to search through undescribed example scripts that each contain hundreds of lines of code that doesnt explain much of what its doing and keeps the reader guessing. Even if I could make it work, I would have to spend days and write a high-level wrapper for myself, otherwise I'd end up with brittle and bloated scripts that become unreadable withing weeks.
I am sorry if I sound frustrated but I kinda am. Issues like these are some of the reasons why bioinformatics is needlessly hard.

For example, the R package clusterProfiler has a high-level interface that works exactly like that: https://yulab-smu.top/biomedical-knowledge-mining-book/clusterprofiler-go.html#clusterprofiler-go-ora

@szarecor I agree, the tone of my original wording was not constructive, hence I redacted it. However, I still stand by the content of the issue. I think it is constructive, as it actually provides an example for a real improvement that could be made that would greatly increase the usability of this library. I think it is relevant, since I have seen several other Issues going in the same direction.
On top of that, I point out an R library that does it exactly as in the example that I gave, adding further relevance and credibility to the issue.
I am not sorry for calling out a problem that has cost me several hours, since it has probably cost several hours to several hundreds of grad students. With the clusterProfiler package I had my solution within 15 minutes, so people should be advised to rather invest their time in learning r2py to integrate R in their python workflow.

I didn't imply anything, I directly addressed the issue that I have. It is nice that you guys figured it out, however, that doesnt mean it can't be improved. And again, I don't say the library is bad, it just has unnecessary hurdles that keep people from using it (and, thus, the people from citing the library's paper in their work). Just as an example of what could be easily improved:
For the command line usage, how should the three files look like? Does the ontology have to be an .owl file, an .obo file or is .csv okay, too? Does it work with Entrez Ids, Ensemble Ids or Gene Symbols? The only help refers to tests/data/which contains roughly 20 files, none of which is named like population_example_fileor study_example_fileor something. Why is the user kept guessing?
All I wanted is to point out how easy it would be to make this library ten times more accessible. I also get the feeling that this kind of improvement is not welcome here. I have now built my solution in python using lightgeoa and implemented missing features myself.


Move integration tests into a different folder.

The top level __ part kind of annoys me and it isn't significant to Jest in any way, so let's move some things around :)
cc @dmitriiabramov

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


do you have somewhere python code many records data for example file  2021_US_Region_Mobility_Report.csv

do you have somewhere python code many records data for example file  2021_US_Region_Mobility_Report.csv
maybe in your paid courses ?
I am looking how to use data with many records
all you code exampled in git are for very few records - small data files

https://forecastegy.com/posts/free-high-quality-marketing-mix-modeling-datasets/
On Wed, Sep 6, 2023 at 4:39 PM Sandy4321 @.***> wrote:

do you have somewhere python code many records data for example file
2021_US_Region_Mobility_Report.csv
maybe in your paid courses ?
I am looking how to use data with many records
all you code exampled in git are for very few records - small data files
—
Reply to this email directly, view it on GitHub
https://github.com/hammer-mt/VEX-MMM/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABIFJVAZYD6GT6G7GVEVTFLXZCKJPANCNFSM6AAAAAA4NRH2VA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


HDDS-4306. Ozone checkstyle rule can't be imported to IntelliJ.

What changes were proposed in this pull request?
CheckStyle: Move LineLength Check parent from TreeWalker to Checker, otherwise fail to import to latest IntelliJ
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4306
How was this patch tested?
Import to IntelliJ checkstyle plugin and verify there is no syntax error.

Thanks @adoroszlai for the review. The suggested change LGTM, I will make change in the next commit. One thing I notice that you suggest use LineLengthCheck instead of LineLength module. I think it is typo based on the document [here|https://checkstyle.sourceforge.io/config_sizes.html#LineLength]

One thing I notice that you suggest use LineLengthCheck instead of LineLength module. I think it is typo

Today I learned: both forms work fine.
However, you are correct, I didn't intend to propose changing the module name.  Even if both are OK, it's unnecessary for the fix.


Not seen for a while.

Seen again here:
https://sponge.corp.google.com/target?id=a902c438-fbd4-4f69-ae3c-c9c388527e99&target=github/grpc/aggregate_tests&searchFor=&show=FAILED&sortBy=STATUS

Only seeing this very rarely.


Is this project still active?

I see lots of stars, but almost no issues. The commits also dropped off sharply...

@tslater yes, internal development is done on a internal git repo and then pushed as release candidate branches (like the one currently opened 4 days ago which contains roughly 100 commits).

From what I understand, Tumblr has more people working on this project now than at any point in the past :)
That said, it would be certainly be nice if the internal repo could be pushed to github more often. The current setup makes it difficult for potential external users/contributors, since we may be branching off of stale code, unknowingly introducing merge conflicts, etc.

Yes, we are very much dedicated to Jetpants development as Dallas and Evan pointed out. We do have internal jetpants plugins for all of our custom logic but we make every effort to keep the core fully working and usable by other companies/individuals.
We definitely should be releasing new versions much more often.


matrix-appservice-irc: init at 0.8.0

Motivation for this change
I've never packaged a node package before, so feedback is welcome :smile:
This package is used to bridge matrix with IRC.
I'm gonna put some work into setting up a module of this later on, my plan is to make it very easy to set up on NixOS.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
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)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

@etu have you seen this? https://github.com/Ralith/matrix-appservice-irc-nixos

Nope, good to know. But I closed down my matrix server yesterday. That's
why I closed this as well since I don't need it.
On Fri, 27 Apr 2018, 01:47 Ruben Maher<EMAIL_ADDRESS>wrote:

@etu https://github.com/etu have you seen this?
https://github.com/Ralith/matrix-appservice-irc-nixos
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/38196#issuecomment-384821832, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAcMkoOiVZgROItGRqkgk-efw9qFVbuQks5tslyRgaJpZM4TCZB7
.


Submit a Bug report not working in 0.12.0 rc7

The Issue
Click the 'Submit a bug report' button in the help menu to report an issue.  Fill in description
click green 'Submit Report' button and nothing happens.    Has this been disabled on purpose?
Steps to reproduce

Click the 'Submit a bug report' button in the help menu
Fill in description
click green 'Submit Report' button and nothing happens

Expected behaviour
It should show some sort of notification that the report has been submitted
Actual behaviour
It shows no change.  Click the button as many times as you like.  It doesn't do anything.
System Configuration

LBRY Daemon version: 0.11.0rc3
LBRY App version: 0.12.0rc7
LBRY Installation ID: 6y7x4ht2F8NAtarEz8RSEw8DkXYuaeUJGTLQ19UWt4nJjWNJzsk7spJS9RSkAGRVzP
Operating system: Windows (Windows-10-10.0.14393)

Anything Else

Screenshots

@kauffj is this disabled for a reason or a bug? Fix in next release tag if needs corrective action?

This is fixed in master and will be fixed when 0.12.1 is released.


Android N support

Required Information

card.io Android SDK Version: 5.4.0
Nexus 5S, Android N DP4
Issue Description
User can't work with card.io in split screen: camera is not rotated, keyboard cannot be used.

@zerg0s


Support resolving node hostnames

It should be possible for pods to resolve node hostnames.
Apart from being generally useful, it is a also requirement for #2.

This is also needed for MetricsBeat, would love to see this working


Refactor, update styling, update content for about page

Description:
This commit makes the following changes to the About screen:

Removes the screen dimensions field and label
Restyled and repositioning the copy on the screen
Refactored the existing code and stripped out unused styling
Updates screenshots

The following global changes were also made to allow these changes to happen:

Created the faintViolet color variable and applied it to primaryBackground
Created the extraBold and header5 typography tokens

Linked issues:
https://trello.com/c/kptBs0kz/86-as-a-user-i-want-the-about-page-layout-to-be-consistent-with-the-mockups-and-the-spacing-typography-to-be-consistent-with-the-re
Screenshots:

Co-authored-by: Alex Chen<EMAIL_ADDRESS>

also looks like you need to run prettier: yarn format. you can also add prettier to vscode such that it runs on file save.


reuse session cookie:

Grab session cookie and store in keyring.  Attempt to reuse that
session cookie when requesting saml assertions

Really solid improvement! I like it a lot.


Update arithmetic of infinity

PR for consistency of arithmetic of infinite. Please see #36.

Much better indeed - thanks!


Add url to the app in production to the repo

You can add the url in the About section.

added to the readme


Make an "update ruff version every X months" github action

          That makes sense to me. Can we create a github bot or something to remind us to update every 3mo-6mo?

Originally posted by @korikuzma in https://github.com/GenomicMedLab/software-templates/pull/8#pullrequestreview-1863420536
Should be pretty easy: https://docs.github.com/en/actions/managing-issues-and-pull-requests/scheduling-issue-creation

I still think this would be nice to have, but still low priority IMO

@korikuzma I have actually thought about this a lot (for some reason) and will probably get something basic cooked up in the next week or two

I thiiiink this is done in #22 + additional commits. Time will tell!


Allow components to define the slot they are always filling

What problem does this feature solve?
We were currently working on a new UI component library where we want to try and keep the work for devs using it as minimal as possible.  Let's consider we have a Page component that comes with a Header and a Body.  The Header consists of a Title, and an Icon, and we can have some action buttons.
Keeping our devs in mind, we want to allow them to be able to do the following:
<template>
  <Page>
    <PageHeader>
      <PageTitle>Some brilliant page</PageTitle>
      <PageIcon><SomeIconComponent></SomeIconComponent></PageIcon>
      <PageActions>
        <Button>Update</Button>
        <Button>Delete</Button>
      </PageActions>
    </PageHeader>
    <PageBody>
      ... Contents could go here
    </PageBody>
  </Page
</template>

Now obviously we don't want the devs to alwahs have to think about how to structure the child components or in what order to pass them in.  Our UX designer might like the icon to the left and the buttons to the right of the screen, but he might change his mind later down the road... So: enter named slots.
Just looking at the PageHeader, we would create a component like this:
PageHeader.vue
<template>

      <slot name="icon"></slot>
      <slot name="title"></slot>

    <slot name="actions"></slot>

</template>

Now this all works brilliantly, but now to pass down the content to the right scope, a developer would have to do the following:
<PageHeader>
  <template v-slot:icon>
    <PageIcon>
      <SomeIconComponent></SomeIconComponent>
    </PageIcon>
  </template>
  <template v-slot:title>
    <PageTitle>
      Some brilliant page
    </PageTitle>
  </template>
  <template v-slot:actions>
    <PageActions>
      <Button>Update</Button>
      <Button>Delete</Button>
    </PageActions>
  </template>
</PageHeader>

This gets a bit verbose to me, so I was looking at the short hands that are supported
When there is only one slot passed down, we can get rid of the template tags because
<SomeComponent v-slot:name>
  Hello
</someComponent>

is a shorthand for
<SomeComponent>
  <template v-slot:name>
    Hello
  </template>
</SomeComponent>

But I can't get around the idea that this shorthand is a little useless.  Most of the times, you would be naming your slots exactly because you have more than one in a parent component, so those are the use cases where the shorthand doesn't work.
in an ideal world, I want my devs to not having to worry about this, and just be able to nest the components and have the components do their work
What does the proposed API look like?
So building on the example above, we would really like it if we could build our components as follows:
Page.vue
<template>

    <slot name="header"></slot>
    <slot name="body"></slot>

</template>

PageHeader.vue
<template v-slot:header>

    <slot></slot>

</template>

PageBody.vue
<template v-slot:body>

    <slot></slot>

</template>

then when we are creating a page, we could just do this:
<Page>
  <PageHeader>
    header content goes here
  </PageHeader>
  <PageBody>
    body goes here
  </PageBody>
</Page>

and vue would know that the pageheader and pagebody components would need to go into the slots named header and body respectively as defined in the Page component.
I've been trying to bend my mind as to why the shorthand doesn't work like this to begin with, but I'm sure I'm missing some info there, so feel free to let me know.
But when creating UI components like this, I believe somehing like this would really make things easier, and clean up a lot of the code we sometimes have.

<Page>
  <PageHeader>
    header content goes here
  </PageHeader>
  <PageBody>
    body goes here
  </PageBody>
</Page>

The above code means the same as the following code in terms of the current semantics:
<Page>
  <template v-slot:default>
    <PageHeader>
      header content goes here
    </PageHeader>
    <PageBody>
      body goes here
    </PageBody>
  </template>
</Page>

So I think it's probably the biggest obstacle to stopping this feature.

Yes, I realise this.  However, since a component in itself is a template, it feels like we have nested
I very much know it might be a breaking change, but it still feels like one I would enjoy ;-)

This is not even a breaking change, strictly speaking, but it inverts responsibilities and opens up a lot of questions both technically and from a DX perspective.

Technical: This change would require the compiler to be aware of the child component's "slot setting. this means, we can no longer compile an SFC on its own.
Similarly, from a DX POV: You can no longer actually infer from the parent template into which slot the content goes. You might be able to guess from the components names, but you will only ever know after having looked into the parent, the child and all of the individual slot components passed to the child.
Reusability: Will these components

throw an error if passed to a component not providing the proclaimed slot?
be usable as children of a normal
 element, where there is no named slot to fill?

Another DX problem stemming from the last point: Wrapping a slot child component in an element would likely have to break this contract, and require you to refactor into using <template v-slot:some-name> again:

<Page>
  <PageHeader>
    header content goes here
  </PageHeader>
  <PageBody>
    body goes here
  </PageBody>
</Page>

<! --- lets add a wrapper div for some positioning -->
<Page>
  <PageHeader>
    header content goes here
  </PageHeader>

    <PageBody>
      body goes here
    </PageBody>

</Page>

<Page>
  <PageHeader>
    header content goes here
  </PageHeader>
  <template v-slot:body>

      <PageBody>
        body goes here
      </PageBody>

  </template>
</Page>

I'm sure a lot more questions would pop up. I would therefore like to move this to the discussions area. If a proper proposal would come of this, an RFC could be written and officially proposed in the rfcs repo.

Hi @LinusBorg,
Thanks for the reply, and yes: I totally agree with your remarks / views.
Some feedback / questions I have:

Technical: you mean you can not compile the parent sfc on its own then?  Because I don't see an issue for the child component, unless I'm missing something that I didn't get.  Also, for the parent: what is the use case of wanting to compile a parent without its children?  I'm guessing you have a reason and valid point here, but I just don't see it.
I agree.  However, it would be up to the developer to decide whether he wants the behaviour; he would still have the ability to use the

<Page>
  <PageHeader v-slot:header>
  </PageHeader>
</Page>

as a shorthand for
<Page>
  <template v-slot:header>
    <PageHeader>
    </PageHeader>
  </template>
</Page>

which in my book also makes more sense as then it feels like I'm adding the v-slot directive to the

Reusability: In my book, this would only be used in components that belong to a UI library where you can't have a child without the parent for instance.  You can't have a  without a wrapping  or  for instance.  Likewise we would only be using it where a PageHeader for instance is supposed to be wrapped inside of a Page component otherwise messing up the UI.  It would actually prevent devs to use the PageHeader outside of a Page component.  I agree however that the usage would have to be documented, but I still see a lot of added value here.

I totally understand this is not a quick bugfix and definitely believe this should be treated as an RFC.  Is that something you need me to do something for?

Technical: you mean you can not compile the parent sfc on its own then? Because I don't see an issue for the child component, unless I'm missing something that I didn't get.

slot content is compiled into a function which is passed down to the child component. This function has a closure over the parent template, but is run in the child, so the child collects the reactive dependencies (so that the child re-rendered when they change, not the parent. So the compiler has to know - while processing the parent component - which part of the slot content has to be wrapped in a function, and into which slot it has to be passed.
h(Parent, {}, {
  header: () => h(PageHeader)
  default: () => h(PageBody)
})

Also, for the parent: what is the use case of wanting to compile a parent without its children? I'm guessing you have a reason and valid point here, but I just don't see it.

So far, the compiler can process each SFC completely on its own. it's not important what other SFCs contain in order for the compiler to do its work.
Your proposal would require a re-work of the compiler to process the child components of an SFC as well, in order to understand which slot they belong in. Further: Vue allows for components to be globally registered. Now the compiler would have to somehow know which components from the template are registered globally, and where to find their code, in order to check which slot they belong in, and so forth.
Also, components could be imported from a precomiled package in node_modules, so now the compiler has to analyse the AST of this package to find the component, and its slot setting while compiling Parent.
Just a giant complexity increase.

Reusability: In my book, this would only be used in components that belong to a UI library where you can't have a child without the parent for instance. You can't have a li without a wrapping ul or olfor instance. Likewise we would only be using it where a PageHeader for instance is supposed to be wrapped inside of a Page component otherwise messing up the UI. It would actually prevent devs to use the PageHeader outside of a Page component. I agree however that the usage would have to be documented, but I still see a lot of added value here.

I find this to be a limited use case that so far, doesn't warrant the complexity and work is would bring with it.

I totally understand this is not a quick bugfix and definitely believe this should be treated as an RFC. Is that something you need me to do something for?

I personally am not a fan of the  implicit context-dependent behavior this proposal would introduce, just for saving keystrokes. An RFC is a lot of work and needs something how believes in the proposal and is willing to work for it.
I am not that person. You either need to be that yourself or find someone willing to be.
PSA: I'll move this to discussions.


chore(main): release 1.0.0

:robot: I have created a release beep boop
1.0.0 (2024-07-07)
Features

init (74cf8ed)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.0.0
:sunflower:


i get error while the code is uploading

even though when i upload the code to my esp32 from arduino ide it works. the upload finishes but i don't see managmentAP ssid in wifi networks available here is the error in the brackets
(Uploading stub...
Running stub...
Stub running...
Changing baud rate to 115200
Changed.
Unable to perform XMC flash chip startup sequence (Cannot configure port, something went wrong. Original message: PermissionError(13, 'A device attached to the system is not functioning.', None, 31)).
FLASH_CRYPT_CNT 0
ABS_DONE_0 False
Compressed 24016 bytes to 14877...
Compressed 3072 bytes to 103...
Compressed 723248 bytes to 447613...
is stub and send flash finish)

I don't understand the issue. You said that uploading the code using Arduino IDE works, but the title and error says that there was an error while uploading/flashing the code onto the ESP32. If you have problem with flashing the code, it's not related to this project and you should ask on ESP32 forum for help.

Thanks.... issue resolved my data cable was faulty i think


Module build failed: TypeError: ngAnnotate is not a function

Run with npm run start or other, report error:
... ...
ERROR in ./src/website/bootstrapApp.js
Module build failed: TypeError: ngAnnotate is not a function
    at Object.module.exports (/Users/hugo/programming/github/workflow/webpack-gulp-es6-angular-express/node_modules/ng-annotate-loader/loader.js:68:24)

... ...

ERROR in ./src/server/main.js
Module build failed: TypeError: ngAnnotate is not a function
    at Object.module.exports (/Users/hugo/programming/github/workflow/webpack-gulp-es6-angular-express/node_modules/ng-annotate-loader/loader.js:68:24)
 @ multi main

I assume you are working on Windows ... I have just updated the repository, that issue should now be fixed.

As shown absolute path above, i am not working on Win.
My env is:
OS: "mac os x", version: "10.10.5", arch: "x86_64", family: "mac"
Node:  v5.0.0
Webpack: 1.13.1
And this error still exists.

Delete the 'node_modules/ng-annotate-loader' folder at the root of the project, do 'npm install' and it should work

Thank you very much. it works now.


COOK-98 Add CDAP SDK bin to PATH

This adds the CDAP SDK bin directory to the system's PATH for login shells.

This is currently failing tests due to some cookbooks that have been updated to require Chef 12+ that are indirect dependencies. I'll have to work these out and update the Berksfile before this can be merged.

👍 lgtm


Unhelpful error message when running make

$ cd /tmp
$ git clone https://github.com/evanmiller/ChicagoBoss.git
Initialized empty Git repository in /tmp/ChicagoBoss/.git/
remote: Counting objects: 2321, done.
remote: Compressing objects: 100% (1069/1069), done.
remote: Total 2321 (delta 1674), reused 1626 (delta 1202)
Receiving objects: 100% (2321/2321), 990.49 KiB | 228 KiB/s, done.
Resolving deltas: 100% (1674/1674), done.
$ cd ChicagoBoss/
$ make
==> ChicagoBoss (compile)
make: *** [all] Error 1
-> How to troubleshoot this issue further?
Operating System is Ubuntu 10.10. and Erlang version is:
Erlang R13B03 (erts-5.7.4) [source] [smp:2:2] [rq:2] [async-threads:0] [hipe] [kernel-poll:false]

Can we just get this one out of here? Seems like it's a non issue.


Multiple devices launch in ros2

Hi @AdamPettinger ,
Thankyou for maintaing the repo. I have multiple devices of nano17 F/T sensor. I have changed the IP_address of the devices in webpages
device-1 : <IP_ADDRESS>
device-2 : <IP_ADDRESS>
I launched the
ros2 run netft_utils netft_node --address <IP_ADDRESS>

and
ros2 run netft_utils netft_node --address <IP_ADDRESS>

in diff. terminals.
I see there is conflict in same topic names. May I know how to diff. the topic names based on the no. of devices.

Did changed the netft_node.cpp so it will take the ipaddress last digit and append to topic name.
// Extract the last digit of the IP address
  size_t last_dot_pos = address.find_last_of('.');
  if (last_dot_pos == string::npos) {
    cerr << "Invalid IP address format" << endl;
    exit(EXIT_FAILURE);
  }
  string last_digit = address.substr(last_dot_pos + 1);

  // Set up ROS publishers
  auto node = std::make_shared<rclcpp::Node>("netft_node" + last_digit);
  const rclcpp::QoS qos(10);
  rclcpp::Publisher<std_msgs::msg::Bool>::SharedPtr ready_pub = node->create_publisher<std_msgs::msg::Bool>("netft_ready" + last_digit, qos);
  rclcpp::Publisher<geometry_msgs::msg::WrenchStamped>::SharedPtr geo_pub = node->create_publisher<geometry_msgs::msg::WrenchStamped>("netft_data" + last_digit, 100);


Select Field Filtered By More than one Field

I think it could be interesting fielter a select field by more than one model, i.e., I have a model that can be filtered by n models, because it have n foreign keys and it could be usefull filter it by more than one model.

I think this is outside the scope of this project. That would be incredibly difficult to actually implement with this project.
This is exactly the type of thing that django-autocomplete-light was designed for and could absolutely handle.
Due to that, I'm going to close this. But feel free to contribute more ideas!


Process multiple requests per worker

Currently, we can't process multiple requests in parallel on a single worker. This means that the number of concurrent requests is limited by the number of web workers which is far from optimal.
I vaguely remember we had a reason for this temporary hot-fix, but I'm unsure whether it was just to move fast or if there was some big blocker for implementing this feature.

I see this in 99b98c6c:

This regresses our ability to handle streaming, but fixes the
concurrency problems.

The problem is that we need a "request context" to assign model operations to their request. For example, when mutating an entity in database, we need to check that the current request is not a GET; and we also need to use a separate transaction (or transactions) for each request.
At this moment, we keep the "request context" in a global variable, which means that one Javascript global context can handle just a single request. We either need another way to keep the "request context" around, or we need to have multiple global contexts.


Seems to be case sensitive

I thought this was meant to be case-insensitive (and I wish it was), it frustrates me constantly that it doesn't seem to be.
$ z -l ia
common:    /Users/George/Documents/Subjects/Computing/BritishInformaticsOlympiad
0.5        /Users/George/Documents/Subjects/Computing/BritishInformaticsOlympiad/2017
0.75       /Users/George/Documents/Subjects/Computing/BritishInformaticsOlympiad/2016
1.5        /Users/George/Documents/Subjects/Computing/BritishInformaticsOlympiad/2016/Challenge
4.5        /Users/George/Documents/Subjects/Computing/BritishInformaticsOlympiad
16         /Users/George/Documents/Subjects/Computing/BritishInformaticsOlympiad/2015
$ z -l IA
common:    /Users/George/Documents/Subjects/Maths/IA
0.5        /Users/George/Documents/Subjects/Maths/IA/Examples
7          /Users/George/Documents/Subjects/Maths/IA
19.5       /Users/George/Documents/Subjects/Maths/IA/Resources
149.5      /Users/George/Documents/Subjects/Maths/IA/LaTeX

It uses a "prefer case sensitive" algorithm. See examples at https://github.com/rupa/z/issues/209#issuecomment-342682486

I also wish z to be case-insensitive. I am on MacOS.

I've submitted PR #221 that allows smart case sensitivity matching by default, and adds parameters to force case insensitive or case sensitive matching. Solution is just 1 LOC bigger than the original implementation.


PHOENIX-6290 Extend IndexRegionSplitPolicy from SteppingSplitPolicy o…

…n master

I missed this in PHOENIX-6286 @gjacoby126.
Now that you mentioned it in your previous review, I've checked it, and it uses the default policy for HBase 1, but HBase 2 has changed the default policy again, and we didn't apply that on master.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
9m 58s
the patch passed

+1 :green_heart:
compile
1m  1s
the patch passed

+1 :green_heart:
javac
1m  1s
the patch passed

+1 :green_heart:
checkstyle
0m 30s
phoenix-core: The patch generated 0 new + 11 unchanged - 1 fixed = 11 total (was 12)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 52s
the patch passed

+1 :green_heart:
spotbugs
3m 41s
the patch passed

_ Other Tests _

-1 :x:
unit
116m 45s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 27s
The patch does not generate ASF License warnings.

157m 44s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1046/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1046

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux dd7b45d37ab8 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / d097857

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1046/1/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1046/1/testReport/

Max. process+thread count
6675 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1046/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Add dummy diff for internal review

Add dummy diff for internal review
Choose a PR Template
Switch to "Preview" on this description then select one of the choices below.
Click here to open a PR for a Data Plane API.
Click here to open a PR for a Control Plane (ARM) API.

I don't see other swaggers adding the repeatability-result header to responses either, so should be okay but we can ask in the Azure REST API stewardship review


send explicit deauth if not default

Closes #589

@llewelld I've invited you for the review as you raised the point in the first place 🙂

Yeah, I have to admit I was surprised myself that we don't have that call as part of the django-open-humans package! Do you want to make an issue in the GH repo of the project or should I? :)

Yeah, I have to admit I was surprised myself that we don't have that call as part of the django-open-humans package! Do you want to make an issue in the GH repo of the project or should I? :)

As it happens I started creating a PR; I'll submit it shortly.

Awww, thanks!

Great, thanks! 🚀


Naming things is hard

https://github.com/sammcj/gollama
🤣

It's not my problem, I don't know this project.


Increase kubelet klog verbosity

What would you like to be added:
The Kubernetes community recommends a logging verbosity of 2 for most systems. Today, we use the default V(0), unless a different verbosity is explicitly passed via userData as an extra Kubelet argument.
We should set the logging verbosity to V(2) by default in our AMIs to follow the recommendation.
Why is this needed:
Increasing Kubelet verbosity will help when reading Kubelet logs while debugging issues. Increased verbosity may also decrease the resolution time on support tickets.

It would be interesting to see if there's feedback around changing the default value here. Some things Bronson and I have discussed:

Today we manage log rotation through journald and we set the max usage to 15% of disk space. This isn't changing.
We do not configure a max retention time, this won't be changing?
It would be interesting to learn about how users set up agents to export logs - fluentbit / fluentd and if this change affects their log aggregation process?
There is still a way to change the logging to the earlier default level of 0 by passing kubelet-args.

I'd be interested in customer feedback as well. Customers who replace nodes regularly may not have gotten anywhere near the 15% disk usage and may start to see it now. Customers will potentially see a surprise increase in expense or compute needs to manage the logs, though I'm not sure how much of a difference we're talking about, if it's minor or significant.

Before we resolve this issue, let's add a short section to the README on how customers can override the kubelet verbosity in userdata.

https://github.com/awslabs/amazon-eks-ami/pull/629 was merged. Closing issue.


Fix spelling and add an icon to GitHub link

This just fixes a minor inconsistency in your gh-page design, but it was bothering me for a while already #ocd :grimacing:

Thanks, I think I never realised it was GitHub and not Github :)
However FYI, you did the change directly from the gh-pages branch which means this will be overridden on the next deployment. You should have do the change from the master branch instead. It's fine I'll apply your patch there as well.


chore: ignore generated markdown in pull requests

It is hart to test it now without content so we need to rebase our feature branch


Added: Blog list page and rough outline of blog display page

So I have done the student blog page as reference given.

and added the link that will include the unique id of blog that should be extracted from db (need to do styling)

#26


issue/hitide-ui-42: made potential fix to image links

Changes

changed source of where collection thumbnail images come from (cmr vs hardcoded)

Notes

I am not able to load the affected collections on my development build so I can't test this fix until it is UAT or I can access the proper collections in my HiTIDE development build.

Update

I was able to fix the bug that prevented the collections from showing up in my local development branch. It looks good to go now.

This PR is associated with #42

@jbyrne6 We don't want to add the .vscode dir to the repo.  That's only for the IDE.  Can you take that out?
Thanks!

@jbyrne6  Can you look at maybe trying to grab the URL from CMR instead? That seems to be more reliable way, and that url you put in there seems like it could change.
In CMR it looks like this:
{
"Description": "Thumbnail",
"URLContentType": "VisualizationURL",
"Type": "GET RELATED VISUALIZATION",
"URL": "https://podaac.jpl.nasa.gov/Podaac/thumbnails/AMSR2-REMSS-L2P-v8.2.jpg"
},
You can grab the RelatedURL with description Thumbnail, and then return the URL.

What do you think @sliu008 ?


Improve info card hover effect

Changes

New hover effect
Add link around profile image

Screenshots

Before
After

@rabilrbl The same component seems to be used over here

Let's not have the hover effect here


Py38 compatibility

Fixes compatibility with Python 3.8 and adds newer Pythons to tox and travis configurations.
Could you please release a new version with this fix?

The failures are caused by missing Python interpreters. If you want, I can transform travis configuration to use https://github.com/fedora-python/fedora-python-tox which is Docker image based on Fedora with all available Pythons installed which would solve this and future problems with missing Python interpreters.
What do you think?

And now there is another problem with Python 3.11. assertEquals no longer works as an alias for assertEqual. Please let me know if you want me to finish this PR, fix scales for the latest Pythons and test it with them.


Use mixer python code to convert global dictionary.

MIxer python global dictionary conversion code did not use "yaml" package.  Instead it is just checking "-" prefix.
https://github.com/istio/mixer/blob/master/bin/generate_word_list.py
If python yaml is used, 200 has to be wrapped with single quote as '200' so it will be loaded as string instead of int.
Since mixer converter did not use yaml loading,  mixer dictionary is using '200' with single quota.
To be consistent,   mixerclient should not use yaml loading too. Instead of changing mixer, it is easier to change client.

Jenkins job mixerclient/presubmit passed

Jenkins job mixerclient/presubmit passed


Feature/validation reports

Added first daily report for 2023-11-27

Preview: https://pr-179-preview.khpreview.dea.ga.gov.au/validation/daily-report/


Separate get modes in different funcs

I believe this way the code is more readable, easy to maintain and less error prone.
The separate get functions save some ifs and only need to deal with a single operation mode each. The get implementation is chosen at initialisation time once. Just as valSafe() was choosing the operation mode before.
This is just a refactor, the functionality should stay exactly the same. Otherwise it was an unintended mistake.

Does this change performance/inlining properties, adding that indirect call?

Does this change performance/inlining properties, adding that indirect call?

Right!
Haven´t bench-marked this, but yes, most likely the dynamic call will prevent in-lining.
Perhaps a more surgical change could still provide more readability while keeping the original performance characteristics: Use just a single if wrapping both code paths entirely instead of trying to avoid repeating a few instructions in both code paths by doubling that if.


CASMINST-5302: Added Networking, User, and Metal release notes for Papaya

Added Networking, DNS, and DHCP entries to the release notes

The lint check is invalid and should be ignored.

The lint check is invalid and should be ignored.

This is the only relevant line from the lint check
https://github.com/Cray-HPE/docs-csm/actions/runs/3091355378/jobs/5001321425#step:5:13

We don't care about that line.  The changes are intended to have duplicate headers.  I didn't see a way to ignore lines or checks, only files.

I just rebased these changes on top of the latest release/1.3 changes.


Read only property for ServerObjectManager nextNetworkId

Please explain the suggested feature in detail.
Adding a read only property for what the next NetId that would be assigned to a spawned object.
How exactly does this keep you from releasing your game right now?
I use network id's as a form of ownership check on clients, and being able to access the net id before spawning so that its part of initial payload is ideal.

You can create a very simple NetIdGenerator and set the field on ServerObjectManager. And then add the Next Id a public field on that.
Would be better to use a custom NetIdGenerator instead of add a getter for next id. The property would only be able to give the next ID if using the default ids but not if using Generator.


Czech translation

The Vanced team only accepts translations over crowdin.
https://crowdin.com/project/vanced
https://crowdin.com/project/vanced-manager
You're going to want too go to the upstream https://github.com/microg/GmsCore for microG translations.

@gghhkm it's fine to do PR for vanced microg settings as we have strings not in upstream


Right edge doesn't scroll (MacOS 14 inch)

On my machine the upper, left, and lower edges scroll just fine, the right edge doesn't scroll, no matter how much to the right I move.
Let me know if there's some way I can help debug this.

Similar behavior in windowed mode, actually: The mouse has to be out of the game completely to scroll, see video:
https://github.com/lampe-games/godot-open-rts/assets/297744/47501399-18fe-4b51-8c3c-ba8bb225b498
Restricting the mouse to the game window (in settings) doesn't help but makes it so that the mouse sometimes moves to the left by itself when moving it to the right at the right edge.

Similar behavior in windowed mode, actually: The mouse has to be out of the game completely to scroll, see video.
Restricting the mouse to the game window (in settings) doesn't help but makes it so that the mouse sometimes moves to the left by itself when moving it to the right at the right edge.
https://github.com/lampe-games/godot-open-rts/assets/297744/3845bdc1-4493-4666-9886-dbc53c601fca

@domenukk can you try increasing screen_margin_for_movement of IsometricCamera3D of res://source/match/Match.tscn ?

Setting it to 2 helped.
Related, the "Restrict the mouse" option seems pretty broken though, also unrelated to the scroll behavior. When set, the mouse sometimes moves up when I try to move down. I can open an extra bug for that if it helps (hard to explain, though)

@domenukk feel free to create separate ticket for that


Add functionality to use ZooKeeper ACLs. Disabled by default

This stops (or at least impedes) an attacker with network access to ZK
from injecting data into ZK, e.g. injecting data causing a malicious job
to be deployed on some or all agents.
Everyone, including unauthenticated users, has read access to all data.
For futher permissions credentials are needed. Agents and masters use
different credentials, limiting the consequences if the agent credentials
are compromised.

@rohansingh @mattnworb @davidxia
This is still WIP. There stuff left to do:

Documentation (?)
Tests to make sure it all works
Ideally, we also set it up so that at least some integration tests run with ZK ACLs disabled, to verify that that still works as it should
???

the stuff with the list of Rules in ZookeeperACLProvider is nice :ok_hand:
but it feels weird to me to hardcode the list of rules in the constructor as oppose to passing them in - makes the other functionality of that class (scanning the list of rules and OR-ing things together) harder to unit test since you can't test it with different variations of rules. I would suggest moving the hard-coding up a level so you can test the class.

@mattnworb yeah that [moving the list of rules out of the ctor] probably makes sense. it bugged me too -- but I wasn't  sure the extra boilerplate needed would be worth it.
(If you just want to be able to test with different rules, a quick and dirty approach is to create an auxiliary getAclForPath(String path, List<Rule> rules) method and make it package-local)

@gimaker or just add an overloaded constructor like
public ZooKeeperAclProvider(final String masterDigest, final String agentDigest) {
  this(masterDigest, agentDigest, DEFAULT_RULES);
}
public ZooKeeperAclProvider(final String masterDigest, final String agentDigest, List<Rule> rules) {
   ...
}

@mattnworb Yeah, supplying the rules in the ctor is what I'm thinking of doing. But it requires extra scaffolding/refactoring since the rules contain the digests as it is now (in the Id object).

womp womp czechstyle

Current coverage is 45.08%

Merging #803 into master will increase coverage by +0.20% as of 8e2e5b3

@@            master    #803   diff @@
======================================
  Files          259     263     +4
  Stmts        10852   11084   +232
  Branches      1511    1539    +28
  Methods          0       0
======================================
+ Hit           4871    4997   +126
- Partial        432     445    +13
- Missed        5549    5642    +93

Review entire Coverage Diff as of 8e2e5b3

Powered by Codecov. Updated on successful CI builds.

This is looking good to me at this point.
@davidxia @mattnworb Could you please review?
@gimaker Was there anything more you wanted to add or do?

@rohansingh nope, not really. Ideally it'd be good to have some tests that run without ACLs to make sure things still work when they're disabled, but maybe that's not needed? Other than that, the only thing that comes to mind is if we want to give agents more permissions on everything under status - e.g. give the CRWD on everything under /status/hosts/<host>, to avoid problems if we ever need more permissions.

Another thing that might be prudent to do is to run all tests and examine the logs for NoAuth exceptions (that may be problematic even though they don't cause tests to fail?).

:+1: from me, nice work

:+1:

@gimaker I think for now let's stick with the permissions we have. If giving agents more permissions becomes necessary in the future, we can do it then. Folks will have to rerun helios-initialize-acl, but that shouldn't be too big of a deal.

@rohansingh WFM. If we want to change permission in the future, helios-initialize-acl will need to be re-run with "super" authentication, as neither the client nor the master user has ADMIN permissions (and thus cannot change ACLs on existing nodes).


Supervisely, Fmask support

Should probably merge the changes, regardless of the fact that the splitting of pre-processed products is not implemented yet?

Ah, would also need to update the build-check for the new dependencies.


Plugins for popular Test Runners

Add to the stackinabox.util functionality for plugging into some popular testing functionality to make it easy to integrate:

[ ] PyTest Plug-in, Fixtures
Others?

Make sure to make it an optional dependency if support is ever added


Add CMake PLATFORM option for SDL

Adds a PLATFORM=SDL option to CMakeLists.txt, handled in LibraryConfigurations.cmake
Tested on Win 11 ARM64 (MSVC, vcpkg)

@awfulcooking Thanks for the review!

Currently, the examples fail to build for me.
cmake .. -DPLATFORM=SDL
...
[  3%] Linking C executable audio_mixed_processor
/usr/bin/ld: ../raylib/libraylib.a(raudio.c.o): undefined reference to symbol 'exp@@GLIBC_2.29'
/usr/bin/ld: /usr/lib/libm.so.6: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status

This patch sorted it.
-    target_link_libraries(${example_name} raylib)
+    target_link_libraries(${example_name} raylib m)

However, I ran into the following issue on raylib_opengl_interop.c:
[ 44%] Building C object examples/CMakeFiles/raylib_opengl_interop.dir/others/raylib_opengl_interop.c.o
/home/peter/pg/raylib/examples/others/raylib_opengl_interop.c: In function ‘main’:
/home/peter/pg/raylib/examples/others/raylib_opengl_interop.c:94:5: error: unknown type name ‘GLuint’
   94 |     GLuint vao = 0;
      |     ^~~~~~
/home/peter/pg/raylib/examples/others/raylib_opengl_interop.c:95:5: error: unknown type name ‘GLuint’
   95 |     GLuint vbo = 0;
      |     ^~~~~~
/home/peter/pg/raylib/examples/others/raylib_opengl_interop.c:96:5: error: implicit declaration of function ‘glGenVertexArrays’ [-Werror=implicit-function-declaration]
   96 |     glGenVertexArrays(1, &vao);
      |     ^~~~~~~~~~~~~~~~~
/home/peter/pg/raylib/examples/others/raylib_opengl_interop.c:97:5: error: implicit declaration of function ‘glBindVertexArray’; did you mean ‘rlLoadVertexArray’? [-Werror=implicit-function-declaration]
   97 |     glBindVertexArray(vao);
      |     ^~~~~~~~~~~~~~~~~

I think this is not because of cmake. This example only checks #ifdef PLATFORM_DESKTOP before trying to include the necessary headers (glad). Changing it to PLATFORM_DESKTOP || PLATFORM_DESKTOP_SDL sorts that.
After that fix, rlgl_standalone.c fails to link due to lack of glfw symbols. This one should just be skipped. Actually, this one is also a problem with a glfw shared lib, because that doesn't expose the glfw symbols to the linker either.
I'll submit PRs for the issues I identified here, and investigate skipping the standalone example at a later date.

Fwiw

https://stackoverflow.com/a/54935652
Visual Studio does not need or want you to explicitly request linking the math library. You must avoid adding it as a link library when building for Windows. Instead of unconditionally doing target_link_libraries(MY_EXECUTABLE m), then, you might use:
IF (NOT WIN32)
  target_link_libraries(MY_EXECUTABLE m)
ENDIF()


Remove --watch mode

Codecov Report

Merging #585 (72a9910) into main (89ede91) will increase coverage by 1.14%.
The diff coverage is 0.00%.

:exclamation: Current head 72a9910 differs from pull request most recent head ba05d02. Consider uploading reports for the commit ba05d02 to get more accurate results

@@            Coverage Diff             @@
##             main     #585      +/-   ##
==========================================
+ Coverage   48.92%   50.06%   +1.14%
==========================================
  Files          43       43
  Lines        2228     2177      -51
==========================================
  Hits         1090     1090
+ Misses        954      903      -51
  Partials      184      184

Impacted Files
Coverage Δ

pkg/commands/options/filestuff.go
0.00% <ø> (ø)

pkg/commands/resolver.go
35.29% <0.00%> (+4.59%)
: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 89ede91...ba05d02. Read the comment docs.

This is ready to go now.


Missing label

There is no label element in the dialog container for the cities, so the "Lighthouse" tool will throw an error of accessibility.

Hi!
Thanks for the feedback. I've rewritten the codelab from scratch and believe I have fixed this issue. The code has been updated, and the new guide is now live.
If you find any issues with the new codelab, please let us know!
Thanks!


ENH:  Series between inclusive pair (GH: 12398)

[ X  ] closes #12398
[ X ] tests added / passed
[ X ] passes git diff upstream/master | flake8 --diff
[ X ] whatsnew entry

Amends pandas.Series.between method to set different inclusive/exclusive endpoints.
inclusive : Boolean to indicate whether or not to include both the left
and right endpoints (True: a <= series <= b, False: a < series < b),
or an iterable boolean pair to set them separately, e.g
inclusive=(False, True) for a < series <= b.

I guess. pls add some doc-string examples
use closed='left'|'right'|None like we do for DatetimeIndex
closed : string or None, default None
    Make the interval closed with respect to the given frequency to
    the 'left', 'right', or both sides (None)

up pls update for 0.18.1. pls also create a new issue to deprecate .between (and i'll mark for 0.19.0)

closed in favor of #13027


Updates CLI version metadata of every v7 sample script. Closes #5440

Updates CLI version metadata of every v7 sample script. Closes #5440

Thank you @nanddeepn, we'll try to review it ASAP!

Merged manually, thank you!


Dim timer when idle

Implement's @pmarsceill's idea in #12.
Screenshots

Closes #12.

This looks good!


Fixing swagger model validation failures

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[x] Other, please clarify:

_There were swagger model validation failures in some of the ExpressRoute files. They were throwing following error: Long running operation should return location or azure-AsyncOperation in header but not provided. Fixed this in all such files _

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Please fix Swagger LintDiff errors too . Looks like Location header should also be present.


Fix CONTRIBUTING links

Currently some of them are not pointing to the correct place.
Notice that in the beginning of the file there is the following, which looks like links that were not applied because of missing md related parts:

Thanks for this!


Try to delete a record with relationship field failed, and then can do nothing

I created a entity named "Category", and a relationship field (one to more) named "things" to entity "Thing", if I want to delete a record that things count >0, that will be failed, and then I can do nothing, all operations will be failed, include create / edit /delete.
How to fix: Restart my app, everything will be well.
By the way, I added the checking function for things field that count must <= 0, but if somewhere I lost the checking function, issue will be raised again.

@Talnaj what's the deletion rule of your relationship from Category to Things?


Whitespace in the Firestore document ID

Description
If there is a space in the Firestore document id the MeiliSearch record will not be created and nothing logged
Expected behavior
A functions log tells that whitespaces not allowd
Current behavior
Nothing in the logs
Screenshots or Logs

Environment (please complete the following information):

OS: [e.g. Debian GNU/Linux]
Meilisearch version: [e.g. v.0.20.0]
firestore-meilisearch version: [e.g v0.1.0]

Hey @yamankatby , thanks for raising this :)
Currently, no errors are raised as the extension is not aware an error occurred. Since adding documents in Meilisearch is an asynchronous task, to know if the addition was successful we need to check on the task later on. Which this extension does not.
To still have the knowledge of the error, adding an id validator checking on all the formatting requirements of a document id is a good idea. Nonetheless, other task-related errors will remain un-logged and you'll only be aware of it by checking the tasks statuses manually.


Add keyword extraction logic and rename source text collector directory

Fixes
Nothing, but partially addresses #55
Description

Renames html_tag_collector directory (and associated references) to source_tag_collector
Create KeywordExtractor, a tool that utilizes the KeyBERT library to extract keywords from a web page's html

Testing

A unit test has been created in test_source_text_collector_unit.py, which can be run to demonstrate basic functionality of the added method
The integration test in test_source_text_collector_integration.py can be run on the given urls (or others) to see how the keywords appear alongside other included elements

@EvilDrPurple would you want to test this one / leave your review?

I tested it and looks very good. One thing I should note is it took about 10 minutes to execute for 18 urls, meaning it will take approximately 37 hours to run on our current list of over 4000 urls. Perhaps we could add an option to disable the keyword extractor, sort of like how it's done with the render-javascript feature. This way when we don't need the keywords generated we don't have to wait a very long time to get the tags.

I tested it and looks very good. One thing I should note is it took about 10 minutes to execute for 18 urls, meaning it will take approximately 37 hours to run on our current list of over 4000 urls. Perhaps we could have the keyword extraction disabled by default, sort of like how it's done with the render-javascript feature. This way when we don't need the keywords generated we don't have to wait a very long time to get the tags.

I may like to take a second look at how I'm implementing it -- considering the model is pre-trained, in theory labeling shouldn't take so long after the initial download of the model.
I may also need to think about how to test it to account for the sort of hardware we would run it on, as I may get faster run times because of my personal hardware which could bias my assessment of its performance in the cloud.
I also confess that I had tested it primarily for functionality and not performance, which is worthwhile for me to take into consideration. Relatedly, @josh-chamberlain, I wonder if the PR template might benefit from the inclusion of a header called "Performance Impacts" or something similar, to encourage disclosing how a change impacts execution time and other metrics.

@josh-chamberlain In terms of implementation, I see several possible options. There are others, but these stand out to me as most apparent:
Option 1: Inclusion in source_text_collector.py, under all conditions
Pros

Code is already designed for that, so minimal alterations would be required
Ensures consistent output in data

Cons

Permanently increases execution time of source_test_collector.py
Impact of keywordization may be variable, depending on data -- for web pages with little code in expected structures, keywords may improve overall quality of data. For web pages that already have a lot of content, keywords may not add much

Option 2: Inclusion in source_text_collector.py, under select conditions
Pros

Enables greater flexibility in when to apply, enabling saving time on data that is unlikely to require it
Dynamic application of keywordization can potentially equalize quality between high-content and low-content web pages.

Cons

Will require modifications to setup, both for obtaining metrics to determine when to apply keywordization and the conditional logic to execute it
Dataset becomes more inconsistent -- some rows may have data columns which others lack, which could have unpredictable effects on performance.

Option 3: Implement at separate, later point in pipeline
Pros

Decouples keywordization from other parts of process, enabling greater testability and the ability to more easily disable its functionality if the need arises
Enables keywordization to be implemented at a separate time from other parts of pipeline, improving flexibility and possibly resilience to failure (i.e. if keywordization fails, the rest of source_text_collector.py won't be halted)

Cons

Data for keywordization will either need to be saved for execution (using extra storage space) or re-retrieved when performing keywordization (increasing execution cost as opposed to including it within the other code.
Will require more substantial revamping of code, as well as clarification on where to include the code

@maxachis got it, so we're adding 5.5 seconds per URL on your machine. As a basis for comparison, how long does each URL take on your machine without adding keywords?
Either way, I would probably recommend we test whether adding keywords improves accuracy before merging this. Hard to know whether it's worth it otherwise

@bonjarlow Per your discussion in the last working meeting about how removing the URLs seems to have a negative impact on accuracy, have you looked at how keywords impact accuracy when URLs are removed from the picture?

@maxachis yeah I've played around with different combinations of features,  it seems the model tops out at ~70% with or without keywords. I'll make an issue now

For additional clarity, the issue in question is #75

@bonjarlow @EvilDrPurple Coming back to this: What are your thoughts on including this keyword extraction as a part of the tag collector function? Is this useful/potentially useful enough to include?

@maxachis What if we only generate_ keywords from the human-annotated data? We'd have fewer URLs, guaranteed to be used for training. I think we could use those keywords to scope common crawl or otherwise generate better batches, too.

@maxachis What if we only generate keywords from the human-annotated data? We'd have fewer URLs, guaranteed to be used for training. I think we could use those keywords to scope common crawl or otherwise generate better batches, too.

@josh-chamberlain I'm intrigued by these thoughts, but I'm unclear on how the process would work. Does this mean that humans come up with the keywords, or that we apply automated keyword generation to only human-annotated data? Or some fancy third option?

@maxachis we could ask people for keywords, but I was thinking it would work the same way you had in mind—except only applied to annotated sources. It's a way to worry about a lot fewer keywords with maybe better quality.
It does mean more editing data mid-stream...we'd have to get really good at modifying label studio / hugging face data in a sensible way.

With that in mind, I'm wondering if this PR is ready for prime-time, or if it might need some adjustments. Because as of right now it's designed to pull keywords from everything being pulled.

@maxachis yeah, I just updated #49 to mention it. I think we should only do it for labeled sources; we could also generate descriptions at the same time.


[SUGGESTION] revive by inspiring from other open projects

Hi there, 1st of all thanks for your (voluntary) work !
If this project isn't been definitely abandoned, it would be interesting to revive it by "grab inspiration" from @apple-fritter's RTSP downmix script that renders a 2x2 grid from 4 streams using FFMPEG.
There's also an interesting - but not updated - h264/rtsp Real Time Video player for Android by @eltonwu88 to evaluate.
Of course there are other interesting RTSP viewers projects such as @iEvgeny's CCTV Viewer (that performs extremely smooth on x86 hardware but not on ARM) or @Qrishna's rtsp_stream_viewer (which is C++ coded and relays on OpenCV) but are mutch more "articulated"...
...anyway we believe that active collaboration/knowledge exchanges between devs could bring benefits to any project.
Hope that inspires.

Apologies regarding my lack of understanding the GitHub platform, but maybe this dialogue can continue on in a different venue than this repo's discussion section? I feel though it may be related but is off topic.

Apologies regarding my lack of understanding the GitHub platform, but maybe this dialogue can continue on in a different venue than this repo's discussion section? I feel though it may be related but is off topic.

Well, GH notifies discussion to any "tagged" author (mentioned by "@author")...
...this is one of (working) methods we adopted to stimulate discussion - and hopefully collaboration - between projects' devs/maintainers.
However, since some (you and Evgeny, for example) have reacted positively to our stimulation, we have opened a dedicated discussion here: https://github.com/forart/HyMPS/discussions/17

It's nowhere as near production ready as displaycamears and it's quite simple, but I came up with a quick replacement for my use cases here.


A custom component to Select All checkboxes

I have a few boolean fields in some tables that I would like to select all.
I tried to create a custom component for it but I am not sure how I could connect to the boxes that I want.
Is there a way I could do that?

Could you give an example of how you imagine this to work?

Closing because of lack of response


Fix ChatView TableView crash when scrolling to bottom

This PR resolves a race condition that caused a crash when scrolling to the bottom. The issue stemmed from outdated section row count data, leading the system to believe a section had rows when, in actuality, it didn't.
This PR also removes the method scrollToTop as it wasn't used anywhere
MOB-2578

!squash


Installing beef on Windows 10

What did you do?
I ran the command C:/Ruby22/bin/bundle install

What did you expect to happen?
I expected Bundler to install beef.

What happened instead?
Instead, what actually happened was it showed this message:

Error details
    SyntaxError: C:/Ruby22/lib/ruby/site_ruby/devkit.rb:13: syntax error, unexpe
cted '<', expecting end-of-input
<% tool_names.each_pair do |k,v| -%>
 ^
      C:/Ruby22/lib/ruby/2.2.0/rubygems/defaults/operating_system.rb:3:in `load'

      C:/Ruby22/lib/ruby/2.2.0/rubygems/defaults/operating_system.rb:3:in `block
 in <top (required)>'
      C:/Ruby22/lib/ruby/2.2.0/rubygems/installer.rb:275:in `call'
      C:/Ruby22/lib/ruby/2.2.0/rubygems/installer.rb:275:in `block in run_pre_in
stall_hooks'
      C:/Ruby22/lib/ruby/2.2.0/rubygems/installer.rb:274:in `each'
      C:/Ruby22/lib/ruby/2.2.0/rubygems/installer.rb:274:in `run_pre_install_hoo
ks'
      C:/Ruby22/lib/ruby/2.2.0/rubygems/installer.rb:235:in `install'
      C:/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/source/rubyg
ems.rb:142:in `block in install'
      C:/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/rubygems_int
egration.rb:151:in `preserve_paths'
      C:/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/source/rubyg
ems.rb:134:in `install'
      C:/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/installer/ge
m_installer.rb:56:in `install'
      C:/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/installer/ge
m_installer.rb:14:in `install_from_spec'
      C:/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/installer/pa
rallel_installer.rb:90:in `block in worker_pool'
      C:/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/worker.rb:55
:in `call'
      C:/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/worker.rb:55
:in `apply_func'
      C:/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/worker.rb:50
:in `block in process_queue'
      C:/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/worker.rb:47
:in `loop'
      C:/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/worker.rb:47
:in `process_queue'
      C:/Ruby22/lib/ruby/gems/2.2.0/gems/bundler-1.11.2/lib/bundler/worker.rb:22
:in `block (2 levels) in initialize'

Environment
    Bundler   1.11.2
    Rubygems  <IP_ADDRESS>
    Ruby      2.2.3p173 (2015-08-18 revision 51636) [i386-mingw32]
    GEM_HOME  C:/Ruby22/lib/ruby/gems/2.2.0
    GEM_PATH  C:/Ruby22/lib/ruby/gems/2.2.0;C:/Users/****/.gem/ruby/2.2.0
    Git       not installed

It is recommended that you install ruby version 2.1.X on the RubyInstaller website because it is stable and provides a wider range of supported packages; maybe you could give that a try as well as install the corresponding DevKit for that version of Ruby.
There may be an issue with the version of DevKit you have installed. You can lodge a bug report to RubyInstaller issue tracker. Make it more clear than the issue you lodges here ;).
I will ask some questions to that you can answer that may help you troubleshoot.

The Ruby you have installed is version 2.2.3 and is for the i386 architecture. Does the DevKit you have installed match that version and architecture of the installed Ruby?
Have you followed all the steps to [install DevKit][] correctly?

Also, install git. You will need it when dealing with gems from git repositories.
This isn't bundler related so I am gonna close this.

No response: closing


update ember to 3.28 and bump dependencies

Hello,
I updated ember to 3.28 and bumped dependencies.

Hello @skaterdav85, do you have time to check this ?

@Henridv @andrewpye @sovietspaceship2 any one can check this ?

Hi @mostafa-sakhiri! The contributors you've tagged have each only contributed one small PR to this addon or are no longer active on GitHub. It looks like @iamdtang has been mostly inactive on here for a couple of months, but any decision on how to proceed here is his to make 🤷

Hi @mostafa-sakhiri! The contributors you've tagged have each only contributed one small PR to this addon or are no longer active on GitHub. It looks like @iamdtang has been mostly inactive on here for a couple of months, but any decision on how to proceed here is his to make shrug

Okay, thank you @andrewpye


[1.2] Time sync - tracking

Reproduction steps
PR inspection
Bug prevalence
always
GitHub hash of the SDK that was being used
abb7a802231f2b615b3030c5df43f5144871e09c
Platform
core
Platform Version(s)
No response
Type
Common Cluster Logic
Anything else?

[ ]  Figure out what happens if the TZ offset is out of range AND the code fails to load a time zone. See https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1240951613. In particular, which error code needs to be returned (I think this still needs to be a constraint error), AND can we do this check in a way that prevents making changes that necessitate reloading the time
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1240951626 - align errors between the ember command parser and the
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1212444174 - better overflow protection when going from chip epoch to unix epoch
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1247927627 - handlers for <IP_ADDRESS> SHOULD - If a Node has used the Last Known Good UTC Time, it SHOULD recheck its security materials and existing connections if it later achieves time synchronization.
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242621779 - time zone name copying
[ ] document event generation on time zone name only change. https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242626060
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242627777 - change event flag from parameter to return
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242630331 - change size comparison
[ ] follow up on ScheduleDelayedAction function https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242638706
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242689236 - adjust TZ / DST list on time change
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242639975 - propagate error for set or document why the error changes
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1241153735 - tighten up time get / set features to move them closer to the receive / send boundary
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242642964 - remove casts on TZ / DST offset
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242655854 - refactor DST list parsing code
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242657708 - remove mEventFlag
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242658973 - minor code suggestion from Boris
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242660231 - don't encode local time on error
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242667611 , https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242668186 use unknown value check for enums
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242673209 - double check error code for invalid enum
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242671601 - tighten up granularity check
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242676471 - fix how we're setting granularity
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242683543 - move event generation into the instance rather than handling in the ember functions
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1240968943 - fix time source check to allow domain name addresses
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242685200 - move the IP / domain address checks out of the delegate - this is not something the app needs to care about.
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1241227274 - adjust revision in the lighting app example
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242680899 - rename GetUpdatedTimeZoneState to UpdateTimeZoneState
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242684936 - remove NTPDomain check from delegate - this should be an SDK decision
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242550991 - remove mEndpoint - time sync is now mandated to be only on EP0 per the spec (also https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242569896)
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242547766 - document expected size of the buffer for time zone.
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242548121 - document expected size of the buffer for DST
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242545328 - document expected size of buffer for default NTP
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242607150 - static assertion that the name sizes match between the storage and incoming
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242608673 - document where the 64 for time zone name comes from (spec ref)
[ ] https://github.com/project-chip/connectedhomeip/pull/26082/files#r1242613876 - fix size comparison
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242628037 - document or fix event generation when going into or out of invalid TZ state
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242628882 - initialize CharSpan using array form
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242631916 - fix error codes on dstoffset
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242634295 - consider refactoring LoadDSTOffset and LoadTimeZone out of SetDSTOffset / SetTimeZoneOffset to reduce the number of call sites
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242635346 - factor out duplicated logic in LoadTimeZone
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242650472 - document or fix size change on tzList
[ ] https://github.com/project-chip/connectedhomeip/pull/26082#discussion_r1242668186 - minor code change

Woah - why was this closed?

Thanks @cecille for the catch. I have started working on some of these already.


Implement -r command with findCuisine command

Codecov Report

Merging #69 (0e7a112) into master (9fe5a24) will decrease coverage by 1.00%.
The diff coverage is 0.00%.

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


Parse subunit output from tempest into junit

Currently we have no way of tracking the output of tempest in
the CI.
This patch adds a new playbook to extract the logs from the tempest
container, transform them into junit files and parse them on CI
for easy tracking of the tempest tests.
Just setting SOCOK8S_TEMPEST_PARSE_RESULTS=True should be enough to get
the output file with the tempest results
What it does its that it creates a temporal container with the tempest
pvc attached in order to extract the data from the tempest run, then
brings it to ansible_host, creates a temporal virtualenv to install
the tools needed for transofrming the data, and then transforms it
into a junit file so the CI can understand the output.
This requires a small change in our tempest deployment, which creates
a workspace at /var/lib/tempest/data, which is where the pvc is mounted,
in order to save the results. This also means that you can run tempest
several times and all the results will be in the same place, accesible
by creating a container and mounting the pvc.

does not work, pod is completed by the time we try to do this. Would be cool if results were stored in the pvc so we could launch a container and extract those, maybe even do everything (transformation) inside the container

This is now working, yay!

OMG IS WORKING: https://ci.suse.de/blue/organizations/jenkins/cloud-socok8s-integration/detail/PR-732/2/tests
And its turning the job into red due to the test output!

Looks cool. I will propose a few simplifications with the code later today.

@evrardjp when is later? This should be getting in asap so we can start working on those failing tests asap. Being able to track those is of utmost importance.

Last change (after the approvals) is to make the step isolated from other so it can fail gracefully and it doesnt intervene with the teardown.

Looks cool. I will propose a few simplifications with the code later today.

@evrardjp when is later? This should be getting in asap so we can start working on those failing tests asap. Being able to track those is of utmost importance.

Agreed

This is actually passing but it has 4 failing tempest test, so the job goes to fail: https://ci.suse.de/blue/organizations/jenkins/cloud-socok8s-integration/detail/PR-732/25/tests
Lets merge this! I will follow up on this with the tempest fixes/skip/expected failures


Speed up preprocessing for dataset

Description
There are two possible bottlenecks for the preprocessing pipeline:

Updating the mean and variance estimators
Removing self energies

In the following, I will outline some of the operations that I noticed are responsible for these bottlenecks. Not all of them can be easily mitigated, but there is room for further improvement.
Todos

[ ] TODO 1

Status

[ ] Ready to go

Closing this since @chrisiacovella already prepared a PR with the same scope in #123


⚠ Bofrost.at has degraded performance

In 0b3a61d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1826 ms

Resolved: Bofrost.at performance has improved in d7766d4 after 6 minutes.


EPIC: Re-architecture Temurin SBOM format

The Temurin SBOM has grown organically over time with various enhancements. It has got to a point where we need to carefully consider the current and future use cases, and possibly develop an updated architecture/layout of the SBOM
[SXA: Added issues arising from the secure dev call on 30/Sep/2024]

[ ] https://github.com/adoptium/temurin-build/issues/3013
[x] https://github.com/adoptium/temurin-build/issues/3960
[ ] https://github.com/adoptium/temurin-build/issues/3961
[ ] https://github.com/adoptium/temurin-build/issues/3962
[ ] https://github.com/adoptium/temurin-build/issues/3963

@andrew-m-leonard @sxa I see this got moved to in progress but without an assignee; is there someone leading this that we should assign this issue to?


Hotels:  make sure the most recommended hotels would appear on the top of the results

One more thing related to hotels - can you please make sure the most recommended hotels would appear on the top of the results? (This has been maybe changed in some of the recent versions of the package - hotels are now ranked based on their distance from the center - and resulted in a drop of bookings)

It should already be ordered by popularity
https://github.com/kiwicom/graphql/blob/master/src/hotel/dataloaders/HotelsAvailability.js#L48


Update cryptography and pyOpenSSL (security)

Update cryptography as well as compatible with it version of pyOpenSSL and paramiko.
https://cryptography.io/en/latest/changelog/#v39-0-1

Yay, RFR!
That was quite a rabbit hole 🐰


Provide an option to explicitly force IPv4 ping

I had issues when my Linux system didn't apparently handle IPv6 pings to Google very well, and for some reason tmo_monitor/gateway/base.py wanted to use IPv6 ping. It would be really nice to either explicitly force ping -4 by default, or allow the user to specify ping -4 as a command line option.
In my configuration I wanted to make double sure it didn't use IPv6 ping, so I just hardcoded base.py to add the -4 flag...

@therealbobrice I've set the ping command to default to passing the -4 flag except on Mac OS X which does not support it. When using the ipv6 ping option, it will use ping6 or ping -6 as it did before.