Explore support for developing on WSL

WSL allows you to run linux program on Windows. We are looking into providing support for working with WSL when Code runs on Windows.  This is related to https://github.com/Microsoft/vscode/issues/29194.
Other related items are:

https://github.com/Microsoft/vscode/issues/9502
https://github.com/Microsoft/vscode/issues/13138
https://github.com/Microsoft/vscode/issues/20220
https://github.com/Microsoft/vscode/issues/22663
https://github.com/Microsoft/vscode/issues/28667
https://github.com/Microsoft/vscode/issues/50795

Here is the query of all open issues labeled with WSL: query

Just a heads-up, for reference, most JetBrains IDEs now support WSL interpreters without the remote-interpreter-over-ssh workaround. It's available in PyCharm 2018.3, RubyMine 2017.3, WebStorm 2018.2.

Just a heads-up, for reference, most JetBrains IDEs now support WSL interpreters without the remote-interpreter-over-ssh workaround. It's available in PyCharm 2018.3, RubyMine 2017.3, WebStorm 2018.2.

As for JetBrains IDEs, it's true and nice but as for Python (PyCharm), virtualenvs are not supported so at least for me, this makes this feature useless. Unfortunately.

Yes, a totally agree with uishon. Vscode is from windows and now the python package too (and the top downloaded package). I think they should focus more on getting the best integration between vscode, python and WSL.
When I'm doing Django development on windows, I need to use wsl because I got some bugs on translations and channels for example. If I use that, I can't set the python linter for vscode.
The fix I needed to do was have two virtualenvs, one for windows and another to WSL.

Does debugging through docker work?

Oh god yes!
I need this. The integration today is really bad, and actually causes a lot of problems.
Support for WSL git as the main source control, but also critical for language extensions (Node, Dotnet, Python, Go). The lack of support currently means I have to have SDKs for all languages installed under both Windows and WSL
Don't forget tasks and debug also have massive issues with WSL today, with path translations and locating binaries. Trying to get a set of clean launch configs that work on any developers system is impossible

Also the filenames and project folder would need transform before passing into wsl
e.g. C:\your\workspace -> /mnt/c/your/workspace
when using wsl:// schema

Shame that every month this moves out another month. I wouldn't mind but some news on progress, what is being worked on/investigated would give us WSL users some hope! 😁

Have you gentle people seen this announcement about the next Windows feature update and \\wsl$? I think this might neatly solve the problem, but of course, I do not have that Windows version yet, so I can't say for sure.

@dscho Thanks for the heads up on that. Pretty cool, but it only enables you to interact with wsl files. There still needs to be more work on having the vscode instance be able to work with linux binaries, unless I'm missing something.
I tried setting git.path to \\wsl$\Ubuntu\usr\bin\git (technically \\\\wsl$\\Ubuntu\\usr\\bin\\git in settings.json) to no avail

I tried setting git.path to \\wsl$\Ubuntu\usr\bin\git

Why not using wsl git?
C:\>wsl git version
git version 2.7.4

Why not using wsl git?

@dscho I was just using the git executable as an example. I appreciate the willingness to help, but I want to avoid taking this thread off-topic; see https://github.com/Microsoft/vscode/issues/9502 on why that solution doesn't work

Oh I think the wsl based vscode is really needed. If the wsl python interpreter and remote python interpreter(I don't know if this will be surpported) is surpported in vscode, I will change my IDE from Pycharm to VsCode.

A simple suggestion: the integration should be simple as reference WSL commands and paths using a WSL schema: wsl://<path>.
Example:
wsl://usr/bin/python

That seems very useful. One caveat is that people may have multiple WSL environments installed, so there should be a way to set which one should be used.

Maybe use wsl+<environment>://<path>.
Example:
wsl+ubuntu://usr/bin/python

I think it would be better a thing like wsl://ubuntu/ or wsl-distro://ubuntu/ and wsl:// referring to default distro

We just announced remote development with VS Code, check out the blog post for details https://code.visualstudio.com/blogs/2019/05/02/remote-development


DTWRKS-713 Upgrade AWS Provider to 4.53 and add provider tagging

@nathanbigaignon @tobywalls For awareness.  Update to the provider and provider tagging to conform to standards


GRAPH_SHORTEST_PATH does not return all shortest paths

The documentation for this function states: "The GRAPH_SHORTEST_PATH function returns all shortest paths of a graph." I have a very simple graph with four vertices where there are two paths of distance 2 from the first to the fourth vertex and I only ever get one path returned. I have tried this with and without a weight property where the weights were equal and I always only get one path returned.
This is the query used:
FOR e in GRAPH_SHORTEST_PATH("ratingGraph",
"rahasya_users/TestAverageTrustedConnectionRatings1",
"rahasya_users/TestAverageTrustedConnectionRatings4",
{
direction : "outbound",
edgeCollectionRestriction: "rahasya_ratings",
startVertexCollectionRestriction: "rahasya_users",
endVertexCollectionRestriction: "rahasya_users",
weight: "rating"
})
RETURN e
The vertices:
[{"_id":"rahasya_users/TestAverageTrustedConnectionRatings1","_key":"TestAverageTrustedConnectionRatings1","_rev":"78627903","lat":0,"lon":0,"olat":0,"olon":0,"quality":0,"updated":0,"radius":0,"systemrating":0,"minvis":0,"nick":"TestAverageTrustedConnectionRatings1"},{"_id":"rahasya_users/TestAverageTrustedConnectionRatings2","_key":"TestAverageTrustedConnectionRatings2","_rev":"78890047","lat":0,"lon":0,"olat":0,"olon":0,"quality":0,"updated":0,"radius":0,"systemrating":0,"minvis":0,"nick":"TestAverageTrustedConnectionRatings2"},{"_id":"rahasya_users/TestAverageTrustedConnectionRatings3","_key":"TestAverageTrustedConnectionRatings3","_rev":"79152191","lat":0,"lon":0,"olat":0,"olon":0,"quality":0,"updated":0,"radius":0,"systemrating":0,"minvis":0,"nick":"TestAverageTrustedConnectionRatings3"},{"_id":"rahasya_users/TestAverageTrustedConnectionRatings4","_key":"TestAverageTrustedConnectionRatings4","_rev":"79414335","lat":0,"lon":0,"olat":0,"olon":0,"quality":0,"updated":0,"radius":0,"systemrating":0,"minvis":0,"nick":"TestAverageTrustedConnectionRatings4"}]
The edges:
[{"_id":"rahasya_ratings/80135231","_key":"80135231","_rev":"80135231","_from":"rahasya_users/TestAverageTrustedConnectionRatings1","_to":"rahasya_users/TestAverageTrustedConnectionRatings2","rating":0.91},{"_id":"rahasya_ratings/80528447","_key":"80528447","_rev":"80528447","_from":"rahasya_users/TestAverageTrustedConnectionRatings1","_to":"rahasya_users/TestAverageTrustedConnectionRatings3","rating":0.91},{"_id":"rahasya_ratings/80921663","_key":"80921663","_rev":"89572415","_from":"rahasya_users/TestAverageTrustedConnectionRatings2","_to":"rahasya_users/TestAverageTrustedConnectionRatings4","rating":0.4},{"_id":"rahasya_ratings/81314879","_key":"81314879","_rev":"81314879","_from":"rahasya_users/TestAverageTrustedConnectionRatings3","_to":"rahasya_users/TestAverageTrustedConnectionRatings4","rating":0.4}]

The behaviour of this has changed with 2.6 for performance reasons: https://docs.arangodb.com/Upgrading/UpgradingChanges26.html
You're right, the Documentation doesn't reflect this properly.

Is there an alternative you can suggest where I can get all shortest paths, not just the first that is found?

I would also like to comment that the result is structured incorrectly for a single path result as it uses a two dimensional array for the edges. Only a single dimensional array would be needed for a single path result.

Yes, thats intentional, since if you change the grammer of an interface, all the clients need to be adjusted and evenually handle two structural ways.
The way its now an old client will work with the new output without changes.

@dylanclewis The result format with Array of Array is due to the fact, that GRAPH_SHORTEST_PATH can get a set of vertices as start and as endpoints (either as Array or as example object).
So we can f.e. execute:
GRAPH_SHORTEST_PATH("graph", {root: true}, {leaf: true})

Which will compute all shortest path between all root-nodes and all leaf-nodes. This will result in a two dimensional array, one for every root --> leaf combination.
If there is exactly one root and one leaf in the graph (by accident) it would be unpredictable for the client if this would now return a single dimensional array, which would indeed be enough.
Right now there is not yet an easy alternative for multiple shortest paths, but i like the idea and will add an issue to allow a flag in SHORTEST_PATH computation to calculate more than one path.

@mchacki Thanks for the reply, I do need reminding every now and then that the example parameter has many forms and can return multiple results.


Hardcoded bucket name

Some panels in the grafana dashboard doesn't have from(bucket: "${bucket}") but it's hardcoded 'tower' bucket.
Since even changing tower with the variable or the right bucket nothing appears, there may be a problem with names also from the script in the container since values are not populated (with a bucket with different name)?

I have not designed the influxdb v2 grafana dashboard, it was designed by @20chan ( Please see #9 ). I would like to refer this issue to @20chan if he can help with this.


NIFI-4271 - Revert double-click behavior back...

...to delete a bend point
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?

Reviewing...

Thanks @yuri1969 this has been merged to master!


testautomation test closes prematurely

The testautomation stops in subsystems_referenceCount, but has still 3 tests to do.
https://github.com/libsdl-org/sdl2-compat/actions/runs/10650456036/job/29521852563#step:14:6499
13: INFO:  09/01/24 00:18:25: ===== Test Suite 23: 'Subsystems' started
13: INFO:  09/01/24 00:18:25: ----- Test Case 23.1: 'subsystems_referenceCount' started
13: INFO:  09/01/24 00:18:25: Test Description: 'Makes sure that subsystem stays until number of quits matches inits.'
13: INFO:  09/01/24 00:18:25: Test Iteration 1: execKey<PHONE_NUMBER>330723016

It turns out logging after SDL_Quit stops working.
After SDL_Quit, the verbosity is reset to the default SDL_LOG_PRIORITY_ERROR.
The following patch "fixes" the issue.
--- a/test/testautomation_subsystems.c
+++ b/test/testautomation_subsystems.c
@@ -27,6 +27,7 @@ static void subsystemsTearDown(void *arg)
 {
     /* Reset each one of the SDL subsystems */
     SDL_Quit();
+    SDL_LogSetPriority(SDL_LOG_CATEGORY_TEST, SDL_LOG_PRIORITY_INFO);

     SDLTest_AssertPass("Cleanup of subsystems test completed");
 }

Looks great!

Looks great!

Is it? SDL2 does not have this behavior.
This would diverge the SDL2 and SDL2-compat tests.

sdl2-compat resets the logging level to default after SDL_Quit(), this is fine.

Wait, this is sdl2-compat. It should be doing that, can you look and see why that's not working?


cpp-utilities: 5.13.0 -> 5.14.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/cpp-utilities/versions.
meta.description for cpp-utilities is: "Common C++ classes and routines used by @Martchus' applications featuring argument parser, IO and conversion utilities"
meta.homepage for cpp-utilities is: "https://github.com/Martchus/cpp-utilities"
meta.changelog for cpp-utilities is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 5.14.0 with grep in /nix/store/9vipsp23kzk723xsnfcspsxxd9jpdzx5-cpp-utilities-5.14.0

found 5.14.0 in filename of file in /nix/store/9vipsp23kzk723xsnfcspsxxd9jpdzx5-cpp-utilities-5.14.0

Rebuild report (if merged into master) (click to expand)

10 total rebuild path(s)

10 package rebuild(s)

10 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
cpp-utilities
libsForQt5.qtutilities
libsForQt512.qtutilities
libsForQt514.qtutilities
libsForQt515.qtutilities
plasma5Packages.qtutilities
syncthingtray
syncthingtray-minimal
tageditor
tagparser

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9vipsp23kzk723xsnfcspsxxd9jpdzx5-cpp-utilities-5.14.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cpp-utilities https://github.com/r-ryantm/nixpkgs/archive/b9832511698066dbe0a7e02fddf5e8afedfc5603.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9vipsp23kzk723xsnfcspsxxd9jpdzx5-cpp-utilities-5.14.0
ls -la /nix/store/9vipsp23kzk723xsnfcspsxxd9jpdzx5-cpp-utilities-5.14.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

8 packages built:

cpp-utilities
libsForQt5.qtutilities
libsForQt512.qtutilities
libsForQt514.qtutilities
syncthingtray
syncthingtray-minimal
tageditor
tagparser

Maintainer pings
cc @doronbehar for testing.

@ofborg eval


External access not working

Hey, I'm having issues with getting external access for the WebRTC protocol. I've tried both of the ways of getting external access but neither has been successful. I've opened ports to my OPNSense router, as well as the address where my HASS instance lives. I can't get WebRTC to load on either when outside of my LAN.
I've also tried to run a TURN server (coturn) on a AWS EC2 VPS. I've opened all the necessary ports on it and I can test it here successfully, but it doesn't seem to work for the integration. My turnserver config is this:
realm={external-ip}
server-name=mydomain.com
fingerprint
listening-ip={internal-ip}
external-ip={external-ip}/{internal-ip}
listening-port=3478
min-port=49152
max-port=65535
log-file=/var/log/turnserver.log
user=test:test123
lt-cred-mech
verbose

I'm also not sure about if this is the right behavior, but I can test the turnserver using the turnutils_client command successfully, but only when it's TCP. When I use UDP I get channel bind: error 403 (Forbidden IP)
The HASS logs only show this when my ice_servers are specified (I've tried all combinations of google stun server, my own ice server as well as stun server):
2022-05-27 16:45:03 DEBUG (webrtc) [custom_components.webrtc.utils] 2022/05/27 16:45:03 websocket.JSON.Receive EOF
2022-05-27 16:45:03 DEBUG (webrtc) [custom_components.webrtc.utils] [GIN] 2022/05/27 - 16:45:03 | 200 |  3.841934293s |       <IP_ADDRESS> | GET      "/ws?url=rtsp://username:password@camera-ip:554/h264Preview_01_main"

If I leave out the ice_server config out of the card yaml, I see this in the logs repeated over and over, but no external access:
2022-05-27 16:41:43 DEBUG (webrtc) [custom_components.webrtc.utils] 2022/05/27 16:41:43 Set ICEServers [stun:stun.l.google.com:19302]
2022-05-27 16:41:43 DEBUG (webrtc) [custom_components.webrtc.utils] 2022/05/27 16:41:43 Set UDP ports to 49152 .. 50152

I am running HASS in a docker container in an LXC on a Proxmox host, no firewall rules changed or applied.
If anyone has any advice on what I'm doing wrong, please let me know.

You say you are using docker, do you forward the ports out of docker or try setting network=host on your docker? I thought you had to be listening on high udp ports like around 50000 or 60000 for webrtc access. For my setup on hyperv without docker im pretty sure i just forwarded it on my router and it worked right away, if your ip is public you shouldnt need all this extra turn and ice setup, at least, i didnt

You say you are using docker, do you forward the ports out of docker or try setting network=host on your docker? I thought you had to be listening on high udp ports like around 50000 or 60000 for webrtc access. For my setup on hyperv without docker im pretty sure i just forwarded it on my router and it worked right away, if your ip is public you shouldnt need all this extra turn and ice setup, at least, i didnt

I'm using docker for HASS, coturn is ran as a binary on my EC2 instance.

Check my new project. It has solution for external access
https://github.com/AlexxIT/go2rtc

Should be fixed in v3


ISPN-6071 NullPointerException when executing RemoveExpiredCommand

https://issues.jboss.org/browse/ISPN-6071

Pushed to 8.1.x, thanks


stuck in walls when you descend down a level

thought i fixed this one a while back but nope :(

done, not the most elegant solution but it works


Sub xml support

Add support for extracting a subset of an XML structure given an XPath

Tested and understood. Not 100% pleased with the complexity involved to solve a simple 'get subxml' problem.
Does not build in windows platform


[Doc] Missing parameter description for profileName in resendSignUpConfiramtionCode section

"resendSignUpConfiramtionCode" method of User Information Recovery Service in [1] describes parameters used in request body and 'profileName' is missing here.
[1] https://docs.wso2.com/display/IS540/User+Information+Recovery+Service#UserInformationRecoveryService-resendSignUpConfiramtionCode

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


Push does not seems to be relaible

hi,
im having some weird issue.
I shared, moving also the ownership, a big folder (about 6-7GB) on account 2, then added other files to account 2.
Account 1 still show the space as used, and account 2 show me only 3GB used.
What scare me the most is that after the push was successful, i tun it again just to be sure (already noticed that dimension issue) and found out some file was missing. Then again and was up-to-date. Then again and some file was missing.
Is this happening to someone else?

Hi Mauro,
I had a similar issue https://github.com/odeke-em/drive/issues/613 that I sent a PR for. Basically if you had a multicore machine there was a race condition with processing the list of files when more than 100 files were being pushed/pulled which caused some files to be skipped. If that seems similar, you might be able to check again once the PR is merged.

May be the problem, both machine are multi core.
I am just preparing to do a new big push, I may hold it, thanks!

If you can't wait you can also try GOMAXPROCS=1 drive push which will work around the multicore issue if that is the problem.

@MauroMombelli I've merged @sselph's fix(thank you) in https://github.com/odeke-em/drive/pull/639. Please get the latest from master and retry.

Ping!

sorry, but seems i already got everything uploaded at the first time and part of the issue was drive showing false value for space used


GeneratePackageOnBuild missing from docs

There doesn't seem to be any reference here (which there should be IMO) to the GeneratePackageOnBuild property. It would be great to have it added to the docs particularly with an explanation of how it works with IsPackable

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

ID: cb4428fc-215c-78e1-5ff0-fe73f7a08260
Version Independent ID: 6741b1de-38a4-fbb1-d79d-acc47d549a2d
Content: Additions to the csproj format for .NET Core
Content Source: docs/core/tools/csproj.md
Product: dotnet-core
GitHub Login: @blackdwarf
Microsoft Alias: mairaw

Some info is here: https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package-msbuild#automatically-generate-package-on-build

Some info is here: https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package-msbuild#automatically-generate-package-on-build

Since the csproj article will be removed tomorrow, and its replacement doesn't cover NuGet publish properties directly, I'm going to close this issue. I will reopen https://github.com/NuGet/docs.microsoft.com-nuget/issues/1097 instead.

Since the csproj article will be removed tomorrow, and its replacement doesn't cover NuGet publish properties directly, I'm going to close this issue. I will reopen https://github.com/NuGet/docs.microsoft.com-nuget/issues/1097 instead.


Support for multiple Godot versions and pre-generated bindings in 0.9

With Godot 3.2 becoming stable, and breaking changes happening in the engine, we would like to be able to support multiple versions of Godot in the future. To accomplish this, each stable Godot release branch will get their own API crate, in the form of gdnative-bindings-{major}-{minor}, starting from Godot 3.2.
Additionally, the API crates will have a default pregenerated feature flag, which when enabled will make the crate use pre-generated code in order to save compilation time. Users may specify default-features = false to opt out of this and run generation on their own machines.
Godot 3.2 will be the first version we'll commit to supporting, meaning that it will be considered a breaking change to drop it, and a maintenance branch will be created if that happens. Support for the Godot 3.1.x branch may be dropped in future minor versions without further maintenance. The existing gdnative-bindings crate will have the Godot 3.2 API, and will be deprecated after it's last release as part of 0.8. It will stay as-is after the release.
Details
Versioning
The API crates will be versioned as follows:

Each API crate will share the compatibility of gdnative-core, i.e. same minor version in 0.x, and same major version after 1.0.
Godot patch version updates are not considered breaking changes, even if there should be a breaking change in Godot. This is to maintain point 1 when upstream version numbers differ in semantics from semver.

bindings_generator and gdnative-sys will be considered internal dependencies, and will always stay in 0.x. Their versions may go out of sync with gdnative-core, gdnative-derive, gdnative, and the API crates.
Implementation
Each API crate will have a gdnative-bindings-pregenerated-{major}-{minor}counterpart published on crates.io, which contains the pre-generated version, and is used as an optional dependency. When pregenerated is enabled, the API crate will simply re-export everything from the -pregenerated- crate. Otherwise, it will invoke bindings_generator to generate code as it works now.
API crates will be generated on packaging, and will not be checked into the source tree.
Steps

[ ] Implement the binary api-crate-generator which will handle generating and packaging API crates.
[ ] Create an internal in-tree API crate used for development, which will not be published. Migrate examples and tests to the internal crate .
[ ] Add documentation about the API crates.
[ ] (At 0.8 release) deprecate gdnative-bindings after a final update.

Delayed this to 0.9, as larger changes are planned, and we decided to release 0.8 as a small, relatively stable update before the big changes land.

Further delayed to 0.10, but it can be made non-breaking if we introduce engine version feature flags in 0.9.

With building for custom versions being much more ergonomic than back when this issue was created, and new ideas proposed in #814 to handle backward compatibility, there might no longer be a need to distribute multiple versions pre-generated bindings.
Closing for now.


Implement this in R

This could be useful for the fractalplotr package. For example for generating sierpinski triangles. But also more organic shapes or maybe semi-random art.

It's implemented but quite slow.
Ideas for improvements:

Don't save the lines as lists. Keep one vector for x and one for y and insert NA to force line breaks when loading state.
Don't save the states separately. Just keep a recort of every x and y and direction and when saving save the index inside those vectors. Then load the value from that index when loading state.


BuildDeployWindow: warning CS0162: Unreachable code detected

Assets/HoloToolkit/Build/Editor/BuildDeployWindow.cs(88,13): warning CS0162: Unreachable code detected

Just make LocalIPsOnly non-const?

Great, now I made a mess with git's online editor and my attempted silent fix w/ rebase.


Workaround for libc++ include path for HIP-Clang

HIP-Clang cuda_wrapper headers require clang include path before standard C++ include path.
However libc++ include path requires to be before clang include path.
To workaround this, we pass -isystem /opt/rocm/llvm/lib/clang/11.0.0 instead of
-isystem /opt/rocm/llvm/lib/clang/11.0.0/include to clang, and use
#include <include/cuda_wrappers/algorithm> instead.

I have tested it works fine with both libc++ and libstdc++

ping @emankov could you please review again? Thanks.


how to adapt it for squad2.0 dataset?

I also encountered the same problem.Please reply me if you solved it！！


HTML

HTML
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage
so that I can easily find and read information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, and JavaScript with associated notes listed

HTML initial code added to prework so issue completed


[SR SQL Planner Summer Camp] add backup analyzer

What type of PR is this：

[ ] bug
[x] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #7951
Problem Summary(Required) ：

add backup analyzer

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage Check]
:heart_eyes: pass : 77 / 92 (83.70%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[388]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
1
2
50.00%
[114]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
43
55
78.18%
[28, 44, 53, 54, 66, 71, 77, 88, 94, 104, 114, 115]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
30
31
96.77%
[3455]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 135 / 158 (85.44%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[388]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
18
23
78.26%
[458, 459, 884, 885, 908]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
78
94
82.98%
[31, 52, 62, 74, 79, 85, 95, 99, 100, 107, 117, 123, 128, 129, 133, 154]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
30
31
96.77%
[3455]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage Check]
:heart_eyes: pass : 132 / 155 (85.16%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[409]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
18
23
78.26%
[463, 464, 930, 931, 954]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
78
94
82.98%
[31, 52, 62, 74, 79, 85, 95, 99, 100, 107, 117, 123, 128, 129, 133, 154]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
27
28
96.43%
[3613]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

run starrocks_fe_unittest

您好，您的邮件已收到，我会尽快给你回复。

[FE PR Coverage Check]
:heart_eyes: pass : 123 / 142 (86.62%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[422]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
4
5
80.00%
[946]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
83
99
83.84%
[33, 54, 64, 76, 81, 87, 97, 101, 102, 109, 119, 125, 130, 131, 135, 161]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
27
28
96.43%
[3650]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 123 / 142 (86.62%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[422]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
4
5
80.00%
[946]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
83
99
83.84%
[33, 53, 63, 75, 80, 86, 96, 100, 101, 108, 118, 124, 129, 130, 134, 160]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
27
28
96.43%
[3650]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 123 / 142 (86.62%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[422]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
4
5
80.00%
[946]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
83
99
83.84%
[33, 53, 63, 75, 80, 86, 96, 100, 101, 108, 118, 124, 129, 130, 134, 160]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
27
28
96.43%
[3650]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 123 / 142 (86.62%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[427]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
4
5
80.00%
[946]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
83
99
83.84%
[33, 53, 63, 75, 80, 86, 96, 100, 101, 108, 118, 124, 129, 130, 134, 160]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
27
28
96.43%
[3797]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 123 / 142 (86.62%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[453]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
4
5
80.00%
[986]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
83
99
83.84%
[33, 53, 63, 75, 80, 86, 96, 100, 101, 108, 118, 124, 129, 130, 134, 160]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
27
28
96.43%
[3994]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 123 / 142 (86.62%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[468]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
4
5
80.00%
[986]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
83
99
83.84%
[33, 53, 63, 75, 80, 86, 96, 100, 101, 108, 118, 124, 129, 130, 134, 160]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
27
28
96.43%
[4053]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

run  starrocks_admit_test

run starrocks_admit_test

@Mergifyio rebase

run all

run starrocks_admit_test
run starrocks_fe_unittest

[FE PR Coverage Check]
:heart_eyes: pass : 123 / 142 (86.62%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[468]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
4
5
80.00%
[986]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
83
99
83.84%
[33, 53, 63, 75, 80, 86, 96, 100, 101, 108, 118, 124, 129, 130, 134, 160]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
27
28
96.43%
[4053]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 125 / 142 (88.03%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[468]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
4
5
80.00%
[986]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
85
99
85.86%
[33, 53, 63, 80, 86, 100, 101, 108, 118, 124, 129, 130, 134, 160]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
27
28
96.43%
[4053]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

run starrocks_admit_test

run starrocks_admit_test

[FE PR Coverage Check]
:heart_eyes: pass : 125 / 142 (88.03%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[468]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
4
5
80.00%
[986]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
85
99
85.86%
[33, 53, 63, 80, 86, 100, 101, 108, 118, 124, 129, 130, 134, 160]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
27
28
96.43%
[4053]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 125 / 142 (88.03%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[468]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
4
5
80.00%
[986]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
85
99
85.86%
[33, 53, 63, 80, 86, 100, 101, 108, 118, 124, 129, 130, 134, 160]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
27
28
96.43%
[4053]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 125 / 142 (88.03%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[468]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
4
5
80.00%
[986]

:large_blue_circle:
com/starrocks/sql/analyzer/BackupStmtAnalyzer.java
85
99
85.86%
[33, 53, 63, 80, 86, 100, 101, 108, 118, 124, 129, 130, 134, 160]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
27
28
96.43%
[4053]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/BackupStmt.java
6
6
100.00%
[]

:large_blue_circle:
com/starrocks/common/ErrorCode.java
1
1
100.00%
[]


[ BUG ] Conversion from v1alpha3 to v1 failed for metadata field

We have not been able to reproduce the problem. We are closing this ticket for the time being.


Content after Code block is not rendered

Hello,
I found an issue with content not rendered after a code block.
The first element that happens to be after a code block will not be displayed with MudBlazor.Markdown. When inspecting the rendered HTML with Devtools the element is really not rendered to the website.
I use Blazor WASM 6.0.1, MudBlazor 6.0.5 and MudBlazor.Markdown 0.0.6.
I also first tried to repro this issue with Markdig 0.26.0 standalone to make sure it isn't a Markdig issue, but Markdig alone renders the samples correctly, so it seems to come from MudBlazor.Markdown itself.
Repro:
Given the following Markdown content:
# Heading 1
Some text.

```csharp
public int GetTheAnswer()
{
   return 42;
}
```

## Another headline <-- this element is NOT rendered with MudBlazor.Markdown
## Another headline <-- this element is shown again

It really doesn't matter what follows the code block. The whole next element will be ignored. In the following example the whole list with all three items is not rendered to the page and ignored:
```text
some
code
```

* List item 1
* List item 2
* List item 3

## Another headline <-- this element is shown again

@gingters thank you for reporting the issue
@MihailsKuzmins, please investigate

damn, stupid iteration mistake with _i and i 😄
renamed the variables in order not to make the same mistakes (and unit tests of course)
@my-nihongo please review the pr

@gingters, a new NeGet package v0.0.7 has been published. It should be available within a few minutes.
Please reopen the issue if the problem still persists


Jasmine's Second Meetup Reflection

Nice!  Talking to people is definitely a plus.  The people who were in groups porbably have surprisingly tenuous connections- they've seen each other in a meetup a few times, for instance.  As faces start to become familiar it'll be easier to break the ice.


Fix route prefix for the API v2

Closes #1627
While I was looking at the code, it occurred to me that we use os.Exit improperly as it doesn't run deferred functions. I refactored that part in this PR but it can go in another PR if someone prefers.
Finally, there's still a problem with the UI: the Status tab doesn't render properly but I'm not familiar enough with the front-end code to know how to fix it. @stuartnelson3 and @mxinden, you probably know better.

Finally, there's still a problem with the UI: the Status tab doesn't render properly but I'm not familiar enough with the front-end code to know how to fix it. @stuartnelson3 and @mxinden, you probably know better.

@mxinden did you have a chance to look at the status issue?

Finally, there's still a problem with the UI: the Status tab doesn't render properly but I'm not familiar enough with the front-end code to know how to fix it. @stuartnelson3 and @mxinden, you probably know better.

@mxinden did you have a chance to look at the status issue?

Not yet. Given that this bug is not introduced through this pull request I would like to delay the fix to a follow up pull request.


Document commit signing

We need to document commit signing, that we support it for GPG and SSH. That we don't support it for certs. And the configuration that is required.
We should also probably talk about the credential management that is used here for securely storing and accessing the passwords for the keys on the various platforms.

This has been integrated into the mainline of the book repostiory. Therefore, I am closing this issue.


"FAILED: Build did NOT complete successfully (1 packages loaded)"

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20.04.1
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NA
TensorFlow installed from (source or binary): Source
TensorFlow version: I am not sure. I cloned it from the Github repository so it should be the latest version
Python version: 3.7
Installed using virtualenv? pip? conda?: Trying to install with Pip, but I am getting an error when I try to build a pip package via Bazel.
Bazel version (if compiling from source): 3.1.0
GCC/Compiler version (if compiling from source): 9.3.0
CUDA/cuDNN version: NA
GPU model and memory: Radeon RX 5700XT, G.Skill Trident-Z 2x16GB

Describe the problem
I am trying to build Tensorflow from the source since my training sessions are performing really slow and barely utilizing my hardware. I read that I can get better performance by building it from the source for my machine. However, I am getting an error when I tried to build a pip package via Bazel as according to the steps from the link:
https://www.tensorflow.org/install/source
This is the output I am getting when I try to build the package with Bazel:
root@weapon-of-mass-instruction:/home/chris/tensorflow# bazel build [--config=option] //tensorflow/tools/pip_package:build_pip_package
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=140
INFO: Reading rc options for 'build' from /home/chris/tensorflow/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /home/chris/tensorflow/.bazelrc:
  'build' options: --apple_platform_type=macos --define framework_shared_object=true --define open_source_build=true --java_toolchain=//third_party/toolchains/java:tf_java_toolchain --host_java_toolchain=//third_party/toolchains/java:tf_java_toolchain --define=tensorflow_enable_mlir_generated_gpu_kernels=0 --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --noincompatible_prohibit_aapt1 --enable_platform_specific_config --config=short_logs --config=v2
INFO: Reading rc options for 'build' from /home/chris/tensorflow/.tf_configure.bazelrc:
  'build' options: --action_env PYTHON_BIN_PATH=/usr/bin/python3 --action_env PYTHON_LIB_PATH=/usr/lib/python3/dist-packages --python_path=/usr/bin/python3 --config=xla --action_env TF_CONFIGURE_IOS=0
INFO: Found applicable config definition build:short_logs in file /home/chris/tensorflow/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /home/chris/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:xla in file /home/chris/tensorflow/.bazelrc: --define=with_xla_support=true
INFO: Found applicable config definition build:linux in file /home/chris/tensorflow/.bazelrc: --copt=-w --host_copt=-w --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxopt=-std=c++14 --host_cxxopt=-std=c++14 --config=dynamic_kernels
INFO: Found applicable config definition build:dynamic_kernels in file /home/chris/tensorflow/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
DEBUG: Rule 'io_bazel_rules_go' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1557349968 -0400"
DEBUG: Repository io_bazel_rules_go instantiated at:
  no stack (--record_rule_instantiation_callstack not enabled)
Repository rule git_repository defined at:
  /root/.cache/bazel/_bazel_root/a819f6789d392dd47d3107e5934b6ad1/external/bazel_tools/tools/build_defs/repo/git.bzl:195:18: in <toplevel>
ERROR: Skipping '[--config=option]': no such target '//:[--config=option]': target '[--config=option]' not declared in package '' defined by /home/chris/tensorflow/BUILD
ERROR: no such target '//:[--config=option]': target '[--config=option]' not declared in package '' defined by /home/chris/tensorflow/BUILD
INFO: Elapsed time: 8.402s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (1 packages loaded)
    currently loading: tensorflow/tools/pip_package
    Fetching @local_config_cuda; Restarting.

Provide the exact sequence of commands / steps that you executed before running into the problem
1. git clone https://github.com/tensorflow/tensorflow.git
2. cd tensorflow
3. ./configure
4. Left everything default and chose no for ROCM/CUDA/Clang/etc.
5. bazel build [--config=option] //tensorflow/tools/pip_package:build_pip_package

Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
I do not have an ROCM compatible GPU (at least as far as I am aware. If I am wrong, I would definitely appreciate some advice on making Tensorflow work with my card) so I am trying to optimize Tensorflow to run on my CPU, which is a Ryzen R9 3900X. When I run Tensorflow, it appears to barely utilize my CPU as according to my process monitor, so I am looking to build Tensorflow for my machine in hopes that it will make a difference in performance.
All advice and help with issue will be greatly appreciated!

See https://github.com/RadeonOpenCompute/ROCm#supported-gpus
I suggest you also to profile your code with https://www.tensorflow.org/guide/profiler
Tensorflow ROCM is available at https://pypi.org/project/tensorflow-rocm/

You're not supposed to input [--config=option] as is. Brackets usually means "you can supply something in here in this format."
 Removing the brackets worked. Also, I will check out RoCM since I see that it supports Ryzen CPUs. I thought it only supported GPUs.
Thanks a ton for your help!

@cray12399,
Thank you for the update. Marking this issue as closed, as it is resolved. Please feel free to re-open if necessary.


FileSystemProvider gets reinitialized in a completely new JavaScript context

VSCode Version: 1.47.2 user setup
OS Version: Windows 10

Steps to Reproduce:

Clone my extension https://github.com/TomasHubelbauer/vscode-email-viewer and the repository in VS Code
Go to debug by pressing F5
Watch the extension host window pointed to the demo directory appear and select real.eml
Watch a progress indicator appear and go while the email file loads - this populates the cache from cache.ts in extension.js
Watch a new workspace directory appear and list the correct entries (3 PNGs and 1 HTML file) as the cache now has an entry for the parsed contents of the real.eml file selected previously
Wait a bit
Watch a spinner appear next to the already loaded and populated workspace directory node for the real.eml file virtual directory as stat on the FS provider is called again even though it was already called while populating the node initially
Watch an error message pop up because the cache.ts module was reloaded for some reason and this stat call sees {} not the populated cache object which was initialized before when the progress indicator appeared after clicking real.eml
See the debug console in VS Code proper (not the extension host window) and notice the Cache init line appear twice when it should have appeared once because it is in the cache.ts module global context which to me is indicative of a JavaScript context change/reload? (But the window did not reload...)
Be confused

Does this issue occur when all extensions are disabled?: N/A

I am confused. Is this a debugger issue or is this because the extension host restarted after changing the workspace?

I have no idea what causes this. Were you able to reproduce?

I am not trying ;-) I know that we don't do anything special for file system providers, esp nothing like creating new JS contexts. So, this can only an issue with debugging and/or when reloading the extension host. Did you try this when bundling and locally installing your extension?

I don't think this is related to the extension host reloading, because this happens within the span of a single debugging session. Perhaps it is something with the debugger, but I really couldn't tell you, I have no knowledge of how the VS Code debugger works. I will try to bundle and install locally and report back if that helped. I don't know how to debug this further myself, so if you or anyone else capable of diagnosing this are not going to try and reproduce this, I think that will leave this issue at a dead end.

For completeness' sake, when packaging the extension as VSIX and installing it through it, the problem persists: it seems as though the runtime is reloaded from under the extension as it is running. It is as if the module import caused the module to evaluate multiple times (clearing the cache in effect), which AFAIK is not the module loading behavior in either CJS nor ESM.
I still don't know exactly what it is that causes this, but it seems safe to rule out it being a debugger / extension how window issue and instead firmly a runtime issue or an issue with my understanding/assumptions about how the runtime behaves.

Do you see the same with the file system provider sample: https://marketplace.visualstudio.com/items?itemName=jrieken.vscode-memfs?


[🚨] Potential Secrets Disclosed

Hi @SAP,
It seems that you are disclosing some hardcoded secrets here:
https://github.com/SAP/credential-digger-tests/blob/97415a27c4981ad8456fb306a5de114c5a6ae4a4/file_b.txt#L5
Best,
Github Monitor.

Hi @jessica-25-github I guess your tests are working well :)
Do you want me to keep this issue open or do you want me to close it?


list + float/symbol/bang/pointer methods...

A float message is different from a list message with a single float element, hence the list and float methods will pick them up separately, but we, as developers, should know that and work it out in the case we have a message like "list 1"...

also check addanything?????


Assignment to symbols is allowed

Why does this compile outside of a class body?
:foo = bar

Oh, I guess this makes a nonzero amount of sense for well-known symbols, like :asyncIterator ??= Symbol 'Symbol.asyncIterator' in a polyfill. But for the ones like this that compile to Symbol.for it's always an error so it shouldn't be allowed.

I could be wrong, but I think Civet emits invalid JavaScript in a variety of contexts where the input is invalid. So I'm not sure we need to detect this at the transpilation level; we can leave it for detection downstream (by TypeScript, eslint, Node, etc.). Unless you think we should try to catch all JS errors ourselves?

Huh, I guess you're right (example). I hadn't noticed that before.


new Constants.py to  libbitcoin_server , libbitcoin_server_testnet and PROTOCOL_VERSION

Add constants for libbitcoin_server , libbitcoin_server_testnet and PROTOCOL_VERSION

pullRequest # 53  is repeated , the valid pull is 48


HCP ASL pipeline

https://github.com/physimals/hcp-asl

duplicate of https://github.com/NeuroDesk/neurocontainers/issues/765


conformToMask (numberMask) always returns integer value

Hey all,
not sure if I understand the conformToMask function correctly but I assume it simply formats a given number into the masked string, right?
I'm using Angular 2+: The following snippet always outputs an integer value although 'allowDecimal = true' as option. Bug or do I something wrong?
let maskOptions = {
        prefix: '€',
        suffix: '',
        includeThousandsSeparator: true,
        thousandsSeparatorSymbol: '#',
        allowDecimal: true,
        decimalSymbol: ',',
        decimalLimit: 2,
        integerLimit: null,
        requireDecimal: false,
        allowNegative: true,
        allowLeadingZeroes: false
    }

let mask = createNumberMask(maskOptions);

let cValue = "124.2";
let conformedPhoneNumber = conformToMask(cValue, mask(cValue), {});
console.log(conformedPhoneNumber.conformedValue);

Output is always an integer formatted string '€1#242' but has to be a decimal one '€124,2'
Thanks for your help. :)

Seems to be an issue with the decimal symbol.. I had a quick look in the src but couldn't figure out exactly what is going wrong.. I'll hopefully get time to take a deeper look later

allowDecimal: true


Repeated I/O errors when pushing lots of files

Whenever I try to put a large amount of files (say DCIM folder from a phone), I get I/O errors really often. It doesn't seem to matter whether or not I use pk-mount or the web UI. Using the fuse driver, this happens with both rsync and cp. With the web ui, I can watch consistent failures (usually throwing a 500) in the dev console.
I could give pk put file a try but I wasn't sure how to target a specific root and subnode for a destination

Hey, can you paste the errors here?


Toggle Static Dot Clickable

Simple change that makes the Static Dot clickable only if the line itself is intended to be clickable.

Thank you for your contribution, has been updated to 2.8.16


how to use debug with PM2?

how to use debug with PM2?
DEBUG=* pm2 start app.js
There is no debug logs.

Isn't it possible to use the ecosystem.config.js to configure different environment variables when starting a process with PM2?
See https://github.com/Unitech/pm2/wiki/Applications-Declaration
Should be possible to include DEBUG=* in the env section of your desired process

That works, and there is another question, the debug logs are all in PM2's error log, not in out.log, do you know why?

When you use debug on nodejs it writes to stderr by default (see node.js)
It is possible though to redirect the output of a logger to another stream https://github.com/visionmedia/debug/blob/master/examples/node/stdout.js

That's greet!


Added automated captcha feature

I have added an automated captcha feature which could automatically solve the captcha within a second. I have kept the option for the user to choose if they want the auto/manual captcha feature.
Please review.

@Nakul93 Even I thought of this but for now, we're going with the manual process of entering captcha. Thanks for this PR. Will look into it.

Well that’s why I submitted it to dev branch

Yeah, I know. Still it's better for now to keep manual.


Collapsed Dependencies

Might you might allow for collapsed dependencies to easily be gotten from output of the dependency parser via some option?

The current roadmap is to do semantic role labelling instead.
Is there a reason you need the collapsed dependencies in particular?

I've just them for a task and was wondering whether I'd be able to easily
switch to spaCy for it. Are they seen as a deprecated concept?
On 7 April 2015 at 14:24, Matthew Honnibal<EMAIL_ADDRESS>wrote:

The current roadmap is to do semantic role labelling instead.
Is there a reason you need the collapsed dependencies in particular?
—
Reply to this email directly or view it on GitHub
https://github.com/honnibal/spaCy/issues/47#issuecomment-90705986.

It's really something the Stanford tools provide, but hasn't been taken up so much by other researchers.
I think for many tasks it's a more useful output than basic dependencies, but for those tasks semantic dependencies are usually better still.

Fair enough :) I have a question about the output of your parser. Is this where I should ask such questions, or do have a forum or something?

I've decided to try hosting this on Reddit, instead of the usual solutions (mailing list, Google Groups, etc).
https://www.reddit.com/r/spacynlp/
You can write your question here if you prefer, or you can try out posting it on the new subreddit.

Why not Gitter right here on GitHub?


Preparations for release

Update metadata and docs for the release 0.4.2

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

7 of 9 (77.78%)  changed or added relevant lines in 6 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.2%) to 64.222%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

daiquiri/files/search.py
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

daiquiri/core/utils.py
2
56.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
4712

Relevant Lines:
7337

💛  - Coveralls


feat: request/response support in both operation and message objects

Title: "Request/Response paradigm support in both operation and message objects"
Related issue(s): #55 #94 #558
Champion: @smarek

Since nobody yet took the opportunity, i'm gonna try to champion this Feature RFC.

Explanation of Problem & Solution:
Very common type of operation is currently missing in specification per discussion in referenced (related) issues. Operation that results in direct or indirect response to the caller.
The most basic example is publishing a message, where the result of publish operation should be known as soon as possible to the caller. Eg. invoking operation on given channel will return the specific message (or oneOf messages) right away to the caller.
The complicated example is correlation of the request and response, where publish/subscribe operation with given message will result in the specific message to be delivered back to the caller via different channel.
Solution has two parts:

Allowing referencing single or multiple messages as a result to operation (indifferent to whether the operation is server or client initiated)
Allowing hinting single or multiple messages that can be expected by other party to be received as a result to using specific message in any kind of operation

Which allows for "Acknowledge" messages, "HTTP Request/Response" correlation and foremost to better describe (and for api document reader understand) the situations where one might receive specific message

Illustrative examples:
I'll limit myself to two examples, as various are already discussed in related (referenced) issues.

HTTP Message Binding - Request and Response
- HTTP standard expects the caller to consume the response headers and possibly a response payload, if given HTTP verb allows it.
- This feature would allow to specify response headers and json body that would represent the result of HTTP GET, POST, PUT or other http operation
WebSocket protocol binding / (SignalR, RPC)
- SignalR interface specifies two-way methods in rpc-like manner, where client or server can invoke operations (interface methods/functions) on each other, where each operation can take arguments and can produce any kind of response (be it scalar value or complex objects), the transport is JSON over WebSocket
- This feature allows the SignalR protocol to correctly define the messages that client/server can receive as a result of invoking operation on the other party OR invoking operation with specific message type

Also mentioned should be usage of current x-response extension https://www.asyncapi.com/blog/websocket-part2#describe-responses---specification-extensions

Identification of potential concerns, challenges, and drawbacks:

Current spec edit proposal allows for infinite chaining of the responses, which if not implemented asynchronously, would result in terrible call-stack-overflows
- I actually think it is desired and it should be concern of user/developer whether the response message chaining is used correctly or not
Allowing specifying different kind of messages on operation as well as on message might create ambiguous situations, where the consumer must account both for messages that can be produced on operation and messages that are related to "request message"
-  This is in my opinion necessary to support as wide spectrum of bindings/protocols as possible, some protocols produce different kind of messages on single channel item operation (eg. getNextOfAnyType kind of operations) and some protocols use the invoke/getResult paradigm where the response message is always directly linked to the invoked operation and "request message" used in such
My last concern is that making both of these result fields OPTIONAL is not long-lasting solution and will not drive the community to use the option to make their API documentations more strong-typed, and I'm honestly not sure whether there is anything we can do about it

@fmvilas @derberg could you please, if applicable, add RFC label to this PR?

@fmvilas from my point of view this is Stage 1: Proposal. Nothing is missing for Stage 1 I think

Yup. Thanks for noticing, @smarek.

Proposal shared with the wider community:

LinkedIn
Twitter
Slack (need to join first- {invite link](https://www.asyncapi.com/slack-invite))

Thanks for @smarek for the interesting proposal.
Reading through I had two thoughts:

As this is AsyncAPI (and there exists OpenAPI, which lives to represent synchronous HTTP calls), perhaps it's not in scope to model synchronous HTTP request/reply scenarios.  Maybe this plays into @fmvilas vision of linking together various APIs into an uber API, rather than having AsyncAPI be able to handle it.
That said, the larger vision of modeling async causality amongst n actor/endpoints is intriguing to me. @clemensv mentions this in  https://github.com/asyncapi/spec/issues/601.  @smarek  is right that knowing what to expect in response to a publish is important.  But for many enterprises it's also important  to understand the choreography of multiple endpoints.

In that way,  limiting this functionality only to request reply amongst two consumers is perhaps not generic enough.  It might be worth exploring how to handle choreography within the spec that handles "defining multi-directional conversations abstractly: Not just request/reply, but also scatter/gather patterns, saga patterns, etc.", as @clemensv puts it.

@jmenning-solace thank you for discussion as well

your first point is really described in initial comment, section "Illustrative examples", point 2. Where WebSocket is full-duplex, asynchronous, protocol, and so is SignalR over WebSocket. However this particular async api/application protocol (and definitely not only one that does that) supports typed interfaces where response to given request (both from client and server side) is expected and validated. Which is also the original reason I became interested in getting this topic solved in spec, current inability to link the endpoint reaction to the request. In low-level there is "correlation id" that links the request and response, but from the consumer/integrator point-of-view it is necessary to define the meaningful relation between the two messages, if the protocol supports/expects it. But since the operation/message level reaction (response) is not necessary part of any async api, both options are specified as OPTIONAL, so you can describe such asynchronous protocol with AsyncAPI but you're not forced to do so
i did not know the mentioned https://github.com/asyncapi/spec/issues/601 and it is indeed tricky to describe, but i'm not sure if the choreography can be described well using declarative language, such as asyncapi spec, since i'd expect the choreography to be based in some kind of turing/state-full machine and that is imho topic/challenge completely different from describing API/RPC interfaces. Regardless of what I just said, i don't think we should abandon my PR since many APIs can be sufficiently descibed with request/response causality, and the higher abstraction, enterprise point-of-view, can be added later on top of this or side-by-side

@smarek Could you please take a look at my comment. I'd like to hear from you and see how we can evolve the proposed model in order to support your requirements.  As this proposal introduces breaking changes, they should be part of AsyncAPI v3.0.0. Thank you!

To me, the request-response information should not interact with the publish nor subscribe information and thus, the request-response details should not have any interaction with the pub-sub oriented sections.  I imagine something like this:
channels:
  basic:
    exchanges:
       fetchThing:
         receive:
           # ...
         respond:
           # ...
    publish:
      # ...

That is to say:

Upon channel basic, I participate the following exchanges, including the fetchThing. During the fetchThing exchange, I will receive message x and I will respond with message y.

This introduces a new, optional field of the channel object, which should (without deep understanding of the spec) maintain backwards compatibility, allowing this to slot into v2.x.
Some semantic considerations:

I don't personally love the verb-oriented labels of receive/respond, however this remains consistent with the existing, verb-oriented publish and subscribe.
The exchanges label a bit vague and risks becoming ambiguous when considering future pattern implementations; an "exchange" does not necessarily involve exactly two messages. (For example, a tcp handshake is a 3-message exchange.) A  more specific label might be appropriate (but alternatives in my head -- such as requestResponses -- just seem too awkward).
Whereas receive/respond is consistent with publish/subscribe, they occur at a different nesting level.  This is not ideal, but may be necessary in order to appropriately group the information. Perhaps this lends itself to a future change (v3 and beyond) that places the exchange patten directly under the channel and then describes the messages following that pattern. (ex: channels.basic.pubSub.publish...).  Like point 2, this speaks to future support of other, well-established messaging patterns.

I'd like to suggest another way of documenting request-reply messages:
Instead of Documenting them on the request message (or seperately on the channel) moving the Documentation to the replies can have some benefits.
channels:
  requestData:
    publish:
      message:
        $ref: '#/components/messages/requestSpecialData'
  returnChannel:
    subscribe:
      message:
        $ref: '#/components/messages/specialDataResponse'
        trigger:
          on: message
          channel: requestData
          message:
            $ref: '#/components/messages/requestSpecialData'

The samantic of this would roughly be: If a requestSpecialData message appears in channel requestData then a specialDataResponse message can be received later on the returnChannel.
benefits:

Triggers can be extended later to allow for timers, conditions, channel subsciption events, environment events, etc. without breaking compatibility and without introducing a new concept.
Triggers naturally allow to specify multiple responses
One only needs knowledge about what can trigger a message to correctly specify all message triggers
Allows other applications to extend existing request-response patterns by triggering new messages on the same condition
Allows specifying request-response chains across different channels, even allows for responses to channels with a variable

Disadvantages:

Finding replies to responses in the spec becomes harder and needs tool support (this issue is less severe if the question that is more often asked is "what do i need to do in order to get this specific message?" as triggers would answer that directly)
Triggers can become very complex (but we could start with defining only very simple triggers)
Needs more work to specify the exact semantics of triggers

I don't have a qood answer for where to put these triggers. In the current spec they should be as close as possible to the triggered messages, because we only have the two operations publish and subscribe per channel that need to describe all messages on that channel. If a channel can have any number of operations that can be specified as send or receive operations, then triggers should be specified on these operations (then we can also have triggers for when en operation fails with an error). If multiple operations per channel are allowed, then messages that have the same purpose can be grouped into a single operation that can be used to document these messages. Operations would then be logical operations that can be performed on a channel, rather than "physical" operations the channel itself allows (publish/subscribe or send/receive) like they are now. (The proposal in #618 already allows multiple operations per channel.)
I believe that triggers are a better fit for async messaging based apis because they can capture the event based or reactive behaviour of such apis. They are also more flexible then a specific solution to document request-reply message pairs and can be extended in the future.

Would this work well if we wanted to describe a JSON RPC 2.0 Api ?
Here's an example request:
--> {"jsonrpc": "2.0", "method": "subtract", "params": [42, 23], "id": 1}
<-- {"jsonrpc": "2.0", "result": 19, "id": 1}

And here's an error example:
--> {"jsonrpc": "2.0", "method": 1, "params": "bar"}
<-- {"jsonrpc": "2.0", "error": {"code": -32600, "message": "Invalid Request"}, "id": null}

Another thing to consider is that we have some subscribers that ignore messages if there is not some kind of "reply to" address provided. e.g. if I have send a message to user.free_account.signup but I don't provide a temporary topic that it can reply to, then it will just ignore my message without creating a user.
That being said, I'd like a way to specify that the subscriber will not perform any action if no reply address is given (e.g. replyTopicRequired: true).

Would this work well if we wanted to describe a JSON RPC 2.0 Api ?
Here's an example request:
--> {"jsonrpc": "2.0", "method": "subtract", "params": [42, 23], "id": 1}
<-- {"jsonrpc": "2.0", "result": 19, "id": 1}

And here's an error example:
--> {"jsonrpc": "2.0", "method": 1, "params": "bar"}
<-- {"jsonrpc": "2.0", "error": {"code": -32600, "message": "Invalid Request"}, "id": null}

Yes, however missing "id" param in error reply is problematic, since the reply cannot be easily linked with the request (which I'd expect in async reply, and which is understandably not required when response is provided synchronously, eg. the response is expected before another request occurs)

Another thing to consider is that we have some subscribers that ignore messages if there is not some kind of "reply to" address provided. e.g. if I have send a message to user.free_account.signup but I don't provide a temporary topic that it can reply to, then it will just ignore my message without creating a user.
That being said, I'd like a way to specify that the subscriber will not perform any action if no reply address is given (e.g. replyTopicRequired: true).

I agree, but that should be in my opinion part of different RFC, since it describes topic/address related flow, not just "what kind of response can subscriber expect for given request/message"

@buehlefs thank you, i don't think i will adopt your proposal in this RFC, since triggers are complex topic on its own.
I'm afraid that documenting which message can be passed on which channel based on which condition/trigger is separate discussion. In most cases i'd say the response to request is expected on the same (or single different, downstream) channel/topic.
In terms of your example, if we have one publish/request channel and one subscribe/response channel it'd still be meaningful to identify response messages as part of requestData::publish::message along with additional identification of channel/topic where response/answer is provided. Here I'd extend on @samueleaton comment, we should probably allow documenting that "response is not mandatory" (so far my proposal allows documenting only success/error responses, but specific api design can be that no response will/might be provided at all)
That being said how about responseBehavior
channels:
  basic:
    message:
      oneOf:
        - $ref: '#/components/messages/ping'
    responseBehavior: 'mandatory' # possible values (the list can be expanded) 'mandatory', 'optional', 'success-only', 'error-only', 'no-response'
    response:
      oneOf:
        - $ref: '#/components/messages/unauthorized'
components:
  messages:
    ping:
      payload:
        $ref: '#/components/schemas/ping'
      response:
        $ref: '#/components/messages/pong'

This way the reaction (response) of the other party could be expected without going much into detail of business-logic of the application

And at last, as reaction to https://github.com/asyncapi/spec/issues/94#issuecomment-1109424017 by @derberg and other mentions of this topic, seems like the general community consensus is that this RFC contains breaking changes and should not be based against 2.x but 3.x version of AsyncAPI, where others and more complex topics are currently being addressed/discussed. I'm not able nor willing to join all the discussions.
So if my understanding is correct, please close this PR and address the request/response needs in other way (more compliant with all the other changes designed in 3.x), i will not champion this topic in 3.x version.
If it's not (meaning request/reply should be part of 2.x), I vote to not complicate the topic more here and provide basic support of request/reply as already presented in this PR, for something this trivial, the discussion is taking too long and i'm losing interest.
References:

https://github.com/asyncapi/spec/pull/594#discussion_r736527639 - my response to 2.x/3.x and taxonomy
https://github.com/asyncapi/spec/pull/594#issuecomment-975949498 - complete change of PoV introducing breaking changes, which i wanted to avoid in the first place
https://github.com/asyncapi/spec/pull/594#issuecomment-1010946193 - same, breaking changes and trigger/conditions discussion, which should be addressed elsewhere
https://github.com/asyncapi/spec/issues/618#issuecomment-974603269 and whole #618 - again, trying to solve bigger problems instead of adding single, non-breaking, feature

Please let me know, and if appropriate, you can directly close this PR

First @smarek great job so for and i am totally with your. There is a need to describe the response well! Describe it unrelated would make the schema very confusing, as well if it is large (as i face it often).
At the moment i solve this issue with naming conventions of the '#/components/messages/*' But this is not very helpful when talking about code generator.
A little about my use case
I use messaging solution like JMS, MQTT, JCSMP, ....
The you mostly have to header fields to identify the response.
Options A: Well defined response topic + "correlationId". There you have a well defined response topic and use as "correlationId" to match the response to the question.
Options B: Per process individual inbox aka. "replyTopic" + "correlationId". It works mostly the same as Option A.
Options C: Temporary reply topic for a individual response. This is mostly preferred in a request -> multi response scenario.
Where is see problems
Where i see problems with your suggestion, there there is no possibility to define:

message traits
well defined reply topics

I dont think "responseBehavior" is an good idea:

Why there is a need for the option "no-response". Simply not define "response"
The options 'success-only', 'error-only' are error prone. I dont think it is a good idea to only response either success or error. How should the requestor act if there is no response. No answer normally means in a request reply pattern that the messages was not transmitted, the opponent is down or unable to process the message.
May opinion is: always answer and do it always with the same schema. Everything else will make you trouble with fixed typed programming languages (like java).

Here my suggestion:
An attribute: "channels[].subscribe.responseChannel" pointing to a message channel, can be the same but dont have to.
An attribute  "channels[].response" with same structure as "subscribe"/"publish" describing the response message
Example for "Options A"
channels:
  tms/monitoring/monalesy/p/v1/serviceDesc/request:
    subscribe:
      traits:
      - $ref: '#/components/operationTraits/solace'
      message:
        $ref: '#/components/messages/ping'
      responseChannel: 'tms/monitoring/monalesy/p/v1/serviceDesc/inbox/{correlationId}'
  tms/monitoring/monalesy/p/v1/serviceDesc/inbox/{correlationId}:
    description:
      The reply topic needs to start with api name "tms/monitoring/monalesy/p/v1/serviceDesc" to not colide with other application.
      The reply topic needs to match a schema will not be blocked by ACL "tms/monitoring/monalesy/p/v1/serviceDesc/inbox/*".
    parameters:
      correlationId:
        $ref: '#/components/schemas/correlationId'
    response:
      traits:
      - $ref: '#/components/operationTraits/solace'
      message:
        $ref: '#/components/messages/pong'
components:
  messages:
    ping:
      traits:
      - $ref: '#/components/messageTraits/requestHeader'
      payload:
        $ref: '#/components/schemas/ping'
    pong:
      traits:
      - $ref: '#/components/messageTraits/responseHeader'
      payload:
        $ref: '#/components/schemas/pong'
  messageTraits:
    requestHeader:
      headers:
        type: object
        required:
        - correlationId
        properties:
          correlationId:
            $ref: '#/components/schemas/correlationId'
    responseHeader:
      headers:
        type: object
        properties:
          messageIndex:
            type: int
            minimum: 0
          messageCount:
            type: int
            minimum: 1

Example for "Options B"
channels:
  tms/monitoring/monalesy/p/v1/serviceDesc/request:
    subscribe:
      traits:
      - $ref: '#/components/operationTraits/solace'
      message:
        $ref: '#/components/messages/ping'
      responseChannel: 'tms/monitoring/monalesy/p/v1/serviceDesc/request'
    response:
      traits:
      - $ref: '#/components/operationTraits/solace'
      message:
        $ref: '#/components/messages/pong'
components:
  messages:
    ping:
      traits:
      - $ref: '#/components/messageTraits/requestHeader'
      payload:
        $ref: '#/components/schemas/ping'
    pong:
      traits:
      - $ref: '#/components/messageTraits/responseHeader'
      payload:
        $ref: '#/components/schemas/pong'
  messageTraits:
    requestHeader:
      headers:
        type: object
        required:
        - correlationId
        - replyTo
        properties:
          correlationId:
            type: string
            format: uuid
          replyTo:
            type: string
            examples:
            - tms/monitoring/monalesy/p/v1/serviceDesc/inbox/your-host-name/your-process-uuid
    responseHeader:
      headers:
        type: object
        required:
        - correlationId
        properties:
          correlationId:
            type: string
            format: uuid
          messageIndex:
            type: int
            minimum: 0
          messageCount:
            type: int
            minimum: 1

Closing as #847 has been merged 🎉


Revert "[IOTDB-2439]Library-UDF documents on website"

Reverts apache/iotdb#4920

Coverage decreased (-0.01%) to 67.75% when pulling 021ba81a93b447a7e523b88907578995393a8952 on revert-4920-library-merge-doc into d2c70405fbe297ec84c8fcf9a79b906410d96efc on master.


[Bug]: Summary polishing and custom API buttons are not available

前置阅读 | Pre-reading

[X] Issues
[X] README

服务类型 | Service Type
Official hosted service
系统信息 | System Information
Windows
Office 版本 | Office Version
microsoft 365
问题重现 | Bug reproduce

Could you please recheck features and now only translation button work? thanks a lot for your help

I can't reproduce the problem, can you supply more infomations?

Now it works, I have no idea.
From: Kuingsmile @.>
Sent: 2024年2月28日 6:10
To: Kuingsmile/word-GPT-Plus @.>
Cc: Master Yi @.>; Manual @.>
Subject: Re: [Kuingsmile/word-GPT-Plus] [Bug]: Summary polishing and custom API buttons are not available (Issue #46)
I can't reproduce the problem, can you supply more infomations?
—
Reply to this email directly, view it on GitHub https://github.com/Kuingsmile/word-GPT-Plus/issues/46#issuecomment-1968240668 , or unsubscribe https://github.com/notifications/unsubscribe-auth/A2TXLNQTWWPE2MQTDZ5JO7LYV23YVAVCNFSM6AAAAABD36CFT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRYGI2DANRWHA .
You are receiving this because you are subscribed to this thread.  https://github.com/notifications/beacon/A2TXLNW2BVTGGYHK3W3E45TYV23YVA5CNFSM6AAAAABD36CFT2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTVKD4BY.gif Message ID: @.*** @.***> >


Add Bicep sample

Follow up from https://github.com/microsoft/monaco-languages/pull/132
Contributing this as I noticed the sample on the demo page (https://microsoft.github.io/monaco-editor/) doesn't display:

Thank you!


AbstractArray -> MallocArray conversion?

I find MallocArray useful for working with ccall because it allows me to more easily pass in ref-wrapped structs that contain arrays. But it's a little clunky to manually have to convert from a plain Array to a MallocArray. Would there be anything wrong with having a default conversion like this?
function Base.convert(::Type{MallocArray{T, N}}, x::AbstractArray{T, N}) where {T, N}
    return MallocArray(pointer(x), length(x), size(x))
end

Okay, thanks! I didn't know about ArrayView, it seems like that's what I actually want here.

Cool! PRs welcome if you want to change anything here!


Fixed the footer issue, and it does not interfere with the horizontal scrollbar.

Description
Fixed the footer issue, and it does not interfere with the horizontal scrollbar.

Related Issue

[ ] Is this related to a specific issue? Is so please specify:

#44
Type of Changes
Use a check for ✓ the following type of changes:

Type

:bug: Bug fix

✓
:sparkles: New feature

:hammer: Refactoring

:100: Add tests

:link: Update dependencies

:scroll: Docs

Updates
Before
[If applicable, include a picture of the behavior before the changes were made. I.e. a screenshot of the behavior before the changes were made.]
After
[I.e. a screenshot of the behavior after the changes were made.]
Testing Steps / QA Criteria
[Describe the steps taken to test upcoming changes. Describe any additional testing that needs to be done beyond the steps outlined above. This might include manual testing, exploratory testing, or other types of testing that can't be easily automated.]
Checklist:

[ ] This PR is up to date with the development branch, and merge conflicts have been resolved
[ ] My code follows the style guidelines of this project
[ ] I have executed npm run lint and resolved any outstanding errors.
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] My changes generate no new warnings

@AitchGrasso or @mjbramich could either of you review this? I must have a smaller screen and so it doesn't look all that right.

Looking at the screenshot though, I think that looks pretty good.
I'm not sure when we changed the footer, but I like how it includes the github. maybe we can get rid of the github link when clicking on the kandoo logo later on.


Dark theme support

https://nebraltd.slack.com/archives/C0XGF69SN/p1647280802060629?thread_ts=1647279479.807949&cid=C0XGF69SN
@Louisreed what colors do we want for the dark theme?

@vpetersson the colors showing are colors for dark mode. This is the issue already opened for dark mode support.
@Louisreed should we use the same colors we have for light mode or you would share other color codes for these theme fields.
primary:
primaryBackground:
primaryText:
secondaryBackground:
secondary:
secondaryText:
error:
surface:
surfaceText:
surfaceSecondary:
surfaceSecondaryText:
surfaceContrast:
surfaceContrastText:

@Andrewsopoku Try this...
primary: #424242
primaryBackground: #424242
primaryText: #FFFFFF
secondaryBackground: #1D1D1D
secondary: #1D1D1D
secondaryText: #FFFFFF
error: #E74C3C
surface: #424242
surfaceText: #FFFFFF
surfaceSecondary: #1D1D1D
surfaceSecondaryText: #FFFFFF
surfaceContrast: #000000
surfaceContrastText: #FFFFFF

@Louisreed Looks like this after applying the shared colors.

@Andrewsopoku Looks good apart from the 'You have 1 Hotspot(s)" in black - can this field be changed to white (#FFFFFF) please?

Closed with https://github.com/NebraLtd/maker-starter-app/pull/67

@Louisreed Can we revisit this? That doesn't look great IMHO. Contrast are not great and it looks just off.

@vpetersson @Andrewsopoku Have the latest dark mode colours been published? I'll see what it look like on my ipad and make changes from there.

@Louisreed yes it has

@Louisreed Please are you able send the new colors for darkmode?

@Louisreed does the background remain same?

@Andrewsopoku Yes please

@Louisreed how does this look;

@Andrewsopoku Looks a little too dark, Instead of black can it be #242424 please?

@Andrewsopoku Yeah looking better thanks!


Function returned error

Good afternoon,
I'm running into an error when trying to use this package, even with your sample data and code. Below is the code in my do-file and the Stata error message it produces. I use Stata/SE 18.0.
Any suggestion for troubleshooting this would be greatly appreciated. And thank you for creating this useful package.
net install bumpline, from("https://raw.githubusercontent.com/asjadnaqvi/stata-bumpline/main/installation/") replace

ssc install palettes, replace
ssc install colrspace, replace

ssc install schemepack, replace
set scheme white_tableau

use "https://github.com/asjadnaqvi/stata-bumpline/blob/main/data/owid_emissions_reduced.dta?raw=true", clear

drop if iso_code==""

// keep a random set of years
keep if inlist(year, 1990, 1992, 1995, 2000, 2005, 2007, 2010, 2013, 2016, 2019)

bumpline total_ghg year, by(country)

bumpline total_ghg year, by(country)
ColrSpace::_recycle():  3021  class compiled at different times
ColrSpace::Palette():     -  function returned error
ColrSpace::palette():     -  function returned error
getpalette():     -  function returned error
:     -  function returned error
r(3021);

I restarted Stata and the issue no longer appears as long as I don't run the following code:
set scheme white_tableau

looks like there is an error in the code where the colors are processed.
try updating colorpalette and colrspace and see if the error still persists:
ssc install palettes, replace
ssc install colrspace, replace


Add option to export static strings

Hi,
Could there be an option to export the static strings that floss extracts?
When analyzing obfuscated strings that are not decoded in the first place by floss but are extracted as static after a dump with the decrypted strings, these static strings are not present in the .json output for x64dbg (at least that I know of, guess IDA is the same case).
I think it can be something that will not be used everytime but can be in certain situations. Having the option is always nice but not doing it by default is something expected.

Hi @orapic
Good idea, the static strings will definitely be present in the JSON output document in the upcoming v2.0 release.
https://github.com/mandiant/flare-floss/blob/master/floss/results.py#L164


Brainstorm WSGI integration

Utilities for generating / returning HTML

This could fit into the Connection framework pretty nicely.
We need to add some kind of HttpConnection implementation at some point.

https://github.com/vkottler/runtimepy/pull/165 I think this PR implements this idea well.


4.0.4 not actually installing newrelic-sysmond

From what I can see of newrelic::server::linux it should be installing the newrelic-sysmond package.
I'm trying to feed data from hiera, so I have:
newrelic::server::linux::newrelic_license_key: ''
Is that not enough?
Because it's not actually installing the package

Could you paste your manifest declaring the newrelic module/parameters and a fake hiera data so I can reproduce here with the same config.

Also the Linux OS/version.

We are seeing the same problems with 4.1.1 and puppetlabs-apt 2.1.0 on Ubuntu 14.04.

file { "/etc/newrelic.ini":
    ensure  => file,
    owner   => "root",
    group   => "root",
    mode    => 644,
    content => template("mynode/newrelic/newrelic.ini.erb"),
    notify  => Service["newrelic-sysmond"],
}
class { 'newrelic::server::linux':
    newrelic_license_key => hiera('newrelic::license_key'),
    newrelic_nrsysmond_labels => "Region:${ec2_availability_zone};Stack:${ec2_stack_name};Environment:${ec2_stackenvironment};Tier:${ec2_tiertype}",
}

I'm leveraging automatic parameters, so I'm just including your module via console classification (PE3.8) and setting this in hiera:
newrelic::server::linux::newrelic_license_key: 'my key here'
Ubuntu 14.04.02 (on both nodes and puppetmaster)

I'm not sure if that's the same issue but I'm having troubles on the first run as well:
Notice: /Stage[main]/Newrelic::Params/Apt::Source[newrelic]/Apt::Setting[list-newrelic]/File[/etc/apt/sources.list.d/newrelic.list]/ensure: defined content as '{md5}dce2a5607c7980c71f6492b7ba83390f'
Info: /Stage[main]/Newrelic::Params/Apt::Source[newrelic]/Apt::Setting[list-newrelic]/File[/etc/apt/sources.list.d/newrelic.list]: Scheduling refresh of Class[Apt::Update]
Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install newrelic-sysmond' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package newrelic-sysmond
Error: /Stage[main]/Newrelic::Server::Linux/Package[newrelic-sysmond]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install newrelic-sysmond' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package newrelic-sysmond

That's how I'm using it:
  class {'newrelic::server::linux':
    newrelic_license_key => '...',
  }

Is this still an issue using the latest version of the module?

I just now did the same thing, and I got the same error with puppet version 4.8.1. It stops at E: Unable to locate package newrelic-sysmond, however, it is resolved when puppet is run again. Other info:

Linux 4.2.0-42-generic x86_64
New Relic agent <IP_ADDRESS>


Negotiate time frames before request in Store

Currently, if a node signals that it suns Store (as a server), it is assumed that it can respond to any client request. This assumes that each Store node stores all past messages forever, which may not be sustainable. Explore the following idea:

a server can choose which pieces of history it serves;
a server announces what past periods it covers;
a client chooses a server accordingly.

Two sub-ideas on how time frame negotiations can happen:

servers announce them proactively in the P2P network;
a client asks a particular server before sending the actual request.

Indeed. Related to capability discovery. Ideally we should use 1) since its more efficient than 2). In other words, having this capability announcement as part of discovery, allows peers to search for the capability they are interested in a more efficient way. 2. would require going node by node, setting up a connection to query the capabilities, which is very inneficient.

we should use 1) since its more efficient

On the other hand, 1) distributes the burden to the whole network, while in 2) only the two involved nodes care about this negotiation. I'm thinking about edge cases, for example, when the description of which time frames a node covers is in itself heavy.  This is likely a secondary concern though.

A malicious operator could set up its node such that it covers lots of small irregular intervals, and everyone would have to sync this across the DHT or whatever peer discovery mechanism

yep, we should limit this to a fixed (or max) length field. The simpler the better. I dont think it would be necesary to allow for weird configurations. Just "this node stores the last x days" in shard y", where x and y are parameters advertised as capabilities in the discovery layer.


CME groups with NoMDEntries>1

Hello,
sorry to open a new request, this is related to #241.
We're using cpp decoder.
We have found that CME messages with repeating group (tested with message id=32 and id=42), every entry of the group beyond the first isn't decoded properly if there is some padding to blockLength (which is 32 in the mentioned messages).
To have the messages decoded we had to increase (Listener.cpp line 619 ):
relativeOffsetAnchor_ = bufferOffset_  + [ missing offset to 32 ]
thanks

It seems to work by replacing Listener.cpp line 619 with :
    relativeOffsetAnchor_ += stack_.top().blockLength_;

tests are ongoing.

Thanks for diving into this. Let me know what else you uncover.
I believe there is a unit test that tests for this case. But could be mistaken. So, would be interested to see why that test seems to work but the template you mention does not.
Due to travel and other commitments, will be a little while before I can properly look into this.

Hi @kino71 ,
I have the similar issues too. I tried to replace Listener.cpp line 619 with :
relativeOffsetAnchor_ += stack_.top().blockLength_;

It seems to work. I hope @tmontgomery  can take a look at this.

Hi guys,
Currently I am working on CME data and the suggestions I found here were very useful.
Nevertheless, even after applying the suggested fix, I get negative values for PRICENULL field: mantissa.
I believe that's incorrect value for market data, hence I believe there is a issue with the decoder.
Any ideas ?
Best regards,
Gosh

The C++ OTF decoder has been totally redone. It should account for blockLength correctly now.


SessionState Collection Plan B

Hi  Jerry
Here is another implementation that I enhanced as dictionary.
I added some comment for some method.
please review.

Hi J
return left?.Equals(right) ?? false;

this is not needed cos it is struct like KVP<K,V>. It won't be null.

This PR is not compat with the master base, could you update?


yum_package flush_cache shouldn't need to be an array

The documentation doesn't make it clear that flush_cache needs to be an array http://docs.opscode.com/resource_yum.html.
Works:
flush_cache [:before]

Doesn't:
flush_cache :before

NoMethodError
-------------
undefined method `any?' for :before:Symbol

Surely this doesn't need to be an array of one?

I think we should do the right thing and convert the scalar value to an array for you.  This is a broader issue with how we parse resource attributes.

Great thanks


Bump inmanta-dev-dependencies[async,extension,pytest] from 2.77.0 to 2.78.0 (#434)

Pull request opened by the merge tool on behalf of #434

Merged in 3299a076b205590ffcff9465ffef51d2b3fa7507


Debugger

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: Mehrkish:x: alarst13Mehrkish seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fixes #77: Use cert & key for SSL opts as detailed at http://apidock.com/ruby/v1_9_3_392/Net/HTTP/start/class#docs_body

:+1:

LGTM
Thanks @jimmidyson !
Can you please elaborate how/in which project do you use kubeclient?

@abonas Thanks for merging! Using it in fluentd plugin at https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter/ to add Kubernetes metadata to container logs. This is hopefully being used in Kubernetes to provide logging cluster addon, WIP.

This is hopefully being used in Kubernetes to provide logging cluster addon, WIP.

@jimmidyson , this is very interesting. can you elaborate more on the logging cluster addon part? who is working on that/what is the planned functionality?

There are some initial docs at https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/logging.md. I'm working on it as we've had centralised logging working in fabric8 for a while now & it's worth contributing. It's also going to be tech preview for openshift release I believe. I'm using this ruby client to enrich the logs with kubernetes metadata to make it easier to filter & provide authz too.

There are some initial docs at https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/logging.md. I'm working on it as we've had centralised logging working in fabric8 for a while now & it's worth contributing. It's also going to be tech preview for openshift release I believe. I'm using this ruby client to enrich the logs with kubernetes metadata to make it easier to filter & provide authz too.

thanks @jimmidyson , yes I understood the enrichment part the plugin was doing, but didn't know the details regarding the centralized logging work.


Laravel 11 Compatibility

Thank you very much for developing & maintaining this package. I observed it's last updated in 2022 for Laravel 9.
Is there a plan to update it for latest Laravel 11 versions?

If you want I can update it

Yes, please that would be great.


Get Content To Pack is creating Target Folders

When invoking GetContentToPack it is creating target folders if they don't exist. When JSON validator was invoking this it is creating a folder in the pack.

Fixed by #125