Bitbucket backend, pagination not working.

Describe the bug
The number of item fetched from the bitbucket backend is capped and the pagination does not happen.
To Reproduce
Steps to reproduce the behavior.

Use the default configuration file.
Change backend to bitbucket and connect to a test repo containing (at minimum):

One folder called _posts
11 Files in the _postsfolder

Connect to Netlify-CMS and navigate to collection/posts
Only 10 of the 11 files are visible and there are no ways to see the remaining ones.

A search still returns all files.
Screenshots

Applicable Versions:

Netlify CMS version: 2.3.2
Git provider:  BitBucket
Browser version  Firefox 64.0.2
Node.JS version:

CMS configuration
Default file with:
backend:
  name: bitbucket
  branch: master
  repo: username/reponame

Yes I can confirm that it is not specific to the grid view.

Argh can't log in to bitbucket, will follow up once I work things out with their support team.

If you need me to test just let me know @erquhart

Tried with a collection of exactly 11 items, scrolling down loads the 11th item. Tried in grid and list, with Safari and Firefox, with different browser window sizes. Can't reproduce 😕

I can reproduce the issue on Chrome. I don't think it's related to the Bitbucket API per se, but it has to do with how the infinite scrolling pagination is implemented.
For me, the easiest way to reproduce it is to have a window that is roughly as tall as the initial list of content fetched, which is 10 items. Infinite scrolling will work fine on the first page load. Then:

Click on a content entry and navigate into it;
Click on the back button to get back to the collection;
Infinite scrolling is now broken.

I honestly haven't dug in the code, so I'm just guessing here – but I think it's due to how the waypoint trigger element is removed/replaced in the page when navigating in and out of the content editor.
Here's a recording of the reproduction, hoping it clears up what I said: https://gfycat.com/deliciousforsakenhoatzin
Other backends don't use the infinite scrolling pagination (I believe because of the different API design), so it's not a problem for those.

Thanks for digging into that @iprignano, it does seem to be a bug.
@barthc this behaves the same as the bug in #1744, any chance they're the same?

@erquhart  I cannot reproduce the gif from my end. @iprignano what's your CMS version?

@barthc I was on 2.1.3 – I didn't try to upgrade before reporting the issue because I didn't see anything related to it in the changelog. My bad! I've updated to 2.4.1 and the behaviour seems fixed now. Thank you and thanks @erquhart for the prompt response.

@G-T-P can you confirm whether this is still an issue for you in 2.4.1 or later?

Thanks all for looking into it.
I retried the original test and the issue was still there so I updated to 2.4.2 and I still see the issue.
I am loading the page through a custom install on nextJS so I tested instead with the simplest set-up:
<link href="path/to/config.yml" type="text/yaml" rel="cms-config-url">
<script<EMAIL_ADDRESS>
And that fixed the problem. The initial load yields only 10 items but scrolling down does as expected and triggers the fetch of the remaining items.
To give some details on my install set-up:

Admin page in NextJS static page folder
The page contains a dynamic loader which imports (on client build only) the unmodified source code

I suppose that something in the way the infinite scrolling is implemented conflicts with the dynamic loader. What I find strange however is that there are no request whatsoever leaving the page to fetch the extra items. On the "simplest" set-up the request is automatically fired as expected.

Interesting - this does sound like a compatibility issue that should be looked into, keeping open.

This should be fixed here https://github.com/netlify/netlify-cms/pull/3216.
Please re-open if issue still persists


Added maven 3.2

Maven was recently updated to 3.3.1, breaking compatibility with JDK 1.6. This is a copy of the last version of the maven formula.

Merged in https://github.com/Homebrew/homebrew-versions/commit/22a7524e3a0e4ac102d8ef561b9b96c312a62e8e. Thanks for your contribution to Homebrew, we appreciate it! :smiley_cat:. Please note the preferred commit message for new formulae is maven32 3.2.5 (new formula) or similar, Thanks!


Allow /refresh to complete without returning contents of configuration

The contents of IConfiguration could be very large in some cases, resulting in less than ideal response times for calls to /refresh.
It would be nice if there was a way to prevent the contents from being returned. The toggle should live in IRefreshOptions and the default behavior should be to return contents. If the switch is turned off, a single item should be returned that indicates returning IConfiguration content has been disabled.

#811


GDAL Support?

There was discussion at the Data Users Workshop Hackday of building parallel PDS image viewers: one in pure Python and one that uses GDAL + PVL. (See: https://github.com/planetarypy/planetaryimage/wiki/Requirements) It looks like maybe the first is underway but not the second. Is anybody working on the GDAL angle, and do you still think it's necessary?

@cmillion yeah, I know there were people who were interested in this.  I personally am not interested in doing it unless someone can show me how GDAL supports opening many different mission image types.
I am definitely not advocating against someone else doing this work.  I'd fully support having and alternate GDAL based backend.
Having a rough idea as to how GDAL supports the products listed here, would be a first step:
http://planetaryimage.readthedocs.org/en/latest/supported_planetary_image_types.html
(Note: the green/red markers on that page are somewhat notional as far as I am concerned.  Until someone with true knowledge about a specific mission data type evaluates and writes a test confirming that we support something doesn't.  How to formalize our supported data products is still TBD.
If you or someone you know wants to start thinking about GDAL, I'd be happy to discuss strategies with you/whoever.  I should also point out one large API change that I know we will have to make already ... we need to support multiple data objects (#19).  So image.data will have to become image.data[] or some such.  @cmillion you probably have more experience than I do here, since all of the cameras I've worked on have always had only one data object in the file.  I was surprised in May to learn what sort of crazy stuff people will jam into a PDS product.
CC @wtolson so he's aware of this discussion.

Thank you. I don't personally see a reason to fork out a GDAL solution right now.
The data object issue does interest me, and I'd be happy to try to help with it, but I don't recall ever trying to work with PDS data more complicated than image or table + header. I'm aware that the "crazy stuff people will jam into a PDS product" was a problem, though, and think that this was one of the big justifications for PDS4. Do you have an example? In a quick search of PDS documentation referenced by #19, I found references to TIFF, TEX, and QUBE formats.

Just as a heads-up, GDAL now has support for reading and writing ISIS3 cubes. This update does give one some interesting JSON options from python. Only in truck and still beta. For some example access and creation options see: http://www.gdal.org/frmt_isis3.html


Save button should be disabled if file is not dirty

I am clicking on save all button in my vs code and it stays active even after there are all changes saved.
Version: 1.53.2
Commit: 622cb03f7e070a9670c94bae1a45d78d7181fbd4
Date: 2021-02-11T11:45:54.515Z
Electron: 11.2.1
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 20.1.0
Please check the attached video.
https://user-images.githubusercontent.com/73881409/107940677-9f261d80-6fae-11eb-877a-18337f53f3da.mov

Yeah that is the Save All button, we always allow to save, since that triggers formaters for example and disabling save if there are no changes would break some other people flow.
So for now - no action planned here, but leaving this open to gather more potential user feedback

@isidorn Perhaps have another button with basically the same icon except decorated with something to indicate unsaved changed (perhaps a dot). Use complementary when-clauses on this new item and the existing one so only the correct one shows.

That might be a good idea, but I would not make any changes to the Open Editors view right now which is hidden by default.


DX-762: Pay by Link doesn't display all available payment methods

Probably connected with https://github.com/CommerceWeavers/SyliusTpayPlugin/issues/117 but without additional context I cannot guarantee :D

Let's continue on #165


Selection Too Dark

The selection colour is a little dark and you cannot see the text under the selection. I have updated mine with "selection": "color(var(gray) alpha(0.20)", so maybe update if you are happy with that.
Many thanks, Karim

I've also added the following to bring it more in line with the Neovim port.
        "gutter_foreground_highlight": "var(green)",
        "selection": "color(var(gray) alpha(0.20)",
        "selection_foreground": "var(gray2)",
        "line_highlight": "var(black2)"

I agree that it needs a lower alpha, especially on comments, but 0.2 seemed a bit low to me elsewhere. I just updated it to be 0.4 which looks good on some samples I was looking at. Lmk if you think that's sufficient contrast.
Also good call with the line numbers!

No problem, happy to help out. Will give it a go later. Are you updating the gutter foreground to var(green) too, cannot see that under your commits, unless I've missed it?

I was being stupid, can see it. Sorry about that!


Save personal information

User story

As a user (HR employee)
I want / need to save the added personal information of the employee
So that it is stored in the database.

Acceptance criteria

Definition of done (DoD)

Added only after week 5
The same for all features
Here goes the project specific part

DoD general criteria

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Developers agreed to release

duplicate with #7


Google Play Music Playlist in  Media Player GNOME Shell extension

Feedback from Brian McLean:

I would love the ability to view my playlist and like/dislike songs through the media player indicator extension on Gnome.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

I'm afraid playlists would be too fragile to implement. I don't dare to do that.


Fix FIXME and remove superfluous queries in models/org

I realize this is long, but I want to give some context for my changes. Please bear with me, or jump to the TL;DR at the bottom if you're impatient.
This PR addresses the following FIXME in models/org.go, line 474-475 (an identical FIXME is also in models/action.go, line 661):
// FIXME: only need to get IDs here, not all fields of repository.
repos, _, err := org.GetUserRepositories(user.ID, 1, org.NumRepos)

org.GetUserRepositories(uid, ..) first computes the necessary repoIDs, then loads the repos with those repoIDs, then finally computes a count (the second return value, which is ignored above). It would therefore make sense to create a separate function for computing the repoIDs (say org.GetUserRepositoryIDs(uid, ..)) that both org.GetUserRepositories(..) and models/org.go, 474-475 can use.
There's more: of the several places where org.GetUserRepositories(..) is called, the count is ignored in all but one place (routers/user/home.go, line 355). So most of the time when org.GetUserRepositories(..) is called, the count is calculated (which involves a join), and then the count is immediately thrown away. I therefore decided to not have org.GetUserRepositories(..) compute the count, but instead move that logic to another function (say org.GetAccessibleReposCount(uid)) to avoid wasting work. routers/user/home.go, line 355 would then make two calls: one to org.GetUserRepositories(..) and another to org.GetAccessibleRepoCount(..).
This seems promising, but there's one problem with this approach: both computing the repoIDs (in org.GetUserRepositoryIDs(..), and by extension org.GetUserRepositories(..)) and computing the count (org.GetAccessibleRepoCount(..)) require determining which teams the specified user belongs to. In routers/user/home.go, line 355, where I actually care about the count, I will need to compute the teams that a user belongs to twice (once for org.GetUserRepositories(), another time for org.GetAccessibleRepoCount()). The same problem occurs in places where both org.GetUserRepositories() and org.GetUserMirrorRepositories()) are called, (e.g. routers/user/home.go, line 116).
Taking a step back, there are three functions

org.GetUserRepositoryIDs(uid, ..)
org.GetAccessibleRepositoryCount(uid)
org.GetUserMirrorRepositories(uid)

all of which require the same preprocessing, and we would like to avoid doing the preprocessing more than once if we call these functions multiple times with the same uid. The solution that occurred to me was to move these functions to a AccessibleRepoEnvironment interface. The implementation of the interface, accessibleRepoEnv, would store the results of the preprocessing (i.e. the teamIDs a particular user belongs to), and each function/method would just use those results instead of (re)computing them.
Under my changes, to call these functions/method, one can do the following
env, err := org.AccessibleRepoEnv(userID) // preprocessing done here
// check err
count, err := env.CountRepos() // org and uid not provided, they're specific to env
// check err
repos := env.Repos()
// check err
...

and no work will be wasted or duplicated :smiley:. The interface, or at least the idea behind, could also be used in other parts of the codebase.
TL;DR: I got rid of useless/duplicated queries by moving some functions to an interface.
I'm open to suggestions (particularly for naming) and would be happy to hear any feedback on this.

I tried to fix #746 when I bumped into exactly the same issue.
Your point makes sense to me. But I'm no sql expert so maybe @lunny could take a look?

LGTM

LGTM


createError fails with no second argument

The optional second argument is not really optional
apollo-errors/dist/index.js:87
  var data = arguments.length > 1 && arguments[1] !== undefined ? arguments[1] : { message: 'An error has occurred', options: options };
                                                                                ^
ReferenceError: options is not defined

var createError = exports.createError = function createError(name) {
  var data = arguments.length > 1 && arguments[1] !== undefined ? arguments[1] : { message: 'An error has occurred', options: options };

  var e = ApolloError.bind(null, name, data);
  return e;
};

options is not optional.  some of the fields ON options are optional, but a message property on the options object is required.  I think the solution here is an assert clause that gives a proper error message about options being required (per the docs, as well)

https://github.com/thebigredgeek/apollo-errors/blob/master/src/index.js#L44 < there is a syntax error, though, with initializing a default second param... options isn't defined.  The default should be removed and we should use assert to test for validity of the second parameter

@riley-stroud-ck any interest in submitting a PR for the syntax error fix?

@riley-stroud-ck  any interest in submitting a PR for the syntax error fix?

Should be fixed here


Add support for graceful worker shutdown

This is the initial version of the graceful worker shutdown functionality (tested with automated randomized query submissions + shutdown requests). \cc @martint @cberner @dain
Note: In this version due to a network glitch a worker can go from "shutting down" state to the "failed" state and then back to the "active" state (as that node will be removed from the known node states when it gets marked as "failed" -- see DiscoveryNodeManager.nodeStates map). And in the "active" state the coordinator will submit tasks to that shutting down worker and it is possible that these tasks may be received after the worker registers the task completion listeners, eventually causing those tasks to fail ungracefully. One possible way to prevent this is to reject these tasks at the workers (in TaskResource.createOrUpdateTask() if a worker is in the "shutting down" state) and let the coordinator re-schedule them (not sure whether this is easy to implement with the current scheduling code).

Had some comments. Also, can you squash your commits together? I think the whole feature should be a single commit

@cberner Addressed your comments & squashed the commits. How do we want to handle state transitions to ACTIVE and INACTIVE in ServerInfoResource::updateState()?

As discussed, currently state transitions to ACTIVE and INACTIVE are not supported.

I think it would be good to have an end-to-end test for this. Here's one suggestion for doing that:

Add a ShutdownAction interface with an onShutdown method. The default implementation would just call System.exit(0). Then make GracefulShutdownHandler call this, instead of System.exit(0) directly.
Add a test similar to TestMemoryManager that submits a query or two, then initiates a shutdown on one of the TestingPrestoServers. Modify TestingPrestoServer to bind a TestShutdownAction which stores a boolean, instead of calling System.exit, then you can check that the flag is set in your test

Had some more comments, but overall this is looking good!

@cberner addressed the comments & rebased, thanks. I extracted a new GracefulShutdownModule for simplifying the testing with a test shutdown action and added unit tests in TestGracefulShutdown.

@cberner updated.

You've missing a test in TestServerConfig (see Travis)

Looks good, except for the minor comments and the Travis failure

@cberner fixed the travis failure & addressed the comments.

Merged. Thanks!


Author email address bounces back

In the metadata.json the current author's email address bounces back. For a project I am working on I need a contact person to reach out to. Is there anyone that is available for this? Who is the current maintainer?

@pranav @PaulFurtado should we setup an email alias for this?

WINNING!


Ensure python38-devel is installed

We want the controller to run everything under python3.8, so lets make
sure it is installed.
Signed-off-by: Paul Belanger<EMAIL_ADDRESS>

Pull-request updated, HEAD is now b5475a6712913bbb9faa6c6ac493b543e2c1fae3


Not working in singleplayer World

Hey, I saw you said it did not need to be installed client-side only on the server, does it still work in singleplayer worlds, because it did not for me. I have fabric installed for the correct snapshot and have the api. I also have 3 other mods installed, mini hud, REI (Roughly Enough Items), and malilib Fabric all mods are working besides unpatch-zero-tick-farms.

I've just updated the mod for Minecraft 1.16.3 and tested it on singleplayer, give it another try if you can!


The typescript compiler sometimes interprets "--outFile" as a file to compile resulting in error TS6231.

🔎 Search Terms
outFile TS6231
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about outFile and TS6231

⏯ Playground Link
No response
💻 Code
Steps:
$ tsc --lib es7 –-outFile image.js ts/image.ts --showConfig

🙁 Actual behavior
Actual results:
The options contain a file called "./--outFile":
{
    "compilerOptions": {
        "lib": [
            "es7"
        ]
    },
    "files": [
        "./–-outFile",
        "./image.js",
        "./ts/image.ts"
    ]
}

🙂 Expected behavior
Expected:
I expect the output to look like:
{
    "compilerOptions": {
        "outFile": "./myfile.js"
    },
    "files": [
        "./ts/image.ts"
    ]
}

Additional information about the issue
Note:
Running version 5.3.3 on Debian version 12.
tsc -v
Version 5.3.3

cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Note:
When you  don't use the showConfig option, you get the TS6231 error:
error TS6231: Could not resolve the path '–-outFile' with the extensions: '.ts', '.tsx', '.d.ts', '.cts', '.d.cts', '.mts', '.d.mts'.
  The file is in the program because:
    Root file specified for compilation

Note:
Both outFile and outfile sometimes work as expected:
$ tsc --outFile myfile.js ts/image.ts --showConfig
{
    "compilerOptions": {
        "outFile": "./myfile.js"
    },
    "files": [
        "./ts/image.ts"
    ]
}

$ tsc --outfile myfile.js ts/image.ts --showConfig
{
    "compilerOptions": {
        "outFile": "./myfile.js"
    },
    "files": [
        "./ts/image.ts"
    ]
}

Note:
The workaround is to use "outfile" instead of "outFile":
$ tsc --lib es7 --outfile myfile.js ts/image.ts --showConfig
{
    "compilerOptions": {
        "lib": [
            "es7"
        ],
        "outFile": "./myfile.js"
    },
    "files": [
        "./ts/image.ts"
    ]
}

Using a tool like this one, you can tell that the first of the two dashes before outfile is actually an en dash, not a normal hyphen, so there looks to be no issue here.

Wow, good find.  I just removed the characters and typed two dash and it
works as expected.
On Mon, Jan 29, 2024 at 7:41 PM Abraham Guo @.***>
wrote:

Using a tool like this one
https://www.babelstone.co.uk/Unicode/whatisit.html, you can tell that
the first of the two dashes before outfile is actually an en dash, not a
normal hyphen, so there looks to be no issue here.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/TypeScript/issues/57194#issuecomment-1916018421,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC3UMKI3BV7OTG3Q4O4QM3DYRBTYFAVCNFSM6AAAAABCMYK672VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJWGAYTQNBSGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

No problem! To clarify a bit more for anyone else reading the issue — camelcasing vs lowercasing has no effect; it was simply coincidence that the first example was the only one that contained the mis-copied en dash.
@RyanCavanaugh let me know if you think it would be beneficial to add some sort of user-friendly error handling for this case, although I would guess that most other CLIs would have no special handling for this case and would give similarly cryptic results.

Smart quotes (and hyphens) strike again!

The wonderful thing about humans is, by sheer numbers, we eventually make every possible mistake.
If it happens again we can think about hardening the commandline parser


VRF proof-of-concept in Solidity

Implement a solidity contract that is capable of verifying a VRF following the same standards as for the vrf-rs Rust crate.

This issue became more about implementing a Proof of Concept on how to compute VRF verifications on solidity becase we identified several improvements that could be made, mostly about performance and gas cost.

As conclusion of the PoC task (code is available in the branch poc), there potential future issues to be addressed.
Regarding underlying contracts:

Implement an Elliptic Curve contract specific for secp256k1
Generalize the EC contract to support any up to 256-bit curves

Regarding the VRF contract itself:

Polish the repository (e.g. descriptions in README.md and package.json)
Document code
Include some function checks (e.g. proof length and yBit value)
Assess potential performance improvements (e.g. provided ctr value in hash_try_and_increment function)


CLA test

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.tinychaos42 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fault injection should use abort instead of timeout (#1279)

This commit introduces a new fault injection file that simulates
HTTP abort in addition to the HTTP timeout exampls. The documentation
will be updated to add this as an fault injection example.
What this PR does / why we need it:
Adds a fault injection example using HTTP abort in addition to the HTTP timeout example
Which issue this PR fixes: fixes #1279
Special notes for your reviewer:
Documentation will be updated to use this example.

Hi @asomya. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/ok-to-test

@asomya do you have a docs PR created already? if so, please post link in description or as a comment

Docs PR: https://github.com/istio/istio.github.io/pull/978

@GregHanson I updated the patch with files for consul and eureka.

@asomya: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
ec2459bf85aa4ad613983e2a147344c17f85dcda
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

@asomya: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
ec2459bf85aa4ad613983e2a147344c17f85dcda
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


IntelliSense on 3rd party module only includes some items

Hi,
I'm running VS 2015u3, with Python Tools 2.2.6. I've installed the F5 SDK (pip install f5-sdk or https://github.com/F5Networks/f5-common-python ), and it's functioning properly. It's also showing up under the IntelliSense listing with a checkmark as expected, and I've repeatedly rebuilt the Intellisense DB without issue. (I've also rebuilt my VS profiles/etc).
The problem I'm running into, is that while it lists many IntelliSense items, it's by no means complete.
For example:
from f5.bigip import ManagementRoot
mgmt = ManagementRoot("<IP_ADDRESS>", "admin", "admin")
pools = mgmt.tm.ltm.pools.get_collection()
... is a fairly simple usage of the SDK. However, In that example, mgmt.tm or mgmt.tm.(anything) won't show up, but a list of several other items does. Some other items show no completion at all.
Is the lack of IntelliSense items due to the way the module was written, or something the reflection routines are missing?
Thanks in advance for any assistance!

It'll be a bit of both. We use static analysis to determine IntelliSense results, so when it's not easy to determine a return type or attribute type we likely end up missing it completely.
We'd have to look into the F5 SDK to see whether this is likely. I'll leave this open as a reminder to investigate in case there is something that can easily be changed (either on our side or in the SDK itself) to make this analysis better.

See #3046


[PREVIEW] Implement session tracking by VLAN

Sorry for keeping you waiting. Here is a proof-of-concept for adding VLAN id when tracking sessions. I've been quite busy lately, so I haven't gotten around to finish the work, but I'm sharing what I've done so far.
There's still stuff that VLAN tracking is not implemented for, like for instance the Suricata plugin, but I can add that as well, if you want.
When running tests.pl, the following tests fail:

Test 8 - pcap/cassandra1 (different VLAN IDs on ingress and egress traffic)
Test 18 - pcap/dns-flags0110 (only VLAN tag on DNS query)
Test 69 - pcap/modbus (not sure why, yet!)
Test 70 - pcap/mongo (duplicate packets using another VLAN ID)
Test 83 - pcap/oracle (duplicate packets using another VLAN ID)
Test 137 - pcap/stun (different VLAN IDs on ingress and egress traffic)

License
I confirm that this contribution is made under an Apache 2.0 license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Thanks! There is a bunch of work to meet #2722 do you
a) want to continue working on it
b) want me to contribute to your PR
c) want me to take over

From the last commit (and the issue), it seems like you have a clear picture of how you want to solve this, so I would be happy if you would  just take over 😊


Fix ${namespace} and "$staticIp"

Some arguments are set as ${namespace} and ${staticIp} but they should be $namespace and $staticIp.
As far as I tried, the namespace is registered as ${namespace} on Azure though we expected the value of namespace is regsitered.

@kemurayama : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@kemurayama thanks for the contribution. I fixed the merge conflict in a separate branch and merged your changes.


Add shadowColor to AppBar and AppBarTheme

Description
This PR exposes the shadowColor parameter of AppBar and AppBarTheme so that users can specify the color of shadow generated by elevation just like they can when using Material widget.
Related Issues
This PR fixes https://github.com/flutter/flutter/issues/27461 partially.
Tests
I added the following tests:

AppBar.shadowColor takes priority over AppBarTheme.shadowColor

Checklist

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

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[X] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change.

@googlebot I fixed it.

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.
ℹ Googlers: Go here for more info.

I fixed it.

@googlebot I fixed it.

Mistakenly closed. Reopened...

@HansMuller Can you review this PR? I hope I tagged the right person, according to the tree hygiene document.

Hi @anisalibegic welcome! And thank you for the contribution! 🎉
We may want to incorporate this as part of the ThemeData as the conversation in the issue suggests. @HansMuller has been doing a lot of work in Theming, WDYT Hans?

Thanks for your contribution! It will land when the build is green again.

Thanks for your contribution! It will land when the build is green again.

Thank you very much!


Timer Reset not stopping Timer

Actual Behaviour
When the repeat action is set to Reset on the timer layer effect, the timer resets to 0, but doesn't actually stop counting. This means to cancel a timer you have to remove and copy back in the layer.
Reproduction steps
Create a timer layer and set the Repeat action to Reset.
Frequency
Every time the timer is run.
Aurora Version:
0.7.1
Previously an Issue?
Don't Know

This is not a bug, it is the intentional behaviour for the reset mode.
A new option that cancels the timer when the trigger has been pressed has been PRed.


Update java app to take argument

Update the exposure data scraper java app to take argument - indicating what type of exposure data to collect from Open AQ. Currently will just support "pm25" and "O3"

delivered


how to create dynamic tables using jexcel

i used jexcel for static columns, what if I want to add Column's dynamically based on user selection.
See below image left side assume we have jexcel table right side box has columns, based on column selection is it possible to load "columns" selection in jexcel.
columns: [
{
type: 'dropdown',
url:'https://bossanova.uk/jspreadsheet/v4/countries',
width:200,
} ]
does above code section support JSON object data binding for columns block ?
or is there a way to load this column config dynamically.

You can use insertColumn to create columns dynamically. Or simple hide/show some pre loaded ones.


Add a testing issue generator

What this PR does / why we need it:
At the beginning of every testing phase, we have to create testing issues with Prow commands that trigger the specific test. That is error prone, and takes way too much time. Ideally, there should be a command that we can run, that's going to parse the tests definitions, and do the magic. ✨ This PR is doing exactly that!
This PR abuses our existing tests generator to add a new generation type called gh/GitHub. It has two modes of operation:

Generate issue content and print it on the selected output (e.g. stdout or a file)
Generate issue content and automatically create a GitHub issue (requires setting the GITHUB_TOKEN environment variable and the -create-issues flag)

This feature supports creating multiple issues (or generating contents for multiple issues) from a single invocation. By default, it's going to create issues for all defined tests (unless the infrastructure has a (newly added) disclude parameter). Further filtering can be accomplished by using -scenario and -provider flags which are filtering by scenario (as defined in tests.yml) and providers (as defined in tests_definitions.go), respectively.
From the code perspective, this code heavily abuses maps. First of all, the structure of tests.yml doesn't work well for creating GitHub issues, our GitHub issues are per provider, per scenario, per operating system. tests.yml is per scenario, per Kubernetes version, per combination of provider/OS. We need to repack that to a struct that we can easily iterate through. I considered option to create additional structs and do that, but accessing random struct in a slice is hard. That said, maps are maybe not as memory friendly, or nice, but they provide very easy accessibility.
To invoke this code, go to the tests/e2e directory and run:
# Generate all possible issues
go run ../generator -file ../tests.yml -type gh -output "-" -k1version "1.10"

# Generate all possible issues for AWS
go run ../generator -file ../tests.yml -type gh -output "-" -k1version "1.10" -provider aws

# Generate all possible issues for AWS and install_conformance_external (that's actually only one issue)
go run ../generator -file ../tests.yml -type gh -output "-" -k1version "1.10" -provider aws -scenario
install_containerd_external

# At the end... create GitHub issue
go run ../generator -file ../tests.yml -type gh -output "-" -k1version "1.10" -provider aws -scenario install_containerd_external -create-issues

Some examples: #3400 #3401 #3402 #3403
What type of PR is this?
/kind feature
Does this PR introduce a user-facing change? Then add your Release Note here:
NONE

Documentation:
TBD

/assign @kron4eg

/lgtm
/approve


feature/inbound-transport-profile

When implementing a custom inbound transport there is no way to access settings through the profile. This PR adds a root profile to the BaseInboundTransport class that allows custom implemented inbound transports access to the profile provided to InboundTransportManager.
main changes:

transport/inbound/base.py, now has a root_profile attribute.
transport/inbound/manager.py,  passes profile into register_transport

Codecov Report

Merging #1407 (28192e5) into main (d7dedcf) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1407   +/-   ##
=======================================
  Coverage   95.31%   95.31%
=======================================
  Files         482      482
  Lines       29121    29123    +2
=======================================
+ Hits        27758    27760    +2
  Misses       1363     1363


Remove "General" Members

Remove AI General Members, and replace with bucket for Associate Members
Pre-submission checklist:
Please check each of these after submitting your pull request:

[ ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[ ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[ ] Have you picked the single best (existing) category for your project?
[ ] Does it follow the other guidelines from the new entries section?
[ ] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[ ] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[ ] Does your project/product name match the text on the logo?
[ ] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~5 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Build failed because of:
item does not have a name
Membership subcategory "Premier" does not have corresponding entry in settings.membership


Prepended text appears over a positioned element (add-on with z-index)

As you can see on thsi picture : http://imgur.com/sPyiz the prepended text is showing over the panel instead of being under.
This is because, the add-on class has a z-index set to 2.
Why this default value ? Can't we leave it to auto ?

Removed in 2.0-wip.


fix: correct "M.config" with config

On the 150th line of init.lua,
The M.config may be a typo and can be corrected by `config.

Awesome thank you


error when packaged

I added a menu and a world to walk in to test the plugin, when I packaged the game and ran the exe file this error popped up "Plugin 'AsyncLoadingScreen' failed to load because module 'AsyncLoadingScreen' could not be found.  Please ensure the plugin is properly installed, otherwise consider disabling the plugin for this project." and wont let me start

It seems like your project is blueprint-based. You are trying to use the plugin when you haven't installed it properly. You can download the plugin on GitHub, add it to your Plugins folder, and compile it again.

I found out that is was a packaging error, I fixed it


Support for light bulb ("dj" category)

Hi. I have some cheap bluetooth RGBCW light bulbs and i'd really like to integrate it into HA. Here's what i got from Tuya website:
Product Name Beacon RGBCW
Device ID bf39aclihavy7at7
Product Category dj

"dj" category should be supported. If the device is not a least found by the integration (even if non working), it might be bluetooth but not BLE.
Also, since a device can have a single connection, be sure no Tuya app on the same account is running, even in background, on any phone so this integration can work

If the device is not a least found by the integration (even if non working), it might be bluetooth but not BLE.
That's exactly what happens. Didn't knew there are also non-BLE devices, thanks. Are there any way to work with them without tuya hub?


Avoid flexible array members for easier interoperability with C++

C++ doesn't support flexible array members and compiling the library with a strict compiler will emit warnings. This issue is not a promise but I'll look into it :)

Proof of concept change is available at https://github.com/spaskalev/buddy_alloc/pull/79


Changes to power_factor calculation

Proposed change
Only update power factor values if valid values are available.

@agocsdaniel  can you take a look? It would be nice to merge this and then get the quirk merged.

I don't really know by definition what is the power factor when apparent power is zero. But I think it might be better setting it to 0 instead of not setting it at all. If it is possible to return NaN or None, then I think that would be the ideal solution.

Then I think it would be better to just remove the pf calculation from this quirk al together.

it is a calculated value. We do not have any knowledge of the measuring methods the device uses so we lack knowledge on how to properly calculate it.
I don't think calculated values belong in a quirk it is misrepresenting the real functionality of the device.
There is still a test coverage warning on the pf calculation in the PR.

In general I think it is way more important to get the PR of the quirk merged.


Wrong converting from .otf to .ttf, glyphs become transparent!

I discovered this issue when converting Gilroy-Light.otf to .ttf format with your plugin otf2ttf, in Windows it displays wrong and all glyphs are transparent, but the same file on Mac displays correctly, i don't know what the problem on Windows. Hence, .woff and .woff2 files on Windows also trasparent. You may check .otf, .ttf and .woff glyphs in browser via https://fontdrop.info/.
This font with free license by Radomir Tinkov, you may download and check it - https://www.tinkov.info/gilroy.html

After converting:

This package had solved my problem: https://www.npmjs.com/package/otfforge


Building an iOS app with Xcode 11 fails with IDEFoundationErrorDomain Code=1 "IPA processing failed"

When I try to build an iOS app using Xcode 11, the build fails and the following error appears in the build output log:
Error Domain=IDEFoundationErrorDomain Code=1 "IPA processing failed" UserInfo={NSLocalizedDescription=IPA processing failed}

** EXPORT FAILED **

##[error]Error: /usr/bin/xcodebuild failed with return code: 70

This error wasn't present when my selected Xcode version was 10.3.
What should I do in order to fix this?

@tamassengel have you contacted our support team on this issue? Click the blue chat button at the bottom-right corner of every App Center page, that connects you directly to our dedicated support team.

@jwargo Thanks for your response, I've contacted the support team.

As it turned out, this is an issue in my project. Thank you for your assistance!

As it turned out, this is an issue in my project. Thank you for your assistance!

I am also seeing this issue @tamassengel what was the resolution?

@desaikevin It was caused by a framework incompatible with Xcode 11. I'm now building with Xcode 10.3 until that framework gets updated.

thank you! @tamassengel

I have the exact same issue as you. Can you share what is the frame you found that cause the issue?@tamassengel

@yilunx-flurrydev It was an earlier version of the FoxitRDK framework. I downloaded the latest version again and it works perfectly now.

Thank you for your response.
On Mon, Sep 30, 2019 at 11:52 PM tamassengel<EMAIL_ADDRESS>wrote:

@yilunx-flurrydev https://github.com/yilunx-flurrydev It was an earlier
version of the FoxitRDK framework. I downloaded the latest version again
and it works perfectly now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/appcenter/issues/1055?email_source=notifications&email_token=ANFTBWDXDMVLXMDBRJQN6BLQMLXUVA5CNFSM4IYO7P5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAAFXLI#issuecomment-536894381,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANFTBWFPTMNLONLYXYQEV7LQMLXUVANCNFSM4IYO7P5A
.

Hi @tamassengel
i think i have a similar problem as one of my dependencies (pods) is not able to be exported with XCode 11 Tools... May i ask how you found out which was the incompatible one, i can`t detect in the logs from the export.
Thank s in advance!

Hi @auernmri,
Can you bring a light on what was incompatible for you and how did you found it?
Thanks!

Hi @zulkis
i found the problem in the device error logs after the "ipa processing failed".
I was using some embedded framework and it came with a script (apparently which is stripping some architectures and codesigning). After executing the script in build phases it worked again.
The error came up with XCode 11, but i guess it s more related to the new build system... (just a guess)

https://www.darrenblog.cn/#/detail/5dbf9a8a7bb725236692b6d4


Evaluate Javascript

Hey , like Title says , can we evaluate javascript , and use a bridge or something to communicate

I think it's doable as an implementation!
flutter_inline_webview_macos is flutter_inappwebview It's pretty much based on this package and is supported there I think it's possible!
If you can do it, I'd be happy to pull it out!
Also, keep an eye on this issue! https://github.com/akaboshinit/flutter_inline_webview_macos/issues/12

@akaboshinit thanks for the reply , i tried on that plugin as well , and faced some issues , but that package is still in beta phase of macos , so i guess that will be fixed

I took a closer look at it and yes, thanks!
But the swift mechanism I'm using inside is the same as that package, so I think it's possible to implement it, though I'd need to modify it a bit!
More than that https://github.com/akaboshinit/flutter_inline_webview_macos/issues/12 What do you think about this?
Even if I implement "Evaluate Javascript", I don't think it's a package that can be used for development.
I think we can wait until this is settled.

I also want to evaluate javascript , and use a bridge or something to communicate.

@akaboshinit yes seems like waiting is the only option ,
@sugur we have another option , puppeteer ,if our main goal is to evaluate JS, and perform some tasks from the Web

puppeteer
Can use puppeteer  to set header , then open url in webview?


Color theme not applying on Firefox

Expected Behavior
Code has color
Actual Behavior
No color for code. But I can change other settings like window control, background, etc.

Browser:
  Firefox 62.0b18 (64 bit) in private browsing mode

Code Snippet (If Applicable)

Sorry about this! I just fixed it with b19bbf26aeb352426a9393f9d039418e541fe3c2. I will get it redeployed now.

If you still see the issue, try reloading your browser with CMD + Shift + R

If the issue is still presented, you can fix the issue by running:
"allow pasting"
if ('serviceWorker' in navigator) {
  navigator.serviceWorker.getRegistrations().then(function (registrations) {
    //returns installed service workers
    if (registrations.length) {
      for(let registration of registrations) {
        registration.unregister();
      }
    }
  });
}


feat(backingimage): backup backing image support

ref: https://github.com/longhorn/longhorn/issues/4165

Conflicts resolved

Conflict resolved

Conflicts resolved

Conflicts resolved

Conflicts resolved


docs: mention that "podman version" prints out Remote API Version

Since "man podman-version" seems to want to list everything printed
about the current version, add a reference to Remote API Version
for completeness.
Signed-off-by: Robert P. J. Day<EMAIL_ADDRESS>

Friendly ping.

/ok-to-test

@rpjday what is going on with this?
/approve

/lgtm


Assign Course to Placeholder Modal (Front-End)

Summary
This pull request implements the front-end for the modal that opens to assign courses to placeholders to continue Templates development. Follow-up from #592.

[x] Open modal when a placeholder is clicked
[x] Refactor NewSelfCheckCourseModal to handle placeholder assigning as well
[x] Implement removing placeholder button and styling (with confirmation)
[x] Add temporary description/learn more values with TODOs

Remaining TODOs:
Complete the requirements side of this modal in a later PR. This should be easier as real placeholder data is populated into a user's Firestore collection. Specifically...

[ ] Filter out the courses that can be added in the new modal
[ ] Assign selected course to requirement
[ ] Replace placeholder in front-end with selected course (and show confirmation)
[ ] Show corresponding description and learn more link from requirements sidebar

Test Plan
Similarly to #592 - placeholder data has to be added to Firestore manually. Afterward...

Confirm clicking on a placeholder opens up a modal with the name of the placeholder as its title
Confirm the styling of the modal matches the designs
Confirm pressing remove on the modal deletes the placeholder from the plan, and refreshing it
Confirm courses are properly filtered in a self-check add modal and can be assigned to the requirements and semesters as before.

Notes
@kkkehui could you take a look and let me know if this looks good? I think I closely followed the designs - but I did keep the placeholder text inside the input box the same as our other add modals for consistency and easier coding. Let me know what you think!
Additionally, This PR can be safely merged as long as the self check add modal remains unchanged, as real users cannot yet have placeholders!

Hi Will, sorry I just saw this! everything looks good so far!
The only thing I am not sure about is the outline for the input, it seems to be black in this picture when the input bar is clicked. On the current website, I think it is blue (#0E62C9). If you are reusing the elements from the current add modal, then it should be fine! lmk if there's anything confusing. Thanks!


Bare-metal multi-GPU training fails launching subprocesses due to unexpected args

What happened?
Launching
HYDRA_FULL_ERROR=1 ANEMOI_BASE_SEED=1 anemoi-training train --config-name happy_little_config --config-dir=/pathToConfigs/config
for training models in a multi-GPU setup (on a single machine, outside of a SLURM environment) fails to launch sub-processes successfully. Specifically, the first sub-process is initiated properly but processes afterwards error (see: Relevant log output).
Training runs successful with a single-GPU setup but fails when using multiple devices. The desired behavior is for multi-GPU training to be feasible outside of a SLURM environment. The issue might require further looking into, but it may be related to this or that.
What are the steps to reproduce the bug?
On bare-metal (or: without using any resource scheduler):
In the configurations, if using
hardware:
	num_gpus_per_node: 1
	num_nodes: 1
	num_gpus_per_model: 1

the process launches successfully and trains as expected. However, when changing to
hardware:
	num_gpus_per_node: 2
	num_nodes: 1
	num_gpus_per_model: 1

or
hardware:
	num_gpus_per_node: 2
	num_nodes: 1
	num_gpus_per_model: 2

the process crashes during creation of child processes while parsing arguments that are not recognized.
Version
anemoi-training 0.3.0 (from pip)
Platform (OS and architecture)
Linux eohpc-phigpu27 5.4.0-125-generic #141-Ubuntu SMP Wed Aug 10 13:42:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Relevant log output
...
[2024-11-19 16:44:28,847][anemoi.models.layers.attention][WARNING] - Flash attention not available, falling back to pytorch scaled_dot_product_attention
[2024-11-19 16:44:33,689][anemoi.training.train.forecaster][INFO] - Pressure level scaling: use scaler ReluPressureLevelScaler with slope 0.0010 and minimum 0.20

[2024-11-19 16:44:35,481][lightning_fabric.utilities.distributed][INFO] - Initializing distributed: GLOBAL_RANK: 0, MEMBER: 1/2
usage: .__main__.py-train [--help] [--hydra-help] [--version] [--cfg {job,hydra,all}] [--resolve] [--package PACKAGE] [--run] [--multirun] [--shell-completion] [--config-path CONFIG_PATH] [--config-name CONFIG_NAME] [--config-dir CONFIG_DIR] [--experimental-rerun EXPERIMENTAL_RERUN] [--info [{all,config,defaults,defaults-tree,plugins,searchpath}]] [overrides ...]
.anemoi-training-train: error: unrecognized arguments: hydra.run.dir="outputs/2024-11-19/16-43-03" hydra.job.name=train_ddp_process_1 hyra.output_subdir=null

[2024-11-19 16:44:43,698][lightning_fabric.strategies.launchers.subprocess_script][INFO] - [rank: 1] Child process with PID 763811 terminated with code 2. Forcefully terminating all other processes to avoid zombies 🧟
Killed

Accompanying data
No response
Organisation
No response

In case additional platform information is relevant:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.82.01    Driver Version: 470.82.01    CUDA Version: 11.4     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA RTX A6000    On   | 00000000:00:05.0 Off |                    0 |
| 30%   37C    P8    27W / 300W |      0MiB / 45634MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  NVIDIA RTX A6000    On   | 00000000:00:06.0 Off |                    0 |
| 30%   36C    P8    29W / 300W |      0MiB / 45634MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

seems to be similar to what was fixed here : https://github.com/ecmwf/anemoi-training/pull/82#issue-2581613296

Can you try running without --config-dir and report back:
Just cd into the directory where happy_little_config.yaml exists, and then:
HYDRA_FULL_ERROR=1 ANEMOI_BASE_SEED=1 anemoi-training train --config-name happy_little_config

Thanks for the reference, this is insightful. However, doing a cd to .../lib/python3.11/site-packages/anemoi/training/config and running HYDRA_FULL_ERROR=1 ANEMOI_BASE_SEED=1 anemoi-training train --config-name=happy_little_config still gives the same error as in the original post.  Just let me know what additional info might be useful, some of the relevant packages in my environment are:

anemoi-training           0.3.0                    pypi_0    pypi
anemoi-utils              0.4.8                    pypi_0    pypi
hydra-core                   1.3.2                    pypi_0    pypi
pytorch-lightning         2.4.0                    pypi_0    pypi

Thanks, will investigate and get back to you asap.


--nosudo not working

I am trying to install GEMINI without admin access and it fails saying
gemini_install.py: error: unrecognized arguments: --nosudo
This is the command I used,
python gemini_install.py ~/gemini ~/gemini --nosudo

Hi, gemini doesn't use sudo any more, so just run without --nosudo.
I just removed the last remnants of that from the docs. thanks for reporting.

Thank you so much for the quick response!


Validate binary Search Tree

🛠 Issue (1131)
Issue no #1131

[✔] My code follows the code style of this project.
[✔] This PR does not contain plagiarized content.
[✔] The title of my pull request is a short description of the requested changes.

📷 Screenshots
C++

C

Java

Python

Resolve the CodeFactor issues

@Kumar-laxmi Resolved.

@Kumar-laxmi merge it is ready to merge for 2 weeks.


fix tritonserver gpu id & fixed timeout for criteo integration tests

Increases timeout on criteo because we have to account for more of dataset, so it takes more time. Added correct "0" gpu to account for blossom only supporting one GPU per job.

rerun tests


Where can i find stepper?

I want to create a process using stepper like as https://mdbootstrap.com/docs/b4/vue/components/stepper/.

It's unlikely this component would ever be made, especially prior to a v1.0. This is neither a Bootstrap or bootstrap-vue component. Maybe in the far future this library could be reviewed and some components could be ported over, but there's a lot to do before getting to that point.

@syukriyansyah-ipb Have you designed such a component in the meantime? I'm looking for that too.


Release: 3.1.0

@StarlightIbuki Hi! Thanks for opening this PR! Could you add these changes to #4860 instead and then close this PR? That's the PR we are using for merging all of our doc changes for 3.1 into main (we accidentally merged it yesterday). Thanks!

Hi @StarlightIbuki ! What is the purpose of this change, and where are you getting instructions to make it?
The change in this current PR deletes some needed metadata rather than adding any. As well, it's using labels that we don't use normally. Is this something coming from an automated process?
In general, the docs team handles release prep for both open-source and enterprise gateways. Engineers don't need to worry about updating the release metadata.

@lena-larionova Sorry for causing the confusion. This PR is created by an automation tool, a step called docs_pr in a script to release kong's new version. The script itself is manually involved so unless if there's someone like me mistakenly ran it, this will not happen.