Unable to import docusign-esign into App.js file. Module not Found errors. [How to set up your SPA with DocuSign]

I have a basic create-react-app application that I'm trying to import docusign into. I have run the
$ npm i docusign-esign

command to add the dependency to the project and then required the dependency as such
import React, { Component } from 'react';
import logo from './logo.svg';
import './App.css';
const docu = require('docusign-esign');

However, I'm seeing issues when this require line is included:
Module not found: 'model/EnvelopesInformation' in /Users/asrikanth/Documents/testing/my-app/node_modules/docusign-esign/src

 @ ./~/docusign-esign/src/index.js 15:4-9950

Error in ./~/docusign-esign/src/index.js
Module not found: 'model/ErrorDetails' in /Users/asrikanth/Documents/testing/my-app/node_modules/docusign-esign/src

 @ ./~/docusign-esign/src/index.js 15:4-9950

Error in ./~/docusign-esign/src/index.js
Module not found: 'model/EventNotification' in /Users/asrikanth/Documents/testing/my-app/node_modules/docusign-esign/src

 @ ./~/docusign-esign/src/index.js 15:4-9950

Error in ./~/docusign-esign/src/index.js
Module not found: 'model/EventResult' in /Users/asrikanth/Documents/testing/my-app/node_modules/docusign-esign/src

 @ ./~/docusign-esign/src/index.js 15:4-9950

Error in ./~/docusign-esign/src/index.js
Module not found: 'model/Expirations' in /Users/asrikanth/Documents/testing/my-app/node_modules/docusign-esign/src

 @ ./~/docusign-esign/src/index.js 15:4-9950

Error in ./~/docusign-esign/src/index.js
Module not found: 'model/ExternalDocServiceErrorDetails' in /Users/asrikanth/Documents/testing/my-app/node_modules/docusign-esign/src

 @ ./~/docusign-esign/src/index.js 15:4-9950

Error in ./~/docusign-esign/src/index.js
Module not found: 'model/ExternalFile' in /Users/asrikanth/Documents/testing/my-app/node_modules/docusign-esign/src

and so on with about every requirement of the docusign-esign/src/index.js file.
I did run an npm install after adding it and that doesn't fix it. How could I resolve this?

Hi @Animanny, which version of docusign-esign are you running?

I believe my package.json says 5.0.2
Yes, I've tried that to no avail. I've noticed that it works when it's not in a react-app. Is this is a known issue?

@Animanny so it appears you are importing docusign-esign into your client code. However, DocuSign doesn't not support CORS.  However, DocuSign doesn't not support CORS. We have a good article on how best to set this up for your SPA here: https://www.docusign.com/blog/dsdev-building-single-page-applications-with-docusign-and-cors-part-1/
https://www.docusign.com/blog/dsdev-building-single-page-applications-with-docusign-and-cors-part-2/

Its also a problem in backend webpack (we use aws lambda)

It is still an issue in AWS lambda build where we are also using webpack.

I have the same issue with webpack in AWS lambda


[BAT] Merge project creation fix.

Coverage increased (+7.6%) to 61.699% when pulling 1c6bdfb85192b17539d0a2cb9f78bd1e92a1f688 on wy65701436:drone into 4d465bb1275cd911b5b217096c0e567d013024f8 on vmware:drone.

Coverage remained the same at 54.079% when pulling 7aa8f90f18f065734744ccb6265b88762d67a21b on wy65701436:drone into 4d465bb1275cd911b5b217096c0e567d013024f8 on vmware:drone.


Knife animations, gloves

Has anyone fixed knife animations, and made gloves work?

some info on gloves: https://www.unknowncheats.me/forum/counter-strike-2-a/604003-change-gloves.html
don't know anything about sequences tho


Proper code Bug

Challenge Use a CSS Class to Style an Element has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

 CatPhotoApp

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

Please use help chat when you get stuck.
Happy Coding


Fail the CI build if there are any uncommitted changes

I'll only be updating cibuild.cmd so ignore the other change as I'm using it to test this.

Also print out the diff for ease of understanding :)

@dotnet-bot test Windows_NT for Desktop please

@dotnet-bot test this please


During make lint - there are lint errors they should be fixed as PR would not be accepted

lint error (make lint) - make lint gives following errors:
routers/web/admin/repos.go:83: File is not `gofumpt`-ed with `-extra` (gofumpt)

routers/web/admin/repos_test.go:26: File is not `gofumpt`-ed with `-extra` (gofumpt)

routers/web/web.go:584: File is not `gofumpt`-ed with `-extra` (gofumpt)

modules/setting/repository.go:274:34: var-naming: don't use underscores in Go names; func parameter enable_size_limit should be enableSizeLimit (revive)
func SaveGlobalRepositorySetting(enable_size_limit bool, repo_size_limit int64) error {
                                 ^
modules/setting/repository.go:271:26: var-declaration: should drop = 0 from declaration of var RepoSizeLimit; it is the zero value (revive)
    RepoSizeLimit   int64 = 0
                            ^
routers/web/admin/repos.go:52:2: var-naming: don't use underscores in Go names; var repo_size_limit should be repoSizeLimit (revive)
    repo_size_limit, err := base.GetFileSize(form.RepoSizeLimit)

Please try to follow this part of guideline it is expected we run the make lint ourselves:
https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#testing-redux
Something has been changed on gitea site so our PR doesn't run through automated tests every time. I will ask for this.
But I think project expects we run tests ourselves. For tests to be successfull you need to clone the repo every time as new and then do the:
TAGS="bindata sqlite sqlite_unlock_notify" make build
TAGS="bindata sqlite sqlite_unlock_notify" make tests
TAGS="bindata sqlite sqlite_unlock_notify" make test-sqlite
TAGS="bindata sqlite sqlite_unlock_notify" make test-e2e-sqlite

Confirmed as fixed in https://github.com/DmitryFrolovTri/gitea/commit/9e5f2fd4e3b7f91aab527c33e7aecaaba4372cda


Missing dependencies in elegantrl/train/config.py and .../run.py or Incorrect calls from finrl/agents/elegantrl/models.py

Describe the bug
missing dependencies from running main.py --mode=test with elegantrl demo settings.
File "/usr/local/lib/python3.7/site-packages/finrl/main.py", line 149, in
raise SystemExit(main())
File "/usr/local/lib/python3.7/site-packages/finrl/main.py", line 81, in main
kwargs=kwargs,
File "/usr/local/lib/python3.7/site-packages/finrl/train.py", line 49, in train
from finrl.agents.elegantrl.models import DRLAgent as DRLAgent_erl
File "/usr/local/lib/python3.7/site-packages/finrl/agents/elegantrl/models.py", line 11, in
from elegantrl.train.config import Arguments
==> ImportError: cannot import name 'Arguments' from 'elegantrl.train.config' (/usr/local/lib/python3.7/site-packages/elegantrl/train/config.py)
list of missing modules:
from elegantrl.train.config import Arguments
from elegantrl.train.run import init_agent
from elegantrl.train.run import train_and_evaluate
A clear and concise description of what the bug is:
When running main.py in test mode, code executes until calling ...agents/elegantrl/models.py from train.py. ...agents/elegantrl/models.py calls elegantrl.train.config where many arguments and initializers exist, however the referenced imports do not exist and no function/method/class takes the correct parameters from the calls.
Line 84 in agents/elegantrl/models.py referenced call for train_and_evaluate: train_and_evaluate(model)
Line 92 in agents/elegantrl/models.py referenced call for Arguments: Arguments(agent_class, env)
Line 97 in agents/elegantrl/models.py referenced call for init_agent: init_agent(args, gpu_id)
To Reproduce
Steps to reproduce the behavior:

run main.py in test mode with elegantrl as the defined drl_lib (demo settings)
See error

Expected behavior
ppo analysis
Desktop (please complete the following information):

OS: macOS Big Sur
Browser: Chrome
Version: 11.7.1 (20G918)

Additional context
No additional context to provide at this time

same issue occurs!

Does anyone know if the Config class from elegantrl.train.config is supposed to be called and not "Arguments"? The Config class takes in similar parameters and returns almost everything that's being asked of it from finrl.agents.elegantrl. If someone can help me understand what's needed or what it's trying to do, I can either build the Arguments class or append the Config class. I've edited the Config class to work with the call, but I don't know if it's executing as intended.

From what I'm seeing, it's supposed to supply the arguments for each type of model, but I may not be reading it right. Just trying to understand and contribute where possible.


Stock limit showing even when minimum stock has not been reached and adding stock fails sometimes

Describe the bug

Adding the stock was okay at first but after a while, I realized some of the stock added wasn't entered until I redid it again wonce or twice more sometimes, but it doesn't always occur so I cant exactly pinpoint the cause.
I initially added products without categories, then later added the categories and updated the products to add them to a category, after this process the minimum stock limit checker seems to have bugged out as it shows random products are in low stock even when their stock is high.

Expected behavior
Everything to work as intended, products added once successfully and stock limit to be maintained.
Actual Behavior
As described above
Environment

Operating System: Windows 10
Pharmaspot Version: 1.4.3

Hi,
I cannot replicate the issue on my end. Can you please provide a video preview of the issue?

I couldn't get a video, but I got images of how it looks.
The minimum stock for all of these is set to 5, but as you can see, even some with more than 100 in stock still complain about Low Stock


copy button is not working and file upload only works with image

Hello again,
I am using your nice app regularly now. So I have a couple of feedback an update request.

copy button is not working somehow, meaning that copy button doest copy the text or code into clipboard.
Second of all I tried to upload pdf, txt, .md, .py files in the upload sessions but I am getting error, when I try to upload image it is working.
Lastly , could you please add shortcut for clearing or deleting the current chat (like shift+del or cntr+del).

copy button part error:

I got this error
script.js?v=2.4.1:778 Uncaught TypeError: Cannot read properties of undefined (reading 'writeText')
    at HTMLButtonElement.<anonymous> (script.js?v=2.4.1:778:37)
(anonymous)	@	script.js?v=2.4.1:778
script.js?v=2.4.1:726 Uncaught TypeError: Cannot read properties of undefined (reading 'writeText')
    at HTMLButtonElement.<anonymous> (script.js?v=2.4.1:726:37)
(anonymous)	@	script.js?v=2.4.1:726

this is when I upload .py file for asking the about the code (to meta llama 3.1 from cebras)

For the copy part, I fixed it because of localhost; I followed this ==>
Chrome: You can enable the "Insecure origins treated as secure" flag in Chrome for specific URLs like http://localhost:8000.
Go to chrome://flags/ in your Chrome browser.
Search for "Insecure origins treated as secure."
Add http://localhost:8000 (or your application's URL) to the list of allowed origins.
Restart Chrome.

Hello again,
I am using your nice app regularly now. So I have a couple of feedback an update request.

copy button is not working somehow, meaning that copy button doest copy the text or code into clipboard.
Second of all I tried to upload pdf, txt, .md, .py files in the upload sessions but I am getting error, when I try to upload image it is working.
Lastly , could you please add shortcut for clearing or deleting the current chat (like shift+del or cntr+del).

copy button part error:
I got this error
script.js?v=2.4.1:778 Uncaught TypeError: Cannot read properties of undefined (reading 'writeText')
    at HTMLButtonElement.<anonymous> (script.js?v=2.4.1:778:37)
(anonymous)	@	script.js?v=2.4.1:778
script.js?v=2.4.1:726 Uncaught TypeError: Cannot read properties of undefined (reading 'writeText')
    at HTMLButtonElement.<anonymous> (script.js?v=2.4.1:726:37)
(anonymous)	@	script.js?v=2.4.1:726

this is when I upload .py file for asking the about the code (to meta llama 3.1 from cebras)

Hello Süleyman, thank you for the contribution and feedback, this will help make this interface even better.
I will check what can be done to enable the upload of other file types besides images.
Currently, only Google Gemini has the option to upload video, audio, pdf, and txt implemented; most other models do not accept these other formats. However, it is possible to convert the content to text and send the text instead of the file. I will check the possibility of implementing this soon.
You can use the shortcut Ctrl + Q´  to start a new chat without deleting the current one, and I have just implemented Ctrl + Del` as suggested, which deletes the current chat.

That's it. You can now send files other than images.
PDF is still only possible with Google Gemini.
Have a great day!


(FACT-3184) Prefer #require_relative to #require

This should have a positive performance impact for Facter on windows at
the cost of maybe less lisible code for developers.
Only the code in the /lib directory was updated, the /bin and /spec
directories are kept untouched.

Can one of the admins verify this patch?


Add basic auth handling

When a wrong password is inserted the first time, and after a retry you enter a correct password, the callback isn't valid anymore.

no longer working ... not able to sign in


Add dependabot support

Summary of Bug
Utilize dependabot to keep up to date with maven central and github action versioning.

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

closed by #46


if something is missing, provide the markdown needed to paste in to the repo to fix

Where would you do this?
This might be out of scope for this repository. It would work well with standard-readme though.

Not sure.  Sounds fine to me.  @jbenet requested originally.

I think I will be the main person doing this, and I think there are better ways to do this than to have the markdown suggested here. If anyone can come up with a really nice way of doing this, happy to rethink.


Websocket only returns type string

Hello everyone,
I have created a web socket on hyper-express (version 6.17.2) and have the issue that messages are always recognised as type 'string' while I send for example Binary data.

Is this a known issue or something related to my code?
Message send via Postman:

Backend Code
const webserver = new HyperExpress.Server();

webserver.get('/', (request, response) => {
    response.status(200).send("Hello world");
})

// WebSocket route
webserver.ws('/stream', {max_payload_length: 5 * 1024 * 1024 }, (ws) => {
    console.log('Socket connection opened.');

    ws.on('message', (message) => {
        console.log('Type of message:', typeof message); //Gives type of message
        if (Buffer.isBuffer(message)) {
            // This will check if the data is binary (received as Buffer in Node.js)
            console.log('Received binary data (Buffer):');
        } else {
            console.log('Received non-binary data:');
        }
    });
    ws.on('close', (code, reason) => {
        console.log(`WebSocket connection closed. Code: ${code}, Reason: ${reason}`);
    });
});
webserver.listen(6060)
    .then((socket) => console.log("Webserver started on port 6060"))
    .catch((error) => console.log("Failed to start webserver on port 6060"))````

Hi, please review the docs for Router and you will find that when binding Router.ws() to create a route, you can specify a message_type option alongside other route options which will dictate the type of the data.
So essentially you can change the default string parsing behavior by defining the message_type option alongside max payload length and others.


Errors during SSR

Hey!
We're using this component in a project that we render on a server.
But there is a line which triggers an error:
https://github.com/orbita-center/react-dadata-box/blob/39a98fa6950c48c7d84fbae5d15cfbb30711bb6c/src/index.js#L223
Is it possible to move it into componentDidMount? It looks like it's not used for the first render.
We would like to do it, but not sure about the status of this component. Is it still maintained?

If you have a mind about how to fix your case - make PR.
I can publish the hotfix release with it

@igoradamenko
Your transfer proposal (initialization of XMLHttpRequest to componentDidMount) will be implemented as part of #64
that's coming soon

@RUVATA, oh, thanks! I was trying to find time to implement this, but (as usually) failed 😞

@igoradamenko
implementation it turned out to be simple
and literally like you suggested.
see: src/index.js:227 on this commit 2bf5c35b8e3ecffc93f10cee1259bb3378963d55
for base logic of component this change - doesn't change anything.
If it is solve problem with SSR - this is almost free

@RUVATA, it definitely solves the problem, thanks!

@igoradamenko
at now published 1.3.7 version of react-data-box lib
I invite you to update the version of the package - and post feedback about it solves your problem or give your requested functionality

Hey @RUVATA.
We've updated to the latest version and everything works perfectly 👌
Thanks again 🐨


protect against SQL injection attacks

SqlStatement can be constructed from a std::string of arbitrary origin, which allows the possibility for SQL injection attacks, especially if any part of the query string is dependent on user input. We should prevent unsafe use of this API to the largest possible extent.
Ideally we should be only accept query strings from a trusted sources like string literals, with all untrusted values relegated to parameters as described in https://cloud.google.com/spanner/docs/sql-best-practices

It is my understanding that SQL injection attacks are from the user to the application, not the application to the library. For example, an application that doesn't use parametrized queries is vulnerable to SQL injection. The library needs to trust input from the application (otherwise it wouldn't be very usable), but the application shouldn't trust input from the user as you should always assume the user is malicious.

Ideally we should be only accept query strings from a trusted sources like string literals

Do you mean only allow string literals and not std::string or force the usage of only parametrized queries? I don't think either option would make the library very usable and the onus still falls upon the developer to minimize passing untrusted input to the library.

Correct - the idea is to make it difficult for the application developer to inadvertently pass untrusted input to the API. This does place some additional requirements on developers using the library, but the general feeling (inside Google, at least - this topic came up in an internal discussion) is that providing APIs that cannot be used unsafely is the best way to prevent these types of issues, and it's standard practice for a lot of APIs internally.
https://github.com/google/safe-html-types/blob/master/doc/safehtml-types.md is one example that's analogous to what I'm describing.

That makes sense and thanks for the example. The FromConstant function is very interesting.

FTR, one incomplete way to do this in C++ is with a class like this (https://godbolt.org/z/xr1aUx):
struct StringLiteral {
  template <std::size_t N>
  explicit StringLiteral(char const (&a)[N]) : s(a, N) {}
  std::string s;
};
...
StringLiteral s("hello");

It's incomplete because it only requires a constant character array, not specifically a string literal. Though incomplete, it's portable, and may still be useful or helpful in our library.
Additionally, there are some compiler extensions that would enforce compile-time string literals for us. The problem here is that portability may suffer. But we could look into this.
Also, there might be some way to build a compile-time string class out of something like
template <char ...>
struct StringLiteral { ... };

But this is just a guess and someone would need to work out the details (if it's possible).

There is a proposal for something similar: n4121 std::string_literal
It's from 2014 but there may be a newer or more modern incarnation of the same concept. Or if it doesn't exist, we can just implement it.

What do we think about something like this: https://github.com/googleapis/google-cloud-cpp-spanner/pull/407
As a follow-up PR, we could add some compiler-specific extension hooks to ensure even more that the arguments are compile-time strings.
It's not a 100% solution, but it encourages safe practices, and makes unsafe practices harder and fairly explicit.

Personally, I still vote for implementing the basic_string_literal class (or some other incarnation of it).
Pros:

No need for compiler-specific extension hooks
We have a self-documenting strong type
We can simply pass a string_literal around, rather than having char const (&arr)[N]

Cons:

Additional complexity
More code to maintain

Furthermore, if we are following the example of the SafeHtml library I like the idea of being explicit. So the analogue of FromConstant("this-enforces-the-string-to-be-a-compile-time-string") to something like SqlStatement sql1(string_literal{"select ...."});
There may be specific design disadvantages that I haven't thought of. Thoughts?

@remyabel so that I'm clear, are you suggesting a particular difference in implementation, or are you simply proposing that whatever we do here should be done more generically and named something like "StringLiteral" (or google::cloud::basic_string_literal or something)?

I believe your current implementation (which could be perfectly fine) accepts non-const char arrays. For example:
struct Foo {
    template <std::size_t N>
    Foo(char const (&arr)[N]) {
        static_assert(N > 0, "String literal required");
    }
};

Foo foo("test");
char c[5] = "test";
Foo foo2(c); // allowed

Using std::basic_string_literal:
struct Bar {
    template <std::size_t N>
    Bar(std::basic_string_literal<char, N> wah) {
    }
};

Bar bar(wah);
Bar bar2(c); // compiler error

Live example

The basic_string_literal example you posted also accepts non-const char arrays. See https://gcc.godbolt.org/z/6ftlVA
  char c[5] = "test";
  std::basic_string_literal<char, 5> wah = c;  // <-- compiles

That solution makes it look prettier in general though because it's using C++17 class-template argument deduction. Sadly, this library needs to support a lot of users, and most users are still using C++11, so we're stuck there.
The general mechanism used by basic_string_literal is exactly the same as the one used in PR #407. They both use a function template with a non-type template parameter to detect an array size.

The basic_string_literal example you posted also accepts non-const char arrays. See https://gcc.godbolt.org/z/6ftlVA

Good point. I missed that the compiler error for my example was for a completely different reason.

That solution makes it look prettier in general though because it's using C++17 class-template argument deduction. Sadly, this library needs to support a lot of users, and most users are still using C++11, so we're stuck there.

That's a progressive enhancement and controlled by the #ifdef. Naturally the proposal includes it in the example implementation, but we don't need it.

So it sounds like the real question for us to decide is should we give SqlStatement this constructibe-from-a-string-literal support directly, or should we factor it out into a separate StringLiteral class.
Some questions/comments to answer this:

Do we need this support anywhere else? I can't think of anywhere else we need it.

If we bake this support into SqlStatement (as #407 does), maybe we can consider making its constructor non-explicit, which seems pretty safe since it can only be implicitly constructed from string literals. The benefit of doing this is that then syntax like client.ExecuteSql("SELECT Foo from Bar") will automatically work (which we wanted int #395).

Do we need this support anywhere else? I can't think of anywhere else we need it.

Feel free to abandon the idea since I had a misunderstanding of how it would solve the problem.
Here's another question. Presumably we only accept string literals because they are compile-time constants. Would it be acceptable to disallow non-const char arrays like char disallowed[5] but allow const char allowed[5]? Example:
struct SqlStatement {
  template <std::size_t N>
  SqlStatement(char (&arr)[N]) = delete;

  template <std::size_t N>
  explicit SqlStatement(char const (&arr)[N])
      : statement_(arr, N - 1) {
    static_assert(N > 0, "String literal required");
  }

  std::string statement_;
};

int main() {
    SqlStatement s("hello");
    char disallowed[5] = "Test";
    // SqlStatement s2(disallowed);
    const char allowed[5] = "Test";
    SqlStatement s3(allowed);
    const char *disallowed2 = "test";
    // SqlStatement s4(disallowed2);
}

So it sounds like the real question for us to decide is should we give SqlStatement this constructibe-from-a-string-literal support directly, or should we factor it out into a separate StringLiteral class.

Yes.

Some questions/comments to answer this:

Do we need this support anywhere else? I can't think of anywhere else we need it.

I think we will need this for BigQuery when/if we implement that library?
There is also this crazy expression language that is used in several services and (maybe, I am not really sure) could benefit from this:
https://github.com/google/cel-spec

The decision from Spanner product folks is that the C++ library should behave like the other Cloud Spanner libraries in other languages in this regard, meaning that we should not require or go out of our way to support SQL-hardening techniques. We should support SQL queries from runtime-computed sql query strings, and not require SQL query strings from compile-time literals, etc.
Note, since we support bound parameters, that helps a bit to protect against SQL injection attacks since user-supplied parameters should be specified as a bound param, and not as part of the generated SQL query string itself.
So, at this point, there is nothing for us to do. At some point if we have an actual feature request to support SQL-injection mitigation, we can open a new issue for that request.


Update Readme to mention HotKey instance must not be de-allocated

There’s no garbage collection in Swift. It will be removed from the heap because of the automatic reference counting.

@oliverepper isn't automatic reference counting one of the many ways to do garbage collection?

@oliverepper wikipedia seems to agree with me (check the reference counting part) https://en.wikipedia.org/wiki/Garbage_collection_(computer_science)

Yes. You might be right. Haven't thought about it that way. My guess is that you're right and GC is in fact a generic term. I see it used for something opposed to ARC often, though. Maybe some compiler/language-guy can jump in here?

it doesn't matter if it is done on compile time or on runtime, if you don't manually release the items it is garbage collection

Would be nice if you linked to that instead of a screenshot. Can you do that? I think there's a distinction to be made between what is generally perceived as GC (even if technically wrong) and ARC where the programmer is involved in memory management at least with preventing retain cycles.
In the context of your pull-request I don't think that this discussion is even necessary.

Alright, I can see that I'm going against the marketing here, I'm sure a computer scientist would agree that ARC is just another way of GC, in any case, I will modify the wording a bit to please the gods


Samples in Python

Thanks for the amazing documentation. It will also be helpful if we could have more example using Python, something like  using a session/client as a global variable, that gets instantiated from the first invocation requiring the session object, which generally speaking is considered an anti-pattern in python (not sure if this applies "best practices").

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cb8d85a7-1ca3-71f4-85fb-7fb02850b60e
Version Independent ID: 3d7daee4-fd6d-0e96-299a-90b3637e6150
Content: Manage connections in Azure Functions
Content Source: articles/azure-functions/manage-connections.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Hello @ingridxinzhuo163 - Thank you for your feedback! We will review and update as appropriate.


Add Color-Stop-Position

Hello,
is it possible to add the feature with adding a color stop position to each color?
default:
['#fff', '#000', '#f0f']
optional:
[{color: '#fff', pos: 0}, {color: '#000', pos: .3}, {color: '#f0f', pos: 1}]
Thanks!

This is a good idea, I keep this in the features to add.

中文

How is your plan in adding this? If you share your idea/solution, I could try to send you a PR then.
If it's like I suggested, I could start right away :)

Oh great if you plan to add this ! :smile:.
I added you on the contributors channel on Gitter (https://gitter.im/Granim-js/Contributors).
We can talk more in details of the way to implement it.

Color-Stop-Position is now supported in V2.0.0 (#46)


remove obsolete script

Scope & Purpose
Remove an obsolete script.

[ ] :hankey: Bugfix
[ ] :pizza: New feature
[ ] :fire: Performance improvement
[x] :hammer: Refactoring/simplification

Checklist

[ ] Tests

[ ] Regression tests
[ ] C++ Unit tests
[ ] integration tests
[ ] resilience tests

[ ] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)
[ ] Backports

[ ] Backport for 3.11: -
[ ] Backport for 3.10: -
[ ] Backport for 3.9: -

Related Information

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket:
[ ] Design document:

@neunhoef stated that this script is still in use from time to time.
Closing PR as obsolete.


[Adaptive Cards > WeatherCompact.Json] - Voice over focus is moving separately on '46' and 'degree F' in 'WeatherCompact.json' card.

Test Environment:
Device: iPhone 11
iOS Version: 16.7.1
App Version: 1.0 (2.4.0-beta.<IP_ADDRESS>)
Screen Reader: Voice Over
Repro Steps:

Launch Adaptive Cards iOS application.
Home screen will appear.
Activate voice over
Navigate to "V1.5" control and select it.
Navigate to 'Scenarios' control and activate it.
Navigate to 'WeatherCompact.json' under 'Scenarios' list item and activate it.
Card will be appear.
Navigate to '46' and 'degree F'
Observe voice over issue.

Actual Result:
Voice over focus is moving separately on '46' and 'degree F' in 'WeatherCompact.json' card.
Expected Result:
Voice over focus should move together on '46' and 'degree F' in 'WeatherCompact.json' card.
Voice over should announce as '46 degree F'.
User Experience:
Voice over user will be confused if proper reading order is not followed by voice over.
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/meaningful-sequence
"Have feedback to share on Bugs ? Please help fill Trusted Tester Bug Feedback (office.com) “
https://github.com/microsoft/AdaptiveCards-Mobile/assets/95913748/b7ee393b-55f2-4596-af8a-e93dcd2e82a8

The card, by definition, contains 2 different TextBlocks for value and degree type. I can't provide a general solution for this because is correct to show the accessibility separately. Solution for this will be more on card definition.

Same issue is repro on Android Platform as well.


Simple additions

Heya
I've added in (and already testing on 1000+ servers) some vlan support plus descriptions etc..
Just noticed your feature/[blah] branch sorry.. will make sure the next PR conforms

Thank you for your contribution.
I am wondering why you have sorted the keys alphabetically.
This is also the order they appear in the config file.
So far I grouped them in an order that makes sense.

Happy to add to this role, it was much needed (personally) and makes perfect sense!
About the ordering.. absolutely no reason for me changing them, just wanted to skim the line with my eyes and be certain I didn't miss X (if that makes any sense..)
Really ansible or the interfaces format itself neither care which order (in my experience) it is.. just my OCD I guess lol


enhancement check unimplemented func in nereids

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

run buildall

run buildall

run buildall

run buildall

run buildall


Add compression level option for RocksDB checkpoint

Why are the changes needed?
Allows the user to specify the compression level of the RocksDB checkpoint for both single and multithreaded compression.
Fixes an issue where the compression level for the multithreaded compression was not being used.
Does this PR introduce any user facing changes?
Adds the property key alluxio.master.metastore.rocks.checkpoint.compression.level.
Removes the property key alluxio.master.metastore.rocks.parallel.backup.compression.level as its value was not being used.

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.8 please

alluxio-bot, cherry-pick this to branch-2.9 please


Force flush seq

Closes #228

oh, this line
https://github.com/zero-os/0-Disk/blob/master/tlog/tlogserver/server/vdisk.go#L372-L373
missed the continue, will fix it on zero-os repo


Add less linter via npx

Why?
Add a linter to ensure consistent/unified code style.
Why this less liniter?
Other linter had nicer output, but was slower and no clear name of broken rule.
Config
Different config formats supported:
.lesshintrc (no highlight by default - json)
.lesshintrc.json (json with highlight - easy to find - currently used)
.lesshintrc.y?ml
package.json
Rules
Some rules from default stylish ruleset are disabled because of heavy usage. Maybe some can be removed, but changes some styles.
https://github.com/lesshint/lesshint/blob/master/lib/linters/README.md
{
  "idSelector": false, // is used
  "importPath": false, // less path _ import stuff
  "importantRule": false, // often used and with heavy deep nesting hard to resolve
  "maxCharPerLine": false, // language & font stuff
  "propertyOrdering": false, // lot of work and not that important
  "qualifyingElement": false,
  "spaceAroundComma": false, // looks broken and complains about correct syntax
  "stringQuotes": "double", // Singlequote are the default option
  "universalSelector": false, // Do not use * usage
  "zeroUnit": "no_unit"
}

Exit codes for drone
https://github.com/lesshint/lesshint#exit-status-codes

Codecov Report

Merging #6936 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6936      +/-   ##
==========================================
- Coverage    41.4%   41.39%   -0.01%
==========================================
  Files         441      441
  Lines       59736    59736
==========================================
- Hits        24734    24730       -4
- Misses      31762    31767       +5
+ Partials     3240     3239       -1

Impacted Files
Coverage Δ

models/unit.go
62.16% <0%> (-5.41%)
:arrow_down:

routers/repo/view.go
42.02% <0%> (-1.02%)
:arrow_down:

models/repo_list.go
67.89% <0%> (+1.05%)
:arrow_up:

Continue to review full report at Codecov.

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

Good idea adding a linter. Generally, I came to prefer stylelint, maybe something we want to migrate to later.

@silverwind no problem with it. Should be easy to use a similar ruleset I tried a few linter for less (i normally work with yarn, sass and a gulp pipeline) and this one was the fastest. I searched based on links in lessc tool i found.

FYI stylelint replacement up in https://github.com/go-gitea/gitea/pull/7305.


pkg/report: deduplicate sctp "no chunks on the queues" reports

Adding such things here may also be an option:
https://github.com/google/syzkaller/blob/master/pkg/report/report.go#L143-L181
Esp if they pop up in more than 1 report. If it's just 1, then it's hard to say which is better.

Codecov Report

Merging #1071 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1071   +/-   ##
=======================================
  Coverage   67.41%   67.41%
=======================================
  Files         118      118
  Lines       20548    20548
=======================================
  Hits        13853    13853
  Misses       6051     6051
  Partials      644      644

Impacted Files
Coverage Δ

pkg/report/freebsd.go
90.24% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Add a11y tests to workflow

Description
Run accessibility tests when running the build and test workflow. The tests are and have been in the repository for a while, not sure why they weren't included in the workflow
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[x] All tests pass

[x] yarn lint
[x] yarn test-unit

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Accessibility errors will go away when #640 is merged

Converting to draft until we get guidance on how to fix a11y issues

Closing as unfinished. Please feel free to finish / reopen. Thanks!
[Catch All Triage w/ 1, 2, 3]


Workload Identity: Federated Identity Credential example is missing audience

[Enter feedback here]
The federated identity credential example here:
https://learn.microsoft.com/en-us/azure/aks/workload-identity-deploy-cluster#establish-federated-identity-credential
Is missing the required audience. I found details on what it should be here:
https://learn.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation-considerations
which says it should be: api://AzureADTokenExchange
Please update the example with this argument so it is complete.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 773aa5fa-a931-f6f1-f339-6367cef12209
Version Independent ID: 48c7d57f-55a0-5894-5379-ef7d6ed1e24d
Content: Deploy and configure an Azure Kubernetes Service (AKS) cluster with workload identity (preview) - Azure Kubernetes Service
Content Source: articles/aks/workload-identity-deploy-cluster.md
Service: azure-kubernetes-service
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@richshadman
Thanks for your feedback! We will investigate and update as appropriate.

@richshadman
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.


Validate openapi3 response at /api

As of 2018-04-05 I can't find a reliable openapi3 document schema.  When one is published use it for validation here.

Removing from Core Conformance checklist, as it can't be done now.


Dap ux enhancements

Opening this PR for internal review. Note: it depends on a peer changeset to be merged to the Noir repo (will link once I push that one)

Other than the eslint errors (which made reviewing harder than necessary), I left a question re: how does this work with existing launch.json configurations.

Oops sorry about the linting, I didn't know there was a project linter (I should have!) and I didn't stick around the PR long enough to see all those horrible messages 🙈


bash build_paddle.sh fails

Hey team,
I'm trying to build on MAC OS Monterey Version 12.5, but it fails with this message:
2261.4 Scanning dependencies of target strided_slice_grad_kernel_base
2261.5 [ 13%] Building CXX object paddle/phi/kernels/CMakeFiles/strided_slice_grad_kernel_base.dir/cpu/strided_slice_grad_kernel.cc.o
2271.4 [ 13%] Linking CXX static library libtemporal_shift_grad_kernel.a
2271.5 [ 13%] Built target temporal_shift_grad_kernel
2271.5 [ 13%] Building CUDA object paddle/phi/kernels/CMakeFiles/strided_slice_grad_kernel_base.dir/gpu/strided_slice_grad_kernel.cu.o
2292.2 /tmp/nvcc-lazy-build.KEVGwZ3b/build.sh.pre: line 18: 56852 Killed                  cicc --c++14 --gnu_version=90300 -w --orig_src_file_name "/opt/tritonserver/Paddle/paddle/phi/kernels/gpu/strided_slice_grad_kernel.cu" --allow_managed --extended-lambda --relaxed_constexpr -arch compute_86 -m64 --no-version-ident -ftz=0 -prec_div=1 -prec_sqrt=1 -fmad=1 --include_file_name "strided_slice_grad_kernel.fatbin.c" -tused --gen_module_id_file --module_id_file_name "/tmp/nvcc-lazy-build.KEVGwZ3b/strided_slice_grad_kernel.module_id" --gen_c_file_name "/tmp/nvcc-lazy-build.KEVGwZ3b/strided_slice_grad_kernel.compute_86.cudafe1.c" --stub_file_name "/tmp/nvcc-lazy-build.KEVGwZ3b/strided_slice_grad_kernel.compute_86.cudafe1.stub.c" --gen_device_file_name "/tmp/nvcc-lazy-build.KEVGwZ3b/strided_slice_grad_kernel.compute_86.cudafe1.gpu" "/tmp/nvcc-lazy-build.KEVGwZ3b/strided_slice_grad_kernel.compute_86.cpp1.ii" -o "/tmp/nvcc-lazy-build.KEVGwZ3b/strided_slice_grad_kernel.compute_86.ptx"
2292.2 make[2]: *** [paddle/phi/kernels/CMakeFiles/strided_slice_grad_kernel_base.dir/build.make:76: paddle/phi/kernels/CMakeFiles/strided_slice_grad_kernel_base.dir/gpu/strided_slice_grad_kernel.cu.o] Error 137
2292.2 make[2]: *** Waiting for unfinished jobs....
2293.2 Scanning dependencies of target stack_grad_kernel
2293.2 [ 13%] Building CXX object paddle/phi/kernels/CMakeFiles/stack_grad_kernel.dir/cpu/stack_grad_kernel.cc.o
2294.5 [ 13%] Building CUDA object paddle/phi/kernels/CMakeFiles/strided_slice_kernel_base.dir/gpu/strided_slice_kernel.cu.o
2301.4 make[1]: *** [CMakeFiles/Makefile2:16722: paddle/phi/kernels/CMakeFiles/strided_slice_grad_kernel_base.dir/all] Error 2
2301.4 make[1]: *** Waiting for unfinished jobs....
2301.4 [ 13%] Building CUDA object paddle/phi/kernels/CMakeFiles/stack_grad_kernel.dir/gpu/stack_grad_kernel.cu.o
2319.8 [ 13%] Linking CXX static library libtile_kernel.a
2319.9 [ 13%] Built target tile_kernel
2320.0 [ 13%] Linking CXX static library libtop_k_grad_kernel.a
2320.1 [ 13%] Built target top_k_grad_kernel
2339.7 [ 13%] Linking CXX static library libdropout_grad_kernel.a
2339.8 [ 13%] Built target dropout_grad_kernel
2344.6 [ 13%] Linking CXX static library libstack_grad_kernel.a
2344.6 [ 13%] Built target stack_grad_kernel
2394.0 [ 13%] Linking CXX static library libtrace_kernel.a
2394.1 [ 13%] Built target trace_kernel
2448.2 [ 13%] Linking CXX static library libstrided_slice_kernel_base.a
2448.3 [ 13%] Built target strided_slice_kernel_base
2479.7 [ 13%] Linking CXX static library libtranspose_kernel.a
2479.8 [ 13%] Built target transpose_kernel
2479.9 make: *** [Makefile:130: all] Error 2
executor failed running [/bin/sh -c python3 -m pip install pyyaml && mkdir build-env &&     cd build-env &&     cmake .. -DWITH_PYTHON=OFF              -DWITH_GPU=ON              -DWITH_TESTING=OFF              -DWITH_INFERENCE_API_TEST=OFF              -DCMAKE_BUILD_TYPE=Release              -DCUDA_ARCH_NAME=Auto              -DON_INFER=ON              -DWITH_MKL=ON              -DWITH_TENSORRT=ON              -DWITH_ONNXRUNTIME=ON              -DCMAKE_C_COMPILER=which gcc-8 -DCMAKE_CXX_COMPILER=which g++-8 &&     make -jnproc]: exit code: 2
It seems to me the "cmake" command cause the problem, any idea on how to fix this?

I'm sorry we didn't test and support it on Mac OS.
Usually Mac OS does not have  GPU, you can try to modify the cmake instruction:
RUN python3 -m pip install pyyaml && mkdir build-env && \
    cd build-env && \
    cmake ..
I tried setting "DWITH_GPU=OFF" and the build finished successfully! Cheers!
However when I tried the next step:
$ bash scripts/build_paddle_backend.sh
It fails with
(paddle_env) user@user-MBP paddlepaddle_backend % bash scripts/launch_triton_server.sh

docker build -t tritonserver-paddle .
[+] Building 52.7s (4/4) FINISHED
=> [internal] load build definition from Dockerfile                                                                                0.0s
=> => transferring dockerfile: 3.50kB                                                                                0.0s
=> [internal] load .dockerignore                                                                                0.0s
=> => transferring context: 2B                                                                                0.0s
=> ERROR [internal] load metadata for nvcr.io/nvidia/tritonserver:21.10-py3-min                                                                                52.4s
=> ERROR [internal] load metadata for nvcr.io/nvidia/tritonserver:21.10-py3                                                                                52.6s

[internal] load metadata for nvcr.io/nvidia/tritonserver:21.10-py3-min:

[internal] load metadata for nvcr.io/nvidia/tritonserver:21.10-py3:

failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to authorize: rpc error: code = Unknown desc = failed to fetch anonymous token: unexpected status: 401 Unauthorized
It seems to have something to do with nvidia again. Should I modify the build_paddle_backend.sh script to ignore GPU accordingly?

@bdeng3  Yes!
Error running 'bash scripts/launch_triton_server.sh'  script, or  'bash scripts/build_paddle_backend.sh' script?
Example:
https://github.com/triton-inference-server/paddlepaddle_backend/blob/a27ff0ccb49edc2b2dc72612d69a037247c0d657/Dockerfile#L46  .It needs to be modified back to:
&& python3 -m pip install paddlepaddle paddlenlp faster_tokenizer

The launch_triton_server.sh script has GPU parameters:
delet  '--gpus=all'

@bdeng3
Could you please describe your requirements and usage scenarios?
I can compile a Mac OS image for you, but it's worth noting that we haven't done all the build tests yet.

@heliqi Thank you for the detailed explanation!
Sure. I need to deploy the open-source PaddleOCR models to the triton server. Specifically, the en_PP-OCRv3_det_infer, ch_ppocr_mobile_v2.0_cls_infer and en_PP-OCRv3_rec_infer models provided here.
I'm very new to triton so I'm not exactly sure how to do it. I tried a couple of ways:

Convert those models from pdmodel format into ONNX and pull a docker image of Triton inference server from here. This seems to be the most straightforward way, but I got the following errors when I did docker run .... My assumption is I didn't write the config.pbtxt correctly for those models.

Another way I've tried is trying to build the Paddle Backend in this repo by following the README instructions.

Even now I'm not sure which way is the best approach to solve this problem. Both seem legit to me. It would be great if you could share some high-level suggestions on how to deploy a paddle model to Triton server. Thank you!!

Are you deploying the model on Mac OS, not Linux?
Currently Paddle only provides a way to start the Triton service based on Docker. You can try pulling the image and starting the service:
# pull image
docker pull paddlepaddle/triton_paddle:21.10

# run docker (The directory to which the disk is mounted needs to be modified)
ocker run -it   --net=host --name paddle_triton --rm  -v  /path/to/models :models   paddlepaddle/triton_paddle:21.10 bash

# start service
/opt/tritonserver/bin/tritonserver  --model-repository=models

Documentation for Triton and Paddle Backend:
Triton model repository
Triton model configuration
Paddle model configuration
If use Paddle Backend, the model names in the edition subdirectories under the Models directory must be model.pdmodeland model.pdiparams.
Example:
models
  └── ResNet50
      ├── 1
      │   ├── model.pdiparams
      │   └── model.pdmodel
      └── config.pbtxt

Eventually we'll deploy to model on a Linux server, but currently I'm trying it out locally just to see how things work.
Sure. I'll try what you recommended (paddle backend) and see how things go. Just curious, are you recommending against converting the model into ONNX and deploying it?

Since Mac OS is not very Docker friendly, I urge you to try it directly on a LInux server.
I recommend using Paddle Backend directly unless you do not meet your requirements. Converting to ONNX format can introduce other errors, such as conversion failure, precision misalignment, and so on...

@bdeng3  If Paddle Backend does not meet the requirements, you can convert the model to ONNX format using Paddle2onnx, then use ONNXRuntime Backend.

/opt/tritonserver/bin/tritonserver  --model-repository=models

When I run the command above, I can see the ONNX backend is being initialized. I made sure backend: "paddle" is set in the model configuration file. I also tried restarting the docker and running again, but that doesn't help either.
I attached the output below:

use nvidia-smi and check whether the driver version matches.
The Triton image requires the driver version:  Nvidia Docs

For some reason I have to stick with trying it out locally on my Mac, so we don't really have GPU. Other warning messages in the screenshot above such as DCGM unable to start: DCGM initialization error also seem to be related to GPU. Is it possible it is because of paddlepaddle/triton_paddle:21.10 image is just for CPU?
Attached the config.pbtxt file below:
===================================
name: "ch_ppocr_mobile_v2.0_cls_infer"
platform: "paddle"
max_batch_size : 1
input [
{
name: "data_0"
data_type: TYPE_FP32
format: FORMAT_NCHW
dims: [ 3, 32, 100 ]
}
]
output [
{
name: "output"
data_type: TYPE_FP32
dims: [ -1, 2 ]
}
]
===================================
name: "en_PP-OCRv3_det_infer"
platform: "paddle"
max_batch_size : 1
input [
{
name: "data_0"
data_type: TYPE_FP32
format: FORMAT_NCHW
dims: [ 3, 960, 960 ]
}
]
output [
{
name: "output"
data_type: TYPE_FP32
dims: [ -1, 1, 960, 960 ]
}
]
===================================
name: "en_PP-OCRv3_rec_infer"
platform: "paddle"
max_batch_size : 1
input [
{
name: "data_0"
data_type: TYPE_FP32
format: FORMAT_NCHW
dims: [3, 48, -1]
}
]
output [
{
name: "output"
data_type: TYPE_FP32
dims: [ -1, -1, 97 ]
}
]

"platform"  must be changed to "backend".
Pay attention to this example:
name: "ResNet50-v1.5"
backend: "paddle"
max_batch_size: 64

input [
  {
    name: "x0"
    data_type: TYPE_FP32
    dims: [ 3, 224, 224 ]
  }
]

output [
  {
    name: "save_infer_model/scale_0.tmp_1"
    data_type: TYPE_FP32
    dims: [ 1000 ]
  }
]

instance_group [
  {
    count: 1
    kind: KIND_CPU
  }
]

My bad! after changing "platform" to "backend", it seems to be working! I'll do more experiments and see if everything works as expected! Great thanks for your support!!

However when I ran curl -v localhost:8000/v2/health/ready as suggested here to verify triton is running smoothly, Connection refused.

Is this expected since we do not exactly follow the steps in the README? I'll follow the examples in the repo to see how can we send images to triton server and get the results

@bdeng3  Check your client and be sure to close the proxy.


Running the model without GPU

Hello,
I just want to run the trained model on the dataset to see how it performs. Is it possible to do that without a GPU. I downloaded the weights and put it in a folder and ran the following command:
python tools/test_lanenet.py --weight_path weights/ --image_path ./data/tusimple_test_image/0.jpg
However, I get an error no module tensorflow and I cannot download it because I do not have a gpu.
Is it possible to test the model without a GPU. Please let me know,
Thank you,
Haritha

@aghari19 you may install a cpu version of tensorflow:)

Thank you! I was able to test with one image and the algorithm works as expected. I am currently running the command provided in the readme for a single image. Is there a way I can run it on a folder of images and save the outputs to a folder.
Please let me know,
Thanks,

@aghari19 You may have to modified the code urself:)

Got it! Thank you for all the help!


Make consistent table column widths

Added explicit width values for first and second
table columns corresponding to "Recipe" and "Crates".
Please note that this is a broad CSS style for all tables
which will break any non TOC tables.
For a cleaner solution we would need to explicitly
add class attribute to the generated HTML.
resolves: https://github.com/brson/rust-cookbook/issues/42

Thank you!


Consistently use extensions/v1beta1 for ingress and hide warnings

networking v1 doesn't work for clusters <1.18 and extensions v1beta1 is
removed in 1.22. No need to show warning to the Epinio users. We will
handle this when 1.22 it out.
Fixes #188, #200 (and others ?)
When 1.22 is out we can say we no longer care about <1.18 and switch everything to networking/v1

No more warnings:
~/workspace/epinio (hide_kube_warnings)*$ ./dist/epinio-linux-amd64 apps list

🚢 Listing applications
Organization: workspace

✔  Epinio Applications:
|  NAME  | STATUS |                ROUTES                | SERVICES |
|--------|--------|--------------------------------------|----------|
| sample | 1/1    | sample.<IP_ADDRESS>.omg.howdoi.website |          |
~/workspace/epinio (hide_kube_warnings)*$

docs: https://kubernetes.io/blog/2020/09/03/warnings/#customize-client-handling


French Translation

I translated the plugin to french, hope I did everything right :)

Thanks for translation!


Upgrade to vsc 1.49 and fix nyc compile error

#14406 introduced a nyc compiler error resulting from importing two proposed API interfaces from 'vscode' instead of 'vscode.proposed.d.ts'. Additionally, the proposed API for contributing to the debug context menu was introduced in https://code.visualstudio.com/updates/v1_49#_contributable-context-menu-for-variables-view.

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[ ] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).
[ ] The wiki is updated with any design decisions/details.

Codecov Report

Merging #14455 into main will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #14455      +/-   ##
==========================================
- Coverage   59.19%   59.16%   -0.03%
==========================================
  Files         720      720
  Lines       40211    40211
  Branches     5829     5829
==========================================
- Hits        23802    23791      -11
- Misses      15147    15156       +9
- Partials     1262     1264       +2

Impacted Files
Coverage Δ

...ience/interactive-common/interactiveWindowTypes.ts
100.00% <ø> (ø)

.../pythonEnvironments/common/externalDependencies.ts
56.41% <0.00%> (-10.26%)
:arrow_down:

src/client/common/utils/platform.ts
64.00% <0.00%> (-4.00%)
:arrow_down:

src/client/linters/pylint.ts
94.82% <0.00%> (-3.45%)
:arrow_down:

...covery/locators/services/posixKnownPathsLocator.ts
97.43% <0.00%> (-2.57%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
75.38% <0.00%> (-1.54%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

Continue to review full report at Codecov.

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

Doing this in #14460 due to https://github.com/microsoft/vscode-python/pull/14460#issuecomment-713771134


Wrong photo selected with PickPhotoAsync

Hello,
There's an issue after selecting an image from the gallery on Android 5.1.1 (Genymotion), its seems to store the temp file with another image resource than the selected. This doesn't happen neither on ios nor in previous versions of Android
I'm using the 2.1.2 version of he plugin.media.

where are you seeing the image temp file? I haven't had any issues from what I can see and the correct image is displayed for me.

Hello,
When i select the image, it returns me the wrong filename (It has the filename of another image).
Note that this happens just in genymotion and could be an emulator issue.

I would assume yes that it is a genymotion issue. Can you try on a real device or a different simulator?
Never trust an emulator :)

I couldn't reproduce this behaviour yet on a real device, however it happens very often on genymotion.
I will give you some feedback if this issue appears on another platform.
Let's assume that the issue it's due to genymotion.
Thank you for your response.

Sounds good :) will close


can you add a function that can gen code?

node-red is very fantastic,but i found it just run in itself,so i want to kown whether it can gen code and save as a bin or model package that can run in nodejs?

No, that isn't something it can do. We have no plans for it to be able to do that either.
For general questions like this, please use the mailing list, linked to from the bottom of nodered.org.
Thanks!


closes #99

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@AlcibiadesCleinias should this be closed with the issue?

https://github.com/fluencelabs/fRPC-Substrate/pull/100#issuecomment-1752502043
sure, was my misunderstanding in what npm repo it is expected from us to press npm i


Fix up services support in cookiecutters

This is a general fixup of the cookiecutter's services support which currently isn't very good on main. I think this should make it good enough to handle the services and DB needs of our various projects.
The immediate motivation for this is to allow https://github.com/hypothesis/data-tasks to have Postgres as a Docker Compose and GitHub Actions service generated by the cookiecutter (see https://github.com/hypothesis/data-tasks/pull/5).
This work should also be useful in the near future when applying the cookiecutter to apps that have services like h, LMS, and Checkmate.
Examples:
Draft PRs based on this branch that add services to various projects:

https://github.com/hypothesis/cookiecutter-pyramid-app-test/pull/42
https://github.com/hypothesis/cookiecutter-pyapp-test/pull/5
https://github.com/hypothesis/cookiecutter-pypackage-test/pull/27
https://github.com/hypothesis/data-tasks/pull/5

Testing
Generate a Pyramid app with a DB:
cookiecutter gh:hypothesis/cookiecutters --checkout fix-services-support --directory pyramid-app --no-input db=yes

Test our various commands like make services, make sql, and make sure. Try adding .cookiecutter/includes/docker-compose/postgres.yml, .cookiecutter/includes/docker-compose/services.yml, .cookiecutter/includes/docker-compose/tail.yml, and .cookiecutter/includes/.github/workflows/ci/services.yml files and running make template checkout=fix-services-support and looking at the results.
Notes

A project can put "db": "yes" in cookiecutter.json and this will cause a docker-compose.yml file with a Postgres service to be generated, a make services command to be added to Makefile, a services section with a Postgres service to be added to ci.yml, etc. This works for both apps and packages, so packages like data-tasks can have services as well.
__db_port in cookiecutter.json can be used to customise the Postgres port
__postgres_version in cookiecutter.json can be used to customise the Postgres version
docker-compose.yml can be customised using three raw text includes:

docker-compose/postgres.yml, for adding extra lines to the bottom of the Postgres service definition. For example h and LMS stuff have network stuff here.
docker-compose/services.yml, for adding extra lines to the bottom of the services section of docker-compose.yml. For example to add non-Postgres services that the cookiecutter doesn't know anything in particular about, like Elasticsearch and RabbitMQ.
docker-compose/tail.yml, for adding extra lines to the very bottom of the docker-compose.yml file. For example h and LMS have some networking stuff here.

Similarly the services section in ci.yml can be customised with a raw text .github/workflows/ci/services.yml include.

It's tempting to try to define all the services once in a services.json include and have that JSON data be used by both the docker-compose.yml and ci.yml templates. But I think this would be quite difficult to do. The services sections in docker-compose.yml and ci.yml can contain all kinds of arbitrary YAML data including resursively nested dicts and lists (with increasing indentation) and who knows what else that Docker Compose and GitHub Actions might support (YAML is a hell of a thing). I think we might have to write some fairly hardcore recursive Jinja2 code to render an arbitrary and potentially arbitrarily nested services.json file to YAML. And we'd have to write that Jinja2 code twice since with cookiecutter there's no way to share template code between the docker-compose.yml and ci.yml templates. We may also run into issues with JSON being unable to express things that can be expressed in the much more complicated YAML.

Sorry for such a long comment, but I think it's worth trying our best to get this as right as is reasonable before it's in 25 projects and we can't face getting it back out.

For what it's worth the changes in this PR will only effect projects that use services: just a few mostly test projects at first, several projects in the longer run. Currently there are draft PRs to add services to the three test projects (https://github.com/hypothesis/cookiecutter-pyramid-app-test/pull/42, https://github.com/hypothesis/cookiecutter-pyapp-test/pull/5 and https://github.com/hypothesis/cookiecutter-pypackage-test/pull/27) and to data-tasks (https://github.com/hypothesis/data-tasks/pull/5). That's all for now. As we roll the cookiecutter out to our applications, those applications that use services will make use of the feature in this PR. But other projects won't be affected.

I've no doubt this would work, but I'm a little unclear which specific problem we are trying to solve over what went before. The description says it's for a few things simultaneously and I'm not sure what the focus is.

It might be worth clarifying what's currently on main. I'll edit the PR description to make this clearer. main currently doesn't have working services or DB support, and what this PR does is add services and DB support that should be good enough to meet the services and DB needs of our projects (including our apps when the cookiecutter gets applied to them).
data-tasks can't use the cookiecutter's db option on main to add a DB to that project because the db option on main only works with the pyapp and pyramid-app cookiecutters not pypackage. On main the cookiecutter can't be applied to projects like h, LMS, Checkmate etc that have non-Postgres services because there's no way to include non-Postgres services in docker-compose.yml or ci.yml.
This PR makes it so that all those projects can use the cookiecutter and have the services they need

A quick word about the YAML formatting: I think pasting in text is a totally fine way to go (it's what we do for most other things), but I think if we wanted a JSON file that rendered out as YAML we wouldn't bother writing a converter in jinja2, we'd use a serializer and splat out the output. This means the JSON would be 1:1 with the output YAML except... why bother? If we aren't going to map it, why not store the YAML as YAML as we do here and treat it as text? One answer is we could use the same data differently in another context (e.g. for ports), but then you are tied to the first format you chose. Anywho...

I'm not sure what's being suggested here. How could we serialize a JSON file into YAML without converting JSON to YAML? You're saying we'd find an off-the-shelf JSON→YAML library and use that?
Unfortunately the cookiecutter can't generally use third-party libraries. The way that cookiecutters are used is that the user installs cookiecutter (e.g. pipx install cookiecutter), the user runs a command like cookiecutter gh:hypothesis/cookiecutters --directory pyapp, and then the various Python files in our cookiecutters (like post_gen_project.py and local_extensions.py) get run by cookiecutter in cookiecutter's Python environment (for example ~/.local/pipx/venvs/cookiecutter if you installed cookiecutter with pipx). cookiecutter is the only Python package that is installed in this venv (well, plus whatever cookiecutter itself depends on which isn't much). Our cookiecutter is just a template not a Python package. There's no way for it to declare dependencies on Python packages from PyPI.
So we're limited to the standard library which I don't think contains any YAML parser or serializer.
I think there are actually a couple of ways that we could get around this limitation but I don't it'd be worth it.

Is Postgres a special case, or just another service?
One thing that jumped out at me is that we separate out Postgres for special treatment. Is this something that we could / should treat as a generic "service"?
I think the answer is yes but we might want to extend the treatment to others...

Yes. We absolutely want to single-out Postgres for special treatment as there's much more to it than just the Docker Compose service itself. There's make sql, there are scripts for creating the test DBs that get called automatically, there's CI support, etc. It would be an absolute pain for each Postgres-using project is the cookiecutter didn't have special Postgres support.
Yes also to we might want to extend the treatment to others with emphasis on the might. I think we could add boolean cookiecutter.json options for other services that we have multiple projects using like elasticsearch (although actually only h uses that) or rabbitmq or nginx. On the other hand if these other services don't need as much boilerplate (outside of the docker-compose.yml file itself) then maybe it's not worth it. We'll see.

What I'm wondering is how we would onboard other services that did become standard to be more like the way we treat Postgres? I have some ideas for this:

Instead of db=yes and other files we could have services=postgres,nginx,elasticsearch
This way our test changes from if db == 'yes' to if 'postgres' in services (treated as a list not a string somehow)

You can't put actual lists in cookiecutter.json unfortunately because cookiecutter interprets them as choice variables (so it'll make the user choose one of postgres, nginx or elasticsearch to be the value of the services option). What you can do though is have a cookiecutter.json option whose value is a CSV string. This is what we do with the python_versions option. Then we have a python_versions() function (available to templates globally) that parses the CSV and returns the Python versions as a list of strings (or in fact a list of custom PythonVersion objects in this case).
So we'd have to do the same thing for services and have a global services() function and it'd be {% if "postgres" in services() %}.

Our check for whether we have services at all becomes if services

This would actually have to be {% if cookiecutter.get("services") %} if you want to treat the raw services CSV string as a boolean (probably not a good idea because things like whitespace-only strings would be truthy) or {% if services() %} if you want use the list of strings from the custom services() function I mentioned above. This PR currently has {% if has_services() %}.

We could have .cookiecutter/includes/docker-compose/service/<service_name>.yml (and maybe <service_name>-tail.yml?)

Yep. That's what we have currently for Postgres (.cookiecutter/includes/docker-compose/postgres.yml) so I think we'd add the same for any other services that we added specific support for.

I think I'd prefer sticking with the current db=yes boolean option (although I should probably rename it to postgres=yes) and then adding more boolean options like elasticsearch=yes if we want to in future. For a few reasons:

Currently a CSV services="postgres" option would be weird because it would ostensibly be a list of comma-separated service names but in fact "postgres" is the only possible valid value. This may not be a temporary situation: I think it's entirely likely that Postgres will be the only service that we ever add support for

It's simpler, not requiring the CSV parsing or a custom services() function. Writing {% if cookiecutter.get("db") == "yes" %} all the time is quite awkward, we could wrap that in a global boolean function db() if we wanted the template code to be a bit nicer

There's less potential for invalid values. The value of the "db" option is either "yes" (interpreted as truthy) or anything else is considered falsey. (If we want that to be a bit more forgiving about the exact string value then we should add the aforementioned db() function.) A CSV string on the other hand can be invalid CSV or it can be valid CSV but get some of the service names wrong: elastic_search instead of elasticsearch, or putting redis in there when we don't actually support Redis, etc. We might end up wanting to write validation code for it.

I think boolean options work better with the cookiecutter.json file, discoverability, and cookiecutter's interactive interface.
You can look in any project's cookiecutter.json file and see that there's an option called "db" that is set to "no", and you can just change that to "yes" and then re-run make template. This is better than seeing a "services" option whose value is "" and having no idea that the value should be a CSV string or what service names are valid to put in there.
When you run cookiecutter to create a new project it presents you with the interactive choices no or yes for the db option:
Select db:
1 - no
2 - yes
Choose from 1, 2 [1]:

This is the same as what it does for several other boolean options that the cookiecutter has. It's not possible to choose an invalid value. Also if you use cookiecutter's command line interface (cookiecutter gh:hypothesis/cookiecutters --directory pyramid-app --no-input db=yes) then it validates for us that the value of db is either yes or no.
This is better than it asking the user to type in a comma-separated list of service names and the user having no way of knowing that they should enter a CSV string or what the valid service names are. We could try to give them a clue by having a default value like postgres,elasticsearch,rabbitmq,nginx but that would force the user to delete all those if they don't want all those services and the default (for example if you just run cookiecutter gh:hypothesis/cookiecutters --directory pyramid-app --no-input) would be to turn on all the services. With our current boolean value the default is always no: you get a minimal project by default and can opt-in to each optional feature.

Putting these together will help with discoverabilty
At the moment, if you generated a project without Elasticsearch and wanted to add it, there's a steep wall to working out what to do. You might look in the cookie cutter config, but there's nothing there. When you compare the two files from a project with or without services, there's no difference you can spot. You might look in the includes directory, but there's nothing there either.

I think there's a misunderstanding here FWIW. You'll see "db": "no" in cookiecutter.json and just change that to "yes" and re-run make services. When creating a new project cookiecutter's interactive interface will ask you whether you want db to be yes or no. If we add a similar elasticsearch boolean in future it'll work the same way.

The correct thing to do is touch .cookiecutter/includes/docker-compose/services.yml to turn it on, which is a big leap.

I think this is the misunderstanding. You don't need to have a services.yml include in order to have services (to have a docker-compose.yml file etc). You just need to set "db" to "yes". But if you do have a services.yml then that will turn on the docker-compose.yml file even if "db" is not "yes". What the two services.yml includes are for is: adding services that the cookiecutter knows nothing about. Which currently is any services other than Postgres. services.yml is just a way for the project to inject arbitrary text into the docker-compose.yml file. The cookiecutter has certain things that it can do for you (like Postgres) and then if you want to add some arbitrary docker-compose.yml text of your own (whether that's to add more services or anything else) you can use the includes to do so.

Imagine this experience instead: When you look in your cookie cutter config file you see services=. If you compare this with h you see services=postres,elasticsearch,rabbit so you guess it's services=elasticsearch.

I think this is actually less discoverable than seeing "postgres": "no", "elasticsearch": "no" and "rabbitmq": "no" in your project's cookiecutter.json and just having to change them to "yes" (and also cookiecutter's interactive interface presenting you with the three boolean options when creating new projects).

Ok, I think I've gone through all of the points raised here.
I'm gonna rename the db option to postgres as I think that's a better name and matches with the __postgres_version and __postgres_port options. Then I'll merge this.
I think a lot of the discussion is beyond the scope of this PR (e.g. talking about the general mechanism of how include() works etc). I've enabled GitHub Discussions on this repo so we can have a place to discuss things like this: https://github.com/hypothesis/cookiecutters/discussions
I think the main suggestion that's within the scope of this PR is to change the "db": "yes" boolean into a "services": "postgres"list. But I think that suggestion may be based on a misunderstanding that it's necessary to have an include file to enable the services feature, rather than just setting"db"to"yes"`. I think the boolean options are better, some notes in this comment: https://github.com/hypothesis/cookiecutters/pull/97#issuecomment-1351694995


feat(utils): use vim.system for running process if available

Use the new vim.system() API on neovim 0.10 or higher, in place of
vim.fn.system(). It's more performant by using libuv (vim.loop),
though only slightly and known to have less glitches.

Two remarks:

The use_lua_io parameter is actually not being used, and it even doesn't work! Note the line cmd == "string" (not `type(cmd) == "string").

I find this implementation is vulnerable to injection, and no longer used. This was introduced in #126 for speed concerns, but we never use given "shell" cmdline (actually we should never use it), how about removing this completely? It's an internal utility so it would be fine.

You might wonder why I wanted to have this feature in the first place, given that vim.fn.system({"cmd", "--args"}) just works. Well, actually there are some subtle glitches of neovim: when vim.fn.system() is running, it may have some unwanted effects on TUI. For example, the cursor blinks on startup if vim.fn.system() is being called during initialization (what a weird bug).

See this GIF; the cursor blinks during plugin initialization, when fzf-lua.utils.git_version() is called:
This is some bug that might have to be fixed on neovim core, but since the bug is around in neovim 0.9.x stable, it'd be good to have some fix on fzf-lua's side too. Actually vim.system() should be always preferred if available in neovim 0.10+.
Somehow this doesn't happen with the new libUV-based vim.system implementation.

Ty @wookayin, this is great, I had no idea about this change, I also much prefer a libuv based solution.

The use_lua_io parameter is actually not being used and it even doesn't work! Note the line cmd == "string" (not type(cmd) == "string").

I agree, this can be safely removed, it was never used (as you astutely pointed out) and the concern for performance raised in #126 turned out of be a different issue.
As for removing it, we can add it to this PR, have a new PR or I can remove it myself tomorrow - whichever you prefer, lmk.

You might wonder why I wanted to have this feature in the first place

ty for this explanation!

I think it'd be better to address here together. Hope I didn't break anything lol

I think it'd be better to address here together.

Looks great @wookayin, much better without the never actually used code :)

Hope I didn't break anything lol

We’ee about to find out since I’m merging it rn :)


Library import<PHONE_NUMBER>

PR was created by workflow 'FIXME: workflow_id_here'

The PR was successfully merged into main using workflow


[v2.9] EKS - Security groups section missing under Networking

Setup
Rancher - v2.9-1c2b815c8dd66e141b21630904127adc8e03c3de-head
Dashboard - master https://github.com/rancher/dashboard/commit/df60f440f41fe1b59c35b5181292504bb5e66059
Browser type & version: Chrome latest
Describe the bug
EKS (Vue UI): Security groups section missing while provisioning cluster. The same is present on v2.8 Ember UI.
To Reproduce

Create EKS cluster from Rancher UI and select existing subnets option

Screenshots
2.8

2.9

Looks like in ember this is only applicable if the user selects custom subnets. They can then override the default behaviour of rancher creating a new one by selecting an existing one.
There's some logic for this in RKE EC2 world, but not much

Given that the user should still be able to create the cluster, just not with existing security groups, i'm not sure this a blocker... however it is a regression. @mantis-toboggan-md up to you?

this will be a combination of automation and manual testing. moving to To Test

Validation passed on build, able to select security group with existing subnets option
Rancher - v2.9-81337b95660cba868629d6fe769bd7e8242b5aee-head
Dashboard - master 3da1205


Templates not rendering

Issue Type:

[x] Bug Report
[ ] Feature Request
[ ] Documentaion

Describe the bug

Templates not rendering.

Possible solution

Problem in json needs to be corrected

\assign

@Jayanth-MKV describe the bug properly

Actually the templates are not rendering due to a problem in the json files

Actually the templates are not rendering due to an issue in the json files that needs to be corrected


Add sha function

What type of PR is this?
/kind feature

What this PR does / why we need it:
fix issue #1128

Which issue(s) this PR fixes:
fix issue #1128

Does this PR introduce a user-facing change?
NONE

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@luyou86
Firstly thank you very much for your contribution.
Next time, before proceeding with specific work, leave a comment on the relevant issue saying you want to do this.
Regarding this issue, for changes to the c++ section you can execute . /run-ut.sh --run to make sure that all single tests are run through.
Also you need to run build-support/clang-format.sh to make sure the code is formatted according to the code style
Regarding this issue, you can make some optimizations. For example, in most cases the hash_length parameter of sha2 is often a constant, so for this case the optimization can be done in the prepare phase of the function, so that unnecessary if/else branches can be avoided during the execution. This part can be referred to the implementation of the like function.
In addition, for illegal hash_length, NULL should be returned.

@luyou86
Firstly thank you very much for your contribution.
Next time, before proceeding with specific work, leave a comment on the relevant issue saying you want to do this. Regarding this issue, for changes to the c++ section you can execute . /run-ut.sh --run to make sure that all single tests are run through.
Also you need to run build-support/clang-format.sh to make sure the code is formatted according to the code style
Regarding this issue, you can make some optimizations. For example, in most cases the hash_length parameter of sha2 is often a constant, so for this case the optimization can be done in the prepare phase of the function, so that unnecessary if/else branches can be avoided during the execution. This part can be referred to the implementation of the like function.
In addition, for illegal hash_length, NULL should be returned.

ok. i'm a newcomer, next time i will leave a comment on the issue.
i will fix the clang-format and failed unittest

ok. i'm a newcomer, next time i will leave a comment on the issue. i will fix the clang-format and failed unittest

@luyou86
You are welcome in StarRocks community.
I am very happy to conduct you to contribute this change list.
Please feel free to ask whatever you want.

run starrocks_be_unittest


STP-3237: Clarified steps and updated links in post-install customizations

Summary and Scope
The Prometheus and Grafana steps were improved. Added spaces to the "Kubernetes/Compute Resources/Pod" dashboard name, otherwise the search will not work properly in Grafana.
Added .cmn to the Grafana and Prometheus links.
Issues and Related PRs

Resolves STP-3237

/backport release/1.2

I added 3 linting commits. I am going to cherry-pick them to the backport branches as well

@nrockershousen This still needs a 1.0 backport, right? (minus the URL changes due to BICAN)

Yes, I'll get one opened up. Thanks for all of the linting help!

/backport release/1.0


Bad solutions for exercise one [Two sum]

你好,
I noticed that solutions (for both tests and implementation)  for exercise one (Two sum) correspond to exercise two (Add two numbers).
I could make a PR uploading the actual examples for Two sum, but it feels like it's been done already but lost somewhere.

ops, it's my mistake. Thank you very much for pointing this problem out. I have fixed it. Thx~


Dm_Control Dependencies

Hello, there is currently an issue when using the IK modules with dm_control==1.0.1 (error below). This is resolved by using dm_control 1.0.5. Could you please update the dependencies?
Traceback (most recent call last):
File "/home/sasha/anaconda3/envs/poly-backup/lib/python3.8/site-packages/zerorpc/core.py", line 153, in _async_task
functor.pattern.process_call(self._context, bufchan, event, functor)
File "/home/sasha/anaconda3/envs/poly-backup/lib/python3.8/site-packages/zerorpc/patterns.py", line 30, in process_call
result = functor(*req_event.args)
File "/home/sasha/anaconda3/envs/poly-backup/lib/python3.8/site-packages/zerorpc/decorators.py", line 44, in call
return self._functor(*args, **kargs)
File "/home/sasha/Desktop/household_robot_dataset/r2d2/franka/robot.py", line 31, in launch_robot
self._ik_solver = RobotIKSolver()
File "/home/sasha/Desktop/household_robot_dataset/r2d2/real_robot_ik/robot_ik_solver.py", line 13, in init
self._physics = mjcf.Physics.from_mjcf_model(self._arm.mjcf_model)
File "/home/sasha/anaconda3/envs/poly-backup/lib/python3.8/site-packages/dm_control/mjcf/physics.py", line 495, in from_mjcf_model
return cls.from_xml_string(xml_string=xml_string, assets=assets)
File "/home/sasha/anaconda3/envs/poly-backup/lib/python3.8/site-packages/dm_control/mujoco/engine.py", line 424, in from_xml_string
return cls.from_model(model)
File "/home/sasha/anaconda3/envs/poly-backup/lib/python3.8/site-packages/dm_control/mujoco/engine.py", line 407, in from_model
return cls(data)
File "/home/sasha/anaconda3/envs/poly-backup/lib/python3.8/site-packages/dm_control/mujoco/engine.py", line 122, in init
self._reload_from_data(data)
File "/home/sasha/anaconda3/envs/poly-backup/lib/python3.8/site-packages/dm_control/mjcf/physics.py", line 530, in _reload_from_data
super()._reload_from_data(data)
File "/home/sasha/anaconda3/envs/poly-backup/lib/python3.8/site-packages/dm_control/mujoco/engine.py", line 370, in _reload_from_data
self._warnings_before = np.empty_like(self._warnings)
File "<array_function internals>", line 180, in empty_like
RuntimeError: Caught an unknown exception!

Do you mean the QP-optimization Cartesian controller or the MoMa IK utility (based on the same controller actually)? It's difficult to tell from your stack trace what it is you're doing, but the exception is thrown during instantiation of the mjcf model, so the controller is unlikely to be the cause. By the way both modules are still running fine for me.

We now use dm_control 1.0.8


ParserSyntaxError: Syntax Error "in" bug report

An error happened on myschema.py.
Traceback (most recent call last):
  File "env/lib/python3.10/site-packages/bump_pydantic/main.py", line 185, in run_codemods
    output_tree = transformer.transform_module(input_tree)
  File "env/lib/python3.10/site-packages/libcst/codemod/_command.py", line 87, in transform_module
    tree = self._instantiate_and_run(transform, tree)
  File "env/lib/python3.10/site-packages/libcst/codemod/_command.py", line 57, in _instantiate_and_run
    return inst.transform_module(tree)
  File "env/lib/python3.10/site-packages/libcst/codemod/_codemod.py", line 108, in transform_module
    return self.transform_module_impl(tree_with_metadata)
  File "env/lib/python3.10/site-packages/libcst/codemod/_visitor.py", line 32, in transform_module_impl
    return tree.visit(self)
  File "env/lib/python3.10/site-packages/libcst/_nodes/module.py", line 90, in visit
    result = super(Module, self).visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/base.py", line 218, in visit
    should_visit_children = visitor.on_visit(self)
  File "env/lib/python3.10/site-packages/libcst/matchers/_visitors.py", line 511, in on_visit
    return CSTTransformer.on_visit(self, node)
  File "env/lib/python3.10/site-packages/libcst/_visitors.py", line 44, in on_visit
    retval = visit_func(node)
  File "env/lib/python3.10/site-packages/libcst/codemod/visitors/_remove_imports.py", line 300, in visit_Module
    node.visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/module.py", line 90, in visit
    result = super(Module, self).visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/base.py", line 218, in visit
    should_visit_children = visitor.on_visit(self)
  File "env/lib/python3.10/site-packages/libcst/matchers/_visitors.py", line 718, in on_visit
    return CSTVisitor.on_visit(self, node)
  File "env/lib/python3.10/site-packages/libcst/_visitors.py", line 123, in on_visit
    retval = visit_func(node)
  File "env/lib/python3.10/site-packages/libcst/codemod/visitors/_gather_unused_imports.py", line 71, in visit_Module
    node.visit(annotation_visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/module.py", line 90, in visit
    result = super(Module, self).visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/base.py", line 227, in visit
    _CSTNodeSelfT, self._visit_and_replace_children(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/module.py", line 74, in _visit_and_replace_children
    body=visit_body_sequence(self, "body", self.body, visitor),
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 227, in visit_body_sequence
    return tuple(visit_body_iterable(parent, fieldname, children, visitor))
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 193, in visit_body_iterable
    new_child = child.visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/base.py", line 227, in visit
    _CSTNodeSelfT, self._visit_and_replace_children(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/statement.py", line 1931, in _visit_and_replace_children
    body=visit_required(self, "body", self.body, visitor),
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 81, in visit_required
    result = node.visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/base.py", line 227, in visit
    _CSTNodeSelfT, self._visit_and_replace_children(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/statement.py", line 697, in _visit_and_replace_children
    body=visit_body_sequence(self, "body", self.body, visitor),
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 227, in visit_body_sequence
    return tuple(visit_body_iterable(parent, fieldname, children, visitor))
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 193, in visit_body_iterable
    new_child = child.visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/base.py", line 227, in visit
    _CSTNodeSelfT, self._visit_and_replace_children(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/statement.py", line 442, in _visit_and_replace_children
    body=visit_sequence(self, "body", self.body, visitor),
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 177, in visit_sequence
    return tuple(visit_iterable(parent, fieldname, children, visitor))
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 159, in visit_iterable
    new_child = child.visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/base.py", line 227, in visit
    _CSTNodeSelfT, self._visit_and_replace_children(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/statement.py", line 1542, in _visit_and_replace_children
    annotation=visit_required(self, "annotation", self.annotation, visitor),
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 81, in visit_required
    result = node.visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/base.py", line 227, in visit
    _CSTNodeSelfT, self._visit_and_replace_children(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/expression.py", line 1673, in _visit_and_replace_children
    annotation=visit_required(self, "annotation", self.annotation, visitor),
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 81, in visit_required
    result = node.visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/base.py", line 227, in visit
    _CSTNodeSelfT, self._visit_and_replace_children(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/expression.py", line 1604, in _visit_and_replace_children
    slice=visit_sequence(self, "slice", self.slice, visitor),
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 177, in visit_sequence
    return tuple(visit_iterable(parent, fieldname, children, visitor))
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 159, in visit_iterable
    new_child = child.visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/base.py", line 227, in visit
    _CSTNodeSelfT, self._visit_and_replace_children(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/expression.py", line 1549, in _visit_and_replace_children
    slice=visit_required(self, "slice", self.slice, visitor),
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 81, in visit_required
    result = node.visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/base.py", line 227, in visit
    _CSTNodeSelfT, self._visit_and_replace_children(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/expression.py", line 1463, in _visit_and_replace_children
    value=visit_required(self, "value", self.value, visitor),
  File "env/lib/python3.10/site-packages/libcst/_nodes/internal.py", line 81, in visit_required
    result = node.visit(visitor)
  File "env/lib/python3.10/site-packages/libcst/_nodes/base.py", line 218, in visit
    should_visit_children = visitor.on_visit(self)
  File "env/lib/python3.10/site-packages/libcst/matchers/_visitors.py", line 718, in on_visit
    return CSTVisitor.on_visit(self, node)
  File "env/lib/python3.10/site-packages/libcst/_visitors.py", line 123, in on_visit
    retval = visit_func(node)
  File "env/lib/python3.10/site-packages/libcst/codemod/visitors/_gather_string_annotation_names.py", line 65, in visit_SimpleString
    self.handle_any_string(node)
  File "env/lib/python3.10/site-packages/libcst/codemod/visitors/_gather_string_annotation_names.py", line 74, in handle_any_string
    mod = cst.parse_module(value)
  File "env/lib/python3.10/site-packages/libcst/_parser/entrypoints.py", line 109, in parse_module
    result = _parse(
  File "env/lib/python3.10/site-packages/libcst/_parser/entrypoints.py", line 55, in _parse
    return parse(source_str)
libcst._exceptions.ParserSyntaxError: Syntax Error @ 1:1.
parser error: error at 1:2: expected one of (, *, +, -, ..., AWAIT, EOF, False, NUMBER, None, True, [, break, continue, lambda, match, not, pass, ~

in
^

code
class Schema(BaseModel):
    option: Literal["in", "not_in", "exact"] = "in"

That's on LibCST, I can't do anything to solve it. 😥


While using Microsoft.Data.SqlClient getting reference error for System.Data.SqlClient

Due to the below error i am blocked on the work.
System.TypeInitializationException: The type initializer for 'Microsoft.Data.SqlClient.SqlConnection' threw an exception.
---> System.TypeInitializationException: The type initializer for 'Microsoft.Data.SqlClient.SqlConnectionFactory' threw an exception.
---> System.TypeInitializationException: The type initializer for 'Microsoft.Data.SqlClient.SqlPerformanceCounters' threw an exception.
---> System.TypeInitializationException: The type initializer for 'Microsoft.Data.Common.ADP' threw an exception.
---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
File name: 'System.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at Microsoft.Data.Common.ADP..cctor()
--- End of inner exception stack trace ---
I have dereferenced the System.Data.SqlClient in the entire project but still getting this exception.
I have added the reference for Microsoft.Data.SqlClient i even upgraded this to the latest version.[version="5.0.1" targetFramework="net472"]
I have verifying the connection string by using the VS Community DataBase TestConnection it is working fine.
We are getting this error while trying to establish connection through c# code.
.NetFramework: net472
VSCommunity editor with C# as the scripting language and Windows 11 as the OS.

@gupta01sunil -- thank you for your detailed feedback.  This repo is solely for documentation issues, and this seems implementation-related.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


Update Node Image

This PR simplifies the Docker build commands and updates the Node image to the latest stable version. And it is the most secure one, with no vulnerabilities on Snyk scan.

@davehorton these changes would be good for the main branch as well I think.


Dr-1111 - Add plans page

Overview
This Pr will add the plans page for a user to be able to upgrade his account.
Changes:

Add Plan page, controller  and service.
Fix responsive issues.

Technical debt:

Test.

👍

Nice work @mvillaseco ! remember to remove all the links to the new page before merge.


Prepares 3.5.0 release

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #580 (5e48665) into master (ef2ceb2) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 5e48665 differs from pull request most recent head c3286c3. Consider uploading reports for the commit c3286c3 to get more accurate results

@@           Coverage Diff           @@
##           master     #580   +/-   ##
=======================================
  Coverage   83.38%   83.38%
=======================================
  Files          37       37
  Lines        1794     1794
=======================================
  Hits         1496     1496
  Misses        298      298

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


define KBFS_MOUNT_POINT in run_keybase, and allow overrides

This is useful for testing, and in multi-user cases like
https://github.com/keybase/client/issues/5120#issuecomment-268445442
@chrisnojima and I talked about this a little this morning. Some concerns about saying we support multi-user before we really do, and also right now mounting in a nonstandard place will break the GUI's "open folder" features. But despite all that, maybe nicer to have something better than "copy this script and edit it" for people trying to do multi-user right now? @malgorithms @maxtaco?

not much of an opinion on this...if it's helpful for testing, that's cool with me.
As for a user facing thing, I fear it's of minimal value because this kind of setting's documentation will be hidden who-knows-where, so no one will discover it... and if it breaks the gui that sucks....so I feel like almost no one will/should end up with it set, and it will be a power feature rarely used/discovered. I'd always rather spend time on things that affect way more users... (But like I said, if you need it for testing, that's cool.)

I would find it useful for testing, and in the issue linked above it would've made it easier to suggest a power user workaround.

What's the status of this PR?

I think it wasn't totally clear whether we wanted to do it? But it would probably work almost entirely unchanged right now if we wanted it.


fix: Only use a fudge factor if we fail to find patterns normally

It seems, that this change made my predictions very different, is it on purpose?
Before merging this, for this data input:
https://turnipprophet.io?prices=<IP_ADDRESS>.145........
I had predictions ranging between 50-207, now the predictions are rather capped to 52-145:


REST API endpoints convention

Advice
Resources will be named in snake case and we will go with a root level resource design. See https://www.moesif.com/blog/technical/api-design/REST-API-Design-Best-Practices-for-Sub-and-Nested-Resources/.

We could create a lint rule for the OpenAPI description file that makes sure these conventions are followed.