how to use ExoPlayer ？

the doc do not have a guide on how to enable ExoPlayer, any help please?

react native info:
System:
    OS: macOS 11.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 128.96 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 12.19.0 - /usr/local/bin/node
    Yarn: 1.22.5 - ~/.yarn/bin/yarn
    npm: 7.0.8 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.0 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.3, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK:
      API Levels: 21, 23, 25, 26, 27, 28, 29
      Build Tools: 23.0.1, 26.0.1, 26.0.2, 27.0.3, 28.0.3, 29.0.2
      System Images: android-30 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.1 AI-201.87<IP_ADDRESS>53283
    Xcode: 12.3/12C33 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_212 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1
    react-native: ^0.64.0-rc.2 => 0.64.0-rc.2
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Hi.
You need to create react-native.config.js file on your root project folder with this part of code:
module.exports = {     dependencies: {         'react-native-video': {             platforms: {                 android: {                     sourceDir: '../node_modules/react-native-video/android-exoplayer',                 },             },         },     }, };

Hi.
You need to create react-native.config.js file on your root project folder with this part of code:
module.exports = { dependencies: { 'react-native-video': { platforms: { android: { sourceDir: '../node_modules/react-native-video/android-exoplayer', }, }, }, }, };

You're life saver)

Why this is not added in Readme yet ? Should I make a PR ?

Hi.
You need to create react-native.config.js file on your root project folder with this part of code:
module.exports = { dependencies: { 'react-native-video': { platforms: { android: { sourceDir: '../node_modules/react-native-video/android-exoplayer', }, }, }, }, };

Without knowing this I've wasted my 48hrs. AWESOME.

Hi. You need to create react-native.config.js file on your root project folder with this part of code:
module.exports = { dependencies: { 'react-native-video': { platforms: { android: { sourceDir: '../node_modules/react-native-video/android-exoplayer', }, }, }, }, };

Thanks a lot man...

Cannot be enable. How should I do next steps like re-run: yarn start, yarn android or something like that

Yes, you need to rebuild the app after switching to exoplayer

Hi. You need to create react-native.config.js file on your root project folder with this part of code:
module.exports = { dependencies: { 'react-native-video': { platforms: { android: { sourceDir: '../node_modules/react-native-video/android-exoplayer', }, }, }, }, };

This helped me with react-native-video-player as well.


width option ignored in html output

    curve = hv.Curve((x_axis, y_axis["Gesamt"]), "Monat", "Kunden")
    curve_opts = {"width" : 1000,
                  "height": 600,
                  "color" : "white"}
    curve.options(**curve_opts)
    renderer = hv.renderer('bokeh')
    plot = renderer.html(curve).replace(',"plot_width":300', ',"plot_width":1000')

remove the replace() and it is back to outputting a 300 width plot to the page.

Almost all methods in HoloViews return a new object, i.e. they are not inplace operations. When you run
curve.options(**curve_opts)

that will return a new object with the options applied and since you are not assigning it to anything those options are simply lost. So you should do something like:
    curve = hv.Curve((x_axis, y_axis["Gesamt"]), "Monat", "Kunden")
    curve_opts = {"width" : 1000,
                  "height": 600,
                  "color" : "white"}
    curve = curve.options(**curve_opts)
    renderer = hv.renderer('bokeh')
    plot = renderer.html(curve)


Intellisense

Hello, The Intellisense in razor views not working
Ubuntu 16.4
VS Code

Hi,
razor views or pages?

Razor Views, when I write @Model.  Not working

Which version of vs code are you running?

Version: 1.11.1

Version 1.11.2 =》   vs code are you funning？

@yeganehaym No intellisense available for razor

1.20.1
x64
No intellisense in cshtml page:
@Model. ???


[Question] How easy would it be to make a language server library from this code?

Specific use case : I find myself wanting a Terraform language server.
Terraform is written in Go. I feel like the best plan is to implement a language server that can consume all of Terraform's code to mine it for type information on the various resources.
Since this is a language server written in Go... is there a good enough break here between "implements a language server in Go" and "implements a language server for Go" to make it simple to write other language servers in Go?

I actually considered writing a terraform LS a while ago for fun, but never found the time. So I agree with your idea. The pkg/lsp type definitions you will find useful. Otherwise there really isn't that much that you could share with the stuff in langserver, nor would you want to. You basically just want pkg/lsp and the jsonrpc2 package. To implement your handler take a look at this entry point https://github.com/sourcegraph/go-langserver/blob/master/langserver/handler.go#L131 Note: Our handler code is kinda over-engineered because we use and compose parts of it in our private code.

Thanks for the pointers!


Easy way to get the score for hand tracking from results.multi_handedness

When   print(results.multi_handedness):
I got :
[classification {
  index: 1
  score: 0.9999532699584961
  label: "Right"
}
]

Is there an easy way to get the score in python?

Hi @mathmax12, Yes you can use the results to check the score and label  mentioned above.

if I want to access the label only what's the right way to do it.
print(results.multi_handedness[0].classification["score"])
  print(results.multi_handedness[0].classification["score"])
TypeError: 'NoneType' object is not subscriptable

Hi @mathmax12, You can try the solutions from this https://github.com/google/mediapipe/issues/1374 issue


Don't restart the coroutine in connectAsyncWithRetry()

Task/Issue URL: https://app.asana.com/0/488551667048375/1207003406045665/f
Description
See task.
No UI changes

#4401  👈
develop

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

Join @lmac012 and the rest of your teammates on  Graphite


Remember the previously used path for the feature "Help" -> "Collect diagnostic info"

Description
I wish the application to remember the path to the output folder I used earlier so that I don't have to set it again every time I use this feature.

DBeaver Version
Enterprise Edition 24.2.3-202410122322
Operating System
Windows 10
Database and driver
No response
Steps to reproduce

call menu "Help" - > Collect diagnostic info
set some specific folder, for example: C:\myfolder\
press OK (or Cancel)
call the same menu again

Expected:
The folder C:\myfolder\ is shown in "Output folder" textbox.
If the user closes the application and opens it again, then clicks the menu "Collect diagnostic info", the folder  C:\myfolder\ is shown in the "Output folder" textbox.
Actual: the folder C:\Users\%username% is shown
Additional context
No response

@ask9 can I contribute to it ?
Got the fix for it

@cgujarat I would be happy!
Just wait for the answer of the DBeaver's team.

@cgujarat yes, you could try :)

@E1izabeth I got the fix for the following scenario :
if the user chooses the output folder path and opens it again in Collect diagnostic info , the folder path is retained
but if the user closes the application and opens Collect diagnostic info , the root folder path is retained because we are setting the root folder path as default path in the code base on application startup .
the issue is in CollectDiagnosticInfoHandler.java file .
Can you please provide info on whether it is possible to retained the folder path if the user closes the application and then opens diagnostic info dialog box , if yes can you provide some more pointers on where I need to look to make changes for it ?
Thanks !

@E1izabeth created PR for this :
https://github.com/dbeaver/dbeaver/pull/36007


Allow "Go To Definition" to work with fixtures in Pytest, similar to Pycharm

I searched existing issues, and couldn't find something exactly like what I'm describing.
When using pytest, you can use conftest.py to import a bunch of fixtures from various files to be used in your actual tests. These fixtures are passed in as parameters to the test methods themselves, and pytest figures out everything via some magic under the covers. VSCode doesn't seem to understand where to find these fixtures when using the "Go To Definition" command from the method that is using the fixtures, whereas Pycharm does seem to understand how to resolve it and allow their go to definition to function as I would have expected.
Is there any chance that we can get this to work with Pylance? Below is a video that I took demonstrating the issue - Pycharm on the left, VSCode on the right.
https://user-images.githubusercontent.com/8128941/133654689-aaf685a8-fb77-41dd-a703-1be9f717c7bb.mp4
Here's a minimal sample project to repro this: https://github.com/macintacos/fixtures-pylance-test
It uses Poetry for dependency management. You can repro what I gave above by just cloning the repo and doing:
poetry install
poetry run fix # this is just to test that the project runs fine
poetry run pytest tests # this will show you that the fixture is coming up okay - it's meant to fail.

Please let me know if there's any additional information I can provide. Thanks!

This is a dupe of #1750.

Thanks @jakebailey, will follow that along with interest 🙂


Wiki request - rewrite and simplify explanation of Global Function Object

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function

Moved this issue to Wiki repository, see https://github.com/FreeCodeCamp/wiki/issues/361.


Change combatant comparison to constructed object

If merged, resolves #10494
It looks like the self:participant:own-turn comparison in the entries array in createEncounterRollOptions() is comparing a constructed and not-yet-constructed actor when targeting. I quickly did a console log to see what was happening:
    console.log(encounter.combatant?.actor === actor);
    console.log(encounter.combatant?.actor, actor);

and got

The first pair (two combatants) of logs are when nothing is targeted, the second pair are when an enemy is targeted.

Yeah, I can reproduce the issue myself


setup.py, hook into letsencrypt plugin architecture

We've established in https://github.com/letsencrypt/lets-encrypt-preview/pull/390 that due to our current development stage, it'd be better to include this repo in the core, rather than hook into the plugin architecture yet.

Well, thanks anyway! That was a really quick turnaround, even if we're going either the stable version for now :)


Rewrite with sqlmodel

You have developed an incredible sqlmodel. Please rewrite the app for it.

I just did! :rocket: :tada:


dialog won't close after clicking on an existsing link

In the advanced example http://voog.github.io/wysihtml/examples/advanced.html , create a link and then click on it.
The dialog will never close when I click the cancel btn.
The log shows that after the dialog was closed, the editor was focused and triggered an event on the existing link and then reopened the dialog.
(In my case, my dialog is placed exactly over the editor, and clicking on the ok btn also reopen the dialog T. T)

actually the cancel button works, but the dialog doesn't close anymore when clicking "ok" on an existing link to edit it. I could reproduce this on the "advanced example"

+1
This seems to be true in 0.5.0-beta8 as well. The dialog opens when you focus on a link, and clicking the Ok button will focus where you had the marker last, which now is a link, hence, opening the dialog... It seems like. :) (Wysihtml newb here though).
It would be good if there was some way to control when the link dialog opens as well. (Or is there?) Id rather have it like TinyMCE where you click the link first, and then click the edit button. Because I want the insert/edit link dialog to be sort of a modal. But I cant have the modal open every time you click a link. :)


Enable TORCH_NCCL_AVOID_RECORD_STREAMS=1 by default

This PR enables the magic environment variable to be on by default for Thunder. The change should be restricted only to Thunder.
This magick environment variable is supposed to fix a problem with the allocator thrashing when using collectives from the NCCL backend of PyTorch.
I have tested performance with the command provided by @parthmannan in #420
torchrun --nproc_per_node=8 --nnodes=1 thunder/benchmarks/benchmark_litgpt.py --model_name Llama-2-13b-hf --compile thunder_cudnn --distributed_mode fsdp --shard_mode zero2 --bucketing_mode none --micro_batch_size 1 --global_batch_size 8

and this PR gives ~2.11x performance improvement (1517 ms -> 716 ms).
Fixes https://github.com/Lightning-AI/lightning-thunder/issues/420.
cc @parthmannan

Does this work, though, from the PyTorch source it would seem that it needs to be set for the process group:
https://github.com/pytorch/pytorch/blob/f343f98710dfa7305a873f558086c595a3c3d3d4/torch/csrc/distributed/c10d/ProcessGroupNCCL.cpp#L776

Yes, getCvarBool parses the environment variable with std::getenv https://github.com/pytorch/pytorch/blob/f343f98710dfa7305a873f558086c595a3c3d3d4/torch/csrc/distributed/c10d/Utils.hpp#L160

As a side note: in relation to this https://github.com/pytorch/pytorch/pull/76861#issuecomment-1233565169
It would be interesting to understand what happens if we automatically insert wait_stream at the end of a region (or the whole model iteration), instead of disabling record streams entirely.

As a side note: in relation to this pytorch/pytorch#76861 (comment)
It would be interesting to understand what happens if we automatically insert wait_stream at the end of a region (or the whole model iteration), instead of disabling record streams entirely.

Thunder doesn't know anything about CUDA streams today.

As a side note: in relation to this pytorch/pytorch#76861 (comment)
It would be interesting to understand what happens if we automatically insert wait_stream at the end of a region (or the whole model iteration), instead of disabling record streams entirely.

Thunder doesn't know anything about CUDA streams today.

Fair point

Setting the environment variable from the command line or in thunder/__init__.py results in consistently better performance suggesting that the current approach in this PR doesn't quite work
TORCH_NCCL_AVOID_RECORD_STREAMS=1 torchrun --nproc_per_node=8 --nnodes=1 thunder/benchmarks/benchmark_litgpt.py --model_name Llama-2-13b-hf --compile thunder_cudnn --distributed_mode fsdp --shard_mode zero2 --bucketing_mode none --micro_batch_size 1 --global_batch_size 8

Average iter time: 722.36 ms

Setting the environment variable from the command line or in thunder/__init__.py results in consistently better performance suggesting that the current approach in this PR doesn't quite work
TORCH_NCCL_AVOID_RECORD_STREAMS=1 torchrun --nproc_per_node=8 --nnodes=1 thunder/benchmarks/benchmark_litgpt.py --model_name Llama-2-13b-hf --compile thunder_cudnn --distributed_mode fsdp --shard_mode zero2 --bucketing_mode none --micro_batch_size 1 --global_batch_size 8

Average iter time: 722.36 ms

Maybe the backward call is not affected by this decorator because it's a separate thread and setting the env variable in thunder/__init__.py works because then the side C++ thread to PyTorch's Autograd engine inherits the variable value.

Does this work, though, from the PyTorch source it would seem that it needs to be set for the process group:
https://github.com/pytorch/pytorch/blob/f343f98710dfa7305a873f558086c595a3c3d3d4/torch/csrc/distributed/c10d/ProcessGroupNCCL.cpp#L776

Right, and this needs to be set at the process group creation meaning in usual scripts before the init_process_group(backend="nccl") call.

This would help fix a lot of performance issues we have been seeing with large models/large batch sizes where we see memory thrashing. Thanks for working on this Ivan 🚀

Seems like legit CI failures in distributed. This seems a common thing
  File "/__w/1/s/thunder/core/module.py", line 142, in no_sync
    _sync_grads(self)
  File "/__w/1/s/thunder/distributed/__init__.py", line 142, in _sync_grads
    with tdist.distributed_c10d._coalescing_manager(group=process_group, async_ops=True) as cm:
  File "/usr/lib/python3.10/contextlib.py", line 142, in __exit__
    next(self.gen)
  File "/usr/local/lib/python3.10/dist-packages/torch/distributed/distributed_c10d.py", line 2079, in _coalescing_manager
    cm.append(work)  # type: ignore[possibly-undefined]
UnboundLocalError: local variable 'work' referenced before assignment

in these failures:
2024-06-04T13:07:07.0476853Z FAILED thunder/tests/distributed/test_ddp.py::CompileDDPTest::test_ddp_with_no_sync_grad_accumulation_executor_torch_bucket_size_in_mb_0_dataset_size_1 - RuntimeError: Process 0 exited with error code 10 and exception:
2024-06-04T13:07:07.0491884Z FAILED thunder/tests/distributed/test_ddp.py::CompileDDPTest::test_fsdp_with_no_sync_grad_accumulation_executor_torch_bucketing_block_zero2 - RuntimeError: Process 0 exited with error code 10 and exception:
2024-06-04T13:07:07.0499141Z FAILED thunder/tests/distributed/test_ddp.py::CompileDDPTest::test_fsdp_with_no_sync_grad_accumulation_executor_nvfuser_bucketing_block_zero2 - RuntimeError: Process 1 exited with error code 10 and exception:
2024-06-04T13:07:07.0506343Z FAILED thunder/tests/distributed/test_ddp.py::CompileDDPTest::test_ddp_with_no_sync_grad_accumulation_executor_nvfuser_bucket_size_in_mb_25_dataset_size_2 - RuntimeError: Process 0 exited with error code 10 and exception:
2024-06-04T13:07:07.0521375Z FAILED thunder/tests/distributed/test_ddp.py::CompileDDPTest::test_fsdp_with_no_sync_grad_accumulation_executor_nvfuser_bucketing_block_zero3 - RuntimeError: Process 0 exited with error code 10 and exception:
2024-06-04T13:07:07.0528651Z FAILED thunder/tests/distributed/test_ddp.py::CompileDDPTest::test_ddp_with_no_sync_grad_accumulation_executor_nvfuser_bucket_size_in_mb_25_dataset_size_1 - RuntimeError: Process 1 exited with error code 10 and exception:
2024-06-04T13:07:07.0536202Z FAILED thunder/tests/distributed/test_ddp.py::CompileDDPTest::test_ddp_with_no_sync_grad_accumulation_executor_torch_bucket_size_in_mb_25_dataset_size_2 - RuntimeError: Process 1 exited with error code 10 and exception:
2024-06-04T13:07:07.0543807Z FAILED thunder/tests/distributed/test_ddp.py::CompileDDPTest::test_fsdp_with_no_sync_grad_accumulation_executor_torch_bucketing_block_zero3 - RuntimeError: Process 0 exited with error code 10 and exception:
2024-06-04T13:07:07.0551037Z FAILED thunder/tests/distributed/test_ddp.py::CompileDDPTest::test_ddp_with_no_sync_grad_accumulation_executor_nvfuser_bucket_size_in_mb_0_dataset_size_1 - RuntimeError: Process 1 exited with error code 10 and exception:
2024-06-04T13:07:07.0558736Z FAILED thunder/tests/distributed/test_ddp.py::CompileDDPTest::test_ddp_with_no_sync_grad_accumulation_executor_nvfuser_bucket_size_in_mb_0_dataset_size_2 - RuntimeError: Process 1 exited with error code 10 and exception:
2024-06-04T13:07:07.0566267Z FAILED thunder/tests/distributed/test_ddp.py::CompileDDPTest::test_ddp_with_no_sync_grad_accumulation_executor_torch_bucket_size_in_mb_25_dataset_size_1 - RuntimeError: Process 1 exited with error code 10 and exception:
2024-06-04T13:07:07.0573911Z FAILED thunder/tests/distributed/test_ddp.py::CompileDDPTest::test_ddp_with_no_sync_grad_accumulation_executor_torch_bucket_size_in_mb_0_dataset_size_2 - RuntimeError: Process 0 exited with error code 10 and exception:

That's unfortunate that the error is coming from the PyTorch source code and is not reproducible with my build. I'll fix it.

Awesome @IvanYashchuk !


wasmplugin allows 'nil' value sha256

Please provide a description of this PR:
We used to allow the Sha256 field to be optional, in fact istio sets "nil" to the null sha256 value to bypass the xDS API checksum and reverts this special value to "" in the pilot-agent, see https://github.com/istio/istio/blob/ d14105866e811a925414e901b6386b3fbad4f800/pkg/wasm/convert.go#L217 .
We later changed the field to required in Update WasmPlugin code to work with non-optional sha256 #35608, but kept the pilot-agent but kept the compatible logic in the pilot-agent.
I think it makes sense to allow not setting valid sha256 values in scenarios like testing, so I submitted this PR: The special value was released in the istio validation logic

@YonkaFang: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
29fc09f765a9b8e98a048a86b541353d8f8f17f7
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes

Why set "nil" instead of just ""?

@howardjohn
Let me explain the origin of this matter.

Firstly, it's because envoy (go-control-plane) validates this field and requires it to be non-empty:
 if utf8.RuneCountInString(m.GetSha256()) < 1 {
     return RemoteDataSourceValidationError{
         field:  "Sha256",
         reason: "value length must be at least 1 runes",
     }
 }

Prior to https://github.com/istio/istio/pull/35608, the design in istio-api allowed sha256 to be empty. In order to pass the validation in go-control-plane, the Istio code would actually convert the empty value to the "nil" magic value and then convert it back in pilot-agent. However, https://github.com/istio/istio/pull/35608 may have considered this operation to be dirty and removed it. Therefore, even though Istio's validation logic allows this field to be empty, if the user actually sets it to empty, it will fail the validation in go-control-plane.

To solve the new conflict introduced in 2, and to support some lenient scenarios (such as testing) where a valid sha256 may not be necessary, I introduced the changes in this PR: users can choose to set sha256 to "nil" to achieve the effect of "ignoring sha256 validation".

I still don't get it. There is Istio API and envoy API.
Why would we ever need the Istio API to be "nil" when we can just make it
empty?
Then we can translate that to envoy however - that seems irrelevant?
On Thu, Jul 6, 2023, 7:11 PM YonkaFang @.***> wrote:

Why set "nil" instead of just ""?
@howardjohn https://github.com/howardjohn
Let me explain the origin of this matter.

Firstly, it's because envoy (go-control-plane) validates this field
and requires it to be non-empty:
if utf8.RuneCountInString(m.GetSha256()) < 1 {
    return RemoteDataSourceValidationError{
        field:  "Sha256",
        reason: "value length must be at least 1 runes",
    }
}

Prior to #35608 https://github.com/istio/istio/pull/35608, the
design in istio-api allowed sha256 to be empty. In order to pass the
validation in go-control-plane, the Istio code would actually convert the
empty value to the "nil" magic value and then convert it back in
pilot-agent. However, #35608
https://github.com/istio/istio/pull/35608 may have considered this
operation to be dirty and removed it. Therefore, even though Istio's
validation logic allows this field to be empty, if the user actually sets
it to empty, it will fail the validation in go-control-plane.
3.
To solve the new conflict introduced in 2, and to support some lenient
scenarios (such as testing) where a valid sha256 may not be necessary, I
introduced the changes in this PR: users can choose to set sha256 to "nil"
to achieve the effect of "ignoring sha256 validation".
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/45847#issuecomment-1624542367, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXLAJVDEOYENNQGS75LXO5V4RANCNFSM6AAAAAA2ADP7GQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

wait.. are we converting Istio API to envoy API but then sending it to
Istio agent instead of envoy... but still using envoy validation?
That is.. very odd
On Thu, Jul 6, 2023, 7:16 PM John Howard @.***> wrote:

I still don't get it. There is Istio API and envoy API.
Why would we ever need the Istio API to be "nil" when we can just make it
empty?
Then we can translate that to envoy however - that seems irrelevant?
On Thu, Jul 6, 2023, 7:11 PM YonkaFang @.***> wrote:

Why set "nil" instead of just ""?
@howardjohn https://github.com/howardjohn
Let me explain the origin of this matter.

Firstly, it's because envoy (go-control-plane) validates this field
and requires it to be non-empty:
if utf8.RuneCountInString(m.GetSha256()) < 1 {
    return RemoteDataSourceValidationError{
        field:  "Sha256",
        reason: "value length must be at least 1 runes",
    }
}

Prior to #35608 https://github.com/istio/istio/pull/35608, the
design in istio-api allowed sha256 to be empty. In order to pass the
validation in go-control-plane, the Istio code would actually convert the
empty value to the "nil" magic value and then convert it back in
pilot-agent. However, #35608
https://github.com/istio/istio/pull/35608 may have considered this
operation to be dirty and removed it. Therefore, even though Istio's
validation logic allows this field to be empty, if the user actually sets
it to empty, it will fail the validation in go-control-plane.
3.
To solve the new conflict introduced in 2, and to support some
lenient scenarios (such as testing) where a valid sha256 may not be
necessary, I introduced the changes in this PR: users can choose to set
sha256 to "nil" to achieve the effect of "ignoring sha256 validation".
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/45847#issuecomment-1624542367, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXLAJVDEOYENNQGS75LXO5V4RANCNFSM6AAAAAA2ADP7GQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@howardjohn
Let me briefly describe it:

Envoy does not allow it to be empty;

Istio wants a more lenient restriction and has already implemented it (see pkg/wasm/convert.go#L217), but ignored it in the Istio API validation;

Pilot-agent converts remote code to local code, and the xDS data actually sent to Envoy no longer includes sha256, so it is not limited by the validation logic in go-control-plane, as seen in pkg/wasm/convert.go#L241C3-L241C3:

    // Rewrite remote fetch to local file.
    vm.Code = &core.AsyncDataSource{
        Specifier: &core.AsyncDataSource_Local{
            Local: &core.DataSource{
                Specifier: &core.DataSource_Filename{
                    Filename: f,
                },
            },
        },
    }

@howardjohn
Let me briefly describe it:

Envoy does not allow it to be empty;
Istio wants a more lenient restriction and has already implemented it (see pkg/wasm/convert.go#L217), but ignored it in the Istio API validation;
Pilot-agent converts remote code to local code, and the xDS data actually sent to Envoy no longer includes sha256, so it is not limited by the validation logic in go-control-plane, as seen in pkg/wasm/convert.go#L241C3-L241C3:

    // Rewrite remote fetch to local file.
    vm.Code = &core.AsyncDataSource{
        Specifier: &core.AsyncDataSource_Local{
            Local: &core.DataSource{
                Specifier: &core.DataSource_Filename{
                    Filename: f,
                },
            },
        },
    }

None of this suggests the user facing Istio API needs to change.
Here is how it should work

User creates a WasmPlugin with sha256="". This already is supported
We send this to pilot-agent as a RemoteDataSource. What we set in Sha256 here is purely an implementation detail.
Agent resolves based on RemoteDataSource and rewrites it

IIUC the issue is (2) is that somewhere is calling .Validate() on it?
If so, the solution seems to be to convert "" to "nil" here https://github.com/istio/istio/blob/82c6704f85127bf7347a7b9af657b918443205e2/pilot/pkg/model/extensions.go#L232 perhaps?
Regardless, the user should never set "nil"

Validate

@howardjohn
Yes, our go-control-plane will call Validate during marshal to disallow empty sha256 values.
Previously, Istio had done this by changing empty sha256 values set by users to "nil". However, this behavior was removed in PR https://github.com/istio/istio/pull/35608. Currently, the simplest way I see to allow users to temporarily not set a valid sha256 value is to allow "nil" values in Istio's validation logic.

Under no circumstances should the API allow anything other than a real
sha256 (which maybe we should validate is a valid one?) or "". It should
never accept "nil". That is leaking internal hacks into the user facing API.
On Mon, Jul 10, 2023 at 4:25 AM YonkaFang @.***> wrote:

Validate
@howardjohn https://github.com/howardjohn
Yes, our go-control-plane will call Validate during marshal to disallow
empty sha256 values.
Previously, Istio had done this by changing empty sha256 values set by
users to "nil". However, this behavior was removed in PR #35608
https://github.com/istio/istio/pull/35608. Currently, the simplest way
I see to allow users to temporarily not set a valid sha256 value is to
allow "nil" values in Istio's validation logic.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/45847#issuecomment-1628773029, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXJBQFXEW7PINNLCRADXPPRD7ANCNFSM6AAAAAA2ADP7GQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

That

@howardjohn What do you think about retrieving the previous logic: change the "empty value" sha256 of istio-api allowed by Istio internally to "nil", which is semantically consistent and not exposed to users?

@YonkaFang Can you describe what you need to do?
As @howardjohn mentioned, use of empty sha256 is totally implementation specific.
In other words, ECDS from Istiod is targeted to be passed to Istio Agent, but not Envoy directly.
So, I don't think that use of Envoy validation logic is appropriate to validate ECDS which comes from Istiod.
FYI, there are also the other fields in ECDS which is optional in Istio API surface, but not in Envoy API surface.

@ingwonsong
This is not a suitable question, but a current fact: the istio API allows sha256 to be empty, but in reality it will be flagged as an error by the validation code in go-control-plane when istio performs content serialization, so it is actually not usable.
What I want to do:

Make the "istio API allowing sha256 to be empty" work.

Reason for 1: In some testing scenarios, requiring a valid sha256 input can be cumbersome.

go-control-plane will call Validate during marshal to disallow empty sha256 values.

@YonkaFang Can you navigate me to the code path you mentioned in the statement above?


Investigate refactor of histogram_to_array for better accuracy

Currently, the _histogram_to_array function does not use the midpoint of the bins to recreate the original dataset.
Investigate accuracy of the _histogram_to_array function currently in comparison to (which uses the midpoint):
def _histogram_to_array(self):
    # Extend histogram to array format
    bin_counts = self._stored_histogram['histogram']['bin_counts']
    bin_edges = self._stored_histogram['histogram']['bin_edges']
    is_bin_non_zero = bin_counts > 0
    bin_midpoints = (bin_edges[1:][is_bin_non_zero]
                     + bin_edges[:-1][is_bin_non_zero]) / 2
    hist_to_array = [
        [midpoint] * count for midpoint, count
        in zip(bin_midpoints, bin_counts[is_bin_non_zero])
    ]
    array_flatten = np.concatenate(hist_to_array)

    # the min/max must be preserved
    array_flatten[0] = bin_edges[0]
    array_flatten[-1] = bin_edges[-1]

    # If we know they are integers, we can limit the data to be as such
    # during conversion
    if not self.__class__.__name__ == 'FloatColumn':
        array_flatten = np.round(array_flatten)

    return array_flatten

@JGSweets is this still something we should look into?

It might improve its accuracy, but TBH unsure of the overall results.


"Self-driving" mode for set-up and adminstration

Make it possible for people to set up and use Clowdr without devs in the loop.

[ ] Admin manual / README
[ ] Set up a demo site that we can show people

This isn't finished, of course, but we're making progress on both items.  No need for Urgent any more.

We're working towards getting this back in the new UI. Closing this issue in favour of tracking in newer ones (inc. some of our internal ones)


International hotline phone numbers in app

Your Question
According to https://github.com/corona-warn-app/cwa-website/issues/755 the international prefix has been removed from the technical and teleTAN hotline numbers (see for instance https://www.coronawarn.app/en/faq/#who_can_help).
What is happening with the phone numbers stored in the app?
In Android the overflow menu (three dots) > App Information > Technical Hotline
shows the phone number
+49<PHONE_NUMBER>
Similarly
Have you been tested? NEXT STEPS > no TAN yet?
shows the phone number
+49<PHONE_NUMBER>
Related also to https://github.com/corona-warn-app/cwa-hotline/issues/5.

iOS PR https://github.com/corona-warn-app/cwa-app-ios/pull/1836
Android PR https://github.com/corona-warn-app/cwa-app-android/pull/2176

Internal Tracking ID: EXPOSUREAPP-2566 iOS
Internal Tracking ID: EXPOSUREAPP-4677 Android

@MikeMcC399, yes, we are aware of the issue. Thanks. DS

@MikeMcC399, yes, we are aware of the issue. Thanks. DS

Internal Tracking ID: EXPOSUREAPP-2566

Internal Tracking ID: EXPOSUREAPP-2566

+49 will be removed and wording will change slightly.

+49 will be removed and wording will change slightly.

PR https://github.com/corona-warn-app/cwa-app-ios/pull/1836

PR https://github.com/corona-warn-app/cwa-app-ios/pull/1836

Internal Tracking IDs:
EXPOSUREAPP-2566 iOS
EXPOSUREAPP-4677 Android

Internal Tracking IDs:
EXPOSUREAPP-2566 iOS
EXPOSUREAPP-4677 Android

Android PR https://github.com/corona-warn-app/cwa-app-android/pull/2176

Android PR https://github.com/corona-warn-app/cwa-app-android/pull/2176

In CWA 1.12.0 for Android this has been addressed.
To reproduce go through the following two sequences in the CWA app user interface:

three-dot overflow menu > App Information > Technical Hotline shows phone number "0800 7540001"
NEXT STEPS > No TAN yet? says "Call the nationwide hotline and request a TAN: 0800 7540002"

Both telephone numbers are now national telephone numbers as planned.

So if I understsnd correctly these hotline numbers work only from Germany?
Is there also a way to get a TeleTAN from outside Germany? Or is that considered a cornercase and not supported?

@ndegendogo

So if I understsnd correctly these hotline numbers work only from Germany?
Is there also a way to get a TeleTAN from outside Germany? Or is that considered a cornercase and not supported?

The main topic for this is https://github.com/corona-warn-app/cwa-documentation/issues/502 and I asked more or less the same question as you did in https://github.com/corona-warn-app/cwa-documentation/issues/502#issuecomment-778251940.

If somebody would like to check that the phone numbers have been changed to local numbers in the iOS 1.12.x app I would go ahead and close this issue. I guess that the menus in iOS are identical to Android, except maybe that "NEXT STEPS" is in mixed case?
Verification for Android

overflow menu (three dots) > App Information > Technical Hotline
shows the phone number
0800 7540001

Have you been tested? NEXT STEPS > no TAN yet?
shows the phone number
0800 7540002

@MikeMcC399
@ndegendogo
Yes, this is issue can be closed.
Both phone numbers shown as national numbers in iPhone

and we continue with  #502

@dsarkar
Thank you for checking! Now closing, as suggested and agreed.


Introduce version variables for erlang docs

Similar to what we have for Java & Collector already this pushes the versions used in erlang docs to the page front matter. This is only an intermediate step, in a further update we should have those taken from data/

Nice, but let's keep this DRY.. The version params should exist in a single file: content/en/docs/instrumentation/erlang/_index.md. All files in the section will have access to the params via the param shortcode.

cool, I was wondering the same, I guess java is doing that and I somehow missed it

@chalin fixed

Alright I did a fuckywucky with the refcache somehow in another PR, so the red in this PR is a false negative. I'm just going to merge it and then fix my mess up


iOS projects linker error

Hello Robert,
currently (Kha 8f4886e), my generated ios project fails to link because it can't find mouse related functions. I managed to fix it by just copying the Kha/Kore/Backends/OSX/Sources/Kore/Input folder to Kha/Kore/Backends/iOS/Sources/Kore.

Fixed it in exactly the same way. Thanks a lot!


Add preview deployment for Opening/Closing PRs

This builds previews to Cloudflare Workers for PRs and updates them as new commits are added. It also clears the Workers as commits are closed.
To setup, secrets for Cloudflare and Github need to be setup.

Key
Value

CF_ACCOUNT_ID
Cloudflare Account ID

CF_API_TOKEN
Cloudflare API Token (Use Manage Workers Preset)

CF_BASE_URL
Your worker subdomain (the "vladb" part in "vladb.workers.dev")

CF_ZONE_ID
Cloudflare zone ID

GH_BOT_TOKEN
A Github Token (with repo perms) needed for posting link comments

looks good, I'm going to leave this open until tomorrow and I'll come back and add the secrets


BF: Allow reading of FIF files with incorrect date

Reference issue
Fixes GH-7492.
What does this implement/fix?
Currently, FIF files that have an invalid birthday or measurement date set cannot be read, as an exception is raised (see #7492). This PR catches the exception, skips the entry (effectively adding it as None to the info dict), and emits a warning. This way, users can at least load the data, even though the metadata may then be partially incomplete.
Additional information
Tested with the problematic Cam-CAN data mentioned in #7492.
I need advise on how to best come up with a test for this.

I just discovered https://github.com/mne-tools/mne-python/blob/586a8711fc94048876ea23fdf5a638783770d50b/mne/io/meas_info.py#L1315-L1317
This should probably be adjusted too? Not sure what exactly it refers to – measurement date of the helium level? (whatever that means – supply level? pressure? temperature?)

certain meas_date which are not info['meas_date'] are meant to stay as
tuple of int. So not clear.

problem comes when you make a datetime object from these tuple of ints that
is bad.

I think a potential alternative would be would be to catch the exception here:
https://github.com/mne-tools/mne-python/blob/943dee405fcc68f985107a8f7c6912ee2adfa87a/mne/io/tag.py#L369-L371
and return None. I think that would cover all julian dates.

@bloyl ok, thanks, will look into this tomorrow :)

To test this, you could read a file with a legitimate date, change it to a bad date, save it (to a temp dir), then read it back in while catching the warning, and finally testing that the date was None. Seems pretty contorted, but if you tacked it onto an existing test that was already doing some of those steps, it might be worth it?

To test this, you could read a file with a legitimate date, change it to a bad date, save it (to a temp dir)

I was thinking about this but since dates are converted to datetime objects now before writing, I cannot write out "invalid" dates, I'm afraid

I have now followed a suggestion by @agramfort and created a very small raw file with an invalid birthday via MNE-Python 0.19; this is now included in the testing data at mne/io/tests/data.
When looking at how the measurement date was stored, I figured that apparently already in 0.19 and potentially even earlier (?) datetime objects had been used, and it's only the birthday for which a (YYYY, MM, DD) tuple was used, which lead to the issue I'm trying to solve here (i.e., invalid dates could end of in the metadata). Therefore, I'm limiting my adjustments and testing to the info['subject_info']['birthday'] field now.
This also made me believe that catching an exception when reading the data quite late, namely in meas_info.py, should be sufficient – I'm just doing this for the birthday now, anyway. You okay with that, @bloyl?

Thx @hoechenberger


fail positive on github action fails.

Commit Queue failed- Loading data for nodejs/node/pull/45573
✔  Done loading data for nodejs/node/pull/45573
----------------------------------- PR info ------------------------------------
Title      deps: V8: cherry-pick 2ada52cffbff (#45573)
Author     Michaël Zasso  (@targos)
Branch     targos:fix-45171 -> nodejs:main
Labels     build, v8 engine, needs-ci
Commits    1
 - deps: V8: cherry-pick 2ada52cffbff
Committers 1
 - Michaël Zasso
PR-URL: https://github.com/nodejs/node/pull/45573
Fixes: https://github.com/nodejs/node/issues/45171
Refs: https://github.com/v8/v8/commit/2ada52cffbff11074abfaac18938bf02d85454f5
Reviewed-By: Jiawen Geng
Reviewed-By: Richard Lau
Reviewed-By: Colin Ihrig
Reviewed-By: Yagiz Nizipli
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/45573
Fixes: https://github.com/nodejs/node/issues/45171
Refs: https://github.com/v8/v8/commit/2ada52cffbff11074abfaac18938bf02d85454f5
Reviewed-By: Jiawen Geng
Reviewed-By: Richard Lau
Reviewed-By: Colin Ihrig
Reviewed-By: Yagiz Nizipli
--------------------------------------------------------------------------------
   ⚠  Commits were pushed since the last review:
   ⚠  - deps: V8: cherry-pick 2ada52cffbff
   ℹ  This PR was created on Tue, 22 Nov 2022 08:21:45 GMT
   ✔  Approvals: 4
   ✔  - Jiawen Geng (@gengjiawen): https://github.com/nodejs/node/pull/45573#pullrequestreview-1189584648
   ✔  - Richard Lau (@richardlau) (TSC): https://github.com/nodejs/node/pull/45573#pullrequestreview-1190006137
   ✔  - Colin Ihrig (@cjihrig) (TSC): https://github.com/nodejs/node/pull/45573#pullrequestreview-1190051320
   ✔  - Yagiz Nizipli (@anonrig): https://github.com/nodejs/node/pull/45573#pullrequestreview-1191762773
   ✖  Last GitHub CI failed
   ℹ  Last Full PR CI on 2022-11-23T14:48:53Z: https://ci.nodejs.org/job/node-test-pull-request/48124/
- Querying data for job/node-test-pull-request/48124/
   ✔  Last Jenkins CI successful
--------------------------------------------------------------------------------
   ✔  Aborted `git node land` session in /home/runner/work/node/node/.ncuhttps://github.com/nodejs/node/actions/runs/3538908052
Originally posted by @nodejs-github-bot in https://github.com/nodejs/node/issues/45573#issuecomment-1326111158

It's not a false positive. I rebased and pushed after the last review.

Yes, but that's expected. Someone needs to submit a review after the push.

Isn't it because of this?

I reopened because the error was wrong, but I still think the failure was expected (Jenkins CI had a failure).

Yeah, "GitHub CI" is not very accurate because all it does is check the "status of the PR", which includes the Jenkins results.

But why did ncu say "Last Jenkins CI successful" when https://ci.nodejs.org/job/node-test-pull-request/48124/ is clearly red?

Another one: https://github.com/nodejs/node-core-utils/issues/691

I had a look and it's because of this part of the code:
https://github.com/nodejs/node-core-utils/blob/4ef0fe2607f3986f702bcd1ada244965cfcd4457/lib/pr_checker.js#L393-L410
It's actually the Jenkins CI check that is red. I wonder if we should remove this whole block. I don't know what kind of "old" checks we expect to be here.


Event list does not show correct date

Prerequisites

[ x] Put an X between the brackets on this line if you have done all of the following:

Checked the Quick Start documentation page and confirmed configuration is correct: https://marksie1988.github.io/atomic-calendar-revive/quickstart.html
Checked the FAQs on documentation page for common solutions: https://marksie1988.github.io/atomic-calendar-revive/faq.html
Checked that your issue isn't already filed: https://github.com/marksie1988/atomic-calendar-revive/issues?q=is%3Aissue

Describe the bug
Event List show only current date at first event. Next events in following line do not show any date info.
Expected behavior
Expecting the date of the event next to the description
Actual behavior:

[Screenshots
https://abload.de/img/screenshot2020-06-14agbjmx.jpg

Card Configuration
type: 'custom:atomic-calendar-revive'
entities: calendar.privates
name: Termine
maxDaysToShow: 14
`### Versions

HomeAssistant Version: all latest
Plugin Version:

So is the issue that these events shouldnt be showing under the 14th and should only be under the 13th?
If you have multiple events on one day, it is normal that the date will only appear next to the first event for that day,

Sorry, I think I was not clear on the description. I am using a caldav calendar entity (which works fine in HA). Events are extracted but all have the date set to the current date. There is an error in the date parsing function for a calddav event (maybe different from Google calendars?)

I have the same issue using caldav.
This Caldav item:
message: Bar
all_day: true
start_time: '2020-07-06 00:00:00'
end_time: '2020-08-03 00:00:00'
location: null
description: null
offset_reached: false
friendly_name: foo

Shows as  "All day, until July 19" and today is July 20. Another item that are from  July 23 -  July 25 is shown the same even though its a day in the future.

Thanks for the feedback, I will see if I can setup a caldav and hopefully will have some time to look at this as part of v2 release and see if there is a simple fix that could be implemented.
As this is designed for use with Google calendar I can't guarantee I will get it working but will try, have some good ideas around it to also include some other functionality.

I have now setup a NextCloud test server to have a look at this, this is now the only outstanding issue with v2.0

I just installed the very last version and the error remains, actually looks even more bizarre, every event is "all day", dates in the past etc. Apparently the script cannot handle date formats provided by caldav servers. In the HA mainpage my calendar dates are all correct thus no error on the caldav binding.
Screenshot below: German "vor 14 Stunden" means "14h ago"

Unfortunately I haven't had time to look at this properly yet. Ive been really busy with work.
I will look as soon as I get some time hopefully over the next week or two.

I can see that when an event uses caldav that the following is populated:
eventClass:
description: null
end: "2020-08-19T11:00:00+01:00"
location: null
start: "2020-08-19T10:00:00+01:00"
summary: "test NC"
uid: "dfb0d768-2be0-463c-bf73-bd958bc549ff"

This event happens between 10am and 11am on the 19th but actually when processed by Moment the dates change:
_endTime: v
_d: Mon Aug 17 2020 23:59:59 GMT+0100 (British Summer Time) {}
_isAMomentObject: true
_isUTC: false
_isValid: true
_locale: E {_calendar: {…}, _longDateFormat: {…}, _invalidDate: "Invalid date", _dayOfMonthOrdinalParse: /\d{1,2}(st|nd|rd|th)/, ordinal: ƒ, …}
_pf: {empty: false, unusedTokens: Array(0), unusedInput: Array(0), overflow: -2, charsLeftOver: 0, …}
__proto__: Object
_startTime: v
_d: Tue Aug 18 2020 00:00:00 GMT+0100 (British Summer Time) {}
_isAMomentObject: true
_isUTC: false
_isValid: true
_locale: E {_calendar: {…}, _longDateFormat: {…}, _invalidDate: "Invalid date", _dayOfMonthOrdinalParse: /\d{1,2}(st|nd|rd|th)/, ordinal: ƒ, …}
_pf: {empty: false, unusedTokens: Array(0), unusedInput: Array(0), overflow: -2, charsLeftOver: 0, …}
__proto__: Object

So between the card receiving the data and then processing it the date information is lost.

Ok i have now found the cause of this issue.
An event from Google will come in this format:
end:
    dateTime: "2020-08-20T11:00:00+01:00"
    timeZone: "Europe/London"

where as CalDav is like this:
end: "2020-08-19T11:00:00+01:00"

Google are adding an extra level to events that arent full day, this means that when there is no "dateTime" the card will assume that its an all day event, an all day event in Google is end.date however from caldav as you can see all events just show as end
I will add an additional check for this which should mitigate against this.

I can confirm that with your latest alpha branch 2.2.3 the caldav event are now properly displayed in the event list.
Thanks for your effort!

Awesome! Will try it out asap!
Thank you!

I think there are still some issues which is why I've not pushed it to the master yet.
Unfortunately I'm really busy preparing for an exam at the moment but hopefully I'll be back at it mid next week 🙂


Migrated VM has input endpoints which is not right since endpoints don't exist in ARM

I see that the migrated VM has input endpoints in the networkProfile which is incorrect since endpoints concept does not exist in ARM. What needs to be done instead is to create NSGs and restrict access for the equivalent endpoints. Azure only checks for networkInterface id in the networkProfile and discards everything else.
        "networkProfile" : {
          "networkInterfaces" : [{
              "id" : "[resourceId('Microsoft.Network/networkInterfaces','win2012kay_win2012kay_nic')]"
            }
          ],
          "inputEndpoints" : [{
              "endpointName" : "PowerShell",
              "privatePort" : 5986,
              "publicPort" : 5986,
              "protocol" : "tcp",
              "enableDirectServerReturn" : false
            }, {
              "endpointName" : "Remote Desktop",
              "privatePort" : 3389,
              "publicPort" : 61597,
              "protocol" : "tcp",
              "enableDirectServerReturn" : false
            }
          ]
        },

Thanks Kay for reporting this. Fixed and pushed.

@Ercenk We migrated this code to https://github.com/Azure/classic-iaas-resourcemanager-migration. Can you make sure any changes made here are submitted there as well?


2.3 Nightly build produces error when initializing system in TF documentation's Colab tutorial

System information

Have I written custom code: NO
TensorFlow installed from: pip (tf-nightly)
TensorFlow version: 2.3.0-dev20200605

Describe the current behavior
TPU won't initialize in colab using the nightly build.
Describe the expected behavior
Run the https://www.tensorflow.org/guide/tpu notebook successfully, as one would if using TF 2.2.
Standalone code to reproduce the issue

Load https://www.tensorflow.org/guide/tpu in colab.
Run !pip install tf-nightly in a new cell before running anything else.
Run the TPU initialization section of the notebook.
Observe the following error:

@jasonbrancazio
I have tried in  colab with TF nightly version (2.3.0-dev20200605) .Please, find the gist here.Is this expected behavior?.Thanks!

@ravikyram Yes, the InvalidArgumentError is the same error I experienced.

That indicates a version mismatch between your colab client and TPU worker. Is your TPU worker also nightly?

@rxsang I don't see how to determine without modifying the steps indicated above whether the TPU worker is using a nightly version of tf. Would you mind posting how to determine this?
I did see your trick here, which seems to be related to provisioning a worker at a certain version level rather than inspecting its properties: https://github.com/tensorflow/tensorflow/issues/34346#issuecomment-598399912
Regardless, I just retried the steps outlined in my bug report. I no longer see the error I reported.
Perhaps the default versions in colab notebooks are no longer mismatched.

@jasonbrancazio Looks like this was already resolved. I cannot reproduce the error with tf-nightly. Please check the gist here.
I am closing this issue as this was already resolved. Please feel free to reopen if I am mistaken. Thanks!


Instantiate abstract class Euclidean

Hi Yantao,
May I ask a question regarding the instantiation of the class Euclidean? Your code gives me such an error:

I am using Python 2.7 and Pytorch 0.3. Could you please let me know how to solve this problem? Thank you in advance!

Hi, it is because of the updating of The metirc-learn module. To be specific, it seems that this problem is caused by our code of "reid/metric_learning/euclidean.py" didn't override "score_pairs" abstract method (which is a new API) in "BaseMetricLearner" of "metric_learn.base_metric",  or we can use a "super call" in "reid/metric_learning/euclidean.py" to aviod it.


Add checks from ursula-inspec

Inspec checks from ursula-inspec have been added.
This includes mongodb, kvm, mysql, and rabbitmq.
This depends on https://github.com/blueboxgroup/ursula-inspec/pull/5
This is in conflict and needs to be rebased with https://github.com/blueboxgroup/ursula/pull/2632.

ok to test

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

retest

ok I've separated inspec call for kvm and nova-data in the nova-data role.


feat: allow Symfony6 + phpunit upgrade

This PR allows using this bundle with Symfony6. Until it is merged, you can use the fork:
"repositories": {
    "strangebuzz/easy-deploy-bundle": {
        "type": "vcs",
        "url": "git@github.com:strangebuzz/easy-deploy-bundle.git"
    }
},

Oops, this is already done in https://github.com/EasyCorp/easy-deploy-bundle/pull/127.


Firewall: 'iptables' finished with error:

The framework works great while using the rebinding strategy "First than second".
But if i try out the  "Multiple answers" strategy there occus an error the following error  'iptables' finished with error:  nil
As a result, no firewall rule is created and the requests are not blocked.
Can you give me a hint about what goes wrong?

This log message is misleading and in this case probably means no error ('nil') happened server side.
I assume you run Singularity on Linux with iptables server-side.
Did you set the interval to "1" second? This technique was successfully tested with this interval only.
Are you targeting your host or another host on the network? This technique was successfully tested against 'localhost' type of target specification only.
If targeting 'localhost', ensure that you set the target IP address to '<IP_ADDRESS>' on Windows and to '<IP_ADDRESS>' on Linux/macos.


[Bug]: (Mono) Failed to GetExport ( g_free )

All of the following criteria must be met

[X] All Requirements must be installed.
[X] Full Latest.log file included. If no file exists then leave this unchecked and state so.

All of the following are optional to answer

[X] Tried reinstalling the Game.
[X] Tried reinstalling MelonLoader.
[X] Tried restarting PC.
[ ] Was able to see the Start Screen.

Describe the issue.
On many Unity Mono games using Unity versions from around ~2019, MelonLoader cannot find the export g_free from mono.
I am running under Proton with the requirements installed (I followed the wiki).
I am unable to find any working Unity mono game in my games list, and coincidentally all appear to be using older Unity versions, whereas most newer Unity games do not use Mono or have native Linux support.
Additionally, I had to work around another issue, Failed to Load Mono Library! by copying MonoBleedingEdge/EmbedRuntime/mono-2.0-bdwgc.dll to MonoBleedingEdge/EmbedRuntime/mono.dll. For some reason all of these non-working games seem to have a mono.dll called mono-2.0-bdwgc.dll and I have no information about this but obviously this is a version compatibility issue and I am unsure if it's meant to be supported by MelonLoader or not.
What is clear is that my workaround is allowing some exports to be resolved but with the ones that work, it seems to be g_free.
When switching between Proton versions Proton is sometimes unable to load the dll I assume and it results in Failed to Load Mono Library! even with my workaround. It also does this for some even older mono.dlls (that I steal from other games) and I have attached logs trying each of these, with a fresh install of the game.
I have tested with a few mono games under Steam Proton 5.0-10 & 5.13-6 and none work correctly:

20 Minutes Till Dawn (the game I am trying to get MelonLoader to work for) which uses unity version 2019.4.21f1 (Latest.log)
Stacklands (
Latest.log)
Rounds - Fails on first export, mono_jit_init (Latest.log
)
Inscryption - Failed to load mono even with workaround (Latest.log)

All of these games also have the following folders in their MonoBleedingEdge/etc/mono folder: 4.5, 4.0, & 2.0
Did you attach your log file?

[X] Yes, I attached my log file to the text box above.
[ ] No, I could not find a log file at {Game_Directory}\MelonLoader\Latest.log

Okay so unfortunately I am clearly doing a lot of things wrong. Renaming mono.dll is not a workaround, it just causes more issues. I had gotten the impression trying to find workarounds that this was helping to find mono, but this is not the underlying issue. Closing and opening under a separate issue.


add link text but visually hide it

Fixes the Pa11y error of having a link with no link text
Looks like this has always been an issue, but doesn't usually get caught as the link is replaced with a different one when the users logged in status is determined. As @rcantin-w mentioned on Slack, It would appear that when pa11y ran this time, that status update took longer than normal and so this error was exposed.
I've added text to the link, but hidden it visually, so there is no change to how the page previously rendered.

Nice spot @rcantin-w and nice fix @gestchild 👍


mini-map incorrect and wonky after creating new graph

After creating a new graph, the mini-map still looks like it's relating to the previous graph I had open. See below...

Refreshing the page yields this:

And finally, zooming out reveals...

This might be what actually happened to me here: https://github.com/noflo/noflo-ui/issues/449
I'm willing to bet this is it. Somehow the mini-map and zoom setting of the graph area got in this state, which to my novice mind looked exactly like my graph being deleted.
I'll leave that issue open until someone with a better grasp on thing can repro this for themselves and rule out data loss in that other issue.

That would also explain how the undo button did not appear to do anything when https://github.com/noflo/noflo-ui/issues/449 happened

Noted here: https://github.com/the-grid/the-graph/issues/201

@forresto ah, my bad for duplicating issues then (I didn't make the connection)
what about the graph auto zooming in to the max setting making it appear as though everything disappeared? That's what messed me up so bad (thinking the graph was gone). Same issue, or side effect but separate?


Change c++_codegen_lib from build: protoc to build: all

this is a "backport" right?

LGTM

Btw, why exactly do we need this?

Got explanation offline.

@vjpai , @dgquintas  turns out explanations made offline are a bad idea because now I don't remember why we needed this and this causes #6011.   I'm tempted to revert, what would be the consequences?

Next import would fail.
I think I know how to fix this forever... By removing the need to create
the codegen stuff as libs. Going to amend #6092 to set the stage (and also
fix the bug you referred to)
On Thu, Apr 7, 2016, 7:44 AM Jan Tattermusch<EMAIL_ADDRESS>wrote:

@vjpai https://github.com/vjpai , @dgquintas
https://github.com/dgquintas turns out explanations made offline are a
bad idea because now I don't remember why we needed this and this causes
#6011 https://github.com/grpc/grpc/issues/6011. I'm tempted to revert,
what would be the consequences?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/5951#issuecomment-206936856


Please format file and commit before running validation - Error

Expected Behaviour
I expect that the project will build properly
Actual Behaviour
When building the project I get an error when building the AF Core Bundle module.  "aem-core-forms-components-master\bundles\core\src\main\java\com\adobe\cq\forms\core\components\internal\models\v1\aemform\AEMFormImpl.java' has not been previously formatted.  Please format file and commit before running validation! "
Reproduce Scenario (including but not limited to)
Build the maven project
Steps to Reproduce
Build the maven project
Platform and Version
Windows 10
Sample Code that illustrates the problem
Logs taken while reproducing problem

@tonijhanel You can find the code formatting rules in the eclipse-formatter.xml 0 file. The code formatting is automatically checked for each build. To automatically format your code, please run:
mvn clean install -Pformat-code

I suspect this may be due to a trailing character in end-line on Windows older versions. It works on Windows 11, and on linux/Mac based OS.
Thanks for reporting this. While this does not means that the repo has unformatted code, but some character insertion by Windows at EOL which is getting the format checker to fail. To unblock yourself, you can add -Dformatter.skip=true in the mvn command.


Fixed typo in Project References

Fixed typo. "timestamps" instead of "timestmaps".

Perfect, thanks


[release-v1.9] Update golang image to existing one

/cherry-pick main

/cherry-pick main

/cherry-pick main

/cherry-pick release-v1.10


Minimap Misaligned

Describe the bug
This was always an issue, even with the old version, but hoping you can help. I have my minimap on the bottom of my screen, x-370, y0. Even at y0, the minimap is not properly aligned with the bottom of the screen. When I look at moving the anchors in Elvui, it's like the frame itself is misaligned with the minimap (frame starts a few pixels below the minimap, and ends a few pixels from the top). This drives me crazy, would love a way to fix the alignment.
To Reproduce
Steps to reproduce the behavior:

Move Minimap to bottom of screen
Go crazy as you can't reach the bottom of screen

Expected behavior
Screenshots
https://imgur.com/a/KmxO6cr
Version (please complete the following information):

Version ElvUI [13.76]
Version Elvui_Enhanced [5.1.1]

Additional context

Hello @Grayfox2325,
thank you for thus report. I could reproduce it and will take a look into.

Fixed in v5.1.2


Ansible error

Getting following error
[WARNING]:  * Failed to parse /Users/xxx/Documents/Sources/kubernetes/hkube/kubespray/inventory/mycluster/hosts.ini with ini plugin:
/Users/xxx/Documents/Sources/kubernetes/hkube/kubespray/inventory/mycluster/hosts.ini:4: Expected key=value host variable assignment, got: x.x.x.x.x
[WARNING]: Unable to parse /Users/xxx/Documents/Sources/kubernetes/hkube/kubespray/inventory/mycluster/hosts.ini as an inventory source
[WARNING]: No inventory was parsed, only implicit localhost is available
Hosts are not found over the inventory. Any suggestions?

Hi! Could you please share your config.json file?

{
"hcloud_token": "[redacted]",
"hcloud_user_sshkey_name": "vsc",
"hcloud_server_type": "cx11",
"hcloud_location": "fsn1",
"hcloud_name": "k8s",
"hcloud_count": "6"
}%
Here it is.. Thanks for having a look into it.

Hi @vschwaberow
I have updated the tool. Issue was because of kubespray ansible playbook changes. Sorry fro delay(

Many thanks. I will test it.


Normalized Hamming Distance

It would be better to have a normalization options in distance metric for BCR support. Still not clear on how to use the abstract class DistanceCalculator (tutorial could help)

Pinging @ktpolanski, who added the Hamming Distance Feature: What do you think about the normalization?

Regarding the DistanceCalculator: What's your question in particular? I think it should be feasible to implement a custom distance calculator that inherits from the abstract base class by looking at the examples and docstrings in metrics.py.

Does normalisation imply dividing by the length of the sequence? If so, then that puts us pretty close to what Dandelion does, no?

Does normalisation imply dividing by the length of the sequence? If so, then that puts us pretty close to what Dandelion does, no?

This would put it more in line with what immcantation's ShaZam does. Both scirpy and dandelion groups the sequences by distance first before performing the calculations, hence doesn't require length normalization.
The normalization in ShaZam is done as follows:
if (normalize == "len") {
   dist_mat <- dist_mat / seq_length

for dist_mat, they use a sliding window approach to bin each sequence into 5mers (replacing gaps with Ns, and padding Ns to the first and last 5mer to get the size the same), and then hamming distance is calculated for each pair of 5mers in order. The total distance is then sumed, and subsequently divided by sequence length according to the function above.
This should allow BCRs with different lengths to be grouped as a clonotype if they pass the similarity cut-off, but keep it a substitution-only context. immcantation reccomends a model-based approach for the cut-off, by looking for bimodal pattern of the distribution of the normalized hamming distance, but also leaves it up to the user to define a manual cut-off based on visual inspection of the histogram.
It's frequently used and I can understand its appeal as it allows for more relaxed/unbiased grouping and discovery of potential related BCR patterns that use the same V- and J-genes. It does "violate" the same length requirement for BCR SHM that textbooks teaches us but you could potentially argue it's due to technical things like sequencing error.
An easy way to do all this is to parse to AIRR format and access the immcantation tools directly, or parse to dandelion where wrappers for these immcantation tools are available, and then read it back to scirpy. Or you could try and implement it in some fashion here but would require a new class to handle it.

I think we're all talking about slightly different things. If we take the Hamming distance and divide it by sequence length, we'll obtain a "percent of mismatches" measure, which is what dandelion does. That is, if this is what OP meant by "normalised Hamming".


Migrate archived cards

Right now archived cards are not migrated as nextcloud can not deal with more than e.g. 2000 archived cards-

Maybe a good idea would be to allow to set filters for cards which should not be migrated (e.g. no description, no checklists etc.)


support cursor and offset

umm... test is passed in local environment. test depends to master branch of this repo. CI is failed, but it is correct.


sbgemm support for ARM Neoverse N2

#3671

Thank you very much for your contribution.
I notice that the ncopy and tcopy sources do not appear to have anything neoverse-specific in them, so they could probably be renamed to their unroll factor suffix and/or reused for other broadly similar cpus. (And sbgemm_beta is probably identical to the generic sgemm_beta - or at least I do not see why it could not be - so we could just reference that in the KERNEL file, but a bit
of redundancy does not hurt.)


Allow skipping enums when saving

US-style crosswords typically do not provide enums.

Added with v0.24


Refactor tests to not use Ops.ALU

Remove op, arg hack from ops.py
Update tests to not use Ops.ALU, but the actual op (which used to be the arg)
regenerate dataset

I regenerated the dataset with extra/optimization/generate_dataset.sh, just saw that the current dataset is much smaller than the previous on master, will look into why.

dataset seems too small
https://github.com/tinygrad/tinygrad/actions/runs/11685310452/job/32538457601?pr=7553 showed 259 rows only. it should have a few thousands

@chenyuxyz yeah I'm looking into why it's so small

thanks for the help to improve dataset gen, will merge #7554 if that works.


Resillience and Future-proof profiles for the repository workbench of the conformance test suite

This issue proposes two new optional profiles for the conformance test suite.

Resilience tests that the technology under test can handle badly formatted events and REST payloads.

These payloads should be ignored at minimal cost

Future-proof tests that the technologgy under test can cope with extended events and REST payloads that are coming from a possible future release of egeria.

These payloads should be processed, ignoring the additonal fields, if understood.
If the payloads represent a new command then it should be ignored.

We should keep this open - it is still a valid requirement

We should keep this open - it is still a valid requirement

We should keep this open - it is still a valid requirement


Release with no README?

When I download the new release of bungiesearch, this happens:
    Traceback (most recent call last):
      File "<string>", line 20, in <module>
      File "/private/var/folders/yp/ddctgj6s3vv0wgkm57b2w4040000gn/T/pip-build-pR13wb/bungiesearch/setup.py", line 11, in <module>
        with open(join(dirname(__file__), 'README.md')) as f:
    IOError: [Errno 2] No such file or directory: '/private/var/folders/yp/ddctgj6s3vv0wgkm57b2w4040000gn/T/pip-build-pR13wb/bungiesearch/README.md'

I downloaded the compressed folder, opened it up, and, indeed, the README has disappeared. Do you have any idea why this may have happened?

Hum, no I don't know how that could have happened. I'll have to check that in like twelve hours, sorry.

Thanks for finding that. Please use version 1.2.1 instead. It's already on Pypi too.


website should have a dedicated download page

as a user wanting to download NHSbuntu
I should be able to click on a download tab
and see the available downloads, including current stable x64, 32bit, ARM, and virtualbox image/vagrant boxen

Duplicate of #26
Closing


download pretrained model

Thank you for the great work. Is download link for pretrained model expired? Is there any alternative way to download the pretrained model? Thanks!

please see https://github.com/vlkniaz/ThermalGAN/issues/4

Not able to download pre-trained weights using this link: http://zefirus.org/datasets/models/ThermalGAN/ThermalGAN.pth.
It says Page not Found.


Download hadoop only if hdfsTest is run

ack

[Current coverage][cc-pull] is 79.75%

Merging [#3509][cc-pull] into [master][cc-base-branch] will decrease coverage by -8.14%

@@             master      #3509   diff @@
==========================================
  Files          1166       1166
  Lines         39492      36025   -3467
  Methods           0          0
  Messages          0          0
  Branches       6435       6240    -195
==========================================
- Hits          34711      28731   -5980
- Misses         4679       4994    +315
- Partials        102       2300   +2198

3 files (not in diff) in ...in/java/io/crate/udc were modified. more

Misses +2
Partials +5
Hits -11

3 files (not in diff) in ...icsearch/action/bulk were modified. more

Misses +5
Partials +24
Hits -41

1 files (not in diff) in ...elasticsearch/action were modified. more

Misses +5
Partials +16
Hits -29

1 files (not in diff) in ...va/org/elasticsearch were modified. more

Partials +7
Hits -11

2 files (not in diff) in ...io/crate/rest/action were modified. more

Misses +4
Partials +5
Hits -12

2 files (not in diff) in ...te/planner/statement were modified. more

Partials +6
Hits -52

4 files (not in diff) in ...r/projection/builder were modified. more

Misses -3
Partials +2
Hits -8

11 files (not in diff) in ...e/planner/projection were modified. more

Misses +36
Partials +53
Hits -94

9 files (not in diff) in ...ate/planner/node/dql were modified. more

Misses -17
Partials +33
Hits -70

3 files (not in diff) in .../crate/planner/fetch were modified. more

Misses +3
Partials +8
Hits -15

Powered by Codecov. Last updated by [4a7fdc3...19b6401][cc-compare]
[cc-base-branch]: https://codecov.io/gh/crate/crate/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/crate/crate/compare/4a7fdc3411cfca27fd16b7e434e081f9e5d5efc5...19b6401341399b4e2e791836f3e4ea01e9e34428
[cc-pull]: https://codecov.io/gh/crate/crate/pull/3509?src=pr


Adding operations on keypoints/landmarks?

This tool is awesome, especially for the elastic distortion function. Is is possible to add operations on given keypoints/landmarks, which means the inputs and outputs are images and corresponding points? This is helpful for alignment problems.

Hi, thanks for opening the issue.
I am not quite sure what you mean. Could you elaborate a little? Maybe with some code of how you'd think such an operation would work with Augmentor or maybe some example input and output images?

Hi, thank you for replying.
 Now I want to get more labeled images by image augmenting, for training a neural network. However, after the operation, the key-points will move and I can't get their positions on new images. So is it possible to do the same operation(rotation, affine transformation, etc) to the key-points as well, which means the input could be a pair (input_image, key_points) and the output is a pair (output_image, key_points) ?
Maybe the code will look like this:
import Augmentor
p = Augmentor.Pipeline("/path/to/input/label/file", "/path/to/output/label/file")
p.sample(10000)

and the label file may look like this:
/path/to/image1  key_pt1_x, key_pt1_y, key_pt2_x, key_pt2_y ...
/path/to/image2  key_pt1_x, key_pt1_y, key_pt2_x, key_pt2_y ...
...

so the augmentor reads the key-points with each image, augments the images, and generates an output label file which contains all the generated images and their key-points. Have I made myself clear?
You may have a look at this tool: imgaug
This tool augments images with basic operations, with key-points preserved. While I love the elastic distortions in your augmentor and wish it could be better. Many thanks if you would consider this.

Hi, ok I see what you are saying now. Well currently that won't be possible because I use PIL as a backend for most of the image operations. However, I do plan on replacing PIL as a dependency in a future update, and use only numpy for the image manipulations, which would make it possible to implement what you are asking for. When I do this, I will add this feature. I can't really give you a timeline on when that might be, unfortunately.
M.

This tool is fantastic. I especially like the piping design and randomization of this system. After reading the document, however, I find that I also need to operate the key-points of annotation.
I am very much looking forward to adding this feature to Augmentor in the near future, which will be a very important step in data generation.

Yeah, the tool looks good and I really like the interface. Would be great to have 2d points and bounding boxes augmentation support like you can find in imgaug or fastai libraries. The later one operates with 2d tensors directly.

Hi @devforfu, right now I have no plans to add bounding boxes or the like to Augmentor. It may happen in future, but it's not really a priority at the moment. 2D points and bounding boxes would be nice features to have, so I may try to implement them at some point however!


How to run from worker thread?

Hello, I've included the Estimote Android SDK in a React Native Android app. The problem though is that the SDK appears to require being run on the main thread rather than a worker thread (where React Native native modules are run from).
Is there some way to include the SDK as a native module for React Native android? Or at least some way to get the SDK running from a worker thread (and I can bundle it as a native module for RN Android from there)?
Why does the SDK require being executed on the main thread? If the SDK was open source this would be much simpler to understand.
This is the error I get:
Estimote SDK 1.0.3
Exception in native call
java.lang.RuntimeException: Can't create handler inside thread that has not called Looper.prepare()
        at android.os.Handler.<init>(Handler.java:200)
        at android.os.Handler.<init>(Handler.java:114)
        at com.estimote.coresdk.service.BeaconManager$IncomingHandler.<init>(BeaconManager.java:1008)
        at com.estimote.coresdk.service.BeaconManager$IncomingHandler.<init>(BeaconManager.java:1008)
        at com.estimote.coresdk.service.BeaconManager.<init>(BeaconManager.java:316)
        at com.estimoteTeeth.EstimoteTeethManager.<init>(EstimoteTeethManager.java:21)
        at com.estimoteTeeth.EstimoteTeethModule.<init>(EstimoteTeethModule.java:36)
        at com.estimoteTeeth.EstimoteTeethPackage.createNativeModules(EstimoteTeethPackage.java:18)
        at com.facebook.react.XReactInstanceManagerImpl.processPackage(XReactInstanceManagerImpl.java:958)
        at com.facebook.react.XReactInstanceManagerImpl.createReactContext(XReactInstanceManagerImpl.java:879)
        at com.facebook.react.XReactInstanceManagerImpl.access$600(XReactInstanceManagerImpl.java:110)
        at com.facebook.react.XReactInstanceManagerImpl$ReactContextInitAsyncTask.doInBackground(XReactInstanceManagerImpl.java:214)
        at com.facebook.react.XReactInstanceManagerImpl$ReactContextInitAsyncTask.doInBackground(XReactInstanceManagerImpl.java:193)
        at android.os.AsyncTask$2.call(AsyncTask.java:288)
        at java.util.concurrent.FutureTask.run(FutureTask.java:237)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
        at java.lang.Thread.run(Thread.java:818)

Hello @c-h-
Sorry for the late response. We didn't prepare our SDK to be interoperable with React Native yet. We need to apply proper fixes and change architecture a little bit to match such cases. I'll keep you informed about the progress - maybe not this month, but in a close future  :)
Cheers!

Thanks @pawelDylag I'll be watching in anticipation!


var2 in SRCSRVTRG isn't translated to correct path

I try to SourceLink our code hosted in self-hosted GitBlit repository, but I don't get correct URL generated into my PDB files. My FAKE target looks like this:
p.CreateSrcSrv "https://gitserver/raw/ABC%2Fdef.git/{0}/%var2%" repo.Revision (repo.Paths files)

The generated *.srcsrv file contains correct URL:
SRCSRVTRG=https://gitserver/raw/ABC%2Fdef.git/abf8cc13265b3e5aeb2aed146a970ba9f89e05b8/%var2%

But the resulting PDB file is indexed with incomplete URL. Output from srctool.exe:
[file1.cs] trg: https://gitserver/raw/ABCvar2%
[file2.cs] trg: https://gitserver/raw/ABCvar2%
...

All indexed files have wrong URL. Is the percent character in my path causing the problem or is there any common problem with GitBlit URLs?

Sorry for the delay. I think that can be taken care of with Uri.EscapeDataString. I created .CreateSrcSrvEscaped that does just this. It will be in the next build.


Location sensor

Don't know why but this pull request does not have the latest changes related to isGpsEnabled() function. I'll close this one down and create a new one from the same branch.

Don't know why but this pull request does not have the latest changes related to isGpsEnabled() function. I'll close this one down and create a new one from the same branch.


M> (G) Comparisons with Other High Throughput Scalable Blockchains

In my outreach attempts to grow the RChain community, I'm often faced with questions as to how RChain compares to other High Throughput scalable blockchains like EOS, Hashgraph, Zilliqa, Red Belly Blockchain.
I think it would be beneficial to have a simple comparison table to compare between potential competitors in RChain's space similar to the Comparison of Blockchains Architecture Documents which was really well done. This is a question frequently asked and I believe it will be greatly beneficial in highlighting advantages of RChain like concurrency.
I have compiled some of the whitepapers of upcoming competitors below for anyone who wants to take on this task.

EOS : https://github.com/EOSIO/Documentation/blob/master/TechnicalWhitePaper.md

HASHGRAPH : http://www.swirlds.com/downloads/SWIRLDS-TR-2016-01.pdf

ZILLIQA : https://docs.zilliqa.com/whitepaper.pdf https://docs.zilliqa.com/positionpaper.pdf

RED BELLY BLOCK CHAIN : http://poseidon.it.usyd.edu.au/~concurrentsystems/doc/ConsensusRedBellyBlockchain.pdf

Feel free to add any others like NEO or even solutions like Plasma just for a quick side by side comparion.

This is a great idea and is something we have in the plans for Marketing. @Mervyn853
I've added this to the "Marketing" project and if you wanted to start the table that would be great!
let me know what your thinking and I'll help where I can

Hey Patrick,
As I come from a non-technical finance background, it might take me awhile to work through the whitepapers. Will see what I can come up with.
Just thought that this would be useful for outreach / marketing, so anyone who might be interested, feel free to take on this issue!

Hmm, ok I will add it to the content ideas sheet and will work on getting some people onto it.

Hey Guys,
I will join you Mervyn i found comparision chart on ICON 's website we can have kickstart with this.

Side-by-Side Comparison of Blockchains --> contribute, offer comments,
where you see fit
https://docs.google.com/spreadsheets/d/1fbh37xWa898raYm0NTgI4XL23hmI6ndCsyNz2_QhOIw/edit?usp=sharing
On Thu, Nov 23, 2017 at 10:11 PM, Nik<EMAIL_ADDRESS>wrote:

Hey Guys,
I will join you Mervyn i found comparision chart on ICON 's website we can
have kickstart with this.
[image: comparision]
https://user-images.githubusercontent.com/4531201/33194076-3b770778-d09b-11e7-8705-bd8d93f65dcc.PNG
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rchain/Members/issues/180#issuecomment-346733429, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGZmhsKVCVzm7W1cgHRU4KgkymKCOUJtks5s5jPfgaJpZM4Qnk2R
.

--
Jacob Bassiri-Tehrani, MBA
(516) 458-7439

Really great stuff guys! @jbassiri thanks for the quick response!

Well done! I'm going to add what I know about it, just as I'm just studying this.

This is what I have so far please let me know what you think and when ever you have updated the table to complete it  I[Comparison Table.pdf]
Comparison Table.pdf

@ValeBF great work

Closing this due to inactivity, and because a Competitive Intelligence WG is taking over most of this area of concern.


Build with go-1.21 and use slog instead of zap for logging

Codecov Report

Merging #122 (1873788) into master (1346cc6) will decrease coverage by 0.14%.
The diff coverage is 32.14%.

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

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##           master     #122      +/-   ##
==========================================
- Coverage   65.39%   65.25%   -0.14%
==========================================
  Files          10       10
  Lines        1491     1491
==========================================
- Hits          975      973       -2
- Misses        332      333       +1
- Partials      184      185       +1

Files Changed
Coverage Δ

pkg/service/ipam-service.go
46.84% <32.14%> (ø)

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


1420C0CF:SSL routines:ssl_write_internal:protocol is shutdown error

Hi all,
This is very likely to be NOT a bug with this package, but rather some issue with my own setup or the setup of the imap server of our client, but I was wondering if anyone has come accross this before and could provide any suggestions on which way to go?
I've tried a bit of basic googling but nothing seems to make much sense to me.
ErrorException {#4936
  #message: """
    fwrite(): SSL operation failed with code 1. OpenSSL Error messages:\n
    error:1420C0CF:SSL routines:ssl_write_internal:protocol is shutdown
    """
  #code: 0
  #file: "/home/forge/my-cool-laravel-app.com/releases/20210316094131/vendor/webklex/php-imap/src/Connection/Protocols/ImapProtocol.php"
  #line: 307
  #severity: E_WARNING
  trace: {
    /home/forge/my-cool-laravel-app.com/releases/20210316094131/vendor/webklex/php-imap/src/Connection/Protocols/ImapProtocol.php:307 { …}

  }
}

The relevant call from ImapService is like this:
$messagePage = $folder->query(config('imap.null_charset') ? null : 'UTF-8')
                                          ->whereSince($dateRange['start'])
                                          ->whereBefore($dateRange['end'])
                                          ->setFetchFlags(false)
                                          ->setFetchBody(false)
                                          ->leaveUnread()
                                          ->limit($limit, $page)
                                          ->get();

Hi @robtesch ,
sorry for the late response. Do you have access to the "mail server" logs?
Best regards,

Unfortunately not. I have recently changed our whole IMAP setup to use "overview" method instead of complex queries like above, and so far things seem to be a bit better. I will let you know if this issue resurfaces.

Wait, so this isn't a "startup" error, but rather an error which occurs "randomly"?

Well, we have a lot of customers, and only a small percentage of those use IMAP as their email provider, and only a small percentage of those were facing this issue. The main one who we noticed this issue with is no longer a customer (because we simply could not connect to their server anymore... We used to be able to), so we are not entirely sure if the issue remains or not.

But, to be clear, I wouldn't consider it a "startup" issue, since we were able to successfully do $client->connect() first without any errors.

I'm sorry I don't have a definit answer.. But could it be a general connection issue (routing between the servers) or a rate limit of some sort which simply "kills" the connection?
Have a great weekend,

I will report back if I have anything new. Thanks for taking the time to
look at this.
On Sat, 19 Jun 2021, 16:38 Webklex, @.***> wrote:

I'm sorry I don't have a definit answer.. But could it be a general
connection issue (routing between the servers) or a rate limit of some sort
which simply "kills" the connection?
Have a great weekend,
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Webklex/laravel-imap/issues/397#issuecomment-864421859,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHH7VGJ4QHDOOLBIBHCI2NTTTS2YXANCNFSM4ZIL3YUA
.

Hi @robtesch ,
I'm closing this issue as of now.
Please head over to webklex/php-imap and create a new issue if the problem persists.
Best regards,


Using relative submodule paths

The repo supports being fetched with either the ssh protocol, or with https.
The submodules, however, are hard-coded right now to use ssh protocol. If you try to fetch the repo with https, and don't have github ssh keys configured, then you won't be able to grab the submodules unless you do temporary surgery in your .git directory.
Apparently you can do relative submodule URLs though: https://stackoverflow.com/questions/32317365/multiple-urls-of-git-submodule-per-remote-submodules
It sounds like it could be a good idea, but I would like someone who knows what they're doing with submodules to chime in.

I am a bit confused, aren't the submodules private repositories
on GitHub and thus require SSH keys for auth to fetch anyway?

On GitHub, auth for the https protocol is done via the gh program. It does not require an ssh key to be configured on your account. If submodules are configured to use https, they will also auth with the gh program.


implement cost_and_stats_calculator

Let Stat be the base class of TableStat
Move some variables and functions inside Cost class to avoid linking problem
Add cost_and_stats_calculator_test with a simple test case of testing the seqscan

Coverage decreased (-72.9%) to 0.0% when pulling 7446b0849e4f76e4d801b2824903d62315157a06 on AllisonWang:costandstats into 8ee0c0c5741a63fed4f1df8b7eebbd34cd639aed on cmu-db:master.

Coverage decreased (-72.9%) to 0.0% when pulling 7446b0849e4f76e4d801b2824903d62315157a06 on AllisonWang:costandstats into 8ee0c0c5741a63fed4f1df8b7eebbd34cd639aed on cmu-db:master.

@bechob What is the status of this? There hasn't been any updates in two weeks.

Coverage decreased (-72.9%) to 0.0% when pulling a63048b21eaaa1056cbc498382427cb68de7927c on AllisonWang:costandstats into 8ee0c0c5741a63fed4f1df8b7eebbd34cd639aed on cmu-db:master.

Coverage decreased (-72.9%) to 0.0% when pulling d9468827c41dffd07a79b984d161938b7592abec on AllisonWang:costandstats into 8ee0c0c5741a63fed4f1df8b7eebbd34cd639aed on cmu-db:master.

Coverage decreased (-72.9%) to 0.0% when pulling d9468827c41dffd07a79b984d161938b7592abec on AllisonWang:costandstats into 8ee0c0c5741a63fed4f1df8b7eebbd34cd639aed on cmu-db:master.

Coverage decreased (-72.9%) to 0.0% when pulling d9468827c41dffd07a79b984d161938b7592abec on AllisonWang:costandstats into 8ee0c0c5741a63fed4f1df8b7eebbd34cd639aed on cmu-db:master.

Coverage decreased (-72.9%) to 0.0% when pulling d9468827c41dffd07a79b984d161938b7592abec on AllisonWang:costandstats into 8ee0c0c5741a63fed4f1df8b7eebbd34cd639aed on cmu-db:master.

Coverage decreased (-75.2%) to 0.0% when pulling 61347b29bd72a271980934e5efc1c8c03bbddd84 on AllisonWang:costandstats into 570cc8ecf2e8b7b9b342e581da6b466d0ef6f1ac on cmu-db:master.

Coverage decreased (-10.2%) to 64.937% when pulling 37a326a21befbc051298d1fb15a47351fb2c1a7d on AllisonWang:costandstats into 570cc8ecf2e8b7b9b342e581da6b466d0ef6f1ac on cmu-db:master.

Coverage decreased (-10.2%) to 64.922% when pulling 2f08dfcb4b7de98920308952933015d943750e23 on AllisonWang:costandstats into 570cc8ecf2e8b7b9b342e581da6b466d0ef6f1ac on cmu-db:master.

Coverage decreased (-75.2%) to 0.0% when pulling 2f08dfcb4b7de98920308952933015d943750e23 on AllisonWang:costandstats into 570cc8ecf2e8b7b9b342e581da6b466d0ef6f1ac on cmu-db:master.

Coverage decreased (-75.2%) to 0.0% when pulling 2f08dfcb4b7de98920308952933015d943750e23 on AllisonWang:costandstats into 570cc8ecf2e8b7b9b342e581da6b466d0ef6f1ac on cmu-db:master.

Coverage decreased (-0.06%) to 75.101% when pulling e2bdfc03b11fb0bba5eecc5f4147fe483b4018d5 on AllisonWang:costandstats into 570cc8ecf2e8b7b9b342e581da6b466d0ef6f1ac on cmu-db:master.

Coverage decreased (-0.1%) to 75.061% when pulling 2cd188fca2e5aeaadfbc49b872623b8bd1ce714b on AllisonWang:costandstats into 570cc8ecf2e8b7b9b342e581da6b466d0ef6f1ac on cmu-db:master.

Coverage decreased (-0.1%) to 75.059% when pulling 0b2f79e183a9f356ea793980968701410e6945c5 on AllisonWang:costandstats into 570cc8ecf2e8b7b9b342e581da6b466d0ef6f1ac on cmu-db:master.

Coverage decreased (-0.06%) to 75.062% when pulling bebff0ce0183281be87e593ca527ff1829384a0c on AllisonWang:costandstats into 924578f17affc2b6bbdc5e7ada67a7d869e7015e on cmu-db:master.

Coverage decreased (-0.2%) to 74.941% when pulling bebff0ce0183281be87e593ca527ff1829384a0c on AllisonWang:costandstats into 924578f17affc2b6bbdc5e7ada67a7d869e7015e on cmu-db:master.

@hzxa21 Could you review this PR? Thanks!

Coverage decreased (-75.1%) to 0.0% when pulling ae313922d8ecb6cadf2ee75f639f4cae981801ff on AllisonWang:costandstats into 924578f17affc2b6bbdc5e7ada67a7d869e7015e on cmu-db:master.

Coverage decreased (-75.1%) to 0.0% when pulling 70bbe932f7bff1d47303cb1d4254cba346a7f398 on AllisonWang:costandstats into 924578f17affc2b6bbdc5e7ada67a7d869e7015e on cmu-db:master.

Coverage decreased (-0.08%) to 75.047% when pulling 70bbe932f7bff1d47303cb1d4254cba346a7f398 on AllisonWang:costandstats into 924578f17affc2b6bbdc5e7ada67a7d869e7015e on cmu-db:master.

@bechob @AllisonWang I will merge this after the build passes.

I took a quick look over this and noticed a few files that don't adhere to formatting guidelines. Please run clang-format on the files that were changed.

Coverage decreased (-0.2%) to 75.047% when pulling 0dd8cf104d87a0c3ff4816f834742b83425d98b1 on AllisonWang:costandstats into 597d05e358e717179cfafb949f369ff6ec5418cc on cmu-db:master.

Coverage decreased (-0.2%) to 75.059% when pulling 6f2ff469c510496ced36124350d5c49e6945d97a on AllisonWang:costandstats into 88e33b64a964188d0b79c6204ee4c21d468af9bc on cmu-db:master.

Coverage decreased (-0.2%) to 75.028% when pulling 6f2ff469c510496ced36124350d5c49e6945d97a on AllisonWang:costandstats into 88e33b64a964188d0b79c6204ee4c21d468af9bc on cmu-db:master.

Coverage decreased (-0.2%) to 75.028% when pulling bfad690f09d1aa7a47d8659fd7f1e697e0a57763 on allisonwang:costandstats into 82430b6ee33c07857d9c0b79bc885b658657d995 on cmu-db:master.

Coverage decreased (-0.2%) to 75.034% when pulling a8385386ed3c298e56b9cb914c2fd27792f0af79 on allisonwang:costandstats into 82430b6ee33c07857d9c0b79bc885b658657d995 on cmu-db:master.


handle potential overflow on job history

Fixes #1198

There's enough space there that this should be an edge case, and I don't think we should throw tooltips on everything because it would get noisy. I have some ideas in this space that I'll explore in a follow-on.


Added missed import. Without import adding new XMPP account doens't w…

…ork by java.langClassNotFound exception

@ibauersachs please check. This issue included in nightly builds so Jitsi is unusable for XMPP at the moment

You don't need to mention me in every issue or pr, I'll get the notifications anyway.