Importing aws:ec2/routeTable:RouteTable produces resource with ipv6Cidr resource with empty string resulting in invalid CIDR address error

Update: 28 May '24
It looks as though this specific issue is triggered when using ignore_changes=["routes"] after doing pulumi import on a RouteTable resource
According to the docs, by omitting the routes input, this should then ignore route changes. I've tried this and it looks to be working okay for our use case.
For now it looks as though this isn't a blocking issue for importing Route Tables since there is a workaround, it's probably just not ideal that import is producing an invalid resource state that cannot be validated as per @tmeckel's reply: https://github.com/pulumi/pulumi-aws/issues/3986#issuecomment-2129313732
Latest info and steps to repro are in: https://github.com/pulumi/pulumi-aws/issues/3986#issuecomment-2130139319

What happened?
Not sure if this is a pulumi-aws or upstream Terraform problem!
When pulumi importing an AWS Route Table with AWS Classic (aws:ec2/routeTable:RouteTable), it appears that it also imports routes associated with the route table. The attributes on a route are set to "" if there is no value associated. I’m seeing an issue where "ipv6CidrBlock": "" then causes pulumi preview to complain that "" is not a valid CIDR block: invalid CIDR address.
When I pulumi state edit and remove the ipv6CidrBlock: "", line from the aws:ec2/routeTable:RouteTable resources the error goes away.
If I also compare a aws:ec2/routeTable:RouteTable created by pulumi up vs an imported resource via pulumi import, the fields without values are all "" in the imported version and not present in the pulumi up.
Example
pulumi import aws:ec2/routeTable:RouteTable public_rt rtb-4e616f6d69
pulumi preview

error: aws:ec2/routeTable:RouteTable resource 'public_rt' has a problem: "" is not a valid CIDR block: invalid CIDR address: . Examine values at 'public_rt.routes'.

      15       "urn": "urn:pulumi:ccoe-sandbox-usw2-tbarlow::riotvpc::aws:ec2/routeTable:RouteTable::customer_tbarlow_PublicRouteTable_<IP_ADDRESS>/28_az1",
      14       "custom": true,
      13       "id": "rtb-0845eafb29d28dbb9",
      12       "type": "aws:ec2/routeTable:RouteTable",
      11       "inputs": {
      10         "__defaults": [],
       9         "routes": [
       8           {
       7             "__defaults": [],
       6             "carrierGatewayId": "",
       5             "cidrBlock": "<IP_ADDRESS>/0",
       4             "coreNetworkArn": "",
       3             "destinationPrefixListId": "",
       2             "egressOnlyGatewayId": "",
       1             "gatewayId": "igw-09254a252d322b940",
    156              "ipv6CidrBlock": "",
       1             "localGatewayId": "",
       2             "natGatewayId": "",
       3             "networkInterfaceId": "",
       4             "transitGatewayId": "",
       5             "vpcEndpointId": "",
       6             "vpcPeeringConnectionId": ""
       7           }
       8         ],

Section of state where the empty strings are being added to route attributes:
"custom": true,
"type": "aws:ec2/routeTable:RouteTable",
"inputs": {
  "__defaults": [],
  "routes": [
    {
      "__defaults": [],
      "carrierGatewayId": "",
      "cidrBlock": "<IP_ADDRESS>/0",
      "coreNetworkArn": "",
      "destinationPrefixListId": "",
      "egressOnlyGatewayId": "",
      "gatewayId": "igw-00000000",
      "ipv6CidrBlock": "",
      "localGatewayId": "",
      "natGatewayId": "",
      "networkInterfaceId": "",
      "transitGatewayId": "",
      "vpcEndpointId": "",
      "vpcPeeringConnectionId": ""
    }
  ],

Output of pulumi about
  ❯ pulumi about
  CLI
  Version      3.116.1
  Go Version   go1.22.2
  Go Compiler  gc

  Plugins
  KIND      NAME    VERSION
  resource  aws     6.35.0
  language  python  unknown

  Host
  OS       darwin
  Version  14.3.1
  Arch     arm64

  This project is written in python: executable='.../python3' version='3.11.7'

...

Dependencies:
  NAME                        VERSION
  ansible                     9.5.1
  isort                       5.13.2
  mypy-boto3-ec2              1.34.101
  mypy-boto3-ram              1.34.0
  mypy-boto3-route53          1.34.31
  mypy-boto3-route53resolver  1.34.102
  parameterized               0.9.0
  pip                         23.3.2
  pre-commit                  3.7.1
  pytest                      8.2.0
  yamllint                    1.35.1

Additional context
Discussed this a little bit on Slack: https://pulumi-community.slack.com/archives/C84L4E3N1/p1715987354126929
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

The above shown data in routes is clearly invalid, because for an optional Terraform property the property shouldn't show up at all. That's why removing the empty string "" will solve the shown error by pulumi.
https://github.com/hashicorp/terraform-provider-aws/blob/4827180fd06cbdc17b6209f9dc8f9513a0a8d4a7/internal/service/ec2/vpc_route_table.go#L91

CC: @t0yv0

Thank you for reporting this issue so clearly and thanks for the cited workaround! I'm adding the appropriate labels. This is indeed common theme of issues, our team will need to tackle as time permits. Adding to a tracking issue.

Updated the main issue comment, since I don't believe this is a blocking issue if the trigger is only when ignore_changes=["routes"] is added, since the RouteTable resource has a built-in method of ignoring routes by simply omitting the input.
I don't know enough about how import works with pulumi-aws and the terraform bridge to know if this could be a wider issue though where the import CLI is producing a state that won't pass validation.

I just tried to reproduce this using the latest https://github.com/pulumi/pulumi-terraform-bridge/tree/master and it looks like it has been fixed.
After the next bridge release we can pull in the new version and test it out to confirm.

Tracking https://github.com/pulumi/pulumi-terraform-bridge/issues/2314 in the bridge.

@tombee the issue should now be fixed on the latest version. I tested with your repro and it was successful.

Thank you @corymhall! That's great news.
On Wed, Sep 11, 2024 at 1:33 PM Cory Hall @.***> wrote:

Closed #3986 https://github.com/pulumi/pulumi-aws/issues/3986 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/pulumi/pulumi-aws/issues/3986#event-14215433878, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAOVJDUCE3DII4FIQH5GB3ZWA2CTAVCNFSM6AAAAABIHKCEGKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGIYTKNBTGM4DOOA
.
You are receiving this because you were mentioned.Message ID:
@.***>


update flaml version in MathChat notebook

update flaml version in MathChat notebook. (Line 16 and 32)

Why are these changes needed?

Related issue number

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/FLAML/. See https://microsoft.github.io/FLAML/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Would you like to add a link to the mathchat notebook in the doc website? Can do it in this PR: #1089

Sure!

Would you like to add a link to the mathchat notebook in the doc website? Can do it in this PR: #1089

Sure!

When would you add it?

Would you like to add a link to the mathchat notebook in the doc website? Can do it in this PR: #1089

Sure!

When would you add it?

My bad. Just add it

@kevin666aa could you make the pydantic change in this PR?

@kevin666aa could you make the pydantic change in this PR?

Sure

@kevin666aa could you make the pydantic change in this PR?

Sure

I've already merged with main. So that issue should be fixed.


add plugin tutorial in tutorial.md

from idea to finish

Hi, is this issue still open? I would like to work on it if its still open.
Thank you!

This project is deprecated. Please use the new link in the readme
Sent with GitHawk


03/28/2018 06:46 : Create Pull Request for branch prTesting_2018032806 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

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


Bump the default CPU request for the helm-sync container to avoid helm failures (#378)

When the helm-sync container pulls the wordpress chart on the autopilot clusters, it fails with a signal: killed error. It turns out it consumes more CPU than requested.
This commit bumps the default CPU request from 10m to 50m.

Just to be clear the wordpress chart change hasn't been cherry picked to the release branch, so those tests are still using the prior chart. Is this change intended as a functional change for 1.14.2 rather than just for test stability?

Correct, this change is intended as functional change for 1.14.2.
For the wordpress change, I'm inclined to not cherry pick to the release branch. The downside is that it will continue leaking Firewall rules in the release CI project, but once we get to 1.15.0, it should be fixed.

SGTM
/lgtm
/approve


Generating markup exits grunt-contrib-watch task

I have the following issue:
I use several grunt plugins during development, concat, uglify, spritesmith, sass, liquid, connect and watch. My watchers are set up in a nice way to run the exact tasks I need at any time.
When I have only one .liquid file to parse, with whatever amount of includes, my watch task sees that there has been modification in the markup folder and runs the liquid task, browser refreshes, all fine.
But! When I have multiple .liquid files to create multiple .html files from, the watch task runs the liquid task, generates the correct files, but then my grunt watch task exits and the node.js command prompt waits for a command.
Let me know if you need anything at all from me, details, configuration files, I enjoy this plugin very much and would like to help you find this bug.

I was also having this problem. Basically whenever I ran the liquid task before the watch task it exited to the console. In the end I used grunt-concurrent to bundle my liquid and sass tasks and put the watch after. This works fine.
...
watch: {
liquid: {
files: ['src/**/*.liquid'],
tasks: ['newer:liquid'],
},
...
concurrent: { rebuild: ['liquid', 'sass', 'uglify']  }
...
grunt.registerTask('dev', ['express', 'open', 'watch']);
grunt.registerTask('default', ['concurrent:rebuild', 'dev']);

I'm facing the same issue, with spawn enabled. See #21


Karan m1 schrodinger

Hi @karanprime - Great work. I have a few comments before merging your code to the main branch.
[ ] Can you change the folder name to "Learning_the_Schrödinger_Equation"?
[ ] Please move the content of the "lessons" folder into the main "Learning_the_Schrödinger_Equation" folder.
My main concern is that you have used torch as opposed to keras. What is the justification for this choice? We agreed to use tf/keras for all deep learning modules. Obviously, we don't have enough time before the workshop to fix this but we would need to address it later.

Hi @soltaniehha, I have updated the folder structure to that specification. I have named it Learning_the_Schrodinger_Equation instead of Learning_the_Schrödinger_Equation because ö might cause weird bugs in folder names.
Regarding the use of PyTorch, I used it because it is much easier to define the derivatives/gradients required for the physics informed neural net in PyTorch, and the code for doing that is more readable. I can change it to Keras/TF during the workshop.


Build dockerfile from neon=repo

Problem
Summary of changes
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

Created following PR from a cleaner branch
https://github.com/neondatabase/neon/pull/6195
Closing this PR.


allowExternal option for v8 coverage provider

Clear and concise description of the problem
Since the @vitest/coverage-c8 is removed in favor of @vitest/coverage-v8 (https://github.com/vitest-dev/vitest/pull/3339) and coverage-v8 doesn't provide the allowExternal option this will break coverage reports when upgrading to the latest vitest version (and switching providers).
Suggested solution
Implement the allowExternal option (as suggested in the above-mentioned PR). I'd be happy to provide the implementation (LMK if you have any inputs/suggestions on how to do this)
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

This should also be implemented to @vitest/coverage-istanbul. They both use the same test-exclude dependency which I think provides this in c8: https://github.com/bcoe/c8/blob/a13584d5be5259ebb6a00455d352c3e8b16006de/lib/report.js#L48-L52.

I'd be happy to provide the implementation

PR is welcome! Here is one PR for reference to show which files, tests and documentation needs changes when adding new coverage options: https://github.com/vitest-dev/vitest/pull/3453.
Let me know if you need any help.

@AriPerkkio I drafted a PR for this, can you check it out? https://github.com/vitest-dev/vitest/pull/3894
I actually would need help with writing good tests for this feature. I added some tests but I don't think they do what they should do. Please check out the comments in the PR 🙏


[Camp Rohwer Remains][Audio continues]

Camp Rohwer Remains
The Before section music (Any music really) plays over the page if you use the drop down menu in the before section to jump to the war is over.
What We Should Do to Fix it

[x] Have a check that unplays whatever the music was?

adjusted the change scene script to reflect these changes so that now the war is over button jumps to the splash page for the war is over instead. the bug can now no longer be replicated (I hope 🤞)


Failure to get device count with multiple GPUs

I have an application that runs fine with one AMD W6800 (using HIP API). But when I add another GPU into the same machine, it doesn't work.
When I run rocm-smi, before running the application, I am able to see two devices:
GPU  Temp (DieEdge)  AvgPwr  SCLK    MCLK   Fan     Perf  PwrCap  VRAM%  GPU%
0    50.0c           46.0W   500Mhz  96Mhz  40.78%  auto  213.0W    0%   2%
1    47.0c           48.0W   500Mhz  96Mhz  40.78%  auto  213.0W    0%   1%

Then, I load my application in gdb and set a break point in main() and as soon as I hit the breakpoint, rocm-smi give this output and hipGetDeviceCount() returns 100.
======================= ROCm System Management Interface =======================
================================= Concise Info =================================
Expected integer value from monitor, but got ""
Expected integer value from monitor, but got ""
================================================================================
================================================================================
Expected integer value from monitor, but got ""
Expected integer value from monitor, but got ""
Expected integer value from monitor, but got ""
Expected integer value from monitor, but got ""
================================================================================
================================================================================
Expected integer value from monitor, but got ""
Expected integer value from monitor, but got ""
GPU  Temp (DieEdge)  AvgPwr  SCLK  MCLK  Fan  Perf     PwrCap       VRAM%  GPU%
0    N/A             N/A     None  None  0%   unknown  Unsupported    0%   0%
1    N/A             N/A     None  None  0%   unknown  Unsupported    0%   0%

Any idea what's going on here?
I am running:
HIP version: 5.4.22802-aaa1e3d8
AMD clang version 15.0.0 (https://github.com/RadeonOpenCompute/llvm-project roc-5.4.1 22465 d6f0fe8b22e3d8ce0f2cbd657ea14b16043018a5)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /opt/rocm-5.4.1/llvm/bin

Can you run the application with AMD_LOG_LEVEL=7 ./a.out and share the log


Typo - Issue - 1719

Typo fixed under 'Create a fat binary' subheading.
#1719

Thanks so much for your fix @viveknatarajan, however it looks like it was fixed internally. We appreciate you taking the time.


Update kubernetes documentation for users

@emilywoods I think it should be re-referenced to https://crate.io/docs/crate/reference/config/index.html


[for test only] do not merge

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


[Bug]: Policy "coverage until" exceeds all existing policies' "active until"

What happened?
Not sure if this is a bug, but longest available bundle expires on 2023-04-23 09:37 UTC  and I was allowed to create a policy offering protection until 2023-01-28 03:54 UTC

I'd: 0x10ec3bda41c74a1995d4563febbbdfe8b160830a068ccca37eca318ec0db238f
Wallet: 0x1608F32b98312AC2B9801e2872F6842e551eb0a4
What operating system are you seeing the problem on?
Windows, Android
What browsers are you seeing the problem on?
Firefox, Other (please mention in the description)
What wallet extension are you using?
Metamask
Rules

[X] I agree to follow this project's rules

This is expected behavior. The expiration of a bundle defines how long new policies can be issues on this bundle (we are going to change the text to make this clearer).
The actual policy duration is defined by the minimum and maximum coverage duration. This effectively means that the bundle cannot be burned before all policies are expired or claimed, which means the money can be locked for the lifetime plus the maximum coverage duration.

will change the text coverage until in #213 to make this clearer.


⚠ Bofrost.at has degraded performance

In 13262bb, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1464 ms

Resolved: Bofrost.at performance has improved in 6bb327c.


[FEAT] Add option to support user defined learning rate scheduler for NeuralForecast Models

Rationale

Similar to the work of adding the support of an user-defined optimizer, now we can accept an user defined scheduler. This feature is asked in https://github.com/Nixtla/neuralforecast/issues/852#issuecomment-1961923861 and https://nixtlacommunity.slack.com/archives/C031M8RLC66/p1713516602654109

@JQGoh Thanks for your work, the PR looks good to me. @cchallu @jmoralez I'm happy to add this as feature to neuralforecast, wdyt?

Can you please add warnings if the user provides lr_scheduler_kwargs but doesn't provide lr_scheduler (that the kwargs will be ignored)? We got a similar request for the optimizer by the sktime folks.

https://github.com/sktime/sktime/pull/6235#issue-2216009123

I was facing the same issue when I wanted to use a custom scheduler and you have a solution that is pretty much what I have, the only thing that I am missing in it is that I think we should also be able to change the other arguments of "lr_scheduler_config" like the frequency or the interval (https://lightning.ai/docs/pytorch/stable/common/lightning_module.html#configure-optimizers for a list of other parameters). My solution was in fact to add 2 new kwargs, lr_scheduler_kwargs as you have and lr_scheduler_config as expected by lightning, only adding the actual scheduler to it in configure_optimizers with lr_scheduler_config['scheduler'] = self.lr_scheduler(optimizer=optimizer, **lr_scheduler_kwargs). I think that if someone is bothering to manually change the lr_scheduler it makes sense to give them full control of it.

I'm not really a fan of adding so many arguments to all models. Would it be possible to instead provide a function that overrides the configure_optimizers method? Either by calling it or monkey patching.

Honestly, I think that in this case, the cleanest solution is to add one more argument. We already have arguments for the trainer, optimizer, and scheduler. Introducing a different approach for configuring the scheduler, which is part of the same system, could confuse users and require them to write additional boilerplate code to achieve their goals. Here are some scenarios to further develop my point:

Using the CosineAnnealingLR Scheduler
The default scheduler configuration is fine because the scheduler is not affected by it.

Using the OneCycleLR Scheduler
The default scheduler configuration is fine if the user knows that the default is {'frequency': 1, 'interval': 'step'}. They would only need to calculate the number of steps to pass as total_steps in the lr_scheduler_kwargs. However, if they do not know this, they would need to check the code (since it is not documented) to ensure the model trains as intended.

Using the ReduceLROnPlateau Scheduler
In this case, the user needs to change the scheduler configuration because, typically, we want to identify a plateau by epoch rather than by step. Additionally, the user has to specify the "monitor" metric they want. Without the ability to pass the scheduler configuration directly, users would need to use one approach to pass the scheduler and its kwargs and another approach (such as calling another function or monkey patching) to overwrite the scheduler configuration.

I see no reason for users to have to handle each scenario above differently. Additionally, this approach would allow us to document the default behavior clearly.

What I mean is that we currently have two arguments (for the optimizer), this adds two more (for the scheduler) and you're proposing adding a fifth, when all of these are going to be used in the same method (configure_optimizers) and they all could've been just one where the user passes a callable that takes the model parameters and returns what pytorch lightning expects from the configure_optimizers method.
Given that sktime is already using the optimizer arguments it'd be a bad experience to deprecate them and introduce a new one that takes a function, so I think we should move forward with adding more to not deprecate something we recently introduced, I just wish we'd done the single argument approach from the start.

Thank you so much for the implementation of a custom lr scheduler!
@BrunoBelucci :
Could you explain how it is possible to implement a ReduceLROnPlateau scheduler? I think some of your earlier discussion evolved around it, however, I couldn't make it work yet.
Currently I am passing through the lr_scheduler and  lr_scheduler_kwargs parameters. However, I get the below error when implementing ReduceLROnPlateau. Other schedulers, like OneCycle, work perfectly though!
MisconfigurationException('The lr scheduler dict must include a monitor when a ReduceLROnPlateau scheduler is used. For example: {"optimizer": optimizer, "lr_scheduler": {"scheduler": scheduler, "monitor": "your_loss"}}').


Slick creates weird button

See stackOverflow question:
A quick note: I'm not sure this is a slick but but I'm guessing it is based on its nesting within a slick slideshow.
http://stackoverflow.com/questions/42900930/slick-slider-slideshow-creates-button

reduced test case please


missing required architecture armv7 in file RealmSwift on device

I'm getting this long error for almost the files which are realm objects while compiling on device. I didn't get anywhere similar question.

@shahankit how have you installed RealmSwift in your project?

Yeah bigfist24 I have and things are working great on simulator. Also I made a demo project and it worked fine on device. But it's giving me this weird error in my main project.

Did you install via Cocoapods, Carthage or just added the dynamic framework to your project?

Using dynamic framework, the first method shown on getting started page.
Sent with MailTrack
<EMAIL_ADDRESS>On Thu, Aug 13, 2015 at 10:58 PM, Adam Fish<EMAIL_ADDRESS>wrote:

Did you install via Cocoapods, Carthage or just added the dynamic
framework to your project?
—
Reply to this email directly or view it on GitHub
https://github.com/realm/realm-cocoa/issues/2394#issuecomment-130770987.

--
Ankit Shah

If you go to the "General" section in your target settings, is Realm & RealmSwift included in Embedded Binaries section?

Yeah Realm and RealmSwift both are there in Embedded binaries. I used the
first method only and have also included the Run Script.
On Thu, Aug 13, 2015 at 11:06 PM, Adam Fish<EMAIL_ADDRESS>wrote:

If you go to the "General" section in your target settings, is Realm &
RealmSwift included in Embedded Binaries section?
—
Reply to this email directly or view it on GitHub
https://github.com/realm/realm-cocoa/issues/2394#issuecomment-130773209.

--
Ankit Shah

Ok, can you let me know what your build settings are for the following:
Build Active Architecture Only
Valid Architectures

Build Active Architectures only:
Debug: Yes
Release: No
Valid architectures : arm64 armv7
On Thu, Aug 13, 2015 at 11:10 PM, Adam Fish<EMAIL_ADDRESS>wrote:

Ok, can you let me know what your build settings are for the following:
Build Active Architecture Only
Valid Architectures
—
Reply to this email directly or view it on GitHub
https://github.com/realm/realm-cocoa/issues/2394#issuecomment-130775049.

--
Ankit Shah

What is the path in Framework Search Paths in your build settings?

$(PROJECT_DIR)
$(inherited)
$(PROJECT_DIR)/Frameworks
On Thu, Aug 13, 2015 at 11:49 PM, Adam Fish<EMAIL_ADDRESS>wrote:

What is the path in Framework Search Paths in your build settings?
—
Reply to this email directly or view it on GitHub
https://github.com/realm/realm-cocoa/issues/2394#issuecomment-130787495.

--
Ankit Shah

Can you make sure the RealmSwift framework is in the folder for one of those paths?

Yes I can because if it isn't then I would get a error because of Run
script phase but there is no such error.
On Thu, Aug 13, 2015 at 11:56 PM, Adam Fish<EMAIL_ADDRESS>wrote:

Can you make sure the RealmSwift framework is in the folder for one of
those paths?
—
Reply to this email directly or view it on GitHub
https://github.com/realm/realm-cocoa/issues/2394#issuecomment-130789771.

--
Ankit Shah

Which version of Realm are you using?

1.2
On Fri, Aug 14, 2015 at 12:12 AM, Adam Fish<EMAIL_ADDRESS>wrote:

Which version of Realm are you using?
—
Reply to this email directly or view it on GitHub
https://github.com/realm/realm-cocoa/issues/2394#issuecomment-130796759.

--
Ankit Shah

Sorry which release version of Realm are you using such as 0.94.1?

0.94.1
On Fri, Aug 14, 2015 at 12:15 AM, Adam Fish<EMAIL_ADDRESS>wrote:

Sorry which release version of Realm are you using such as 0.94.1?
—
Reply to this email directly or view it on GitHub
https://github.com/realm/realm-cocoa/issues/2394#issuecomment-130797918.

--
Ankit Shah

Can you make sure you are using the iOS Realm and RealmSwift frameworks and not the OS X versions?

Tell me how do you want me to make sure, because things are working fine
with simulator? You want me repeat installations steps and try out or is it
ok because it's working fine on simulator and confirm that I'm using ios
versions only (Although I perfectly remember that I've done that only)?
On Fri, Aug 14, 2015 at 2:37 AM, Adam Fish<EMAIL_ADDRESS>wrote:

Can you make sure you are using the iOS Realm and RealmSwift frameworks
and not the OS X versions?
—
Reply to this email directly or view it on GitHub
https://github.com/realm/realm-cocoa/issues/2394#issuecomment-130845254.

--
Ankit Shah

I would recommend you remove the frameworks and drag the iOS frameworks back in and retry running on the device.

@bigfish24 Things got fixed I was mistakenly using 0.94.0 instead of 0.94.1.


Create a prow test harness

Based off the kubeflow test harness, this is a container that'll get pulled down and run by prow. It currently:

Lints
Runs the python tests.

In the future, it'd be awesome to spin up clusters.

Partially fixes https://github.com/tensorflow/minigo/issues/24

Also, @cjwagner -- fyi


fix(ContentHeader): Allow children in ContentHeader

Allow children in ContentHeader
cc @radekkaluzik

Preview: https://react-component-groups-pr-component-groups-408.surge.sh


onReceivedHttpAuthRequest is not called in IOS

[x] I have read the README
[x] I have already searched for the same problem
[x] I have read and done the setup for Android: IMPORTANT Note for Android and iOS and IMPORTANT Note for Android
[x] I have read and done the setup for iOS: IMPORTANT Note for Android and iOS and IMPORTANT Note for iOS

Description
I have created an app to load the website using NTLM for authentication. i am using onReceivedHttpAuthRequest to proceed with the authentication. it is work perfectly in Android, but onReceivedHttpAuthRequest is not called in IOS.
onReceivedHttpAuthRequest: (InAppWebViewController controller, HttpAuthChallenge challenge) async {
return re=HttpAuthResponse(username: _userName, password: _password, action:
HttpAuthResponseAction.PROCEED, permanentPersistence: true);
}
I will really appreciate if anyone can help m e on this issue.
Thank you.

Oh interesting, I was just thinking about opening a bug for this. I am deeply in trouble right now, as I am using headlessInAppWebView for navigating through pages to grab data for my app. However in some occasions I need NTLM.
I thought this was not possible at all with inappwebview, but interesting that you say it works on android.
I hope this can be fixed in near future, as this is completely rendering InAppWebView useless for me right now. :(

Oh interesting, I was just thinking about opening a bug for this. I am deeply in trouble right now, as I am using headlessInAppWebView for navigating through pages to grab data for my app. However in some occasions I need NTLM.
I thought this was not possible at all with inappwebview, but interesting that you say it works on android.
I hope this can be fixed in near future, as this is completely rendering InAppWebView useless for me right now. :(

Hello, I also had the same problem in NTLM authentication in IOS and the method was not started due to the absence of calls: NSURLAuthenticationMethodNegotiate and NSURLAuthenticationMethodNTLM.
I located the swift file that makes this call that is on the path: flutter_inappwebview / ios / Classes / InAppWebView.swift
When adding locally for testing, it worked!
...
public func webView(_ webView: WKWebView, didReceive challenge: URLAuthenticationChallenge, completionHandler: @escaping (URLSession.AuthChallengeDisposition, URLCredential?) -> Void) {
    if challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodHTTPBasic ||
        challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodDefault ||
        challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodNegotiate ||
        challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodNTLM ||
        challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodHTTPDigest {

....
Getting something like above.
I have already notified the developer to evaluate include this and have this verification.
Thanks
Ricardo Nogueira

Hello, I also had the same problem in NTLM authentication in IOS and the method was not started due to the absence of calls: NSURLAuthenticationMethodNegotiate and NSURLAuthenticationMethodNTLM.
I located the swift file that makes this call that is on the path: flutter_inappwebview / ios / Classes / InAppWebView.swift
When adding locally for testing, it worked!
...
public func webView(_ webView: WKWebView, didReceive challenge: URLAuthenticationChallenge, completionHandler: @escaping (URLSession.AuthChallengeDisposition, URLCredential?) -> Void) {
    if challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodHTTPBasic ||
        challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodDefault ||
        challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodNegotiate ||
        challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodNTLM ||
        challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodHTTPDigest {

....
Getting something like above.
I have already notified the developer to evaluate include this and have this verification.
Thanks
Ricardo Nogueira


Minor fix of ARM common type and foundations

Closes #1108, #1107

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@azure-tools/typespec-azure-resource-manager

Show changes

You can try these changes at https://cadlplayground.z22.web.core.windows.net/typespec-azure/prs/1156/
Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/typespec-azure/prs/1156/


Update Cargo.tomls in preparation for release

The version is set at "0.1.0-alpha.0". The License file was also copied
to each part  of the workspace

This will be superseded by anything done for #37 so this will be closed for the moment.


🐛 Bug Report: Docker run is failing with an error

📜 Description
I followed the instructions posted on this document https://backstage.io/docs/deployment/docker for building a docker container with backstage. When I executed the docker run command as stated in the document, I see errors.
👍 Expected behavior
Expected to see a running backstage docker container.
👎 Actual Behavior with Screenshots
Error message is in the Reproduction steps below.
👟 Reproduction steps
Commands executed in sequence:
npx @backstage/create-app@latest
cd backstage
yarn install --frozen-lockfile
yarn tsc
yarn build:backend --config ../../app-config.yaml
docker image build . -f packages/backend/Dockerfile --tag backstage
docker run -it -p 7007:7007 --name backstage backstage

Console output:
Loading config from MergedConfigSource{FileConfigSource{path="/app/app-config.yaml"}, FileConfigSource{path="/app/app-config.production.yaml"}, EnvConfigSource{count=0}}
{"level":"info","message":"Found 0 new secrets in config that will be redacted","service":"backstage"}
{"level":"info","message":"Listening on :7007","service":"rootHttpRouter"}
{"level":"info","message":"Plugin initialization started: 'app', 'proxy', 'scaffolder', 'techdocs', 'auth', 'catalog', 'permission', 'search', 'kubernetes'","service":"backstage","type":"initialization"}
/app/node_modules/@backstage/backend-defaults/dist/database.cjs.js:457
        throw new Error(
              ^

Error: Failed to connect to the database to make sure that 'backstage_plugin_app' exists, Error: connect ECONNREFUSED <IP_ADDRESS>:5432
    at PgConnector.getClient (/app/node_modules/@backstage/backend-defaults/dist/database.cjs.js:457:15)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at listOnTimeout (node:internal/timers:538:9)
    at process.processTimers (node:internal/timers:512:7)

Node.js v18.20.4

📃 Provide the context for the Bug.
I am trying to run the app for the first time.
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Hey :wave: This looks like it's struggling to connect to the database? Do you have a running PostgreSQL database that you've configured?


Fix gcloud docker push

The gcloud docker push command fails unless -- is specified:
ERROR: gcloud crashed (ArgumentError): argument DOCKER_ARGS: unrecognized args: push eu.gcr.io/build-lgp/guestbook
The '--' argument must be specified between gcloud specific args on the left and DOCKER_ARGS on the right.

If you would like to report this issue, please run the following command:
  gcloud feedback

To check gcloud for common problems, please run the following command:
  gcloud info --run-diagnostics
Build step 'Execute shell' marked build as failure
Finished: FAILURE

👍

Agreed. This should be merged.


refactor(templates): Simplify target template file names with post_gen_project.py hook

:books: Documentation preview :books:: https://meltano-sdk--2061.org.readthedocs.build/en/2061/

Thanks again @vicmattos!


About the 0.5.0 version

I noticed that there is version number 0.5.0 on crates.io for grammers-client and it is not here in the repository, why?

Forgot to push - the commits are now in (https://github.com/Lonami/grammers/commit/b583c89f06acd6da30eb13b22da305b091c3d8b2). Thanks.


Unsinged raster dimensions, allocation in size_t. No segfaults, yay.

This PR fixes segmentation fault mentioned in #32 and other potential allocation related problems.

@fester is there a reason not to support uint64_t? (and was there in general an argument for not using size safe integer types?)
Further, I think this should be covered by a test case.

Do you mean using uint64_t for raster dimensions?
Let's put it this way: given the scope of this utility, I can't see any reason to assume rasters larger than 4.2 billion pixels in any of the dimensions.
As for the test case, it's a good idea. Given the overflow happening in a private method and results in an incorrect heap memory allocation, the only way to test it is to check for the actual amount of memory allocated. Do you have any idea how to implement this kind of check in a cross platform fashion using standard C++ runtime?

I meant for a general reason not to use fixed sized integers all over the code :) I think the dimensions used in issue https://github.com/heremaps/tin-terrain/issues/32 are realistic and should be supported if that is just an issue of using uint64_t (maybe something for the future, not this PR).
Testing is simple. Allocate such a large array and it should not segfault (I understood it that way, that with the old code and using those dimensions, it did segfault). Then again, if the testing machine does not have that much memory, this is also an issue... Ok, forget the testing bit :D
In order to address the original issue, we could add a sanity test either in the alloc (and just fail the alloc if the user requests a raster size we don't support) or in the calling code. And that can then be tested :) What do you think?

I have a feeling we are not on the same page here.
Raster class implementation uses 4-byte ints ints to store raster dimensions. In order to allocate enough memory to hold the raster data, Raster's alloc() method calls new T[m_width*m_height]. The operator new[] expects a number of elements to be allocated as an 8-byte size_t, but because m_width and m_height are 4-bytes, compiler multiplies two 4-byte values resulting in a quiet overflow and new[] gets the leftover of the muliplication. This PR manually lifts ints to size_t telling compiler to generate 8-byte multiplication which doesn't overflow, producing a correct new[] call and a correct alocation. Since the allocation is correct now, segfault is gone and tin-terrain can accept any raster whose dimensions are under 2^32-1 pixels. It's up to OS to verify whether the system is capable of allocating needed amount of memory.

No we are on the same page here. The only comment I had (as did Vova) was, that we might need to throw an error, to accommodate for any limitations we are having in the code. Since I am new to the code base, I cannot assess this yet and thus asked you to add an exception, if limitations should be imposed.
I will merge this now and if you feel an exception should be added, let's have another PR.

+1


some styles require a preceding whitespace while some do not

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

open a chat
try bold/italics/strike-through/inline-code once with a preceding whitespace and once without that

Expected results:
all styles should be applied in absence of a whitespace
Actual results:
only inline-code works without whitespace and others don't. No consistency is there.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/235367497-bb932042-82bb-43a6-9346-efe36b1b8358.mp4
https://user-images.githubusercontent.com/43996225/235367502-a32078dd-fcc9-456d-8638-56f0a8a30557.mp4
Expensify/Expensify Issue URL:
Issue reported by: @chiragxarora
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1682784275262739
View all open jobs on GitHub

Triggered auto assignment to @michaelhaxhiu (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@michaelhaxhiu Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

I'll post on the slack thread

I am not going to push this forward until we get more input form team. I'm re-assigning the label because I'm preparing to go OOO.

I'll grab this back, working a few hours from airport and the thread post is leaning toward "this is a feature not a bug". Closing for now.


Auto

Bro the account whose bearer token is added have to play with that account to get questions or it will automatically get questions without playing with that account as that account is my extra account

Please reply as soon as possible

You don't have to play with the account linked to the bearer token.


Show numeric code instead of UNKNOWN_ERROR

Helps in interpreting extended error codes which aren't included in the current SQLiteErrorCode.
In my case, allowed me to discover that
... org.sqlite.SQLiteException: [UNKNOWN_ERROR] unknown error (attempt to write a readonly database)

was really
... org.sqlite.SQLiteException: 0x608 (attempt to write a readonly database)

aka. SQLITE_READONLY_DIRECTORY because while my DB file was writable, the directory was not...

@mdavidsaver can you check the failing CI?

Seems formatting only, you can use the Spotless plugin: mvn spotless:check and mvn spotless:apply

I have 2 questions:

why display the code as 0x608 while the SQLite website display them as decimal, like 1544 ?
could we also include more error codes in SQLiteErrorCode ?

fyi. this small PR came about while troubleshooting an afternoon project ~9 months ago.  I'd like to help others avoid some frustration, but there are limits to the time I can spend on it.  If there are some quick changes I can make to get this merged, then please state this clearly.  I'm not going to be offended.  Likewise if someone would like to take this PR and go further, or do something different.

I think I looked at the C headers.  These are defined as two decimal numbers, combined with or+shift, which is kind of confusing.

$ grep SQLITE_READONLY /usr/include/sqlite3.h
#define SQLITE_READONLY     8   /* Attempt to write a readonly database */
...
#define SQLITE_READONLY_DIRECTORY      (SQLITE_READONLY | (6<<8))

Sure.

As a further idea.  I also noticed const char *sqlite3_errstr(int), which seems more future proof than maintaining a duplicate of the error string table.  However, I'm personally not keen to wade into JNI again.

I think your PR has value, and i approach it with external eyes, hopefully we can make it beneficial for everyone.
I think the error code displayed will make more sense if it can be looked up using the SQLite webpage.

As a further idea. I also noticed const char *sqlite3_errstr(int), which seems more future proof than maintaining a duplicate of the error string table. However, I'm personally not keen to wade into JNI again.

I think having the enums in Java make sense, as it can be used within the code to perform various conditions and checks. I also agree with you, we shouldn't touch JNI more than necessary 😅

I will try to update your PR to display decimal codes, and i will try to include the missing codes too.


CSS Link tag not rendering for craft.vite.script

Describe the bug
When I include {{ craft.vite.script(src/ts/index.ts) }} in my twig template, and dev server is not running, no <link rel="stylesheet" ...> tag is generated in my markup.
To reproduce
Steps to reproduce the behaviour:

npm run build - assets and manifest are generated correctly
include {{ craft.vite.script(src/ts/index.ts) }} in page template
ensure dev server is not running
load page containing craft.vite.script tag

Expected behaviour
scripts and styles are linked and loaded as described in docs: https://nystudio107.com/docs/vite/#production
Actual behavior
scripts are loaded and executed (no console errors), but style tag does not appear in page markup
Code Examples
The rendered head code:

Minimal template example:
<!DOCTYPE html>
<html lang='en'>
  <head>
    <title>{{ (pageTitle is defined ? pageTitle ~ ' - ' ~ site.siteTitle : site.siteTitle)|title }}</title>
    <meta charset='UTF-8'>
    <meta name='viewport' content='width=device-width, initial-scale=1.0'>
     {{ craft.vite.script("src/ts/index.ts", false) }}
  </head>
  <body class='flex flex-col min-h-screen'>
    {% include 'site/header'%}
    <main class='grow flex flex-col'>
      {% block main %}
      {% endblock %}
    </main>
    {% include 'site/footer' %}
  </body>
</html>

My index.ts does include an import of the css
import Alpine from 'alpinejs'
import '../css/index.css'

// Accept HMR as per: https://vitejs.dev/guide/api-hmr.html
if (import.meta.hot) {
  import.meta.hot.accept(() => {
    console.log("HMR")
  });
}

window.Alpine = Alpine
Alpine.start()

And here's my manifest.json
{
  "src/ts/index.ts": {
    "file": "assets/app.e48127f3.js",
    "src": "src/ts/index.ts",
    "isEntry": true
  },
  "style.css": {
    "file": "assets/style.92e9556c.css",
    "src": "style.css"
  }
}

Vite is generating my minified, processed css files correctly, hence why I think this is on the Plugin side.
Versions

Plugin version: 4.0.2
Craft version: <IP_ADDRESS>

Alright, after digging into the source code, I see that my src/ts/index.ts key in manifest.json should have a css key that refers to the style.css asset in order for that asset to be loaded in my template.  This seems to not be a bug with this plugin, but some failure of my vite build process to generate that key in manifest.json.

What version of Vite are you running?

vite 3.0.3. Though it was happening with 2.9.5 as well.
I found that if I have build.cssCodeSplit: true, then all works well! So I can at least move forward, though I am curious why disabling code splitting changes the manifest.json in that particular way.

That is pretty interesting. I do plan to add a way to manually include CSS tags for people who really want to do that, which is something that support was only added for in Vite 3.x
What is the default setting for build.cssCodeSplit? I'm assuming it is true?

Yes, the default is true. I had manually set it to false, but I would have expected the only difference to be that all css is never split into multiple files, not a change in the manifest pattern.
https://vitejs.dev/config/build-options.html#build-csscodesplit


Move external link directive functions to service

This movers most of the logic out of the directive and into a service, which allows much easier allows easier overriding per project via decorators

This can be released as a MINOR release, as the external API has remained and has not been broken.

@incuna/js Please review/merge

Other than that, all good

@henrahmagix Renamed to bindModal as that is what that function is responsible for

Nice, bindModal is better than any of my suggestions =)


ionic start with zip file

Using Continuous Integration, I would like to recreate and build my app with Jenkins.
In my build script, I do not want to download each time the blank template so I try to create a new Ionic app with this command :
ionic start -z /ionic-starter-blank-master.zip
It does not work and still try to download start template from: https://github.com/driftyco/ionic-app-base/archive/master.zip
I've also try the following command according to "start" help command:
ionic start -t /ionic-starter-blank-master  (with zip uncompressed)
ionic start -t blank -z /ionic-starter-blank-master.zip
I can not find the solution
Please help me :)

Have you tried just pulling your files from git and rebuilding them instead of starting a new app each time?

+1
-z doesn't seem to work at all (perhaps should be removed from the docs if it's intended).
From investigations so far it seems like it's getting parsed and then completely ignored by https://github.com/driftyco/ionic-app-lib/blob/master/lib/utils.js#L188 i suspect it needs to add it as options.zipFileDownload but trying that out locally I seem to be missing quite a few other steps as well (the zip files downloading but the end project is still a blank starter project).

Oh and as an explanation, i'm looking for a way to let people start projects based off a zip file.

@jbavari the main purpose for me is to rebuild from scratch the application with continuous integration...
@jawache I managed to create my own template by not using "ionic start" but instead merging those 2 zip from :
https://github.com/driftyco/ionic-app-base
and
https://github.com/driftyco/ionic-starter-blank
then you can replace resources, www or any content and use ionic commands (do not forget to do npm install & bower install if necessary)
@jbavari if -z or any other option could work from zip or local directory it would be nice ! Perhaps you have a better idea for continuous integration process ?
To both of you, thanks for your help !!!

Greetings @skyfitz79!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


CI: K8sIdentity Identity expiration Expiration of CiliumIdentity: Unable to restore endpoint (interface lxc... could not be found)

Suite-k8s-1.18.K8sIdentity Identity expiration Expiration of CiliumIdentity
Initial triage suggests that this is a test pollution issue from Bookinfo tests, and is likely to affect other tests depending on test ordering.
https://jenkins.cilium.io/job/Cilium-PR-K8s-newest-kernel-4.9/318/testReport/junit/Suite-k8s-1/18/K8sIdentity_Identity_expiration_Expiration_of_CiliumIdentity/
test_results_Cilium-PR-K8s-newest-kernel-4.9_318_BDD-Test-PR.zip
Stacktrace
/home/jenkins/workspace/Cilium-PR-K8s-newest-kernel-4.9/k8s-1.18-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:387
Found 1 Cilium logs matching list of errors that must be investigated
/home/jenkins/workspace/Cilium-PR-K8s-newest-kernel-4.9/k8s-1.18-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:385

Standard Output
⚠  Found a "JoinEP: " in logs
Number of "context deadline exceeded" in logs: 0
⚠  Number of "level=error" in logs: 6
⚠  Number of "level=warning" in logs: 50
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
Top 5 errors/warnings:
removing identity not added to the identity manager!
Error while rewriting endpoint BPF program
before filtering labels during regenerating restored endpoint
endpoint regeneration failed
Mutation detector is enabled, this will result in memory leakage.
Cilium pods: [cilium-lmkhb cilium-rpnbj]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod                             Ingress   Egress
hubble-cli-j5n24
hubble-cli-tw429
hubble-relay-58c8798f47-xhsgn
coredns-7964865f77-wxxxc
Cilium agent 'cilium-lmkhb': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 26 Failed 0
Cilium agent 'cilium-rpnbj': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 19 Failed 0

Standard Error
08:37:41 STEP: Running BeforeAll block for K8sIdentity
08:37:41 STEP: Ensuring the namespace kube-system exists
08:37:41 STEP: Deleting cep [details-v1-55cf6d74d-k98wn,reviews-v1-6948677f85-mnb8v,reviews-v2-77c4d85c6c-8kzqk] in namespace default
08:37:41 STEP: Waiting for 3 deletes to return (details-v1-55cf6d74d-k98wn,reviews-v1-6948677f85-mnb8v,reviews-v2-77c4d85c6c-8kzqk)
08:37:41 STEP: Unable to delete cep details-v1-55cf6d74d-k98wn with 'kubectl -n default delete cep details-v1-55cf6d74d-k98wn': Exitcode: 1
Stdout:

Stderr:
 	 Error from server (NotFound): ciliumendpoints.cilium.io "details-v1-55cf6d74d-k98wn" not found

08:37:41 STEP: Installing Cilium
08:37:42 STEP: Waiting for Cilium to become ready
08:37:42 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
08:37:47 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
08:37:52 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
08:37:57 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
08:38:02 STEP: Number of ready Cilium pods: 2
08:38:02 STEP: Installing DNS Deployment
08:38:02 STEP: Restarting DNS Pods
08:38:09 STEP: Validating Cilium Installation
08:38:09 STEP: Performing Cilium controllers preflight check
08:38:09 STEP: Performing Cilium status preflight check
08:38:09 STEP: Performing Cilium health check
08:38:12 STEP: Performing Cilium service preflight check
08:38:12 STEP: Performing K8s service preflight check
08:38:12 STEP: Waiting for cilium-operator to be ready
08:38:12 STEP: Waiting for kube-dns to be ready
08:38:12 STEP: Running kube-dns preflight check
08:38:15 STEP: Performing K8s service preflight check
08:38:16 STEP: Making sure all endpoints are in ready state
08:38:17 STEP: Creating unused CiliumIdentity
08:38:17 STEP: Waiting for CiliumIdentity to be garbage collected
=== Test Finished at 2020-05-21T08:38:22Z====
08:38:22 STEP: Running JustAfterEach block for K8sIdentity
FAIL: Found 1 Cilium logs matching list of errors that must be investigated
===================== TEST FAILED =====================
08:38:22 STEP: Running AfterFailed block for K8sIdentity
cmd: kubectl get pods -o wide --all-namespaces
Exitcode: 0
Stdout:
 	 NAMESPACE     NAME                               READY   STATUS             RESTARTS   AGE   IP              NODE   NOMINATED NODE   READINESS GATES
	 kube-system   cilium-lmkhb                       1/1     Running            0          41s   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system   cilium-operator-6c758b54bf-68sbw   1/1     Running            0          41s   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system   cilium-rpnbj                       1/1     Running            0          41s   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system   coredns-7964865f77-wxxxc           1/1     Running            0          21s   <IP_ADDRESS>       k8s2   <none>           <none>
	 kube-system   etcd-k8s1                          1/1     Running            0          17m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system   hubble-cli-j5n24                   0/1     CrashLoopBackOff   5          13m   <IP_ADDRESS>      k8s1   <none>           <none>
	 kube-system   hubble-cli-tw429                   0/1     CrashLoopBackOff   5          13m   <IP_ADDRESS>      k8s2   <none>           <none>
	 kube-system   hubble-relay-58c8798f47-xhsgn      1/1     Running            0          13m   <IP_ADDRESS>      k8s2   <none>           <none>
	 kube-system   kube-apiserver-k8s1                1/1     Running            0          17m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system   kube-controller-manager-k8s1       1/1     Running            0          17m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system   kube-proxy-mbkzb                   1/1     Running            0          17m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system   kube-proxy-szqxv                   1/1     Running            0          16m   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system   kube-scheduler-k8s1                1/1     Running            0          17m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system   log-gatherer-69z26                 1/1     Running            0          15m   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system   log-gatherer-wbfqv                 1/1     Running            0          15m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system   registry-adder-9jr2j               1/1     Running            0          15m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system   registry-adder-ps2ql               1/1     Running            0          15m   <IP_ADDRESS>   k8s2   <none>           <none>

Stderr:

Fetching command output from pods [cilium-lmkhb cilium-rpnbj]
cmd: kubectl exec -n kube-system cilium-lmkhb -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                       IPv6       IPv4         STATUS
	            ENFORCEMENT        ENFORCEMENT
	 2          Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s2                                                ready
	                                                            reserved:host
	 177        Disabled           Disabled          4          reserved:health                                   fd00::98   <IP_ADDRESS>   ready
	 1017       Disabled           Disabled          1797       k8s:io.cilium.k8s.policy.cluster=default          fd00::b    <IP_ADDRESS>    ready
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=coredns
	                                                            k8s:io.kubernetes.pod.namespace=kube-system
	                                                            k8s:k8s-app=kube-dns
	 1623       Disabled           Disabled          2044       k8s:io.cilium.k8s.policy.cluster=default          fd00::7c   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=kube-system
	                                                            k8s:k8s-app=hubble-cli
	 3562       Disabled           Disabled          56769      k8s:io.cilium.k8s.policy.cluster=default          fd00::82   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=kube-system
	                                                            k8s:k8s-app=hubble-relay

Stderr:

cmd: kubectl exec -n kube-system cilium-rpnbj -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                       IPv6        IPv4         STATUS
	            ENFORCEMENT        ENFORCEMENT
	 269        Disabled           Disabled          2044       k8s:io.cilium.k8s.policy.cluster=default          fd00::172   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
	                                                            k8s:io.kubernetes.pod.namespace=kube-system
	                                                            k8s:k8s-app=hubble-cli
	 1342       Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s1                                                 ready
	                                                            k8s:node-role.kubernetes.io/master
	                                                            reserved:host
	 4048       Disabled           Disabled          4          reserved:health                                   fd00::16b   <IP_ADDRESS>    ready

Stderr:

===================== Exiting AfterFailed =====================
08:39:13 STEP: Running AfterEach for block EntireTestsuite

08:39:13 STEP: Running AfterAll block for K8sIdentity

From the pod-kube-system-cilium-rpnbj-cilium-agent.log:
2020-05-21T08:37:47.977484834Z level=warning msg="Unable to restore endpoint, ignoring" endpointID=390 error="interface lxcac2ec8525ac7 could not be found" k8sPodName=default/reviews-v2-77c4d85c6c-8kzqk subsys=daemon

Note the pod name here, reviews-v2. Seems like a leftover from an Istio test.
Seems like the list of events is something like:

reviews-v2 is deployed
Cilium is restarted
After Cilium processes the list of endpoints to restore, the reviews-v2 pod is finally deleted from k8s
Cilium is still regenerating the endpoint, and then fails because the device has disappeared underneath it.

Two possible avenues for exploring fixes:

Look into how Cilium subscribes to pod deletion events during startup to see whether there is a way to 'cancel' this regeneration quietly. Benefits: No extraneous log messages. Downsides: Probably more work, and it's not clear that this is a real bug.
Look at the tests for testsuites that deploy reviews-v2 pod and ensure that the pods are all fully cleaned up before proceeding to the next test like this one. Then we shouldn't see these logs at all in subsequent tests and hence resolve this occasional flake.

Looks like "Istio" is wrong, it's more about the "bookinfo" test that runs prior to this test. Tail of previous test + log of this one from jenkins console:
01:37:42  • [SLOW TEST:47.961 seconds]
01:37:42  K8sServicesTest
01:37:42  /home/jenkins/workspace/Cilium-PR-K8s-newest-kernel-4.9/k8s-1.18-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:436
01:37:42    Bookinfo Demo
01:37:42    /home/jenkins/workspace/Cilium-PR-K8s-newest-kernel-4.9/k8s-1.18-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:436
01:37:42      Tests bookinfo demo
01:37:42      /home/jenkins/workspace/Cilium-PR-K8s-newest-kernel-4.9/k8s-1.18-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:471
01:37:42  ------------------------------
01:37:42  K8sIdentity Identity expiration
01:37:42    Expiration of CiliumIdentity
01:37:42    /home/jenkins/workspace/Cilium-PR-K8s-newest-kernel-4.9/k8s-1.18-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:471
01:37:42  08:37:41 STEP: Running BeforeAll block for K8sIdentity
01:37:42  08:37:41 STEP: Ensuring the namespace kube-system exists
01:37:42  08:37:41 STEP: Deleting cep [details-v1-55cf6d74d-k98wn,reviews-v1-6948677f85-mnb8v,reviews-v2-77c4d85c6c-8kzqk] in namespace default
01:37:42  08:37:41 STEP: Waiting for 3 deletes to return (details-v1-55cf6d74d-k98wn,reviews-v1-6948677f85-mnb8v,reviews-v2-77c4d85c6c-8kzqk)
01:37:42  08:37:41 STEP: Unable to delete cep details-v1-55cf6d74d-k98wn with 'kubectl -n default delete cep details-v1-55cf6d74d-k98wn': Exitcode: 1
01:37:42  Stdout:
01:37:42
01:37:42  Stderr:
01:37:42   	 Error from server (NotFound): ciliumendpoints.cilium.io "details-v1-55cf6d74d-k98wn" not found
01:37:42
01:37:42
01:37:42  08:37:41 STEP: Installing Cilium
01:37:42  08:37:42 STEP: Waiting for Cilium to become ready
01:37:42  08:37:42 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
01:37:48  08:37:47 STEP: Cilium DaemonSet not ready yet: only 0 of 2 desired pods are ready
01:37:52  08:37:52 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
01:37:58  08:37:57 STEP: Cilium DaemonSet not ready yet: only 1 of 2 desired pods are ready
01:38:02  08:38:02 STEP: Number of ready Cilium pods: 2
01:38:02  08:38:02 STEP: Installing DNS Deployment
01:38:02  08:38:02 STEP: Restarting DNS Pods
01:38:09  08:38:09 STEP: Validating Cilium Installation
01:38:09  08:38:09 STEP: Performing Cilium controllers preflight check
01:38:09  08:38:09 STEP: Performing Cilium status preflight check
01:38:09  08:38:09 STEP: Performing Cilium health check
01:38:12  08:38:12 STEP: Performing Cilium service preflight check
01:38:12  08:38:12 STEP: Performing K8s service preflight check
01:38:12  08:38:12 STEP: Waiting for cilium-operator to be ready
01:38:12  08:38:12 STEP: Waiting for kube-dns to be ready
01:38:12  08:38:12 STEP: Running kube-dns preflight check
01:38:16  08:38:15 STEP: Performing K8s service preflight check
01:38:16  08:38:16 STEP: Making sure all endpoints are in ready state
01:38:17  08:38:17 STEP: Creating unused CiliumIdentity
01:38:17  08:38:17 STEP: Waiting for CiliumIdentity to be garbage collected
01:38:23  === Test Finished at 2020-05-21T08:38:22Z====
01:38:23  08:38:22 STEP: Running JustAfterEach block for K8sIdentity
01:38:23  FAIL: Found 1 Cilium logs matching list of errors that must be investigated
01:38:23  ===================== TEST FAILED =====================
01:38:23  08:38:22 STEP: Running AfterFailed block for K8sIdentity
01:38:23  cmd: kubectl get pods -o wide --all-namespaces
01:38:23  Exitcode: 0
01:38:23  Stdout:
01:38:23   	 NAMESPACE     NAME                               READY   STATUS             RESTARTS   AGE   IP              NODE   NOMINATED NODE   READINESS GATES
01:38:23  	 kube-system   cilium-lmkhb                       1/1     Running            0          41s   <IP_ADDRESS>   k8s2   <none>           <none>
01:38:23  	 kube-system   cilium-operator-6c758b54bf-68sbw   1/1     Running            0          41s   <IP_ADDRESS>   k8s2   <none>           <none>
01:38:23  	 kube-system   cilium-rpnbj                       1/1     Running            0          41s   <IP_ADDRESS>   k8s1   <none>           <none>
01:38:23  	 kube-system   coredns-7964865f77-wxxxc           1/1     Running            0          21s   <IP_ADDRESS>       k8s2   <none>           <none>
01:38:23  	 kube-system   etcd-k8s1                          1/1     Running            0          17m   <IP_ADDRESS>   k8s1   <none>           <none>
01:38:23  	 kube-system   hubble-cli-j5n24                   0/1     CrashLoopBackOff   5          13m   <IP_ADDRESS>      k8s1   <none>           <none>
01:38:23  	 kube-system   hubble-cli-tw429                   0/1     CrashLoopBackOff   5          13m   <IP_ADDRESS>      k8s2   <none>           <none>
01:38:23  	 kube-system   hubble-relay-58c8798f47-xhsgn      1/1     Running            0          13m   <IP_ADDRESS>      k8s2   <none>           <none>
01:38:23  	 kube-system   kube-apiserver-k8s1                1/1     Running            0          17m   <IP_ADDRESS>   k8s1   <none>           <none>
01:38:23  	 kube-system   kube-controller-manager-k8s1       1/1     Running            0          17m   <IP_ADDRESS>   k8s1   <none>           <none>
01:38:23  	 kube-system   kube-proxy-mbkzb                   1/1     Running            0          17m   <IP_ADDRESS>   k8s1   <none>           <none>
01:38:23  	 kube-system   kube-proxy-szqxv                   1/1     Running            0          16m   <IP_ADDRESS>   k8s2   <none>           <none>
01:38:23  	 kube-system   kube-scheduler-k8s1                1/1     Running            0          17m   <IP_ADDRESS>   k8s1   <none>           <none>
01:38:23  	 kube-system   log-gatherer-69z26                 1/1     Running            0          15m   <IP_ADDRESS>   k8s2   <none>           <none>
01:38:23  	 kube-system   log-gatherer-wbfqv                 1/1     Running            0          15m   <IP_ADDRESS>   k8s1   <none>           <none>
01:38:23  	 kube-system   registry-adder-9jr2j               1/1     Running            0          15m   <IP_ADDRESS>   k8s1   <none>           <none>
01:38:23  	 kube-system   registry-adder-ps2ql               1/1     Running            0          15m   <IP_ADDRESS>   k8s2   <none>           <none>
01:38:23
01:38:23  Stderr:
01:38:23
01:38:23
01:38:23  Fetching command output from pods [cilium-lmkhb cilium-rpnbj]
01:39:21  cmd: kubectl exec -n kube-system cilium-lmkhb -- cilium endpoint list
01:39:21  Exitcode: 0
01:39:21  Stdout:
01:39:21   	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                       IPv6       IPv4         STATUS
01:39:21  	            ENFORCEMENT        ENFORCEMENT
01:39:21  	 2          Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s2                                                ready
01:39:21  	                                                            reserved:host
01:39:21  	 177        Disabled           Disabled          4          reserved:health                                   fd00::98   <IP_ADDRESS>   ready
01:39:21  	 1017       Disabled           Disabled          1797       k8s:io.cilium.k8s.policy.cluster=default          fd00::b    <IP_ADDRESS>    ready
01:39:21  	                                                            k8s:io.cilium.k8s.policy.serviceaccount=coredns
01:39:21  	                                                            k8s:io.kubernetes.pod.namespace=kube-system
01:39:21  	                                                            k8s:k8s-app=kube-dns
01:39:21  	 1623       Disabled           Disabled          2044       k8s:io.cilium.k8s.policy.cluster=default          fd00::7c   <IP_ADDRESS>   ready
01:39:21  	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
01:39:21  	                                                            k8s:io.kubernetes.pod.namespace=kube-system
01:39:21  	                                                            k8s:k8s-app=hubble-cli
01:39:21  	 3562       Disabled           Disabled          56769      k8s:io.cilium.k8s.policy.cluster=default          fd00::82   <IP_ADDRESS>   ready
01:39:21  	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
01:39:21  	                                                            k8s:io.kubernetes.pod.namespace=kube-system
01:39:21  	                                                            k8s:k8s-app=hubble-relay
01:39:21
01:39:21  Stderr:
01:39:21
01:39:21
01:39:21  cmd: kubectl exec -n kube-system cilium-rpnbj -- cilium endpoint list
01:39:21  Exitcode: 0
01:39:21  Stdout:
01:39:21   	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                       IPv6        IPv4         STATUS
01:39:21  	            ENFORCEMENT        ENFORCEMENT
01:39:21  	 269        Disabled           Disabled          2044       k8s:io.cilium.k8s.policy.cluster=default          fd00::172   <IP_ADDRESS>   ready
01:39:21  	                                                            k8s:io.cilium.k8s.policy.serviceaccount=default
01:39:21  	                                                            k8s:io.kubernetes.pod.namespace=kube-system
01:39:21  	                                                            k8s:k8s-app=hubble-cli
01:39:21  	 1342       Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s1                                                 ready
01:39:21  	                                                            k8s:node-role.kubernetes.io/master
01:39:21  	                                                            reserved:host
01:39:21  	 4048       Disabled           Disabled          4          reserved:health                                   fd00::16b   <IP_ADDRESS>    ready
01:39:21
01:39:21  Stderr:
01:39:21
01:39:21
01:39:21  ===================== Exiting AfterFailed =====================
01:39:21  08:39:13 STEP: Running AfterEach for block EntireTestsuite
01:39:21  <Checks>
01:39:21  ⚠  Found a "JoinEP: " in logs
01:39:21  Number of "context deadline exceeded" in logs: 0
01:39:21  ⚠  Number of "level=error" in logs: 6
01:39:21  ⚠  Number of "level=warning" in logs: 50
01:39:21  Number of "Cilium API handler panicked" in logs: 0
01:39:21  Number of "Goroutine took lock for more than" in logs: 0
01:39:21  Top 5 errors/warnings:
01:39:21  removing identity not added to the identity manager!
01:39:21  Error while rewriting endpoint BPF program
01:39:21  before filtering labels during regenerating restored endpoint
01:39:21  endpoint regeneration failed
01:39:21  Mutation detector is enabled, this will result in memory leakage.
01:39:21  Cilium pods: [cilium-lmkhb cilium-rpnbj]
01:39:21  Netpols loaded:
01:39:21  CiliumNetworkPolicies loaded:
01:39:21  Endpoint Policy Enforcement:
01:39:21  Pod                             Ingress   Egress
01:39:21  hubble-cli-j5n24
01:39:21  hubble-cli-tw429
01:39:21  hubble-relay-58c8798f47-xhsgn
01:39:21  coredns-7964865f77-wxxxc
01:39:21  Cilium agent 'cilium-lmkhb': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 26 Failed 0
01:39:21  Cilium agent 'cilium-rpnbj': Status: Ok  Health: Ok Nodes "" ContinerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 19 Failed 0
01:39:21
01:39:21  </Checks>
01:39:21
01:39:21  08:39:13 STEP: Running AfterAll block for K8sIdentity
01:39:21
01:39:21  • Failure in Spec Teardown (AfterEach) [91.787 seconds]
01:39:21  K8sIdentity
01:39:21  /home/jenkins/workspace/Cilium-PR-K8s-newest-kernel-4.9/k8s-1.18-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:436
01:39:21    Identity expiration [AfterEach]
01:39:21    /home/jenkins/workspace/Cilium-PR-K8s-newest-kernel-4.9/k8s-1.18-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:436
01:39:21      Expiration of CiliumIdentity
01:39:21      /home/jenkins/workspace/Cilium-PR-K8s-newest-kernel-4.9/k8s-1.18-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:471
01:39:21
01:39:21      Found 1 Cilium logs matching list of errors that must be investigated
01:39:21
01:39:21      /home/jenkins/workspace/Cilium-PR-K8s-newest-kernel-4.9/k8s-1.18-gopath/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:385
01:39:21  ------------------------------

Possibly the same issue as https://github.com/cilium/cilium/issues/11076


Pallas Tutorial outputs RESOURCE_EXHAUSTED

Description
Hi there,
I am trying to learn Pallas by running the code bits from the official documentation from Jax but I am having trouble understanding why I'm short on GPU memory.
from functools import partial
import jax
from jax.experimental import pallas as pl
import jax.numpy as jnp
import numpy as np

def matmul_kernel(x_ref, y_ref, z_ref):
  z_ref[...] = x_ref[...] @ y_ref[...]

def matmul(x: jax.Array, y: jax.Array):
  return pl.pallas_call(
    matmul_kernel,
    out_shape=jax.ShapeDtypeStruct((x.shape[0], y.shape[1]), x.dtype),
    grid=(2, 2),
    in_specs=[
      pl.BlockSpec(lambda i, j: (i, 0), (x.shape[0] // 2, x.shape[1])),
      pl.BlockSpec(lambda i, j: (0, j), (y.shape[0], y.shape[1] // 2))
    ],
    out_specs=pl.BlockSpec(
      lambda i, j: (i, j), (x.shape[0] // 2, y.shape[1] // 2)
    )
  )(x, y)
k1, k2 = jax.random.split(jax.random.PRNGKey(43))
x = jax.random.normal(k1, (1024, 1024))
y = jax.random.normal(k2, (1024, 1024))
z = matmul(x, y)
np.testing.assert_allclose(z, x @ y)

This code which is copy pasted from the documentation (except for the PRNGKey) is giving me the following error:
XlaRuntimeError: RESOURCE_EXHAUSTED: Shared memory size limit exceeded: requested 4194304, available: 101376
I saw that to manage memory allocation, we can set 3 environment variables to skip the part where Jax pre-allocates 75% of the memory, but it is still giving me the error.
Any ideas on this? First time really diving into GPUs so I might not have all the theoretical concepts.
System info (python version, jaxlib version, accelerator, etc.)
jax=0.4.25
jaxlib=0.4.25+cuda11.cudnn86
jaxtyping=0.2.25
python=3.11.8

Why did I close the issue? Just realised someone else was on the shared GPU, I ran the code with smaller matrices and it works fine.


Reconfigure spin watch on manifest change

This went through many extremely untidy stages and I surely need to read over it again (and do a bunch more testing), but it seems to work correctly.  Yay!  Now let us never speak of it again

I will take a look at this when I'm back from Peru in a week and a half.

Good call.  There are a lot of moving parts and the names don't express well how they fit together.  Thank you for taking the time to review and to test!  (And I hope Peru was great!)


Extend listener interface with imported() method

A new listener method that gets events when something is imported is needed.

It must be possible to separate library and resource import and also get notification about variables. We could have separate library, resource and variables methods, but it's probably better to have imported method that gets the import type as the first argument. The listener API already has output_file method that works similarly.
copied from: https://github.com/robotframework/robotframework/pull/2026#issuecomment-112553868

Have you had time to look at this? We are going to release beta 1 on Friday and there's no time to get this included into it anymore. We try to get beta 2 or perhaps even rc 1 out next week. We thus need to get this implemented early next week to be able to also get #1936 in. I can also take a look at this myself after we've got other issues done.

In order to track transitive imports from resource files, the imported-method will need as an argument the origin of the import (the file in which the import happens as a path) and then probably also it would be a good idea to include the path to the imported file as a source. With that information it should be possible to map a tree about the imports.

@jussimalinen, I reviewed the final version of code and tests and everything looked good. I did a little clean-up for tests in the previous commit, though, and also added docs a little earlier. Please review my changes and we pretty close to cal this issue done.
When writing docs, I noticed keys in attribute dicts consisting of multiple words have earlier used wordstogether style like starttime and totaltests. Should we be consistent and change new original_name to originalname or origname?

Consistency is good, so I it should be changed. I would prefer originalname  over origname.

Yeah, let's use originalname.


Raise errors for validataclasses with missing type annotations

Currently, the following code will raise an AttributeError because the class has no attribute __annotations__:
@validataclass
class ExampleClass:
    pass

You can replace the decorator with the usual @dataclass validator if you need an empty dataclass, but it would be more intuitive if the @validataclass decorator worked here too. So, simply check if __annotations__ exists and silently return if it doesn't.
... BUT there is a catch to this solution: It could hide potential errors and make debugging difficult.
@validataclass
class ExampleClass:
    some_field = IntegerValidator()

In this example, it's most likely an error that the field is missing the type annotation (some_field: int = IntegerValidator()). This would mean that the field doesn't even exist as a dataclass field at all. Currently, the AttributeError would be raised, so the error would be noticed.
So, better solution: Raise an error if __annotations__ is empty, but with a more userfriendly error message, and implement a parameter allow_empty that can be set to explicitly allow an empty dataclass (e.g. @validataclass(allow_empty=True).
Better solution: Detect fields with missing annotations directly, and raise errors about that. But only if the value of a field is of type Validator, Default or a tuple containing one of those (so that you can still define class variables without type annotations that are not supposed to be validated fields).

Solved in #27.


tests: move xfail out of functions

I had a look at the flox tests and moved the xfails out of the function body. This is marginally faster as the skipping happens at collection time.
(It's is certainly not worth it but I couldn't sleep..., let me know if any of them look too ugly)

This is great. Thank you!


Smorgrav/tenantinfo get api

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

This should implement the read functionality for tenant info at tenant/info
I also took the opportunity to start refactor these classes due to their size.


Api remove register mds

Current coverage is 82.37% (diff: 40.00%)

Merging #557 into master will decrease coverage by 0.26%

@@             master       #557   diff @@
==========================================
  Files            21         20     -1
  Lines          4032       4017    -15
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           3332       3309    -23
- Misses          700        708     +8
  Partials          0          0

Powered by Codecov. Last update 5cd3b9e...9342ca1


[EtsyBridge] Repair bridge and flip checkbox

Flip the checkbox because the absence of a checkbox cannot be detected and the default is desired to be checked.

Tested. Looks broken still?

@dvikan Seems the website was changed since the PR. I updated the classes

Patch doesnt apply. Can you merge master into your branch?

Rebased onto master

This change breaks existing feeds e.g. http://rssbridge.localhost/?action=display&bridge=Etsy&query=lamp&queryextension=&showimage=on&format=Html
Because the showimage option was removed.
Etsy search was unable to receive or process the remote website's content!
Error message: `Invalid parameters value(s): showimage`
Query string: `action=display&bridge=Etsy&query=lamp&queryextension=&showimage=on&format=Html`
Version: `git.master.6d4155f`

Other than that the bridge was repaired!

I considered the breaking changes, but I think it is best to go ahead with breaking it, since the option was previously useless. I guess one solution is to keep the showimage parameter but make the default off, but I don't like that since Etsy heavily depends on images.

Since we don't have a way to hide legacy options I think it's okay to break it. Also because it was already broken.


Naming llava models

Question
Hello
Some confusing models name: Llava-Plus, Llava-1.6 and Llava-Next.  Which one is the latest and gives the best overall results?

Llava-Next is the rename of Llava-1.6 (the name Llava-1.6 is deprecated), which provides the best overall results as a single Large Multimodal Model (LMM). The document is at: https://llava-vl.github.io/blog/2024-01-30-llava-next/

Llava-Plus (Plug and Learn to Use Skills), is an extension of LLaVA/LMM to build multimodal agent with external tool use. The document is at: https://arxiv.org/abs/2311.05437


Fix CSS imports when using tailwind rails and propshaft

Is this related to the error I am getting on a fresh install?
Error: Failed to find 'highlight.js/styles/github-dark.css' 13:25:32 css.1  |   in [ 13:25:32 css.1  |     /Users/niklas/work/kursus/app/assets/stylesheets 13:25:32 css.1  |   ] 13:25:32 css.1  |     at /snapshot/tailwindcss/node_modules/postcss-import/lib/resolve-id.js:35:13 13:25:32 css.1  |     at async LazyResult.runAsync (/snapshot/tailwindcss/node_modules/postcss/lib/lazy-result.js:261:11) 13:25:32 css.1  |     at async Object.watch (/snapshot/tailwindcss/lib/cli/build/plugin.js:370:13) 13:25:32 css.1  |     at async build (/snapshot/tailwindcss/lib/cli/build/index.js:47:9)


Allowing browser names containing a space

ua-parser-js can return browser names containing a space (such as "Chrome Headless").

@benouat Thank you for your review!


Adding a Group in editor should offer drop-down or autocomplete

Godot 3.0
When adding a node to a group from the Node dock in the editor, it would be nice if the engine could survey the other groups that have been created in the game, and list them in a drop-down in the field next to the "Add" button.
For that matter, it would be nice if calling the is_in_group  function could do the same thing, listing all the groups that have been added to the game.

Related to #5744.

Fixed by #16502.


Bump dependencies to upstream 1.24

Update dependencies to versions based on upstream v1.24

/assign @thejasn @alebedev87

/label px-approved
/label qe-approved
/label docs-approved


[Worker Task] Ability to define output properties on HTTP Call Task with JsonPath

Is your request related to a problem? Please describe.
When making a HTTP call, a response may be received. We want to be able to define output properties based on elements in the response body.
Describe the solution you'd like
Define multiple output properties in an easy to use way based on JsonPath
Describe the benefits or justification for this request
Currently we have to have multiple steps to process the output property using the JsonPath to Property task where as it could be all in one.
Additional context
n/a

Lowered priority as you can run the HTTP task and the result body will be an output parameter that you can then use the JsonPath to Property task to filter further.

Rejecting as will no longer be needed with the new Tekton Results implementations.


Increment version for identity releases

Increment package version after release of com.azure azure-identity

Closing this, as it doesn't target master branch.


pipewire: fix build without gstreamer support

Description of changes
Gate support for the gstreamer-device-provider behind the gstreamerSuppert flag. gstreamer-device-provider requires glib-2.0 as well as all the gstreamer dependences which are only pulled in when gstreamerSupport is enabled.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This will have to go to staging.

Sorry about the label/reviewer pings. I didn't mark the PR as draft before rebasing. Should I close this PR and reopen a new PR without them?

Yes.


Overflow of vertical space / z-index?

Issue Type (delete the irrelevant ones)

[x] Bug (likely not a bug)
[x] General Question

Specs
What version are you using?
2.21.10
What browser?

Chrome
Safari

Expected Behavior
What did you expect to happen?
I'm creating a control to help users delete multiple records or update their status using a bootstrap button select element.  I want the element displaying the menu items to expand over the table rows.
Actual Behavior
What actually happened?
When adding interactive elements in the column template that expand beyond the height of the table, the z-index seems to expand below the table and overflow out of sight.
Steps to Reproduce the Problem
Add this element to a column template:
              <vue-good-table
                  :columns="columns"
                  :rows="rows">

              <template slot="table-column" slot-scope="props">

                      <button id="btnGroupDrop1" type="button" class="btn btn-secondary dropdown-toggle" data-bs-toggle="dropdown" aria-expanded="false">
                        Dropdown
                      </button>

Dropdown link

Dropdown link

            </template>
           ...

hey @dyerrington sorry for the delay. Does bootstrap button select element have an 'attach-to-body' property? What's happening is that the js/css is attaching the dropdown element to the button itself. It is a known issue and not related to VGT specifically.
closing.


Create guestbook-logs-metrics-with-elk.md

zh-trans guestbook-logs-metrics-with-elk.md
ref:k8smeetup/website-tasks#3362

Dup of #22870 ?
/hold

Dup of #22870 ?
/hold

yes, the content is the same, I don't know how to delete one.

Close as dup
/close


Http Error 500 Using If in razor view

Using the following line of code in a MVC 6 razor view generates a Server Error 500, why ?
I have double checked the model and it works fine, The problem only occurs when I add the if statement.
The code is working fine in MVC5.
<div class="form-group" style="@if (Model.Id=="") {<Text>display:none;</Text>}">

Doing a bit more of testing and the following code also works:

If you add the developer exception page, you should be able to see the exception message.
https://github.com/aspnet/Diagnostics/blob/dev/samples/DeveloperExceptionPageSample/Startup.cs#L11

Yeah, that's what's strange.
I have it enabled, still only getting the HTTP 500 error crash without any more info.

Is your environment set to Development? Are you launching from VS or from the console? If console, set ASPNET_ENV=Development

Launching from VS and have the ASPNET_ENV=Development .
However, when I started a new ASP 5 Web project and added the following code to the Index.cshtml page:
display:none;}">
  Hide Me

The following error occurred:
Not all code paths return a value in lambda expression of type 'Func<TextWriter, Task>'
See attached screen shoot

/cc @pranavkm @NTaylorMullen

Can you list your project.json and perhaps a screenshot of the References node in vs expanded to list the versions of Mvc and Razor being used? The lambda generated as parameter to WriteAttributeValue should be async as of beta8 (this would be the Razor issue tracking the change - https://github.com/aspnet/Razor/issues/494).

Sure thing:
{
"version": "1.0.0-*",
"compilationOptions": {
"emitEntryPoint": true
},
"dependencies": {
"Microsoft.AspNet.Diagnostics": "1.0.0-rc1-final",
"Microsoft.AspNet.IISPlatformHandler": "1.0.0-rc1-final",
"Microsoft.AspNet.Mvc": "6.0.0-rc1-final",
"Microsoft.AspNet.Mvc.TagHelpers": "6.0.0-rc1-final",
"Microsoft.AspNet.Server.Kestrel": "1.0.0-rc1-final",
"Microsoft.AspNet.StaticFiles": "1.0.0-rc1-final",
"Microsoft.AspNet.Tooling.Razor": "1.0.0-rc1-final",
"Microsoft.Extensions.Configuration.FileProviderExtensions" : "1.0.0-rc1-final",
"Microsoft.Extensions.Configuration.Json": "1.0.0-rc1-final",
"Microsoft.Extensions.Logging": "1.0.0-rc1-final",
"Microsoft.Extensions.Logging.Console": "1.0.0-rc1-final",
"Microsoft.Extensions.Logging.Debug": "1.0.0-rc1-final",
"Microsoft.VisualStudio.Web.BrowserLink.Loader": "14.0.0-rc1-final"
},
"commands": {
"web": "Microsoft.AspNet.Server.Kestrel"
},
"frameworks": {
"dnx451": { },
"dnxcore50": { }
},
"exclude": [
"wwwroot",
"node_modules"
],
"publishExclude": [
".user",
".vspscc"
],
"scripts": {
"prepublish": [ "npm install", "bower install", "gulp clean", "gulp min" ]
}
}

Here is an example project, showing the problem.
Just run the app and it will show the error.
BugHunt.zip

Duplicate of: https://github.com/aspnet/Razor/issues/594
Is fixed for next release :smile:

Nice :)

I also face this. So annoying but at least ternary syntax works for now.


Use response.ok in error-handling docs.

Checking the response status is in the 2xx range is equivalent to checking .ok.
https://github.com/github/fetch/blob/master/fetch.js#L334
This has the added benefit of documenting that API (.ok is a little vague), and making the example code a bit simpler (albeit less explicit).
PS - since this is just a small edit spanning two commits, I think it would be better to squash it in.

The ok attribute is documented in the specification. Also see #278.


[Event Request] page 5600 "Fixed Asset Card" – ShowAcquireNotification

Could we please have a publisher OnBeforeShowAcquireNotification in function ShowAcquireNotification page 5600 "Fixed Asset Card"
     local procedure ShowAcquireNotification()
    var
        ShowAcquireNotification: Boolean;
        // start kvsmed - Variables added
        IsHandled: Boolean;
    // stop kvsmed - Variables added
    begin
        // start kvsmed - Event Raiser
        OnBeforeShowAcquireNotification(Rec, Acquirable, IsHandled);
        if IsHandled then
            exit;
        // stop kvsmed - Event Raiser

        ShowAcquireNotification :=
          (not Acquired) and FieldsForAcquitionInGeneralGroupAreCompleted and AtLeastOneDepreciationLineIsComplete;
        if ShowAcquireNotification and IsNullGuid(FAAcquireWizardNotificationId) then begin
            Acquirable := true;
            ShowAcquireWizardNotification;
        end else
            Acquirable := false;
    end;

    // start kvsmed - Event Publisher
    [IntegrationEvent(false, false)]
    local procedure OnBeforeShowAcquireNotification(FixedAsset: Record "Fixed Asset"; var Acquirable: Boolean; var Handled: Boolean)
    begin
    end;
    // stop kvsmed - Event Publisher

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


OptiX 7.5 and nvcuda

@Saancreed @jp7677
I have so far not "released" wine-nvoptix for the new SDK 7.5 version, as per default this would require CUDA SDK 11.7 support. And i am having severe issues getting that to work.
I created a separate issuethread over at my nvcuda devel page since it is not directly related to wine-nvoptix, but would very much appreciate it if you guys could have a look at it and provide some feedback since i am completely at a dead end there (and have been for quite a while)
https://github.com/SveSop/nvcuda/issues/1

I have hopefully solved this with a hack to nvcuda: https://github.com/SveSop/nvcuda/commit/b1be06d200176aff838032707a9e1d350b4840f5
So closing this for now unless it is just working for me ofc.
PS. Recompiled my OptiX SDK samples for 7.5 up to 8.0 using its respective CUDA SDK (up to SDK 12.0 for OptiX 8.0) and it seems to work fine save for the winebug mentioned elswhere here.