truncate_long_and_double default to true

Description
Sets the default value for truncate_long_and_double to true. Int64 shows up frequently in transformer models. These should compile out of the box with minimal configuration
Fixes # (issue)
Type of change
Please delete options that are not relevant and/or add your own.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

Checklist:

[ ] My code follows the style guidelines of this project (You can use the linters)
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas and hacks
[ ] I have made corresponding changes to the documentation
[ ] I have added tests to verify my fix or my feature
[ ] New and existing unit tests pass locally with my changes
[ ] I have added the relevant labels to my PR in so that relevant reviewers are notified

I want this opt in because otherwise we silently change numerics. It makes it much harder to debug / understand why you may be seeing different outputs between pytorch and tensorrt.


overlapping firewall rules kill vagrant

If an overlapping firewall rule is created vagrant fails with an error. The machine is created but this should be handled cleanly

This blocks us from having concurrent cookbook jobs over the same public IP


[BUG] Unable to get a working demo

First of all, great project! Seriously cool.
I believe this is just a bit of lagging documentation, but I'm unable to find a set of versions for terranova/terraform/providers that work happily together. The closest I have found is:
github.com/johandry/terranova v0.0.3 (I also tried 0.0.2, they run ito the same bug)
github.com/hashicorp/terraform v0.12.17 (as specified at the top of the readme, expecting terranova 0.0.2)
github.com/terraform-providers/terraform-provider-aws v1.60.1-0.20191003145700-f8707a46c6ec  (as specified in readme, compatible providers section)
Which seems to almost work but results in this error:
$ go get
# github.com/terraform-providers/terraform-provider-aws/aws
../../go/pkg/mod/github.com/terraform-providers/terraform-provider-aws@v1.60.1-0.20191003145700-f8707a46c6ec/aws/resource_aws_datasync_task.go:102:9: undefined: datasync.PosixPermissionsBestEffort

I've tried a bunch of combinations, this seems to be the closest to functions. Do you happen to have a configuration that is currently functional for the aws provider?  Thanks!

Hi, thanks for the feedback, it's nice to know terranova is been used :)
I'm using terranova with KubeKit on production (here is the go.mod) and we use:
require (
  ...
  github.com/aws/aws-sdk-go v1.25.4
  github.com/kubernetes-sigs/aws-iam-authenticator v0.3.1-0.20181019024009-82544ec86140
  github.com/terraform-providers/terraform-provider-aws v1.60.1-0.20191003145700-f8707a46c6ec
  ...
)

There are also some examples in the terranova-examples repository here all of them are using AWS however they are very simple examples.
May I see the go.mod file that you are using?
It may be related to version of github.com/aws/aws-sdk-go/service/datasync you are importing/requiring in the go.mod file. If you are using a version for github.com/aws/aws-sdk-go higher than v1.25.4 then try to use v1.25.4.
require github.com/aws/aws-sdk-go v1.25.4

If you need higher than that, the last version where datasync.PosixPermissionsBestEffort is defined in aws-sdk-go/service/datasync/api.go is v1.25.39.
So, unfortunately the latest version of github.com/aws/aws-sdk-go you can use could be v1.25.39.
This bug is related to the feature in issue #26. Once this feature is done you can use any version of AWS you want.

Related to:

Issue #26

Excellent, thanks!  My issues was definitely the aws-sdk-go version - simple demo is working fine now!   Any chance terranova can work with alternate backends, or is that a feature not yet on the radar?

I haven't need it but all features request are welcome.
I'll check about it and add it as a feature :)
Thanks for all the feedback and I'll work on the documentation too.


차태훈 학생의 자기소개 변경

음 이건 제가 직접 해드리죠. 박사과정생님들은 바쁘십니다.

I'm Taehun Cha, a Ph.D. candidate in AIML. While I was in graduate school, I majored in Sociology, Cultural study, and Applied Statistics. Though I currently do not utilize most of the knowledge I learned at that time, I learned how to think, write, and communicate with people from totally different backgrounds.
After graduation, I needed to find a way to manage my livelihood. So I learned financial engineering and was certificated as an International Financial Risk Manager. Though I currently do not utilize most of the knowledge I learned at that time (again), my curiosity about modern language models ignited at that time. Also, I'm still interested in AI applications in the financial domain.
Now I'm learning mathematics to rigorously explain the several common behaviors of LLMs. Though digging LLMs from a mathematical aspect is yet immature and challenging, I believe we, humans, need to understand how and why this works clearly, before it is adopted too deeply into our lives.
참고로 학사 졸업은 2019년, 석사 졸업은 2022년입니다.

Resolved by #11


Bypass warning about detached head

This avoids log spam like this:
⚠  aarch64   | Cloning into '/tmp/tmp.Dvzsqj'...
⚠  aarch64   | Note: switching to 'ec85d900b413d3d9d6f60cece3fb5bc665275087'.
⚠  aarch64   |
⚠  aarch64   | You are in 'detached HEAD' state. You can look around, make experimental
⚠  aarch64   | changes and commit them, and you can discard any commits you make in this
⚠  aarch64   | state without impacting any branches by switching back to a branch.
⚠  aarch64   |
⚠  aarch64   | If you want to create a new branch to retain commits you create, you may
⚠  aarch64   | do so (now or later) by using -c with the switch command. Example:
⚠  aarch64   |
⚠  aarch64   |   git switch -c <new-branch-name>
⚠  aarch64   |
⚠  aarch64   | Or undo this operation with:
⚠  aarch64   |
⚠  aarch64   |   git switch -
⚠  aarch64   |
⚠  aarch64   | Turn off this advice by setting config variable advice.detachedHead to false
⚠  aarch64   |
Updating files: 100% (48253/48253), done./48253)

Not in this PR, but there's a ton of other spam there that we may at some point reduce as well. Mainly when it's copying the . to the container (I think, or at least that's what it looks like to me).

Looks like the failure is not a flake?
2023/12/27 16:26:45 ERROR: failed to build package. the build environment has been preserved:
ℹ  x86_64    |   workspace dir: /tmp/melange-workspace-3112014763
ℹ  x86_64    |   guest dir: /tmp/melange-guest-2160339963
Error: failed to build package: unable to build guest: unable to generate image: installing apk packages: installing packages: installing gobject-introspection: unable to install files for pkg gobject-introspection: unable to install file over existing one, different contents: usr/bin/gapplication
2023/12/27 16:26:45 error during command execution: failed to build package: unable to build guest: unable to generate image: installing apk packages: installing packages: installing gobject-introspection: unable to install files for pkg gobject-introspection: unable to install file over existing one, different contents: usr/bin/gapplication


[Security]: Vulnerability awaits to be verified

Describe the bug
Our team (School of Cyber Science and Technology, Shandong University)have found the a potential issue in the current version of nanomq,it may cause heap-use-after-free when it handles the publish messages
Expected behavior
We use ASAN to compile the target server, and when we send a large number of malformed data packets to it, it may crash and output the following information ：

the Call stack information is：

Actual Behavior
Describe what occurred.
To Reproduce
we will provide the POC below to the developer for validation:
heap-use-after-free-poc.zip
** Environment Details **

NanoMQ version master branch version commit #8c54cd7
Operating system and version Ubuntu 20.04
Compiler and language used  gcc 9.4.0 clang 10.0.0
testing scenario

start nanomq with ./nanomq start
Send the packet：nc <IP_ADDRESS> 1883 < heap-use-after-free-poc（Repeat multiple times）
util cause NanoMQ crashes
Additional context
To trigger the issue, it is necessary to continuously replay the poc multiple times until nanomq crashes,it may need 2 - 15 times

Unable to reproduce this issue either, plz try with most updated nanonng branch

Thank you for your timely reply. We replayed the raw we provided on the previous branch again, and it can still trigger stably. We will try the new updated nanonng branch!

This issue is pretty interesting, it helps me identify a rarely seen data racing

This issue is pretty interesting, it helps me identify a rarely seen data racing

I suspect this vulnerability is triggered by multithreading because POC replicates are not stable.
Similarly, I offer a completely different new UAF vulnerability in nmq_mqtt.c:404:

NanoMQ version：master branch version commit #0485998, NanoNNG Git Commit#bb6f17f (all newest)
running server:  ./nanomq start
Send the packet：nc <IP_ADDRESS> 1883 < poc.raw（Repeat multiple times, ） until cause NanoMQ crashes

It is worth mentioning that even with the same POC, the location of the vulnerability may change, so it is doubtful that this could be related to a multithreaded implementation
This poc.zip may trigger the uaf vulnerability discovered above (@ZuoYuanP),  or it may trigger the new uaf vulnerability situation below, so try replaying the poc as much as you can until the server crashes.

anothe_uaf_asan_log.txt
poc(new uaf).zip

Similar to the reply above（NanoMQ master commit #0485998, NanoNNG #bb6f17f, the following raw file can trigger one new uaf in mqtt_codec.c:3919.
This poc is also unstable and likely to trigger as @ZuoYuanP mentioned , with a certain probability of triggering vulnerabilities in the following code locations, and you need to replay it multiple times until NanoMQ crashes.

uaf_asan_log.txt
uaf in mqtt_codec.c_3919.zip

Another new use-after-free in sub_handler.c:323
I also found a new use-after-free vulnerability in sub_handler.c:323, which I analyzed and found it could be triggered steadily with the help of gdb.
Environment: NanoMQ master commit #0485998, NanoNNG #bb6f17f
To Reproduce
# run gdb
gdb nanomq
b /home/songxiangpu/Documents/nanomq_newest/nanomq/sub_handler.c:323
set args start
run
# replay poc
nc <IP_ADDRESS> 1883 < ./poc.raw
# skip the breakpoint until NanoMQ crashes
c
c
c
...

UAF-sub_handler.c-asan.txt
UAF-sub_handler.c-poc.zip

Describe the bug Our team (School of Cyber Science and Technology, Shandong University)have found the a potential issue in the current version of nanomq,it may cause heap-use-after-free when it handles the publish messages
Expected behavior We use ASAN to compile the target server, and when we send a large number of malformed data packets to it, it may crash and output the following information ：  the Call stack information is：
Actual Behavior Describe what occurred.
To Reproduce we will provide the POC below to the developer for validation: heap-use-after-free-poc.zip
** Environment Details **

NanoMQ version master branch version commit #8c54cd7
Operating system and version Ubuntu 20.04
Compiler and language used  gcc 9.4.0 clang 10.0.0
testing scenario

start nanomq with ./nanomq start Send the packet：nc <IP_ADDRESS> 1883 < heap-use-after-free-poc（Repeat multiple times） util cause NanoMQ crashes
Additional context To trigger the issue, it is necessary to continuously replay the poc multiple times until nanomq crashes,it may need 2 - 15 times

after #1187 , there is only a bizarre memleak problem remaining.
The poc data contains multiple issues, including an illegal protocol name packet.
But memleak is gone once I refuse this illegal packet, it is worth tracking so I keep a log here.
==1909241==ERROR: LeakSanitizer: detected memory leaks
``
Direct leak of 168 byte(s) in 1 object(s) allocated from:
#0 0x7f75e84b4a37 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154
#1 0x56372d50aa58 in nni_zalloc /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/platform/posix/posix_alloc.c:26
#2 0x56372d4f4822 in nni_msg_alloc /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/core/message.c:387
#3 0x56372d87071d in tcptran_pipe_recv_cb /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/sp/transport/mqtt/broker_tcp.c:686
#4 0x56372d504e52 in nni_taskq_thread /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/core/taskq.c:50
#5 0x56372d50620a in nni_thr_wrap /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/core/thread.c:94
#6 0x56372d50f3bf in nni_plat_thr_main /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/platform/posix/posix_thread.c:266
#7 0x7f75e7c94b42 in start_thread nptl/pthread_create.c:442
Indirect leak of 125 byte(s) in 1 object(s) allocated from:
#0 0x7f75e84b4a37 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154
#1 0x56372d50aa58 in nni_zalloc /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/platform/posix/posix_alloc.c:26
#2 0x56372d4f35fd in nni_chunk_grow /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/core/message.c:158
#3 0x56372d4f4872 in nni_msg_alloc /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/core/message.c:397
#4 0x56372d87071d in tcptran_pipe_recv_cb /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/sp/transport/mqtt/broker_tcp.c:686
#5 0x56372d504e52 in nni_taskq_thread /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/core/taskq.c:50
#6 0x56372d50620a in nni_thr_wrap /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/core/thread.c:94
#7 0x56372d50f3bf in nni_plat_thr_main /home/jaylin/Projects/EdgeComputing/nanomq/nng/src/platform/posix/posix_thread.c:266
#8 0x7f75e7c94b42 in start_thread nptl/pthread_create.c:442
SUMMARY: AddressSanitizer: 293 byte(s) leaked in 2 allocation(s).
``

The following issues are basically same problem.
will be fixed with one PR

thanks for finding issues btw

The following issues are basically same problem. will be fixed with one PR

I think the above issue may not be caused by the same problem, as the use-after-free vulnerability can still be triggered stably triggered in the newest branch.
Environment

NanoMQ：Git Commit #69224a88554e7187f6d303a23ed825a7875b8a7d
NNG Git Commit#df24367b201a7429a4c3daab4477c424113bda8b

sub_handler_poc.zip

They all caused by parallel processing and replacing the retain msg, You can prove me wrong by submitting a PR, that would be wonderfu!
BTW, told you to move the head, or you can wait for us to publish a new version in next month

They all caused by parallel processing and replacing the retain msg, You can prove me wrong by submitting a PR, that would be wonderfu!
BTW, told you to move the head, or you can wait for us to publish a new version in next month

Nervermind, I agree that it is the competition of data or conditions that leads to these vulnerabilities.
I then just did a regression test on the latest branch and found that there were omissions, so mention it again.

All bugs discovered by this issue/ticket have been fixed. I am gonna closed this


Redirect login/register routes when already signed in

This PR adds functionality that will automatically redirect signed-in users going to /login or register to the home page /.
To make this work, both routes are wrapped into (unauth) named route and inherit a layout which will check the auth state on the server and maybe performs the redirect.
Feel free to reject/accept/modify, @jianyuan 😊

This has been integrated into https://github.com/jianyuan/pocketbase-sveltekit-auth/commit/087d4f3724d08fdedd5d95485b6be8f6cca1d306. Thanks!


power rename doesn't appear in context menu

Microsoft PowerToys version
0.69.1
Installation method
Scoop
Running as admin
Yes
Area(s) with issue?
PowerRename
Steps to reproduce
Click right in selected file in the explorer then the power rename icon should appear
PowerToysReport_2023-05-08-08-06-56.zip
✔ Expected Behavior
Click right in selected file in the explorer then the power rename icon should appear
❌ Actual Behavior
Nothing
Other Software
No response

/dup #27622


Adding instructions to run cluster api tilt environment

This PR adds step-by-step documents to set up Kind cluster and use Tilt for Cluster API development and testing.

@jan-est can you make this PR towards the already existing CAPI-dev folder as that folder which I created earlier seems to be obsolete now according to your tests. So I don't see any point of keeping old information.

@kashifest if it is OK to you I will delete the old CAPI-dev folder with my PR?

@kashifest if it is OK to you I will delete the old CAPI-dev folder with my PR?

Sure. If nothing is needed from that folder , go ahead and delete it.

looks ok to me


Feature Charts: Add Longhorn 1.4.0 Chart in 2.7.0

Longhorn has an upcoming release 1.4.0 which will be released in late December so we need to add this new release in the feature charts along with Rancher 2.7.0. We will probably need to make this OOB.
Add 1.4.0 LH chart in feature chart 2.7.0 - Cluster Manager/Rancher Marketplace
Cc: @cchien816 @innobead @khushboo-rancher @MKlimuszka @prachidamle @yangchiu @yasker
Related issue for 2.6.9: https://github.com/rancher/rancher/issues/39749

Closing as verified and completed.


Response is Null when Navigating to a PDF

When navigating to a PDF in headless mode the Response is Null. What Im trying to do is download the loaded pdf page and save it locally. Bellow is my code.. Thanks.
const puppeteer = require('puppeteer');

(async () => {
const browser = await puppeteer.launch({headless:true});
const page = await browser.newPage();
const response = await page.goto('http://www.africau.edu/images/default/sample.pdf', {waitUntil: 'networkidle'});
console.log(response);
browser.close();
})();

hi, is there any solution to achieve this using puppeteer? The pdf Im trying to download is build on the fly, so its quite difficult to use Http Request and pass all the needed cookies or parameter to download the pdf. I try to catch it using the page request and response but still no luck on it. please I really need help on this. Thanks a lot!

@floydtagle this works fine in non-headless mode, so looks like a bug in headless. I filed upstream bug: crbug.com/761295

@aslushnikov Thank you so much, but my deployment is on linux server so I really need this functionality.. no choice I need to wait until this bug is fix.. Thank you so much again..

Hi @aslushnikov  using non-headless do you have any suggestion or idea on how to save locally the pdf? Thanks a lot.

@floydtagle that's under development; see #299

@aslushnikov Thanks!
about this.., does it mean, that you cannot navigate to pdf in headless chrome? or what? Thanks!

@floydtagle yes, chrome headless doesn't know how to navigate to PDFs. You can use pdf.js to render PDF if there's a need to.

I might have the working solution.. I've spent half a day understanding what was going on.
My idea was to use the Fetch API, and then use the arrayBuffer or blob response type in order to send the result back to an exposed function, which in turn would write the data to a file.
But obviously, the page.exposeFunction() method serializes the exposed function parameters using JSON.stringify, meaning we cannot pass data such as ArrayBuffers or Blobs (these type would be destroyed).
Using the Fetch API DOMString response type (string) did not work either, for some reason the string was somehow altered (its encoding I think) when passed into the exposed function.
Eventually, I decided to fetch the PDF data as an ArrayBuffer, convert the ArrayBuffer to a string in UTF-16 encoding, pass that UTF-16 string into the exposed function, and then compute the reverse method on the other side: the exposed function convert the UTF-16 string back to an ArrayBuffer, which can be used to write the data in a file on the user file system.
Some bits of my code here:
`page.exposeFunction("writeABString", async (strbuf, targetFile) => {
    var str2ab = function _str2ab(str) { // Convert a UTF-16 String to an ArrayBuffer

        var buf = new ArrayBuffer(str.length*2); // 2 bytes for each char
        var bufView = new Uint16Array(buf);

        for (var i=0, strLen=str.length; i < strLen; i++) {
          bufView[i] = str.charCodeAt(i);
        }
        return buf;
    }

    console.log("In '_writeABString_' function...");

    return new Promise((resolve, reject) => {

        // Convert the ArrayBuffer string back to an ArrayBufffer, which in turn is converted to a Buffer
        let buf = Buffer.from(str2ab(strbuf));

        // Try saving the file.
        fs.writeFile(targetFile, buf, (err, text) => {
            if(err) reject(err);
            else resolve(targetFile);
        });
    });
});`

And then, from within an evaluate call, you would have the following :
`page.evaluate( async () => {
function ab2str(buf) { // Convert an ArrayBuffer to an UTF-16 String
    return String.fromCharCode.apply(null, new Uint16Array(buf));
}

let geturl = "https://whateverurl.example.com";
return fetch(geturl, {
    credentials: 'same-origin', // usefull when we are logged into a website and want to send cookies
    responseType: 'arraybuffer', // get response as an ArrayBuffer
})
.then(response => response.arrayBuffer())
.then( arrayBuffer => {
    return window._writeABString_(ab2str(arrayBuffer), '/tmp/downloadtest.pdf');
})
.catch(function (error) {
    console.log('Request failed: ', error);
}); `

@Xavatar this worked nicely, thanks! Please edit your comment above because the page.evaluate() line is missing. (see your comment in this thread)
Also, I had to start Chrome with --disable-web-security to disable CORS and be able to fetch from other domains (sometimes necessary).

@gombosg : Thanks for pointing this out, I've fixed it, and also added JS highlighting!


Feature - Improve enable_cors.sh script

Now it is possible to enable and disable CORS using the enable_cors.sh script

This script is being improved on another PR


Result interpretation

Hello, I'm working on DANN algorithm and I'm wondering how to interpret my print results from your repo ? I got this after 100 epochs:
tgt -> Avg Loss = 0.019690, Avg Accuracy = 77.73%, 7761.0/9984, Avg Domain Accuracy = 58.553686%
src -> Avg Loss = 0.000233, Avg Accuracy = 99.56%, 59704.0/59968, Avg Domain Accuracy = 68.128002%
``

please inspect the source code for more info.


[GCI] Fixed About Page Layout

Fixes #542

Coverage remained the same at 82.507% when pulling 13060d62cb9532cf25b953ab17b34c294a5d6632 on MrBartusek:about-page-layout#542 into 6569232a75d650e5123363c7f51280129df87f9b on CircuitVerse:master.

@tachyons @ankitkataria
I have approved the GCI task for this.
Please review the pr.

PR to stories/new_ux branch please

@MrBartusek please do the needful.

@tachyons @aayush-05 changed base branch to stories/new_ux


Moving download link for SSMS to more formal text

Markdown headers should not be used as reference/hyperlinks to other content. Moving the link for downloading SSMS to a more formal here as all users are familiar with seeing.
Fixes #3431
Fixes #3469

@wsmelton : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Verified the update.
@wsmelton Thanks for submitting this update.


fix(deps): Update dependencies to k8s 0.17.0

PLEASE DO NOT MERGE, need test locally on k8s

Tested locally on minikube 1.16.0, applied some of examples, no problem found

:tada: This PR is included in version 0.4.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Documentation: Usage with React-Router and Mobx

w1zeman1p helped me figure this out in the irc developer support channel. I am providing the info here so it can be verified and potentially incorporated into the documentation.
In order to use with React Router and Mobx:

Route(s) which wish to use react-stripe-elements must be wrapped with StripeProvider, as normal. AsyncStripeProvider will work as well.
The route(s) where react-stripe-elements will be used have to be wrapped in Elements like so:

<Elements>
  <Route path='/billing/payment-method' exact component={PaymentMethod} />
</Elements>

The "Page Component" (eg, PaymentMethod in above example) has to use injectStripe (whether as decorator or middleware like so:

as decorator:
@inject('store') @observer @injectStripe class PaymentMethod extends Component {}

NOTE: the order is important, it has to come after @inject and @observer or it won't work.
as middleware:
class PaymentMethod extends Component {};
export default injectStripe( observer( injectStore( 'store', PaymentMethod )));

version info:
mobx: 5.15.0
mobx-react: 6.1.4
react-router: 5.1.2

Thank you for compiling this information! As of now, this is more specific than we intend to include in this repository's documentation. While I think it is valuable to have this written down, it's not something we want to include in the main docs right now.
This would be well suited for a blog post or article though!

@mbarrett-stripe doesn't make much sense, because you're including information about redux and redux-connect in your documentation, but whatever you say hombre.


video still playing after clicking on previous story

fixed after adding _videoController!.pause(); in onprevious  function

Yes the video will still plays if you tap previous and the current story item is first, functionality of closing the story if the current story item is first will be added in the next version.

Bro why do not add all fields needed in storyitem , like caption , like date , i already updated it locally
To avoid changing the state of current index , but it perfect bro thank you
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Muhammad Adnan @.>
Sent: Sunday, June 4, 2023 12:52:59 AM
To: AdnanKhan45/flutter-story-view @.>
Cc: samih damaj @.>; Author @.>
Subject: Re: [AdnanKhan45/flutter-story-view] video still playing after clicking on previous story (Issue #1)
Yes the video will still plays if you tap previous and the current story item is first, functionality of closing the story if the current story item is first will be added in the next version.
—
Reply to this email directly, view it on GitHubhttps://github.com/AdnanKhan45/flutter-story-view/issues/1#issuecomment-1575214569, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASTKYTY3UMAOHEB4OAPG4GLXJOW3XANCNFSM6AAAAAAYWTLKB4.
You are receiving this because you authored the thread.Message ID: @.***>

It like real WhatsApp the caption just shows up only on first story and the date uploaded is same for all of the uploaded stories that is why it's not included in the StoryItem. But, we will improve it by adding more features and adding the capabilites that you suggest Thanks you for your interest in the package :)


alias for add and createAddStream.

Currently calling ipfs.add and ipfs.createAddStream will fail since the alias isn't picked up until after the ipfs.files command is called.
Not sure if this is the best approach but this will allow people to use add with or without files until the namespace collision is solved.
This was referenced in issue #301
@noffle could you check this and see if there could be any issues aliasing this way instead of how you had it.

awesome @nginnever, several people reported this, thank you for fixing it! :)


Links proposal (updated)

The previous PR was updated, and the comments got all jacked up.  So here's a new PR, the old one has been closed but you can see comments there in all their glory.

To support HAL-style linking, as suggested in #688, I propose the following:

A mechanism for design-time, static links between responses and operations to make operations on responses visible to consumers
A reusable linking structure to allow link definitions to be DRY
A mechasim for parameterized link traversal to avoid server-side computation of links through reuse of existing, OAS-defined operations

Additional considerations:

This is not intended to be a run time linking solution.  This solution does not require users to redesign their runtime API.  It may be able to represent the intent of runtime HAL-style links in responses.  It does not intend to represent dynamically generated, arbitrary links.
A clear separation of concerns, between payloads and operations.  Therefore no operation data shall be tied to payload schemas.

Spec changes

Introduction of a Link Object to represent a single link
Addition of a  links object in the Response Object to define what links are available from a specific operation
Addition of a links section in the Components Object to allow reuse across operations
Introduction of a Link Parameters Object to represent parameters to build a link from
A mechanism for reading values from response payloads and using them for client-side link computation

approved by @OAI/tdc

I was approaching this PR with some hope that it could be used to support hypermedia types being represented in OAS, but I see now that there's a requirement for the links to be "static."  This requirement alone breaks the coupling semantics for Web Linking, on which (nearly?) all the hypermedia types depend.
And that's okay if that's not the supported use case for this feature.  But it leaves me a bit bewildered.  Can someone help by defining use cases or existing APIs that could benefit from this feature in its current form?  It seems like this introduces a lot of hopping around between references to grok what's going on.  What are the intended benefits?  Maybe it's obvious to most people.  Hopefully, it is.  But right now, I'm in the dark.
Thanks.

@kevinswiber consider reading the comments in the previous (mangled) PR and the corresponding issues for the rationale


Add user side app and DM functionality

Add the ability to use the bot as a user side app, for support with some current as well as upcoming commands. Also add DM functionality, similar to a chat bot but more info oriented rather than chat

do you mean user-side app as in a control panel or something? or like the discord add to user feature

I don't know how that would contribute to a moderation bot tbh, unless you mean like a dashboard
or go in the complete opposite direction and hop on the AI bandwagon

I don't know how that would contribute to a moderation bot tbh, unless you mean like a dashboard
or go in the complete opposite direction and hop on the AI bandwagon

I was thinking using it as a way to check statuses of certain things, like banned members, settings, etc., rather than having it as a slash command that needs to be ran in a server

oh, makes sense..
would it be like a bot inside the discord client or a third-party dashboard?

oh, makes sense..
would it be like a bot inside the discord client or a third-party dashboard?

Either or, it would be easier to do it inside the client I presume

thru discord I'm assuming

thru discord I'm assuming

Yes, like I said, inside the client

ohh, yeah that makes a bit more sense...
I don't see a good reason to make it a user-side app if one can do the same thing through the original server. I don't know how these discord apps work, so I might be missing something.


add leader-path-prefix flag

Signed-off-by: chenyunfei<EMAIL_ADDRESS>#1037
add new flag --leader-path-prefix to add prefix to leader-election-path.

empty by default, leader election will use docker/swarm/leader as before

if set --leader-path-prefix="/mycluster", will use /mycluster/docker/swarm/leader

Woops - so I opened #1048 as well.
The difference is that in this one it's configurable, on the other one it's based on the discovery prefix (so they are shared).
Thoughts?

I agree with your thought. and also prefer to use the same prefix.
but considering that there maybe other users don't want to share the prefix,  I add a new flag.

@aluzzardi I'd like to be able not to share the same key space for both mechanisms, I use my [etcd/consul/zookeeper] cluster specifically for Swarm (not sharing it with any other service).
With the same key space, someone can mistakenly wipe out the entire cluster role state (leader/follower, nodes inside the cluster) because you can still access and manage the store independently from Swarm. This is a worst case scenario but this can happen and result in an interruption of service.
In my case I'd prefer to have this configurable even though this is one more flag to set ;)

If we do that, then we'll have to add a flag for every single file we write out to consul/etcd/zookeeper

Fixed by #1048
@aluzzardi I first merged the intended behavior as there seems to be a consensus on using the same prefix for both.
@cloudfly Thank you for the contribution, we can re-open this one later if we improve the UI around the configuration of the store/discovery.


DependencyContainer doesnot apply the conditions on displaying action modal

Iwrtie this codes in a action class
public function fields(NovaRequest $request)
{
return [
Select::make(__('Status'), 'insurance_policy_status')
->options([
'no_insurance' => __('No Request Insurance'),
'in_progress' => __('In Progress Insurance'),
'rejected' => __('Rejected Insurance'),
'done' => ('Done Insurance'),
]),
DependencyContainer::make([
Image::make(('Insurance Image'), 'image')
->path('images/loads-insurance'),
])->nullable()->dependsOnNotIn('insurance_policy_status', ['no_insurance','in_progress','rejected']),
];
}
But when It shows modal, the image field is shown. It must doesnot show on modal opening

The ''تصویر بیمه نامه" field is the image that must appearing on selecting the last option in the select box.

+1 here too


SR300 not acquiring depth frames (Linux)

Trying to connect the depth camera with realsense-viewer, the camera just disconnects after a few seconds, never showing any frame. Running the basic examples, I get this error:
RealSense error calling rs2_pipeline_wait_for_frames(pipe:0x5564abec8e00):
    Frame didn't arrive within 15000

Grabbing color frames works as expected - both using realsense-viewer and e.g. rs-color.
On Windows, everything works fine - including depth. So, the camera is OK.

Required Info

Camera Model
SR300

Firmware Version
<IP_ADDRESS>

Operating System & Version
Linux Ubuntu 20.04

Kernel Version (Linux Only)
5.4.0-73-generic

Platform
PC

SDK Version
2.45.0 and development branch

Language
C++

Hi @rhaschke   Could you test please whether the Laser Power value of the camera is a factor in the SR300 disconnecting when the depth stream is used.
A method for doing this is to launch the Viewer and expand open the Controls category of the Viewer's options side-panel to locate an option called Laser Power.

Set the Laser Power option to zero using the slider before you enable the depth stream.

If the camera does not disconnect, slowly move the slider to increase the Laser Power value incrementally.

If the camera disconnects after the Laser Power is increased above a certain level then this indicates that the problem is related to the USB port supplying insufficient power to the camera to meet its power needs.

The camera only works with LaserPower = 0. I will try on a different machine. Thanks for the hint!

Indeed, moving to a different laptop resolved the issue. However, I noticed that it's not possible to stream both depth and color at 30 Hz. Trying to do so, one stream is lagging a second behind!

Hi @rhaschke  If you are using auto-exposure and are using both depth and color at the same time, you can enforce a constant FPS by going to the RGB section of the Viewer's options side-panel and disabling an option called Auto-Exposure Priority (a separate option from the Auto-Exposure in that section).


Hold QR animation on brightness tips and reset animated QR sequence

Depends on #494
This PR actually only has minimal changes; to get a proper diff you need to compare against https://github.com/kdmukai/seedsigner/tree/qr_encoding_refactor
Description
For fountain encoders, the first n frames are extremely valuable. But since we start the animated QR sequence with the brightness tip overlaid, many of the early frames will be wasted and/or unreadable.
This change pauses the current frame whenever the brightness tip is visible and then restarts the animated QR sequence (per @jdlcdl's suggestion) when the brightness tip deactivates.
Fountain encoders: should be beneficial
"Simple" animated encoders (Specter xpub): doesn't really matter
Static encoders: no effect
This pull request is categorized as a:

[x] New feature (really a behavior change)

Checklist

[x] I’ve run pytest and made sure all unit tests pass before sumbitting the PR

If you modified or added functionality/workflow, did you add new unit tests?

[x] N/A

If this evolves to support more elaborate changes to the fountain encoder sequence, then dedicated tests will be added.
I have tested this PR on the following platforms/os:

[x] Raspberry Pi OS Manual Build
[ ] SeedSigner OS on a Pi0/Pi0W board

Note: Keep your changes limited in scope; if you uncover other issues or improvements along the way, ideally submit those as a separate PR. The more complicated the PR the harder to review, test, and merge.

ACK tested as of commit 2653c8e
This worked for me, rather nicely especially when late about getting the camera focused on seedsigner screen.
I see all tests passed above, they passed on a linux desktop and also on my rpi0 dev setup.

ACK and tested without any issues


Textbox Validation Error Underline is not getting aligned

Textbox Validation Error Underline not Aligned.
Expected behavior

What I am getting, even after removing all styles

Expected behavior

What I am getting

And you checked your css? What if you replace your css with the default in Matblazor?

And you checked your css? What if you replace your css with the default in Matblazor?

Yes, even after removing all the other css except matblazor the issue still exists.

I too am having this issue.


Add form for creating/editing a user

Only usable by content admins
Allow creating integrations leads with a multiselect for associated atlases

Complete! Thx


Error.message returns wrong type (or wrong value)

Hello,
I found a bug in the types of ZodError.message. It should return a string, but returns an Error-Object. Either the Type or the return-value is wrong.
import { z } from 'zod'

const myString = z.string()

const results = myString.safeParse(5)

if (!results.success) {
  const message = results.error.message
  // type said message is a string, but got an Array with an Error-Object
  console.log('message:', message)
}

BTW: Thank you for this wonderful library!

But it is a string?
console.log('message:', typeof message) // message: string
It just looks like an object because the space parameter to JSON.stringify is 2.

Oh, sorry, the message variable has the form:
[
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "number",
    "path": [],
    "message": "Expected string, received number"
  }
]

but you are right, it is a string, it just looks like an array with an object.
I was expecting message to have the value of "Expected string, received number". Therefore, this is not a problem with the data type. I apologize for any confusion and have corrected the title accordingly. Thank you!

Ok, this is unexpected for me, but intentional for the author. I close this, because I think, there is nothing to fix here.

I agree it is a bit unexpected 🤔. I think I ran into this same confusion when I was first experimenting with zod myself.


[QUESTION] Multi keyword error keeps showing in VSCode

Please describe.
I have a robot suite and the Suite Setup looks like this:
*** Settings ***
Suite Setup         Run Keywords
...                     Set Library Search Order    MASTER    AND
...                     HERO6: Connect

The "My Keyword" is from module I wrote and puts in workspace folder, and it keeps highlighted with error:
Multiple keywords with name 'HERO6: Connect' found. Give the full name of the keyword you want to use:
...

Below is RobotCode settings in settings.json, and I pretty sure RobotCode extension can load my module, since I can track keyword in my robot suite with cmd + click
"robotcode.robot.pythonPath": [".", ".venv/bin/python"]

I'm not sure if this is an issue of RobotCode or vscode, is there any solution?
 Or is there another library with the same keyword?
The keyword that is found multiple times is HERO6: Connect and not My Keyword, in which line does the error occur?

Sorry for my mistake, it's should be the below code.
*** Settings ***
Resource            ../../../Keywords/Main.robot
Suite Setup         Run Keywords
...                     Set Library Search Order    MASTER    AND
...                     HERO6: Connect

This problem is happened on HERO6: Connect, and the resource file Main.robot import 2 times of my module indeed (like the below code):
Library        path.to.my.module.HERO6Client  WITH NAME  MASTER
Library        path.to.my.module.HERO6Client  WITH NAME  SLAVE

I want to ensure that would I get these warning if I already use the keyword Set Library Search Order to specify the keyword I want? Is it expected behavior or not?

ok, I understand, unfortunately RobotCode does not support Set Library Search Order, as this can only be evaluated dynamically at runtime. However, RobotCode only performs a static analysis.
A workaround is, and because it is actually more readable, simply put the namespace in front of the keyword:
*** Settings ***
Library        path.to.my.module.HERO6Client  WITH NAME  MASTER
Library        path.to.my.module.HERO6Client  WITH NAME  SLAVE
Suite Setup     MASTER.HERO6: Connect

You can also replace the WITH NAME with AS, WITH NAME is deprecated and will be removed in one of the next RobotFramework versions.
*** Settings ***
Library        path.to.my.module.HERO6Client  AS  MASTER
Library        path.to.my.module.HERO6Client  AS  SLAVE
Suite Setup     MASTER.HERO6: Connect

If you do not want this, you can also simply hide the error by telling RobotCode to ignore this error.
*** Settings ***
Resource            ../../../Keywords/Main.robot
Suite Setup         Run Keywords
...                     Set Library Search Order    MASTER    AND
...                     HERO6: Connect    # robotcode: ignore

Simply add # robotcode: ignore ignore in the line where the error occurs as a comment.

OK, I'll give it a try, thanks alot!!


Lib usage

Hello, one question about lib usage. I would like to use c# Bitmap (or raw image data array) as the way to communicate with your openpose wrapper (right now Mat is used but it is not clear how to convert Bitmat to Mat and vice versa). Do you maybe have an example code in c# showing how to do that?

How do you create raw image byte[]?
If you create it from System.Drawing.Bitmap or BitmapSource, it contains padding. So it occurs problem.

Is this header needed

No

Do you maybe know what could be the problem?

This C++ wrapper creates cv::Mat instance and it is passed to openpose procee in function but it may be destruct even though it was passed to openpose. I guess this cv::Mat maybe should be cv::Mat*.
Could you show the your code to reproduce issue?

Size of bitmap array is exactly widthheight3 bytes so that looks ok... But I suspect that maybe my dll export is maybe done in wrong way... Can you please check?... Below are signatures of both versions of emaplaceAndPop:
        [DllImport(NativeMethods.NativeLibrary, CallingConvention = NativeMethods.CallingConvention)]         public static extern IntPtr op_wrapper_emplaceAndPop_cvMat(OpenPose.DataType dataType, IntPtr wrapper, IntPtr mat);
        [DllImport(NativeMethods.NativeLibrary, CallingConvention = NativeMethods.CallingConvention)]         public static extern IntPtr op_wrapper_emplaceAndPop_rawImage(OpenPose.DataType dataType,                                                                       IntPtr wrapper,                                                                       byte[] data,                                                                       int width,                                                                       int height,                                                                       int type);

I tried Wrapper.EmplaceAndPop(byte[] image, int width, int height, int type).
        [DllImport(NativeMethods.NativeLibrary, CallingConvention = NativeMethods.CallingConvention)]
        public static extern IntPtr op_wrapper_emplaceAndPop_rawImage(OpenPose.DataType dataType,
                                                                      IntPtr wrapper,
                                                                      byte[] data,
                                                                      int width,
                                                                      int height,
                                                                      int type);

        public StdSharedPtr<StdVector<T>> EmplaceAndPop(byte[] image, int width, int height, int type)
        {
            if (image == null)
                throw new ArgumentNullException(nameof(image));

            var ret = NativeMethods.op_wrapper_emplaceAndPop_rawImage(this._DataType,
                                                                      this.NativePtr,
                                                                      image,
                                                                      width,
                                                                      height,
                                                                      type);
            return new StdSharedPtr<StdVector<T>>(ret);
        }

It works fine.
At first, I passed wrong value as int type. It produded same issue you faced.
This time. type was 17. Correct value is 16. I guess your CV_8UC3 may be wrong value.

Could you test 334341e80757226107b7353201a379d87c1c6c69?
1_BodyFromImage_Bitmap example uses new EmplaceAndPop.

You are right, had a wrong value for CV_8UC3. Number 16 is correct. It is working for me also.
By the way, just to confirm, IntPtr when passing array also works (on C# side you need to pin the array and get the pointer). E.g.
       public StdSharedPtr<StdVector<T>> EmplaceAndPopRawImage(IntPtr data, int width, int height, int type) {             if (data == null)                 throw new ArgumentNullException(nameof(data));             var ret = NativeMethods.op_wrapper_emplaceAndPop_rawImage(this._DataType, this.NativePtr, data, width, height, type);             return new StdSharedPtr<StdVector<T>>(ret);         }

You are right. But IntPtr is not used for VB.NET. I don't want to expose IntPtr signature as much as possible.
And byte[] is Bittable type. So CLR marshaller make good. Sure, do pinning also.
You can refer https://docs.microsoft.com/ja-jp/dotnet/framework/interop/blittable-and-non-blittable-types

Yes, I agree byte[] is OK.
I am having problems now accessing Array values where pose key points are stored. There are two problems I see:

I can't get to the values using Array indexer i.e. [] operator.
Most of the times I can get to values using Array.toString() (and I see correct values), but sometimes this method goes into memory access violation exception.
Before I access the array I do check that Array is existing and is not empty.
Can you maybe look into why is 1. happening?

Hi. I added Mat,ToBitmap and Wrapper.EmplaceAndPop(Bitmap) to latest develop branch.
Give it a try!!

I can't get to the values using Array indexer i.e. [] operator.

Do you have a image file which be able to reproduce issue?
Or you faced issue while using webcam? If so, it is difficult to resolve issue.

OK, thanks, I will try it.

Do you have a image file which be able to reproduce issue?
The problem is not in the image... image is processed OK, but afterwards, calculated key points can't be accessed using indexer of Array< float >. By the way,

Just in case, could you check the https://github.com/takuya-takeuchi/OpenPoseDotNet/blob/master/examples/TutorialApiCpp/8_SynchronousCustomOutput/WUserOutput.cs ?
This sample works fine. And I have never seen problem you faced.
I doubt Array object is corrupted by GC.


Add Map Flavours with FDroid flavor and Google Maps flavor

Added gradle flavors for FDroid and Google Play store.
To work within a particular flavor switch the variant to either fdroidDebug/Release or googleplayDebug/Release and then use run from the IDE. See screenshot

From commandline
./gradlew :app:assembleGoogleplayDebug
# Or
./gradlew :app:assembleFdroidDebug
# The command below will generate both APKs (debug) in the `app/build/outputs/apk/` folder
./gradlew :app:assembleDebug

Also read Gradle Plugin Documentation regarding product flavors and watch the video about the Gradle Flavor stuff
Each Flavor needs to implement MapModuleFactory providing a MapModule which can do stuff as decided by the interface for MapModule. Right now I just made it to return me a Fragment, but you can do other stuff as well.

@creativepsyco Please checkout my comments, then we can merge this :smile:. Nice work by the way. This flavours thing is really cool.

Updated.

Cool but it says Travis failed. I can't make out why. Kindly check.

Just a timing issue on Travis. sometimes the ADB fails to upload the APK.

How did you tell?

Here is the error:
com.android.ddmlib.ShellCommandUnresponsiveException
	at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:513)
	at com.android.ddmlib.Device.uploadAPK(Device.java:1015)
	at com.android.ddmlib.Device.installPackages(Device.java:895)
	at com.android.builder.testing.ConnectedDevice.installPackages(ConnectedDevice.java:105)
	at com.android.builder.internal.testing.SimpleTestCallable.call(SimpleTestCallable.java:125)
	at com.android.builder.internal.testing.SimpleTestCallable.call(SimpleTestCallable.java:48)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Unable to install /home/travis/build/fossasia/open-event-android/app/build/outputs/apk/app-debug.apk
com.android.ddmlib.InstallException: Unable to upload some APKs
	at com.android.ddmlib.Device.installPackages(Device.java:913)
	at com.android.builder.testing.ConnectedDevice.installPackages(ConnectedDevice.java:105)
	at com.android.builder.internal.testing.SimpleTestCallable.call(SimpleTestCallable.java:125)
	at com.android.builder.internal.testing.SimpleTestCallable.call(SimpleTestCallable.java:48)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
com.android.builder.testing.ConnectedDevice > runTests[test(AVD) - 5.0] FAILED
	com.android.builder.testing.api.DeviceException: com.android.ddmlib.InstallException: Unable to upload some APKs
		at com.android.builder.testing.ConnectedDevice.installPackages(ConnectedDevice.java:108)
null

Here's the solution:
http://stackoverflow.com/questions/28949722/android-tests-fail-on-travis-with-shellcommandunresponsiveexception
But sometimes doesn't work for some reason.

Cool It has passed. So I'll merge it.


Remove first name fields from SMS game form

The first name fields tested in #4247 and implemented in #4710 are unfortunately being reverted! :fire: Although they increased completion rate for games, they decreased conversion rates significantly. Therefore, we're going to remove those fields and return styles to how they were previously.
/cc @mikefantini @namimody

According to Freddie, there are no changes needed on the Node backend for this change & he's working on updating the language used in the games to not reference player names.

@mikefantini This is ready to go once #5160 is merged. Just waiting on confirmation that we're okay for these changes to go live.

we will be by the time we deploy to prod yeah. thanks @DFurnes


C++/winRT migration

Hi all,
This is the PR for migrating the library to C++/winRT. The migration currently exists as a separate project, with a separate namespace, but this is just nicities for later.
What happened here, in a nuttshell:

All classes that were not needed to be winRT classes have been moved to vanila C++ (mostly sample providers and other low level stuff that integrates with FFMPEG).
There is still some work to be done on the hardware accelerated video effect (haven't migrated that but it should be mostly mechanical work).
Need to fix all bugs and test this well.

Some additional breaking changes:

Metadata tags are now returned as Map<string, Vector> instead of Vector<KeyValuePair<string, string>>. Mostly a small difference.
What do you think, @lukasf  @JunielKatarn ?

Am I dumb or is it really hard to implement the IBuufferByteAccess in c++/winrt?

I am quite close to getting it 100% working. There's a problem with the texture and buffer pools, objects returned in the pool can't be recycled apparently.

So directx and software decoding seems to work for video now. I will need to fix passthroughs.
Most bugs seem to originate from uninitialized variables.

Wow @brabebhin, really nice work! This is really amazing. Kudos for all the heavy lifting.
I did not yet have time for a deep review. But some general remarks:

When the migration is complete, this should be a drop-in replacement. So the namespace should be the same and also no API changes, if possible (the metadata API change is accepted). I guess you used a separate namespace for development and testing, which is fine. But finally, we should use the old namespace. From the consumer perspective, it should not make a difference if our Windows Runtime Component was developed using C++/CX or C++/WinRT.

The files are in a new folder, which will make git lose the history. If you are more or less finished with migration, the new files should be put back into the old Source folder (any leftover files deleted there). Then I can review old against new implementation, which will be much better then just looking at the new sources.

There are a lot of changesets in here. I think we should make this a squash commit, to get a clean history. We need to be extra careful when merging this PR.

We also need to think about when we will merge this. Since the changes are so massive, we probably should not hurry this one out. Maybe we should first push out the original 1.0 release PR (I planned to do this before my long journey, but didn't have the time in the end). Then we can thoroughly test this and make it a 1.1, once we are confident there are no leaks or bugs. We can include the metadata API change into the 1.0 release already, so we won't have API changes between 1.0 and 1.1.

@lukasf agreed. We need serious testing on this.
I originally wanted to do drop in migration, but the project file got all mingled up and decided starting fresh is just easier, and once everything works, I just rename the namespace and move the files back in.

Sure, if you like, you can push the API changes to 1.0 branch as well.
I can do the NuGet stuff once we are ready for a release.

@JunielKatarn
In your experience, does it make sense to initialize hstring instances as empty strings? like this? hstring bla = L"";?

@JunielKatarn
In your experience, does it make sense to initialize hstring instances as empty strings? like this? hstring bla = L"";?

I believe this is the "preferred modern C++" initialization style: winrt::hstring myHstring{};.

So I merged the v1.0 PR. This one will need a rebase.
@brabebhin Do you have an account on nuget.org, by the way? I'd like to make you second owner for the libs, as a backup.

Hi,
Just created one now, same username, "Brabebhin".

Okay, done. Updating the NuGet libs is pretty simple. Just click on „Upload“ on top, drop the created .nupkg, verify that the displayed metadata looks fine (version number, etc), and then proceed. It may take a few minutes until the libs go live.
I'll take care of this normally, but it's probably good if you can do it as well, just in case.

Got the invites, thanks.
I hope you're good :)

Yes, the vacation was pretty amazing, thanks! :)

On a short test, the port seems to run fine on my PC. Basic playback working and no major memory leaks after opening a bunch of files. Fixed some NuGet issues and aligned toolset versions, trying to get AppVeyor build working...

I will need to port the BasicVideoEffect these coming days.

So apparently using win2D is quite the hustle. We need to download a specific version of win2D, use cppwinrt.exe to generate some header files and pack the dll along with the winmd. This will needs to be done manually...

The effect is not buggy as hell, I just broke it with the 1.0 namespace change.
On StackOverflow, I read that with more recent Win2D versions (as of mid 2018), you just need to reference the NuGet package and then the headers will be auto-generated. Did you try that?
Also Microsoft is moving Win2D into the WindowsAppSdk, and they have a separate NuGet package for WinUI 3 apps (which is not 100% finished as I read). But if we use that, it probably won't work in UWP apps. So if we cannot get the normal Win2D package working, we might have to move the effect out to a separate addon library, specific for WinUI 3. Maybe it would be a good idea anyways, to have a separate lib for stuff like the video effect and custom subtitle rendering, which are both more or less independend of the FFmpegInteropX core library.

I wasn't referring to the activation when i said it's buggy. For some reason, simply installing the nuget doesn't work for me. But if it works does you,  then it means there's something wrong with me setup.

Thanks for the hint @lukasf
After installing some new updates to visual studio, it does generate the header files for me automatically. Which is great, I pushed the changeset.
All i need to do now is understand how the activatable class id for the effect works in C++/winRT. Apparently it is not as easy as in C++/CX. I'll leave this for later.

Turns out the problem was unrelated to the class ID, which is the same as in C++/CX, but rather was another idl/ cppwinrt gotcha:
The IDL of the class must contain a parameterless constructor. The [default_interface] attribute does not suffice, the constructor must be declared explicitly.

I just pushed a big changeset to address all those compiler warnings. Some of them actually pointed to problems and even bugs. The basic funtionality seems to be working now. Maybe it is a good time to move the files back, so we can start a proper review of all file changes.
Of course, this will need intense testing of all the special cases and functionalities, with various files and formats.

I actually think we should merge the other outstanding PR before migrating the namespace and folder.

Hi @lukasf
I merged the branch fix-leaks. Can you check and see if the merge was ok?
Thanks.

Looks good. I done some minor changes there.
We should also consider making use of com_ptr class in WinRT for all the D3D stuff. It really simplifies the ref handling, making it more solid at the same time. And you can just use .as<T> instead of QueryInterface, which is also a lot nicer.

Yes. That is a good idea. I also thought of it, but i initially decided to port the code as is and do stuff like this later.
On the other hand, since there's no rush, i could do it before merge.

We can do it later as well. The merging will probably be easier, if we do not do too much of refactoring upfront.

By the way, in the WinRT samples, I often see assignments through blocks like this:
int main()
{
    winrt::Windows::Foundation::IStringable s{ winrt::make<MyStringable>() };
    auto result{ s.ToString() };
}

Do you have any insights on why they do it like that?  I wonder if it has any benefits.

As per my understanding, it depends on what you initialize. For a class with constructor, it basically calls the constructor. For classes without constructors, it initializes the members of the class in order.  This is quite the gotcha in some directx12 structures.  I lost days debugging something like that. In your examples i think it doesn't make any difference between the two examples.
In some situations it also helps the compiler disambiguate situations in which you have an variable with the same name as a function and your try to call the constructor of that variable.

Yeah I only know this style from initialization from structs. And it comes with the disadvantage that you don't know which parameter goes into which field, if you don't know the exact struct layout.
But if you have a constructor, then why not call it directly? Why not store the result of a method with =? To me it feels like abusing a language construct that was ment for something different. And without any obvious benefit, at least I don't see it. I really wonder who came up with that idea, and why they decided to use it so heavily.

I just read some interesting things about strong and weak references in C++/WinRT. In the old implementation, we had this requirement that we need to store the FFmpegMediaSource reference in the app, to prevent it beging collected during playback. With C++/WinRT, we can add get_strong() to the MSS event registration code. Then the MSS would hold a strong reference to the FFmpegMediaSource and prevent any early collection. No more need to store it in app code.
https://docs.microsoft.com/en-us/windows/uwp/cpp-and-winrt-apis/weak-references#safely-accessing-the-this-pointer-with-an-event-handling-delegate
Also in other event handlers, we should think about lifetime issues, and consider using strong or weak references explicitly, where appropriate.

Interesting find. I think that would basically solve the problem if we register events in the mss (like the starting event) with our ffmpeg media source as a strong reference.
I think we need to decide of we want to do those refactorings now. It could be useful to do all possible dangerous changes in one go.
Perhaps something along the lines of:
Merge stream buffer
Put files back in folder
Review changes
Do dangerous stuff(com ptr, references etc)
Review again
Merge

I agree that it is a good idea to test all this together. But I would really like to keep the history clean, and not mix too many things into one PR. So I would propose to bring all these to master, but as separate PRs (winrt, stream buffer, refactorings). Each PR should be roughly tested and reviewed. But final testing will be done on master branch once all things are there, before we make it an official release.
I think that it will also make reviews better, if you can see a clean diff of e.g. only the pure winrt migration without refactoring, only stream buffer, only com_ptr refactoring,...
What do you think?

This is also a good idea. But we need to decide  if we want to merge this before stream buffer or after.
Once this is merged I will also import it in my own app and i will be able to do some more advanced testing on it.

To me it does not really matter now which one gets merged first. Whatever feels finished first gets merged first. There will be some manual merge effort when these two get in touch, but I think it does not really matter in which order it arrives.
I am still not 100% happy with the stream buffer implementation. It works, but it has some design weakness that I don't like. I had to use workarounds to avoid circular references. Maybe I will come up with a better design to avoid these workarounds and have cleaner code. So that branch might also need some more time.
We should probably do a 1.0.1 release with the fix for the BasicVideoEffect, before anything else gets merged to master.

Ok, then i will put the files back in this week. Probably today or tomorrow, if things go well.

OK, I've moved the files back, but the build isn't working. There seems to be a problem with the precompiled header which I can't figure out, tried several approached and all ended in the same problem. I pushed this so maybe you can also take a look and see what I'm missing. I will keep trying.

I fixed most of the build but two errors remain, regarding WinRT actication factory.
Probably need to compare project files more.

Cool. I will focus on that now. Nice job with the pch, I tried various combinations and none worked :( (I even thought its contents were to blame somehow, hence commenting it out)

The C# sample works fine, but I found two issues with the CPP sample, surprisingly:

The binding of CharacterEncodings does not work. We can get the value find, but an ArgumentException comes when assigning it to Combobox.ItemsSource.
When opening a file, somehow the app continues on a wrong thread, causing an exception when accessing the splitter (close pane). co_await the file open returns normally on UI thread, but co_await on our MediaStreamSource somehow returns on a background thread. That should not happen of course. Pretty weird. Playback still works, but there is something wrong with the async stuff we return in our CreateFromXX methods.

We need to find out what is wrong here.

I fixed the second issue by manually switching back to UI thread. To me, this does not seem right. Normally, the co_await on the UI page should switch us back to UI thread, no matter what the lib does. But it seems that the WinRT resume on background switches the context in a way that UI won't switch back. This is very different from what I know async/await. I have kind of a bad feeling about this.
I tried a few things about the CharacterEncoding but failed. The old class has that Bindable attribute. But the attribute is missing in the winrt headers. And if I include the legacy header, I get loads of compile errors. I have also seen [bindable] in the idl file in some docs, so I added that but it didn't help as well. I am not even sure if that is the problem.

The problem seems to be the VectorView that we return rather than the CharacterEncoding class.

It's strange that the observable vector works, but the normal vector does not work. The normal vector is supposed to work as well, and it does in C++/CX. It's just that it won't report updates, but we are not updating this one anyways.
I needed to add the [bindable] attribute in the IDL file, otherwise binding to properties of CharacterEncoding did not work for the CPP sample. We should consider adding this to any class that might be bound in a UI, such as the StreamInfo classes.
And I just found two problems in the subtitle providers:
Looks like style parsing does not work anymore on the C++/WinRT branch. sscanf_s always returns 0 parameters parsed, although the input data looks perfectly fine. On master, the same input data returns 23 parameters parsed.
And also the code to parse the actual subtitle lines seems to be one index off, but that occurs on master as well?? I only tested with one file, need to test more. It might be a change in FFmpeg. The ssa text is not in the standard format anymore, looks like the first parameter is missing. I wonder how long this is broken. Subtitles are still displayed, but styles are not applied anymore.

I tested this in an actual app and found some more issues, especially subtitle related. There was also a crash on cleanup, and some other things. Now it is looking pretty good, still more testing needed.
I tried a few hacks to get XML docs working, but it only works for methods, not properties, events or enums. It's a shame that C++/WinRT does not even support XML docs. Such a basic thing not working, every other language has that.
I noticed that AttachedFile is part of the IDL. It is only used internally, we should keep that as a pure C class. The current AttachedFile would break when our main class is destroyed. If we'd want to expose AttachedFiles, we'd need to think about refernce handling.

AttachedFile is public in the current c++/cx version.

Sorry I was out and about the past few days. I see what you mean with the AttachedFile, however, that api has been public for quite some time. Changing it would be a breaking change.

That's true. But since there was no way to create it (no public ctor, no other API), I would not really consider this a breaking change. I have created a PR to remove it from old implementation as well.

TBH I never used that API since we merged it the first time around.

Nice work! Surely trumps my template method in pch.
If i remember correctly, i only used one event handler with weak references, can't remember which one

For me this is looking all good now. Maybe a little final testing and we are good to merge.

Cool. I will give it some short tests over the weekend.
On a side note: biggest PR yet?

Looking good for me.

We are on master now. Nice work!

Really good to see this work.
Kenji Mouri


updated merge sort with better code and comments

updated merge sort with better code and easy to understand comments

Thanks for contributing!


ENH: Move install-target specification for TubeTKLib into TubeTKLib

When building as an external remote module, install-target specification must
occur within the CMakeLists.txt that declares the target.

  I'm still doing some spring
cleaning and updating to "modern" cmake.   Stay tuned!
Thanks!
Stephen
On Wed, Mar 11, 2020 at 5:05 PM Hans Johnson<EMAIL_ADDRESS>wrote:

@hjmjohnson approved this pull request.
In CMakeLists.txt
https://github.com/KitwareMedical/ITKTubeTK/pull/1162#discussion_r391266704
:

@@ -292,8 +292,8 @@ include_directories( ${TubeTK_SYSTEM_INCLUDE_DIRS} )

add_subdirectory( TubeTKLib )
-install( TARGETS ${TubeTKLib_LIBRARIES} EXPORT TubeTKLib-targets

ARCHIVE DESTINATION lib )
+#install( TARGETS ${TubeTKLib_LIBRARIES} EXPORT TubeTKLib-targets

Remove commented out code.
In apps/ComputeTubeProbability/CMakeLists.txt
https://github.com/KitwareMedical/ITKTubeTK/pull/1162#discussion_r391267027
:

@@ -29,8 +29,6 @@ SEMMacroBuildCLI(
${TubeTK_SOURCE_DIR}/docs/TubeTKLogo.h
TARGET_LIBRARIES
${ITK_LIBRARIES}

ITKIOMeta

NICE removal of redundancy.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/KitwareMedical/ITKTubeTK/pull/1162#pullrequestreview-373123800,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACEJL5TXHX73FPPVPFAKM3RG74IPANCNFSM4LF6TQGA
.

--
Stephen R. Aylward, Ph.D.
Senior Director of Strategic Initiatives
Kitware: Advancing the frontiers of understanding
by developing innovative open-source software platforms
and integrating them into research, processes, and products.


Split MMG-SQL table into multiple tables

The MMG-in-SQL Table comes as a single JSON to DBX bronze tables.
These need to be separated into its own tables.
All repeat elements are under a "tables attribute on the main schema. Each repeat should become its own table (after routing to proper program/route).
Ex.;

Preferably we can do this dynamically by splitting any child of tables into its own table.

[x] Bronze Notebook: Raw -> Bronze data
[x] Silver Notebook: Bronze -> Silver data
[x] Gold Notebook: Silver -> Gold data, to include Routing

[x] Line up schema Bronze
[x] Line up schema Silver
[x] Line up schema Gold

[x] Gold refactor to streaming: change to batch process per mmg and to foreachbatch

[x] Bronze switch to streaming (possible anytime)
[x] Silver switch to streaming (possible anytime)
[x]  Gold switch to streaming (blocked by gold refactor to streaming above)

https://github.com/CDCgov/data-exchange-hl7-dbx/pull/21
https://github.com/CDCgov/data-exchange-hl7-dbx/pull/24


making the navbar identical for all the pages

🐛 Bug Report
(A clear and concise description of what the bug is.)
Add relevant screenshot or video (if any)
(Add here)
the nav bars of all pages are different. All the pages must have same navbars otherwise it wont look professional.

/assign

The pr for this have been already made. @ashana1647


Fix highlights downloading: add token for highlight title for dirname/filename_pattern, and add option to download only highlights matching a title

Currently, for the parameters --dirname-pattern and --filename-pattern, there is no available token, such as a hypothetical {highlight_title}, for just the highlight title.
When downloading highlights with the --highlights parameter, there is thus no way to organize the downloaded files by which highlight they belonged to, and all the files just end up an undifferentiated mass in the same download directory, instead of being organized by highlight title as they are on the Instagram profile. And if we afterwards manually organize the downloaded files into different directories, without something like --filename-pattern={highlight_title}\..., on a download session later in the future, there is no way for Instaloader to check/know if a highlight file has already been downloaded on a previous session.
Such an available token would also be useful for downloading only highlights that match a specific title; in this example, we are matching for the title "foobar":
--highlights-filter="highlight_title==foobar"
Months ago, I posted about this issue, and it was suggested that the {target} token be used as a workaround, since with --dirname-pattern={target}, Instaloader will place each highlight into a different folder.  However, the {target} token does not actually work to solve this issue, since it gets replaced not with the highlight title by itself, but with the combination of profile name and highlight title. For example, if we are downloading with...:
instaloader --dirname-pattern=somepath\{target} --highlights --no-posts dogsofinstagram
...then the highlights are not downloaded to the directory pattern "somepath\highlight_title", but instead to the directory pattern "somepath\dogsofinstagram\highlight_title".
Moreover, this behavior for {target} is at odds with that described by the documentation at https://instaloader.github.io/cli-options.html, which says:

--dirname-pattern DIRNAME_PATTERN

{target} is replaced by the target you specified, i.e. either :feed, #hashtag or the profile name.

Per that documentation, {target} should refer to just the target specified, not a combination of the target with something else. There should be a separate token for highlight title, for three reasons: first, to be in agreement with the documentation; second, to allow other directory patterns; and third, to use as a filter to download only highlights matching a specific title.
For example, if we are downloading with...:
instaloader --dirname-pattern={target} --highlights --no-posts dogsofinstagram
...then the specified target is "dogsofinstagram". So the documentation would suggest that the highlights would be downloaded to the directory pattern "dogsofinstagram", but instead, the highlights are downloaded to the directory pattern "dogsofinstagram/highlight_title".
Suppose we want to download do a directory that is not in that exact format, for example, to the directory pattern "foobar/highlight_title" or to the directory pattern "dogsofinstagram/Highlights/highlight_title". Currently, there is no way to do either of those examples, since --dirname-pattern={target} forces the directory pattern "dogsofinstagram/highlight_title".
{highlight_title} should be a separate token from {target}, so that we can, for example, download to "foobar/highlight_title" by setting --dirname-pattern=foobar/{highlight_title} or download to "dogsofinstagram/Highlights/highlight_title" by setting --dirname-pattern={target}/Highlights/{highlight_title}.
Finally, such an available token would also be useful for downloading only highlights that match a specific title; in this example, we are matching for the title "foobar":
--highlights-filter="highlight_title==foobar"

The problem with introducing an additional token for the highlight title that would be supported by the dirname pattern is, that dirname patterns which uses the new token would break for non-highlight downloads e.g. regular posts. For example, if using a --dirname-pattern={profile}/{highlight_title} what value would it have for regular posts? Since the dirname pattern affects the dirname of all posts and is not specific for highlights, it would be difficult to properly introduce such a new token.

The problem with introducing an additional token for the highlight title that would be supported by the dirname pattern is, that dirname patterns which uses the new token would break for non-highlight downloads e.g. regular posts. For example, if using a --dirname-pattern={profile}/{highlight_title} what value would it have for regular posts? Since the dirname pattern affects the dirname of all posts and is not specific for highlights, it would be difficult to properly introduce such a new token.

We already have existing tokens that are not valid in certain situations: for instance, {caption}, which is meaningless when downloading stories or highlights. If the user is using "{caption}" when downloading stories, that's the fault of the user for not using that token as intended. Similarly, if the user is using "{highlight_title}" when not downloading highlights, that would be on the user for not using the token as intended.
For non-highlights, the token {highlight_title} would just have no value, that is, have the value of an empty string (""), so that example given of --dirname-pattern={profile}/{highlight_title} would, for non-highlights, after substitution, just become "profile/", which still works fine.

However, at least in the way the feature (or set of at best weakly related features) is presented here, we would not be able to accept it, as it is not logically consistent.

On the contrary, I'm trying to fix logical inconsistency: as mentioned in the original post, this behavior for the {target} token is inconsistent. The {target} token is usually substituted with the target, except when the --highlights option is set, when it instead is substituted with the combination of target and highlight title.

Further, it is unclear to me - even after reading through your issue several times, by the way - what problem your proposed feature is trying to solve. This makes it difficult to meaningfully argue for or against a proposal, let alone decide.

Okay, the core problem: highlights cannot currently be downloaded to arbitrary directory names. Suppose I want to download highlights of the profile dogsofinstagram to the directory "C:\Foobar", with the highlights sorted to different subdirectories of that directory by highlight title. If you look at the dogsofinstagram profile right now, the three most recent highlight groups are "Giveback", "Great Pet Care", and "Holiday". So the desired behavior is that the "Giveback" highlights would be downloaded to "C:\Foobar\Giveback", the "Great Pet Care" highlights would be downloaded to "C:\Foobar\Great Pet Care", and the "Holiday" highlights would be downloaded to "C:\Foobar\Holiday".
The problem is that this is currently impossible for Instaloader to do.
Using
--dirname-pattern=C:\Foobar
does not work because then the downloaded highlights are not sorted to different subdirectories by title; instead, all the highlights get downloaded to "C:\Foobar".
The previously suggested workaround of using the {target} token does not work either. Using
--dirname-pattern=C:\Foobar\{target}
will not work because the highlights instead get downloaded to subdirectories of "C:\Foobar\dogsofinstagram", not to subdirectories of "C:\Foobar":

"Giveback" highlights would be downloaded to "C:\Foobar\dogsofinstagram\Giveback" instead of "C:\Foobar\Giveback"
"Giveback" highlights would be downloaded to "C:\Foobar\dogsofinstagram\Great Pet Care" instead of "C:\Foobar\Great Pet Care"
"Giveback" highlights would be downloaded to "C:\Foobar\dogsofinstagram\Holiday" instead of "C:\Foobar\Holiday"

We do not like the fallback of {highlight_title} resolving to an empty string if not a highlight is being downloaded.
This seems like a case where a custom script should be used rather than the Instaloader CLI. The custom script could be even as simple as an invocation of Instaloaders CLI followed by an mv command.
We are not convinced that this would be a meaningful addition to Instaloader.

We do not like the fallback of {highlight_title} resolving to an empty string if not a highlight is being downloaded.

{caption} resolves to an empty string for posts without captions, for stories, and for highlights, so there should be no problem with the same thing happening for {highlight_title}.

This seems like a case where a custom script should be used rather than the Instaloader CLI. The custom script could be even as simple as an invocation of Instaloaders CLI followed by an mv command.

But that causes problems whenever the user wants to update the highlights later for new highlights added to the profile.
To continue on from the example previously used, if what the user wants is highlights in the directory
C:\Foobar
So the user uses
--dirname-pattern=C:\Foobar{target}
on the profile dogsofinstagram, and then afterwards the user uses mv commands to move everything from those subdirectories of "C:\Foobar\dogsofinstagram" up a directory level to "C:\Foobar".
A week later, the user wants to update the downloaded highlights for NEW highlights since added to that profile. The user would then have to use mv commands to move everything from "C:\Foobar" BACK to "C:\Foobar\dogsofinstagram" before the update so that Instaloader only downloads NEW highlights without wasting a lot of requests re-downloading highlights that have already previously been downloaded.
This process of moving all the highlights back and forth from "C:\Foobar\dogsofinstagram" to "C:\Foobar" (after the previous Instaloader CLI invocation) and from "C:\Foobar" to "C:\Foobar\dogsofinstagram" (before the next Instaloader CLI invocation) would have to be repeated EVERY time the user is attempting to update highlights, a move which is not so trivial for profiles that have hundreds or thousands of highlights.
All this could be avoided and solved with just the addition of a {highlight_title} token.

@EveryDirection I understand your request and it is a very valid one. Since the devs are refusing to acknowledge the issue, I would suggest you write a small script yourself to automatically restructure your downloads path once Instaloader finishes its job. It's trivially easy. If you're on linux you can do something like:
mv ig_downloads/mrbeast/mrbeast/highlights ig_downloads/mrbeast/.
rm -rf ig_downloads/mrbeast/mrbeast


Setting up Nginx reverse proxy and octant as subpath

Hi Team,
I am looking to use actant as a subpath but not able to succeed in it can anyone please help me with this. Here is my configuration
cat /etc/nginx/sites-available/test.conf
server {
    listen 80;
    server_name xx.com
    return 301 https://$server_name$request_uri;
}

upstream octant {
        server <IP_ADDRESS>:7777;
    }

map $http_upgrade $connection_upgrade {
    default Upgrade;
    ''      close;
}

server {

    listen 443 ssl http2;
    server_name xx.com;

    ssl_certificate           /etc/ssl/private/xx.pem;
    ssl_certificate_key       /etc/ssl/private/xx.key;

   # ssl on;
    ssl_session_cache  builtin:1000  shared:SSL:10m;
    ssl_protocols  TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
    ssl_prefer_server_ciphers on;

    access_log            /var/log/nginx/access.log;
  location / {

                proxy_pass http://<IP_ADDRESS>:8000;
                proxy_redirect   off;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header Host $host;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                # websocket headers
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection $connection_upgrade;
   }

  location /central/octant/ {
        proxy_pass http://octant/;
        proxy_redirect off;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-Proto https;
        proxy_headers_hash_max_size 512;
        proxy_headers_hash_bucket_size 128;
        proxy_read_timeout 300s;
        proxy_send_timeout 300s;
        proxy_set_header Upgrade "websocket";
        proxy_set_header Connection "keep-alive, Upgrade";
        proxy_set_header Origin "";
        proxy_request_buffering off;
        proxy_buffering off;
    }
  location /api/v1/stream {
      proxy_pass http://<IP_ADDRESS>:7777;
      proxy_http_version 1.1;
      proxy_set_header Upgrade "websocket"; #prevent error websocket: the client is not using the websocket protocol: 'websocket' token not found in 'Upgrade'
      proxy_set_header Connection "keep-alive, Upgrade";
      proxy_set_header Origin "";
      proxy_request_buffering off;
      proxy_buffering off;
    }
  }

Any help will be much appreciated.
Thank you

@sunnythepatel unfortunately, Octant is a desktop application. The octant server is only intended to be run as a backend to an Electron window and isn't intended to be run as a standalone service.


How can this error be fixed: "Python.exe - Ordinal Not Found" ?

Here is a simple python snippet that produces the error:
import cvxpy as cp
import numpy as np

n = 3
x = cp.Variable(n, integer=True)
#x = cp.Variable(n)
A = np.array([3,4,8]).reshape((1,3))
b = np.array([14]).reshape((1,1))
c = np.array([1,1,1]).reshape((1,3))
cons = [A @ x <= b, x >= 0]
obj  = cp.Maximize(c @ x)

# Construct a CVXPY problem
prob = cp.Problem(obj,cons)
prob.solve()
print("Status: ", prob.status)
print("The optimal value is", prob.value)
print("A solution x is")
print(x.value)

Here, is the complete error message in the popup window:

python.exe - Ordinal Not found

The ordinal 242 could not be located in the dynamic link library
C:\Python36\Library\bin\mkl_intel_thread.dll

and this error message is shown after I close the popup:

Long-step dual simplex will be used
Intel MKL FATAL ERROR: Cannot load mkl_intel_thread.dll.

I have tried many suggestions posted on the web; e.g. reinstall numpy and cvxpy, removal of suggested dll's, etc. I also tried some changes of my own; but none worked.
Note:
1. The error occurs when prob.solve() is executed
2. I do not have Anaconda installed
3. Windows 10 platform
4. Python vers. 3.6.5
5. cvxpy  vers. 1.1.5
6. numpy  vers. 1.19.2
7. mkl_intel_thread.dll is located in C:\Python36\Library\bin\
8. No error occurs if I replace x = cp.Variable(n,integer=True) with x = cp.Variable(n)

People often find anaconda helpful for managing your environment. Otherwise you need to fix issues like this yourself, which are due to the environment rather than anything in cvxpy.

The C:\Python36\Library\bin\ was in the environment path for the user. It should have been in the environment path for the system :(-


Claim fails and retry every 5 mins

Seems like claim fails and retry every 5 mins, which forced me to claim on the twitch site.
The screenshot of the log is as follows:

Hmmm, maybe Twitch changed something on their end. Would have to test this
for myself in order to figure it out. I'll look into it
Op za 29 okt. 2022 om 18:34 schreef Taozc @.***>:

Seems like claim fails and retry every 5 mins, which forced me to claim on
the twitch site.
The screenshot of the log is as follows:
[image: log]
https://user-images.githubusercontent.com/41264828/198842394-320bb64a-ac90-4c53-921e-ebea8c17b589.png
—
Reply to this email directly, view it on GitHub
https://github.com/AlexSterk/TwitchDropGrabber/issues/34, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADIH3WUOIUSCX2U6D3S2S33WFVGZPANCNFSM6AAAAAARR3PPC4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Okay so it seems Twitch is cracking down on bots and have added checks that (for now) make it impossible for the tool to work. I will add a disclaimer but I can't fix it. Unfortunately

Ok, sorry to hear that... and thanks for your work!


Fix #7354 "AttributeError" from tlsconfig.py

CertStore was inserting raw x509.Certificate objects into default_chain_certs instead of Cert objects, which caused an error later in tlsconfig.py when the certs were used.
Description
This fixes #7354, and has been tested to work locally.
Checklist

[ ] I have updated tests where applicable.
[ ] I have added an entry to the CHANGELOG.

This appears to be a regression from https://github.com/mitmproxy/mitmproxy/commit/0b5e310881f0116c9e8e2ca5b9da98e258de0a11?