Make 8.0.0 Core available. New protocol and register removed.

This would be a huge pull request, relating to protocol, agent and backend. 8.x would be an new core without back forward compatibility.
After the experiences of removing endpoint_inventory, I found out this
strategy is successful.
Especially, we totally get rid of register, so I want to do more.
SkyWalking 8.0.0
First, it is already unexpected for me, we have to move to 8.0.0 so
quickly, but after the discussion with @hanahmily , and thinking about this for several days, I think
we have to.
The key chances are following

Remove service, service instance, and network address register. The old
register protocols are totally going to be removed.
The agent doesn't need to do register anymore. Service name and Service
Instance name are generated by the agent itself, but the extra information,
such as IP, hostname, language, should report to backend separately.
Service Traffic should be added just like the endpoint traffic but keep
the time bucket as we need accurate service name in the given duration
Service Instance Traffic should be added too, with external information,
such as language, hostname.
Trace context propagation context should be changed to accept string in
service instance name, endpoint name and network address. This could ease
the agent logic, but also, requires changes in all language agent and
plugin test tool,
Trace report protocol requires to change too, in order to adopt the
string.
e2e tests have to ignore PHP and LUA at first, and remove the 6.x
compatibility test(doesn't support anymore).

The benefits we will get are

Don't worry about the inventory(s) that has been deleted randomly by end
users. (We received a lot of issue reports about this)
The upgrade could be easier erasing the whole storage and reboot the new
one. (Users don't feel comfortable about upgrade)
No hot-reboot case in the agent side
No cache of network address register information in the agent.
No service and service instance cache in the OAP
No register lock in the OAP
No file buffer mechanism in the OAP too, same as no register happens.

In my mind, I think this totally break upgrade is super meaningful and will
be good change. Even we break many things, they are easy to follow.
@mrproliu  I think by following this, we need
to change the collaboration header to sw8 :) As no 7.1.0 release will
happen.
Link to mail list, https://lists.apache.org/thread.html/rda36fa8d191fc5750fc793993c69e14a917138bf97f9c2a461b72811%40<dev.skywalking.apache.org>

The codes level key changes are

Set up traffic for service and service instance. Service Inventory and Instance Inventory are removed.
Add ServiceInstanceProperties as a new source.
Remove Month as downsamping and query step.
...

@kezhenxu94 @ascrutae @arugal @heyanlong @ElderJames
New protocol

https://github.com/apache/skywalking/blob/8.x-core/docs/en/protocols/Skywalking-Cross-Process-Propagation-Headers-Protocol-v3.md
https://github.com/apache/skywalking/blob/8.x-core/docs/en/protocols/Trace-Data-Protocol-v3.md

@apache/skywalking-committers , I just made the project package passed. Now we could move on the core tests.

I will continue working on local testing including H2, MySQL and ElasticSearch 6.
@dmsolr Please help on agent plugin tests and InfluxDB storage implementation.
@arugal Please help on go2sky project
@heyanlong Please help on PHP project
@elderjames Please help on .net project
@ascrutae Please help on nodejs project.
@kezhenxu94 Please help on testing and new e2e setup
@mrproliu Please help on backend testing, especially profiling and LUA agent test.
@JaredTan95 Please help on backend testing.
@hanahmily Please run tests on mesh case after the above are done.
@TinyAllen @Fine0830 Please remove the month step support when UI time selector choose more than one month. In this case, still set to days, and Max days should be 60 days. The month step has been removed from the GraphQL.

Codecov Report

Merging #4599 into master will increase coverage by 2.18%.
The diff coverage is 15.92%.

@@            Coverage Diff             @@
##           master    #4599      +/-   ##
==========================================
+ Coverage   26.92%   29.11%   +2.18%
==========================================
  Files        1256     1189      -67
  Lines       28968    26018    -2950
  Branches     3958     3496     -462
==========================================
- Hits         7800     7574     -226
+ Misses      20455    17762    -2693
+ Partials      713      682      -31

Impacted Files
Coverage Δ

...m/network/trace/component/command/BaseCommand.java
0.00% <ø> (-100.00%)
:arrow_down:

...k/trace/component/command/CommandDeserializer.java
0.00% <0.00%> (ø)

...rk/trace/component/command/ProfileTaskCommand.java
0.00% <ø> (ø)

...rk/trace/component/command/TraceIgnoreCommand.java
0.00% <ø> (ø)

...agent/core/commands/CommandExecutionException.java
0.00% <ø> (ø)

...pm/agent/core/commands/CommandExecutorService.java
41.66% <ø> (-12.18%)
:arrow_down:

...alking/apm/agent/core/commands/CommandService.java
28.26% <ø> (-8.70%)
:arrow_down:

...alking/apm/agent/core/context/ContextSnapshot.java
0.00% <0.00%> (ø)

...g/apm/agent/core/context/IgnoredTracerContext.java
71.42% <0.00%> (ø)

...apm/agent/core/context/ids/DistributedTraceId.java
0.00% <0.00%> (-69.24%)
:arrow_down:

... and 327 more

Continue to review full report at Codecov.

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

@BFergerson Please notice this PR, as you want to move the vert.x case in the main repo too.
We are changing the protocol, to make the backend has better performance and agent implementation easier. Read this #4595 as step one and this PR as step two, you will have more context.

Mark it as "Ready for review" as the test cases should be fixed now, and move to next step if anyone will review the code

Summary
This pull request is open for 10 days, and I worked on this 2 weeks ago. Thanks everyone to help making this PR and tests work now.
Here are the list of changes we made in this pull request. Top 3 are the principle changes, others are following these principles.

New agent and mesh report protocol.
New agent header protocol.
Service register, instance register and network address register have been removed permanently.
Service traffic, instance traffic and network alias metrics are added to replace the service, instance and network address inventory.
Register process has been removed.
Metrics stream process supports insert only mode, especially for traffic entities.
Metrics stream process supports no-downsampling mode for traffic entities and network alias.
Remove all register mechanism and cache in the java agent.
Remove MONTH step in GraphQL query.
Update UI to remove MONTH step query, the max query range is 60 days now.
Simplify the TTL to metrics and record. And the unit has been formatted in Day unit. No specific TTL for ElasticSearch storage.
Buffer mechanism of trace receiver and mesh receiver has been removed due to no register.
New service id, instance id and endpoint id rules, including service relation, instance relation and endpoint relation id rules.
Java agent support keep tracing mode, meaning, agent generating tracing context even the backend is unconnected/unavailable.
Plugin test tool up to date, in order to support new protocol.
Plugin tests expected data files updated.
E2E tests updated.
[TBD] InfluxDB storage implementation is not available, need @dmsolr to fix later, in order to reduce the master change block by this PR.

FYI @apache/skywalking-committers

@kezhenxu94 Are you going to do code level review?

@kezhenxu94 Are you going to do code level review?

I can do another round of review recently, but that’s not a blocker to merge this, it looks good to me generally, just merge it if necessary

@kezhenxu94 I am adjusting some documentations, after that, I will merge this.


CURIEs & IRIs transformed

@balhoff @kltm It can be a bit misleading that Minerva is transforming the results of a SPARQL query; I have seen that in the past where I was expecting to retrieve a IRI and was retrieving a transformed CURIE.
In @tmushayahama ART, this is causing an issue as he is chaining the results of SPARQL queries and was not expecting those variables to be transformed. There are workarounds on the client side, but we want to avoid too much logics or transformations on this end.
Proposed action: have a tag in minerva requests to block or enable the current transform in the response

turning off direct sparql query access


chore(pyproject): update dependencies

Description
Update dependencies to make the project compatible with more package versions.
Checklist

[ ] Tests covering the new functionality have been added
[ ] Code builds clean without any errors or warnings
[ ] Documentation has been updated
[ ] Changes have been added to the CHANGELOG.md
[ ] You added yourself to the CONTRIBUTORS.md

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 93.002%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
367

Relevant Lines:
389

💛  - Coveralls


ValidatedGraphConfig Initialization Failed

OS Platform and Distribution
MacOS ARM
Compiler version
No response
Programming Language and version
Python 3.11.8
Installed using virtualenv? pip? Conda?(if python)
virtualenv pip
MediaPipe version
0.10.10
Bazel version
7.0.2
XCode and Tulsi versions (if iOS)
15.2
Android SDK and NDK versions (if android)
No response
Android AAR (if android)
None
OpenCV version (if running on desktop)
4.9.0
Describe the problem
It gives me errors everytime I run anything that relates to mediapipe. CV runs great, but when trying to use hands = mpHands.Hands(), hands = mp.solutions.hands, I get the error. Is it because I'm running on Mac ARM? I
Complete Logs
/Users/usera/Documents/Development/Apps/prj/.venv/bin/python /Users/usera/Documents/Development/Apps/prj/main.py

2024-02-24 17:53:59.478 python[83108:17726527] WARNING: AVCaptureDeviceTypeExternal is deprecated for Continuity Cameras. Please use AVCaptureDeviceTypeContinuityCamera and add NSCameraUseContinuityCameraDeviceType to your Info.plist.
Traceback (most recent call last):
  File "/Users/usera/Documents/Development/Apps/prj/main.py", line 8, in <module>
    hands = mpHands.Hands()
            ^^^^^^^^^^^^^^^
  File "/Users/usera/Documents/Development/Apps/prj/.venv/lib/python3.11/site-packages/mediapipe/python/solutions/hands.py", line 114, in __init__
    super().__init__(
  File "/Users/usera/Documents/Development/Apps/prj/.venv/lib/python3.11/site-packages/mediapipe/python/solution_base.py", line 248, in __init__
    self._graph = calculator_graph.CalculatorGraph(
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: ValidatedGraphConfig Initialization failed.
ImageToTensorCalculator: ; RET_CHECK failure (mediapipe/calculators/tensor/image_to_tensor_calculator.cc:144) ValidateOptionOutputDims(options) returned INTERNAL: ; RET_CHECK failure (./mediapipe/calculators/tensor/image_to_tensor_utils.h:136) options.has_output_tensor_float_range() || options.has_output_tensor_int_range() || options.has_output_tensor_uint_range()Output tensor range is required.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ImageToTensorCalculator: ; RET_CHECK failure (mediapipe/calculators/tensor/image_to_tensor_calculator.cc:144) ValidateOptionOutputDims(options) returned INTERNAL: ; RET_CHECK failure (./mediapipe/calculators/tensor/image_to_tensor_utils.h:136) options.has_output_tensor_float_range() || options.has_output_tensor_int_range() || options.has_output_tensor_uint_range()Output tensor range is required.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
SplitTensorVectorCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.

Process finished with exit code 1

I was able to replicate this error on an M1 mac with 3.11.7, running mediapipe 0.10.10, trying to run mediapipe holistic pose estimation. Downgrading to 0.10.9 fixed this issue.
It appears to happen on intel macs too, as I only tested the upgrade while trying to fix an issue from someone running 0.10.10 on an intel mac

philipqueen

Thanks for the tip. I was facing the same issue on my M3 Mac and downgrading mediapipe to 0.10.9 did resolve

yeaaaaah same, downgrading from 0.10.10 to 0.10.9 worked for me, thanks big dog

Thanks a lot!!!! Downgrading to 0.10.9 worked for mi, too (apple M2)

Thanks a lot, you guys saved my day. Downgrading MediaPipe to 0.10.9 works like a charm !

Hi @M8DLT,
Could you please share the exact standalone code you are following, Or steps taking from our documentation from here? Additionally, kindly confirm the macOS version you are using. This information will help us reproduce and better understand the issue on our end.
Thank you!!

I get the same error starting with 0.10.10 on a Mac M2 when loading legacy models (FaceMesh or Hands):
$ python -c "from mediapipe.python.solutions.face_mesh import FaceMesh; FaceMesh()"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/twoertwein/miniforge3/envs/mediapipe/lib/python3.10/site-packages/mediapipe/python/solutions/face_mesh.py", line 95, in __init__
    super().__init__(
  File "/Users/twoertwein/miniforge3/envs/mediapipe/lib/python3.10/site-packages/mediapipe/python/solution_base.py", line 248, in __init__
    self._graph = calculator_graph.CalculatorGraph(
RuntimeError: ValidatedGraphConfig Initialization failed.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ImageToTensorCalculator: ; RET_CHECK failure (mediapipe/calculators/tensor/image_to_tensor_calculator.cc:144) ValidateOptionOutputDims(options) returned INTERNAL: ; RET_CHECK failure (./mediapipe/calculators/tensor/image_to_tensor_utils.h:136) options.has_output_tensor_float_range() || options.has_output_tensor_int_range() || options.has_output_tensor_uint_range()Output tensor range is required.
SplitTensorVectorCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
SplitTensorVectorCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
SplitTensorVectorCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.

$ python -c "from mediapipe.python.solutions.hands import Hands; Hands()"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/twoertwein/miniforge3/envs/mediapipe/lib/python3.10/site-packages/mediapipe/python/solutions/hands.py", line 114, in __init__
    super().__init__(
  File "/Users/twoertwein/miniforge3/envs/mediapipe/lib/python3.10/site-packages/mediapipe/python/solution_base.py", line 248, in __init__
    self._graph = calculator_graph.CalculatorGraph(
RuntimeError: ValidatedGraphConfig Initialization failed.
ImageToTensorCalculator: ; RET_CHECK failure (mediapipe/calculators/tensor/image_to_tensor_calculator.cc:144) ValidateOptionOutputDims(options) returned INTERNAL: ; RET_CHECK failure (./mediapipe/calculators/tensor/image_to_tensor_utils.h:136) options.has_output_tensor_float_range() || options.has_output_tensor_int_range() || options.has_output_tensor_uint_range()Output tensor range is required.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ImageToTensorCalculator: ; RET_CHECK failure (mediapipe/calculators/tensor/image_to_tensor_calculator.cc:144) ValidateOptionOutputDims(options) returned INTERNAL: ; RET_CHECK failure (./mediapipe/calculators/tensor/image_to_tensor_utils.h:136) options.has_output_tensor_float_range() || options.has_output_tensor_int_range() || options.has_output_tensor_uint_range()Output tensor range is required.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
SplitTensorVectorCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.

I was able to replicate this issue with mediapipe 0.10.11 on my M1 (Monterey) Mac as well.
Using @twoertwein's example, but with another legacy solution (holistic): python -c "from mediapipe.python.solutions.holistic import Holistic; Holistic()"

Is there any solution? I have the same error!

I'm getting the same error when running mediapipe.solutions.pose.Pose(), and downgrading to 0.10.9 didn't work.

i m also getting same error in mac  M1 , is there any solution

Hi @AdityaBeewal,
Could you please outline the complete steps you are following, referring to the documentation or standalone code, to replicate the issue and subsequently resolve it if necessary?
Thank you!!

downgrading mediapipe from 0.10.11 to 0.10.9 worked for me on my m1 mac :)

@kuaashish Is any work being done on this? The past two releases on mac error when trying to use any of the legacy solutions. Will this be fixed or are the legacy solutions deprecated?
Below is the full error message. The list of errors seems relatively straightforward, although I'm not familiar enough with the inner workings of mediapipe to tackle it myself.
python -c "from mediapipe.python.solutions.holistic import Holistic; Holistic()"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/philipqueen/miniconda3/envs/mp_test/lib/python3.11/site-packages/mediapipe/python/solutions/holistic.py", line 114, in __init__
    super().__init__(
  File "/Users/philipqueen/miniconda3/envs/mp_test/lib/python3.11/site-packages/mediapipe/python/solution_base.py", line 248, in __init__
    self._graph = calculator_graph.CalculatorGraph(
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: ValidatedGraphConfig Initialization failed.
ImageToTensorCalculator: ; RET_CHECK failure (mediapipe/calculators/tensor/image_to_tensor_calculator.cc:144) ValidateOptionOutputDims(options) returned INTERNAL: ; RET_CHECK failure (./mediapipe/calculators/tensor/image_to_tensor_utils.h:136) options.has_output_tensor_float_range() || options.has_output_tensor_int_range() || options.has_output_tensor_uint_range()Output tensor range is required.
InferenceCalculatorCpu: ; RET_CHECK failure (mediapipe/calculators/tensor/inference_calculator_cpu.cc:63) !options.model_path().empty() ^ kSideInModel(cc).IsConnected()Either model as side packet or model path in options is required.
SplitDetectionVectorCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
ImageToTensorCalculator: ; RET_CHECK failure (mediapipe/calculators/tensor/image_to_tensor_calculator.cc:144) ValidateOptionOutputDims(options) returned INTERNAL: ; RET_CHECK failure (./mediapipe/calculators/tensor/image_to_tensor_utils.h:136) options.has_output_tensor_float_range() || options.has_output_tensor_int_range() || options.has_output_tensor_uint_range()Output tensor range is required.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
SplitTensorVectorCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
SplitNormalizedLandmarkListCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
SplitLandmarkListCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
SplitNormalizedLandmarkListCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
SplitNormalizedLandmarkListCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
SplitNormalizedLandmarkListCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
SplitNormalizedLandmarkListCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
ImageToTensorCalculator: ; RET_CHECK failure (mediapipe/calculators/tensor/image_to_tensor_calculator.cc:144) ValidateOptionOutputDims(options) returned INTERNAL: ; RET_CHECK failure (./mediapipe/calculators/tensor/image_to_tensor_utils.h:136) options.has_output_tensor_float_range() || options.has_output_tensor_int_range() || options.has_output_tensor_uint_range()Output tensor range is required.
SplitNormalizedLandmarkListCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
ImageToTensorCalculator: ; RET_CHECK failure (mediapipe/calculators/tensor/image_to_tensor_calculator.cc:144) ValidateOptionOutputDims(options) returned INTERNAL: ; RET_CHECK failure (./mediapipe/calculators/tensor/image_to_tensor_utils.h:136) options.has_output_tensor_float_range() || options.has_output_tensor_int_range() || options.has_output_tensor_uint_range()Output tensor range is required.
InferenceCalculatorCpu: ; RET_CHECK failure (mediapipe/calculators/tensor/inference_calculator_cpu.cc:63) !options.model_path().empty() ^ kSideInModel(cc).IsConnected()Either model as side packet or model path in options is required.
ImageToTensorCalculator: ; RET_CHECK failure (mediapipe/calculators/tensor/image_to_tensor_calculator.cc:144) ValidateOptionOutputDims(options) returned INTERNAL: ; RET_CHECK failure (./mediapipe/calculators/tensor/image_to_tensor_utils.h:136) options.has_output_tensor_float_range() || options.has_output_tensor_int_range() || options.has_output_tensor_uint_range()Output tensor range is required.
InferenceCalculatorCpu: ; RET_CHECK failure (mediapipe/calculators/tensor/inference_calculator_cpu.cc:63) !options.model_path().empty() ^ kSideInModel(cc).IsConnected()Either model as side packet or model path in options is required.
ImageToTensorCalculator: ; RET_CHECK failure (mediapipe/calculators/tensor/image_to_tensor_calculator.cc:144) ValidateOptionOutputDims(options) returned INTERNAL: ; RET_CHECK failure (./mediapipe/calculators/tensor/image_to_tensor_utils.h:136) options.has_output_tensor_float_range() || options.has_output_tensor_int_range() || options.has_output_tensor_uint_range()Output tensor range is required.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
SplitTensorVectorCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
ConstantSidePacketCalculator: ; RET_CHECK failure (mediapipe/calculators/core/constant_side_packet_calculator.cc:64) (cc->OutputSidePackets().NumEntries(kPacketTag))==(options.packet_size())Number of output side packets has to be same as number of packets configured in options.
SplitTensorVectorCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
ImageToTensorCalculator: ; RET_CHECK failure (mediapipe/calculators/tensor/image_to_tensor_calculator.cc:144) ValidateOptionOutputDims(options) returned INTERNAL: ; RET_CHECK failure (./mediapipe/calculators/tensor/image_to_tensor_utils.h:136) options.has_output_tensor_float_range() || options.has_output_tensor_int_range() || options.has_output_tensor_uint_range()Output tensor range is required.
SplitTensorVectorCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
SplitTensorVectorCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.
SplitTensorVectorCalculator: The number of output streams should match the number of ranges specified in the CalculatorOptions.

Thanks a lot, downgrading mediapipe to 0.10.9 worked for me as well. I've Macbook Air M1.

Hi @philipqueen,
If the issue stems from legacy solutions, we believe it will not be addressed, as we have already deprecated and ceased maintenance on them.
Thank you!!

If the issue stems from legacy solutions, we believe it will not be addressed, as we have already deprecated and ceased maintenance on them.
@kuaashish thanks for the response. Maybe it's best if mediapipe adds a deprecation warning when trying to run code like this? It seems even for solutions that are still maintained (hands, pose), they fail with a calculator graph error. Checking the documentation, it seems there's new code recommended on for the maintained solutions:

import mediapipe as mp

BaseOptions = mp.tasks.BaseOptions
PoseLandmarker = mp.tasks.vision.PoseLandmarker
PoseLandmarkerOptions = mp.tasks.vision.PoseLandmarkerOptions
VisionRunningMode = mp.tasks.vision.RunningMode

options = PoseLandmarkerOptions(
    base_options=BaseOptions(model_asset_path=model_path),
    running_mode=VisionRunningMode.IMAGE)

with PoseLandmarker.create_from_options(options) as landmarker:
  # The landmarker is initialized. Use it here.

But accessing the old method like from mediapipe.python.solutions.pose import Pose; Pose() is still possible, it just gives you a calculator graph error.
I think the expected behavior would be either an import error when trying to import the solutions this way, or a logged warning that this is no longer the proper way of calling this solution.

Hi, I built an extensive application on mediapipe.solutions.face_mesh.FaceMesh()
Where can I find details on how to refactor my code to use the latest API please?

owngrading to 0.10.9 fixed this issue.
It appears to happen on intel macs too, as I only tested the upgrade while trying to fix an issue from someone running 0.10.10 on an intel mac

thank you worked for me too on M1

downgrading mediapipe from 0.10.11 to 0.10.9 worked for me on my m1 mac :)

hey, i use m1 mac too, but it not work for me, help me

Thanks a lot, downgrading mediapipe to 0.10.9 worked for me as well. I've Macbook Air M1.

hey @arnabdotpy, i've macbook air m1 too, but downgrading mediapipe 0.10.9 not work for me. help me pls

Also having this issue on M1

I was able to replicate this error on an M1 mac with 3.11.7, running mediapipe 0.10.10, trying to run mediapipe holistic pose estimation. Downgrading to 0.10.9 fixed this issue.
It appears to happen on intel macs too, as I only tested the upgrade while trying to fix an issue from someone running 0.10.10 on an intel mac

Thanks for the information! Same error on an M3 Mac with python 3.10.11, running mediapipe 0.10.11. Downgrading to 0.10.9 also worked for me!

Where can I find details on how to refactor my code to use the latest API please?

https://developers.google.com/mediapipe/solutions/guide#legacy

The legacy solutions seem to work with 0.10.13 on Mac again :)
$ python -c "from mediapipe.python.solutions.face_mesh import FaceMesh; FaceMesh()"
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
I0000 00:00:1714788179.915617 3679575 gl_context.cc:357] GL version: 2.1 (2.1 Metal - 88), renderer: Apple M2 Pro
INFO: Created TensorFlow Lite XNNPACK delegate for CPU.


[DOCS] README updates

Updated Scala and scala libs versions, highlight the possibility to specify scala_version for scala_proto_repositories rule (because default is 2.11.8 and it obviously doesn't work with default scala version).

I signed it!

Thanks!


Fixed: convert to single function and use processIOReader

Codecov Report

Merging #155 into master will increase coverage by -0.02%.

@@            Coverage Diff             @@
##           master     #155      +/-   ##
==========================================
- Coverage   57.07%   57.05%   -0.02%
==========================================
  Files          30       30
  Lines        3797     3789       -8
==========================================
- Hits         2167     2162       -5
+ Misses       1486     1485       -1
+ Partials      144      142       -2

Impacted Files
Coverage Δ

processmon/processmon.go
62.93% <95%> (+0.02%)
:white_check_mark:

Continue to review full report at Codecov.

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


fix: retry user agent get from libp2p peerstore

This pr fixes the flaky test that checks for libp2p user agent in logs in high load environments like CI. It also ensures higher probability that the user agent is logged in high load environments.
The core problem is that the peerstore may not contain all keys and values right after the connections is created.
This retry mechanism ensures more reliable user agent propagation.

This change is

I think this needs a rebase


Revert "fix: remove trace from ops (#780)"

Changes

#805  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @NathanFlurry and the rest of your teammates on  Graphite


Add doc for --tags-from-host from v3.3.0

This was done via #791 and released in v3.3.0. The PR prose refers to a command-line flag that is wrong :(

Many thanks @petemounce, what did I get wrong in the PR?

I think it was --add-host-tags in #791's description/comments.


Fixed #25889 -- Organize tests in tests/queries

The tests follow the documentation to the best they can. There were some places where improvisation was needed. There were some cases where I was confused(see ticket for further information) and if someone can resolve them I will be happy to edit the changes. Ticket

This isn't what I had in mind. Part of the goal is to not to have a 4K line test file.
The added docstrings don't conform to the test docstring style described at https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/coding-style/#python-style.

Sorry about the docstring. I will redo that. But per your comment left on the ticket by you stated that the tests first required a cleanup and then further tickets should be made to partition them into different files. I could do it all under one ticket only but I thought it would be better to get this approved then I could start on the splitting up of tests into different files.

Unfortunately, I think most of the proposed docstrings are not very helpful.


Add initial rubocop config

Hello
As mention in #606. Here is the initial commit for rubocop. I added the todo list of offenses. We still have to choose which "cops" we enable and sometimes at which level.
This PR rely on #607 otherwise I was not able to build the app.

Merci! Does that Travis CI output look right to you? It doesn't look like it's only running on changed files.

I'm not an expert here. Tests are passing. Good to merge?

Hold up, @benoittgt added something that was supposed to only run rubocop on changed files I think but it doesnt appear to work. Wanna hear his reply first.
I am also OK with just running Travis on all files every build.

Yes. I don't seem that Travis is impacted about the result of rubocop. I'm gonna have a look.

Ok it works for Travis. If I run on all files I have two offenses that's why the CI failed.

Cool, fix 'em and lets merge this.

I was able to fix one. But the one in config/environments/production.rb:89 was a mystery for me.
I tried
  config.cache_store = if ENV["MEMCACHIER_SERVERS"]
                         :dalli_store,
                           (ENV["MEMCACHIER_SERVERS"] || "").split(","),
                           {:username => ENV["MEMCACHIER_USERNAME"],
                            :password => ENV["MEMCACHIER_PASSWORD"],
                            :failover => true,
                            :socket_timeout => 1.5,
                            :socket_failure_delay => 0.2
                         }
                       else
                         :dalli_store
                       end

But
/Users/bti/.rvm/gems/ruby-2.4.1/gems/bootsnap-0.3.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:17:in `require': /Users/bti/code/codetriage/config/environments/production.rb:90: syntax error, unexpected ',', expecting keyword_end (SyntaxError)
                 :dalli_store, (ENV["MEMCACHIER_SERVERS"] ||

So it's disabled for this part. If you have a solution I will change it.

Good enough 👍  Thanks @benoittgt!


Generate Training data

Hello, thank you very much for your code. I am very interested in your work and I have tried using evaluate.py to generate nuScenes training data. But, I have noticed that its speed is a bit slow (only one GPU is in use). May I ask if there is any solution?
I tried to modify a single GPU to multiple GPUs, but failed:  all GPUs are processing the same scene. May I know how to modify this code? Looking forward to your reply!

Hello, I often get IndexError: list index out of range errors when generating NuScenes training data. Usually, they look like this
 Is my situation normal?
It looks like it's because of scene_depth_results is empty. And the code about updating 'scene_depth_results':

How should I modify this code?

Hi @heiheishuang , thank you for your interest in our work and sorry for the delayed response.
About the speed of generating the data: I've just used a single GPU to generate the data and it took me a couple of days. I guess if you have multiple GPUs available you could try to modify the code such that you can specify which gpu should be used. Then you could divide all nuScenes scenes into n split-files and n config-files where each file would look as follows:
nuScenes_split_gpu0.txt:
scene-0000
scene-0000
...

dataset_generation_nuscenes_gpu0.yaml:
...
datasets:
  validation:
     split: [nuScenes_split_gpu0.txt]
...
...

...
you could then run the script simultaneously multiple times for each available gpu (assuming you also have sufficient memory):
python evaluate.py --config <path_to_config>/dataset_generation_nuscenes_gpu0.yaml

About the error you've encountered: Sorry for the trouble this caused. For the specific scenes where this error occurs, the algorithm fails to do any reasonable scene reconstruction (e.g. because the scene is static) and thus no estimations are accumulated. This in itself is not an issue because we do not want to train on such sequences anyway. It can be fixed by simply changing L174 in eval_dataset.py to ...
if 'depth' in self.metrics and len(scene_depth_results) >= 1:

... i.e. we skip evaluation for scenes where we do not have any predictions. I've changed the code accordingly.
Note about NuScenes training: If you generate the data for NuScenes from scratch I suggest you remove L138 in NuScenesDataset.py. We actually had a bug in our training where the intrinsics we used for NuScenes were slightly off. Thus this line is there to get the same results as in the paper. You might be able to achieve better results by using the correct NuScenes intrinsics.

Hello, I have modified this code.   if 'depth' in self.metrics and len(scene_depth_results) >= 1:
But a new error has appeared.

"I'm training on the DDAD dataset, but encountered an error similar to the one shown in the image. Initially, I suspected that the scene 000199 in my dataset was downloaded incorrectly. So, as shown in the image, I used scene 000198 as the last one, but still encountered the error 'IndexError: index 3906 is out of bounds for dimension 0 with size 3900'. What should I do to modify the code?"

Hello, I have modified this code:  if 'depth' in self.metrics and len(scene_depth_results) >= 1:
But a new error has appeared.

"I'm training on the DDAD dataset, but encountered an error similar to the one shown in the image. Initially, I suspected that the scene 000199 in my dataset was downloaded incorrectly. So, as shown in the image, I used scene 000198 as the last one, but still encountered the error 'IndexError: index 3906 is out of bounds for dimension 0 with size 3900'. What should I do to modify the code?"


feat: add error markers to groups

closes #180

Unfortunately, @bpmn-io/sr does not work for this one. To test it out, link the properties-panel from @camunda/linting and change the import path for the properties-panel css to @bpmn-io/properties-panel: https://github.com/camunda/linting/blob/549ec9cfbed996845312015a804090ba08aeffb6/test/spec/modeler/Linting.spec.js#L40

I've left a couple of comments regarding CSS. Once we fix them, I think we are on a good track to merge this.

Thank you for the review, I think the point is valid - we should not use non-namespaced classes. I implemented your suggestions with 4f17111


Add apply_ln to stack_head_results and stack_neuron_results

Description
Previously I added an apply_ln parameter to accumulated_resid and decompose_resid in PR #220 to address issue #209 . After using them, I'm noticing it's also natural to make an analogous call to stack_head_results and stack_neuron_results (like when doing direct logit attribution). This PR adds the same functionality to stack_head_results and stack_neuron_results so they are all consistent. I also deleted a line from the stack_head_results doc string which doesn't seem true.
Type of change

[x ] New feature (non-breaking change which adds functionality)

Checklist:

[x ] I have made corresponding changes to the documentation
[x ] My changes generate no new warnings
[x ] I have added tests that prove my fix is effective or that my feature works
[x ] New and existing unit tests pass locally with my changes
[x ] I have not rewritten tests relating to key interfaces which would affect backward compatibility

Thanks, looks good!


[vNext] System.Text.Json as default serialization mechanism

This PR works on replacing Json.NET as the default serialization mechanism in the SDK. While Json.NET can still be used through an implementation of CosmosSerializer (like the current one for V3) all REST API contracts, and item operations (CRUD and Queries) will use System.Text.Json by default.
In this PR:

All Public REST API classes use System.Text.Json converters
The internal default serializer is https://github.com/Azure/azure-cosmos-dotnet-v3/blob/1e6a86c50d70520deadb4a5dd07df878b3fdc138/Microsoft.Azure.Cosmos/azuredata/Serializer/CosmosTextJsonSerializer.cs
Some files that were previously linked to the V3 versions have now been unlinked and new versions created. This was needed to de-couple from Json.NET contracts, for example, Spatial types such as LineString.
Emulator and Unit Tests that relied on Json.NET serialization comparisons were adjusted to use System.Text.Json instead
Deserialization of classes coming from Microsoft.Azure.Cosmos.Direct, such as OfferV2 and Error are using Converters that get added to the serializer, such as https://github.com/Azure/azure-cosmos-dotnet-v3/blob/1e6a86c50d70520deadb4a5dd07df878b3fdc138/Microsoft.Azure.Cosmos/azuredata/Serializer/TextJsonOfferV2Converter.cs because the source code of those classes is not available to be decorated.


fix the online locaregistry in the cluster details only displays 'online'

Signed-off-by: liuying<EMAIL_ADDRESS>
What type of PR is this?
/kind bug

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #73
Special notes for reviewers:

Does this PR introduced a user-facing change?

Additional documentation, usage docs, etc.:

/lgtm
/approve


Update internal transaction trace.

A recent PR changes the trace of transaction trace. The changes are described as follows.
中文摘要

trace 列表的每个 item 增加一个 field "valid". "valid" 为 false 时表示该条 trace 因为 revert 等原因没有改变 state.
Gas 费用的收取和存储押金的收取、退还将产生 trace. 类型为 "internal_transfer_action".
Type 为 ”internal_transfer_action“ 的 trace 项添加两个 field, "fromPocket" 和 "toPocket". 只有当 "fromPocket" 等于 "balance" 时，才意味着 "from" 的余额被修改。

The "valid" field
If the inner message call triggers an error and the error is caught by the outside contract, the whole transaction could also succeed, but the effects of the inner message call are reverted. The traces of the reverted message call will also be retained for debugging usage.
Here, we add a new field "valid" to indicate whether the corresponding trace is reverted.
Trace for gas payment.
Any transaction bumping nonce during execution will generate one or two traces with type "internal_transfer_action" to indicate gas payment and gas refund.
Consider a transaction has gas limit 40000 and gas price 3 Drip.
For gas payment, if the transaction is sponsored, the trace will be
{
    "action": {
        "from": <contract_address>,
        "fromPocket": "sponsor_balance_for_gas",
        "to": <zero_address>,
        "toPocket": "gas_payment",
        "value": 120000,
    }
    "type": "internal_transfer_action"
    ......
}

If the transaction is not sponsored, the trace will be
{
    "action": {
        "from": <sender_address>,
        "fromPocket": "balance",
        "to": <zero_address>,
        "toPocket": "gas_payment",
        "value": 120000,
    }
    "type": "internal_transfer_action"
    ......
}

This should be the first trace of most transactions.
After execution, if this transaction costs 25000 gas, up to 1/4 of gas limit, i.e., 10000 gas (30000 Drip when gas price = 3) will be refunded, then it will generate a trace
{
    "action": {
        "from": <zero_address>,
        "fromPocket": "gas_payment",
        "to": ...,
        "toPocket": ...,
        "value": 30000,
    },
    "type": "internal_transfer_action",
    ...
}

Trace for storage collateral.
Consider a transaction collateralize 10 Drip (it can not happen in a real Conflux system, just for example).
If the transaction is sponsored,
{
    "action": {
        "from": <contract_address>,
        "fromPocket": "sponsor_balance_for_collateral",
        "to": <contract_address>,
        "toPocket": "storage_collateral",
        "value": 10,
    },
    "type": "internal_transfer_action",
    ...
}

If the transaction is not sponsored,
{
    "action": {
        "from": <sender_address>,
        "fromPocket": "balance",
        "to": <sender_address>,
        "toPocket": "storage_collateral",
        "value": 10,
    },
    "type": "internal_transfer_action",
    ...
}

When releasing storage, the value will be returned to the same route.
Changes in the sponsorship (example)
When a user adds sponsor balance for gas for a contract, the trace will be
Before change
{
    "action": {
        "from": <sender_address>,
        "to": <internal_contract_for_sponsorship>, // 0x088800...01
        "value": ...,
        ...
    },
    "type": "call",
    ...
}

After change
{
    "action": {
         // call type trace has no fromPocket and toPocket field. Because the pocket is always "balance".
        "from": <sender_address>,
        "to": <internal_contract_for_sponsorship>, // 0x088800...01
        "value": ...,
        ...
    },
    "type": "call",
    ...
}
{
    "action": {
        "from": <internal_contract_for_sponsorship>, // 0x088800...01
        "fromPocket": "balance",
        "to": <contract_address>,
        "toPocket": "sponsor_balance_for_gas"
        "value": ...,
        ...
    },
    "type": "internal_transfer_action",
    ...
}

Now you can know which contract is sponsored from the trace.
Changes in the staking (example)
When a user stakes, the trace will be
Before change
{
    "action": {
        "from": <sender_address>,
        "to": <internal_contract_for_staking>, // 0x088800...02
        "value": ...,
        ...
    },
    "type": "internal_transfer_action",
    ...
}

After change
{
    "action": {
        "from": <sender_address>,
        "fromPocket": "balance",
        "to": <sender_address>,
        "toPocket": "staking_balance",
        "value": ...,
        ...
    },
    "type": "internal_transfer_action",
    ...

}

Changes in integrity constraints
Before change

The balance increasing (or decreasing) of an address (except the internal contract) during transaction execution corresponds to a trace whose "to" (or "from") is this address.

After change

The balance increasing (or decreasing) of an address (all the address) during transaction execution corresponds to a trace whose "to" (or "from") is this address and "toPocket" (or "fromPocket") is "balance". (Note: for trace type except "interal_transfer_action", the "fromPocket" and "toPocket" equal to "balance" implicitly.)
The staking balance/collateral balance/sponsor balance for gas/sponsor balance for collateral increasing (or decreasing) of an address during transaction execution corresponds to an internal_transfer type trace whose "to" (or "from") is this address and "toPocket" (or "fromPocket") is "sponsor_balance"/"storage_collateral"/"sponsor_balance_for_gas"/"sponsor_balance_for_collateral".

Specification for pocket
In Conflux, each account could have several pockets to store CFX.

balance
staking_balance
storage_collateral
sponsor_balance_for_gas
sponsor_balance_for_collateral

The fromPocket field and toPocket field could be one of them.
Besides these five values, the "pocket" could be two special values "mint_burn" and "gas_payment".

fromPocket = "mint_burn": mint CFX, e.g., generate staking interest
toPocket = "mint_burn": burn CFX, e.g., when a contract is killed, its staking balance will be burnt.
fromPocket = "gas_payment": gas payment, usually equals to gas_price * gas_limit
toPocket = "gas_payment": gas refund after transaction execution.

Reference:
Paragraph of Changes in integrity constraints -> After change
The staking balance/collateral balance/sponsor balance for gas/sponsor balance for collateral increasing (or decreasing) of an address during transaction execution corresponds to an internal_transfer type trace whose "to" (or "from") is this address and "toPocket" (or "fromPocket") is "sponsor_balance"/"storage_collateral"/"sponsor_balance_for_gas"/"sponsor_balance_for_gas".
Comment:
Should the last word sponsor_balance_for_gas be sponsor_balance_for_collateral

Fixed


parallelize temporal inference

Temporal inference is currently single threaded. It is a issue because we are now in the need of more throughput.

Event trace should solve this fine, I just need to add a event bag'ish deriver to the branch


Posterior Predictive Module

Codecov Report

Merging #519 into master will decrease coverage by 2.94%.
The diff coverage is 12.13%.

@@            Coverage Diff             @@
##           master     #519      +/-   ##
==========================================
- Coverage   88.53%   85.59%   -2.95%
==========================================
  Files          35       36       +1
  Lines        4353     4526     +173
==========================================
+ Hits         3854     3874      +20
- Misses        499      652     +153

Impacted Files
Coverage Δ

scvi/inference/__init__.py
100% <100%> (ø)
:arrow_up:

scvi/inference/ppc.py
11.62% <11.62%> (ø)

scvi/inference/autotune.py
75.57% <0%> (-0.22%)
:arrow_down:

Continue to review full report at Codecov.

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

@romain-lopez I made some changes, including keeping everything sparse to reduce memory consumption (need to use a new package called sparse to handle 3-d sparse matrices). I also moved this to a new "folder" called criticism and made it general enough for any posterior predictive samples, so it's a bit scVI agnostic. Finally, I added some testing for it. I still need to add docstrings and examples.
I think this is a good thing to have in our codebase for benchmarking our own models, and could potentially make it easier for others to compare their models to ours. What do you think?

I don't see the coverage running ?

The sparse implementation looks much better to me !

as well as not attaching it to the dic of posterior right away

I don't see the coverage running ?

There was something wrong with the last merge (like 1/3 of travis fails because of autotune) so codecov didn't run properly on master.

tried to restart the build

@adamgayoso are we ready to merge this ? did you add a bit of docstring ?

To merge, we simply need to add a mock edit to trigger codecov

@romain-lopez I haven't had time yet to finish this. Probably need a few more weeks.

@romain-lopez I'm not entirely sure this belongs here. We could move it to the norm jam repo?

I'm fine either way. If we don't have some code explicitly using that I'm indeed not sure it's worth it to maintain it. It's still good code we can archive to the normjam.

@adamgayoso quick thought. Is there a way to use the sample function to perform posterior predictive checks as well as prior predictive checks? Should we add this to a scvi-tools default somehow? (cf. our work at normjam)

if this is too much work, or out of line, we may want to close this PR

Going to close this. I think it's out of scope for now.

Going to close this. I think it's out of scope for now.


SONARMSBRU-12: amended targets file to escape assembly path in UsingTask

LGTM, except for the automatic guessing of the path to assembly from within the .targets file (see my inline comment)


Docs/publish plugin private registry

Hey, I just made a Pull Request!
Hi Team, I have updated document to publish the plugin to the private registry
Screenshot

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

I wonder if it is worth maintaining such a document given that there are a lot of different approaches for publishing packages people could follow. Also, we will end up repeating some node or node package managers instructions as at this point there is nothing Backstage specific.

@vinzscam, I wrote this document in response to feature requirement #24527 since the publish-private was empty. Are there any changes needed to make it specific to Backstage? I'm open to your suggestions 🙂

@vinzscam, I wrote this document in response to feature requirement #24527 since the publish-private was empty. Are there any changes needed to make it specific to Backstage? I'm open to your suggestions 🙂

@vinzscam Need your help here 🙏

@vinzscam, I wrote this document in response to feature requirement #24527 since the publish-private was empty. Are there any changes needed to make it specific to Backstage? I'm open to your suggestions 🙂

@vinzscam Need your help here 🙏

Sorry for the delay in replying, we're are just back from summer vacations...
I'm reopening for feedback from backstage/maintainers 🙂


Add new telemetry providers

Add new telemetry providers for HfEnum, HfAud, BthEnum, AVCTP and AVRCP

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


problem with product counter

Current behavior
when the button is pressed, the counter behaves inappropriately
Expected behavior
item will be added with the correct value
Steps to reproduce the issue

Repository
https://github.com/DivanteLtd/vue-storefront
Can you handle fixing this bug by yourself?

NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Environment details

Browser: chrome
OS: ubuntu 18.04
Node: 10+
Code Version: current

Additional information

It’s been fixed with 1.10 - please recheck

@pkarw demo.vuestorefront.io
this site still has this problem

Sure, the demo is on 1.9.2; https://next.storefrontcloud.io is on 1.10

@pkarw

The debounce has been added to 1.11 (develop branch) - this behavior you showed on the screenshot is a correct one (quite a lot of requests but in the end they're queued so the totals are OK with the cart state) + the Add To Button (showed on the initial screen is being disabled until product land in the cart to prevent race conditions)


Inspector: It should auto-update on system changes

This is awesome. I think we can close it now, right?


handle illegal escape chars in format strings regardless of OS.

Rather than solely replacing the File.separatorChar that is dependent on OS, the plugin should handle invalid escape chars specified directly in the cucumberOutputDir. For example, someone could theoretically specify a full path such as C:\blah\somedir\target\etc in the pom file.
Fixes issue #10

Thanks for the contribution.


⚠ Develop API Endpoint has degraded performance

In 5e568c8, Develop API Endpoint (http://develop.roblox.com/) experienced degraded performance:

HTTP code: 503
Response time: 1091 ms

Resolved: Develop API Endpoint performance has improved in 2e09f77 after 58 minutes.

Resolved: Develop API Endpoint performance has improved in 8487bc9 after 58 minutes.


Prisma cant find a table of a newly generated database.

Bug description
After generating a new database using SQLITE:
npx prisma db push
Prisma cant find the User table. Even though it exists within SQLITE.

What's going on?
PS: It did generate a new prisma client.
How to reproduce

Create new Prisma project with TypeScript and SQLITE
Create a User model with the properties of the image above
Use findFirst or findUnique
See error

Expected behavior
To return the user I was looking for or none.
Prisma information

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "sqlite"
  url      = "file:database2.sqlite"
}

model User {
  id Int @id @default(autoincrement())
  username String @unique
  password String
  image String
  description String
  lists List[]
}

Environment & setup

OS: Windows
Database: SQLite
Node.js version: 16.13.2

Prisma Version
prisma                  : 3.9.1
@prisma/client          : 3.9.1
Current platform        : windows
Query Engine (Node-API) : libquery-engine bcc2ff906db47790ee902e7bbc76d7ffb1893009 (at<EMAIL_ADDRESS>
Migration Engine        : migration-engine-cli bcc2ff906db47790ee902e7bbc76d7ffb1893009 (at<EMAIL_ADDRESS>
Introspection Engine    : introspection-core bcc2ff906db47790ee902e7bbc76d7ffb1893009 (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt bcc2ff906db47790ee902e7bbc76d7ffb1893009 (at<EMAIL_ADDRESS>Default Engines Hash    : bcc2ff906db47790ee902e7bbc76d7ffb1893009
Studio                  : 0.457.0

I can not reproduce this with:

npm init -y && npm install prisma && npx prisma init --datasource-provider sqlite
Add schema:generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "sqlite"
  url      = "file:database2.sqlite"
}

model User {
  id Int @id @default(autoincrement())
  username String @unique
  password String
  image String
  description String
}

npx prisma db push:C:\Users\Jan\Documents\throwaway\11788>npx prisma db push
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Datasource "db": SQLite database "database2.sqlite" at "file:database2.sqlite"

SQLite database database2.sqlite created at file:database2.sqlite

Your database is now in sync with your schema. Done in 73ms

Running generate... (Use --skip-generate to skip the generators)

><EMAIL_ADDRESS>postinstall C:\Users\Jan\Documents\throwaway\11788\node_modules\@prisma\client
> node scripts/postinstall.js

npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>added 2 packages from 1 contributor and audited 4 packages in 4.61s
found 0 vulnerabilities

✔ Generated Prisma Client (3.9.2 | library) to .\node_modules\@prisma\client in 76ms

Create minimal script.js:const { PrismaClient } = require('@prisma/client')

const prisma = new PrismaClient()

async function main() {
  const all = await prisma.user.findMany()
  console.log(`all: `, all)
}

main()
  .catch((e) => {
    console.error(e)
    process.exit(1)
  })
  .finally(async () => {
    await prisma.$disconnect()
  })

node script.js:C:\Users\Jan\Documents\throwaway\11788>node script.js
all:  []

Am I missing something?

Yes, my bad. It was because node_modules was out of sync. I had 2 pairs of node_modules, one outside the /API/schema and one inside. My bad!


Inconsistent display output with 4.9.0-kfd-compute

Hi,
I installed the ROCm 1.5 release today and am experiencing some display issues. Sometimes, the display will come up without issue, other times it will remain black. A few times it came up with only low resolutions available, and I observed the following output while it was starting:
[    3.453722] Raw EDID:
[    3.453724]  	00 ff ff ff ff ff ff 00 ff ff ff ff ff ff ff ff
[    3.453726]  	56 50 9e 26 0d 50 54 21 0b 00 d1 c0 d1 fc 81 c0
[    3.453728]  	0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d 0d
[    3.453730]  	01 01 01 01 01 01 37 8b 80 18 71 38 2d 40 58 2c
[    3.453732]  	45 00 dd 0c 11 00 00 1e 00 00 00 fc 00 4e 58 2d
[    3.453734]  	56 55 45 32 34 0a 20 20 20 20 00 00 00 fd 00 1e
[    3.453735]  	90 a2 a2 24 01 00 20 20 20 20 20 20 00 00 00 ff
[    3.453737]  	00 4e 49 58 32 34 31 35 0a 20 20 20 20 20 01 54
[    3.453740] amdgpu 0000:03:00.0: DP-1: EDID invalid.

There are many nearly identical messages. Swapping DP outputs or to HDMI didn't change anything.
My system configuration is Intel 5820k on an Asrock Extreme 4 x99, with an RX 480 Reference model w/ Ubuntu 16.04, and monitor is Nixeus VUE24. Please tell me if I can supply any other messages/output that can help. I'm not sure this is exactly a ROCm problem, but I don't see this happen when booting Ubuntu's stock kernel or previously ROCm 1.4's kernel. Thanks!

Can you try ROCm 1.6 it released on Thursday here are new install instructions https://rocm.github.io/ROCmInstall.html

Hi,
Thanks for your reply - when I get back to my desktop in about a week, I will do as you suggested and report back. I understand that headless operation is sort of a priority over display stuff, so I appreciate you looking at this anyway.

I tried this on the same machine and the problem persists with about the same message. However, although it occurs with my Nixeus panel no matter what port is used (including DVI->HDMI), using a much older NEC monitor over the RX 480's HDMI port never causes a problem. I'd be happy to provide any other outputs if it would help.

This is the issue in the base Linux AMDGPU driver,  not ROCm stack, they are addressing this with Linux kernel 4.15 and 4.16


updated docker and nginx configuration to support env variables

Resolves #75

I wonder if we should move away from committing docker-compose.yml and make it into another .template file. It's a bit inconvenient to have git clobber the local config every pull. I realize the new one is general purpose, but I'm thinking of laptop deployments where the current compose file might need to be modified beyond what the new generalized one provides, based on various Windows quirks.

I'm trying to reduce installation configuration steps for the Windows deploys, so one change I'm looking at is using internal volume management for the postgres container, which requires an additional build step (which does not require additional configuration) but eliminates the need for the user to create a named volume. I also don't want users to have to manage environment variables. And we'll be running under http on the laptops since they won't be on the internet when the tool is running (just a user's laptop or an internal ship network)

It sounds like we'd be managing to distinct deployment options at that point, so maybe the right answer is to have separate releases for each avenue? We already do a specific release branch for the server (to keep gulp compiled), so we could do two? This one might be better to talk through verbally


OOM error when evaluate detection on lvis minival

Hello, I am facing an out of memory problem when testing with the eval_lvis.py file.
My hardware setup is 8*1080 Ti GPU with pytorch 1.5. I have managed to successfully run the training code with batch size as 1, but when I try to test the detection on lvis performance, there is an out of memory error as following:  line 76 at util/dist.py.
Can you help me with this problem? Thank you in advance.

It is the gpu memory that is running out. The error information is following:

Thank you!

Try setting the env variable "MDETR_CPU_REDUCE" to "1", this should help with memory during reduce

Thank you for the help, can you tell me what size of memory is enough for the evaluation? Also, is there any way to reduce the usage of memory a little bit?
Now I am encountering with the memory error.

I don’t have precise figures, but it could be in the vicinity of 80gb/card of ram required.
If memory is a concern, you could try modifying the code of the LVIS_evalutor to avoid doing an "all_gather" (which is memory costly), but instead have every process dump to disk, then reload from the main process. This is a bit hacky but could help you move forward.

Thank you for the response, I will try the implementation to dump result to disk and gather them from disk. Now, I am concerning about the training time when fine-tuning upon the 100 % lvis dataset, can you tell me the specification you've used, like the amount of gpus, and how long it will probably take to finish the training? Thank you ahead!

It is not work.

set "MDETR_CPU_REDUCE" to "1"  is not work，I find that mdetr will occur the memory not release during the training epoch increasing。

@linhuixiao Hello, have you addressed this issue? During the pre-training phase, after completing the second epoch, an OOM issue arises. Additionally, after finishing the first epoch, there are 4-5 extra processes per card, with each process occupying 500MB of GPU memory.


我的项目是基于sass的，但是7.0.x版本要引入的是less文件，无法与我项目兼容，怎么处理

What problem does this feature solve?
解决项目是基于sass开发的问题
What does the proposed API look like?
"styles": [
"../node_modules/ng-zorro-antd/src/ng-zorro-antd.sass"
],

you can use both less and sass file in angular cli, please read angular cli doc.


Implement a Move Option

Please add a move or cut and paste option to allow moving a file from one container/folder to another.
Currently to do this a user needs to:

Right click file and choose Copy
Traverse to new container
Right click "something" and choose Paste
Traverse back original container
Right click file and choose Delete

If the user makes an error in copy and doesn't realize it, they could then delete the file too.  So this would prevent that too.
Cut-n-Paste flow would be:

Right click file and choose Cut
Traverse to new container
Right click "something" and choose Paste

I understand that from a code aspect, you would would need to do Copy and Delete but from a user aspect you can do that all in step #3.

@tjohnson1010 thanks for the suggestion. Unfortunately, when we've had features like this in the past we've seen users become confused during the operation, or even after it finished (with and without failures), about what has been moved/deleted. Therefore we've chosen to not provide this type of feature, and instead leave it up to the user to perform the steps manually. That way you can verify everything is where you want it before deleting anything.


Preserve base URL host and scheme when requesting next API page

API responses always return next/prev links with https:// since API doesn't know if the request was made internally or through nginx. This means that apps using _iter methods will try to request page=2 from https://..., which doesn't work when accessing the API apache server directly.
To fix this we make _request always use base_url host and scheme.

👍


Implement more Effects

This PR

Implements the remaining effects
Adds a number of examples and improves the existing examples
Improves glue generation with a platform/glue-gen.sh script to capture the key steps
Fixes documentation generation

glue_manual has thousands and thousands of lines. The name makes it sounds like you wrote it manually but I guess not? Do you mean that it is still generated but just generated differently?


Add option to hide/show release notes on update #44020

Addressed feature request #44020

Thanks!


Moving to dtudk organization

Hi!
I am Nick from DCC (@ DTU), and we are governing the https://github.com/dtudk/ namespace.
Your project will be used by all students as they join the DTU introductory courses (math or programming or...).
As such we believe it is important that students has confidence in a package affiliation with the teaching environment they exist in.
At least at the "top level".
I have discussed with Tue and Jakob about moving your repository to the dtudk namespace for consistency.
This will have limited impact.

the project will be hosted on github.com/dtudk/dtumathtools
you will still get access to it as maintainers and should thus be able to do everything you do now.
External collaborators would need approval (from dtudk admins)
external contributions via forks are not impacted.

As such we do not plan to impact, or steal, your work. Only to ensure that students will see the DTU affiliation directly.
If you have any questions, feel free to let me know!

I completely agree. The current model works as long as I am a part of the team ;)
You should then also create a pypi account, so the dtudk team can push new packages. dm me when this is done

The plan is not to expell any current members of the team, if you feel all are necessary.
This is primarily (only) about its location.
If you are the responsible, you will still be the responsible, and hence there shouldn't be any others who can publish to pypi etc.
It would, however, be ideal if you could invite me (username: zeroth) as maintainer/owner. Then both you and me can publish the package. Do note, that I intent to NOT do anything without your consent. I plan to stay in the background and aid only IFF this is required by you or any teacher, as such there shouldn't be any problems related to the pypi upload stuff.
I believe this can be controlled on the pypi site, manage/project/dtumathtools/settings/publishing where one can specify namespace, and package name.
I would then recommend you propose a transfer to the dtudk namespace (and await for my approval).
I'll create a new team on the namespace with all current developers of dtumathtools.
Let me propose that the project name will be all lowercase: "dtumathtools", so it reflects the package name for pip, I believe you can do this when transferring.
Let me know what you think?

I have invited you to a team, once it has been moved, I need to assign the team as maintainers, and then nothing more should be required, access are as they were etc.

As I "don’t have the permission to create public repositories on dtudk", I am unable to do the transfer to dtudk currently. I will do it as soon as I am able to.
For the transfer of the pypi project to dtudk, the organization need to be created first. Do you want to create (and thus be owner of) that?

As I "don’t have the permission to create public repositories on dtudk", I am unable to do the transfer to dtudk currently. I will do it as soon as I am able to.
For the transfer of the pypi project to dtudk, the organization need to be created first. Do you want to create (and thus be owner of) that?

dtudk is already created, so you should be able to do so as soon as you have accepted the dtumathtools invite from dtudk (you should have gotten one?)

Ah, saw you have accepted, so I think it should be ready now?

Do not think that fixed it... Now it simply claims that "dtudk/dtumathtools already exists and You don’t have the permission to create public repositories on dtudk".

Hmm.. I have just checked, it won't work until you are admin in that org, the easiest would be to jest transfer it to me, then I can move it. I have admin rights there.
I'll fix everything tomorrow, if this is ok?
To be on the safe side, you can just have a local copy, I will also have one.

@Chrillebon a gentle ping, do you mind trying to move it to me? zerothi? I'll move it again... That seems like the simplest path.

@Chrillebon thanks! Now done! You should still have access, let me know if there are problems.
I have invited the other two contributors as team members to maintain the package, so far no response.
If anybody needs access, let me know! :)
Thanks!


Typo - Toogle -> Toggle

Under the section titled "Managed Deployment using Intune"  Step 4 has a typo of "toogle" that should be the word "toggle".
[Enter feedback here]

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

ID: bfa69a96-b69c-4175-80b5-b5ca227a7b86
Version Independent ID: be5e50f6-d123-5fe3-5d88-f28f9fc2beb1
Content: Create OMA-DM based VPNv2 Profiles to Windows 10 devices
Content Source: WindowsServerDocs/remote/remote-access/vpn/vpn-create-oma-dm-based-vpnv2-profiles.md
Product: windows-server
Technology: remote
GitHub Login: @Teresa-Motiv
Microsoft Alias: v-tea

Nice catch, thanks. Will fix.

By the way, have you noticed anything else on the page in need of fixing or simply adjusting to look more correct?

All I saw was that typo.  The rest is fine and is in line with all the other articles in that area.  Just figured I would send in a note about the typo.
Matthew Everett  |  Senior Network Technician  |  Global Aerospace Inc.
One Sylvan Way, Parsippany, NJ, 07054
+1<PHONE_NUMBER> (w)  |  +1<PHONE_NUMBER> (m)   |  www.global-aero.com
Follow us on:    LinkedIn https://www.linkedin.com/company/global-aerospace?trk=company_logo   |  Twitter https://twitter.com/GlobalAerospace
Latest News: Get the tools and insights you need for professional development through the SM4 Online Learning Management System - Learn Morehttps://sm4.global-aero.com/community-of-excellence/level-2-lms/
From: Trond B. Krokli<EMAIL_ADDRESS>Sent: Thursday, September 17, 2020 3:17 PM
To: MicrosoftDocs/windowsserverdocs<EMAIL_ADDRESS>Cc: Matthew Everett<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/windowsserverdocs] Typo - Toogle -> Toggle (#4826)
By the way, have you noticed anything else on the page in need of fixing or simply adjusting to look more correct?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windowsserverdocs/issues/4826#issuecomment-694444429, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANAPMPSGKSGVXUYRIOYFHCDSGJOETANCNFSM4RQ3LSUA.

This email (and any attachments) is for the exclusive use of the intended recipient(s) only and may contain legally privileged and/or confidential information that is exempt from disclosure under applicable law. If you have received this email in error, please immediately advise the sender by return email and delete the original and all copies of the email (and any attachments). For further information please visit our website at www.global-aero.comhttp://www.global-aero.com. If the purpose of this email is to deliver an insurance policy or policies, endorsement(s), certificates(s) or other policy related document(s), Please Click Herehttp://www.global-aero.com/wp-content/uploads/2016/11/Electronic-Delivery-of-Policy-Documents-Statement-18Oct2016.pdf to review our Electronic Delivery of Policy Documents statement.

Thank you for the useful feedback and your initial report post.
The issue will be resolved by the Pull Request #4828 , which will also close this ticket automatically.


mark flaky tests as flaky

Description

@jonahwilliams Were these marked flaky because of https://github.com/flutter/flutter/issues/68144?


[BUG] Invalid measuring width for Cambodian text

Description
I am using SkiaSharp for measuring the given text. so I have given the Cambodian text as input but it measuring width is higher than the GDI measuring width. How to get the same GDI measuring width.
Code
           string text = "លិខិតស្ថានភាពពាក្យបណ្តឹង";
            float fontsize = 12;

            //SkiaSharp Measurement
            SKImageInfo info = new SKImageInfo(120, 120);
            float skiaMeasurement = 0;
            using (SKSurface surface = SKSurface.Create(info))
            {
                SKCanvas canvas = surface.Canvas;
                canvas.Clear(SKColors.White);
                using (SKPaint paint = new SKPaint())
                {
                    paint.Typeface = SKTypeface.FromFile(@"C:\Users\MadhanKumarasamy\Downloads\Khmer.ttf");
                    paint.Color = SKColors.Black;
                    paint.IsAntialias = true;
                    paint.TextSize = fontsize;
                    paint.SubpixelText = true;
                    paint.TextAlign = SKTextAlign.Left;
                    paint.TextEncoding = SKTextEncoding.Utf8;
                    SKRect rect = new SKRect();
                    skiaMeasurement = paint.MeasureText(text, ref rect);
                    Console.WriteLine("SKia Width = " + rect.Width);
                }
            }

            //GDI Measurement
            Bitmap bitmap = new Bitmap(540, 720);
            Graphics graphics = Graphics.FromImage(bitmap);
            // Create string to draw.
            String drawString = text;
            graphics.FillRectangle(Brushes.White, new System.Drawing.Rectangle(0, 0, (int)540, (int)720));
            // Create font and brush.
            Font drawFont = new Font("Khmer", fontsize, FontStyle.Regular, GraphicsUnit.Point);
            SolidBrush drawBrush = new SolidBrush(Color.Black);
            StringFormat drawFormat = new StringFormat(StringFormat.GenericTypographic);
            //remove the linelimit flag from create stringformat object.
            //The behavior of the linelimit flag is “only entire lines are laid out in the formatting rectangle”,
            //By default layout continues until the end of the text, or until no more lines are visible as a result of clipping”.
            drawFormat.FormatFlags &= ~StringFormatFlags.LineLimit;
            drawFormat.FormatFlags |= StringFormatFlags.MeasureTrailingSpaces;
            drawFormat.FormatFlags |= StringFormatFlags.NoClip;
            graphics.PageUnit = GraphicsUnit.Point;

            drawFormat.Trimming = StringTrimming.Word;
            // Set format of string.
            float width = graphics.MeasureString(drawString, drawFont, new PointF(0, 0), drawFormat).Width;
            Console.WriteLine("GDI Width = " + width);

Expected Behavior
SKia Width = 145.3125
GDI Width = 145.3125
Actual Behavior
SKia Width = 170.4766
GDI Width = 145.3125
Basic Information

Version with issue:  1.68.1
IDE:  Visual Studio 2017
Platform Target Frameworks: .Net core 2.1

Skia isn't performing any text shaping that is required by many non Latin writing systems. To get the expected result you have to shape the text via HarfBuzzSharp.
@mattleibow What can we do to avoid these reportings?


Blazor CS0154	The property or indexer 'MyComp.Value' cannot be used in this context because it lacks the get accessor

I started getting this error:
Blazor CS0154	The property or indexer 'MyComp.Value' cannot be used in this context because it lacks the get accessor
in VS2022 recently in my "Error List" window when using blazor component which I've created without get; for the Parameter
The solution builds successfully and runs.
I see these errors only when the .razor file using these components is opened.
These errors also don't appear in the output window.
Steps To Reproduce
Have a blazor component with a parameter without get;
    [Parameter]
    public object Value { set { ... } }

use this component in a .razor file, open that file, look in VS "error list" window
<MyComp bind-Value="Prop1" />

.NET Version
7

@omuleanu can it be that you are running against the last successful build?
I believe we have never supported set only parameters

Thanks for reporting, this is my fault :)
At design time we generate some extra code to allow Go To Definition, hover, etc work nicely in the attribute name, but seems I forgot to account for write-only properties. That's why it doesn't affect build.

@javiercn .net 7, VS 17.5.3
get is never used anyway because the value is sent back using ValueChanged.InvokeAsync so I wrote only the set


Support Tar metaidx for EROFS

What this PR does / why we need it:
So that turboOCI-apply --import can be used.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Please check the following list:

[ ]  Does the affected code have corresponding tests, e.g. unit test, E2E test?
[ ]  Does this change require a documentation update?
[ ]  Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ]  Do all new files have an appropriate license header?

This also closes https://github.com/containerd/overlaybd/issues/337

LGTM


SleepSession/Sleep: Inconsistent record name between requestPermission and getGrantedPermissions

I found an inconsistency between requesting sleep permission where the record name is SleepSession but when checking for granted permissions the record name is Sleep

It seems like this inconsistency comes from the health connect core. I will try to investigate this.

Duplicate of https://github.com/matinzd/react-native-health-connect/issues/63.


Transparent proxy on Linux for local originating traffic

I struggled with getting this working and found a few posts around the internet from people with the same issue. The macOS section talks about this so I've just "ported" that to the linux world.
Thanks for the fantastic tool BTW :tada:

Thanks! 👍 🎉


Examples: host the builds somewhere for demo

It would be useful for trying things out in the browser quickly to newcomers if we host our examples somewhere.

This will be obsolete after doing #291


acme.challenges.DNS01 does not exist

Hi, I'm running into the following issue:
Traceback (most recent call last):
  File "letsencrypt-aws.py", line 521, in <module>
    cli()
  File "/home/ubuntu/le-aws/local/lib/python2.7/site-packages/click/core.py", line 716, in __call__
    return self.main(*args, **kwargs)
  File "/home/ubuntu/le-aws/local/lib/python2.7/site-packages/click/core.py", line 696, in main
    rv = self.invoke(ctx)
  File "/home/ubuntu/le-aws/local/lib/python2.7/site-packages/click/core.py", line 1060, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/ubuntu/le-aws/local/lib/python2.7/site-packages/click/core.py", line 889, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/ubuntu/le-aws/local/lib/python2.7/site-packages/click/core.py", line 534, in invoke
    return callback(*args, **kwargs)
  File "letsencrypt-aws.py", line 477, in update_certificates
    force_issue, domains
  File "letsencrypt-aws.py", line 383, in update_elbs
    domain.get("key_type", "rsa")
  File "letsencrypt-aws.py", line 335, in update_elb
    logger, acme_client, elb_client, route53_client, elb_name, host
  File "letsencrypt-aws.py", line 199, in start_dns_challenge
    [dns_challenge] = find_dns_challenge(authz)
  File "letsencrypt-aws.py", line 83, in find_dns_challenge
    isinstance(combo[0].chall, acme.challenges.DNS01)
AttributeError: 'module' object has no attribute 'DNS01'

When I print dir(acme.challenges) I get:
['Challenge', 'ChallengeResponse', 'ContinuityChallenge', 'DNS', 'DNSResponse', 'DVChallenge', 'HTTP01', 'HTTP01Response', 'KeyAuthorizationChallenge', 'KeyAuthorizationChallengeResponse', 'OpenSSL', 'ProofOfPossession', 'ProofOfPossessionResponse', 'RecoveryContact', 'RecoveryContactResponse', 'TLSSNI01', 'TLSSNI01Response', 'UnrecognizedChallenge', '_TokenDVChallenge', '__builtins__', '__doc__', '__file__', '__name__', '__package__', 'abc', 'crypto_util', 'errors', 'fields', 'functools', 'hashes', 'hashlib', 'jose', 'logger', 'logging', 'other', 'requests', 'socket']

I have run pip install -r requirements.txt
My acme version is: 0.5.0.dev0
Not sure if I'm doing something egregiously wrong, any help would be appreciated. Let me know if you need more information about my configuration.

Did you install another version of acme somehow? This looks like what would happen if you installed acme from master instead of from the branch we use. What version of pip are you using?

Ah, I was using pip 1.5 because I created a new virtualenv. I'll upgrade to 8.0.2 and see if I can fix my problem, thanks alex!

(Unless I hear otherwise closing this)

@alantliang Hi , how did you solve the problem about the "AttributeError: 'module' object has no attribute 'DNS01'"?
I get the same problem


[Suggestion] BenchmarkDotNet.Analyzers.IAnalyser - use same spelling for namespace and type?

Hi!
The IAnalyser interface belongs to BenchmarkDotNet.Analyzers namespace. The first one uses British English spelling, and the second one - American English.
There can be only one, I think:)

thanks for the suggestion!


Update Spleen Bundle to enable deterministic training

Fixes # .
Description
This PR is contributed by @heyufan1995 and is used to update the bundle training results.
Status
Read
Please ensure all the checkboxes:

[x] Codeformat tests passed locally by running ./runtests.sh --codeformat.
[ ] In-line docstrings updated.
[ ] Update version and changelog in metadata.json if changing an existing bundle.
[ ] Please ensure the naming rules in config files meet our requirements (please refer to: CONTRIBUTING.md).
[ ] Ensure versions of packages such as monai, pytorch and numpy are correct in metadata.json.
[ ] Descriptions should be consistent with the content, such as eval_metrics of the provided weights and TorchScript modules.
[ ] Files larger than 25MB are excluded and replaced by providing download links in large_file.yml.
[ ] Avoid using path that contains personal information within config files (such as use /home/your_name/ for "bundle_root").

/build


Add shape utility method to Spec to get a scan's simplified shape

Add Spec.shape() method which gives the the number of dimensions in the scan in the simplest possible view
Add tests for shape method

Issue for mypy problems: https://github.com/dls-controls/scanspec/issues/82


Fixes #301

Adds apache commons-lang3 to the project.

Did you test this? I'm pretty sure you will need to shade it in the jar too, but I may be wrong.

@twizmwazin Not yet, I'll do it now

@twizmwazin Yes I did have to add it to the shade. Don't use maven to much so I'm not familiar with this sort of stuff.


Sync to "upstream/master" to fix (golang.org/x/net) CVE-2023-39325/CVE-2023-3978

What type of PR is this?

What this PR does / why we need it:
Sync's to "upstream/master" to fix (golang.org/x/net) CVE-2023-39325/CVE-2023-3978
Which issue(s) this PR fixes:

Fixes #
CVE-2023-39325/CVE-2023-3978
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

69 of 79 (87.34%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 78.881%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/blob/controllerserver.go
24
25
96.0%

pkg/blob/blob.go
28
31
90.32%

pkg/blob/nodeserver.go
17
23
73.91%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
2058

Relevant Lines:
2609

💛  - Coveralls


Clarify that TerminateProcess is not "asynchronous" when the process terminates itself.

@BillyONeal : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@BillyONeal : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

#sign-off


Option to disable all light themes

Scenario
Often time developers switch themes using the extremely handy CTRL + `  shortcut.

Problem
However, when going through the list of themes (with instant preview in the background), the user inevitably has to go through some light themes during the navigation. This literally hurts the eyes.
It's possible to uninstall 3rd party light themes, but the default light themes remain.
Suggestion
It would be preferable to have an option to disable all light themes using cmd + shift + p.
That was I don't have to uninstall my light themes, but at night, I can have the option to not get flashed by my editor

Another option would be to split themes:

Ayu Light
Light (Visual Studio)
Solarized Light
-----------------------
Ayu Dark
Dark (Visual Studio)
Solarized Dark

Alphabetic sort should persist, but now in groups.

@usernamehw That'd work to. As long the user doesn't have to go bear a flash while switching themes, it would definitely solve the issue.


chore(master): release 0.37.0

:robot: I have created a release beep boop
0.37.0 (2024-03-26)
Features

upgrade to bee 2 (#412) (1759c96)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ethersphere/swarm-desktop/releases/tag/untagged-e25407e7602d395c971f :sunflower:


Facebook Messenger Doesn't Work

I can log into messenger no problem, but all my conversation icons are greyed out and can't send messages.
Using latest Ferdi on Mac OS, and the problem should be something obvious to a dev because the console is logging errors:
GET https://www.messenger.com/rsrc.php/v3/yD/r/rlA4pw-3d_K.png 404
ErrorUtils caught an error:
Client disconnected

WebSocket connection to 'wss://edge-chat.messenger.com/chat?region=lla&sid=8371693053542399&cid=41305cd6-bd4b-444f-810f-18a93d017933' failed: Error during WebSocket handshake: Unexpected response code: 503

I know Franz has been having an issue for a few days where messenger shows the entirety of Facebook so I'm wondering if the Facebook Overlords™ have elected to block apps like this, forcing us to use their app?
UPDATE: I appear to  be getting the same websocket error even on facebook.com in a browser, so perhaps the whole system is janked?

+1

There seems to be an ongoing major outage at Facebook: https://developers.facebook.com/status/dashboard/


reverse of number in c++

Why:

Closes #ISSUE_NUMBER
What's being changed:
added the code for reversing a number in c++

👋🏻 Hey @palak-k5
💖 Thanks for opening this pull request 💖
This PR will be reviewed and merged shortly.

what does this mean may i know

i am a newbie  ,i did it by mistake

The issue is assigned to someone else. Please look for other issues to contribute. Make sure you type !assign to grab the issue
Thank you!


New traveling merchant item

A new item was added to the traveling merchant rotations this week, this has broken the first 2 slots on the merchants 'Current Stock'.
https://runescape.wiki/w/Horn_of_honour

Thank you very much, I was trying to get this worked out as well. Sorry I didn't see your PR earlier, I'll figure out why I didn't get an email.


Don’t unnecessarily invalidate the module map

Additional imports in PureScript sources (compared to their JavaScript output) shouldn’t always invalidate the module map because imports of types are erased and re-exports are followed.
Also Prim.* modules are internal to the compiler and won’t ever be present in the module map.
Fix https://github.com/ethul/purs-loader/issues/123.

Thanks for this PR. I will take a look soon.

The last commit makes bundles made by webpack without purs bundle noticeably smaller 🎉

Great! Thanks for working on this. Is this good to go?

Yes it is!

Thanks!


Grant Log access to customers

User Story

As a customer I want to be able to access logs stored in Loki via Grafana Explore feature

This should be doable via the viewers_can_edit setting, see https://grafana.com/docs/grafana/latest/administration/user-management/manage-dashboard-permissions/#enable-viewers-to-edit-but-not-save-dashboards-and-use-explore

Would be nice for metrics as well, as some customers would probably like to explore metrics too.

I think this feature would enable access for both metrics and logs.

Testing current behaviour on gauss:

logging as "customer" on grafana

I don't see private dashboards

I have no "explore" feature.

That's all expected. Now let's try changing this!

done ✅


Fix project and editor data paths not being opened correctly on macOS

This closes #21904. Testers on macOS are welcome, as I am not currently able to test this.

Thanks!


When releasing a new breaking version of a package, could we start with a beta tag instead of latest ?

At the moment, when releasing on the package manager a new breaking version it automatically goes to latest tag.
I was wondering if we could, when the situations call for it, first use an intermediary tag to further test implementations in other repos.
For exemple, how angular-instantsearch has handled it: https://classic.yarnpkg.com/en/package/angular-instantsearch

I think this will be a good approach after v1 for every minor, but not for patches and fixes, so I wouldn't introduce this just now, but later I would really like it! :)

Yes, this is a good idea, once we will release stable versions of our integrations. For the moment, it's too much I think 🙂

Oke! I understand your point of view. Sometimes I'm a bit afraid that my packages wont work with another project (which should not happen with the tests of course). But with a beta tag I could try them out without having to npm pack everywhere.
Nonetheless, it would make more sense after v1


Separate bongocat keymap

I was really happy to find your bongocat animation, and admittedly don't use the pimoroni. Would you be open to separating out an updated keymap of the bongocat with via support? I've been trying to modify it for myself but keep running into quirks. Making the original VIA-compatible has suddenly lost me right encoder functionality, and trying to port the animation over to the current VIA keymap has broken the animation.

@kimisgold I've made a separate branch without the Pimoroni trackball but with VIA and bongo cat added. https://github.com/foureight84/qmk_firmware/tree/sofle_foureight84_bongo_no_trackball
Give it a try and let me know how it works out

Thank you so much! It works great, and I really appreciate your quick response.

@kimisgold you're welcome