add example how to provided Gogo commands

I was not aware that if we use a component to provide functions (see ComponentSingle and ComponentMulti) we need to provide a service.
At least for me it does not work without the service field of the component annotation.

Thank you for this Pull Request. Expanding the set of enRoute examples is a good thing, and we appreciate the input.
In this case there are a number of things that would need to be fixed before this example could be included in enRoute. Some of these are stylistic (e.g. we are encouraging the use of OSGi R7 over older alternatives) and others are more significant (the enRoute examples must follow OSGi best practices).
The other important thing is that each example must be accompanied by a page on the enRoute site which describes the layout of the example, and the key lesson that it is trying to teach.

we are encouraging the use of OSGi R7 over older alternatives
the enRoute examples must follow OSGi best practices

To which part of the code do you refer to?
Do you refer to the ServiceSingle and ServiceMulti class?
I just want to show the difference options to provide the Gogo commands.

use programmatic service registration

provide a single function
provide multiple functions

use components

provide a single function
provide multiple functions

Can you point me to some documentation?

Can you point me to some documentation?

One of the main purposes of enRoute is to provide this documentation because so little of it exists. Sadly this does make our lives harder.

To which part of the code do you refer to?

There are a few places with separate issues - we use the GitHub review system which will hopefully make it clear what/where they are.

I just want to show the difference options to provide the Gogo commands.

use programmatic service registration

provide a single function
provide multiple functions

Use of the programmatic API is discouraged in enRoute. The purpose of the examples is to demonstrate good practice using R7. As per the about page:
"enRoute is not intended to be an encyclopedia for experienced OSGi developers, nor is enRoute aligned with any particular open source initiative. enRoute is intended to be a useful toolbox, and to give a solid understanding of the basics of OSGi."
This means (amongst other things) that we don't use the low level APIs because years of experience have taught us that they are not basic.

@timothyjward Thank you for your comments.
The four classes (component and service) could be merged into one single component that shows how to add at least two functions (with respect to your comment above). This should be enough for an working example.
As long as there are no component property types or osgi.implementation capability provided by Gogo, I assume there is no change for such an example.

As long as there are no component property types or osgi.implementation capability provided by Gogo, I assume there is no change for such an example.

In the absence of component property types provided by Gogo I would expect this example to create its own, and for the docs to explain how that works. Component Property types are mostly supposed to be user-created, and this would be quite a good example of how to use them.
As for the osgi.implementation capability. I think this is a bug that needs to be raised against Gogo (how else will things improve?) and we can look to see whether there is anything else sensible to require in the meantime.

In the absence of component property types provided by Gogo I would expect this example to create its own

I have done it already and I agree this will make the stuff much cleaner without the need to use "magic" constants.

Now that the code is in place it will be possible to refer to it in the website documentation if you update the checked out submodule.

@timothyjward Perhaps you already know, but see https://issues.apache.org/jira/browse/FELIX-5970

Sorry @timothyjward first I have been very busy, then I missed it...
Do you know if Raymond has already added the required annotations?

@maggu2810 yes they are in the latest gogo versions. Note there's also a gogo bom now for convenience. org.apache.felix:org.apache.felix.gogo.bom:1.0.2


Microoptimizations in CachingHiveMetastore

Three parts here:

Adds a benchmark for baseline. This commit will be discarded because it's not generally useful, only necessary to show the benchmark code used. The benchmark itself is set up to fetch twice as many partitions per iteration than the cache allows. This guarantees that some large proportion of cache churn per iteration.
Refactors the code in CachingHiveMetastore to prefer re-using the WithIdentity keys to recreating them. The effect is that partition values need not be re-parsed from the partition name string, fewer objects are allocated, and the returned keys are alias equals to the stored cache key.
Adds a cached hashCode field to WithIdentity. Since these classes are only used in cache key form, the work is never wasted and can be used to speed up equals at the same time. However, this adds 8 bytes (4 bytes from int, 4 bytes waste from alignment) per instance. I've included it in this PR for consideration comparing the results below, but am interested to hear how others feel about the trade-off of CPU time vs memory consumption. I'm happy to drop this commit too if others think the memory overhead isn't worth the performance gain.

Below, benchmark runs from my laptop. TL;DR:

Refactored code achieves ~1.25x better throughput than baseline
Refactored code with cached hashCode achieves ~1.7x better throughput than baseline

Baseline Benchmark Run
Benchmark                                                 (cacheSize)  (databaseCount)  (identityCount)  (partitionColumnCount)  (partitionsPerCall)  (partitionsPerTableCount)  (tableCount)   Mode  Cnt     Score     Error  Units
BenchmarkCachingHiveMetastore.benchmarkGetPartitionStats           50                1                3                       5                  100                       1000            10  thrpt   10  4836.039 ± 532.213  ops/s
BenchmarkCachingHiveMetastore.benchmarkGetPartitions               50                1                3                       5                  100                       1000            10  thrpt   10  5803.520 ± 311.179  ops/s

Refactor Only, no precomputed hashCode
Benchmark                                                 (cacheSize)  (databaseCount)  (identityCount)  (partitionColumnCount)  (partitionsPerCall)  (partitionsPerTableCount)  (tableCount)   Mode  Cnt     Score     Error  Units
BenchmarkCachingHiveMetastore.benchmarkGetPartitionStats           50                1                3                       5                  100                       1000            10  thrpt   10  5808.788 ± 222.566  ops/s
BenchmarkCachingHiveMetastore.benchmarkGetPartitions               50                1                3                       5                  100                       1000            10  thrpt   10  7699.901 ± 125.262  ops/s

Refactored Code, with precomputed hashCode
Benchmark                                                 (cacheSize)  (databaseCount)  (identityCount)  (partitionColumnCount)  (partitionsPerCall)  (partitionsPerTableCount)  (tableCount)   Mode  Cnt     Score     Error  Units
BenchmarkCachingHiveMetastore.benchmarkGetPartitionStats           50                1                3                       5                  100                       1000            10  thrpt   10  8419.244 ±  74.695  ops/s
BenchmarkCachingHiveMetastore.benchmarkGetPartitions               50                1                3                       5                  100                       1000            10  thrpt   10  9835.061 ± 203.398  ops/s

@dain benchmark commit dropped, ready for merge.

Test failure seems unrelated


Option to disable key binding tips

Could you please add a settings option to disable the "key binding" tips that are displayed in the main area when no files are open? Some may find them helpful. I find them very distracting.

The package name is atom-background-tips.

You can disable this feature by disabling the background-tips package:

Hope that helps!

Great, thanks!


Please do no embrace Manifest V3 in Edge Browser

Any chance that this decision to use Manifest V3 from google can be deferred or even rejected for use with Edge browser?
Google's real intent of stopping the use of ad blockers should not be embraced by the wider Chromium based browsers, including Edge browser from Microsoft.
Or, as you will, fully embrace it publicly so users can outright then reject using Edge and all other Chromium based browsers.
It's shameful really on Microsoft's part that you would openly and eagerly accept such a change pushed and demanded by Google with their hidden intent of forcing adverts and trackers and so on without a users ability to block same, shameful.
Please reconsider following Googles obvious intent to block ad blockers.

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

ID: 815c941b-4a07-481a-9bb5-f8ef3d6b1118
Version Independent ID: 815c941b-4a07-481a-9bb5-f8ef3d6b1118
Content: Overview and timelines for migrating to Manifest V3 - Microsoft Edge Development
Content Source: microsoft-edge/extensions-chromium/developer-guide/manifest-v3.md
Product: microsoft-edge
Technology: extensions
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Thanks for your feedback, unfortunately this isn't the right repository for it.
Here, we only deal with issues and features about the documentation of Microsoft Edge's developer technologies. This isn't a place to discuss the strategic decisions of the product.
I would advise sending your feedback on the Edge tech community forum instead: https://techcommunity.microsoft.com/t5/microsoft-edge-insider/ct-p/MicrosoftEdgeInsider
Thanks for your understanding.


Admin sees extra types at /v1 that don't work

The user who happens to be admin, or everybody if auth is off, sees all sorts of extra types at the root of the API (e.g. registrationTokens, containers) that appear to do things but don't really work because they are resources that can only belong to a environment (/v1/project).
The root /v1 level of API should contain only types that are relevant for a user, even if the user is admin.
If we want to add the behavior that admin has a way to see a collection of e.g. all containers across projects, I propose that goes into a separate namespace like /v1/admin/containers vs a bunch of resources at the top level for admin.

I was allowed to add a container using /v1/containers using user api keys which really did not succeed because of placement error since it was trying to add container with its own ID and not the account Id of the project it belonged to. Should API throw an error in this case , rather than allowing the container to be deployed ?

Yes, that is one example.. a user cannot own hosts so there is nowhere to run it.


Which optimizer to use for large training projects ?

I will be training a large model from scratch with a large dataset and i wanted the training process to be as good as possible. what optimizer is advised in such situations ?

This a topic for the official TF forum. Please post a thread there


Merge branch to main for: fixing Focus problem with WPF ComboBox (related to MaterialDesign v4.1.0 library.

Fixes #182.


Feature request : get all players in radio

Maybe an export to get all players in same/all radio calls

can do i'll add this in the next version (busy with uni coursework rn)


fix: Enable build in pre-montery machines

What is the purpose of the change
PR https://github.com/osmosis-labs/osmosis/pull/1268 introduces a build failure bug on Mac OS <= 11 by the package  zondax/hid.
$ make build
Makefile:75: RocksDB support is disabled; to build and test with RocksDB support, set ENABLE_ROCKSDB=true
go build -mod=readonly -tags "netgo ledger" -ldflags '-X github.com/cosmos/cosmos-sdk/version.Name=sim -X github.com/cosmos/cosmos-sdk/version.AppName=simd -X github.com/cosmos/cosmos-sdk/version.Version=0.46.0-alpha2-160-gf4d50a989 -X github.com/cosmos/cosmos-sdk/version.Commit=f4d50a989fec8ffbc2e640ad492d40f72580064c -X "github.com/cosmos/cosmos-sdk/version.BuildTags=netgo,ledger" -X github.com/tendermint/tendermint/version.TMCoreSemVer=v0.35.2 -w -s' -trimpath -o /Users/danielwedul/git/cosmos-sdk/build/ ./...
# github.com/keybase/go-keychain
cgo-gcc-prolog:203:11: warning: 'SecTrustedApplicationCreateFromPath' is deprecated: first deprecated in macOS 10.15 - No longer supported [-Wdeprecated-declarations]
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Security.framework/Headers/SecTrustedApplication.h:59:10: note: 'SecTrustedApplicationCreateFromPath' has been explicitly marked deprecated here
# github.com/zondax/hid
In file included from ../../go/pkg/mod/github.com/zondax/hid@v0.9.1-0.20220302062450-5552068d2266/hid_enabled.go:38:
./hidapi/mac/hid.c:693:34: error: use of undeclared identifier 'kIOMainPortDefault'
        entry = IORegistryEntryFromPath(kIOMainPortDefault, path);
                                        ^
1 error generated.
make: *** [build] Error 2

Although #1268 does remove unnecessary warning logs on Mac OS >12, I think ensuring successful build upon different machines is way more important, which could be done by reverting 1268(which upgrades the zondax/hid to 0.9.1) and use it as it was 0.9.0
cref: https://github.com/cosmos/cosmos-sdk/issues/11364#issue-1166774561, https://github.com/cosmos/cosmos-sdk/pull/11365
Brief change log

Reverts  https://github.com/osmosis-labs/osmosis/pull/1268

Testing and Verifying
Locally tested in both mac os >12, mac os <= 11 that #1268 fails on mac os <= 11, while it succeeds on mac OS > 12.
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? no
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? no
How is the feature or change documented? not applicable

Agreed with conclusion of lowering library version!

Codecov Report

Merging #1351 (3d8f047) into main (f56fbe5) will decrease coverage by 0.04%.
The diff coverage is 4.00%.

@@            Coverage Diff             @@
##             main    #1351      +/-   ##
==========================================
- Coverage   19.82%   19.77%   -0.05%
==========================================
  Files         202      202
  Lines       27685    27718      +33
==========================================
- Hits         5489     5482       -7
- Misses      21175    21215      +40
  Partials     1021     1021

Impacted Files
Coverage Δ

x/gamm/pool-models/balancer/amm.go
17.58% <ø> (ø)

x/gamm/pool-models/stableswap/amm.go
43.28% <0.00%> (-12.49%)
:arrow_down:

x/gamm/pool-models/stableswap/pool.go
0.00% <0.00%> (ø)

x/gamm/client/cli/tx.go
59.50% <100.00%> (-0.69%)
:arrow_down:

Continue to review full report at Codecov.

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


The type initializer for 'Tweetinvi.TwitterCredentials' threw an exception.

As reported on codeplex: https://tweetinvi.codeplex.com/workitem/2649

This has re-appeared! I can no longer use Auth.SetCredentials(); !

Does the error happens consistently?

Happening with my project too. When requesting the Authentication url from twitter using CredentialsCreator it throws three exceptions:
Exception thrown: 'System.IO.FileLoadException' in Tweetinvi.dll
Exception thrown: 'System.TypeInitializationException' in Tweetinvi.dll
Exception thrown: 'System.Reflection.TargetInvocationException' in mscorlib.ni.dll

Would you be able to share your project?

Yup, here's the repo: https://github.com/prajjwaldimri/Friend-App

Thanks, I will take a look at this when I am out of work.

Alright. Thanks

Install with the following command in nuget :
Install-Package tweetinviapi -version <IP_ADDRESS>-w10-uap -pre
Let me know if this worked out for you.
Linked to https://github.com/linvi/tweetinvi/issues/105


Fix #10

Update IdToken and AccessToken definitions
Change from map[string]map[string]interface{} to map[string]interface{} as per documentations and other clients

Related Issue or Design Document

Checklist

[ ] I have read the contributing guidelines
and signed the CLA.
[ ] I have referenced an issue containing the design document if my change
introduces a new feature.
[ ] I have read the security policy.
[ ] I confirm that this pull request does not address a security
vulnerability. If this pull request addresses a security vulnerability, I
confirm that I got green light (please contact
<EMAIL_ADDRESS>from the maintainers to push
the changes.
[ ] I have added tests that prove my fix is effective or that my feature
works.
[ ] I have added necessary documentation within the code base (if
appropriate).

Further comments

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

Thank you for the PR! Unfortunately this library is autogenerated and any changes made in this PR will be overwritten. You will need to make these changes in Ory Hydra directly (in the go code for example) :)

It's actually should be
// ConsentRequestSession struct for ConsentRequestSession
type ConsentRequestSession struct {
	// AccessToken sets session data for the access and refresh token, as well as any future tokens issued by the refresh grant. Keep in mind that this data will be available to anyone performing OAuth 2.0 Challenge Introspection. If only your services can perform OAuth 2.0 Challenge Introspection, this is usually fine. But if third parties can access that endpoint as well, sensitive data from the session might be exposed to them. Use with care!
	AccessToken interface{} `json:"access_token,omitempty"`
	// IDToken sets session data for the OpenID Connect ID token. Keep in mind that the session'id payloads are readable by anyone that has access to the ID Challenge. Use with care!
	IdToken interface{} `json:"id_token,omitempty"`
}

We fixed this in the OpenAPI spec, but it's not yet released :)

rgr


tests: crypto: rand32 test issue regression

Describe the bug:
in our bench tester many board test fail now  with:
tests/crypto/rand32
for example:
west build -p always -b   nucleo_f746zg  tests/crypto/rand32

test is blocked
it is due to this commit:
https://github.com/zephyrproject-rtos/zephyr/commit/78af1c1e3878c410067bd49846771300fa86b840
entropy: stm32: suspend when pool is full
78af1c1e3878c410067bd49846771300fa86b840
author: Dawid Niedzwiecki<EMAIL_ADDRESS>2023-12-01 11:27:37
Committer: Maureen Helm<EMAIL_ADDRESS>2023-12-05 23:27:53
thanks  to have a look

I've sent a fix to review. Would you be able to confirm it works?
Sorry for the bug.

@Desvauxm-st sorry for a late question. Are the results of your test runs available somewhere or it is an internal thing?

@niedzwiecki-dawid Tests results might be available here: https://github.com/zephyrproject-rtos/test_results/
Updated once/week.
Regarding internal archives, they are not deep enough to be able to retrieve the info that late. Would be easier to re-run test

Thanks for the info. I don't need archive of this test, just asking about access to test results :).

One more question, is there any easy way to read the result? E.g. If I would like to get 5 last results of a specific test for a specific board. Or I just need to grep commits.

TBH, I don't know. @hakehuang might be able to answer as Testing group chairman


Regression: ws feature probably broken in 0.47.0

https://github.com/snapview/tokio-tungstenite/pull/142 means that Tungstenite (the websocket client) is still using Tokio 0.2, which may crash at runtime since it can't find a valid Tokio 0.2 context (since it is distinct from a Tokio 1.0 context).
I missed this in the initial upgrade because most of that work was done before #360 was merged.
In the meantime, use tokio-compat-02 if you need any websocket features.

We don't use tokio-tungstenite (using async-tungstenite with tokio-runtime mainly because that supports rustls) and tungstenite itself doesn't depend on tokio.
ws example is working locally for me on master. But we should get some tests running on Circle CI.

We don't use tokio-tungstenite (using async-tungstenite with tokio-runtime mainly because that supports rustls) and tungstenite itself doesn't depend on tokio.
ws example is working locally for me on master. But we should get some tests running on Circle CI.

We do have bytes v0.5 from multiple crates (http, tungstenite, k8s-openapi (updated but unreleased)) though.

We do have bytes v0.5 from multiple crates (http, tungstenite, k8s-openapi (updated but unreleased)) though.

Examples are running with and without the ws feature since #394, and tokio is all at >1 in cargo tree, so closing this for now.
CI is at least testing it, although it is struggling a bit under my free circleci plan.


And please use the latest version. Previous version haf an issue.

It seems this issue is old enough, because there were many changes for past 2+ months to enhance the authentication and session flows. Please feel free to reopen it, if it occurs again.


Gf chj

gutil test 2019 06 15 21:06

@2892931976 CI没有过

以修改

Codecov Report

Merging #210 into master will increase coverage by 3.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #210      +/-   ##
==========================================
+ Coverage   73.18%   76.25%   +3.06%
==========================================
  Files         204      204
  Lines       17558    17558
==========================================
+ Hits        12849    13388     +539
+ Misses       4024     3534     -490
+ Partials      685      636      -49

Impacted Files
Coverage Δ

g/container/gtree/gtree_avltree.go
97.5% <0%> (-1%)
:arrow_down:

g/container/gtree/gtree_btree.go
91.87% <0%> (-0.68%)
:arrow_down:

g/net/ghttp/ghttp_response_cors.go
0% <0%> (ø)
:arrow_up:

g/container/gtree/gtree_redblacktree.go
96.95% <0%> (ø)
:arrow_up:

g/os/gtimer/gtimer_entry.go
88.5% <0%> (+3.44%)
:arrow_up:

g/util/gconv/gconv_struct.go
76.16% <0%> (+9.3%)
:arrow_up:

g/util/gconv/gconv_map.go
100% <0%> (+46.55%)
:arrow_up:

g/util/gconv/gconv_time.go
100% <0%> (+55%)
:arrow_up:

g/util/gconv/gconv.go
100% <0%> (+59.93%)
:arrow_up:

g/util/gconv/gconv_slice.go
100% <0%> (+84.36%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


Improving movies app ui

Title
Improving the movies app ui
Project link
[Click here](Paste link of project here)
Domain
Add 'x' inside [ ] to cross check box.

[ ] App with Flutter
[ ] App with Java
[ ] App with Kotlin
[x] Web with Html,css javascript
[ ] Web with React

Describe the Issue
Current ui is simpler with a while bg on hover for overview.
Expected
Changes will make the hover overview little stylish with a contrast background color and opaqe bg.
Screenshots

Additional context
Add any other context about the problem here else write NA.

Cool 👍


Controller Buttons aren't working

Sorry in advance I kinda got into testing mod but the main issue I was having is getting the left and right shoulder buttons to map to controller, so far i can get the left and right triggers to work and the Dpad keybindings worked but whichever d pad binding you use  wont work in the inventory menu anymore while the wand is equipped ( ex. if right is your summon keybinding than you can't move right in the inventory menu while the wand is equipped, tested all 4 and it was the same) DPadUp summons and unequips at the same time and DpadDown summons and uses your forsaken power at the same time as well, and the right trigger destroys the skeletons at the same time that it summons it. all the other options don't do anything. There is also no Controller Keybinding option to summon better skeletons using extra resources.
I attached the cfg and log in the zipfile hopefully that works
ChebsNecromancyBugReport.zip

Hello, thanks for opening the issue.
I'd like to mention in advance that I do not have a controller to test the mod with and, as far as I'm aware, you are the first to use it with a controller. So I'm sorry that you're the first to experience these issues. But fortunately, you can hopefully help me fix them.
It's true that many buttons are doubled up. For example, in the config you sent:
ChebGonaz_SkeletonWandCreateMinionGamepad = DPadRight
ChebGonaz_SkeletonWandNextMinionGamepad = LeftShoulder
ChebGonaz_SkeletonWandFollowGamepad = ButtonWest
ChebGonaz_SkeletonWandWaitGamepad = ButtonEast
ChebGonaz_SkeletonWandTeleportGamepad = SelectButton
ChebGonaz_DraugrWandCreateMinionGamepad = ButtonSouth
ChebGonaz_DraugrWandNextMinionGamepad = ButtonSouth
ChebGonaz_DraugrWandFollowGamepad = ButtonWest
ChebGonaz_DraugrWandWaitGamepad = ButtonEast
ChebGonaz_DraugrWandTeleportGamepad = SelectButton
ChebGonaz_OrbOfBeckoningCreateMinionGamepad = ButtonSouth
ChebGonaz_OrbOfBeckoningNextMinionGamepad = ButtonSouth
ChebGonaz_OrbOfBeckoningFollowGamepad = ButtonWest
ChebGonaz_OrbOfBeckoningWaitGamepad = ButtonEast
ChebGonaz_OrbOfBeckoningTeleportGamepad = SelectButton

A lot of these are set to ButtonSouth. Try making sure that they're all unique and let me know if it works better.

There is also no Controller Keybinding option to summon better skeletons using extra resources.

In the short term, you can disable that button by setting it to nothing which will fix the issue: ChebGonaz_SkeletonWandUnlockExtraResourceConsumption =

@RheaRhe94 did you get it all working?

Other people also having problems: https://youtu.be/JJixlbHBi_M
Hopefully some benevolent contributor can fix this on my behalf. I don't have a controller

In the newest version I was forced to disable controller support completely due to this issue. Sorry about that


Crash when using watch mode v.1

<--- Last few GCs --->

[86779:0x104001c00]  1676975 ms: Mark-sweep 1393.2 (1525.1) -> 1393.0 (1524.1) MB, 804.3 / 0.0 ms  allocation failure GC in old space requested
[86779:0x104001c00]  1677964 ms: Mark-sweep 1393.0 (1524.1) -> 1392.8 (1475.1) MB, 987.8 / 0.0 ms  last resort
[86779:0x104001c00]  1678831 ms: Mark-sweep 1392.8 (1475.1) -> 1392.8 (1463.6) MB, 866.5 / 0.0 ms  last resort

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x38a5b5128799 <JSObject>
    1: DoJoin(aka DoJoin) [native array.js:~95] [pc=0x1f86e945d46f](this=0x3c04e9d02311 <undefined>,p=0x3d03ef2ffce1 <JSArray[2]>,q=2,E=0x3c04e9d023b1 <true>,A=0x3c04e9d02471 <String[0]: >,z=0x3c04e9d02421 <false>)
    2: Join(aka Join) [native array.js:~120] [pc=0x1f86e9476729](this=0x3c04e9d02311 <undefined>,p=0x3d03ef2ffce1 <JSArray[2]>,q=2,A=0x3c04e9d02471 <String[0]: >,z=0x3c04e9d02421 <fal...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/usr/local/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/usr/local/bin/node]
 3: v8::Utils::ReportOOMFailure(char const*, bool) [/usr/local/bin/node]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]
 5: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/usr/local/bin/node]
 6: v8::internal::Runtime_StringBuilderConcat(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
 7: 0x1f86e8e046fd
 8: 0x1f86e945d46f
 9: 0x1f86e9476729
10: 0x1f86e9507154
11: 0x1f86e93f598d
12: 0x1f86e8ef9f5c

Often see things like this and crash when mocha-webpack --watch --interactive true is run.
Using "mocha-webpack": "^1.0.0-rc.1",

Hello,
I am facing exactly the same issue, any idea why this is happening? Many thanks!
Cheers


Added section on ASP.NET Core distributed caching

What issue does this PR address?
https://github.com/IdentityServer/IdentityServer4/issues/4371
Does this PR introduce a breaking change?
no
Please check if the PR fulfills these requirements

[x] The commit follows our guidelines
[ ] Unit Tests for the changes have been added (for bug fixes / features)

Other information:

Great, thanks!


Try to improve support for .notdef glyphs through FontTweak

The idea consists of adding fallbacks to the FontTweak structure, which then get used in egui's Font (actually a wrapper over multiple FontImpl) to identify fallback characters. We look through each wrapped FontImpl, stopping in the first fallback character we found, defaulting to the empty glyph if none is found.
Example output when replacing the user font by MaterialSymbolsSharp in the egui custom font example:

impl eframe::App for MyApp {
    fn update(&mut self, ctx: &egui::Context, _frame: &mut eframe::Frame) {
        egui::CentralPanel::default().show(ctx, |ui| {
            ui.heading("\u{E834} egui using custom fonts");
            ui.text_edit_multiline(&mut self.text);
        });
    }
}

Note that as it is (mostly due to my very limited understanding of fonts in general), this isn't enough to load .notdef properly, even with a user-definied fallback character set. I suspect this however has to do with ttf_parser seemingly not actually loading .notdef.

Closes https://github.com/emilk/egui/issues/3526 (this one was technically originally closed by https://github.com/emilk/egui/pull/4542)
See https://github.com/emilk/egui/issues/4642

When would you want to have a different replacement char?

Whenever the default replacement character of a font is neither the empty square nor that font has a question mark, which is the case for Material Symbols Sharp:


Hotifx 4.0.10

Fixed using custom profile and custom user class.
Before, [SCUser currentUser] was being instantiated before custom classes could have been registered -- because of that currentUser was always of class SCUser and profile always of class SCUserProfile .
@jaskooo @trapi
I have a problem with tests here, not sure how to write them.
The issue wasn't discovered in current tests, because we log out user out after each single test (which clears user object saved on disk).
The issue is only visible when there is a user object on disk. Any suggestions?

I'm thinking now - maybe we should also clean the _currentProfile variable after each successful call to registerClassWithUserProfile:? (not remove it from user defaults, just set the variable to nil)
This way, we could theoretically swap user profile classes multiple times during one runtime - doing it currently will crash. Probably not really a common use, but sounds neat :)

Code looks good.


[Draft] layer-local dask cache

Description
Following some conversations on zulip, here's a proof of principle approach that would have us move away from a global dask cache, and allow each dask-backed layer to have it's own dask cache that only gets activated in a context manager surrounding _set_view_slice
The key here is that the configure_dask function creates a closure on a dask Cache, which the layer can then use in
with layer.dask_optimized_slicing(): ...
cc @perlman, @jni

note: an alternative here is to not create layer-local caches (i.e. keep the global utils.dask_cache ...) but rather than calling cache.register here:
https://github.com/napari/napari/blob/c6df8cfb4155d6314796ed4e7c5334646ed75665/napari/utils/dask_utils.py#L47
add it to the context manager here:
https://github.com/napari/napari/blob/c6df8cfb4155d6314796ed4e7c5334646ed75665/napari/utils/dask_utils.py#L184

In principle I love this, but I still have questions:

what is the lifetime of this cache object? Will it get cleared when I delete the layer?
how can I control this cache from napari? For dynamic operations like napariboard, we actually want the cache off. It would be pretty awesome if we could control the cache behaviour per layer!

what is the lifetime of this cache object? Will it get cleared when I delete the layer?

that would be my assumption, but we can test it.  If you grab a dask layer created by napari.add_image in the current PR, you'll  see the actual cache object at layer.dask_optimized_slicing.__closure__[0].cell_contents.__closure__[0].cell_contents.cache ... I believe that closure is probably the only reference to that cache and will likely be collected with the layer.

how can I control this cache from napari? For dynamic operations like napariboard, we actually want the cache off. It would be pretty awesome if we could control the cache behaviour per layer!

we'd need to add a new layer parameter, or a settings object and or context manager (still coming, promise)

This is ready for review.  I know @jni already approved it... but here's what's changed since then (chatted with @jni on zulip to make sure he's ok with the changes).  This PR turns dask caching behavior back on by default.  However, unlike the previous implementation, this PR no longer calls cache.register() globally, which means it should not affect dask caching behavior for anyone using dask arrays outside of napari layers.
Instead, the cache is added to the "dask_optimized_slicing" context manager here, which gets used only in the set_view_slice method here.  There is a still a single global cache (which is desirable, so they can all share that space)... it's just not "always on".
because @jni mentioned that he'd like some layers to be able to opt-out of caching, there is a new Layer.__init__ parameter called cache, which defaults to True.  by setting it to False, a single layer can opt out of caching.  And to generally opt-out of caching, one can still use resize_dask_cache(0) as before.
This PR does remove the utils.dask_cache variable... I don't think that would have been used by anybody, but technically it was in a public namespace, so just pointing that out.

@tlambert03 I still approve of this, and was going to move to "awaiting merge", but the test failure is on MINREQ is genuine, unfortunately!


Multiple language output.

I'd ask for a feature to add additional languages to output. Sometimes chatting in a group with multiple asians requires constant switch between languages.

The limiting factor here is currently the maximum characters the chatbox allows. So, adding multiple outputs is going to fill the chatbox really quickly. I will look into it but cannot guarantee that I will be able to do it.

The limiting factor here is currently the maximum characters the chatbox allows. So, adding multiple outputs is going to fill the chatbox really quickly. I will look into it but cannot guarantee that I will be able to do it.

Oh, for real. Thank you for looking into this. Maybe add an option to disable, for example, the showcase of original language? And adding some kind of a meter that says when the message is too long (So you could calibrate your mind;saying to fit in limited length). I remember having problems with long sentences, yes.


Fix clear element(x) with canDeselect

Fix clear element(x) showing on the right when canDeselect = false
References this issue: https://github.com/vueform/multiselect/issues/61

Added canClear prop which allows you to control the clear button regardless of canDeselect.


add NGINX implementation of proxy_set_header Forwarded

Type of Change

Tool Source:

generators/conf/nginx.conf.js
generators/conf/proxy.conf.js
templates/global_sections/reverse_proxy.vue
localizations (EN done, others need translating)

What issue does this relate to?
Closes #270
What should this PR do?
Add NGINX implementation of Forwarded header with two options for coexistence with X-Forwarded-*
What are the acceptance criteria?
Tests pass
New mappings and proxy_set_header Forwarded $proxy_add_forwarded; populate as default
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; populates as default
proxy_set_header X-Forwarded-For ""; populates as option

Interesting change.

Could you make sure the copyright year is updated in the header of each file that you've updated as well, please? :)
Functionality-wise this is looking great, just a couple small things:

Oof, forgot the copyright update in PR #272 too. Want another PR for that one?


Delete a connector

Description

Design

Task list

[ ] #1475

Closing as it it part of this epic: #1155


Release 0.9.0

Bumping dependencies to prepare for 0.9.0 release.
This is blocked by #228

Issue is because of https://github.com/timescale/promscale/pull/1126

Blocked by #231

Current release blockers and their completion status:

[ ] timescaledb chart being published
[ ] https://github.com/timescale/promscale/pull/1159
[ ] https://github.com/timescale/tobs/pull/249
[ ] https://github.com/timescale/tobs/pull/246
[ ] https://github.com/timescale/tobs/issues/244
[ ] https://github.com/timescale/tobs/issues/238

All hard requirements for a release are completed. We can proceed with this PR and create a release.
cc @VineethReddy02 @cevian

@paulfantom the CLI uses version from here to let users know the version of CLI they are using https://github.com/timescale/tobs/blob/master/cli/cmd/version/version.go#L12
And the installer script also uses version tag here this needs to be updated to the latest.

Done.


Fix code in mail subject

fixes #245

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: vinzBad:x: xFeXxYou have signed the CLA already but the status is still pending? Let us recheck it.


controller error on "deis pull" if image already associated with previous release

Setup info:

workflow v2.4.1
using an external registry (quay.io)

$ deis releases -a acceptance
v45	2016-08-28T22:23:19Z	admin deployed quay.io/my_repo/able_rails:16019582573fe2f2f51b0a293de1d19a922afbbf
v44	2016-08-28T20:27:08Z	ci deployed quay.io/my_repo/able_rails:4d5244329212e570fd19ecf0d910b9bac5d9072c
v43	2016-08-28T06:15:31Z	ci deployed quay.io/my_repo/able_rails:16019582573fe2f2f51b0a293de1d19a922afbbf
...

STR:

deploy able_rails:16019582573fe2f2f51b0a293de1d19a922afbbf image from external registry using deis pull
deploy a newer able_rails:4d5244329212e570fd19ecf0d910b9bac5d9072c image using deis pull
deploy same image from step 1 using deis pull
after getting Creating build... Error: Unknown Error (400): {"detail":"(app::deploy): ('failed to update Service \"acceptance\" in Namespace \"acceptance\": 409 Conflict', 'acceptance', 'acceptance')"}, I tried again

As a result, the app was scaled down to no processes:
INFO [acceptance]: Deployment acceptance-worker with release v45 already exists. Stopping deploy
INFO [acceptance]: Deployment acceptance-cron with release v45 already exists. Stopping deploy
INFO [acceptance]: Deployment acceptance-web with release v45 already exists. Stopping deploy
acceptance-web-1647476401-mzrld -- shutting down, got signal: Terminated
acceptance-web-1647476401-pfdwa -- shutting down, got signal: Terminated
acceptance-worker-1374294020-rkxl5 -- shutting down, got signal: Terminated

And I was unable to scale them back up normally:
[seanknox:...ucture/us-east-1/nonphi/k8s]$ deis ps:scale web=1 worker=1 cron=0 -a acceptance                                (master✱)
Scaling processes... but first, coffee!
Error: Not Found

I rolled back a release and was then able to scale processes back up.
Full controller error below:
INFO [acceptance]: admin deployed quay.io/my_repo/able_rails:16019582573fe2f2f51b0a293de1d19a922afbbf
INFO [acceptance]: quay.io/my_repo/able_rails:16019582573fe2f2f51b0a293de1d19a922afbbf exists in the target registry. Using image for release 45 of app acceptance
ERROR [acceptance]: (app::deploy): ('failed to update Service "acceptance" in Namespace "acceptance": 409 Conflict', 'acceptance', 'acceptance')
ERROR:root:(app::deploy): ('failed to update Service "acceptance" in Namespace "acceptance": 409 Conflict', 'acceptance', 'acceptance')
Traceback (most recent call last):
  File "/app/scheduler/__init__.py", line 216, in _update_application_service
    self.update_service(namespace, namespace, data=service)
  File "/app/scheduler/__init__.py", line 1229, in update_service
    'update Service "{}" in Namespace "{}"', namespace, name
scheduler.KubeHTTPException: ('failed to update Service "acceptance" in Namespace "acceptance": 409 Conflict', 'acceptance', 'acceptance')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/app/api/models/app.py", line 562, in deploy
    async_run(tasks)
  File "/app/api/utils.py", line 169, in async_run
    raise error
  File "/usr/lib/python3.5/asyncio/tasks.py", line 241, in _step
    result = coro.throw(exc)
  File "/app/api/utils.py", line 182, in async_task
    yield from loop.run_in_executor(None, params)
  File "/usr/lib/python3.5/asyncio/futures.py", line 361, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.5/asyncio/tasks.py", line 296, in _wakeup
    future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 274, in result
    raise self._exception
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/app/scheduler/__init__.py", line 148, in deploy
    self._update_application_service(namespace, name, app_type, port, routable, service_annotations)  # noqa
  File "/app/scheduler/__init__.py", line 219, in _update_application_service
    self.update_service(namespace, namespace, data=old_service)
  File "/app/scheduler/__init__.py", line 1229, in update_service
    'update Service "{}" in Namespace "{}"', namespace, name
scheduler.KubeHTTPException: ('failed to update Service "acceptance" in Namespace "acceptance": 409 Conflict', 'acceptance', 'acceptance')

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

Traceback (most recent call last):
  File "/app/api/models/build.py", line 64, in create
    self.app.deploy(new_release)
  File "/app/api/models/app.py", line 566, in deploy
    raise ServiceUnavailable(err) from e
api.exceptions.ServiceUnavailable: (app::deploy): ('failed to update Service "acceptance" in Namespace "acceptance": 409 Conflict', 'acceptance', 'acceptance')

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

Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/rest_framework/views.py", line 471, in dispatch
    response = handler(request, *args, **kwargs)
  File "/app/api/views.py", line 181, in create
    return super(AppResourceViewSet, self).create(request, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/rest_framework/mixins.py", line 21, in create
    self.perform_create(serializer)
  File "/app/api/viewsets.py", line 21, in perform_create
    self.post_save(obj)
  File "/app/api/views.py", line 258, in post_save
    self.release = build.create(self.request.user)
  File "/app/api/models/build.py", line 71, in create
    raise DeisException(str(e)) from e
api.exceptions.DeisException: (app::deploy): ('failed to update Service "acceptance" in Namespace "acceptance": 409 Conflict', 'acceptance', 'acceptance')

I believe you are hitting the bug that https://github.com/deis/controller/pull/1003 solved (currently in master only, will ship with the next release)

@helgi right you were! I applied controller v2.4.2 and deploys are working without downtime. Though I'm (still) seeing pods from previous releases spun up erroneously, more info at https://github.com/deis/controller/issues/989.

thanks again!


Android code cleanup and preparation for Maven deployment

Set the package name to com.airbnb.android.react.maps instead of com.AirMaps
Adds gradle scripts for Maven deployment
Removes dependency on NDK (seems to be unnecessary)
General cleanup and organization around the android source code (formatting, project structure, etc).

Can you also update the naming in these instructions? https://github.com/lelandrichardson/react-native-maps/blob/master/docs/installation.md

cc @jrichardlai @christopherdro

usage instructions updated!

Thanks @felipecsl.
@lelandrichardson I'm not sure what are the implications of using Maven.
Should the example project be updated?
Also was not possible to use com.airbnb.android.react.maps ?

@jrichardlai the sample should probably be updated too. I see that it lives in a different root folder though. Ideally it should be under android too, so we can easily make it depend on the library.
I can definitely do that as a follow up after this PR is merged.

@jrichardlai updated to use only one .maps :)

It's unclear to me what the right example project structure is because I think needing it to run on both ios and android might change some things...

@lelandrichardson hmm that's true, i didn't realize that.
We can always use the trick project(':react-native-maps').projectDir = new File(rootProject.projectDir, ... to make it work, so I think it won't be a problem

lgtm! For my knowledge whats the advantage of using Map instead of HashMap?

@jrichardlai it is a common java idiom to use List and Map instead of ArrayList of HashMap whenever possible. That is because whether it's an ArrayList or LinkedList is an implementation deatail and you don't need to make your type so restrictive, since all you care about is that it's a List anyways. Same goes for Map, it's just more flexible this way

@jrichardlai regarding the implications of maven...
The React Native community seems to be hell-bent on using NPM for everything. When integrating RN with existing large code bases that use existing platform conventions and package managers (gradle/maven/cocoapods/etc), this can come as quite a shock and I think is quite honestly hurting RN's adoption amongst existing native developers.
For use inside of Airbnb, we are going to start using Maven and Cocoapods to depend on even 3rd party native modules that aren't publishing them themselves. We will still be publishing the source through NPM which users can install the old way if they'd like,
@felipecsl anything to add to this?

@lelandrichardson that's absolutely accurate. Just to make it 100% exact, we're been already using Maven and Cocoapods for 3rd party dependencies on Android and iOS respective for quite a while, as these are the de-facto standards for these platforms

Ah I guess you mean 3rd party react native modules specifically. So yeah, you're right!

@felipecsl Right. by "start using", i really meant "start using for react native" :)

k. Going to merge this in! Thanks, @felipecsl

Thanks for the explanation @felipecsl.
@lelandrichardson  👍

Can you clarify what changes i would need to make to use version 0.5
" Updated package to com.airbnb.android.react.maps" , is this something i would need to modify in MainActivity
Or perhaps installation will be updated.
thank you

@jeveloper the usage instructions are still being updated/fixed (see #237), but mainly you have to use MapsPackage instead of AirPackage

Thank you @felipecsl  👍
would it be better to just remove npm and install it again , not sure if there is a rnpm relink of some kind that will make all necessary changes


Add support for me

I looked at this briefly once before and it seemed like a bit of a pain because I want to be able to spin off a background thread for the webserver and still have the user have full interactive access to the r2 CLI, so r2pipe wasn't really the right tool for the job. I've definitely intended to revisit this and I will have a look again soon :)

On 14 Jun 2016, at 3:06 AM, radare<EMAIL_ADDRESS>wrote:
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Maybe I'm misunderstanding, but I thought r2pipe was just for remote-controlling a headless r2 instance. Can the user interact directly with the r2 CLI when using r2pipe?
Re: race conditions, Voltron actually does do locking where appropriate. LLDB provides an API for this which Voltron uses, GDB does not (and crashes horribly if you try to do things from a background thread). For this reason Voltron supports sync and async requests. Blocking requests are queued and then dispatched when the debugger "stops" again (ie. hits a breakpoint or steps or whatever). Non-blocking requests are dispatched immediately regardless of the debugger state. LLDB supports async, but GDB only supports sync. The built-in views support both modes, and will use async if it's available (meaning views can be updated immediately upon launch rather than waiting for the first time the debugger stops, etc).

r2pipe is the simplest way to talk with r2. And by talking i mean, being able to run a command and get the output. R2Pipe works on several channels and its implemented for many programming languages.
The channels r2pipe can talk are:

dlopen+dlsym to call r_core_cmd_str()
stdin/stdout with null terminated strings
rlang by sharing a pointer of the function
http
rap
tcp
pipes (socket files)
...

and there are probably more ways to use r2pipe that i just dont think of right now :P
you can spawn the r2 webserver in background using the =h& command. this way you can connect blessr2 or any other r2pipe-http powered interface to talk with r2 without blocking the shell.
I have an idea for fixing those race conditions in an easy way... just need to find 5m of spare time to implement and test it properly.
r2pipe api is sync for python, but there's a work-in-progress support for async using promises. async r2pipe works by queieing the pending commands.
if you look at blessr2 you'll see what im talking about :)

http://radare.org/r/blessr2.html

OK cool I'll have a look, thanks!

@radare is there a way I can get a callback each time the debugger is stepped or a breakpoint is hit etc? Voltron relies on the stop_hook mechanisms in GDB and LLDB to be informed when the debugger state has changed so it can update its displays. I looked at blessr2 and it doesn't seem to update if the debugger is stepped from within the r2 console.
If not, I might have to look at writing a C plugin for r2 rather than using r2pipe I guess?

I've got about 3/4 of a debugger adapter class for r2 going so Voltron can talk to r2 via r2pipe to get register state, read memory (tho memory read isn't working properly per the issue I opened), etc, but getting a callback to update the view state is gonna be a showstopper if it's not possible.

you can use di to know why the process is stopped. adding callbacks in a sync api is usually a bad idea because it can turn into infinite loops and such. if you step or continue, the api will hold you until its done. if you are using r2pipe use the async api for that, so you can get a “callback” when the process stops. and that will be a blocking operation while the process is running

On 15 Oct 2016, at 08:18, snare<EMAIL_ADDRESS>wrote:
@radare https://github.com/radare is there a way I can get a callback each time the debugger is stepped or a breakpoint is hit etc? Voltron relies on the stop_hook mechanisms in GDB and LLDB to be informed when the debugger state has changed so it can update its displays. I looked at blessr2 and it doesn't seem to update if the debugger is stepped from within the r2 console.
If not, I might have to look at writing a C plugin for r2 rather than using r2pipe I guess?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/snare/voltron/issues/152#issuecomment-253965895, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3-lo-dChfjrIo5fcl-gC4nPbMeo1mPks5q0HBTgaJpZM4I1KHp.

awesome! i have some spare time that i may use for r2 the next week :) will try to priorize your bug reports.
thanks

On 15 Oct 2016, at 08:20, snare<EMAIL_ADDRESS>wrote:
I've got about 3/4 of a debugger adapter class for r2 going so Voltron can talk to r2 via r2pipe to get register state, read memory (tho memory read isn't working properly per the issue I opened), etc, but getting a callback to update the view state is gonna be a showstopper if it's not possible.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/snare/voltron/issues/152#issuecomment-253965938, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3-lvzfLqv_Imf-rkN0Vhntdr9xSpYaks5q0HCegaJpZM4I1KHp.

OK thanks, I'll try the di command. Voltron doesn't really use callbacks as such - the requests on the webserver block until the stop_hook calls the Voltron server's dispatch_queue() function to dispatch any blocked requests. Sounds fairly similar to the way the r2 API works, so that should do the job. Will have a go at it tomorrow.

Does the Python r2pipe support async? [This page](https://github.com/radare/radare2/wiki/R2PipeAPI] indicates it doesn't. If I call di from the web server while the process is running, it doesn't block and I just get something like this returned immediately:
[http://localhost:9090/cmd/]> di
type=unknown
signal=SIGINT
signum=2
sigpid=15443
addr=0x0
inbp=false
pid=15443
tid=1
uid=-1
gid=-1
cmdline=/voltron/tests/inferior_linux
stopreason=12

And in the r2 console:
[0x00400667]> dc
[HTTP] <IP_ADDRESS>:50466 /cmd/di

BTW just to be clear, I mean stepping or continuing the process from the r2 CLI. Voltron does not issue the commands that do the stepping or continuation. It is designed such that it bolts onto the "side" of the debugger, rather than sits on top of it, so the user still has their normal interactions with the debugger's CLI. So a use case would be

Load binary into r2
Launch r2 web server
Launch r2->voltron proxy (this is prob gonna have to be the way it works for now until I maybe rework the Voltron client to support talking to the r2 web server directly)
User sets a breakpoint in r2 CLI
User continues process in r2 CLI
Debugger stops at breakpoint - something here has to notify Voltron that the debugger has stopped and the views need to be updated (as I said, in GDB and LLDB, the stop_hook command calls into Voltron and goes "yo debugger has stopped, dispatch any queued requests")
Voltron updates its views by requesting data from the webserver

The way that it works with GDB/LLDB is:

Voltron view makes a request to the web server, which blocks
User steps in debugger
Stop hook calls dispatch_queue which fulfils blocking requests which are then returned to the views to render the new data
View then immediately issues a new blocking request, waiting for the next debugger stop

Re
On Oct 16, 2016 4:30 AM, "snare"<EMAIL_ADDRESS>wrote:

Does the Python r2pipe support async? [This page](
https://github.com/radare/radare2/wiki/R2PipeAPI] indicates it doesn't. If
I call di from the web server while the process is running, it doesn't
block and I just get something like this returned immediately:

The async python inplementation is in a separate module, its done for py2
and py3 but it should be merge into the main python r2pipe implementation
Check the r2pipe repo for the python-async directory

[http://localhost:9090/cmd/]> di type=unknown signal=SIGINT signum=2
sigpid=15443 addr=0x0 inbp=false pid=15443 tid=1 uid=-1 gid=-1
cmdline=/voltron/tests/inferior_linux stopreason=12
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Yeah it doesnt block bwcause you arw running the webserver in a thread
On Oct 16, 2016 4:30 AM, "snare"<EMAIL_ADDRESS>wrote:

Does the Python r2pipe support async? [This page](https://github.com/
radare/radare2/wiki/R2PipeAPI] indicates it doesn't.
Reply to this email directly, view it on GitHub
https://github.com/snare/voltron/issues/152#issuecomment-254023356, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA3-ljvrI6IUV9GwTPY3SH2eq9oywD7Wks5q0YwqgaJpZM4I1KHp
.

Ah ok, I'll check the python-async implementation. Thank you.

cool! would you like to do the merge of both apis?

On 16 Oct 2016, at 11:58, snare<EMAIL_ADDRESS>wrote:
Ah ok, I'll check the python-async implementation. Thank you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/snare/voltron/issues/152#issuecomment-254037845, or mute the thread https://github.com/notifications/unsubscribe-auth/AA3-llDXXmF_XPp9wYVVk6_xhI_bx4adks5q0fVggaJpZM4I1KHp.

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "r2pipe/open_base.py", line 202, in cmd
    return self._cmd(cmd, **kwargs)
TypeError: _cmd_http() got an unexpected keyword argument 'callback'

So I gather the async API only works with the pipe method or something else?

Hi| @snare are you using Python 2 or 3?
In Python 2, currently, async is not implemented. We're working on that. I hope this feature are implemented soon

Oh my bad @radare said that earlier. I was using Python 2. I can try it with 3 for development (Voltron supports both).

I'm looking to use voltron with radare2, is this possible yet? Is there a way to help? Thanks for all your work!

Any update on this @snare, pretty please?

Hi,
Any updates on this? Are there any pending/blocking tasks ? I was so looking forward to using the Voltron plugin API instead of writing it for r2 and gdb individually

@radare / @snare can we help somehow?

Ask if u need anything from me in order to make that integration happen

On 7 Nov 2018, at 15:05, ❂<EMAIL_ADDRESS>wrote:
@radare / @snare can we help somehow?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@snare could you at least PR your changes for @radare so others can continue where you left off?


Remove test on rasterio rc and test for 0.36 instead

See https://github.com/pydata/xarray/issues/2316

The failing tests seem unrelated


Feat: multi entry

https://github.com/getAlby/nostr-wallet-connect/pull/222 should be merged first.
This PR removes the app type conditional in the go app by adding two separate entrypoints powered by build tags.
Now the wails app also sets the react app type at build time, so no env variable / .env file is needed.
COOKIE_SECRET is now only checked in the HTTP entrypoint.
The default (HTTP) mode arguments do not change because it uses a NOT WAILS (!wails) build tag.

how about we do it as in lndhub and move the main* to a cmd folder?
cmd/http.go and cmd/wails.go etc.?

how about we do it as in lndhub and move the main* to a cmd folder?
cmd/http.go and cmd/wails.go etc.?

how about we do it as in lndhub and move the main* to a cmd folder?
cmd/http.go and cmd/wails.go etc.?

I don't think we can fix this right now without a big app restructure: we need to move everything out of the main package.
Also, I could be wrong but I'm not sure the default Wails build command supports this: https://wails.io/docs/reference/cli#build - we might need to do a manual build.
It seems go build tags are more suited to this usecase (a slight variant of executing the same application).
If we decide to make this change I think it can be done in the future. The build commands will change but everything else should stay the same. Or do you see a problem here that we need to address now?


feat: support for databricks

Tell us about the problem you're trying to solve
New integration for databricks.
Describe the solution you’d like
We will use databricks-sql-connector to make the connection with databricks.
Tasks:

[ ] Add integration for databricks
[ ] add docs for new integration
[ ] Manually test for all the metrics fo data bricks, as integration test will not be available.

resolved by https://github.com/waterdipai/datachecks/pull/82


Add expands

From lanetix/odata-parser/pull/1.  Also, $search now requires double quotes around the search term, so this is (still) a breaking change, but this time it affects UI.  Hence we will need to switch UI over to using double quotes before we can merge in the OData changes.

Whoops, this isn't really ready for pushing to the public repository yet.


Lidar lite

Please use PX4 Discuss or Slack to align on pull requests if necessary. You can then open draft pull requests to get early feedback.
Describe problem solved by the proposed pull request
This PR corrects a write_reg() usage error in the LidarLite I2C driver that might be causing issues with newer hardware as reported in #12278 and this forum post (tbd).  Also, an unused _retries variable is deleted, and uniform initialization in the base class is employed.
Test data / coverage
Bench tests perform identical to master branch.  This PR:

PX4:master:

Additional context
See #12278
Thanks @dakejahl for the potential fix!

@ar1040, could you test this PR and see if it solves your issue?

Rebased on current master, squashed commits, and bench tested again. Everything looks good from a functional standpoint:

Thanks @dagar!

@mcsauder, yes my is working now, but only if I run the ll40ls start command in the Mavlink Console, otherwise it never shows in the analyze window.

Describe problem solved by the proposed pull request
This PR corrects a write_reg() usage error in the LidarLite I2C driver that might be causing issues with newer hardware as reported in #12278 and this forum post (tbd). Also, an unused _retries variable is deleted, and uniform initialization in the base class is employed.
Test data / coverage
Bench tests perform identical to master branch. This PR:

PX4:master:

Additional context
See #12278
Thanks @dakejahl for the potential fix!

This phenomenon is not right I think. I can also do this with 2019/5 Garmin lidar lite v3 product. but only in nsh. I use pixhawk and FW 1.9.2 stable. I have set SENS EN LL40LS to I2C. But the driver will never start as I boot the pixhawk. In nsh, It would also never start as  I type' ll40ls start i2c' for the first time, but just like you tested, at secont time or third, it will start.

PR's welcome! :) #12278


Error Form-Field

Hi,
There is an error when using CRUD Generator - On Post event I believe that it is trying to search for FORM-FIELD.blade.stab file whereas there is no folder "form-fields".
File does not exist at path /var/www/html/app/test/resources/crud-generator/form-fields/form-field.blade.stub
Appreciate if you can help with these.
Thanks,
Vik

Hi @vik0803 ,
I could not found any issue at all.
Did you follow the installation command?
eg. `php artisan laravel-admin:install'
Let me know if you still get stuck.

I also encountered this issue.

Sorry guys it was my fault I did not add the stuff when updated the crud-generator package.
Fixed at 0b580ad
Please let me know if you're still having any issues.


bus option color support

Adds support to edit bus option colors; the listener clients will have to be modified to support these colors as most of them are currently hard coded to green/red

@hrueger can you help implement this in the web tally viewer? In the bus_options array, there is now a color property.

Why did you comment out the previewprogram bus option?

It's been commented out since possibly 1.0. Basically decided to implement the previewprogram state in the listener client level. But I am open to re adding it.

OK. I suggest re-adding it for now so that we can have people modify the yellow color, too,

I am also giving some thought toward adding other aux busses as well and letting the user assign the incoming source type to what the TA bus is. For example, with TSL 3.1, they could say "tally1" should go to TA Preview.

Each listener client will have to be modified to support this. Right now, it is up to the listener client to evaluate whether it's in preview, program, or both, and then what to do with that info.

@hrueger if you have the skill to add a colorpicker for editing, please do. I will have to google my way through that

nevermind, you already did :) :)

In the web tally the program priority is now the default mode and can be disabled by adding ?programPriority=false to the url. I also added a paragraph to the docs.
Could someone verify that this actually works? I don't have anything right now to output some tally data and the test mode does not (yet? 😉) provide the programpreview bus.

I thought the plan was to remove the previewprogram bus as it is not really a bus but a reflection of the device being in multiple other busses.

Ah, sorry, I completely forgot about that ;-) So how exactly should we handle that in the web tally? We're using previewprogram there only to get the user's custom color from the settings.

@hrueger take a look at the python script for the blink(1) client. Basically you should check the device's states (device_states) and display the color of the one that has the highest priority number. Then I thought it would be nice to display the other states in a small table on the screen as well.
def processTallyData():
	busses = []

	for device_state in device_states:
		if len(device_state['sources']) > 0:
			bus = getBusById(device_state['busId'])
			busses.append(bus)

	priority = 0
	tallyBus = []

	for bus in busses:
		if bus['priority'] > priority:
			priority = bus['priority']
			tallyBus = bus

	#this should leave us with a tallyBus object where the highest priority bus is in this object
	evaluateMode(tallyBus)

def evaluateMode(bus):
	global deviceId
	device = getDeviceById(deviceId)
	if len(bus) > 0:
		deviceName = device['name']
		print('{} is in: {}'.format(deviceName,bus['type']))
		color = hexToRGB(bus['color'])
		doBlink(color[0], color[1], color[2])

Ah, that makes sense. Sorry that I didn't get that in the first place.
We should also modify the section in the settings where the devices are listed (to for example also show the aux outputs there).
However, with your latest commit my TA does not start anymore:
C:\Users\Hannes\Desktop\Angular\TallyArbiter\index.js:2376
        deviceStateObj.deviceId = deviceObj.id;
                                  ^

ReferenceError: deviceObj is not defined
    at initializeDeviceStates (C:\Users\Hannes\Desktop\Angular\TallyArbiter\index.js:2376:35)
    at loadConfig (C:\Users\Hannes\Desktop\Angular\TallyArbiter\index.js:2307:5)
    at startUp (C:\Users\Hannes\Desktop\Angular\TallyArbiter\index.js:816:5)
    at Object.<anonymous> (C:\Users\Hannes\Desktop\Angular\TallyArbiter\index.js:7302:1)

I’ll fix that.

The long term plan, I hope, is to let the user define as many busses in TA as they want. Then, when defining Device-to-Source Bus Mapping, they will, for example, need to say “Address 1” PGM on my ATEM is TA Bus “Aux 1”. This is a big overhaul.

Ah, I had to delete my config file and re-add the devices. We probably need some kind of migration to add the needed properties so that not everybody has to delete their config? (linkedBusses)

@hrueger can we delete this branch now?

Yes, I think so 👍


🐛 Added movie in icon list for currently playing

Category

One of: Bugfix

Overview

Movies were forgotten in the "Currently playing" list and showed a default "?" icon.

Issue Number (if applicable)

Closes #1302

Screenshot

Thanks!


Change menu order, change where button in about goes (iOS)

menu order changed
about button relabelled "More about Cogeco Peer 1"
about button goes to cogecopeer1.com

:+1:

change button from "more about cogeco peer 1" to "Visit cogecopeer1.com"


Imagine Api sometimes can't receive the message from discord websocket.

the code that reproduces this issue or a replay of the bug
const client = await new Midjourney({
ServerId: config.ServerId,
ChannelId: config.ChannelId,
SalaiToken: config.SalaiToken,
Debug: true,
Ws: true,
});
await client.init();
await client.Connect();
client.Imagine('Imagine card artwork, card illustration, the ferocious werewolf, spray effects, black and white style, yoji shinkawa style, ink render, clean details, 16k --ar 9:16');
Describe the bug
Describe the bug
In my server logs, just output the prompt log, and have nothing about ws message like "has message xxx", and i found the prompt result is display in the discord channel.
In ordinary times, the ws message can display in my server logs.
One important thing that when i restart my midjourney server, server can normal running.
I am not sure if I have made myself clear. I hope you can understand.  Thank you.
Expected behavior
Expect the ws can keep connect with discord ws
Screenshots

error log
no ws message output

I also experience this from time to time on Upscale. The image will be created but the promise doesn't resolve.

Since yesterday I've been consistently experiencing this issue, can anyone provide any suggestions to resolve it ?

How can I solve this problem that I also encounter

I also encountered this problem. Basically, after the server runs for a day, when I initiate a request to generate an image, the request task can be triggered normally in Discord, but I cannot get the callback result of the task. Has anyone solved this problem? Or found the reason for this problem?

I have the same problem. It happens sometimes randomly 🤔


Incorrect GIF format detection if extension was omitted?

Hello, I've found some GIF files were detected as non-GIF format.
Please see this screenshot:

Left: Results from FFprobe / Right: Results from MediaInfo

As you see, Detected formats are non-GIF format or missing even these files have valid GIF89a files and has GIF file signature with 89a extension (GIF89a signature).
Please see left panel on this screenshot:

Interesting part is: GIF analysis works if i add .gif extension to files.
Please see right panel of this screenshot:

You can download sample files on below links:

https://s3.amazonaws.com/test-mooyoul/public/mediainfolib-samples/hijl325b9s06xggrhsd9
https://s3.amazonaws.com/test-mooyoul/public/mediainfolib-samples/kwdu1fwympyuksxmqjic
https://s3.amazonaws.com/test-mooyoul/public/mediainfolib-samples/t3ugtcnyndfei40jn7hd
https://s3.amazonaws.com/test-mooyoul/public/mediainfolib-samples/uedhjaijuljgmug6opej

Is it intended result? what's different if filename has extension, or not?

Not intended. When the extension is .gif, the GIF parser is prioritized, and it catches the file; when no extension is provided, all parsers are tested, and here some parsers (not GIF) consider it is their formats, due to not enough precise detection.
Definitely a bug.

Ah okay, Is there any way to prioritize specific parser without modifying original filename? I've tried with mediainfo --File_FileName=some-image.gif mediainfolib-samples/hijl325b9s06xggrhsd9 but there's no luck.

Hidden option (definitely lack of doc :( )
mediainfo --File_ForceParser=GIF

woo, works like a charm. In the meantime i'll just peek given file to detect GIF signature and pass force parser option to mediainfo if given file was detected as GIF. Merci, @JeromeMartinez!


Few material-bread enhancement

I Love material-bread !
I made a few modification :

[x] Add iconComponent to drawer-item
[x]  SearchBar update with navigationIcon and closeIcon
[x] Passing theme in props in searchBar, Drawer, DrawerHeader, DrawerItem.
[x] Update DefaultTheme to exclude hard coded styles in searchBar, Drawer, DrawerHeader, DrawerItem.
[x] Drawer component drawerWidth calcul update. You can pass widthPercentage or width props.
[x] Doc update.
[x] Travis Cl build fix

@achoisy Wow this looks great! Moving appropriate styles to the theme object is very much needed.

@achoisy Nice work! Thanks!


[1.15+] timeout in a batch script instantly exits a defterm window

Oh god this is so much worse in 1.15. It doesn't timeout at all, it instantly exits!
echo foo
@rem set /p id=Enter ID:
timeout /t 10
echo bar
exit 1234

Originally posted by @zadjii-msft in https://github.com/microsoft/terminal/issues/12951#issuecomment-1338357561

~OH oh oh I bet this has to do with focus events. That's my guess - timeout will bail on input. Like, any input? That I'm not sure about. But I bet the regression between 1.12 when this was filed, and now (1.15/16/17) is the focus event stuff, and I bet eveything is immediately getting a focus event in the input queue right off the bat.~
I'll need to go inspect timeout's source to confirm. That's my hypothesis.
Notably, this doesn't repro the same if you actually "restart" the batch script, until you press a key:

I noticed this when I restored the Terminal from being quit, and this defterm window came back ~(presumably, without the focus event)~. This might be related to #13514
Okay, my hypothesis was wrong. Looks like timeout does filter FOCUS events out... even if it does have some other horrifying code in it.

Uh, this looks fixed. At least in 1.19.whatever.this.selfhost.build.is


Use isAbstractClassCast in DataCollectionEloquentCast for easy override

I'm using abstract data classes in a way that's different to the eloquent-cast functionality of laravel-data (related to the problem I described in my old example PR https://github.com/spatie/laravel-data/pull/304).
The approach I have now is different / cleaner as I move from V2 to V3, but I need to be able to disable the abstract class functionality in DataCollectionEloquentCast and I'd prefer not to duplicate the code in the casts if possible!

If you're curious, what I'm doing is using properties inside the DTO to describe which concrete class / variant of the abstract class to use (as per https://github.com/spatie/laravel-data/pull/304). I've got support for creation from request payloads (with validation), singular data classes, data collections and nesting.
An example use case is having Vehicle as an abstract data class with type (to determine which concrete to use) and a common passengers property. Each concrete can then add additional properties e.g.:
"vehicles": [
    { "type": "horse", "max_passengers": 1, "name": "Bill" },
    { "type": "car", "max_passengers": 5, "transmission": "manual" },
]

It's something that's been super useful for us and a feature I think would be really great to have built-in. If you're curious about how I'm solving that problem I'm happy to share what I've got (outside this PR of course) 😄


Incorrect SKCodecOrigin from dng files

APC_0316.zip
APC_0193.zip
Sample images attached. The following sample code results in SKCodecOrigin.TopLeft, which is incorrect.
    private static SKBitmap Decode(string path, out SKCodecOrigin origin)
    {
        using (var stream = new SKFileStream(path))
        {
            using (var codec = SKCodec.Create(stream))
            {
                // create the bitmap
                var bitmap = new SKBitmap(codec.Info.Width, codec.Info.Height);

                origin = codec.Origin;

                return bitmap;
            }
        }
    }

Is this supported for dng files? The chrome browser is able to auto-orient them as expected.

I can confirm this is happening... not sure why - maybe skia doesn't respect that property. I will have to investigate further.


Revert "Drop crypto app reliance"

Reverts rebar/rebar#637

Revert, since Travis still can fail (https://travis-ci.org/rebar/rebar/jobs/266578654 in https://travis-ci.org/rebar/rebar/builds/266578650).

rand module since OTP 20 depends on the crypto module, so I think rebar.app should include crypto.

So the dynamic compat module is fine, but we should retain the crypto:start() call. Or does rand start crypto on demand?

I might be wrong. It's vice versa: crypto now depends on rand. Check the manual here
http://erlang.org/doc/man/crypto.html#rand_seed-0
(I'm not really familiar with the dependency between crypto and rand since OTP 20 yet)
rand does not start crypto at all. See
https://github.com/erlang/otp/blob/master/lib/stdlib/src/rand.erl

I missed the deprecation change in 20.0 and must say it's interesting that crypto is needed for rand:uniform but crypto:rand_uniform will be removed in the future.

I see, so while rand:uniform does not call into crypto, we are expected to use the seeder from crypto. But then I'm confused why we have rand:seed. I mean, when I use random:uniform or rand:uniform, the docs don't indicate that I should not use rand:seed/random:seed. Also, the docs for crypto:rand_seed mention it being for rand:uniform use.

rand:seed is implicitly executed at the first invocation of rand:uniform. rand:seed's result will not be fixed at all (depending on all the timers and process ids are other variable factors in the BEAM) so this will be ok.
OTOH random:uniform without rand:seed results in a fixed result of seeding (by the implicit execution), so random:uniform must be explicitly seeded with a variable factor to obtain different results.
I believe some people developing crypto module thought the current plugin interface of rand module was suitable to encapsulate cryptographically-strong random number generation functions for OTP 20. I haven't really checked out the crypto module yet, but I guess some functions in crypto module are actually forming plugins of rand module.

@lrascao, let's merge this revert and re-introduce the 20.0.2 warnings. We can try to fix this again, probably differently, and a warning is better than spurious Travis-CI errors in the ct_run test suite.

On 8/21/17, Kenji Rikitake<EMAIL_ADDRESS>wrote:

@tuncer: did you get the deprecation warning for crypto:rand_uniform/2? I
guess this code in otp_internal.erl generates it:
https://github.com/erlang/otp/blob/OTP-20.0.2/lib/stdlib/src/otp_internal.erl#L107L111

Yes. I'll come up with a new patch to approach this differently in an
hour or so, and we can continue the discussion there.

@jj1bdx, yes that's the warning.

tl;dr: I don't know how to fix the warning, especially in a backwards compatible (OTP version and rebar features) way.
Long story: I was thinking we could seed in rebar:main and call rebar_rnd:uniform in rebar_ct and rebar_eunit, but it's a more complicated. The EUnit tests randomization/?shuffling? feature looks for input from the PRNG seed on the command line. I don't know how we would keep that and centralize PRNG initialization.

tl;dr: I don't know how to fix the warning, especially in a backwards compatible (OTP version and rebar features) way.
Long story: I was thinking we could seed in rebar:main and call rebar_rnd:uniform in rebar_ct and rebar_eunit, but it's more complicated. The EUnit tests randomization/?shuffling? feature looks for the PRNG seed on the command line. I don't know how we would keep that and centralize PRNG initialization.
Here's what I think the PRGN use was intended to achieve:

rebar_ct: create a unique nodename for use as the node when spawning ct_run
Like I said before, a PRNG isn't really the right solution here anyway.
rebar_eunit: shuffle tests, but I could be wrong.
A shuffling algo like Fisher-Yates appears more application here.

Both PRGN uses seem to not require PRNG (and crypto) at all, if solved in a fundamentally different and arguably more appropriate fashion.

tl;dr: I don't know how to fix the warning, especially in a backwards compatible (OTP version and rebar features) way.
Long story: I was thinking we could seed in rebar:main and call rebar_rnd:uniform in rebar_ct and rebar_eunit, but it's more complicated. The EUnit tests randomization/?shuffling? feature looks for the PRNG seed on the command line. I don't know how we would keep that and centralize PRNG initialization.
Here's what I think the PRNG use was intended to achieve:

rebar_ct: create a unique nodename for use as the node when spawning ct_run

Like I said before, a PRNG isn't really the right solution here anyway.

rebar_eunit: shuffle tests, but I could be wrong.

A shuffling algo like Fisher-Yates appears more applicable here.

Both PRGN uses seem to not require PRNG (and crypto) at all, if solved in a fundamentally different and arguably more appropriate fashion.

@tuncer pulled me in here, so I am not sure I have caught up with everything..., but I will try to throw some random hints at this.
@jj1bdx  is right as far as I can see.  The rand module does not depend on crypto, but the crypto application calls the randmodule fromcrypto:rand_seed/0andcrypto:rand_seed_s/0.  I guess you are not interested in cryptographically strong numbers here, so the crypto` application should not be needed.
You can suppress warnings, for example by creating a wrapper module that calls all functions you do not want deprecation warnings about.  Then you turn off all deprecation warnings in that wrapper module.  Your wrapper module can use try - catch to find a useful implementation.
If seeding is a problem you can re-implement a seed function yourself for example by mimicking the code in the last clause of OTP-20.0 rand:seed_s/1.  You only need to produce a 3-tuple of non-negative integers with a quality of your own choice to seed rand:seed/2, rand:seed_s/2 or random:seed/1.


Add gfx1150 platform

add gfx1150 configurations
add navi3.5 yamls from navi32

If your commit involves changes to a YAML file, please take note.
Due to PR-1117 (https://github.com/ROCm/hipBLASLt/pull/1117) adding ActivationType: hipblaslt_all, all YAML files now need to include the ActivationType field if Activation: true (for hipblaslt logic YAML, use ActivationType: hipblaslt_all (not all); for tensile test YAML, you can use either all or hipblaslt_all).
Correspondingly, in the Logic YAML filename, the _A that originally represented ActivationType: all should also be changed to _HA. These changes have been implemented in PR-1117.


Fixed Global/Sub Twitch Emotes

This simply updates where the mod gets the emote information from twitchemotes.com and rather fixes the link to reflect the change in the twitchemotes.com v3 API docs as stuff.

Is this tested with a clean cache? It shouldn't be working just by changing the URL as the actual format of the API response has changed too, e.g.
{
	"VaultBoy": {
		"id": 206490,
		"code": "VaultBoy",
		"emoticon_set": 0,
		"description": null
	},
	"QuadDamage": {
		"id": 206494,
		"code": "QuadDamage",
		"emoticon_set": 0,
		"description": null
	}
}

while the code is still looking for a template string and emotes object, image_id instead of id, etc.

Ok. Fixed the sub emote registration system when it comes to getting stuff from the API, same with global Twitch emotes as well. The Twitch Turbo Emote Pack won't be created when enabled now because of the fact that Twitch doesn't just have the emotes for Turbo laying around anymore. They are now a client side thing in the web browser by the looks of it.

twitchemotes.com doesn't have Turbo emotes anywhere, but they are accessible via Twitch's own API under emoteset 19194
https://api.twitch.tv/kraken/chat/emoticon_images?client_id=gdhi94otnk7c7746syjv7gkr6bizq4w&emotesets=19194
However, that's probably out of scope for this PR.

The recent commit fixes up the Twitch Turbo functionality (renamed everywhere to Twitch Prime) along with the changes you requested that I fix.

Also, this is starting to surprise me on how little issues I have been having with making these changes. I code projects in Javascript... This is the first time I have done anything with a minecraft mod in Java. I think I did pretty good for my first time.

Thanks, will release later

No problem! Thank you as well for approving it!


Add instructions to readme for install via brew

I created a cask for tev https://github.com/Homebrew/homebrew-cask/pull/113398 updated readme to include homebrew installations

That's amazing, thank you! I moved the description from "building" to "obtaining" before merging. Thanks again!


Support list_with_offset for Azure using continuation token

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Azure object store implementation uses default list_with_offset implementation. It lists everything and does the filtering client side.
This is problematic for Delta Lake with large directories where we only really care about listing the latest files from a certain path.
Describe the solution you'd like
Microsoft pointed me to the Hadoop Azure filesystem listStatus API where startFrom is supported.
Basically the starting path is embedded in the opaque continuation token provided when the list API needs to page results. On the initial request this token is created and provided to the list API to start from the path.
The downside is that this is not documented. Perhaps this could be an opt-in option if there is hesitation using an undocumented format for the token that could break.

I think I would prefer to not implement undocumented shenanigans, that I presume would be hard to test 😅

👍 we tried to implement this and what they suggested to us is not working anyway, so we're going to pursue other options.


Write mssql dialect

Write mssql dialect and place it in the drivers.

I'd like to take a crack at this.


feat: Center loading vertically using infinite-scroll

Type: feat
Platform: mobile webview
I'd like to center the loading-spinning in the center of screen horizontally and vertically using infinite-scroll.
Like in this example, http://codepen.io/felquis/pen/pCHim seems like there's no easy way to center the spinning vertically, since infinite-scroll reside inside .scroll that doesn't fit 100% of the height of the viewport like ion-pane does.
Would be nice to have a center-vertically="true" (or something like this) option in the infinite-scroll API session here http://ionicframework.com/docs/api/directive/ionInfiniteScroll/
Thanks.

Moving this to our trello board as it is a feature request.
https://trello.com/c/lrqhyeT4/84-center-infinite-loading-icon-on-initial-load


Tag build failure 2024.2.6

Overview
What do you think happened, if anything?
Looks like we had some issue setting the user project when accessing GCS - the reported status of all the stages was:
Stage status (0 means success):
ETL_SUCCESS: 0
SAVE_OUTPUTS_SUCCESS: 0
UPDATE_NIGHTLY_SUCCESS: 0
UPDATE_STABLE_SUCCESS: 0
DATASETTE_SUCCESS: 0
CLEAN_UP_OUTPUTS_SUCCESS: 0
DISTRIBUTION_BUCKET_SUCCESS: 0
GCLOUD_TEMPORARY_HOLD_SUCCESS: 1
ZENODO_SUCCESS: 0

Next steps
What next steps do we need to do to understand or remediate the issue?
- [ ] investigate what sets this GCLOUD_TEMPORARY_HOLD_SUCCESS value and what might have changed since yesterday's build which succeeded.

Verify that everything is fixed!
Once you've applied any necessary fixes, make sure that the nightly build outputs are all in their right places.
- [ ] [S3 distribution bucket](https://s3.console.aws.amazon.com/s3/buckets/pudl.catalyst.coop?region=us-west-2&bucketType=general&prefix=nightly/&showversions=false) was updated at the expected time
- [ ] [GCP distribution bucket](https://console.cloud.google.com/storage/browser/pudl.catalyst.coop/nightly;tab=objects?project=catalyst-cooperative-pudl) was updated at the expected time
- [ ] [GCP internal bucket](https://console.cloud.google.com/storage/browser/builds.catalyst.coop) was updated at the expected time
- [ ] [Datasette PUDL version](https://data.catalyst.coop/pudl/core_pudl__codes_datasources) points at the same hash as [nightly](https://github.com/catalyst-cooperative/pudl/tree/nightly)
- [ ] [Zenodo sandbox record](https://sandbox.zenodo.org/doi/10.5072/zenodo.5563) was updated to the record number in the logs (search for `zenodo_data_release.py` and `Draft` in the logs, to see what the new record number should be!)

Relevant logs
link to build logs from internal distribution bucket
ERROR: (gcloud.storage.objects.update) HTTPError 400: Bucket is a requester pays bucket but no user project provided.

cc @zaneselvans in case you have any specific insight!

I think I just forgot to explicitly set the billing project for the object hold command.


Add ltex quarto support

Add support for ltexls.
This is a draft which might be helfpul to you.
https://github.com/jmbuhr/quarto-nvim-kickstarter/issues/14#issue-1638376008

Thanks for the PR! Though it is even simpler than that. I added it now as an optional, commented out part here: https://github.com/jmbuhr/quarto-nvim-kickstarter/commit/e17573dfbc708918442b9b7b2015d501cff72029
I found it a bit too intrusive to enabled by default, but it certainly has value.


Adapt cleaning interval depending on remaining diskspace

If the disk space gets low, the cleaner should remove unneeded files more frequently (currently, only done during the off-peak time and only after the retention period has passed). If space is low, images should be deleted even if the retention period has not passed to ensure that the server remains responsive.

Addressed with commit f57921935348f3427f9f222bf2f20cff478ebf58


Implement Terraform Workspace deletion.

Hello there 👋 Thanks for this awesoe tool.
This PR fixes #583 : it implements 2 methods to handle Terraform Workspace's deletion.
Please note that deleting the workspace default is not supported as it triggers edgy use cases.

Hello @brikis98 , thanks a lot for the review.
I've updated the PR with a bunch of your feedbacks, but I need inputs on some.
Please note that I haven't squashed the commits yet, in order to allow further update or rollback as necessary.

Ok, I've checked all your feedbacks, it should be ok (also rebased from upstream). Let me know if I missed something else.
Thanks for all the feedbacks and the review!

Tests passed! Merging now.

https://github.com/gruntwork-io/terratest/releases/tag/v0.32.17


Add try; except to cells that fail and print out the error message so…

… that the notebook can execute end-to-end

Great idea!


Guidance on upstream settings for an azure containerized function

Due to operational constraints, we need to run the upstream function inside a container on AKS.
Environment

Net 6
Isolated
Signalr Serverless mode
Upstream
Azure Containerized function
AKS with workflow identity,
Container has its own service principle.

The only thing i am unsure about is the upstream URL and its code
<host>/runtime/webhooks/signalr?code=<API_KEY>
The host is fine.
I can access that route from postman  /runtime/webhooks/signalr though unauthorized, which is a good start.
I am wondering if its possible to hook up the api-key ?
Are containerized upstream functions supported? or is there a work around?

Are you using Azure Functions on Kubernetes with KEDA?

@Y-Sindo Yeah the upstream singalr azure function is running in a container on AKS. the problem i am having in particular is the secret used in the upstream setting in the azure signalr service
http://host/runtime/webhooks/signalr?code=
I have progressed a little and figured that secret for  signalr is actually a system key which is found and backed by the AzureWebJobsStorage connectionstring in the azure function environment variables.
Now i am just on a learning curve, of how to create and or allow the containerized function to use similar storage, to obtain a the system key, so the upstream setting of the azure signalr service can authenticate with that particular function system key.
I.e i assume if i get this right, i should be able to call http://host/runtime/webhooks/signalr?code= from postman, and have it not return 401 or 500.
Anyway, that is my working hypothesis for now, which makes this likely not a azure signalr serverless question. and more a azure containerized function on AKS question :/
However any help would be appreciated

If you confirm that you're using KEDA, then SignalR trigger is not supported according to Supported triggers in KEDA.
Implementing an HTTP trigger to handle SignalR requests might be a workaround, as the SignalR trigger is an HTTP trigger actually. You can refer to serverless protocol for more details. But there is another concern that HTTP trigger seems to need more effort to auto-scale according to the doc

@Y-Sindo thanks for your help, yeah, i think i am pushing this too far up hill, for little benefit


Preserve message ordering

Awesome tool that you've developed! I've been looking a long time for a good gRPC documentation generator and sabledocs is by far the best I've seen.
One comment is that it may be better to see the messages in the documentation in the same order as they are in the .proto file.
Currently, they seem to be ordered alphabetically and I'm curious what is the rationale behind this choice.
https://github.com/markvincze/sabledocs/blob/2421ae8926322ca911600dfe4f0d81963b7ae300/src/sabledocs/proto_descriptor_parser.py#L182

Hi @fclad,
Thank for submitting the issue, I'm glad you like the library!
The rationale was just to have a deterministic ordering, so that if we have a lot of types, then make it easy to find a specific type in the list by eye.
And this seemed to be the approach used by other documentation generators out there, for example methods in a C# class:

Or interfaces in a Java package:

But I understand that sometimes it would be useful to preserve the ordering which was in the original proto files, as it can be more logical than the alphabetical.
One thing I don't know is whether protoc preserves the original order, when it creates the binary descriptor, and especially what it does if there were multiple proto files specified in the input.
I'll check if that works correctly, and add a parameter to the toml config with which this can be controlled, so you can choose between alphabetical ordering, or preserving the original order.


dependency is missing in the Godeps file.

dependency is missing in the Godeps file.
github.com/gogo/protobuf
github.com/dgryski/go-bitstream

They're present in the Godeps file.


Use of deprecated template + all DITA to MarkDown output files have "html" extension.

Using DITA OT 2.2.2 to produce MarkDown from DITA, there seems to be a warning in the console:

[xslt] file:/D:/projects/eXml/samples/dita/flowers/topics/care.dita:15:33: [DOTX066W][WARN]: Template "getString" is deprecated. Remove references to this template from your custom XSLT or plug-ins.

furthermore the output files seem to have the "html" extension.

The former issues has been fixed in 76dd0b676328652646a26b4814c341e36cf3b3c3


dart2js: runtimeType.toString() is wrong when using minify

This issue was originally filed by<EMAIL_ADDRESS>
Dart classes have a 'runtimeType' property
DivElement foo = new DivElement();
print(foo.runtimeType); // prints 'DivElement'
However, with the minify flag on, you get the minified class name returned
// --minify TRUE
print(foo.runtimeType); // prints 'cB' for example

This is not just a minification issue. All classes have different JavaScript names, and the JavaScript name is strongly related (1-1) to the runtimeType name. We would have to substantially change the type representation to fix this. I'm not saying we should not fix this, just that it has a nontrivial implementation cost.
We could store the full name against the minified name. This would increase the size of minifed programs by about 5%. Many of our customers do not believe this cost is justified and would need a way to make it opt-in.
A consequence of the 1-1 correspondence is that even unminified programs can print the 'wrong' name.
The following program prints:
Thing
Thing0

-------- 9217.dart --------
import '9217a.dart' as a;
import '9217b.dart' as b;

main() {
  print(new a.Thing().runtimeType);
  print(new b.Thing().runtimeType);
}
-------- 9217a.dart --------
class Thing {}
-------- 9217b.dart --------
class Thing {}

I have same error with JSON Object. On Android, it is _InternalLinkedHashMap<String, dynamic>, on Web it's _JsonMap. But on release is mininy:ds. don't use dynamic.runtimeType, replace with object is Map<String,dynamic> instead

Found this to be a problem manifesting when building a Flutter project for release, if built for debug, the names where correct. example:
...
await ApiGuardSystemsService().getAssets(
...
  ).then((rawAssets) async {

    print("rawAssets.runTimeType = ${rawAssets.runtimeType.toString()}");

    if(rawAssets.runtimeType == List<dynamic>) {
      await globals.mOfficeDatabase.transaction(() async {
        for (var rawAsset in rawAssets) {
          print("inserting rawAsset");
...
    print("getAssets done !");
   });

Here I get the following print results in console:
Debug build:
rawAssets.runTimeType = List<dynamic>
inserting rawAsset
getAssets done !

In release build:
rawAssets.runTimeType = minified:H<dynamic>
getAssets done !

You see, my expected type check didn't checkout because the expected runtimeType is different in release vs debug...
Will file an issue for this in Flutter/dart...
Thanx for mentioned this here!

@RoarGronmo Don't compare types like this. Use is checks instead. <dynamic>[].runtimeType is not guaranteed to be exactly List<dynamic>, it can be _SomeImplementationOfList<dynamic>.
Object.runtimeType exists primarily for debugging purposes (e.g. to print it), any sort of code that dispatches on it should be avoided.

Well...
My undestanding of dynamic is beginning to be loose...

When it says it is just dynamic at first..

I feel I have a "right to know" that type of the dynamic actually is.


Plesse allow setting the seeding port

Some VPNs like for example PIA only give you one port, so it would be nice if I could set that port as the seeding port in the Android app, I was not able to find a setting for it.

Thanks for this suggestion, will consider adding it when we integrate
libtorrent 2.0 (soon)
https://x.com/gubatron https://twitter.com/gubatron
On Sat, Nov 23, 2024 at 12:27 AM Max Staff @.***> wrote:

Some VPNs like for example PIA only give you one port, so it would be nice
if I could set that port as the seeding port in the Android app, I was not
able to find a setting for it.
—
Reply to this email directly, view it on GitHub
https://github.com/frostwire/frostwire/issues/1022, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABIBCPNNGELJ6UDKZTGBVD2CAU6VAVCNFSM6AAAAABSKZGSRCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY4DKNJVG4ZTSNQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>