Server cache working

@devoncarew @lukechurch

Files cached locally for 10 minutes (default) - can be changed, please comment if you have suggestions.
Files moved to static subdirectories.
Sample up at dev.dartproject-1000.appspot.com.
Still need to cache codemirror javascript somehow - a bit different from the other files since it's in a package.

#650

Thanks @Georgehe4 this looks like a good thing. I'm correct in thinking this only change the embedded version? The main dartpad site is still serving statics out of the root folder with 'no-cache' set? Don't need to fix that in this PR, but if you could file a tracking bug that'd be great.

Correct, only embedded/mobile versions will use files that are cached.
We may also want to cache codemirror - this would mean that the main dartpad site will use cached files.

There are some dependency issues with pub. I'll look at it tomorrow.

Wow, this PR has a huge performance benefit:

I have some ideas for caching codemirror (in a future PR).

lgtm!

Merging.


3398 - Attachments - Reclassify File Tag

https://app.zenhub.com/workspaces/foi-flow-607f0ab6ae54b700111dc733/issues/gh/bcgov/foi-flow/3398

There are some things here I'd like to review with another dev before merging


Tab menu

I implemented the tab menu as stated in invision.
https://zalando.invisionapp.com/d/main#/console/10454474/256823763/preview

First thing, you should really try to have atomic PR's as I see a fix(header) and feat(tab-menu). We should try to stick to our contributing guides. Even for small things.

If you check the files there is no change in the headers. This is because squash commits creates new commit hashes which are shown here as new commits.

And yes the tab menu only implements the tab menu. It propagates the changed value and the rest is left to you application

thx for the review. Lets talk about the package-lock.json tomorrow


The tenant option is not avaialble

[Enter feedback here]
The page is not available to download the user license guide. Admin center is moved, and there is no tab of Tenant on the left side.

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

ID: d3b45f80-ff57-2bfe-2195-1a9376986b59
Version Independent ID: 1e776630-ea6f-ac89-14ef-d767575a870d
Content: Licensing and license management - Power Platform
Content Source: power-platform/admin/wp-license-management.md
Service: power-platform
GitHub Login: @dileepsinghmicrosoft
Microsoft Alias: dileeps

@thealisakhi
Tenant does appear in the Power Apps admin center. This admin center will be retired soon and the documentation will be updated then.

Hi @jimholtz
What is the alternative to get the report, on what date a licensed was assigned to users. Currently in Dynamics 365 you will see a full list of office 365 users.


Constructing shapefiles in memory

This is my first time trying to contribute to open source so sorry for any breaches in etiquette.
I am trying to use dotspatial to create a shapefile on the fly in a web app.  I can create them to disk no problem but this is not an option on my server, I need to create them purely in memory.
My original plan was to construct each file in memory as a stream and then wrap the streams in a zip for download but the existing API does not seem well suited to this. I don't want to make too much mess and I would prefer to have a result that would be useful to the community.
I wondered if anyone has tried doing it in memory in the past? Or if there is any reason it would be impossible? Or if my feature is just crazy?
Steve

It's not crazy :). Your goal is return shapefile inside zip archive without storing intermediate files at hard-drive, is it?  Then yes, I think it's possible to adapt DotSpatial API for saving files into streams, and this feature will be quite useful for others.

Yes that is the goal exactly. I've had a look and perhaps it is not as hard as I thought, I will try to make the changes. I see support for .shp, .shx, .dbf and .prj. do you use any of the other files?

.shp, .shx, .dbf and .prj

only these files


Fix test failing on time conversion

One of the tests was failing when executed in the PST timezone due to time zone conversion.
When executing this command:
mvn test -Dsuites="com.sap.kafka.connect.sink.AvroLogicalTypesTest @put propagates to DB with schema containing date fields"

The test has failed with this message:
[INFO] --- scalatest-maven-plugin:1.0:test (test) @ kafka-connector-hana_2.12 ---
Run starting. Expected test count is: 1
AvroLogicalTypesTest:
[ScalaTest-main-running-AvroLogicalTypesTest] INFO com.sap.kafka.connect.sink.hana.HANASinkTask - Starting Kafka-Connect task
[ScalaTest-main-running-AvroLogicalTypesTest] INFO com.sap.kafka.connect.sink.hana.HANASinkTask - init HANA Writer for writing the records
[ScalaTest-main-running-AvroLogicalTypesTest] INFO com.sap.kafka.connect.sink.hana.HANASinkTask - init HANA Writer for writing the records
[ScalaTest-main-running-AvroLogicalTypesTest] INFO com.sap.kafka.connect.sink.hana.HANASinkTask - PHASE - 1 - get records from kafka, Started for task with assigned partitions []
[ScalaTest-main-running-AvroLogicalTypesTest] INFO com.sap.kafka.connect.sink.hana.HANASinkTask - Number of Records read for Sink: 1
[ScalaTest-main-running-AvroLogicalTypesTest] INFO com.sap.kafka.connect.sink.hana.HANAWriter - write records to HANA
[ScalaTest-main-running-AvroLogicalTypesTest] INFO com.sap.kafka.connect.sink.hana.HANAWriter - initialize connection to HANA
[ScalaTest-main-running-AvroLogicalTypesTest] INFO com.sap.kafka.client.hana.HANAJdbcClient - Creating table:DATE_TABLE with SQL: CREATE TABLE "TEST"."DATE_TABLE" ("date_field" DATE NOT NULL, PRIMARY KEY ("date_field"))
[ScalaTest-main-running-AvroLogicalTypesTest] INFO com.sap.kafka.connect.sink.hana.HANAWriter - flush records into HANA
[ScalaTest-main-running-AvroLogicalTypesTest] INFO com.sap.kafka.client.hana.AbstractHANAPartitionLoader - Creating prepared statement: INSERT INTO "TEST"."DATE_TABLE" ("date_field") VALUES (?)
[ScalaTest-main-running-AvroLogicalTypesTest] INFO com.sap.kafka.connect.sink.hana.HANAWriter - flushing records to HANA successful
[ScalaTest-main-running-AvroLogicalTypesTest] INFO com.sap.kafka.connect.sink.hana.HANASinkTask - PHASE - 1 ended for task, with assigned partitions []
- put propagates to DB with schema containing date fields *** FAILED ***
  "2013-10-1[6]" did not equal "2013-10-1[5]" (AvroLogicalTypesTest.scala:75)
  Analysis:
  "2013-10-1[6]" -> "2013-10-1[5]"
Run completed in 899 milliseconds.
Total number of tests run: 1
Suites: completed 1, aborted 0
Tests: succeeded 0, failed 1, canceled 0, ignored 0, pending 0
*** 1 TEST FAILED ***
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for kafka-connector-hana 0.9.5-SNAPSHOT:
[INFO]
[INFO] kafka-connector-hana ............................... SUCCESS [  0.973 s]
[INFO] kafka-connector-hana_2.12 .......................... FAILURE [  2.762 s]
[INFO] kafka-connector-hana_2.13 .......................... SKIPPED
[INFO] kafka-connector-hana-examples ...................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  3.835 s
[INFO] Finished at: 2023-01-31T13:47:18-08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.scalatest:scalatest-maven-plugin:1.0:test (test) on project kafka-connector-hana_2.12: There are test failures -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :kafka-connector-hana_2.12

Fix: convert Date value to String using Calendar before asserting it instead of calling toString on the date object. This is the same approach taken for similar tests for time and timestamp values in this test suite.

thanks


Investigate into Message Pack and GZIP support

Currently the transport uses a JSON string as a payload. To reduce the payload we could:

zip the content of the string
use Message Pack instead of JSON

We should investigate both options and measure the saving we can have.
This must be optional and would best be done using header properties to negotiate this as in HTTP

CBOR format which was inspired by MessagePack seems to be better choice.
As is it a web standard https://tools.ietf.org/html/rfc7049.

@artas90 thanks for pointing this out.

We're looking at moving more of our remotable services in VS from JSON to MessagePack. I'm concerned about losing interoperability with node-based processes. I'd love to see vscode-jsonrpc support a pluggable formatter (like StreamJsonRpc has) so that the encoding can be whatever the user wants. JSON can be the default formatter, and we can supply the MessagePack one if it isn't in-box as an option as well.

@artas90 As I already have a great deal of investment and code based on MessagePack, I'm biased. But I wonder if you want to persuade me as to why CBOR is superior to MessagePack. They are both spec'd standards. One being RFC and the other spec'd elsewhere isn't particularly compelling. JSON itself at least started as a spec on https://www.json.org/ as I understand it.

This must be optional and would best be done using header properties to negotiate this as in HTTP

FWIW, the format we use tends to be important to maintain across an entire RPC session. While we can change text encodings from message to message, switching between JSON and MessagePack isn't supported in StreamJsonRpc. So while you could declare the encoding to be messagepack in your HTTP headers, at least for our purposes we need to know whether MessagePack or JSON will be used up front when establishing the connection.

@AArnott Honestly I never used neither CBOR nor MessagePack. Just wanted to mention that such standard as CBOR exists. And it might be considered as well

I rebased the work I started on master today and a first version of this is here: https://github.com/microsoft/vscode-languageserver-node/tree/dbaeumer/encodingSupport2
Implementation wise this works as follows:

support pluggable encoders and decoders (gzip, ...)
content format is still JSON
handshake is done using HTTP header properties (e.g. Accept-Encoding and Content-Encoding). This only support encoding responses (which usually are the big payload)
in LSP I will add capabilities to negotiate the encoding in the initialize phase to avoid sending the headers all the time. In addition it will support encode notification and request.

For MessagePack in would propose that we indicate it using a different Content-Type since it is not JSON anymore. The content type I would use is application/msgpack  (see the discussion in https://github.com/msgpack/msgpack/issues/194). As with encoding I would also support in LSP to negotiate msgpack during the initialize phase.

Thanks for the update, @dbaeumer. Your design sounds like you're definitely planning on a mix of messagepack and JSON messages on the same connection, which is exactly what I was hoping we wouldn't do. I'll have to review what kind of state our formatters build up over a connection to see what kind of features will break if we switch formats from one message to another.

This is mainly driven by the fact that I want to offer an upgrade path from the current behavior. In my current thinking the initialize handshake will always be plain json (like the header is always encoded using ascii). After the first handshake a connection can then be either in a state where encoding and content type is determined using header properties or where client and server agree on a encoding and / or content type for all messages.
Otherwise LSP would need to specify command line arguments on how to define content type and encoding on startup. And a server needs to document the supported types and encodings since they are reused in different clients with different content type and encoding capabilities.

Does every LSP server already have a client portion that knows how to spawn that particular LSP server? In VS that's the way it is. I thought perhaps it was this way in VS Code as well. As I understood it, LSP doesn't prescribe how the LSP server is spawned, what command line args it takes, or how to establish the pipe between the client and server processes.
If that's all true, why not simply document in the LSP spec that LSP may be encoded as JSON or MessagePack, or any other encoding that the client and server agree on.
Then the spec itself doesn't have to prescribe a handshake. For example, if I wrote an LSP server for F#, I would also have to write the LSP client that spawns the F# LSP server. Since I want a super-fast experience, I choose to encode with MessagePack. My client and server are hard-coded to always use MessagePack, and things just work.
All that would be left is for the vscode-jsonrpc library to support swapping in different formatters.
But I'm guessing I'm missing something. @dbaeumer can you tell me why you feel it's something that needs to be specified at the LSP spec level?
Consider: If we are to include MessagePack provisions in the LSP spec, we could get far more benefit by specifying indexes for each property so that we can encode the data as arrays instead of maps in messagepack. We'd never have to serialize and transmit property names, which can dramatically reduce the payload size and time spent serializing.

This requires that we spec command line arguments to at least make the way how a content type is picked the same across servers. This simply adds another dimension to the spec which I want to avoid. But more important is the fact that we have requests to support the following:

connect to an already running server
multi tenant support

Hardwiring the content type and encoding will make it a lot harder to support the two things. I have no problem to specify that the content type and encoding must stay fixed after the initialize (doesn't change on every message, as it would be possible with HTTP).

I'm imagining that even if LSP is "relayed" across multiple nodes (e.g. LSP Server<->LSP Client on Live Share host<->Live Share host<->Live Share guest<->LSP client on guest) that each individual leg may be encoded with MessagePack or not. So it's not something necessarily even in the LSP spec -- just a decision that the individual JSON-RPC library is using when it sets up an individual leg on the connection.
I'd like MessagePack encoding support in vscode-jsonrpc so we can use MessagePack for (non-LSP related) JSON-RPC messages as part of our 'brokered services' between VS and VS Code.
Beyond that, @CyrusNajmabadi expressed interest in switching their LSP server to messagepack in https://github.com/dotnet/roslyn/issues/42595#issuecomment-601910125, and I think we can do that without any change to the LSP spec (or vscode-jsonrpc for that matter). But if VS Code were to participate in that same perf win, vscode-jsonrpc would need to support MessagePack as well, and the VS Code LSP system would have to support allowing the LSP client that spawns the Roslyn LSP server to set up the MessageConnection with the MessagePack encoder before handing off to VS Code to then use RPC invocations (ignorant of messagepack being underneath) to talk to their LSP server.

I think there are two use cases: you have all connection under control and want to use message pack. With the changes I did to the jsonrpc library that is possible. You don't have all connection under control (e.g. you connect to a running server) and need to negotiate the encoding. This needs support in LSP.

Sounds reasonable. But how can you connect to an existing server without controlling that connection?

You control the connect but not the content type / encoding. This could depend on the version of the server or the client connecting.

I'm checking out your dbaeumer/encodingSupport2 branch with the intent to find a way to get vscode-jsonrpc to work with messagepack in a way that is compatible with StreamJsonRpc's existing support for it. I may have a PR to send you.

Yes, got merge. With the difference that it is not header negotiable anymore.

I will close the issue. Support has been added to the library but nothing has been added to the spec yet. To make use of this in the protocol we need to start on the LSP level and spec it there.

@dbaeumer has support for using msgpack instead of JSON been finalized? If yes, is there documentation on enabling it?
If not, what's missing and how can I help to push it forward?
I believe using msgpack will provide significant performance benefits for our LSP implementation.

FWIW, one idea my team has played with is the LSP server somehow advertising (through a manifest perhaps) that it supports msgpack via being launched by some switch. Then the LSP client spawns the server with that switch and assumes msgpack instead of JSON.

The support has been finalized in JSONRPC lib but there is still no handshake up upgrade a server connection. So you need to do what @AArnott suggests that you spawn your server with a special command line argument.

Adding the command line argument is reasonable and easy to do. But is there some configuration on the client side? How do I tell the client to use msgpack for requests and responses?

@vinistock good point. I never added that :-( but will be easy to do. But please note that this will only work for transports different than Node IPC.

Do you have any pointers on how to get started? I can take a stab at making this an option for clients.
About the transports: can you elaborate? Would that impact language servers implemented in languages other than NodeJS?

But please note that this will only work for transports different than Node IPC.

I'm confused over why a transport mechanism or platform would limit whether you can encode LSP as msgpack. We use msgpack across IPC with a node process for non-LSP purposes already.

@vinistock it was my mistake. The code is actually already there since you can always pass a function as a server (see https://insiders.vscode.dev/github/microsoft/vscode-languageserver-node/blob/main/client/src/node/main.ts#L126) which returns a MessageTransport which you can setup accordingly.
@AArnott  Node provides a special IPC mechanism where you can directly send and receive JS object and the Node runtime does the serialization / de-serialization. You could may be use msgpack -> number[] -> Node IPC but I guess this is counter productive. You can of course use msgpack with node using sockets / pipes.

If you a pass a function as the server, because you only return a MessageTransport, you need to handle the life cycle of the server process (this._serverProcess) yourself, correct?
Is there interest in adding an option and handling this inside the library? Something like
const serverOptions = {
  run: /* ... */,
  debug: /* ... */,
  transport_encoding: TransportEncodings.Msgpack
}

@vinistock yes, that is correct.
What we can think of is supporting something like this in options: https://insiders.vscode.dev/github/microsoft/vscode-languageserver-node/blob/main/jsonrpc/src/node/test/messages.test.ts#L237
I don't want to have any hard reference to external libraries.

Thank you for considering it, I think it'll be a good quality of life improvement when using different encodings - since we can avoid having to deal with the life cycle of the process which is already implemented in the library.
I put together a draft of what this could look like in #1250. Please let me know if you're okay with the addition and the approach.


[iCubSingapore01] Fix Gearbox values

What changes:
This PR fix the value of the joint 0 (pitch) of both legs from 100 to 150.
Note:
This is the second PR concerning iCubSingapore01's maintenance, the first is:

https://github.com/robotology/robots-configuration/pull/552

cc @sgiraz

Hi @AntonioConsilvio

This PR fix the value of the joint 0 (pitch) of both legs from 100 to 150.

It's the first time that I see a gear ratio = 150:1. Our HD sizes for these joints are generally 100:1 or 160:1. Can you please confirm?
cc @fiorisi

Might be related to this discussion (see section Further details on the hip_pitch joint).


Tip for creators of bounties

Hi, Dustin,
This one should be really simple, because it's just about a little text reminder for creators of bounties.  I thought of it when Michael L brought up a point: "What if I do a crappy job?"  Creating a bounty is effectively writing a contract.    Also remember, there are always three aspects: good, fast, and cheap.  We're probably not paying each other, so that only leaves good or fast, because no one can provide all three."

Thanks Bill,
Good suggestion.  I will implement this.


Provide a Redirect Point to Directly Link Article

This opens a endpoint which redirects the user to the article

Example

test 🚀


ac:framerate in ROI vocabulary

Currently ac:framerate is organized in the Region of Interest Vocabulary section of the Term List document. This proposal is to move it to the Resource Creation Vocabulary (to be with its audio analog mo:sample_rate).
Existing metadata:
ac:framerate tdwgutility:organizedInClass <http://rs.tdwg.org/ac/terms/RegionOfInterest>.

Proposed metadata:
ac:framerate tdwgutility:organizedInClass <http://rs.tdwg.org/dwc/terms/attributes/ResourceCreation>.

Implications
This is an organizational change that has no effect on implementations.

On 2021-12-05, the Maintenance Group agreed to move this to public comment.

Reminder that public comment on this issue closes soon.

Public comment period has now ended.

Approved by Executive Committee decision on 2022-02-23 and implemented in this release


error no exported member 'Renderer2'

Hi,
I am having an error when I start npm now because of ng2-materialize. Here's the error I get:
WARNING in ./~/ng2-materialize/dist/collection/collection.component.js
33:12-21 "export 'Renderer2' was not found in '@angular/core'
ERROR in ....../node_modules/ng2-materialize/dist/collection/collection.component.d.ts (4,30): Module .../node_modules/@angular/core/index"' has no exported member 'Renderer2'.
How do I fix this?
Thank you!

Hi @misisriddle,
When we updated the package to Angular 4 we noticed that Renderer has been deprecated and is replaced by Renderer2 (you can find the reference here).
We started to use Renderer2 for this reason but I guess we forgot that this is against our efforts to keep the package compatible for both Angular 2 and 4 at least for now to give time to people to update.
I know this is not an ideal solution and we are sorry about this but by now the quick fix would be to update your application to Angular 4.
Note that Angular 4 brings many benefits such as performance boost so for that reason we encourage you to update. You can find a nice overview of the changes and benefits for updating to Angular 4 here.
That being said, we are going to sit back and see if there is anything we can do to avoid this issue in the short term but in the long run we are definitely going to move forward with Angular 4 and we are not planning to keep support with Angular 2.

@misisriddle In the meantime, you should be fine with<EMAIL_ADDRESS>npm install --save<EMAIL_ADDRESS>

@misisriddle as one of my collegue mentioned, in the meantime, you should be fine with<EMAIL_ADDRESS>npm install --save<EMAIL_ADDRESS>
But obviously to get the new features and bug fixes you will need to update your applicaton to Angular 4.

Thank you @jfcere :) We don't have time to upgrade now to Angular 4 but will do so in the near future. Thanks again!


Make a fluent builder class, to handle all custom HTTP Handlers that the client may have

https://www.codeproject.com/Articles/640997/Fluent-interfaces-and-Method-Chaining-in-Csharp

What do you foresee the API looking like for this? What's the purpose of a fluent API on this lib?
man, I always feel like my terse questions make me sound like an asshole, but I genuinely want to know.. if for no other reason than that I'd like to submit a PR

Hahaha, I want to have this builder available, in case the user has other Custom Handlers of his own. We have to make sure that our HttpTracerHandler is the "Root" handler, and all other custom handlers, are chained in the InnerHandler of our Tracer handler.

How does that work? What's the purpose of multiple handlers?

That doesn't work if one of the handlers is adding a gzip header/handler.
On Tue, Apr 10, 2018, 10:17 PM Chase Florell<EMAIL_ADDRESS>wrote:

How does that work? What's the purpose of multiple handlers?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/TorontoMobileDevelopers/HttpTracer/issues/2#issuecomment-380304747,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABwV_irJCzR6ql-3daURbFLd7VZeQiCDks5tnWfEgaJpZM4TNVSh
.

I thought that we could chain the httphandlers that users might have together, make sure our handler would be the root, so we would be sure that the user could have other handlers and also have ours. But after testing it out, it seems that I was wrong on how the handlers behave. @dylanberry is completely right. This will not work. I'm closing this issue o/

aaaand we are bringing this back ahahaha.


viewInstance not working with flash messages

Hi, thank you for implementing this feature.
https://github.com/adonisjs/adonis-framework/commit/08bdca3eac4e2c6804e74a84909a66b8f33c7949
But now flash messages are buggy,
Got error when rendering view:
Error: Unable to call old, which is undefined or falsey
And flash messages do not show up, or shows up couple of page reloads later.

That commit has not been release yet. Are you using the code from Github?

Infact I tested that commit and all worked fine for me. So I released it as 3.0.12

It is working now. Thanks


addons: Enforce interactive mode if required params are missing

If the user sets all required addon parameters as command-line flags, we
can safely skip the interactive mode. Otherwise we enable it.

/hold Found a bug when testing this

/unhold Fixed

/hold cancel


Use GITHUB_ACTION_PATH instead of github.action_path

This is required in order to use this action within a docker container.
Relates to #21

Successful example here using the action within a github action docker container strategy.  Script doesnt work yet for ubuntu 20.04, but does work for 22.04 👍🏼

@flynneva  I looked at the tests on your repository. The tests on jammy are probably failing because there is no bootloader, kernel and rootfs in an expected directory ./images/*. I think we need to change the github.action_path to GITHUB_ACTION_PATH everywhere, especially in the get-images step.
On focal there is another problem because it has Python in version 3.8.2, but parts of our type hints require at least Python 3.9 due to change PEP 585 (https://peps.python.org/pep-0585/). So you need to upgrade your Docker container to run this action properly. Perhaps we should note this requirement somewhere.

@flynneva I have fixed the rest of ${{ github.action_path }} appearances in the pull request #25 if you want to see. I think this should fix one of your issues.

@WiktorOgrodnik awesome stuff! I'll check it out probably over the weekend when I get a chance and report back 🙏🏼👍


Always creating default SSL context

With this change we'll always use default SSL context (https://docs.python.org/3/library/ssl.html#ssl.create_default_context) to use the best defaults.

The default ssl_context already considers common cases. If no TLS certificates are provided on our side, it trusts the system's default CA. And we block requests to bank servers with untrusted CAs.
cafile, capath, cadata represent optional CA certificates to trust for certificate verification, as in [SSLContext.load_verify_locations()](https://docs.python.org/3/library/ssl.html#ssl.SSLContext.load_verify_locations). If all three are [None](https://docs.python.org/3/library/constants.html#None), this function can choose to trust the system’s default CA certificates instead
``

The default ssl_context already considers common cases. If no TLS certificates are provided on our side, it trusts the system's default CA. And we block requests to bank servers with untrusted CAs.
cafile, capath, cadata represent optional CA certificates to trust for certificate verification, as in [SSLContext.load_verify_locations()](https://docs.python.org/3/library/ssl.html#ssl.SSLContext.load_verify_locations). If all three are [None](https://docs.python.org/3/library/constants.html#None), this function can choose to trust the system’s
default CA certificates instead

Passing [SERVER_AUTH](https://docs.python.org/3/library/ssl.html#ssl.Purpose.SERVER_AUTH) as purpose sets [verify_mode](https://docs.python.org/3/library/ssl.html#ssl.SSLContext.verify_mode) to [CERT_REQUIRED](https://docs.python.org/3/library/ssl.html#ssl.CERT_REQUIRED) and either loads CA certificates (when at least one of cafile, capath or cadata is given) or uses [SSLContext.load_default_certs()](https://docs.python.org/3/library/ssl.html#ssl.SSLContext.load_default_certs) to load default CA certificates.

The following lines disabled certificate checks completely.
ssl_context.check_hostname = False
ssl_context.verify_mode = ssl.CERT_NONE
Also the following line is effectively equivalent to the above two. The source code of _create_unverified_context is available here: https://github.com/python/cpython/blob/main/Lib/ssl.py#L730
ssl_context = ssl._create_unverified_context()


Draft of Flutterflow blog post

Need to add screenshots that explain some of the points. Please comment on the overall flow, readability and understand-ability. Meme help always welcome

Good post. Make sure you change the stuff in the header above the second ---.
Also add an emoji to the title!


please push 0.3.0 to npm registry, it's still at 0.1.0

seems like a lot of the duplicate module name errors can be solved by using the latest version of this project instead of the default installed by npm.
Problem: Using npm install react-native-clean-form installs version 0.1.0
Workaround: Manually using "react-native-clean-form": "esbenp/react-native-clean-form", in package.json will cause version 0.3.0 to be installed.
#8, #27, #37

Your right ;) ... but only @esbenp has access to the npm package. I can merge here but nothing more.

0.4.1 has been created and published :-)

Thank you!
On Wed, Apr 12, 2017 at 3:04 AM, Esben Petersen<EMAIL_ADDRESS>wrote:

0.4.1 has been created and published :-)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/esbenp/react-native-clean-form/issues/39#issuecomment-293492204,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AY9MYMcKPY5q_GVoCStGL9X0uiexqRODks5rvHeMgaJpZM4M6rIt
.


service is anavailable

Hi, since today the QBitNinjaClient doesnt work due to a sever error the url https://tapi.qbit.ninja keep sending 500 error
is it gonna be Ok sometimes soon or should we migrate to another provider

strange, will take a look.

it is back up after a restart. First time it happens to me. If it happen again, I will investigate.


No license

Thanks for the samples, @SteveSyfuhs!
Could you add a license file? Otherwise it's difficult to reuse your samples.
Thank you in advance!

I've added an MIT license. That said, these are very old samples and are only kept around for historical reasons. Take a look at the CertificateRequest class built in to .NET now. It'll do way more than this sample ever did. https://docs.microsoft.com/en-us/dotnet/api/system.security.cryptography.x509certificates.certificaterequest?view=net-5.0

I've added an MIT license. That said, these are very old samples and are only kept around for historical reasons. Take a look at the CertificateRequest class built in to .NET now. It'll do way more than this sample ever did. https://docs.microsoft.com/en-us/dotnet/api/system.security.cryptography.x509certificates.certificaterequest?view=net-5.0

That's fantastic! Thanks a lot Steve for such a prompt reply and fix!
That's a good point that things changed and some classes are in the framework now.

That's fantastic! Thanks a lot Steve for such a prompt reply and fix!
That's a good point that things changed and some classes are in the framework now.


Don't append ".xml" to output filename

It would seem more consistent to not append ".xml" to the output filename. E.g. the debug output just below the part where the file is opened, outputs the filename without ".xml", which might be confusing. Also, I expected that the output flag takes my argument as the literal filename -- it appending ".xml" was surprising.

I've also experienced this.


Can't install pods

Computer OS: macOS
Unity Editor Version: 2022.3.21
Appodeal Unity Plugin Version: 3.3.0
Xcode Version: 15.3
CocoaPods Version: 1.15.2

I installed the new version of Appodeal 3.3.0 according to the instructions.  I specifically checked, you do have such problems in your repository. What am I doing wrong? I'm attaching the errors
pod install --repo-update
Error logs
logs.txt
pod file
Podfile.txt

Hi @Lucasito,
Appodeal SDK 3.3.0 requires a newer iOS Firebase version (~> 10.22) that corresponds to Firebase Unity SDK 11.8
I checked with the Firebase Unity SDK 11.8.1 version and it works.


Implement pagination model

follow.ts, line 23: should return a Page object instead of a plain object

follow.ts, line 23: should return a Page object instead of a plain object

@paulojbleitao, just found that the follow endpoint returns a different kind of paging, we can't use the same Page implementation, so, it will be an issue :cry:


Check data from db against what's passed to backrest

It would be possible to mix up two databases by mixing up db-port and db-path when more than one cluster is running on a system.
Prevent this by checking data_directory in the database and making sure that it matches db-path.  This should make checking the version against the db obsolete since it's already done in Db->Info().
Also check that the value passed in db-socket-path begins with / so it cannot be a host name.

Implemented in a10dd8b.
Decided to keep the db version check and cross-check that against the value in pg_control.  The db has to be queried for data_directory anyway so it doesn't hurt performance and might help catch an edge case.


[Bug]: automation rules and actions did not generate audit records

ODC version
4.2.2
OB version
none
What happened?
Automatic authorization rules and actions did not generate audit records.
What did you expect to happen?
Every sensitive action about resources and privileges need to be audit.
How can we reproduce it (as minimally and precisely as possible)?
Create and trigger a automation rule.
Anything else we need to know?
No response
Cloud
No response

pass


Handle importing the immediate setup.py.

Exception occurred:
File "conf.py", line 6, in
ImportError: No module named 'setup'

Maybe instead of handling importing the immediate setup.py, I should add a new API. Not everyone imports their setup.py into their conf.py, and when they do they might handle setting sys.path.append() in their own way.
To handle conf.py's with bad/missing sys.path.append() calls (e.g. v2.2.0 of this project :P) maybe let users define callback functions in their current conf.py (ignore conf.py's in git refs, just like scv_* variables are treated) that SCVersioning calls for each git ref after forking/spawning.


[chore] Upgrade monorepo 5.15.2

Macro path update based on https://github.com/mui/material-ui/pull/40262


matter: add compile support for NuttX

Summary
A nuttx with the matter command can be compiled using cmake and enable CONFIG_MATTER option.
The matter compiled by the current script is just a lighting example of
a limited number of commands that can be tested by chip-tool.
After nuttx is connected to the LAN and the matter command is executed, other devices in the LAN, such as linux PCS, can run the following commands to scan, connect, turn on and off, adjust brightness and contrast, and so on.
chip-tool pairing onnetwork 1 20202021
chip-tool onoff on 1 1
chip-tool levelcontrol move-to-level 128 10 0 0 1 1
chip-tool colorcontrol move-to-hue-and-saturation 240 100 0 0 0 1 1
Depends on the following configuration options:
CONFIG_CRYPTO_MBEDTLS=y
CONFIG_DEV_URANDOM=y
CONFIG_LIBCXX=y
CONFIG_LIBM=y
CONFIG_NET_IPv6=y
CONFIG_NET_ICMPv6=y
CONFIG_NET_ICMPv6_AUTOCONF=y
CONFIG_NET_ICMPv6_NEIGHBOR=y
CONFIG_NET_ICMPv6_ROUTER=y
CONFIG_NET_ICMPv6_SOCKET=y
CONFIG_NET_IGMP=y
CONFIG_NET_MLD=y
CONFIG_NET_MLD_ROUTER=y
This initial version does not yet have Bluetooth and OTA support.
The community version needs to dynamically fetch the matter source code at compile time and apply the required nuttx adaptation patch.
Impact
Testing
sim:local and risc-v32 board

@zhhyu7 let's create a new patch to new ci on sim.

@zhhyu7 let's create a new patch to new ci on sim.

OK.


Go tool installer failing with 403

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: Go tool installer
Environment

Server - Azure Pipelines
Agent - Hosted

If using Hosted agent, provide agent queue name: Azure Pipelines

Issue Description
Starting: install go
==============================================================================
Task         : Go tool installer
Description  : Find in cache or download a specific version of Go and add it to the PATH
Version      : 0.180.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/tool/go-tool
==============================================================================
Downloading: https://storage.googleapis.com/golang/go1.13.windows-amd64.zip
##[error]Failed to download version 1.13. Please verify that the version is valid and resolve any other issues. Error: Unexpected HTTP response: 403
Finishing: install go

Getting the same thing:
Go Version 1.16:
2021-04-16T20:19:48.0330202Z ##[section]Starting: GoTool
2021-04-16T20:19:48.0336522Z ==============================================================================
2021-04-16T20:19:48.0337205Z Task         : Go tool installer
2021-04-16T20:19:48.0337699Z Description  : Find in cache or download a specific version of Go and add it to the PATH
2021-04-16T20:19:48.0338176Z Version      : 0.180.0
2021-04-16T20:19:48.0338551Z Author       : Microsoft Corporation
2021-04-16T20:19:48.0339009Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/tool/go-tool
2021-04-16T20:19:48.0339527Z ==============================================================================
2021-04-16T20:19:48.2072339Z Downloading: https://storage.googleapis.com/golang/go1.16.linux-amd64.tar.gz
2021-04-16T20:19:48.3352972Z ##[error]Failed to download version 1.16. Please verify that the version is valid and resolve any other issues. Error: Unexpected HTTP response: 403
2021-04-16T20:19:48.3387934Z ##[section]Finishing: GoTool

Go Version 1.16.3:
2021-04-16T20:28:11.6598627Z ##[section]Starting: GoTool
2021-04-16T20:28:11.6605295Z ==============================================================================
2021-04-16T20:28:11.6606133Z Task         : Go tool installer
2021-04-16T20:28:11.6606693Z Description  : Find in cache or download a specific version of Go and add it to the PATH
2021-04-16T20:28:11.6607215Z Version      : 0.180.0
2021-04-16T20:28:11.6607714Z Author       : Microsoft Corporation
2021-04-16T20:28:11.6608229Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/tool/go-tool
2021-04-16T20:28:11.6608788Z ==============================================================================
2021-04-16T20:28:11.8472892Z Downloading: https://storage.googleapis.com/golang/go1.16.3.linux-amd64.tar.gz
2021-04-16T20:28:12.9977132Z ##[error]Failed to download version 1.16.3. Please verify that the version is valid and resolve any other issues. Error: Unexpected HTTP response: 403
2021-04-16T20:28:13.0024796Z ##[section]Finishing: GoTool

Hi...
It works with any version listed on: https://storage.googleapis.com/golang/

The link was broken for everyone, but should be working now: https://github.com/golang/go/issues/45603

Closing this issue as link was broken and it is fixed now.


OmniFaces/PrimeFaces Namespaces

Allow this plugin to support both namespace URL and URN.
http://omnifaces.org/ui --> omnifaces.ui
http://omnifaces.org/functions --> omnifaces.functions
xmlns:p="http://primefaces.org/ui" --> xmlns:p="primefaces"
xmlns:pe="http://primefaces.org/ui/extensions" --> xmlns:pe="primefaces.extensions"

We should add a separate issue to add Omnifaces functions if it's not already there

Well i think i tried to add functions but since they are EL expressions there is nothing to AutoComplete


Icon submission: Buenbit

Icon type
Logo based
URL of the site or app
https://www.buenbit.com
Logo / icon info
Image traced of https://assets-global.website-files.com/617c7ed623b070e01c889509/617ff20f05064990d7ae786e_favicon.png
Background color info
Background color is accent color frow web page.
Upload icon(s)
Buenbit.zip
Anything else?
No response
Confirmation

[X] I have read and carefully followed CONTRIBUTING document

Image traced of https://assets-global.website-files.com/617c7ed623b070e01c889509/617ff20f05064990d7ae786e_favicon.png
With what software? Also, I highly don't recommend image tracing really low resolution images.

Use actual logo, not favicon: https://assets-global.website-files.com/617c7ed623b070e01c889509/617c7ed623b0700e0a88952a_logo_buen-bit-SVG.svg

Sorry! was in a hurry and made a mess. Originally, I used the svg logo you linked and fixed it manually as I didn't found any other proper "isotype" on their web site. I've now found the actual logo (https://app.buenbit.com/static/media/icon-logo-mobile.6b3a693c.svg) and used it to make a new svg.
As for the background color, I picked the class "highlight_blue-sky" (#1a9cff), as they use it as the accent/primary color on the landing page (https://www.buenbit.com/es-ar); on this new attached svg, I used the background color of the logo recently found (#00317a).
Hope this helps. Greeting
Buenbit.zip
s

Added to the repo!


Question:

Hi,
Awesome lib thx for this.
I need a non minified version of the lib.
How can I build one ?
Context: I'm fluent in JS but not JS build tools.
Thanks

Building it is pretty straightforward, but you need to have the repo cloned locally (with git or GitHub Desktop) and have node.js/npm installed. One you have those pieces sorted and run npm install on the project from the commandline to install all the dependencies, then run this command:
npm run build

This will generate a non-minified version.

Thanks great.
Worked.
(i had to install : npm install npm-run-all --save-dev)
Thanks again


E: Unable to locate package moby-engine

I'm attempting to set up an AMD-64 device following these instructions, when I get to 'sudo apt-get install moby-engine' I receive the error 'E: Unable to locate package moby-engine'.  I followed the same instructions on January 25th for another device without any issue.  Is there something wrong with the repository feed for 16.04 devices?

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

ID: a3b8296d-c923-e990-dcad-35ef2b908a2a
Version Independent ID: 5f85fd7b-f2b6-b3b1-6be2-b6054bb33507
Content: Install Azure IoT Edge on Linux
Content Source: articles/iot-edge/how-to-install-iot-edge-linux.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@gerfen Thank you for the valuable feedback,we are investigating the issue.

@Adam-Smith-MSFT FWIW, I discovered that the instructions here do work:  https://docs.microsoft.com/en-us/azure/iot-edge/quickstart-linux

@gerfen Did you notice this step in the instructions
"Prepare your device for the IoT Edge runtime installation, replacing  with 16.04 or 18.04 as appropriate for your release of Ubuntu."

Yes of course.  As I stated I managed to get it to work with another device and by following the instructions in the latter link.  Either the  current instructions are incorrect or there was a temporary glitch with the repository.  I'll leave that to your team to figure out.  :). Thanks!

Thanks for confirming. The instructions are in fact the same for both pages, so we'll chalk it down to a repository glitch. Glad you are unblocked now.
Feel free to reach out via github.com/azure/iotedge/issues if you have any questions.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

the error still persistent on Raspberry Pi OS Stretch.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Please check my post.

@veyalla can you confirm if we have fixed this issue or shall we request more details from @talalgit environment? Let me know if I should reopen this thread or we can create a new issue here: https://github.com/Azure/iotedge/issues
Thanks!

From the screenshot, I see sudo apt-get update was not run after adding the MS repo info as noted in the doc. If issues persist after that, please open an issue in https://github.com/azure/iotedge/issues

We are encountering the same issue when installing onto Ubuntu 18.04.  See below (cleaned user specific data from the path):
root@pingioted01:/home/# sudo apt-get update
Hit:1 http://ca.archive.ubuntu.com/ubuntu bionic InRelease
Hit:2 http://ca.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:3 http://ca.archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:4 http://ca.archive.ubuntu.com/ubuntu bionic-security InRelease
Reading package lists... Done
root@pingioted01:/home/# sudo apt-get install moby-engine
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package moby-engine

My problem is resolved.  I missed a step in the install.


nodemon is used in production

nodemon is useful for local development when we want to refresh our server as we make changes. We probably want to just npm run start which runs node index.js. It is also a developer dependency. Maybe we should just make it run nodemon on npm run watch.

Resolved by changing scripts to start: node src/index.js and dev: nodemon ....
This was never deploying with nodemon in prod though

Good to know, however npm run start is usually ran in node containers so best practice to seperate it. The task for nodemon is usually npm run watch as it runs it and watches for changes.


Replace sprintf to native concat and itoa.

Thanks, but I'd rather stick with the established coding style.


Added contributors names

Fixes Issue🛠

Closes #1382
Description👨💻

Added contributors name
Type of Change📄

[ ] Bug fix (non-breaking change which fixes a bug)
[X] New feature (non-breaking change which adds functionality)
[ ] Style (non-breaking change which improves website style or formatting)
[ ] Documentation (non-breaking change which updates or adds documentation)
[ ] Responsiveness (non-breaking change which improves UI/UX on different screen sizes)

Checklist✅

[X] I am an Open Source contributor
[X] I have performed a self-review of my code
[X] My code follows the style guidelines of this project
[X] I have commented on my code, particularly in hard-to-understand areas

Screenshots/GIF📷

@Rakesh9100 Please review the pr and let me know if any further changes are required

The code and functionality are working as expected, but the API rate limit is being exceeded, which I will address @saadgibawa


None files match should not throw

When none files match the pattern test/**/*.test.js, call mocha with --opts will throw Error: cannot resolve path (or pattern) 'test/**/*.test.js'. The pattern for glob is ok, even though its return files.length = 0. So I think this case should not be considered as an error.
The code in mocha is:
      files = glob.sync(path);
      if (!files.length) {
        throw new Error("cannot resolve path (or pattern) '" + path + "'");
      }

@kiliwalk Thanks for the suggestion.  Can you explain why this is problematic?  It seems like reasonable behavior to me, and is exhibited by other test runners (if you would consider the mocha executable to be a "test runner").

I'm now creating a toolset to use mocha to test. When I tested it with none-match case, the throw error made me confused. I thought maybe my pattern was wrong format till I found the code.
I agree that throw error is reasonable as you said, but how about to change the error description? Like Cannot find any files to match the pattern + path, or something like this?

@kiliwalk Would accept PRs for any and all improvements to error messaging!


WIP: 612 yarn timeline v2

Which issue(s) this PR fixes

Fixes #623
Additional comments

Work in progress: I'm not able to get the Timeline server V2 rest api up currently.
Agreements

[x] I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004.
[x] I hereby agree to grant TOSIT a copyright license to use my contributions.

Please, do not merge master in your branch, use rebase instead.

Please, do not merge master in your branch, use rebase instead.

Yes, I will rollback this and do a rebase ; I did it (I thought I did it only on my local copy) to catch up with the release quickly. It was not aimed to be pushed.


TCP proxy API: Weighted clusters and cluster_from_sni

API changes to support weighted clusters (https://github.com/envoyproxy/envoy/pull/4430).
In addition, add an option to select the upstream cluster
based on the SNI value. This will be used for cross cluster routing in Istio,
where traffic from one cluster lands on the gateway Envoy in another
cluster, carrying the cluster name in the SNI field. The gateway envoy
would then forward the traffic to the appropriate upstream cluster.
(In some sense, its pretty similar to the cluster_header field in HTTP Route).
PR with implementation will follow shortly. Wanted to get the API out so as to
not conflict with Venil's PR (https://github.com/envoyproxy/envoy/pull/4430) for
weighted cluster implementation.
Signed-off-by: Shriram Rajagopalan<EMAIL_ADDRESS>

cc @PiotrSikora & @louiscryan (per offline discussion).
FYI @venilnoronha this is the weighted cluster spec I mentioned in your PR.
There is some scope for reuse of the WeightedClusters struct, but its nestled in HTTP route, with a bunch of HTTP specific things like add/remove request headers.

Alright. I am closing this, as we decided to make the cluster name optional in a TCP proxy (in fact, its already optional!, looking at the code). Will try to do the DynamicMetadata (i.e FilterState) that sets the cluster and use it in TCP proxy..


Extend Cisco AAA model template with missing fields

Pull Request summary:
Extend the AAA template with missing functionalities.
Description of changes:
Added missing variable which is required during modification of the template and missing device models.
Checklist:

[x] Make sure to run pre-commit before commiting changes
[x] Make sure all checks have passed
[x] PR description is clear and comprehensive
[x] Mentioned the issue that this PR solves (if applicable)
[x] Make sure you test the changes

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/pull/325


Callouts on image markers working randomly

I'm using custom image markers with default callouts, here's my code:
<MapView.Marker
	key={location.id}
	coordinate={{
		latitude: ParseDMS(location.latitude),
		longitude: ParseDMS(location.longitude),
	}}
	image={location.locationType == 'food' ? iconFood : iconHerbs}
	title={location.title}
	description={'Vestibulum id ligula porta felis euismod semper.'}
	onPress={() => console.log('lol press')}
	calloutVisible={true}
	>
</MapView.Marker>

Callouts only show up on press when there's one marker wrongly fixed to the top left corner, as mentioned in #499

Whenever that bug stops showing up (which is random) the markers stop working.
Anybody having the same problem?

https://github.com/airbnb/react-native-maps/issues/553

#553


[Request] Reducing the spacing between paragraphs

Is there a way to reduce the spacing between paragraphs? It feels like the space between each is abit too much making it look abit awkward.

upcoming CSS changes will fix this.


Indent menu when first menu item is not rendered all the way on the left side.

I wanted to put an app title at the start of the line, but noticed that the menu renders at the left side of the window:
impl Widget for &mut App {
    fn render(self, area: Rect, buf: &mut Buffer) {
        use Constraint::*;
        let [top, main] = Layout::vertical([Length(1), Fill(1)]).areas(area);
        let [title, menu] = Layout::horizontal([Length(10), Fill(1)]).areas(top);

        Paragraph::new(self.content.as_str())
            .block(Block::bordered().title("Content").on_black())
            .render(main, buf);

        "tui-menu"
            .bold()
            .blue()
            .to_centered_line()
            .render(title, buf);

        // draw menu last, so it renders on top of other content
        Menu::new().render(menu, buf, &mut self.menu);
    }
}

Renders as:

This is probably a super easy fix, but I wanted to check if @shuoli84 had any feedback before implementing it.
It would be a good idea to indent

That's a nice feature to implement. 👍


Topological Sort code C++

Can I contribute in this as part of Hacktober fest?

Hey @Taneesha-creates , this will be my 4th issue in this repository can I take it or my limit is up


fix: suppress spell check failure to ignore LOBF, bcnn, CTRV and DLCPU

Description
In https://github.com/autowarefoundation/autoware.universe/pull/6432, json-schema-check is not working for some reasons.
So I recreate.
I fix spell check failures to ignore LOBF, bcnn, CTRV and DLCPU.
I followed ↓.
https://github.com/autowarefoundation/autoware.universe/blob/6b1a459a138bb04f1fcf5f8c9c160718032ce65d/common/tvm_utility/data/models/abs_model_aarch64/inference_engine_tvm_config.hpp#L40
Related links

Tests performed

Notes for reviewers

Interface changes

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

I found that json-schema-check is required action but it does not need for this PR because I don't edit schema.json or param.yaml.
https://github.com/autowarefoundation/autoware.universe/blob/main/.github/workflows/json-schema-check.yaml#L3-L8
https://github.com/autowarefoundation/autoware.universe/pull/6432 does not has any problem, so I reopen it.


PDF Element linking to external source not persisted

Description
I've encountered an issue where the PDF element that links to an external source is not being persisted. I am using the Data Persistence feature with Literal AI (formerly Chainlit Cloud). Specifically, when I reopen an old thread, the PDF element is missing. I.e., during a new chat, the PDF element is open-able via the link in the message. However, when re-opening the thread, the same link is no longer available. The PDF element is also not found as an attachment on cloud.getliteral.ai. This seems to be a potential bug, but I am unsure if this behavior is intended or not.
Steps to Reproduce

Define callback on receiving a new message from the user.

@cl.on_message
async def main(message: cl.Message):
    image = cl.Image(path="./data/test_welcome.png", name="image1", display="inline")
    pdf = cl.Pdf(name="pdf1", url="https://www.w3.org/WAI/ER/tests/xhtml/testfiles/resources/pdf/dummy.pdf", display="side")
    text = cl.Text(name="text1", content="miau", display="side")
    # Attach the image to the message
    await cl.Message(
        content=f"This message has an image! image1, pdf1, text1"
        elements=[image, pdf, text],
    ).send()

Create a new chat in the browser.
Create a new message and interact with the elements.
Close the browser or switch threads.
Reopen the same thread.

Expected Behavior
The PDF element linking to an external source should be persistent and visible upon reopening the thread.
Actual Behavior
The PDF element is missing when the thread is reopened.
Potential Cause
I have identified some lines of code that seems to be causing this issue:
chainlit/element.py:126
@dataclass
class Element:
    # [... omitted ...]
    async def _create(self) -> bool:
        if (self.persisted or self.url) and not self.updatable:
            return True
        # [...]

Additional Information

Chainlit version: 1.0.101, 1.0.200

It would be helpful to get clarification on whether this is a bug or intended functionality, and if it's a bug, any guidance on potential fixes would be appreciated. I'd be able to create a corresponding pull request.

Hi. thank you for this bug report, I was able to reproduce the bug. I am working on a fix.

Should be fixed with today's release!


python.testing.cwd ignored when discovering or running tests

Environment data

VS Code version: 1.40.1
Extension version (available under the Extensions sidebar): 2019.11.49689
OS and version: MacOS Catalina 10.15.1
Python version (& distribution if applicable, e.g. Anaconda): 3.7.4
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
Relevant/affected Python packages and their versions: pytest==5.3.0
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): Jedi

Expected behaviour
Tests are displayed in the test explorer according to python.testing.cwd setting and I am able to run single test or tests from single file
Actual behaviour
python.testing.cwd is ignored for displaying tests and I am unable to run single test or tests from single file because I am getting an error file not found.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
Sample project: https://github.com/pbotsman/sample_project

Open project
Open tests/py/some_test.py to start exploring tests
Try to execute single test test_something or tests in some_test.py file.
Get the error ERROR: file not found: ./tests/py/some_test.py::test_something
(Sometimes in order to reproduce the problem I had to relaunch my VSCode)

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
> ~/.virtualenvs/sample_project/bin/python -m pytest --rootdir ~/projects/sample_project --junitxml=/var/folders/0_/6w94lk1171vc_fpwbjqx02nw0000gn/T/tmp-4746yxdv7Lw3muwB.xml -v -s --log-cli-level INFO ./tests/py/some_test.py::test_something
cwd: ~/projects/sample_project/tests/py

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
console.ts:137 [Extension Host] Info Python Extension: 2019-11-20 14:06:31: getActivatedEnvironmentVariables, Class name = b, completed in 1ms, Arg 1: <Uri:/Users/pavel/projects/sample_project>, Arg 2: undefined, Arg 3: undefined
console.ts:137 [Extension Host] Info Python Extension: 2019-11-20 14:06:31: > ~/.virtualenvs/sample_project/bin/python -m pytest --rootdir ~/projects/sample_project --junitxml=/var/folders/0_/6w94lk1171vc_fpwbjqx02nw0000gn/T/tmp-5598WI4lpp4kFEsC.xml -v -s --log-cli-level INFO ./tests/py/some_test.py::test_something
console.ts:137 [Extension Host] Info Python Extension: 2019-11-20 14:06:31: cwd: ~/projects/sample_project/tests/py

Additional info

Looks like something has changed in the last release:

Previously tests would be displayed in the test explorer just as some_test.py would be root test. I mean that tests/py would be omitted in the test explorer since I have "python.testing.cwd": "tests/py" in my settings.
Currently directories tests/py are displayed in the test explorer even though I have this setting.
I can't run single test because I am always getting an error file not found. It looks like something is wrong with the file paths.
When the command
~/.virtualenvs/sample_project/bin/python -m pytest --rootdir ~/projects/sample_project --junitxml=/var/folders/0_/6w94lk1171vc_fpwbjqx02nw0000gn/T/tmp-5598WI4lpp4kFEsC.xml -v -s --log-cli-level INFO ./tests/py/some_test.py::test_something
is called my current working directory is set to python.testing.cwd and that is why I am getting the error.
So in the command mentioned above valid file path should be ./some_test.py::test_something, not ./tests/py/some_test.py::test_something.

Thanks for the bug report! We just wanted to quickly acknowledge we received it and we will triage this as soon as we can.

Hi @pbotsman 👋 Thank you for reaching out and thoroughly filling out the issue template 👍
Seems like we don't take python.testing.cwd into account when running single tests using pytest.
A possible workaround while waiting for a fix would be to move the content of python.testing.cwd in the list of pytest arguments, let me know if the following works for you:
{
    "python.pythonPath": "/path/to/python",
    "python.testing.pytestArgs": [
        "./tests/py",
        "-v",
        "-s",
        "--log-cli-level", "INFO",
    ],
    "python.testing.unittestEnabled": false,
    "python.testing.nosetestsEnabled": false,
    "python.testing.pytestEnabled": true
}

Hi @kimadeline,
Thanks for the workaround. This is exactly what I did 👍

FWIW, I just stumbled upon this, and would love to see a fix that changes the working directory to python.testing.cwd before running pytest.

@bhrutledge Please upvote the original comment to help up prioritize it.
Thanks!

I am running into this problem too - I am working in a team where others are using different IDEs... within their environment, their tests load a file from the same directory as the code.
Even with adding the directory to the execution path to python.testing.unittestArgs the current working directory still is not set, and I need to change the paths to the data files in order for the tests to pass.

Any progress or workarounds for this issue? Setting option  "python.testing.pytestArgs": ["--rootdir=path/to/root"] doesn't help.

Seems like we don't take python.testing.cwd into account anymore when discovering tests, or running single tests using pytest.

This looks like a bug. It also seems to affect the unittest tests. Setting python.testing.cwd has zero effect on them.
# python.testing.cwd == <workspace_root>/sdk/python

# Here is what I see during test discovery:

> .../python .../.vscode/extensions/ms-python.python-2020.4.74986/pythonFiles/pyvsc-run-isolated.py -c "
import unittest
loader = unittest.TestLoader()
suites = loader.discover(".", pattern="*test*.py")
print("start") #Don't remove this line
for suite in suites._tests:
    for cls in suite._tests:
        try:
            for m in cls._tests:
                print(m.id())
        except:
            pass"
cwd: <workspace_root>

See how the bottom line prints a different value of cwd.

Any progress or workarounds for this issue? Setting option  "python.testing.pytestArgs": ["--rootdir=path/to/root"] doesn't help.

That seems to be because the extension sets --rootdir to ${workspaceFolder}, overriding anything you've specifically set there.

Disclaimer: I have about zero days experience with Typescript, and the vscode-python extension... however I think the issue might have stemmed from this commit:
"Force the pytest root dir to always be the workspace root."
https://github.com/microsoft/vscode-python/commit/9fe2a76322236bf752fe36e4e4230b2d2036ddff

I had a similar problem and in my case the problem was this, basically pytest doesn't add the directory to the PYTHONPATH for me solution 3 seems the most appropriate, simply create a conftest.py file in your root directory you want to run the tests from and Voila.
Also related to #10005

This looks like a bug. It also seems to affect the unittest tests. Setting python.testing.cwd has zero effect on them.

I can confirm that it affects unittest tests as well. Interestingly, when running the whole test-suite ("Run All Tests") cwd is correctly set to the folder containing the tests files (even without setting python.testing.cwd at all). When I run a single test, cwd is set to the workspace-root, regardless of the python.testing.cwd setting.

This also has the folow up effect of breaking a pattern of referencing ${PDW} in an envFile when setting PYTHONPATH for example. I use  PYTHONPATH=${PWD}/public:${PWD}/instruments/common:${PWD}/motor Which works for running and debugging as well as when activating the environment with pipenv but $PWD expands to my home when used during test discovery which breaks that.

python.testing.cwd is needed f.e. in cases where some config files are being read from cwd. Without it, I can't set the proper testing discovery.

python.testing.cwd is needed f.e. in cases where some config files are being read from cwd. Without it, I can't set the proper testing discovery.

Hi, I can confirm that this issue does not appear to have been resolved and I have similar behaviour.

Yeah I'm having this issue with nosetests in vscode -  some tests need to be run in specific directories and there doesn't seem to be any workaround other than creating launches for each test

This bug actually forced me to switch to Pycharm. I experienced the bug using unittest. I hope it get's resolved soon!

Hey folks, sorry for the frustration with this issue. We're planning to tackle this and many other testing bugs once we migrate into VS Code's testing API (https://github.com/microsoft/vscode-python/issues/15750), but we don't have an ETA for that yet.
In the mean time, adding "--rootdir","path_to_desired_cwd"  to pytestArgs should give a workaround for this issue. So for the sample in the opening comment of this issue, it would look like this:
    "python.testing.pytestArgs": ["--rootdir","./tests/py"],

@flyte you had mentioned setting this up didn't work for you, would you mind sharing your project structure so we can see what's going on?

I've tried using pytestArgs but it doesn't appear to be used and still seems to use -rootdir ${workspaceFolder} -s unit_tests

@flyte you had mentioned setting this up didn't work for you, would you mind sharing your project structure so we can see what's going on?

I can barely remember which project I worked on five weeks ago let alone five months 😅
If I come across this again I'll post more details but otherwise I'm afraid it's lost to history.

@ChildishGiant and just to make sure, you have the tests set up to use pytest and not unittest (i.e. "python.testing.pytestEnabled": true in your settings)?
if you could share your .vscode/settings.json and your project structure, that would help a lot! 😊

The only relevant settings are this:
"python.testing.pytestEnabled": true,
"python.testing.pytestArgs": ["--rootdir","${workspaceFolder}/unit_tests"]

In my project all my tests are under a unit_tests folder. It reads files relative to that folder but the command used in Test Log discover pytest -- --rootdir f:\code\cloverleaf\web -s unit_tests, not --rootdir f:\code\cloverleaf\web\unit_tests. I've also tried without ${workspaceFolder} but have had no luck.

I have also noticed after setting rootdir in python.testing.pytestArgs in either
"python.testing.pytestArgs": ["--rootdir","${workspaceFolder}/unit_tests"]

or
"python.testing.pytestArgs": ["--rootdir=${workspaceFolder}/unit_tests"]

The unit test results (pass or fail) are no longer updated in the TEST explorer.

@luabud
As @danstreeter and I pointed out before, the issue is that this extension forces the --rootdir parameter to pytest to be set to the workspaceFolder.
The fix is to perhaps have this as the default, but allow users to override the argument in their settings.
The problem was introduced here https://github.com/microsoft/vscode-python/commit/9fe2a76322236bf752fe36e4e4230b2d2036ddff#

@karthiknadig great to see that you took over.

Merged a fix for this just now to main. Fix is essentially what https://github.com/microsoft/vscode-python/issues/8678#issuecomment-808210852 said. If there is --rootdir in python.testing.pytestArgs, we won't override it. so for the sample repo, the settings change would be:
{
    "python.testing.pytestArgs": [
        "-v",
        "-s",
        "--log-cli-level",
        "INFO",
        "--rootdir",
        "tests/py"
    ],
    "python.testing.unittestEnabled": false,
    "python.testing.pytestEnabled": true
}

That should work:

Try this out with this build https://github.com/microsoft/vscode-python/suites/3858667759/artifacts/95863817 if that doesn't work please provide repro steps.

Works for me
Had to restart VS Code in order tests to appear in the sidebar without being nested inside tests directory

(Apologies if this is a rediculously silly question...)
Can I install the aformentioned vsix extension on my day-to-day working VSCode instance without risk of completely breakign it without any way back?!
Can it be uninstalled once installed when this fix reaches launch?

@danstreeter You can install this and uninstall to restore your VS Code to stable extension or any extension version.
Here is how you would do it:

Install the VSIX using Extension tab > ... > Install from vsix... option from the "..." menu.
You may have to Reload VS Code (command pallet Reload Window command). Test out to see if this works for you.
To revert back, Go to extensions tab, find the python extension and Uninstall it.
Reload VS Code (command pallet Reload Window command), go to extensions tab and install from market place. This should get you back to stable build of the extension.

Note, you can also click on the 'Gear' icon next to the extension in the extensions tab to install a specific version using "Install Another version..."
If you want to try this out is complete isolation, you could install VS Code Insiders (which can install side by side with your stable one) and install this vsix there and test it out. then uninstall the whole thing. This way it won't touch your day-to-day VS Code instance.

Thanks @karthiknadig, I've got it installed in my main 'day-to-day' instance however still not quite working for me...
Using the default provided config after 'configuring tests', I end up with the followign in my settings file:

Thanks @karthiknadig , I've got it installed in my main 'day-to-day' instance however still not quite working for me...
Using the default provided config after 'configuring tests', I end up with the following in my settings file:
    "python.testing.pytestEnabled": true,
    "python.testing.pytestArgs": [
        "tests"
    ],

This matches my project layout, as all tests are stored in the ./tests directory with all actual code in ./src
Running my tests with my normal workflow still works fine by running make test which actually runs:
export PYTHONPATH=./src
pipenv run python -m pytest tests

When performing discovery with the above config, I get the following in the Python output:
~/path-to-code/.venv/bin/python3.8 ~/.vscode/extensions/ms-python.python-2021.10.1267871984-dev/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir  -s --cache-clear tests
Error 2021-09-24 19:51:20: Error discovering pytest tests:
 [r [Error]: ============================= test session starts ==============================
platform darwin -- Python 3.8.5, pytest-6.2.4, py-1.10.0, pluggy-0.13.1
rootdir: /
plugins: asyncio-0.15.1, html-3.1.1, metadata-1.11.0
collected 0 items

I also get the following warning:
PytestCacheWarning: could not create cache path /.pytest_cache/v/cache/stepwise

Also, if I add any --rootdir to the config as follows:
    "python.testing.pytestEnabled": true,
    "python.testing.pytestArgs": [
        "--rootdir",
        "my-root-dir-fake-name",
        "tests"
    ],

The error change as 'expected' with the root directory and trys to target a path on root:
~/path-to-code/.venv/bin/python3.8 ~/.vscode/extensions/ms-python.python-2021.10.1267871984-dev/pythonFiles/testing_tools/run_adapter.py discover pytest -- -s --cache-clear --rootdir my-root-dir-fake-name my-root-dir-fake-name
Error 2021-09-24 19:53:03: Error discovering pytest tests:
 [r [Error]: ERROR: Directory '/my-root-dir-fake-name' not found. Check your '--rootdir' option.

Why is it trying to target root?

OOH OOH OOH - I FIXED IT!!!
I needed an absolute path in the rootdir... Using my pseudo, sanitised example above - this now works!
    "python.testing.pytestEnabled": true,
    "python.testing.pytestArgs": [
        "--rootdir",
        "/full/path/to/my/path-to-code",
        "tests"
    ],

@danstreeter can you try:
"python.testing.pytestEnabled": true,
    "python.testing.pytestArgs": [
        "--rootdir",
        "./tests"
    ],

Doing the above gives:
> ~/path-to-code/.venv/bin/python3.8 ~/.vscode/extensions/ms-python.python-2021.10.1267871984-dev/pythonFiles/testing_tools/run_adapter.py discover pytest -- -s --cache-clear --rootdir ./tests ./tests
Error 2021-09-24 20:00:44: Error discovering pytest tests:
 [r [Error]: ERROR: Directory '/tests' not found. Check your '--rootdir' option.

@danstreeter Are you missing the '.' before the './tests'? Just checking because '/tests' will not work.

Definately there:

I see. Thanks for the input. This should work for most case with this:
    "python.testing.pytestEnabled": true,
    "python.testing.pytestArgs": [
        "--rootdir",
        "${workspaceFolder}",
        "tests"
    ],

I will tweak it, it seems like for some reason, the cwd gets set to `` (empty) string instead of . which seems to be the problem here. But that is unrelated to this.

@karthiknadig IMHO it is safer to  use
    "python.testing.pytestEnabled": true,
    "python.testing.pytestArgs": [
         "--rootdir=${workspaceFolder}/tests"
    ],


Better issue templates

Better templates for Bugs, issues and questions.
Automatically add labels for bug and enhancements.

@DonJayamanne this is currently breaking the bot's workflow as it can't tell that you meant to leave the classify label on since the instant you add any label it takes it off, so the automatic "type" labels strip it off. That means the bot needs updating or we drop the added label. We will also need to go back and check for issues lacking any labels but "type" to make up for the ones we overlooked.

@brettcannon 	I'll remove the automatic type labels.


build: Disable dry-run

:tada: This PR is included in version 1.0.0-next.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


compile fails

Maven targets Java 1.5 by default, so this example that uses features of Java 1.8 is not going to compile.  Did you have some settings in your ~/.m2/settings.xml file that were not captured in this repo?
$ mvn compile
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building sparksocket 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ sparksocket ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ sparksocket ---
[INFO] Changes detected - recompiling the module!
[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!
[INFO] Compiling 2 source files to /Users/cswarth/Development/spark-websocket/target/classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /Users/cswarth/Development/spark-websocket/src/main/java/Chat.java:[10,63] diamond operator is not supported in -source 1.5
  (use -source 7 or higher to enable diamond operator)
[ERROR] /Users/cswarth/Development/spark-websocket/src/main/java/Chat.java:[21,59] method references are not supported in -source 1.5
  (use -source 8 or higher to enable method references)
[ERROR] /Users/cswarth/Development/spark-websocket/src/main/java/Chat.java:[21,83] lambda expressions are not supported in -source 1.5
  (use -source 8 or higher to enable lambda expressions)
[INFO] 3 errors

I fixed this issue by adding the appropriate <configuration> directives to the pom.xml file.  While I was at it, I also updated the build to use the latest version of the spark API (v2.5).  I had to add an explicit dependency on slf4j-simple or the app would fail at runtime due to lack of a logging implementation.
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>sparksocket</groupId>
    <artifactId>sparksocket</artifactId>
    <version>1.0-SNAPSHOT</version>

    <dependencies>
        <dependency>
            <groupId>com.sparkjava</groupId>
            <artifactId>spark-core</artifactId>
  	    <version>2.5</version>
        </dependency>
        <dependency>
            <groupId>com.j2html</groupId>
            <artifactId>j2html</artifactId>
            <version>0.7</version>
        </dependency>
  	<dependency>
  	  <groupId>org.slf4j</groupId>
  	  <artifactId>slf4j-simple</artifactId>
  	  <version>1.7.21</version>
  	</dependency>
    </dependencies>
  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>3.5.1</version>
        <configuration>
          <source>1.8</source>
          <target>1.8</target>
        </configuration>
      </plugin>
    </plugins>
  </build>
</project>

Sorry about that, I just pushed the change :)

I guess I can migrate to 2.5 while we're at it.


One question regarding padding

hi,
I see that you are padding the inputs to get equal length of 52. But, it seems padding is applied to only character inputs but not to words.
 # 0-pads all words
 def padding(Sentences):
     maxlen = 52
     for sentence in Sentences:
         char = sentence[2]
         for x in char:
             maxlen = max(maxlen, len(x))
     for i, sentence in enumerate(Sentences):
         Sentences[i][2] = pad_sequences(Sentences[i][2], 52, padding='post')
     return Sentences

Sentences contains below:
         dataset.append([wordIndices, caseIndices, charIndices, labelIndices])
     return dataset

I see that you have made batches of inputs with words of equal length.  Is this the correct approach?
Can you pls let me know.

Hello! That's correct. This is because the convolutional neural net (CNN) processes the padded character vectors of equal length. Alternatively, one could split the CNN input into equal-size batches (e.g. here). Each input batch to the bi-directional LSTM has the same length, depending on how many words there are in a document.

Thank you for responding. One follow up question.
What was the rationale behind padding characters to a maximum length of 52. There will be 26 upper case letters, 26 lower case letters and other punctuation characters.  Can you pls let me know?

A maximum length was chosen after analyzing the longest words in the documents, such that no words are cut off.

There is some confusion. In my understanding, padding is applied to only characters not to words.

Padding is indeed applied to characters. For example, the padded character-level input below is for the word "RECORD". The output of the padding(Sentences) function is a list of documents of a list of words, cases, characters and labels (see output of the createMatrices(sentences, word2Idx, label2Idx, case2Idx, char2Idx) function.


wip-catalog chart's apiserver svc type dependent on debug?

The wip-catalog Helm chart has the apiserver's Service type dependent on whether debug=1 is set or not.
I can't understand why the type of service we use should be dependent on whether we're debugging or not. Additionally, when debugging, one gets a service of type: LoadBalancer and that avoids this error, which arises if not debugging  / using service of default type: ClusterIP:
$ helm install     --set "registry=${REGISTRY},version=${VERSION}",storageType=etcd,insecure=true     --namespace catalog     ./deploy/wip-catalog
Error: release lumpy-bee failed: Service "apiserver" is invalid: spec.ports[0].nodePort: Invalid value: 30001: may not be used when `type` is 'ClusterIP'

https://github.com/kubernetes-incubator/service-catalog/blob/master/deploy/wip-catalog/templates/apiserver.yaml#L59-L61

I am moving this out of MVP 1

This was addressed when the charts were completely re-written in #546. Closing.


fix pylint errors

This PR aims to resolve all the pylint errors.
I choose to disable the following rules:

W0107 - unnecessary pass
We might need this for parent classes which haven't implemented the method but also dont want to throw an error

W0702: No exception type(s) specified (bare-except)
Useful when we need to catch all the exceptions

R0801: Similar lines in 2 files.
Disabled because it flags any file even those which are unrelated such as rapidast.py and updater_config.py

R1705: Unnecessary "elif" after "return", remove the leading "el" from "elif" (no-else-return):
I think this is a personal style preference. I personally like the elif as it makes it immediately clear to me (without reading the if block code) that we will only take this branch if the if block fails

R1710: Either all return statements in a function should return an expression, or none of them should. (inconsistent-return-statements)
Disabled because this is not feasible when creating recursive functions or even functions which might possibly return None

To fix the eval error, I implemented a safe_add function which safely evaluates all strings that are a simple addition or subtraction expression. I could have added another package such as simpleeval but since our use case was very basic it didn't make sense to add another dependency

What do you think about adding C0209 too? so that we can use both string.format() and f-string.

I didn't add that cause I thought we might want consistency across the project? f-string is just supposed to be more readable. Let me know if we want both, I will disable C0209 as well then

@cedricbu WDYT? your call, as it's related to https://github.com/RedHatProductSecurity/rapidast/blob/development/scanners/zap/zap_podman.py#L53


Add support for touch events to violent theremin demo

It would be nice to be able to use the demo in a touch environment (eg: phone or tablet). (Not required: sound could be continuous after a 'start/down' event until an 'end/up' event is received)

(side-note: the event listeners for triggering init should be removed in init, otherwise using the keyboard causes init to be triggered multi times, and DOMExceptions when trying to remove the startMessage that has already been removed).

Issue moved to mdn/content #1448 via ZenHub

Issue moved to mdn/content #1448 via ZenHub


Sonar class configuration

Address following error:
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:<IP_ADDRESS>22:sonar (default-cli) on project customer-feedback-api: Your project contains .java files, please provide compiled classes with sonar.java.binaries property, or exclude them from the analysis with sonar.exclusions property. -> [Help 1]

CI: Security warnings found!


TeaVM dependencies update

Uses the new TeaVM dependencies.
Updates to the latest TeaVM beta release instead of snapshots. Attempts to fetch the TeaVM backend version from Maven Central.
Adds @SkipClass to the TeaVM builders.
Refactors the Kotlin TeaVM launcher and builder.

This seems to work fine; I haven't tried refreshing the dependencies yet, but the project generates fine, as far as I can tell. Merging!


Deployment: support solution deployment in opt-in regions (e.g. Hong Kong, Milan)

Describe the feature
The solution cannot be deployed in opt-in regions like Hong Kong, Milan regions. The root cause is that the solution comes with a built-in console which is served via CloudFront. However, CloudFront cannot output logs to S3 buckets in opt-in regions.
Use Case
As a customer, I'd like to deploy the solution in Hong Kong, Milan and other opt-in regions.
Proposed Solution
No response
Other Information
No response
Log Hub version used
v1.1.0

Since Cloudfront in AWS OpsIn Region (such as Hong Kong,  Milan, Bahrain) currently does not support the function of logging to the bucket of this region, it is necessary to manually modify the Cloudformation template to deploy Log Hub.
Here is the workaround for Log Hub v1.1.0 to deploy in AWS OpsIn Region.
Step 1. Download the v1.1.x Log Hub OIDC template.

Click: https://aws-gcr-solutions.s3.amazonaws.com/log-hub/v1.1.0/LogHubWithOIDC.template

Step 2. Delete the Logging property in CloudFormation template.

Open the template which downloaded in step1.
Search for "Logging": {
Delete the Logging property.
Save the template.

Step3. Create a CloudFormation Stack by upload edited template


[ROCm] creating a wrapper for the rocblas lib, and updating all calls to use the wrapper

/cc @cheshire @chsigg

@deven-amd  Can you please resolve conflicts? Thanks!

@gbaned done.  rebased PR to resolve the merge conflicts


azurerm: added synapse eventhub purview

Changes:

added synapse eventhub purview
upgraded azure-sdk-for-go to v57.1.0
fixed cosmodb API changes between v42 and v57
updated data_factory docs

@sergeylanzman
Could you review this new PR, please?

@sergeylanzman

thanks for your speedy reply
previous interation got stuck at the cia/google check
triggering the googlebot manually cleared the pending verification
Now I think that it's ready and unblocked.

Can we proceed with this PR? 😄


The model for the report output version 1

Type of issue
Other (describe below)
Description

--output-version
Sets the report output version. Allowed value is 1. Defaults to 1. Requires the --format json option. When a new JSON version is available, the command will produce the new format by default. This option will let you specify that the command should produce an earlier format. Available starting in .NET SDK 7.0.200.

Can someone help me find the model for the report output version 1? Is it somewhere on the GutHub?
Page URL
https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-list-package
Content source URL
https://github.com/dotnet/docs/blob/main/docs/core/tools/dotnet-list-package.md
Document Version Independent Id
3d4b052c-33fa-cc83-4df6-4a3341f12763
Article author
tdykstra

Associated WorkItem - 183672

The answer is here.

@tdykstra thanks but