Optimize provisioned throughput with ReplaceThroughputAsync performance

Hello, recently we've been dealing with some research regarding the  rate-limit throughput , where we came to know If you provision 400 RU/s and issue a query that costs 40 RUs, you will be able to issue 10 such queries per second. Any request beyond that will get rate-limited and you should retry the request., we also came to know that the SDK v3 could handle the RequestRateTooLarge (http code 429) automatically but we would like to go a little deeper and some performance optimization around it:

How the SDK would manage the RequestRateTooLarge scenario, does it have a built-in retry policy? In our Azure Portal Cosmos Metrics, we saw some some Http 429 happened there, but not sure if that's already been handled by the SDK or not.
How would we change the retry-policy in configuration?
We noticed there is something related to ReplaceThroughputAsync() in SDK, our thought is if we perform a different throughput dynamically, depending on the data size/volume we received every time (e.g, if our data size is 1,000 we change the throughput to 1,000 RU/s, if our data size if 5,000, we change the throughput to 5,000 RU/s),

Would the replace throughput affect immediately?
Any performance would be impacted within this update?
If multiply functions are trying to change the container throughput in different size at same time, would there be any conflict happening there?

//*********************************
// Change performance (reserved throughput) of CosmosContainer
//    Let's change the performance of the container to 500 RU/s
 //*********************************
 await simpleContainer.ReplaceThroughputAsync(500);

Thank you very much for your help!

How the SDK would manage the RequestRateTooLarge scenario, does it have a built-in retry policy?
Yes SDK retry policy is derived from CosmosClientOptions.MaxRetryAttemptsOnRateLimitedRequests and CosmosClientOptions.MaxRetryWaitTimeOnRateLimitedRequests.

On RequestRateLarge service also responds with a retry-after and client honors retry-after with the above client configuration.

How would we change the retry-policy in configuration?
Application can tune number of retries and duration through above CosmosClientOptions.
Also application can turn-off SDK retry by setting them to '0' and handle retries in the application.

We noticed there is something related to ReplaceThroughputAsync() in SDK, our thought is if we ...

Would the replace throughput affect immediately?
Once the call completes then its immediate.

Any performance would be impacted within this update?
Regular scale-up might mostly not have any impact. Scale-down will have impact as expected.

If multiply functions are trying to change the container throughput in different size at same time, would there be any conflict happening there?
If the idea is to handle it part of the application then it might be a local decision. Instead I would suggest to do this outside application based on monitoring counters (might be little delayed but its global view instead of instance view).

I don't have any example or experience using it but there is Azure Monitor.
Another alternative is to add Azure App insights or a custom monitor that records the RU's of every request. You can use the handler pipeline to add a logger.

@j82w , thank you for sharing your thoughts! Instead of just monitoring from Azure Monitor or App insight, we're thinking if there is anyway that can increase the throughput at run-time to improve the performance. In our case, we have no idea when our data request might need a large throughput to avoid less Http 429 response (e.g, we may have only 1,000 items came at 8:00 - 8:14 am but could receive around 500,000 items at 8:15 am, so when we handle the event at 8:15 dealing with 500,000 items, we may need to increase the throughput to avoid less rate-limited response and to make sure that all of our request should be able to complete process within the built-in retry logic ),
actually the default retry policy is something we don't know the exact logic and concerned that, after certain times of retry (let's say 3 times), if we're not increasing our throughput, among the 500,000, would it be possible that only 50,000 items are processed but rest of the 495,000 will be returned as exception? Or will them be added into the process queue and cosmos will execute later on? How would we ensure that all of our items would be processed with a smaller throughput in this case?
One thing that I've noticed is the "ThrottlingHandler example", where we seem to be able to customize the default retry behavior when Http 429 response received, would it be a good idea to implement some kind of logic that in the retry, like increasing the throughput based on retry count?

Closing due to inactivity.


Mobile menu is missing

In mobile, menu is not shown. I would expect to have top header as menu. That will be nice.

A simple fix is to comment out...
*@media (max-width: 480px) {   #taglist {     display: none;   }
... at the bottom of webkid.css. That stops the menu from hiding.

I'm closing this issue because of f7fba6409c84c12d255107070e5ac7afbc8b8392.
Feel free to open a pull-request if you come up with a generic solution.
Thank you!


Add LazyWorkerInterface

This is a new WorkerInterface class that will be used in the internal PR, see comments to understand what it does.

@npaun @AdityaAtulTewari @harrishancock ping


chore(travis-CI): add node v8 to CI and remove v4

Summary
Add node v8 to CI and remove v4
Description

Add of node v8 to CI and remove v4 in orders-update

Part of this issue

Codecov Report

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

@@          Coverage Diff          @@
##           master    #17   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines         102    102
=====================================
  Hits          102    102

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 674cfa5...1d2c598. Read the comment docs.


Is it possible to dynamically register modules?

tried to dynamically register modules for different pages, and got this error:
"Can't add module after vuexStore() has been called"
is this achievable somehow? register all modules for all pages doesn't seem to be ideal.
thanks

:thinking: interesting... there's no good reason why it shouldn't be possible.  Except that it hasn't been done.

Thanks for the PR. I'll publish to npm when I'm back at a computer.

Published as vuex-typex v3.1.5


Create wrapper for recipe api [3076] (Assignee:antong12)

By Mathias Lykke Pedersen (mat0pad -<EMAIL_ADDRESS>on 2017-02-10 16:39:13.653
Create a wrapper for interacting with spoonacular. Use http-async android (github clone/fork)

Migrated from https://hub.jazz.net/ccm41/resource/itemName/com.ibm.team.workitem.WorkItem/3076


⚠ Samsung has degraded performance

In f13b610, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2052 ms

Resolved: Samsung performance has improved in caf1e03.


4.5.0->6.0.0 migration issue (befuddling compilation error)

I'm upgrading from 4.5.0 to 6.0.0 and have one last compilation error that's stumping me. My code was inspired from a combination of Moya docs and the Eidolon source from a year or so ago. Any help is most appreciated - I'm having a rough time since the error message is quite opaque to me (it sounds like a contradiction). It should be pretty familiar to how Eidolon's API was structured a while back, though it seems to have had a lot of new abstraction added since then.
Here's where compilation fails:
static func DefaultProvider() -> ReactiveManabiAPIProvider<ManabiAPI> {
        return ReactiveManabiAPIProvider(endpointClosure: endpointsClosure,
            requestClosure: endpointResolver(),
            stubClosure: StubBehaviour,
            plugins: APIProvider.plugins)
    }

error: cannot convert value of type '(ManabiAPI) -> Endpoint<ManabiAPI>' to expected argument type '_ -> Endpoint<_>'
        return ReactiveManabiAPIProvider(endpointClosure: endpointsClosure,
                                                          ^~~~~~~~~~~~~~~~

And here are the relevant bits referenced above:
enum ManabiAPI {
[...]
}

extension ManabiAPI : TargetType {
    var baseURL: NSURL { return NSURL(string: "[...]")! }
    var path: String {
    [...]
    }
    var parameters: [String: AnyObject]? {
    [...]
    }
    var method: ReactiveMoya.Method {
    [...]
    }
    [...]
}

public class ReactiveManabiAPIProvider<Target where Target: TargetType> : ReactiveCocoaMoyaProvider<Target> {
    var appController: AppController
    var requestErrors: RACSubject

    override init(endpointClosure: MoyaProvider<Target>.EndpointClosure = MoyaProvider.DefaultEndpointMapping,
        requestClosure: MoyaProvider<Target>.RequestClosure = MoyaProvider.DefaultRequestMapping,
        stubClosure: MoyaProvider<Target>.StubClosure = MoyaProvider.NeverStub,
        manager: Manager = Alamofire.Manager.sharedInstance,
        plugins: [PluginType] = [], stubScheduler: DateSchedulerType? = nil) {
            let appDelegate = (UIApplication.sharedApplication().delegate as! AppDelegate)
            appController = appDelegate.appController!

            requestErrors = RACSubject()

            super.init(endpointClosure: endpointClosure, requestClosure: requestClosure, stubClosure: stubClosure, manager: manager, plugins: plugins)
    }
[...]
}

Please let me know if it'd be helpful to see anything else. Thanks!

I've posted the question on StackOverflow since it's not particularly Moya-specific: http://stackoverflow.com/questions/34707426/what-does-this-swift-type-error-mean-it-reads-like-whats-expected-is-already-t

Yikes! I'll take a closer look later, but when I encountered problems upgrading eidolon to Moya 6, most problems were solved by being more explicit about closure parameter/return types. You can check out our existing inplementation, too.

I'm having the same problem. I thought it was a derived data issue or something like that but nothing I could do was working. When I removed my plugins it would compile but none of the autocomplete was working and it was seeming to happen with other pods to. It was driving me a little crazy glad I'm not the only one.

Just realized I didn't post the actual implementation of endpointsClosure, at the top of this:
struct APIProvider {
    static var username: String? = nil
    static var password: String? = nil

    static var endpointsClosure = { (target: ManabiAPI) -> Endpoint<ManabiAPI> in
        var base64Login: NSString?

        if let username = username {
            if let password = password {
                let login = NSString(format: "%@:%@", username, password)
                let loginData: NSData = login.dataUsingEncoding(NSUTF8StringEncoding)!
                base64Login = loginData.base64EncodedStringWithOptions([])
            }
        }

        let parameterEncoding: ReactiveMoya.ParameterEncoding = target.method == .GET ? .URL : .JSON

        let endpoint: Endpoint<ManabiAPI> = Endpoint<ManabiAPI>(
            URL: url(target),
            sampleResponseClosure: {.NetworkResponse(200, target.sampleData)},
            method: target.method,
            parameters: target.parameters,
            parameterEncoding: parameterEncoding)

        if let base64Login = base64Login {
            let headerFields = ["Authorization": "Basic \(base64Login)"]
            return endpoint.endpointByAddingHTTPHeaderFields(headerFields)
        } else {
            return endpoint
        }
    }

    static func StubBehaviour(_: ManabiAPI) -> ReactiveMoya.StubBehavior {
        return .Never
    }

    static func DefaultProvider() -> ReactiveManabiAPIProvider<ManabiAPI> {
        return ReactiveManabiAPIProvider(endpointClosure: endpointsClosure,
            requestClosure: endpointResolver(),
            stubClosure: StubBehaviour,
            plugins: APIProvider.plugins)
    }

    private struct SharedProvider {
        static var instance = APIProvider.DefaultProvider()
    }

    static var sharedProvider: ReactiveManabiAPIProvider<ManabiAPI> {
        get {
            return SharedProvider.instance
        }

        set (newSharedProvider) {
            SharedProvider.instance = newSharedProvider
        }
    }
}

Update for me. I was also getting a casting to objc bridge error on my plugins array. Which is odd because I wasn't doing any objc.
let plugins = [somePlugin]

Now works as
let plugins:[PluginType] = [somePlugin]

Not sure if this is a related issue but was a similar obscure result.

Thanks @gregpardo that may help. But I've disabled plugins in an attempt to narrow down this issue. Glad you found your fix.

 I don't know if this is related to what you ran into, but at least your problem led me to it.

Ah, sounds like trouble :) Is this issue good to be closed?

It may be more of a swift 2 lint/compile error than anything else. Just seems like sometimes the errors are really unrelated to what is actually going on.

Yep, all resolved now... Sorry for the noise, thanks.

Hey, don't worry about it! Issues are the perfect spot for questions like this. I guarantee other Swift developers are getting similar errors, and if we debug problems like this in the open, then they won't have to fix it by themselves next time :wink:

I'd just like to note for posterity that if anyone lands here I had the exact same issue and the fix was being more explicit about the types.
I had something like
static var sharedProvider = ...

That then returned my provider.
I fixed the issue by switching to
static var sharedProvider: MoyaProvider<EtherAPI> = ...

Seems like a very similar issue. The swift compiler sometimes needs to be explicit but does not properly hint on where the problem is. I'm going to keep this in mind for this and other projects.


Add nightly feature

Currently downsample_rs cannot be built with stable compiler, because nightly_simd is enabled by default for argminmax.
I've added nightly feature (which is enabled by default) which activates nightly_simd, so this crate can be compiled with stable with default-features=false
(yes, I really need that :) )

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Doesn't work for packages that are not on Hackage?

I don't know how is cabal-db working, but as far as I can see it's not working for packages that are not on Hackage.
I have a library and executable that I develop using sandbox so every dependency is in the sandbox or in system-level dirs. Is there a way to make cabal-db working in this case? Would it be too hard to add this feature?

:+1: Would be really useful to have, was just about to ask the same question.

A nice middle ground would be to accept a .cabal file instead of a package name, and just add that to the db, then query on the (extracted) package name.
That wouldn't help for the situation where you have multiple packages that are locally-hosted, but it would allow you to run cabal-db queries against a package that you have not yet released (or one that you just added dependencies to, and want to see a dependency graph for, because it just stopped building... ;)

Another vote for supported dependency graphing for local packages. I'm trying to make sense of the dependencies of an internal package at work that will never end up on Hackage.

And for anyone else ending up here, Stack has a stack dot command that supports local packages and pruning: https://docs.haskellstack.org/en/stable/dependency_visualization/.

It's very unlikely i'll update cabal-db now, and I'll just probably try to merge whatever is missing into stack itself if I get to it.


Could we provide a more flexible get<> and at<> API?

What is the issue you have?

(I didn't see a "feature request" category when opening a new issue thus I post this ticket as a "bug report")
I'm wondering could we provides a more flexible get<> (get with key) or at<> (at with type parameter) API like:
template <typename ValueType>
ValueType get(const key_type &key) {
   return this->operator[](key).get<ValueType>();
}

template <typename ValueType>
ValueType at(const key_type &key) {
   return this->at(key).get<ValueType>();
}

I have notice we already has

get with type parameter but without key
at and [] with key but no type parameter
value with key but requires a typed default value.

I think the new API above would provide great convenience.
Please describe the steps to reproduce the issue.
None.
Can you provide a small but working code example?
None.
What is the expected behavior?
As the description of this issue.
And what is the actual behavior instead?
No such API.
Which compiler and operating system are you using?
None.

If such API is acceptable, I could prepare a pull request for that.

Also for get_ref<>.

Can you provide some code snippets that demonstrate the usage of this API?
BTW, there is a "Ideas" category at Discussions which seems to be meant for submitting proposals.


Using psql command instead of postgres in initialScript

Resolves : https://github.com/juspay/services-flake/issues/63

The CI is going into an infinite loop while running the postgres_test.nix, stopping it for now.

@rsrohitsingh682 will merge this today if there is nothing more to add


Setting a wallpaper

Can't figure out how to set a desktop wallpaper with a solid color. (Or in alternative with an image)
The SetDesktopWallpaper function is not documented.
thanks

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

The file was deleted from mediafire @youngerwarrior

@kuitog
IDesktopWallpaper:=ComObject("{c2cf3110-460e-4fc1-b9d0-8a1c0c9cc4bd}","{b92b56a9-8b55-4e14-9a89-0199bbb6f93b}")
loop 100 {
    ComCall(8,IDesktopWallpaper,"Uint",Random(0,0x00FFFFFF))
    Sleep 1000
}

this will set a random rgb color every 1000ms
IDesktopWallpaper:=ComObject("{c2cf3110-460e-4fc1-b9d0-8a1c0c9cc4bd}","{b92b56a9-8b55-4e14-9a89-0199bbb6f93b}")
ComCall(8,IDesktopWallpaper,"Ptr",0,"WStr","C:\path\to\wallpaper.jpg") ;monitorID=0 for all monitors

this is for setting a wallpaper(image) on all virtual desktops, and all monitors
#include %A_LineFile%\..\VD.ah2
VD.setWallpaperToDesktopNum("C:\path\to\wallpaper.jpg", 1)

this is for setting a wallpaper(image) to Desktop 1

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

@FuPeiJiang Hi!
many thanks for the reply!
Example 1 is perfect, but I can't figure out how to assign it only to desktop 2
IDesktopWallpaper:=ComObject("{c2cf3110-460e-4fc1-b9d0-8a1c0c9cc4bd}","{b92b56a9-8b55-4e14-9a89-0199bbb6f93b}") loop 100 {     ComCall(8,IDesktopWallpaper,"Uint",Random(0,0x00FFFFFF))     Sleep 1000 }

@kuitog
I don't even know how to do this manually in windows: how to set a different solid color for each virtual desktop
a workaround would be to use a .png (that is a solid color) for each virtual desktop
if you want that, I'll try to write a random solid color .png generator in ahk ?
it's a very good way to understand the format, imo


Crash caused by swizzling in GoogleUtilities

Describe your environment

Xcode version: 11.0 beta 6
Firebase SDK version: 6.5.0
Firebase Component: GoogleUtilities
Component version: 6.2.5

Describe the problem
Steps to reproduce:
This code was added to GULSwizzledObject.m in https://github.com/firebase/firebase-ios-sdk/pull/3300:
- (void)dealloc {
  // We need to make sure the swizzler is deallocated after the swizzled object to do the clean up
  // only when the swizzled object is not used.
  GULObjectSwizzler *swizzler = nil;
  BOOL isInstanceOfGeneratedClass = NO;

  @autoreleasepool {
    Class generatedClass = [self gul_class];
    isInstanceOfGeneratedClass = object_getClass(self) == generatedClass;

    swizzler = [[self gul_objectSwizzler] retain];
    [GULObjectSwizzler setAssociatedObject:self
                                       key:kSwizzlerAssociatedObjectKey
                                     value:nil
                               association:GUL_ASSOCIATION_RETAIN_NONATOMIC];
  }

  [super dealloc];

  [swizzler swizzledObjectHasBeenDeallocatedWithGeneratedSubclass:isInstanceOfGeneratedClass];
  [swizzler release];
}

We're seeing a crash at [super dealloc] in iOS 13 triggered by the deinit call of a UIViewController class that holds a reference to a custom WKWebView subclass.
In iOS 12, we've seen that we can continue through the rest of this dealloc method above, but our app then crashes immediately after.
When reverting to Firebase 5.19.0, our crashes disappeared. The crashes also disappeared when we replaced our custom WKWebView with the default WKWebView class.
While we've been able to revert to the default WKWebView class to solve our own particular issue, other users are may be seeing similar crashes. The stack trace on iOS 12 wasn't giving us enough information to track down the issue:
Stack Trace.txt
iOS 13 was a little more helpful.
iOS13 Stack Trace.txt

@swillsea Thank you for the detailed bug report!
As far as I can see, the custom WKWebView subclass is swizzled by Firebase Performance because the class declares URLSessionTaskDelegate conformance. Based on this I can suggest following temporary workaround options:

Avoid WKWebView conformance to URLSessionTaskDelegate directly in your subclass. Prefer using a separate private class confirming to URLSessionTaskDelegate for this instead.
Temporary remove Firebase Performance from dependencies if other options are not working for you.

There is ongoing work to make network performance tracking safer for all cases (tracked internally at b/127764622) but it may take some more time to be completed.
@swillsea I would like to ask couple details that will help us to fix the this particular case:

Is the crash reproducible 100% times?
If you have a simple app where the crash is reproducible?

cc @visumickey

@maksymmalyhin Thank you for both workarounds! We are making some changes to our WKWebView's cookie handling, so this may still be helpful for us even though we removed the specific implementation that declares URLSessionTaskDelegate conformance.
As for your questions, it was definitely reproducible 100% of the time. I don't have a simple app ready for you at the moment, but I could try to put something together if you think it would help.

@swillsea The app will definitely save us some time on additional questions because we will have everything we need to debug the issue and test fixes, so it is highly appreciated.

@maksymmalyhin I've been unable to reproduce the issue on a sample app, somewhat frustratingly. If you do decide to close the ticket out, I understand. At least having the discussion here may help other users in the future (assuming it wasn't specific to our app only)

@swillsea Thank you for the update. Let's close the ticket so far. Feel free to reopen it with more details.


Fix printing of undefined components

Currently, creating a vector of undefined components results in an error:
julia> buses = Vector{Bus}(undef, 5)
5-element Array{Bus,1}
Error showing value of type Array{Bus,1}:
ERROR: UndefRefError: access to undefined reference

On the other hand, buses = Vector{Bus}(undef, 5); works, because the issue is related to show. This PR fixes this error:
julia> buses = Vector{Bus}(undef, 5)
5-element Array{Bus,1}
#undef
#undef
#undef
#undef
#undef

it'd also be good to add a simple test, taking inspiration from test.show.jl in Base
https://github.com/JuliaLang/julia/blob/032cbc20f4ba53d4b4d3c3d13f8a1915d9cbb67e/test/show.jl#L25
e.g. a test using Vector{TestComponent}(undef, 3)

Sure. What would be a good test? Is something like this enough?
@testset "Test component prints" begin
    v = Vector{PowerSystemType}(undef, 3)
    @test println(v) === nothing
end

yeah, sprint(show, v) == "..." is the way to go, i think

Need to call include(".github/workflows/formatter_code.jl") in the rood directory to format the code (using JuliaFormater).


internal: align code to code style

bors r+
🤖

Looks like this commit already landed in a later PR


DIP25: implement in druntime

No win64.mak change?

Sorry, forgot it. Will fix.

Oops looks like it was failing unittests. Reverting.

auto merge auto merge auto merge

I'm really not sure why the EXPERIMENTAL feature needs the druntime fix? Any compiler changes for DIP25 should not introduce any library changes. Am I misunderstanding?

auto merge auto merge auto merge

Note, auto-merge is not a very well-documented feature... I only figured it out by seeing it happen and guessing.

Note, auto-merge is not a very well-documented feature... I only figured it out by seeing it happen and guessing.

Do you really think Andrei doesn't know how to use auto-merge?


SpinLock should be a class, not a struct

When using a SpinLock, consuming code should be always referencing the same instance - as its purpose is to have shared state.
At the moment, there are at least two easy ways of accidentally breaking the functionality of a SpinLock on account that it is a struct rather than a class.
private readonly SpinLock Locker = new()
This causes a copy of the SpinLock to be created every time it is used. So Locker.Enter works on a new instance, and effectively disables any locking
Making Locker type members readonly is a common practice, but the caveat here is "unless it's a SpinLock".
Another example is as follows:
public static class SpinLockExtensions
{
  public static void ExecuteLocked(this SpinLock locker, Action action)
  {
    ...Get the lock
    ...Do stuff
    ...Release the lock
  }
}

This creates a copy of the SpinLock each time Locker.ExecuteLocked() is called. To fix this we have to change the code to this ref SpinLock locker.
It seems the idea of a single-instance with shared state contradicts the idea of a struct that is copied to a new instance.
Changing SpinLock to a class would allow readonly members (which is good practice) and avoid accidental copying on extension methods.
And, as far as I can see, there is no reason to ever want a SpinLock to be copied.

private readonly SpinLock Locker = new()

Here is a proposal for that code to produce a warning: https://github.com/dotnet/runtime/issues/33773.

Changing SpinLock to a class

That would be a breaking change, so I'm quite certain it's not going to happen.

What would it break?

If nothing else, it would be a binary breaking change. That is, it would break if you have a library that was compiled targeting a framework where it's a struct and try to run it without recompilation on a runtime where it's a class.
This is because the IL is different, e.g. calling Locker.Exit() looks like this for a struct:
ldarg.0
ldflda valuetype SpinLock C::Locker
call instance void SpinLock::Exit()

But like this for a class:
ldarg.0
ldfld class SpinLock C::Locker
callvirt instance void SpinLock::Exit()

The difference between ldflda and ldfld is what would cause the issue.

I don't think .net 6 version assemblies will call .net 7 ones by default though, will they?

@mrpmorris They will, if they are run on .Net 7.
Imagine I create a .Net 6 library that uses SpinLock and publish it to NuGet. Then you create a .Net 7 application and want to use my library. If SpinLock was changed from struct to class in .Net 7, then my library won't work in your application.

In which case, mark it as obsolete and create a class named SpinLocker.

@stephentoub @terrajobst


React-slick vanishes when a using page is translated

React-slick works perfectly for 'english' but when page is translated to some right hand language like arabic or urdu, it shows no card.
I have resolved the issue by wrapping the react-slick carousel in a div and giving this div 'direction:ltr'. I think there must be a prop for this property also. Even there is a prop 'rtl' which does not work for this issue.
Thank you!!

@mghazanfar I'm facing the same issue.
Why did you close the issue then if it wasn't fix?

Because I got my own fix =D

@mghazanfar yeah i've tried this solution but its not fully working. there is a problem with the transform translate calculation as well. its only showing one item, even if there are more items to display.
I advice you to re-check your project ;)

I'll see for sure

Great. consider re-open this issue so there is no reason for me to open a new one.
@akiran do you know about this?

Confirm. The same for me. Just want to watch for updates

Can you regenerate it on codesandbox, because I'm trying it on my machine, and it's working fine without the issue. Please feel free to request reopen the issue.

I'm able to successfully translate the page without breaking anything. If someone is still facing the issue, please generate a demo on codesandbox and feel free to request reopen.

@laveesingh see my comment on #952


Remove definitions for FABsMenu

You can remove the included definitions for FABsMenu (https://github.com/jahirfiquitiva/FABsMenu) since it already includes the definitions in the library itself. As it is now I have two entries for it:

Btw. feel free to add my project andOTP (https://github.com/andOTP/andOTP) to the list of apps that use AboutLibraries.

@flocke please open a PR :)

@mikepenz sure, will do.

thank you


Output seems to be not right

Hi
I ran the stereoDNN in TX2 with the image given in the sample app and the output doesn't seem to be right.
nvidia@tegra-ubuntu:~/mohanen/stereoDNN/bin$ ./nvstereo_sample_app nvsmall 513 161 ../models/NVTiny/TensorRT/trt_weights_fp16.bin ../sample_app/data/img_left.png ../sample_app/data/img_right.png disp fp16

Output

Can anyone let me know what seems to be the problem here ..
Thanks and Regards,
Mohanen B

At the moment, the only network that correctly handles FP16 is ResNet18_2D.
The history is a little bit complicated: Stereo DNN code was originally released for TensorRT 3.0 where all networks were working fine, though not fully utilizing FP16 potential. In TRT 4.0, there were some changes which enabled proper FP16 support (and close to 2x speedup) in plugins given the plugins opt-in. We did not have time to update all of our plugins, so other networks will not work properly in FP16.

Ok, I am able to get the output in fp32 with NVTiny

hi, i have a problem. when i execute nvstereo_sample_app, there is a error: cannot execute binary file.  i have do "chmod 777 file" . i cannot solve it,  could help me, thank u


Display warning message or loading animation while Beacon post is saving

While dogfooding Beacon, I've navigated away from the page before the documents have finished uploading, because I didn't notice the % uploaded status in the lower left corner.
A nice-to-have would be:

a pop-up that tells me there are unsaved changes (like the one on Conductor)
or darkening the screen and adding a loading animation that make it really obvious that something is happening on the page, and they shouldn't navigate away

Can you add a screenshot/screencap? I can certainly add the dirtyForms plugin to Beacon without a ton of trouble, but I'm not totally sure what you mean.

Something like this?

:+1:


Add DPoP docs first cut

Closes/fixes #issue
This adds some basic documentation for Demonstrating Proof of Possession.
Checklist

[ ] This PR makes changes to the public API
[ ] I have included links for closing relevant issue numbers

thanks for contributing


Create a fresh ArrayEventContainer for each event in SimTelEventSource

Seems to have no impact on performance:
This branch:
SimTelEventSource: 1010ev [00:46, 21.70ev/s]

Master:
SimTelEventSource: 1010ev [00:46, 21.66ev/s]

I was bitten by the reuse of the container again, this time it was DL2 information from the previous events not being cleared.

i’m considering even replacing the current Container implementation with a dataclass based one,

That won't have all our features like prefixes / data types / help strings etc. dataclasses are a very powerful code generator, but in the end you get normal python classes with some fields. We have our own code generator here (that's essentially what the ContainerMeta class is, a code generator) that's I think better suited than starting over from dataclasses.


1.1.4 wmagent for patch2

Include following patch
#7933 filter exceptions on error log for wmstats
#7937 Accept plain list of lumis in the Run object
#7946 Fix merge cmssw version mismatch
#7952 Add site info for skipped file report
#7955 Add drain thread
#7957 Rollback unfinished transactions if ErrorHandler hits an exception
#7959 Fix a problem with new lumilist format
#7964 Raise HTTPException instead of ServerNotFoundError

 Bundle #7965 - fix #7933 - filter exceptions on error log for wmstats

 Bundle #7965 - fix #7937 - Accept plain list of lumis in the Run object

 Bundle #7965 - fix #7946 - merge cmssw version mismatch fix

 Bundle #7965 - fix #7952 - add site info for skipped file report

 Bundle #7965 - fix #7955 - Add drain thread

 Bundle #7965 - fix #7957 - Rollback unfinished transactions if ErrorHandler hits an exception

 Bundle #7965 - fix #7959 - Fix a problem with new lumilist format

 Bundle #7965 - fix #7964 - Raise HTTPException instead of ServerNotFoundError


Add info

This is a try to add the minimal required info functionality to get the version.

I'll test it with Yuneec SITL where we have the vendor version populated.


Hacks to fix build problems on import.

This fixes another build problem found while importing #23281.

Known issues: #23028


sway-contrib.grimshot: 0-unstable-2024-01-20 -> 0-unstable-2024-03-19

Description of changes

Added gnugrep to wrapper (fixes https://github.com/NixOS/nixpkgs/issues/315172)
sway-contrib.grimshot: 0-unstable-2024-01-20 -> 0-unstable-2024-03-19 (one new commit which includes bash completion: https://github.com/OctopusET/sway-contrib/commit/5d33a290e3cac3f0fed38ff950939da28e3ebfd7)
Added bash shell-completion

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 315364 run on aarch64-linux 1

3 packages built:

sway-contrib.grimshot
sway-contrib.grimshot.man
sway-contrib.inactive-windows-transparency


aws-sdk-cpp-config.cmake references .cmake files that don't exist

I get this error when I try to build my Android project:
CMake Error at /Users/christophersimmons/Documents/repos/DoclilyAndroid/build-aws-cpp-sdk/aws-sdk-cpp-config.cmake:1 (include):
include could not find load file:
/Users/christophersimmons/Documents/repos/DoclilyAndroid/build-aws-cpp-sdk/aws-cpp-sdk-core/aws-cpp-sdk-core-config.cmake

When I look at aws-sdk-cpp-config.cmake, I see that it references .cmake files that don't exist.
~/Documents/repos/DoclilyAndroid/build-aws-cpp-sdk$ cat ./aws-sdk-cpp-config.cmake
include("${CMAKE_CURRENT_LIST_DIR}/aws-cpp-sdk-core/aws-cpp-sdk-core-config.cmake")
include("${CMAKE_CURRENT_LIST_DIR}/aws-cpp-sdk-cognito-identity/aws-cpp-sdk-cognito-identity-config.cmake")
include("${CMAKE_CURRENT_LIST_DIR}/aws-cpp-sdk-iam/aws-cpp-sdk-iam-config.cmake")
include("${CMAKE_CURRENT_LIST_DIR}/aws-cpp-sdk-access-management/aws-cpp-sdk-access-management-config.cmake")
~/Documents/repos/DoclilyAndroid/build-aws-cpp-sdk$ ls -1 aws-cpp-sdk-core
CMakeFiles
Makefile
cmake_install.cmake
libaws-cpp-sdk-core.so

The other three folders look similar. How can I fix this problem? In case it matters, I originally created the sdk's build folder by running the following:
cmake -DTARGET_ARCH=ANDROID -DNDK_RELEASE=r13b -DANDROID_NATIVE_API_LEVEL=21 -DBUILD_ONLY="cognito-identity;access-management" -DANDROID_ABI=mips64 -Wno-dev ../deps/aws-sdk-cpp/

What happens when you clear your build directory and add 'core' to the BUILD_ONLY list?

Same issue when I ran
cmake -DTARGET_ARCH=ANDROID -DNDK_RELEASE=r13b -DANDROID_NATIVE_API_LEVEL=21 -DBUILD_ONLY="core;cognito-identity;access-management" -DANDROID_ABI=mips64 -Wno-dev ../deps/aws-sdk-cpp/

What version of cmake are you using?

~/Documents/repos/DoclilyAndroid/build-aws-cpp-sdk$ cmake --version
cmake version 3.6.3

CMake suite maintained and supported by Kitware (kitware.com/cmake).

Oh wait, the packaging and config generation is not enabled for android I think.  We should be able to fix this fairly quickly.

I have a potential fix pushed to the FB-ConfigFix branch.  Can you give it a try?  If it works out, we will probably have it pushed to mainline after some more extensive testing tomorrow.

I'll try it now.

I'm hitting a different issue that's due to an error on my part, but I think that the CMake issue is fixed now.
~/Documents/repos/DoclilyAndroid/build-aws-cpp-sdk$ ls -1 ./aws-cpp-sdk-core
CMakeFiles
Makefile
aws-cpp-sdk-core-config-version.cmake
aws-cpp-sdk-core-config.cmake
aws-cpp-sdk-core-targets.cmake
aws-cpp-sdk-core.pc
cmake_install.cmake
libaws-cpp-sdk-core.so


Fix MinHeight reference

@jwmsft : PR passed the acceptance checklist. Please evaluate further and approve/merge if appropriate. Thanks!


Feat: return base64 encoded images for PDF's

Closes #2302.
Summary

add functionality to get a Base64 encoded string from a PIL image
store base64 encoded image data in two metadata fields: image_base64 and image_mime_type
update the "image element filter" logic to keep all image elements in the output if a user specifies image extraction

Testing
from unstructured.partition.pdf import partition_pdf

elements = partition_pdf(
    filename="example-docs/embedded-images-tables.pdf",
    strategy="hi_res",
    extract_element_types=["Image", "Table"],
    extract_to_payload=True,
)

or
from unstructured.partition.auto import partition

elements = partition(
    filename="example-docs/embedded-images-tables.pdf",
    strategy="hi_res",
    pdf_extract_element_types=["Image", "Table"],
    pdf_extract_to_payload=True,
)

Thanks @awalker4 :)

I wish I had thought of this earlier, but with so many interdependent parameters, I wonder if it would have made more sense to have extract_to_payload be a Tuple(str, list) instead of a list. Then the first index could be used to determine extract_to_payload or image_output_dir_path since those two parameters seem to be mutually exclusive.

I know this isn't the intended use for these parameters, but NarrativeText isn't working as a element type for extract_element_types. It raises a warning: The requested type (NarrativeText) doesn't match any available type.

Also noticing on this document that the table element isn't complete. It's element[5], but element[6] is categorized as a Title element and element[6].text is 'Corrosion rate (mm/year)', which is cut off in the image that's generated when using image_output_dir_path.

An idea for a future enhancement, but would it make sense to have "all" be an option for extract_element_types?


win32: Improve default font

Currently, Fixedsys is the default font on Windows.
It is not suitable for recent High DPI environments.

Change the default font to Consolas.
Allow to change the default font by the translation message. E.g.:msgid "DefaultFontNameForWindows"
msgstr "Courier New"

Close #12919

Is there a reason why we need to provide a localized default font?

I don't think about using Fixedsys at all.
I am considering using MS Gothic as the Japanese default font. It is the most widely used Japanese fixed-pitch vector font.
I think there are similar kinds of fonts for other CJK languages.
That's the reason why I'm going to provide a way to set a localized default font.
The problem might be that the ANSI part is not so beautiful compared to Consolas.
set gfn=MS_Gothic

I guess one issue is that the substituted font is usually not a monospace font

Yes. The Japanese part is not shown well aligned if Consolas is used.
set gfn=Consolas

Using 'guifontwide' shows the ANSI part and the Japanese part very nicely. However, using 'guifontwide' has some pitfalls.
So, I don't want to make this the default.
set gfn=Consolas gfw=MS_Gothic

Right. FWIW, part of the reason why I'm asking is that I'm changing how MacVim is rendering fonts and was looking at the GTK/Win32 code for reference.
I'm planning to change it so that in MacVim, if you do set guifont=Consolas,MSGothic, MSGothic will be chosen as a fallback font and automatically used when the first font doesn't support the Unicode value of the character you need (e.g. Japanese characters). Right now, the Vim fallback logic is just picking the first font in the list that loads, but it doesn't do per-character fallback. Doing this also kind of means guifontwide is unnecessary as you can just specify the entire fallback list you want in guifont. Only issue is you have to query the font to for every character you want to render to see if it's supported by the font you want, so I need to profile if there's a performance cost at all or whether caching is necessary.
Also, the existing behavior is also why people have to rely on patched fonts (e.g. Nerd Font) for Powerline etc because Vim can only load one font at a time. Terminals like Kitty actually already provide fallback font options so you can do what I just mentioned above and have Kitty automatically pick a font that supports the character you are typing. I think some terminals also support different Italic/Bold font as well (I think I may support that in MacVim as well using a special syntax in guifont, e.g. something like set guifont=Menlo:h12,Monaco:sItalic).
Sorry to get a little off topic, just wanted to share this before I work on it in case the Windows/GTK implementations of gVim may want something like that as well and want to share the syntax.

Yes. The Japanese part is not shown well aligned if Consolas is used.

Regardless of default font choice, I kind of feel like this could be fixed up? I think the Win32 code mandates fixed-width font right now but I never knew if there's a particular technical reason or whether it's just because it looks bad otherwise. The issue with the mandate is that the OS is going to internally substitute with a non-fixed-width font anyway when they try to render CJK characters (as was the case when you were using Consolas). Is it something that could be fixed up in the font rendering code to make them align better? I haven't touched the Win32 font rendering code so I don't have a lot of contexts.

Also, just curious how are you generating that list of CJK / Hiragana / Katakana etc symbols? Is that a custom script / file you use?

Also, just curious how are you generating that list of CJK / Hiragana / Katakana etc symbols?

:dig!
This is useful when checking the font rendering. (This doesn't include Kanji / Hanzi, though.)


Team Leader #4

Currently the coordinators know their team leads, in the future we may need more team leads outside of redeemers.


onPointer events errors in console

Hello,
when I added one of accountDropdownProps and navProps to my Site.Wrapper i have warnings in console (screenshot below). When I comment accountDropdown and navProps, warnings disappears.
How to fix it?
const accountDropdownProps = {
      name: `${user.firstName} ${user.lastName}`,
      description: 'Administrator',
      options: [
        { icon: 'user', value: 'Profile', to: '/' },
        { icon: 'settings', value: 'Settings', to: '/' },
        { icon: 'mail', value: 'Inbox', badge: '6', to: '/' },
        { icon: 'send', value: 'Message', to: '/' },
        { isDivider: true },
        { icon: 'help-circle', value: 'Need help?', to: '/' },
        { icon: 'log-out', value: 'Sign out', onClick: () => logout() },
      ],
    };

const navBarItems = [
  { value: 'Home', to: '/', icon: 'home', LinkComponent: NavLink },
  {
    value: 'Forms',
    to: '/form-elements',
    icon: 'check-square',
    LinkComponent: NavLink,
  },
  {
    icon: 'file-text',
    value: 'Documentation',
    to: 'https://tabler.github.io/tabler-react/documentation',
  },
];

        <Site.Wrapper
          headerProps={{
            href: '/',
            alt: 'Tabler React',
            accountDropdown: accountDropdownProps, // when I comment this, warnings disappears
          }}
          navProps={{ itemsObjects: navBarItems }} // when I comment this, warnings disappears
        >

This is caused by my implementation of the events in most of the components. React has an event handler for pointers that doesn’t seem to be implemented.
Right now this shouldn’t cause any problems to your code has it is ignored.
I have to remove the eventHandler for pointers from the code.

On Aug 28, 2018, at 06:56, Dominik Kurbiel<EMAIL_ADDRESS>wrote:
Hello,
when I added one of accountDropdownProps and navProps to my Site.Wrapper i have warnings in console (screenshot below). When I comment accountDropdown and navProps, warnings disappears.
How to fix it?
const accountDropdownProps = {
name: ${user.firstName} ${user.lastName},
description: 'Administrator',
options: [
{ icon: 'user', value: 'Profile', to: '/' },
{ icon: 'settings', value: 'Settings', to: '/' },
{ icon: 'mail', value: 'Inbox', badge: '6', to: '/' },
{ icon: 'send', value: 'Message', to: '/' },
{ isDivider: true },
{ icon: 'help-circle', value: 'Need help?', to: '/' },
{ icon: 'log-out', value: 'Sign out', onClick: () => logout() },
],
};
const navBarItems = [
{ value: 'Home', to: '/', icon: 'home', LinkComponent: NavLink },
{
value: 'Forms',
to: '/form-elements',
icon: 'check-square',
LinkComponent: NavLink,
},
{
icon: 'file-text',
value: 'Documentation',
to: 'https://tabler.github.io/tabler-react/documentation',
},
];
<Site.Wrapper
headerProps={{
href: '/',
alt: 'Tabler React',
accountDropdown: accountDropdownProps, // when I comment this, warnings disappears
}}
navProps={{ itemsObjects: navBarItems }} // when I comment this, warnings disappears
>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

https://reactjs.org/blog/2018/05/23/react-v-16-4.html
I just updated React to 16.4 when I had the same problem.

Closing this as I believe it has been resolved but please comment if that is not the case and I will reopen.

I had the same problem:
index.js:1406 Warning: React does not recognize the staticContext prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase staticcontext instead. If you accidentally passed it from a parent component, remove it from the DOM element.
in a (created by LinkAnchor)
in LinkAnchor (created by Context.Consumer)
in Link (created by Context.Consumer)
in NavLink (created by Context.Consumer)
in withRouter(NavLink) (created by Nav.Link)
in Nav.Link (created by NavItem)
in li (created by ClickOutside)
in ClickOutside (created by NavItem)
in NavItem (created by Nav)
in ul (created by Nav)
in Nav (created by Site.Nav)
in div (created by Grid.Col)
in Grid.Col (created by Site.Nav)
in div (created by Grid.Row)
in Grid.Row (created by Site.Nav)
in div (created by Container)
in Container (created by Site.Nav)
in div (created by Site.Nav)
in Site.Nav (created by Site.Wrapper)
in div (created by Page.Main)
in Page.Main (created by Site.Wrapper)
in div (created by Page)
in Page (created by Site.Wrapper)
in Site.Wrapper (at SideWrapper.js:118)
in SideWrapper (at home.js:22)
in Home (created by Context.Consumer)
in Route (at routes/index.js:53)
in Switch (at routes/index.js:48)
in Routes (at App.js:19)
in Router (at App.js:17)
in PersistGate (at App.js:16)
in Provider (at App.js:15)
in App (at src/index.js:6)

@moraes65
In case the warning is still bothering you, you can fix it by modifying the withRouter call inside the SiteWrapper.react.js.
Change this:
 LinkComponent: withRouter(NavLink)
To This:
withRouter(({staticContext, ...props}) => { return <NavLink {...props}/>})
More about the issue of the static context inside the router  here.


Change names of Workflow and PR Bridge Repos and Changelog App

For a better understanding of work in this project, the new suggested names for the repos in the changelog process should changed:

From OpenSearch_Parse_Chagelog_Action to OpenSearch_Changelog_Workflow (this repo)
From OpenSearch_Changeset_Bot to OpenSearch_Changelog_PR_Bridge (repo in this link)
From OpenSearch_Changeset_Bot to OpenSearch_Changelog_Bot (app in this link)

The update in the repos and app will require an entire update in the .md files for the links to the repos and app

This is already addressed in release v1.0.0-alpha


colorschemes do not show up in nvim or nvim-qt

An example ~/.vim/dein.vim (sourced from ~/.vimrc):
" Required:
set runtimepath+=/home/jsakkine/.vim/dein/repos/github.com/Shougo/dein.vim

" Required:
if dein#load_state('/home/jsakkine/.vim/dein')
  call dein#begin('/home/jsakkine/.vim/dein')

  " Required:
  call dein#add('/home/jsakkine/.vim/dein/repos/github.com/Shougo/dein.vim')

  " Plugins:
  call dein#add('NLKNguyen/papercolor-theme')

  " Required:
  call dein#end()
  call dein#save_state()
endif

My .config/nvim/init.vim:
set runtimepath^=~/.vim runtimepath+=~/.vim/after
let &packpath = &runtimepath
source ~/.vimrc

In vim and gvim I can set PaperClip colorscheme but not in nvim or nvim-qt.

https://github.com/Shougo/dein.vim/issues/261


Planck FFP10 noise sims interface

It might be useful to have a class / function to load FFP10 Planck noise sims on to the same geometry and coordinate system as the SO noise sims. Let's discuss whether this is really useful and what the details might look like.

/global/cfs/cdirs/cmb/data/planck2018/ffp10


Simpler tests bootstrap

Dropped the test bootstrap file as it's not necessary.

Tests are failing on Travis and on my machine (even on master). For example:
--- Expected
+++ Actual
@@ @@
-'
-
An aside

-
+'
An aside

Maybe the latest version of CommonMark changed the way it renders?


WIP - instancetype: Refactor find logic

What this PR does
This PR starts the process of refactoring pkg/instancetype/instancetype.go as set out in the following design proposal:
design-proposal: instancetype.kubevirt.io - pkg/instancetype refactor
https://github.com/kubevirt/community/pull/323
This initial series extracting find logic into subpackages.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

NONE

/sig code-quality

/lgtm

/hold
Apologies, bad rebase. I'll correct now.

Changed - Imports reworked, FWIW this is linted so our current lint config isn't catching these nits it needs to be addressed.

/close
Replaced by https://github.com/kubevirt/kubevirt/pull/13036


:seedling: Rename x64 kai binaries

The nodejs os.arch() function uses the name x64 and not amd64 for intel/amd arch.
See: https://nodejs.org/docs/latest-v20.x/api/os.html#osarch

Thank you @sjd78

Ran into this today also - thanks!


Google Big Query: Timestamp format when using extract to GCS as JSON new line

Hey,
we are using extract jobs with the NEWLINE_DELIMITED_JSON format to export data from BigQuery to CloudStorage.
When the export data contains a TIMESTAMP field, the resulting JSON entry looks like this:
"2020-09-11 09:18:26 UTC"

In PHP, this format can be represented as Y-m-d H:i:s e. Unfortunately, this format is not part of the built-in formats of DateTimeInterface:
interface DateTimeInterface {
    const ATOM = 'Y-m-d\TH:i:sP';
    const COOKIE = 'l, d-M-Y H:i:s T';
    const ISO8601 = 'Y-m-d\TH:i:sO';
    const RFC822 = 'D, d M y H:i:s O';
    const RFC850 = 'l, d-M-y H:i:s T';
    const RFC1036 = 'D, d M y H:i:s O';
    const RFC1123 = 'D, d M Y H:i:s O';
    const RFC2822 = 'D, d M Y H:i:s O';
    const RFC3339 = 'Y-m-d\TH:i:sP';
    const RFC3339_EXTENDED = 'Y-m-d\TH:i:s.vP';
    const RFC7231 = 'D, d M Y H:i:s \G\M\T';
    const RSS = 'D, d M Y H:i:s O';
    const W3C = 'Y-m-d\TH:i:sP';
//...
}

Questions

Why are you choosing this (non-standard?) format?
OR is there a specific name for this format?

@jdpedrie Let's chat about this in Tuesday's meeting to see if there is something we should do here to fix/explain.

@jdpedrie Let's chat about this in Tuesday's meeting to see if there is something we should do here to fix/explain.


nakama closes connection for specific user

Description
For specific user nakama closes connection. On release server we proxy connection via nginx to nakama, so, to make it clear:

I've copied release db on test server.
Opened nakama for public access.
Even disabled ssl.
Same problem - for specific user nakama closes connection.

On test server we have debug logs, so, here we are.
Logs
A lot of:
{"level":"debug","ts":"2019-07-24T17:43:50.089Z","msg":"Sending *rtapi.Envelope_Channel message","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9","envelope":"cid:\"wchqild1698mn267uz56htjeypkifn\" channel:<id:\"2...[8f752e66-88ee-4852-9cb4-79bdffc5b475]13\" self:<user_id:\"b246adbe-c1af-4532-88ca-f1d1709b0211\" session_id:\"b95adfce-0aae-46fb-8080-e97b20f6e3d9\" username:\"MXcirdiWGi\" persistence:true > > "}
{"level":"debug","ts":"2019-07-24T17:43:50.089Z","msg":"Received *rtapi.Envelope_ChannelJoin message","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9","cid":"tg8l0deerpb1j386o373homxpnc9le","message":{"ChannelJoin":{"target":"028ea038-8311-4361-aa9f-5ac30bff4c9c","type":3,"persistence":{"value":true},"hidden":{}}}}

And after that:
{"level":"debug","ts":"2019-07-24T17:43:50.089Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.090Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.091Z","msg":"Sending *rtapi.Envelope_Channel message","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9","envelope":"cid:\"tg8l0deerpb1j386o373homxpnc9le\" channel:<id:\"3.028ea038-8311-4361-aa9f-5ac30bff4c9c..\" self:<user_id:\"b246adbe-c1af-4532-88ca-f1d1709b0211\" session_id:\"b95adfce-0aae-46fb-8080-e97b20f6e3d9\" username:\"MXcirdiWGi\" persistence:true > > "}
{"level":"debug","ts":"2019-07-24T17:43:50.091Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"debug","ts":"2019-07-24T17:43:50.091Z","msg":"Received *rtapi.Envelope_StatusUpdate message","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9","cid":"j9tybnfb0el7u87h96dn9eyxj5qpj6","message":{"StatusUpdate":{"status":{"value":"{\"n\":\"UnnyNet\"}"}}}}
{"level":"debug","ts":"2019-07-24T17:43:50.091Z","msg":"Sending <nil> message","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9","envelope":"cid:\"j9tybnfb0el7u87h96dn9eyxj5qpj6\" "}
{"level":"debug","ts":"2019-07-24T17:43:50.091Z","msg":"Error reading message from client","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9","error":"websocket: read limit exceeded"}
{"level":"warn","ts":"2019-07-24T17:43:50.091Z","msg":"Could not write message","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9","error":"websocket: close sent"}
{"level":"info","ts":"2019-07-24T17:43:50.091Z","msg":"Cleaning up closed client connection","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9"}
{"level":"info","ts":"2019-07-24T17:43:50.091Z","msg":"Cleaned up closed connection matchmaker","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9"}
{"level":"debug","ts":"2019-07-24T17:43:50.091Z","msg":"Processing presence event","joins":1,"leaves":0}
{"level":"info","ts":"2019-07-24T17:43:50.091Z","msg":"Cleaned up closed connection tracker","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9"}
{"level":"debug","ts":"2019-07-24T17:43:50.091Z","msg":"Processing presence event","joins":0,"leaves":140}
{"level":"info","ts":"2019-07-24T17:43:50.091Z","msg":"Cleaned up closed connection session registry","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9"}
{"level":"debug","ts":"2019-07-24T17:43:50.091Z","msg":"Could not send close message","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9","error":"websocket: close sent"}
{"level":"info","ts":"2019-07-24T17:43:50.091Z","msg":"Closed client connection","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"b95adfce-0aae-46fb-8080-e97b20f6e3d9"}
{"level":"info","ts":"2019-07-24T17:43:50.516Z","msg":"New WebSocket session connected","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"8cb7de72-a19d-492d-832f-f01ea883bace","format":0}
{"level":"debug","ts":"2019-07-24T17:43:50.840Z","msg":"Error reading message from client","uid":"b246adbe-c1af-4532-88ca-f1d1709b0211","sid":"8cb7de72-a19d-492d-832f-f01ea883bace","error":"websocket: read limit exceeded"}

Environment

Nakama: 2.5.1
Cockroach: 2.1.4
Operating System and version: Ubuntu 16.04.5 LTS

From the logs it looks like there is specific message that reads this:
"error":"websocket: read limit exceeded"}

Looks like the client has exceeded sending/receiving messages from the Websocket connection. You need to either change your client to send less messages, or increase the buffer size:
--max_message_size_bytes

This isn't an issue in Nakama but a misconfiguration on your setup.


Updates to version numbers, dates, rotation of authorship for coordin…

…ated release.
Pull Request Testing

[ ] Describe testing already performed for these changes:

[ ] Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:

[ ] Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes or No]

[ ] Do these changes include sufficient testing updates? [Yes or No]

[ ] Will this PR result in changes to the test suite? [Yes or No]
If yes, describe the new output and/or changes to the existing output:

[ ] Do these changes introduce new SonarQube findings? [Yes or No]
If yes, please describe:

[ ] Please complete this pull request review by [Fill in date].

Pull Request Checklist
See the METplus Workflow for details.

[ ] Add any new Python packages to the METplus Components Python Requirements table.
[ ] Review the source issue metadata (required labels, projects, and milestone).
[ ] Complete the PR definition above.
[ ] Ensure the PR title matches the feature or bugfix branch name.
[ ] Define the PR metadata, as permissions allow.
Select: Reviewer(s) and Development issue
Select: Milestone as the version that will include these changes
Select: Coordinated METplus-X.Y Support project for bugfix releases or METdataio-X.Y.Z Development project for official releases
[ ] After submitting the PR, select the :gear: icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
[ ] After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
[ ] Close the linked issue and delete your feature or bugfix branch from GitHub.

Thanks!
On Tue, Dec 17, 2024 at 2:25 PM Julie Prestopnik @.***>
wrote:

@.**** requested changes on this pull request.
@bikegeek https://github.com/bikegeek for the official release, under Update
Release Notes
https://metplus.readthedocs.io/en/develop/Release_Guide/metdataio_official.html#update-release-notes
the instructions say "When creating the official release, combine the beta
release sections into one section (i.e. “Version X.Y.Z release notes
(YYYYMMDD)”)." so I believe we want to combine all of the betas and rc
release notes into one section for the official release so that it has the
main header for the page ("METdataio Release Notes") but only one
subsection ("METdataio Version 3.0.0 Release Notes (20241217)") but
contains all of the dropdowns with the current information that is
currently separated into subsections. Please let me know if you have any
questions.
—
Reply to this email directly, view it on GitHub
https://github.com/dtcenter/METdataio/pull/358#pullrequestreview-2510172436,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4UJHQUHOVUX4XQOGJ3GWT2GCJDXAVCNFSM6AAAAABTZIYOPOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKMJQGE3TENBTGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks Julie.  We DO NOT want to consolidate the mysql files, these are
used for incrementally updating the schemas so they are not documentation
but considered code.
On Tue, Dec 17, 2024 at 3:15 PM Julie Prestopnik @.***>
wrote:

@.**** requested changes on this pull request.
Thanks for making the updates to the release notes, @bikegeek
https://github.com/bikegeek. I have one more suggestion - instead of
leaving the area under "New Functionality" empty, could you please add
"NONE" so that users can be sure to know that we didn't add any new
functionality instead of inadvertently leaving it blank? Apologies - I know
this is very nit-picky... One more question - in the upgrade instructions,
I noticed that there are references to files with filenames that contain
references to "beta" (for example,
"METdataio/METdbLoad/sql/updates/update_for_6_0_beta6.sql") and in that
directory
https://github.com/dtcenter/METdataio/tree/main_v3.0/METdbLoad/sql/updates,
I see that we previously had filenames like "update_for_5_1.sql
https://github.com/dtcenter/METdataio/blob/main_v3.0/METdbLoad/sql/updates/update_for_5_1.sql".
Do we want to combine the update_for_6_0_beta4.sql
https://github.com/dtcenter/METdataio/blob/main_v3.0/METdbLoad/sql/updates/update_for_6_0_beta4.sql,
update_for_6_0_beta5.sql
https://github.com/dtcenter/METdataio/blob/main_v3.0/METdbLoad/sql/updates/update_for_6_0_beta5.sql,
and update_for_6_0_beta6.sql
https://github.com/dtcenter/METdataio/blob/main_v3.0/METdbLoad/sql/updates/update_for_6_0_beta6.sql
files into one update_for_6_0.sql file? I don't fully know what these are
or how they are used so I don't know what's best, but thought it was worth
inquiring about.
—
Reply to this email directly, view it on GitHub
https://github.com/dtcenter/METdataio/pull/358#pullrequestreview-2510261790,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4UJHTR7YNVQJ2FUIAYBL32GCO7ZAVCNFSM6AAAAABTZIYOPOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKMJQGI3DCNZZGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ugh, I just noticed it says this is a "Draft".  I went ahead and approved.  Let me know if you need me to re-approve.  Apologies that I did not notice that sooner.


Write documentation about the * special content action, #17

This PR explicits the use of the * key in the contentActions prop.
It also fixes the interactivity of the tooltip content.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Minor changes to the FnApi Runner to allow Java to run.

Aligned the GBK urn.
Started a logging service, which Java can't run without.
Added some logging that was helpful for debugging.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @herohde
Go should be able to use this as well.

LGTM
Cool!

R: @aaltay Could you give your approval as a committer?

LGTM. Thank you. Please self-merge.


Feature/refactor

remove unused/redundant schemas to make syncing faster

remove Protocol.blockNumber/timestamp
remove Market.baseAmount/quoteAmount (the value is incorrect anyway)

annotate event entities as @entity(immutable: true)
normalize Market.feeRatio
read referral contract address from periphery metadata

Hope we can save 50% sync time 🤞


eureka: 5.57 notes, array support for notes

5.57 patch notes included Dyunbu's note (12) to drop in 2 additionals skirmishes, one which already had a drop so I added it as an array and added a typeof check to support both.
Hasn't been tested because of maintenance.

Sorry I haven't gotten back to this, but I was waiting for you to test/respond to comments above.  Were you planning on looking at this some more?

Hello, didn't have time to manage this for now, if you want to take over please do, I don't wanna drag it for too long !


Inconsistent type narrowing behavior between compound assignment operators and their expanded equivalents

🔎 Search Terms
"assignment operator" "type narrowing"
🕗 Version & Regression Information

This is the behavior in every version in the Playground that I tried, and I reviewed the FAQ for entries about assignment operators and narrowing (there isn't any, though)

⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.8.0-dev.20241116#code/GYVwdgxgLglg9mABAdzgJwNYGcAUAHAQzQIFsAuRLKNGMAc0QB9EwQSAjAUzQEoKqa9RAG8AUIkSFiJRAF5JRUogDUiAEQE1AbnGI0nKCDRIppLYgD0FxAEEIETniicAJhQDkpku8QwsLIjQ4ZFdEKDhEdwFaOndRAF9RUVBIWARKAAs4EAAbFxscrDgAdXQMACEQKAAROE4sADk4KHxFckpqGKYWNi5efk6hMQkvFXkNbV19Q2MFaXMrRAAVAE88TkQAUTQgtA8vHz9EAH0wZuOAneDQ8Mjo+jj4oA
💻 Code
function works(param: string | number): string {
  param = param + "a";
  return param; // Accepted: 'param' is narrowed to 'string'
}

function shouldAlsoWorkButDoesNot(param: string | number): string {
  param += "a";
  return param; // Type Error: 'param' is _not_ narrowed to 'string'
}

🙁 Actual behavior
Compound assignments (+=) and their expanded equivalents (x = x + ...) behave differently: param = param + "a" correctly narrows but param += "a" does not.
🙂 Expected behavior
+= should behave equivalently to x = x + ... with respect to type narrowing.
Additional information about the issue
The code example is taken from here.
Another less relevant issue which also reveals the inconsistency between += and x = x + ... is #60521.

duplicate-ish of #9815 and/or #17204 and/or #44553? Also related to #47027 (as linked above).


Tapping on signature box area produces empty signature image

When we tap any finger on signature box area, sometimes it does not produce any dot/image but it still saves the empty signature image in the form of bitmap. I have one action to perform in my app which should meet all the requirements including the signatures. Since, there are no signatures drawn in front of the user and it still produces the signature image internally and it allows the user to perform an action by taking the empty signature ahead. Please try to resolve the problem as soon as possible.
Thanks
Varun Goyal

SignaturePad has an isEmpty() function. I noticed it is set when a motion is detected on the view.
Is there a way for it to inspect the resulting bitmap for signature strokes, or the presence of anything other than blank/white content? I feel this would be a far better implementation of isEmpty() than just checking if a user touched the view.

I have prevented this bug and this could be work around for not generating empty image.
`@OnTouch(R.id.signature_pad)
boolean buttonsTouched(View v, MotionEvent event) {
AppLogger.d(getTag(), String.valueOf(event.getAction()));
switch (event.getAction()) {
case MotionEvent.ACTION_DOWN:
AppLogger.d(getTag(), "ACTION_DOWN");
movementMilis = event.getEventTime();
return false;
case MotionEvent.ACTION_UP:
if (event.getEventTime() - movementMilis < 100) {
/* required */
}
AppLogger.d(getTag(), "ACTION_UP");
return false;
case MotionEvent.ACTION_MOVE:
if (event.getEventTime() - movementMilis > 100){
mSaveButton.setVisible(true); //key factor. only visible save button after 100ms movement on screen
}
AppLogger.d(getTag(), "ACTION_MOVE");
return false;
        default:
            break;
    }
    return true;

}`

above code not working and mSignaturePad.isEmpty() only


Update README.md

Added publications, software repos, video and book links

Meanwhile, to have the literature entries consistent, I am not sure about whether we should always point to the DOI and link the authors copy as a separate [PDF] link at the end of the entry?
Side note: I would recommend to use authorarchive (or CoverPage) for self-archived PDFs.


Wildcard routing

As usual I have an awkward use case, or so it seems. I'm using PHP-Foundation and I think I need some kind of wild card routing. Let me explain why.
Coast CMS is a static site or static web page editor which I love for it's wonderful user interaction. However, the code base is dated and security isn't optimal.
My intention is to recreate Coast CMS using a modern and solid framework: PHP Foundation.
The issue is this: Coast CMS does not require any modification of a static web page. When a user is logged in it simple injects additional CSS and JS to make certain parts of the page content editable.
By using a route like this in /App/index.php:
$app->get('/:page', ['\App\ShowSitePageController', 'showPage']);

I can process a HTML page and also any other file like an image which are at the same directory level as the page. The problem is that all other files in sub directories are not routed. That's why I'm wondering about wildcard routing, like for instance:
$app->get('/:page/*.*', ['\App\ShowSitePageController', 'showPageResource']);

To separate the framework and the static site ideally I would like to have this file structure:
cms/
index.html
about.html
images/logo.png

where the framework is in cms/ and the other three files make the static site. This structure, I concluded, is not possible.
Second best is this structure:
site/
site/index.html
site/about.html
site/images/logo.png
app/
index.php
... all other framework files

where the static site is in it's own directory named site.
With the wildcard router one could simply route /about.html and all accompanying CSS files and images and have the controller fetch them from the site directory.
I fear this is currently not supported, in which case this is a feature request.

The router is built around forward slashes as the separators between path segments, as you can see here:
/** Regular expression used to find named parameters in routes */
const REGEX_PATH_PARAMS = '/(?<=\/):([^\/]+)(?=\/|$)/';
/** Regular expression used to match a single segment of a path */
const REGEX_PATH_SEGMENT = '([^\/]+)';

If you don’t want that, you could change those two constants.
Or you could work with Router#getRootPath and Router#getRoute directly and decide based on that, without defining routes for the router in the first place.
These are also available via App#currentRoute (also: App#getRequestMethod).
Finally, you could work with $_SERVER['REQUEST_URI'] directly.
All these solutions would leave out the root definitions in your index.php and just do something based on the variables and methods listed above. The two App methods should probably be the most helpful.
When it comes to your different directory structure, this should (both) be possible by adjusting the routing in the .htaccess (in the single section named “Routing”).

When a user is logged in it simple injects additional CSS and JS to make certain parts of the page content editable.

But it writes back to the files on the server, right? So there must be some actual (server-side) authentication somewhere.

Thanks for your help on this.
For the purpose of these issues also being a kind of knowledge base I'd like to share how I solved it.
The directory structure is exactly what I wanted in the first place:
steckelfish/
draft/index.html
draft/about.html
draft/images/logo.png
index.html
about.html
images/logo.png

The PHP-Foundation app is in the steckelfish/ directory while the draft/ directory holds draft versions of pages that can (in future) be published to the site root once they are ready to go public. Of course the editing of draft pages and the publish action is only allowed to logged in users/authors.
The site root is not the webserver document root and to get this setup these are the configuration settings:
In steckelfish/config/.env:
# The public HTTP(S) URL pointing at the application's root directory
APP_PUBLIC_URL=http://localhost/sf2-dev/

BTW this site root URL is available in PHP through $app->url('/') and in a Twig template as app.url('/').
The .htaccess file, normally in the framework directory (steckelfish/ in this case) is moved one level up, so it is in sf2-dev/. This is in the section “Routing”:
# Do not rewrite physical files with the exception of
# directories and HTML files in the draft directory
RewriteCond %{REQUEST_FILENAME} -f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^(.*)/draft/.*\.html$
RewriteRule . - [L]

# And let 'index.php' handle everything else
RewriteRule . steckelfish/index.php [L]

Now the routing is pretty straightforward. I looked at the regular expressions at PHP-Router#17 as you pointed out but going that route is way over my head. So these are the routes in steckelfish/app/index.php is like this:
$app->get('/draft', [ '\App\DraftPageController', 'showIndex' ]);
$app->get('/draft/', [ '\App\DraftPageController', 'showIndex' ]);
$app->get('/draft/:page', [ '\App\DraftPageController', 'showPage' ]);

Again thank you for your help.

For the purpose of these issues also being a kind of knowledge base I'd like to share how I solved it.

This is very much appreciated, thank you!
Regarding your solution, what you write all makes sense and looks good.

I looked at the regular expressions as you pointed out but going that route is way over my head.

Changes to these regular expressions would only have been required because you said you need forward slashes (which are not URL-encoded either) in (the variable parts of) your routes.

My pleasure! I would love to see your framework being used more. Explaining my use case is my way of contributing.
Regarding the initially required wildcards in routes, these are actually not needed in my case. This use case mimics the workings of Coast CMS which requires all HTML pages to be in the site root. So there are no sub directories below draft/. This let me off the hook.


Possibility of running Smarts without any graphical output?

Is it possible to make the simulator run by suppressing all graphical output and related connections necessary for that. Nodes that support GPUs and graphical outputs are limited (if at all) in HPCs, and it would be great if you can make the simulator run without a need for an explicit graphical output.

@Sriram94 thank you for the question. Yes, it is entirely possible to suppress the graphical output.
If using any of the inbuilt environments is to pass in headless=True and visdom=False.
https://github.com/huawei-noah/SMARTS/blob/feee8fd8a1f0c10ab2aaf6f12acc8c9cc0f861af/smarts/env/hiway_env.py#L70-L82
If using SMARTS directly it is possible to not render by simply not providing the envision or visdom parameters.
https://github.com/huawei-noah/SMARTS/blob/feee8fd8a1f0c10ab2aaf6f12acc8c9cc0f861af/smarts/core/smarts.py#L81-L91

@Sriram94 , I apologise I was about to close the issue but just connected what might be the problem you have. There still needs to be a display, even if a dummy one, in order to use smarts as it is now.
We have a Dockerfile that shows some of the set-up to solve the problem of a missing display:
https://github.com/huawei-noah/SMARTS/blob/feee8fd8a1f0c10ab2aaf6f12acc8c9cc0f861af/Dockerfile#L32-L33
At minimum this means: the following dependencies
apt-get install x11-apps xserver-xorg-video-dummy

And then there are a few extra steps to set up the "x-server":
https://github.com/huawei-noah/SMARTS/blob/feee8fd8a1f0c10ab2aaf6f12acc8c9cc0f861af/Dockerfile#L45-L49
And then the dummy "x-server" will need to run in the background, this following command will need to be run every time the "x-server" is taken down:
https://github.com/huawei-noah/SMARTS/blob/feee8fd8a1f0c10ab2aaf6f12acc8c9cc0f861af/Dockerfile#L67-L71

This definitely makes a lot more sense. Thanks for the clarification @Gamenot. My issue was asking if it was possible to look into a version of Smarts without this display. In the meantime I will work with the suggestions you have given me. Thanks.

PR #729 may have helped with this.  If you do not have any vehicles with camera-based sensors (that require the display for rendering their observations), you can now run Smarts without a display.  I won't close this yet though, as it hasn't yet been merged into master and released.  I note that we also would still like to remove this final dependency for camera-based sensors as well, eventually, but that will require considerably more work.

For headless Panda3D rendering, consider using ./utils/docker/Dockerfile.headless in pull request #1016 .


Could not import mongo_connector.doc_managers.neo4j_doc_manager.

Hi,
when I run the following command:
mongo-connector -m localhost:27017 -t http://localhost:7474/db/data -d neo4j_doc_manager
displays the following error:
No handlers could be found for logger "mongo_connector.util"
Traceback (most recent call last):
File "/usr/local/bin/mongo-connector", line 9, in
load_entry_point('mongo-connector==2.3', 'console_scripts', 'mongo-connector')()
File "/usr/local/lib/python2.7/dist-packages/mongo_connector-2.3-py2.7.egg/mongo_connector/util.py", line 85, in wrapped
func(_args, *_kwargs)
File "/usr/local/lib/python2.7/dist-packages/mongo_connector-2.3-py2.7.egg/mongo_connector/connector.py", line 1041, in main
conf.parse_args()
File "/usr/local/lib/python2.7/dist-packages/mongo_connector-2.3-py2.7.egg/mongo_connector/config.py", line 118, in parse_args
option, dict((k, values.get(k)) for k in option.cli_names))
File "/usr/local/lib/python2.7/dist-packages/mongo_connector-2.3-py2.7.egg/mongo_connector/connector.py", line 824, in apply_doc_managers
module = import_dm_by_name(dm['docManager'])
File "/usr/local/lib/python2.7/dist-packages/mongo_connector-2.3-py2.7.egg/mongo_connector/connector.py", line 814, in import_dm_by_name
"vailable doc managers." % full_name)
mongo_connector.errors.InvalidConfiguration: Could not import mongo_connector.doc_managers.neo4j_doc_manager. It could be that this doc manager has been moved out of this project and is maintained elsewhere. Make sure that you have the doc manager installed alongside mongo-connector. Check the README for a list of available doc managers.

This appears to be an error caused by failing to pin the py2neo dependency to a specific version. This project was written using py2neo 2.0.7 but failed to pin that version, as py2neo 3.0 is  now being pulled in a few things are breaking.
We will push an update for 3.0 soon, in the meantime you can get around this by uninstalling py2neo and installing version 2.0.7:
lyonwj@lyonwjs-MacBook-Pro-2 ~/n/mongo_demo> pip uninstall py2neo
Uninstalling py2neo-3
...
lyonwj@lyonwjs-MacBook-Pro-2 ~/n/mongo_demo> pip install py2neo==2.0.7
Collecting py2neo==2.0.7
  Downloading py2neo-2.0.7.tar.gz (251kB)
    100% |████████████████████████████████| 256kB 2.6MB/s
Installing collected packages: py2neo
  Running setup.py install for py2neo ... done
Successfully installed py2neo-2.0.7
lyonwj@lyonwjs-MacBook-Pro-2 ~/n/mongo_demo>
mongo-connector -m localhost:27017 -t http://localhost:7474/db/data -d neo4j_doc_manager
Logging to mongo-connector.log.

This appears to be an error caused by failing to pin the py2neo dependency to a specific version. This project was written using py2neo 2.0.7 but failed to pin that version, as py2neo 3.0 is  now being pulled in a few things are breaking.
We will push an update for 3.0 soon, in the meantime you can get around this by uninstalling py2neo and installing version 2.0.7:
lyonwj@lyonwjs-MacBook-Pro-2 ~/n/mongo_demo> pip uninstall py2neo
Uninstalling py2neo-3
...
lyonwj@lyonwjs-MacBook-Pro-2 ~/n/mongo_demo> pip install py2neo==2.0.7
Collecting py2neo==2.0.7
  Downloading py2neo-2.0.7.tar.gz (251kB)
    100% |████████████████████████████████| 256kB 2.6MB/s
Installing collected packages: py2neo
  Running setup.py install for py2neo ... done
Successfully installed py2neo-2.0.7
lyonwj@lyonwjs-MacBook-Pro-2 ~/n/mongo_demo>
mongo-connector -m localhost:27017 -t http://localhost:7474/db/data -d neo4j_doc_manager
Logging to mongo-connector.log.

I had the similar issue @joelmatiassilva
your solution solved for macOS
but it uninstalled
Uninstalling py2neo-4.0.0b2:

does 5.0b1 work ok ? or is it just 2.0.7 ?  I had 2.0.8 and had similar probs w py2neo

pyneo 2.0.7 is not available anymore, does any of the new versions work with neo4j_doc_manager?


Add Test option for using run-instance API rather than create-fleet API for compute Fleet

Description of changes

Making changes for using instances, region and OS dimensions for TEST_CONFIG Yaml file.
Added --force-run-instance-fleet-manager testing option for using run-instance API rather than create-fleet API for compute Fleet

Tests

Tested the changes Locally

Checklist

[ ] Make sure you are pointing to the right branch and add a label in the PR title (i.e. 2.x vs 3.x)
[ ] Check all commits' messages are clear, describing what and why vs how.
[ ] Make sure to have added unit tests or integration tests to cover the new/modified code.
[ ] Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Need to remove the 2nd commit where I have hardcoded the instance type with ARM architecture.

Closed in favour of https://github.com/aws/aws-parallelcluster/pull/5427


What is the range of pitch correlation when lowering the temperature

When synthesis, we should lower the temperature. The range of  pitch correlation (features[c, fr, 37] in test_lpcnet.py) is (-0.5, 0.5)
https://github.com/mozilla/LPCNet/blob/3a7ef33dcbade95ec08b85839b6268e35b8d3366/src/test_lpcnet.py#L91-L92

Because pitch correlation(frame_corr in src/lpcnet_enc.c) has been normalized.
https://github.com/mozilla/LPCNet/blob/3a7ef33dcbade95ec08b85839b6268e35b8d3366/src/lpcnet_enc.c#L668

But in paper , the range of pitch correlation is (0, 1)

Is there a difference between the implementation and the paper, or am I misunderstanding?

Hi, I also have this question.Have you solved it now?


Research Page Cards [React Version]

Sample Reference
Do refer to the current version on the main branch too (Except the way the pictures are placed)
The color of the buttons needs to be changed to suit the theme
The cards should be mobile responsive.
Use Animation on Scroll
We need Abstract, Paper, and Cite buttons
Add an on hover effect for the buttons
The data should be defined in a variable and dynamically inserted as done in the current research.js
Images/illustrations should be placed inside assets/images/research/

I'll do this @smaranjitghose

Any updates @aditisingh2412 ?

@smaranjitghose I'm still working on this. I'll submit a PR in few days.

Also, I wanted to ask I have to change research.html page to React JS right?

the research.html is on the master branch. You have to make a similar page for the react version on the reactjs version.


Fix llvm-cov build

Another crack at #620.

Could you remove the version bump? I do that at the same time as a release. Otherwise LGTM.

Could you remove the version bump? I do that at the same time as a release. Otherwise LGTM.

Done!


angular2-uuid.js not found (with Angular2 rc4)

I installed angular2-uuid by typing npm install angular2-uuid --start.
In my code I import uuid
import { UUID } from 'angular2-uuid';
At this point, I have no error.
But when I write

let uuid = UUID.UUID();

, I have an 404 error (see below).
Did I miss something to write in my code ?
``
(index):98 Error: Error: XHR error (404 Not Found) loading http://localhost:5555/node_modules/angular2-uuid.js
at XMLHttpRequest.wrapFn [as _onreadystatechange] (http://localhost:5555/node_modules/zone.js/dist/zone.js?1467495843717:769:30)
at ZoneDelegate.invokeTask (http://localhost:5555/node_modules/zone.js/dist/zone.js?1467495843717:356:38)
at Zone.runTask (http://localhost:5555/node_modules/zone.js/dist/zone.js?1467495843717:256:48)
at XMLHttpRequest.ZoneTask.invoke (http://localhost:5555/node_modules/zone.js/dist/zone.js?1467495843717:423:34)
Error loading http://localhost:5555/node_modules/angular2-uuid.js as "angular2-uuid" from http://localhost:5555/app/[...]/dvls-security-groups.component.js

Check your build tooling and linking. Your issue is not related to this project.


Easier access to Response and in particular to ResponseBody.string()

We are using okHttps for microservices implementation. We send requests and get back simple responses from other services. In 100% of our use-cases and probably in the whole company in 95% of all use-cases, we receive short response bodies, which can be stored without any problems in memory.
From that perspective, currently, access to Response and in particular to ResponseBody is really uncomfortable. A response has to be closed and released, so I have to pass response in a lambda to some component which can handle automatically closing Response to avoid doing it in every function where a response is collected. Also, I found the behavior of ResponseBody.string() to be very strange. It returns value only first time, but then just empty string. But if the first time response body is loaded, then why not to cache it and return every time it is requested?
I think that it will be better to not require to close the whole response. It should be enough to close ResponseBody and moreover it can be done internally in the Response object. Getting the string() from ResponseBody should only throw a runtime exception, during unsuccessful dereference of the stream. In all other cases, it should just return the cached value of the response body. Handling of closing the stream should be done internally in Response object depending on usage scenario.
I would like to add that overall I really like the design: request (query) object --> processing --> response object. IMHO that's the correct way of doing that and that's why we are using okHttp instead of standard Spring functionality. The only missing point for me is what I have explained above.

We've modeled responses to be one-shot. We expect you to stream the response, decode it from JSON or another format, and use the result as a model object. Keeping the response body around looks like a memory leak to applications that don't use it.
I think what you probably want instead of a friendlier Response API is an entire abstraction on top of OkHttp like Retrofit. OkHttp wants to do the low level HTTP stuff only and generally favors efficiency over ergonomics when the two are in conflict.

I really appreciate the overall design. The only point which needs attention is the response object. Because of that, I don't want to go for anything more complex, especially not for high-level frameworks.
Few important points supporting this view:

immutability of most fields in Response doesn't matter if you have a single field which is not immutable. You can not consider Response as an immutable object
you cannot pass Response up the stack e.g. in Exception
probably about 95% of usages of Response in microservices is just reading the whole body to the memory
handling of exceptions when reading the body of the response complicates significantly logic behind the processing of the response.

I think it is reasonable for a client to decide which response it wants to get as a result: value-based or stream based. So one possible way to go is to create different modes to get a response and allow the client to decide which one is desirable.
In our microservice, we have to wrap okHttp response into our own response object, which has already resolved stringBody. That way we can pass Response to many functions which can process a body without worrying that in some point it is null.
But this solution is still far from good:

we are using okHttp.Request as it is, but we are returning our own Response object. Not very nice
I would like to keep the structure of the okHttp.Response in the most part - it has nice builders. But reimplementing it in our own object is a significant effort.

I hope I explained my use-case at least a bit. If you need more information, do not hesitate to ask.

If you want, create a class like InMemoryResponseBody that can be constructed from another ResponseBody.
Then use an application interceptor to replace the streaming one with the in-memory one.

No action to take here.


Fix Tabs groupId typo + other typos

Description
Mainly to a fix typo in the Tabs groupId (was incorrectly groupid) attribute of /how-to-guides/advanced-user-guides/monitoring-alerting-guides/enable-monitoring.md.
Also fixed a couple other typos:
Github -> GitHub
Dockerhub and DockerHub -> Docker Hub

Thanks Billy, approved!


[Feature] Configuring Etherum providers using multiple RPC endpoints(httpFallback or quorum)

Description
We have been operating several graph nodes and facing get genesis failed failure frequently when the RPC endpoint is unhealthy or the connection is not good(could be regional issue?).
I want to configure the providers with multiple rcp endpoints as httpfallback mode in which the first rpc endpoint is bad, then fallback to the second one. But I cannot find this kind of feature support mentioning in the doc https://github.com/graphprotocol/graph-node/blob/master/docs/config.md#configuring-ethereum-providers.
Is this built-in function already and just doc not updated?
Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.
No response
Some information to help us out

[ ] Tick this box if you plan on implementing this feature yourself.
[X] I have searched the issue tracker to make sure this issue is not a duplicate.

hey @josedev-union you can configure multiple RPC endpoints, but is the issue that you are looking for specific fallback behaviour?

hey @josedev-union you can configure multiple RPC endpoints, but is the issue that you are looking for specific fallback behaviour?

@azf20 yeah, i think i can configure multiple RPC endpoints as chain provider url but only one endpoint is used for each subgraph or even for provider health check.

I'm not sure why we should allow multiple RPC endpoints.  User should send queries to proxyd and proxyd can be configured with multiple endpoints.
https://github.com/ethereum-optimism/optimism/tree/4be8847aacaa35cab2a63b274b79567ff6240051/proxyd

👍 agree with @matthewdarwin that it makes sense to leverage dedicated proxy tooling here. Closing for now, re-open if you have a different view @josedev-union


Which json value tells me whether the battle was victory or defeat?

The way to determine the winning team is as follows:

In the "common" response there is a parameter called "winner_team".
In the "battle_performance" response there is a parameter called "team".

So if "team" = 1 and "winner_team" = 2 then the battle was lost.
If "team" = 1 and "winner_team" = 1 then the battle was won.

Thanks alot for quick response!


How to create a dev environment to run tpch benchmarks?

I'd like to make a development environment to run TPCH benchmarks locally on my macbook. Is there a set of environment files I should apply?

Pinging @crusaderky because I'm guessing that he has a good handle on the various environment files here (but I could be wrong)

@milesgranger also did some work here recently. I think we should put this into the readme

This ought to be what you're after:
mamba create -n tmp python=3.9
mamba activate tmp
mamba env update -f ci/environment.yml
pip-compile ci/requirements-2tpch-non-dask.in
pip install -r ci/requirements-2tpch-non-dask.txt

I'll leave this open as a reminder to add to the README.

It's already in the README; not sure if there's anything actionable here?
https://github.com/coiled/benchmarks/blob/main/tests/tpch/README.md#setup


Is there a graphical depiction of the model being used/trained here?

I would like to see what kind of model clstm uses but it seems I can't to find the structure of it anywhere here.
Any tips/links would be appreciated.

clstm is largely obsolete these days, superseded by engines based on frameworks like tensorflow and torch. Apart from digging through the code to and perusing @tmbdev's publications, you won't find much documentation I'm afraid.

clstm is basically the same as ocropy, but implemented in c++ instead of python.
So the answer is the same:
https://github.com/tmbdev/ocropy/issues/327

Thanks
On Mon, Jul 29, 2019 at 5:27 PM Amit D<EMAIL_ADDRESS>wrote:

clstm is basically the same as ocropy, but implemented in c++ instead of
python.
So the answer is the same:
tmbdev/ocropy#327 https://github.com/tmbdev/ocropy/issues/327
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tmbdev/clstm/issues/150?email_source=notifications&email_token=AAB4LMXOYDJOHN2PQ4HUTRTQB4D7PA5CNFSM4H3QH7C2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3BCLLA#issuecomment-516040108,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB4LMRB73JNDJY65TJLZCLQB4D7PANCNFSM4H3QH7CQ
.

--
Kind Regards,
Tadas Šubonis

... superseded by engines based on frameworks like tensorflow and torch.

https://github.com/tmbdev/ocropy/wiki/Related-Projects


validate should throw an error if a replace operation is called without an value

Describe the bug
In my unit-test suite I test my scim service against a various number of invalid patch requests. I just tested my test suite with this node package and encountered that the following call is not rejected even though the following body is not valid IMO.
To Reproduce
Steps to reproduce the behavior:
Sample request:
{
  "Operations": [
    {
      "op": "replace",
      "path": "displayName"
    }
  ],
  "schemas": [
    "urn:ietf:params:scim:api:messages:2.0:PatchOp"
  ]
}

expected
the function patchBodyValidation should throw an error.

@soccermax thanks for opening this issue.
I have not much time to work on it for now but if you want to open a pull request to fix it, it would be awesome.
I will get back to it as soon as I have some free time.

Closing the issue for the lack of answer.


Update to embedded-hal v1.0

Embedded-hal v1.0 has now officially released :tada: (migration guide blog-post)
pca9535 has already updated to rc2 but rc3 made some changes to the IO traits which might need some general adjustments of the pca9535 crate architecture. Also the general architecture of the crate needs to undergo a check to make sure the crate integrates well into embedded-hal 1.0. One thing that comes to mind is that things like shared-bus are now discouraged to use (looks like only for SPI bus though) so I need to make sure pca9535 works well with the new approaches.

Currently the hil tests on cached expander do not pass due to golemparts/rppal#137. Gonna wait until this is resolved and all tests pass.