The error ocurred when I run dcnv3/tests/test_dcnv3_module.py and test_grad.py

The error occurred when I run dcnv3/tests/test_dcnv3_module.py
#####################################################
DCNv3(
(dw_conv): Sequential(
(0): Conv2d(4, 4, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), groups=4)
(1): Sequential(
(0): to_channels_last()
(1): LayerNorm((4,), eps=1e-06, elementwise_affine=True)
)
(2): GELU(approximate='none')
)
(offset): Linear(in_features=4, out_features=36, bias=True)
(mask): Linear(in_features=4, out_features=18, bias=True)
(input_proj): Linear(in_features=4, out_features=4, bias=True)
(output_proj): Linear(in_features=4, out_features=4, bias=True)
)
Traceback (most recent call last):
File "D:\project(yolo)\dcnv3\tests\test_dcnv3_module.py", line 17, in
test_dcnv3_module()
File "D:\project(yolo)\dcnv3\tests\test_dcnv3_module.py", line 12, in test_dcnv3_module
output = m(x)
File "D:\anaconda3\envs\yolo\Lib\site-packages\torch\nn\modules\module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "D:\anaconda3\envs\yolo\Lib\site-packages\torch\nn\modules\module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "D:\anaconda3\envs\yolo\Lib\site-packages\dcnv3\ops_dcnv3.py", line 214, in forward
x = self.output_proj(x)
File "D:\anaconda3\envs\yolo\Lib\site-packages\torch\nn\modules\module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "D:\anaconda3\envs\yolo\Lib\site-packages\torch\nn\modules\module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "D:\anaconda3\envs\yolo\Lib\site-packages\torch\nn\modules\linear.py", line 114, in forward
return F.linear(input, self.weight, self.bias)
TypeError: linear(): argument 'input' (position 1) must be Tensor, not NoneType
############################################################
Input is NoneType? Why?
The error ocurred when I run dcnv3/tests/test_grad.py
###############################################################
Traceback (most recent call last):
File "D:\project(yolo)\dcnv3\tests\test_grad.py", line 61, in
test_dcnv3()
File "D:\project(yolo)\dcnv3\tests\test_grad.py", line 40, in test_dcnv3
c_output.sum().backward()
AttributeError: 'NoneType' object has no attribute 'sum'
#####################################################
Original code below:
c_output = dcnv3.ops.dcnv3(input, offset, mask,
                           kernel_h, kernel_w,
                           stride_h, stride_w,
                           pad_h, pad_w,
                           dilation_h, dilation_w,
                           group, group_channels,
                           offset_scale,
                           im2col_step,
                           remove_center)
c_output.sum().backward()

c_output is Nonetype? Why?

Sorry, I forgot this repo is mine and almost ignored GitHub's notification 😂.
Honestly, I don't know what could possibly go wrong as it still works on my machine. Did you install the TestPyPI wheel or compile from source? Note that the TestPyPI wheel only works if your configuration matches that of the GitHub Action server where I built them. Even if you installed from source, there are a lot of possibilities.
I just updated the TestPyPI wheel to make it compatible with torch>=2.1.0 and Cuda 12.1 (previously it could run on 1.9.0<=torch<=2.0.1 and Cuda 11.8). When you run the script again if you see this error, then you need to recompile from source:
Detected that PyTorch and Extension were compiled with different CUDA versions. PyTorch has CUDA Version={t_major}.{t_minor} and Extension has CUDA Version={ext_major}.{ext_minor}. Please reinstall the Extension that matches your PyTorch install.


fix bug on TRA dataset

solve issue "qrun TRA model error (#1062)"
This is my first contrib here. I'd appreciate your help if there is anything wrong:)

Description

Motivation and Context

How Has This Been Tested?

[ ] Pass the test by running: pytest qlib/tests/test_all_pipeline.py under upper directory of qlib.
[ ] If you are adding a new feature, test on your own test scripts.

Screenshots of Test Results (if appropriate):

Pipeline test:
Your own tests:

Types of changes

[X] Fix bugs
[ ] Add new feature
[ ] Update documentation

Please merge the main branch to run the new version of CI. Thanks

It looks great!
Thanks for your contribution.
Welcome to become one of Qlib's contributors.


⚠ Bofrost.lu has degraded performance

In c3aba10, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1221 ms

Resolved: Bofrost.lu performance has improved in 291cb01 after 13 minutes.


Duplicating the particles in memory

All the codes currently create a duplicate data-set for the particles (inside each cell). This can probably be avoided by creating another temporary index for the particles that contains the cell-id, and then sorting the particles on cell-id (and freeing the temporary index). Probably will lead to better cache-behaviour as well.
The fix requires implementing a new cellarray struct that keeps track of the start/end locations for particles per cell. Then a new gridlink has to be coded up to assign the temporary index, sort the particles based on the index (using SGLIB to simultaneously sort the X/Y/Z arrays) and then another loop to find the start and end indices for particles in a cell.
cellstruct should probably contain just the start and end indices - just need to be careful about off-by one errors in the for loops inside the relevant countpairs_* functions.

My tests on wp (on my laptop) show a slight slowdown with this new cellstruct !
Need to test on a real server with larger cache + nthreads.

Implemented for xi_theory/wp in the v2.0 branch with commit f03ad6bc735ffe034e15d280bc6359bef641d9be. valgrind reports no errors and the tests pass.
Since this non-duplicated memory implementation turns out to be slighlty slower, I might not pull this fix into the other codes. Might be worth implementing for the mocks.


BUGFIX: Send reminders on behalf of direct reports

Previously, attempting to send a reminder on behalf of a direct report would result in a forbidden response, which appears to be the logged out page, although the user wasn't actually logged out.
I'm not entirely happy with the implementation, especially in _send_reminder.html.erb and line 11 of reminders_controller.rb. A cleaner solution probably requires an object that can be routed, so that we can say form_for [@subject, reminder].compact. However, in the interests of fixing the immediate problem, this helps.

I think the Travis failure is bogus.


Feat/simplefoc

PR Checklist
1- PR Comments
DONT FORGET TO ADD THE IMAGES

WARNING : Do not edit the checklist below.

2- Developer section

[ ] [Documentation] is up to date with new feature
[ ] [Tests] are passed OK (Non regression, new features & bug fixes)
[ ] [Code Quality] Remind to check if :

Each function has a header (description, inputs, outputs)
Code is commented (particularly in hard to understand areas)
There are no new warnings that can be corrected
Commits policy is respected (constitancy commits, clear commits comments)

3- QA section

[ ] [Review] tests for new features have been reviewed
[ ] [Changelog] is up-to-date with expected tags
🆕 Feature: [Feature] Description...
🆕 Added: [Feature] Description...
🆕 Changed: [Feature] Description...
🛠 Fix: [Feature] Description...

PR to be closed :
It's already done in PR #342


Default values of the integration integer variable is not extracting with scaffold

Default values of the integration integer variable is not extracting with scaffold from Dev environments.
Defined Integer values as below in Dev environment but with scaffold default value of integer datatype is empty but if I download from Dev environment manual, integer value is as expected.
Defined in Dev env:

Screenshot from scaffold output:

with manual extracted src file, even integration deploy also reflecting as empty in higher environments.

Fixed and Released in v0.74.2

Thanks @ssvaidyanathan  and @srinandan


WIP: Add scheme, host, and port to #req{}

@tsloughter et al., what exactly do you need here?

N.B. These changes break backward compatibility for elli_http:parse_path/1. Should we bump to 3.1.2 then to follow semver?

To 3.0.0, I guess so.

why was this closed?

Because I ran git flow feature finish scheme-host-port locally. It’s merged into develop and the release/3.0.0 branch is ready to go unless someone wants to add someone else.

Closed #28.


Create Physical Backed Token Module

I agree.
@moco-bunzz you need to write test script.
Please check https://lastrust.notion.site/Checklist-for-coding-reviewing-phase-d8c89b8eee0f4656ba4719488d9fbbfa

Hi @moco-bunzz, thank you for assigning me.
Priority-wise, preparing the audit report is not the first task according to the discussion with GK and Shota.
Now I'm focusing on the improvement of documentation and code quality.
I'd love to review from that point of view.


[Fuji] Skip running test on Jenkins DATABASE=redis axis

Because integration-test jenkins jobs has been changed to use Matrix project type in edgexfoundry/ci-management#581, the jobs for fuji branch is running test twice with Mongo DB. The DATABASE=redis axis should skip the test and make a build as successful.

closed by #418


Baseline troubleshooting guide

Overview/Summary
Replace this with a brief description of what this Pull Request fixes, changes, etc.
This PR fixes/adds/changes/removes

Adds baseline troubleshooting guide

Breaking Changes

Replace me
Replace me

Testing Evidence
Replace this with any testing evidence to show that your Pull Request works/fixes as described and planned (include screenshots, if appropriate).
As part of this Pull Request I have

[ ] Read the Contribution Guide and ensured this PR is compliant with the guide
[ ] Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
[ ] Checked for duplicate Pull Requests
[ ] Associated it with relevant GitHub Issues
[ ] (AVD LZA Team Only) Associated it with relevant ADO Items
[ ] Ensured my code/branch is up-to-date with the latest changes in the main branch
[ ] Performed testing and provided evidence.
[ ] Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Docs etc.)

@moisesjgomez thanks for your contribution.


Fixed the aliyun-secret-manager-client SDK version

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


rosetta-cli check with --lookup-balance-block=false doesn't find reconciliation errors unless --interesting-accounts is given

Describe the bug
In testing of a Rosetta implementation on a blockchain that should contain reconciliation errors, the check command fails to find the errors unless --interesting-accounts is used. This seems to be caused by the reconciliation checks becoming overly delayed so as to never happen.
To Reproduce
Run rosetta-cli check --lookup-balance-by-block=false --interesting-accounts interesting.json and watch it find reconciliation errors.
Run rosetta-cli check --lookup-balance-by-block=false and let it spin forever and never find any reconciliation problems.
Expected behavior
I expect the same errors to be found, though perhaps in different amounts of time.

Thanks for posting this issue @metajack! You found a very annoying bug that only affects check when --lookup-balance-by-block=false.
This issue can occur if an account (in this case, ones that have reconciliation issues) are skipped while check is catching up to tip and never show up in blocks again.
When accounts are skipped, they are not added to the inactive reconciliation queue: https://github.com/coinbase/rosetta-sdk-go/blob/6fcf086bc01df22380c3809332641cb870683d9b/reconciler/reconciler.go#L446-L456


Problema CORS

Hello, i am trying get data to a server with other port diferent to admin-on-rest. But when I try the console browser show a error of Fetch Cors 8080

Your API servers need to manage CORS by exposing Access-Control-Allow-Origin HTTP Header on each response.
Here is an explainer/tutorial.

Sure, it is.
All the moderns browsers doesn't allow to do HTTP requests other than GET if the client host is different from the requested server.
It is the serve's role to define which host is allowed to request it.

Thanks for the support. Right now I am reviewing my API server.
For the moment, I attached the error console browser.
2016-11-04 7:35 GMT-06:00 Kmaschta<EMAIL_ADDRESS>
Sure, it is.
All the moderns browsers doesn't allow to do HTTP requests other than GET
if the client host is different from the requested server.
It is the serve's role to define which host is allowed to request it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/marmelab/admin-on-rest/issues/126#issuecomment-258432191,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD7W_6OBzDtYw5oKl3vb8gs7h6rO2uR4ks5q6zSLgaJpZM4Kpe6l
.

--
"El secreto del éxito no lo conozco, pero el del fracaso es tratar de
agradarle a los demas"

The problem persist. I added the server API
// CORS (Cross-Origin Resource Sharing) headers to support Cross-site

HTTP requests
app.all('', (req, res, next) => {
res.header("Access-Control-Allow-Origin", "");
res.header("Access-Control-Allow-Methods",
"GET,HEAD,OPTIONS,POST,PUT");
res.header("Access-Control-Allow-Headers", "Origin,
X-Requested-With, Content-Type, Accept, Authorization");
next();
});

In the admin I have:
<Admin restClient={simpleRestClient('http://localhost:5000')}
title="Example Admin">

,
document.getElementById('root')
);
Error console
fetch-mock.js:284 unmatched call to http://localhost:5000/todos
Fetch API cannot load http://localhost:5000/todos. Response to preflight
request doesn't pass access control check: A wildcard '*' cannot be used in
the 'Access-Control-Allow-Origin' header when the credentials flag is true.
Origin 'http://localhost:8080' is therefore not allowed access.
failure.js:18 TypeError: Failed to fetch
2016-11-04 8:19 GMT-06:00 Gerardo Lopez<EMAIL_ADDRESS>
Thanks for the support. Right now I am reviewing my API server.
For the moment, I attached the error console browser.
2016-11-04 7:35 GMT-06:00 Kmaschta<EMAIL_ADDRESS>
Sure, it is.
All the moderns browsers doesn't allow to do HTTP requests other than GET
if the client host is different from the requested server.
It is the serve's role to define which host is allowed to request it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/marmelab/admin-on-rest/issues/126#issuecomment-258432191,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD7W_6OBzDtYw5oKl3vb8gs7h6rO2uR4ks5q6zSLgaJpZM4Kpe6l
.

--
"El secreto del éxito no lo conozco, pero el del fracaso es tratar de
agradarle a los demas"

--
"El secreto del éxito no lo conozco, pero el del fracaso es tratar de
agradarle a los demas"

The error message seems pretty self explanatory. Try to restrict the Access-Control-Allow-Origin header to the actual locations you're issuing the request from.
Note that if both the admin and the API are hosted on localhost, you shouldn't have any CORS problem.


[BUG] High memory usage on first GPU, despite perfectly-balanced stages in pipeline

Describe the bug
When using pipelining (with or without LayerSpec inside PipelineModule), the first GPU seems to have a considerably higher memory consumption, compared to the other ones. This is even visible on perfectly balanced ML models (like the model i attach below)
To Reproduce

extract the train loop in train.py, the ML model and dataset in benchmark.py, and the ds config in ds_config.json, all zipped inside code.zip

this is a model of 2048 very-simple perfectly-balanced linear layers;

run deepspeed --num_gpus=8 train.py --deepspeed --deepspeed_config ds_config.json --pipeline_num_stages 8 --pipeline_spec_layers

this runs the memory efficient (with SpecLayer) pipeline implementation. Remove --pipeline_spec_layers to run the non-SpecLayer implementation, and this issue is still visible;
launch with --pipeline_num_stages X to define number of stages X $\in [2, 4, 8]$. The issue is still visible;

confirm that stages are memory-balanced:

[2023-10-09 10:57:02,180] [INFO] [engine.py:151:__init__] RANK=3 STAGE=3 LAYERS=512 [1536, 2048) STAGE_PARAMS=16842752 (16.843M)
[2023-10-09 10:57:02,180] [INFO] [engine.py:151:__init__] RANK=6 STAGE=6 LAYERS=512 [3072, 3584) STAGE_PARAMS=16842752 (16.843M)
[2023-10-09 10:57:02,180] [INFO] [engine.py:151:__init__] RANK=0 STAGE=0 LAYERS=512 [0, 512) STAGE_PARAMS=16842752 (16.843M)
[2023-10-09 10:57:02,180] [INFO] [engine.py:151:__init__] RANK=1 STAGE=1 LAYERS=512 [512, 1024) STAGE_PARAMS=16842752 (16.843M)
[2023-10-09 10:57:02,180] [INFO] [engine.py:151:__init__] RANK=2 STAGE=2 LAYERS=512 [1024, 1536) STAGE_PARAMS=16842752 (16.843M)
[2023-10-09 10:57:02,180] [INFO] [engine.py:151:__init__] RANK=5 STAGE=5 LAYERS=512 [2560, 3072) STAGE_PARAMS=16842752 (16.843M)
[2023-10-09 10:57:02,180] [INFO] [engine.py:151:__init__] RANK=4 STAGE=4 LAYERS=512 [2048, 2560) STAGE_PARAMS=16842752 (16.843M)
[2023-10-09 10:57:02,180] [INFO] [engine.py:151:__init__] RANK=7 STAGE=7 LAYERS=512 [3584, 4096) STAGE_PARAMS=16842752 (16.843M)

on a different terminal, run watch nvidia-smi and check the memory usage across GPUs when you start training.

Expected behaviour
Running nvidia-smi should output the memory usage values. A big difference between GPU 0 and the others should be visible:

ds_report output
[2023-10-09 10:53:47,040] [INFO] [real_accelerator.py:158:get_accelerator] Setting ds_accelerator to cuda (auto detect)
--------------------------------------------------
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
async_io ............... [NO] ....... [OKAY]
fused_adam ............. [NO] ....... [OKAY]
cpu_adam ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
random_ltd ............. [NO] ....... [OKAY]
 [WARNING]  sparse_attn requires a torch version >= 1.5 and < 2.0 but detected 2.0
 [WARNING]  using untested triton version (2.0.0), only 1.0.0 is known to be compatible
sparse_attn ............ [NO] ....... [NO]
spatial_inference ...... [NO] ....... [OKAY]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
 [WARNING]  NVIDIA Inference is only supported on Pascal and newer architectures
transformer_inference .. [NO] ....... [NO]
--------------------------------------------------
DeepSpeed general environment info:
torch install path ............... ['~/.local/lib/python3.10/site-packages/torch']
torch version .................... 2.0.1+cu117
deepspeed install path ........... ['~/.local/lib/python3.10/site-packages/deepspeed']
deepspeed info ................... 0.10.3, unknown, unknown
torch cuda version ............... 11.7
torch hip version ................ None
nvcc version ..................... 12.2
deepspeed wheel compiled w. ...... torch 2.0, cuda 11.8
shared memory (/dev/shm) size .... 125.89 GB

System info:

Ubuntu 20.04.6 LTS
deepspeed=0.10.3, torch==2.0.1 and torch.version.cuda==11.7
1 single compute node, with 8x NVIDIA GeForce GTX TITAN X.

I have the same issue here, is there any solution for it?

Same issue here, any solutions now? :)


Can you package current git codes to marven?

Hi,dev:
Can you public to current git codes to marven, I need to use it in jdk 1.8.
Thanks.:)
With Best Regards,
jingtao.

Done as part of release 2.3.

I am sorry but I can't find jparsec 2.3 in maven:
https://repo1.maven.org/maven2/jparsec/jparsec/
Did I missed something?

It seems I forgot to release from staging... Will do that.


cmd/cgo: add support for pre-compiled cgo packages

This is the GitHub issue for my half-baked proposal posted on golang-dev.
Inspired by https://github.com/golang/go/issues/35721#issuecomment-556427116
and my own desire for easily cross-compiling Gio programs, I wonder whether it is
feasable to re-use cgo processing through pre-generation of the cgo tool output.
Packages that import "C" require quite a lot of support software:
a native toolchain, development libraries, headers. Invoking the host compiler
is also slow. For example, cross-compiling Cgo programs for macOS and iOS is particularly
difficult (and perhaps legally impossible), and cross-compiling for Android requires
a ~700MB NDK.
On the other hand, it's not always possible to avoid C dependencies: Gio uses
system libraries that are impossible to implement in Go.
One option is .syso files (https://github.com/golang/go/wiki/GcToolchainTricks),
pre-compiled native code that the Go linker knows how to link in. However .syso
files are too low level: they can't link to shared (system) libraries and there is no
Go<->C bridging for making calls across the language barrier safe.
So I wonder: can you imagine a Goldilocks option where a package can have access
all Cgo features through pre-generated cgo files? It's similar to the old binary-only package
feature, but only for the Cgo parts. I hope that C's much more stable ABI makes a pre-generated
cgo file format viable than pre-built Go binary packages.
I wouldn't mind if the hypothetical cgo file format changes once in a while, say every Go
release, as long as I could supply multiple files covering the Go releases I support. If none
of the pre-generated files are usable, the Go toolchain falls back to just running cgo processing.
As a strawman, I suggest a way to invoke
$ go tool cgo build <package>

which then outputs, say, <package_go115>.cgo. If  is later built, possibly on a different
machine, the Go toolchain will look for *.cgo files in the package directory and use one of them
if possible, skipping cgo processing altogether.
Advantages
With pre-compiled Cgo the building process is faster, and I can avoid having the headers and development libraries available for my target platform, needing only a native toolchain for external linking.
What's really interesting is then adding support for -linkmode=internal when Cgo is used, alleviating the need for a native toolchain completely. This is https://github.com/golang/go/issues/38918.
In other words, pre-generated cgo could give Cgo programs some of the nice cross-platform properties of pure Go programs.

This is exactly what I wanted to do ad-hoc for SQLite, would love to see it!
https://twitter.com/FiloSottile/status/1245831899290820608
I think there wouldn't even be any need for new .cgo file types, it should be possible to just generate .go and .syso files that build with the current toolchain. It might even be relatively stable: the ABI is fixed, so the only unstable internal is asmcgocall.
This actually means it could be a fully external tool, at least for prototyping. Indeed, the thing that needs toolchain support is #38918, which is where things get interesting.

@FiloSottile I had your SQLite and x509 work in mind when filing this proposal :) Perhaps you'd like to join the next golang-tools call May 13th for further discussion?

I think there wouldn't even be any need for new .cgo file types, it should be possible to just generate .go and .syso files that build with the current toolchain. It might even be relatively stable: the ABI is fixed, so the only unstable internal is asmcgocall.
This actually means it could be a fully external tool, at least for prototyping.

Indeed. What I'd like to achieve first is some indication that work towards pre-generation may end up in the main repository. I don't fancy maintaining an out-of-tree tool.

I don't really understand how to do this in general.
cgo packages can and do refer to external libraries; presumably we would have to find all of those external libraries and make them available somewhere.  But the libraries are going to vary a lot.  How do we find them and where do we put them?
Some of those libraries are written in C++.  C++ code requires extra work from the linker to support things like global constructors and destructors and exception handling.  If we can't invoke the external linker, we have to implement all of that code in cmd/link, and we have to maintain it as C++ changes.
Maybe I'm missing something, but while I can see how this could work in the simplest cases, I don't see how it could work in general.

I don't really understand how to do this in general.
cgo packages can and do refer to external libraries; presumably we would have to find all of those external libraries and make them available somewhere. But the libraries are going to vary a lot. How do we find them and where do we put them?

Can we ask the native toolchain while pre-pregenerating, in a similar way Cgo currently asks the toolchain about the structure of native types, functions etc.?

Some of those libraries are written in C++. C++ code requires extra work from the linker to support things like global constructors and destructors and exception handling. If we can't invoke the external linker, we have to implement all of that code in cmd/link, and we have to maintain it as C++ changes.
Maybe I'm missing something, but while I can see how this could work in the simplest cases, I don't see how it could work in general.

My use-case is system libraries, which are usually designed to have simple C (or Objective-C interfaces as well as being impossible to replace with Go by definition. Having pre-generation work on a best-effort basis would be ok for me, I would simply not provide pre-generated files for the platforms/libraries that are not supported.

I am looking forward to this feature, but there seems to be no progress.

Is there a simple way to implement it? Pack the intermediate files generated by gcc into a zip, and continue to use a third-party linker. The main trouble with C language cross-compilation is various dependencies and libraries. I don't know much about compiling and linking, and I might understand it incorrectly.

If you have to have the third party linker and the third party libraries anyhow, then I don't think this idea is going to help very much.

I think there wouldn't even be any need for new .cgo file types, it should be possible to just generate .go and .syso files that build with the current toolchain. It might even be relatively stable: the ABI is fixed, so the only unstable internal is asmcgocall.

Even this may be unnecessary - it should be possible to precompile CGO code to Go assembly. This would then reduce the scope of the problem to creating a CGO -> C .S assembly -> Go .S assembly tool, which would presumably be run via go generate. The only build system change required would probably then be a magic comment that defines shared libraries to link to.
This way, CGO can be moved from the build process to the go generate process and become an internal detail purely for developers of CGO packages, making it more in line with other code generation projects. This would also resolve the difficulties of reproducible builds when using system libraries.

cgo packages can and do refer to external libraries; presumably we would have to find all of those external libraries and make them available somewhere. But the libraries are going to vary a lot. How do we find them and where do we put them?

In the case of system libraries like libc or OpenGL, there's an implicit assumption that they're already preinstalled in the OS.
Otherwise, I think it's okay to push the burden of distributing shared libraries onto developers, much like the way they work in C/C++.

Some of those libraries are written in C++. C++ code requires extra work from the linker to support things like global constructors and destructors and exception handling. If we can't invoke the external linker, we have to implement all of that code in cmd/link, and we have to maintain it as C++ changes.

I think it's okay to not support C++ shared libraries (I didn't even know this was possible - I thought C++ shared libraries always exported a C interface?)

Maybe I'm missing something, but while I can see how this could work in the simplest cases, I don't see how it could work in general.

I think supporting those simplest cases would be enough.
For context, there are plenty of Go projects that involve automatically generated bindings to C libraries, such as go-gl. It would be great if they also gained the ability to precompile themselves to all supported systems from CI, allowing Go developers the newfound ability to cross-compile windowed applications.

I think there wouldn't even be any need for new .cgo file types, it should be possible to just generate .go and .syso files that build with the current toolchain. It might even be relatively stable: the ABI is fixed, so the only unstable internal is asmcgocall.

Even this may be unnecessary - it should be possible to precompile CGO code to Go assembly. This would then reduce the scope of the problem to creating a CGO -> C .S assembly -> Go .S assembly tool, which would presumably be run via go generate.

Some prior art for this approach can be found at c2goasm, with an article describing it here: https://medium.com/@frankwessels_nl/c2goasm-c-to-go-assembly-bb723d2f777f

The only build system change required would probably then be a magic comment that defines shared libraries to link to.

After some further investigation, it looks like this is already how CGO does linking today:
https://github.com/golang/go/blob/883f062fc0a097bf561030ad453fd3e300896975/src/cmd/cgo/doc.go#L767-L775
With that in mind, how feasible would it be to add a CGO tool that takes a list of files that import "C", invokes the system C compiler on them, and then translates the resulting C assembly into Go assembly with //go:cgo_dynamic_linker and //go:cgo_import_dynamic directives?

👋 Hey. Coming from the dd-trace-go library where we wanted to add a C library bindings at some point where we had already a large user base and adding all CGO requirements for these users where out of question. We studied a lot of different options and we decided to use a tool called purego that uses a lot of internal mechanisms of the runtime directly. This has been working for the last 6 months already but having an official method to not impact users in case a library decides to start using CGO certainly seems more reliable. Looking forward to see this happening.

In general this is very difficult / impossible. One of many difficulties is keeping both static and dynamic builds working correctly. If you need C code, use cgo.

This proposal has been declined as infeasible.
— rsc for the proposal review group

As @eliottness shared, this is more or less already feasible and this is how we make it in dd-trace-go:

Compile your CGO bindings with the options -x -work to be able to copy the CGO-generated files, especially the Go type definitions generated out of the C ones).
Copy and adapt them to work without CGO, since a lot of things in there will rely on compiler directives that don't work without CGO_ENABLED=1.
Build your C library as a shared library that you can embed in your binary with go:embed.
Use purego, which is a higher-level helper runtime/cgo package, to open the shared lib and call it, the same way as CGO would, as it relies on runtime/cgo too (present with or without CGO_ENABLED).


Add lambda support into gradle

compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}

It was added earlier


⚠ Bofrost.fr has degraded performance

In 8735690, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1738 ms

Resolved: Bofrost.fr performance has improved in d6cd58a after 19 minutes.


WIP: June23 demo

A branch for developing the model to the point where it can run the thermodynamics and dynamics demos for the June 2023 SASIP meeting in Bergen.
Based on the dynamics branch (#304) and the thermodynamic single column demo (#127), this branch also incorporates the changes necessary to get the demo up and running.

The switched ordering of array indices, including all the imported code.
Add the config files for the demos.
Correct the handling of zero ice thickness.
Fill in the correct values of the ice temperature at the correct point of the timestep.
Remove the code from the dynamics which drives the cyclonic test case.
Regenerate start files with a consistent land mask.
Including headers missing in the Linux version.
Close diagnostic files before ending the test to prevent exceptions.
Pass the forcing velocities (winds, currents) to the dynamics.
Retrieve the ice velocity from the dynamics.
Adding @einola's changes to the albedo treatment
Fix the Melting Conditions test with a corrected test value
Adding a ModelArray for the short wave penetrating flux
Add a smesh file for the topaz mask
Set the number of ice Z-levels for DummyThermodynamics
Remove all the new lines printed when generating the ParametricMesh

Closes #336.

Superseded by #359


Add branch for aave use case

 Issue #64

Fixes #
Checklist

[x] My branch is up-to-date with upstream/develop branch.
[x] Everything works and tested for Python 3.8.0 and above.
[x] I ran pre-commit checks against my changes.
[x] I've written tests against my changes and all the current present tests are passing.

Current behaviour
The RpcHelper class only contains request functions that decode the hex data from a json eth_call or a web3 call using the web3.codec or eth_abi.decode. This can be an issue when making a call on a contract that returns an array of tuples ("Tuple[]") as neither the web3.codec.decode_abi or eth_abi.decode functions can decode this data type.
New expected behaviour
I have added the batch_eth_call_on_block_range_hex_data() function to rpc.py as an alternative to batch_eth_call_on_block_range() that returns the encoded hexbyte data from an eth_call directly instead of decoding. This allows alternate decoding methods to be used for decoding tuple arrays.
I have also added the /time_series endpoint to the core api. This endpoint allows for the retrieval of equally spaced snapshots over a given time period for the purposes of building graphs or gaining insights over relatively large time frames. Additionally, a helper function for this endpoint has been added in data_utils.py to facilitate the retrieval of this data.
Change logs
Added

Added batch_eth_call_on_block_range_hex_data() to snapshotter/utils/rpc.py

Added /time_series endpoint to snapshotter/core_api.py

Added get_project_time_series_data to snapshotter/utils/data_utils.py

Changed

changed .gitmodules to point to current aave fork. Will update when merged to powerloom repo.

changed snapshoter_autofill.sh namespace to "aavev3"

updated README to with specific instructions for this branch

Deployment Instructions
No changes

Meaningful changes merged with this commit by @xadahiya
442ca7f


VLAZ: Watch allegiantsky.com

VLAZ requests the watch of the watch_keyword allegiantsky\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Approved by cigien in Charcoal HQ

allegiantsky\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.


Poster is loaded twice

Just open the official demo https://plyr.io, and you'll find the poster image loaded twice as below. I am not sure if this is necessary?

Yep it is unfortunately as we display it in a custom element. The only other solution would involve removing the progressive enhancement. I don’t think removing the poster attribute with JavaScript would abort the initial load. I doubt it.

Haha, OK, thank you.

maybe you could append the image to the custom element from media element maybe with sth like
let sourceImage = document.createElement('img'),
     imgContainer = document.getElementById("custom-element");
 sourceImage.src = "[some img url or cloning loaded poster img]";
 imgContainer.appendChild(sourceImage);

 function cloneImg(){
     imgContainer.appendChild(sourceImage.cloneNode(true));
 }

not tested ;)

If we had access to the shadow DOM then we could clone the contents yep but its not possible.

Closing this one for now as there's not much we can do.


Enable 1.9 versions of GKE

Versions are filtered on 1.8 as of today, we should enable 1.9 as well.
https://github.com/rancher/ui/blob/master/lib/shared/addon/components/cluster-driver/driver-googlegke/component.js#L193

Version - 2.0 master 4/17
Verified fixed


TS Errors that go away after updating

I was getting the following TypeScript errors in VS Code in a brand new Vite+React+TS project.

Errors on every HTML tag
Errors on importing React
Errors on importing a tsx file with extension

All these were automatically solved when I updated VS Code from 1.75 to 1.78. However I wasted a lot of time trying to find a solution. It felt like an odd behavior for a code editor. You'd generally expect such errors to originate in your source code or in your library or tsconfig, not because your code editor is not up-to-date.

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.75
OS Version: Fedora 37

Steps to Reproduce:

Create a new vite project with the following command:
npm create vite@latest myapp -- --template react-ts

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.78.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

All these were automatically solved when I updated VS Code from 1.75 to 1.78

Sounds like the issue is already fixed then?

You'd generally expect such errors to originate in your source code or in your library or tsconfig, not because your code editor is not up-to-date.

The editor is what reports issues with your code, so if there's a bug with the editor then it very much could be fixed by updating


How to Listening to HTML content change inside a WebView

Please Add New Feature for Listening to HTML content change inside a WebView, I Find Out lot But Can't Get Any Solution,
Wen UI Changed Then We can are get New Html Code
onNavigationChage Event Work Only If we go to from one page to Another, but what for if Content Chageged on Same Page or url
Please Give Any Solution, Thankyou

Use the injectedJavaScript prop and set a MutationObserver on the part of the page that you’re interested in watching.

Use the injectedJavaScript prop and set a MutationObserver on the part of the page that you’re interested in watching.


[Bug]: If you delete a Pipeline, the run reference leads to a weird error page

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
We have an issue where when you delete the Pipeline to runs that are already created, navigating to the Runs list page you can see the Run and click on the Pipeline.
You see this error page:

It's not the best, I imagine we can improve this UX somehow.
Expected Behavior
An improved experience when viewing a deleted Pipeline (from the run list)
Steps To Reproduce

Create a Pipeline
Create a Run for that Pipeline
Delete the Pipeline
View the Run on the Global Runs list page
Click on the Pipeline link

Workaround (if any)
No response
What browsers are you seeing the problem on?
No response
Open Data Hub Version
Dashboard: v2.10.0

Anything else
No response

@kywalker-rh not sure if you have a preference on how we address this... the dropdown has values to "Create Run", that's not going to work out.
Suggestions on how we address this issue?

I saw this issue today too.  One option could be to remove the pipeline runs when the pipeline is deleted. The pipeline deletion dialog could warn users about it

If its possible to simply remove the link to the pipeline that no longer exists I think that's the simplest option. Does that break anything else? I think there is a use-case where someone could want to reference Runs for a Pipeline that was deleted, so if we can avoid that I'd like to.

If its possible to simply remove the link to the pipeline that no longer exists I think that's the simplest option. Does that break anything else? I think there is a use-case where someone could want to reference Runs for a Pipeline that was deleted, so if we can avoid that I'd like to.

There could be a heavier option for sure about querying for the resource itself, so if I query for the Pipeline, get a 404 back, I'd know the resource is not there anymore and thus has been delated (reasonably sure that's the right and sane path to take).
But this is a performance hit to fetch every pipeline that is referenced in the Runs page (we could do this lazy like so it's by your number of items on your page). We'd need to be careful about how we store the data and how it is managed throughout the app -- We'd need to do this on both the Runs Triggered / Scheduled tables as well as the bottom drawer in the Run Details page.

Okay, sounds like we need a short term solution, and maybe time to think about a way to do it longer term that isn't so resource heavy. For short term can we create an empty state that says:
Pipeline not found
To see more pipelines navigate to the pipelines page.
[See all pipelines]

Sounds good, this will also help if you bookmark your Pipeline or have a tab open and it refetches and it is no longer there anymore (or if you try to manually type that id lol -- not likely a real use-case)

/assign


Extension READMEs do not support 'width' and 'height' attributes

VS Code Version: 1.53.2
OS Version: macOS Big Sur (Version 11.0.1)

Steps to Reproduce:

Open an extension's page from the Extensions view.

For example, this is what the Terminal All In One extension README looks like:

The width attribute of the image is 200, however, the real width of the image is larger, and it seems that the real width is used rather than the width attribute.

Does this issue occur when all extensions are disabled?: Yes

/verified


Spelling mistake

You will see a list of workflows tha

"tha" -> "that"
[Enter feedback here]

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

ID: 0b651f2c-f149-4616-9f02-12b064a1b989
Version Independent ID: 41ba41f4-03e5-b267-9a52-8290b30dfbec
Content: Build workflows with the Azure IoT Central connector in Microsoft Flow
Content Source: articles/iot-central/howto-add-microsoft-flow.md
Service: iot-central
GitHub Login: @viv-liu
Microsoft Alias: viviali

Thanks @rangv I will create a PR with the fix

#sign-off

@viv-liu Would you please review the PR #77260

Thanks again @rangv I merged the typo fix :)

Thanks!


Please document how to compile from source and add the results to a unity project

cd native
cargo ndk -t arm64-v8a build
cd ..
dotnet pack YetAnotherHttpHandler.sln --runtime android-arm64 --include-symbols --include-source -o publish

generates
native/target/aarch64-linux-android/debug/libyaha_native.so
publish/YetAnotherHttpHandler.0.1.0.nupkg
publish/YetAnotherHttpHandler.0.1.0.symbols.nupkg

and publish/YetAnotherHttpHandler.0.1.0.nupkg contains Cysharp.Net.Http.YetAnotherHttpHandler.dll
but the installation from https://github.com/Cysharp/YetAnotherHttpHandler.git?path=src/YetAnotherHttpHandler#v0.1.0 provides instead
libCysharp.Net.Http.YetAnotherHttpHandler.Native.so

How is libCysharp.Net.Http.YetAnotherHttpHandler.Native.so created?
The build.yml instruction gives
unzip -o ./publish/YetAnotherHttpHandler.*[0-9].nupkg 'runtimes/*' -d src/YetAnotherHttpHandler/Plugins/Cysharp.Net.Http.YetAnotherHttpHandler.Native/ || true
Archive:  ./publish/YetAnotherHttpHandler.0.1.0.nupkg
caution: filename not matched:  runtimes/*

See https://github.com/Cysharp/YetAnotherHttpHandler/issues/18 for details on how to proceed.

When creating a NuGet package, it is renamed from libyaha_native.so to libCysharp.Net.Http.YetAnotherHttpHandler.so, and the result of unzipping it is committed to Git. At this point, if you want to test it in a local environment, you need to manually rename and place it, or extract it from the NuGet package.
The path to the DLL referenced when creating a NuGet package is as follows:
native\artifacts\[target]\(lib)yaha_native.{so,dll}

https://github.com/Cysharp/YetAnotherHttpHandler/blob/1a7d5f0852b9059623f3ab11129d1bac44ad02c8/src/YetAnotherHttpHandler/YetAnotherHttpHandler.csproj#L79-L85
https://github.com/Cysharp/YetAnotherHttpHandler/blob/1a7d5f0852b9059623f3ab11129d1bac44ad02c8/src/YetAnotherHttpHandler/YetAnotherHttpHandler.csproj#L61-L63


[system] Remove custom behavior for sx={{ width: 1 }}

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
https://mui.com/system/sizing/
<Box sx={{ width: 1 }} />

feels a bit like a foot gun. I would expect 1px, not 100%. This discussion started in https://github.com/mui/mui-x/pull/5177/files#r895041464.
Examples 🌈
I would propose:
diff --git a/packages/mui-system/src/sizing.js b/packages/mui-system/src/sizing.js
index 0454dfb170..c6c8920e49 100644
--- a/packages/mui-system/src/sizing.js
+++ b/packages/mui-system/src/sizing.js
@@ -3,7 +3,7 @@ import compose from './compose';
 import { handleBreakpoints, values as breakpointsValues } from './breakpoints';

 export function sizingTransform(value) {
-  return value <= 1 && value !== 0 ? `${value * 100}%` : value;
+  return value < 1 && value > 1 ? `${value * 100}%` : value;
 }

 export const width = style({

Motivation 🔦
No response

hi @oliviertassinari , can you please assign me this issue?


Documenting your experiences to develop in the Solid/LD ecosystem

I will reformat this comment later, but I am sharing stuff now so I don't forget.

There is a steep learning curve for linked data which is mainly because all the educational websites are pretty old, and there are no new examples.
There are not that many linked and open data sets out there that one can use to build an application. Most of them are related to education which doesn't work that well with a real-life use case app.
It was very hard to find/understand how to make specifications for the linked data. Not knowing what schemas and ontologies to use was really annoying.
A good amount of the resources we found were archived or no longer available. Moreover, there were no example applications that combined all the technologies we used so we had to piece all the small examples together to get a working demo.
I believe we still do not take full advantage of the power of linked data, but because of the short time we had to get a grasp of the situation, and also build, I don't think much more could have been done.

I tried to list many of the higher-level issues you've experienced with the LD ecosystem, please use from this as much as you want https://thorgalle.notion.site/Feedback-for-Solid-LD-3faa05dcf2ac4e5491d149b9e8e1ef02
Consider also how you would improve the situation :)

OKAY so there's a lot of thoughts here
Open data
The vision of open data is something I wholeheartedly support. The TED talk that was shown was very inspirational and did genuinely remotivate me
Linked data/RDF
This is a tough one. Linked Data is a really cool and good idea, but it is held back by the incredibly steep learning curve, numerous dead links and resources, non-human-readable/writeable or kind of bloated file formats (you can write a JSON file by hand, but RDF? oh no). The biggest hope I see for Linked Data is the support of large entities. DBpedia/Wikipedia and Europe for example. But this reliance on longevity and size also kind of defeats the purpose a bit I feel?
Solid
Solid I like a lot more. The Inrupt clients - as tough as they were to get started with - ended up being incredibly nice to work with. The idea of being able to choose where to host, including but not limited to yourself, is a great idea, and many of the solid specs' ideas are amazing. It is however not consumer ready; considering the current lack of secure & consistent of public hosts and well maintained apps to hook into those hosts means this service is barely ready to be used by tech people, let alone your regular consumer (although both those can be fixed over time). My main long-term concern is the same with all decentralised technologies; if Solid has any longevity, I hope it'll be less of an ecological disaster than some other decentralised technologies.
Its kind of rough! We were only able to grasp how all the technologies worked near the end of development. And realising that this app is more of a proof of concept than anything does smart a little, as I have no clue how much longevity is in here. (But I am super happy with the experience of osoc & having a great team but don't tell them that shush)

Finished and added to the dosier


Build Errors on MacOS

I downloaded and unzipped the 1.0.0 zip file and tried unsuccessfully to build. Am I missing a step?
❯ ./build compile
/Users/timkellogg/Downloads/dt-1.0.0/build.zig:5:23: error: no field or member function named 'standardOptimizeOption' in 'build.Builder'
    const optimize = b.standardOptimizeOption(.{});
                     ~^~~~~~~~~~~~~~~~~~~~~~~
/usr/local/Cellar/zig/0.10.1/lib/zig/std/build.zig:31:21: note: struct declared here
pub const Builder = struct {
                    ^~~~~~
referenced by:
    runBuild: /usr/local/Cellar/zig/0.10.1/lib/zig/build_runner.zig:232:22
    usage__anon_4562: /usr/local/Cellar/zig/0.10.1/lib/zig/build_runner.zig:242:13
    remaining reference traces hidden; use '-freference-trace' to see all reference traces

Thanks for taking a look!
I'll have to add a better warning in the build script itself.
Right now the project will only build with Zig 0.11.0 or higher (currently the "master" release https://ziglang.org/download/). If you also want to run tests, you'll need to have a recent version of cargo, but nothing unstable.
As a side note: I don't plan to track unstable versions of Zig in the future, it makes packaging more challenging, and I might downgrade because of it depending on when Zig 0.11.0 is released. I switched to the version mostly for build/packaging changes that I ultimately didn't require (or at least not yet).

Added a note on Zig 0.11.0 requirement for build-from-sourcers in dt 1.0.0 release notes.

Added Zig versioning requirements to the build script, which should make this less mysterious for the next person.
https://github.com/booniepepper/dt/pull/11
I'll roll it into the next release.

Hey, sorry for the delay. I did a fresh clone and zig build dt -Doptimize=ReleaseSmall as the README now says and it gae me this error. Sorry, I don't know much abou zig, not sure what to do

Hey, how do I install Zig 0.11.0? It's not on the official downloads page

Ah, I figured it out eventually. It builds! On macos I had to run zig from my ~/Downloads directory (for anyone else following). The homebrew version was too old.
Now to figure out how this dt thing works!


Websockets implementation for Streaming Extensions

Through streaming extension, enable DL speech scenarios.

[ ] Basic POC (with most base classes done, no segmentation logic).
[ ] Segmentation for big streams.

Came here from the Streaming Extensions PR. Wanted to understand if Streaming Extensions is enabled and if there are any samples?

Hello @vijaysaimutyala , the streaming work is currently paused, nothing ready to use yet. We plan to continue this effort on our next milestone

See #1216


Seek help !!! No sentinel server available for autodiscovery

++There are so many errors like "No sentinel server available for autodiscovery” in php logs frequently. but the sentinels and redis service are normal. at the same time, No errors or warnings in sentinel or redis log.
++our development framework is laravel
++The detail logs is:
No sentinel server available for autodiscovery. {"exception":"[object] (Predis\ClientException(code: 0): No sentinel server available for autodiscovery. at /data/www/ic/vendor/predis/predis/src/Connection/Aggregate/SentinelReplication.php:268)

The sentinel status:
Sentinel
sentinel_masters:1
sentinel_tilt:0
sentinel_running_scripts:0
sentinel_scripts_queue_length:0
sentinel_simulate_failure_flags:0
master0:name=sentinel--,status=ok,address=:,slaves=1,sentinels=3
<IP_ADDRESS>:> sentinel sentinels sentinel--****

"name"
"03e7cb302fff7552343fbbc9fb071f92404588a7"
"ip"
"****"
"port"
"****"
"runid"
"03e7cb302fff7552343fbbc9fb071f92404588a7"
"flags"

"sentinel"
"link-pending-commands"
"0"
"link-refcount"
"1"
"last-ping-sent"
"0"
"last-ok-ping-reply"
"498"
"last-ping-reply"
"498"
"down-after-milliseconds"
"20000"
"last-hello-message"
"936"
"voted-leader"
"?"
"voted-leader-epoch"
"472"

"name"
"6f8ba8e8f5a22accf02b943b4e92e8fbd461f439"
"ip"
"****"
"port"
"****"
"runid"
"6f8ba8e8f5a22accf02b943b4e92e8fbd461f439"
"flags"

"sentinel"
"link-pending-commands"
"0"
"link-refcount"
"1"
"last-ping-sent"
"0"
"last-ok-ping-reply"
"498"
"last-ping-reply"
"498"
"down-after-milliseconds"
"20000"
"last-hello-message"
"629"
"voted-leader"
"?"
"voted-leader-epoch"
"473"

The function "stream_socket_client" is enable in php.ini

I have same issue.Sometimes this error happens, sometimes not.
Environment:
PHP 7.3.7
Redis 5.0.6
Lumen 5.5.*
Any idea?

I also have same issue and didnt find fix or workaround.

Same

Also have this issue, any idea?

The No sentinel server available for autodiscovery is generic error that can hide other problems. The original exception is likely getting eaten up here: https://github.com/nrk/predis/blob/v1.1/src/Connection/Aggregate/SentinelReplication.php#L464 or here: https://github.com/nrk/predis/blob/v1.1/src/Connection/Aggregate/SentinelReplication.php#L432 Try to add debugging that prints out the $exception around those lines to get more information about the original problem. It is likely a connection issue, possibly a timeout as the default is set very low - 0.1s.


Update cats-effect to 3.0.0

Updates org.typelevel:cats-effect from 3.0.0-RC3 to 3.0.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

github:typelevel/cats-effect/v3_0_0?sha=series/3.x

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

labels: library-update, semver-pre-release, scalafix-migrations

Superseded by #119.


Windows node register command does not work

What kind of request is this (question/bug/enhancement/feature request): bug
Steps to reproduce (least amount of steps as possible):

Bring up a windows cluster - 1 linux all roles. (custom cluster)
The register command from the custom cluster gives this error when run on a windows node

Unable to find image 'rancher/rancher-agent:master-2412-head' locally
C:\Program Files\Docker\docker.exe: Error response from daemon: manifest for rancher/rancher-agent:master-2412-head not found: manifest unknown: manifest unknown.

Expected Result:
Windows node should register successfully.
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master-head - commit id: 570461823
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): custom windows
Kubernetes version (use kubectl version):

1.17

Verified on latest -master-head - commit id: 5ee70d014

Windows cluster is deployed successfully - 3 linux nodes - 1 etcd, 1 control plane and 1 worker node and 3 windows worker nodes.
command kubectl get all -A works. Output:

e.g. kubectl get all
> kubectl get all -A
NAMESPACE       NAME                                          READY   STATUS      RESTARTS   AGE
cattle-system   pod/cattle-cluster-agent-698d67bdd6-qb6wr     1/1     Running     0          27m
cattle-system   pod/cattle-node-agent-hjskj                   1/1     Running     0          27m
cattle-system   pod/cattle-node-agent-jvtj6                   1/1     Running     0          26m
cattle-system   pod/cattle-node-agent-rjr5x                   1/1     Running     0          27m
cattle-system   pod/cattle-node-agent-windows-7slnl           1/1     Running     0          23m
cattle-system   pod/cattle-node-agent-windows-gz77h           1/1     Running     0          23m
cattle-system   pod/cattle-node-agent-windows-tvqwm           1/1     Running     0          23m
ingress-nginx   pod/default-http-backend-67cf578fc4-pcrbj     1/1     Running     0          28m
ingress-nginx   pod/nginx-ingress-controller-l8xlm            1/1     Running     0          26m
kube-system     pod/coredns-7c5566588d-jh9n8                  1/1     Running     0          28m
kube-system     pod/coredns-autoscaler-65bfc8d47d-5j6kf       1/1     Running     0          28m
kube-system     pod/kube-flannel-8d8gt                        2/2     Running     0          28m
kube-system     pod/kube-flannel-kd7k2                        2/2     Running     0          26m
.......

Automation was run on windows.
workloads are deployed successfully.
Steve dashboard is enabled on windows cluster.


updating so that only first word is taken as command

Example writing $contact works but writing $contact 999 would not work since the entire input is being considered.
If we consider the command to be only the first word by using command = command.split()[0] and then running trim and tolowercase, we solve this problem

ok this recent one works
basically only one line of code, but it helps out in handling a few more cases
pls do consider this pr for hacktober

Hi @Paulie-Aditya
Thanks for your interest.
If we were to implement this we might not get the benefit from #3.
When #3 is implemented the command will look something like this
setname Jake

What are your thoughts?
Regards
THT

we can just keep those as edge cases, say the command is setname, then we will also consider the first argument
basically a simple if else can be put in case to resolve that, not a big issue

Makes sense.
Let's do one thing.
I'll first merge #3 and then merge this one to avoid any code conflict.
Does that work for you?
This PR will be considered under hacktoberfest.
Thanks

yep, works for me 👍

just do let me know what all commands have to take in additional input (after finishing up #3), I'll fix it accordingly

Cool. I'll update you when #3 is merged.

#3 is merged. You can work on this now @Paulie-Aditya

@thtauhid done, Please do check the same and merge it upon success.

Hi @Paulie-Aditya
If I enter setname tauhid, the space is getting removed between setname and tauhid and it's showing command not found.
Can you check this once?

@Paulie-Aditya you need to merge the main branch to your feature branch.

gimme some time, I'll mention you once this is fixed

nvm my code was fine, only had problems in taking previous merged stuff into account

cool @thtauhid , works now.
Please perform the necessary checks and approve if found satisfactory.

Nice work @Paulie-Aditya
Looking forward to seeing more contributions from you in open source.

Join our Discord server to discuss ideas, ask questions, and collaborate with others.


[staging] dotneteng-status-staging website is down

Currently the website: https://dotneteng-status-staging.azurewebsites.net/ shows that the service is offline:
We received an availability alert for the website on 11/26

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[ ] Internal Infrastructure Improvements

Release Note Description

This seems to have started with this build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2590102&view=result.

Rerunning a build of the previous commit: https://dev.azure.com/dnceng/internal/_build/results?buildId=2590102&view=results resolved the azure monitor alert and brought the website back online. I will prepare a revert of the change.

Revert here: https://github.com/dotnet/dnceng/pull/4601

We had two healthy builds with the secret manager changes

https://dev.azure.com/dnceng/internal/_build/results?buildId=2594479&view=results
https://dev.azure.com/dnceng/internal/_build/results?buildId=2594407&view=results

So the changes are not related to why the service went down. This will need further investigation from the folks in the FR rotation.


[BUG] - keyboard navigation on autocomplete / select

NextUI Version
canary
Describe the bug
There're two observations here.

the list closes suddenly after reaching the end of visible options (i.e right after max height) and only happen on the first load
an unexpected scrolling was triggered

For the first one, the close logic was introduced in https://github.com/nextui-org/nextui/pull/3414 so the first behaviour won't exist in production (v2.4.2) but the second one does.
We need to find out why there is a scroll triggered when keyboard navigation reaches the end of visible options.
It is due to listbox with max-height.
maybe related to
    if (manager.focusedKey != null) {
      // Refocus and scroll the focused item into view if it exists within the scrollable region.
      let element = scrollRef.current.querySelector(`[data-key="${CSS.escape(manager.focusedKey.toString())}"]`) as HTMLElement;
      if (element) {
        // This prevents a flash of focus on the first/last element in the collection, or the collection itself.
        if (!element.contains(document.activeElement)) {
          focusWithoutScrolling(element);
        }

        let modality = getInteractionModality();
        if (modality === 'keyboard') {
          scrollIntoViewport(element, {containingElement: ref.current});
        }
      }
    }

Your Example Website or App
Go to Storybook - Autocomplete - Default
Steps to Reproduce the Bug or Issue

Go to autocomplete storybook - Default
click to open autocomplete
Keep pressing ArrowDown key to navigation
After Tiger, the list is closed due to an unexpected scrolling

Expected behavior
The list shouldn't be closed when using keyboard navigation
Screenshots or Videos
issue3468-demo.webm
Operating System Version
macOS
Browser
Chrome

@wingkwong  this is happening with Select too.

i am not getting this error
https://github.com/user-attachments/assets/d313696d-1add-4a90-8cbe-386ef1fafe59

@Tejas-Sands It only happens on first load.

In my initial analysis, i found out that, it is happening because of the key data-key inside optionProps  from useOption provided by @react-aria/listbox .
Please check the below code in use-listbox-item.ts
  const {isFocused, isSelected, optionProps, labelProps, descriptionProps} = useOption(
    {
      key,
      isDisabled,
      "aria-label": props["aria-label"],
      isVirtualized,
    },
    state,
    domRef,
  );

If you delete the key data-key, then the list does not close and their is no unexpected scrolling, but the side effect of it is that it does not auto-scroll to the items below.
https://github.com/user-attachments/assets/4f7fd640-8046-4359-9a56-2853aa3a2f6e

@wingkwong  which files in repo contain the above mentioned code ?

The one I posted is from react-spectrum side.

closing - no longer reproducible in latest version


feat: Add atom for controlling refresh rate halving in Steam

Adds atom for controlling whether we halve the hz in SteamUI. See https://github.com/hhd-dev/hhd/commit/ea00e99a446f0face75f82b95bd6d801ac7f7efc

also cleans up git format-patch to make diffs cleaner in the future


Using Nuget to enhance other mod development

Hi, Mipen.
I have used you Modlib for my mod.
For now, I had fork this latest repositorie to make sure the reference also be the latest.
Have you consider upload the ModLib to Nuget?

+1 It would be nice to have this avaible on Nuget


[#1277] chore: add flatten maven plugin

What changes were proposed in this pull request?
add flatten maven plugin
Why are the changes needed?
If we add shaded module for clients, we must add flatten-maven-plugin, or the dependences in not-shaded module will not be included in the shaded jar.
Fix: #1277
Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI

We're currently processing your upload.  This comment will be updated when the results are available.

Merged. Thanks @jerqi


Wagtail v6.2 migration error

Django==5.1, wagtail==6.2
when running "python manage.py migrate", the following error occurs -
Operations to perform:
  Apply all migrations: admin, auth, contenttypes, home, sessions, taggit, wagtailadmin, wagtailcore, wagtaildocs, wagtailembeds, wagtailforms, wagtailimages, wagtailredirects, wagtailsearch, wagtailusers
Running migrations:
  Applying wagtailcore.0020_add_index_on_page_first_published_at...Traceback (most recent call last):
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\backends\utils.py", line 105, in _execute
    return self.cursor.execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django_d1\database.py", line 195, in execute
    self.results = self.run_query(query, params)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django_d1\database.py", line 22, in newfn
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django_d1\database.py", line 159, in run_query
    raise DatabaseError(errorMsg)
django.db.utils.DatabaseError: internal error

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "E:\WORKPLACE\AA\d1wag\manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\core\management\__init__.py", line 442, in execute_from_command_line
    utility.execute()
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\core\management\__init__.py", line 436, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\core\management\base.py", line 413, in run_from_argv
    self.execute(*args, **cmd_options)
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\core\management\base.py", line 459, in execute
    output = self.handle(*args, **options)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\core\management\base.py", line 107, in wrapper
    res = handle_func(*args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\core\management\commands\migrate.py", line 357, in handle
    post_migrate_state = executor.migrate(
                         ^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\migrations\executor.py", line 135, in migrate
    state = self._migrate_all_forwards(
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\migrations\executor.py", line 167, in _migrate_all_forwards
    state = self.apply_migration(
            ^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\migrations\executor.py", line 255, in apply_migration
    state = migration.apply(state, schema_editor)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\migrations\migration.py", line 132, in apply
    operation.database_forwards(
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\migrations\operations\fields.py", line 241, in database_forwards
    schema_editor.alter_field(from_model, from_field, to_field)
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\backends\base\schema.py", line 905, in alter_field
    self._alter_field(
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\backends\sqlite3\schema.py", line 378, in _alter_field
    self._remake_table(model, alter_fields=[(old_field, new_field)])
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\backends\sqlite3\schema.py", line 257, in _remake_table
    self.delete_model(model, handle_autom2m=False)
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\backends\sqlite3\schema.py", line 279, in delete_model
    self.execute(
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\backends\base\schema.py", line 202, in execute
    cursor.execute(sql, params)
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\backends\utils.py", line 122, in execute
    return super().execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\backends\utils.py", line 79, in execute
    return self._execute_with_wrappers(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\backends\utils.py", line 92, in _execute_with_wrappers
    return executor(sql, params, many, context)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\backends\utils.py", line 100, in _execute
    with self.db.wrap_database_errors:
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django\db\backends\utils.py", line 105, in _execute
    return self.cursor.execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django_d1\database.py", line 195, in execute
    self.results = self.run_query(query, params)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django_d1\database.py", line 22, in newfn
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "E:\WORKPLACE\AA\d1env\Lib\site-packages\django_d1\database.py", line 159, in run_query
    raise DatabaseError(errorMsg)
django.db.utils.DatabaseError: internal error

Hey @xeroticikot getting back at this issue, i was able to fully migrate and run the wagtail bakery demo application using this library django-cf in conjunction with workers-dbms that uses Durable Objects instead of D1 as the database.
The application was fast enought for me, but let me know what you think
Learn how to use workers-dbms here


Add automatic master channel handling

Summary
When adding samples to a channel group, the absolute time is supplied. If a master channel is configured, this channel should use that time but the time needs to be converted to relative time.
The idea is to check  if a time master exist and if so set the proper relative time. The relative time should be relative to the start time. This time is store when the StartMeasurement() is called.
The StartMeasurement() function shall update samples in the cache while the SaveSample() function only needs to update the master channel value before creating.

Added so the master time channel uses the sample time to calculate the relative time. The user only needs to create the time master channel and the writer object will fix calculating the correct values from sample time and start time.


Create Cégep Saint-Jérôme

Thank you for adding Cégep Saint-Jérôme to the list.

sorry for the delay - the domain's already added!


Increment version for websites releases

Increment package version after release of Azure.ResourceManager.AppService

API change check
API changes are not detected in this pull request.

/check-enforcer override

Failure unrelated to these changes; merging.


Use preset colors for piecharts

Instead of calculating colors, simplify by using a flat set of colors adapted from http://duoparadigms.com/2013/10/11/10-color-palettes-perfect-autumnfall-season/.
This improves the appearance of the pie charts, and simplifies a bit of unecessarily complicated code.

New:
Old:

I like the new colors.


Fix typos in API.md

Current coverage is 99.54%

Merging #79 into master will not affect coverage as of 5dbf25c

@@            master     #79   diff @@
======================================
  Files           40      40
  Stmts          220     220
  Branches         0       0
  Methods          0       0
======================================
  Hit            219     219
  Partial          0       0
  Missed           1       1

Review entire Coverage Diff as of 5dbf25c

Powered by Codecov. Updated on successful CI builds.

Thanks!


Newlib retargetable lock init fails on qemu_xtensa

Describe the bug
__retarget_lock_init fails on the qemu_xtensa board.
To Reproduce
Build tests/lib/newlib/thread_safety and run it on qemu_xtensa.
Expected behavior
The malloc call in __retarget_lock_init succeeds.
Impact
Any components using the newlib are unusable on Xtensa.
Logs and console output
*** Booting Zephyr OS build zephyr-v2.6.0-2927-ga77e7566a8bb  ***
Running test suite newlib_thread_safety_locks
===================================================================
START - test_retargetable_lock_sem
ASSERTION FAIL [*lock != ((void *)0)] @ WEST_TOPDIR/zephyr/lib/libc/newlib/libc-hooks.c:362
        non-recursive lock allocation failed
@ WEST_TOPDIR/zephyr/lib/os/assert.c:45
E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
E: Current thread: 0x60008db0 (test_retargetable_lock_sem)
E: Halting system

Environment (please complete the following information):

OS: Ubuntu 20.04
Toolchain: Zephyr SDK 0.13.0
Commit SHA: a77e7566a8bb0135b52737e62fd1d6503b7b057a

Additional context
For some unknown reason, a77e7566a8bb0135b52737e62fd1d6503b7b057a causes the newlib malloc to fail and return NULL on Xtensa.
After full twister run on the tests/lib/newlib/thread_safety, only qemu_xtensa fails and the rest of the platforms succeed.

This is very bizarre. The failure is observed only when the size of sram0_seg is 36816 bytes.
sram0_seg:       36816 B        64 MB      0.05%

This goes away when the size of sram0_seg is below or above 36816 bytes ...
@dcpleung any ideas?

wonder if this has something to do with bss size change?

So I did some investigation and it happens only for the first malloc call whose first sbrk call returns a pointer that falls on a 0x1000 page boundary (at least, what newlib's malloc thinks is page boundary -- yes, we should fix these).
*** Booting Zephyr OS build zephyr-v2.6.0-2927-ga77e7566a8bb  ***
sbrk: 0x60009fd0, 48
sbrk: 0x6000a000, 0
0, (nil)
sbrk: 0x6000a000, 4096
1, 0x60009fe0
2, 0x6000a000
3, 0x6000a020
...

This only happens on Xtensa -- I have reproduced a similar case on other archs, but they all work as expected:
ARM (qemu_cortex_m3)
*** Booting Zephyr OS build zephyr-v2.6.0-2927-ga77e7566a8bb  ***
sbrk: 0x20001fd0, 48
sbrk: 0x20002000, 0
0, 0x20001fd8
sbrk: 0x20002000, 4096
1, 0x20001ff8
2, 0x20002018
3, 0x20002038
...

SPARC (qemu_leon3)
*** Booting Zephyr OS build zephyr-v2.6.0-2927-ga77e7566a8bb  ***
sbrk: 0x4000efd0, 48
sbrk: 0x4000f000, 0
0, 0x4000efd8
sbrk: 0x4000f000, 4096
1, 0x4000eff8
2, 0x4000f018
3, 0x4000f038
...

It looks like a newlib bug. What is special about Xtensa, compared to other archs, is that its MALLOC_ALIGNMENT is 16 rather than 8:
https://github.com/zephyrproject-rtos/newlib-cygwin/blob/4f5997d3c0f9011135e9627dad700c9d64be4a4b/newlib/libc/stdlib/mallocr.c#L1399-L1401
https://github.com/zephyrproject-rtos/newlib-cygwin/blob/b1fe4401fdbd0860e0b91227219b15d2e0142b78/newlib/libc/include/sys/config.h#L198


<EMAIL_ADDRESS>- Evaluation article

Different Types of Bean Injection in Spring.

Closing Pull Request as this was for evaluation article


Add support for onLayout events

you can use playground project for experiments: https://github.com/maxkomarychev/svgplayground
It's now possible to use onLayout prop on elements to get coordinates of the elements in coordinate space of a view.
I understand the algo is slightly unoptimal because it requires to recalculate matrixes backwards. If you have an idea how to get reverse transform with single operation I'd happily improve it, at the same time I didn't notice big performance issues.
(red rectangles are simple react View with coordinates obtained through new prop).

thanks @sibelius !
where can we expect this to be merged into upstream?

@msand can we get this merged in?

Sure, I can take a look perhaps on monday evening and merge the open PRs. I've changed jobs to a startup I cofounded, and I'm not currently working on any react native code base, except some hobby project experiments.  So, we should probably try to find more maintainers for now as well, as I won't have much time for much testing nor further development right now. @dustinsavery @brentvatne Do you have anyone/time available?

@msand updated PR, ready for review

Looks good, but is the inverse initial transform really needed on android? We're creating the canvas ourselves, and it should have the identity as the initial transform, no?

@msand, I didn't really check value of CTM on android, just translated code from iOS.
Will only be able to look into it next wee.

@msand initial ctm on android is identity matrix indeed, so we don't need to keep neither initial ctm nor invert, just take current ctm and convert rect with it.
ready for review

Looks good, haven't tested yet though. Also been thinking it would be good to expose https://www.w3.org/TR/SVG11/types.html#InterfaceSVGLocatable
interface SVGLocatable {

  readonly attribute SVGElement nearestViewportElement;
  readonly attribute SVGElement farthestViewportElement;

  SVGRect getBBox();
  SVGMatrix getCTM();
  SVGMatrix getScreenCTM();
  SVGMatrix getTransformToElement(in SVGElement element) raises(SVGException);
};

But, as this is react-native, perhaps onLayout is sufficient, as e.g. getBBox must return the actual bounding box at the time the method was called, even in case the element has not yet been rendered.
Will merge and test before releasing.

@maxkomarychev I've added getBBox, getCTM, getScreenCTM, getTotalLength, getPointAtLength and isPointInFill to the develop branch now. Would you be available to help testing?
I have a PR open here: #1135


SmartScreen complains the app isn't downloaded often, consider EV code signing

Microsoft have had a brilliant new idea - a regular code signing cert isn't enough any more to make IE happy. Now you need an EV code signing cert, which is mandated to be in a USB stick. Cost: $450 for one year. All because their original code signing infrastructure can't even use passwords to protect the private key, sigh.
Currently IE produces a "This program is not commonly downloaded and could be dangerous" warning which requires going into download history to work around.
In theory SmartScreen should learn that the existing certificate is OK once a bunch of people have downloaded it and Lighthouse has not been reported as a virus. Then an EV cert wouldn't be needed. The EV cert is only really useful because by paying up you get some pre-assigned reputation. So let's see how downloads go and whether it learns the download is OK.

Actually I was wrong. This warning is from Windows Chrome, not IE.

Seems like this has gone away now.


snapshot.storage.k8s.io incorrectly marked beta for v1.16

This is a Bug Report

Problem:
I got #16207 merged too early. snapshot.storage.k8s.io is not going beta in v1.16 but I put a misguided /lgtm on PR #16207
Proposed Solution:
Revert; see PR #16207
Page to Update:
https://kubernetes.io/docs/concepts/storage/volume-snapshot-classes/

/sig storage

Sorted via #16207
/close


feat/adaptation-following-shared-domain

Please review before merging.

:tada: This PR is included in version 1.14.0 :tada:
The release is available on:

GitHub release
v1.14.0

Your semantic-release bot :package::rocket:


TCP server start doesn't print a log

Description:
Once TCP service gets started it doesn't print any log. It would be better if we can print a log saying Started TCP listener  <port>

For low level modules like TCP and UDP, let's not print such log. Because, for instance, say someday we write a HTTP library using this TCP module, then we won't be able suppress this log. It will always be there.
Going forward we can even think of removing such logs from all the listeners. If the user wants they can print a log in the service init method (even though it is not the same, it is close enough)


Unit test for TEArrayList

Description:
TEArrayList is a wrapper of std::vector adapted to areg-sdk needs. It is needed to add unit tests to test all public methods and to cover as much codes as possible.
Solution:

There is a ./tests/units/ folder in the project to add unit tests.
Add in that folder a new unit testing file, for example TEArrayListTests.cpp, and write unit tests.

The unit tests should run at least with int, unsigned int, float / double and std::string and String / WideString types.
The tests with the custom types, like custom structures, are welcome, but it is optional.
If the amount of testing methods are to large, they can be split and can be implemented either in a separate folder (for example array) or can be split to separate files like TEArraListStringTest.cpp.
Each created file should be added in the CMakeLists.txt and in the areg-tests MSVC project.
Each .cpp file should have a list of tested methods at the top
Each test method should have convenient name that is describing the purpose of the test, and should have short description.

The tests should run. In case if a bug found, create a ticket and mention the priority in the title, like [bug]. Each created ticket should have at least 2 labels: bug and unit test.

Completed with PR #350


attack_eval.ieval. how to run this step on gpu??

for result in tqdm.tqdm(attack_eval.ieval(correct_samples), total=len(correct_samples)):
this step is so slow! how can do this on GPU??

call for a resolution too, I want to train on 7 GPUs, how to set parallel training?


Created Combine 2024 webpage

Moved combine2023 to past events and created a new event page for the combine2024. Only changes to the event pages were applied. We would like to send a save-the-date mail before christmas so it would be nice to have the website online soon.

Hi @shoepfl. Please note that there have been a few recent commits to master and Harmony 2024 (London in April) is the next Combine meeting coming up and is currently the default event. You'll have to merge in from master and resolve any conflicts. You probably also want to remove the names from the list of participants until registration opens.

Thanks, @pgleeson. I didn't have the Harmony this year in mind. All conflicts are now resolved and the list of participants is also empty.


Feat elastic layout

Introduce fitToBounds content mode.

Add FloatingPanelController.contentMode
Update 'Show Detail Panel' sample

Depends on #238 and #239
TODO

[ ] Add the description in README

Should you merge this pull request @SCENEE ?

Should you merge this pull request @SCENEE ?

I will merge it after #205 :)

Should you merge this pull request @SCENEE ?

I will merge it after #205 :)

Hope to have this feature soon :D


Getting Filter and Slicer Information in Visual

How can I get the filter and selected slicer details in my custom visual.
Please help.

Hi - please take a look at the SampleSlicer visual for documentation.
thx


Can I have a chat with you?

Dear Antonio Tripodi
I have an interesting crypto based game project and currently looking for a senior developer who can help me.
Can we have a little chat?
dreemhai#9292
This is my discord id, please send me a message.
Looking forward to talking with you.
Thanks

Dear @dreemhai,
Thank you for the proposal but unfortunately I am currently busy with some projects and I don't know when I will be free.
Thank you very much again for the proposal 🙏🏻
Best regards
Antonio Tripodi

@Tony133 thanks for your reply.
okay, then I will close this issue. Good luck with your work!


⚠ SceneTime has degraded performance

In ead33b3, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 5409 ms

Resolved: SceneTime performance has improved in bac20fd after 2 minutes.


moveit: 1.1.10-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository moveit to 1.1.10-1:

upstream repository: https://github.com/ros-planning/moveit.git
release repository: https://github.com/ros-gbp/moveit-release.git
distro file: noetic/distribution.yaml
bloom version: 0.11.2
previous version for package: 1.1.9-1

chomp_motion_planner
* Fix segfaults in CHOMP (#3204 <https://github.com/ros-planning/moveit/issues/3204>)
* Contributors: Robert Haschke

moveit

No changes

moveit_chomp_optimizer_adapter

No changes

moveit_commander
* Limit Cartesian speed for link(s) (#2856 <https://github.com/ros-planning/moveit/issues/2856>)
* Validate JointState argument to moveit_commander.set_joint_value_target (#3187 <https://github.com/ros-planning/moveit/issues/3187>)
* Adjust python PSI to new CollisionObject.pose interface (#3176 <https://github.com/ros-planning/moveit/issues/3176>)
* moveit_commander: make current joint state copy-paste-able (#3133 <https://github.com/ros-planning/moveit/issues/3133>)
* Replace obsolete distutils.core with setuptools (#3103 <https://github.com/ros-planning/moveit/issues/3103>)
* Contributors: Filip Sund, Michael Görner, Stephanie Eng

moveit_core
* Limit Cartesian speed for link(s) (#2856 <https://github.com/ros-planning/moveit/issues/2856>)
* Generalize computeCartesianPath() to consider a link_offset (#3197 <https://github.com/ros-planning/moveit/issues/3197>)
* Generate version.h with git branch and commit hash (#2793 <https://github.com/ros-planning/moveit/issues/2793>)
* robot_model_test_utils: Add loadIKPluginForGroup()
* Remove ConstraintSampler::project() (#3170 <https://github.com/ros-planning/moveit/issues/3170>)
* Add dual arm test (#3119 <https://github.com/ros-planning/moveit/issues/3119>)
* Fix PlanarJointModel::satisfiesPositionBounds (#3160 <https://github.com/ros-planning/moveit/issues/3160>)
* Switch to hpp headers of pluginlib
* Fix bug in applying planning scene diffs that have attached collision objects (#3124 <https://github.com/ros-planning/moveit/issues/3124>)
* Fix flaky constraint sampler test (#3135 <https://github.com/ros-planning/moveit/issues/3135>)
* Constraint samplers with seed (#3112 <https://github.com/ros-planning/moveit/issues/3112>)
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Fix null pointer access to CollisionEnvObject in PlanningScene (#3104 <https://github.com/ros-planning/moveit/issues/3104>)
* ACM: Consider default entries when packing a ROS message (#3096 <https://github.com/ros-planning/moveit/issues/3096>)
* Contributors: Captain Yoshi, Jafar, Jochen Sprickerhof, Michael Görner, Robert Haschke, Rufus Wong, Tahsincan Köse, cambel

moveit_fake_controller_manager
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Contributors: Michael Görner

moveit_kinematics
* Merge PR #3172 <https://github.com/ros-planning/moveit/issues/3172>: Fix CI
* Fix test_ikfast_plugins.sh
* auto_create_ikfast_moveit_plugin.sh: allow xacro input
* Switch to hpp headers of pluginlib
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Contributors: Jochen Sprickerhof, Michael Görner, Robert Haschke

moveit_planners

No changes

moveit_planners_chomp

No changes

moveit_planners_ompl
* Remove ConstraintSampler::project() (#3170 <https://github.com/ros-planning/moveit/issues/3170>)
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Cleanup OMPL's PlanningContextManager's protected API
* planning_context_manager: rename protected methods
* Contributors: Michael Görner, Robert Haschke

moveit_plugins

No changes

moveit_ros

No changes

moveit_ros_benchmarks
* Fix namespace of planning plugin for benchmarks examples (#3128 <https://github.com/ros-planning/moveit/issues/3128>)
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Filter more invalid values in moveit_benchmark_statistics.py (#3084 <https://github.com/ros-planning/moveit/issues/3084>)
* Contributors: Hugal31, Michael Görner, Robert Haschke

moveit_ros_control_interface

No changes

moveit_ros_manipulation
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Contributors: Michael Görner

moveit_ros_move_group
* Limit Cartesian speed for link(s) (#2856 <https://github.com/ros-planning/moveit/issues/2856>)
* Optionally enable dynamics monitoring in move_group node (#3137 <https://github.com/ros-planning/moveit/issues/3137>)
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Contributors: Michael Görner

moveit_ros_occupancy_map_monitor
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Contributors: Michael Görner

moveit_ros_perception
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Contributors: Michael Görner, Robert Haschke

moveit_ros_planning
* Limit Cartesian speed for link(s) (#2856 <https://github.com/ros-planning/moveit/issues/2856>)
* trajectory execution manager: reactivate tests (#3177 <https://github.com/ros-planning/moveit/issues/3177>)
* Clean up TrajectoryExecutionManager API (#3178 <https://github.com/ros-planning/moveit/issues/3178>)
* MoveItCpp: Allow multiple pipelines (#3131 <https://github.com/ros-planning/moveit/issues/3131>)
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Contributors: Jochen Sprickerhof, Michael Görner, Robert Haschke, cambel, v4hn

moveit_ros_planning_interface
* Limit Cartesian speed for link(s) (#2856 <https://github.com/ros-planning/moveit/issues/2856>)
* Generalize computeCartesianPath() to consider a link_offset (#3197 <https://github.com/ros-planning/moveit/issues/3197>)
* Validate JointState argument to moveit_commander.set_joint_value_target (#3187 <https://github.com/ros-planning/moveit/issues/3187>)
* Add dual arm test (#3119 <https://github.com/ros-planning/moveit/issues/3119>)
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Replace obsolete distutils.core with setuptools (#3103 <https://github.com/ros-planning/moveit/issues/3103>)
* Contributors: Filip Sund, Michael Görner, Robert Haschke, Stephanie Eng, cambel, v4hn

moveit_ros_robot_interaction
* Find end-effectors for empty parent_group (#3108 <https://github.com/ros-planning/moveit/issues/3108>)
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Consider eef's parent group when creating eef markers (#3095 <https://github.com/ros-planning/moveit/issues/3095>)
* Contributors: Michael Görner, Robert Haschke

moveit_ros_visualization
* Fix rviz segfault when changing move group during execution (#3123 <https://github.com/ros-planning/moveit/issues/3123>)
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Replace obsolete distutils.core with setuptools (#3103 <https://github.com/ros-planning/moveit/issues/3103>)
* Contributors: Michael Görner, Robert Haschke, bsygo

moveit_ros_warehouse
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Contributors: Michael Görner, Robert Haschke

moveit_runtime

No changes

moveit_servo

No changes

moveit_setup_assistant
* Limit Cartesian speed for link(s) (#2856 <https://github.com/ros-planning/moveit/issues/2856>)
* MSA templates: replace hard-coded package name
* Extended ACM editing in MSA (#3093 <https://github.com/ros-planning/moveit/issues/3093>)

    * Allow disabling/enabling links by default
    * Use matrix view by default

* Optionally enable dynamics monitoring in move_group node (#3137 <https://github.com/ros-planning/moveit/issues/3137>)
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Improve Gazebo-compatible URDF generation in MSA (#3081 <https://github.com/ros-planning/moveit/issues/3081>)
* Contributors: AM4283, Michael Görner, Robert Haschke, rickstaa

moveit_simple_controller_manager
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Contributors: Michael Görner

pilz_industrial_motion_planner
* Add missing header for std::unique_ptr (#3180 <https://github.com/ros-planning/moveit/issues/3180>)
* Switch to hpp headers of pluginlib
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Contributors: Jochen Sprickerhof, Michael Görner

pilz_industrial_motion_planner_testutils
* Replace bind() with lambdas (#3106 <https://github.com/ros-planning/moveit/issues/3106>)
* Contributors: Michael Görner

Depends on #34459

Holding for Noetic sync


Epic: Improve feature versioning

This epic tracks the subtasks on improving Tekton pipeline feature versioning including feature flag improvements, documentations, maintenance routine and cleanups etc.
Feature flag improvements 🎏

[ ] Per feature flag
[ ] Decoupling API versioning and Feature versioning for features turned on by default
[ ] Default enable-api-fields value for opt-in features once feature and API versioning are decoupled

Documentations 📑

[ ] Update our policies/development guide/TEP process to mention that new features start out in the alpha track
[ ] Update our policies to mention that new feature authors should open an issue to track the feedback on that feature and promotion to beta once the feature lands in a release
[ ] Better documentations for feature stability levels

Maintenance routine 📝

[ ]  Consider retroactively opening issues to track feedback/promotion for current features in alpha
[ ]  Implement a quarterly alpha feature review to come up to review current features in alpha (this does not preclude moving features to beta outside of this review. This is mostly a way to ensure all alpha features are reviewed on a regular basis). First one schedule for September 12 during the API WG.

Cleanup 🧹

[x] Do not require enable-api-fields=alpha for spire
[x] Move feature flags testing functions into testing package
[x] Replace redundant function CheckAlphaOrBetaFields
[x] Update Stability Level for CSI and Projected Volume Workspaces

/kind epic

/kind Epic

/area epic

/lifecycle frozen

Closing with the completion of the following:

https://github.com/tektoncd/pipeline/issues/5632
https://github.com/tektoncd/pipeline/issues/6592
https://github.com/tektoncd/pipeline/issues/6948


Use iodata when building SQL queries

Let's do it by parts so we don't have one big PR. :)
I believe the adapter should still return a binary (because of query caching) but the building can be done with iodata and then we can call IO.iodata_to_binary once at the end.

It's funny that you mention it, since I was working on it some time ago, but didn't finish. I have regular query generation for postgres (excluding ddl).
Through my measurements I didn't notice any significant speed difference, though I assume the GC pressure would be much lower since it would be producing less garbage. It might be that I messed up with the measurements.

Shoulds this still be open since #1802 is merged?

This is pending removing the IO data conversion from adapters and doing it in the connection. This will benefit particularly insert_all.


Update README.md

Actually we should even tell linux users not to use apt, snap or else you'll get the wrong version. The best is the binary from github release put into some $PATH directory.
I'll update that part.