CI Fail - stx dependency in the bazel external

Failure here: https://drake-jenkins.csail.mit.edu/job/RobotLocomotion/job/drake-shambhala/job/PR-35/10/console
Analyzing: target //apps:simple_continuous_time_system (10 packages loaded)
ERROR: /home/ubuntu/.cache/bazel/_bazel_ubuntu/4ec442eb70ae159fd7ea51f91a92aa37/external/drake/drake/common/BUILD.bazel:52:1: no such package '@stx//': The repository could not be resolved and referenced by '@drake//drake/common:essential'

This popped up due to the change in Drake #7241.
Stx got shifted to utilising a new_local_repository approach. This can't be replicated when drake is brought in as an external because the path to those headers can't be retrieved.
It's possibly also not the correct thing to do - the path for a new_local_repository is supposed to absolute according to the docs, though obviously the bazel executable doesn't actually back that up. I am guessing that the spirit of this mechanism is for experimenting with dependencies on your local system, not for managing sandboxed sets of files within the project.

@jwnimmer-tri thoughts?

This also breaks the cmake external project build.

Wrong install directory: install/include/stx/stx/optional.hpp

It's possibly also not the correct thing to do - the path for a new_local_repository is supposed to absolute according to the docs, ...

Good catch.  Filed as RobotLocomotion/drake#7261.

Stx got shifted to utilising a new_local_repository approach. This can't be replicated when drake is brought in as an external ...

I'll grant you that its obscure, but "can't" is one step too far:
--- a/drake_bazel_external/WORKSPACE
+++ b/drake_bazel_external/WORKSPACE
index 15d5f75..32cfd6a 100644
@@ -39,20 +39,35 @@
 # Drake
 ################################################################################

+_DRAKE_REPO = "RobotLocomotion/drake"
+_DRAKE_COMMIT = "master"
+_DRAKE_SHA256 = None
+# alternatively for a specific tag
+# _DRAKE_COMMIT = "65c4366ea2b63278a286b1e22b8d464d50fbe365",
+# _DRAKE_SHA256 = "899d98485522a7cd5251e50a7a6b8a64e40aff2a3af4951a3f0857fd938cafca",
+
 github_archive(
     name = "drake",
-    repository = "RobotLocomotion/drake",
-    commit = "master",
-    sha256 = None
-    # alternatively for a specific tag
-    # commit = "65c4366ea2b63278a286b1e22b8d464d50fbe365",
-    # sha256 = "899d98485522a7cd5251e50a7a6b8a64e40aff2a3af4951a3f0857fd938cafca",
+    repository = _DRAKE_REPO,
+    commit = _DRAKE_COMMIT,
+    sha256 = _DRAKE_SHA256,
 )

 ################################################################################
 # Drake Dependencies
 ################################################################################

+new_http_archive(
+    name = "stx",
+    urls = [
+        "https://github.com/%s/archive/%s.tar.gz" % (
+            _DRAKE_REPO, _DRAKE_COMMIT)
+    ],
+    sha256 = _DRAKE_SHA256,
+    strip_prefix = "drake-" + _DRAKE_COMMIT + "/third_party/com_github_tcbrindle_cpp17_headers",
+    build_file = "tools/stx.BUILD",
+)
+
 bitbucket_archive(
     name = "eigen",
     repository = "eigen/eigen",

--- a/drake_bazel_external/tools/stx.BUILD
+++ b/drake_bazel_external/tools/stx.BUILD
new file mode 100644
index 0000000..45cceb5
@@ -0,0 +1,9 @@
+# -*- python -*-
+
+package(default_visibility = ["//visibility:public"])
+
+cc_library(
+    name = "stx",
+    hdrs = ["stx/optional.hpp"],
+    includes = ["."],
+)

This mess is consistent with RobotLocomotion/drake#7259 being unfinished.

But also, let me take a step back here.  I do not think that Shambhala's drake_bazel_external is ripe yet.
To the extent we investigate and fix when it fails CI, we are wasting our time.  To the extent that Drake's users look at it for advice, we are doing them harm.
Its code fails the "don't repeat yourself" sniff test, and it sets users on the wrong path for how to pursue downstream Bazel integration.  It goes against current best practices in the Bazel ecosystem for how to chain Bazel projects together.  Once we finish RobotLocomotion/drake#7259, then we should pursue the drake_bazel_external exemplar, and show users how to do it right.
In the meantime, I suggest removing it from master.  If that's not tenable, then at least it should have a bigger "The code in this folder is a bad idea and don't copy it!" disclaimer.  The current **Under Construction** text doesn't really get that message across strongly enough, in my opinion.

@jwnimmer-tri your above code and comment was quite useful! I didn't realize that drake#7259 was in progress and I was going down a rabbit hole.
Is the workflow in the drake-iiwa-driver bazel build going to be the suggested way forward for external drake apps? We have ended up using many different versions of drake in various parts of the system and would like to start standardizing.
FWIW - adding your above comment (or linking to it) to the drake_bazel_external README would be very useful.

I'd say that workaround effectively falls into what I consider "can't". It's starting to resort to clever, but obscure/drastic methods which suggests it's now fighting with the system rather than working with it.
Having this here was intended to motivate an exploration in how to do this properly prior to advertising Shambhala. Some efforts were rebuffed and so it lingered. I was about to bump this for resolution (one way or another) as part of a final effort to getting Drake & Shambhala ready and under CI as we already have groups trying various brittle approaches to get this working. In that respect, I am glad that drake#7259 has now articulated this is a desired goal.
Regardless of whether it will be supported or not, a discerning note concerning the situation for downstream bazel projects would be entirely relevant in a README here since the question is oft asked.

@dmsj

Is the workflow in the drake-iiwa-driver bazel build going to be the suggested way forward for external drake apps? We have ended up using many different versions of drake in various parts of the system and would like to start standardizing.

I don't know drake-iiwa-driver much at all.  But from first glance, it seems like it's only grabbing Drake to refer to some of its LCM messages?  I thought that's what https://github.com/RobotLocomotion/lcmtypes was for?  So as the first choice, I guess I would say to stop depending on Drake if possible, in that repository.
In general though, once RobotLocomotion/drake#7259 is ready, then it would be an option to use Bazel in your own code and refer to Drake that way.  Alternatively, Drake will offer a CMakeLists.txt that will compile and install Drake in a way that other CMake-based projects can use naturally.  Depending on what your code wants, one of those two ways should be an easy path forward.

@stonier

I am glad that drake#7259 has now articulated this is a desired goal.

To be clear, I think we should focus 100% of our efforts on Drake's CMake wrapper to get that support up and running perfectly first.  Only when we are done (or blocked) on that front, should we invest in shipping a supported direct-into-Bazel interface.

To be clear, I think we should focus 100% of our efforts on Drake's CMake wrapper to get that support up and running perfectly first. Only when we are done (or blocked) on that front, should we invest in shipping a supported direct-into-Bazel interface.

This is of course, implicit.

Driving doesn't need or want RobotLocomotion/drake#7259 in any way, shape or form.

Why would driving not make use of it? It is a downstream bazel project, that at some point may have dependencies that don't already fully intersect with those of Drake's.

Driving is not allowed to pull dependencies off the internet.  It's entire WORKSPACE is custom, and shares nothing with Drake.

Noted, thanks.


Focus on fiber

Use Case
As a user with fibers in the data I am viewing, I would like to be able to click a fiber and focus the view near the center of the fiber I clicked.
Acceptance Criteria
When a user clicks on a fiber, the center point of the view focuses on the average position of that fiber's subpoints.
Details
Currently, the view centers at zero for all fibers.
Instead, center on the average position of the subpoints in the fiber. Could also use the average of just the two endpoints, to keep performance from being an issue for fibers with many subpoints.
Eventually I think it would be best if you could click on a segment between two subpoints and center on that, but that is out of scope right now.

I suspect this is actually a bug.
TODO: check the line in VisAgent.ts:
            this.agentData.visType === VisTypes.ID_VIS_TYPE_FIBER &&

and substitute
            this.agentData["vis-type"] === VisTypes.ID_VIS_TYPE_FIBER &&


User friendliness

Have no idea why I wasn't notified by email of this pull request.
Sorry.
Time to delve into my settings.


pip install azure-storage command is deprecated

@demetrioi commented on Fri Jun 05 2020
The command pip install azure-storage is deprecated
" Starting with v0.37.0, the 'azure-storage' meta-package is deprecated and cannot be installed anymore.
Please install the service specific packages prefixed by azure needed for your application.
The complete list of available packages can be found at:
https://aka.ms/azsdk/python/all"

[Insira comentários aqui]

Detalhes do documento
⚠ Não edite esta seção. É necessário para a vinculação do problema do docs.microsoft.com ➟ GitHub.

ID: 1661ae0f-130e-8ec1-94f0-ca184223bca6
Version Independent ID: f88ca50c-493a-d357-e67f-0bcbaf1d6745
Content: Início Rápido: Ler dados capturados do aplicativo Python – Hubs de Eventos do Azure
Content Source: articles/event-hubs/event-hubs-capture-python.md
Service: event-hubs
GitHub Login: @ShubhaVijayasarathy
Microsoft Alias: shvija

@srvbpigh commented on Fri Jun 05 2020
Hello, @demetrioi
Thank you for your feedback.
We are actively reviewing your comments and will get back to you soon.
Kind regards,
Microsoft DOCS International Team

@CeciAc
Thanks for your feedback! We will investigate and update as appropriate.

@CeciAc  Thanks for your contribution, I've addressed this issue in PR: https://github.com/MicrosoftDocs/azure-docs-pr/pull/117995
The changes should be live EOD or tomorrow. We will now close this issue. In future, if you see any minor bug fixes in the doc, feel free to click on the edit button and submit a PR to update. we love to take community contributions.


Week 2

Templating
Name
Steven Whitton
Class
TECH2b
Repo link
https://github.com/daoneandonly/cmda-be
Summary

Use Express to handle the routes of /, about and profile
Add Pug templating engine
Add data is separate file
Use conditionals in about
Use mixins in the header
Use a layout file for general HTML layout
Use blocks and includes to render specific parts of the site
Write out my thoughts on the different templating engines in my wiki

Resources used

Pug Docs

Any thoughts?
Pug is life ❤

Source

Good reasoning to choose Pug over the other templating engines, do make sure to commit often and consistent (8 days ago? you don't have to commit when a feature is perfect/done). I would say you are ready to connect a database to your project


Upgrade to RC0

Hello, I`ve upgraded your fields to RC0 of SPFX and fixed the PeoplePicker with a newer version of app-fabic-ui-react. There might be some errors but I guess it is a start.

Thanks a lot for this submit. I also worked on RC0 migration and I will merge with your changes, the fix on the PeoplePicker is really helpfull thanks a lot. I'm moving also old http calls to the new sp-http module. Thanks again a lot for that. Regards,
Olivier


Sitekey not found in local dev.

Popping this here in case anyone has the same issue I did.
Installed on a statamic v3 site not problem - but I saw getting a must supply sitekey error in the console.
The cause was that my local dev site is not on a secure domain.
The fix is to use switch to using ssl, or in my case I switched to using the google test keys for local dev instead.

Closing as just an FYI.


nixos/matomo: introduce services.matomo.package option

for e.g. being able to use an updated matomo from unstable or custom sources.
Motivation for this change
During 18.03's lifetime, I had several maintainership issues with Matomo releasing new versions that are not strictly security-relveant, but were still of crucial importance to a limited set of people.
The most prominent example was the GDPR update: If GDPR did not apply to you, you might would not want to risk the stability of your system, but for users in/targeting Europe, the update was crucial to be allowed to still operate a Matomo instance.
This option should allow me to be more strict on what's required for stable, as users really needing the update could easily get it from unstable with this option. The service definition itself is very unlikely to break with Matomo new releases, so this should just work.
Can we still get this into 18.09, at least eventually? I know I'm late, but this should not be able to break anything and help maintaining a stable Matomo during 18.09's lifetime.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Fits CONTRIBUTING.md.

Now that 18.09 is released, I moved the changelog entry to 19.03 as I suspect nobody will read the changelog again after updating.


Update label transformer serialization

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 95.50562% with 4 lines in your changes missing coverage. Please review.

Project coverage is 85.15%. Comparing base (eda30bb) to head (5208fc4).

Files with missing lines
Patch %
Lines

eir/experiment_io/label_transformer_io.py
95.06%
4 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #87      +/-   ##
==========================================
- Coverage   89.96%   85.15%   -4.81%
==========================================
  Files         154      155       +1
  Lines       14625    14665      +40
==========================================
- Hits        13157    12488     -669
- Misses       1468     2177     +709

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


How to compile to an executable

I wanted to create a more automatic version of the program with a fixed IP and settings, but do not know how to compile it into an executable to run with other automation programs.

To compile to an executable, run the following build script at the root of the project
npm run bundle


iOS dependency on SystemConfiguration framework

When testing the plugin with a simple test application, the linker failed because of unresolved dependencies. I had to add the SystemConfiguration framework to resolve these issues. Shouldn't this framework be added too in the plugin.xml configuration file?

This was fixed along the way at some point.


add func to show/delete bridge

#74
nsxctl show segment -v
show bridge vlan id and profile names
nsxctl delete bridge <segment name> [--vlan-id <vlan ids,...>]
delete bridge or some of bridged vlan ids

Thank you for great contribution!


Outcomes should not be part of the offer message

Right now, outcomes are sent from the offerer to the acceptor.
This should not be the case, the outcomes should be received from the oracle. (though I am unsure if that's the case when the oracle is signing a price rather than a specific outcome)
Currently, the offerer is sending the SHA256 of outcomes, but on what basis the acceptor should validate them? The acceptor can only validate them if he already checked what the Oracle said he will sign. If so, then the offer outcomes are redundant.

As I wrote this, I understand the offer still need a way to gives his payout/reward attached to the outcome. So the current protocol is fine.
I actually complained about the offerer sending the SHA256 of outcome before. But now I believe it makes sense, because the acceptor should already know the pre image of the hashes from the oracle.


Idea: Markov chain in private chat [low prio]

Markov chains make for great entertainment when it comes to chat bots, and could be something to implement for private messages.
These bots basically learn from existing text (either pre-loaded or from messages received via chat) and construct new ones based on patterns found in existing text.
This might be a lot of work if there aren't any existing libraries for it out there, and is not part of core functionality.

@machuga can this be closed? Don't see it happening anytime soon


Does using a connection pool with Python's Async CosmosClient improve performance?

I'm writing a FastAPI app that uses the async CosmosClient. I'm expecting a lot of requests.
Would using some sort of connection pool improve performance? Or does the nature of async meant that there's no advantage to using a pool, since only one task would be running and using the CosmosClient at any one time anyway?
Every article about connection pools always compares them to setting up and tearing down a new connection on every request. I'm interested in how the performance compares of a single, global CosmosClient that gets reused for all requests, or a pool of Cosmos Clients, in an async environment.
If using a connection pool would be beneficial, is there any documentation for what that might look like in Python?
Related question - is using the async CosmosClient from multiple concurrent tasks safe? Or is there a chance that one task might get a response meant for another task, or make a request at the same time as another task?

Thanks for your question @tal-zvon!
Generally speaking, if you're using the CosmosClient within a context manager, the connection pool should be managed internally in the default transport:
async with CosmosClient(...) as client:
    await client.do_something(...)

If you're needing multiple clients, then the connection pool can be maintained between clients, then this can be achieved by creating your own transport and sharing it between clients, as in this sample here:
https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/core/azure-core/samples/example_shared_transport_async.py#L51-L71
Regarding your question of concurrency - depending on your usage, yes, the clients are intended to be thread (sync) and coroutine (async) safe. I say "depending on", because we currently have an open bug for concurrency-safety with usage of the response_hook parameter for accessing response headers. Though there's already a PR open for this and we expect to have it resolved soon.
Hopefully this helps - let me know if anything needs further details or clarification :)

Thanks @tal-zvon,
To clarify, the connection pool itself is not implemented in the Azure SDK, we leverage 3rd party HTTP libraries as the transport underpinning the SDK - so the exact behaviour of the connection pool may vary a bit depending on the transport used.
The default transport for async operations is aiohttp.
The CosmosClient maintains an aiohttp ClientSession.
This session is instantiated with minimal configuration.
If you wish to further refine the behaviour of the session, or customize it in any way - you can create your own aiohttp.ClientSession and pass it into the client transport as can be seen in the sample I linked to above.
Reusing the same CosmosClient should offer no performance disadvantage/advantage over sharing the same transport between multiple clients - so the decision would largely come down to the design of the application/stylistic choice.
Another consideration here will be your choice of authentication mechanism, for example if using AAD (via DefaultAzureCredential), then this will also maintain a connection.
You can find more discussion on the topic in this issue: https://github.com/Azure/azure-sdk-for-python/issues/28665
In terms of creating a pool of CosmosClient instance - assuming they're reusing the connection pool - the only advantage that would come to mind right now would be as a workaround for the concurrency bug in response_hook I mentioned earlier if you would be impacted by this before we can get the fix out.
I hope this helps!

@annatisch Thank you! That was very helpful!

@annatisch I'm noticing the keepalive_timeout in TCPConnector is 15 seconds. So when a request is sent within 15 seconds, performance is greater (a few ms). However, if a new request is sent after the timeout, the first request can take 2 seconds. How can I increase this timeout? Thanks!


Add error reporting when looking up types by demangled name.

When mangled name lookups fail, it can be pretty hard to track down the cause. There are many places where it can fail, and when nested generics are involved you can end up recursing a lot. My technique so far has involved adding lots and lots of ad-hoc logging calls to track down the failure.
This PR plumbs error reporting through the whole structure. Errors are recorded as a function pointer and a context pointer, allowing errors to gather relevant information, but also avoiding the overhead of string building on paths where the caller is going to have some sort of fallback instead of reporting the error.
For an example of what this does, here's an error I debugged the other day:
failed to demangle witness for associated type 'Body' in conformance 'Syndrome.ProcessPaymentButton: View' from mangled name '+�'
And here's what that error looks like with this PR:
failed to demangle witness for associated type 'Body' in conformance 'Syndrome.ProcessPaymentButton: View' from mangled name '+�' - _gatherGenericParameters: context: $s7SwiftUI12ProgressViewVMn 0x1a214efd0 <SwiftUI.EmptyView> parent: <null> - incorrect number of generic args (1), 2 local params, 2 total params
This would have saved a huge amount of debugging time (and hopefully will save a huge amount in the future!).

@swift-ci please benchmark

Build failed before running benchmark.

@swift-ci please benchmark

Build failed before running benchmark.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 0854fb609e77b7dab999a019d75f6df2e1f50b96

Build failed
Swift Test OS X Platform
Git Sha - 0854fb609e77b7dab999a019d75f6df2e1f50b96

https://github.com/apple/llvm-project/pull/1702
@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 0854fb609e77b7dab999a019d75f6df2e1f50b96

https://github.com/apple/llvm-project/pull/1702
@swift-ci please clean test

Build failed
Swift Test OS X Platform
Git Sha - 0854fb609e77b7dab999a019d75f6df2e1f50b96

Build failed
Swift Test Linux Platform
Git Sha - 0854fb609e77b7dab999a019d75f6df2e1f50b96

https://github.com/apple/llvm-project/pull/1702
@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 1dec95205a759db9b81ca42d6e2a52893f190633

Build failed
Swift Test OS X Platform
Git Sha - 1dec95205a759db9b81ca42d6e2a52893f190633

https://github.com/apple/llvm-project/pull/1702
@swift-ci please benchmark

Build failed before running benchmark.

apple/llvm-project#1702
@swift-ci please benchmark

Build failed before running benchmark.

https://github.com/apple/llvm-project/pull/1702
@swift-ci please test

https://github.com/apple/llvm-project/pull/1702
@swift-ci please benchmark

Build failed
Swift Test Linux Platform
Git Sha - aa800c67906b49885e167a8bb6a7e1d9de382d60

Build failed
Swift Test OS X Platform
Git Sha - aa800c67906b49885e167a8bb6a7e1d9de382d60

https://github.com/apple/llvm-project/pull/1702
@swift-ci please benchmark

Performance: -O

Improvement
OLD
NEW
DELTA
RATIO

Set.isSubset.Int.Empty
51
43
-15.7%
1.19x

Set.isStrictSubset.Int.Empty
51
45
-11.8%
1.13x (?)

Set.isSuperset.Seq.Empty.Int
50
45
-10.0%
1.11x (?)

Code size: -O
Performance: -Osize

Regression
OLD
NEW
DELTA
RATIO

ObjectiveCBridgeStubToNSStringRef
70
79
+12.9%
0.89x (?)

RemoveWhereFilterInts
24
27
+12.5%
0.89x

Improvement
OLD
NEW
DELTA
RATIO

FlattenListFlatMap
4535
3627
-20.0%
1.25x (?)

Set.isStrictSubset.Int.Empty
54
47
-13.0%
1.15x (?)

Set.isDisjoint.Seq.Int.Empty
51
47
-7.8%
1.09x (?)

Code size: -Osize
Performance: -Onone
Code size: -swiftlibs

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac mini
  Model Identifier: Macmini8,1
  Processor Name: 6-Core Intel Core i7
  Processor Speed: 3.2 GHz
  Number of Processors: 1
  Total Number of Cores: 6
  L2 Cache (per Core): 256 KB
  L3 Cache: 12 MB
  Memory: 64 GB


chore: Add more generality to theme customizations

[ ] Ensure all custom elements have elevated entry point for users to easily add their own logo, descriptions, etc.
[ ] Create coherence between Chakra theme and SCSS theme variables.
[ ] Adjust plop templates for better variability (e.g., components without SCSS, default Chakra component(s), etc.).
[ ] Add more info sections to home page

Header Logo should be wrapped in a link and default to home page
Mobile nav menu should auto hide after link is clicked
Mobile Nav GitHub link not working


Fixing routes

@senner007 I have removed 404 page and left the routing fix. Can you please review? Thanks

Approved


add github action to show testing coverage

Problem
We want to measure our test coverage
Solution

Add coverage to dev report
Post coverage report on PRs using a github action .
We can also have to do inline reporting that shows when a function isn't covered by a test, but that will be overwhelming at this moment.

Type of change
Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

Thanks for doing this! I know we didn't talk about simularium-viewer specifically during the meeting earlier, but looks like we can set up thresholds for specific file paths, which would be more informative https://jestjs.io/docs/configuration#coveragethreshold-object

yeah, that's a good idea. The print out that you get locally in also more informative than what gets posted here in the PR. (it is broken down by file). That will be especially helpful for wanting the best coverage on selectors on the website.


feat-update question format closes #54

Should be good to go!

does this work though? I think the path to the index.js file is from inside the index.html, no?

LGTM, ill merge 🕺


Custom flex classes

Having a class that sets flex:1 would be super handy.

A better option would be to provide developers with the ability to pack their own custom classes into the Brixi CSS output.
classes: {
    "flex-1": "flex: 1;",
    "class-name": "css"
}


porting "additional resources" content from previous repo

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/resources/index.md
:warning:Warning

Details

docs/resources/_images/3dblueprintvisiotemplate.jpg
:white_check_mark:Succeeded

docs/resources/_images/azurearchinfographicthumb.jpg
:white_check_mark:Succeeded

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded

docs/resources/_images/edxcourse.png
:white_check_mark:Succeeded

docs/resources/index.md

Line 38: [Warning] Invalid file link:(~/reference-architectures).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/resources/_images/3dblueprintvisiotemplate.jpg
:white_check_mark:Succeeded

docs/resources/_images/azurearchinfographicthumb.jpg
:white_check_mark:Succeeded

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded

docs/resources/_images/edxcourse.png
:white_check_mark:Succeeded

docs/resources/index.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/resources/_images/3dblueprintvisiotemplate.jpg
:white_check_mark:Succeeded

docs/resources/_images/azurearchinfographicthumb.jpg
:white_check_mark:Succeeded

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded

docs/resources/_images/edxcourse.png
:white_check_mark:Succeeded

docs/resources/index.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/resources/_images/3dblueprintvisiotemplate.jpg
:white_check_mark:Succeeded

docs/resources/_images/azurearchinfographicthumb.jpg
:white_check_mark:Succeeded

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded

docs/resources/_images/edxcourse.png
:white_check_mark:Succeeded

docs/resources/index.md
:white_check_mark:Succeeded

docs/toc.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_bread/toc.yml
:white_check_mark:Succeeded

docs/resources/_images/3dblueprintvisiotemplate.jpg
:white_check_mark:Succeeded

docs/resources/_images/azurearchinfographicthumb.jpg
:white_check_mark:Succeeded

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded

docs/resources/_images/edxcourse.png
:white_check_mark:Succeeded

docs/resources/index.md
:white_check_mark:Succeeded

docs/toc.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_bread/toc.yml
:white_check_mark:Succeeded

docs/resources/_images/3dblueprintvisiotemplate.jpg
:white_check_mark:Succeeded

docs/resources/_images/azurearchinfographicthumb.jpg
:white_check_mark:Succeeded

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded

docs/resources/_images/edxcourse.png
:white_check_mark:Succeeded

docs/resources/diagrams.md
:white_check_mark:Succeeded

docs/resources/index.md
:white_check_mark:Succeeded

docs/resources/training.md
:white_check_mark:Succeeded

docs/toc.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_bread/toc.yml
:white_check_mark:Succeeded

docs/resources/_images/3dblueprintvisiotemplate.jpg
:white_check_mark:Succeeded

docs/resources/_images/azurearchinfographicthumb.jpg
:white_check_mark:Succeeded

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded

docs/resources/_images/edxcourse.png
:white_check_mark:Succeeded

docs/resources/diagrams.md
:white_check_mark:Succeeded

docs/resources/index.md
:white_check_mark:Succeeded

docs/resources/training.md
:white_check_mark:Succeeded

docs/toc.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_bread/toc.yml
:white_check_mark:Succeeded

docs/resources/_images/3dblueprintvisiotemplate.jpg
:white_check_mark:Succeeded
View

docs/resources/_images/azurearchinfographicthumb.jpg
:white_check_mark:Succeeded
View

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded
View

docs/resources/_images/edxcourse.png
:white_check_mark:Succeeded
View

docs/resources/diagrams.md
:white_check_mark:Succeeded
View

docs/resources/index.md
:white_check_mark:Succeeded
View

docs/resources/training.md
:white_check_mark:Succeeded
View

docs/toc.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_bread/toc.yml
:white_check_mark:Succeeded

docs/resources/_images/3dblueprintvisiotemplate.jpg
:white_check_mark:Succeeded
View

docs/resources/_images/azurearchinfographicthumb.jpg
:white_check_mark:Succeeded
View

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded
View

docs/resources/_images/edxcourse.png
:white_check_mark:Succeeded
View

docs/resources/diagrams.md
:white_check_mark:Succeeded
View

docs/resources/index.md
:white_check_mark:Succeeded
View

docs/toc.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_bread/toc.yml
:white_check_mark:Succeeded

docs/resources/_images/3dblueprintvisiotemplate.jpg
:white_check_mark:Succeeded
View

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded
View

docs/resources/diagrams.md
:white_check_mark:Succeeded
View

docs/resources/index.md
:white_check_mark:Succeeded
View

docs/toc.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_bread/toc.yml
:white_check_mark:Succeeded

docs/resources/_images/3dblueprintvisiotemplate.png
:white_check_mark:Succeeded
View

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded
View

docs/resources/diagrams.md
:white_check_mark:Succeeded
View

docs/resources/index.md
:white_check_mark:Succeeded
View

docs/toc.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_bread/toc.yml
:white_check_mark:Succeeded

docs/resources/_images/3dblueprintvisiotemplate.png
:white_check_mark:Succeeded
View

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded
View

docs/resources/diagrams.md
:white_check_mark:Succeeded
View

docs/resources/index.md
:white_check_mark:Succeeded
View

docs/toc.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_bread/toc.yml
:white_check_mark:Succeeded

docs/resources/_images/3dblueprintvisiotemplate.png
:white_check_mark:Succeeded
View

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded
View

docs/resources/diagrams.md
:white_check_mark:Succeeded
View

docs/resources/index.md
:white_check_mark:Succeeded
View

docs/toc.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_bread/toc.yml
:white_check_mark:Succeeded

docs/resources/_images/3dblueprintvisiotemplate.png
:white_check_mark:Succeeded
View

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded
View

docs/resources/diagrams.md
:white_check_mark:Succeeded
View

docs/resources/index.md
:white_check_mark:Succeeded
View

docs/toc.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/_bread/toc.yml
:white_check_mark:Succeeded

docs/resources/_images/3dblueprintvisiotemplate.png
:white_check_mark:Succeeded
View

docs/resources/_images/cnesymbols.png
:white_check_mark:Succeeded
View

docs/resources/diagrams.md
:white_check_mark:Succeeded
View

docs/resources/index.md
:white_check_mark:Succeeded
View

docs/toc.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


CLI banner displays .local domain in HA URLs regardless of user-provided settings

I noticed today that the welcome banner in the CLI includes two URLs to Home Assistant endpoints:
  Home Assistant URL:       http://homeassistant.local:8123
  Observer URL:             http://homeassistant.local:4357

These endpoints are hard-coded to use the .local domain, as seen here in cmd/banner.go:
https://github.com/home-assistant/cli/blob/8d8c11abf3103e752705d56da916dca2f1a4fcfb/cmd/banner.go#L167-L168
In my case, these URLs were not working because I had not enabled mDNS on my network.
Enabling mDNS would fix the issue on my network, but I think it would be better if HA reported the user-configured domain where possible, then gracefully fall back to .local if no domain is available.
Can anyone think of any downsides to this approach? Would there be any interest in merging a PR to make this change? Is this info even available to the CLI, or would I have to move upstream and change the Supervisor info API?

Thank you, my network is ".lan" as provided by pi-hole. So this message from "ha banner" is missleading.

Enabling mDNS would fix the issue on my network, but I think it would be better if HA reported the user-configured domain where possible, then gracefully fall back to .local if no domain is available.

With user configured domain you mean the domain suffix as provided through DHCP?
This might be the better option here indeed. We kinda use mDNS as fallback since most folks have mDNS enabled and almost all platform support it out-of-the box. So it is a somewhat safe fallback.
I guess the question would be how many folks have a borked router/setting where the DHCP provided suffix ends up not working :thinking: :grimacing:
Also, technically if you have two instances with the same name, your DHCP might not allocate the domain name for you. But that problem also exists on mDNS so :man_shrugging: . Maybe we could even learn if that was the case from the DHCP response? :thinking:

Hm, yeah NetworkManager actually exposes quite some information:
DHCP4.OPTION[5]:                        domain_name = lan
...
DHCP4.OPTION[8]:                        host_name = ha-virt-proxmox-dev
...
DHCP4.OPTION[12]:                       requested_domain_name = 1

I guess if we look at this information we can say with reasonably high accuracy that ha-virt-proxmox-dev.lan will work in this case.


Bug: api.add_tag() takes 1 positional

Hey 👋
I think a find a new bug in this wrapper.
When I tried to add a tag using api.add_tag("test", "FF0000"), I got the following error :
vscode ➜ /workspaces/KumaCompanion (main) $ kuma tag add --name test -c "#FFFFFF"
Traceback (most recent call last):
  File "/workspaces/KumaCompanion/src/main.py", line 44, in <module>
    main()
  File "/workspaces/KumaCompanion/src/main.py", line 38, in main
    args.func(args)
  File "/workspaces/KumaCompanion/src/commands/tag/add.py", line 13, in add_tag
    api.add_tag("TEST", "#FF0000")
TypeError: UptimeKumaApi.add_tag() takes 1 positional argument but 3 were given

Here a snippet of my code :
def add_tag(args):
    # Connection to Uptime Kuma API
    api = KumaCompanion().get_api()

    # Creating a new tag
    # Add tag
    api.add_tag("TEST", "#FF0000")

Do you have any solutions ?

Try using keyword arguments as per the documentation:
api.add_tag(name="TEST", color="#FF0000")


Decoding uppercase domains as well

Just noticed that php native idn_to_ascii() also handles utf-8 domains in uppercase and lowercase equally, e.g. 'пример.испытание' and 'ПРИМЕР.ИСПЫТАНИЕ' produce the same result. This library produce different results which is wrong of course.
So second commit adds the mb_strtolower() conversion before encoding.

Plus looking at RFC 3492 it checks out.
Thank you for your patch, a new release will be done soon.


[otbn] Fully specify RND CSR/WSR

Specify what to expect when reading from the CSR/WSR.
Better specify quality of random number in the RND CSR/WSR
Code on bignum has access to random numbers through the RND CSR or WSR. We need to specify the properties of these random numbers.
We currently haven’t decided on how the random numbers exposed to the bignum application are generated. They will be somehow linked to the CSRNG outputs, but could be produced by CSRNG directly, or the output of CSRNG could be used as seed for a local LFSR.
Provide more than one type of randomness
Currently, there is one single type of randomness made available to the application through the RND special-purpose register. It might be interesting to provide more than one type of randomness, e.g. “weak” and “cryptographically strong” randomness. This could be made available for example through two separate registers, e.g. RNDWEAK and RNDSTRONG
See also https://github.com/lowRISC/opentitan/issues/3522

Closing as covered by #2638


Fixes banner markup and styles to allow for skinny mobile screens

yo @derrickstaten can you check this out?

:+1:

Sweet. @dmitrig01 lmk if I can merge this

:+1:


[embedded] When missing a source location in a PerformanceDiagnostic, at least print the function name

I know this isn't great, but it's at least something. Turns
<unknown>:0: error: cannot use metatype of type 'Int' in embedded Swift

into:
<unknown>:0: error: cannot use metatype of type 'Int' in embedded Swift
in function $ss17FixedWidthIntegerPsE03bitB0SivgSi_Tg5

@swift-ci please test

@swift-ci please test


Change filmstrips notebook not working

Real_world_examples > Change_filmstrip notebook not working for me.

ipyleaflet map doesn't load. If a polygon is selected it will process, but produces this error:

However, the exported .png is fine.
The Exporting_satellite_images notebook which also uses ipyleaflet seems to be working fine.

This seems to work fine for me.


return_cellID for motif_enrichment_knn and motif_enrichment_dist

Analogous to how the return_cellID flag works for find_patterns_rand and find_patterns_grid, would it be possible to implement a return_cellID option for motif_enrichment_knn and motif_enrichment_dist?

Yes, I updated motif_enrichment_knn/dist, now we can choose to return cell_id by setting return_cellID=True.


How can use im2rec to create a rec file with grey scale images as input.I mean how can i make a single channel Rec file?

How can use im2rec to create a rec file with grey scale images as input.I mean how can i make a single channel Rec file?

im2rec should have a option to allow greyscale.

@piiswrong
Yes,I do think this is the case,but I cann't find the option. Bellow are the option list.
Usage: <image.lst> <image_root_dir> <output.rec> [additional parameters in form key=value]\n"
"Possible additional parameters:\n"
"\tresize=newsize resize the shorter edge of image to the newsize, original images will be packed by default\n"
"\tlabel_width=WIDTH[default=1] specify the label_width in the list, by default set to 1\n"
"\tnsplit=NSPLIT[default=1] used for part generation, logically split the image.list to NSPLIT parts by position\n"
"\tpart=PART[default=0] used for part generation, pack the images from the specific part in image.list\n"
"\tcenter_crop=CENTER_CROP[default=0] specify whether to crop the center image to make it rectangular.\n"
"\tquality=QUALITY[default=80] JPEG quality for encoding, 1-100.\n");

OK. I understand I should get the latest version of mxnet.

closing for now, please feel free to reopen it


launch tmux window instead of iTerm2 if tmux is running

Attempt at fixing https://github.com/TheNewNormal/kube-solo-osx/issues/147 though it's my first time using XCode

thanks for the PR, this only work for first initialisation, up.command will not use tmux as obj-c calls up.command shell script via iTerm.


Fit mock lens with Sersic source & SIE

First attempt at fitting the main part of the lens gives large residuals. It looks like an SPLE would fit much better. I have a torch SPLE implementation that I can try out.


Custom Validation in validate()

I am using Open Cart API. The api has a very weird mechanism..
The API return header status code 200 even on unauthorized access, instead of 401.And returns the 401 error code in the body as attached in the image.

This way, my response success block is triggered instead of retrying the request. I have been using the Alamofire Adapter and Retrier for a long and this seems to be working find when the header status code is 401. But the API returns me 401 status code in the body which doesn't trigger the  delegate method while validating the request.
    func should(_ manager: SessionManager,
                retry request: Request,
                with error: Error,
                completion: @escaping RequestRetryCompletion)

How should i handle this situation... Is there a way i can call the retrier delegate method manually?

One way how i solved it is
extension DataRequest {

    public func validateBodyStatusCode() -> Self {

        return validate { request,response,data in

            PrinterHelper.jsonPrinter(self.delegate.data!)
            do {
                if  let json = try JSONSerialization.jsonObject(with: data!, options: []) as? [String : Any]{

                    if let statusCode =  json["statusCode"] as? Int, statusCode == 401{

                        let reason:AFError.ResponseValidationFailureReason = .unacceptableStatusCode(code: 401)
                        return .failure(AFError.responseValidationFailed(reason: reason))

                    }else{

                        return .success
                    }
                }else{

                    return .success
                }

            } catch let error {

                print("Json serialization error \(error)")
                let reason:AFError.ResponseValidationFailureReason = .unacceptableStatusCode(code: response.statusCode)
                return .failure(AFError.responseValidationFailed(reason: reason))

            }
        }
    }
}

And using the custom Validation as
 let apiRequest = manager!.request(networkAddress, method: EndPoint.method, parameters: parameter, encoding: enCodingFormat, headers:authFlagHeader).validateBodyStatusCode().responseJSON { (response) in

            let parsedResult =  ResponseParser<EndPoint.ResponseType>.parseResponse(withResponse: response)
            callback(parsedResult.0,parsedResult.1)

        }

@anishparajuli555 You've hit a rather prickly use case for us. Right now validate() is only intended for simple validation scenarios. As you've seen, it doesn't really work that well for validating something in the response data. In fact, that's a highly inefficient use of it, since the response data may then be decoded twice. At the moment I would suggest any validation you need to perform on the response data be done in a custom response serializer and not validate. In the future we'll be reevaluating validate()s capabilities and how it fits into Alamofire.

Have the same issue. API always send 200 status code and in json response body code with real response status.

@kiokumicu  i have added solution above..please have a look

@anishparajuli555 yeap, I use it, thx.
Maybe guys add native support )

@cnoon thanks guy

@jshier / @cnoon - is there any available fix for problems like these in AF5? I’m on beta 6 and was curious your guys recommendations for a situation similar to OP. I am getting 200’s but there is in fact an error in the body that will cause me to refresh some tokens and then retry. What is your recommended solution given we are using AF5. Thanks again.

@croossin Once you need to parse response bodies as errors and return the value, it's usually easier and more efficient to do so in the response serialization phase, rather than in validation. Especially now, after beta 5, where the ability to trigger retry from serialization errors were added. So, for parsing, you have a few options:

Use responseDecodable and, if there was a failure decoding, attempt to parse your error body. (Make sure to pass a custom DispatchQueue and call back to .main for this.)
Use responseData and do both the intended type parsing and the failure parsing in the response handler. (Make sure to pass a custom DispatchQueue and call back to .main for this.)
Write your own ResponseSerializer-conforming type and do the parsing there.

Then, just create your own error type and handle the particular case you need in a RequestRetrier to trigger the retry.
Personally, I write my own ResponseSerializer for all of my projects, especially those that need custom response handling like this.

@jshier how do you use custom ResponseSerializer with async-await AF api?


TLS 1.2 keys change

Adding missing registry key

@jaszperez : Thanks for your contribution! The author, @barbkess, has been notified to review your proposed change.

#sign-off


(Partially) Re-enable akochan for Mahjong Soul

I am maintainer of 雀魂牌譜屋. Since my server caches log data for recent matches (usually for 1 ~ 2 days), I think akochan can use these data to allow reviewing recent matches. What do you think? If you like this idea, I can message you an HTTP endpoint for getting log data. :)

Hi, thank you for your hard efforts running the useful site.
I think my tensoul isn't broken yet aside from some possibly needed updates; it just demands a good reliable host for it to be deployed so that all logs will be accessible again. But I have been busy working my new AI engine for the recent months, so I've put this on hold.

I see, cheers!


Implement at() in terms of operator[] to avoid bound checks in deque and vector

The containers in the STL that support random access implement two different functions to access specific elements in the container:

operator[]
at

operator[] just accesses the element without bound checks, while at perfoms the same operation, but doing bound checks and throwing an out_of_bounds exception when the index is out of bounds.
I propose that the containers (deque and vector basically) implement at() in terms of operator[], and perfom bound checks only when calling at(). That way they're more compliant to the STL ones. This is my proposed solution for vector (for deque is the same idea):
template <typename T>
inline STDGPU_DEVICE_ONLY typename vector<T>::reference
vector<T>::at(const vector<T>::index_type n)
{
    return const_cast<vector<T>::reference>(static_cast<const vector<T>*>(this)->at(n));
}

template <typename T>
inline STDGPU_DEVICE_ONLY typename vector<T>::const_reference
vector<T>::at(const vector<T>::index_type n) const
{
    STDGPU_EXPECTS(0 <= n);
    STDGPU_EXPECTS(n < size());
    STDGPU_EXPECTS(occupied(n));

    return this->operator[](n);
}

template <typename T>
inline STDGPU_DEVICE_ONLY typename vector<T>::reference
vector<T>::operator[](const vector<T>::index_type n)
{
    return _data[n];
}

template <typename T>
inline STDGPU_DEVICE_ONLY typename vector<T>::const_reference
vector<T>::operator[](const vector<T>::index_type n) const
{
    return _data[n];
}

Thanks for the report! Defining the functions this way is definitely the better solution. Exception handling goes beyond this particular case and probably needs to be investigated separately.

I opened #185 to make the suggested changes. Unfortunately, the CI is currently broken, so merging will be delayed until the problem gets fixed.

Throwing std::out_of_bounds is the way the STL reports the error, but this is code executed in the GPU, so error handling doesn't have to be compliant to the STL containers, in my opinion.
Also, I suspected that CI was going to break due to the fact that now operator[] doesn't do bounds check, so a deeper look in the test must be done.

CI breakage is actually unrelated to the changes as installing the required packages already fails:
https://dev.azure.com/patrickstotko/stdgpu/_build/results?buildId=409&view=logs&j=26ef8efa-a13f-5927-0bd6-f52d59ca1b8a&t=6e8fff25-1341-5e4b-5d44-a0c41a8a32ee&l=74
Reading package lists...
E: Failed to fetch http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04/InRelease  403  Forbidden [IP: <IP_ADDRESS> 80]
E: The repository 'http://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_18.04  InRelease' is no longer signed.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://storage.googleapis.com/bazel-apt stable InRelease: The following signatures were invalid: EXPKEYSIG 3D5919B448457EE0 Bazel Developer (Bazel APT repository key<EMAIL_ADDRESS>
##[error]Bash exited with code '100'.

We need to wait until the CI images get either reverted or fixed.

CI is working again. Merged the PR as all tests passed. Thanks again for the report!


Camera zoom functionality is not there?

Can't a user do zoom in and zoom out while he select camera app and take pictures? If then can you suggest me where I should add the required code. Will add and create a pull request.

Camera functionality is provided by cwac-cam2. I suppose you could ask the author to implement it and update it. I will update the dependency by then.


listenbrainz-mpd: 2.2.0 -> 2.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/listenbrainz-mpd/versions.
meta.description for listenbrainz-mpd is: ListenBrainz submission client for MPD
meta.homepage for listenbrainz-mpd is: https://codeberg.org/elomatreb/listenbrainz-mpd
meta.changelog for listenbrainz-mpd is: https://codeberg.org/elomatreb/listenbrainz-mpd/src/tag/v2.3.0/CHANGELOG.md
Updates performed

Rust version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.3.0 with grep in /nix/store/6837bh7bi1554za9riv3zc4fkqw9vr35-listenbrainz-mpd-2.3.0
found 2.3.0 in filename of file in /nix/store/6837bh7bi1554za9riv3zc4fkqw9vr35-listenbrainz-mpd-2.3.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
listenbrainz-mpd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6837bh7bi1554za9riv3zc4fkqw9vr35-listenbrainz-mpd-2.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/c2abf8b74280be85aad22de6449fc8b25ab3b022#listenbrainz-mpd

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6837bh7bi1554za9riv3zc4fkqw9vr35-listenbrainz-mpd-2.3.0
ls -la /nix/store/6837bh7bi1554za9riv3zc4fkqw9vr35-listenbrainz-mpd-2.3.0/bin

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

1 package built:

listenbrainz-mpd

Maintainer pings
cc @DeeUnderscore for testing.

>   = note: ld: framework not found SystemConfiguration
>           clang-11: error: linker command failed with exit code 1 (use -v to see invocation)
>
>
> error: could not compile `listenbrainz-mpd` (bin "listenbrainz-mpd") due to previous error
For full logs, run 'nix log /nix/store/007yd4bpn90gznmqmaz43s47iah2mcja-listenbrainz-mpd-2.3.0.drv'.

Superseded by #266315


ENH: Add kwargs in Brain.add_* and pass it to mayavi modules

Add kwargs in Brain.add_* and pass it to mayavi modules, so that we could directly manipulate mayavi display settings, like point resolution and overlay opacity.

Thanks @DingkunLiu


bun create tamagui fails if git clone.defaultRemoteName is not "origin"

Current Behavior
When you try to get started with tamagui, it dies while trying to do a git pull from something called origin if you have changed defaultRemoteName to something more ergonomic, like for example up.
Expected Behavior
It should either not depend at all on the remote name or, if that's too hard, then read the default remote name via git config clone.defaultremotename and use that.
Tamagui Version
1.0.1-rc.7.1 (according to `bunx create-tamagui-app --version`)

Platform (Web, iOS, Android)
N/A

Reproduction
% rm -rf ~/.tamagui
% git config --global clone.defaultRemoteName up
% bun create tamagui

System Info
System:
    OS: macOS 14.4.1
    CPU: (8) arm64 Apple M1
    Memory: 138.23 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.2 - /opt/local/bin/node
    Yarn: 1.22.21 - /opt/local/bin/yarn
    npm: 10.7.0 - /opt/local/bin/npm
    bun: 1.1.7 - ~/.bun/bin/bun
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 124.0.6367.119
    Safari: 17.4.1

Fix in next release 6b592edccb93140c4efca301ef277dca91de874e


pkg/helm: add wrapper to get the Helm history we expect

We expect to get the history in descending order by version and limited
to 1 version to get the last version so we can ensure the user has the
last version of the Helm chart.
However, it turns out the Helm API doesn't honor the Max config parameter and
returns the Helm history in a non-deterministic order.
This adds a wrapper function that sorts what the Helm API returns in the
way we expect and uses that.
Fixes #1442

Sorry, pushed to the wrong branch :sweat_smile:


Login Credentials Set Through CLI Not Working for New Users

Ever since I updated to the latest GRAV install I have had issues with creating new users.
First I was getting this issue:
PHP Fatal error:  Uncaught RuntimeException: Opening file for writing failed on error fopen(/home/kelseyurgo/xdci/cache/compiled/blueprints/master-localhost.php): failed to open stream: Permission denied in /home/kelseyurgo/xdci/vendor/rockettheme/toolbox/File/src/File.php:202
Which was odd because master-localhost.php didn't exist, but master-xdci.renci.org.php did.
After not getting anywhere I did find a similar permissions issue here https://github.com/getgrav/grav/issues/912 turns out the permissions are fine, the file just didn't exist. So I copied the file that did exist into a new file name master-localhost.php.
This did move things along to a new error that looked similar, but it was looking for a new file that didn't exist, this time in cache/compiled/files which definitely had to do with permissions because once I loosened permissions recursively on cache/ directory, the bin/plugin login newuser command was able to run and I was able to complete the process.
However, the credentials I have set (and I have done this three times now just to be sure) are leading to a failed login page.
This is happening across two different sites since updating.
Any help would be greatly appreciated!

How are you creating new users? From the CLI command?
I just tested with the latest develop branch and it worked fine. What version of Grav are you running?

I am creating new users through the CLI Command. I am running version Grav v1.3.8 - Admin v1.6.6.

So can you confirm that when logged in and using the CLI you can actually create files in the user/accounts/ folder?
Try something like:
$ touch user/accounts/testfile

If that gives a permission error, then check the permission on the user/accounts folder and see if your current logged in user has write permissions.

So the CLI can definitely has permission as it is able to create the user yaml files (there are new correctly named files under user/accounts/ after each new user added).
The issue comes in when someone actually goes to log in on the frontend (our url with /admin appended), the credentials that were set up don't actually work. And I have checked this multiple times across both recently updated installs of GRAV.

And just to be sure I rantouch user/accounts/testfile and testfile was successfully created.

Ok, then the problem is that the webserver itself cannot write to the file.  Ideally you should have the user that logs in to the CLI be the same user that webserver runs under.  This way there's no chance of having permission issues.  An alternative is to share a group that has write permissions.  More info here: https://learn.getgrav.org/troubleshooting/permissions

I'm currently seeing a similar error message when trying to use bin/gpm:
PHP Fatal error: Uncaught RuntimeException: Opening file for writing failed on error fopen(/var/www/redacted/cache/compiled/blueprints/master-localhost.php):

Now, @kelseyurgo said:

Which was odd because master-localhost.php didn't exist, but master-xdci.renci.org.php did.

Which is interesting, because when I checked the above directory on my machine, I saw that master-localhost.php did not exist, but master-<IP_ADDRESS>.php does. So it seems that in both cases, Grav is looking for the maser-localhost.php file, when the localhost potion might actually be the IP / hostname.


[Bug] [Api] Not refresh workflow list when batch delete workflow failed

Purpose of the pull request
fix #10674

Brief change log

Verify this pull request

This pull request is already covered by existing tests, such as (please describe tests).

Codecov Report

Merging #10706 (c1207f1) into dev (fb8d0c8) will decrease coverage by 0.00%.
The diff coverage is n/a.

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

@@             Coverage Diff              @@
##                dev   #10706      +/-   ##
============================================
- Coverage     40.72%   40.71%   -0.01%
+ Complexity     4820     4818       -2
============================================
  Files           900      900
  Lines         36143    36137       -6
  Branches       3982     3976       -6
============================================
- Hits          14718    14713       -5
- Misses        19971    19973       +2
+ Partials       1454     1451       -3

Impacted Files
Coverage Δ

...org/apache/dolphinscheduler/remote/utils/Host.java
43.47% <0.00%> (-2.18%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
51.38% <0.00%> (-1.39%)
:arrow_down:

...r/plugin/task/sqoop/parameter/SqoopParameters.java
53.33% <0.00%> (-1.34%)
:arrow_down:

...rver/master/runner/task/BlockingTaskProcessor.java
75.60% <0.00%> (-0.30%)
:arrow_down:

...eduler/api/service/impl/DataSourceServiceImpl.java
29.49% <0.00%> (ø)

.../dolphinscheduler/plugin/task/datax/DataxTask.java
0.00% <0.00%> (ø)

...cheduler/plugin/task/api/ShellCommandExecutor.java
0.00% <0.00%> (ø)

...er/api/service/impl/TaskDefinitionServiceImpl.java
24.01% <0.00%> (+0.05%)
:arrow_up:

...hinscheduler/plugin/alert/wechat/WeChatSender.java
29.78% <0.00%> (+0.20%)
:arrow_up:

...olphinscheduler/plugin/alert/email/MailSender.java
51.38% <0.00%> (+0.35%)
:arrow_up:

Continue to review full report at Codecov.

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

@zhuxt2015 Hi, may I ask whether you are still interested in following up with this PR? Thanks : )

It seems that there is still an unresolved comment, cc @songjianet @zhuxt2015 @Amy0104

Close due to inactivity.


Unsound unsafe code in vulkano_utils Context::new

Version of vulkano: 0.33.0
OS: N/A
GPU (the selected PhysicalDevice): N/A
GPU Driver: N/A
Upload of a reasonably minimal complete main.rs file that demonstrates the issue: See below (GitHub won't let me upload a .rs file, for whatever reason)

Issue
vulkano_util's Context::new has an unsound unsafe block at context.rs line 154 - There is no check that the user's closure does not in fact make any calls to the vulkan API, and thus UB can be caused with purely safe code on the user side.
Minimal demonstration:
use std::sync::Arc;
static DEVICE_RW: std::sync::OnceLock<Arc<vulkano::device::Device>> =
    std::sync::OnceLock::<Arc<vulkano::device::Device>>::new();
fn main() {
    let config = vulkano_util::context::VulkanoConfig {
        instance_create_info: vulkano::instance::InstanceCreateInfo {
            enabled_extensions: vulkano::instance::InstanceExtensions {
                ext_debug_utils: true,
                ..Default::default()
            },
            ..Default::default()
        },
        debug_create_info: Some(
            vulkano::instance::debug::DebugUtilsMessengerCreateInfo::user_callback(Arc::new(|_| {
                if let Some(device) = DEVICE_RW.get() {
                    // We now have safe access to the vulkan api where we absolutely should not.
                    // Do crimes.
                }
            })),
        ),
        ..Default::default()
    };
    let context = vulkano_util::context::VulkanoContext::new(config);
    let device = context.device();

    // Give our device to the debug messenger
    let _ = DEVICE_RW.get_or_init(|| device.clone());

    // Do something to trigger a debug message, and behold as unsafety crimes occur.
    println!("Hello, World!");
}

Good catch!

I think fundamentally the issue is that Instance has two constructors, so Context also needs two constructors, which is annoying.
This could be solved by making a wrapper type around the callback function, that can only be constructed unsafely. The safety condition of that wrapper would be "the wrapped function must not call the Vulkan API". Then, the user must promise to follow that condition to construct the wrapper, and then all other parts of the API take that wrapper type and become safe. Essentially, the unsafety is shifted away from the construction of Instance, and onto the construction of the wrapper.


nltk.wsd missing from documentation

The nltk.wsd module is part of NLTK 3.x, but doesn't appear in the online documentation (e.g. http://www.nltk.org/py-modindex.html).

Resolved in https://github.com/nltk/nltk/commit/4df9ff00bccf0ee6d78ddac261c09a58f7d00ab1 and deployed, cf http://www.nltk.org/api/nltk.html?highlight=wsd#module-nltk.wsd

Thanks @davechallis


Succeeded Event Not Firing

In version 0.6.2, the succeeded event is not being triggered on playback. The _beginPlaying event is firing and reporting correctly, but the event dispatcher is never being called for the succeeded event upon audio playback successfully starting as documented.
I've put a temporary fix into a version i've got included in my project, where I'm calling a local function, and it's then behaving as intended, but a little stumped as to why that specific this._sendEvent("succeeded"); isn't behaving as expected.

Will check it out. Any chance you have a sample handy?

Sure...
I'm loading the sounds in a preloader, I believe as documented:
`preloader_one = new createjs.LoadQueue(true, "", true);
preloader_two = new createjs.LoadQueue(true, "", true);
preloader_one.installPlugin(createjs.Sound);
preloader_two.installPlugin(createjs.Sound);
preloader_one.on("complete", preloader_one_complete);
preloader_two.on("complete", preloader_two_complete);
preloader_one.on("progress", preloader_one_progress);
preloader_two.on("progress", preloader_two_progress);
preloader_one.on("error", preloader_error);
preloader_two.on("error", preloader_error);`
And then on in a button press scope, which is aware of the load status of the preloaders, i'm calling the following commands to play the sound:
track = createjs.Sound.play(track_id_list[now_playing], {volume:0}); track.on("succeeded", sound_playing); track.on("complete", sound_finished);
The track.on("complete", sound_finished); is called as expect at the end of the sound, but the track.on("succeeded", sound_playing); never get's called, as mentioned above.
I've got round this by putting a call to sound_playing in soundjs in the p._beginPlaying function on line 5990 (in combined).
Let me know if I you need anything else to give it context.
Nice one.

Interesting. Will definitely check it out.

Interesting. Will definitely check it out.

So it looks like this is actually impossible using play because the "succeeded" event is called synchronously. In order to get "succeeded", you have to create the instance first, or call play() on an existing instance:
var inst = createjs.Sound.createInstance(...);
inst.on("succeeded", fn);
inst.play(...);

Alternately, you can check the playState of the instance, and check for "succeeded".


alex description added

Hi there,
I would like to at first thank you for this very useful repository and I would also like to let you know that I am brining in this pull request, the Alex Robot (with three types of end-effector) from Boardwalk Robotics to this repository.

Hi @kkouhkil,
The meshes are 30MiB, could you try to reduce those a bit ? Meshlab and Blender are usually good solutions for this issue.

Hi @kkouhkil, The meshes are 30MiB, could you try to reduce those a bit ? Meshlab and Blender are usually good solutions for this issue.

Hi there, thank you for your text. I did bring the size down to 19MiB, I would be appreciated to know if it is good enough as each mesh file is now under 1MiB.

This is still big :/
I had a look at the meshes, and I think there is no reason to be that big. And then I found that these are plain ASCII files. I should have seen it earlier, sorry.
With https://github.com/Neizvestnyj/stl-to-obj it seems easy to go down to 11M. Can you do that, and check everything is still OK for your use case ?

I'll handle it and make a release I think

ref. #254

I don't have time for now, so let's merge it. I'll deal with the excessive size in another way.


rename queue-msg

i hate the name of this library, open to suggestions

P-high bc i want to rename this asap


User Bower or some other js package library

We have quite a few JS libraries already and will likely add more over time. Start using a JS package manager to help with installing and upgrading libraries

pull request #234


Enhancement: Update CONTRIBUTING.md with instructions

This PR

[x] updates CONTRIBUTING.md with instructions for using composer scripts

Fixes #817.

Thank you, @svpernova09!


fix case where we missed pushing a JobFailure

we missed pushing the JobFailure in the case when there is a fail queue item limit and the current number of failed items is 0
the fix is to call rpush in this case as well

nice catch, any way we can have a testcase for this ?


feat: add prop to include deep nesting

Description

updates the prop function to fetch deeply nested attributes. It works the same way as the path.
it also ensures it runs faster recursively

closes #3426
Type of change

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

How Has This Been Tested?

Run npm test and npm run browser_test

Hi @ridge-kimani , we have R.path for this.

Hello @kedashoe. Yeah sure. I saw the need to add deep nesting to extend R.prop functionality to be similar to R.path.
Is there a major "choice" difference between "Prop" and "Path"? Why would I pick "Prop" over "Path" if I don't have a nested object?
I felt like having the two functions working similarly wouldn't break a sweat if it comes down to picking either or.
It also runs faster compared to the path fn.

As an isolated change, this introduces a great inconsistency in Ramda's API.
Where they now accept a property name, all the various *prop* functions (eqProps, props, propSatisfies, ...)  would have to accept property name arrays as arguments too. All the has* functions too – I guess – because they serve a related purpose.
In Ramda, the name "prop" refers to an established mental image/concept which is of great benefit when reasoning about code.

I have to agree with @kedashoe , this function already exists as R.path. If we really wanted this functionality, I feel like it would make more sense to upgrade R.path to also support props, as it already is the function that does "more"? Or just have a new function that decides whether to call prop or path?
I also ran a quick benchmark of path and this new prop function, and it runs significantly slower when inputting an array. This is likely due to creating a lot of new functions due to using curried and arrow functions, creating some new arrays in reduce and not exiting when possible.
// inputting arrays for nested values
path arr      x 5,773,850 ops/sec ±1.52% (20 runs sampled)
prop arr     x 158,810 ops/sec ±0.62% (24 runs sampled)

// inputting string / [string] to get prop
path str      x 4,316,608 ops/sec ±0.88% (23 runs sampled)
prop str     x 4,556,412 ops/sec ±0.84% (23 runs sampled)

I've seen it will also have some inconsistencies with other functions like props which rely on it. If there's any signficant improvement to be done it would make sense to be in the R.path function.
Thanks for the feedback.
I will close this issue.


Pull additional route parameters out of the JSON API request object

When designing RESTful API's you often want to use url's with additional context like this:
https://api.local/v1/customer/{customerId}/invoice/{invoiceId}

The current JSON API request makes it hard to pull out all named route parameters before the json api request part of the URL starts. There should be an easy to use mechanism to fetch named route parameters from the request, in addition to the existing id method. Without having that feature, one has to find a workaround to bypass the application default request object to the request handler without using the default json api tools.

After looking into this, I came to the conclusion to not implement a new default mechanism to manage route parameters or any other additional request features, since most of it is framework dependent and therefor depends on the requirements of the implementation. Instead, we can include any custom objects or parameters when initializing the request handler classes in the json api server scenario. Let's try a Laravel implementation as demo:
/** @var \Psr\Http\Message\RequestInterface $psrRequest*/
$jsonApiRequest = JsonApiRequest::createFromHttpRequest(
    $psrRequest,
    $this->server->createRequestBody($psrRequest->getBody()->getContents()),
    null
);

/** @var \Illuminate\Http\Request $request */
foreach (config('jsonApi.handler') as $type => $handlerClass) {
    $handler = new $handlerClass();
    if ($handler instanceof AbstractCustomRequestHandler) {
        $handler->setLaravelRequest($request);
    }
    $this->server->addHandler($type, $handler);
}

In the above example I would create a custom AbstractRequestHandler which would either include a custom constructor parameter for the Laravel request or a setter. Using that pattern, we can inject any custom parameter into the request handler. However, to reduce the memory load which is required to hold all instantiated request handler classes, while only one of them is needed to handle the request, it would be good if the addHandler method would support callables, so only the used request handlers would be instantiated when needed. I will create a follow up for that feature request.


Fine grained access control for environments

Is your feature request related to a problem? Please describe.
All developers on our project are able to access all environments, so everyone can access customer/production data and possibly accidentally delete it.
Describe the solution you'd like
A possibillity to control the access of the cli features and if best the access of the resources itself. The most important feature would be to allow users just to access certain environments.
Describe alternatives you've considered
I tried doing that via IAM and the resource restriction is possible, but i cant control the access per environment. Also its very exhausting to keep up with all resource changes.

@Jupdi thanks for the suggestion, but the CLI itself has no authorization model builtin and the security aspects you are looking for must be done at AWS level. In the team workflow docs page we provide some possibilities on how teams could work, individual account per team member give the best isolation so everyone can be admin and as no sensitive data like credentials or anything saved by Amplify into the source files, Prod, Staging, etc environments should be secured by the AWS provided ways as well, accessed by only CI/CD servers and such. That kind of fine grained auth is out of scope for the CLI.

@Jupdi thanks for the suggestion, but the CLI itself has no authorization model builtin and the security aspects you are looking for must be done at AWS level. In the team workflow docs page we provide some possibilities on how teams could work, individual account per team member give the best isolation so everyone can be admin and as no sensitive data like credentials or anything saved by Amplify into the source files, Prod, Staging, etc environments should be secured by the AWS provided ways as well, accessed by only CI/CD servers and such. That kind of fine grained auth is out of scope for the CLI.


Move 'klips-api' to 'klips-sdi'

moves the repository https://github.com/klips-project/klips-api to this repo
makes development easier

Feel free to merge.


drawer from the top

is this possible to set the position to draw out from the top bar??

You can change params in  method createView() in ActionSheet.java margin bottom params like this
params.gravity = Gravity.BOTTOM;

to
params.gravity = Gravity.TOP;


Set dynamically height of editor acording to content for read only mode.

I have integrated TinyMCE editor 6 to .NET 7 blazor web assembly app according to official doc.
https://www.tiny.cloud/docs/tinymce/6/blazor-ref/
https://www.tiny.cloud/docs/tinymce/6/blazor-cloud/
Nuget packages:
<PackageReference Include="TinyMCE" Version="6.4.2" />
<PackageReference Include="TinyMCE.Blazor" Version="1.0.4" />

I'm using TinyMCE Editor component also for 'read only' mode and I have issue with setting dynamically height of editor acording to content.
I'm using currently autoresize plugin, but it has some bug and it not always resize editor correctly. Sometimes I can see just first 3 lines of text. This bug happens totally randomly.
This is how it looks like if it will not resize correctly.

This is how it looks like if it will resize correctly.

<MudCard>
      <MudCardContent>
            <Editor
                Value="@_html"
                Conf="@_editorReadOnlyConfig"
                Disable=true
                ScriptSrc="/lib/tinymce/tinymce.min.js"
            />
     </MudCardContent>
</MudCard>

    private readonly Dictionary<string, object> _editorReadOnlyConfig = new()
    {
        { "plugins", new string[] { "autoresize" } }, // https://www.tiny.cloud/docs/plugins/opensource/autoresize/
        { "toolbar", false },
        { "menubar", false },
        { "statusbar", false },
    };

Any ideas how to deal with this?
Can i do the same thing just with css?
I'm using Editor component in readonly mode to view html because the blazor app will break all css if i would render the html as MarkupString.
Thank you!

Ref: INT-3183

I hacked it by invoking tiny mce command 'autoResizeCommand' 500ms after blazor component with editor is initialized. Which is really nasty fix. See code below.
Can you add to  component event which will fire after content is loaded or something like that? I think         calling StateHasChanged() after content is loaded is sufficient.
@using TinyMCE.Blazor

<Editor Value="@HtmlString"
        Conf="@_editorReadOnlyConfig"
        Disable=true
        ScriptSrc="/lib/tinymce/tinymce.min.js" />

public partial class ReadonlyEditor
{
    private readonly Dictionary<string, object> _editorReadOnlyConfig = new()
    {
        { "plugins", new string[] { "autoresize" } }, // https://www.tiny.cloud/docs/plugins/opensource/autoresize/
        { "toolbar", false },
        { "menubar", false },
        { "statusbar", false },
    };

    [Inject]
    public IJSRuntime JSRuntime { get; set; } = default!;

    [Parameter, EditorRequired]
    public string HtmlString { get; set; } = default!;

    protected async override Task OnInitializedAsync()
    {
        await Task.Delay(500);
        await JSRuntime.InvokeVoidAsync("autoResizeCommand");
        await base.OnInitializedAsync();
    }
}

window.autoResizeCommand = () => {
const global = typeof window !== 'undefined' ? window : global;
try {
    global.tinymce.activeEditor.execCommand('mceAutoResize');
} catch (e) {
    console.log(e);
}

}

Okey, Can you add to component event which will fire after content is loaded or something like that? I think calling StateHasChanged() after content is loaded is sufficient. this was too abcisious claim :D this is not true. It works just with executing autoResizeCommand command after 500MS. Can I do this with some tiny mce event?
I have tried this but it did not worked:
window.editorEventsConfiguration = {
     setup: (editor) => {
        editor.on('LoadContent', (e) => {
            console.log('The Editor has load content.');
            try {
                editor.activeEditor.execCommand('mceAutoResize');
            } catch (e) {
                console.log(e)
            }
        });
    },
   init_instance_callback: (editor) => {
       editor.on('ExecCommand', (e) => {
           console.log(`The ${e.command} command was fired.`);
        });
        editor.on('LoadContent', (e) => {
            console.log('AAAAAAAAAThe Editor has initialized.');
            editor.activeEditor.execCommand('mceAutoResize');
       });
    }]
}

@using TinyMCE.Blazor

<Editor Id="@_editorId"
        Value="@HtmlString"
        Conf="@_editorReadOnlyConfig"
        JsConfSrc="editorEventsConfiguration"
        Disable=true
        ScriptSrc="/lib/tinymce/tinymce.min.js" />

This code throws
window.editorEventsConfiguration = {
    setup: (editor, tinyEventHandler) => {
        tinyEventHandler.bindEvent(editor, 'Load', (e) => {
            try {
                editor.execCommand('mceAutoResize');
            } catch (e) {
                console.log(e);
                console.log('Load');
            }
        });
        tinyEventHandler.bindEvent(editor, 'LoadContent', (e) => {
            try {
                console.log(editor)
                editor.execCommand('mceAutoResize');
            } catch (e) {
                console.log(e);
                console.log('LoadContent');
            }
        });
    },
}

this error:
tinymce.min.js:4 Uncaught TypeError: Cannot read properties of undefined (reading 'getRng')
at tinymce.min.js:4:382988
at tinymce.min.js:4:383369
at mceFocus (tinymce.min.js:4:383375)
at $O.execCommand (tinymce.min.js:4:383961)
at kT.execCommand (tinymce.min.js:4:411066)
at kT.focus (tinymce.min.js:4:410376)
at $O.execCommand (tinymce.min.js:4:383820)
at kT.execCommand (tinymce.min.js:4:411066)
at kT. (main.min.js:1:233)
at JO.dispatch (tinymce.min.js:4:386989)
Any ideas how to force editor resize?

Okey I hacked this bug with better solution. I try to execute every 100 ms autoResizeCommand command until it succeeds.
    protected async override Task OnInitializedAsync()
    {
        bool success;
        do
        {
            await Task.Delay(100);
            success = await JSRuntime.InvokeAsync<bool>("");
        }
        while (!success);

        await base.OnInitializedAsync();
    }

window.autoResizeCommand = () => {
    try {
        const global = typeof window !== 'undefined' ? window : global;
        if (global.tinymce && global.tinymce.activeEditor) {
            global.tinymce.activeEditor.execCommand('mceAutoResize');
            return true;
        }
        return false;
    } catch (e) {
        return false;
    }
}


docs: describe Moov Accounts a bit better

From some descriptions Wade posted in slack.

Codecov Report

Merging #50 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #50   +/-   ##
=======================================
  Coverage   64.66%   64.66%
=======================================
  Files          11       11
  Lines         784      784
=======================================
  Hits          507      507
  Misses        204      204
  Partials       73       73

Continue to review full report at Codecov.

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


Smith generates wasm files with elem.drop even with bulk memory disabled

elem.drop is part of bulk memory, but it is emitted by this command:
$ wasm-tools smith input.dat -t -o /dev/stdout --bulk-memory false | grep elem.drop
      elem.drop 1
      elem.drop 1
        elem.drop 2
      elem.drop 2
            elem.drop 2

Tested on latest release, wasm-tools-1.0.54-x86_64-linux/.
input.dat.gz

Thanks for the report! Should be fixed in https://github.com/bytecodealliance/wasm-tools/pull/1326


track contributors endpoint returns a 404 error: {"status":404,"subStatus":2001,"userMessage":"Resource not found"}

The track contributors endpoint is not working for me. The error is in the description. I'm quite new to this repo but all the endpoints I've tested so far work fine. What is the issue here?

Hi,
Maybe there are no contributors available for the track? Have you tried it with other artefacts?

My bad. My code was the problem. It works now.


Cheat Future

What is the future of the read? Is it finally abandoned?
Your work is awesome.

It's not abandoned, but the work is happening in a private repo for now. With how aggressive the recent vac updates have been I don't think I can keep it undetected for long if it was public. Once I lose interest in developing it further I will probably release the code.

It's not abandoned, but the work is happening in a private repo for now. With how aggressive the recent vac updates have been I don't think I can keep it undetected for long if it was public. Once I lose interest in developing it further I will probably release the code.

The CVars for backtracking (cl_interp and cl_updaterate) where removed, what should we replace them with?

The CVars for backtracking (cl_interp and cl_updaterate) where removed, what should we replace them with?

right now I just have
float calc_lerp() noexcept {
    return 0; // FIXME: figure out how this works in cs2
}

works fine-ish but probably isn't accurate in many cases. I'll re-write the entire backtrack at some point properly, maybe...


🐛 [Bug]: Canvas API Flag rendering issue

Describe the bug
When you press the 'Show canvases' button multiple times it breaks the flag
To Reproduce
Steps to reproduce the behavior:

Go to https://webapis-playground.vercel.app/demo/canvas-api
Click on Show Canvases multiple times

Expected behavior
Flag should stay the same.
Screenshots

Desktop (please complete the following information):

OS: Windows 11
Browser: Chrome
Version: Latest

I would like to work on this

I would like to work on this

Please take it.

@atapas I have already completed the fix.
@ansh-saini May be you can take a look at my code to check.

@atapas You can take a look at these bugs for which fix is already developed but need to be pushed.
https://github.com/atapas/webapis-playground/issues/175
https://github.com/atapas/webapis-playground/issues/176


TraceMismatchError when using trace decorator

Hi!
I faced this error when I followed instruction on the MegEngine Page to train a simple CIFAR-10 model.
Here is the error:

It seems the JIT part doesn't work when I use @trace(symbolic=True) or @trace(symbolic=False) during Training or testing. I could run the code when I remove this decorator. It seems the JIT doesn't work. I was using Python 3.8 and Ubuntu eviroment 18.04. Where Can I find procedure to install JIT for MegEngine correctly?
Thanks!

trace accepts tensor as input not numpy array, so you can do following before calling to traced function:
data = mge.tensor(data)
label = mge.tensor(label)

then it will work as expected.

trace accepts tensor as input not numpy array, so you can do following before calling to traced function:
data = mge.tensor(data)
label = mge.tensor(label)

then it will work as expected.

I don't think this problem is due to not correct type. When I use trace decorator in prediction, it should use @trace(symbolic=True, capture_as_const=True)
The input pred and label have already been converted to tensor.
After I changed the decorator input, the problem is fixed.
But, I strongly suggest you to update the instruction on the official website.
Thank you!

@megvii-mge

trace accepts tensor as input not numpy array, so you can do following before calling to traced function:
data = mge.tensor(data)
label = mge.tensor(label)

then it will work as expected.

I don't think this problem is due to not correct type. When I use trace decorator in prediction, it should use @trace(symbolic=True, capture_as_const=True)
The input pred and label have already been converted to tensor.
After I changed the decorator input, the problem is fixed.
But, I strongly suggest you to update the instruction on the official website.
Thank you!

Happy to see you have solved the problem!
However, I want to mention something here: it's not necessary to use symbolic=True and capture_as_const=True specifically. In general symbolic(True) and symbolic(False) should give you the same results, they are just different ways for tracing which lead to the same endpoint. capture_as_const is required when you want to dump your model, if not, then it's unnecessary.
BUT, We do need to update our online tutorials, that's a very good suggestion!!! @MegChai

@yzchen  Thanks for the mention! Good idea. Actually, I had updated the doc website just a few hours ago before this issue was created. Some content has been reorganized.
According to @JackSnowWolf 's feedback,
it seems that the current document is not clear enough for the explanation of the parameters that the trace accepts. I am planning to add some explanation about capture_as_const on trace page and give a link to dump page.

There is no need to set the parameter capture_as_const=True each time while we using jit.trace .

The input pred and label have already been converted to tensor.

I'm not sure about this behavior in given codes so it might need to show more details.

Thank you for your response!
Actually, I tried several times.

The first time, I only use @trace during training and predicting. It's okay to use trace during training, but there is an error when predicting, which is TraceMismatchError.
The second time, I remove that decorator and run the script successfully.
After that, I use @trace(symbolic=True, capture_as_const=True) during predicting and run the script successfully.
Then, @yzchen and @MegChai talked about the input type issue. #163 (comment) I tried to input a tensor pred and an nd.array label. But this time I got a different error, which is about invalid operation between type tensor and nd.array.

@MegChai I'm not very sure about that whether capture_as_const is required during predicting, but the exception is reported inside the eval_func. Maybe I dump the model after this step, but I guess this operation is unknown or unpredicting in this stage. I guess such kind of error should be reported in the dump operation. If you can locate the error, that that's great.

@JackSnowWolf  I guess I have got your point.

The first time, you explicitly converted the input training data and label to Tensor type in the training code but forgot to do the same work during predicting. This may be due to some old-fashioned official tutorials, our tutorial is keeping updated recently. Now we clearly know the tutorial should remind the user to convert the type.
The second time, you remove that decorator. In dynamic graph mode, the input ndarray will be implicitly converted to Tensor.  (But not for all operators, so we still suggest do explicitly conversion) Everything works.
capture_as_const=True will capture global vars or closures as const value including ndarray vars, so it will make thing seems right. But it was not the recommended way.
The last situation: " I tried to input a tensor pred and an nd.array label. "

Note that the label should also be converted to Tensor:
data = mge.tensor(data)
label = mge.tensor(label)  # Notice this line

Please have a try again~

Could you please give us the complete code here? So we can reproduce the error. It's the most efficient way to find the actual reason. By the way, there are many examples in MegEngine/Models that might be helpful.
I think this bad user experience is caused by our incomplete docs, welcome to give us more suggestions.

I guess I've already got your point. The misunderstanding is mainly due to unclear error message. I guess It should report invalid error type instead of TraceMismatchError. Maybe it's a good idea to also add implicit type convert for trace option.
Thank you for your answer and your updating the official page.