Add ignore for 3rdparty code for MSVC code analysis

Signed-off-by: The MathWorks, Inc<EMAIL_ADDRESS>

Codecov Report

Merging #692 (7531ee6) into development (fec264e) will decrease coverage by 5.42%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           development     #692      +/-   ##
===============================================
- Coverage        90.21%   84.78%   -5.43%
===============================================
  Files              234      106     -128
  Lines            13385     4699    -8686
===============================================
- Hits             12075     3984    -8091
+ Misses            1310      715     -595

Impacted Files
Coverage Δ

framework/src/bundle/BundleStorage.h
0.00% <0.00%> (-100.00%)
:arrow_down:

framework/src/service/ServiceListeners.h
0.00% <0.00%> (-100.00%)
:arrow_down:

util/include/cppmicroservices/util/DataContainer.h
0.00% <0.00%> (-100.00%)
:arrow_down:

...ework/include/cppmicroservices/detail/ScopeGuard.h
0.00% <0.00%> (-100.00%)
:arrow_down:

framework/include/cppmicroservices/Any.h
0.00% <0.00%> (-93.47%)
:arrow_down:

.../cppmicroservices/detail/BundleAbstractTracked.tpp
16.12% <0.00%> (-71.46%)
:arrow_down:

...include/cppmicroservices/detail/TrackedService.tpp
14.70% <0.00%> (-70.30%)
:arrow_down:

...ork/include/cppmicroservices/detail/CounterLatch.h
35.29% <0.00%> (-61.49%)
:arrow_down:

...include/cppmicroservices/detail/ServiceTracker.tpp
29.62% <0.00%> (-55.72%)
:arrow_down:

util/src/BundleObjFile.cpp
71.42% <0.00%> (-28.58%)
:arrow_down:

... and 207 more


Sync eng/common directory with azure-sdk-tools for PR 1077

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/1077
See eng/common workflow

/check-enforcer override


Incorrect intelligence and problem refreshing the error after correction

From @saurabhnachankar on November 8, 2016 6:13

VSCode Version: Code 1.7.1 (02611b40b24c9df2726ad8b33f5ef5f67ac30b44, 2016-11-03T13:53:14.822Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

net-core-project-manager
ksubedi
0.3.6

csharp
ms-vscode
1.4.1

Steps to Reproduce:

Intelligence should be improved in Visual Studio Code. Proper suggestion are not specified in the intelligence
Error are not refreshed in code after correcting it.
Very poor approach for developing in code considering other IDE's

Copied from original issue: Microsoft/vscode#15143

From @saurabhnachankar on November 9, 2016 5:52
This was my controller's method invoking for creating XL file through
Epplus.
Issue No. 1  : This was my following using :  using
Microsoft.Net.Http.Headers; for ContentDispositionHeaderValue.
But i was not able to get it through intelligence in Visual Studio Code. so
i opened it in visual studio community and got the appropriate using.
Eg :
Response.Headers["Content-Disposition"] = new
ContentDispositionHeaderValue("attachment")
Issue No 2 : Even commented code is complied in debugger and later shows
the following error of commented code like
Eg :

In Browser error:
An error occurred during the compilation of a resource required to process
this request. Please review the following specific error details and modify
your source code appropriately.
Please fix the issue of VS-Code
Regards,
Saurabh Nachankar
On Tue, Nov 8, 2016 at 7:41 PM, Martin Aeschlimann<EMAIL_ADDRESS>
wrote:

@saurabhnachankar https://github.com/saurabhnachankar For what language
is that? Can you also add a small code sample that demonstrated the issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/15143#issuecomment-259146007,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AR87YDT1IbIm29xgJknSJqQjyGnhek8oks5q8IMegaJpZM4KsEgV
.

@saurabhnachankar For what language is that? Can you also add a small code sample that demonstrated the issue?

Moving to C#

I suspect this is the same as #858. I've prepared a brand new release of the C# extension that should address this problem. Would you be willing to try this new release before we ship it on the VSCode marketplace? Use the following instructions to try it out.

Download the VSIX from here
Open Visual Studio Code
Select View->Extensions to display the Extensions pane.
In the Extensions pane, click the little gear icon next to the C# extension and select Uninstall.
Confirm any prompts and allow Visual Studio Code to reload itself.
In the Extensions pane, click the [...] that appears in the top-right corner and select "Install from VSIX..."
Select the VSIX you downloaded.
Let Visual Studio Code reload itself.

This should be fixed in the 1.5.2 release. Please let us know if it is still a problem.

Thank you for replying..
Regards,
Saurabh Nachankar
On Wed, Nov 16, 2016 at 11:48 PM, Dustin Campbell<EMAIL_ADDRESS>wrote:

Closed #894 https://github.com/OmniSharp/omnisharp-vscode/issues/894.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OmniSharp/omnisharp-vscode/issues/894#event-861532627,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AR87YOF28_-DGugw4hFVyDO6_jTydHBhks5q-0jdgaJpZM4KtQNt
.


[SPARK-23375][SQL][FOLLOWUP][TEST] Test Sort metrics while Sort is missing

What changes were proposed in this pull request?
#20560/SPARK-23375 introduced an optimizer rule to eliminate redundant Sort. For a test case named "Sort metrics" in SQLMetricsSuite, because range is already sorted, sort is removed by the RemoveRedundantSorts, which makes this test case meaningless.
This PR modifies the query for testing Sort metrics and checks Sort exists in the plan.
How was this patch tested?
Modify the existing test case.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Test build #99852 has started for PR 23258 at commit 408ccf8.

cc: @mgaido91

Test build #99856 has started for PR 23258 at commit 6e36336.

Test build #99856 has finished for PR 23258 at commit 6e36336.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #99852 has finished for PR 23258 at commit 408ccf8.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/99856/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/99852/
Test FAILed.

Test build #99864 has finished for PR 23258 at commit 6e36336.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/99864/
Test PASSed.

Test build #100430 has started for PR 23258 at commit 0f514fd.

Test build #100431 has started for PR 23258 at commit 4ee2c8d.

Test build #100431 has finished for PR 23258 at commit 4ee2c8d.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #100430 has finished for PR 23258 at commit 0f514fd.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100431/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100430/
Test FAILed.

retest this please.

Test build #100432 has started for PR 23258 at commit 4ee2c8d.

Test build #100432 has finished for PR 23258 at commit 4ee2c8d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100432/
Test FAILed.

retest this please.

Test build #100436 has started for PR 23258 at commit 4ee2c8d.

retest this please.

Test build #100445 has started for PR 23258 at commit 4ee2c8d.

Test build #100445 has finished for PR 23258 at commit 4ee2c8d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #100466 has started for PR 23258 at commit 1e55f31.

Test build #100466 has finished for PR 23258 at commit 1e55f31.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100466/
Test FAILed.

retest this please.

Test build #100468 has started for PR 23258 at commit 1e55f31.

Test build #100468 has finished for PR 23258 at commit 1e55f31.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #100495 has finished for PR 23258 at commit c3336d8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100495/
Test PASSed.

Test build #100505 has started for PR 23258 at commit 75d0c08.

Test build #100505 has finished for PR 23258 at commit 75d0c08.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100505/
Test PASSed.

Test build #100525 has started for PR 23258 at commit 386a7e5.

Test build #100525 has finished for PR 23258 at commit 386a7e5.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100525/
Test FAILed.

retest this please.

Test build #100528 has started for PR 23258 at commit 386a7e5.

Test build #100528 has finished for PR 23258 at commit 386a7e5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100528/
Test PASSed.

Test build #100557 has finished for PR 23258 at commit c496c54.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100557/
Test PASSed.

Merged build finished. Test PASSed.

Test build #100566 has finished for PR 23258 at commit 3ce0e03.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/100566/
Test PASSed.

Test build #100574 has started for PR 23258 at commit 5e94a3e.

@srowen @mgaido91 I have made changes according to your comments in the new commit.

LGTM, thanks for your work on this @seancxmao!


migration to package extensions

Closes #405.
We can hopefully remove all these strong dependencies.

[ ] Dates
[ ] Markdown: needed for interactive help (probably always loaded by Julia anyway)
[x] Pkg: removed juliacall.Pkg
[ ] REPL: it is only imported when needed (i.e. when juliacall is loaded in an interactive Python session)
[ ] Requires
[ ] Serialization: this is needed by __reduce__ in jlwrap anyway (unless we load it on demand??)
[ ] Tables

@cjdoris Do you want help for migration to package extensions?
If so, would you like to keep the package working for Julia versions < v"1.9" via Requires?
For Stipple.jl we have chosen that pathway.

@cjdoris Do you want help for migration to package extensions? If so, would you like to keep the package working for Julia versions < v"1.9" via Requires? For Stipple.jl we have chosen that pathway.

Maybe, though the only things remaining on the list are Dates and Tables.
I think Dates can't be removed because if you do pyconvert(Any, some_python_datetime) then we need it to be converted to a Julia DateTime and Dates won't necessarily be loaded if we make it a weak dependency.
I'm not sure about Tables. We use it in two places:

The PyPandasDataFrame wrapper type. The Tables functionality here can definitely go into an extension.
The pytable function. For this to go into an extension, we'd need to know that Tables is definitely already loaded before pytable(x) is called for any table x. I don't think we can guarantee this because a package can just provide its Tables-compatibility via an extension, so if we call pytable(::FooPackage.FooTable) then FooPackage is certainly loaded but Tables might not be. It also won't work if x is a named tuple of vectors or a vector of named tuples, which are both considered tables, unless we provide special handling for them. As a concrete case, if we moved the PyPandasDataFrame stuff into an extension as in the previous bullet point, then pytable(::PyPandasDataFrame) would stop working because Tables wouldn't be loaded.

So all in all I think there's no more to do on this.

Well, I think there is. There are three occurrences of @require which would all be replaced by package extensions. The content of the extensions will be precompiled while there is no precompilation happening when you rely on @requires. As said above, we have kept Require.jl in the package environment for compatibility but we only use it for Julia versions < v1.9.
From Julia 1.11 on we have the possibility of defining version-dependent Project.toml files so that Requrire.jl will no longer be used.

Yes you're right the current uses of @require can be migrated to extensions.
Didn't know about the upcoming version-dependent Project.toml, that's cool!


Monomorphization and specialization of Simplifier, leg 5

Fixes #3325
Scope:
The 5th leg of the Simplifier monomorphization and specialization.
Modules affected:
Kore.Builtin.AssocComm.CeilSimplifier
Kore.Builtin.Builtin
Kore.Builtin.Map
Kore.Exec
Kore.Reachability.Claim
Kore.Rewrite.Function.Evaluator
Kore.Rewrite.Rule.Simplify
Kore.Simplify.And
Kore.Simplify.AndTerms
Kore.Simplify.Application
Kore.Simplify.Ceil
Kore.Simplify.Condition
Kore.Simplify.Equals
Kore.Simplify.Exists
Kore.Simplify.Iff
Kore.Simplify.Implies
Kore.Simplify.In
Kore.Simplify.Not
Kore.Simplify.OrPattern
Kore.Simplify.Pattern
Kore.Simplify.Predicate
Kore.Simplify.SubstitutionSimplifier
Kore.Unification.SubstitutionSimplifier
Kore.Unification.UnifierT
Estimate:

Review checklist
The author performs the actions on the checklist. The reviewer evaluates the work and checks the boxes as they are completed.

[ ] Summary. Write a summary of the changes. Explain what you did to fix the issue, and why you did it. Present the changes in a logical order. Instead of writing a summary in the pull request, you may push a clean Git history.
[ ] Documentation. Write documentation for new functions. Update documentation for functions that changed, or complete documentation where it is missing.
[ ] Tests. Write unit tests for every change. Write the unit tests that were missing before the changes. Include any examples from the reported issue as integration tests.
[ ] Clean up. The changes are already clean. Clean up anything near the changes that you noticed while working. This does not mean only spatially near the changes, but logically near: any code that interacts with the changes!

Result: 3.21% decrease in time.
report-monom--leg-5_master.pdf


Cross platform P/Invoke

Summary
Adds an article detailing the order in which DLLs are searched on Windows, Linux and macOS. I haven't seen any pre-existing docs for this and it's very useful information when writing cross-platform P/Invoke code. See dllimport.cpp for runtime source.

Thanks @saul
While I wait for @jkoritzinsky to weigh in, can you add a project file (*.csproj) where you added the new file? You'll need to specify a single entry point, so the compiler doesn't complain about multiple Main methods. That way, we ensure that everything compiles cleanly.
(If it's not too much to ask, these should be separate projects as they are all standalone programs, but I realize that's a lot to ask in expanding this PR).

Thanks again @saul
I'll :shipit: now.


chunk h=100

While training the DiT-Block Policy models to predict sequences of H = 100 actions, this approach served as regularization during training and allowed us to use temporal ensembling to enhance stability during runtime.
Following the parameters described in the paper, experiments conducted in the aloha environment of lerobot seem to yield suboptimal results. If temporal ensembling is not employed, there is severe jitter in action execution. Have you experienced similar issues during your training processes?  Thank you!

It's a bit hard to comment, since so many of these things can vary task to task. But I've definitely noticed jitter before that goes away with temporal ensembling. I would strongly recommend you tune the alpha parameter in ensembling if you employ it.
Also, if your val metrics are super high, it may mean you need to tune the training hyperparameters (e.g., ac_chunk, lr schedule, pre-trained parameters, etc.) a bit. Another idea is to collect more training data, or improve your demo dataset's quality (e.g., more diversity in demos).


move apply method to seperate package (#149)

cherry pick https://github.com/open-cluster-management-io/work/pull/149 to 2.6.1

move apply method to seperate package

Signed-off-by: Jian Qiu<EMAIL_ADDRESS>
make sure the update apply func returns existing object

Signed-off-by: zhujian<EMAIL_ADDRESS>Signed-off-by: Jian Qiu<EMAIL_ADDRESS>Signed-off-by: zhujian<EMAIL_ADDRESS>Co-authored-by: Jian Qiu<EMAIL_ADDRESS>

/hold

cc @qiujian16 @elgnay

/test verify

/test verify

/approve
/lgtm

/hold cancel
2.6.2 is open


Fix conflict detection failure while pushing local delete operations

This PR closes https://github.com/Azure/azure-mobile-apps-js-client/issues/179.
Root cause of the bug is that the push operation does not pass the version information and hence a conflict is never detected.
This PR stores the version information in a metadata column in the operation table. This way we can retrieve the version of a deleted record while performing a push.

@danderson00 - The diff is relatively large, but the crux of the fix is in the source files in the 3rd commit. Rest all are mostly test related changes. I can walk you through the main changes, if required.

It's getting difficult to see what is happening in changes, particularly given I lack a lot of context. There seems to be a lot of code here, it's hard to see if features could be expressed more concisely.
Particularly, try to keep your modules smaller and more focused. Once they start getting into the hundreds of lines, it starts to become very difficult to understand the entire module. Smaller modules are much easier to understand.

Calling modules "xManager" is a sure sign they are not conforming to SRP

Ok, let's talk about it. Is the name xManager bothering you or is it the actual contents of https://github.com/Azure/azure-mobile-apps-js-client/blob/master/sdk/src/sync/operations.js? https://github.com/Azure/azure-mobile-apps-js-client/blob/master/sdk/src/sync/operations.js is responsible just for doing the operation table tasks and that way is very focused.

Merging PR, but if you have any thoughts about anything that can be done better, do let me know.


Compiler hangs if two interfaces try to import each other

On d23d5f249
interface Test1
    exposes [
    ]
    imports [
        Test2
    ]

interface Test2
    exposes [
    ]
    imports [
        Test1
    ]

No crash or output from the compiler, just stalls until killed.

This situation now gives a very neat error message:
── IMPORT CYCLE ─────────────────────────────────────────────── Interface2.roc
I can't compile Interface2 because it depends on itself through the
following chain of module imports:
┌─────┐
│     Interface2
│     ↓
│     Interface1
│     ↓
│     Interface2
└─────┘

Cyclic dependencies are not allowed in Roc! Can you restructure a
module in this import chain so that it doesn't have to depend on
itself?
So I think this issue is solved and can be closed. @Anton-4 ?


Load all the services providers attached to a module...

... and write a manifest for each module like Laravel does.
TODO:

[x] Write some tests about that. Laravel doesn't have any, so need to think about it.
[ ] Test with Lumen.

Thanks! 👍


Error on awsmobile publish

ERROR in app/app.module.ts(37,5): Error during template compile of 'AppModule'
Function expressions are not supported in decorators in 'AmplifyAngularModule'
'AmplifyAngularModule' references 'AmplifyAngularModule'
'AmplifyAngularModule' references 'ɵ1'
'ɵ1' contains the error at ../aws-amplify-angular/lib/aws-amplify-angular.module.js.ts(12,43)
Consider changing the function expression into an exported function.
build command exited with code 1

Related to https://github.com/aws/aws-amplify/issues/766
Only workaround for now is to disable AOT, which is not ideal:
Edit "awsmobilejs/.awsmobile/info/project-config.json" and change the build command to "ng build --prod --aot=false"
Need to investigate if a potential upgrade to Angular 6 could help the AOT build or wait for a fix on Amplify.

Fixed with latest commit and updated amplify versions:
"aws-amplify": "^0.4.8",
"aws-amplify-angular": "^0.1.6",


Added generic custom matcher builder

Description
Adds automatic generation for custom matchers without the need to define them manually.
Check List

[ x ] New functionality includes testing.

[ x ] All tests pass ($ rake test).
[ x ] New resources and/or actions have are included in the matchers.rb and matchers_spec.

Nice! So much better than what we had before :smile: I'll be good with this once we get the Travis issues fixed


[FLINK-19031] Remove deprecated StreamExecutionEnvironment#setStateBackend(AbstactStateBackend)

What is the purpose of the change
Remove long deprecated StreamExecutionEnvironment#setStateBackend(AbstactStateBackend)
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Also looks good to merge! Finally, we get rid of the deprecation warnings in the IDE...

Very thank @dawidwys for opening the PR to remove the deprecated method! It also looks good to me, and it should free users from the trouble to cast the StateBackend explicitly. Only left a very minor  comment on the code style.

Thank you both for the review. I'll merge it.


How to traverse the AST

Let's say i have a source code hello-world.cpp:
#include <iostream>

int add(int a, int b)
{
  int c = a + b;
  return c;
}

int main()
{
  std::cout << "Hello World\n";
  int res = add(1, 2);
  return 0;
}

I want to get every function body and save it as string. I know I can realize it by this ClangSharp, but i cant find any tutorial on how to traverse the ast, like how to use CXCursor.VisitChild. This is as far as i can go now:
 var tmpfile = "Hello-world.cpp";
        CXIndex Index = CXIndex.Create(false, false);
        CXTranslationUnit TU;
        CXTranslationUnit_Flags tmpFlag = CXTranslationUnit_Flags.CXTranslationUnit_DetailedPreprocessingRecord;
        var error = CXTranslationUnit.TryParse(Index, tmpfile, new ReadOnlySpan<string>(args), null, tmpFlag, out TU);

Can anyone can me some hint and an example code is the best :)
I can achieve this function in python:
import clang.cindex

file_name = "hello-world.cpp"
index = clang.cindex.Index.create()
# unsaved_files=[('test.cpp', code)],
translation_unit = index.parse(path=file_name, args=['-std=c++11'])  #
for node in translation_unit.cursor.walk_preorder():
    if node.kind == clang.cindex.CursorKind.FUNCTION_DECL:
        if node.extent.start.file.name == file_name:
            print(node.extent.start.file.name)
            print('Found Function:', node.spelling)
            print('Function Body:', node.extent.end.offset - node.extent.start.offset)
            print(node.extent.start.line, node.extent.start.column)
            st = node.extent.start.line
            print(node.extent.end.line, node.extent.end.column)
            ed = node.extent.end.line
        # print(node.extent.start.file.contents[node.extent.start.offset:node.extent.end.offset])
            count = 0
            for line in open(file_name,encoding='UTF-8'):
                count += 1
                if count >= st+1 and count<=ed:
                    print(line)

You can write effectively the same code, just needing to change a couple minor things where python has defined its own extension points.
You have two options. You can either use the raw interop APIs or the higher level wrapper. The higher level wrapper is easier/friendlier and more closely matches the Clang C++ API surface.
You would do var translationUnit = TranslationUnit.GetOrCreate(TU) to get a managed wrapper over the raw translation unit. You then have access to the cursor via translationUnit.TranslationUnitDecl and can find all its direct children via .CursorChildren.
A basic visitor can be seen here: https://source.clangsharp.dev/#ClangSharp.PInvokeGenerator/PInvokeGenerator.cs,4f00f2f122c68eda,references
You can naturally filter or otherwise handle things using LINQ, pattern matching, or other kinds of checks.

I have installed NuGet ClangSharp & libClangSharp 16.0, but there's an Error System.DllNotFoundException: 'Unable to load DLL 'libClangSharp':. Could u give some hint how to sovle it? Do I need VS19 or lower?

You're probably hitting a known limitation with NuGet. You can resolve the issue by adding the following to your csproj:
  <PropertyGroup Condition="'$(RuntimeIdentifier)' == ''">
    <RuntimeIdentifier>$(NETCoreSdkRuntimeIdentifier)</RuntimeIdentifier>
  </PropertyGroup>

Thanks for your speedy reply, I have successfully run this tool, but it seemed clang can only parse function with standard return type? For example, I have three functions:
extern bool NeedUpgradeStockInTransitAccount (CBizEnv& bizEnv, CBusinessObject* bo);

CBusinessObject	*CWarehouse::CreateObject (const TCHAR *id, CBizEnv &env)
{
	TRACE_METHOD;
	return new CWarehouse (id, env);
}

CWarehouse::CWarehouse (const TCHAR *id, CBizEnv &env) :
	CSystemBusinessObject (id, env),
	m_AlertInCheckDelete(true)
{
	TRACE_METHOD;
}

But this tool can only recognize the first function.

I have successfully run this tool, but it seemed clang can only parse function with standard return type?

Sorry, I missed this last response. If I remember correctly, then due to how the AST actually exists you need it to traverse the CWarehouse declaration. That will then allow the definitions to be found via the actual declaration; otherwise it appears to be uninstantiable code.


do you have any example using Oauth providers?

Hi, this seems really promising, love the fact about how simple is use it for user/password authentication, but the documentation using oauth providers seems not be enought, do you have some examples or documentations about how use it? thank you!

yes, here's some documentation:
https://docs.nhost.io/platform/authentication/sign-in-with-google
https://docs.nhost.io/platform/authentication/sign-in-with-facebook
https://docs.nhost.io/platform/authentication/sign-in-with-github
https://docs.nhost.io/platform/authentication/sign-in-with-linkedin
https://docs.nhost.io/platform/authentication/sign-in-with-spotify
You can check the environment variables for the providers here: https://github.com/nhost/hasura-auth/blob/main/src/config/providers.ts


Add an atomic, bounded connection counter

This avoids a buffer underflow error I've seen in the client which caused the connectionCount to go from 0 to 65535

This is a potential fix to #45. A better solution would be to figure out how the client gets down to zero connections and tries to remove another one, but I wasn't able to trace that pathway as easily.

Hi Paul,
Thanks for this. I'd like to get to the bottom of this as well.

Hi @lukebakken, just for reference, there's an internal Basho issue that we've had open for a while with much more detailed logs which may be helpful to you as well. It's internal request #12852 in the helpdesk system.

Thanks @pguelpa I've been participating internally on that ticket as well. I'll get to this once basho/riak-python-client#430 is fixed.

I've added your commits to #48. Thanks.


Can we remove DCO?

we should also think about the copyright header in every file.
Of course the original copyright and licence still applies, but its probably better to handle that in LICENCE.md or so, because this header licences are a) not really required b) hard to manage (do i have to add my name if i change a source? what if i copy a file? move a file?, etc.) and c) noisy.
Maybe @aeneasr @ory need to specify of what happens to the licence of this project and how the copyright should be handled. Also i would prefer MIT Licence personally, but just because i am not a lawyer and i don't like bureaucracy ;-)

Yeah we can remove the license headers. I don't think they're maintained very well anyways.
I would not remove the DCO because if it is removed, we could not switch to MIT without asking every single contributor for permission. I'm fine with MIT or Apache 2.0

Yeah we can remove the license headers. I don't think they're maintained very well anyways.
I would not remove the DCO because if it is removed, we could not switch to MIT without asking every single contributor for permission. I'm fine with MIT or Apache 2.0

ok, i think you know better about these topics. But i think the DCO is not checked right? Or is this just a silent agreement?

Seems like the DCO bot does not work anymore so you are correct, it is currently not enforced.

Ok this appears to be somewhat resolved, closing as part of the cleanup.


[gpio,SiVal] Testplan update for gpio

Added list of features to the gpio specification.
Moved adc_ctrl chip tests to chip_gpio_testplan.hjson
Added si_stage: SV* test cases to cover functionality enumerated in the list of features.
Updated the pre-silicon test cases with relevant SV* labels.

CHANGE AUTHORIZED: hw/ip/gpio/data/gpio.hjson

CHANGE AUTHORIZED: hw/ip/gpio/data/gpio.hjson


No logo provided for module.

The module does not have a logo.png in it base folder (/modulename/logo.png).

Thanks for reporting. we have fixed this issue in a new release.


Charm VS Elf Enemies

Charm effects vs elf enemies properly have advantage but the reason why is listed as "none." It was making it very confusing to figure out why certain enemies had advantage. I'm not sure if this is a solasta or mod thing. Either way maybe the mod can help with a clarification.

You should report this to TA. Let them know MovementAffinityConditionRestrained need a title and description.


Change text colors to green

Change text colors to green

Change text colors to green

Thanks Admin for the good works


Moving ballerina by example to mdbook and organize.

Created a new issue in repository - https://github.com/ballerina-lang/ballerina
issue - ballerina-lang/ballerina#4778
hence closing this issue


@angular-devkit/build-angular depends on vulnerable version of vite

Command
new
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Running npm audit on Angular v17 project causes an error output, because @angular-devkit/build-angular depends on vulnerable version of vite which is dependent on<EMAIL_ADDRESS>See more details: GHSA-gcx4-mw62-g8wm
Minimal Reproduction
Create new Angular v17 project.
Run npm audit in the project folder
Exception or Error
No response
Your Environment
Angular CLI: 17.3.8
Node: 20.16.0
Package Manager: npm 10.8.2
OS: win32 x64
Angular: 17.3.12
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package                         Version
@angular-devkit/architect       0.1703.8
@angular-devkit/build-angular   17.3.10
@angular-devkit/core            17.3.8
@angular-devkit/schematics      17.3.8
@angular/cdk                    17.3.10
@angular/cli                    17.3.8
@schematics/angular             17.3.8
rxjs                            7.8.1
typescript                      5.4.5
zone.js                         0.14.8
Anything else relevant?
No response

This is probably due to an outdated package lock file. Please re-generate your lock file.

I have regenerate then also it is giving the vulnerability issue after running npm ls rollup. I got the below result
npm ls rollup
<EMAIL_ADDRESS>C:\Users\DHAVJAI\Desktop\WebWorkspace\xmp-frontend
--<EMAIL_ADDRESS> +--<EMAIL_ADDRESS> | --<EMAIL_ADDRESS>|   --<EMAIL_ADDRESS>deduped   --<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>

Please reopen and resolve the issue @alan-agius4

@JainDhaval, based on the logs above, it seems you haven't successfully regenerated the lock file.
To regenerate the lock file, please run the following commands:
rm -rf node_modules package-lock.json
npm install

I also double-checked, and it does indeed appear that this is an issue on your end.
npm ls rollup
<EMAIL_ADDRESS>/XXXXXXXXXXXXXX
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>


Update to Swift 4.1

Codecov Report

Merging #132 into master will increase coverage by 5.34%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           master   #132      +/-   ##
========================================
+ Coverage   54.65%    60%   +5.34%
========================================
  Files           3      3
  Lines        2430   2430
========================================
+ Hits         1328   1458     +130
+ Misses       1102    972     -130

Flag
Coverage Δ

#Socket
60% <ø> (+5.34%)
:arrow_up:

Impacted Files
Coverage Δ

Sources/Socket/Socket.swift
59.64% <0%> (+5.39%)
:arrow_up:

Sources/Socket/SocketUtils.swift
91.66% <0%> (+5.55%)
:arrow_up:

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 6e19b61...27dea65. Read the comment docs.

Hi @billabt please review and merge and tag if you are happy. Thanks!


[SUPPORT] migration of Analytics content

PCX-6633

I'll drop a post in the migration chat about the localized files, but here are two things that need to happen before this can go live.
Additional changes required:

Fix table formatting at https://github.com/cloudflare/cloudflare-docs/pull/8512/files#diff-da30b23136cbf9bd1b1260bf0b5316a4ae278ffc64e6372c7366fb719fed6b34L299
Migrate all referenced images files to an /analytics/static/ folder

Merging b/c this is complete from a PCX perspective && we don't want to keep larger PRs floating around for too long since they can get merge conflicts.


Higher Order Types

You might be interested in this project also: https://github.com/DanielGronau/highj

Thanks. A few months ago I wrote Kind as semi-higher order type abstraction and then removed it from the project. It may re-appear when creating a project javaslang-pure, which will be a thin, algebraic abstraction layer above javaslang.

Higher order types as we know them from other languages, like Scala, are not possible in Java.
We already investigated the Kind type in Javaslang. But from my currently viewpoint it is still only a partial workaround which clutters the API a lot. Therefore I will close this ticket.
Please let me know if I missed s.th. or give me more details on how to bring this feature into Java/Javaslang.

an annotation processor is being worked on to add type-safety to the highj encoding. See derive4j/hkt#1 (input welcomed).


0.3.0 Release

Things to complete before release

[x] #181
[x] #182
[ ] Preferably #159

The release workflow should run once we make a tag and create a Github release.

[x] @jhamman could you check the secrets before and after the move?

@kwilcox volunteered to help with the release process.
xref: #172

And Xpublish 0.3.0 is now a thing!
You may now update pip to no longer being a git+ install.


.Net Core 3 Preview 5 compatibility

Hi Chris, PR to implement the changes from my notes.
The only point of note was that I couldn't work out how to get the blazor-sample project to reference the styles.css file from the BlazorModal project, so I've just manually copied it into the blazor-sample project to get it working.
This all runs fine on my machine under Preview 5.

Thanks for this @tomRedox. I'll take a look at the styles.css file issue now it's all merged.


Batch preprocessing plugin does not open

I can't open the batch preprocessing plugin:
Failed to import command at 'napari_sediment.batch_preproc:BatchPreprocWidget': module 'napari_sediment.batch_preproc' has no attribute 'BatchPreprocWidget'
The batch preprocessing in the Sediment plugin works though.

Should be fixed with 43fd64e


fix: ovn-cluster mode

After update ovn to 2.12, the previous ovn cluster can not be established. The reasons are nbctl/sbctl can not write data to local database and return error if it's not the leader and when restart it should point to the new leader to rejoin the cluster.

nb and sb leader may in different pods, we should handle them separately.


[INTEGRATION] In React native , pod install sooooooo slow

Describe the bug

In ReactNative
Pod install is sooooo slow.
the SDK url : HERE
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS] MacBook Pro Apple M1
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

it takes about 10 seconds for me, might be your connection speed?
Also this repo is specifically for the swift package install, you want to open a ticket instead, it’s listed s the other option when you click new ticket


Upgrade 3.0 sentry mode switch missing

After installing the new 3.0 integration, it seems the sentry mode switch is missing?

This is another feature I wasn't able to test unfortunately. Some checks were added to only add the sentry mode switch if the vehicle actually has sentry mode. Is there any chance you would be able to turn on debug logging for teslajsonpy and share the response when the vehicle_data endpoint is called?
To turn on debug logging, in your HA configuration.yaml, you set:
logger:
  default: info
  logs:
    teslajsonpy: debug

Restart HA and open your logs. There's a lot of entries but if you search for "vehicle_data", I'm just looking for the response after that which is going to be a lot of data. It should look something like:
2022-10-22 20:45:49.284 DEBUG (MainThread) [teslajsonpy.connection] 200: {"response":{"id":1... with a bunch of text after.
I'm really just looking for two specific keys, "sentry_mode_available" and "sentry_mode". If you can find those and let me know what their values are set to, that would help.
I made the assumption that "sentry_mode_available" was a key that specifies whether the vehicle has sentry mode because there's another one called "sentry_mode".

It might not be related to the integration at all.
Earlier today I had 34 entities, and suddenly four of those were disabled (rear seat heating x3 and sentry mode), so I removed the integration and reinstalled, and had a lot of problems doing that tonight, it failed a lot of times.
Then suddenly it finished installing without errors, and I am back to 34 entities, including sentry mode.
I have had some issues with connecting to the car tonight, one time it said 403 error, and an update that was being downloaded earlier today,  suddenly disappeared, so maybe Tesla servers has some issues?
Lets put this issue on hold for a day or two, and see if it is resolved..
I will however hijack my own thread and ask for something a little bit related..😀
In version 2.x there was a Max range switch (setting charge to 100%), has this been removed?

I think the key detection is fine. I think the issue is that random entities break and we're not cleanly accounting for that. I also had to remove and readd to re-enable my sentry and some of my seat heaters. I didn't have logging enabled, but if it was a 403 or or other error, we should gracefully handle that state and create the entity if it ever appears.

I will however hijack my own thread and ask for something a little bit related..😀 In version 2.x there was a Max range switch (setting charge to 100%), has this been removed?

Yeah there's no max range switch anymore but you should be able to just use the charger numbers entity and set it to 100%.

I think the key detection is fine. I think the issue is that random entities break and we're not cleanly accounting for that. I also had to remove and readd to re-enable my sentry and some of my seat heaters. I didn't have logging enabled, but if it was a 403 or or other error, we should gracefully handle that state and create the entity if it ever appears.

I'm thinking if we implement the idea of storing the data we get from the endpoint to a JSON file and just reference that when the car is asleep, connection issues, etc., it might resolve a lot of these issues. It would also fix the issue of not being able to restore the previous state after a restart.

I'm not a fan of using out of band storage. If this is important, use what HA already has with recoverable state. It's something a base class switch.

I can confirm the sentry mode switch is functional for me with V3.

I think the key detection is fine. I think the issue is that random entities break and we're not cleanly accounting for that. I also had to remove and readd to re-enable my sentry and some of my seat heaters. I didn't have logging enabled, but if it was a 403 or or other error, we should gracefully handle that state and create the entity if it ever appears.

I think you are spot on here.. 🙂
I am now back to all 34 original entities (with V3). Yesterday, when having connection issues also with Tesla App, it was suddenly 30, then 33, and today the last one showed up again (software update sensor).

I can confirm I was missing four entities including rear seat heaters and sentry mode. After reloading the integration several times while driving and parked online with sentry active the entities appeared (total of 34). Here it seems that another logic for detecting these might be helpful (maybe static depending on the model?). I will monitor for stability...

Same here but I have it with sentry, homelink, in addition to the 3 rear seat heating. It is working sometimes, sometimes not ...very strange

Just did a restart of HA, I’d say 30-40% of all entities are unavailable. Let’s see if they come back when the car wakes up by themselves or if a reload will be necessary…

Same here, when the car goes asleep (offline), the sentry mode, homelink, and rear seat heaters become unavailable. When I wake the car with the app (turning sentry mode on), those entities remain unavailable until I reload the integration.
This is especially unfortunate with homelink and sentry, as you should be able to use them when the car is asleep as they send a wake first.

Ok so we have a common theme, perhaps at start of the integration (or HA reboot) a car wake up should be forced? I'll try to manually wake the car just before an HA reboot to see

ok tried again, all entities are ok if I wake up the car before I restart HA ( and so the Tesla integration)

Yeah, this is an issue because if the car is asleep and the integration is initialized, it’s unable to obtain the JSON response data from the vehicle data endpoint. Some of the keys we’re using to check whether or not a vehicle has a device is in the vehicle data endpoint, so without that data, the entities are not created which is causing this issue.
Originally, I had it setup where the vehicle is always woken up on HA restart but some users apparently restart HA a lot and didn’t want the integration waking up their vehicles on start (unnecessary use of energy). So by default, it only wakes up the vehicle when the integration is first added and does not when it’s re-initialized (i.e. HA reboot). There is an option, however, to force the vehicle to be woken up on re-initialization in the integration configuration options.
Ideally, we could use different keys like options codes which comes from an endpoint that we always have access to, whether the vehicle is awake or asleep. The problem is the option codes are apparently no longer accurate, so we’re kind of stuck. The other option would be to just create every entity for every vehicle, but now you have entities for vehicles that are not valid.

What is interesting for all those missing entities : they depend on a check the "car" object to be setup at startup:
-rear seats:
            if "rear" in seat_name and not car.rear_seat_heaters:
                continue

-sentry
        if car.sentry_mode_available:
            entities.append(TeslaCarSentryMode(hass, car, coordinator))

-homelink
        if car.homelink_device_count:
            entities.append(TeslaCarTriggerHomelink(hass, car, coordinator))

to me clearly the car object is not fully initialised when entities are created, so we do miss an await or a block before we create those entities.
I do think that this is the same as #297

Thanks @shred86 we cross posted :) yes the wake car on start is probably the one I'm looking for to solve this issue ...

@shred86  While digging through this issue myself I also noticed a couple related suspects in teslajsonpy, notably that the TeslaCar._car dict is never updated after init (which means properties like .state is never updated), and _vehicle_state can be overwritten with an empty dict when generate_car_objects is called multiple times for a given controller (which it seems might be happening).
I finally got a dev HA container running and pointing to my own fork of teslajsonpy so I can play around with this, but I'm hoping the changes I have in mind will fix this issue. If so I'll have a PR for review.

@carleeno TeslaCar._car is coming from the vehicle list endpoint. I thought we were updating that object every time the endpoint is called, but it looks like I may have missed that. We’re definitely pulling from the vehicle list endpoint constantly as this is how we’re determining if the vehicle is online or offline. If we’re grabbing the latest data here, makes sense to just update the Controller._vehicle_list dict.
As for generate_car_objects, that’s only being called when the integration starts. It’s being called from this integration, not within teslajsonpy, so it should only be occurring once on HA start or if you reload the integration. If you’re restarting HA, we’re starting teslajsonpy from scratch so there is no vehicle data yet so it shouldn’t be an issue. However, if you reload the integration (so teslajsonpy hasn’t been “restarted”), then I suppose it would be an issue if the car is asleep. This area definitely needs to be reworked. I think one solution was to use some existing HA functionality that allows you to persist data between restarts.
Unfortunately I haven’t had time to really work on any updates since this was released so there’s definitely a lot of changes/updates that are needed.

@shred86 thanks yep I realized that it's only being called once after some debug logging.
I'm making some progress however, I've fixed the rear seat heater availability by updating the dicts in vehicle_list whenever we call the list api, and pointing all references to vehicle_config to self._car.get instead of self._vehicle_data.get since that information persists even when the car is offline.
As for sentry mode, steering wheel, and homelink, those are using values that only exist in _vehicle_data, so I'm looking at using option codes instead for entity creation.
There's another option I'm looking at: in v2 when I added homelink, we always created the homelink entity, but updated the entities available() method dynamically. If we do something like this for these new entities, they would be added and hidden upon first install or reboot if the car is asleep, but if they ever become available later, they'll show up magically without having to reload the integration.

Option codes would be ideal but they are not reliable, according to this Tesla JSON API site. I compared it with my option codes and I found some references to Model 3 related codes when I have a Model S. I’m not sure why Tesla would keep this in their API if it’s bogus data but I haven’t had a chance to look into it further.


Don't set accordion content width to screen width

Describe the bug
Add GFAccordion as a child of SimpleDialog, when it's collapsed, its width is the default SimpleDialog width. When accordion expanded, the width is much larger to reach the insetPadding of dialog.
Expected behavior
The expanded width should be the same as collapsed.
Screenshots
Collapsed

Expanded

Expanded: after deleting width: MediaQuery.of(context).size.width
https://github.com/ionicfirebaseapp/getwidget/blob/9bceb782716bb5926d5dd488de1cdaca7af3ae61/lib/components/accordian/gf_accordian.dart#L160

Desktop (please complete the following information):

OS: macOS
Version 10.15

Additional
the file name and folder name should be accordion rather accordian?

The content's width is added in this commit: https://github.com/ionicfirebaseapp/getwidget/pull/68/commits/72a2cabe11d9f6b1431f99d32b877cf994c11a15
@shravyackm could you please explain about the effect of width here? is there any bugs related to it or any parent need to resolve children's size?

If no one want to explain or fix this problem, I want to close it to stop tracking.

The project seems to be inactive.


Fixed #32471 -- Doc'd the return value of EmailMessage.send().

https://code.djangoproject.com/ticket/32471

@hramezani Thanks :+1: CI failure is unrelated, see #14035.


rename driver.py to app.py

rename backend/driver.py file to app.py for consistent structure/readability between our backend services

In the process the dockerfile and the npm run startb comments show also change

@alantao912 are you working on this task currently or it's done?


Add realtime inference consumer

Realtime Consumers are consumers for the results from the invocation of a model from the realtime analysis pipeline (see model-builder, model-invocation-endpointand ksqldb). The results from the pipeline are in JSON and the invocation is called by a KSQL function which gets inference results then puts the results in a kafka topic. These consumers are meant to consume data from this topic.
3 terms used -

Action: Any task to be performed is an action. This can be sending a notification or an email
or just logging something.
Condition: This is a predicate that will be evaluated on the incoming data. For instance, this
can be used to evaluate if the ML model run crossed a threshold of some sort.
RealtimeInferenceConsumer: This is the base consumer for realtime results topics. Each consumer
can be configured with a set of Conditions and Actions. If all the conditions evaluate to be
true, then all the actions are triggered.

Currently, only one Condition is provided which evaluates a JSONPath expression. This should be sufficient for most simple use cases.
More complex use cases can create concrete implementations of the Condition
interface or ConditionBase abstract class. Currently, the JsonPath expression is read from the
configuration file and hence is static for a particular consumer and topic. Later, we can also
provide this through AppConfig so it can be dynamic based on userId or projectId.
The supported config (for instance an intervention using aRMT app) is of the format -
realtime-consumers:
  - name: 'lstm-lung-study-consumer' # Name of the consumer
    topic: 'lung_study_lstm_ad_inference' # Kafka topic to consume from (this should contain the inference results)
    notify_errors:
      email_addresses:
        -<EMAIL_ADDRESS>    conditions:
      - name: 'LocalJsonPathCondition' # Name of the condition
        projects: [ 'radar-test' ]  # Only evaluate for these projects
        subjects: [ 'sub-1', 'sub-2' ]  # Only evaluate for these subjects
        properties:
          jsonpath<EMAIL_ADDRESS>== true)]' # JsonPath expression to evaluate
          key: 'invocation_result' # Key that contains data to evaluate
    actions:
      - name: 'ActiveAppNotificationAction' # Name of the action
        projects: [ 'radar-test' ] # Only execute for these projects
        subjects: [ 'sub-1', 'sub-2' ]  # Only execute for these subjects
        properties:
          questionnaire_name: 'ers' # Name of the questionnaire to trigger
          time_of_day: '09:00:00' # Local user time of day to trigger at
          default_timezone: 'Europe/London' # Default timezone to use for the time of day if not found in the appserver
          appserver_base_url: 'http://localhost:8080/' # Base URL of the appserver
          management_portal_token_url: 'http://localhost/managementportal/api/oauth/token' # URL to get the management portal token
          client_id: 'realtime_consumer' # Client ID for the management portal
          client_secret: 'secret' # Client secret for the management portal
          metadata_key: 'invocation_result' # Key that contains the metdata to be forwarded to the aRMT app
      - name: 'EmailUserAction'
        projects: [ 'radar-test' ]
        subjects: [ 'sub-1', 'sub-2' ]
        properties:
          email_addresses: [<EMAIL_ADDRESS>]

Note: The properties section is specific to each Action and Condition. Please take a look at the
condition and action docs for the keys supported. If the projects or subjects key is not
specified the action and condition will be used on all projects or subjects respectively.

@mpgxvii, is it possible for you to review this when you have some free bandwidth? I think you plan to use this in the near future, so might be good to review and familiarise, unless you plan to use something else?


Sdk implement system

Please add a system so that we can add sdk in our android godot game. This feature is very much important for Android game developer. Because are are too many google service that can be implement via there sdk. Please 🥺🙏 🥺🥺 add this system.

I'm sorry but it's not clear to me what exactly you'd like to see in Goost, especially when I'm not familiar with Android development. In any case, I think that's not something which is in alignment with neither Godot nor Goost development due to open-source philosophy, and there may be other legal reasons.
Unfortunately, we're currently in the state of war with Russia, so I may be slow to respond (writing from a bomb shelter at the moment).

🥺🥺🥺🥺


Add a note explaining the choice to not use PR approach for GitOps scenario

Users may get confused while performing changes using ArgoCD UI instead of sending PRs (GitOps recommended approach).

We have recently changed the way developers modify the application configuration via the ArgoCD directly due to the performance issue even if this might not be better DevEx. To reduce the provisioning time and increase performance, we clone the original repository to integrate with the ArgoCD (ApplicationSet) rather than referring to each user's Gitea repo. That's why the PR based on individual Gitea repo doesn't impact to the application deployment in the ArgoCD.
This is a known issue around DevEX vs. Provision performance. I will trace this to find a better solution in the future release.


Consistent naming scheme across attacks

WIP

I think it would make sense to discuss this change on the cleverhans-dev mailing list first because it would be a major API change

(just to be clear, I think coming up with an unified terminology for the different attack parameters is a good idea and would be beneficial to the community if done based on a consensus)

I think the result of the discussion on the mailing list was that we're OK with it, right @npapernot ?
However, the PEP8 tests are currently failing, because some lines are too long now.

Yes there were no objections on the mailing list so we are good to proceed with the change

@aidangomez any updates?

@npapernot sorry, super preoccupied with work at the moment. Will return to this shortly.

Ping @aidangomez ?

Okay so since the diffs are unreadable here is what has been changed:

nb_iters -> step_count
eps_iter -> step_size
epsilon -> eps (or eps_iter depending on the intended use)
2 space indent following the Tensorflow style guide

Thanks for making the changes @aidangomez
I talked about this offline w/ @goodfeli. We'd rather avoid merging such a large PR right before ICLR so we'll hold on this for another 2 weeks.
It would also be cleaner for the history to make two different PRs: one that changes to 2 space indents and one that changes the names. Would you be able to work on that after ICLR or should I take care of it?

@npapernot Hmm so I was thinking about this and maybe we should create a decorator that warns when someone is using an deprecated name?

SGTM, will check in after ICLR

Let's close this PR for now. After the ICLR deadline passes, let's do one mega-PR that changes all the whitespace. After that, let's redo the other changes proposed here.


Avoid lock on read (issue: https://issues.apache.org/jira/browse/CXF-6825)

This is seems to be a bottle neck in our performance tests

You HAVE to have the lock on the get as well as the put.   During the put, the entire map is allowed to be restructured internally (buckets recalculated, etc... if the map grows) which would make anything going on in the get invalid.

So what do you suggest to do?
Maybe we should use some other data structure (one of the concurrent ones)?

What do you mean by invalid?
I understand that it can return null because it didn't find the thread in the map
but do you think it is really possible for it to return something else?
(in the case of null my code is treating it well)

I am closing this, will open other one when fix is ready


Lookup search api URL dynamically

Rather than hardcode the name and namespace of the search-api service
this commit searches for it using its well-known search labels.  As is
currently the case, if a user provides an override on the Inventory CR
then we use that rather than searching for it.

/lgtm


Comments are hard to read

Hello,
I'm using both nord for XResources and vim, and to me, it looks very hard to read especially when I'm not directly aligned to the screen. For example, looking at the top of my screen.
I wonder if I have a color that is wrong or if it's really designed like this:

You can customize the contrast of the comment color via the comment contrast theme configuration.

Hello,
I didn't know there was options for the theme. Thanks and sorry to didn't see it earlier :)


Feat: generic file system kv store

Thanks!

May I ask what the purpose of this store is?  I tried using it with MultiVectorRetriever it is in incompatiable because it is declared as BaseStore<string, Uint8Array> and MultiVectorRetriever requires  BaseStore<string, Document>

There is a wrapper class called EncoderBackedStore to make this usable there - we need docs on it though CC @bracesproul

Thanks.  So looking at that class, looks like I would want to do something like:
const docstore = createDocumentStoreFromByteStore(new LocalFileStore({rootPath: localFileStoreDirectory}))

const retriever = new MultiVectorRetriever({
        vectorstore: vectorStore,
        docstore,
        idKey,
});

Correct?

Yes that looks correct!


(hitbtc) order amount should be evenly divisible

Selling 59.3 SWT to hitbtc for 0.00029004 BTC
Exception in thread Thread-3:
Traceback (most recent call last):
  File "C:\Python27\lib\threading.py", line 801, in __bootstrap_inner
    self.run()
  File "C:\Python27\lib\threading.py", line 754, in run
    self.__target(*self.__args, **self.__kwargs)
  File "C:\Users\Kenneth\eclipse-workspace\Chank\trade-daemon.py", line 105, in sell_xfer
    print destexch.create_limit_sell_order(market, xfer_target_balance, maxprice)
  File "C:\Python27\lib\site-packages\ccxt\exchange.py", line 945, in create_limit_sell_order
    return self.create_order(symbol, 'limit', 'sell', *args)
  File "C:\Python27\lib\site-packages\ccxt\exchanges.py", line 11788, in create_order
    raise ExchangeError(self.id + ' order amount should be evenly divisible by lot unit size of ' + str(market['lot']))
ExchangeError: hitbtc order amount should be evenly divisible by lot unit size of 1.0

I know what this error means, and I know how it fix it, but my question is... how can I tell which precision level HitBTC prefers for each coin? Is that information available anywhere in ccxt, or will I need to construct a database table for tracking these requirements of each exchange?
Thanks so much!

Hi!

Is that information available anywhere in ccxt,

Yep ;)

how can I tell which precision level HitBTC prefers for each coin?

You can tell that from the lot property of each particular market:
print(hitbtc.markets['BTC/USD']['lot'])  # ?

You're my hero, @kroitor
Thanks so much! That's absolutely perfect for my needs.

@PhinixPhire you're welcome! )


Text doesn't get properly created displayed

At times text doesn't get properly displayed. It simply shows a black rectangle then. This seems to happen if a few texts have been created then it seems to fail to create another one.
The error is likely in the text creation process but this is not guaranteed.

It is fixed. There was data used from a free'd struct instead of its decendence's struct's.


Assignment 2: Team with Oskar Kalm

Hi Faris, I see that you have posted some changes. Please make sure that in the root of your folder there is a file called about.html that is the only page that my website is going to look for in your folder. If it cannot find it, it won't work
it needs to be like this:

The same applies to Oskar.
Please let me know if you have further questions

Hello Nico,
Thanks for letting me know. Did you receive my updated pull request with
the correct root folder?
On Wed, Nov 15, 2023 at 14:15 cimslab @.***> wrote:

Hi Faris, I see that you have posted some changes. Please make sure that
in the root of your folder there is a file called about.html that is the
only page that my website is going to look for in your folder. If it cannot
find it, it won't work
it needs to be like this:
[image: image]
https://user-images.githubusercontent.com/44410076/283223624-15b967f2-5a03-4ed0-a526-e4b988ece49d.png
The same applies to Oskar.
Please let me know if you have further questions
—
Reply to this email directly, view it on GitHub
https://github.com/nicoarellano/reposarch/pull/158#issuecomment-1813114677,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCNTZZWZT2ZX6DPCFTQ6FL3YEUIGTAVCNFSM6AAAAAA7M7AYY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJTGEYTINRXG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Faris, you need to be very careful about the file naming. Your html is looking for a file called main.js

and your folder only has a Main.js (notice the capital M). For coding, M and m are totally different characters, so your html will never find it.

Please revise.

Professor Nico,
Oh man, sorry for the back and forth. I think this should be better.
Please let me know…
On Wed, Nov 15, 2023 at 14:46 cimslab @.***> wrote:

Faris, you need to be very careful about the file naming. Your html is
looking for a file called main.js
[image: image]
https://user-images.githubusercontent.com/44410076/283229959-95d3468c-b879-4f41-bd70-2c0b87aa5cde.png
and your folder only has a Main.js (notice the capital M). For coding, M
and m are totally different characters, so your html will never find it.
[image: image]
https://user-images.githubusercontent.com/44410076/283230273-aa7a9849-501b-4f85-b612-966553f6eb73.png
Please revise.
—
Reply to this email directly, view it on GitHub
https://github.com/nicoarellano/reposarch/pull/158#issuecomment-1813161209,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCNTZZUAWIURM7VHJ5B76XLYEULYRAVCNFSM6AAAAAA7M7AYY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJTGE3DCMRQHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

This is just a comment, I have not received your updated code. Make sure you commit, push and create a pull request

😬 thanks for letting me know.
Maybe now?
On Wed, Nov 15, 2023 at 15:16 Nico Arellano @.***>
wrote:

This is just a comment, I have not received your updated code. Make sure
you commit, push and create a pull request
—
Reply to this email directly, view it on GitHub
https://github.com/nicoarellano/reposarch/pull/158#issuecomment-1813198644,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCNTZZWTG4DBP5KTYGOJAYLYEUPJDAVCNFSM6AAAAAA7M7AYY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJTGE4TQNRUGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


build slim, GPU-less docker image

build a cpu-only docker image which is significantly smaller than the gpu image
ollama          cuda              dfdbcb88bc3d   4 minutes ago   754MB
ollama          slim              fb2e67c26718   7 minutes ago   148MB

Related #516

Is this going to be merged? Would be super useful!

Will close this given the current one includes Linux, ROCm, etc.
However, I do think docker-related examples would be helpful:

docker-compose
A slim cpu-only dockerfile
How to pre-bake a model in an image (this is a very popular request)


Check output throw angular parse exception

Hello,
When a sensu client do a check which return a JSON object with URL encoded data in output field, the browser freeze and this JS error is thrown:

@caparisi Could you let us know which version of Uchiwa you are running?

Uchiwa : 0.4.0
Sensu : 0.16.0

@caparisi Could you provide me an example of a JSON object that cause this particular issue? Thanks!

Of course :
{"request":[{"url":"http://test.com","name":"Nom de ma requete comme 'Test de l'injecteur'","user":"user","password":"password","input":"inputTest.xml","input_encoded":"%3C%3Fxml+version%3D%221.0%22+encoding%3D%22ISO-8859-1%22%3F%3E%0A%3Cy%3Ainput+xmlns%3Ay%3D%22http%3A%2F%2Fwww.yseop.com%2Fengine%2F3%22+xmlns%3Ai18n%3D%22http%3A%2F%2Fapache.org%2Fcocoon%2Fi18n%2F2.1%22+xmlns%3Aft%3D%22http%3A%2F%2Fapache.org%2Fcocoon%2Fforms%2F1.0%23template%22+xmlns%3Afi%3D%22http%3A%2F%2Fapache.org%2Fcocoon%2Fforms%2F1.0%23instance%22+xmlns%3Afd%3D%22http%3A%2F%2Fapache.org%2Fcocoon%2Fforms%2F1.0%23definition%22+xmlns%3Afb%3D%22http%3A%2F%2Fapache.org%2Fcocoon%2Fforms%2F1.0%23binding%22+%3E%0A++%3C%2Fy%3Ainput%3E%0A","keyword":"mot clé a rechercher dans la page","http_code":"code http attendu"}],"Message":"Mon Message de sortie"}
When sensu client send it, I can see on my browser console :

Hi @caparisi
This issue was probably fixed with the upgrade to AngularJS 1.3 we made, I'm now able to show the input_encoded property without any issue:

You'll need to upgrade to at least Uchiwa 0.6.0. Let me know if you still have any issue!
Thanks


Release note link is 404

No the end of the world, but if you select to display the release notes in 60b4, the link is 404.
It points to https://github.com/Ranchero-Software/NetNewsWire/releases/tag/mac-6.0b4 instead of https://github.com/Ranchero-Software/NetNewsWire/releases/tag/mac-6.0beta4
Ultimately, it shouldn’t be much of an issue in the final release which shouldn’t have the beta tag in the link, but it might reflect an issue with the way the link is coded in the release note command int he app so I thought I should report it here…

Thanks for the heads up. It looks like we got this right in the final release, so I'm closing this issue.


Save Shibboleth Error Logs

Save error logs in /var/log/shibboleth

created volumes for both shibboleth and apache error logs


Add Evo. Models for brown dwarfs

Add a way to combine the evo models as done in the original SEDkit where we have the cubic spline between the bd and star boundary.

Closing this as @SherelynA added MC routine for better evo model uncertainties in #83 .


Can not protect update by field level permission ?

Which Category is your question related to?
API
Amplify CLI Version
4.27.3
What AWS Services are you utilizing?
AppSync
Provide additional details e.g. code snippets
I set up a field-level permission setting (exclude update) in GraphQL's schema,
and I was able to update the value of the update request from the AppSync console page query.
Could you please let me know if there is a workaround?
Below are the schema settings and the mutation at update time.
type Task
  @model
  @auth(rules: [
    { allow: owner, operations: [create, read, update, delete] }
    { allow: private, provider: iam, operations: [read, update] }
  ])
{
  id: ID!
  owner: String!
  expiredAt: AWSDateTime
    @auth(rules: [
      { allow: owner, operations: [create, read, delete] }
      { allow: private, provider: iam, operations: [read, update] }
    ])
}

Muataion:
mutation MyMutation {
  updateTask(input: {_version: 10, id: "8b166100-b33b-48af-831d-08fb1774583e", expiredAt: "2020-12-31T00:00:00.000Z"}) {
    id
    expiredAt
  }
}

Query:
query MyQuery {
  getTask(id: "8b166100-b33b-48af-831d-08fb1774583e") {
    id
    _version
    expiredAt
  }
}
{
  "data": {
    "getTask": {
      "id": "8b166100-b33b-48af-831d-08fb1774583e",
      "_version": 11,
      "expiredAt": "2020-12-31T00:00:00.000Z"
    }
  }
}

Here's the doc of the private level auth, were you able to update the field even without logging in as an user?

@UnleashedMind

were you able to update the field even without logging in as an user?

No login user could not update the field.
I checked update pattern below:

Owner user

result: can update
expect: can not update

No owner user(logined)

result: can not update (expected)

No login user

result: can not update (expected)

IAM

result: can update (expected)

Response:
Owner User(Cognito)
{
  "data": {
    "getTask": {
      "expiredAt": "2020-01-01T00:00:00.000Z",
      "id": "8b166100-b33b-48af-831d-08fb1774583e",
      "_version": 12
    }
  }
}

No owner user(Cognito)
{
  "data": {
    "updateTask": null
  },
  "errors": [
    {
      "path": [
        "updateTask"
      ],
      "data": null,
      "errorType": "ConditionalCheckFailedException",
      "errorInfo": null,
      "locations": [
        {
          "line": 2,
          "column": 3,
          "sourceName": null
        }
      ],
      "message": "The conditional request failed (Service: DynamoDb, Status Code: 400, Request ID: MPVSNNNDUI32Q6287FGIB6VH4FVV4KQNSO5AEMVJF66Q9ASUADJG, Extended Request ID: null)"
    }
  ]
}

No login User
{
  "errors": [
    {
      "errorType": "UnauthorizedException",
      "message": "Valid authorization header not provided."
    }
  ]
}

IAM
{
  "data": {
    "getTask": {
      "expiredAt": "2020-02-01T00:00:00.000Z",
      "id": "8b166100-b33b-48af-831d-08fb1774583e",
      "_version": 13
    }
  }
}


504 for no reason for css files only

I'm testing locally and the server get 504 for a lot of my css files when my server log shows 200
prerender service log
2015-10-14T07:17:22.336Z got 504 in 340ms for static/bower_components/bootstrap/dist/css/bootstrap.css

my server log
::1 - - [14/Oct/2015:07:17:20 +0000] "GET /static/bower_components/bootstrap/dist/css/bootstrap.css HTTP/1.1" 200 141414 "http://localhost:8000/" "Mozilla/5.0 (Macintosh; Intel Mac OS X) AppleWebKit/534.34 (KHTML, like Gecko) PhantomJS/1.9.8 Safari/534.34 Prerender (+https://github.com/prerender/prerender)"

The result is the pre-rendered page looks very ugly because phantom cannot get the css files.

Sorry. It's my browser try to ask for the css again.

@sunshineo could you explain this a little more? I'm having the same issue currently but can't quite figure out how to solve.

css files or any other non-html files shouldn't be sent to the prerender server. If you are testing directly against your prerender server like:
http://prerenderserver.com/http://www.example.com
Then any relative links from www.example.com will be sent to the prerender server since that's the domain on the request. This is expected and not a problem to see 504s in this case.
Once you proxy the request through your middleware, the relative URLs from the static HTML will be returned from your server so you won't see this issue since the css and other static files will be requested from your domain. If you are seeing css files requested from the prerender server after accessing the page through the middleware, then your middleware might not be set up correctly.

@thoop said it much better than I could.

It looks like I'm having a similar problem in #365, where I get a 404 for failing to load a CSS asset. Any hints in the right direction would be much appreciated!

I have the same issue and it makes sense.
But how do you proxy the request through the middleware? I have
app.use(require('prerender-node').set('prerenderServiceUrl', 'http://localhost:3000'));
and request
http://localhost:3000/http://localhost:9000/
and I get that error.

You would request your website like:
http://localhost:9000/?_escaped_fragment_=
And if the middleware is working correctly, that should return a prerendered page.

Right on, so that's what you mean with proxying through the middleware. Maybe it's because I am not a native english-speaker, but I think that is not very clear in the documentation.
Anyway, that worked like a charm - thanks a lot!

Sorry! We'll try to make that clearer :)


change the way we provide additional params via environment and config file

This PR moves away from relying on picocli default provider and programmatically reconstructs the command line arguments with the additional params from environment and config file.
The basic idea is:

get all the options available for the current commandLine (or subcommand)
exclude the options that has been already specified as argument
search for matching params in environment\configFile
rebuild the CLI arguments by appending matched params to the original params

fixes #5878
Documentation

[x] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[x] I thought about adding a changelog entry, and added one if I deemed necessary.

@ajsutton I managed the situation where multiple config\env referring to the same param are specified.
ie TEKU_ETH1-ENDPOINT and TEKU_ETH1-ENDPOINTS
Currently I explicitly stop and throw an exception instead of trying to resolve the conflict.
It makes me think that this could be a breaking change because in our previous version we were giving the precedence based on the ordering of names in the @Option definition.
To print a warning instead and replicate exactly the previous behaviour I should stream starting from Option names... should be doable...

hmm, that is an interesting one.  It's probably not a particularly big deal if we can't support both being set but if we can keep it working that would definitely be better.

done.
Now it should be OK.
The only edge case I can reason about is:
giving an option like this:
  @Option(
      names = {"-n", "--name", "--names"},
      split = ",")
  List<String> getNames();

and this env vars
TEKU_N=a
TEKU_NAME=b
TEKU_NAMES=c

previous behaviour: name will be b
new behaviour: name will be a
(because now we consider single-dash options too)

(because now we consider single-dash options too)

oh darn, I think I've given you bad advice here. I think we deliberately ignored single - options in the past because we had problems where teku wouldn't start because someone had an env var set called TEKU_V or TEKU_H and it triggered the version or help output.  It could potentially have been avoided by only considering options that accept a value (even if it's optional) but I'm not sure which way we went now.

The extractAPISpec failure is interesting too:
Invalid value for option '--logging': 'en_US.UTF-8' is not a valid log level. Supported values are [OFF|FATAL|WARN|INFO|DEBUG|TRACE|ALL]

Did we pick up an env var we didn't previously?

  @Option(
      names = {"-l", "--logging"}

better to filter out again single dashed options...

I reintroduced the startsWith("--") requirement on the names
A quick assessment:

plus -h and -V
Now this version should behave exactly as the current one.


TypeError: get_item_eligibility_preview() takes 1 positional argument but 4 were given

Type error when trying to run get_item_eligibility_preview(), I think there might be a problem on line 21 with how the return is defined (maybe adding self.) but I'm not sure please let me know if the problem is on my end, thank you.
To Reproduce
marketplace_id = ['ATVPDKIKX0DER']
eleg = FbaInboundEligibility(credentials=credentials).get_item_eligibility_preview(marketplace_id,"asin","INBOUND")
print(eleg)
API Response was expected

OS: [Windows]

Error Message
TypeError                                 Traceback (most recent call last)
 in
1 marketplace_id = ['ATVPDKIKX0DER']
----> 2 eleg = FbaInboundEligibility(credentials=credentials).get_item_eligibility_preview(marketplace_id,"asin","INBOUND")
3 print(eleg)
~\anaconda3\lib\site-packages\sp_api\base\helpers.py in wrapper(*args, **kwargs)
19                 'method': method
20             })
---> 21             return function(*args, **kwargs)
22         wrapper.doc = function.doc
23         return wrapper
TypeError: get_item_eligibility_preview() takes 1 positional argument but 4 were given

You're passing arguments to a function that doesn't take args but kwargs. Please have a look at the documentation.


Discussion: Do we want to introduce any form of QA (Quality Assurance) before an alpha release?

Background
@RISC-OS-Community/code-reviews-team
Given that DME is something we are creating for end-users of all level of experience on RISC OS, do we think it may be beneficial to introduce a "layer" of formal testing within the RISC OS Community before we release the code for a broader audience to test and report?
Definition of Done

[x] Idea proposed
[ ] Idea being discussed
[ ] We have reached a conclusion

I think development and testing should all be in the open, so I would prefer a pre-release testing scheme in that case. Releases on Github can be tagged as pre-release, and such a build could be given to the community with a request for input in that context.

Good point, pre-releases sound like a good way to ask the community for feedback and bug reports, until we believe it's "good enough" to tag an official release.


Tutorial: Cloud shell Train + Predict Pipeline

Description
Please provide a description of the changes you have made in this PR.
How has this been tested?
Please explain how you have tested the new changes.
Checklist

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have successfully run the E2E tests, and have included the links to the pipeline runs below
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have updated any relevant documentation to reflect my changes
[ ] I have assigned a reviewer and messaged them

Pipeline run links:

It's looking really good! My main suggestion is this: it feels like we need a clear narrative to tie everything together. For example, the sections where we are discussing details that the user will not need to change, then explain that these are just educational points. Suggest even renaming the non-interactive portion's titles with something signifying this.
Once the non-interactive parts are done, some blurb about "now we're going to take an example and productionise it" would help - i.e. taking the audience along with your thinking. Not major suggestions, but I really feel like it'd tie everything together.

clearer workflow for audience to follow
make it clearer up front what the intended audience is (are we merely understanding how the template works? Are we taking an existing model into production? Are we productionising a toy example?)
Differentiate between sections which are for interest, sections which are calls to action

It's looking really good! My main suggestion is this: it feels like we need a clear narrative to tie everything together. For example, the sections where we are discussing details that the user will not need to change, then explain that these are just educational points. Suggest even renaming the non-interactive portion's titles with something signifying this.
Once the non-interactive parts are done, some blurb about "now we're going to take an example and productionise it" would help - i.e. taking the audience along with your thinking. Not major suggestions, but I really feel like it'd tie everything together.

clearer workflow for audience to follow
make it clearer up front what the intended audience is (are we merely understanding how the template works? Are we taking an existing model into production? Are we productionising a toy example?)
Differentiate between sections which are for interest, sections which are calls to action

@jgammon-dt Thanks for the review, updated the workflow with connectors & differentiation between sections for understanding & call to action

It's looking really good! My main suggestion is this: it feels like we need a clear narrative to tie everything together. For example, the sections where we are discussing details that the user will not need to change, then explain that these are just educational points. Suggest even renaming the non-interactive portion's titles with something signifying this.
Once the non-interactive parts are done, some blurb about "now we're going to take an example and productionise it" would help - i.e. taking the audience along with your thinking. Not major suggestions, but I really feel like it'd tie everything together.

clearer workflow for audience to follow
make it clearer up front what the intended audience is (are we merely understanding how the template works? Are we taking an existing model into production? Are we productionising a toy example?)
Differentiate between sections which are for interest, sections which are calls to action

@jgammon-dt Thanks for the review, updated the workflow with connectors & differentiation between sections for understanding & call to action

@felix-datatonic

Looking good to me! Found it easier to follow the intent (:


Weird intermittent hangs in tower after updating to 0.69

Current and expected behavior
So this isn't going to be the best error report because the problem seems to be intermittent. But I'm going to make it anyway because maybe someone else might be having the same problem.
I was on kube 0.64, everything was working fine, but when I upgraded to 0.69 I noticed that sometimes my k8s resources weren't being created. I enabled all debug logs are it seems to get stuck on. tower::buffer::worker service.ready=true processing request. I didn't have this issue locally. And its intermittent.
Since then I have downgraded back to 0.64 and everything seems to be working fine.
Sorry that I couldn't be more helpful here. Maybe I should make this in the tower repo. Maybe this is only present after the tower-http 0.2 upgrade. When I have more time I will try a few different things to see if I can narrow it down.
Was curious if anyone else using kube-rs has seen a similar issue.
Possible solution
No response
Additional context
No response
Environment

gke cluster (1.20.12-gke.1500)
debian:bullseye-slim

Configuration and features
No response
Affected crates
kube-client
Would you like to work on fixing this bug?
no

Hm, odd.

Can you confirm that the bug is new in 0.69, and does not happen with 0.68?
Would you mind running cargo update on the latest build of your app that does work fine for you (whether that ends up using kube-rs 0.64, 0.68, or something in between), and confirm that that still works?
Would you mind posting the diff between the Cargo.locks of the newest working and oldest broken versions?

I can reproduce it in controller-rs repo in main now: tilt up against k3d
after about a minute the controller stops handling messages and it prints a bunch of tower and hyper messages:
foo-controll… │ {"timestamp":"2022-02-16T16:54:52.700113Z","level":"TRACE","fields":{"message":"worker polling for next message"},"target":"tower::buffer::worker"}

foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384825Z","level":"TRACE","fields":{"message":"decode; state=Chunked(Size, 0)"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384847Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384875Z","level":"TRACE","fields":{"message":"received 905 bytes"},"target":"hyper::proto::h1::io"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384883Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384888Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384893Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384897Z","level":"TRACE","fields":{"message":"Chunk size is 898"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384904Z","level":"DEBUG","fields":{"message":"incoming chunked header: 0x382 (898 bytes)"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384910Z","level":"TRACE","fields":{"message":"Chunked read, remaining=898"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384925Z","level":"TRACE","fields":{"message":"flushed({role=client}): State { reading: Body(Chunked(BodyCr, 0)), writing: KeepAlive, keep_alive: Busy }"},"target":"hyper::proto::h1::conn"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384940Z","level":"TRACE","fields":{"message":"flushed({role=client}): State { reading: Body(Chunked(BodyCr, 0)), writing: KeepAlive, keep_alive: Busy }"},"target":"hyper::proto::h1::conn"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384955Z","level":"TRACE","fields":{"message":"decode; state=Chunked(BodyCr, 0)"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384962Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:55.384974Z","level":"TRACE","fields":{"message":"flushed({role=client}): State { reading: Body(Chunked(Size, 0)), writing: KeepAlive, keep_alive: Busy }"},"target":"hyper::proto::h1::conn"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.112946Z","level":"TRACE","fields":{"message":"decode; state=Chunked(Size, 0)"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.112967Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.112992Z","level":"TRACE","fields":{"message":"received 903 bytes"},"target":"hyper::proto::h1::io"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.112999Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.113003Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.113006Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.113009Z","level":"TRACE","fields":{"message":"Chunk size is 896"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.113014Z","level":"DEBUG","fields":{"message":"incoming chunked header: 0x380 (896 bytes)"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.113018Z","level":"TRACE","fields":{"message":"Chunked read, remaining=896"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.113030Z","level":"TRACE","fields":{"message":"flushed({role=client}): State { reading: Body(Chunked(BodyCr, 0)), writing: KeepAlive, keep_alive: Busy }"},"target":"hyper::proto::h1::conn"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.113066Z","level":"TRACE","fields":{"message":"decode; state=Chunked(BodyCr, 0)"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.113074Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.113084Z","level":"TRACE","fields":{"message":"flushed({role=client}): State { reading: Body(Chunked(Size, 0)), writing: KeepAlive, keep_alive: Busy }"},"target":"hyper::proto::h1::conn"}
foo-controll… │ {"timestamp":"2022-02-16T16:54:56.113109Z","level":"TRACE","fields":{"message":"Non-error received, resetting backoff"},"target":"kube_runtime::utils::stream_backoff"}
foo-controll… │ {"timestamp":"2022-02-16T16:55:03.040278Z","level":"TRACE","fields":{"message":"decode; state=Chunked(Size, 0)"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:55:03.040343Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:55:03.040448Z","level":"TRACE","fields":{"message":"received 118 bytes"},"target":"hyper::proto::h1::io"}
foo-controll… │ {"timestamp":"2022-02-16T16:55:03.040473Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:55:03.040487Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:55:03.040502Z","level":"TRACE","fields":{"message":"Chunk size is 112"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:55:03.040516Z","level":"DEBUG","fields":{"message":"incoming chunked header: 0x70 (112 bytes)"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:55:03.040542Z","level":"TRACE","fields":{"message":"Chunked read, remaining=112"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:55:03.040581Z","level":"TRACE","fields":{"message":"flushed({role=client}): State { reading: Body(Chunked(BodyCr, 0)), writing: KeepAlive, keep_alive: Busy }"},"target":"hyper::proto::h1::conn"}
foo-controll… │ {"timestamp":"2022-02-16T16:55:03.040765Z","level":"TRACE","fields":{"message":"decode; state=Chunked(BodyCr, 0)"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:55:03.040804Z","level":"TRACE","fields":{"message":"Read chunk hex size"},"target":"hyper::proto::h1::decode"}
foo-controll… │ {"timestamp":"2022-02-16T16:55:03.040847Z","level":"TRACE","fields":{"message":"flushed({role=client}): State { reading: Body(Chunked(Size, 0)), writing: KeepAlive, keep_alive: Busy }"},"target":"hyper::proto::h1::conn"}

That would make sense with the minute delay too, actually...
Does the reloading affect our public API? Do we want to release a 0.69.1 with it reverted for now?

It's an entirely private change - let's spend a little bit of time to see if we can spot the cause in the PR before releasing a fix. It's simple to repro, and the PR is small.

If I had to guess I would think its blocking here:
                if let Some(token) = token_file.read().await.cached_token() {
                     bearer_header(token)
                 } else {
                     bearer_header(token_file.write().await.token())
                 }

think i got it. swapping the rwlock for a mutex and taking the lock outside that branch start seems to stop it from happening

Thanks, you guys are awesome from issue report to fix in within an hour. Appreciate it. Using kube-rs has been awesome 😊

0.69.1 is now released, and contains the fix!

0.69.1 confirmed working in cluster. Thanks!

Sorry for this :( Thanks for getting the fix released quickly @clux @teozkr.
I thought I had tested it, but maybe that was only with the initial version that used Mutex. We can also remove cached_token() with Mutex.

What can we do to prevent this in the future? Always update and test controller-rs before release?

Yeah, it's not really practical to run all tests in-cluster (and even if we had run tests in-cluster before release, we would not have caught this because the unit test does not exercise the layer in parallel). It's also not to practical to always run controller-rs as it's our convenience + example rather than a CI enforced thing (it's a nice thing for us run for us when we do change in-cluster things regardless though) - and it's hard + overkill to make it a CI enforced thing.
E2E tests sit at the top of our testing pyramid to explicitly catch issues related to in-cluster changes. We have just one test in that category (awkwardly named dapp), and it's there just to make sure in-cluster auth works. I think we should work on the e2e suite so that we can test that the in-cluster auth works across reload points.
I don't really want to move too many tests in-cluster unless there are specific cases we cannot catch with lower level tests. E2E tests, while powerful, are also the most cumbersome to write, and debug when they break down as they suffers the most from CI interaction effects and slow execution times.
Stronger Controller testing is a separate issue I think we should also work on - albeit not related to this - as we currently are lacking coverage of this module even in the land of unit/integration tests. We should focus on that separately.


Adapt MeshView for working with CSCS Localizoom analysis tool

Need implementation:

V0.8 Meshview linked not Flash version
Remove download
are the buttons "load" and "save" relevant? if we keep them we should define where this is stored

Status 03.09.2021. Other priorities: WebAlign.

With webapp implementation this issue is not relevant anymore. Closing 30.11.2022


Improve CI pipeline speed

The CI pipeline currently takes ~5 minutes just to lint.
We should consider configuring the actions cache or, if necessary, building a docker image with everything ready to go.
@tbenthompson

Closed by https://github.com/Confirm-Solutions/imprint/pull/107


Could you provide the scripts to update weather data?

Thanks for the nice work. I wonder if you could update the NOAA weather data (currently till 11/14/2020) or provide the scripts to fetch them.

This was a temporary glitch, the data should be current now. The scripts are all open source, you can find them under the src/pipelines/weather/ folder.


[BEAM-1340,BEAM-1345] Tighten the Dataflow runner's API surface

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify.
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @tgroh
Nothing but moves, raising to top level, and annotations here. Still needs a worker dance, but an easy one.

Coverage increased (+0.01%) to 70.557% when pulling 7b857ebbaa3cbac70c78d3344d6b53bf95ef6e62 on kennknowles:DataflowRunner-surface into ad12f63162a4b03c61c815887dee24fb176065a9 on apache:master.

Coverage remained the same at 70.515% when pulling 6f31a7b884b39f0421f5880f18c827768e5a9574 on kennknowles:DataflowRunner-surface into 24c6ff44e88d5c42e6685a1db4d8ff4973a5baa5 on apache:master.

Coverage increased (+0.05%) to 70.511% when pulling 97447b30a8588da658aa6292b72c6f78a6aae403 on kennknowles:DataflowRunner-surface into 9fffa7efac634eebecf802626c6d7c88e3d60be5 on apache:master.

Gonna break this into things with long-term payoff that cannot be done later vs the whole shebang.


Update README.md

"extra":{
"installer-paths":{
"./monolog/": ["monolog/monolog"]
} <- this one was mising
}

Just like in master branch #23