id
stringlengths 4
10
| text
stringlengths 4
2.14M
| source
stringclasses 2
values | created
timestamp[s]date 2001-05-16 21:05:09
2025-01-01 03:38:30
| added
stringdate 2025-04-01 04:05:38
2025-04-01 07:14:06
| metadata
dict |
|---|---|---|---|---|---|
190237212
|
Add support for SHA2.384
SHA384 is the only hash size natively supported by Ruby in the SHA2 module that you were not supporting. This size is commonly used for Subresource integrity tags on the web and so would be convenient to store alongside web content that makes use of SRI.
Coverage decreased (-1.6%) to 81.429% when pulling 900432c6e72ba5d4f80992bba1f760b8c5c838a2 on grempe:updates into 6df2c884ccdfa0b048b79d1c207e0a87212b1798 on ioquatix:master.
Regarding the coveralls coverage decrease. There are no existing tests for most of the hash types. I would have been glad to add a test for my one-liner change if I was extending your existing test suite for hashes.
I will test this and add more specs for the hash functions, and then do a point release.
OKkay this is all done :) Thanks for all your feedback and ideas.
|
gharchive/pull-request
| 2016-11-18T05:07:01 |
2025-04-01T04:34:36.289650
|
{
"authors": [
"coveralls",
"grempe",
"ioquatix"
],
"repo": "ioquatix/fingerprint",
"url": "https://github.com/ioquatix/fingerprint/pull/3",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1104840140
|
Firefly on Mac doesnt open after Password !!! [Bug]:
Issue description
I have problems to get access to my account/Staking. after receiving iota it doesnt work
I have put in the password but the window doesnt start.
Sat, 15 Jan 2022 16:55:50 GMT
ReqwestError: error sending request for url (https://chrysalis-nodes.iota.cafe/api/plugins/participation/addresses/iota1qpjrqk84tu564k4kjqqllatajuee4uwxnphpg83dsta5877tycysgedeenp): error trying to connect: dns error: failed to lookup address information: nodename nor servname provided, or not known
Sat, 15 Jan 2022 16:55:50 GMT
ClientError: error sending request for url (https://mainnet-node.tanglebay.com/api/v1/info): error trying to connect: dns error: failed to lookup address information: nodename nor servname provided, or not known
Expected behaviour
Access to my account on firefly app / platform
Actual behaviour
after password, it is in a constant loading process ....
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
No response
Diagnostics
No response
Errors
Sat, 15 Jan 2022 16:55:50 GMT
ReqwestError: error sending request for url (https://chrysalis-nodes.iota.cafe/api/plugins/participation/addresses/iota1qpjrqk84tu564k4kjqqllatajuee4uwxnphpg83dsta5877tycysgedeenp): error trying to connect: dns error: failed to lookup address information: nodename nor servname provided, or not known
Sat, 15 Jan 2022 16:55:50 GMT
ClientError: `error sending request for url (https://mainnet-node.tanglebay.com/api/v1/info): error trying to connect: dns error: failed to lookup address information: nodename nor servname provided, or not known`
Duplicate declaration
[X] I have searched the issues tracker this issue and there is none
Code of Conduct
[X] I agree to follow this project's Code of Conduct
This is a duplicate to #2131. Therefore I´m going to close this issue. Please see the solution described below. If this doesn´t solve your issue please use issue #2131.
Here is the solution described in the reported issue:
Can you try it with a fresh installation of Firefly? Before you do that make sure to have your 24 words or a stronghold backup + password.
For a fresh installation uninstall Firefly and also delete the folder Firefly in username/Library/Application Support/ (macOS). With this folder all your data like your previous profiles will be deleted. Install Firefly again and restore your wallet with your 24 words or your stronghold file + password.
|
gharchive/issue
| 2022-01-15T20:23:37 |
2025-04-01T04:34:36.306013
|
{
"authors": [
"MiKeF05",
"PaulBo123"
],
"repo": "iotaledger/firefly",
"url": "https://github.com/iotaledger/firefly/issues/2134",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
838881721
|
Error "Addresses start with prefix atoi" when there is a typo in the address behind "atoi"
Issue description
Error "Addresses start with prefix atoi" when there is a typo in the address behind "atoi"
There is sometimes alos the the error pop-up "Somthing went wrong" with a mistyped address.
We should have different message for non-network prefix addresses and typos after the network prefix.
Wallet version
0.3.1
System specification
Win 10
Is it a repeatable issue?
Y
Steps To reproduce the issue
Try to send for exmaple to the invalid address "atoi1asdl7uasduz7asdjhasd7asdhasjdkasdhbbnasdasdad23nnnasdsadas3"
Expected behaviour
Expected error: "Invalid address: checksum failed"
Actual behaviour
Error "Addresses start with prefix atoi" (a user would be confused, as his address does start with the network prefix.
Or "Something went wrong", even when we know it's the address that is corrupted.
Errors
There are no errors logged.
hello, i have the same prefix address ( atoi ), when i try to send a transaction it is not possible ( invalide address ) what i have to do to solve the issue ? thanks
hello, i have the same prefix address ( atoi ), when i try to send a transaction it is not possible ( invalide address ) what i have to do to solve the issue ? thanks
Not every number starts with atoi is a valid address, a checksum validates addresses to avoid copy&paste and typo errors. IOTAs sent to an invalid address can never be recovered anymore, no one will ever find the private key.
The but greport here is that the error shoudl not say "Addresses start with ...", as sometimes they really do, but are stil invalid. I suggest in case they really do start with atoi... but is still invalid, to report "invalid address, please check again".
The atoi... prefix is just here to avoid a copy&paste error of an valid address i.e. from testnet to be used in mainnet (starts with iota...).
thanks for the information and clarification
user "dinangery" experienced the following:
directly after the first profile setup he wanted to request funds from the community, so he clicked on "receiving" and coied the shown address to the clipboard, pasted the address to discord.
I tried to send there and got following error:
logout and relogg didnt change his address, he also clicked the address refresh button, but address stayed the same
closing and restarting the wallet - still same receive address in this first account so he only could generate a new profile.
here his screenshots and errors:
https://cdn.discordapp.com/attachments/824207474470158346/824221744310779925/20210324_093710.jpg
https://cdn.discordapp.com/attachments/824207474470158346/824222955583832064/20210324_110705.jpg
https://cdn.discordapp.com/attachments/824207474470158346/824222956023840809/20210324_110654.jpg
https://cdn.discordapp.com/attachments/824207474470158346/824223927538155530/20210324_111108.jpg
I have improved the errors around the address validation.
But I think in dinangery case this was manually copied incorrectly, it should be atoi1lqqfgyr8fvakxpkfm5lej0k4fldwr2l4ena3nydc6vwyj7vlk5uywuwttztt
You can clearly see from the screen grab that there is a l after the atoi1 which matches the other characters that were transposed from "l" to "1"
I have the same issue , should I close this account and generate a new account?
|
gharchive/issue
| 2021-03-23T16:04:20 |
2025-04-01T04:34:36.315996
|
{
"authors": [
"Phyloiota",
"dinangeri",
"github-i286",
"obany",
"xiaoru99"
],
"repo": "iotaledger/firefly",
"url": "https://github.com/iotaledger/firefly/issues/715",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1301487093
|
feat: implement android back action
Summary
This PR implement android back button action, preventing the app from close asking with a drawer to exit, or formir going back again.
Changelog
- Look commits ;)
Relevant Issues
Closes #2638
Testing
Platforms
Please select any platforms where your changes have been tested.
Desktop
[ ] MacOS
[ ] Linux
[ ] Windows
Mobile
[ ] iOS
[x] Android
Instructions
Please describe the specific instructions, configurations, and/or test cases necessary to test and verify that your changes work as intended.
...
Checklist
Please tick all of the following boxes that are relevant to your changes.
[ ] I have followed the contribution guidelines for this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or modified tests that prove my changes work as intended
[ ] I have verified that new and existing unit tests pass locally with my changes
[ ] I have verified that my latest changes pass CI workflows for testing and linting
[ ] I have made corresponding changes to the documentation
I have some points about the approach:
When I close the app through the back button and restart again, it always throws me out after entering the pin. Can you confirm that?
Can't close the popup through a swipe or with clicking the shaded area
Maybe it would be better to use the popup to say that the back button action is disabled for now? At least until the first point is fixed?
* When I close the app through the back button and restart again, it always throws me out after entering the pin. Can you confirm that?
It's only happens on dev mode, if you execute: yarn build && NODE_ENV=production yarn android works without crash.
* Can't close the popup through a swipe or with clicking the shaded area
yes it should be done better, I could not find a fast way to implement it with the popup, but you right we should allow to close with swipe gesture.
* Maybe it would be better to use the popup to say that the back button action is disabled for now? At least until the first point is fixed?
yes why not, what do you suggest? I'm out of ideas 😅
I'll keep it opened to make the changes
It's only happens on dev mode, if you execute: yarn build && NODE_ENV=production yarn android works without crash.
Okay, then it is just about closing the popup. Forget about the first and the last point.
yes why not, what do you suggest? I'm out of ideas
I would say the solution is a good workaround, I was just worried about the pin crash thing. So maybe you can add the swipe. If that would take too long merge anyway.
I've double checked and finally could be able to reproduce it, so before the release I hidded the code to exit the app to avoid the crash. I've created a new task to work on the fixes.
Let's merget it to get the uploaded state.
|
gharchive/pull-request
| 2022-07-12T03:30:45 |
2025-04-01T04:34:36.325607
|
{
"authors": [
"amadeu2",
"paul-boegelsack"
],
"repo": "iotaledger/firefly",
"url": "https://github.com/iotaledger/firefly/pull/3852",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
296580106
|
Inconsistent API with JS lib
Why does the sendTrytes func expect []Transaction instead of []Trytes
https://godoc.org/github.com/iotaledger/iota.lib.go#SendTrytes
Doesn't the JS lib expect an array of trytes? Why are they inconsistent?
Good point, I think a SendTransactions function would be better, so that the user doesn't have to convert between Trytes and Transactions.
next/v1.0.0 is/will be aligned with the iota.js library.
|
gharchive/issue
| 2018-02-13T01:08:02 |
2025-04-01T04:34:36.328227
|
{
"authors": [
"AaronVasquez",
"cwarner818",
"luca-moser"
],
"repo": "iotaledger/giota",
"url": "https://github.com/iotaledger/giota/issues/52",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1000901210
|
[Task] Separate DID from DIDUrl
Description
Split CoreDID and IotaDID into separate DID and DIDUrl structs.
E.g.:
DID: "did:iota:main:9rK6DPF46MCEzgfLD8AHFsaTuMqvmRo6kbXfjqQJPJmC"
DIDUrl: "did:iota:main:9rK6DPF46MCEzgfLD8AHFsaTuMqvmRo6kbXfjqQJPJmC/path?query#keys
Motivation
We currently have two DID structs: CoreDID and IotaDID:
CoreDID is a re-export of the did-url crate, which is optimised to represent a full DIDUrl, potentially including a fragment, query, and/or path.
IotaDID just wraps CoreDID to enforce the IOTA DID Method specification.
The discussion in #387 makes apparent that we need some way to distinguish a DID from a DIDUrl. Specifically to enforce invariants in structs and improve clarity in function parameters.
For example:
a CoreDocument uses CoreDID (DIDUrl) for the id and controller fields, which should conform to the base DID syntax according to the did-core specification, but currently theoretically allows any DIDUrl.
Client::resolve takes an IotaDID (DIDUrl) parameter but ignores any URL segments and just uses the base DID.
the Account defines an IdentityTag which represents just the network and tag of a DID for mapping internally.
Note that any solution should translate well to the external Wasm bindings API, which does not support generics or interfaces properly.
NOTE: any invariants should be enforced when deserialising these structures.
Resources
DID: https://www.w3.org/TR/did-core/#did-syntax
DIDUrl: https://www.w3.org/TR/did-core/#did-url-syntax
To-do list
Please link PRs that match the To-do list item behind the item after it has been submitted.
[ ] Implement CoreDID and CoreDIDUrl
[ ] Implement IotaDID and IotaDIDUrl
[ ] Replace IdentityTag, IdentityKey with IotaDID in the Account
Change checklist
Add an x to the boxes that are relevant to your changes, and delete any items that are not.
[ ] The feature is implemented in Rust and across all bindings whereas possible.
[ ] The feature has sufficient testing coverage
[ ] All tests and examples build and run locally as expected
[ ] Every piece of code has been document according to the documentation guidelines.
[ ] If conceptual documentation (mdbook) and examples highlighting the feature exist, they are properly updated.
[ ] If the feature is not currently documented, a documentation task Issue has been opened to address this.
Very nice proposal!
Does that mean that Account::sign would in the future take just a IotaDidUrl? E.g.:
BEFORE: account.sign(did, "key-1", &mut credential).await?;
AFTER: account.sign(did_url, &mut credential).await?;
and I imagine it would be nice to have methods that can easily convert to a url. For example
let did: IotaDid = "did:iota:main:9rK6DPF46MCEzgfLD8AHFsaTuMqvmRo6kbXfjqQJPJmC".parse().unwrap();
let did_url: IotaDidUrl = did.to_url().set_fragment("key-1");
account.sign(did_url, &mut credential).await?;
Seems like that would be a nice-to-have to make working with Account::sign easy, given just an IotaDid. It can look different, of course, but the point is, it should be easy to convert.
|
gharchive/issue
| 2021-09-20T12:15:38 |
2025-04-01T04:34:36.340335
|
{
"authors": [
"PhilippGackstatter",
"cycraig"
],
"repo": "iotaledger/identity.rs",
"url": "https://github.com/iotaledger/identity.rs/issues/408",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2158870134
|
Mark filtered blocks as invalid.
We currently do not mark filtered blocks as invalid. It seems to me that it would make sense to mark such a block as invalid.
Originally posted by @jonastheis in https://github.com/iotaledger/iota-core/issues/90#issuecomment-1963514907
We should re-think if the Invalid flag on a block level still makes sense.
|
gharchive/issue
| 2024-02-28T12:36:04 |
2025-04-01T04:34:36.342291
|
{
"authors": [
"piotrm50"
],
"repo": "iotaledger/iota-core",
"url": "https://github.com/iotaledger/iota-core/issues/783",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1355966345
|
Add testnet support for Ledger device
Description
Currently Ledger accounts only encode addresses for the Shimmer mainnet HRP, despite being connected to a testnet. It would be nice to have testnet HRP support on Ledger devices, but that requires also changing the coin_type parameter in the BIP32 path.
It seems that testnet BIP paths typically use 0x1 in the BIP path rather than the actual coin_type as to prevent replay attacks with testnet transactions.
# Shimmer mainnet BIP32 path
2c'/107b'/...
# Shimmer testnet BIP32 path
2c'/1'/...
Motivation
Not technically necessary, but it would be nice to have matching addresses displayed both in Firefly confirmation popups and the Ledger device prompt rather than a testnet address in Firefly and a mainnet address on the device.
Requirements
Write a list of what you want this feature to do.
Deduce from the client options whether the account manager is a dev one or not
Display testnet addresses if "dev" account manager and mainnet addresses if normal account manager
Open questions (optional)
N/a
Are you planning to do it yourself in a pull request?
No.
The bech32 HRP is hardcoded in the ledger app for security reasons, we can't change it without a change in https://github.com/iotaledger/ledger-shimmer-app (which will most likely not happen, but feel free to open an issue there)
|
gharchive/issue
| 2022-08-30T15:42:44 |
2025-04-01T04:34:36.349336
|
{
"authors": [
"Thoralf-M",
"maxwellmattryan"
],
"repo": "iotaledger/wallet.rs",
"url": "https://github.com/iotaledger/wallet.rs/issues/1398",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
187774343
|
Add page that shows all blog posts (multiPage).
Picking up from the previous PR...
Add the page that shows al blog posts (actually, just shows 20 max for now).
Reuse some common code.
This is probably ready for @kianoshp or @hthi to look at the html and css.
So.... now I've got the site rendering mostly using a simple, custom-written template function. There's one view that's rendered via server-side React. Now I'm wondering which direction I should go: 100% React or 100% simple.
I wrote the simple function when I couldn't figure out how to get server-side React to work. I like that it allows the templates to be HTML. (imho, this makes them easier to iterate on -- and jibes with my forthcoming Scalability blog posts.) On the other hand, I feel like we might want to demonstrate our React skillz.
Comments?
|
gharchive/pull-request
| 2016-11-07T17:25:07 |
2025-04-01T04:34:36.353025
|
{
"authors": [
"unscriptable"
],
"repo": "iotopia-solutions/the-site",
"url": "https://github.com/iotopia-solutions/the-site/pull/10",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
2320019675
|
🛑 备用KMS激活服务器 01 is down
In f41381c, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:
HTTP code: 0
Response time: 0 ms
Resolved: 备用KMS激活服务器 01 is back up in b293ec3 after 10 minutes.
|
gharchive/issue
| 2024-05-28T02:47:33 |
2025-04-01T04:34:36.357603
|
{
"authors": [
"iougemini"
],
"repo": "iougemini/ikms-uptime",
"url": "https://github.com/iougemini/ikms-uptime/issues/1664",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2731387273
|
🛑 备用KMS激活服务器 11 is down
In 359f3b0, 备用KMS激活服务器 11 (s01.ikms.eu.org) was down:
HTTP code: 0
Response time: 0 ms
Resolved: 备用KMS激活服务器 11 is back up in 09e905f after 29 minutes.
|
gharchive/issue
| 2024-12-10T22:54:16 |
2025-04-01T04:34:36.359921
|
{
"authors": [
"iougemini"
],
"repo": "iougemini/ikms-uptime",
"url": "https://github.com/iougemini/ikms-uptime/issues/3630",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
679820646
|
RFC: pid/tgid in a namespaces
The pid and tgid grab the values from the root namespace. This can make it tricky to related events you see in your namespace/container to what you see on the host.
A new helper landed in 5.6 which makes it possible grab the pid/tgid from within the namespace
int bpf_get_ns_current_pid_tgid(u64 dev, u64 ino, struct
bpf_pidns_info *nsdata, u32 size)
Description
Returns 0 on success, values for pid and tgid as seen
from the current namespace will be returned in nsdata.
Return 0 on success, or one of the following in case of
failure:
-EINVAL if dev and inum supplied don't match dev_t and
inode number with nsfs of current task, or if dev
conversion to dev_t lost high bits.
-ENOENT if pidns does not exists for the current task.
(dev and ino are used to identify the namespace, they're obtained by stating /proc/pid/ns/pid)
The namespace id (dev+ino) makes this helper a bit trickier to use. It cannot be used as a simple builtin, like pid and tid are.
I've been playing with this for a bit, what I've come up with
pidns_id(const pid_t pid)
pidns_id(uint64_t dev, uint64_t ino)
This creates a "pid namespace identifier". The pid version gets resolved at compile time, the dev/ino version can be done at run time (altough im not sure there is a way to get these values easily).
Internally this will be an immutable struct like type that can be assigned to variables and maps.
For the pid/tgid:
nspid(pidns_id id)
nstgid(pidns_id id)
and a shortcut with a pid
nspid(const pid_t pid)
nstgid(const pid_t pid)
these would be equal to nspid(pidns_id(<pid>))
An example of opensnoop in a single namespace would be:
BEGIN { @ns = pidns_id(123); }
tracepoint:syscalls:sys_enter_openat
/nspid(@ns)/ {
printf("%lu [%lu] %s\n", nsec, nspid(@ns), str(args->filename));
}
I'm mainly concerned about the pidns_id call, but I cannot come up with an alternative either.
I've got a PoC implementation that mostly works here
Thoughts?
Related to #1462
@brendangregg
Naming aside (we can debate about that later), I'm not sure I like how pidns_id is a compile time function where the args have to be hard coded in. That makes it hard to write a reusable script.
As a more restricted alternative, what about having a nspid/nstgid builtin that prints the current pid/tgid viewed from bpftrace's pid namespace? Then users can do nsenter -p -t $TARGET_PID /bin/sh -c 'bpftrace myscript.bt' or equivalent.
Thanks :)
As a more restricted alternative, what about having a nspid/nstgid builtin that prints the current pid/tgid viewed from bpftrace's pid namespace? Then users can do nsenter -p -t $TARGET_PID /bin/sh -c 'bpftrace myscript.bt' or equivalent. This option feels a bit more unix-y to me.
Having it default to the namespace bpftrace is in sounds good. The nsenter feels a but clunky but might work well enough.
Naming aside (we can debate about that later), I'm not sure I like how pidns_id is a compile time function where the args have to be hard coded in. That makes it hard to write a reusable script.
nspid($1) or pidns_id($1) should work but it's not great.
The main reason I had for adding pidns_id what that it gives you some flexibility, you can assign it and reuse it. Maybe filter 2 namespaces at once. But we could also add that when we have a good usecase for it.
I think both versions (builtin and call) would benefit from a good way to supply args to a script (other than positional args).
|
gharchive/issue
| 2020-08-16T20:29:13 |
2025-04-01T04:34:36.370274
|
{
"authors": [
"danobi",
"fbs"
],
"repo": "iovisor/bpftrace",
"url": "https://github.com/iovisor/bpftrace/issues/1467",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
627025494
|
Remove RLIMIT_AS limit
We haven't seen any OOM issues in a while so I suspect either our type
fixes in bpftrace or upstream llvm changes have resolved the issue.
This closes #1355.
Checklist
[ ] Language changes are updated in docs/reference_guide.md
[x] User-visible and non-trivial changes updated in CHANGELOG.md
LGTM!
(Maybe we could set up some alarms in our infra to see how OOMs / memory usage our bpftrace invocations get?)
|
gharchive/pull-request
| 2020-05-29T06:14:16 |
2025-04-01T04:34:36.372661
|
{
"authors": [
"danobi",
"javierhonduco"
],
"repo": "iovisor/bpftrace",
"url": "https://github.com/iovisor/bpftrace/pull/1358",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
420368748
|
"Nativeness" of IPFS Desktop
As of building #866, we clearly verify that the app could be much better and simpler if done natively or with something else than Electron that is even snappier/faster. Although, the approach of going full native have pros and cons. I'd like to discuss with you all if this is an effort we should focus on or not.
How
By going native, we'd need to create separate macOS, Windows and Linux apps. During transition period, we could eventually build one by one and keep the Electron version alongside.
For macOS: we could write an app natively in Swift.
For Windows: we could write an app natively in C#.
For Linux: we could either keep the Electron version or see if we could manage to do something else with Qt perhaps. To refer that Linux is the OS where things can vary more and is harder to support.
We could perhaps have a shared library in C++ if needed for something like a ipfsd-ctl. Or perhaps we wouldn't even need it.
Cons
Usually people start by the pros, but I thought about starting with the negative aspects of going native:
We'd need to support three different technologies.
The above requires more work to keep the three platforms in parity of functionality.
We'd need to, perhaps, ditch the "so-deep" integration with Web UI. It's not that deep: it's just the language and three preferences. We could just open the Web UI on user's default browser.
Pros
On the bright side of the situation:
Native means native.
Better functionality:
Right now, the macOS app is the one which seems more native because Electron uses the native menus. On the other hand, on Windows, Electron doesn't use the native menu's and doesn't feel as native.
There are some features really hard to implement using the current solution. Please see https://github.com/ipfs-shipyard/ipfs-desktop/issues/678#issuecomment-472479791 for an example.
By being native we could perfect the functionality.
Smaller binaries.
Faster.
I'd really like your thoughts on this. There are some things I'd like to implement (native integrations) but that won't be really easy to do with Electron/Node.js. Not impossible, just harder.
This would be a big change and would require a lot of work. Would it be worth it?
Not entirely "native" but DeskGap could be a viable lighter-weight alternative too, it uses the OS webview rather than bundling chromium. Might we worth experimenting with.
@cwaring didn't know that! I'll keep an eye of them. They're still missing really important APIs for us such as Tray.
Dear friends, just updated the main comment. Please read through it and leave your comments. /cc @cwaring @olizilla @alanshaw @lidel @fsdiogo 😄
My concerns about switching from a single language/library to three would be related to PMing challenges:
spreading ipfs-desktop team too thin, or
overhead of the need to sync between implementations
(especially if team grows and development/bugfixes are done by different people)
That being said, if we keep app's surface small, getting MVP in sync on all three platforms would be mostly a one-time effort. Everything else would be platform-specific native integrations that do not block/lag other implementations.
@lidel for me, the main feature of IPFS Desktop is to keep running IPFS in the background. Everything else are native integrations (drag'n'drop, add to context menu, protocol handling, etc...).
I can't see many features that could be considered 'attached' to what IPFS Desktop is. Perhaps if we added the possibility of running multiple versions/nodes yes, that would be required to be in all implementations, but those are good functionalities. I think the main point is to provide good and reliable native integrations.
So... I agree with you and I believe that basically what we have now is IPFS running + native integrations. The only thing we'd need to ditch is the Web UI inside a Window perhaps. But I don't think that'd be a really big/important change IMO. We could even tell that Web UI's running through Desktop with a URL query value. What do you think?
I'd like to improve the stability of what we have first. I think 0.7 is a good release, but I know we can make it better.
We're a small team with a large number of websites and apps to look after, so I'd rather we spend the next quarter improving what we have before we explore starting again.
I do totally take your point @hacdias that now we have reduced the scope of IPFS Desktop right down, it'd make a lot of sense to try out a fully native alternative, but don't forget that we need to also come up with reliable installers and update mechanism for each platform, it just feels like we should spend our time improving proto.school and js-ipfs and webui in time for camp.ipfs.io as a much higher priority.
Something just caught my eye: https://wails.io/
cc @SgtPooki
related to #2184
Something just caught my eye: https://wails.io/
I think Tauri would work better tbh, as there is Android and iOS support in the works right now, but I could be wrong here. :)
Just FYI - I tried https://github.com/fyne-io/fyne and it looks promising, but I couldn't get it to work.
I agree that Wails might IMHO be best for GO apps and especially IPFS. I would be super happy if you decide to switch to it 😉
Fyi that selfupdate is possible with wails. Example at https://github.com/achhabra2/riftshare/blob/main/internal/update/selfupdate.go
Wails maintainer here 👋 Would be happy to support your efforts if you decided to use it or do a PoC 👍
Wails maintainer here 👋 Would be happy to support your efforts if you decided to use it or do a PoC 👍
@leaanthony I attempted a small PoC with https://github.com/SgtPooki/ipfs-desktop-wails but i'm not a gopher and i'm not sure how best to execute another go-cli(https://github.com/ipfs/kubo) as a subprocess. Ideally, Kubo functionality should all exist in https://github.com/ipfs/boxo but we're not there yet.
I attempted a PoC with https://github.com/SgtPooki/ipfs-desktop-wails. But I haven't touched it in a while. I think the only blocker for me right now is figuring out how to execute Kubo on the backend (and get TS types from Kubo's go types) to allow for easy migration to Boxo in the future.
If anyone wants to help with that repo, please let me know and I can add you as a maintainer.
I attempted a PoC with https://github.com/SgtPooki/ipfs-desktop-wails. But I haven't touched it in a while. I think the only blocker for me right now is figuring out how to execute Kubo on the backend (and get TS types from Kubo's go types) to allow for easy migration to Boxo in the future.
If anyone wants to help with that repo, please let me know and I can add you as a maintainer.
I am not sure if I can be "maintainer" level, but count me interested.
Also, @SgtPooki, should we create GitHub discussion or maybe Discord channel on IPFS server to discuss this alternative implementation.
ie. I am not sure it is right move to have process fork to run Kubo, while you can just allow (for now) users to run pure Kubo or IPFS Desktop in background, while ipfs-desktop-wails is in alpha state.
Also, I was not entirely able to get the embed the IPFS (web) UI to get work from your repo,
but that should (I hope) be easy fix, if all you need is Wails to be a wrapper around it.
Later on, ipfs-desktop-wails can be bound to Boxo library and even (ideally) use Go layer instead of JavaScript one.
Anyway, I am more than happy to dive into this - I just think we need different thread for that :-/
You can expose Go structs and methods to TS via the automatic bindings and model generator. It's not perfect but works for most use cases.
I wrote this as a slack update, but moving here so it can be referenced in future
My understanding is that the conversation on Wails stalled due to the lack of resources.
Mind, the current team does not have spare cycles to do basic maintenance like updating to latest Electron (https://github.com/ipfs/ipfs-desktop/issues/2775).
Personally, I'd love to make ipfs-desktop more lean, and leave Electron behind, but rewriting with a different engine requires full-time commitment over a long period of time, which the team is not able to allocate right now.
If someone is determined to help and make this happen,
it is fine to work on this in their own repo until it is ready.
In my mind, problems that need to be solved by such person (in order):
propose new autoupdate mechanism
iiuc (https://github.com/wailsapp/wails/issues/1178) Wails seems to have no robust anser for this, there are many competing libraries with single maintainer.
we can't switch to something worse than current one based on actively maintained electron-updater with distribution based on Github Releases.
have a plan for migrating existing users that are tied to electron-updater
porting current functionality (embedding kubo + ipfs-webui as PWA looking as native app, context menu integration on MS Windows etc)
Mind, until autoupdate story is not ready, there is no point in spending time porting functionality.
iiuc (Support Self-Updating wailsapp/wails#1178) Wails seems to have no robust anser for this, there are many competing libraries with single maintainer.
We don't have an official updater because the feedback from the community was that people wanted to make their own as they have different needs. Not that it's hard mind: https://github.com/achhabra2/riftshare/blob/main/internal/update/selfupdate.go
|
gharchive/issue
| 2019-03-13T08:17:28 |
2025-04-01T04:34:36.494293
|
{
"authors": [
"RubenKelevra",
"SgtPooki",
"cwaring",
"hacdias",
"leaanthony",
"lidel",
"mainiak",
"olizilla"
],
"repo": "ipfs/ipfs-desktop",
"url": "https://github.com/ipfs/ipfs-desktop/issues/867",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
989485937
|
🛑 Kicking (recu) is down
In a90dbd7, Kicking (recu) (https://recu.kickinglotus.com/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Kicking (recu) is back up in fcf227d.
|
gharchive/issue
| 2021-09-06T23:51:27 |
2025-04-01T04:34:36.545064
|
{
"authors": [
"iplanwebsites"
],
"repo": "iplanwebsites/up",
"url": "https://github.com/iplanwebsites/up/issues/74",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1706666210
|
how to update channels.xml files
Description
so i know how to run the grabber to scrape my own guide locally, but how can i update the channels.xml files to add more channels to scrape? i manually added a few more channels to one of the xml files by matching names and id's from the guide website but that would take so long to do!
Checkout the Contributing Guide. The same applies to local edits but may as well share with the community if you find some channels that can be added.
|
gharchive/issue
| 2023-05-11T22:44:01 |
2025-04-01T04:34:36.567144
|
{
"authors": [
"PopeyeTheSai10r",
"ovladuk"
],
"repo": "iptv-org/epg",
"url": "https://github.com/iptv-org/epg/issues/2053",
"license": "Unlicense",
"license_type": "permissive",
"license_source": "github-api"
}
|
111494396
|
Allow for numeric labels and retain type information on selection
closes #157
@jdfreder on :fire:
@jdfreder on
Yes, it's a good day to get some ipywidgets stuff done. I'll try to push 4.1 by this weekend.
|
gharchive/pull-request
| 2015-10-14T21:12:08 |
2025-04-01T04:34:36.592214
|
{
"authors": [
"SylvainCorlay",
"jdfreder"
],
"repo": "ipython/ipywidgets",
"url": "https://github.com/ipython/ipywidgets/pull/179",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
1234521397
|
What is happening in SRR17712969 at M3
Both V (v0.3.7) and G illumina have in green embedded in blue
Here is G
and here is V
closing - trees are cleaner with refactor, and these issues have become noise. have added a label so can find again
|
gharchive/issue
| 2022-05-12T21:58:45 |
2025-04-01T04:34:36.594192
|
{
"authors": [
"iqbal-lab"
],
"repo": "iqbal-lab-org/viridian_workflow",
"url": "https://github.com/iqbal-lab-org/viridian_workflow/issues/62",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1549631980
|
[WIP] Data Tiling for GPU
This PR is the first attempt for data tiling for GPUs. It implements materialization for the encoding.
Note that, it cannot compile any program. Because it generates tensor.pad and we don't know how to tile it yet. #10184 can be enabled to tile for tensor.pad but it results bufferization problem #11273
Closing stale PR.
|
gharchive/pull-request
| 2023-01-19T17:36:24 |
2025-04-01T04:34:36.669257
|
{
"authors": [
"benvanik",
"grypp"
],
"repo": "iree-org/iree",
"url": "https://github.com/iree-org/iree/pull/11904",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2451159752
|
Trim installed packages in samples.yml.
This fixes the nightly 'samples' workflow.
I thought this libstdc++-12-dev dep would help use clang instead of gcc here: https://github.com/iree-org/iree/pull/18076. Turns out that package doesn't exist on ubuntu-20.04: https://github.com/iree-org/iree/actions/runs/10260247034/job/28385997161#step:4:43 E: Unable to locate package libstdc++-12-dev. A working clang toolchain also already exists. Ugh Linux. Tested here: https://github.com/ScottTodd/iree/actions/runs/10269229609.
(Yes, we could use Docker to manage toolchains / system deps like this, but I'd really rather not)
skip-ci: no impact on regular workflows (and soon this won't trigger them at all)
If the intend was to get to use clang instead of gcc and if this package is required, what about upgrading the action to ubuntu-22.04 for which the package is available? Anyway, trimming the list of packages to install looks good to me.
That would work too, but I'd prefer to bump all uses of ubuntu-20.04 across the repo at the same time.
|
gharchive/pull-request
| 2024-08-06T15:24:49 |
2025-04-01T04:34:36.672308
|
{
"authors": [
"ScottTodd"
],
"repo": "iree-org/iree",
"url": "https://github.com/iree-org/iree/pull/18117",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
511697844
|
number validator cannot return false
resty -e 'local jsonschema = require "resty.jsonschema" local myvalidator = jsonschema.generate_validator {
type = 'object',
properties = {
foo = { type = 'string' },
bar = { type = 'number' },
},
}
print(myvalidator{ foo='sss', bar=ppp }) '
true
resty -e 'local jsonschema = require "resty.jsonschema" local myvalidator jsonschema.generate_validator {
type = 'object',
properties = {
foo = { type = 'string' },
bar = { type = 'number' },
},
}
print(myvalidator{ foo=111, bar=ppp }) '
falseproperty "foo" validation failed: wrong type: expected one of , got number
local jsonschema = require "resty.jsonschema"
local myvalidator = jsonschema.generate_validator {
type = 'object',
properties = {
foo = { type = 'string' },
bar = { type = 'number' },
},
}
-- ppp is nil
print("1st: ", myvalidator({foo='sss', bar=ppp}))
print("2st: ", myvalidator({foo='sss'}))
local ppp = "sss"
print("3st: ", myvalidator({foo='sss', bar=ppp}))
+ resty test.lua
1st: true
2st: true
3st: falseproperty "bar" validation failed: wrong type: expected number, got string
$ cat test.lua
local jsonschema = require "resty.jsonschema"
local myvalidator = jsonschema.generate_validator {
type = 'object',
properties = {
foo = { type = 'string' },
bar = { type = 'number' },
},
required = {"foo", "bar"}
}
print("1st: ", myvalidator({foo='sss', bar=ppp}))
print("2st: ", myvalidator({foo='sss'}))
$ resty test.lua
|
gharchive/issue
| 2019-10-24T04:23:15 |
2025-04-01T04:34:36.676468
|
{
"authors": [
"membphis",
"zcong2333"
],
"repo": "iresty/lua-resty-jsonschema",
"url": "https://github.com/iresty/lua-resty-jsonschema/issues/6",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1816797225
|
Suggestion : Add TreeDataGrid control theme
It is a control provided and supported by Avalonia team, and they often suggest to use it over default datagrid port.
Lots of themes does not have support for it, so having theme for this control will help Avalonia.Semi to stand out
https://github.com/AvaloniaUI/Avalonia.Controls.TreeDataGrid
Will take a look.
https://github.com/AvaloniaUI/Avalonia.Controls.TreeDataGrid/tree/master/src%2FAvalonia.Controls.TreeDataGrid%2FThemes
Surprisingly TreeDataGrid is targeting .net 5 instead of .net standard 2.0 ...
|
gharchive/issue
| 2023-07-22T15:13:21 |
2025-04-01T04:34:36.681913
|
{
"authors": [
"Al-Dyachkov",
"rabbitism"
],
"repo": "irihitech/Semi.Avalonia",
"url": "https://github.com/irihitech/Semi.Avalonia/issues/238",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1921630910
|
code: added org
Hey there, I have added ReactPlay which is an open-source platform to learn, create and share ReactJS projects with the developer community.
Kindly review and merge my PR !
Hey @iriteshmishra kindly label the PR as hacktoberfest accepted, for it to count as a PR in the event !
I have added both @dakshsinghrathore thanks for reminding me.
|
gharchive/pull-request
| 2023-10-02T10:16:52 |
2025-04-01T04:34:36.760246
|
{
"authors": [
"dakshsinghrathore",
"iriteshmishra"
],
"repo": "iriteshmishra/Open-source-Organization",
"url": "https://github.com/iriteshmishra/Open-source-Organization/pull/2",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
771778862
|
3.5.30 worker version not listening on port 5001
Fresh download of the worker application. Unzip and run, but it only starts the http listener on port 5000 and not the https listener, so it's not possible to sign in to O365.
Startup messages:-
info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[63]
User profile is available. Using 'C:\Users\Richard\AppData\Local\ASP.NET\DataProtection-Keys' as key repository and Windows DPAPI to encrypt keys at rest.
info: Microsoft.Hosting.Lifetime[0]
Now listening on: http://localhost:5000
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: C:\Users\Richard\Downloads\3.5.30_Windows_x64_x86
Hmmm odd, this is what I get if I download latest. Do you have the dotnet core dev cert installed?
https://docs.microsoft.com/en-us/aspnet/core/security/enforcing-ssl?view=aspnetcore-5.0&tabs=visual-studio#trust-the-aspnet-core-https-development-certificate-on-windows-and-macos
That was it - didn't have the dev cert installed.. Thanks! Might be worth mentioning that in the documentation - I'd assumed I could just download and run this version.. Or maybe have it throw an error that it can't find the dev cert? At the moment, it doesn't do anything other than not listen on 5001.
Are there any plans to update this version to have the custom API options? I've used those on the other version to successfully integrate with HomeAssistant.
Or to add MQTT support, which would also be incredibly useful.
My goal is to add feature parity between the 2. I will also add a note in the README.
Closing and creating feature request #213
Closing and creating feature request #213
|
gharchive/issue
| 2020-12-21T02:01:02 |
2025-04-01T04:34:36.849296
|
{
"authors": [
"isaacrlevin",
"rscott1010101"
],
"repo": "isaacrlevin/PresenceLight",
"url": "https://github.com/isaacrlevin/PresenceLight/issues/207",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
189552707
|
win32 rename EPERM: fail fast if target exists
When rename is used on Windows, and encounters an EPERM or EACCES
error, graceful-fs will retry for up to 30 seconds with gradual backoff
to get around file system locking due to A/V etc.
This was fixed in 59145cea32af980b675121ebc8c3255f780b7fc5
However, this is a problem if the target exists, which can cause an
EPERM or EACCES that is not due to folder locking.
This commit causes it to fail fast when an EPERM or EACCES is
raised by rename if the target exists.
Fix #98
r? @sam-github
LGTM
|
gharchive/pull-request
| 2016-11-16T00:57:52 |
2025-04-01T04:34:36.853436
|
{
"authors": [
"isaacs",
"sam-github"
],
"repo": "isaacs/node-graceful-fs",
"url": "https://github.com/isaacs/node-graceful-fs/pull/100",
"license": "isc",
"license_type": "permissive",
"license_source": "bigquery"
}
|
3479546
|
npm fails installing in vmware "shared folders"
Hi
npm fails installing any package in vmware tools "shared folders".
My development environment:
Mac OS X 10.7.3 --> VMware Fusion Version 4.0.2 (491587) with vmware tools and "shared folders". VM: CentOS 5.7.
My Node.js application is located within CentOS 5.7 and within "shared folders".
Here is the full error log:
[root@vm MyApplicationFolder]# cat /mnt/hgfs/workspace/MyApplicationFolder/npm-debug.log
info it worked if it ends with ok
verbose cli [ 'node', '/usr/local/bin/npm', 'install' ]
info using npm@1.1.0-2
info using node@v0.6.6
verbose config file /root/.npmrc
verbose config file /usr/local/etc/npmrc
verbose config file /usr/local/lib/node_modules/npm/npmrc
verbose caching /mnt/hgfs/workspace/MyApplicationFolder/package.json
verbose loadDefaults MyApplicationFolder@0.0.1
verbose where, deps [ '/mnt/hgfs/workspace/MyApplicationFolder',
verbose where, deps [ 'express',
verbose where, deps 'xml2js',
verbose where, deps 'request',
verbose where, deps 'mongoskin',
verbose where, deps 'eventemitter2',
verbose where, deps 'jsonrpc2',
verbose where, deps 'clone',
verbose where, deps 'winston',
verbose where, deps 'forever' ] ]
verbose from cache /mnt/hgfs/workspace/MyApplicationFolder/package.json
info preinstall MyApplicationFolder@0.0.1
verbose caching /mnt/hgfs/workspace/MyApplicationFolder/node_modules/clone/package.json
verbose loadDefaults clone@0.0.4
verbose caching /mnt/hgfs/workspace/MyApplicationFolder/node_modules/jsonrpc2/package.json
verbose loadDefaults jsonrpc2@0.1.1
verbose caching /mnt/hgfs/workspace/MyApplicationFolder/node_modules/eventemitter2/package.json
verbose loadDefaults eventemitter2@0.4.8
verbose caching /mnt/hgfs/workspace/MyApplicationFolder/node_modules/winston/package.json
verbose loadDefaults winston@0.5.10
verbose caching /mnt/hgfs/workspace/MyApplicationFolder/node_modules/express/package.json
verbose loadDefaults express@2.5.2
verbose caching /mnt/hgfs/workspace/MyApplicationFolder/node_modules/mongoskin/package.json
verbose loadDefaults mongoskin@0.3.0
verbose caching /mnt/hgfs/workspace/MyApplicationFolder/node_modules/jquery/package.json
verbose loadDefaults jquery@1.6.3
verbose caching /mnt/hgfs/workspace/MyApplicationFolder/node_modules/request/package.json
verbose loadDefaults request@2.9.100
verbose caching /mnt/hgfs/workspace/MyApplicationFolder/node_modules/xml2js/package.json
verbose loadDefaults xml2js@0.1.13
verbose from cache /mnt/hgfs/workspace/MyApplicationFolder/package.json
verbose from cache /mnt/hgfs/workspace/MyApplicationFolder/node_modules/clone/package.json
verbose from cache /mnt/hgfs/workspace/MyApplicationFolder/node_modules/eventemitter2/package.json
verbose from cache /mnt/hgfs/workspace/MyApplicationFolder/node_modules/express/package.json
verbose from cache /mnt/hgfs/workspace/MyApplicationFolder/node_modules/jquery/package.json
verbose from cache /mnt/hgfs/workspace/MyApplicationFolder/node_modules/jsonrpc2/package.json
verbose from cache /mnt/hgfs/workspace/MyApplicationFolder/node_modules/mongoskin/package.json
verbose from cache /mnt/hgfs/workspace/MyApplicationFolder/node_modules/request/package.json
verbose from cache /mnt/hgfs/workspace/MyApplicationFolder/node_modules/winston/package.json
verbose from cache /mnt/hgfs/workspace/MyApplicationFolder/node_modules/xml2js/package.json
verbose already installed in /mnt/hgfs/workspace/MyApplicationFolder skipping clone@>= 0.0.4
verbose already installed in /mnt/hgfs/workspace/MyApplicationFolder skipping winston@>= 0.5.10
verbose cache add [ 'forever@>= 0.8.5', null ]
silly cache add: name, spec, args [ undefined, 'forever@>= 0.8.5', [ 'forever@>= 0.8.5', null ] ]
verbose parsed url { pathname: 'forever@', path: 'forever@', href: 'forever@' }
silly cache add: name, spec, args [ 'forever', '>= 0.8.5', [ 'forever', '>= 0.8.5' ] ]
verbose parsed url { pathname: '=', path: '=', href: '=' }
verbose addNamed [ 'forever', '>= 0.8.5' ]
verbose addNamed [ null, '>=0.8.5' ]
silly name, range, hasData [ 'forever', '>=0.8.5', false ]
verbose already installed in /mnt/hgfs/workspace/MyApplicationFolder skipping express@2.5.2
verbose already installed in /mnt/hgfs/workspace/MyApplicationFolder skipping xml2js@>= 0.1.13
verbose already installed in /mnt/hgfs/workspace/MyApplicationFolder skipping request@>= 2.9.100
verbose already installed in /mnt/hgfs/workspace/MyApplicationFolder skipping mongoskin@>= 0.3.0
verbose already installed in /mnt/hgfs/workspace/MyApplicationFolder skipping eventemitter2@>= 0.4.3
verbose already installed in /mnt/hgfs/workspace/MyApplicationFolder skipping jsonrpc2@>= 0.1.0
verbose raw, before any munging forever
verbose url resolving [ 'https://registry.npmjs.org/', './forever' ]
verbose url resolved https://registry.npmjs.org/forever
http GET https://registry.npmjs.org/forever
http 200 https://registry.npmjs.org/forever
silly get cb [ 200,
silly get cb { vary: 'Accept',
silly get cb server: 'CouchDB/1.1.0 (Erlang OTP/R14B04)',
silly get cb etag: '"3BZ7B0TQMXMU9HP9UCZ3LJ8WB"',
silly get cb date: 'Fri, 02 Mar 2012 16:20:13 GMT',
silly get cb 'content-type': 'application/json',
silly get cb 'content-length': '46046' } ]
verbose mkdir (expected) error ENOENT, no such file or directory '/root/.npm/forever'
verbose mkdir done: /root/.npm/forever 755
silly name, range, hasData 2 [ 'forever', '>=0.8.5', true ]
silly versions [ 'forever',
silly versions [ '0.6.0',
silly versions '0.6.1',
silly versions '0.6.2',
silly versions '0.6.3',
silly versions '0.6.4',
silly versions '0.6.5',
silly versions '0.6.6',
silly versions '0.6.7',
silly versions '0.6.8',
silly versions '0.6.9',
silly versions '0.7.0',
silly versions '0.7.1',
silly versions '0.7.2',
silly versions '0.7.3',
silly versions '0.7.4',
silly versions '0.7.5',
silly versions '0.8.0',
silly versions '0.8.1',
silly versions '0.8.2',
silly versions '0.8.3',
silly versions '0.8.4',
silly versions '0.8.5' ] ]
verbose bin dist [ '0.6-ares1.7.5-DEV-evundefined-openssl0.9.8e-fips-rhel5-v83.6.6.14-linux-x64-2.6.18-274.7.1.el5',
verbose bin dist { shasum: '9f7dd2eb19111cf0e77136d5b04e80425f03d18a',
verbose bin dist tarball: 'http://registry.npmjs.org/forever/-/forever-0.8.5.tgz' } ]
verbose addRemoteTarball [ 'https://registry.npmjs.org/forever/-/forever-0.8.5.tgz',
verbose addRemoteTarball '9f7dd2eb19111cf0e77136d5b04e80425f03d18a' ]
verbose mkdir (expected) error ENOENT, no such file or directory '/tmp/npm-1330705214381'
verbose mkdir (expected) error ENOENT, no such file or directory '/tmp/npm-1330705214381/1330705214381-0.2000103467144072'
verbose mkdir done: /tmp/npm-1330705214381/1330705214381-0.2000103467144072 755
verbose fetch to /tmp/npm-1330705214381/1330705214381-0.2000103467144072/tmp.tgz
http GET https://registry.npmjs.org/forever/-/forever-0.8.5.tgz
http 200 https://registry.npmjs.org/forever/-/forever-0.8.5.tgz
silly updated sha bytes 40960
silly updated sha bytes 14262
info shasum 9f7dd2eb19111cf0e77136d5b04e80425f03d18a
info shasum /tmp/npm-1330705214381/1330705214381-0.2000103467144072/tmp.tgz
verbose mkdir (expected) error ENOENT, no such file or directory '/tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm'
verbose mkdir done: /tmp/npm-1330705214381/1330705214381-0.2000103467144072/__package.npm 755
verbose unpack uid, gid [ 0, 0 ]
verbose unpackTarget /tmp/npm-1330705214381/1330705214381-0.2000103467144072/package
silly gunzTarPerm modes [ '755', '644' ]
silly afterUntar undefined
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/CHANGELOG.md
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/README.md
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/LICENSE
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/.npmignore
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/package.json
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/bin
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/bin/foreverd
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/bin/forever
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/process-send.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/env-vars.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/env-server.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/list-multiple.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/spawn-and-error.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/error-on-timer.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/log-on-interval.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/all-env-vars.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/multiple-processes.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/always-throw.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/chroot.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/custom-cwd.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/cli-multiple-start
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/count-timer.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/server.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/signal-ignore.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/examples/initd-example
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/docs
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/docs/forever.html
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/docs/docco.css
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/docs/forever
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/docs/forever/monitor.html
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/docs/forever/cli.html
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/cli-test
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/plugins
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/plugins/logger-test.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/core
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/core/tail-stopall-test.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/core/check-process-test.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/worker
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/worker/multiple-workers-test.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/worker/simple-test.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/service
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/service/simple-test.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/monitor
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/monitor/fork-test.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/monitor/env-spawn-test.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/monitor/spin-test.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/monitor/watch-test.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/monitor/signal-test.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/monitor/simple-test.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/fixtures
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/fixtures/start-daemon.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/fixtures/watch
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/fixtures/watch/removeMe
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/fixtures/watch/.foreverignore
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/fixtures/watch/file
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/fixtures/watch/daemon.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/helpers
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/helpers/macros.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/helpers/mocks
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/helpers/mocks/stream.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/helpers/mocks/child-process.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/test/helpers/mocks/monitor.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/worker.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/monitor.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/cli.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/plugins
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/plugins/watch.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/plugins/logger.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/service
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/service/service.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/service/index.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/service/cli.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/service/adapters
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/service/adapters/adapter.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/service/adapters/initd
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/service/adapters/initd/index.js
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/service/adapters/systemv
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/service/adapters/systemv/foreverd
silly asyncMap in gTP /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package/lib/forever/service/adapters/systemv/index.js
verbose gunzed /tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package
verbose rm'ed /tmp/npm-1330705214381/1330705214381-0.2000103467144072/package
verbose renamed [ '/tmp/npm-1330705214381/1330705214381-0.2000103467144072/___package.npm/package',
verbose renamed '/tmp/npm-1330705214381/1330705214381-0.2000103467144072/package' ]
verbose caching /tmp/npm-1330705214381/1330705214381-0.2000103467144072/package/package.json
verbose loadDefaults forever@0.8.5
verbose tarball contents [ 'package', 'tmp.tgz' ]
verbose from cache /tmp/npm-1330705214381/1330705214381-0.2000103467144072/package/package.json
verbose pack /tmp/npm-1330705214381/1330705214381-0.2000103467144072/package
verbose pack /tmp/npm-1330705214381/1330705214381-0.2000103467144072/package /root/.npm/forever/0.8.5/package.tgz
silly makeList /tmp/npm-1330705214381/1330705214381-0.2000103467144072/package
silly dir, dirLen [ '/tmp/npm-1330705214381/1330705214381-0.2000103467144072/package',
silly dir, dirLen 64 ]
verbose tarball /root/.npm/forever/0.8.5/package.tgz
verbose parent /tmp/npm-1330705214381/1330705214381-0.2000103467144072/package
verbose mkdir (expected) error ENOENT, no such file or directory '/root/.npm/forever/0.8.5/___package.npm'
verbose mkdir done: /root/.npm/forever/0.8.5/__package.npm 755
verbose unpack uid, gid [ 0, 0 ]
verbose unpackTarget /root/.npm/forever/0.8.5/package
silly gunzTarPerm modes [ '755', '644' ]
silly afterUntar undefined
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/CHANGELOG.md
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/README.md
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/LICENSE
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/.npmignore
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/package.json
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/bin
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/bin/foreverd
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/bin/forever
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/process-send.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/env-vars.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/env-server.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/list-multiple.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/spawn-and-error.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/error-on-timer.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/log-on-interval.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/all-env-vars.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/multiple-processes.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/always-throw.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/chroot.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/custom-cwd.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/cli-multiple-start
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/count-timer.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/server.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/signal-ignore.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/examples/initd-example
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/docs
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/docs/forever.html
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/docs/docco.css
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/docs/forever
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/docs/forever/monitor.html
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/docs/forever/cli.html
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/cli-test
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/plugins
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/plugins/logger-test.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/core
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/core/tail-stopall-test.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/core/check-process-test.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/worker
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/worker/multiple-workers-test.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/worker/simple-test.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/service
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/service/simple-test.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/monitor
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/monitor/fork-test.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/monitor/env-spawn-test.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/monitor/spin-test.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/monitor/watch-test.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/monitor/signal-test.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/monitor/simple-test.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/fixtures
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/fixtures/start-daemon.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/fixtures/watch
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/fixtures/watch/removeMe
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/fixtures/watch/.foreverignore
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/fixtures/watch/file
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/fixtures/watch/daemon.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/helpers
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/helpers/macros.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/helpers/mocks
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/helpers/mocks/stream.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/helpers/mocks/child-process.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/test/helpers/mocks/monitor.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/worker.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/monitor.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/cli.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/plugins
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/plugins/watch.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/plugins/logger.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/service
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/service/service.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/service/index.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/service/cli.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/service/adapters
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/service/adapters/adapter.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/service/adapters/initd
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/service/adapters/initd/index.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/service/adapters/systemv
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/service/adapters/systemv/index.js
silly asyncMap in gTP /root/.npm/forever/0.8.5/___package.npm/package/lib/forever/service/adapters/systemv/foreverd
verbose gunzed /root/.npm/forever/0.8.5/___package.npm/package
verbose rm'ed /root/.npm/forever/0.8.5/package
verbose renamed [ '/root/.npm/forever/0.8.5/___package.npm/package',
verbose renamed '/root/.npm/forever/0.8.5/package' ]
verbose caching /root/.npm/forever/0.8.5/package/package.json
verbose loadDefaults forever@0.8.5
silly updated sha bytes 40960
silly updated sha bytes 13962
info shasum 5fdd754c17956cb6d687f645269bd9a5fc5940a8
info shasum /root/.npm/forever/0.8.5/package.tgz
verbose from cache /root/.npm/forever/0.8.5/package/package.json
verbose chmod /root/.npm/forever/0.8.5/package.tgz 644
verbose chown [ '/root/.npm/forever/0.8.5/package.tgz', 0, 0 ]
silly resolved [ { name: 'forever',
silly resolved preferGlobal: 'true',
silly resolved description: 'A simple CLI tool for ensuring that a given node script runs continuously (i.e. forever)',
silly resolved version: '0.8.5',
silly resolved author: { name: 'Nodejitsu Inc', email: 'info@nodejitsu.com' },
silly resolved contributors:
silly resolved [ { name: 'Charlie Robbins', email: 'charlie@nodejitsu.com' },
silly resolved { name: 'Fedor Indutny', email: 'fedor.indutny@gmail.com' },
silly resolved { name: 'James Halliday', email: 'mail@substack.net' },
silly resolved { name: 'Bradley Meck', email: 'bradley@nodejitsu.com' },
silly resolved { name: 'Dominic Tarr', email: 'dominic@nodejitsu.com' },
silly resolved { name: 'Maciej Małecki', email: 'maciej@nodejitsu.com' } ],
silly resolved repository: { type: 'git', url: 'git://github.com/nodejitsu/forever.git' },
silly resolved keywords: [ 'cli', 'fault tolerant', 'sysadmin', 'tools' ],
silly resolved dependencies:
silly resolved { broadway: '0.1.x',
silly resolved cliff: '0.x.x',
silly resolved daemon: '0.4.x',
silly resolved flatiron: '0.1.x',
silly resolved microtime: '0.2.x',
silly resolved minimatch: '0.0.x',
silly resolved nconf: '0.5.x',
silly resolved nssocket: '0.3.x',
silly resolved 'node-fork': '0.4.x',
silly resolved optimist: '0.2.x',
silly resolved pkginfo: '0.x.x',
silly resolved portfinder: '0.x.x',
silly resolved 'ps-tree': '0.0.x',
silly resolved timespan: '2.0.x',
silly resolved watch: '0.5.x',
silly resolved utile: '0.0.x',
silly resolved winston: '0.5.x' },
silly resolved devDependencies: { eventemitter2: '0.4.x', request: '2.x.x', vows: '0.5.x' },
silly resolved bin: { forever: './bin/forever', foreverd: './bin/foreverd' },
silly resolved main: './lib/forever',
silly resolved scripts: { test: 'vows test/**/*-test.js --spec -i' },
silly resolved engines: { node: '>= 0.4.8' },
silly resolved _id: 'forever@0.8.5',
silly resolved optionalDependencies: {},
silly resolved _engineSupported: true,
silly resolved _npmVersion: '1.1.0-2',
silly resolved _nodeVersion: 'v0.6.6',
silly resolved _defaultsLoaded: true,
silly resolved dist: { shasum: '5fdd754c17956cb6d687f645269bd9a5fc5940a8' } } ]
info into /mnt/hgfs/workspace/MyApplicationFolder forever@0.8.5
info installOne forever@0.8.5
info unbuild /mnt/hgfs/workspace/MyApplicationFolder/node_modules/forever
verbose from cache /root/.npm/forever/0.8.5/package/package.json
verbose mkdir (expected) error ENOENT, no such file or directory '/mnt/hgfs/workspace/MyApplicationFolder/node_modules/__forever.npm'
verbose unpack uid, gid [ 0, 0 ]
verbose unpackTarget /mnt/hgfs/workspace/MyApplicationFolder/node_modules/forever
ERR! Could not create /mnt/hgfs/workspace/MyApplicationFolder/node_modules/___forever.npm
ERR! error installing forever@0.8.5
info unbuild /mnt/hgfs/workspace/MyApplicationFolder/node_modules/forever
verbose installOne cb forever@0.8.5
ERR! Error: UNKNOWN, unknown error '/mnt/hgfs/workspace/MyApplicationFolder/node_modules/___forever.npm'
ERR! You may report this log at:
ERR! http://github.com/isaacs/npm/issues
ERR! or email it to:
ERR! npm-@googlegroups.com
ERR!
ERR! System Linux 2.6.18-274.7.1.el5
ERR! command "node" "/usr/local/bin/npm" "install"
ERR! cwd /mnt/hgfs/workspace/MyApplicationFolder
ERR! node -v v0.6.6
ERR! npm -v 1.1.0-2
ERR! path /mnt/hgfs/workspace/MyApplicationFolder/node_modules/___forever.npm
ERR! code UNKNOWN
ERR! message UNKNOWN, unknown error '/mnt/hgfs/workspace/MyApplicationFolder/node_modules/___forever.npm'
ERR! errno {}
verbose exit [ 1, true ]
I think that this was fixed sometime in the last few releases. Try upgrading to node 0.6.12 and npm 1.1.4
I have updated my NPM to version 1.1.4 and I have node.js version 0.6.6.
After update I have the same problem and I get the same error message.
|
gharchive/issue
| 2012-03-02T16:40:55 |
2025-04-01T04:34:36.938234
|
{
"authors": [
"egolovaniuc",
"isaacs"
],
"repo": "isaacs/npm",
"url": "https://github.com/isaacs/npm/issues/2221",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1988612200
|
🛑 Bo Truyol is down
In 3caa906, Bo Truyol (https://bo.truyol.com/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Bo Truyol is back up in 789bc30 after 53 minutes.
|
gharchive/issue
| 2023-11-11T00:45:56 |
2025-04-01T04:34:36.970863
|
{
"authors": [
"iscrdh"
],
"repo": "iscrdh/upptime",
"url": "https://github.com/iscrdh/upptime/issues/272",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2272829131
|
🛑 ALFANET.isolucion.co is down
In c8b50ab, ALFANET.isolucion.co (https://ALFANET.isolucion.co) was down:
HTTP code: 0
Response time: 0 ms
Resolved: ALFANET.isolucion.co is back up in dd6aea6 after 2 days, 12 hours, 56 minutes.
|
gharchive/issue
| 2024-05-01T02:49:02 |
2025-04-01T04:34:37.035122
|
{
"authors": [
"isolucionco"
],
"repo": "isolucionco/EstadoIsolucionHosting",
"url": "https://github.com/isolucionco/EstadoIsolucionHosting/issues/2705",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1807291341
|
Configurability for Site or Tenant
We need a configuration for the OpenAI key per site or tenant for the case that somebody wants to use it seriously. The common key is for trying it out, but shouldn't be used for all time.
While we'r at site specific configurations: It's sensible to add a possibility to configure additional prompts, which could be put there as well.
Open points: the OpenAI key is a secret - how to make sure not every editor can see it?
This is essentially implemented with https://github.com/ist-dresden/composum-AI/pull/36 using Sling Context Aware Configuration with configuration com.composum.ai.backend.slingbase.model.OpenAIConfig "Composum AI OpenAI Configuration" .
|
gharchive/issue
| 2023-07-17T08:49:02 |
2025-04-01T04:34:37.059859
|
{
"authors": [
"stoerr"
],
"repo": "ist-dresden/composum-AI",
"url": "https://github.com/ist-dresden/composum-AI/issues/14",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
254474006
|
Configuration option to include function headers as part of coverage (as Istanbul does)
Below is a screenshot showing a difference between lcov reports from istanbul and nyc. I am trying to migrate from istanbul but in order to safely do so I would preferably like to see same coverage numbers.
My request is about ability to reproduce istanbul behavior in nyc.
Note, I am not the only one suffering from this issue as proven by this problem reported to Codecov https://github.com/codecov/support/issues/391
Many thanks for the great tool which is nyc!
@Rush this would appear to relate to some technical differences in how the instrumenter (or potentially the reporter) opts to instrument functions in Istanbul 2.0 vs. Istanbul 1.0. You can find the instrumenter codebase here:
https://github.com/istanbuljs/istanbuljs/tree/master/packages/istanbul-lib-instrument
I note that it does highlight the line if the function is assigned:
const a = function foo () {
console.log('hello')
}
would love help digging into this further, feel free to join the slack community I've setup if you feel like helping address this issue:
http://devtoolscommunity.herokuapp.com/
https://codecov.io/gh/AirDwing/node-dwing-redis/commit/9e45f7c035ff790c92f8192296a3bd0bd4085a48
Woops!
There was an error processing coverage reports.
Most common issues
coverage.lcov:
TN:
SF:/Users/willin/Documents/dwing/lib/node-dwing-redis/src/index.js
FN:16,createRedisClient
FN:18,(anonymous_1)
FN:33,(anonymous_2)
FN:34,(anonymous_3)
FNF:4
FNH:4
FNDA:7,createRedisClient
FNDA:8,(anonymous_1)
FNDA:1424,(anonymous_2)
FNDA:3,(anonymous_3)
DA:1,3
DA:2,3
DA:3,3
DA:4,3
DA:7,3
DA:9,3
DA:16,3
DA:17,7
DA:18,7
DA:19,8
DA:20,4
DA:22,8
DA:23,5
DA:24,5
DA:31,8
DA:32,8
DA:33,8
DA:34,1424
DA:36,3
DA:43,3
DA:44,3
DA:47,8
DA:49,7
LF:23
LH:23
BRDA:16,0,0,6
BRDA:16,1,0,6
BRDA:19,2,0,4
BRDA:19,2,1,4
BRDA:22,3,0,5
BRDA:22,3,1,3
BRDA:24,4,0,5
BRDA:24,4,1,3
BRDA:36,5,0,3
BRDA:49,6,0,7
BRDA:49,6,1,6
BRF:11
BRH:11
end_of_record
@willin are you seeing the same behavior reported in this pull request (function names not highlighted as instrumented?)
|
gharchive/issue
| 2017-08-31T21:31:03 |
2025-04-01T04:34:37.069215
|
{
"authors": [
"Rush",
"bcoe",
"willin"
],
"repo": "istanbuljs/nyc",
"url": "https://github.com/istanbuljs/nyc/issues/658",
"license": "isc",
"license_type": "permissive",
"license_source": "bigquery"
}
|
239895217
|
Get Markers nearest a location (or current location)?
Hi Ivan
I know that you implement markers in a different way, since you allow them to be any React components. I'm wondering if there is a way that I can say "give me the N markers closest to me"?
thanks
Artyom
Dear users,
before you will write anything, please use search,
then please search again.
Most of problems you have is just an one line solution -
there is no need to change this library,
just add anything you want in your code.
Please look at examples, docs, apis - all of this were created for you not for me ;-).
You can find every algorithm for geo data here https://github.com/mourner or at mapbox github
For your case see this https://github.com/mourner/rbush-knn
Or if you have just few thousands markers you can just sort them by distance and take first N, it will be really fast. Or you can find Nth min by distance element and filter out all with less distance (have complexity O(n) but harder to implement vs sort solution with complexity O(n*log(n)))
Ah, thanks. I meant more on a per call basis... If you have 100 locations in a city, and a user w a phone says, "get me the three closest locations please..."
@artemis-prime Let me know if you found an easy solution!
|
gharchive/issue
| 2017-06-30T21:41:11 |
2025-04-01T04:34:37.073009
|
{
"authors": [
"effortlesseffort",
"istarkov",
"itsmichaeldiego"
],
"repo": "istarkov/google-map-react",
"url": "https://github.com/istarkov/google-map-react/issues/405",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
127086453
|
Missing css in one of the examples
http://istarkov.github.io/google-map-react/map/events/
I am trying to do the same thing, but the "click" text already shown on the screen, could you also list out the css animation code? Thanks.
Examples on site are builded from the sources, so all code you need is there
ya, thanks.
|
gharchive/issue
| 2016-01-17T10:21:19 |
2025-04-01T04:34:37.074547
|
{
"authors": [
"ansonla3",
"istarkov"
],
"repo": "istarkov/google-map-react",
"url": "https://github.com/istarkov/google-map-react/issues/94",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
504919758
|
Use dev build instead of daily builds
Daily builds are no longer published
Also we don't have gencheck on this repo so some random changes are
included that are generated.
@howardjohn: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
noauth_installer
e69f1a46595366206f81b45f96aa95cda0b15402
link
/test noauth_installer
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.
/retest
|
gharchive/pull-request
| 2019-10-09T22:03:08 |
2025-04-01T04:34:37.078464
|
{
"authors": [
"howardjohn",
"istio-testing"
],
"repo": "istio/installer",
"url": "https://github.com/istio/installer/pull/430",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
261109477
|
use istio-system as default namespace
as istio.yaml indicated for mixer deployment config.
Jenkins job istio.github.io/presubmit passed
@douglas-reid I remember you objecting to this change in istio/istio when @andraxylia made a similar change. I haven't kept up. So please comment/approve.
Jenkins job istio.github.io/presubmit passed
|
gharchive/pull-request
| 2017-09-27T20:35:31 |
2025-04-01T04:34:37.080602
|
{
"authors": [
"istio-testing",
"linsun",
"rshriram"
],
"repo": "istio/istio.github.io",
"url": "https://github.com/istio/istio.github.io/pull/551",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
493269545
|
Automatically manage ports on ingress LoadBalancer services on behalf of Gateway resources
Describe the feature request
At present, ports on ingress gateway LoadBalancer services are typically specified via Helm chart values files. Adding a new port to a Gateway resource does not dynamically add that port to the spec of the LoadBalancer service associated with the gateway workload instances.
As an Istio user, I would like Istio to have the option to dynamically manage ports in the specification of the LoadBalancer services associated with the workload instances which host my ingress gateways. When I create a Gateway resource with a new port, or add a new port to an existing Gateway resource, if that port is not already exposed on the LoadBalancer service, Istio should add it.
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[X] Configuration Infrastructure
[X] Docs
[X] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[X] Security
[ ] Test and Release
[X] User Experience
[ ] Developer Infrastructure
Additional context
This pretty strongly violates namespace boundaries unless we force Gateway to be in the same namespace as the deployment, since otherwise someone in another namespace (eg does not have permission to istio-system) can arbitrarily modify the gateway deployment
|
gharchive/issue
| 2019-09-13T11:14:10 |
2025-04-01T04:34:37.192171
|
{
"authors": [
"howardjohn",
"nickperry"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/17076",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
504399340
|
New test, TestAuthenticationZ, flaky
Example failure: https://prow.k8s.io/view/gcs/istio-prow/logs/unit-tests_istio_postsubmit/270
There are others too that I have seen.
Please revert the test or fix ASAP
The test seems behave well in the last 24 hours. It's unclear what the cause of flakiness. PR #17719 change the implementation and the test align with the config_dump, so it may help. Will keep an eye on this for another day or two.
https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/17986/unit-tests_istio/2584 is another one
Thanks. From the log, looks like ADS is not ready when we make the request.
The simplest fix would be sleep for few sec.
debug_test.go:384: /authenticationz returns with error code 404:
ADS for "dumpApp-644fc65469-96dza.testns" does not exist. Only have:
On Thu, Oct 17, 2019 at 1:15 PM John Howard notifications@github.com
wrote:
https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/17986/unit-tests_istio/2584
is another one
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/17717?email_source=notifications&email_token=AF7X24LS7QWJYNGJ67EKRGTQPDBXVA5CNFSM4I6Z4PIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBRMFFY#issuecomment-543343255,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF7X24LNYQ2C3COULSRVAG3QPDBXVANCNFSM4I6Z4PIA
.
--
Diem Vu | Software Engineer | diemvu@google.com | +1 408-215-8127
I would rather retry than sleep, otherwise tests take too long and may
still be flaky
On Thu, Oct 17, 2019 at 1:23 PM Diem Vu notifications@github.com wrote:
Thanks. From the log, looks like ADS is not ready when we make the request.
The simplest fix would be sleep for few sec.
debug_test.go:384: /authenticationz returns with error code 404:
ADS for "dumpApp-644fc65469-96dza.testns" does not exist. Only have:
On Thu, Oct 17, 2019 at 1:15 PM John Howard notifications@github.com
wrote:
https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/17986/unit-tests_istio/2584
is another one
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<
https://github.com/istio/istio/issues/17717?email_source=notifications&email_token=AF7X24LS7QWJYNGJ67EKRGTQPDBXVA5CNFSM4I6Z4PIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBRMFFY#issuecomment-543343255
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AF7X24LNYQ2C3COULSRVAG3QPDBXVANCNFSM4I6Z4PIA
.
--
Diem Vu | Software Engineer | diemvu@google.com | +1 408-215-8127
<(408)%20215-8127>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/17717?email_source=notifications&email_token=AAEYGXOUHWMA7AHT2NQLBDTQPDCUNA5CNFSM4I6Z4PIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBRM3WI#issuecomment-543346137,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXLID2RJPYK6BMOGJNTQPDCUNANCNFSM4I6Z4PIA
.
the above PRs seemed to fix
|
gharchive/issue
| 2019-10-09T04:04:46 |
2025-04-01T04:34:37.204536
|
{
"authors": [
"diemtvu",
"howardjohn"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/17717",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
566800288
|
Ingress ISTIO virtualhost based routing doesn't work
Bug description
[x ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
ISTIO ingress virtual host based routing doesn't work
Steps to reproduce:
Deploy simple echo service apple.yaml
kind: Pod
apiVersion: v1
metadata:
name: apple-app
labels:
app: apple
spec:
containers:
- name: apple-app
image: hashicorp/http-echo
args:
- "-text=apple"
kind: Service
apiVersion: v1
metadata:
name: apple-service
spec:
selector:
app: apple
ports:
- port: 5678 # Default port for image
Create http gateway:
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: http-gateway
spec:
selector:
istio: ingressgateway
servers:
port:
number: 80
name: http
protocol: HTTP
hosts:
- "*"
Create host based routing apple_virtual_svc.yaml
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: "apple-service"
spec:
hosts:
"apple.example.domain.org"
gateways:
http-gateway
http:
route:
destination:
host: "apple-service"
port:
number: 5678
When I tried get host apple.example.domain.org istio ingress returns 404 error code:
--2020-02-18 11:24:16-- http://apple.example.domain.org:32324/
Resolving apple.example.domain.org (apple.example.domain.org)... 10.10.136.33
Connecting to apple.example.domain.org (apple.example.domain.org|10.10.136.33|:32324... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-02-18 11:24:16 ERROR 404: Not Found.
When I reconfigure virtual service for use prefix based routing with following config:
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: "apple-service"
spec:
hosts:
"*"
gateways:
http-gateway
http:
match:
uri:
prefix: /apple
route:
destination:
host: "apple-service"
port:
number: 5678
Everything work as expected
**Version
istioctl version --remote
client version: 1.4.2
control plane version: 1.4.2
data plane version: 1.4.2 (5 proxies)
kubectl version
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:26:52Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
helm version
Client: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}
How was Istio installed?
Using standard recommended way install:
istioctl verify-install --kubeconfig ~/.kube/config.my
istioctl manifest apply --set profile=demo --kubeconfig ~/.kube/config.my
Environment where bug was observed (cloud vendor, OS, etc)
Ubuntu 18.04
bug_demo_config.zip
I tried this locally and could not reproduce. I suggest running istioctl analyze, checking https://istio.io/latest/docs/tasks/traffic-management/ingress/, upgrading Istio, and if none of those resolve this posting a config dump from ingress: https://github.com/istio/istio/wiki/Troubleshooting-Istio
I was unable to reproduce and there isn't enough information here to move forward. If you still see issues feel free to reopen. Thanks!
|
gharchive/issue
| 2020-02-18T10:37:53 |
2025-04-01T04:34:37.224491
|
{
"authors": [
"howardjohn",
"luccks"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/21208",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
925444632
|
Websocket over http2 does not work on version 10.1
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Bug description
Envoy does not forward websocket upgrade request to the application. It instead just returns an 400 http error. Non-websocket requests work fine. I have added envoy debug logs.
This is how the request looks like:
gateway-dark-5b7488dd7b-zjwrl istio-proxy ':method', 'GET'
gateway-dark-5b7488dd7b-zjwrl istio-proxy ':authority', 'gully.to'
gateway-dark-5b7488dd7b-zjwrl istio-proxy ':scheme', 'https'
gateway-dark-5b7488dd7b-zjwrl istio-proxy ':path', '/graphql'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'pragma', 'no-cache'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'cache-control', 'no-cache'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'user-agent', 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.106 Safari/537.36'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'origin', 'https://gully.to'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'sec-websocket-version', '13'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'accept-encoding', 'gzip, deflate, br'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'accept-language', 'en-US,en;q=0.9,fr;q=0.8,la;q=0.7'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-prop-gateway-dark', 'true'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'sec-websocket-extensions', 'permessage-deflate; client_max_window_bits'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'sec-websocket-protocol', 'graphql-transport-ws'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-forwarded-for', '74.72.131.115'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-forwarded-proto', 'https'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-envoy-external-address', '74.72.131.115'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-request-id', '180d4217-54d6-4dfe-9b68-02e4fb49f8b9'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-envoy-attempt-count', '1'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-envoy-original-path', '/api/graphql'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'cookie', '<REDACTED>'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'upgrade', 'websocket'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'connection', 'upgrade'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'content-length', '0'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-forwarded-client-cert', <REDACTED>
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-b3-traceid', 'e6dd4b7ccb0099750e0db59a1aa2db7f'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-b3-spanid', 'b02ff16f82baa22e'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-b3-parentspanid', '0e0db59a1aa2db7f'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-b3-sampled', '0'
The request does not get to the main application. This is the response log from envoy.
gateway-dark-5b7488dd7b-zjwrl istio-proxy
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.661587Z debug envoy pool queueing stream due to no available connections
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.661591Z debug envoy pool trying to create new connection
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.661596Z debug envoy pool creating a new connection
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.661663Z debug envoy client [C353] connecting
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.661668Z debug envoy connection [C353] connecting to 10.96.0.24:3000
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.661748Z debug envoy connection [C353] connection in progress
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.661792Z debug envoy connection [C353] connected
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.661797Z debug envoy client [C353] connected
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.661804Z debug envoy pool [C353] attaching to next stream
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.661808Z debug envoy pool [C353] creating stream
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.661817Z debug envoy router [C51][S4812833863188107822] pool ready
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.663017Z debug envoy router [C51][S4812833863188107822] upstream headers complete: end_stream=false
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.663125Z debug envoy http [C51][S4812833863188107822] encoding headers via codec (end_stream=false):
gateway-dark-5b7488dd7b-zjwrl istio-proxy ':status', '400'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'content-type', 'text/html'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'content-length', '11'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-envoy-peer-metadata', '<REDACTED>'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'x-envoy-peer-metadata-id', 'sidecar~10.96.0.24~gateway-dark-5b7488dd7b-zjwrl.production~production.svc.cluster.local'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'date', 'Sat, 19 Jun 2021 17:33:12 GMT'
gateway-dark-5b7488dd7b-zjwrl istio-proxy 'server', 'istio-envoy'
gateway-dark-5b7488dd7b-zjwrl istio-proxy
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.663215Z debug envoy client [C353] response complete
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.663232Z debug envoy router [C51][S4812833863188107822] resetting pool request
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.663247Z debug envoy http [C51][S4812833863188107822] doEndStream() resetting stream
gateway-dark-5b7488dd7b-zjwrl istio-proxy 2021-06-19T17:33:12.663260Z debug envoy http [C51][S4812833863188107822] stream reset
Service for the application looks like this:
apiVersion: v1
kind: Service
metadata:
name: gateway
namespace: {{ $.Release.Namespace }}
labels:
{{- include "production.labels" . | nindent 4 }}
spec:
selector:
app: gateway
ports:
- port: 80
targetPort: 3000
name: http-app
protocol: TCP
Also, I have enabled http2 for envoy to allow for connection upgrades.
"http2ProtocolOptions": {
"allowConnect": true
},
"upgradeConfigs": [
{
"upgradeType": "websocket"
}
],
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
client version: 1.10.1
control plane version: 1.10.1
data plane version: 1.10.1 (23 proxies)
kubectl version --short
Client Version: v1.19.11
Server Version: v1.19.9-gke.1900
How was Istio installed?
istioctl
Environment where the bug was observed (cloud vendor, OS, etc)
GKE
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.
Quick brain dump: from the HTTP spec we see:
presence of a message-body in a request is signaled by the inclusion of a Content-Length or Transfer-Encoding header field in the request's message-headers
And from the Envoy docs on proxying websockets over HTTP2:
the HTTP/2+ upgrade path has very strict HTTP/1.1 compliance, so will not proxy WebSocket upgrade requests or responses with bodies
From request-side Envoy logs we see gateway-dark-5b7488dd7b-zjwrl istio-proxy 'content-length', '0' so could be inclusion of that header throwing things off? I'm a bit confused since I thought we removed the header in 1.10 but we we can see it there in the logs
@skk2142 how are you going about "enabling http2 for envoy to allow for connection upgrades"? With meshConfig.h2UpgradePolicy=UPGRADE?
From local testing I found that websockets didn't work with that h2UpgradePolicy=UPGRADE enabled and that adding AllowConnect: true to the inbound listener here seemed to fix things
I using the http2 upgrade in the destination rule for individual services in the mesh (including the gateway service which receives websocket connection.
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
name: gateway
namespace: {{ $.Release.Namespace }}
labels:
{{- include "production.labels" . | nindent 4 }}
spec:
host: gateway.{{ $.Release.Namespace }}.svc.cluster.local
trafficPolicy:
connectionPool:
http:
h2UpgradePolicy: "UPGRADE"
subsets:
Also, I'm using an envoy filter for allow_connect
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
name: envoy-http2-websocket-and-request-id-response
namespace: istio-system
labels: {{- include "production.labels" . | nindent 4 }}
spec:
configPatches:
- applyTo: NETWORK_FILTER
match:
context: GATEWAY
listener:
filterChain:
filter:
name: "envoy.filters.network.http_connection_manager"
patch:
operation: MERGE
value:
typed_config:
"@type": "type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager"
always_set_request_id_in_response: true
- applyTo: NETWORK_FILTER
match:
listener:
filterChain:
filter:
name: "envoy.filters.network.http_connection_manager"
patch:
operation: MERGE
value:
typed_config:
"@type": "type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager"
http2_protocol_options:
# for websocket
allow_connect: true
Hi Just wanted to check if there are any updates on this. I tried to solve this problem by adding a new gateway-subscription service without the sidecar. I route any request at the istio-gateway with connection: upgrade header to the gateway-subscription service. It still has the same problem, the connection is getting terminated with 400 at the istio-gateway. I tried explicitly removing content-length header but that did not make any difference.
Another update, I noticed that websocket connection does work in safari. It does not work in chrome or firefox. Does it have to do with the TLS version of websocket supported in these browsers? The only difference I noticed in the connection request is that Safari does not send Upgrade: websocket header.
any updates on this? @skk2142 do you have work around for this?
any update on this?
|
gharchive/issue
| 2021-06-19T18:24:38 |
2025-04-01T04:34:37.238073
|
{
"authors": [
"Monkeyanator",
"krasimirdermendzhiev",
"metaphor",
"skk2142"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/33534",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1154457317
|
TestFileSecrets test flake
https://prow.istio.io/view/gs/istio-prow/logs/unit-tests_istio_postsubmit/1498362808511762432
@ramaraochavali this is a real bug, can you take a look? The problem is we have two different methods of handling add and remove. In tests we do "add; Remove; add". Its not always processed in order
Sure
@howardjohn TBH, I did not fully understand the problem but thought you were referring to what I did in https://github.com/istio/istio/pull/37656 . Can u please explain more, if that is not the case?
@howardjohn Can you please expand more on the issue ^^ - was my understanding correct that it is a test bug?
I think it's a real bug. the problem is we may do an add+remove+add of a file. This is perfectly valid and has a defined ordering (ie we did these actions in sequence in single thread).The result should be we are watching the cert
But then in the agent we are handling adds and removes in seperately in different threads. So it turns out we may process them in order "add, add, remove". This ends up NOT watching the cert
I see. Now I get it. Let me try to fix it.
|
gharchive/issue
| 2022-02-28T19:18:51 |
2025-04-01T04:34:37.241903
|
{
"authors": [
"howardjohn",
"ramaraochavali"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/37592",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2629548606
|
enablePrometheusMerge not merging app metrics
Is this the right place to submit this?
[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio
Bug Description
Istio 1.23.3 deployed through helm chart with enablePrometheusMerge: true in meshConfig.
I am unable to scrape my application metrics on the :15020/stats/prometheus (only istio metrics are available).
I see my application metrics fine on the original port :9545/metrics.
Istiod is logging that enablePrometheusMerge is set to true, but I see no details about scraping or merging in istio-proxy logs.
I'm not too sure how to debug this further.
Original pod annotations:
prometheus.io/path: /metrics
prometheus.io/port: 9545
prometheus.io/scheme: http
prometheus.io/scrape: true
Istio enabled pod annotations:
prometheus.io/path: /stats/prometheus
prometheus.io/port: 15020
prometheus.io/scrape: true
Version
$ istioctl version
client version: 1.23.2
control plane version: 1.23.3
data plane version: 1.23.1 (31 proxies), 1.23.3 (2 proxies)
$ kubectl version
Client Version: v1.30.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.5-gke.1014003
Additional Information
No response
pilot-agent will handle this, can you find merged metrics on 15020?
no I cannot. I only see my app metrics on the original port, and on 15020 I only see istio related metrics.
any error logs like failed scraping application metrics?
info mesh configuration updated to: {
(...)
"enablePrometheusMerge": true,
This is all I see on the istiod pods in istio-system namespace. In istio-proxy sidecar logs, I see no mention of merging or scraping .
so that worked as expected?
is count(15020)=count(15090)+count(95450)?
not at all. istio is about 1400 metrics on its own.
curl http://172.16.24.84:15020/stats/prometheus|grep besu_|wc -l
0
curl http://172.16.24.84:9545/metrics|grep besu_|wc -l
782
|
gharchive/issue
| 2024-11-01T17:40:16 |
2025-04-01T04:34:37.248088
|
{
"authors": [
"lesaux",
"zirain"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/issues/53753",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
422593335
|
Locality label istio-locality in k8s should not contain /, use . …
…instead
fixes: #12582
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hzxuzhonghu
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
pilot/OWNERS [hzxuzhonghu]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@hzxuzhonghu: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-integ-k8s-tests.sh
654122619e636c70cceb879640f64b95224a8765
link
/test istio-integ-k8s-tests
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.
@hzxuzhonghu: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-integ-k8s-tests.sh
654122619e636c70cceb879640f64b95224a8765
link
/test istio-integ-k8s-tests
prow/istio-pilot-multicluster-e2e.sh
654122619e636c70cceb879640f64b95224a8765
link
/test istio-pilot-multicluster-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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: howardjohn, hzxuzhonghu
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
pilot/OWNERS [hzxuzhonghu]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@hzxuzhonghu: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-pilot-multicluster-e2e.sh
654122619e636c70cceb879640f64b95224a8765
link
/test istio-pilot-multicluster-e2e
prow/istio-integ-k8s-tests.sh
22109884ccc26b76f55c29a31fa5aa77a65fb8ac
link
/test istio-integ-k8s-tests
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.
@hzxuzhonghu: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-integ-k8s-tests.sh
22109884ccc26b76f55c29a31fa5aa77a65fb8ac
link
/test istio-integ-k8s-tests
prow/istio-pilot-multicluster-e2e.sh
22109884ccc26b76f55c29a31fa5aa77a65fb8ac
link
/test istio-pilot-multicluster-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.
@duderino Please help merge
|
gharchive/pull-request
| 2019-03-19T08:08:42 |
2025-04-01T04:34:37.268889
|
{
"authors": [
"hzxuzhonghu",
"istio-testing"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/12592",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
479212256
|
Don't limit parallelism on unit-tests
Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
@howardjohn: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
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.
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
istio-unit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-unit-tests-master
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.
/retest
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
istio-unit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-unit-tests-master
istio-racetest-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-racetest-master
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.
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
istio-unit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-unit-tests-master
istio-racetest-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-racetest-master
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
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.
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
istio-unit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-unit-tests-master
istio-racetest-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-racetest-master
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
integ-mixer-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-mixer-k8s-presubmit-tests-master
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.
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
istio-racetest-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-racetest-master
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
integ-mixer-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-mixer-k8s-presubmit-tests-master
istio-unit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-unit-tests-master
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.
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
istio-racetest-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-racetest-master
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
integ-mixer-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-mixer-k8s-presubmit-tests-master
istio-unit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-unit-tests-master
istio-codecov-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-codecov-master
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.
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
istio-racetest-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-racetest-master
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
integ-mixer-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-mixer-k8s-presubmit-tests-master
istio-unit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-unit-tests-master
istio-codecov-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-codecov-master
istio-pilot-multicluster-e2e-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-pilot-multicluster-e2e-master
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.
/retest
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
istio-racetest-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-racetest-master
integ-mixer-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-mixer-k8s-presubmit-tests-master
istio-unit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-unit-tests-master
istio-codecov-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-codecov-master
istio-pilot-multicluster-e2e-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-pilot-multicluster-e2e-master
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
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.
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
integ-mixer-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-mixer-k8s-presubmit-tests-master
istio-codecov-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-codecov-master
istio-pilot-multicluster-e2e-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-pilot-multicluster-e2e-master
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
istio-racetest-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-racetest-master
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.
/retest
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
istio-pilot-multicluster-e2e-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-pilot-multicluster-e2e-master
istio-racetest-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-racetest-master
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
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.
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
istio-pilot-multicluster-e2e-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-pilot-multicluster-e2e-master
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
istio-racetest-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-racetest-master
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.
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
integ-new-install-k8s-presubmit-tests-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test integ-new-install-k8s-presubmit-tests-master
istio-racetest-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-racetest-master
istio-pilot-multicluster-e2e-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-pilot-multicluster-e2e-master
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.
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
istio-racetest-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-racetest-master
istio-pilot-multicluster-e2e-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-pilot-multicluster-e2e-master
integ-new-install-k8s-presubmit-tests-master
0097372cdf5df9d16d10da912835e8c931f72c93
link
/test integ-new-install-k8s-presubmit-tests-master
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.
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
istio-pilot-multicluster-e2e-master
45565019becba9d7c078ac2b728ae63cbcff1b71
link
/test istio-pilot-multicluster-e2e-master
integ-new-install-k8s-presubmit-tests-master
0097372cdf5df9d16d10da912835e8c931f72c93
link
/test integ-new-install-k8s-presubmit-tests-master
integ-mixer-k8s-presubmit-tests-master
0097372cdf5df9d16d10da912835e8c931f72c93
link
/test integ-mixer-k8s-presubmit-tests-master
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-racetest-master
Racetest now passes in 13min vs 28min
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
integ-new-install-k8s-presubmit-tests-master
0097372cdf5df9d16d10da912835e8c931f72c93
link
/test integ-new-install-k8s-presubmit-tests-master
integ-mixer-k8s-presubmit-tests-master
0097372cdf5df9d16d10da912835e8c931f72c93
link
/test integ-mixer-k8s-presubmit-tests-master
integ-security-k8s-presubmit-tests-master
0097372cdf5df9d16d10da912835e8c931f72c93
link
/test integ-security-k8s-presubmit-tests-master
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.
/retest
@howardjohn: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
integ-mixer-k8s-presubmit-tests-master
0097372cdf5df9d16d10da912835e8c931f72c93
link
/test integ-mixer-k8s-presubmit-tests-master
integ-security-k8s-presubmit-tests-master
0097372cdf5df9d16d10da912835e8c931f72c93
link
/test integ-security-k8s-presubmit-tests-master
integ-new-install-k8s-presubmit-tests-master
0097372cdf5df9d16d10da912835e8c931f72c93
link
/test integ-new-install-k8s-presubmit-tests-master
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.
|
gharchive/pull-request
| 2019-08-10T01:05:27 |
2025-04-01T04:34:37.391514
|
{
"authors": [
"howardjohn",
"istio-testing"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/16179",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
824148421
|
move functions to cluster builder
Moves functions to cluster builder so that http2protocol options deprecation can be done.
Pre cursor to https://github.com/istio/istio/pull/31273
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[X] Does not have any changes that may affect Istio users.
@hzxuzhonghu PTAL
@ramaraochavali: The following test failed, say /retest to rerun all failed tests:
Test name
Commit
Details
Rerun command
release-notes_istio
ce9066f9b720242f9ebb7737848479dda6ad5087
link
/test release-notes_istio
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 release-notes_istio
|
gharchive/pull-request
| 2021-03-08T04:19:18 |
2025-04-01T04:34:37.398152
|
{
"authors": [
"istio-testing",
"ramaraochavali"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/31307",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
838082724
|
Bump jinja2 version
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.
Is this because a bot suggested it and that bot can't sign the CLA?
A bot suggested it in private since its a security update - but not one that tangibly impacts istio
and in public too: https://github.com/istio/istio/pull/31591
Oops, didn't see that. It has the CLA signed so that one should work too
@howardjohn: The following test failed, say /retest to rerun all failed tests:
Test name
Commit
Details
Rerun command
integ-telemetry-mc-k8s-tests_istio
49574a953fc46d6bf2c22063eba66402ca40b38e
link
/test integ-telemetry-mc-k8s-tests_istio
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.
@howardjohn: The following tests failed, say /retest to rerun all failed tests:
Test name
Commit
Details
Rerun command
integ-telemetry-mc-k8s-tests_istio
49574a953fc46d6bf2c22063eba66402ca40b38e
link
/test integ-telemetry-mc-k8s-tests_istio
integ-telemetry-k8s-tests_istio
49574a953fc46d6bf2c22063eba66402ca40b38e
link
/test integ-telemetry-k8s-tests_istio
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.
/retest
|
gharchive/pull-request
| 2021-03-22T20:27:50 |
2025-04-01T04:34:37.425114
|
{
"authors": [
"craigbox",
"howardjohn",
"istio-testing"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/31628",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1137958499
|
[WIP] [TF] Install Istio with istioctl library
This avoids race conditions associated with using global variables in istioctl.
Please provide a description of this PR:
@nmittler: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-cni_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-cni_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-cni_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-cni_istio
integ-ipv6_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-ipv6_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-cni_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-cni_istio
integ-ipv6_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-ipv6_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-cni_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-cni_istio
integ-ipv6_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-ipv6_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-cni_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-cni_istio
integ-ipv6_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-ipv6_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-istiodremote_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-cni_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-cni_istio
integ-ipv6_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-ipv6_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-cni_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-cni_istio
integ-ipv6_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-ipv6_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-cni_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-cni_istio
integ-ipv6_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-ipv6_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-cni_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-cni_istio
integ-ipv6_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-ipv6_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test gencheck_istio
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-cni_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-cni_istio
integ-ipv6_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-ipv6_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-security_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
lint_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test lint_istio
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-cni_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-cni_istio
integ-ipv6_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-ipv6_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-security_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-cni_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-cni_istio
integ-ipv6_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-ipv6_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-security_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-ipv6_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-ipv6_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-security_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-telemetry_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry_istio
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-security_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-istiodremote_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-security_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
integ-security_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-security_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-pilot-istiodremote_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-telemetry-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-telemetry-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-pilot_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot-istiodremote-mc_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-istiodremote-mc_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-pilot_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-operator-controller_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-operator-controller_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-pilot_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
integ-pilot-multicluster_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-pilot-multicluster_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-pilot_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-pilot_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
integ-pilot-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-multicluster_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-distroless_istio
614156a4ae4fb516b4c3c5b05906755eff250327
link
true
/test integ-distroless_istio
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-pilot_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
integ-pilot-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-multicluster_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
lint_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test lint_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-pilot_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
integ-pilot-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-multicluster_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
integ-distroless_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-distroless_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
gencheck_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test gencheck_istio
integ-cni_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-cni_istio
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-pilot_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
integ-pilot-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-multicluster_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
integ-distroless_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-distroless_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-pilot_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
integ-pilot-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-multicluster_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
integ-distroless_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-distroless_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-telemetry-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
integ-pilot-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-multicluster_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
integ-distroless_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-distroless_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
integ-pilot_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-security_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
integ-pilot-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-multicluster_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
integ-distroless_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-distroless_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
integ-pilot_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-istiodremote_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-telemetry_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
integ-pilot-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-multicluster_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
integ-distroless_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-distroless_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
integ-pilot_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
integ-pilot-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-multicluster_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
integ-distroless_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-distroless_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
integ-pilot_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security_istio
integ-telemetry_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-ipv6_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-ipv6_istio
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
integ-distroless_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-distroless_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
integ-pilot_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security_istio
integ-telemetry_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry_istio
integ-pilot-multicluster_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-multicluster_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-telemetry-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-telemetry-mc_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
integ-distroless_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-distroless_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
integ-pilot_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security_istio
integ-telemetry_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry_istio
integ-pilot-multicluster_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-multicluster_istio
integ-ipv6_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-ipv6_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-security-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
integ-distroless_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-distroless_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
integ-pilot_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security_istio
integ-telemetry_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry_istio
integ-pilot-multicluster_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-multicluster_istio
integ-ipv6_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-ipv6_istio
integ-telemetry-mc_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-mc_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-pilot-istiodremote-mc_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote-mc_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
integ-distroless_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-distroless_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
integ-pilot_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security_istio
integ-telemetry_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry_istio
integ-pilot-multicluster_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-multicluster_istio
integ-ipv6_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-ipv6_istio
integ-telemetry-mc_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-mc_istio
integ-security-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security-istiodremote_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
integ-distroless_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-distroless_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
integ-pilot_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security_istio
integ-telemetry_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry_istio
integ-pilot-multicluster_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-multicluster_istio
integ-ipv6_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-ipv6_istio
integ-telemetry-mc_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-mc_istio
integ-security-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote-mc_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-istiodremote-mc_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-security-multicluster_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-security-multicluster_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
integ-pilot_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security_istio
integ-telemetry_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry_istio
integ-pilot-multicluster_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-multicluster_istio
integ-ipv6_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-ipv6_istio
integ-telemetry-mc_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-mc_istio
integ-security-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote-mc_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-istiodremote-mc_istio
integ-distroless_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-distroless_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-pilot-istiodremote_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-pilot-istiodremote_istio
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
unit-tests_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test unit-tests_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
integ-pilot_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security_istio
integ-telemetry_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry_istio
integ-pilot-multicluster_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-multicluster_istio
integ-ipv6_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-ipv6_istio
integ-telemetry-mc_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-mc_istio
integ-security-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote-mc_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-istiodremote-mc_istio
integ-distroless_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-distroless_istio
integ-security-multicluster_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security-multicluster_istio
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.
@nmittler: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-operator-controller_istio
f9182e6c61e509460e668b2fc4727137921c2642
link
true
/test integ-operator-controller_istio
lint_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test lint_istio
integ-cni_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-cni_istio
integ-pilot_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot_istio
integ-telemetry-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-istiodremote_istio
integ-security_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security_istio
integ-telemetry_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry_istio
integ-pilot-multicluster_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-multicluster_istio
integ-ipv6_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-ipv6_istio
integ-telemetry-mc_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-telemetry-mc_istio
integ-security-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security-istiodremote_istio
integ-pilot-istiodremote-mc_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-istiodremote-mc_istio
integ-distroless_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-distroless_istio
integ-security-multicluster_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-security-multicluster_istio
integ-pilot-istiodremote_istio
3e4b5cf8b570c00d31decee0b9c0951ddc4d70a4
link
true
/test integ-pilot-istiodremote_istio
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.
#37324 for context.
|
gharchive/pull-request
| 2022-02-14T23:12:23 |
2025-04-01T04:34:38.133133
|
{
"authors": [
"istio-testing",
"nmittler",
"therealmitchconnors"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/37332",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1167912538
|
add warn message
Please provide a description of this PR:
add warn message
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[x] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Please check any characteristics that apply to this pull request.
[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.
Hi @xichengliudui. 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.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
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.
/ok-to-test
@xichengliudui: PR needs rebase.
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.
|
gharchive/pull-request
| 2022-03-14T05:36:11 |
2025-04-01T04:34:38.142444
|
{
"authors": [
"Chen-Xintong",
"istio-testing",
"xichengliudui"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/37896",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2376525383
|
Automator: update istio/client-go@master dependency in istio/istio@master
Generated by Automator - 2024-06-27T01:18:28+00:00
@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
b8c34599484a28806b26f8809d32f163f56a1e3a
link
true
/test integ-helm
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-sigs/prow repository. I understand the commands that are listed here.
@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
c6d031f33475a25b6e82a7b3f94dd7a74fcd3e64
link
true
/test integ-helm
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-sigs/prow repository. I understand the commands that are listed here.
@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name
Commit
Details
Required
Rerun command
integ-helm_istio
60f7765c80184d3b7da9cf6893ceb565ade7aa05
link
true
/test integ-helm
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-sigs/prow repository. I understand the commands that are listed here.
|
gharchive/pull-request
| 2024-06-27T01:26:31 |
2025-04-01T04:34:38.153184
|
{
"authors": [
"istio-testing"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/51752",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
364702669
|
fix boilerplate error in /bin and /prow directory
parts of https://github.com/istio/istio/issues/8996
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
If they are not already assigned, you can assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Hi @stewart-yu. 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.
/ok-to-test
/lgtm
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hzxuzhonghu
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
If they are not already assigned, you can assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/lgtm
/approve
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hzxuzhonghu, sdake
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: linsun
If they are not already assigned, you can assign the PR to them by writing /assign @linsun in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/assign @ rshriram
/assign @linsun
/approve
pending pass shellcheck test.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hzxuzhonghu, linsun, sdake
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
OWNERS [linsun]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
New changes are detected. LGTM label has been removed.
/retest
@stewart-yu: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/e2e-mixer-no_auth-mcp.sh
e29c4f794437ebb68357383e8a9ac70624b02d5c
link
/test e2e-mixer-no_auth-mcp
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 e2e-mixer-no_auth-mcp
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hzxuzhonghu, linsun, sdake
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
OWNERS [linsun]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@stewart-yu: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/e2e-mixer-no_auth-mcp.sh
9a6d9a88cb8d158975fecbb6bc57119164ebec90
link
/test e2e-mixer-no_auth-mcp
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.
@stewart-yu: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/e2e-mixer-no_auth-mcp.sh
9a6d9a88cb8d158975fecbb6bc57119164ebec90
link
/test e2e-mixer-no_auth-mcp
prow/istio-unit-tests.sh
9a6d9a88cb8d158975fecbb6bc57119164ebec90
link
/test istio-unit-tests
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.
@stewart-yu: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/e2e-mixer-no_auth-mcp.sh
9a6d9a88cb8d158975fecbb6bc57119164ebec90
link
/test e2e-mixer-no_auth-mcp
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.
@stewart-yu: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/e2e-mixer-no_auth-mcp.sh
9a6d9a88cb8d158975fecbb6bc57119164ebec90
link
/test e2e-mixer-no_auth-mcp
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.
|
gharchive/pull-request
| 2018-09-28T00:53:18 |
2025-04-01T04:34:38.190744
|
{
"authors": [
"hzxuzhonghu",
"istio-testing",
"linsun",
"sdake",
"stewart-yu"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/9024",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
365757679
|
Fix the gate
stackdriver 0.6.0 brings in a slew of dependencies which
are incompatible or otherwise not usable by Istio or its
transitive dependencies. Pin stackdriver to 0.5.0.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: hklai
If they are not already assigned, you can assign the PR to them by writing /assign @hklai in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@sdake: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3
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.
@sdake: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3
prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp
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.
@sdake: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3
prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp
prow/e2e-mixer-no_auth.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-mixer-no_auth
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.
@sdake: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3
prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp
prow/e2e-mixer-no_auth.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-mixer-no_auth
prow/e2e-mixer-no_auth-mcp.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-mixer-no_auth-mcp
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.
@sdake: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3
prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp
prow/e2e-mixer-no_auth.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-mixer-no_auth
prow/e2e-mixer-no_auth-mcp.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-mixer-no_auth-mcp
prow/e2e-dashboard.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-dashboard
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.
@sdake: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3
prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp
prow/e2e-mixer-no_auth.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-mixer-no_auth
prow/e2e-mixer-no_auth-mcp.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-mixer-no_auth-mcp
prow/e2e-dashboard.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-dashboard
prow/e2e-bookInfoTests-v1alpha3.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-bookInfoTests-envoyv2-v1alpha3
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.
@sdake: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3
prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp
prow/e2e-mixer-no_auth.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-mixer-no_auth
prow/e2e-mixer-no_auth-mcp.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-mixer-no_auth-mcp
prow/e2e-dashboard.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-dashboard
prow/e2e-bookInfoTests-v1alpha3.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-bookInfoTests-envoyv2-v1alpha3
prow/istio-pilot-multicluster-e2e.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-multicluster-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.
@sdake: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3
prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp
prow/e2e-mixer-no_auth.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-mixer-no_auth
prow/e2e-mixer-no_auth-mcp.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-mixer-no_auth-mcp
prow/e2e-dashboard.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-dashboard
prow/e2e-bookInfoTests-v1alpha3.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-bookInfoTests-envoyv2-v1alpha3
prow/istio-pilot-multicluster-e2e.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test istio-pilot-multicluster-e2e
prow/e2e-simpleTests.sh
e0e3b4a817191cdc0fad308a56c94a9dc7338f6a
link
/test e2e-simpleTests
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.
@sdake: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
prow/e2e-mixer-no_auth-mcp.sh
8c82568c1680da5879a1b1b31e52d86f86b593cb
link
/test e2e-mixer-no_auth-mcp
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.
|
gharchive/pull-request
| 2018-10-02T06:28:37 |
2025-04-01T04:34:38.245114
|
{
"authors": [
"istio-testing",
"sdake"
],
"repo": "istio/istio",
"url": "https://github.com/istio/istio/pull/9086",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
225539222
|
DO NOT MERGE! Fast Forward stable to 1870ac815d2ba13860088c92cadd9b62432c79f6.
This PR will be merged automatically once checks are successful.
This change is
Jenkins job mixer/postsubmit passed
Jenkins job mixer/e2e-suite passed
|
gharchive/pull-request
| 2017-05-01T22:02:56 |
2025-04-01T04:34:38.247328
|
{
"authors": [
"istio-testing"
],
"repo": "istio/mixer",
"url": "https://github.com/istio/mixer/pull/644",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
490539337
|
WIP: Add force flag to bypass validation
In case users have custom charts, or there's a problem with our schema, we need a bypass for the values validation. This flag will cause the tool to still report validation errors but proceed in spite of them.
@ostromart: The following test failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
lint_operator
e8d8df9b5d3ade8da3a524c44bd58374dc346add
link
/test lint
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.
@ostromart: The following tests failed, say /retest to rerun them all:
Test name
Commit
Details
Rerun command
lint_operator
e8d8df9b5d3ade8da3a524c44bd58374dc346add
link
/test lint
manifest-apply_operator
e8d8df9b5d3ade8da3a524c44bd58374dc346add
link
/test manifest-apply
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.
Moved to https://github.com/istio/operator/pull/353 due to some bad merges being pulled in.
|
gharchive/pull-request
| 2019-09-06T21:59:52 |
2025-04-01T04:34:38.255140
|
{
"authors": [
"istio-testing",
"ostromart"
],
"repo": "istio/operator",
"url": "https://github.com/istio/operator/pull/266",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
265936668
|
Rename Attributes to CompressedAttributes
What this PR does / why we need it:
Istio/api renamed Attributes to CompressedAttributes. Hence this change.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:
@qiwzhang: Adding do-not-merge/release-note-label-needed because the release note process has not been followed.
One of the following labels is required "release-note", "release-note-action-required", or "release-note-none".
Please see: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#write-release-notes-if-needed.
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.
is this just a name and otherwise 100% backward compatible ?
I'm trying to make a new pilot of trunk that will need to work with 0.2.7 for the other components (envoy, mixer,etc)
Just name change. it will not break compatibility
|
gharchive/pull-request
| 2017-10-16T22:31:46 |
2025-04-01T04:34:38.260361
|
{
"authors": [
"istio-testing",
"ldemailly",
"qiwzhang"
],
"repo": "istio/pilot",
"url": "https://github.com/istio/pilot/pull/1505",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
168570485
|
Using the new version. Don't see the notifications. What am i missing.
Selected all the pokemon in favorite pokemon list. Notifications->favorite norification-> ON
Don't see any notification. What am i missing??
And I used version 2.0 IPA
The backgrounding in 2.0 was terminated by iOS more often than we'd like, which meant that notifications would stop. We've worked around the system limitations since the release of 2.0, and the next release will be even more reliable in the background.
I don't see the notifications even with the app running on my screen.
Try with the latest release v2.0.1.
it works with v2.0.1 . Thanks.
|
gharchive/issue
| 2016-08-01T05:36:34 |
2025-04-01T04:34:38.458947
|
{
"authors": [
"istornz",
"mtelaprolu",
"parrots"
],
"repo": "istornz/iPokeGo",
"url": "https://github.com/istornz/iPokeGo/issues/128",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
113725776
|
ng-cher
Angular module for talking to the cher client API
As a developer, I want to be able to install an angular module and use that to talk to the cher admin API. I should be able to specify the API version
|
gharchive/issue
| 2015-10-28T01:50:38 |
2025-04-01T04:34:38.459872
|
{
"authors": [
"jray"
],
"repo": "istrategylabs/cher",
"url": "https://github.com/istrategylabs/cher/issues/33",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
70708552
|
Trying to install, I get this error. Could you help?
2015-04-24 14:39:05,501 27075 INFO 03test openerp.modules.loading: loading product_variant_multi/product_view.xml
2015-04-24 14:39:05,906 27075 ERROR 03test openerp.addons.base.ir.ir_ui_view: Field price_margin does not exist
Error context:
View product.variant.form
[view_id: 2317, xml_id: n/a, model: product.product, parent_id: n/a]
2015-04-24 14:39:05,908 27075 ERROR 03test openerp.http: Exception during JSON request handling.
Traceback (most recent call last):
File "/home/odoo-test/odoo-test/openerp/http.py", line 525, in _handle_exception
return super(JsonRequest, self)._handle_exception(exception)
File "/home/odoo-test/odoo-test/openerp/http.py", line 562, in dispatch
result = self._call_function(*_self.params)
File "/home/odoo-test/odoo-test/openerp/http.py", line 302, in _call_function
return checked_call(self.db, *args, *_kwargs)
File "/home/odoo-test/odoo-test/openerp/service/model.py", line 113, in wrapper
return f(dbname, _args, *_kwargs)
File "/home/odoo-test/odoo-test/openerp/http.py", line 299, in checked_call
return self.endpoint(_a, *_kw)
File "/home/odoo-test/odoo-test/openerp/http.py", line 791, in call
return self.method(_args, *_kw)
File "/home/odoo-test/odoo-test/openerp/http.py", line 395, in response_wrap
response = f(_args, *_kw)
File "/home/odoo-test/odoo-test/addons/web/controllers/main.py", line 953, in call_button
action = self._call_kw(model, method, args, {})
File "/home/odoo-test/odoo-test/addons/web/controllers/main.py", line 941, in _call_kw
return getattr(request.registry.get(model), method)(request.cr, request.uid, _args, *_kwargs)
File "/home/odoo-test/odoo-test/openerp/api.py", line 241, in wrapper
return old_api(self, _args, *_kwargs)
File "/home/odoo-test/odoo-test/openerp/addons/base/module/module.py", line 450, in button_immediate_install
return self._button_immediate_function(cr, uid, ids, self.button_install, context=context)
File "/home/odoo-test/odoo-test/openerp/api.py", line 241, in wrapper
return old_api(self, _args, *_kwargs)
File "/home/odoo-test/odoo-test/openerp/addons/base/module/module.py", line 498, in _button_immediate_function
registry = openerp.modules.registry.RegistryManager.new(cr.dbname, update_module=True)
File "/home/odoo-test/odoo-test/openerp/modules/registry.py", line 346, in new
openerp.modules.load_modules(registry._db, force_demo, status, update_module)
File "/home/odoo-test/odoo-test/openerp/modules/loading.py", line 363, in load_modules
loaded_modules, update_module)
File "/home/odoo-test/odoo-test/openerp/modules/loading.py", line 263, in load_marked_modules
loaded, processed = load_module_graph(cr, graph, progressdict, report=report, skip_modules=loaded_modules, perform_checks=perform_checks)
File "/home/odoo-test/odoo-test/openerp/modules/loading.py", line 182, in load_module_graph
_load_data(cr, module_name, idref, mode, kind='data')
File "/home/odoo-test/odoo-test/openerp/modules/loading.py", line 118, in _load_data
tools.convert_file(cr, module_name, filename, idref, mode, noupdate, kind, report)
File "/home/odoo-test/odoo-test/openerp/tools/convert.py", line 901, in convert_file
convert_xml_import(cr, module, fp, idref, mode, noupdate, report)
File "/home/odoo-test/odoo-test/openerp/tools/convert.py", line 987, in convert_xml_import
obj.parse(doc.getroot(), mode=mode)
File "/home/odoo-test/odoo-test/openerp/tools/convert.py", line 853, in parse
self._tags[rec.tag](self.cr, rec, n, mode=mode)
File "/home/odoo-test/odoo-test/openerp/tools/convert.py", line 763, in _tag_record
id = self.pool['ir.model.data']._update(cr, self.uid, rec_model, self.module, res, rec_id or False, not self.isnoupdate(data_node), noupdate=self.isnoupdate(data_node), mode=self.mode, context=rec_context )
File "/home/odoo-test/odoo-test/openerp/api.py", line 241, in wrapper
return old_api(self, _args, *_kwargs)
File "/home/odoo-test/odoo-test/openerp/addons/base/ir/ir_model.py", line 1067, in _update
res_id = model_obj.create(cr, uid, values, context=context)
File "/home/odoo-test/odoo-test/openerp/api.py", line 241, in wrapper
return old_api(self, _args, *_kwargs)
File "/home/odoo-test/odoo-test/openerp/addons/base/ir/ir_ui_view.py", line 264, in create
context=context)
File "/home/odoo-test/odoo-test/openerp/api.py", line 241, in wrapper
return old_api(self, _args, *_kwargs)
File "/home/odoo-test/odoo-test/openerp/api.py", line 336, in old_api
result = method(recs, _args, *_kwargs)
File "/home/odoo-test/odoo-test/openerp/models.py", line 4007, in create
record = self.browse(self._create(old_vals))
File "/home/odoo-test/odoo-test/openerp/api.py", line 239, in wrapper
return new_api(self, _args, *_kwargs)
File "/home/odoo-test/odoo-test/openerp/api.py", line 462, in new_api
result = method(self._model, cr, uid, _args, *_kwargs)
File "/home/odoo-test/odoo-test/openerp/models.py", line 4198, in _create
recs._validate_fields(vals)
File "/home/odoo-test/odoo-test/openerp/api.py", line 239, in wrapper
return new_api(self, _args, *_kwargs)
File "/home/odoo-test/odoo-test/openerp/models.py", line 1282, in _validate_fields
raise ValidationError('\n'.join(errors))
ParseError: "ValidateError
Field(s) arch failed against a constraint: Invalid view definition
Error details:
Field price_margin does not exist
Error context:
View product.variant.form
[view_id: 2317, xml_id: n/a, model: product.product, parent_id: n/a]" while parsing /home/odoo-test/odoo-test/addons/product_variant_multi/product_view.xml:262, near
product.variant.form
product.product
It seems that product_variant_multi is obsolete and should be updated or deleted from 8.0 branch
The module was deleted
|
gharchive/issue
| 2015-04-24T14:47:15 |
2025-04-01T04:34:38.490887
|
{
"authors": [
"lapagept",
"yelizariev"
],
"repo": "it-projects-llc/pos-addons",
"url": "https://github.com/it-projects-llc/pos-addons/issues/6",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
1278685432
|
Create script that creates users with roles
Description
This is the user story to create a script that will create default users with their roles so that we can use them for testing.
Acceptance Criteria
Create following roles in the system: Користувач, Модератор, Адміністратор
Create script that will create a user :
a. 1 user - has role Administrator
Script has following parameters:
a. facebook email address
b. role that has Administrator by default, but Moderator or Користувач can be specified too
It is possible to login with these users to the system
User is present in db with role Адміністратор
Epic link
E.g.: Epic #66
for any new users by default "Користувач" role will be asign
Estimate: 3 hours
Done: 3 hours
|
gharchive/issue
| 2022-06-21T16:19:53 |
2025-04-01T04:34:38.494668
|
{
"authors": [
"AndriyParaschuk",
"KhrystynaSuliy",
"Vladyslavko36"
],
"repo": "ita-social-projects/Fragments-back-end",
"url": "https://github.com/ita-social-projects/Fragments-back-end/issues/67",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1773281690
|
['Create habit' page edit mode] The new custom habit with empty 'Habit description' input field could be created
Environment:
OS: macOS Monterey
Version: 12.6.5
Browser: Safari
Version: 16.4.1
Reproducible: always
Build found: 25.06.2023
Pre-conditions
Registered user is logged in https://www.greencity.social/
'Create habit' page is open
Steps to Reproduce
Type the name: "my new habit" into the 'Habit title' input field
Click on the 'testing' button in the 'Pick tags for habit' block
Type more than 13 times 'space' into the 'Habit description' input field
Click on the 'Add Habit' button
Scroll down to the bottom of the 'All habits' page
Observe the new custom habit
Actual result
The new custom habit with empty 'Habit description' input field is created
Expected result
The error message 'Habit description input field can not be empty' highlighted in red is shown under the input field
User story
"Change request to #1001 . Add new custom habit https://github.com/nromanen/pratical_testing_2022/issues/192"
Fixed, cannot be added using only spaces in the "Habit title"
|
gharchive/issue
| 2023-06-25T13:20:26 |
2025-04-01T04:34:38.500139
|
{
"authors": [
"Vadym840217",
"machechka"
],
"repo": "ita-social-projects/GreenCity",
"url": "https://github.com/ita-social-projects/GreenCity/issues/5994",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2758849358
|
[TC][Main][Instagram block][Mobile] Verify the user can scroll through Instagram posts to the right and left.
Priority: High
Environment: Mobile
Preconditions:
The "StreetCode" page is opened.
Scroll to Instagram block "Ми в інсті".
Steps to reproduce:
Scroll on the right to Instagram posts
Scroll on the left to Instagram posts
Expected result:
By scrolling right, the posts will change and also the bottom pagination under the posts also changes
By scrolling left, the posts will change and also the bottom pagination under the posts also changes
User story: https://github.com/ita-social-projects/StreetCode/issues/698
We have the same TC - https://github.com/ita-social-projects/StreetCode/issues/1886
|
gharchive/issue
| 2024-12-25T14:55:45 |
2025-04-01T04:34:38.504134
|
{
"authors": [
"Artem650"
],
"repo": "ita-social-projects/StreetCode",
"url": "https://github.com/ita-social-projects/StreetCode/issues/1887",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
810594916
|
Fix for not found lesson check
Validation for not found lesson were added
Changed check for null mentorId
Please, always provide "steps to reproduce" information for issues/PRs marked as bugs. Adding a screenshot probably would be a good practice too.
Also these changes would probably affect this pull request: https://github.com/ita-social-projects/WhatBackend/pull/408
|
gharchive/pull-request
| 2021-02-17T22:44:15 |
2025-04-01T04:34:38.505759
|
{
"authors": [
"Fizik97",
"gingerbread-monster"
],
"repo": "ita-social-projects/WhatBackend",
"url": "https://github.com/ita-social-projects/WhatBackend/pull/429",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
792037680
|
[4001] errore EC025
Salve
al Comune di CARTOCETO in presubentro - idOperazioneANPR 20843227
facendo una estrazione dei cittadini per un intevallo id ANPR
con datiAnagraficiRichiesti=1 (codice presente nella tabella 16)
torna errore EC025 (Codice datiAnagraficiRichiesti non valido)
stessa cosa che mettendo datiAnagraficiRichiesti=1 idOperazioneANPR>20843237
Buongiorno, state chiedendo un range di identificativi troppo elevato
Buongiorno, state chiedendo un range di identificativi troppo elevato
Buongiorno
grazie
quanto è il limite massimo? prima era 2000
Buongiorno
grazie
quanto è il limite massimo? prima era 2000
Sempre lo stesso
Sempre lo stesso
qualcosa non mi torna
sempre per CARTOCETO in PRESUBENTRO
idOperazioneANPR 20847588
con
<idSchedaSoggettoANPRDa>148444139</idSchedaSoggettoANPRDa> <idSchedaSoggettoANPRA>148444388</idSchedaSoggettoANPRA>
da sempre errore EC025 sono 249 schede
qualcosa non mi torna
sempre per CARTOCETO in PRESUBENTRO
idOperazioneANPR 20847588
con
<idSchedaSoggettoANPRDa>148444139</idSchedaSoggettoANPRDa> <idSchedaSoggettoANPRA>148444388</idSchedaSoggettoANPRA>
da sempre errore EC025 sono 249 schede
Potete riprovare? Attendo verifica
Potete riprovare? Attendo verifica
Perfetto sembra tutto risolto, lo stesso problema c'era in produzione e anche li è risolto.
grazie
Saluti
Perfetto sembra tutto risolto, lo stesso problema c'era in produzione e anche li è risolto.
grazie
Saluti
|
gharchive/issue
| 2021-01-22T14:14:36 |
2025-04-01T04:34:38.513764
|
{
"authors": [
"Hdemografici",
"rvinzani"
],
"repo": "italia/anpr",
"url": "https://github.com/italia/anpr/issues/2443",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1057276668
|
codice catastale comune sulla famiglia di altro comune
La famiglia 12641318 era emigrata cerso il comune di Imola in due tranche. Successivamente è stata annullata la mutazione da parte del comune di Imola. Attualmente la famiglia risulta residente nel nostro comune ma permane il codice catastale 037032 del comune di Imola invece che il nostro (037057)
Non riesco a mutarlo.
Cordiali slauti
Cesare
051843576
... oppure elenchi puntati:
punto
punto
... o titoli:
Esempio titolo
--- TESTO DA ELIMINARE ---
Il comune d'appartenenza viene modificato dal sistema nel momento in cui vengono effettuate le operazioni di trasferimento della residenza o di ripristino della posizione anagrafica.
Stiamo verificando come mai nel vostro caso non sia stato correttamente aggiornato.
l'incongruenza è stata eliminata
La issue viene chiusa. Nel caso fosse necessario, si prega di riaprirne una nuova facendo riferimento a questa stessa.
|
gharchive/issue
| 2021-11-18T12:03:22 |
2025-04-01T04:34:38.516824
|
{
"authors": [
"CESARERAMADORI",
"frmariani"
],
"repo": "italia/anpr",
"url": "https://github.com/italia/anpr/issues/2961",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1749624102
|
Atto di Matrimonio - UseCase 319999: Dati Pubblicazione da consolato
Salve,
Nel caso d'uso in oggetto il matrimonio può essere celebrato su delega di un consolato. In base al mapping la pubblicazione di un atto di matrimonio prevede obbligatoriamente i dati di provincia e comune che nella casistica in analisi sono esteri. Non essendo censite le province e i comuni esteri, come passare questi dati inerenti alla pubblicazione?
Attendo riscontro.
Distinti saluti.
Salve @DiBellaDavide
Nel payload di validazione, specificando come idStato il valore che fa riferimento a uno stato estero, il servizio non dovrebbe controllare l'obbligatorietà del comune e provincia. Sul portale di ANPR https://www.anagrafenazionale.interno.it/area-tecnica/tabelle-di-decodifica/ sono disponibili i CSV con le decodifiche degli stati.
Nel caso in cui dovesse risolvere il problema la invitiamo a chiudere la issue.
Cordiali Saluti.
Supporto ANSC
Salve @DiBellaDavide
Stando al model e mapping https://github.com/italia/ansc/blob/main/docs/Mapping_casi_uso/matrimoni/Matr_999_1.csv i dati da lei indicati non risultano essere obbligatori, non dovrebbe quindi avere problemi a eseguire la validazione del payload relativo.
Chiudo la issue, nel caso sia necessario riapra la stessa.
Cordiali Saluti.
Supporto ANSC.
|
gharchive/issue
| 2023-06-09T10:29:59 |
2025-04-01T04:34:38.520721
|
{
"authors": [
"DiBellaDavide",
"amusarra"
],
"repo": "italia/ansc",
"url": "https://github.com/italia/ansc/issues/180",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2014658020
|
usecase 52112 Straniero o apolide, del quale il padre o la madre o uno dei ascendenti in linea retta di secondo grado sono stati cittadini per nascita: acquisto mediante prestazione del servizio militare per lo Stato italiano (Citt_006)
Buonasera,
nel mapping esiste l'obbligatorietà del model evento.eventocollegato per il caso in oggetto.
Sono entrata nella webapp di test per formare un atto uguale a quello che stavo facendo sul mio gestionale: non trovo da nessuna parte dove inserire i dati di quel model.
Sto sbagliando io nel non trovare sulla webapp? Il model è stato lasciato obbligatorio per sbaglio nel file di mapping?
Buongionro non avendo ricevuto risposta, chiudiamo la issue. Se ci fossero ulteiori dubbi o perplessità la preghiamo di aprire una issue dedicata.
|
gharchive/issue
| 2023-11-28T15:06:21 |
2025-04-01T04:34:38.522695
|
{
"authors": [
"annamaraspin",
"asqueglia"
],
"repo": "italia/ansc",
"url": "https://github.com/italia/ansc/issues/515",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2071850458
|
RILASCIO CERTIFICAZIONI
DA LISSONE
Si segnala che quando vengono rilasciati certificati/estratti/copie integrali degli atti, leggendo il QRCODE in alto a destra:
Se il certificato è stato richiesto dalla webapp, non escono i dati del richiedente il certificato
Se il certificato è stato rilasciato per il tramite del nostro gestionale, escono i dati dell’ufficiale dello stato civile che ha richiesto il certificato (cognome, nome ma soprattutto il codice fiscale).
Si chiede di uniformare la certificazione, omettendo il dato del richiedente o quanto meno il codice fiscale
Da servizio cooperativo, il soggetto richiedente da trasmettere non è l'ufficiale di stato civile che emette il certificato ma il cittadino che ha richiesto il certificato per se stesso o per un soggetto terzo.
Con priorità più bassa adegueremo successivamente la web app, per consentire l'inserimento del soggetto richiedente.
|
gharchive/issue
| 2024-01-09T08:15:55 |
2025-04-01T04:34:38.525281
|
{
"authors": [
"asqueglia"
],
"repo": "italia/ansc",
"url": "https://github.com/italia/ansc/issues/595",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2093270649
|
Campo tipoNascitaSoggetto versione 1.23.0
Nel changelog della versione 1.23.0 è indicata l'aggiunta del campo tipoNascitaSoggetto nell'oggetto ModelDatiDiNascita, ma nel file model_evento.yaml risulta invece che sia stato aggiunto nell'oggetto ModelDocumentoRiconoscimento.
Buonasera,
si comunica che è stato corretto l'annidamento del campo tipoNascitaSoggetto, che erronamenente non faceva parte di ModelDatiDiNascita.
Grazie e saluti,
Supporto ANSC
|
gharchive/issue
| 2024-01-22T07:33:17 |
2025-04-01T04:34:38.527039
|
{
"authors": [
"gbuemi",
"siscomanpr"
],
"repo": "italia/ansc",
"url": "https://github.com/italia/ansc/issues/629",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
323627382
|
Nuovo design-react-kit
Sostituzione files di design-react con nuovo design-react-kit basato su Bootstrap Italia e nuovo UI kit.
@gesposito ho aggiunto tutto il tuo lavoro preso da https://github.com/italia/design-react-kit in questo branch. Da qui, quando riusciamo potremmo:
1 - controllare, attraverso il compare, cosa possiamo ereditare da design-react (.editorconfig, documentazione, altro) ed aggiungere commit a questa PR di conseguenza
2 - eliminare design-react-kit
3 - attivare CircleCI qui e staccare Travis (sorry!)
4 - mergiare tutto e portare il nuovo kit su master
5 - rinominare questo repo come design-react-kit (e risistemare CircleCI nel caso si rompa di nuovo)
Ogni suggerimento è apprezzato @dej611 @Takeno @mjhost, anche su Slack #design-devel ovviamente!
Ho seguito i consigli ricevuti qui (e su Slack) ed ho aperto una nuova PR (con integrazione graduale)
https://github.com/italia/design-react/pull/15 (WIP)
|
gharchive/pull-request
| 2018-05-16T13:44:11 |
2025-04-01T04:34:38.530325
|
{
"authors": [
"francescozaia",
"gesposito"
],
"repo": "italia/design-react",
"url": "https://github.com/italia/design-react/pull/14",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
}
|
389711986
|
Richiesta di validazione dei metadati - Unione Bassa Bresciana Occidentale
Buongiorno,
per conto dell'unione si richiede la verifica e il deploy dei metadati esposti all'URL:
https://www.suap.unionecomunibbo.it/simplesaml/module.php/saml/sp/metadata.php/unionebbo
Buongiorno,
In relazione alla richiesta in oggetto, la vostrta azienda ha già presentato un metadata per il comune di oggetto tramite la issue 624.
Poichè per ogni P.A. è possibile definire un unico metadata, qualora sia necessario aggiungere ulteriori servizi, la loro descrizione va aggiunta al metadata già comunicato per la P.A. in questione, avendo cura di mantenere esattamente lo stesso valore dell' identificativo unico (EntityID).
Buongiorno,
ci sono novità in merito?
Grazie
Buongiorno,
ci sono novità in merito?
Grazie
Il Metadata è stato inoltrato verso gli IdP e da essi caricato.
|
gharchive/issue
| 2018-12-11T11:11:47 |
2025-04-01T04:34:38.540074
|
{
"authors": [
"AntonioGiovanniSchiavone",
"globogis"
],
"repo": "italia/spid",
"url": "https://github.com/italia/spid/issues/699",
"license": "CC0-1.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2508573173
|
🛑 ITBM WebSite is down
In 58901a9, ITBM WebSite (https://itbm.mx) was down:
HTTP code: 0
Response time: 0 ms
Resolved: ITBM WebSite is back up in d3dd7da after 9 minutes.
|
gharchive/issue
| 2024-09-05T19:35:24 |
2025-04-01T04:34:38.542639
|
{
"authors": [
"itbm-services"
],
"repo": "itbm-services/projects",
"url": "https://github.com/itbm-services/projects/issues/523",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2042755346
|
deps: bump upper scmrepo limit to <3
Needed for https://github.com/iterative/dvc/pull/10168
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (96c6d9d) 85.37% compared to head (d2c05ca) 85.37%.
Additional details and impacted files
@@ Coverage Diff @@
## main #434 +/- ##
=======================================
Coverage 85.37% 85.37%
=======================================
Files 19 19
Lines 2120 2120
=======================================
Hits 1810 1810
Misses 310 310
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
|
gharchive/pull-request
| 2023-12-15T01:48:31 |
2025-04-01T04:34:38.577736
|
{
"authors": [
"codecov-commenter",
"efiop"
],
"repo": "iterative/gto",
"url": "https://github.com/iterative/gto/pull/434",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1251066522
|
Install error
Unity 2022.1.2f1
installed the latest version through Package Manager
newer versions of unity not supported yet,
try this url instead to install (with the #v1.0.0 suffix)
https://github.com/itisnajim/SocketIOUnity.git#v1.0.0
if not working, choose a lower version of unity and install via
https://github.com/itisnajim/SocketIOUnity.git
Actually errors shown above do not relate to versions of unity. It was due to the lack of Reactive module of your local .Net environment. Reactive can be found on NuGet.
I had the same problem with the latest version, and my I am using Unity 2021.3. Eventually, I resolved it by installing Reactive with NuGetForUnity. Once you install Reactive to your project, errors that shown in the screenshot should be gone after you restart the editor.
Okay, thanks
Your two methods work great, thank you!
|
gharchive/issue
| 2022-05-27T17:38:11 |
2025-04-01T04:34:38.602348
|
{
"authors": [
"WeroCode",
"itisnajim",
"jingfu-wei"
],
"repo": "itisnajim/SocketIOUnity",
"url": "https://github.com/itisnajim/SocketIOUnity/issues/14",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1498163011
|
Fix for YOLO tf models
@FenixFly
@FenixFly, можно мержить, если у тебя нет больше никаких изменений.
|
gharchive/pull-request
| 2022-12-15T10:16:50 |
2025-04-01T04:34:38.603249
|
{
"authors": [
"VankaVstanka03",
"valentina-kustikova"
],
"repo": "itlab-vision/dl-benchmark",
"url": "https://github.com/itlab-vision/dl-benchmark/pull/318",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1815687219
|
Model Wishlist
Was just wondering about the possibility of implementing models with time-varying boundaries (or collapsing boundaries). That said, it might make sense to not have that as a priority, given some of their critiques.
https://www.frontiersin.org/articles/10.3389/fpsyg.2014.01364/full (implementation)
https://www.jneurosci.org/content/35/6/2476 (a critique of these models)
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5450920/ (another critique)
@DominiqueMakowski, I agree with your assessment. There is some controversy regarding the validity of time varying boundaries. I'm definitely not opposed to adding support at some point.
I think this is a good opportunity to create a working wishlist of models we could add. Let me know if there is anything else you want to add.
Model Wishlist
model
assigned
priority
references
finished
time varying boundary
NA
low
1,2,3
No
mlba
itsdfish
high
4
No
References
Zhang, S., Lee, M. D., Vandekerckhove, J., Maris, G., & Wagenmakers, E. J. (2014). Time-varying boundaries for diffusion models of decision making and response time. Frontiers in psychology, 5, 1364.
Hawkins, G. E., Forstmann, B. U., Wagenmakers, E. J., Ratcliff, R., & Brown, S. D. (2015). Revisiting the evidence for collapsing boundaries and urgency signals in perceptual decision-making. Journal of Neuroscience, 35(6), 2476-2484.
Voskuilen, C., Ratcliff, R., & Smith, P. L. (2016). Comparing fixed and collapsing boundary versions of the diffusion model. Journal of mathematical psychology, 73, 59-79.
Trueblood, J. S., Brown, S. D., & Heathcote, A. (2014). The multiattribute linear ballistic accumulator model of context effects in multialternative choice. Psychological review, 121(2), 179.
rtdistsseems to implement LBA with varying drift SDs. Is this a feature that we could add?
Yeah. I pushed a new release which uses a vector for the drift SDs. The default is a vector of ones.
I suspect the same could be done for LNR, but I don't know if that's common
I was wondering the same thing myself. I need to verify its identifiable when the SDs differ. I believe it is.
Also, to add to the wishlist above:
multiple-threshold log-normal race (MTLNR): Reynolds et al. (2020) :)
[ ] Time Varying Extension of the Shifted Wald Model: Howard et al., in press
R code
[ ] Generalised exponential-Gaussian distribution (GEG models): Marmolejo-Ramos et al., 2022
I am also interested in the time varying shifted wald. Let me read that paper this weekend and give a shot at the translation.
Sounds good. I will take a look at the Generalised exponential-Gaussian model.
I decided against adding the generalized Ex-Gaussian because it does not appear to be theoretically motivated. I added the Ex-Gaussian instead. The psychological interpretation of the Ex-Gaussian is dubious too, but I added it because it was simple and it has a historical role in RT modeling.
but I added it because it was simple and it has a historical role in RT modelling
Yes, totally agree, very cool!
because it does not appear to be theoretically motivated
Out of curiosity, can you elaborate a bit?
I did not go through the papers in fine detail, but my tentative impression is that the validity of the ex-gaussian distribution has not been strongly established, and the new shape parameter of the generalized ex-gaussian model has no psychological interpretation. If the $\alpha$ changes, what does that mean in terms of cognitive processes or mechanisms? Probably nothing.
I recommend checking out the paper below. The authors show through simulation and experimentation that the ex-Gaussian parameters do not change selectively with experimental manipulations (or varying DDM parameters). In many cases, all parameters respond to the manipulations, which seems to imply they do not map onto cognitive processes in a clear fashion if at all.
Matzke, D., & Wagenmakers, E. J. (2009). Psychological interpretation of the ex-Gaussian and shifted Wald parameters: A diffusion model analysis. Psychonomic bulletin & review, 16, 798-817.
[ ] Time Varying Shifted Wald Model: Howard et al., in press
R code
After reviewing the specific paper you mentioned, @DominiqueMakowski, it appears to primarily focus on exploiting a particular aspect of the Wald distribution's relationship with another distribution (e.g., ex-Gaussian). This approach is employed to facilitate on-the-fly computation of the posterior through conjugacy. Such trial-varying estimation permits variation in parameters across different trials. Initially, however, I had the impression that you were interested in exploring dynamics within trials, such as fluctuations in drift in the ADDM model, for example. If our focus remains on the former aspect, I believe only minor adjustments (if any) are necessary for the current Wald implementation. Subsequently, it would simply be a matter of demonstrating the procedure as an example of how trial-varying estimation could be implemented in Julia. However, this seems more like an illustrative application rather than the development of an entirely new model for the package. What are your guys thoughts on this?
on-the-fly computation of the posterior through conjugacy
I only gave the paper a cursory read, but arrived at a similar conclusion and wanted to wait for your evaluation. There is no need to create a new model type because the Wald is applied to a moving window of data. In my opinion, the biggest innovation was deriving a conjugate prior, which is difficult except in very simple cases. I think it would be sufficient to add an example to the parameter estimation examples in the docs showing how to use the conjugate prior without the moving window of data. The only thing that was a bit unclear to me was how non-decision time was treated.
👍
Sorry to just add stuff on this thread while being totally useless regarding their assessment and implementation ^^
Unless I'm mistaken, most models can currently already be used for one-choice paradigms (e.g., LBA or LNR with one accumulator; + all the one-choice specific models like exgaussian and Wald). Most but the DDM, currently (?).
This paper apparently shows that it's doable, but I didn't find many details regarding the implementation. Is that something that we could support?
@DominiqueMakowski, I think these ideas are all worthy of discussion and are not necessarily useless. Conjugate priors are quite convenient and have practical utility. So I think that is worth mentioning it in the parameter estimation section.
I think the single choice DDM is something that we could support. Note that it does not have a known PDF and the drift rate mean and SD are not identifiable. One alternative that I would suggest is the WaldMixture, which is similar except it assumes non-decision time is a constant rather than a random variable. The WaldMixture has a known PDF and the mean and SD drift rates are identifiable.
If you are interested in false starts (premature responses), the paper below extends the 1 choice DDM to such situations. It has the same issues, but it models the pre-stimulus decision process.
Walsh, M. M., Gunzelmann, G., & Van Dongen, H. P. (2017). Computational cognitive modeling of the temporal dynamics of fatigue from sleep loss. Psychonomic bulletin & review, 24, 1785-1807.
hybrid racing-diffusion ex-Gaussian(RDEX) stop-signal model: though it doesn't look like a new model per se but rather just using 2 exGaussian ones if I understand correctly
However, in the future, it might be useful to have more examples in the documentation where we show how to implement these published SSM applications with Julia
@DominiqueMakowski, thanks for the suggestions. I'll try to find time to read the paper for the RDEX in more detail. After a cursory read, it looks like it is applied to the Go, No-Go task where the racing diffusion is used for go responses and the ex-Gaussian is used for no go responses. I'm not sure exactly why this mixture is used, but that will probably become clearer once I read the paper more thoroughly.
I can add a page to the document that explains how to extend the API for new models. I think that is a good idea.
Circling back to the time varying idea, I was exploring simulations for a model that captures the concept of certain sources of information coming "online" at different time points. This has been discussed in several applied cases where the drift considered multiple attributes, weighting their importance and changing their latency relative to one another (in the two-attribute case). These are either called starting time DDM (stDDM) or multi-attribute, time-dependent DDM (mtDDM). I put together a simulator for this idea since it is rampant in the literature. Here is a link to the PR:
https://github.com/itsdfish/SequentialSamplingModels.jl/pull/59
Here are some citations of use cases:
Amasino, D.R., Sullivan, N.J., Kranton, R.E., et al. Amount and time exert independent influences on intertemporal choice. Nat Hum Behav 3, 383–392 (2019). https://doi.org/10.1038/s41562-019-0537-2
Barakchian, Z., Beharelle, A.R., & Hare, T.A. Healthy decisions in the cued-attribute food choice paradigm have high test-retest reliability. Sci Rep, (2021). https://doi.org/10.1038/s41598-021-91933-6
Chen, H.Y., Lombardi, G., Li, S.C., et al. Older adults process the probability of winning sooner but weigh it less during lottery decisions. Sci Rep, (2022). https://doi.org/10.1038/s41598-022-15432-y
Lombardi, G., & Hare, T. Piecewise constant averaging methods allow for fast and accurate hierarchical Bayesian estimation of drift diffusion models with time-varying evidence accumulation rates. PsyArXiv, (2021). https://doi.org/10.31234/osf.io/5azyx
Sullivan, N.J., Huettel, S.A. Healthful choices depend on the latency and rate of information accumulation. Nat Hum Behav 5, 1698–1706 (2021). https://doi.org/10.1038/s41562-021-01154-0
-Nonparametric-bound Drift-Diffusion Model (npb-DDM): Seems similar to the time-collapsing-boundaries models -https://www.researchgate.net/publication/377858197_Incorporation_of_a_cost_of_deliberation_time_in_perceptual_decision_making)
Wang 2024: Suggests that the Ornstein-Uhlenbeck Model (OUM) model, a variant of the DDM, might be able to capture more neurally plausible mechanisms than the DDM.
Small helpsheet on priors in DDMs
The LCA is conceptually similar. I am not sure how or whether they might differ. A while back I started an implemention of the OUM, but I was unsure whether it was correct. I will look through the article to see whether I can get some clues.
Just stumbled on the Autocorrelated Bayesian Sampler (ABS) model, which appears like a "one model to rule them all" kind of model
Zhu, J. Q., Sundh, J., Spicer, J., Chater, N., & Sanborn, A. N. (2023). The autocorrelated Bayesian sampler: A rational process for probability judgments, estimates, confidence intervals, choices, confidence judgments, and response times. Psychological review.
Quite an interesting paper, reframing the role of time in cognitive models.
Thanks for sharing. Its been a while since I read that article. I agree that they are interesting ideas. One thing I remember is that some of the model fits were not very good, which is difficult to interpret without understanding to what extend core and auxilary assumptions are driving the predictions. In either case, I do appreciate the effort to broaden the scope of theory.
Sequential sampling without comparison to boundary through model-free reinforcement learning
Although evidence integration to the boundary model has successfully explained a wide range of behavioral and neural data in decision making under uncertainty, how animals learn and optimize the boundary remains unresolved. Here, we propose a model free reinforcement learning algorithm for perceptual decisions under uncertainty that dispenses entirely with the concepts of decision boundary and evidence accumulation. Our model learns whether to commit to a decision given the available evidence or continue sampling information at a cost
https://arxiv.org/pdf/2408.06080
I think it would be reasonable to add a model with an urgancy signal, especially if the physiological evidence is compelling. One reason I have not added such a model is that it was unclear to me whether it was better supported than standard alternatives. These different mechanisms are challenging to distinguish with choice-RT data alone, and might not be possible once auxiliary assumptions are removed (see Jones & Dzhafarov, 2014).
|
gharchive/issue
| 2023-07-21T12:00:36 |
2025-04-01T04:34:38.645951
|
{
"authors": [
"DominiqueMakowski",
"itsdfish",
"kiante-fernandez"
],
"repo": "itsdfish/SequentialSamplingModels.jl",
"url": "https://github.com/itsdfish/SequentialSamplingModels.jl/issues/41",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1762336512
|
updated DDM to reflect tuple output
I have revised the code to align with the standardized coding conventions of the SequentialSamplingModel interface.
Codecov Report
Patch coverage has no change and project coverage change: -0.70 :warning:
Comparison is base (8dca685) 54.51% compared to head (1aee66f) 53.81%.
Additional details and impacted files
@@ Coverage Diff @@
## master #22 +/- ##
==========================================
- Coverage 54.51% 53.81% -0.70%
==========================================
Files 10 10
Lines 543 550 +7
==========================================
Hits 296 296
- Misses 247 254 +7
Impacted Files
Coverage Δ
src/DDM.jl
0.00% <0.00%> (ø)
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
@kiante-fernandez, thanks for the PR!
I thought I had responded, but it looks like I forgot to hit "comment".
Anyways, I think the PR looks good for the most part. I am requesting to minor changes. First, can you please index the choices as 1 and 2 to be consistent with the other models? Second, could you provide information concerning the parameterization of the DDM in the doc strings? For example, what is the value of diffusion noise (typically it is 0.10 or 1.0), and how are the boundaries defined. I assumed 0 and alpha, but I cannot rule out -alpha and alpha. This will help users interpret the starting point. If you have any recommendations for default values in the constructor, that would be appreciated. I was thinking DDM(1.0, .5, .30, .25) but there might be better options.
Once those changes are finalized, I will add some tests and release a new version.
I have made those changes @itsdfish . I have added information about the specifics of the parameterizations and started the doc file as well. Note I saw a citation error in LCA so I just filled that in.
Thanks for fixing the citation error and your attention to detail in the DDM docs. It looks great!
|
gharchive/pull-request
| 2023-06-18T15:06:07 |
2025-04-01T04:34:38.655446
|
{
"authors": [
"codecov-commenter",
"itsdfish",
"kiante-fernandez"
],
"repo": "itsdfish/SequentialSamplingModels.jl",
"url": "https://github.com/itsdfish/SequentialSamplingModels.jl/pull/22",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
265470356
|
add includeMonth()
includeMonth() added as picker property
additional collection view cell that includes a month is added
datetimepicker uses logic to determine which cell to show
replaces PR #44
I think it's all good now. I'll merge it now, though I'll tweak the full date cell layout a bit to make it look better.
Thanks!
Great. I originally designed it like that to leave the style intact while adding the month to the regular cell, but I was going to have to messi-fy the code to make it work. Love the idea of making it look better. Wonderful repo.
|
gharchive/pull-request
| 2017-10-14T06:58:55 |
2025-04-01T04:34:38.670330
|
{
"authors": [
"itsmeichigo",
"monkeywithacupcake"
],
"repo": "itsmeichigo/DateTimePicker",
"url": "https://github.com/itsmeichigo/DateTimePicker/pull/45",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
327070030
|
YouTubeTv doesn’t work
Probably need to spoof the user agent
YouTube TV uses WideVine DRM which isn't supported in WebViews, so it's not realistically possible to make it work in HeliumLift.
|
gharchive/issue
| 2018-05-28T16:05:50 |
2025-04-01T04:34:38.675153
|
{
"authors": [
"itsthisjustin",
"xgerrit"
],
"repo": "itsthisjustin/HeliumLift",
"url": "https://github.com/itsthisjustin/HeliumLift/issues/19",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
1992844118
|
Spark v3 support
Hello,
The documention mentions that spark3 branch should be used for Spark v3.
Could not find spark3 branch, and also there is no spark-greenplum-connector release for Spark v3.
Does spark-greenplum-connector support Spark v3?
Please let me know how to find the sources to build or released artifact for Spark v3.
@hovercraft-github , could you please assist?
Spark v3 has quite a different internal API - that's why connector for it need a separate release.
Yes, we have released connector for Spark v2 only so far.
We have no a strict schedule, but hope v3 connector will be available in the next month.
Hello @hovercraft-github ,
Are there any updates on Spark v3 support?
Just released v3.1.0 for spark3
|
gharchive/issue
| 2023-11-14T14:20:45 |
2025-04-01T04:34:38.677849
|
{
"authors": [
"hovercraft-github",
"ordukhanian"
],
"repo": "itsumma/spark-greenplum-connector",
"url": "https://github.com/itsumma/spark-greenplum-connector/issues/10",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1077606733
|
Add a set of backup flag to enable itzg/mc-backup sidecar
https://hub.docker.com/r/itzg/mc-backup offers instructions on how to configure mc-backup within Kubernetes.
Since this is the official home of the itzg minecraft chart, it would benefit users to have this backup option integrated and configurable via helm chart flags.
see #93, i didn't add rclone or restic completely yet, i have tested this on my server, and seems to be ok. was able to successfully backup and restore
@displague this has been merged
I had forgotten to link up this issue, so I'll close it out.
|
gharchive/issue
| 2021-12-11T18:06:15 |
2025-04-01T04:34:38.697605
|
{
"authors": [
"displague",
"itzg",
"merkinbob"
],
"repo": "itzg/minecraft-server-charts",
"url": "https://github.com/itzg/minecraft-server-charts/issues/91",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
504478951
|
Table zoauth_consumer
Hi,
Looks like zoauth_consumer is missing in the repo?
https://github.com/ivanfemia/abap2gapps/blob/6bf5778ee39c2f531af9fde159cd95684395a457/src/z_gaabap_setup_2_register_user.prog.abap#L121
This project depends on abap2oauth repo
ahh, okay, closing
|
gharchive/issue
| 2019-10-09T07:55:33 |
2025-04-01T04:34:38.724769
|
{
"authors": [
"ivanfemia",
"larshp"
],
"repo": "ivanfemia/abap2gapps",
"url": "https://github.com/ivanfemia/abap2gapps/issues/3",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
302299938
|
Installation Guide - Link to STMS empty - SAPLink nuggets appear old
Dear colleagues,
in the wiki it is told that there is beside of abapGit (Preferred) also the option to install via STMS or SAPLink. But the link behind STMS appears to be empty. And when I look for SAPLink Nuggets in the given links, I see only old nuggets.
Do I miss some information?
Or should we remove the links to STMS and SAPLink as it appears that abapGit is the only pratical path to install abap2xlsx.
Thank you very much,
Rainer Winkler
Rainer,
you are right, STMS and SAPLink are obsolete and no longer maintained.
Dear Rainer,
what you could do is to import abap2xlsx in your NetWeaver ABAP Developer Edition using abapGit and assign the Objects to a package that is assigned to a transport request. That way you can create a transport request containing the latest abap2xlsx version. In future we might be able to use ABAP on SAP Cloud Platform to automate this process.
Best regards
Gregor
Dear Ivan, Dear Gregor,
thank you very much. I will see whether I manage to get a transport file from my developer edition.
Thank you very much,
Rainer
Dear Ivan, Dear Gregor,
I used now the export and import to and from zip file function from abapGit. I exported from my developer edition and imported into a sandbox system of my customer. This worked well. Although I was forced to repeat the import a few times (thereby sometimes overwriting "locally" changed objects or not setting the overwriting). After a few tries I was able to run ZDEMO_EXCEL without errors.
Thank you very much
Rainer
|
gharchive/issue
| 2018-03-05T13:29:31 |
2025-04-01T04:34:38.728682
|
{
"authors": [
"RainerWinkler",
"gregorwolf",
"ivanfemia"
],
"repo": "ivanfemia/abap2xlsx",
"url": "https://github.com/ivanfemia/abap2xlsx/issues/523",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
642658059
|
[Simple POC] - Implementing currency in money to support multiple currencies
Hey @ivanpaulovich, how are you?
I implemented a simple POC so we can discuss the design and you can validate if the things are in the right place.
I created a Currency value object inside Money and created the CurrencyExchangeService injecting the API.
It's not ready to go to master, it's just an example.
See ya!
Hi @vmamore,
I think we very close to merge this PR.
I reviewed, rebased and fixed minor issues I found. We still need to implement the real Exchange Service using an external API right?
What do you think about this one https://fixer.io/ ? We could request to https://data.fixer.io/api/latest
Awesome @ivanpaulovich I saw the implementation here in github, later I'm going to pull and read it all.
Thanks, see ya!
|
gharchive/pull-request
| 2020-06-21T23:11:29 |
2025-04-01T04:34:38.738799
|
{
"authors": [
"ivanpaulovich",
"vmamore"
],
"repo": "ivanpaulovich/clean-architecture-manga",
"url": "https://github.com/ivanpaulovich/clean-architecture-manga/pull/204",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
309015482
|
Project status
Hi,
What is the status of this project? What are the main changes compared to mozilla/shumway? What changes do you plan? What is the goal of this fork?
I am also interested in having a working Flash Player. I have considered forking and refactoring Shumway but eventually started a fresh project (Open Flash - but not ready yet) for architectural reasons. I also actively follow the "open source Flash" petition and related projects.
It seems that you managed to do a good chunk of work here so I'd be interested to learn more about this and hear about what you think.
The goal is to convert it to PixiJS plugin and make AVM optional. Two types of users:
Those who want move from Flash and ready to convert their code to typescript
Those who want use Animate CC to make UI and animations
There's https://github.com/ivanpopelyshev/shumway/tree/refactor-flash-base branch that is a two month behind of what i have now, I'll update it in a few days and add an example.
https://github.com/ivanpopelyshev/shumway/tree/refactor-flash-base/src/flash-legacy/statics - All classes are just general JS classes and not abominations with two prototypes. They have "_sec" injected in them, of course. All statics are stored in special objects, like companion objects in Scala or Kotlin. I create all of those objects in SecurityDomain.
I also dropped AVM support, however I'll add optional AVM2 module later, just to allow people to look how their old code works on new runtime. AVM1 should die, because its easier to just convert old FLA files with JSFL scripts than to support it.
I can launch SWF's without AVM, and my hello world example is small compared to shuobject.
I have been working on this for seven months now
Okay,
Thanks for the reply. I'll look into PixiJS and into your changes when I'll have more time.
It's nice to hear that you cleaned-up the AVM implementation: I agree that it was pretty messy.
I am happy that you managed to make the AVM optional. Just to be sure, it means that it is not shipped to the client at all? Would it be possible to pull it out of Shumway entirely and have it in a different repo (you removed the renderer dependency on the AVM but is there an AVM dependency on the renderer)?
Yes, AVM not shipped at client, at all. Yep, we'll make separate repo when example is ready.
Yeah, good thing i dont need AVM at all - I have access to commercial converter that translates huge number of lines of AS3 code to TS :) We even added int and uint types in typescript!
And now we have real problem: background appears through seams in graphics shapes. And shumway renderer cant deal with it. Do you have any ideas?
Okay, great for the VM.
Regarding the background and seams, are you referring to the issue demonstrated in this example?
<canvas id="cvs" style="background: red;" width="100" height="100"></canvas>
const cvs = document.getElementById("cvs");
const ctx = cvs.getContext("2d");
ctx.fillStyle = "white";
ctx.beginPath();
ctx.moveTo(20, 20);
ctx.lineTo(80, 20);
ctx.lineTo(80, 80);
ctx.fill();
ctx.beginPath();
ctx.moveTo(20, 20);
ctx.lineTo(20, 80);
ctx.lineTo(80, 80);
ctx.fill();
I draw two triangles forming a square but you can still see the diagonal:
This is an old issue that I found when decoding SWF shapes (already there about 8 years ago). I can think of two solutions.
Render an upscaled aliased version and then resize it. Easy but may be inefficient.
Try to do some bleeding by enlarging the shape. More complex to do right.
I believe that Adobe uses some form of the first solution by tracking the colored subpixels (it'd make sense that they use twips).
I tried to quickly apply the first solution on my canvas example but haven't really managed to do it. I need to take a closer look at it because I also encounter this problem quite often.
the only good solution i see is to render shapes in separate canvas and use additive blending there.
I remember that I "healed" exported svg file by adding a filter that removed alpha from some places.
It is done, SFW imports dont have that problem anymore. Manual graphics has, but its not important.
I sent pixijs slack invitation to you, we are forming a channel :)
|
gharchive/issue
| 2018-03-27T15:18:12 |
2025-04-01T04:34:38.748769
|
{
"authors": [
"demurgos",
"ivanpopelyshev"
],
"repo": "ivanpopelyshev/shumway",
"url": "https://github.com/ivanpopelyshev/shumway/issues/3",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
911322998
|
add SwiftUI modifier
Goal
Add SPAlert as SwiftUI modifier
Checklist
[x] Testing in iOS
[x] Installed correct via Swift Package Manager and Cocoapods
Thank you for such a beautiful library, I added SwiftUI modifier syntax for it @ivanvorobei
Wow, looks super cool!
Thanks! Soon check it deep and can merge and release.
Many users ask about it.
|
gharchive/pull-request
| 2021-06-04T09:42:40 |
2025-04-01T04:34:38.757512
|
{
"authors": [
"HonQii",
"ivanvorobei"
],
"repo": "ivanvorobei/SPAlert",
"url": "https://github.com/ivanvorobei/SPAlert/pull/32",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
680878052
|
XPC connection invalid
I'v added Privacy - Bluetooth Always Usage Description to my Info.plist and then call .bluetooth permission with SPPermissions.list([.bluetooth]) but I get [CoreBluetooth] XPC connection invalid error when I touch the Activate button and no native alert is showed.
Note that when I manually call centralManager = CBCentralManager(delegate: self, queue: nil) I get my delegate centralManagerDidUpdateState well called and native alert is showed.
I notice that in my case, centralManagerDidUpdateState in SPBluetoothPermission.swift is never called...
After investigations, it seems that the instance of SPBluetoothPermission returned by manager(for permission: SPPermission) in SPPermission.swift was released before the delegate method was called.
Temporarily, I made SPBluetoothPermission a Singleton and return SPBluetoothPermission.shared in manager(for permission: SPPermission)...
Any idea on how to improve this and fix it cleaner ?
Thanks
The same problem, how to fix it?
it's been a while since I did that but I update SPBluetoothPermission class and add a static shared property like this:
// The MIT License (MIT)
// Copyright © 2019 Ivan Varabei (varabeis@icloud.com)
//
// Permission is hereby granted, free of charge, to any person obtaining a copy
// of this software and associated documentation files (the "Software"), to deal
// in the Software without restriction, including without limitation the rights
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
// copies of the Software, and to permit persons to whom the Software is
// furnished to do so, subject to the following conditions:
//
// The above copyright notice and this permission notice shall be included in all
// copies or substantial portions of the Software.
//
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
// SOFTWARE.
#if os(iOS) && SPPERMISSION_BLUETOOTH
import UIKit
import CoreBluetooth
class SPBluetoothPermission: NSObject, SPPermissionProtocol {
static public let shared:SPBluetoothPermission = .init()
typealias SPBluetoothPermissionHandler = ()->()?
private var completion: SPBluetoothPermissionHandler?
private var manager: CBCentralManager?
var isAuthorized: Bool {
if #available(iOS 13.0, *) {
return CBCentralManager().authorization == .allowedAlways
}
return CBPeripheralManager.authorizationStatus() == .authorized
}
var isDenied: Bool {
if #available(iOS 13.0, *) {
return CBCentralManager().authorization == .denied
}
return CBPeripheralManager.authorizationStatus() == .denied
}
func request(completion: @escaping ()->()?) {
self.completion = completion
self.manager = CBCentralManager(delegate: self, queue: nil, options: [CBPeripheralManagerOptionShowPowerAlertKey:true])
}
}
extension SPBluetoothPermission: CBCentralManagerDelegate {
func centralManagerDidUpdateState(_ central: CBCentralManager) {
if #available(iOS 13.0, *) {
switch central.authorization {
case .notDetermined:
break
default:
self.completion?()
}
} else {
switch CBPeripheralManager.authorizationStatus() {
case .notDetermined:
break
default:
self.completion?()
}
}
}
}
#endif
Than I simply called it like this SPBluetoothPermission.shared instead of SPBluetoothPermission() in extension SPPermission at line 186 in method fileprivate static func manager(for permission: SPPermission) -> SPPermissionProtocol
it's been a while since I did that but I update SPBluetoothPermission class and add a static shared property like this:
// The MIT License (MIT)
// Copyright © 2019 Ivan Varabei (varabeis@icloud.com)
//
// Permission is hereby granted, free of charge, to any person obtaining a copy
// of this software and associated documentation files (the "Software"), to deal
// in the Software without restriction, including without limitation the rights
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
// copies of the Software, and to permit persons to whom the Software is
// furnished to do so, subject to the following conditions:
//
// The above copyright notice and this permission notice shall be included in all
// copies or substantial portions of the Software.
//
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
// SOFTWARE.
#if os(iOS) && SPPERMISSION_BLUETOOTH
import UIKit
import CoreBluetooth
class SPBluetoothPermission: NSObject, SPPermissionProtocol {
static public let shared:SPBluetoothPermission = .init()
typealias SPBluetoothPermissionHandler = ()->()?
private var completion: SPBluetoothPermissionHandler?
private var manager: CBCentralManager?
var isAuthorized: Bool {
if #available(iOS 13.0, *) {
return CBCentralManager().authorization == .allowedAlways
}
return CBPeripheralManager.authorizationStatus() == .authorized
}
var isDenied: Bool {
if #available(iOS 13.0, *) {
return CBCentralManager().authorization == .denied
}
return CBPeripheralManager.authorizationStatus() == .denied
}
func request(completion: @escaping ()->()?) {
self.completion = completion
self.manager = CBCentralManager(delegate: self, queue: nil, options: [CBPeripheralManagerOptionShowPowerAlertKey:true])
}
}
extension SPBluetoothPermission: CBCentralManagerDelegate {
func centralManagerDidUpdateState(_ central: CBCentralManager) {
if #available(iOS 13.0, *) {
switch central.authorization {
case .notDetermined:
break
default:
self.completion?()
}
} else {
switch CBPeripheralManager.authorizationStatus() {
case .notDetermined:
break
default:
self.completion?()
}
}
}
}
#endif
Than I simply called it like this SPBluetoothPermission.shared instead of SPBluetoothPermission() in extension SPPermission at line 186 in method fileprivate static func manager(for permission: SPPermission) -> SPPermissionProtocol
Yeah you are right.
I add a Singleton in SPBluetoothPermission.swift, such as:
static let shared = SPBluetoothPermission()
private override init() {
super.init()
}
Use 'SPBluetoothPermission.shared' at SPPermission.swift line 186.
And fork the repo, add my fix code above, create my repo.
Finally, use pod 'SPPermissions/Bluetooth', :git => 'https://github.com/xxx/SPPermissions.git''
This is just a temporary approach, but I'm still looking forward to the author's update.
Again, thank you for your help.
PS:
His reply:
@Manfred-Wang lol, autoreplay? Really?)
I have a slightly cleaner fix which simply retains the manager until the request completion block is called:
/**
Request permission now
*/
public func request(completion: @escaping ()->()) {
var manager: SPPermissionProtocol? = SPPermission.manager(for: self)
if let usageDescriptionKey = usageDescriptionKey {
guard let _ = Bundle.main.object(forInfoDictionaryKey: usageDescriptionKey) else {
print("SPPermissions Warning - \(usageDescriptionKey) for \(name) not found in Info.plist")
return
}
}
manager!.request(completion: {
completion()
// retain the manager until we're done
// fix for https://github.com/ivanvorobei/SPPermissions/issues/202
manager = nil
return ()
})
}
This seems to solve the issue for me.
Fixed in version 5.5.5. Please update pods, now should work good.
Fixed in version 5.5.5. Please update pods, now should work good.
Thanks !
|
gharchive/issue
| 2020-08-18T10:12:46 |
2025-04-01T04:34:38.769153
|
{
"authors": [
"Bejil",
"Manfred-Wang",
"gumbypp",
"ivanvorobei"
],
"repo": "ivanvorobei/SPPermissions",
"url": "https://github.com/ivanvorobei/SPPermissions/issues/202",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
185180443
|
Incompatible with Python 3
I tried to check some Python3 project and found out that this image incompatible with Py3K features and syntax. For example, flake8 throws NameError at FileNotFoundError and throws SyntaxError at PEP 484 (type hints) syntax.
yeah - this tool was never tested vs. Python 3 projects. We're just preparing to migrate our projects to Python 3, so that wasn't a priority previously, but most likely will become a priority soon. BTW contributions are welcome )
I think we can close this issue, base Python 3 image can do codestyle checks for Python 2 projects as far as Py2 version uses Py3-compatible code. And we should consider it's a bug if such errors exists in first place.
|
gharchive/issue
| 2016-10-25T17:19:47 |
2025-04-01T04:34:38.774032
|
{
"authors": [
"stebunovd",
"valentjedi"
],
"repo": "ivelum/codestyle",
"url": "https://github.com/ivelum/codestyle/issues/1",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
456179874
|
Major Issue 3MB image getting 22MB after save.
There is a major issue when i am uploading and saving 3MB image its getting 22MB after save. It will slow my application if we go with this issue. Please resolve it asap. Thanks!
Thanks for issue posting, please debug saving chain in painterro and create PR for fix if you will find reason. Saving there is pretty simple it just involves builtin canvas methods
My save handler:
saveHandler: function (image) {
var tImg = new Image();
tImg.src = image.asDataURL();
tImg.onload = function () {
ctx.drawImage(tImg, 0, 0);
var content = canvas.toDataURL('image/jpeg');
$('.tool_ajupload_content').val(content);
$('.fm_ajuploadhere').submit();
$('[title="Close Painterro"]').click();
}
}
asDataURL('image/jpg') do not affect type, return png anyway.
@SeibelStan There is no such mime type like image/jpg' https://stackoverflow.com/a/37266399/3479125
Где у меня jpg? Везде jpeg и в коде я значения по-умолчанию пробовал ставить на jpeg, всё равно png отдаёт, перегоняю через свой канвас, пока такой костыль.
asDataURL хоть принимает тип, реально его не применяет. Собранный исходник без сокращения имён давать не хочешь, так что даже не могу разобраться куда ставить. Я не фронтендер, в сборщики влазить не планировал как класс. Собранный жс отладить скорее всего могу.
@SeibelStan
Then you made the wrong statement in a comment:
All unminified sources are in the repo and they require bundling, we have no other sources. The minified file is a result of bundler, it is not a source
Неважно, всяко пробовал, и в параметр и в коде менял, в коменте просто опечатка, как-то же я сделал через свою канву в итоге.
Я понимаю что это не исходник, но в src подключается билд, и можно сделать билд без сокращения имён, не говори что невозможно.
Имеет смысл сделать жпег по-умолчанию, 99,9% там рисуют стрелочки на фотографиях потом неприятно удивляются что размер вырос в 10 раз. Для точной передачи есть блоб уже.
Tested on index.html test page, works exactly as designed for me. @SeibelStan I think you doing something wrong.
<button onclick="saveTest()">Save</button>
...
function saveTest() {
const u = window.p.imageSaver.asDataURL('image/jpeg');
console.log('saved', u.length, u);
}
function saveTest() {
const u = window.p.imageSaver.asDataURL('image/png');
console.log('saved', u.length, u);
}
Feel free to create an issue with specifying exact steps to reproduce
|
gharchive/issue
| 2019-06-14T10:37:34 |
2025-04-01T04:34:38.781883
|
{
"authors": [
"SeibelStan",
"ivictbor",
"paritoshcardinal"
],
"repo": "ivictbor/painterro",
"url": "https://github.com/ivictbor/painterro/issues/57",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
2584233578
|
🛑 21Eurkon is down
In b575311, 21Eurkon (https://blog.eurkon.com/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: 21Eurkon is back up in a387d2a after 23 minutes.
|
gharchive/issue
| 2024-10-13T19:59:44 |
2025-04-01T04:34:38.843376
|
{
"authors": [
"iwyang"
],
"repo": "iwyang/check",
"url": "https://github.com/iwyang/check/issues/10085",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1228644037
|
🛑 Nekolas's Blog is down
In 9f4763b, Nekolas's Blog (https://blog.nekolas.cafe/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Nekolas's Blog is back up in e6884ea.
|
gharchive/issue
| 2022-05-07T14:36:20 |
2025-04-01T04:34:38.845734
|
{
"authors": [
"iwyang"
],
"repo": "iwyang/check",
"url": "https://github.com/iwyang/check/issues/1220",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1007392833
|
🛑 Takagi is down
In 6dd0af7, Takagi (https://lixingyong.com) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Takagi is back up in 2d26d78.
|
gharchive/issue
| 2021-09-26T13:31:10 |
2025-04-01T04:34:38.848005
|
{
"authors": [
"iwyang"
],
"repo": "iwyang/check",
"url": "https://github.com/iwyang/check/issues/509",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2523293726
|
🛑 21Eurkon is down
In 0268cbe, 21Eurkon (https://blog.eurkon.com/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: 21Eurkon is back up in 834c7dc after 11 minutes.
|
gharchive/issue
| 2024-09-12T20:27:53 |
2025-04-01T04:34:38.850301
|
{
"authors": [
"iwyang"
],
"repo": "iwyang/check",
"url": "https://github.com/iwyang/check/issues/9546",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
785746636
|
Modernize the ixo address generation function
Apparently the "bytes" value for the crypto's digest function's
"encoding" argument is deprecated. It looks like it was used to
make the function output a Buffer data type, but the digest
function is currently behaving the same way even if we don't
specify an encoding.
This is no big deal in Node environments as it seems like this
legacy argument is still supported, but it breaks when we use the
React Native shim for crypto. One can say that it is susceptible
of breaking in similar scenarios.
Removing this parameter seems to be safe, in my experiments it
worked in both Node and the shimmed RN environments.
References:
https://github.com/mvayngrib/react-native-crypto
https://nodejs.org/api/crypto.html#crypto_hash_digest_encoding
https://nodejs.org/api/buffer.html#buffer_buffers_and_character_encodings
Sounds good @gwn. I've tested out quickly locally and it looks OK.
Sounds good @gwn. I've tested out quickly locally and it looks OK.
Thank you for dealing with this quickly!
Thank you for dealing with this quickly!
|
gharchive/pull-request
| 2021-01-14T07:20:22 |
2025-04-01T04:34:38.860513
|
{
"authors": [
"gwn",
"migueldingli1997"
],
"repo": "ixofoundation/cosmosjs",
"url": "https://github.com/ixofoundation/cosmosjs/pull/3",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2139630452
|
🛑 Ixtanet Main is down
In 30ed590, Ixtanet Main ($MAIN_ROUTER) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Ixtanet Main is back up in d39ba44 after 22 minutes.
|
gharchive/issue
| 2024-02-16T23:29:08 |
2025-04-01T04:34:38.862875
|
{
"authors": [
"aalonzolu"
],
"repo": "ixtanet/upptime",
"url": "https://github.com/ixtanet/upptime/issues/1243",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2203606842
|
🛑 N IXTANET is down
In b8c4a18, N IXTANET ($N_IXTANET) was down:
HTTP code: 0
Response time: 0 ms
Resolved: N IXTANET is back up in 673f909 after 32 minutes.
|
gharchive/issue
| 2024-03-23T01:26:54 |
2025-04-01T04:34:38.865001
|
{
"authors": [
"aalonzolu"
],
"repo": "ixtanet/upptime",
"url": "https://github.com/ixtanet/upptime/issues/1291",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2616191296
|
🛑 Purificadora Ixtatan is down
In 2db09ee, Purificadora Ixtatan ($WEB_PURIFICADORA_IXTATAN) was down:
HTTP code: 523
Response time: 764 ms
Resolved: Purificadora Ixtatan is back up in 4c83101 after 10 minutes.
|
gharchive/issue
| 2024-10-26T22:47:26 |
2025-04-01T04:34:38.867332
|
{
"authors": [
"aalonzolu"
],
"repo": "ixtanet/upptime",
"url": "https://github.com/ixtanet/upptime/issues/1766",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
191076719
|
Update Robinhood jobs url
The Robinhood jobs page has changed - this is the canonical url.
Awesome! Thanks a ton for contributing :)
|
gharchive/pull-request
| 2016-11-22T17:44:19 |
2025-04-01T04:34:38.932274
|
{
"authors": [
"j-delaney",
"jbinney"
],
"repo": "j-delaney/easy-application",
"url": "https://github.com/j-delaney/easy-application/pull/76",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
646525556
|
Fix NPE if value is null
This is a FIX suggestion for a NPE when a value is null on a POJO.
Thank you for the PR. Since we are getting the value by calling a getter method, we can use the return type of that getter to get the sql type instead of the value's class, something like:
-- Object value = propertyDescriptor.getReadMethod().invoke(record);
-- Integer sqlType = javaTypesToSqlTypes.get(value.getClass());
++ Method readMethod = propertyDescriptor.getReadMethod();
++ Integer sqlType = javaTypesToSqlTypes.get(readMethod.getReturnType());
++ Object value = readMethod.invoke(record);
The getter method should be there (by definition of a javabean). This approach avoids an additional check in the prepareStatement method which starts to become a bit complex already..
Do you agree? If you agree, please update the PR accordingly and it will be good to merge.
I've changed per your suggestion.
Now I have a problem because my Use Case is a little bit "akward". I generate my beans at runtime an don't know the type of the objects my field will have so all my field have the type java.lang.Object. The way I had it, the SQL type would be inferred by the value of the object and that would work. This way it won't (for my use case) recognize the SQL type. Maybe I'll have to stick with a forked version after all...
For my side I would always have to re-implement the prepareStatement method. Would it be okay to move private properties to protected, so I could extend this class, instead of having to make a copy of it to change the method prepareStatement?
LGTM. Rebased, squashed and merged as 0babc6ff643d0fd1ee495ce524520170f1983476.
If you need to fork the project (or one of its classes), that means there is something wrong with Easy Batch! The BeanPropertiesPreparedStatementProvider is designed for regular JavaBeans. Your use case is very specific, so I would keep the implementation targeted at the majority of use cases, and make it possible to extend the default behaviour for specific cases (I made all fields protected as you suggested, see 5e541f8ba550a441da35fd15e63c54d0699c9116).
You can already try that in 6.1.0-SNAPSHOT.
Thank you for your PR!
|
gharchive/pull-request
| 2020-06-26T21:39:55 |
2025-04-01T04:34:38.936003
|
{
"authors": [
"benas",
"seseso"
],
"repo": "j-easy/easy-batch",
"url": "https://github.com/j-easy/easy-batch/pull/376",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2323918402
|
資料集問題
想請教作者資料集的部分是怎麼做處理的?
因為與原始數據不同
以PEMS03舉例，原始npz shape=(26208, 358, 1)，但作者提供的已拆分好
並且變成(15711, 12, 358, 1) 多了12
也多了x和y
想詢問12和x,y各代表什麼意思?
謝謝
您好，假设单个节点的26帧序列值是[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]，shape即（26,1,1）,我们的任务是已知前面12帧数值预测后面12帧数值，例如已知[2,3,4,5,6,7,8,9,10,11,12,13]，预测出结果[14,15,16,17,18,19,20,21,22,23,24,25]，则前面12帧构成的即是模型输入x，后面12帧即是输出y。对于上面26帧序列，我们可以构建26-24+1=3个这样的xy对，则每个输入集合x和输出集合y的shape分别对应（3,12,1,1）。
15711是(26208-24+1)*0.6计算得到，故x和y的shape是（15711,12,358,1）。
|
gharchive/issue
| 2024-05-29T17:56:38 |
2025-04-01T04:34:38.943416
|
{
"authors": [
"j1o2h3n",
"yunxin108"
],
"repo": "j1o2h3n/DDSTGCN",
"url": "https://github.com/j1o2h3n/DDSTGCN/issues/4",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
172258346
|
Add favorite locations
Hi j2rong,
I really love FakeLocation is a neat and really useful tool. However there is one thing your app is missing: a feature to search locations instead of having to pin locations zooming in a map OR a feature to save places as favorites and being able to use them later. If you could add one of these features, you would save users a lot of time.
Please consider adding this.
Thanks for your hard work!
Nice idea!
Yesheepeedag@gmail.com
|
gharchive/issue
| 2016-08-20T07:15:57 |
2025-04-01T04:34:38.945433
|
{
"authors": [
"Pcsl",
"roylaprattep",
"tzr3565"
],
"repo": "j2rong/FakeLocation",
"url": "https://github.com/j2rong/FakeLocation/issues/20",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
236751590
|
Installing On Ubuntu 16.04 lts
Im trying to install polybar but Im getting this message
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
polybar : Depends: libstdc++6 (>= 6) but 5.4.0-6ubuntu1~16.04.4 is to be installed
E: Unable to correct problems, you have held broken packages.
Since you are installing polybar from a repository, someone has already successfully compiled polybar. This is an issue with either your system (see the note about broken packages) or an issue with the packager not listing dependencies properly.
|
gharchive/issue
| 2017-06-18T23:09:59 |
2025-04-01T04:34:38.984210
|
{
"authors": [
"BenderFendor",
"patrick96"
],
"repo": "jaagr/polybar",
"url": "https://github.com/jaagr/polybar/issues/621",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
142619077
|
Hw finished
We have finished our homework which can be found here: https://github.com/bjur/SAT_solver.git
Have a nice day, B
I've added a link to the latest commit. Please let me know if you change anything before the deadline, so I can update the link.
We made a couple fixes, and we apologise for inconvenience.
On Tue, Mar 22, 2016 at 12:24 PM, Janoš Vidali notifications@github.com
wrote:
I've added a link to the latest commit. Please let me know if you change
anything before the deadline, so I can update the link.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/jaanos/LVR-2016/issues/1#issuecomment-199767995
OK, updated.
|
gharchive/issue
| 2016-03-22T11:13:53 |
2025-04-01T04:34:38.992332
|
{
"authors": [
"bjur",
"jaanos"
],
"repo": "jaanos/LVR-2016",
"url": "https://github.com/jaanos/LVR-2016/issues/1",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
218730550
|
启动报关于图片模块导入的错误，希望可以指导下哈
ERROR in ./~/.6.4.1@babel-loader/lib!./~/.1.7.1@eslint-loader!./~/.8.7.0@vue-loader/lib/selector.js?type=script&index=0!./src/components/Navbar.vue
Module not found: Error: Cannot resolve module 'image-webpack' in /Users/jinyunyan/Desktop/test/vuetest/jackblog-vue/src/components
@ ./~/.6.4.1@babel-loader/lib!./~/.1.7.1@eslint-loader!./~/.8.7.0@vue-loader/lib/selector.js?type=script&index=0!./src/components/Navbar.vue 9:14-52
ERROR in ./~/.6.4.1@babel-loader/lib!./~/.1.7.1@eslint-loader!./~/.8.7.0@vue-loader/lib/selector.js?type=script&index=0!./src/components/Article/comment.vue
Module not found: Error: Cannot resolve module 'image-webpack' in /Users/jinyunyan/Desktop/test/vuetest/jackblog-vue/src/components/Article
可能需要安装libpng这东东.
|
gharchive/issue
| 2017-04-01T23:42:55 |
2025-04-01T04:34:39.023349
|
{
"authors": [
"jackhutu",
"yanjinyun"
],
"repo": "jackhutu/jackblog-vue",
"url": "https://github.com/jackhutu/jackblog-vue/issues/14",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.