Unable to Format PivotTable Pivot ROW as integer

Hi, thanks again for this amazing module.
In the below example, I am unable to get the PivotTable rows to format as integers.  The PivotData formats correctly, using PivotNumberFormat. Set-Format works correctly in the main sheet but not in the Pivot Table sheet, where the rows appear in Column B.  Any ideas?
Get-ChildItem -path c:\temp\PhoneBills | Foreach {
file = $_;
$xl = Import-Csv -Path $file.FullName -Encoding Default | Export-Excel -Path "C:\Temp\Output$($file.Name.Replace('.csv','')).xlsx"    -ExcludeProperty "Bill sequence number","Invoice number","Account (BAN)","Sub account (BEN)","Allocation code 1","Allocation code 2","Allocation code 3","Allocation code 4"
-WorksheetName Spend -Autosize -AutoFilter -FreezeTopRow -BoldTopRow -passthru `
Add-WorkSheet -ExcelPackage $xl -WorksheetName Summary

Add-PivotTable -ExcelPackage $xl -PivotTableName Summary `
    -Address $xl.Workbook.Worksheets[2].Cells["B2"] `
    -SourceWorkSheet $xl.Workbook.Worksheets[1] `
    -PivotRows "User name","Country of origin","Dialled number" `
    -PivotData @{"Cost (£)"= 'Sum'} -activate -PivotNumberFormat "£#,##0.00" -PivotTableStyle Dark9

$xl.Workbook.Worksheets.MoveToStart("Summary")
#Works to format "Dialled Number" column in data sheet:
Set-Format $xl.Workbook.Worksheets[2].Cells["E:E"] -NumberFormat '0'
#Does not work to format Pivot Rows in Pivot Table:
$sheet2 = $xl.Workbook.Worksheets["Summary"]
Set-Format -Address $sheet2.Cells["B:B"] -Numberformat '0'
Close-ExcelPackage $xl
}

Could you also post a sample csv file?

Thanks, uploaded as .txt as .csv seems to be unsupported as upload format:
TEST USER.txt

I moved the Set-Format $xl.Workbook.Worksheets["Spend"].Cells["E:E"] -NumberFormat '0' before the the creation of the pivot table, no luck.
Can you get the formatting you want when have the sheet open in Excel?
If you can, try to replicate that in the script.

Yes, I can format the numbers in the open sheet without any issues.  I will have a go, thanks for looking.

You could try searching EPPlus Pivot format number

Er. For  phone numbers you want the full number in the data export as a text string and then to use -NoNumberConversion  but your source data has already converted the phone number into 3.80673E+11 etc
The pivot table can specify "when you calculate the numbers , format them like this". But it can't specify anything to do with the labels (which is what the phone numbers are).
What you need to here is simple. Cheat. These aren't numbers you calculate with, they are labels, so even with your last few digits turned to 0000 you can make them into text and use the text in the pivot like this
$xl = {as before}
**Set-ExcelColumn -Worksheet $xl.Spend -Heading "Dialled Text" -Value {"=Text(E$row,""0"")"}**
Add-WorkSheet {as before}

Add-PivotTable {as before - except **"Dialled number"** becomes **"Dialled Text"**}`

I have tested this and this works!  Thank you so much, this is so helpful to me!


Design Location and CharacterLocation models

Location (name, background_img_url, min_level, desc)
CharacterLocation (char, location)

Done

Done


[BUG][LUIS] Apps.AddCustomPrebuiltDomainAsync throws because of missing tokenizerVersion

Describe the bug
Calling Apps.addCustomPrebuiltDomain gets a 400 response from the server because no tokenizer version is specified.
Exception or Stack Trace
($exception).InnerException.Message:
"Operation returned an invalid status code 'BadRequest'"

((Microsoft.Azure.CognitiveServices.Language.LUIS.Authoring.Models.ErrorResponseException)($exception).InnerException).Request.RequestUri
{https://westus.api.cognitive.microsoft.com/luis/api/v2.0/apps/customprebuiltdomains}

((Microsoft.Azure.CognitiveServices.Language.LUIS.Authoring.Models.ErrorResponseException)($exception).InnerException).Request.Content
"{\r\n  \"domainName\": \"HomeAutomation\",\r\n  \"culture\": \"en-us\"\r\n}"

((Microsoft.Azure.CognitiveServices.Language.LUIS.Authoring.Models.ErrorResponseException)($exception).InnerException).Response.Content:
"{\r\n  \"error\": {\r\n    \"code\": \"BadArgument\",\r\n    \"message\": \"The tokenizer version cannot be null or empty.\"\r\n  }\r\n}"

($exception).InnerException.StackTrace:
"   at Microsoft.Azure.CognitiveServices.Language.LUIS.Authoring.Apps.<AddCustomPrebuiltDomainWithHttpMessagesAsync>d__23.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Microsoft.Azure.CognitiveServices.Language.LUIS.Authoring.AppsExtensions.<AddCustomPrebuiltDomainAsync>d__18.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()\r\n   at LUIS_Prediction_CS.Program.<CreateApplication>d__6.MoveNext() in C:\\Users\\<user>\\Documents\\Quickstarts20190604\\LUIS_Prediction_CS\\LUIS_Prediction_CS\\Program.cs:line 46\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()\r\n   at LUIS_Prediction_CS.Program.<RunQuickstart>d__7.MoveNext() in C:\\Users\\<user>\\Documents\\Quickstarts20190604\\LUIS_Prediction_CS\\LUIS_Prediction_CS\\Program.cs:line 59"

To Reproduce

Get a LUIS subscription key.
Set the environment variable LUIS_SUBSCRIPTION_KEY to your subscription key.
Set the environment variable LUIS_REGION to the region for your subscription key (example: westus).
In Visual Studio 2019, create a .NET Framework C# Console App.
Add the NuGet package Microsoft.Azure.CognitiveServices.Language.LUIS.Authoring v3.0.0 to your solution.
Replace the contents of Program.cs with the following code.
Compile and run.

Code Snippet
using System;
using System.Threading.Tasks;

using Microsoft.Azure.CognitiveServices.Language.LUIS.Authoring;
using Microsoft.Azure.CognitiveServices.Language.LUIS.Authoring.Models;

namespace LUIS_Prediction_CS
{
    struct ApplicationInfo
    {
        public Guid ID;
        public string Version;
    }

    class Program
    {
        private const string key_var = "LUIS_SUBSCRIPTION_KEY";
        private static readonly string subscription_key = Environment.GetEnvironmentVariable(key_var);

        // Note you must use the same region as you used to get your subscription key.
        private const string region_var = "LUIS_REGION";
        private static readonly string region = Environment.GetEnvironmentVariable(region_var);
        private static readonly string endpoint = "https://" + region + ".api.cognitive.microsoft.com";

        static Program()
        {
            if (null == subscription_key)
            {
                throw new Exception("Please set/export the environment variable: " + key_var);
            }
            if (null == region)
            {
                throw new Exception("Please set/export the environment variable: " + region_var);
            }
        }

        // Create a new LUIS application. Return the application ID and version.
        async static Task<ApplicationInfo> CreateApplication(LUISAuthoringClient client)
        {
            string app_version = "0.1";
            var app_info = new PrebuiltDomainCreateObject()
            {
                DomainName = "HomeAutomation",
                Culture = "en-us"
            };
            var app_id = await client.Apps.AddCustomPrebuiltDomainAsync(app_info);
            Console.WriteLine("Created new LUIS application with ID {1}.", app_id);
            return new ApplicationInfo() { ID = app_id, Version = app_version };
        }

        async static Task RunQuickstart()
        {
            // Generate the credentials and create the client.
            var credentials = new Microsoft.Azure.CognitiveServices.Language.LUIS.Authoring.ApiKeyServiceClientCredentials(subscription_key);
            var authoring_client = new LUISAuthoringClient(credentials, new System.Net.Http.DelegatingHandler[] { })
            {
                Endpoint = "https://" + region + ".api.cognitive.microsoft.com"
            };
            var app = await CreateApplication(authoring_client);
        }

        static void Main(string[] args)
        {
            Task.WaitAll(RunQuickstart());
            Console.WriteLine("Press any key to exit.");
            Console.Read();
        }
    }
}

Expected behavior
Expected output:
Created new LUIS application with ID {<guid>}.
Press any key to exit.

Setup (please complete the following information):

OS: Windows 10 Enterprise 1803
IDE : Visual Studio 2019
Microsoft.Azure.CognitiveServices.Language.LUIS.Authoring v3.0.0

Additional context
This seems to be the same issue as https://github.com/Azure/azure-sdk-for-java/issues/4300.
The necessity of the tokenizerVersion property can also be seen from the API testing console.
If you go to "Get LUIS prebuilt domains list" (https://westus.dev.cognitive.microsoft.com/docs/services/5890b47c39e2bb17b84a55ff/operations/59104cec5aca2f0b48c76be3) and use the console to send a request, you get back results such as:
{
  "name": "Calendar",
  "culture": "en-us",
  "tokenizerVersion": "1.0.0",
  "description": "The Calendar domain provides intent and entities for adding, deleting, or editing an appointment, checking participants availability, and finding information about a calendar event.",
  "examples": "-",
  "intents": [{
    "name": "AcceptEventEntry",
    "description": "-",
    "examples": "-"
  },
...

Note the tokenizerVersion field.
If you go to "Add prebuilt application" (https://westus.dev.cognitive.microsoft.com/docs/services/5890b47c39e2bb17b84a55ff/operations/59104e515aca2f0b48c76be5) and use the console to send the default request body:
{
	"domainName": "Web",
	"culture": "en-us"
}

you get back the same response as in the code snippet:
Response status

400 Bad Request
Response latency
111 ms
Response content

Pragma: no-cache
Apim-Request-Id: c0024d77-12bc-4063-8ec1-14ebae8a76a8
Request-Id: c0024d77-12bc-4063-8ec1-14ebae8a76a8
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Request-Context: appId=cid-v1:26a3540d-a02a-4998-a060-715488fd769b
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store, proxy-revalidate, no-cache, max-age=0, private
Date: Mon, 08 Jul 2019 03:02:00 GMT
Content-Length: 116
Content-Type: application/json; charset=utf-8

{
  "error": {
    "code": "BadArgument",
    "message": "The tokenizer version cannot be null or empty."
  }
}

If you change the request body to:
{
	"domainName": "Web",
	"culture": "en-us",
	"tokenizerVersion": "1.0.0"
}

and resend, you get back a successful response:
Response status

201 Created
Response latency
561 ms
Response content

Pragma: no-cache
Apim-Request-Id: 551b309f-5967-426b-bf98-cfff25895c59
Request-Id: 551b309f-5967-426b-bf98-cfff25895c59
Operation-Location: https://westus.api.cognitive.microsoft.com/luis/api/v2.0/apps/customprebuiltdomains/a9fb34c3-25be-4e92-9bc6-3370303803c2
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Request-Context: appId=cid-v1:26a3540d-a02a-4998-a060-715488fd769b
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Cache-Control: no-store, proxy-revalidate, no-cache, max-age=0, private
Date: Mon, 08 Jul 2019 03:14:09 GMT
Location: https://westus.api.cognitive.microsoft.com/luis/api/v2.0/apps/customprebuiltdomains/a9fb34c3-25be-4e92-9bc6-3370303803c2
Content-Length: 38
Content-Type: application/json; charset=utf-8

"a9fb34c3-25be-4e92-9bc6-3370303803c2"

I cloned https://github.com/Azure/azure-sdk-for-net.git and did a search through the LUIS code for "tokenizer" but did not find anything.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Bug Description Added
[x] Repro Steps Added
[x] Setup information Added

Thanks for the bug report. I have routed to the appropriate team for follow-up.

Hi @v-jaswel,
This issue was resolved with the latest SDK. Can you re-test and verify that you are no longer having this issue?
thanks!
Chris


Add tests for reconciliation events

This adds tests that are meant to standardize the expected behavior for events generated by KC. In the end the test should act as a guide for any future changes to how events are generated.
Steps:

Create Kustomization which will deploy a Pod
Set Pod to an unhealthy state and wait for Kustomization to receive status condition for failed health check.
Trigger a reconcile and check the events to make sure that only one event has been created for the failed health check.
Set Pod to a healthy state and wait for Kustomization to receive a healthy status condition
Trigger a reconcile and check the events to make sure that only one event has been created for the health check.

TBD:

Verify external event recorder event message matches status
Update revision and make sure only one event is created for health check.

Its better to try to merge this PR which adds the test to avoid regression and then I can verify that #191 is not present in a later PR,

There is still the issue that the health passed even is sent immediatly when the kustomization is reconciled, even if the health check does not pass.

I don't see how is that possible, on a health check error we return early:
https://github.com/fluxcd/kustomize-controller/blob/main/controllers/kustomization_controller.go#L695

I've added various tests for the events in the last months, closing this.


build: equalize package & lock

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Inference at higher resolution on NYU

Hello,
thanks a lot for providing the code for your method!
I was trying it out on NYU but doing inference at the original resolution of 640x480 always using 500 random valid points. As you see in the plot, I get some bizarre texture in the results. While I acknowledge that the point density is now more than four times lower and that you also ablate a significant performance loss in the paper when using fewer points, I cannot explain why these square textures should appear in the first place, especially in flat regions of the background. Do you have any intuition about which part of the network might be failing there?

Just to double-check, I modified the NYU dataloader so that it does not apply the resizing and cropping to RGB and GT, the camera matrix is not transformed, and no padding is used as the resolution is divisible by 32. Is this the correct procedure to test generalization to other resolutions? And for a different dataset, should I just swap the camera matrix?
Best,
Massimiliano

Sorry that I don't know where these squares come from.
From my view, you should modify camera matrix that the valid depth corresponds to the same 3D space.
Also,  since our method adopt the direct distance as the offset term, evaluation on higher resolution may cause this offset term in a much different distribution than training (e.g. the largest number of offset term is 320 in training, but now it maybe 640).

When the sparsity level rises, the texture appears at training resolution too. This suggests density plays a role, although now the degradation happens with less magnitude and later. But I see your point as well, thanks. I was just expecting the prediction to become blurry rather than forming these squares.

What I meant with the camera matrix is that I kept the original NYU one without dividing by two and shifting the principal point coordinates, effectively bringing it back to 640x480. It should be acting in the correct 3D space. The same I would do with other datasets: swap the camera matrix and adapt it to the resolution I want to process at.


Fix some little issue in lwm2mclient

About the last commit "update to tinyDTLS" :

it is not mandatory to merged, #398  works without it.
please double-check it because I'm not a cmake expert. See those tinydtls commits (f94dc0a2 and 080013fd) to better understand the changes.


Node.cs class screws compiling

it will Error Warning if there is already a script named "Node"
3 hours ago
I have a script named"Node" in my project
Then, it will give me Error....

Solution:
In EventsGraphGUI.cs
Change line 73 public override void NodeGUI(Node node)
to public override void NodeGUI(UnityEditor.Graphs.Node node)
and line 116 Node selectedNode = graph[SelectionOverride.ToString()];
to UnityEditor.Graphs.Node selectedNode = graph[SelectionOverride.ToString()];

Fixed!
Please grab the new release here: https://github.com/MephestoKhaan/UnityEventVisualizer/releases/tag/1.4.1


2.7.5 for Homebrew

Can we please get a 2.7.5 build for Homebrew?
https://github.com/Homebrew/homebrew/commits/master/Library/Formula/arangodb.rb

I have no idea how to do it. As far as I know I can only push the newest. Or is there a trick?

Oh. Maybe it's possible using a combination of git push --force and git reset --hard but I'm no git expert. Might not be worth the effort.

We will try whether we can go the tap route:
https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/brew-tap.md
we will then probably have something like:
brew tap arangodb-homebrew/arangodb275
brew install arangod275
to install maintenance versions via macports.

Please don't bother if I'm the only one who requested this.

Ok, since homebrew is rather used on development systems, and you still can use other means of installation to get the old maintainance version, we will stop the effort on this and close it now.


Implement Shard data consumption and visualization

Use details in https://github.com/Headstorm/shukra/issues/12 perform this task.

UI task for shard data visualization: https://github.com/Headstorm/shukra/issues/31


MapR compatibility

I understand that libhdfs3 isn't really relevant to MapR since they have their own C API, but it would nice for this library to support MapR. It seems like the MapR API is different enough from libhdfs3 to make this a quick and simple project. Still, it seems a shame to to start a different project instead of adding MapR support to this one.
Any high level thoughts or insights on this?

I would tend towards many small libraries with very similar interfaces.  For example the s3fs project shares this interface for Amazon's S3.  I suspect that trying to unify all of the projects at a low-level would be challenging.  Most of the work in getting these things right has to do with interacting with the low-level system and with testing, neither of which are shared between libraries.
If more such libraries start to exist (which appears to be happening) we might consider making an abstract base class to formalize the shared API.

What do you mean by support MapR ?  I think of MapR as a distribution of Hadoop.

@mrocklin Perfect, I also like the idea of keeping implementations separate as well. One thing I want to make sure is that whatever we develop will be compatible with dask -- that's one of our main uses cases. It seems like we just need to implement the API for a FileSystem and File? Maybe it would be nice if there were an interface to subclass...
@quasiben MapR is another distro of Hadoop, but they've totally written the Hadoop implement in C rather than Java, which means the API's are a bit different. In general, MapR tends to behave quite a bit different than Cloudera or Hortonworks.

For inter-operation with Dask the code to look at is here: https://github.com/dask/dask/tree/master/dask/bytes
You have to write and register a couple of functions that, given a path, produce a list of dask.delayed objects corresponding to blocks of bytes or, given a bunch of dask.delayed value objects of bytes, write those bytes to disk.
The HDFS version is here: https://github.com/dask/distributed/blob/master/distributed/hdfs.py (ignore the deprecated read_csv and read_text functions) and it does a bit more work to capture the data-local nature of HDFS, but that's optional if you didn't care too strongly about maximizing performance.
As you suggest, as we invest more into this file-object or filesystem-like interface it might be wise to provide a more direct interface.  Historically it has been the matter of about a day to integrate Dask with a library like hdfs3 or s3fs.  I wouldn't be too worried.  If you can serve byte ranges then things are set up fairly well for libraries like dask.dataframe to take advantage of it.
Pinging @martindurant, who has done most of this work.

Awesome. We'll take a look at that stuff and start developing it soon. Thanks for all your help!

Feel free to be vocal on this issue.  There are a few things we've been talking about changing to make dask.bytes simpler to extend (with ideas like File and FileSystem as you mention) but we haven't yet because a good reason hasn't yet arisen.  Depending on how much time developers have you may end up being that reason.

@stevenmanton does MapR not use the protobuf interfaces in Hadoop 2.X ?

@stevenmanton , just to reaffirm mrocklin's comment: please comment early and often, we are keen to expose multiple storage platforms to python, especially in a manner convenient for dask's parallel processing. I have been meaning to to rationalise the read functionality in dask to make it easier to add backends, but haven't made a start on that yet.

Thanks everyone! We'll start development on this ASAP and will communicate early and often.

So I've been looking into this and I have a working copy that I branched from master. It sounds like there wasn't much appetite for keeping a single repo that is compatible with both libhdfs3 and mapr. Still, there's so much code overlap that maybe we revisit that option. Otherwise, another attractive option would be to maintain a fork that is mapr-only compatible. As hdfs3 continues to develop, at least we could continue to merge in those changes. I would call that package maprfs, but the source code would be largely the same as hdfs3.
I'm hoping to push this code soon to a public repo for comments, but am working that out with our legal team first.

If it's very similar then it might make sense to keep them together.  It would depend on how cleanly we could support both.  If you have a branch off of this repository then I recommend issuing a PR if only so that everyone can compare the differences.  This would be after you clear it with your legal team of course.

@mrocklin sounds good! By the way, does Continuum have any contributor agreements we would need to sign? I'm not too familiar with open source licenses and don't want to get my company in trouble :-)

Dask projects don't currently require contributor license agreements.
That being said, you should check with your employer that they're comfortable with you releasing this code to the public.  You're in no danger of getting your company into trouble.  You're mostly checking that they don't think you're leaking internal code by publishing to an open source project.

"using NFS with a single gateway node" - would you mind elaborating what this means?

Hey @kmatt we worked on a MapR-compatible library by making some small modifications to the hdfs3 library. You can find our repo here. Our work on it kind of fizzled, but I believe it was mostly working last time we used it. We basically wrap MapR's C++ bindings instead of using the libhdfs bindings found in Cloudera or Hortonworks distros.

@martindurant MapR community edition only supports a single NFS gateway node.
I'm wondering if the Dask processes on multiple cluster nodes are bottlenecked thought the single NFS gateway node because we are accessing files via an NFS mount and not via the hdfs3 lib.

@stevenmanton Thanks! I will try building with MapR 5.2
Does it expect a local MapR installation for dependencies? Or is there a way to get it to build on a workstation without a full server install, from a MapR client package?

Hey @kmatt I don't believe there's anything to build. I think it's mostly just configuring the python source code to point to your MapR's MapRPythonClient.a file. Check out the lib.py file to see how we modified it to use MapR instead of libhdfs.so. My guess is that the path on your distro will be the same.
I can try to get you more info on Monday.

@stevenmanton I was able to get the current maprfs-compatibility branch to install and run and hdfs.ls by adding export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/jvm/java-1.8.0-openjdk-<IP_ADDRESS>-0.b14.el7_2.x86_64/jre/lib/amd64/server for libjvm.so
There may be a better way to specify that path in the shell config?


Added in-game role to Forastha

I don't see a use in this. It's also technically factually incorrect.

Sell this to me and I may reconsider.

Please change your GitHub name! I keep forgetting who you are!

I think that it would look a lot more professional for the site to display your in-game role due to the fact that mine is on there as well.  Of if you don't want it to say "Owner" I'll delete this PR keep the branch and then change it so it says "Admin".

Changed, can you

m
e
r
g
e
?


ci: wait up to 5 minutes for Android emulator to start

And if 5 minutes elapses, assume the emulator booted successfully and we missed the sys.boot_completed event.
Remove the timeout-minutes setting on the GitHub Actions job definitions so we only consider booting the emulator in the timeout and not installing the SDK or creating the emulator.
Bug: #24841
Risk Level: Low - CI only
Testing: CI
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A

So whether we want to fail open or fail close will depend on what we will happen in the case of the builds that end up timing out after 300s.

This change makes it so we wait 300s only for the emulator to boot. Nothing is building during this time. And sure, we can adjust this timeout as needed.


Wrong label

This label shall be removed. Maybe it was forgotten to remove
TODO: check out, whats the reason why it was there

This is most likely leftover from the external command text field for file manager and/or terminal


Update readme example

Closes #48
Proposed Changes
Update README with working example.

The PR is no more valid. For more info see https://github.com/InfluxCommunity/influxdb3-js/issues/48


SolanaRpcWebsocket

When using SolanaRpcWebsocket, it seems that I haven't found a way to handle reconnections after a disconnection.

Yes, you’re right. I encountered this issue when simulating a network disconnection."

Thank you for your reply.

I've added the onError and onClose hooks.  However, by trying to test it out by disconnecting my internet connection, I never received an event, but after re-connecting my network connection, after a few seconds I began to receive messages again.

appreciate you trying out the library, unless you would like to see a specific change to the web-socket going to close this out tomorrow.


lazy loading for pages with a lot of api-calls

We should consider implementing lazy loading for the parts page and similar views. There is a lot of unnecessary traffic generated with the current way.

I have noticed that too - each table initialization call should be linked to the first time a particular tab is displayed!


Dev/autocomplete customdescription

adds custom_description parameter to localities autocomplete API
closes WebGeoServices/localities#305
Ready for review, leaving this in draft mode to prevent merge before we have a GO from CCare

this parameter will impact the shape of the description field in the response. No new parameter will be added.


JSS Placeholder Sequence

Description
I have two Placeholders in my code

jss-main - To render components
yi-static - For static things (like set data in browser's localstorage)

<ConditionalStaticPlaceholder name="yi-static" rendering={data}  />
<Placeholder name="jss-main" rendering={data} />

Problem: How can I call Placeholders in sequence and synchronous. So my localstorage data should be set in the browser first and then components should be rendered. But in the current scenario "yi-static" is called after "jss-main" means localstorage data set after components render.
Expected behavior
"yi-static" Placeholder should be called first
"jss-main" Placeholder should be called second after first complete his job (set data in localstorage)

This seems like a React state management issue vs a JSS issue, right? Feel free to reopen if there is a specific change in JSS that you think is needed to support this.


UI Bugs

Creating project does not throw an error when the database exits.
Restore project missing.
We have a potential email activation issue. This could be a mix of wrong settings on the server to the wrong values in the django settings or wrong carry over from django1.6 to django 1.8(they seemed to have changed the way they do emails from 1.7)
Update tokens has an error.
Make project fields except description/kvserver/public uneditable. Fix the error message in update projects.(views.py)
Cannot update values of window.

Point 6 fixed.


DX - Migrate the JS to TS

Because, why not 🤣?
At least for pages dir is using .tsx instead of .js

will working on it mas @mazipan


Add pylint test for python36

Coverage remained the same at 84.899% when pulling 9d1add0076ef27dd9067bceb75fd3a0ebd15d818 on feature/python36 into 20b6608643f31248b361f3c8643cbe8615fbb9bc on master.


Documenting Route attachment for v1alpha2

What type of PR is this?
/kind documentation
What this PR does / why we need it:
This is a follow up to #754 and provides documentation for GEP #724.
Does this PR introduce a user-facing change?:
NONE

Adding a hold until #754 merges, will also add more examples at that point.

/hold

/hold
/lgtm

Thanks for the feedback @bowei! I think I've updated everything, PTAL.

Thanks for the feedback @jpeach, just pushed updates, PTAL.
/hold cancel


Feature Request: Update all states

I notice that when I make a change or an addition to the file it is registered as a change within all of the states and thus requires each state to be updated individually. If you have a lot of states, this means each time you select and then deselect a state it will pop up a dialog asking if you want to update the changes. This is tedious, particularly if you have a lot of states. It would be great to have the option to update all of the states at once.
Thanks!

I am aware of this and get it fixed in the next version


Reactive Property on Inspector

Is there anyway to make Reactive Property available on Inspector?

Just tried some things and I believe it won't be possible without significant refactor of SxProperty/this whole library. Godot's @export annotation would work only with built-in types, nodes and resources, but SxProperty is inheriting RefCounted which cannot be exported in inspector even with a custom inspector plugin. This is not possible, unless I rewrite this library to a GDExtension, which I'm not planning to do anytime soon.
As for now, you can do something like this:
@export var initial_value: int
@onready var value_property: SxProperty = SxProperty.new(initial_value)

Ah yes, understood, this is acceptable solution for now...

I've working on some workaround on this stuff... it's not pretty but, it somehow works...
This is a helper class
extends RefCounted
class_name SxHelper

static func helper_set(obj, property, value):
	if property.begins_with("sx_"): return false # forbid set sx_varName directly
	var res = obj.get("sx_" + property) # get the reactive property
	if res is SxProperty:
		res.value = value # set ".value" if it's SxProperty
		return true
	return false

static func helper_get(obj, property):
	if property.begins_with("sx_"): return null # if get sx_varName, use default handler (returning null)
	elif property.begins_with("s_"): # shortcut to get the signal
		var res = obj.get("sx_" + property.trim_prefix("s_")) # get the reactive property
		if res is SxProperty: return res.as_signal()
	else:
		var res = obj.get("sx_" + property) # get the reactive property
		if res is SxProperty: return res.value # if it's SxProperty, returning .value
	return null

static func helper_property_can_revert(obj, property):
	if property.begins_with("sx_"): return false
	return obj.get("sx_" + property) is SxProperty

static func helper_property_get_revert(obj, property):
	if property.begins_with("sx_"): return null
	var res = obj.get("sx_" + property)
	if res is SxProperty: return res.initial_value
	return null

static var _hasCalledGetPropertyList := false
static func helper_get_property_list(obj):
	if _hasCalledGetPropertyList: return []
	_hasCalledGetPropertyList = true
	var result = obj.get_property_list() \
	.filter(func (prop): return prop.name.begins_with("sx_")) \
	.map(func (prop):
		var sx = obj.get(prop.name)
		var propName = prop.name.trim_prefix("sx_")
		return {
			name = propName,
			type = typeof(sx.initial_value)
		}
	)
	_hasCalledGetPropertyList = false
	return result

Basically I intercept the _get, _set of the properties
@tool
extends Node2D
class_name SxNode2D

func _get(property): return SxHelper.helper_get(self, property)
func _set(property, value): return SxHelper.helper_set(self, property, value)
func _property_can_revert(property): return SxHelper.helper_property_can_revert(self, property)
func _property_get_revert(property): return SxHelper.helper_property_get_revert(self, property)
func _get_property_list(): return SxHelper.helper_get_property_list(self)

Then I could use it like this
@tool
extends SxNode2D

var sx_testInt := SxProperty.new(10) # prefix with sx_ to declare reactive property, this will show in inspector

# Called when the node enters the scene tree for the first time.
func _ready():
	if Engine.is_editor_hint(): return

	self.s_testInt.subscribe(func(value: int): print(value)) # to access the signal, use s_varName, it's same as sx_varName.as_signal()
	self.testInt = 20 # to access the value, use varName directly, it's same as sx_varName.value

So if I subclass SxNode2D, and if I create variable with prefix "sx_", I could access the value without including "sx_" prefix.
But if I access internally, I should use "self.", because it needs to trigger the getter and setter.
And yes, with this way, you will lose the type-check.

Nice that you got something that works for you! Hopefully, there will be some improvement on Godot's side in the future that will make it possible to do it the clean way, so it can be properly implemented in this library.


Switch quickstart to helm charts.

cc @UnderGreen and @eldios I think this is something you should take a look at as it demoes new helm flow for Telekube that we should re-use with you know-who :)


Column Formatting not working

What Kind of Sample (view or column format)
Column Formatting
Sample Description (what should it do) So, my column looks to the Category column and depending on the choice either the Agent field or Team Meeting field should show on the form. This is working as it should be. The issue is when you either edit it or click on the details pane i get the following error: Unexpected token ; in JSON at position 2

I am using the following formula: =if([$Category] == 'Agent', 'true', 'false') and =if([$Category] == 'Team', 'true', 'false') if I remove the formulas the list works as it should.
Are you Willing to Help?
Yes

I just tried it and it appears fine.

If you are still seeing the error screen, sorry, but please create a new issue again.


Update CFE unit tests after rebase of OSAL ticket 17

Previously, CFE ticket #63 was implemented which was based on the proposed unit test framework implemented within OSAL [cfs_osal:17].
The unit test framework has since been revisited and the related OSAL ticket has been rebased accordingly.
Unfortunately, this broke some items that had been done originally within trac #63.  Trac 32 can no longer be rebased since it is merged in "development" already, so this ticket will fix the unit test breakage.

Trac comment by jphickey on 2015-06-23 13:28:48:
NOTE Due to merge/rebase conflicts, this ticket will ALSO include all the changes for prior tickets #87 and #88.
This will result in a single branch that merges together all of the unit test fixes and produces a basically working CFE unit test again.
It is based on the current {{{ic-2015-05-20}}} which includes the CFE 6.4.2 changes.

Imported from trac issue 72.  Created by jphickey on 2015-06-23T12:47:58, last modified: 2019-03-05T14:57:55

Trac comment by jphickey on 2015-07-09 16:44:22:
== UPDATED AND REBASED ==
This change set has been rebased to the current development branch based off the newly-released version 6.4.2.
Commit [changeset:702387c] reflects the latest revision for review.
Note - To reduce possible merge conflicts, #87 and #97 are merged prior to this change set (they touch some of the same files).

Trac comment by glimes on 2015-07-13 14:43:49:
Accept.

Trac comment by jphickey on 2015-07-09 16:45:06:
This is included in the {{{ic-2015-07-14}}} integration candidate for testing

Trac comment by jphickey on 2015-07-15 13:49:19:
== REBASED AGAIN ==
Per the 2015-07-14 CCB review some other dependent change sets were approved (#87 and #97).  Therefore this has been rebased again to the current "development" baseline that contains these change sets.  This now makes it a standalone change set.
New/rebased commitid is: [changeset:49e4135]
(To anyone who as already reviewed, the change is the same, just the parent commit is different)

Trac comment by glimes on 2015-07-27 12:21:48:
Accept.

Trac comment by sduran on 2015-07-27 14:41:52:
Lots of changes to unit test code.  It will be interesting to see how this merges with unit test work underway at JSC.

Trac comment by glimes on 2015-07-28 10:48:39:
Actually tinkered together the Grand Merge of the latest trac-22
branch with development, then the CCB review branch, then out
to the tip of the JPH Bleeding Edge.
The mechanical merge was easy (but not entirely automatic).
As I write this: the Bamboo plan tests it out and gives it
a GREEN status, with one exception in quarantine.
https://babelfish.arc.nasa.gov/bamboo/browse/CFS-CFSOSAL61/latest
The sole Quarantine item:
{{{
osal/src/unit-tests/osfilesys-test/ut_osfilesys_test.c:133: warning: implicit declaration of function 'UT_os_getfsinfo_test'
}}}
Now bear in mind that this is merging Joe's latest (which he has
not said is ready for prime time) with JSC's latest (which you have
not claimed to be ready for prime time).
So the fact that a mechanical merge does this well is surprisingly good.
The downside is that my builds are not compiling any of the VxWorks support
code (which I think your branch touches), and I think I see some new code
being introduced which my existing build scripts do not know to compile, so
there could be all sorts of issues.
My thinking is that as long as we have a known resolution to the mechanically
discoverable merge conflicts in our pocket, we will waste less time when
we eventually get down to the task of resolving any real conflicts.

Trac comment by glimes on 2015-07-30 15:12:44:
[changeset:49e4135 trac-72-cfe-ut-rebase-fixes] is included in [changeset:6ea42ba ic-2015-07-28]

Trac comment by glimes on 2015-09-08 12:58:44:
... somehow was not closed after the 07-28 integration was complete.

Trac comment by jhageman on 2019-03-05 14:57:55:
Milestone renamed

Trac comment by glimes on 2016-02-16 13:16:45:
Susie confirmed these tickets have been approved for CFE 6.5


retrofit 2.20/okhttp 3.6.0 compatibility?

Is there any work being done to provide compatibility with these newer releases?
Bringing the current implementation in causes a conflict with the clone() method between Object and the Call interface:
Exception CloneNotSupportedException in throws clause of Object.clone() is not compatible with Call.clone()
The inherited method Object.clone() cannot hide the public abstract method in Call
I've gotten around this for the moment by implementing clone() and just eating the exception, but that seems very wrong.

Hi Chuck,
Thanks for bringing this to my attention. I merged a pull request recently but didn't do any testing myself. I'll try and take a look and fix as required.
Andy.

Rex, have you pulled the latest commit?  I think I ran into the same issue and added GoogleAppEngineCall.clone(), which should resolve it.
On a similar note, OkHttp 3.8.0 now requires response messages and I'm working on a PR to fix that as well.

@pushbit is this fixed by PR #5 ?

No, I believe it was already fixed by PR #2.

Was away on a vacation, have not pulled the updated version, Will give it a try - thank you!

Seems good for the clone() issues. Though the class and constructor were no longer public which caused me some visibility issues. Was that an intentional change?

Yeah, the idea is that instead of implementing Call.Factory you can just create an instance of GoogleAppEngineOkHttpClient, which does that for you.

Ah, ok, my usage was from before the Client was added so hadn't been using it. I can switch over. This can be marked as closed. Seems to work just fine.


create tglc entry

This looks good to me as well! Thanks @ttdu !

thanks for the feedback! @snbianco is looking into updating astroquery to read HLSPs from AWS, so I'll leave this PR open until we better understand how much work it'll be to make those updates


Running smartcomments as a grunt task

Is it possible to run smartcomments as a grunt task?

Tried and it worked
npm install --save-dev smartcomments
npm install --save-dev grunt-shell

In Gruntfile.js:
shell: {
  smartcomments: {
    command: 'node ./node_modules/smartcomments/bin/smartcomments --generate -t ./your_app_path'
  }
 },

 grunt.task.run([
  'shell:smartcomments',
]);

I only mention this for new visitors to this thread.  Somehow I managed to install smartcomments globally rather than locally, but once I figured out the actual path to it, it worked as shown previously, even now, in 2018.
Thanks!


Configurable subject naming for Avro classes

Hi All,
this PR is an attempt to provide a flexible way of controlling the subject naming for Avro classes and Schema registry integration.
Given the model class org.springframework.cloud.schema.avro.User1 the current solution is generating content type headers in the following format application/vnd.user1.v1+avro or by calling return schema.getName().toLowerCase();.  Those are then registered in the schema registry with a subject user1, which is pretty ambiguous. In the current project we need a much more robust behaviour and agreed that the headers should ideally look like this application/vnd.org.springframework.cloud.schema.avro.User1.v1+avro - with the FQCN as the subject. This will then register the full class name as subject to the schema registry.
In this PR I have extracted the naming to a separate Strategy interface and the default implementation is backward compatible and at the same time it allows to supply a custom naming strategy through the configuration. No idea if this implementation is sufficient, I am happy to take comments / suggestions to get this feature through.

@davidkalosi Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@davidkalosi Thank you for signing the Contributor License Agreement!

@davidkalosi Thanks you for the contribution. We will review and follow up

@davidkalosi Please run the full build you'll see there check-style violations. Also, add your name with '@author' tag on all modules you've touched.
I'll continue to review meanwhile.

Codecov Report

Merging #1108 into master will increase coverage by 0.12%.
The diff coverage is 83.33%.

@@             Coverage Diff              @@
##             master    #1108      +/-   ##
============================================
+ Coverage     56.95%   57.08%   +0.12%
- Complexity      667      672       +5
============================================
  Files           122      123       +1
  Lines          3408     3425      +17
  Branches        484      484
============================================
+ Hits           1941     1955      +14
- Misses         1308     1311       +3
  Partials        159      159

Impacted Files
Coverage Δ
Complexity Δ

...am/schema/avro/AvroMessageConverterProperties.java
61.9% <100%> (+11.9%)
8 <2> (+2)
:arrow_up:

...avro/AvroSchemaRegistryClientMessageConverter.java
61.47% <100%> (+0.64%)
21 <2> (+1)
:arrow_up:

...ream/schema/avro/DefaultSubjectNamingStrategy.java
100% <100%> (ø)
2 <2> (?)

...ma/avro/AvroMessageConverterAutoConfiguration.java
59.09% <62.5%> (+1.94%)
3 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

@olegz any chance to have it backported into the 1.3.X release?

Hi, @davidkalosi. Thanks for all the great work on this! We very much appreciate it.
We have been backporting just the bug-fixes to the older release lines. Given this improvement doesn't fit that criteria, we would like to keep it in master/2.x line. We hope to be on RC by the end of next month and aggressively aim to graduate to a GA release soon after that.

Thanks, until then we will use our custom build on top of the 1.3 milestone with this patch applied.


Can't get the pretrained weights!

Dear author, the pretrained weights on google drive requires your authentication. Could you please provide it? Thank you very much.

Hi,
I have turned sharing on, please try again.

@ZZiyin Thank you very much. It works now.


Calico networkpolicy enforcement does not allow Terminating pods to gracefully shut down

Expected Behavior
When calico for networkpolicy enforcement is installed; pods in Terminating-state should keep their network access until containers are actually removed by the container-runtime.
Current Behavior
Pods that are in state Terminating immediately lose all network connectivity. Applications that are still handling in-flight network connections or applications that might want to reach out to the network for a graceful shutdown can not do so.
In our case, this is causing at least the following issues:

Interrupted (Cron)Jobs can not clean up after themselves
In-flight (HTTP) requests to Pods that are Terminating are timing out because return traffic is silently dropped/rejected and have to be retried

Possible Solution
Postpone iptables cleanup until pod/containers are actually removed.
Steps to Reproduce (for bugs)

Install an AWS EKS-cluster with the AWS VPC CNI. (vpc-cni installation is listed below)
Install calico for network policy enforcement (our installation is listed below)
No need to install any (global)networkpolicies whatsoever, keeping the default all allow behavior

adding (global)networkpolices does not help

Install debug deployment (see below)
Tail the logs from the debug pod
Terminate the pod with kubectl delete pod <pod>
Observe that the container immediately loses network access

Below are the logs of aws-node running on the same node that hosted one of my debug pods. Of particular interest is the following line, which seems to suggest that all iptables rules for my pod are removed, even though the pod is still in Terminating state and cleaning up after itself.
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/endpoint_mgr.go 544: Workload removed, deleting old state. id=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug-77df46cc65-nhdl4", EndpointId:"eth0"}

+ calico-node-8xbsr › calico-node

# immediately after running `kubectl delete pod <pod>`

calico-node-8xbsr calico-node 2021-04-08 11:31:32.158 [INFO][65] felix/calc_graph.go 411: Local endpoint deleted id=WorkloadEndpoint(node=ip-10-28-97-106.eu-west-1.compute.internal, orchestrator=k8s, workload=default/debug-77df46cc65-nhdl4, name=eth0)
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/int_dataplane.go 1430: Received *proto.WorkloadEndpointRemove update from calculation graph msg=id:<orchestrator_id:"k8s" workload_id:"default/debug-77df46cc65-nhdl4" endpoint_id:"eth0" >
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/int_dataplane.go 1430: Received *proto.ActiveProfileRemove update from calculation graph msg=id:<name:"ksa.default.default" >
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 537: Queuing deletion of chain. chainName="cali-pri-ksa.default.default" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 537: Queuing deletion of chain. chainName="cali-pro-ksa.default.default" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 537: Queuing deletion of chain. chainName="cali-pro-ksa.default.default" ipVersion=0x4 table="mangle"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/int_dataplane.go 1430: Received *proto.ActiveProfileRemove update from calculation graph msg=id:<name:"kns.default" >
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 537: Queuing deletion of chain. chainName="cali-pri-kns.default" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 537: Queuing deletion of chain. chainName="cali-pro-kns.default" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 537: Queuing deletion of chain. chainName="cali-pro-kns.default" ipVersion=0x4 table="mangle"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/endpoint_mgr.go 667: Workload removed, deleting its chains. id=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug-77df46cc65-nhdl4", EndpointId:"eth0"}
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 537: Queuing deletion of chain. chainName="cali-tw-eni70482c87d9a" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 591: Chain no longer referenced, marking it for removal chainName="cali-pri-kns.default"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 591: Chain no longer referenced, marking it for removal chainName="cali-pri-ksa.default.default"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 537: Queuing deletion of chain. chainName="cali-fw-eni70482c87d9a" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 591: Chain no longer referenced, marking it for removal chainName="cali-pro-kns.default"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 591: Chain no longer referenced, marking it for removal chainName="cali-pro-ksa.default.default"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/table.go 537: Queuing deletion of chain. chainName="cali-sm-eni70482c87d9a" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.159 [INFO][65] felix/endpoint_mgr.go 544: Workload removed, deleting old state. id=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug-77df46cc65-nhdl4", EndpointId:"eth0"}
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 506: Queueing update of chain. chainName="cali-from-wl-dispatch" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 591: Chain no longer referenced, marking it for removal chainName="cali-from-wl-dispatch-7"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 506: Queueing update of chain. chainName="cali-to-wl-dispatch" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 591: Chain no longer referenced, marking it for removal chainName="cali-to-wl-dispatch-7"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 537: Queuing deletion of chain. chainName="cali-from-wl-dispatch-7" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 537: Queuing deletion of chain. chainName="cali-to-wl-dispatch-7" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 591: Chain no longer referenced, marking it for removal chainName="cali-tw-eni70482c87d9a"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 506: Queueing update of chain. chainName="cali-set-endpoint-mark" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 591: Chain no longer referenced, marking it for removal chainName="cali-set-endpoint-mark-7"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 506: Queueing update of chain. chainName="cali-from-endpoint-mark" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 591: Chain no longer referenced, marking it for removal chainName="cali-fw-eni70482c87d9a"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 537: Queuing deletion of chain. chainName="cali-set-endpoint-mark-7" ipVersion=0x4 table="filter"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/table.go 591: Chain no longer referenced, marking it for removal chainName="cali-sm-eni70482c87d9a"
calico-node-8xbsr calico-node 2021-04-08 11:31:32.160 [INFO][65] felix/endpoint_mgr.go 476: Re-evaluated workload endpoint status adminUp=false failed=false known=false operUp=false status="" workloadEndpointID=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug-77df46cc65-nhdl4", EndpointId:"eth0"}
calico-node-8xbsr calico-node 2021-04-08 11:31:32.161 [INFO][65] felix/status_combiner.go 58: Storing endpoint status update ipVersion=0x4 status="" workload=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug-77df46cc65-nhdl4", EndpointId:"eth0"}
calico-node-8xbsr calico-node 2021-04-08 11:31:32.161 [INFO][65] felix/conntrack.go 90: Removing conntrack flows ip=<IP_ADDRESS>
calico-node-8xbsr calico-node 2021-04-08 11:31:32.204 [INFO][65] felix/status_combiner.go 86: Reporting endpoint removed. id=proto.WorkloadEndpointID{OrchestratorId:"k8s", WorkloadId:"default/debug-77df46cc65-nhdl4", EndpointId:"eth0"}

# after the pod is actually removed, note the terminationGracePeriodSeconds: 30

calico-node-8xbsr calico-node 2021-04-08 11:32:03.106 [INFO][65] felix/iface_monitor.go 187: Netlink address update. addr="fe80::ec14:2bff:fee9:cce" exists=false ifIndex=78
calico-node-8xbsr calico-node 2021-04-08 11:32:03.106 [INFO][65] felix/int_dataplane.go 1036: Linux interface addrs changed. addrs=set.mapSet{} ifaceName="eni70482c87d9a"
calico-node-8xbsr calico-node 2021-04-08 11:32:03.106 [INFO][65] felix/int_dataplane.go 1001: Linux interface state changed. ifIndex=78 ifaceName="eni70482c87d9a" state="down"
calico-node-8xbsr calico-node 2021-04-08 11:32:03.106 [INFO][65] felix/int_dataplane.go 1463: Received interface addresses update msg=&intdataplane.ifaceAddrsUpdate{Name:"eni70482c87d9a", Addrs:set.mapSet{}}
calico-node-8xbsr calico-node 2021-04-08 11:32:03.107 [INFO][65] felix/hostip_mgr.go 84: Interface addrs changed. update=&intdataplane.ifaceAddrsUpdate{Name:"eni70482c87d9a", Addrs:set.mapSet{}}
calico-node-8xbsr calico-node 2021-04-08 11:32:03.107 [INFO][65] felix/int_dataplane.go 1445: Received interface update msg=&intdataplane.ifaceUpdate{Name:"eni70482c87d9a", State:"down", Index:78}
calico-node-8xbsr calico-node 2021-04-08 11:32:03.108 [INFO][65] felix/int_dataplane.go 1036: Linux interface addrs changed. addrs=<nil> ifaceName="eni70482c87d9a"
calico-node-8xbsr calico-node 2021-04-08 11:32:03.108 [INFO][65] felix/int_dataplane.go 1463: Received interface addresses update msg=&intdataplane.ifaceAddrsUpdate{Name:"eni70482c87d9a", Addrs:set.Set(nil)}
calico-node-8xbsr calico-node 2021-04-08 11:32:03.108 [INFO][65] felix/hostip_mgr.go 84: Interface addrs changed. update=&intdataplane.ifaceAddrsUpdate{Name:"eni70482c87d9a", Addrs:set.Set(nil)}
calico-node-8xbsr calico-node 2021-04-08 11:32:12.545 [INFO][65] felix/summary.go 100: Summarising 18 dataplane reconciliation loops over 1m3.1s: avg=12ms longest=60ms (resync-ipsets-v4)

Your Environment

Calico version: v3.18.1
EKS version: 1.18
EKS AMI: v20210302
AWS VPC CNI version: v1.7.9
containerd version: 1.4.1

Context
debug.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  creationTimestamp: null
  labels:
    app: debug
  name: debug
spec:
  replicas: 1
  selector:
    matchLabels:
      app: debug
  strategy: {}
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: debug
    spec:
      terminationGracePeriodSeconds: 30
      securityContext:
        runAsUser: 1000
        runAsNonRoot: true
      containers:
        - image: krallin/ubuntu-tini:trusty
          name: debug
          resources: {}
          command:
            - /bin/sh
            - -c
            - |
              while true; do
                date
                timeout 1s getent hosts kubernetes.default
                sleep 0.25
              done
          lifecycle:
            preStop:
              exec:
                command:
                  - /bin/sh
                  - -c
                  - |
                    echo BEGIN preStop > /proc/1/fd/1;
                    sleep 10
                    echo END preStop > /proc/1/fd/1;
status: {}

kubectl -n kube-system get ds aws-node -o yaml
apiVersion: apps/v1
kind: DaemonSet
metadata:
  annotations:
    deprecated.daemonset.template.generation: "2"
  labels:
    k8s-app: aws-node
  name: aws-node
  namespace: kube-system
spec:
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: aws-node
  template:
    metadata:
      creationTimestamp: null
      labels:
        k8s-app: aws-node
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: beta.kubernetes.io/os
                operator: In
                values:
                - linux
              - key: beta.kubernetes.io/arch
                operator: In
                values:
                - amd64
                - arm64
              - key: eks.amazonaws.com/compute-type
                operator: NotIn
                values:
                - fargate
            - matchExpressions:
              - key: kubernetes.io/os
                operator: In
                values:
                - linux
              - key: kubernetes.io/arch
                operator: In
                values:
                - amd64
                - arm64
              - key: eks.amazonaws.com/compute-type
                operator: NotIn
                values:
                - fargate
      containers:
      - env:
        - name: ENI_CONFIG_LABEL_DEF
          value: failure-domain.beta.kubernetes.io/zone
        - name: ADDITIONAL_ENI_TAGS
          value: '{}'
        - name: AWS_VPC_CNI_NODE_PORT_SUPPORT
          value: "true"
        - name: AWS_VPC_ENI_MTU
          value: "9001"
        - name: AWS_VPC_K8S_CNI_CONFIGURE_RPFILTER
          value: "false"
        - name: AWS_VPC_K8S_CNI_CUSTOM_NETWORK_CFG
          value: "true"
        - name: AWS_VPC_K8S_CNI_EXTERNALSNAT
          value: "false"
        - name: AWS_VPC_K8S_CNI_LOGLEVEL
          value: DEBUG
        - name: AWS_VPC_K8S_CNI_LOG_FILE
          value: /host/var/log/aws-routed-eni/ipamd.log
        - name: AWS_VPC_K8S_CNI_RANDOMIZESNAT
          value: prng
        - name: AWS_VPC_K8S_CNI_VETHPREFIX
          value: eni
        - name: AWS_VPC_K8S_PLUGIN_LOG_FILE
          value: /var/log/aws-routed-eni/plugin.log
        - name: AWS_VPC_K8S_PLUGIN_LOG_LEVEL
          value: DEBUG
        - name: DISABLE_INTROSPECTION
          value: "false"
        - name: DISABLE_METRICS
          value: "false"
        - name: ENABLE_POD_ENI
          value: "false"
        - name: MY_NODE_NAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: spec.nodeName
        - name: WARM_ENI_TARGET
          value: "1"
        image:<PHONE_NUMBER>52.dkr.ecr.eu-west-1.amazonaws.com/amazon-k8s-cni:v1.7.9
        imagePullPolicy: Always
        livenessProbe:
          exec:
            command:
            - /app/grpc-health-probe
            - -addr=:50051
          failureThreshold: 3
          initialDelaySeconds: 60
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        name: aws-node
        ports:
        - containerPort: 61678
          hostPort: 61678
          name: metrics
          protocol: TCP
        readinessProbe:
          exec:
            command:
            - /app/grpc-health-probe
            - -addr=:50051
          failureThreshold: 3
          initialDelaySeconds: 1
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        resources:
          requests:
            cpu: 10m
        securityContext:
          capabilities:
            add:
            - NET_ADMIN
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /host/opt/cni/bin
          name: cni-bin-dir
        - mountPath: /host/etc/cni/net.d
          name: cni-net-dir
        - mountPath: /host/var/log/aws-routed-eni
          name: log-dir
        - mountPath: /var/run/aws-node
          name: run-dir
        - mountPath: /var/run/cri.sock
          name: cri-sock
        - mountPath: /run/xtables.lock
          name: xtables-lock
      dnsPolicy: ClusterFirst
      hostNetwork: true
      initContainers:
      - env:
        - name: DISABLE_TCP_EARLY_DEMUX
          value: "false"
        image:<PHONE_NUMBER>52.dkr.ecr.eu-west-1.amazonaws.com/amazon-k8s-cni-init:v1.7.9
        imagePullPolicy: Always
        name: aws-vpc-cni-init
        securityContext:
          privileged: true
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /host/opt/cni/bin
          name: cni-bin-dir
      priorityClassName: system-node-critical
      restartPolicy: Always
      schedulerName: default-scheduler
      serviceAccount: aws-node
      serviceAccountName: aws-node
      terminationGracePeriodSeconds: 10
      tolerations:
      - operator: Exists
      volumes:
      - hostPath:
          path: /opt/cni/bin
          type: ""
        name: cni-bin-dir
      - hostPath:
          path: /etc/cni/net.d
          type: ""
        name: cni-net-dir
      - hostPath:
          path: /run/containerd/containerd.sock
          type: ""
        name: cri-sock
      - hostPath:
          path: /run/xtables.lock
          type: ""
        name: xtables-lock
      - hostPath:
          path: /var/log/aws-routed-eni
          type: DirectoryOrCreate
        name: log-dir
      - hostPath:
          path: /var/run/aws-node
          type: DirectoryOrCreate
        name: run-dir
  updateStrategy:
    rollingUpdate:
      maxUnavailable: 100%
    type: RollingUpdate

kubectl -n kube-system get ds calico-node -o yaml
apiVersion: apps/v1
kind: DaemonSet
metadata:
  annotations:
    deprecated.daemonset.template.generation: "2"
    meta.helm.sh/release-name: aws-calico
    meta.helm.sh/release-namespace: kube-system
  labels:
    app.kubernetes.io/managed-by: Helm
    k8s-app: calico-node
  name: calico-node
  namespace: kube-system
spec:
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: calico-node
  template:
    metadata:
      creationTimestamp: null
      labels:
        k8s-app: calico-node
    spec:
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
            - matchExpressions:
              - key: kubernetes.io/os
                operator: In
                values:
                - linux
              - key: kubernetes.io/arch
                operator: In
                values:
                - amd64
              - key: eks.amazonaws.com/compute-type
                operator: NotIn
                values:
                - fargate
      containers:
      - env:
        - name: DATASTORE_TYPE
          value: kubernetes
        - name: FELIX_INTERFACEPREFIX
          value: eni
        - name: FELIX_LOGSEVERITYSCREEN
          value: info
        - name: CALICO_NETWORKING_BACKEND
          value: none
        - name: CLUSTER_TYPE
          value: k8s,ecs
        - name: CALICO_DISABLE_FILE_LOGGING
          value: "true"
        - name: FELIX_TYPHAK8SSERVICENAME
          value: calico-typha
        - name: FELIX_DEFAULTENDPOINTTOHOSTACTION
          value: ACCEPT
        - name: FELIX_IPTABLESMANGLEALLOWACTION
          value: Return
        - name: FELIX_IPV6SUPPORT
          value: "false"
        - name: WAIT_FOR_DATASTORE
          value: "true"
        - name: FELIX_LOGSEVERITYSYS
          value: none
        - name: FELIX_PROMETHEUSMETRICSENABLED
          value: "true"
        - name: FELIX_ROUTESOURCE
          value: WorkloadIPs
        - name: NO_DEFAULT_POOLS
          value: "true"
        - name: NODENAME
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: spec.nodeName
        - name: IP
        - name: FELIX_HEALTHENABLED
          value: "true"
        image: quay.io/calico/node:v3.18.1
        imagePullPolicy: IfNotPresent
        livenessProbe:
          exec:
            command:
            - /bin/calico-node
            - -felix-live
          failureThreshold: 6
          initialDelaySeconds: 10
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        name: calico-node
        ports:
        - containerPort: 9091
          hostPort: 9091
          name: metrics
          protocol: TCP
        readinessProbe:
          exec:
            command:
            - /bin/calico-node
            - -felix-ready
          failureThreshold: 3
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        securityContext:
          privileged: true
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /lib/modules
          name: lib-modules
          readOnly: true
        - mountPath: /run/xtables.lock
          name: xtables-lock
        - mountPath: /var/run/calico
          name: var-run-calico
        - mountPath: /var/lib/calico
          name: var-lib-calico
      dnsPolicy: ClusterFirst
      hostNetwork: true
      nodeSelector:
        beta.kubernetes.io/os: linux
      priorityClassName: system-node-critical
      restartPolicy: Always
      schedulerName: default-scheduler
      serviceAccount: calico-node
      serviceAccountName: calico-node
      terminationGracePeriodSeconds: 0
      tolerations:
      - effect: NoSchedule
        operator: Exists
      - key: CriticalAddonsOnly
        operator: Exists
      - effect: NoExecute
        operator: Exists
      volumes:
      - hostPath:
          path: /lib/modules
          type: ""
        name: lib-modules
      - hostPath:
          path: /var/run/calico
          type: ""
        name: var-run-calico
      - hostPath:
          path: /var/lib/calico
          type: ""
        name: var-lib-calico
      - hostPath:
          path: /run/xtables.lock
          type: FileOrCreate
        name: xtables-lock
  updateStrategy:
    rollingUpdate:
      maxUnavailable: 1
    type: RollingUpdate

FYI when uninstalling calico and re-creating all worker nodes, thereby cleaning all iptables rules, the problem does not occur.

@fasaxc just merged a patch through to fix this here: https://github.com/projectcalico/libcalico-go/pull/1397
Will be released in Calico v3.19.0, due in a couple of weeks.

Hi @caseydavenport , thanks for the quick reply. Great to hear that this is a known issue and that a fix is underway! However, this is hitting us very hard. Do you think that perhaps this fix can be backported to 3.18? And if not, is there perhaps a previous version of calico that we can rollback to?

Hi @caseydavenport , thanks for the quick reply. Great to hear that this is a known issue and that a fix is underway! However, this is hitting us very hard. Do you think that perhaps this fix can be backported to 3.18? And if not, is there perhaps a previous version of calico that we can rollback to?

We found a workaround for this issue:
kubectl delete -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/master/config/master/calico-crs.yaml
kubectl delete -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/master/config/master/calico-operator.yaml
curl https://raw.githubusercontent.com/projectcalico/calico/master/hack/remove-calico-policy/remove-calico-policy.sh -o remove-calico-policy.sh
kubectl create configmap remove-calico-policy-config -n=kube-system --from-file=./remove-calico-policy.sh
Create file and add this context  (change toleration if you have):
apiVersion: apps/v1
kind: DaemonSet
metadata:
name: calico-remove-iptables
namespace: kube-system
labels:
k8s-app: calico-remove-iptables
spec:
selector:
matchLabels:
k8s-app: calico-remove-iptables
template:
metadata:
labels:
k8s-app: calico-remove-iptables
spec:
hostNetwork: true
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: projectcalico.org/ds-ready
operator: NotIn
values:
- "true"
tolerations:
- key: CriticalAddonsOnly
operator: Exists
containers:
- name: calico-remove-iptables
image: calico/iptables-remover
command:
- "/bin/sh"
- "-c"
- "cp /etc/config/calico/remove-policy/remove-calico-policy.sh .; chmod +x ./remove-calico-policy.sh; ./remove-calico-policy.sh"
env:
- name: CLUSTER_CIDR
value: ""
securityContext:
privileged: true
volumeMounts:
# /etc/config is where we will store the remove-calico-policy.sh script from the ConfigMap.
- mountPath: /etc/config
name: config-volume
volumes:
- name: config-volume
configMap:
name: remove-calico-policy-config
items:
- key: remove-calico-policy.sh
path: calico/remove-policy/remove-calico-policy.sh
kubectl apply -f .yaml
It will clean all calico settings.
REMOVE:
kubectl delete -f .yaml
kubectl delete configmap remove-calico-policy-config -n=kube-system

I don't understand how this is a workaround? You start by uninstalling calico and then running a script. From the looks of it, this will leave clusters without policy enforcement, whatsoever.

Once we applied calico on our cluster, we got errors when tried to redeploy
deployment.  Calico 3.17 has the bug.
On Tue, Apr 20, 2021, 10:36 Mitch Hulscher @.***> wrote:

I don't understand how this is a workaround? You start by uninstalling
calico and then running a script. From the looks of it, this will leave
clusters without policy enforcement, whatsoever.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/projectcalico/calico/issues/4518#issuecomment-823050371,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEV5QKH42OAO5HEKVQD3TZDTJUVJFANCNFSM42SXQRXQ
.

@eligosfx deleting Calico in that way will leave your cluster broken.  In particular, you'll delete the IPAM tracking data so you may find that new pods get assigned IPs that belong to previously-networked pods.

https://github.com/projectcalico/calico/tree/master/hack/remove-calico-policy
On Tue, Apr 20, 2021 at 1:51 PM Shaun Crampton @.***>
wrote:

@eligosfx https://github.com/eligosfx deleting Calico in that way will
leave your cluster broken. In particular, you'll delete the IPAM tracking
data so you may find that new pods get assigned IPs that belong to
previously-networked pods.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/projectcalico/calico/issues/4518#issuecomment-823177884,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEV5QKCYCHT4TFYDAT3A2O3TJVMEDANCNFSM42SXQRXQ
.

Oh, you're on EKS, then Calico isn't doing IPAM so you should be OK.

Yes, I talked about a workaround for aws eks cluster.
On Tue, Apr 20, 2021 at 3:35 PM Shaun Crampton @.***>
wrote:

Oh, you're on EKS, then Calico isn't doing IPAM so you should be OK.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/projectcalico/calico/issues/4518#issuecomment-823237233,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEV5QKBHMZJMYVJBUA36HGLTJVYJVANCNFSM42SXQRXQ
.

We've had to revert https://github.com/projectcalico/libcalico-go/pull/1397; it caused a downstream problem that we don't fully understand yet.

@fasaxc that is very unfortunate. Is the goal still to fix this issue in the next minor or patch release? Or should we expect it a release after that?

Azure/AKS#2223 documents a pretty good repro of this in AKS. when chained onto the azure cni.
I'm confused if the revert https://github.com/projectcalico/libcalico-go/pull/1406/files might be a fix? If so taking 1.19 might be a soltuion here?

@paulgmiller sadly that was reverting a candidate fix. The candidate fix broke a bunch of system tests in a non-obvious way

Is there perhaps an updated ETA for a fix to this issue?

I would also be keen to know if there is an ETA?

To add an additional data point, we're also experiencing this issue as well.
Calico version: v3.17.3
AWS VPC CNI version: v1.7.9-rc1
containerd version: 1.4.3

We are also having this issue with v3.17.2.  This causes that open requests cannot be served and database connections are left open.
v3.13.2 seems to work as expected. We are currently trying to narrow down the version.

We have been testing various versions of calico and it seems that v3.15.5 is the last one to work as expected and that the next release v3.16.0 is broken, i.e. iptables rules are immediately deleted when SIGTERM is received.

Just to let you know what's going on here; in v3.16 we fixed a different bug and inadvertently caused this one.
The other bug was that pods that terminate without being deleted, such as Jobs, would still appear to Calico to have an IP address even though the CNI plugin had been called to remove the pod from the network.  That was a security problem because Calico would think that the IP still belonged to the old Job pod even though it was now free and could be re-used by a new pod with different permissions.
We closed that loophole by changing Calico CNI to add an annotation to the pod to mark whether it has an IP or not. However, you're not using Calico CNI so you don't get part of the fix; instead, with EKS CNI, we're checking for the annotation and not finding it and treating that as "no IP".  It's not easy to fix because the k8s API doesn't cleanly expose the fact that a pod is "terminating but may be in its grace period" rather than "terminated and no longer owns its IP".

After a lot of investigation we came up with the same observation: that a route to a Pod whose state is switching to Terminating is getting deleted right away - not respecting the Pod lifecycle.
Effect include Kubelet marking the Pod as Unhealthy right away, if Pod is part of an svc/endpoint then traffic is dropped.
It's a significant impact .. but I am glad that reverting to 3.15.1 works (3.15.5 seem to be okay too).
Thank you very much for giving this issue the attention it deserves as ongoing support for EKS using AWS-VPC-CNI is an important feature of Calico project.

. It's not easy to fix because the k8s API doesn't cleanly expose the fact that a pod is "terminating but may be in its grace period" rather than "terminated and no longer owns its IP".

Rather than monitoring the pod, would it be better to monitor the endpoint slice?

@fasaxc  is the pod s[ec patched to remove PodIP after termination for jobs?

This one is being worked on as a high-priority issue - if anyone needs guidance in the meantime, please feel free to get in touch with me.

Not sure if this KEP feature will help
https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1669-graceful-termination-local-external-traffic-policy#additions-to-endpointslice
This is to expose a Terminating condition on the endpoint slice that can be monitored by the CNI

@nikskiz sadly not but we've got the fix in hand. We're just going to restore the old behaviour for non-Calico CNIs.  The old behaviour was to use the "Phase" of the Pod to decide if its IP was legit.  That works almost always but there was a bug in older k8s versions that meant that a pod could get stuck in the wrong phase for too long when it was terminating.

Hi, is there a plan to backport this fix to older versions of Calico? AWS CNI comes with tigera operator 1.13.2 which brings in calico 3.17.1 so i am mostly interested in backports to 3.17
thanks!

@primeroz this is an AWS issue as they should never have moved off the v3.15 release family as this issue was known before the new Calico pattern was adopted. See the comments at the end of https://github.com/aws/amazon-vpc-cni-k8s/pull/1541.

thank you @stevehipwell I see there as well was mentioned that a backport has been done so i will wait for a release of the 3.17 series with the fix in and stick to the 3.15 i am currently running for now until that is released.
thanks

We've stuck with the legacy Calico v3.15.1 version that was in eks-charts until very recently as the upgrade in the linked PR broke any cluster it was run on. We're currently testing v3.20.0 via the operator which seems good so far. Based on the issues on version selection from the AWS team I'm not seeing anything special about v3.17 in the aws-vpc-cni repo and v3.19 in the eks-charts repo so I can't see why the latest v3.20 wouldn't be the best bet?

@stevehipwell great work and i agree on the 3.20 , just had no time to get to test it yet ( sweet sweet holidays )
I am not sure what is holding back the aws repo on that version, even for 1.9.0 ( recently released ) they still use the same operator version which has the bug in it.
If you could report on your testing that would be extremely useful.

I will do @primeroz, you might also be interested in https://github.com/tigera/operator/issues/1428.
FYI I have a custom Tigera Operator Helm chart due to the official chart lacking idiomatic Helm functionality. When I get some time I'll look at seeing if there is any interest in getting the changes into this repo.

Calico v3.19.2 has now been released, which also has the fix.

I see 3.17.5 has been released ( and so is its tiger operator version ) was this backported to it ?

Hi @primeroz, yes v3.17.5 and v3.18.5 both have the pod termination fix backported.


Lab 5 Level 5

Summary
Having some issues with sum and f method in level5.jsh
Description:
My sum and f method in level5.jsh unable to provide the same outputs as required. Anyone can assist for these two methods to return the correct outputs

Hi, if you are looking for a way to get started on level 5, maybe @ZHD1987E's thread might help. https://github.com/nus-cs2030/2324-s2/issues/293


Integrate EntityLink into Entitas

Ship Entitas.Unity.VisualDebugging plugin including EntityLink for linking entities to GameObjects.
See EntityLink https://github.com/sschmid/Entitas-CSharp/wiki/Tools-and-Extensions

Done.


Add zip and debian distributions to validation workflow

Is your feature request related to a problem? Please describe
The current workflow is lacking validation for zip and debain distributions, which needs too be separately validated during releases or when required.
Describe the solution you'd like
Add code to support zip and debian distributions to use the validation workflow with all the supported distributions till date.
Describe alternatives you've considered
No response
Additional context
#4424

Closed via #4447


Server error occur, contact administrator” when disable webauthn register & passwordless

Hello everyone,
we have a problem that is so complicated, namely when we turn off the “Webauthn Register / passwordless” feature it appears error “Server error occurred, contact administrator”, we deliberately turned off the feature because if the feature is active the error appears “Security key registration result is invalid.
WebAuthn is not supported by this browser. Try another one or contact your administrator.” is there anyone here who has the same problem? please help us, thank you.

I don't think your issue is PocketBase related and I don't know from where this screenshot is from.
PocketBase doesn't have Passkeys/WebAuthn support out of the box (see https://github.com/pocketbase/pocketbase/issues/406).


Preferred scan.execute behaviour (API)

What is the preferred behavior for the scan.execute from a user perspective?
At this moment the execute returns a Spark data frame. The data frame contains the measurements of thescan_results.
Maybe it does not make sense to returns this a Spark data frame:

we are doing an extra python -> spark conversion.
if changes are made to the scan results, then we need to update the logic here too.

We could return the scan result object. However, that is maybe not an object the user expects, as it is Soda internal.

Hey @JCZuurmond
Following up on our discussion in Soda's Community Slack, since spark-sql is going to be used with developers as main users, it would be best to be able to run scan functions separately, rather than running an execute which only some of the results might help the data engineer using the tool.
IMHO, this part of soda-spark needs to be designed as a library, rather than a config driven tool.
Happy to chat/help!

The discussion about data frames is held at #95. I am closing this issue since it it too broad.


Hello From Canada Fellow Polak Jak Sie Masz, Im in serious troubble here.

I messed up an drfeally could use a save here. I used this program fro secure abnout 300GB of data, which included  personal and my comapnies info. I cant rcall my password , I did the ecryhption process after a few Vodkas and now am just Kurva na siebie sie zloszce, Can you please help and let me know if it is posible to some hows recover this password.
my encrytiopn file rendered this.
Keystore.cfg
{
"c_encryptionKey": "c16oF0pEE17uS6zz89YfkawBSCI3wLV4BupSXy/ZDNUl4kwjp0mlQw==",
"c_macKey": "LsCsmOxHhH817+uQNRQqsgN06ez0SvkE06qp7z+OCMamdhIbP38igQ==",
"salt": "lBRNx7EP92G6xAhFBlnO3w=="
}
Sfconfig,cfg
Sfconfig.cfg{
"contentCipherScheme": 4,
"filenameCipherScheme": 2,
"version": 1,
"hmacsha256mac": "ZVxrFFTe2Qdwb6YcF9PYbUIYuyCvqPV+9Fcc/GhQv+w="
}
Running oin Win 11 Pro
Aecure folder FS Beta v.<IP_ADDRESS>
my email is<EMAIL_ADDRESS>for priovate one on one convo if need be.  Masybe we can even videro chat about this in Polish
Cejszcz
Thank you kindly .

Hi! Could you make sure you haven't made any changes to the configuration files? SecureFolderFS won't be able to unlock the vault if the config is corrupted.
The app is built to prevent anyone without decryption keys from accessing the vault. There's no central data storage that holds decryption keys -- as that'd be insecure by design. If you really can't recall your password, I've made a simple console app some time ago to use as brute-force.
SecureFolderFS-bruteforce.zip

The upcoming version of SecureFolderFS will allow you to view recovery codes for each vault. However, you'll still need to provide the password to be able to view them (The app has no other way of knowing them)


[Cosmos] async client unable to complete cross-partition 'COUNT' queries

Upon looking into https://github.com/Azure/azure-sdk-for-python/issues/23799, I found that while the synchronous client has no problems executing a count query to return how many total items in a container, the async client runs into some errors trying to make sense of the iterator. This only happens for cross-partition queries (trying to get the total item count).

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Cosmos:0.36731434,azure-spring:0.059326712,Docs:0.05829083'


basic unregister tests

via #1719
@sheerun been reading over the src and seeing how you test commands in bower, due to the use of nextTick promise returns, and non promise guard clauses I have been having one heck of a time implementing some more robust tests.
I would appreciate any advice on how to proceed, or pointers into what you would like to see. Needless to say  I am more than willing to finish this one out.
Thanks for the time and :eyes:

ah I see what you did in b425175587409068033cb1b83d22ea01cf7d6da9
great ok will follow

Hey @samccone. Thank you for spending your time on Bower.
I'm working on releasing some features & bugfixes soon, maybe you'd like to help as contributor?
I could add you to core team members, so your commit experience is more smooth.

hey @sheerun totally would not mind helping out, I spent quite a bit of time over the last few weeks reading over the src to understand the system that is built up over here, I am just trying to get to a point where I can actually start helping out in a more major way :)

Closing this PR for now, will reopen when I have something more substantial


Releasing new extension - Mongo Migration to CosmosDB

Releasing new extension - Azure Cosmos DB Migration for MongoDB
link to - binary

@bharathpalaksha - please fix the gallery content to match the package.json fields:
Error validating package.json. Error: package.json version ^1.39.0 (vscode) does not match extension gallery version * (Microsoft.VisualStudio.Code.Engine)


chore: update bug report template

cc @AlCalzone

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 27.332%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3636

Relevant Lines:
14023

💛  - Coveralls


Typo "Azure Open AI"→"Azure OpenAI"

https://learn.microsoft.com/en-us/azure/communication-services/samples/call-automation-ai?pivots=programming-language-javascript
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/call-automation-ai.md
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/communication-services/samples/includes/call-automation-ai-javascript.md
#PingMSFTDocs

Thanks hyoshioka0128!


Execute application stat counts in parallel

A thread pool is started that gets or executes the counts in parallel.
This requires the test database to not be SQLite, since multiple
connections are not supported while the test suite is running. See
https://github.com/django/django/blob/stable/1.6.x/django/db/backends/sqlite3/base.py#L96
Fix #252
Signed-off-by: Byron Ruth<EMAIL_ADDRESS>

Coverage decreased (-0.01%) when pulling 93e428775c6e70ba981a7990c977a2ca61b16aa3 on issue-252 into b8aa1d2f2fb15dc0a5dd20dc87606f0c869bdd6c on master.

Coverage increased (+0.01%) when pulling a240af4b0c36e00c7206a38a53b5e83fa3ef7129 on issue-252 into b8aa1d2f2fb15dc0a5dd20dc87606f0c869bdd6c on master.

Coverage increased (+0.0%) when pulling 7f890585b545edf8f769240720b5f6b8ce8b91ea on issue-252 into b8aa1d2f2fb15dc0a5dd20dc87606f0c869bdd6c on master.

Coverage decreased (-0.01%) when pulling 6c0046796573e11076a934440f814f5610e0f1af on issue-252 into b8aa1d2f2fb15dc0a5dd20dc87606f0c869bdd6c on master.


Bot Responds: "request failed: Attempt to decode JSON with unexpected mimetype"

I just set up the latest version of maubot-invite, and when I attempt to !invite generate my bot responds with:
request failed: Attempt to decode JSON with unexpected mimetype: text/html; charset=utf-8
Any ideas what may be causing this?

looks like you're probably getting an error code (like a 400 or 500 html response type thing) instead of proper json. i would say double-check your bot config, make sure you're using the right value for legacy_mr to match your install, and test your matrix-registration endpoints to ensure that your api calls work properly without the bot (use curl or postman or something to make the raw api calls).
i could probably add better error handling to the bot so it would tell you what response it got instead of proper json, but that will have to wait a bit.

i've updated the code to show the response code and the html response returned by your matrix-registration endpoint in the hopes it helps troubleshoot issues like this. closing this, but i can re-open if you feel this is still unresolved.

Thank you for this. Ultimately it was a user issue on my end, your update helped me track down the cause. Much appreciated!


addIndexes Method

Please help to use addIndexes() to add already indexed file with current indexed file . Thanks in advance.

Are you referring to the CLucene lucene::index::IndexWriter class? You should post CLucene specific questions to CLucene directly (http://clucene.sourceforge.net/), as that is not part of the BRFullTextSearch API.