C# api

C# is very popular and expressive language with a large community of pro developers.

Providing APIs for every 'very popular' lang would probably bloat the main project quite quickly.

I'd really like to see a C# wrapper. Shouldn't be too hard to p/invoke into the C++ API.

Perhaps CppSharp could be of use? As opposed to SWIG?

:+1:

This is something the core TensorFlow team is unlikely to tackle in the near future, so if you want to contribute it, please go ahead! I would recommend circulating a proposed implementation on the discuss mailing list early on, so that a consensus about where such API might live (in repo / off repo / in 'contrib' directory) can be reached ahead of time.

FYI, @zaphar has just contributed initial C# rules to Bazel. These rules are currently in an early state and currently only support Mono, but the plan is to add Microsoft .NET support once Bazel supports Windows. If anyone is interested in helping with improving Bazel's C# rules, contributions are definitely welcome. :)

Just a general +1 from me!
@davidzchen - I am not familiar with Bazel but assuming the that the idea behind you mentioning it being extended to run on Windows, along with the new C# rules, would be to allow us to build this repo on Windows, including the code for the potential .NET (mono) interop library?
Could an alternative approach be to just build and distribute the native tensorflow libs (dll's) on NuGet - and then in a completely seperate repo, create this.NET interop. This seperate repo can be built using MSBUILD or something so would eliminate Bazel as a blocker?

@dazinator Correct. I am not sure what the TensorFlow team has decided about where support for additional language should live (as @vincentvanhoucke mentioned, in the tensorflow repo, in separate repos, or in a contrib directory). In the meantime, I'm sure it would be fine for somebody to pick this up, circulate a proposal, and implement C# support built using msbuild. We can add BUILD files later for users who would want to use Bazel instead.
I just wanted to put that out there in case somebody is interested in helping out with Bazel's C# rules. :)

The problem is not to invoke C++ code, but to translate the Python part of TensorFlow to either C# or C++. It has about 60K lines of code. That's where TensorFlow "magic" resides on...
I'm currently working on porting TensorFlow to Node.js, and we got stuck on this. Maintaining a synced version of some thousand lines of code will get out of control as soon as something changes in the Master. The way I see it working, is to translate the Python part of TensorFlow to C++.
If you guys are willing to help, please join us at slack: https://github.com/node-tensorflow/node-tensorflow

@ivanseidel - I think one solution for the python code from a .NET perspective, would be to use IronPython - which will allows you to:

call your Python .py from within .NET
run it
get a result back into your .NET app from the Python code.

So i'd assume that for a C# implementation, we'd try and keep all the original python code as is (as much as possible) to save re-writing 60k lines (and keeping them in sync)
Saying that, this is a completely pie in the sky idea and I really haven't looked at any specifics yet! :)

@dazinator That is a way out, but then, you cannot "writte" code from within C# context, you will be limited to writting TensorFlow code in .py and calling it from other languages...
The Idea is to have all the tools available native in the language. Of course this is a working "work-around", but if you need a dynamic TF code, you will get somewhere limited by it =/
But, translating all those lines of codes from Python to C++, wouldn't need to be "in sync" anymore. Just the callers, but not the implementation code... It takes an effort, but a single effort, once, to make things the right way =)

@ivanseidel - I understand.
.NET also has good native interop, so porting this python code to C++ version could be good for both .NET and NodeJS - (especially if using something like node-ffi
My comment around the "sync" was really about - if google decide to continue to evolve their python code, we'd have to continue to keep the c++ code base in line with that.. It would essentially be having to maintain this as a fork - but I do understand the benefits :)

Yep, you are right...
As I see, keeping a fork for it is required, be it a Node.js fork for the Python code, or C#, or even Java. But if there is a fork for C++, all can use it in favor.. C++ is universal in this case, while no other language can support all others as much as C++...
In any case, if you feel engaged to it and would like to help, join us at slack  (link: https://tensor-flow-talk-invite.herokuapp.com/). And good luck with it :)

As I think we have mentioned elsewhere, there is a lot of code in python that we do hope to move into the core C implementation (shape inference, gradients, etc), so that the language bindings only have to be thin, idiomatic wrappers around the core functionality.  But as you know, it is quite a bit of work to do this, and we already have some 100+ open issues to prioritize against too, so please be patient with us.

@vrv , I'm not asking for you guys to priorityze this, but willing to help on this matter. It will save people time when It's ready, and make TF awesome in all other languages... I'm planning on using my vacations on this, but It's not a one-person job. Should I open an issue calling for help on that? I guess Java/C#/Node guys would be willing to help

Great to hear that you are willing to help!  We're not at a state where the work can easily be parallelized across multiple developers, but once we are, we'll definitely try to conscript the community to help.

@dazinator @ivanseidel - I don't understand why IronPython isn't a good idea. Even if all we can do is in / out the data from the c# / .net app - that is a huge step forward. What am i missing?

I don't think you are missing anything, my understanding is that on the one
hand we'd between writing our own surface layer / api with iron python that
sits on top of the tensor flow api's. Only yhat surface that we create will
be calllable from c#.
With the convert to c++ approach, we'd end up being able to use the
existing tensor flow api's in c# directly (via native interop)
On Fri, 4 Dec 2015 2:31 am Joe Booth<EMAIL_ADDRESS>wrote:

@dazinator https://github.com/dazinator @ivanseidel
https://github.com/ivanseidel - I don't understand why IronPython isn't
a good idea. Even if all we can do is in / out the data from the c# / .net
app - that is a huge step forward. What am i missing?
—
Reply to this email directly or view it on GitHub
https://github.com/tensorflow/tensorflow/issues/18#issuecomment-161853432
.

Has anyone actually tried to interpret the TensorFlow python using IronPython?I appreciate there's now a way to use numpy and scipy with IronPython - though I don't know how long ago this was last updated - but IronPython doesn't play nicely with CPython C extensions.

Anyone tried IronPython approach?

No. IronPython will struggle with any C extensions. Though I think there's a work around for numpy and scipy. Does IronPython work on Mono or CoreCLR? My understanding was that TensorFlow won't run on Windows.
On Fri, Jan 8, 2016 at 5:03 AM -0800, "Eugene"<EMAIL_ADDRESS>wrote:
Anyone tried IronPython approach?
—
Reply to this email directly or view it on GitHub.

what about efficiency in a distributed platform if you use Ironpython ?
somewhere in the doc it is mentioned that :
To do efficient numerical computing in Python, we typically use libraries like
NumPy that do expensive operations such as matrix multiplication outside Python,
using highly efficient code implemented in another language.
Unfortunately, there can still be a lot of overhead from switching back to
Python every operation. This overhead is especially bad if you want to run
computations on GPUs or in a distributed manner, where there can be a high cost
to transferring data.

Here is a port of the c api to csharp I just made, using SWIG, to keep the maintenance to a minimum.
https://github.com/unrealwill/tensorflow-csharp-c-api
Still a work in progress to make it more easy to install and use.
But example graph runs fine.

FYI: We recently added some documentation in the form of a  how-to around how TensorFlow intends to support other language bindings.

Some general porting advice / FYIs regarding C# -- (I've seen some clumsily ported libraries in the past, and they were super awkward to work with, I would hate to see something like that happen to a cool library like TensorFlow!)
C# and .NET have built-in support for a lot of the simple stuff (high speed math, SIMD instructions using the built-in vectors and matrices classes, etc.), so there's not as much of a need to shell out to another process to do regular math.
Also, it has built-in operator overloading (so no need for a "mul(x, y)"-like function, etc.  because you can just overload the multiplication operator).  [It also has actual properties, and you can overload the indexer operator, so no need to ever write "get" or "set" functions directly.]
Also there's already some patterns in C# for building a "graph" of operations and deferring their execution to be done later, or even on other hardware (i.e. LINQ can work this way with IEnumerable, but especially with IQueryable where an expression tree can be built and translated or passed on to another machine for execution, etc. -- also the CSOM pattern -- even though it's meant to solve a different problem -- might translate well here -- because the pattern let's you build up multiple queries and then execute them all at once).
If session has any resources that need to be cleaned up when it's done or if it needs to be "stopped" or something, consider making it IDisposable (then we can just wrap it in a using block, etc.)
It would be super cool to be able to build a TensorFlow statement in C# using LINQ and have it execute on the GPU.
[Nothing here is meant to be patronizing, just some tips from a C# power-user that I hope will be of use.]

Another thing I just stumbled on to -- if IronPython won't work, you could try Python for .NET (pythonnet):

https://github.com/pythonnet/pythonnet/.
http://pythonnet.github.io/readme.html
http://stackoverflow.com/a/7368156/398630

Note that this package does not implement Python as a first-class CLR language - it does not produce managed code (IL) from Python code. Rather, it is an integration of the CPython engine with the .NET or Mono runtime. This approach allows you to use use CLR services and continue to use existing Python code and C-API extensions while maintaining native execution speeds for Python code.

And

Python for .NET uses the PYTHONPATH (sys.path) to look for assemblies to load, in addition to the usual application base and the GAC. To ensure that you can implicitly import an assembly, put the directory containing the assembly in sys.path.

It looks like you still have to have Python installed for it to work, but maybe it could be a help where IronPython couldn't?

@asimshankar could you please update this HowTo [C] with the [C++ API]
Looking through the Java language binding using javacpp [1][All APIs implemented in java], I think cppSharp would also be an good alternative than the SWIG approach.

@JimSEOW : What sort of update are you suggesting? Our intention is to have the Java API implemented on top of the C API as mentioned in the doc using JNI.
I haven't looked into the details of javacpp/cppsharp, perhaps @jhseu has and might have some thoughts on the pros and cons of the two approaches.

Yeah, we suggest that you implement it on top of the C API because we'll have versioning stability there after the 1.0 release. It's also what the other language bindings will be using, including Java, which won't be built using javacpp.

@asimshankar @jhseu I understand that you plan to provide Java API using JNI. Do you have a path for .NET API?
Why abandon  [C++ API?] (https://www.tensorflow.org/versions/master/api_docs/cc/index.html) Users of Javacpp has already using the C++ API. It is a matter of time for cppSharp to catch up.
If there is no plan to further support the C++ API, please state clearly so we would need to find alternative solutions to tensorflow when translating and engineer data science solutions during production.

@JimSEOW

There is no intention to abandon the C++ API. The C++ API is fully supported and in fact is what TensorFlow Serving is built on. As a general rule, if it is documented on the TensorFlow website, it is supported :).
That said, the C API was designed with the intent of it being used to build other language bindings (see howto) and that is what other language bindings such as Go, Rust, Ruby and others are built on (most of which are built and maintained by the community, not the TensorFlow team). Specifically, the C API should be appropriate for use with FFI support that languages typically provide (e.g, JNI, cgo, LuaJITs FFI etc.).

I am perhaps not fully grasping your concern here. Are you looking for a recommendation as to whether (1) using something like P/Invoke to wrap over the C API, or (2) cppsharp over the C API, or (3) cppsharp over the C++ API or (4) SWIG over the C API is preferable?
I don't believe we have enough expertise in the .NET framework within the TensorFlow maintainers to make an informed recommendation, and we sincerely welcome any community contributions towards this. My gut instinct would say that it would be preferable to wrap over the small API surface of the C API using whatever FFI support is canonical in .NET and use that as a basis to provide an idiomatic C# library. As opposed to depending on other frameworks or "transliterating" everything in C++ API which may result in non-idiomatic APIs in the language. Though again, I say this without enough expertise in .NET or C# specifically.

(oops, didn't mean to close the issue)

Feedback: please take a look http://bytedeco.org/   (tensorflow is listed)
Why cppSharp? Many who have tried e.g. .NET wrapper for OpenCV for years (P/Invoke) are now trying to explore how to use cppSharp to generate .NET wrapper for OpenCV.
I believe both cppSharp and JavaCpp are similar in the ways of creating wrapper codes automatically. They compile C++ codes and generate the c# or java binding codes respectively.
There is no more need to MANUALLY (in the case of SWIG and P/Invoke) to do regular catch-up with the fast development of the master c++ codes.
This is my view, I may be wrong, I am open to feedback and to learn from others.

Hey guys, dev from CppSharp here, just been made aware of this discussion. Just some clarifications.
If you want to bind a library with a generator like CppSharp, it's usually best to start with a C++ API from the start since that will lead to a more idiomatic generated API.
We can also generate bindings for the C API, but you will usually need to develop an higher-level C# API on top of the generated bindings to have a more idiomatic C# object-oriented API.
The only exception to this is when the original C++ public interface is complex / not very "clean" (boost, lots of templates) and then the auto-generated API might not be very clean and starting from the C API might be preferable.
I can't say what is the best approach for providing bindings for TensorFlow, but if you do end up going with CppSharp we'll do our best to support the project and fix any bugs found along the way.

fyi - I built this script to spit out c# files (en masse) from tensor flow proto buffers for use with grpc https://gist.github.com/johndpope/5d176f4eebeb7ec983fa77d945c18fb1
If you want to co-ordinate efforts further -> jump on #grpc channel
https://tensor-flow-talk-invite.herokuapp.com/invite

Having the C# wrapper use the C API through DllImport is the right approach. I have written many such things (having had to interface with Matlab-exported C a number of times). You can see something of my similar work here: https://github.com/BrannonKing/NLoptNet . I'm willing to work on it. Now I just need a Windows DLL.

JUST DO IT

You can now use tensorflow with pythonnet to call from .NET languages:
https://github.com/pythonnet/pythonnet/issues/299

Is first class support for c# even planned?
Development with wrappers and such is almost always a sub-par experience; and using tf in serious projects when there's no actual support from the devs is not something I'd do.

The TensorFlow maintainers do not currently have plans for creating a C# API. We do however maintain the C API intended for building language bindings and are open to changes to that to assist the community in building C# APIs.

@denfromufa have you tried it (running tensorflow from .net via phytonnet)?
if you did - can you give some pointer on how to do it?

@tiagosomda you can ask from @snarb about his experience with tensorflow and pythonnet. I just tried importing it successfully, but have not played with it yet.

@denfromufa it is ok. works, but I have used it mainly for sort of unit-testing of my C# implementation :)

We are interested in doing this work.
I believe someone in my team had started work on this, if not, we will be happy to contribute it.

@migueldeicaza That'd be great! Please look at https://www.tensorflow.org/versions/r0.11/how_tos/language_bindings/ as a starter guide.
Also, if you'd like code review from the TensorFlow team, then please loop in me and @asimshankar after it's committed somewhere. Thanks!

Pythonnet in .net works, but is not particularly practical. SWIG (using Linux/Mono) generated wrapper/manually exposing the C API in a wrapper is working well for me

@luketg8 with SWIG, someone(s) [most likely from the C API guys who also must know .NET - unfortunately not in this case here] to "manually exposing" to keep/catch up with the latest code change.
With CppSharp, as discussed by @tritao, you need an experienced specialist committed to setup the workflow to create the .NET bindings, after that, users like us could just simply use the created workflow to catch up with the latest code change
With CppSharp, not only there "should not be" issue making the .NET wrapper available for e.g. Linux/Mono, but if we lucky, we also get cross platform support.
Imagine having .NET bindings for tensorflow [through CppSharp]  while coding for Mac, iOS, Android and UWP. If anyone need concrete example, follow what @migueldeicaza's team does with creating .NET binding for c++ Urho3D to cross platform UrhoSharp
In my experience, there still need much work to make embedding python in .NET through Pythonnet reliable and hence practical.

@JimSEOW I agree that it is a lot of effort to maintain the wrapper for the C API when there are new updates, but it is just what is working for me at the minute with the limited amount of C# I need to do. For now, I have just had to write a lot of my code in C++ and prototype in Python.
However, I do agree (having experimented briefly) with the use of CppSharp for this, but I think I'd need to look into it more to write a proper conclusion.

@jhseu Thanks for the pointer, it has proved to be very useful.
I am making good progress on the API, I am doing a line-by-line port of the C API test to make sure that I got the proper API coverage, and also using this as an opportunity to make sure that the API is idiomatic C#.
It is not ready to be reviewed, but for reference, the code is here:
 https://github.com/migueldeicaza/TensorFlowSharp

I'll post on this thread when it is ready to be reviewed.

Nice! Feel free to ping me by e-mail if you run into any issues or have any questions.

Just emailed you on your profile email address :-)

@jhseu [Not sure if you are the right person to ask]
Is there a plan to build native library [libtensorflow.dll] on Windows?
So we could persuade @migueldeicaza to get tensorflow/tensorsharp working on Windows?

We don't have any immediate plans, but making it would likely be trivial once Bazel works on Windows. I believe that's coming soon, but I'm not sure.

FYI: Here is some recent effort to use Bazel Windows to build the native library [libtensorflow.dll]

Along with these solutions, Emgu CV have also added a tensorflow importer to their DNN module https://github.com/emgucv/emgucv

@jhseu It seems that Bazel NOW works on Windows
https://github.com/tensorflow/tensorflow/issues/8919

TensorFlowSharp now works on Window using libtensorflow.dll extracted from tensorflow-1.1.0rc1-cp35-cp35m-win_amd64.whl
https://github.com/migueldeicaza/TensorFlowSharp/issues/49
Image Recognition using Tensorflow now works through TensorflowSharp in Windows (c#)

@JimSEOW great news, thank you everybody for your efforts!

great news to me as well, thanks to tensorflow team! Genius!

Image Recognition based on this example

JimSEOW, thanks for sharing, you are great!

NO! @migueldeicaza makes this possible!!

@DomLi and @luketg8 Could both you share your feedbacks, issues at TensorflowSharp
If you look through these open issues, there are still open technical challenges need to be addressed to make TensorflowSharp or .NET same FIRST class citizen as python for Tensorflow.

will keep trying, but too busy with some other projects at moment, luke and me in the same office:):)

Starting Release 1.2, Windows DLL will be  made available  and tensorSharp binding works!

Which is the status of .Net binding as of today? Are C# and F# really usable languages to work with Tensor Flow or the situation is still as described in this previous comment? Thanks for the quick recap

@giuliohome : The TensorFlow maintainers do not maintain or support the C#/F# bindings and have no plans of doing so. However, we happily point you to TensorFlowSharp, which is built on top of the supported C API. Any questions/comments/concerns you have there are better raised in the TensorFlowSharp repository.

@giuliohome please visit Tensorflowsharp. We are using the latest window dll contributed by this group C API. We need more people to port python tensorflow examples/tutorials codes to .NET

can anyone plz tell me how to write a fresh tensor flow C# project in Visual Studio MacOS? What project should I choose?

Also I have installed TensorFlowSharp using Nuget from inside of Visual Studio MacOS but when I built the existing example project from within of Visual Studio nothing happens

It says built successful but no happens. What output for Example Common generates? Any that is generated or anything?
In case of Tensor Flow & Python....it's shows output in Jupyter but don't know here :(
Someone plz help me out :(
@migueldeicaza tried to help me on Twitter & on this https://github.com/migueldeicaza/TensorFlowSharp/issues/149#issuecomment-331361048
issue but no luck so far

Your best bet is the instruction right here:
https://github.com/migueldeicaza/TensorFlowSharp/issues/149#issuecomment-331329430
There is still no official C# support in TF itself, so we wont be able to help much.

@gunan but how has he created this projects?

ExampleCommon is a library project, not an executable project.   That is why it does not have a [>] icon, but a [|>] icon.   Open an actual example.

@migueldeicaza  amazing effort! Thanks a ton!

so is this thread for C# TensorFlow. I mean will you be able to train models in C# after that? Just like we do in Python?

Yes, you can train models in C#.   It seems like people like to use it to reuse existing code that imports their existing data into TensorFlow.
Today it is better to use Python and Keras to define your models/graphs and then load the result from C# and run that.

Probably this solution will be helpful for C# developers: TensorFlowServingCSharpClient
There are TF MNIST Deep model learning and save model for TF Serving.
.NET console application and SPA .NET Core 2.0 ReactJS examples. It use TensorFlow Serving API with gRPC service calls.

@migueldeicaza Thanks again for TensorFlowSharp! As the feature has been already implemented, I am closing this issue

My company is developing a full C# binding to Python API: https://losttech.software/gradient.html

Another solution is TensorFlow.NET.

Latest tensorflow.dll for c# api


Support TEI on AMD GPUs

Feature request
Are there active plans to add support for generating embedding using AMD GPUs?
Motivation
AMD and Hugging Face are currently engaged in an ongoing collaboration to ensure compatibility of Hugging Face transformers with AMD ROCm and hardware platforms.  Providing support for HF TEI toolkit would add a compelling alternative for deploying and serving open-source text embeddings and sequence classification models.
Your contribution
Work with other on PRs to integrate changes to support AMD GPUs.

Indeed it would be interesting to support more backends.
Adding support for AMD GPUs will happen in Candle tough, not in TEI directly.

@OlivierDehaene Thanks for the response.  Does TEI support python backend instead of Candle? I see https://github.com/huggingface/text-embeddings-inference/tree/d05c949c1234786c15b675f4419776a417519583/backends/python? Is this python code only for the grpc server implementation?

This backend is an example of how you would go about adding other backends to TEI. It is currently out-dated but could be updated to support AMD.

Are there any active effort support to make python backend fully functional?
What models can be run at this moment?
Thank you for all the answers.

Hello? Is there any WiP regarding ROCm support for TEI? Thanks!

Hello? Is there any WiP regarding ROCm support for TEI? Thanks!

I'm interested in this as well. May start working on it myself, but don't want to duplicate efforts if it's already in the works.

Hi, there is some progress in https://github.com/huggingface/text-embeddings-inference/pull/293. Would you mind sharing which AMD GPUs you are using? Thank you!

Currently using MI250s.

Hi, any news on this, is there a way to serve the models with amd gpus on TEI?
regards!


Support TLA+ bags

TLA+ has a "bag" type which is better known as a multiset. We need to support bags and their corresponding operators and functions. A bare-bones Go multiset library is available at https://github.com/soniakeys/multiset.
Original issue: https://bitbucket.org/whiteoutblackout/pgo/issues/32/support-tla-bags

We now have a framework for implementing built-in modules. See pgo.trans.intermediate.TLABuiltins for details.


[Automation] Release new 3.0.2-preview release of the SDK.

Description
Generating new SDK for changes added in the following Rest API Specs PR:

SourceControl spec - https://github.com/Azure/azure-rest-api-specs/pull/2461
Job resource updated - https://github.com/Azure/azure-rest-api-specs/pull/2466
New 2018-01-15 specs updated - https://github.com/Azure/azure-rest-api-specs/pull/2690

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] Please add REST spec PR link to the SDK PR
[x] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[x] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@azuresdkci retest this please

Hi @dsgouda. I am closing this SDK PR as we need to fix some more things in the Swagger Spec. I'll create a new PR. Thanks.


gRPC python server handles one RPS while concurrency is set to 1000

What version of gRPC and what language are you using?
Python 3.6.7
grpcio 1.22.0
What operating system (Linux, Windows,...) and version?
Ubuntu 18.04.2 LTS
What runtime / compiler are you using (e.g. python version or version of gcc)
Python 3.6.7
What did you do?
https://gist.github.com/alirezastack/ec8e4d97dfdfbb8ae1c8724e742bc343
What did you expect to see?
If I set max_workers to 1 and maximum_concurrent_rpcs to 1000 I'd expect to handle concurrent requests until resource gets exhausted.
What did you see instead?
Server works synchronously and receives one request at a time, the other request waits until the first request is served. I used sleep(5) in method call to easily trace the issue.
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs). This the stack trace when testing with ghz gRPC load testing tool
https://gist.github.com/alirezastack/bbc480fa91f0202bdab96b591e6865cb
Anything else we should know about your project / environment?
Cement Python Framework is a wrapper around gRPC server if that helps.

@alirezastack gRPC Python servers are currently all synchronous. That is, each servicer thread you provide in your thread pool handles a single RPC to completion before handling the next. So max_workers effectively dictates your concurrency.
As per the documentation,

maximum_concurrent_rpcs – The maximum number of concurrent RPCs this server will service before returning RESOURCE_EXHAUSTED status, or None to indicate no limit.

So maximum_concurrent_rpcs gives you a way to set an upper bound on the number of RPCs waiting in the server's queue to be serviced by a thread. As such, concurrency is really min(max_workers, maximum_concurrent_rpcs). Although, in general, I would expect maximum_concurrent_rpcs to be higher than max_workers.
If the "1 thread = 1 RPC" model doesn't work for you, we do offer experimental gevent support and we are actively working on asyncio as our standard solution for handling all RPCs on a single thread.


Update role definition names and keys used for MIWI

Which issue this PR addresses:
Role definition names after feedback and more explicit role names.
What this PR does / why we need it:
Role definition names after feedback and more explicit role names.
Test plan for issue:
N/A

/azp run ci, e2e

Can we also update the roleset in pkg/util?

Why is it defined in two places?  (actually three, RP config too).

Can we also update the roleset in pkg/util?

Why is it defined in two places? (actually three, RP config too).

It looks like the pkg/util/rolesets/const.go one is only referenced by the dev cluster hack: https://github.com/Azure/ARO-RP/blob/3b6426c8c155e1ec76e09ab47ef1f410412fa7b1/pkg/util/cluster/cluster.go#L702
The hack could probably read it from the env var to knock it down from three places to two.

/azp run ci, e2e

/azp run ci, e2e


Request: Add .11ty.js examples to README

As mentioned in https://github.com/11ty/eleventy/issues/1217, I request that the README include examples for .11ty.js templating, in addition to the existing Nunjucks and Liquid templating examples. Thanks!

This package is now deprecated. This repository will be archived and the removed from the plugin list.
https://www.npmjs.com/package/eleventy-plugin-meta-generator


Observing "500 Internal server error" when user invoke "API:/v1/read-current-mac-table-from-device"

Observing "500 Internal server error" when user invoke "API:/v1/read-current-mac-table-from-device" with below error message
Package: macaddresstablerecorder_1.0.1.d_impl
Error message:
{
  "code": 500,
  "message": "Failed send data to requestor: Request failed with status code 400"
}

To better understand the error, could you please write into details how you invoke the API?
In particular I need to to know also the body of the message sent by POST because I suspect that the error is due to requestor.


Tasks exported from module, example with psd1?

Is it possible to make something like https://github.com/nightroman/Invoke-Build/blob/master/Tasks/Import/MyModule/MyModule.psm1#L11 work, but with a module that has a psd1 data file?
I've been experimenting with this, but the Set-Alias and Export-ModuleMember never run when there's a definition. Exporting the alias in the psd1 itself also doesn't seem to work (The term 'ModuleBuild.tasks' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.)
e.g. without psd1:
PS /home/voltagex/src/modulebuild> ipmo ./ModuleBuild
VERBOSE: Performing the operation "Set Alias" on target "Name: ModuleBuild.tasks Value: /home/voltagex/src/modulebuild/ModuleBuild/ModuleBuild.tasks.ps1".

with psd1:
PS /home/voltagex/src/modulebuild> ipmo ./ModuleBuild
PS /home/voltagex/src/modulebuild> ipmo -verbose ./ModuleBuild

Thanks in advance for any assistance.

The answer is to put the module name in ModulesToProcess in the psd1, e.g.
@{
ModuleVersion = '0.0.1'
ModuleToProcess = 'ModuleBuild.psm1'
GUID = 'b37bacdc-a2c3-4e4c-9527-fa4257baa9dd'
Author = 'voltagex'
CompanyName = 'Unknown'
Copyright = '(c) voltagex. All rights reserved.'
FunctionsToExport = '*'
CmdletsToExport = @()
VariablesToExport = '*'
AliasesToExport = '*'
PrivateData = @{
    PSData = @{
}


Changed v0.1 to 0.1 in LUIS Section

It should be v0.1 as when it's used in conjunction with dispatch tool, it gives an error.
Fixes #
Proposed Changes

Testing

Pull Request Test Coverage Report for Build 1934

0 of 0   changed or added relevant lines in 0 files are covered.
138 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-2.4%) to 66.282%

Files with Coverage Reduction
New Missed Lines
%

packages/Ludown/lib/ludown-translate.js
1
78.05%

packages/Ludown/lib/translate.js
20
52.08%

packages/Ludown/lib/translate-helpers.js
117
39.88%

Totals

Change from base Build 1920:
-2.4%

Covered Lines:
3898

Relevant Lines:
5570

💛  - Coveralls

@arafattehsin Can you take case of the licence check, so we can merge this in? :) Thanks!

@arafattehsin just click on the line that reads "**license/cla ** Expected — Waiting for status to be reported". Should be pretty straight forward from there.

Unfortunately, that whole line is not clickable at all. Just attaching my screenshot for the reference.

There has been an issue lately and I am not sure if it's related to this: https://blog.travis-ci.com/2018-09-27-deprecating-github-commit-status-api-for-github-apps-managed-repositories

Closing PR as it's very old.
@arafattehsin if this is still relevant, please open a new PR. Hopefully the license check will work properly for you this time around.


Apply "not" selector and "focus" that depends on another component

Hi,
I need an equivalent of this:
  &:not([value='']) {
    outline-none
  }
 ${Input}:focus ~ && {
    text-xs
  }

Is there an equivalent with this library?

@valentin-harrang
If you use latest Tailwind version you can write custom modifiers (selectors) (i.e. &:not([value=''])) with arbitrary variants:
[&:not([value=''])]:outline-none

docs here: https://tailwindcss.com/docs/hover-focus-and-other-states#using-arbitrary-variants
For the next lines, referencing parent elements can be achieved with 'group' modifier and siblings with 'peer' modifier.
For your use case:
Mark the sibling element with:
peer

and the target element(s) with:
peer:focus:text-xs

Docs here:
https://tailwindcss.com/docs/hover-focus-and-other-states#styling-based-on-parent-state
https://tailwindcss.com/docs/hover-focus-and-other-states#styling-based-on-sibling-state
Suggest you to read the entire article.


Can no longer use  require("d3-array") in Node.js

Steps to reproduce

Create a project with d3-array as a dependency (version 3.0.0 and up)
Create a node script with contents require("d3-array");
Execute script with Node.js (node myScript.js);

What you get is this
require() of ES modules is not supported.
require() of /Users/jessejorgenson/projects/uno/node_modules/d3-array/src/index.js from /Users/jessejorgenson/projects/uno/scripts/d3ArrayCheck.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /Users/jessejorgenson/projects/uno/node_modules/d3-array/package.json.

    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1154:13)
    at Module.load (internal/modules/cjs/loader.js:986:32)
    at Function.Module._load (internal/modules/cjs/loader.js:879:14)
    at Module.require (internal/modules/cjs/loader.js:1026:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/Users/jessejorgenson/projects/uno/scripts/d3ArrayCheck.js:1:1)
    at Module._compile (internal/modules/cjs/loader.js:1138:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)
    at Module.load (internal/modules/cjs/loader.js:986:32)
    at Function.Module._load (internal/modules/cjs/loader.js:879:14) {
  code: 'ERR_REQUIRE_ESM'
}

This seems to be due to adding "type": "module" to the d3-array package.json and not including a CommonJS fallback. I don't know exactly how it should be configured given the confusion with bundlers, but I believe just removing "type": "module"  would make everything work again and then bundlers could use the "module" entry point.

@mbostock Any specific reason you closed this?

Probably because everyone asks the same question. We tried to document it in the release notes:

This package now requires Node.js 12 or higher. For more, please read Sindre Sorhus’s FAQ.

and at the top of https://github.com/d3/d3-array


[RELAND][Layouts] Reuse existing materializations in backwards pass

This PR enables reusing existing convert_layout ops in the backwards pass if they didn't get removed through some other means. This enables the compiler to remove some tricky layout conversions by recognizing that the same computations can be reconstructed using other layout conversions.
This relands the original change with the proper dominance fix included. The pass has to be careful when re-using existing rematerializations that they actually dominate the relevant part of the backwards slice. To facilitate this, I changed some functions to pass OpOperand & around, which gives more information about the use->def edges being analyzed.

Checked against internal CI: the change seems good to go now


You should give option to get cities using state name also

Scenario:
If there is a form/screen where the user has to give some details like name, contact, email, state, and city.
So, While adding the above details we will ask the user to select state first. then we will ask for the city based on the selected state. And we will add the details.
But while updating details we will have only the state name. so we will need to save an additional field for the state code also. But you should give the option to get cities based on state name also.

Alright
Thanks


Bug/#152784557

Preferably: merge #73 first so that those changes can be merged into this branch to move style changes into SignupForm.scss
Fixed email field showing errors prior to user inputting anything
This could possibly be applied to the password field as well..

Merged this into Feature/#151586154. Closing.


Handling of unverified email address

Tried running:
python3 execute_morf_job.py --server_config_url file:///Users/miguelandres/Documents/GitHub/morf-install/config/server.config --client_config_url file:///Users/miguelandres/Documents/GitHub/morf-install/config/client.config
Got the following error:
[INFO] retrieving file file:///Users/miguelandres/Documents/GitHub/morf-install/config/client.config to /Users/miguelandres/Documents/GitHub/morf-install/job_runner/work/tmpj41ox9kx
[INFO] uploading config.properties to s3://miggy-test1/miggy_andres/morf-api-test-session/config.properties
[INFO] retrieving file file:///Users/miguelandres/Documents/GitHub/morf/mwe/mwe.tar to /Users/miguelandres/Documents/GitHub/morf-install/job_runner/work/tmpj41ox9kx
[INFO] retrieving file file:///Users/miguelandres/Documents/GitHub/morf/mwe/controller.py to /Users/miguelandres/Documents/GitHub/morf-install/job_runner/work/tmpj41ox9kx
[INFO] uploading docker_image to s3://miggy-test1/miggy_andres/morf-api-test-session/docker_image
[INFO] uploading controller.py to s3://miggy-test1/miggy_andres/morf-api-test-session/controller.py
[WARNING] error sending email to<EMAIL_ADDRESS>An error occurred (MessageRejected) when calling the SendEmail operation: Email address is not verified. The following identities failed the check in region US-EAST-1<EMAIL_ADDRESS><EMAIL_ADDRESS>Traceback (most recent call last):
  File "controller.py", line 29, in <module>
    from morf.workflow.evaluate import evaluate_course
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/morf/workflow/evaluate.py", line 34, in <module>
    import sklearn.metrics
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/sklearn/__init__.py", line 134, in <module>
    from .base import clone
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/sklearn/base.py", line 11, in <module>
    from scipy import sparse
ModuleNotFoundError: No module named 'scipy'
Traceback (most recent call last):
  File "execute_morf_job.py", line 48, in <module>
    main(args.client_config_url, args.server_config_url, args.email_to, args.no_cache)
  File "execute_morf_job.py", line 36, in main
    run_morf_job(client_config_url, server_config_url, email_to, no_cache)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/morf/utils/job_runner_utils.py", line 195, in run_morf_job
    config["job_id"], config["user_id"], config["email_to"])
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/morf/utils/alerts.py", line 136, in send_success_email
    attachment_filepath = download_from_s3(proc_data_bucket, key, s3)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/morf/utils/__init__.py", line 68, in download_from_s3
    s3.download_fileobj(bucket, key, resource)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/boto3/s3/inject.py", line 570, in download_fileobj
    return future.result()
  File "/Users/miguelandres/Library/Python/3.6/lib/python/site-packages/s3transfer/futures.py", line 73, in result
    return self._coordinator.result()
  File "/Users/miguelandres/Library/Python/3.6/lib/python/site-packages/s3transfer/futures.py", line 233, in result
    raise self._exception
  File "/Users/miguelandres/Library/Python/3.6/lib/python/site-packages/s3transfer/tasks.py", line 255, in _main
    self._submit(transfer_future=transfer_future, **kwargs)
  File "/Users/miguelandres/Library/Python/3.6/lib/python/site-packages/s3transfer/download.py", line 349, in _submit
    **transfer_future.meta.call_args.extra_args
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/botocore/client.py", line 314, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/botocore/client.py", line 612, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (404) when calling the HeadObject operation: Not Found

This error is due to unverified email addresses; this should actually be checked before the job even runs, probably in morf_listener() or execute_morf_job().

When an unverified email address is detected, the job should print an alert and ask the user to verify their email address (by calling `verify_email_address()', and stop execution.


Bug with ember-changeset and defaultValue

I'm using one-way-checkbox with ember-changeset. It looks like if I set defaultValue: false on a model boolean attribute, the checkbox acts all weird: Twiddle.
I'm not sure if it is this project's fault or ember-changeset, especially since it works fine if I don't use a changeset. I opened the same ticket there: https://github.com/DockYard/ember-changeset/issues/156

Closing this, identified the issue in the ember-changeset project.


Android support

I've tried to build a project for Android and it tried to link to xcb. Turns out this library depends on xcb :)
Is Android support planned and if not, could we add a compile_error! if the target platform is Android?

Android support is in scope. It looks like the relevant documentation is here.
I've asked the Servo folks about recommended crates for poking at android APIs from Rust, and will add that information here once I get a reply.

@torkleyy I would love this too (I use a tablet with Termux when Im away from my PC), much better than a laptop!
@aweinstock314 there is no need to find any Rust/Android APIs, Termux provide these via its termux-api (an API written in Python that can interact with our ugly Java ways :)
The API provides many commands including:

termux-clipboard-set
termux-clipboard-get

The two above values are all we need added! 👍
It would be really appreciated! (I found a beautiful text editor but it uses this utility so I am currently unable to copy/paste).

I have implemented it. Please take a look: https://github.com/aweinstock314/rust-clipboard/pull/87


Is this SDK working?

Seems not.

This SDK is for old API version which is off since may 2023.
You should use new version of API.
Repository: https://github.com/Tinkoff/investAPI
Documentation: https://tinkoff.github.io/investAPI/


Refractor favorite sections

Describe the feature you'd like
Currently, the favorite event is cached inside the app. We can use the API endpoint: https://api.eventyay.com/v1/user-favourite-events to store it in the server and fetch it whenever the user is logged in
@iamareebjamal Please give some thoughts on this
Would you like to work on the issue?
Yes

Store locally for non logged in person and store on server for logged in person

@anhanh11001 are you working on this ?

@aggarwalpulkit596 Yes I'm

@anhanh11001 any update on this if not can I work on this?

@aggarwalpulkit596 Yes, please go ahead to take over if you are free now

@anhanh11001 cool

@iamareebjamal should I update the favorite list on the server if the user logs or only update favourite which are marked after the user is logged in

First


meanjs 0.4.0 not working when deployed to Heroku

I've just tried the meanjs 0.4.0 in local host and runs fine but when I deploy to heroku (link to app here) and try the "Sign up" option I get this in the navegator console:

POST https://meanjsapptest.herokuapp.com/api/auth/signup 503 (Service Unavailable)

and when I write the comand heroku logs in the CLI I get:

2017-06-06T04:15:35.152983+00:00 app[web.1]: (node:16) DeprecationWarning: Mongoose: mpromise (mongoose's default promise library) is deprecated, plug in your own promise library instead: http://mongoosejs.com/docs/promises.html
2017-06-06T04:15:35.153005+00:00 app[web.1]: crypto.js:635
2017-06-06T04:15:35.153006+00:00 app[web.1]:     throw new TypeError(
2017-06-06T04:15:35.153006+00:00 app[web.1]:     ^
2017-06-06T04:15:35.153007+00:00 app[web.1]:
2017-06-06T04:15:35.153008+00:00 app[web.1]: TypeError: The "digest" argument is required and must not be undefined
2017-06-06T04:15:35.153009+00:00 app[web.1]:     at pbkdf2 (crypto.js:635:11)
2017-06-06T04:15:35.153010+00:00 app[web.1]:     at Object.exports.pbkdf2Sync (crypto.js:628:10)
2017-06-06T04:15:35.153012+00:00 app[web.1]:     at model. (/app/modules/users/server/models/user.server.model.js:112:26)
2017-06-06T04:15:35.153011+00:00 app[web.1]:     at model.UserSchema.methods.hashPassword (/app/modules/users/server/models/user.server.model.js:123:19)
2017-06-06T04:15:35.153013+00:00 app[web.1]:     at _next (/app/node_modules/hooks-fixed/hooks.js:62:30)
2017-06-06T04:15:35.153013+00:00 app[web.1]:     at fnWrapper (/app/node_modules/hooks-fixed/hooks.js:186:8)
2017-06-06T04:15:35.153014+00:00 app[web.1]:     at model. (/app/node_modules/mongoose/lib/plugins/saveSubdocs.js:20:7)
2017-06-06T04:15:35.153014+00:00 app[web.1]:     at _next (/app/node_modules/hooks-fixed/hooks.js:62:30)
2017-06-06T04:15:35.153015+00:00 app[web.1]:     at fnWrapper (/app/node_modules/hooks-fixed/hooks.js:186:8)
2017-06-06T04:15:35.153015+00:00 app[web.1]:     at /app/node_modules/mongoose/lib/plugins/validateBeforeSave.js:33:13
2017-06-06T04:15:35.153016+00:00 app[web.1]:     at /app/node_modules/kareem/index.js:131:16
2017-06-06T04:15:35.153016+00:00 app[web.1]:     at _combinedTickCallback (internal/process/next_tick.js:95:7)
2017-06-06T04:15:35.153017+00:00 app[web.1]:     at process._tickCallback (internal/process/next_tick.js:161:9)
2017-06-06T04:15:35.167579+00:00 app[web.1]: error: Forever detected script exited with code: 1
2017-06-06T04:15:35.173500+00:00 app[web.1]: error: Script restart attempt #1
2017-06-06T04:15:35.292903+00:00 app[web.1]:
2017-06-06T04:15:35.294191+00:00 app[web.1]:
2017-06-06T04:15:35.310954+00:00 app[web.1]: + Error: Certificate file or key file is missing, falling back to non-SSL mode
2017-06-06T04:15:35.311037+00:00 app[web.1]:   To create them, simply run the following from your shell: sh ./scripts/generate-ssl-certs.sh
2017-06-06T04:15:35.311039+00:00 app[web.1]:
2017-06-06T04:15:35.916892+00:00 app[web.1]: Db.prototype.authenticate method will no longer be available in the next major release 3.x as MongoDB 3.6 will only allow auth against users in the admin db and will no longer allow multiple credentials on a socket. Please authenticate using MongoClient.connect with auth credentials.

I don't know what to do now because Heroku supports tell me thar the error is in my code but I haven't changed anything there!

I had to change the node version in Package.js from ">=0.10.0" to "6.6.0" and now it's working fine.

I'll update our engines to reflect 6.10, but where did you get that 0.4.0 version to begin with? this is the generator? because 0.10.0 seems rather an old entry

Yes. The package.js show a node version "node": ">=0.10.0" when I used the Yeoman generator.


publish caliper to npm

Following the conversion of Caliper into a monorepo, with the Caliper components split into their logical component packages, we should publish Caliper to npm so that it may be made available.
We have the following dependancy tree:
caliper-CLI

caliper core
caliper-adapter-A

caliper-core
adapter-A-sdk

caliper-adapter-B

caliper-core
adapter-B-sdk

caliper-adapter-C

caliper-core
adapter-C-sdk

caliper-core

no (internal) deps

Based on the above:

When caliper-core is updated with breaking changes, all modules require dependancy changes
When a new major sdk occurs for an adapter, the adapter and CLI require updating
When an adapter is updated to the next major release, the Caliper-CLI requires updating

The following is proposed:

To prevent confusion in platform version compatibility, adapters are published at the same version level as the technology they target. For instance<EMAIL_ADDRESS>may be used with Fabric version 1.1<EMAIL_ADDRESS>may be used with Fabric 1.4. The adaptor dependancies are set to consume up to the next major version of the target SDK, and the "x" is used by Caliper to provide flexibility in our own publishing for updates/fixes. We can follow a similar pattern with other adaptors.
An alternative to the above would be to publish adapters at 0.xy.z levels, where x-y are the major-minor version of the target platform and the z relates to the caliper patch version number. eg<EMAIL_ADDRESS>would target fabric 1.4. This would retain a release a 0 release for caliper, and the ability to retain patch versions.
caliper-core and caliper-cli remain at 0.x.y levels

We will need to be explicit in release notes regarding the supported target platform(s) that the CLI is capable of interacting with, since there will be a disconnect in the 0.x.y versioning with versioning that mirrors the target platform.
Item for consideration:

Caliper-core dependancies in adaptors and the CLI are set to '~' so they will automatically pull in the next minor (patch) release that is compatible.
This risk in doing the same for a consumed client-sdk within the adapters is that we lose the ability of fixing tests at the client level. This may expose us to breaking changes if the underlying semantic versioning rules are not strictly adhered to.
The need to update caliper-cli version for each individual adapter release leads to a tricky versioning system, or at the very least the need to maintain a compatibility table. We could circumvent this through further subdivision of the project into packages such as caliper-cli-sawtooth or investigate the ability to dynamically pull a versioned dependancy within the cli itself. This item needs more discussion.

hi , Do u succeed install Cli (1.4), i met an erro when install cli ?Any help would be greatly appreciated!

@nklincoln So, I played around with the versioning and publishing stuff a bit. By building on PR #502, this branch restructures the dependencies a little bit.
Reasoning and modifications
The modifications took into account the following assumptions/thoughts:

The CLI package in its own is really lightweight, its only job is to nicely call the common entry points of the adapter packages (through the core, technically), irrespectively of the actual platform and version of the package.
When a user creates a Caliper project, the only thing that should be needed is to install a single package corresponding to the SUT. I think this one-liner setup is crucial for usability until we publish Docker images.
It's a best practice to keep projects as self-contained as possible. We saw that global installs can cause hard-to-debug problems, plus different projects could require different Caliper package versions.

To this end, I inverted the dependencies between the CLI and adapter packages. The dependency tree became simpler, just like the installation of packages. Example for the caliper-fabric-ccp packages:
<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
Result
Once the packages are published (more on that later), creating a Caliper project that targets Fabric 1.4.1 is straightforward:
mkdir secret-project && cd secret-project

# assemble your artifacts, e.g., suppose the contents of packages/caliper-samples are here

# do the usual npm project setup
npm init

# use the local registry for now
npm i --registry http://localhost:4873 --save<EMAIL_ADDRESS>
# use npx for locally installed CLI binary
npx caliper benchmark run -w . -c benchmark/simple/config-linear-rate.yaml -n network/fabric-v1.4.1/raft/fabric-ccp-node-tls.yaml

And that's it. Installing Caliper and the SUT-compatible package took one command, and the extra npx command is not a big price to pay for a self-contained project.
Technicalities
The "specification" of packages to publish is in the npm_publish directory. The publishing script reads the file list and performs a backup-replace-restore workflow on the package.json file of the given package (e.g., packages/caliper-fabric-ccp/package.json ) and publishes it with the given version and corresponding dependencies. So this list is a one-to-one mapping to the published adapter packages (or even Docker images later on).
Up for discussion
Currently, the adapter versions match the backend SDK versions exactly. I'd support the idea of matching only the major and minor versions (publishing the package with the latest SDK patch version), thus leaving the package patch version for adapter-related semantic versioning.
E.g<EMAIL_ADDRESS>uses the latest Fabric SDK (1.4.3) which is (hopefully) compatible with any Fabric 1.4.Y version.

Finally resolved this 👍


简化pubsub参数

Hi @naah69 I think it could be better to have the commit message in English words.

this is careless.


Unfolding: Horrible quality of the minted NFTs + missing animation

Unfoldings - https://kodadot.xyz/base/collection/0xc029b380f8a451cfd9e5124fa9fcad4397b8c119
Base collection minted via frames on Farcaster. The quality of the pictures is very low.
Check how original art looked like in code-checker:
Unfoldings.v1_9 (1).zip
Original code art quality:

When you open on full-screen any NFt from the collection, you can see that the quality is very low.
Looks like gallery on koda outputting only prerendered image instead actual canvas.
Bacuse also animations are not working (click on picture + press A to start the animation)

@JustLuuuu try with this link will be fixed by #10075

fixed by

https://github.com/kodadot/nft-gallery/pull/10075
https://github.com/kodadot/nft-gallery/pull/10092


dashboard/app: use go122

go122 is the latest supported. Let's update.
https://cloud.google.com/appengine/docs/standard/lifecycle/support-schedule#go

Migrated traffic to go122. It works.


Windows .zip folder in releases fails to extract.

Bug
A clear and concise description of what the bug is.
In the releases I go the lbry-desktop.zip, I download it and then click extract on my windows computer and it doesn't extract. It says nothing is in the .zip.
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.
What is supposed to happen is that I can go to the releases click on the zip, download and extract.
Screenshots
If applicable, add screenshots to help explain your problem.
System Configuration
I am using a windows computer.

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Additional context
Add any other context about the problem here.

Reopen if there's a good repro - much has changed with new certificate, etc.


Vectorized implementation

Hi, I put together a vectorized implementation. Are you interested in adding it? If so, how would you like me to proceed?
The implementation is not an iterator: instead, it returns numpy arrays for Xs and Ys.

I should add that I did a couple of simple tests and my implementation is 40x faster.

That sounds great! However, I think the simple implementation has its place:

numpy is a pretty big dependency,
the code is probably more straightforward,
the API should not be changed lightly.

Still, anyone searching for bresenham should probably see the vectorized implementation as well.
I an see two ways to proceed:

add it as a separate module here,
make it a separate project, in which case I'd be happy to link to it from the README.
Which sounds better for you?

I should add that I did a couple of simple tests and my implementation is 40x faster.

That sounds about right :)

Hi @encukou
I'd rather keep both implementations in the same package, as separate modules - it feels more Pythonic, and less confusing to users. This is all if you are happy to add a Numpy dependency.
As for the readability, I think the vectorized implementation is pretty straight-forward, and conceptually maybe even easier to understand than the non-vectorized implementation. Basically, it computes the points on the line at integer intervals on X or Y and then rounds the numbers, with some logic to handle |m| > 1 and swapping p1 with p2.
I made a PR so you can have a look yourself: #5


No longer working with BabyBuddy Container

Using BabyBuddy v1.12.2 via docker, Home Assistant version 2022.9.7. My scripts for starting a timer and logging food (without a timer) no longer work.
Start timer topped working:
  - type: button
    tap_action:
      action: toggle
    entity: switch.child1_last_timer
    show_icon: true
    name: Start Timer

Button to log food stopped working:
  - type: button
    tap_action:
      action: toggle
    entity: script.babybuddy_add_self_fed_snack
    name: Snack

With the below script:
babybuddy_add_self_fed_snack:
  alias: BabyBuddy Self Fed - Snack
  sequence:
  - service: babybuddy.add_feeding
    data:
      type: Solid food
      method: Self fed
      amount: 4
    target:
      entity_id: switch.child1_last_timer
  - service: notify.parents
    data:
      title: BabyBuddy
      message: "\U0001F33D\U0001F966 Snack \U0001F33D\U0001F966"
  mode: single
  icon: mdi:corn

However, I just rolled back to a backup of Home Assistant 9.6 and things appear to work at first glance. Does anyone know what broke with 9.7? Is anyone else having issues?

Any applicable error logs to share?

Upgraded HA to 10.1 and am not having the issue that i saw in 9.7. Marking this as closed.


Showcase Submission for 51-a-pathfinding-algorithm

Thank you Lucas Fredericks for your contribution! A member of the Coding Train team will review it shortly.

Mars Rover Museum Exhibit
Lucas Fredericks

WOW! @lucasfredericks this is amazing! I would love to learn more about the exhibit itself!


Order page style

During the last pull request didn't commit this file, so that it has been deleted but it must be


NIFI-1296, NIFI-1680, NIFI-1764, NIFI-1837, NIFI-1827 implemented new  Kafka processors that leverage Kafka 0.9 API

Improved StreamScanner for better performance
Renamed StreamScanner to StreamDemarcator as suggested by Joe
Added failure handling logic to ensure both processors can be reset to their initial state (as if they were just started)
Provided comprehensive test suite to validate various aspects of both Publish and Consume from Kafka
Added relevant javadocs
Added initial additionalDetails docs
Addressed NPE reported by NIFI-1764
Life-cycle refactoring for the existing PutKafka to ensure producer restart after errors
Incorporated code changes contributed by Ralph Perko (see NIFI-1837)
Addressed partition issue in RoundRobinPartitioner discussed in NIFI-1827

@pvillard31 would be nice (if/when you get time) for you to test and review this one. Basically we want to try to merge this one as quick as possible so community get's a chance to play with it before 0.7 is out so we can address whatever may come up. Keep in mind that this is specifically for 0.9+ brokers

@olegz No problem. Currently in London for a training, will try to test/review it on Friday.

I am going to test the processors with a local installation of Kafka.
A quick question though. Are we going to keep 4 processors for Kafka?
If yes, I think we should add additional information in @CapabilityDescription to help users understand the differences between GetKafka/ConsumeKafka and PutKafka/PublishKafka. As it is now, it can be confusing for users regarding which processor they should use. If we are going to remove Get/Put and use Consume/Publish instead, you can ignore my comment...

I think there is an issue on Consumer side. Here is my test case:
GenerateFlowFile -> ReplaceText -> PublishKafka
ConsuleKafka -> UpdateAttribute -> PutFile
The update attribute processor is to change the filename with uuid to ensure a file is correctly created for each message consumed.
I start all my processors, and after a short moment I only stop the GenerateFlowFile. What I observe is a number X of messages published (confirmed by checking Kafka topic) and a lower number Y of messages consumed. However, the last message published is consumed (I checked the created file). So it seems that some messages are simply skipped.
Then I started only the publish part to have 16 messages published. Stopped the publish part and started the consuming part. I consumed only one message and the number of tasks on ConsumeKafka processor is continually growing (I stopped everything when having 200+ tasks indicated on the processor).
Went in debug, and:
ConsumerRecords<byte[], byte[]> consumedRecords = this.kafkaResource.poll(100);

is empty.
Besides:
boolean reset = this.taskCounter.decrementAndGet() == 0 && !this.acceptTask;

returns false because this.taskCounter.decrementAndGet() = -1
I think it explains the growing number of tasks. But not why some messages are skipped in the process. Will try to figure out why this happens.

Actually @pvillard31 this is yet another great observation as @joewitt and I have seen something similar during the intermittent failures of PublishKafkaTest.validateDemarcationIntoEmptyMessages (missing messages).  I also remember some chatter about similar things on Kafka mailing list specifically related to new API. I'll work on it as well as tidy up lifecycle as it seems yo be an issue for empty polls.
That said, there is also

@olegz @joewitt I updated my last comment to reflect the discussion I had with Oleg regarding the task counter: there is no issue, it was my mistake during debug investigation.

I just played a little bit with the processors and here are some remarks:

Cosmetic remarks

add the duration in provenance events
add the number of messages sent/received (useful when batching)

Testing

Simple case
When I have a topic with one broker and one partition. It seems to be OK: no more data loss, demarcator seems to be used correctly. LGTM.

I then deleted my topic and recreated it with 5 partitions. I am sending flow files with 2 JSON strings (one by line). The PublishKafka is set with appropriate demarcator, plaintext, guarantee replicated delivery, round robin partitioner and snappy compression. All messages are correctly sent to Kafka. The ConsumeKafka has no particular settings (no demarcator). The thing is I do not retrieve all the published messages. For each FlowFile, each JSON contains the date, I can confirm that the very first flow file is correctly published and consumed (two messages), then I have 3 FlowFiles (not consecutive) for which 2 messages are published but only one is consumed.

I don't know it that helps a lot. I'll try to look closer later in the day.

@pvillard31 Thanks for playing with it. Quick question. I don't quite understand the second point.So let me try to paraphrase it until I stumble:

You say PublishKafka publishes correctly. I am assuming you were able to verify that all messages that you have published were published. Correct?
The fist FlowFile you published with two messages is consumed by ConsumeKafka correctly. Correct?. The second FlowFile published . . . that is where I am lost in translation ;)

Just trying to understand a scenario so i can may be add a test for it.
Cheers

As far as cosmetic remarks, all addressed will push soon.

@olegz No problem ;) I was quite in a hurry and I understand why it is not clear at all.
You are correct. By dumping topic content with Kafka CLI, I can confirm that all messages are correctly published. However on 24 messages published (12 FlowFiles), only 21 have been consumed. The 3 missing messages are originating from 3 different FlowFiles. And I noticed that it was not from the first FlowFile published and it was not 3 consecutive flow files (I wanted to check the order just to be sure, it was not related to the deletion / creation of the topic).

applying the patch version of this fails.
merging this branch fails.
uto-merging nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/src/test/resources/zookeeper.properties
CONFLICT (add/add): Merge conflict in nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/src/test/resources/zookeeper.properties
Auto-merging nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/src/test/resources/server.properties
CONFLICT (add/add): Merge conflict in nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/src/test/resources/server.properties
Auto-merging nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/src/test/resources/log4j.properties
CONFLICT (add/add): Merge conflict in nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/src/test/resources/log4j.properties
Auto-merging nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafka/additionalDetails.html
CONFLICT (add/add): Merge conflict in nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.PublishKafka/additionalDetails.html
Auto-merging nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka/additionalDetails.html
CONFLICT (add/add): Merge conflict in nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/src/main/resources/docs/org.apache.nifi.processors.kafka.pubsub.ConsumeKafka/additionalDetails.html
Auto-merging nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/pom.xml
CONFLICT (add/add): Merge conflict in nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-processors/pom.xml
Auto-merging nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-nar/src/main/resources/META-INF/NOTICE
CONFLICT (add/add): Merge conflict in nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-nar/src/main/resources/META-INF/NOTICE
Auto-merging nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-nar/src/main/resources/META-INF/LICENSE
CONFLICT (add/add): Merge conflict in nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-pubsub-nar/src/main/resources/META-INF/LICENSE
Automatic merge failed; fix conflicts and then commit the result.
The logs for travis-ci show an unused import (probably fixed by now).  Please update patch to resolve merge conflicts and I'll try again.  Also, likely worthwhile to have an 0.x and a master version of this PR.

[INFO] reporting-task.css (2512b) -> reporting-task.css (1264b)[50%] -> reporting-task.css.gz (488b)[19%]
Tests run: 5, Failures: 2, Errors: 0, Skipped: 1, Time elapsed: 81.054 sec <<< FAILURE! - in org.apache.nifi.processors.kafka.pubsub.AbstractKafkaProcessorLifecycelTest
validateConcurrencyWithAllFailures(org.apache.nifi.processors.kafka.pubsub.AbstractKafkaProcessorLifecycelTest)  Time elapsed: 29.154 sec  <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.apache.nifi.processors.kafka.pubsub.AbstractKafkaProcessorLifecycelTest.validateConcurrencyWithAllFailures(AbstractKafkaProcessorLifecycelTest.java:369)
validateConcurrencyWithAllSuccesses(org.apache.nifi.processors.kafka.pubsub.AbstractKafkaProcessorLifecycelTest)  Time elapsed: 33.284 sec  <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at org.apache.nifi.processors.kafka.pubsub.AbstractKafkaProcessorLifecycelTest.validateConcurrencyWithAllSuccesses(AbstractKafkaProcessorLifecycelTest.java:291)

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 441.183 sec - in org.apache.nifi.processors.kafka.pubsub.ConsumeKafkaTest
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "main"

Am able to build now after rebasing this on top of master.  However, the ignored tests weren't just long running they were also unreliable as shown in the previous OutOfMemoryError and the preceding lifecycletest issue.  They should be made faster/more discrete/reliable.  Lots of System.out calls.  Those should use the proper logger or be removed.  There is an ignored test 'for sanity'.  Fix or remove.
This is closer but needs those items addressed before merge.

@joewitt the OOM tests are still here and running. They were not @Ignored. I've adjusted them a bit to play nice with the overall build. The @Ignored tests are only affecting the once that run with embedded Kafka which we constantly have to start/stop to run each test in isolation and that takes time. The system.out calls are only coming from one test class (3 test cases) and I kept them there for a reason, primarily to help with review process where values can be visualized by the reviewer. I do intend to remove them in the future after all are comfortable with the approach.

For the “Client ID” property help:   “Correspons” should be changed to “Corresponds”.

Reviewed and tested. LGTM. All tested flows were OK.
Few minor remarks:

I'd update @CapabilityDescription to help users differentiate Publish/Put and Consume/Get. As it stands now they will possibly wonder why we have 4 processors to deal with Kafka when listing processors from the UI.
There is a comment from @joewitt regarding the scope of close() in AbstractKafkaProcessor. Is it still an open issue?

Otherwise I'm a +1, great job!

Thanks @pvillard31! Regarding @joewitt's comment, yes it is still an outstanding issue since we need to modify ReflectionUtils to allow the invocation of non-public methods. So feel free to raise JIRA, but I am also interested what @markap14 thinks about it (allowing ReflctionUtils.invoke*** to invoke non-public methods). In any event, the close() now is implemented with required safety in place to ensure idempotency, so not a pressing issue.

@pvillard31 @olegz Just wanted to let you both know that during the demo of these new Kafka processors, it was suggested that we also update the Put and Get Kafka processor descriptions.  I filed a ticket for that:  https://issues.apache.org/jira/browse/NIFI-1889

@andrewmlim yep some of it has already been addressed, but I'd stay away from munging yet another JIRA to this one. So good point and will be reviewed and addressed once this one is merged. Do you guys agree?

i certainly agree.  this thing has to be one of the most reviewed PRs of all time.  +1 please do merge.


CAN termination GPIO support

The functionality for termination gpio is used on
some boards like ST's b-g431b-esc1 motor controller board. This feature is also supported by SocketCAN in linux.
UPD:
There is only one open question regarding implementation: Would be can_mcan API the best way to propagate this functionality to the application?

With the last commit I've added now can_term_set() function  to can.h s.t. an application can access corresponding gpis functionality if available.

I don't see a reason for a disable in the API. To be honest, I don't even see a benefit over a gpio hog. This node is the last one on the bus, it needs to enable the termination immediately or he other nodes on the bus cannot communicate. If you disable the termination, you stop the whole bus.

UPD:
There is only one open question regarding implementation: Would be can_mcan API the best way to propagate this functionality to the application?

The only useful application I see at the moment is some nonvolatile configuration check at runtime.
I it is board specific (device tree, always on) you can hard wire.

UPD:
There is only one open question regarding implementation: Would be can_mcan API the best way to propagate this functionality to the application?

The only useful application I see at the moment is some nonvolatile configuration check at runtime.
If it is board specific (device tree, always on) you can hard wire.

Thanks. It is a good point with hard-wire. I missed it. I will remove the functionality from can.h (e.g. CAN API).
I think my first implementation would be leaving it inside transceiver within init function.
But I still have a question about termination behavior: SocketCAN in Linux allows enabling/disabling CAN bus termination. I understand it is maybe not standardized CAN bus behavior. But how to handle such scenarios?

In my opinion, termination is not a property of the can controller, but from the bus. There is no need to enable/disable on a state change of the controller.

I wholeheartedly agree.

The termination is most probably not even part of the transceiver.

Again, I wholeheartedly agree.
CAN termination resistors are not physically controlled via the CAN controller, nor via the CAN transceiver (and certainly not via the group of GPIOs used for controlling a GPIO-controlled CAN transceiver, which is just a subset of the available CAN transceiver types out there).
The CAN bus termination resistors are a property of the CAN bus. If a board allows turning CAN termination resistors on/off - or even allow selecting their resistance value, which is not covered by your proposal here - that would be a function of the board, not the board's CAN controller, not the board's CAN transceiver. One way to reflect this on the board-level in Zephyr could be to use a dedicated, board-specific GPIO hog or even represent it as a GPIO-controlled regulator. Control of these resistors does not belong in the CAN controller/tranceiver APIs (I know the Linux kernel put it there, but it is misplaced, if you ask me - and Zephyr is not Linux).
@KozhinovAlexander I appreciate your eagerness in wanting to contribute to the Zephyr CAN subsystem, but I really wish you would start by opening an RFC instead of sketching up a solution based on immediate PR review comments. The RFC process often leads to a better solution and can save both your and the reviewer's time compared to the many back and forth changes, that has already happened on this PR during the last 10 hours.

Thanks for bringing it to together. I am fine with an RFC. Will do it next time first :)

@alexanderwachter @henrikbrixandersen Thank you for your time and reviews. I close this PR, since the functionality is not a part of CAN-Controller and CAN-Transceiver.


Wallet Connect attestation endpoint error

POST request errors to https://verify.walletconnect.com/attestation

It's an issue with some wallets apparently.I had a similar issue. I contacted metamask/binance directly and they had it resolved for me<EMAIL_ADDRESS>Send them a mail. They'll help you out.


Use final fields where needed.

probably just my ocd, but good to ensure variables that should not be modified to be set as final.

Not needed anymore, superseded by PR ACF.


chore(package): update webpack to version 4.1.0

Closes #154 and #158
@thallada I tried to follow as much of edx/front-end-cookie-cutter-application#11 as possible.
Let's work off of this PR since it's the latest webpack 4 version (I take that back, 4.1.1 got published yesterday #lesigh should now be updated to 4.1.1).
What's the right way to make sure our builds haven't regressed in some way? Install Paragon from this commit hash in SFE & edX Platform?
Here's an article about webpack 4 that was published by the webpack core team.

Coverage remained the same at 99.579% when pulling 3017040c3576ed1a340d7f0118e3d5800f6121d8 on greenkeeper/webpack-4.1.0 into 3f31fa844fa28d936f6091400828f2a5bc2cf97c on master.

Coverage remained the same at 99.579% when pulling 3017040c3576ed1a340d7f0118e3d5800f6121d8 on greenkeeper/webpack-4.1.0 into 3f31fa844fa28d936f6091400828f2a5bc2cf97c on master.

Just to sanity check that this works, I'd recommend installing a copy of Paragon built from this branch into edx-platform and/or SFE. @thallada suggested adding a prepare script to run npm run build -- if we do that, we can just install directly from this branch without having to check in any dist files (i.e. "paragon": "edx/paragon/greenkeeper/webpack-4.1.0")

I'm having some trouble running npm start on this branch. I think we should hold off on this change until storybook supports Webpack 4.
Once that happens. How do you all feel about using webpack-merge like we do in other projects so that we could have a separate webpack.dev.config.js, webpack.dev.config.js, and webpack.prod.config.js? I don't think we need a separate themeable and static build for development so it might speed things up a little.

Re: https://github.com/edx/paragon/pull/187, we should go straight to webpack 4.2.0.
It looks like storybook's webpack 4 support might be released as an alpha soon.

Storybook has released an alpha with Webpack 4 support to NPM https://www.npmjs.com/package/@storybook/react We can now install it by specifying "alpha" in the package.json.


Update Scripts With FC REST Updates

closes https://github.com/WIPACrepo/file-catalog-indexer/issues/31

LGTM.
Out of scope for this PR, but I wonder since we're (re)using the logical_name + query construct, if we should add a query shortcut inside the FC to mean this?

It's a good idea since we're making it a construct here. But I'm hesitant to introduce more abstraction to the query interface considering we've departed the "logical_name=locations.path" paradigm. Really, this 2-arg construct is a stop-gap measure since locations.path is not currently suitably indexed to be the sole argument. I do see the benefit of introducing a location-path shortcut key (or similar) that bypasses the "query" argument.

Note: I'm not sure if we'll ever get this version of the FC to index locations.path well. It's something that Clowder may be able to do.


set_render_target_to_screen_rect in Godot 3

Hi,
With Godot 3, it seems the set_render_target_to_screen_rect function for viewport was removed. Is there any replacement of this function, or any workaround?
I was using this function in Godot 2.x to display my pixel perfect game scaled up by integers values only, and with black bars around the viewport.

I wrote an explanation and a complete example for how you can do that in Godot 3.0:
See:
https://github.com/godotengine/godot/issues/6506#issuecomment-373068587
for the explanation, and the comment after it for the full example.

please, use https://godotengine.org/qa/ for questions.

Closing per @chanon's comment.


Getting Null reference execption errors. When clicking a some buildings after i adjusted the min/max level of "large"districts

Error:
Object reference not set to an instance of an object [System.NullReferenceException]
Details:
No details
Output log:
output_log.txt

When was this triggered (e.g. what did you do immediately beforehand)?

I drew a big district which contains hundreds of buildings, Rico and growables. Set min level to 2, max to 3. Click trigger upgrade, click trigger downgrade.
Then clicking a former level 4 building gives the error.

Hmm I did further investigation, and started a new city. There i could not reproduce the error.
So I went back to my original game, removed all districts, saved and restarted the game. sadly still errors when i click a building.. But i think its probably not related to this mod :-S
So i guess we can close?

I can't reproduce for either, but leaving this open for now - even if another mod caused the error, this mod was what threw the exception, so I want to improve this mod to better handle any unexpected situations.  There's scope for additional parameter checking in that particular method in your log, so I'll add that as a precaution against future events.

Closing as no further issues after over a year.


add contributing guidelines

Can we copy or link to Istio/istio ?

This is a dup of Issue #15.  In addition, I slightly modified what was in istio/istio as that has links to all the necessary project boilerplate.


Sweep rooms only when they're inactive

It's quite bad if the room is sweeped during the draft.
Maybe destroy rooms only when there are no event listeners connected?

Implemented in https://github.com/hithroc/oak/commit/84a5f4bff1a706fcb4c20454b402cd629179229c


Update README.md

The project should be made read-only as well. The project tags can be set to deprecated as well.


While adding resource actions component,it showing 'Cannot read params of undefined'.

Hi,
I tried to add component to new resource action, but it showing error as
"TypeError: Cannot read property 'params' of undefined
See development console for more details..."

can you paste the component code?

since there is no answer - closing this one

How can it be that when rendering an action component, we have a prop record underfined from which we take the params?
I have the same problem. If you need a code, I can add it later.
AdminBro version: 3.2.5.

Hmm, after removing .adminbro and restarting the application, this folder was created with the correct .entry.js (it now included my component import) and it worked.
Can you explain, why the .adimnbro folder was not updated?
I found a recommendation to delete this folder here https://stackoverflow.com/questions/61745264/unable-to-use-custom-componets-in-adminbro


Failed to setup error in integration

Hi,
I installed HA 2023.5 yesterday and today I noticed an error with the Magic Mirror integration.
I am running
Home Assistant 2023.5.0
Supervisor 2023.04.1
Operating System 10.1
Frontend 20230503.1 - latest
As for MM I am running the latest version and the latest version of the remote control module (no recent updates there)
In the integrations overview it shows a red exclamation point with the message Failed to setup.
Did multiple restarts of HA (incl complete system reboot) and restarts of the MM Pi.
The log gives this error.
2023-05-04 21:21:32.640 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Magic Mirror for magicmirror
File "/config/custom_components/magicmirror/init.py", line 53, in async_setup_entry
Error setting up entry Magic Mirror for magicmirror
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/magicmirror/init.py", line 53, in async_setup_entry
hass.config_entries.async_setup_platforms(entry, PLATFORMS)
AttributeError: 'ConfigEntries' object has no attribute 'async_setup_platforms'

Hi. Thanks for reporting.
I'm having some issues as well.
I released a beta-version which fixed the error you're reporting, but I'm still having issues with unavailable entities. Will look into this as soon as I have the time.

You can try updating to the latest beta, it seems to have fixed my issues. I'm going to release it pretty soon, there have been a few beta-releases now that have not reached stable because I have forgotten to release.

I downloaded the latest beta 5, did my restart but I am now getting this error
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 258, in _async_refresh
self.data = await self._async_update_data()
File "/config/custom_components/magicmirror/coordinator.py", line 61, in _async_update_data
await self.api.update_available()
File "/config/custom_components/magicmirror/api.py", line 156, in update_available
return ModuleUpdateResponses.from_dict(await self.get(API_UPDATE_AVAILABLE))
File "/config/custom_components/magicmirror/api.py", line 108, in get
return await self.handle_request(get)
File "/config/custom_components/magicmirror/api.py", line 85, in handle_request
raise Exception(f"Response not 200 OK {resp}")
Exception: Response not 200 OK <ClientResponse(http://192.xxx.xxx.xxx:8080/api/updateAvailable) [404 Not Found]>
<CIMultiDictProxy('Access-Control-Allow-Origin': '*', 'X-DNS-Prefetch-Control': 'off', 'X-Frame-Options': 'SAMEORIGIN', 'Strict-Transport-Security': 'max-age=15552000; includeSubDomains', 'X-Download-Options': 'noopen', 'X-Content-Type-Options': 'nosniff', 'X-Permitted-Cross-Domain-Policies': 'none', 'Referrer-Policy': 'no-referrer', 'X-XSS-Protection': '0', 'Content-Security-Policy': "default-src 'none'", 'Content-Type': 'text/html; charset=utf-8', 'Content-Length': '158', 'Date': 'Sat, 06 May 2023 14:46:36 GMT', 'Connection': 'keep-alive', 'Keep-Alive': 'timeout=5')>

Hi @sindrebroch
Any update on the issue?
Thanks!

@hesspoint Thanks for bumping, I forgot about this.
I forgot to mention that the beta-versions require a fork of the MMM-Remote-Control module, only mentioned in the release-notes of 1.5.0b1. I should probably make it compatible with the non-fork as well, but I probably won't have time for it in the near future. I'm guessing that is the issue here.

Hi @sindrebroch
I updated my MMM-Remote on my mirror with your fork of the repo.
Actually in the read me of the fork it still says to execute ```
bash -c "$(curl -s https://raw.githubusercontent.com/Jopyth/MMM-Remote-Control/master/installer.sh)"
I figured I needed to replace "Jopyth" with "sindrebroch" so that it pulls your fork instead of the original one, correct?

Anyhow let the install run. I denied installing the developer version though. Installed fine. After that rebooted my mirror but changed nothing else in the config.

Still the same error comes up in the HA integration.

What did I do wrong?

Thanks

I haven't really done a great job with the documentation on this, I'm sorry. It has been for my own use, so I haven't though much of it... The idea was to contribute back into Jopyth's module, but I haven't gotten to that yet.
I think the installer.sh-script will still pull the code for Jopyth's module, so personally I have done a manual install, but use the URL to my fork instead of his. Could you give that a try?
I can obviously make many improvements here, but been super busy lately, so not much time to look into it sadly.

Ok I removed the module completely and did a manual install of your fork and now it works :) Thanks for the hint.
So for now I am good again until there is a permanent fix of the integration.
Thanks for the great work you are doing as your integration allows me to e.g. shutdown my MM when I leave the house and also make the display turn on and off when my motion controlled lights do.

Just here to say thanks!
This fixed my problem like @hesspoint  said, uninstall the old module from Jopyth
git clone https://github.com/sindrebroch/MMM-Remote-Control
cd MMM-Remote-Control/
npm install


Need Help to fix this error

Go and set CNAME for both www and login subdomains and point them to your domain

Thanks it works

How to host phishlet in evilginx with private features, that will probably makes the phishing link to last for 30days

How to host phishlet in evilginx with private features, that will probably makes the phishing link to last for 30days

I'm sure you don't expect that to be shared openly here.

@biglamar01

U can write me on Telegram

@stop-robot you must be stupid how did i rip you what and how did i rip you pls post evidence you must be stupid i dont even know or have any interaction with you. If you need a service and you cant pay for it you beg for it all this blackmail wont help you.

**Hi 👽 ! If you are interested in ⚙Advanced Phishing⚙ and the ✨Evilginx3✨ tool then I offer you Google Gmail and Custom Phishlets with a ✅Free Tutorial✅ which arrives if the 📈Telegram reaches 50 Subscribers📈
⏳ GOOGLE GMAIL PHISHLET 2024 WITH PROOF ⏳
->
⛔https://www.youtube.com/watch?v=nA47UknIE6A⛔
🔓 Ask your questions and a free tutorial from 50 subs on telegram !!!
->
📩https://t.me/Noremorse1011📩**


Please edit Google colaboratory

I want to launch Web Ui with Google Collaboratory, but I can't specify the zip file directory.

You cannot run the RVC UI on colab, they seem to have started to block instances.
You can sign up to Google cloud for a trial account ($300 in free credits) and connect it to a custom runtime. I use a V100, works like a charm (:
https://research.google.com/colaboratory/marketplace.html


Theres no dist folder which causes npm not to work

Fix path of main JS file so that trumbowyg actually loads in Node

I also realized this requires scss and it requires gulp to be run to generate sprites. Is there anyway to just get CSS, or if not, at least have the sprites built. I'm using npm so I'm not sure how I'd ever be able to deploy this since I wont be able to access node_modules, install gulp, run gulp sprites, and after that then run npm install, start, etc on the main app.

Do you get tagged version? Or trying to get master?
npm need to use this: https://github.com/Alex-D/Trumbowyg/tree/2.0.0-beta.5 for version 2.0.0-beta.5
And you can see the dist folder.

OK. I need to add a .npmignore file, because it's .gitignore which is used insteed and dist folder is ignored in it. :/


Do not link new FTM2 page yet

See Albert’s 12:04a post on #general.
Please do not link from main page yet. Need lots of content edits, UX/UI designs and partners need to update data for this adaptation, thanks!!

The won't label means that the team has decided not to do the work proposed in a github issue so don't put that label on :).
What is FTM2?

Can we close this?

@saikatbhadra yes!


Fix prometheus task metrics in bridged and virtual IP mode

High-level description
This PR updates telegraf to collect metrics from the mesos agent's IP address, rather than its host's loopback address.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-5022 Prometheus task metrics don't work in bridge or virtual IP mode

Related tickets (optional)
Other tickets related to this change:

DCOS_OSS- Foo the Bar so it stops Bazzing.

Checklist for all PRs

[x] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change: there is already a changelog entry
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[x] Test Results: link to CI job test results for component
[x] Code Coverage (if available): link to code coverage report

@mesosphere-mergebot label ready for review

@branden and @gracedo , would you kindly review this when you get a moment?


2022 Alibaba Summer of Code

2022 Alibaba Summer of Code
Welcome to the open source world! If you haven't planned how to spend this summer, come to the Alibaba Summer of Code and coding with us! 💻
Alibaba Summer of Code is a global program focused on engaging students directly in open source software development. Under the guidance of the mentor in the Alibaba open source project, students can experience software development in the real world. Alibaba Summer of code will begin from May 30th to September 1st. Students can use the summertime to participate in the open source project and work with the core members of the project.
What you can get?
On this exclusive developer journey, students will have the opportunity to:
Participate in the top projects of the International Open Source Foundation;

Get a scholarship from Alibaba;

Obtain an open source contributor certificate;

Get a fast pass of Alibaba Internship/recruitment;

Get your code adopted and used by the open source project！

Our Mentor

Li Wei,@francisoliverlee,Apache RocketMQ Committer
Nicholas Jiang,@SteNicholas,Apache RocketMQ Committer
Cheng Junjie,Apache RocketMQ Committer

Apply Now!

You can click on this link to apply directly:

Apache RocketMQ Connect Sink to Apache Doris
Implement of Apache RocketMQ Flink Catalog
Implement of Apache RocketMQ Streams dispatching system

Upload your CV and project proposal via ASOC 2022 official website：ASOC2022

Timeline⏳

Contact us!
If you have any questions, visit the event website:ASOC2022
Email address<EMAIL_ADDRESS>

More features, https://shimo.im/docs/Ee32MjM69Vu9OQA2. ,and the task list will be updated from time to time.

More features, https://shimo.im/docs/Ee32MjM69Vu9OQA2. ,and the task list will be updated from time to time.

Hello，whether the projects in the documents you mentioned will eventually go online to asoc ？

More features, https://shimo.im/docs/Ee32MjM69Vu9OQA2. ,and the task list will be updated from time to time.

Hello，whether the projects in the documents you mentioned will eventually go online to asoc ？

Some topics will be officially selected by ASOC2022, and the remaining topics will be keep open in the community, which can be completed by students interested in.

更多功能，https://shimo.im/docs/Ee32MjM69Vu9OQA2。，并且任务列表会不时更新。
文档中的内容目前可以提issue认领吗

更多功能，https://shimo.im/docs/Ee32MjM69Vu9OQA2。，并且任务列表会不时更新。
文档中的内容目前可以提issue认领吗

非常欢迎， 题目列表中的可选题目都可以通过直接提交issue到对应repo。

@ShannonDing Hi, What topics have not been done in this document?

See you next year.


modulepreload is added to head without running deno task build

I just noticed in v1.5.4 that when I start my Fresh site it loads JavaScripts even though I don't have any islands. It didn't do that before?

<link rel="modulepreload" href="/_frsh/js/<hash>/plugin-twind-main.js">
<link rel="modulepreload" href="/_frsh/js/<hash>/chunk-NFMR776E.js">

Is this a bug or can I disable it somehow?

Does the site use Partials?

Nope, no islands nor partials 😅

Will this be fixed? I don't understand why these modulepreload's gets added to the <head> when the page doesn't even need them. My site works fine without loading in any JavaScript, I tested it by disabling JavaScript in the browser and everything still works and the pages loads faster.

Will this be fixed?

Yes

Awesome! 🎩  Will that be in v2.0?