bug: error when 'dataset' is not defined in metadata, KeyError: 'dataset'

Sometimes, we do not want to define the field dataset in a Garden step. This might be because we have already defined the dataset in previous stages (Snapshot or Meadow).
Ideally, not defining the field dataset should signal that we want ETL to propagate whatever it has from before.
However, this fails at the moment with a KeyError error. Example of error:
ds_garden = create_dataset(dest_dir, tables=[tb_garden], default_metadata=ds_meadow.metadata)
  File "/home/lucas/repos/etl/etl/helpers.py", line 138, in create_dataset
    ds.update_metadata(N.metadata_path)
  File "/home/lucas/repos/etl/vendor/owid-catalog-py/owid/catalog/datasets.py", line 157, in update_metadata
    self.metadata.update_from_yaml(metadata_path, if_source_exists=if_source_exists)
  File "/home/lucas/repos/etl/vendor/owid-catalog-py/owid/catalog/meta.py", line 178, in update_from_yaml
    dataset_sources = annot["dataset"].get("sources", []) or []
KeyError: 'dataset'

A current workaround is to define dataset: {} in the metadata YML file.
[Related slack thread]

@lucasrodes you might have an old version of catalog. This has been fixed about a month ago.

@Marigold, thanks for your help. Indeed, I had an old owid-catalog-py version. To update I simply ran:
cd vendor/owid-catalog-py
git pull


Add layers highlighting and layers assertions

Assert no dependencies between features
Assert no dependencies against layer hierarchy
Draw dependency graph with layers

This PR was released with 0.22.1


去除重复代码

@arnaudbos can you explain what you mean further?

Ahh, I see what you are saying. Good point!


FRDM-K22F: When using I2C there is no console output on CDC

I've ran I2C tests with 24LC256 (EEPROM) and I notices no printouts are send via virtual serial port.
I can see when I run tests, they pass (red LED blink with "OK" low frequency) but no output on USB serial port.
I've checked with logical analyzer I2C, it looks OK (e.g. frequency was 400kHz and transmission was uninterrupted).

singletest.py -i test_spec.json -M muts_all.json -P -V

Building library CMSIS (K22F, ARM)
Building library MBED (K22F, ARM)
Building project I2C_EEPROM (K22F, ARM)
Compile: main.cpp
Link: i2c_eeprom
Elf2Bin: i2c_eeprom
Executing 'python host_test.py -d G:\ -f "C:\Work\mbed\build\test\K22F\ARM\MBED_A19\i2c_eeprom.bin" -p COM93 -t 15 -C 4 -m K22F'
Test::Output::Start
MBED: Instrumentation: "COM93" and disk: "G:\"
HOST: Copy image onto target...
HOST: Initialize serial port...
HOST: Reset target...
Test::Output::Finish
TargetTest::K22F::ARM::MBED_A19::I2C EEPROM read/write test [TIMEOUT] in 30.95 of 15 sec
Building project I2C_EEPROM_LINE (K22F, ARM)
Compile: main.cpp
Link: i2c_eeprom_line
Elf2Bin: i2c_eeprom_line
Executing 'python host_test.py -d G:\ -f "C:\Work\mbed\build\test\K22F\ARM\MBED_A25\i2c_eeprom_line.bin" -p COM93 -t 10 -C 4 -m K22F'
Test::Output::Start
MBED: Instrumentation: "COM93" and disk: "G:\"
HOST: Copy image onto target...
HOST: Initialize serial port...
HOST: Reset target...
Test::Output::Finish
TargetTest::K22F::ARM::MBED_A25::I2C EEPROM line read/write test [TIMEOUT] in 20.96 of 10 sec
Test summary:
+---------+--------+-----------+----------+---------------------------------+--------------------+---------------+-------+
| Result  | Target | Toolchain | Test ID  | Test Description                | Elapsed Time (sec) | Timeout (sec) | Loops |
+---------+--------+-----------+----------+---------------------------------+--------------------+---------------+-------+
| TIMEOUT | K22F   | ARM       | MBED_A19 | I2C EEPROM read/write test      |       30.95        |       15      |  0/1  |
| TIMEOUT | K22F   | ARM       | MBED_A25 | I2C EEPROM line read/write test |       20.96        |       10      |  0/1  |
+---------+--------+-----------+----------+---------------------------------+--------------------+---------------+-------+
Result: 2 TIMEOUT

Completed in 55.51 sec

@0xc0170 promised me a hug if I would solve this, and I am desperate for hugs :(.
Pinout:
// USB Pins
USBTX = PTE0,
USBRX = PTE1,
Test pinout:
#elif defined(TARGET_K22F)
I2C i2c(PTE0, PTE1);
Woohoo, free hug. (In other words: Use different pins, A4, A5 which are the Arduino I2C pins should work probably).

Thanks Erik for looking at it. We should update I2C tests to include other pins, as obviously they overlap with USBxX

No free hugs
#elif defined(TARGET_K64F)
I2C i2c(PTE25, PTE24);

#elif defined(TARGET_K22F)
I2C i2c(PTE0, PTE1);

#elif defined(TARGET_K20D50M)
I2C i2c(PTB3, PTB2);

Pin out is set in test for K22F.

@PrzemekWirkus those 2 are used by serial object as TX and RX therefore it fails to print anything


FRAME: General storage-usage system

At present, when a pallet uses storage, we have a pattern of using a ReservableCurrency item in the Config as well as a Byte and (storage) Item deposit amount. The pallet manually reserves and refunds these deposits as the data stored changes. This is cumbersome, error-prone and forces pallets which use storage to know about and commit to the ReservableCurrency trait.
Instead there should just be a general API (in System, probably) to note that storage usage within a pallet is about to change (including the number of items and total bytes used by them which will be in storage) and make appropriate preparations for it. There can be a default implementation for this which updates funds on hold (or perhaps just frozen).

We implemented storage meter for Acala EVM+ to handle this for EVM storage. Similar pattern could apply here.

I did some prototypes on a HookedMap that could be a useful primitive to do this. The hooks can reserve and un-reserve automatically

As a simple way forward I was thinking something like:
pub struct Footprint {
  items: u32,
  len: u32,
}
impl Footprint {
  fn from_encodable(e: impl Encode) -> Self {
    Self { items: 1, len: e.encode_len() as u32 }
  }
}
pub trait StorageConsideration<AccountId> {
  type Consideration: Encode + Decode + Default + ...;
  fn update_consideration(who: &AccountId, old: Option<Consideration, Footprint>, Option<Footprint>) -> Result<Consideration, DispatchError>;
}

There could be an adapter struct which takes a fungible impl and DepositPerItem, DepositPerByte impls of Get; this could be also be a default config trait item, so easily available to every pallet.
Usage would basically just be:
// put a 32-byte datum in storage
let v = vec![0u8; 32];
let c = T::StorageConsideration::update_consideration(who, None, Some(Footprint::from_encodable(v)))?;
SomeStorageMap::<T>::insert(who, (c, v));

// the 32-byte datum becomes a 64-byte datum...
let (old_c, old_v) = SomeStorageMap::<T>::get(who);
let v = vec![0u8; 64];
let c = T::StorageConsideration::update_consideration(who, Some(old_c, Footprint::from_encodable(old_v)), Some(Footprint::from_encodable(v)))?;
SomeStorageMap::<T>::insert(who, (c, v));

// the data is removed
let (old_c, old_v) = SomeStorageMap::<T>::get(who);
let c = T::StorageConsideration::update_consideration(who, Some(old_c, Footprint::from_encodable(old_v)), None)?;
SomeStorageMap::<T>::remove(who);


support AWS secret manager

Request
I want to be able to retrieve values from AWS Secret Manager in Grafana Alloy and make them available for use in Alloy's configuration.
Use case
The following is used in scenarios that require sensitive information:
metrics.remote_write "prod" {
  remote_write {
    url = "https://mimir:9009/api/v1/push"
    basic_auth {
      username = remote.awssecretsmanager.remote_write.data.username
      password = remote.awssecretsmanager.remote_write.data.password
    }
  }
}

I think its a good enhancement to add into Alloy's AWS components. I'll draft up something this weekend 🥸

In the case of Kubernetes, using External Secrets to store secret information in environment variables can avoid this issue. For EC2, it was necessary to have a mechanism to retrieve secrets using systemd's ExecStartPre
Thank you for taking an interest in this feature enhancement😊

@hainenber
Thank you for responding promptly! 😄
I've been interested and have done a bit of coding.
https://github.com/grafana/alloy/compare/main...fabiiw05:alloy:add_component_aws_secretsmanager
Lately, I haven't had much time, so it doesn't seem like I'll be able to finish it. I'm not confident in my programming skills, but I thought I'd share it in case it's useful to someone.


AL2022 not reporting all disk stats metrics

Harvest tests are failing:
--- FAIL: TestStorageSample (0.00s)
    storage_sampler_linux_test.go:64:
        	Error Trace:	storage_sampler_linux_test.go:64
        	Error:      	Expected value not to be nil.
        	Test:       	TestStorageSample

The problem is that the latest released AMI for AL2022 (current issue date) does not report some metrics that are available in /proc/diskstats, for example, the ReadBytesPerSec,  WriteBytesPerSec, ReadWriteBytesPerSecond.
This issue is keep updating the AL2022 AMI on our canaries till the issue is solved (it seems an internal error of the kernel version)

Metrics not available in the kernel:

Closing this issues as harvest tests failure is not related to the agent misbehavior, instead, an AL2022 current AMI kernel issue.
Next releases of the AMIs should fix the issue.


use dapr.io/enable-debug: "true" to debug dapr failed

When I tried to debug dapr following the steps in the document Doc address the pod failed to start.
kubectl describe pod nodeapp-7659cb75f6-cf28b
 Warning  Failed     2m37s (x4 over 3m45s)  kubelet            Error: failed to start container "daprd": Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"/dlv\": stat /dlv: no such file or directory": unknown

Version Info:
kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-12T14:11:29Z", GoVersion:"go1.16.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-12T14:12:29Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"linux/amd64"}

minikube version
minikube version: v1.21.0
commit: 76d74191d82c47883dc7e1319ef7cebd3e00ee11

@artursouza triaged/resolved maybe mislead, triaged/wait for resolved is better I think

/assign

I can investigate this further tomorrow. @daixiang0 You can go ahead if you are interested in this.

@CodingSinger did you follow the instruction https://docs.dapr.io/zh-hans/developing-applications/debugging/debug-k8s/debug-dapr-services/ to rebuild binaries and docker images?

Root cause is that images from dockerhub do not support debug, if do not build, it would crash into error.
I have tested twice at local, one without build and fail, one with build and succeed.

Root cause is that images from dockerhub do not support debug, if do not build, it would crash into error.
I have tested twice at local, one without build and fail, one with build and succeed.

i follow the instruction to build docker images success.  But when I deployed on minikube,  reported an error “runAsUser container has runAsNonRoot and image has non-numeric user (root)”

@CodingSinger yep, I have met it too, you can update charts as pr shows.

@CodingSinger yep, I have met it too, you can update charts as pr shows.

i pick this pr, but error is still there.

cannot reproduce it at local, @beiwei30 please help look, I guess #3296 may fix.


Trying to access a sub route under an already mounted route does not trigger wildcard pattern

I'm trying authenticated routes with permissions. I'm following a similar method explained in here: https://frontarm.com/navi/en/guides/authenticated-routes/#setting-authentication-state
On wildcard stage, I use a method to authorize routes by comparing required permissions to access the route against permissions that the logged in user have to have more granular control over every route.
export default mount({
  '*': map((request, context) => {
    const { authService, } = context;
    if(!authService.currentUser) {
      const originalUrl = encodeURIComponent(request.originalUrl);
      return redirect(
        `${routeRegistry.login.path}?redirectTo=${originalUrl}`,
        {exact: false,}
      )
    }

    const route = RouteAuthorizer(request, authService.currentUser);
    if (route) {
      return mount(route);
    }
  }),
  [routeRegistry.root.path]: redirect(routeRegistry.login.path),
  [routeRegistry.login.path]: mount(routes[routeRegistry.login.path].route),
});

I have all the routes listed and I use a separate method to authorize routes.
// routes authorizer
export default (req, userObj) => {
  const { path, } = req;
  const { route, permissions, } = Routes[path];
  if (permissions && permissions.length > 0) {
    if (!(userObj && isAuthorized(userObj.abilities, permissions))) {
      return null;
    }
  }
  return {
    [path]: route,
  };
};

// Routes registry
export default {
[routeRegistry.courses.path]: {
    permissions: routeRegistry.courses.permissions,
    route: route({
        title: 'Your courses',
        view: <Courses/>,
    }),
  },
  [routeRegistry.courses.courseDetail.path]: {
    permissions: routeRegistry.courses.courseDetail.permission,
    route: route({
      title: 'Specific course',
      view: <Course/>,
    }),
  },
  ...
}

The issue I'm facing is when I'm trying to navigate to a page while it's parent route is already being mounted.
Ex: I'm trying to access courses/1 but courses/ is already mounted. So instead of going through the wildcard it jumps straight into courses/ route.
Is there a way for me to force each path as unique?
Or do you have a different pattern you use to achieve the same functionality?

I'm having trouble understanding the above code, so just to confirm that I understand, it sounds like the issue is that you have something like:
mount({
  '/courses': route(...),
  '/courses/:id': route(...)
})

And the issue is that /courses and /courses/:id have different permissions?
If this is the case, usually what I'd do is something like this:
mount({
  '/courses': mount({
    '/': route(...)
    '/:id': route(...)
  })
})

Not sure if this answers your question though. If not, it'll be easier to help if you can simplify the example down to the minimal possible size.

Yea sorry about that. Let me try to explain again.
So what I'm trying to achieve is to authorize routes by their permissions. So the logged in user have a set of permissions and a route have a set of permissions which are required for user to access that route.
The authorization process happens inside the wildcard route.
I'm keeping all the routes in a flat object without any nestings. This is because I want to have more granular control over each and every route.
This is how the routes registry looks like:
{
  'courses/': {
    permissions: ...,
    route: {
      '/': route({
        title: 'Your courses',
        view: <Courses/>,
      }),

    },
  },
  'courses/:id': {
    permissions: ...,
    route: route({
      title: 'Specific course',
      view: <Course/>,
    }),
  },
  'courses/create': {
    permissions: ...,
    route: route({
      title: 'Create new course',
      view: <CourseCreate/>,
    }),
  },
}

Lets say user is trying to access courses/ route, since it hasn't being mounted yet.

The request will invoke wildcard route. Then the authorization process happens and if user has necessary permissions and route will get mounted.
Then the user tries to access courses/create route. Since the courses/ route is already mounted, the request will go to courses/ route instead of wildcard and I'm not able to do the authorization process.

What I want to do is to force Navi to route to wildcard route if the path has not being mounted yet disregarding the parent route.
Is this clear enough?

So the way that Navi routes work, if you add a /courses route, then any URL starting with /courses will be routed through it -- it's not actually possible to route these to the wildcard instead.
The reason for this is to do with code splitting. For example, frontarm.com has a route that looks like this:
mount({
  '/courses': lazy(() => import('./courses'))
})

The ./courses file won't actually be loaded until it is first requested, and because of that, it's impossible to know whether it is a single route, or a mount() that holds a bunch of nested routes.
The thing is, a mount() doesn't actually know anything about what its paths are mapped to. Matchers like mount() and route() return plain old functions -- they're a lot like React components. So even if you mount a plain old route at /courses, mount() doesn't know this, and it'll still pass every request that begins with /courses/ through that route.
The simplest way to fix this is to just name your index route differently to your individual course routes, e.g.
mount({
  '/courses': route(...),

  // notice that this isn't a plural
  '/course/:id': route(...),
})

You could even place a redirect within /courses, using a nested mount:
mount({
  '/courses': mount({
    '/': route(...),
    '/:id': redirect(({ params }) => '/course/'+encodeURICompoent(params.id))
  })
})

I see. Thank you for the clear explanation!

The problem here was that when accessing subroutes it tried to look for the subroute in the routes group.

Explained in this unfiltered text from our internal discussion

It lies inside this line:
const selectedRoute = Routes[path];
You do this
const { path, } = req;
This means that you are trying to get this json object with this value
/courses/42589650-ae1c-11e9-99e2-d58b15df4bbf
const route = routes[`/courses/42589650-ae1c-11e9-99e2-d58b15df4bbf`]

route === undefined #true

So in index.js it then tries to redirect to that same path and that fails, because nothing is mounted.
So what happens with this approach you are basically trying to make another router on top of a router system. That is not optimal.
Either you can do some regex and load the right route block, which is courses. You can regex the root route and fetch out that bolk of routes. Then you can keep the redirect and the route loads properly.
So as long as you only the bolk of navi routes from the first bolk we can be good. But we need to remember to not build a complex stuff ontop of a well suited router.

But @jamesknelson, I might be wondering if we are going about this in the wrong approach. Because we are using permissions to restrict the routs you are trying to restrict. But I feel that we are building a strange layer on top of a router. Any thoughts here?

This is hard to say without a lot more familiarity with the code.
The way I see it, is that Navi is a library for implementing routing, just like React is a library for building UIs. I try and keep the feature set as minimal as possible - in fact, some features will probably be removed before 1.0. As a result of this, you may sometimes need to build abstractions on top of the router to get the behavior that you want, which is absolutely okay.
On the other hand, if you don't need to build an abstraction on top of the router, then it's probably best to avoid it. From what I've seen, I feel like there must be a way to make it work reasonably well without abstractions, but only your team has the familiarity required to make that decision.

@jamesknelson thanks for those wise words!


Revert "Minor: remove unnecessary projection in `single_distinct_to_g…

…roup_by` rule (#8061)"
This reverts commit 15d8c9bf48a56ae9de34d18becab13fd1942dc4a.
Which issue does this PR close?

Closes https://github.com/apache/arrow-datafusion/issues/8175
Closes https://github.com/apache/arrow-datafusion/pull/8178
Rationale for this change
Revert the change as it introduced bugs

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

@alamb @haohuaijin

Looks like @NGA-TRAN  and I both added the test (sorry I didn't see https://github.com/apache/arrow-datafusion/pull/8178) . Since this one is green let's merge it .

Thanks again @NGA-TRAN

Thanks for this fix @NGA-TRAN @alamb . I apologize for introducing this bug. The issue arises from mishandling aliases in the group by clause. Consequently, any queries like the following will result in errors in #8061：
select a+1 as alias, count(distinct b) from t group by alias

Thanks again @NGA-TRAN @alamb


What/where is 85_otus-filtered.qza?

This files appears for the first time in the tutorial during taxonomic filtering, and then it is already an input file. I couldn't find it in the tutorial_data folder.

I think this is addressed in #9. It was an older version of tutorial before i decided I wanted an integrated synthetic data and reference set.

I think this is addressed in #9. It was an older version of tutorial before i decided I wanted an integrated synthetic data and reference set.


filesys/nullFilter crashes

Repro steps-

Git clone this repo
Go to filesys/miniFilter/nullFilter, open solution file in visual studio
Launch a 10586 windows 10 vhd in hyper-v
According to this page, run the following commands and reboot
a) bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
b) bcdedit -set TESTSIGNING ON
Copy the nullFilter.sys to guest VM
Run ' sc create nullfilter type=filesys binpath=c:\temp\nullFilter.sys' to install the driver
Run sc start null filter
Guest VM bluescreen with error message something like "THREAD_EXCEPTION_UNHANDLED"

Not sure if it's because I'm not deploying the driver correctly.

Fixed the issue by installing from the inf file.


Need to delete old site (Help needed)

Hi.
Just love this "tool"   Can someone help me please?  How do I delete on old Site?

Delete it from what?

Delete it from what?

Tags in influxdb and probably prometheus too, cannot be deleted. You need to nuke the entire database and start over.
https://github.com/unifi-poller/unifi-poller/wiki/InfluxDB#influxdb

Tags in influxdb and probably prometheus too, cannot be deleted. You need to nuke the entire database and start over.
https://github.com/unifi-poller/unifi-poller/wiki/InfluxDB#influxdb


test(NODE-5617): fix explain tests

Description
Fixes explain tests to be able to handle SBE and non SBE explain results.
What is changing?
Looks for specific strings the JSON stringified version of the explain results. Not that SBE results do not contain an "allPlansExecution" or "executionStats" fields so those assertions were removed.
Is there new documentation needed for these changes?
None
What is the motivation for this change?
NODE-5617

Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: type(NODE-xxxx)[!]: description

Example: feat(NODE-1234)!: rewriting everything in coffeescript

[x] Changes are covered by tests
[ ] New TODOs have a related JIRA ticket

Do we have a backport ticket for this?  5.x is failing as well.

Do we have a backport ticket for this? 5.x is failing as well.

I created subtasks for each now and opened https://github.com/mongodb/node-mongodb-native/pull/3894


Using delayed for item assignment in loop to dask array

I'm attempting to parallelize a function that produces a 2D slice of 3D array by making the function that creates the slice a delayed object, and then assigning the result to a chunked array in a while loop as shown here:
    @delayed
    def doPlane(*args):
        ...
        #something that makes a 2D array of shape NxM
        return slice

    F0 = da.zeros([N,M,P],dtype=np.double,chunks=(N,M,1))
    i = 0
    while i < P:
        F0[:,:,i] = doPlane(*args)
        i += 1
    return F0.compute()

however this isn't how to do it because doPlane returns delayed object, and F0[:,:,i]=... is trying to set a delayed object in those indices. How can I make this compute graph and have dask dynamically schedule it?

The suggested approach is something like this:
    planes = []
    i = 0
    while i < P:
        planes.append(da.from_delayed(doPlane(*args), (N, M), float))
        i += 1
    F0 = da.stack(planes, axis=-1)
    return F0.compute()

I see that @shoyer has just answered this.  I'll stop typing and just send what I had.  Also, these sorts of "how do I do X" questions are also welcome on Stack Overflow with the #dask tag.
You might consider converting each delayed object into a dask array
arrays = [da.from_delayed(delayed_obj, shape=..., dtype=...) for delayed_obj in delayed_objs]

and then stack them together using da.stack
F0 = da.stack(arrays, axis=0)

Generally speaking inplace operations are not well supported.

@mrocklin Thanks, I'll use SO in the future!


[Usage]: How to make model response information appear in the vllm backend logs

Your current environment
I am deploying a qwen2.5-7b model via vllm serve Qwen/Qwen2.5-7B-Instruct with api calls using the langchain framework.
vllm serve Qwen/Qwen2.5-7B-Instruct

But in the process of using it, I found that the vllm background log only records the log of requests to llm, and does not record the log of llm replies, which is very inconvenient in program debugging.

I would like to know how to make vllm background log can record model reply information in real time.For example, as shown in the following figure

How would you like to use vllm
I would like to know how to make vllm background log can record model reply information in real time.For example, as shown in the following figure.Thank you!

Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

The output isn't logged in our code, you'll have to edit chat_completion_stream_generator and/or chat_completion_stream_generator inside vllm/entrypoints/openai/serving_chat.py to log this information.

The output isn't logged in our code, you'll have to edit chat_completion_full_generator and/or chat_completion_stream_generator inside vllm/entrypoints/openai/serving_chat.py to log this information.

Thank you！


transaction response add fee field

Thanks for the PR. I think Vout must also be added to GetTransactionResponseDetails to complete the signature.

Vout should be an Int32 according to this:
gettransaction "txid" ( includeWatchonly )

Get detailed information about in-wallet transaction <txid>

Arguments:
1. "txid"    (string, required) The transaction id
2. "includeWatchonly"    (bool, optional, default=false) Whether to include watchonly addresses in balance calculation and details[]

Result:
{
  "amount" : x.xxx,        (numeric) The transaction amount in btc
  "confirmations" : n,     (numeric) The number of confirmations
  "blockhash" : "hash",  (string) The block hash
  "blockindex" : xx,       (numeric) The block index
  "blocktime" : ttt,       (numeric) The time in seconds since epoch (1 Jan 1970 GMT)
  "txid" : "transactionid",   (string) The transaction id.
  "time" : ttt,            (numeric) The transaction time in seconds since epoch (1 Jan 1970 GMT)
  "timereceived" : ttt,    (numeric) The time received in seconds since epoch (1 Jan 1970 GMT)
  "details" : [
    {
      "account" : "accountname",  (string) The account name involved in the transaction, can be "" for the     default account.
      "address" : "bitcoinaddress",   (string) The bitcoin address involved in the transaction
      "category" : "send|receive",    (string) The category, either 'send' or 'receive'
      "amount" : x.xxx                  (numeric) The amount in btc
      "vout" : n,                       (numeric) the vout value
    }
    ,...
  ],
  "hex" : "data"         (string) Raw data for transaction
}

Welcome aboard :)

tks, @GeorgeKimionis


Select User Prompt

I was just wondering if there is something that can be done to keep the "Switch Users" screen from always being presented.  I am not sure why that is happening.  It is almost like the session cookie is getting corrupted or something like that.  I see that there is a way to put puppeteer into a wait till the page is entirely loaded, but I am not sure that is the problem.
I get the feeling that it may just be my install.
If this is a one off or expected behavior due to chewing through all the pages, please feel free to close.  Otherwise, I would be interested to hear if anyone has been able to eliminate the annoying "Switch Users" screen from happening.
Thanks!

You can thank amazon for throwing that up.  Seemed to be a method of them checking if someone is really there because initially this screen DID NOT appear on the giveaways and then one day poof it starts happening.

I believe this is "expected behavior" unfortunately. Going to close this issue.


feat: Support AddCasdoorWebApi method

Fix: https://github.com/casdoor/casdoor-dotnet-sdk/issues/46

@pangfengzhen plz review

Solved #46  & #32

@pangfengzhen @Removable plz review


use DB connector instead of web API

using the web API is not smart. this PR fixes that issue

@nikooo777 what's the status of this PR? Sitting out here a while.

I have to find time to clean it up... I'll try to get that done asap.


zql [4/n] - pull historical data for initial query execution

The pipelines process write events as they happen but when a pipeline is first attached to a source, we need to query against all historical data.
This adds a path for leaves of the graph to send a message up to the roots. The roots can then reply back, only visiting the paths that sent a request.

To be added later --
When asking for historical data we don't want to send the entire table back if possible.
On the way up a message can accumulate hoistable operations.

"hoist" referring to the process of moving parts of a query out of their original position and evaluating them separately.

These operations are made available to the source so it can constrain its result set.
Example:
CREATE TABLE foo (id PRIMARY KEY, date BIGINT);
SELECT * FROM foo WHERE id > x AND date = y LIMIT 100

id > x and date = y would both be hoisted to the source foo. foo, when fulfilling the history request, would pick the hoisted expression for which it has an index. In this case id > x and only send those items from the table through the graph.
Hoisting is how we're able to efficiently scroll and search over 1 million items in base Materialite.
https://github.com/rocicorp/rails/assets/1009003/f683f673-311b-49cd-8a92-9176eda487d3
https://vlcn-io.github.io/materialite/linearite/
We hoist the cursor to the source, and stop pulling rows when we hit LIMIT, so we don't actually ever visit all 1 million rows.

Sorry, I meant micro task. Fully synchronous.
On Fri, Mar 15, 2024 at 6:20 AM Erik Arvidsson @.***>
wrote:

@.**** commented on this pull request.
In src/zql/query/statement.ts
https://github.com/rocicorp/rails/pull/32#discussion_r1526278037:

// the response of historical data.

this.#materialization.pullHistoricalData();

return this.#materialization as View;
}

subscribe(cb: (value: MakeHumanReadable) => void) {
if (this.#materialization === null) {

 this.view();

}

return must(this.#materialization).on(cb);
}

// Note: should we provide a version that takes a callback?
// So it can resolve in the same event loop tick?

FYI Promises resolve in the same event loop tick already.
—
Reply to this email directly, view it on GitHub
https://github.com/rocicorp/rails/pull/32#pullrequestreview-1938938494,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHWK24SASNVUH3KRHIUQX3YYLYQBAVCNFSM6AAAAABEVFSK3KVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSMZYHEZTQNBZGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Generate correct user edit url

The current generated URL looks like /user?action_name=edit&id=42. However, if you use an authorization gem like cancancan this url requires the capability :index. If you only allow a user to edit itself, for example can :edit, ::User, id: user.id, the current URL would cause an Error to be thrown ( CanCan::AccessDenied ).
When we change action_name to action, the generated URL becomes /user/42/edit which matches the capability can :edit, ::User, id: user.id.
Fixes #3514.

Coverage decreased (-0.2%) to 95.889% when pulling 97d21722241dbfc78b8f516588fee9937c491a92 on fuegas:user-edit-url into ce1bb5a1c166b62412e4032b2d1f798297a7c289 on railsadminteam:master.

Thanks for the fix!


Error during conversion : can't read data from mbtiles sqlite: unable to open database file: out of memory

Hi, thks for this dev. the docker works perfectly but I meet problem with the source version (both on mac & windows). Any idea ?
Sequence:

develop a launch configuration in vscode

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch mbtilestokv",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "program": "${workspaceFolder}/cmd/mbtilestokv",
            "args": [
                "-tilesPath=./testdata/hawaii.mbtiles",
                "-dbPath=./cmd/kvtilesd/map.db",
                "-centerLat=19.741755",
                "-centerLng=-155.844437",
                "-maxZoom=11"
            ]
        }
    ]
}

launch "Launch mbtilestokv"

Unexpected result:
starting: [/Users/thomaspeugeot/go/bin/dlv]() dap --check-go-version=false --listen=<IP_ADDRESS>:51960 --log-dest=3 from [/Users/thomaspeugeot/go/src/github.com/akhenakh/kvtiles/cmd/mbtilestokv]()
{"app":"mbtilestokv","caller":"main.go:43","level":"info","msg":"starting converting tiles","ts":"2022-02-04T07:29:04.91992Z","version":"no version from LDFLAGS"}
{"app":"mbtilestokv","caller":"main.go:62","error":"can't read data from mbtiles sqlite: unable to open database file: out of memory (14)","level":"error","msg":"can't store tiles in db","ts":"2022-02-04T07:29:04.922702Z"}
Process 8257 has exited with status 2
Detaching
dlv dap (7890) exited with code: 0

Nota:
Problem reproduced on windows & macos

It's because you are pointing to a non existing mbtiles file:
go run main.go -tilesPath=dfdd.mbtiles -dbPath=test.db -centerLat=19.41755  -centerLng=-155.844437 -maxZoom=11

{"app":"mbtilestokv","caller":"main.go:43","level":"info","msg":"starting converting tiles","ts":"2022-02-06T01:06:09.384944Z","version":"no version from LDFLAGS"}
{"app":"mbtilestokv","caller":"main.go:62","error":"can't store map using old schema format: can't read data from mbtiles sqlite: SQL logic error: no such table: map (1)","level":"error","msg":"can't store tiles in db","ts":"2022-02-06T01:06:09.389384Z"}
exit status 2

but then poiting to the right path:
go run main.go -tilesPath=../../testdata/hawaii.mbtiles -dbPath=test.db -centerLat=19.41755  -centerLng=-155.844437 -maxZoom=11

{"app":"mbtilestokv","caller":"main.go:43","level":"info","msg":"starting converting tiles","ts":"2022-02-06T01:06:50.175935Z","version":"no version from LDFLAGS"}

I agree the error message could be better ...

merci, I was mislead by the error code indeed,
correct vscode launch.json config is below
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch kvtilesd",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "cwd": "${workspaceFolder}/cmd/kvtilesd",
            "program": "${workspaceFolder}/cmd/kvtilesd",
            "args": [
                "-dbPath=./map.db",
            ]
        },
        {
            "name": "Launch mbtilestokv",
            "type": "go",
            "request": "launch",
            "mode": "auto",
            "cwd": "${workspaceFolder}",
            "program": "${workspaceFolder}/cmd/mbtilestokv",
            "args": [
                "-tilesPath=./testdata/hawaii.mbtiles",
                "-dbPath=./cmd/kvtilesd/map.db",
                "-centerLat=19.741755",
                "-centerLng=-155.844437",
                "-maxZoom=11"
            ]
        }
    ]
}


Relax 'static lifetime on custom ReportKind name

I'm in the process of writing a Python wrapper for ariadne, but ReportKind::Custom has a member with a 'static lifetime, making it impossible to use across FFI boundaries. This change relaxes the 'static lifetime, making it possible to use ReportKind::Custom across FFI.

Thanks, very useful!


[WIP] Support multiple hosts and Cluster VIPs

This is laying the groundwork for future features:

IPv6, which requires that services support multiple cluster VIPs.
MCS, which requires a separate host and cluster VIP for the clusterset.

Summary of changes:

Introducing cluster.AddressMap, which handles the synchronization for the VIPs. This is now used both for ClusterVIPs and ClusterExternalAddresses.
Introducing model.HostVIPs, which combines a hostname with the ClusterVIPs.
Added service field ClusterLocal, which is the HostVIPs for the <svc>.<namespace>.svc.cluster.local host. This is currently the only host until a second is added for the MCS clusterset.local host.
Removed Hostname, ClusterVIPs, and Mutex from service, as they were replaced by ClusterLocal.

Please provide a description of this PR:
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
[x] 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.

[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
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.

@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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/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.

Before looking through the refactor, i want to first ask a question:
according to MCS kep, it is optional but not recommended to use MCS DNS (https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/1645-multi-cluster-services-api#dns)
What's the difference between <service>.<ns>.svc.clusterset.local and <service>.<ns>.svc.cluster.local. in the end? Will you change the cluster.local to access only cluster local endpoints?

@hzxuzhonghu

according to MCS kep, it is optional but not recommended to use MCS DNS (https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/1645-multi-cluster-services-api#dns)

There's really no way to make this work MCS work properly without clusterset.local. I'm not entirely sure why the KEP lists it as optional.

What's the difference between ..svc.clusterset.local and ..svc.cluster.local. in the end? Will you change the cluster.local to access only cluster local endpoints?

Yes, we will gradually transition cluster.local over to being actually cluster local. See the RFC for details.

@nmittler: 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.

@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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-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.

@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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-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.

@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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
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.

@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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
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.

@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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-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.

@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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-operator-controller-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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-ipv6-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.

@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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-ipv6-k8s-tests_istio

integ-cni-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-cni-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.

@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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-ipv6-k8s-tests_istio

integ-cni-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-cni-k8s-tests_istio

integ-helm-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-helm-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
Rerun command

release-notes_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test release-notes_istio

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-ipv6-k8s-tests_istio

integ-cni-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-cni-k8s-tests_istio

integ-helm-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-multicluster-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.

@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
Rerun command

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

unit-tests_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test unit-tests_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-ipv6-k8s-tests_istio

integ-cni-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-cni-k8s-tests_istio

integ-helm-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
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.

@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
Rerun command

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-ipv6-k8s-tests_istio

integ-cni-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-cni-k8s-tests_istio

integ-helm-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-notes_istio

unit-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/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
Rerun command

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-ipv6-k8s-tests_istio

integ-cni-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-cni-k8s-tests_istio

integ-helm-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-notes_istio

unit-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-distroless-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.

@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
Rerun command

lint_istio
b51ffa86ecb6b76939f08926cb325448163b0528
link
/test lint_istio

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-ipv6-k8s-tests_istio

integ-cni-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-cni-k8s-tests_istio

integ-helm-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-notes_istio

unit-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test analyze-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
Rerun command

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-ipv6-k8s-tests_istio

integ-cni-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-cni-k8s-tests_istio

integ-helm-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-notes_istio

unit-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test analyze-tests_istio

lint_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/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
Rerun command

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-ipv6-k8s-tests_istio

integ-cni-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-cni-k8s-tests_istio

integ-helm-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-multicluster-k8s-tests_istio

release-notes_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-notes_istio

unit-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test analyze-tests_istio

lint_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test lint_istio

gencheck_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/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
Rerun command

integ-pilot-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-k8s-tests_istio

release-test_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test release-test_istio

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-k8s-tests_istio

integ-telemetry-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-telemetry-mc-k8s-tests_istio

integ-istiodremote-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-istiodremote-k8s-tests_istio

integ-pilot-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-pilot-multicluster-tests_istio

integ-operator-controller-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-operator-controller-tests_istio

integ-ipv6-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-ipv6-k8s-tests_istio

integ-cni-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-cni-k8s-tests_istio

integ-helm-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-helm-tests_istio

integ-multicluster-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-multicluster-k8s-tests_istio

unit-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test unit-tests_istio

integ-distroless-k8s-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-distroless-k8s-tests_istio

analyze-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test analyze-tests_istio

lint_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test lint_istio

gencheck_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test gencheck_istio

release-notes_istio
c1dbb853b41f9a8db3787a4c90cba794a40988bb
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.

@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
Rerun command

integ-security-multicluster-tests_istio
e06dbda2240485e9282d86c6e1a563aa0e978c8c
link
/test integ-security-multicluster-tests_istio

release-notes_istio
c1dbb853b41f9a8db3787a4c90cba794a40988bb
link
/test release-notes_istio

integ-pilot-multicluster-tests_istio
c1dbb853b41f9a8db3787a4c90cba794a40988bb
link
/test integ-pilot-multicluster-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.

cc @ycai-aspen Let's review this as it pertains to dual stack changes.

@howardjohn @ycai-aspen @hzxuzhonghu PTAL

@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
Rerun command

lint_istio
67161f9b1ab86961f20c625b34ebd1fab8c660e9
link
/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
Rerun command

lint_istio
67161f9b1ab86961f20c625b34ebd1fab8c660e9
link
/test lint_istio

gencheck_istio
67161f9b1ab86961f20c625b34ebd1fab8c660e9
link
/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: 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.

@hzxuzhonghu

I prefer @howardjohn 's suggestion inlined field makes minor change to istio, but since you have manually changed all places, i am ok with either.

@howardjohn is onboard with the new approach since this will be quickly followed up with the introduction of a second field for MCS. He's already approved.

@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
Rerun command

unit-tests_istio
a6dd2165e9657bca5083ae0b01e8aedca48dd25b
link
/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.

/retest


[POC] Add general class-dispatching mechanism

While pushing on dask-expr + cudf support, I noticed that we are still pretty far from the API coverage of dask-cudf.
Dask-cudf currently relies on several forms of “dispatching" to smooth over differences between cudf and pandas:

Sub-classing of the DataFrame/Series/Index classes
Type-based dispatching of compute functions
Backend-config dispatching
Array protocol

I was hoping to avoid (or at least delay) the need for anything new in dask-expr, and so we have almost entirely leaned on the existing dispatching code. However, in order to support differences in sorting, groupby aggregation, and shuffling behavior, we now need to either (a) put in a lot of work to align the existing algorithms, or (b) add something similar to (1) as well.
Since dask-expr also uses an expansive Expr class structure under the hood, I am also thinking that we need general class-level dispatching instead of simple DataFrame/Series/Index subclassing. For example, there are probably several areas where we just want to "lower" an expression differently for cudf, and don't really need to redefine the collection-level API. For cases like this, we can just register a custom class dispatch for the problematic expression, and override the _lower method only.
This POC illustrates one possible solution for a general dispatch system in which any user or external library can effectively override a collection or expression class for a specific metadata type.  Note that I am trying hard to design something as simple as possible, so suggestions are very welcome.
How it's used
From the user perspective, the proposed design is probably as simple as it gets: You are allowed to register a custom dispatch for any FrameBase or Expr class by decorating your code with @<class name>.register_dispatch(<meta type>). For example, if I want to define my own cudf-specific DataFrame collection, I can just do something like:
import cudf
from dask_expr import DataFrame

@DataFrame.register_dispatch(cudf.DataFrame)
class CudfDataFrame(DataFrame):
    ... whatever methods I want to override ...

If the special behavior you want is more specific to a single Expr subclass, you can register a custom dispatch for that class in the same way. For example, if you just want cudf to do something different for groupby.agg, you can do something like:
from dask_expr import Expr
from dask_expr._groupby import GroupbyAggregation

@GroupbyAggregation.register_dispatch(cudf.DataFrame)
class CudfGroupbyAggregation(Expr):
    ... my custom groupby-agg logic ...

Important Note: For typical dask-expr development with a pandas backend, nothing should change as a result of this PR.
How it works
The new system requires very few changes to FrameBase and Expr, because (1) it leverages the existing type-dispatching logic in dask.utils.Dispatch, and (2) it does not require any additional code to register the default FrameBase/Expr classes that are already defined in dask-expr.
Registering of dispatch classes works in the same way that dispatch functions are registered in dask/dask. When base_cls.register_dispatch(meta_type, custom_cls) is used to register a custom class for a (base_class, meta_type) combination, we essentially add the custom class to a Dict[base_class, dask.utils.Dispatch] structure (where the dask.utils.Dispatch element handles the type-based dispatching).
At runtime, class dispatching happens within cls.__new__, which is called before object initialization. Since we can inspect the initialization arguments within cls.__new__, we can also check if the first argument (arg) is an Expr instance, and if we have a custom class registered for the combination of cls and arg._meta. If we do have something registered, we simply use the custom class to create our object instead of cls. This means that our custom class must accept the same __init__ arguments as cls, but attributes like _meta/_lower/etc can all be different.

Looking only briefly at this, I'll admit that I'm not smart enough to understand the proposed design by looking at the code.  I think it might be helpful to write down a bit more at a high level how this would work.  I'd aim for something that you'd send to a new developer to help explain the system.  (If it's sufficiently complex that this would be hard, then it's a sign that it might not be a good design).
In general, my bias is to be very wary of adding a new dimension of dispatching.  Currently I'm trying to think about how to extend dask-expr to arrays, and I'd be quite concened if adding a system like this made it harder to think about expressions such that that arrays became harder to achieve.

I think it might be helpful to write down a bit more at a high level how this would work.

Thanks for taking a look @mrocklin - I added a quick overview, but may be able to revise/simplify later. Overall, I'm aiming for something that very light-weight, and mostly "invisible" within dask-expr itself.
I think we are on the same page in terms of wanting to avoid complexity. I spent a lot of time struggling with this, because it is becoming apparent to me that the current collection API will need a lot of ugly compatibility code if we don't break out cudf-based collections into a distinct API (like dask-cudf). However, even if we do something like the new_dd_object trick, I will still probably end up spending a lot of time duplicating Expr code for the cudf-specific API. I suppose I'm really looking for a solution where RAPIDS can be as surgical/efficient as possible about overriding default dask-expr behavior, without requiring anything heavy in dask-expr itself.

I am a bit concerned about all these dimensions that you could end up registering dispatching mechanisms, but I don't see a better way of achieving what you are aiming for.

but I don't see a better way of achieving what you are aiming for.

Right - I think it is worth mentioning that it may be possible to use a simple *.substitute operation to get what we need, but only if expressions were refactored so that _meta/divisions/npartitions were not calculated until absolutely necessary (e.g. after the expression was "lowered"). Querying one of these properties from the collection API would need to trigger a lower pass. I do think we should do this for divisions/npartitions, but I have doubts that this makes sense for _meta.


Some updates from FIT v2.2

See commits for description of what is included so far. Not everything from v2.2 is included yet. And support for compressed timestamps is still not included, but still not actual files to test with yet!

Coverage decreased (-2.1%) to 71.327% when pulling 014c5de74b9d8281d14849edfff8abb021fb49b3 on dev into<PHONE_NUMBER>600d9f4c37e45889d9fbe91ccbf934 on master.


recipes-tisdk: tisdk-uenv: am62pxx-evm: Fix overlay paths based on ti-linux-6.6-y

With ti-linux-6.6-y, all overlays are now present at /boot/dtb/ti/ of root filesystem in-case of non fit-Image based boot as well. Hence, the if check is no longer valid & can be removed.

Applied with ea4fc09a604ed21220f6646d09fe2d93633d787f


Refactor themes and group permissions

Currently themes act as a permission mechanism, but we really should just have plain old groups. The theme-based permissions can not scale to the hundreds of different sites (sbn blogs) we will need to support. We will also need a method to make these themes configurable via Autotune, so we don't have to add new themes to each and every blueprint.

Work items (To be tracked by individual issues)

[ ] Add group model
[ ] Add themes data to theme model  #293
[ ] Add theme variable requirement based on Unison data
[ ] Add migrations for existing themes
[ ] Add designer role
[ ] Update build to handle theme data
[ ] Add a task to pull unison data
[ ] Add CRUD for themes
[ ] Add Theme editor UI
[ ] Add UI for controlling blueprint access
[ ] Change theme picker logic
[ ] Change authentication to groups from Themes
[ ] Remove custom Theme
[ ] Handle new vertical addition with no theme
[ ] QA authentication and authorization
[ ] QA Themes
[ ] User test new UI
[ ] Update blueprints to handle themes


Let defaultExpr easy to use

As of v0.19.0, it is difficult to use. e.g. defaultExpr = "''" for an empty string.

It might be possible to set the "default" defaultExpr for each type, if static type adapter (#49) is implemented.


Enable Poetry's virtual env in CI

I've removed the setting to disable Poetry's virtual envs in CI checks. Since Poetry is installed through pip into the global environment, it's better to let Poetry install the dependencies into its managed virtual env, so that there can be no conflict between Poetry's own dependencies and those installed via Poetry.

Great, thank you!


jk-router With Express.js Framework

Type: Feature Request
Can We Use Express With It. I Want To Do It Because I Want To Make It Listen On A Port

It's a client side router only, Express is a server router.
You can use both but you should not catch paths destined to Express  with JkRouter.


Seeing a negative value for currentConcurrentExecutionCount metric

The work in #678 appears to be incomplete.  In production, I've seen a command where this metric drops below 0.

This appears to be an unrelated metrics issue, outside of Hystrix.


Fix role example

Short description:
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

!verified

!cherry-pick v4.12


chore: updated deps

:tada: This PR is included in version 3.0.44 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Having a big object (scaled), effects other objects' geometries in a scene.

Hi, i want to first say thanks so much for this awesome project.
When I place a simple plane and scale it 100 or 1000 other objects in the scene lose detail.
I made a quick video showing the issue.
I have this script, exports .blend file to .glb, then runs gltfpack on it.
I also tried loading the same file on https://sandbox.babylonjs.com/ and https://gltf-viewer.donmccurdy.com/, they showed the same result.
https://github.com/zeux/meshoptimizer/assets/8594559/9c381828-a5d2-4204-ae31-acc8b402dce3

Yeah this is a known issue with large scales; tracked in #433. You can use -vpf command line option as a workaround for now, or -kn will also often fix the issue. If you can share the model in question that would be great since it will help make sure the eventual fix will improve it.

MainMenu.blend.zip
.blend and .glb files are in the zip file.
I noticed -kn paremeter helps if I don't apply the scale in blender.
Thanks!

Looking closer at this report and I think it's the exact same cause as #433; I'm going to close this as a duplicate, the actual fix will come as part of #433. -vpf can be used as a workaround in the meantime.


fix: bump sc4s/splunk versions

:tada: This PR is included in version 1.8.21 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


DrawerLockMode not working

Hi,
Great package so far.
I'm using DrawerNavigator nested with TabNavigator. What i'm trying to achieve, is to hide the drawer view on swipe.
I have searched and i found that i can use drawerLockMode, but this option is not working.
drawerLockMode is merged on the master branch?
in "src/Navigators/DrawerNavigator.js" and "src/Views/Drawer/DrawerView.js" there is no reference about this feature.

software
version

react-navigation
^1.0.0-beta.9

react-native
0.43

Best regards,
Mihai

Could you please provide a small sample app (preferably via Snack) that shows what you're trying to do? I'm going to close this for now but we can re-open if a sample is provided. Thanks!


Autocheck 'Fulfilled' checkbox when entering stuff in any fulfillment field

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

What are we trying to do?
In this fulfillment form, there's a boolean checkbox for 'Fulfilled' that's easy to miss -- we should make it so it autochecks if you enter any fields in the fulfillment form.

What feature or behavior is this required for?
Make sure our data entry vols don't accidentally mark someone as not fulfilled.

How could we solve this issue? (Not knowing is okay!)
The code to this partial is in app/views/patients/_fulfillment.html.erb. Any js should go in app/assets/javascripts/patients.coffee.

Here's a screenshot of the partial in action:

I'm agnostic as to the best way to do this, so taker's choice. Probably the most straightforward way to do this is to just check the box if any fields in the form aren't blank or empty.

Anything else?
There's a patient created from rake db:seed that you should use, since the Fulfillment tab doesn't show up until a patient's marked pledge sent. (Name: Pledge Submitted - 3)

Stems from #864 .
Reserving for Jon, who needs a js issue to hammer on!

I'm taking this bad boy


Something wrong with date-fns

Hello, thanks for this project!
I've got following warning on my projects:
WARNING in duplicate-package-checker:
  <undefined>
    undefined ./~/date-fns/parse
    undefined ./~/date-fns/compare_asc
    undefined ./~/date-fns/compare_desc
    undefined ./~/date-fns/difference_in_calendar_months
    undefined ./~/date-fns/difference_in_milliseconds
    undefined ./~/date-fns/difference_in_months
    undefined ./~/date-fns/difference_in_seconds
    undefined ./~/date-fns/distance_in_words
    undefined ./~/date-fns/distance_in_words_to_now
    undefined ./~/date-fns/is_date
    undefined ./~/date-fns/locale/_lib
    undefined ./~/date-fns/locale/en

Can you provide more information on how date-fns is being required?

Is it possible that what's requiring date-fns has a package.json without the name property?

Issue fixed with v1.2.2. Issue was do to non-root package.json files in date-fns.
https://github.com/date-fns/date-fns/issues/264#issuecomment-265128399
https://github.com/jsdnxx/find-root/issues/2

Thanks!


add cleanup-on-shutdown logic for VPN

@uProxyli reports:

If I start my VPN with uProxy, then swipe away android app, the VPN leaves my phone in a network-broken state (I have to go into settings and forget my VPN for it to start working again).

This issue was fixed by https://github.com/uProxy/cordova-plugin-tun2socks/pull/3/commits/ac66a915bf318748bac3722b826f83ca2cdf438e.