Cannot get status of a new device

Hi,
I own 2 Konyks Priska Max Easy FR (connected socket, product_id ux5gchwsd77db0fp) that I can access via tinytuya.
Recently I bought 2 more for a new room and I got the newer version: Konyks Priska Max Easy FR V3 (Light) (product_id zlsvppjacilyow0u).
Even if I can access the two new devices from the Tuya smart app like previous ones, I cannot make them work with tinytuya.
I got this error: DEBUG:status() received data={'Error': 'Unexpected Payload from Device', 'Err': '904', 'Payload': None}
#!/usr/bin/env python3

import tinytuya

def main():
    tinytuya.set_debug(True)

    device = tinytuya.OutletDevice(
        "xxxxxx", "<IP_ADDRESS>", "xxxxxxx"
    )
    device.set_version(3.3)

    # Get Status
    data = device.status()
    print(f"status() result: {data}")

if __name__ == "__main__":
    main()

Here is the console output:
DEBUG:TinyTuya [1.12.8]

DEBUG:Python 3.11.4 (main, Jun  7 2023, 00:42:15) [Clang 14.0.3 (clang-14<IP_ADDRESS>.1)] on darwin
DEBUG:Using PyCrypto (3, 18, '0')
DEBUG:status() entry (dev_type is default)
DEBUG:final payload_dict for 'bf7593e10fcb1a4b2cv6i3' ('v3.3'/'default'): {1: {'command': {'gwId': '', 'devId': '', 'uid': '', 't': ''}}, 7: {'command': {'devId': '', 'uid': '', 't': ''}}, 8: {'command': {'gwId': '', 'devId': ''}}, 9: {'command': {'gwId': '', 'devId': ''}}, 10: {'command': {'gwId': '', 'devId': '', 'uid': '', 't': ''}}, 13: {'command': {'devId': '', 'uid': '', 't': ''}}, 16: {'command': {'devId': '', 'uid': '', 't': ''}}, 18: {'command': {'dpId': [18, 19, 20]}}, 64: {'command': {'reqType': '', 'data': {}}}}
DEBUG:building command 10 payload=b'{"gwId":"bf7593e10fcb1a4b2cv6i3","devId":"bf7593e10fcb1a4b2cv6i3","uid":"bf7593e10fcb1a4b2cv6i3","t":"1686898947"}'
DEBUG:sending payload
DEBUG:payload encrypted=b'000055aa000000010000000a0000008863414d63962e520fc0c1c09cfed89482230ff6fafc241aa3a9b850b23682e27daa94f4cdd6e53b8e345fd5f81e6fea3c6632ad83d10c483b4fe61eaa3d3f804d920cc3a654ff69f99b43f188d9a4ae7c230ff6fafc241aa3a9b850b23682e27d680f970484c92f5bf7c81a69a7e57a0976d59e717ce071f1f49fdb3f53f705e83e648bcd0000aa55'
DEBUG:_recv_all(): no data? b''
DEBUG:_recv_all(): no data? b''
DEBUG:Error decoding received data - read retry 0/5
Traceback (most recent call last):
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 1049, in _send_receive
    rmsg = self._receive()
           ^^^^^^^^^^^^^^^
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 939, in _receive
    data = self._recv_all( min_len )
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 920, in _recv_all
    raise DecodeError('No data received - connection closed?')
tinytuya.core.DecodeError: No data received - connection closed?
DEBUG:_recv_all(): no data? b''
DEBUG:_recv_all(): no data? b''
DEBUG:Error decoding received data - read retry 1/5
Traceback (most recent call last):
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 1049, in _send_receive
    rmsg = self._receive()
           ^^^^^^^^^^^^^^^
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 939, in _receive
    data = self._recv_all( min_len )
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 920, in _recv_all
    raise DecodeError('No data received - connection closed?')
tinytuya.core.DecodeError: No data received - connection closed?
DEBUG:_recv_all(): no data? b''
DEBUG:_recv_all(): no data? b''
DEBUG:Error decoding received data - read retry 2/5
Traceback (most recent call last):
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 1049, in _send_receive
    rmsg = self._receive()
           ^^^^^^^^^^^^^^^
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 939, in _receive
    data = self._recv_all( min_len )
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 920, in _recv_all
    raise DecodeError('No data received - connection closed?')
tinytuya.core.DecodeError: No data received - connection closed?
DEBUG:_recv_all(): no data? b''
DEBUG:_recv_all(): no data? b''
DEBUG:Error decoding received data - read retry 3/5
Traceback (most recent call last):
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 1049, in _send_receive
    rmsg = self._receive()
           ^^^^^^^^^^^^^^^
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 939, in _receive
    data = self._recv_all( min_len )
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 920, in _recv_all
    raise DecodeError('No data received - connection closed?')
tinytuya.core.DecodeError: No data received - connection closed?
DEBUG:_recv_all(): no data? b''
DEBUG:_recv_all(): no data? b''
DEBUG:Error decoding received data - read retry 4/5
Traceback (most recent call last):
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 1049, in _send_receive
    rmsg = self._receive()
           ^^^^^^^^^^^^^^^
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 939, in _receive
    data = self._recv_all( min_len )
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 920, in _recv_all
    raise DecodeError('No data received - connection closed?')
tinytuya.core.DecodeError: No data received - connection closed?
DEBUG:_recv_all(): no data? b''
DEBUG:_recv_all(): no data? b''
DEBUG:Error decoding received data - read retry 5/5
Traceback (most recent call last):
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 1049, in _send_receive
    rmsg = self._receive()
           ^^^^^^^^^^^^^^^
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 939, in _receive
    data = self._recv_all( min_len )
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/user/PycharmProjects/test_tuya/venv/lib/python3.11/site-packages/tinytuya/core.py", line 920, in _recv_all
    raise DecodeError('No data received - connection closed?')
tinytuya.core.DecodeError: No data received - connection closed?
DEBUG:ERROR Unexpected Payload from Device - 904 - payload: null
DEBUG:status() received data={'Error': 'Unexpected Payload from Device', 'Err': '904', 'Payload': None}
status() result: {'Error': 'Unexpected Payload from Device', 'Err': '904', 'Payload': None}

Many thanks in advance and kind regards,

Usually when the initial connection to the device succeeds but no response is received it means the protocol version is wrong.  New devices these days are almost always v3.4 if not v3.5.  Run the scanner to verify the device version: python3 -m tinytuya scan

Hi @fsutter, were you able to get these to work?

Hi @uzlonewolf,
sorry I'm in vacation.
Will test it as soon as I'm back home.
Thanks

Hi @uzlonewolf ,
thanks for the tip: new devices are of version 3.4!!!!!
That was the problem.
Kind regards,
fsutter

That's great!
Since you got it working I'm going to close this out.  Feel free to re-open it if you're still having problems.


Print2 d array

Please retest (force new jenkins build)

retest this please

Hello,
I am committed the working code.
Ready for final review.

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please

test this please

retest this please

Hi @theangrydev
All checks have been passed and all comments have been resolved.


Use multi-stage Dockerfiles for all images

The SDK build process currently has a pretty convoluted process for building docker images that involves several make targets and hack scripts.
I propose that we reduce this complexity by consolidating all image build steps into multi-stage Dockerfiles. With this change we will:

Update Dockerfiles to perform go binary builds in a builder stage rather than copying in a pre-built binary.
Update the image-build make targets to remove the make dependencies that build go binaries in the local environment
Update the image-build make targets to call docker directly.
Remove the hack/image-build-* scripts that are obsolete due to 3).
Move all Dockerfiles into hack/image/<image-name>. They were previously split between hack/image/ and images/
Move loading of images into kind from the image build step to the e2e tests where the images are actually required to be loaded into kind. Image building shouldn't be concerned with e2e setup.

This will give the project several benefits:

Reproducible builds. All images will be built using identical environments, regardless if run in CI or by a developer locally.
Reduce complexity. The build steps are now more self-contained in the respective Dockerfiles.
Co-location in hack/image reduces the overhead of remembering where various files are for each image build.
Simplified support for multiple architectures. Now that the go build happens as part of the image build, it is now much simpler to ensure the binary target architecture matches the image architecture.

There are some things I would consider out-of-scope for this:

Large overhauls of the Makefile. For now, I think we can have the docker go build stage call make to build the same binaries we always have.
Changes to the travis configuration and the way images are pushed and deployed.

Note that the scorecard images are not == these ones. Could we change the scorecard images to follow any final result define here? WDYT about add it in the scope of this change?

Yeah I'm including the scorecard images in the scope of this.
I'll have a PR up shortly.

@joelanford did a PR get put up for this? I like this proposal and would like to see it come to life

@aemperador I don't think this is going to happen quite yet actually. During testing I saw a host of issues with multi-platform builds and generally slow builds, which we can't have in CI. I'll be looking into multi-stage builds after we revamp our release process (see #4034).

/lifecycle frozen

/lifecycle frozen


"Error loading preloads: Could not find renderer" for exceptions

When the code throws an exception the jupyter cell only prints out
Error loading preloads: Could not find renderer.
Disabling this extensions shows the exception. I think it should not suppress exceptions....

Sorry for never getting back to this issue for such a long time.
Please could you share a sample code for replicating this issue
Its possible this has since been fixed as well,

Closing this issue as its been over 4 weeks, since the information was requested.
We'll be happy to reopen the issue when the requested information has been provided.


restic access repository without password

Output of restic version
restic 0.7.3
compiled with go1.9 on linux/amd64
How did you run restic exactly?
restic -r b2:bucket:path snapshots

What backend/server/service did you use?
b2
Expected behavior
i have init b2 on host "A" but when i connect from host "B" and i run snapshots command restic don't ask me password.

Actual behavior

Steps to reproduce the behavior

Do you have any idea what may have caused this?
Do you have an idea how to solve the issue?

Unfortunately you haven't included any output or error messages printed by restic and also not how you configure the B2 access, so I can only guess that on host "B" you've set the environment variable RESTIC_PASSWORD or RESTIC_PASSWORD_FILE. When that's the case, restic won't ask for the password. Try unset RESTIC_PASSWORD; unset RESTIC_PASSWORD_FILE on host "B" and try again.
I'm going to close this issue for now, please feel free to add further comments.

thanks,
on host "B" not set environment variable and no file password.
i will try before unset

Can you please rebuild restic and create a debug log (instructions) and attach it to the issue? Please make sure to replace any sensitive details included in there (authentication tokens, passwords etc) before posting it.
And please take the time to describe on how to reproduce this problem, ideally by filling out the issue template.
How do you configure B2 access for restic on each host? Please paste the commands and variables you use (after replacing sensitive values).


No mention of signerCertificates variable!!!

This tutorial does not work unless you also fill in the variable
private static final Collection<String> signerCertificates
in ProvisioningX509Sample.java with the root and the intermediate certificate.
I lost a full day trying to figure it out. PLEASE fix this tutorial.

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

ID: 9daa2965-cefc-26ec-e809-59cb2ece48c9
Version Independent ID: 970b172c-a7be-c3a1-2126-90962f14365a
Content: Provision a simulated X.509 device to Azure IoT Hub using Java and enrollment groups
Content Source: articles/iot-dps/tutorial-group-enrollments.md
Service: iot-dps
GitHub Login: @wesmc7777
Microsoft Alias: wesmc

@o-lazzarino-reply Thanks for the feedback and reporting the issue. I have assigned the issue to the content author to investigate further and update the document as appropriate.

@o-lazzarino-reply Thank you very much for reporting this. I'll be fixing this very shortly. I'm sorry for the frustration this caused you.

Hi there, Is there a python version of the this same sample in java? To connect via group enrollment?


This plugin failed to load. Please contact the author for more information. [v3.12.2408.1388]

Hello, got this problem today after i log off to generate API key for CHAT GPT (pre log out plugin loaded normally).
What can i do to solve the problem? Installed via Dalamud, sorry to bother, but im not very familiar with FFXIV plugin systems

hello! There is an issue with the config field for the chatgpt API key. I'm submitting a fix for this

hello! There is an issue with the config field for the chatgpt API key. I'm submitting a fix for this

Thanks for your work! Any ETA?

hello! There is an issue with the config field for the chatgpt API key. I'm submitting a fix for this

Thanks for your work! Any ETA?

Update was submitted for approval. We need to wait for it to be published by Dalamud


e2e migration test on PR targeting master

[x] gco master
[x] install app
[ ] maestro click through all screens[^1]
[x] gco release branch
[x] install app again
[ ] maestro click through all screens again

This is all based on the assumption that between GHA steps, we maintain the same AVD. Otherwise, each time we install our app, it will be a fresh install, which will not let us test that a migration from the master branch to the release branch worked without crashing.
Confirmed with https://scans.gradle.com/s/6ulorrahmvalo/timeline and https://scans.gradle.com/s/asm2laxnfiir2/timeline
[^1]: Because we run maestro test with $HOME/.maestro/bin/maestro test .maestro, the test suite will need to exist already on master.

Not able to see the evidence of previous run in https://github.com/lydavid/MusicSearch/actions/runs/9726640692

[ ] retry with maestro


Adding test case for Generate Cluster ID

Added a Testcase to confirm the GenerateClusterID behavior. Committing since it adds to our coverage :)

@CecileRobertMichon done!


Create a UI related to page-breaks

From Pierre:
I think that the page number should be displayed in the bottom slider :

For now we can access to a specific page without known the page number.
Perhaps we can open an issue with this feature ?
Originally posted by @panaC in https://github.com/readium/readium-desktop/issues/368#issuecomment-507305711

Related to #20

Two markups coexist in the real world:
Markup 1:

and Markup 2:
1

See article: http://sketchytech.blogspot.com/2017/01/when-is-page-break-not-page-break-epub.html
We need samples: are there IDPF samples containing epub:type="pagebreak"?

So, instead of trying to display page breaks in the context of the content itself, like Jiminy Panoz tried in #20, could we display page numbers (when present) in the timeline?

We need samples: are there IDPF samples containing epub:type="pagebreak"?

Sure, wherever there is a pagelist, there are page-breaks :)
(in the EPUB epub:type sense, and/or ARIA role mapping equivalents)
All the details are in the original issue:
https://github.com/readium/readium-desktop/issues/82#issuecomment-521457136
(I suggest we don't duplicate info, if we can avoid it)

Two markups coexist in the real world: ...

Actually, there is also role equivalents to epub:type, and aria-label vs. title attributes too. See: https://github.com/readium/readium-desktop/issues/82#issuecomment-526295012

So, instead of trying to display page breaks in the context of the content itself

I don't think reading systems should do anything special with HTML elements marked with epub:type="pagebreak" or role="doc-pagebreak" ... content authors can decide (and usually do) to hide skippable items such as "page numbers / breaks" (CSS display: none is the usual technique), or to inline versus block-display them, etc.
This is naturally an area where ReadiumCSS could be opinionated, by enforcing design choices (see discussions in https://github.com/readium/readium-desktop/issues/20 ).
So I think we should just focus on what affordances Thorium can offer to expose the "pagelist" nav (not any arbitrary pagebreaks in HTML content documents, but just those that are authored in the EPUB NavDoc).

flat, non-hierarchical list (fully visible + scrollable, or on-demand pulldown list) => trivial
search input text ("goto page number x") => trivial too (string matching, number radix)
maybe some mapping with bottom timeline, but this would require locator computations with percentage progress, just like mapping individual (sub)headings => not trivial

Re. ReadiumCSS could be opinionated, it’s worth noting experiments in Readium CSS definitely ended up altering the DOM with pseudo elements – generated content and screen readers already being an issue in and of itself.

The reason why I opened this issue separate from #82 is that I thought that page lists (as a nav structure) and page breaks (as inline elements in the HTML content) were two alternative ways to indicate page numbers. I see now that they are complementary (the nav reference points to the inline id).
Before we close this issue and centralize the discussion in #82, a quick question: does EPUBCheck checks in referential integrity of such ref/id system?

a quick question: does EPUBCheck checks in referential integrity of such ref/id system?

Yes. EPUBCheck verifies the linear order requirement too (within HTML documents, as well as across the spine).
References:
https://github.com/w3c/epubcheck/blob/6af3b9800e1481b634c1fb064afff594207f7357/src/test/java/com/adobe/epubcheck/api/Epub30CheckExpandedTest.java#L230-L253
https://github.com/w3c/epubcheck/blob/6af3b9800e1481b634c1fb064afff594207f7357/src/test/resources/30/expanded/valid/nav-page-list-reading-order/OPS/nav.xhtml#L15-L22
https://github.com/w3c/epubcheck/blob/6af3b9800e1481b634c1fb064afff594207f7357/src/test/resources/30/expanded/invalid/nav-page-list-unordered-fragments/OPS/nav.xhtml#L14-L20
https://github.com/w3c/epubcheck/blob/6af3b9800e1481b634c1fb064afff594207f7357/src/test/resources/30/expanded/invalid/nav-page-list-unordered-spine/OPS/nav.xhtml#L16-L22

Laurent, can we close this now?
("goto page" feature for EPUB nav@epub:type="pagelist" is what we have right now)

The "Go to page" feature now added is sufficient. Let's close this issue.


[From VSTS] Alt+Enter for "Execute in F# Interactive" doesn't work without a loaded solution

Dupe from here: https://developercommunity.visualstudio.com/content/problem/58735/altenter-for-execute-in-f-interactive-doesnt-work.html
Repro steps

Open Visual Studio.
Do not load a solution.
Load (or create) an FSX file.
Type in some code, select it, press Alt+Enter.

Actual result: nothing happens (status bar says "No quick actions available here").
Expected result: F# interactive window should open and the code sent there for execution.
Additional info
The Alt+Enter shortcut is specified in Options -> Environment -> Keyboard with "Use in" = "Global" (see attached screenshot), and it does work as expected as long as a solution is loaded.

I'll look into this and try to see what's going on.

Thanks @JoshVarty!

I've confirmed that the FSharpEditorFactory is not being used to open these files, which explains why we're not getting Alt+Enter keybindings:

I don't think I'm going to be able to track down exactly why this is the case, but I'll take a look at this first thing Monday morning.

@JoshVarty
Thanks mate

So I've looked into this a bit more and made the following observations:
We have registered multiple editor factory GUIDs.
4EB7CCB7-4336-4FFD-B12B-396E9FD079A9 is declared here.
We're using this GUID here which registers interest for various file extensions (.fs, .fsi etc.). However there is no corresponding editor factory for this GUID. It looks like perhaps we used to have an editor factory that was removed at some point.
8a5aa6cf-46e3-4520-a70a-7393d15233e9 is declared here.
It's used to register our Alt+Enter keybindings here and to register our editor factory here.
Proposed Solution

Remove 8a5aa6cf-46e3-4520-a70a-7393d15233e9 and use 4EB7CCB7-4336-4FFD-B12B-396E9FD079A9 everywhere. 4EB7CCB7-4336-4FFD-B12B-396E9FD079A9 was in the codebase first, so it feels natural to prefer it.
Remove this code. We're doing the same thing in our editor factory.
Register interest in the file extensions explicitly in our .pkgdef similar to what Roslyn is doing here.
Register editor factory explicitly in our .pkgdef similar to what Roslyn is doing here.

Problems
Unfortunately, when I make these changes locally I only get the correct behavior after I have loaded at least one solution with an F# project.
I'm buried with other bugs for 15.3 so I won't be able to look into this issue until next week at the earliest.

@JoshVarty I followed your recipe and pushed a version of it here: https://github.com/Microsoft/visualfsharp/pull/3115. Is that what you meant? However I haven't tried it out, and don't know what the different entries are doing exactly

It seems close, but I pulled it down and it seems to have the same issue: If you open a .fs file without a solution you can't use Alt+Enter because the wrong editor factory is chosen.
FWIW, you can see how VS is about to open the file by using Open With... and seeing which it has decided is the "Default" editor factory:

@JoshVarty This stuff is beyond my skills :) I just copied what you had.
Any idea on what to do next?

@cartermp Could you check the repro please when you get the chance? Going back to the original repro, I don't repro this with Nightly installed (I haven't tried without it installed).  F# Interactive Alt-Enter works OK for me
Perhaps I fiddled with my key bindings though,

(I reset my key bindings to "Default" and still couldn't repro

Start VS
Open an existing .fsx script
Highlight some text and hit Alt-Enter

I can reproduce this with Alt+Enter, but not with right-click+Execute in Interactive.

Start VS
Create new F# Script file (Script1.fsx)
Write some quick, basic code
Select all and Alt+Enter

@cartermp Still no repro for me.  What VS setup profile do you have installed?  And any other tools?

Default profile when installed - I don't have anything custom.

And any other tools?

In this case, I also have Xamarin tools installed.  Perhaps that affected it?  This is on the latest servicing release of 15.2 (though I observed it prior to those servicing releases as well).

@cartermp I still can't repro this - I have 15.3.1 and the Xamarin tools

I can no longer repro this with 15.3.3 + Nightlies.  Yay!

Thanks for checking! :) 🍾

With VS 15.5 Alt+Enter stopped working again when creating a blank F# script file (for both Stable and Nightlies). I don't know if it the regression is even older...
After saving the file, closing it and reopening it Alt+Enter works as expected.

I can reproduce this again in 15.6.1 + self-built VSIX.

I haven't the faintest idea how the editor picks the correct key binding, but I suspect this is related to the unused analyzer being triggered in code, thus triggering the lightbulb rather than sending to F# Interactive.

I see this too ..
If I have fsi window visible, it works fine.  If I have created an F# project it works fine.  But if I close fsi, shutdown and restart vs, then alt+ Enter doesn't work and gives a message "No quick Actions available here"  in the status bar.
Wierdly opening the fsi window, doesn't work ... but starting vs with the fsi window visible does work.

Seems like this is still happening in 15.5.1, I have a fresh install and no Alt-Enter support (only tried fsx files so far).

This has been resolved.


Question: I'm detecting the same Object four times using Multidetection but only get one set of coordinates.

Hello,
I'm using find object to detect multiple Objects of the same kind. in order to pick one up I need to have its coordinates, but the multidetection only publishes one set of coordinates. Is there a way to fix that? All the objects get detected using the same ID.
Thank you,
Phil

Hi Phil,
The 3D example didn't work with multiDetection enabled. I updated the code so that it can work. See referred commit above. Some results:

Note however there are no guarantees that "object_1" and "object_1_b" will refer to always to same object (e.g., TF may swap between both between detections).
cheers,
Mathieu

Hi Mathieu,
The code you provided does exactly what I was trying do to.
Tank you very much.


I want to make it a full band. What should I do next

Description

Additional information

Indeed it's not much of a use if it's not full band.

所以，我希望你能告诉我，在哪里可以使它成为一个完整的乐队！
或就该走的方向提供一些建议！
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2019年12月12日(星期四) 上午7:51
收件人<EMAIL_ADDRESS>抄送：  “✎₯㎕James_Bobo” <595284940@qq.com>;“作者”<EMAIL_ADDRESS>主题：  回复：[deezer / spleeter]我想组成一支完整的乐队。我下一步该怎么做（＃177）
的确，如果不是全波段的话，这没什么用。
—
You are receiving this because you authored the thread.
直接发送回复此电子邮件，在GitHub上查看，或取消订阅。

Hi. Do you mean full audio bandwidth?

yeah,I hope it's audio bandwidth is complete, if you have ever been to pytorch version of the separation, do you think it goes with spleeter difference in what place?
https://github.com/sigsep/open-unmix-pytorch
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2019年12月20日(星期五) 凌晨0:24
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [deezer/spleeter] I want to make it a full band. What should I do next (#177)
你好 您是指完整的音频带宽吗？
—
您收到此消息是因为您创建了线程。
直接回复此电子邮件，在GitHub上查看，或取消订阅。

I wasn't aware of Open Unmix project, thanks for that. If you search around, you will find this question has been asked before. Here is the FAQ entry for this query:

Here is a detailed discussion of the issue. #2
What I understand is that Spleeter is not learning from frequencies above 11khz, hence that section is discarded, but there are workarounds that will disable this automatic cutoff, mentioned in FAQ and the thread mentioned.
Also if you want to test, I saw the splitter.ai version of Spleeter has the option to enable/disable 11khz cutoff.

We've just updated the FAQ to provide a new way of performing separation above 11kHz. Also configs that perform separation up to 16kHz were packaged in spleeter as mentioned in the wiki


Modify the sample code to es2015 syntax in README.md

Changes proposed:
We use const in README.md's sample.
Upgrade Path (for changed or removed APIs):
Acceptance Checklist:

[ ] All commits have been squashed to one.
[ ] The commit message follows the guidelines in CONTRIBUTING.md.
[ ] Documentation (README.md) and examples have been updated as needed.
[ ] If this is a code change, a spec testing the functionality has been added.
[ ] If the commit message has [changed] or [removed], there is an upgrade path above.

Coverage remained the same at 76.667% when pulling eb842b5dd9dfd55da98b7ad2ad2a633b5200c6da on abouthiroppy:feature/update-readme into e10181d20c8a1b66cbe21cfc86a19b64c9e2e9a3 on reactjs:master.

Coverage remained the same at 76.667% when pulling eb842b5dd9dfd55da98b7ad2ad2a633b5200c6da on abouthiroppy:feature/update-readme into e10181d20c8a1b66cbe21cfc86a19b64c9e2e9a3 on reactjs:master.

@claydiffrient Updated.

@claydiffrient Updated.

Coverage remained the same at 76.753% when pulling 088f84426736035c693147ff838ad87e7bc090fd on abouthiroppy:feature/update-readme into d50918c1c583ac094f29c0b3b2d0a3bd86b306be on reactjs:master.

Coverage remained the same at 76.753% when pulling 088f84426736035c693147ff838ad87e7bc090fd on abouthiroppy:feature/update-readme into d50918c1c583ac094f29c0b3b2d0a3bd86b306be on reactjs:master.

Coverage remained the same at 76.753% when pulling 647d31ee76f5dd0629b58c58f48ef866889113c9 on abouthiroppy:feature/update-readme into d50918c1c583ac094f29c0b3b2d0a3bd86b306be on reactjs:master.

Coverage remained the same at 76.753% when pulling 647d31ee76f5dd0629b58c58f48ef866889113c9 on abouthiroppy:feature/update-readme into d50918c1c583ac094f29c0b3b2d0a3bd86b306be on reactjs:master.


TFM: Add TFM_CMAKE_BUILD_TYPE config

The value is now passed from the Zephyr build to the TFM build.
Signed-off-by: Øyvind Rønningstad<EMAIL_ADDRESS>

@microbuilder @tejlmand could you take a quick look at this minor patch?

@microbuilder @tejlmand could you take a quick look at this minor patch?

Seems I already approved here: https://github.com/zephyrproject-rtos/trusted-firmware-m/pull/44
@ioannisg could you create github action that will automatically move the PR approval from one repo to another when the code changes location :laughing:


Syncing Reliability Issues / iOS 14 Support

There are currently some circumstances under which this app doesn't sync perfectly, particularly if devices are offline long periods of time. Currently the syncing is based on iOS 10 technology. Under iOS 13, there are improvements to the syncing of CloudKit records that could make this much more reliable and save over 1,000 lines of code from the app. The improvements would also make the OS responsible for detecting when the internet is available and initiating syncing.
To use these improvements, we need to change the target to iOS 13 or iOS 14. I did submit a set of changes to that effect a year ago that would have raised it to iOS 13. Given that the iPads will upgrade to iOS 14, I think it makes the most sense to target the app to iOS 14 and test accordingly, rather than supporting older iOS versions.

Hi @kirvanp ,
Could you resubmit the changes, we will look into integrate them into master.
Thanks

Fixing for current target.


add validation for very close node on road

Addresses issue #6241
Also made a change in inspector, so that when an untagged entity has issues, entity editor is shown to make the issues visible. Otherwise it's a confusing experience for users when they click on an item on the issues pane but don't see the issue show up in the inspector.
Using a cheap check by delta on lat/lon degrees, since 1-e5 degree is ~1 meter. Let me know if the great-circle geo-distance is preferred.
Tested in browser and see the issue gets flagged; also verified the merge operation works.

cc @wonga00 @chrisklaiber

Looks great, thanks @gaoxm 👍

Using a cheap check by delta on lat/lon degrees, since 1-e5 degree is ~1 meter. Let me know if the great-circle geo-distance is preferred.

Awesome, for such tiny distances there's no need to do great circle 😄


workaround defectdojo expecting a non-empty scanstarttime for their e…

…ngagments
fix #456

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

6 of 9 (66.67%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 41.637%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

components/consumers/defectdojo/main.go
6
9
66.67%

Totals

Change from base Build<PHONE_NUMBER>1:
0.006%

Covered Lines:
3378

Relevant Lines:
8113

💛  - Coveralls


Stack loading in reverse

Chris F pointed out to me something that is probably a bug, his controller is run correctly, but his stack is run in the reverse order.  I am still debugging it and will issue a PR if I solve it, but it looks like its related to the way this works:
array_pop and foreach while traversing the array.
array_pop takes the last thing added to the array (the controller) where foreach starts from the first thing in the stack (0). For each reads our routes in the correct order, but Slim's route handling runs middleware in the opposite order they are added... that is the last added is the first run.
For example if your array stack looked like this:
    route:
        stack:
            - auth
            - loader
            - processor
            - controller

the order it would run in is:

processor
loader
auth
controller

Pull request to fix this coming shortly

This resolved the issue for me. Thanks!


Custom Strategy Repo - just an idea

I think there should be a centralized repository (or website) of custom strategies that people have written for Gekko. This will benefit in two areas; it will give newbies like me a better understanding of how to write custom strategies for their own bots, and it will improve the strategies one has written through others testing and discussing their results

Great idea!
When/if people want to share strategies please send them to me (or post them here). I could create a page on the website where I list all of them. Or we could add them to the example strats:
https://gekko.wizb.it/docs/strategies/example_strategies.html

A few issues similar to this has have been posted in the past, but if not a lot of discussion is happening inside this issue I'm not sure if this is the best place for it.
We can also think about other discussion platforms for this:

I used to have an IRC channel for Gekko stuff, but I'd rather opt for something more web friendly.
Someone once made a subreddit for Gekko stuff: https://www.reddit.com/r/GEKKO/ (but I'm not sure if it was ever used)
We could have a forum? I'm just a bit worried about the time it would take to maintain.

What would people think would work?

Tbh, people can post their strats up on github, I found at least 1 that way. I'm trying to figure out the best way to do this for the GA as it happens, but now you've changed the API call so I need to re-test.
For me, it's not about sharing stats so much but the approach to working out what is the best approach to writing and testing your strat. For example, I'm a complete trading noob, but by looking at strat output data, mashing them together, tracking changes in trends via the console etc I can test and learn.
This works for me, and frankly I managed to come to the same conclusion as the GA on a couple of strats just using my puny human brain.

I was actually thinking about this a couple days ago when I was way off topic on an issue. I was thinking a forum would be perfect for discussion and also help people get proactive should they choose to do so. Setting up a web irc client is simple but with just a forum the information will be there for everyone to learn from. I really like the idea of a irc channel for people actively developing gekko but I feel in the end it would be more like live tech support.

I can throw up a forum if need be.

I have a discourse server already set up for comments on a blog that I never post to so the comments will never be used.  It wouldn't take but a few minutes to delete the old data out, remove the part on the blog that auto creates forums, and set up a couple of moderators.

I also asked in another issue which strategies did people use to let the newbies learn from others. I think this is a great idea.

What about Telegram? or slack? They seem to be pretty popular right now and many people probably are already on at least one

Im keen, where can we collab?

I just subbed in the reddit GEKKO.

@askmike this is kinda old

yes, for anyone interested in sharing strategies: head over to the forum :)

@askmike shouldn't this issue be closed?


CSS modules docs suggest using CSSModulesPlugin that does not exist

Documentation at https://github.com/fuse-box/fuse-box/blob/master/docs/plugins/css-modules.md instructs one to use CSSModulesPlugin. I'm fuse-box 3.5.0 and CSSModulesPlugin is gone. I got it working by following the docs but replacing CSSModulesPlugins with CSSModules.
I'm assuming the docs is out-of-date.

there is it
https://github.com/fuse-box/fuse-box/blob/master/src/plugins/stylesheet/CSSModules.ts
Could you help out updating the docs?


[HTTPD] support for multiple simultaneous requests (try 3)  (IDFGH-9868)

Related Issue: https://github.com/espressif/esp-idf/issues/10594
Previous PR: https://github.com/espressif/esp-idf/pull/10669
Add basic support for supporting multiple simultaneous requests in HTTPD server.
This is the 3rd try of this PR:

1st: worked well
2nd: tried to simplified the user api, but made things too complicated for the server code
3rd: went back to the first approach, with slightly cleaner api

Note: This PR does not add native support for simultaneous requests, but instead makes it more ergonomic for users to move a request to a thread that they must create themselves.
Advantages over raw sockets

easier reply: Users can use all the existing httpd functions (i.e. httpd_resp_sendstr) to send their response instead of raw socket send()
LRU safety: A long running async socket will not get closed from underneath us if we run out of sockets

Implementation:

an request handler will first call httpd_req_async_handler_begin()

this gives the user exclusive use of a new request object (to not interfere with the http server's request)
this will mark the socket as "in use" to guarentee the socket to not be LRU purged

async handler must call httpd_req_async_handler_complete() when done

this frees our request object.
this will mark the socket as "no longer in use" to allow it to be closed (LRU purged)

Example

add an example to ESP-IDF, showing usage.

@hmalpani

It works now.
I introduced a small bug right before pushing. 🤦
in httpd_req_async_handler_begin I was calling a memcpy out of order, overwriting a previous assignment.
bad code:
async->aux = malloc(sizeof(struct httpd_req_aux));
memcpy(async, r, sizeof(httpd_req_t)); // overwrites previous assignment.
memcpy(async->aux, r->aux, sizeof(struct httpd_req_aux));

I just had to move the 1st memcpy first before async->aux =.

sha=1289d69870dc5faee84756e168dbacdb59f62a4a

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

Hello @chipweinberger
Can you please sign the CLA agreement. Thanks!

signed

any updates? thanks

Hello @chipweinberger
I have created an internal MR which is under review. It will get reflected on GitHub once it gets merged.
Thanks!

perhaps I can split the PR up into 2 to make it be reviewed faster? Let me know if that would be better.

core changes (which is only a small diff in 4 files)
new example

perhaps I can split the PR up into 2 to make it reviewed faster? Let me know if that would be better.
1. core changes (which is only a small diff in 4 files)

2. new example

Hello @chipweinberger
The PR is already in review and should not take long before getting merged. So no need to update the PR.
Thanks!

PR has been merged into master via commit: 3824eba04dbdc1a962b9a039bbbb8df87436f682
Closing this PR.


ENH: Add param to report.add_epochs to report reject/flat

I think the value of the "reject" parameter should be included via upstream changes to mne.Report.add_epochs().

Originally posted by @hoechenberger in https://github.com/mne-tools/mne-bids-pipeline/issues/839#issuecomment-1917498418
In other words, epochs.reject and maybe epochs.flat could be useful to allow opt-in to reporting in add_epochs so people know what rejection has been done. See linked PR for how it's done in MNE-BIDS-Pipeline for example.

Hello @larsoner , I am Forcha Pearl from Cameroon. It's a pleasure meeting you.  I would love to participate in GSOC 2024 under mne-tools, Please is this what you mean ?
    @fill_doc
    def add_epochs(
        self,
        epochs,
        title,
        *,
        psd=True,
        projs=None,
        image_kwargs=None,
        topomap_kwargs=None,
        drop_log_ignore=("IGNORED",),
        tags=("epochs",),
        replace=False,
+       reject=epochs.reject
    ):

Not exactly -- I actually don't think we need any new parameter, but should just automatically always add a subsection that is basically the contents of this:
https://github.com/mne-tools/mne-bids-pipeline/blob/61b35530b16a61753b25fa663b575d9b2f7a6ed5/mne_bids_pipeline/steps/preprocessing/_09_ptp_reject.py#L215-L221
So just a new add_html in mne.Report._add_epochs, probably inside this conditional:
https://github.com/mne-tools/mne-python/blob/ae6e55e8eb41f080d6c209c129bb86ecdb2fc30d/mne/report/report.py#L3939
Probably need one for reject and one for flat.

Something like that. Not sure what kind is in your example -- that might be MNE-BIDS-Pipeline specific. Maybe try implementing something and running the report tutorial and see if it works as expected?


Add "Clone" button to date annotator in Comprehensive specimen digitization form

When I am parsing a date in Comprehensive specimen digitization form - having a "Clone" button for copying the start date to the end date would be very useful. Most collection objects have the same or very similar start and end dates - so cloning the first entry would save time.
Spec:

I would not enter the end date if it is the same with the start date. But clone button could be useful if only the day is different.

Idea: Maybe "click -> modal" -> [ +1 day, +2 days ] ...

@mjy probably over-complicating it to be honest. Harder to count # of days than to just modify the cloned date.

Agreed

Thanks!


Is pandaPIparser case-sensitive?

I notice with the following domain file that I get this message from the parser:
There is no declaration of the subtask drive-ta in the input
Method move-one-ta has the subtask (__t_id_3) drive-ta. The task is declared with 0 parameters, but 2 are given in the method.
There is no declaration of the subtask drive-ta in the input
Method move-more-ta has the subtask (__t_id_5) drive-ta. The task is declared with 0 parameters, but 2 are given in the method.

The action is declared using drive-TA with caps.  PDDL is case-insensitive, so I think HDDL should be also, shouldn't it?
Indeed, down-casing the action definition makes this message go away.
Here's the domain:
(define (domain toll-domain)
    (:requirements :negative-preconditions :typing :hierarchy)
  (:types
   location - object
   )
  (:predicates
   (toll-area ?r - region)
   (road ?arg0 - location ?arg1 - location)
   (at ?arg1 - location)
   (pay-location ?l - location)
   )

  (:task move
   :parameters (?l1 - location ?l2 - location)
         )

  (:method move-one
      :parameters (?l1 - location ?l2 - location)
    :task (move ?l1 ?l2)
    :ordered-subtasks (and
                       (drive ?l1 ?l2)
                       )
    )
  (:method move-more
      :parameters (?l1 ?l2 ?l3 - location)
    :task (move ?l1 ?l3)
    :ordered-subtasks (and
                       (drive ?l1 ?l2)
                       (move ?l2 ?l3)
                       )
    )
  (:method move-none
      :parameters (?l1 - location)
    :task (move ?l1 ?l1)
    :ordered-subtasks ()
    )
  (:method move-one-ta
      :parameters (?l1 - location ?l2 - location)
    :task (move ?l1 ?l2)
    :ordered-subtasks (and
                       (drive-ta ?l1 ?l2)
                       (pay-toll ?l2)
                       )
    )
  (:method move-more-ta
      :parameters (?l1 ?l2 ?l3 - location)
    :task (move ?l1 ?l3)
    :ordered-subtasks (and
                       (drive-ta ?l1 ?l2)
                       (move ?l2 ?l3)
                       (pay-toll ?l3)
                       )
    )

  (:action drive
   :parameters (?l1 - location ?l2 - location)
   :precondition
           (and
            (at ?l1)
            (pay-location ?l1)
            (road ?l1 ?l2)
            )
   :effect
           (and
            (not (at ?l1))
            (at ?l2)
            )
           )
  (:action drive-TA
   :parameters (?l1 - location ?l2 - location)
   :precondition
           (and
            (at ?l1)
            (road ?l1 ?l2)
            )
   :effect
           (and
            (not (at ?l1))
            (at ?l2)
            )
           )

  (:action pay-toll
   :parameters (?l - location)
   :precondition
           (and
            (at ?l)
            (pay-location ?l)
            )
   :effect ()
           )
  )

Yes, the current version of the parser is indeed case-sensitive. The build-in plan verifier is not case-sensitive (as IPC competitors did ignore case).
The other question would be whether the parser should be case-sensitive. As you correctly point out, PDDL is case insensitive - which would imply that HDDL should also be. I would ask the other PANDA authors whether we should make the change and then implement it. This might however take a while (due to vacation and the like). I hope this is not a problem for you?

I would say that the parser should be case-insensitive, but that making it case-insensitive is a low priority fix.
It is not a problem for me to make my domains correct when processed in a case-sensitive way.


New version: dail8859.NotepadNext version 0.7

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

@stephengillie
It does. For future reference, is it preferred to keep the 3 digit version numbering? Meaning it is preferable to use 0.7.0 rather than just 0.7?

Hi @dail8859,
I searched semantic versioning guidance and couldn't find advice on dropping a trailing zero. So this is left to developer discretion. And so is using semantic versioning.
The version number in the manifest has to match the Apps and features page, as in your screenshot. This is part of how installed versions are matched up with manifest versions, so our package manager knows if an upgrade is available.


[Question]Is it able to convert an existed VIP on Cloud Service classic mode to Reserved IP ?

Description
Is it able to convert an existed VIP on Cloud Service classic mode to Reserved IP ?

Environment summary

I realize we can done this by powershell from the article here: https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-reserved-public-ip
But seems no information to indicate if it is possible to achieve by CLI: https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-deploy-static-pip-arm-cli

CLI Version: What version of the CLI and modules are installed? (Use az --version)
CLI 2.0
OS Version: What OS and version are you using?
CentOS6.7 and by Azure Cloud Shell

CLI 2.0 only supports ARM. There is no support for the cloud service classic model. You could try releasing your classic model IP and then creating a static public IP address, which would create an ARM public IP resource with that address.

Hi Travis,
Thanks for your response.
Is it possible to achieve this by CLI 1.0 or other version ?
Regards,
-Jack

I've asked around and it seems like your best options are to use the Azure PowerShell.  I understand this is not ideal (especially for a Linux user).
New-AzureReservedIP –ReservedIPName MyReservedIP –Location "Central US" -ServiceName TestService

or use CURL to call the REST API, but I honestly don't know where to look up the REST API for the ASM (non-ARM) endpoints.

Closing this, but if you find yourself blocked, don't be afraid to reach out again!


query matchrule

The current set of match rules allows only to check for string equality. This causes a problem in the uri's query when the query is semantically identical but due to a different order of the parameters the string representation is not.
For example:
http://freeside.co/betamax?p=2&q=1vs http://freeside.co/betamax?q=1&p=2.
I follow up with a PR to address the previously described issue.

+1 +1

#207 was merged. Closing...


Add drawings for aortic diseases

I love what this project is doing, great work! Please add drawings icons for

[ ] aortic dissection
[ ] aortic intramural hematoma
[ ] penetrative Atherosclerotic ulcer
[ ] Stanford classification of aortic dissection

Thank you and keep up the good work!

@SterArcher I'll draw these and donate them to the project. Always love open-source projects like this, just give me a few weeks to create them as I'll have some free time coming up.


Add defensive importance sampling

Use a mixture distribution with a flow, and a "defensive distribution".
The defensive distribution should help with the regions where the flow misses important parts of the target (initially during training) or if the tail of the flow is overly light in certain regions.

Done in my current branch. Briefly tested on MoG problem - seems to help for FAB without the replay buffer, but with the replay buffer couldn't see an obvious huge difference.
We can include the optional feature for now and potentially do a more rigorous testing of it in the future.


word vectors  embedding

Description
What steps will reproduce the problem?

glove_dir = '/Artifical Intelligence/RNN/Datasets_RNN/glove.6B'
embedding_index = {}
f = open(os.path.join(glove_dir, 'glove.6B.100d.txt'), encoding = 'utf8')
for line in f:
values = line.split()
word = values[0]
coefs = np.asarray(values[1:], dtype = 'float32')
embedding_index[word] = coefs
f.close()
Traceback
Traceback (most recent call last):
  File "/Users/pavankumar/anaconda3/lib/python3.11/site-packages/spyder/plugins/variableexplorer/widgets/collectionsdelegate.py", line 171, in createEditor
    editor.setup(value, key, icon=self.parent().windowIcon(),
  File "/Users/pavankumar/anaconda3/lib/python3.11/site-packages/spyder/widgets/collectionseditor.py", line 1486, in setup
    self.widget = CollectionsEditorWidget(self, self.data_copy,
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/pavankumar/anaconda3/lib/python3.11/site-packages/spyder/widgets/collectionseditor.py", line 1418, in __init__
    self.editor = CollectionsEditorTableView(self, data, readonly,
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/pavankumar/anaconda3/lib/python3.11/site-packages/spyder/widgets/collectionseditor.py", line 1288, in __init__
    self.source_model = CollectionsModelClass(
                        ^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/pavankumar/anaconda3/lib/python3.11/site-packages/spyder/widgets/collectionseditor.py", line 156, in __init__
    self.set_data(data)
  File "/Users/pavankumar/anaconda3/lib/python3.11/site-packages/spyder/widgets/collectionseditor.py", line 186, in set_data
    self.keys = sorted(list(data.keys()), key=natsort)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/pavankumar/anaconda3/lib/python3.11/site-packages/spyder/widgets/collectionseditor.py", line 85, in natsort
    x = [int(t) if t.isdigit() else t.lower() for t in re.split('([0-9]+)', s)]
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/pavankumar/anaconda3/lib/python3.11/site-packages/spyder/widgets/collectionseditor.py", line 85, in <listcomp>
    x = [int(t) if t.isdigit() else t.lower() for t in re.split('([0-9]+)', s)]
         ^^^^^^
ValueError: invalid literal for int() with base 10: '₂'

Versions

Spyder version: 5.4.3  (conda)
Python version: 3.11.5 64-bit
Qt version: 5.15.2
PyQt5 version: 5.15.10
Operating System: Darwin 23.5.0

Dependencies
# Mandatory:
applaunchservices >=0.3.0                        :  0.3.0 (OK)
atomicwrites >=1.2.0                             :  1.4.0 (OK)
chardet >=2.0.0                                  :  4.0.0 (OK)
cloudpickle >=0.5.0                              :  2.2.1 (OK)
cookiecutter >=1.6.0                             :  2.5.0 (OK)
diff_match_patch >=20181111                      :  20200713 (OK)
intervaltree >=3.0.2                             :  3.1.0 (OK)
IPython >=7.31.1,<9.0.0,!=8.8.0,!=8.9.0,!=8.10.0 :  8.20.0 (OK)
jedi >=0.17.2,<0.19.0                            :  0.18.1 (OK)
jellyfish >=0.7                                  :  1.0.1 (OK)
jsonschema >=3.2.0                               :  4.19.2 (OK)
keyring >=17.0.0                                 :  23.13.1 (OK)
nbconvert >=4.0                                  :  7.10.0 (OK)
numpydoc >=0.6.0                                 :  1.5.0 (OK)
parso >=0.7.0,<0.9.0                             :  0.8.3 (OK)
pexpect >=4.4.0                                  :  4.8.0 (OK)
pickleshare >=0.4                                :  0.7.5 (OK)
psutil >=5.3                                     :  5.9.0 (OK)
pygments >=2.0                                   :  2.15.1 (OK)
pylint >=2.5.0,<3.0                              :  2.16.2 (OK)
pylint_venv >=2.1.1                              :  2.3.0 (OK)
pyls_spyder >=0.4.0                              :  0.4.0 (OK)
pylsp >=1.7.2,<1.8.0                             :  1.7.2 (OK)
pylsp_black >=1.2.0                              :  1.2.1 (OK)
qdarkstyle >=3.0.2,<3.2.0                        :  3.0.2 (OK)
qstylizer >=0.2.2                                :  0.2.2 (OK)
qtawesome >=1.2.1                                :  1.2.2 (OK)
qtconsole >=5.4.2,<5.5.0                         :  5.4.2 (OK)
qtpy >=2.1.0                                     :  2.4.1 (OK)
rtree >=0.9.7                                    :  1.0.1 (OK)
setuptools >=49.6.0                              :  68.0.0 (OK)
sphinx >=0.6.6                                   :  5.0.2 (OK)
spyder_kernels >=2.4.3,<2.5.0                    :  2.4.4 (OK)
textdistance >=4.2.0                             :  4.2.1 (OK)
three_merge >=0.1.1                              :  0.1.1 (OK)
watchdog >=0.10.3                                :  2.1.6 (OK)
zmq >=22.1.0                                     :  25.1.0 (OK)

# Optional:
cython >=0.21                                    :  3.0.9 (OK)
matplotlib >=3.0.0                               :  3.7.4 (OK)
numpy >=1.7                                      :  1.26.2 (OK)
pandas >=1.1.1                                   :  2.2.2 (OK)
scipy >=0.17.0                                   :  1.11.4 (OK)
sympy >=0.7.3                                    :  1.11.1 (OK)

Hi @Pavun-KumarCH thank you for the feedback! Seems like inside your data a 2 is being represented with a '₂' which generates a ValueError over the logic used to parse variables. Did the error appear when trying to see or maybe edit some variable generated by your code? Could it be possible for you to share a self-contained example that could help us reproduce this locally (the code you posted over the OP requires some data in a specific directory structure)?
Any further info to help us better understand this is greatly appreciated. Let us know!

It was Fixed! Thank You
On Wed, Jul 24, 2024 at 12:50 AM Daniel Althviz Moré <
@.***> wrote:

Hi @Pavun-KumarCH https://github.com/Pavun-KumarCH thank you for the
feedback! Seems like inside your data a 2 is being represented with a '₂'
which generates a ValueError over the logic used to parse variables. Did
the error appear when trying to see or maybe edit some variable generated
by your code? Could it be possible for you to share a self-contained
example that could help us reproduce this locally (the code you posted over
the OP requires some data in a specific directory structure)?
Any further info to help us better understand this is greatly appreciated.
Let us know!
—
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/22275#issuecomment-2246109490,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFIYH7QADAPBQQNBUWIIBNLZN2UGXAVCNFSM6AAAAABLGZAR7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBWGEYDSNBZGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@ccordoba12 should we close this or maybe is worthy to further investigate/add a way to handle this kind of error?

Since still no handling has been implement for this kind of error (variables could end up with data that can trigger an error when trying to construct a graphical representation of them) I'm reopening this. Please don't close it @Pavun-KumarCH)


IcPopover When placed in component smaller than itself it stretches component

When IcPopover is placed in a component of fixed height smaller than the size of the popover the component will scroll to show the popover rather than the popover appear above the component as with MUI popover.

@MI6-613 could you provide a code example please and if you had any more information

Closing this issue, please reach out if you have more information.


x509 error: certificate is not valid for any names

Bug description
When I try to add a helm repository via the interface, I get a openssl error.
The error is
"https://fantastic-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Head "https://fantastic-charts.storage.googleapis.com/index.yaml": x509: certificate is not valid for any names, but wanted to match fantastic-charts.storage.googleapis.com for every repo I try to add.
If I add the repo in command line on my node it works without problem.
The bitnami repo is not displayed too, I don't know if it is related.
Expected behavior
I expect to be able to add any repository I want to use them in portainer.
Portainer Logs.
There is no associated logs
Steps to reproduce the issue:

Go to Helm section
Click on the input field and add the url of your repository
Click on add repository
See error in the toast at top right of the screen

Technical details:

Portainer version: 2.17.1 BE
Docker version (managed by Portainer):
Kubernetes version (managed by Portainer): 1.26.1
Platform (windows/linux): linux
Command used to start Portainer : helm repository
Browser: Brave
Use Case (delete as appropriate): Using Portainer at Home
Have you reviewed our technical documentation and knowledge base? Yes

Additional context
My kubernetes installation was made with microk8s.
There is no SSL certificate in the settings related section.

Thanks for your answer.
I am not running a load balancer or using a reverse proxy to acces it, it was done with a port-forward with kubectl on http port

@0xMemoryGrinder
I am unable to reproduce.  Please see testing.
Environment:
Docker Standalone Portainer Server 2.17.1
Portainer Agent K8s 2.17.1
https://user-images.githubusercontent.com/20426210/225479582-d8457c42-fdc3-4e1c-b059-b521f7ba42f6.mov
Environment:
K8s Portainer Server 2.17.1
Local
https://user-images.githubusercontent.com/20426210/225479613-804d35c5-b994-4278-bb3a-bb852e7442d0.mov
Note:  I am installing Portainer Server and Portainer Agent via the Node Port method.

I think this is kinda related to microk8s as I continued to setup my cluster and grafana is generating the same error when I try to fetch a pre-built dashboard.
Could you retry with microk8s ?
Thanks in advance.

After days of digging, I finally found. The dns configuration was messing the certificates.
All requests were redirected to my public ip address (see below how to check if you have the same problem and how to fix it) so when the system that made the request was veryfing the certificate to the issuer, it was poorly failing because the IP was not correct (e.g. not the google registered ones)
How to check if this is my problem
My problem was in the dns configuration in the /etc/resolv.conf file.
The content of the file was
search mydomain.tld
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>

How to solve
Removing the first line containing my domain solves the problem. I did not investigate further, but I think this can works too if you move it after the nameservers list
Sorry @tamarahenson to have wasted your time.

@0xMemoryGrinder
Thank you for the update and additional information.  I am glad to hear you are able to move forward.  I am going to close this for now.  Please re-open if needed.
Thanks!


"inappstore" vulnerability. Please upgrade it from Store Kit 1 to Store Kit 2

There is a vulnerability with the current "inappstore" plugin.
Unlike the Google Play Billing plugin, there is no way to query_purchases() and find out what the user has purchased/subscribed to when the app starts up. This is due to the plugin using StoreKit 1. Apple's StoreKit 2 provides functionality out of the box that allows the user to easily query all past purchases. This plugin should be upgraded to use StoreKit 2.
I assume that most Godot game developers using this plugin have the following logic:
func check_events():
	while in_app_store.get_pending_event_count() > 0:
		var event = in_app_store.pop_pending_event()
		if event.type == "purchase":
			if event.result == "ok":
				// save a local variable somewhere that "purchased = true"

Some notes about this:

For consumable purchases, this is no problem
For "permanent" purchases, this should mostly work. But if a malicious player buys and then quickly refunds your item, you would have no way of telling. There is no "event fired" in StoreKit 1. To detect refunds, you would need to maintain your own server infrastructure that is constantly in contact with Apple's servers, and your app would have to contact your server to revoke the premium features. I guarantee this is out of scope for most Godot game developers.
For "auto-renewing subscriptions", simply being able to read basic information like expiry_date involves maintaining your own server that can do receipt validation. If you want it to detect refunds, renewals, or cancellations, you need to implement the whole App Store Server Api on your server infrastructure. It's a mess.

The new StoreKit 2 is designed to simplify this whole process. You can simply query purchases through the Transaction History methods and get a list of active purchases - that's it! Here's a breakdown:

Transactions retrieved through StoreKit 2 include detailed information such as product identifiers, purchase dates, and expiration dates for subscriptions, all in a decoded and easy-to-use format. This information was previously only obtainable by decoding the opaque receipt file.

Developers can access the complete transaction history, which provides the context necessary for supporting features like restoring purchases or verifying the entitlements of a user at any point in time.

StoreKit 2 requires iOS 15+, but it is installed on 99%+ of iOS devices. No compatibility concerns there. Creating a StoreKit 2 branch would make it a lot easier for your average solo developer or small studio to monetize their Godot games.

Related to https://github.com/godotengine/godot-ios-plugins/issues/17.

I am the primary earner for my family, and I make 100% of my income from my mobile games. All of my games are made in Unity, but I have been in the process of converting all my games over to Godot ever since the "20 cents per install" fiasco. I almost finished porting my first game over to Godot. When it finally came time to add the "monetization features" to my game (which is how I earn any money from my games) everything came to a screeching halt.

The Android Billing plugins had no active maintainers, and were so outdated that they technically became deprecated on Wednesday. I had to spam posts all over various Godot communities to even get a maintainer to "hack a temporary workaround" on the final day of deprecation. Even with the workaround, the plugin is still deprecated, and there are still no active maintainers.
The iOS plugins don't have any contributors, so the plugins are 'rotting'.
There is only one ad monetization plugin to choose from, maintained by a single dude. I don't like the idea of that.

Constructive criticism: What I've come to realize is that Godot is great for devs selling games on Steam, but for anyone who makes their income with mobile games, Godot is essentially a non-option. The features that mobile devs need are totally neglected and rotting, and have been for a while. These plugins need to be higher priority for Godot's development team, if they want mobile devs to use Godot. Maybe the Godot team doesn't care and just wants people to make Steam games - and that's fine, I must have gotten the wrong impression. The development fund is at €50,000+ per month, where are all the contributors?

This has been lacking contributors and is pushing people away from Godot. Is there any way we can all chip in an just pay someone to take care of it. Been over 6 months with no updates or timeline. Godot is amazing and its just going to fade if independent devs cant monetize.

Is there any way we can all chip in an just pay someone to take care of it.

While you are free to contact a developer and pay them (including through a crowdfunding campaign you host), we don't use a bounty system. This is something you will have to organize on your own, including finding that developer and ensuring they do their work correctly. There's a lot of risk involved in this process by design.

I am more than willing to work on the iOS plugins if I can successfully find some information on how to code them. Just give me some time.

almost finished with it ! no worries :)

@dinopanagos hey, did you make any progress on this? If so, would you mind sharing the files?

See:
https://github.com/rktprof/godot-ios-extensions


Email Echo Service

Initial start for setting up echo emails. This is lays the groundwork and wiring for the implementation of template for services.
Resolves https://github.com/ascoderu/lokole/issues/13

Codecov Report

Merging #324 into master will decrease coverage by 2.45%.
The diff coverage is 36.84%.

@@            Coverage Diff             @@
##           master     #324      +/-   ##
==========================================
- Coverage   98.75%   96.29%   -2.46%
==========================================
  Files          14       15       +1
  Lines        1205     1243      +38
==========================================
+ Hits         1190     1197       +7
- Misses         15       46      +31

Impacted Files
Coverage Δ

opwen_email_server/config.py
100% <100%> (ø)
:arrow_up:

opwen_email_server/actions.py
95.18% <20%> (-4.82%)
:arrow_down:

opwen_email_server/utils/format.py
50% <50%> (ø)

opwen_email_server/services/auth.py
98.4% <60%> (-1.6%)
:arrow_down:

opwen_email_server/services/sendgrid.py
94.4% <0%> (-5.6%)
:arrow_down:

Continue to review full report at Codecov.

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

Thanks for all the patience. This is good to go. Going to merge it once I'm done with the big monorepo move.

Added Sendgrid Inbound Parse configuration:


[Documentation] Make changes to contributing guide

Describe how this feature will help us improve

On the docs, it says to create a new branch from your master branch instead of working directly on the master branch of your forked. I think this line should be changed to reflect develop instead of master.
The format for naming will cause an issue as git will throw an error. It's important to tell the user to make use of the escape slash (\) or the other different ways discussed here while trying to name a branch.

This will make it easier for a new contributor to make a PR
Is your proposal related to a problem?
No
Describe the solution you'd considered

Change the text from the master branch to develop branch.
Include the different options of avoiding git error while trying to name a branch using the #-issue-num-branch-name method.

@peoray thank you for reporting an issue! Docs indeed need some update :)


not able to run inference on the docker

When I ran "sudo docker-compose up -d --build" and use  docker-compose logs -f to check, I got the following errors:
My system has 32 GB DRAM and TitanX GPU, 12GB VRAM:
h2ogpt-h2o-llm-1  |     python generate.py --base_model='togethercomputer/GPT-NeoXT-Chat-Base-20B' --prompt_type='human_bot' --lora_weights='GPT-NeoXT-Chat-Base-20B.merged.json.8_epochs.57b2892c53df5b8cefac45f84d019cace803ef26.28'
h2ogpt-h2o-llm-1  |
h2ogpt-h2o-llm-1  |
h2ogpt-h2o-llm-1  | Using Model eleutherai/gpt-j-6b
h2ogpt-h2o-llm-1  | Get EleutherAI/gpt-j-6B model
h2ogpt-h2o-llm-1  | Traceback (most recent call last):
h2ogpt-h2o-llm-1  |   File "/workspace/generate.py", line 1515, in
h2ogpt-h2o-llm-1  |     fire.Fire(main)
h2ogpt-h2o-llm-1  |   File "/usr/local/lib/python3.10/dist-packages/fire/core.py", line 141, in Fire
h2ogpt-h2o-llm-1  |     component_trace = _Fire(component, args, parsed_flag_args, context, name)
h2ogpt-h2o-llm-1  |   File "/usr/local/lib/python3.10/dist-packages/fire/core.py", line 475, in _Fire
h2ogpt-h2o-llm-1  |     component, remaining_args = _CallAndUpdateTrace(
h2ogpt-h2o-llm-1  |   File "/usr/local/lib/python3.10/dist-packages/fire/core.py", line 691, in _CallAndUpdateTrace
h2ogpt-h2o-llm-1  |     component = fn(*varargs, **kwargs)
h2ogpt-h2o-llm-1  |   File "/workspace/generate.py", line 249, in main
h2ogpt-h2o-llm-1  |     go_gradio(**locals())
h2ogpt-h2o-llm-1  |   File "/workspace/generate.py", line 490, in go_gradio
h2ogpt-h2o-llm-1  |     model0, tokenizer0, device = get_model(**all_kwargs)
h2ogpt-h2o-llm-1  |   File "/workspace/generate.py", line 358, in get_model
h2ogpt-h2o-llm-1  |     device = get_device()
h2ogpt-h2o-llm-1  |   File "/workspace/generate.py", line 256, in get_device
h2ogpt-h2o-llm-1  |     raise RuntimeError("only cuda supported")
h2ogpt-h2o-llm-1  | RuntimeError: only cuda supported
h2ogpt-h2o-llm-1  | /usr/local/lib/python3.10/dist-packages/torch/cuda/init.py:107: UserWarning: CUDA initialization: Unexpected error from cudaGetDeviceCount(). Did you run some cuda functions before calling NumCudaDevices() that might have already set an error? Error 804: forward compatibility was attempted on non supported HW (Triggered internally at ../c10/cuda/CUDAFunctions.cpp:109.)
h2ogpt-h2o-llm-1  |   return torch._C._cuda_getDeviceCount() > 0
h2ogpt-h2o-llm-1  | /usr/local/lib/python3.10/dist-packages/bitsandbytes/cextension.py:33: UserWarning: The installed version of bitsandbytes was compiled without GPU support. 8-bit optimizers, 8-bit multiplication, and GPU quantization are unavailable.
h2ogpt-h2o-llm-1  |   warn("The installed version of bitsandbytes was compiled without GPU support. "

@arnocandel
Any idea how to fix this issue?

Thanks,

The installed version of bitsandbytes was compiled without GPU support suggests that something is wrong with the base CUDA installation.
We updated the instructions, make sure to follow all steps: https://github.com/h2oai/h2ogpt/blob/main/INSTALL-DOCKER.md
Also, 12GB VRAM and older generation cards might not work, we develop and test on 3090/4090/A6000/A6000Ada/A100 only.


Remove old prerelease API Vision packages

The features from Google.Cloud.Vision.V1P{1,2}Beta1 are now in Google.Cloud.Vision.V1, so the source for those betas can be removed.
The NuGet packages have been delisted.
This should not affect any users who are still using the packages - they can still be restored from NuGet, they just aren't suggested any more.

The Travis failure (and AppVeyor when it gets that far) is due to the way we build PRs: we find out which projects have changed, and build those. In this case, the two "changed" projects are the deleted ones, which obviously can't be built...


text-splitters: refactor if-elif to mapping

Description: Using mapping to accelerate process

Hello @eyurtsev,
I used mapping to avoid unnecessary transitions between the (if-elif-else) blocks. I believe that using mapping in this case is beneficial because there are no complex statements to check. Even if the difference is slight, mapping operates faster.
How can I provide you with evidence to verify this?


Symbols are displayed very large.

Vscode has changed the behavior of before/after decoration attachments such that the attachment no longer inherits the font-size of the hidden text. The hack we are using is: shrink text so that it is hidden, apply a decoration attachment, and set the font size on the decoration to be very large (to undo shrinking the original text). The result is that symbols now appear very big.

Fixed in release 0.4.1


spec assertion failures blot out stdout, such as p

(I was hoping Crystal wouldn't learn automated testing tips from Python, but...)
When I put a p variable in a spec and run it, the output appears amid the dots .
But when the spec fails an assertion, it eats all the stdout, then displays the assertion's diagnostic. This problem does not help me diagnose why the assertion is failing!
$ crystal -v
Crystal 0.30.1 [5e6a1b672] (2019-08-12)
LLVM: 4.0.0
Default target: x86_64-unknown-linux-gnu

Hi! Could you provide some code that reproduces the issue?

Nope; the problem went away. The p is spewing correctly.
I guess I was passive-aggressively wishing I could report this bug to Python-land, where it's really annoying.


How do I handle the connect authorization for a new account?

Issue Summary
I'm trying to setup a Standard connect flow but with Customer, Account, UserAccount models and actions of customers.create and actions.create neither looking like what I need, I'm not sure of how to handle the authorization redirect.  So far I have this:
class ConnectAuthorize(LoginRequiredMixin, TemplateView):

    def get(self, request, *args, **kwargs):
        auth_code = request.GET.get("code")
        if auth_code:
            url = "https://connect.stripe.com/oauth/token"
            data = dict(
                client_id=settings.PINAX_STRIPE_CA_TOKEN,
                client_secret=settings.PINAX_STRIPE_SECRET_KEY,
                code=auth_code,
                grant_type="authorization_code"
            )
            response = requests.post(url, params=data)
            data = response.json()
            account = Account.objects.get_or_create(
                stripe_id=data["stripe_user_id"],
                user=request.user,
                stripe_publishable_key=data["stripe_publishable_key"]
            )
            accounts.sync_account(account)
            customers.create(self.request.user, account=account)
            messages.success(request, "Successfully connected to Stripe")
        else:
            messages.error(request, "There was an error connecting to your Stripe account")
        return redirect("pinax_stripe_connect")

This makes me feel like we are missing an action or that we need to update one of the existing actions.
In this view the request.user could already have a customer as they may be paying for the service that allows themselves to sell their wares, so I think we have to "get or create" their customer object.
I think we should have an action like:
accounts.connect(request.user, **data)

That handles the complexity for the site dev of determining:

if the user has a customer record already, if so using it, if not, creating it
creating the account object and syncing the details
doing something with the UserAccount object whatever that is

@ticosax @lukeburden @blueyed Thoughts?

In the scenario, I'd like to support, a request.user will be a Customer once they purchase.
Once they purchase, they'll have a customer created for them and be linked.
Once they've purchased, they'll then be able to use the Standard connect method and link their Stripe account so that they can charge their customers on our platform.  So during the connect phase, our customers will most likely already have a customer object and I need to create the Account object and link it to their customer object.
It's still not clear what the point of the UserAccount model is for but the actions seem to assume that that is populated to link the two, however, the customer object already has an FK to Account, which I'm thinking all I need to populate.
Any ideas?

I think I get what's going on now.

customer.stripe_account is the stripe account id of the connected account that customer belongs to
UserAccount allows for account owner users to have more than 1 connected account and a mapping of their customers back to users
The connecting of an Account by a user doesn't need to involve a customer at all:

class ConnectAuthorize(LoginRequiredMixin, TemplateView):

    def create_account(self, user, stripe_user_id, stripe_publishable_key):
        defaults = dict(
            user=user,
            stripe_publishable_key=stripe_publishable_key
        )
        account, created = Account.objects.get_or_create(
            stripe_id=stripe_user_id,
            defaults=defaults
        )
        if not created:
            for key in defaults.keys():
                setattr(account, key, defaults[key])
            account.save()
        accounts.sync_account(account)
        return account

    def get(self, request, *args, **kwargs):
        auth_code = request.GET.get("code")
        if auth_code:
            url = "https://connect.stripe.com/oauth/token"
            data = dict(
                client_id=settings.PINAX_STRIPE_CA_TOKEN,
                client_secret=settings.PINAX_STRIPE_SECRET_KEY,
                code=auth_code,
                grant_type="authorization_code"
            )
            response = requests.post(url, params=data)

            data = response.json()
            self.create_account(
                request.user,
                data["stripe_user_id"],
                data["stripe_publishable_key"]
            )

            messages.success(request, "Successfully connected to Stripe")
        else:
            messages.error(request, "There was an error connecting to your Stripe account")
        return redirect("pinax_stripe_connect")

Am I thinking about this properly?

Hi @paltman - your first and third points are correct. I'll let @blueyed and @ticosax comment on the UserAccount model as they required it, but I think you're more or less on the money there too.

UserAccount is mainly there for the though model, and that is only supported with m2m.
While it allows for multiple users per customer (or vice-versa), it typically is a single one only, but per Account.


failed to make complete framebuffer object 8cd6

Thank you for creating a really good library.
I made a big size view.(2,300, 1800)
However, the following situation has occurred :
How can I solve this problem?

is that resolution in pts or px? I've tested up to the px size of the iPad Pro (2732 x 2048px, 1368 x 1024pt). I suspect you're above the max allowed texture size for the device, which I believe is around 2048 pts)

You're right.
I did not know the max allowed texture size for the device. That the maximum size of texture is 2048. When I think of the size, I realize that the size of texture is too big for me, so how should I handle it?
And is there a way to make a larger Canvas using a bunch of smaller texture?

There are two options that I can think of. The first would be to create a 2nd JotView and layout next to the first. This'll be tricky to handle drawing strokes that cross that boundary, but theoretically is possible.
The second option would be to create a JotView with the correct width/height ratio, then use a transform to scale the JotView's texture to the correct visible size.

Thank you for your kind reply.
I thought you'd do it as well as you told me.
Of course I'm not convinced of myself, but I'm more confident when I hear your words.
I think the first method would be much better than the second one.
I guess there's a lot of work to do, but I think it's worth challenging.
The first method didn't seem to be able to produce prototypes quickly, so I tried to test them in the second way.
Moreover, the performance was worse than expected, and the quality was poor.
Of course I can't make it because I can't make it, but I want to improve it.
I'll try to make lots of attempts.
Of course I haven't even understood your code yet.
Thank you !

good luck and lmk what you end up with! i'll close out this issue, but feel free to open another as questions arise


[v2] Add TypeScript Support

Support TS with type declarations.

:tada: This issue has been resolved in version 1.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Adding click telemetry for new database dialog

Adding the following telemetry:

On click of "New database dialog"

Not required as similar telemetry is already being captured by ADS.


Coded Value Domain Description Not Shown in Viewer Mode

This is from a student in my course.
"When creating domains for this project I had two that I used "Coded Value Domain" for, the "Problem" and "Injured" domains. I had a few (~5) different options for these (Fire, Damaged Road, Power Line down or Minor Injury, Moderate Injury etc) so obviously there'd be 1-5 for codes for each. After uploading the feature layer to a web map and subsequently the GeoForm Web App, I noticed the Geo Form only displayed the actual code, not the description. So when a user went to view submissions they would see this:

From a purely operational standpoint this looks like it says "2 Injured" when in reality it means "Yes [there are injured], minor injuries" which could be quite misleading.
The thing is, the web map this app uses displays the information properly:

I don't completely know what is going on here but I thought I'd bring it to your attention. IT looks like it might be an issue with the App itself. Let me know if there are any solutions. "

We'll get this working better in 4x version


An introduction to gene expression and RNA sequencing

At the meeting last night, several people were interested in learning more about the biology underlying gene expression and RNA sequencing. The following links provide an introduction to these topics, and may be of interest.
Wikipedia - Gene Expression
Wikipedia - RNAseq
RNA molecules are sometimes called transcripts, and all of a cell's RNA are collectively referred to as the transcriptome. The work we are doing with the sequencing data falls under the umbrella of 'transcriptomics'.
NIH Transcriptome Fact Sheet
One of the reasons that that the data is so difficult to interpret is that genes are involved in many interconnected regulatory networks. If you are interested in learning more about this, here is some preliminary info.
NIH - Biological Pathways Fact Sheet
Wikipedia - Gene regulatory network
Finally, we also talked about technical confounders that influence the data. This (open access) review article introduces batch effects in RNAseq data.
Leek et al 2010

Here is an MIT Open Courseware Lecture on RNAseq analysis - in case anyone is interested!


DSO: Fix the VMS DSO name converter to actually do something

This function has never before actually done its work.  This wasn't
discovered before, because its output wasn't important before the FIPS
provider self test started using its value.
This function is now made to insert the VMS DSO extension (".EXE") at
the end of the filename, being careful to make sure what can be a
typical VMS generation number (separated from the file name with a
';') remains at the end.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Pushed.


Build minified and unminified bundles

I've defaulted to the minified version (by setting that as .browser in package.json), which I think is probably preferable, but up for debate.

Debatable indeed because the browser field is always used by the bundler like browserify/webpack.
I've also suddenly realized that we'd want to use the source version in our own code (to dedupe the bluebird/lodash/etc) which will contradict with the browser field (as it will provide the UMD bundle instead).
What do you think?

Mmm, this is interesting. I haven't really been thinking about downstream bundling concerns, because if you're bundling downstream generally you don't want us to provide a browser bundle.
As you mention for in the UI case, for example, we really want to just depend on the raw source so that everything gets deduped and you can control bundling yourself, and I think that probably holds for nearly 100% of other bundling users too. I can't think of any reason you'd normally want the bundle in these cases.
Given that, the use case for the bundle is in non-commonjs bundled environments - raw globals, requirejs, maybe more exotic things. I don't think any of other options use the browser field, so we should actually just drop it entirely, and have everything that uses package.json get the non-bundled version, and people use the bundled version only when they're setting things up manually. Does that sound reasonable?

Yes I think that's the proper way to go.
On Tue, Jan 10, 2017 at 7:18 PM, Tim Perry<EMAIL_ADDRESS>wrote:

Mmm, this is interesting. I haven't really been thinking about downstream
bundling concerns, because if you're bundling downstream generally you
don't want us to provide a browser bundle.
As you mention for in the UI case, for example, we really want to just
depend on the raw source so that everything gets deduped and you can
control bundling yourself, and I think that probably holds for nearly 100%
of other bundling users too. I can't think of any reason you'd normally
want the bundle in these cases.
Given that, the use case for the bundle is in non-commonjs bundled
environments - raw globals, requirejs, maybe more exotic things. I don't
think any of other options use the browser field, so we should actually
just drop it entirely, and have everything that uses package.json get the
non-bundled version, and people use the bundled version only when they're
setting things up manually. Does that sound reasonable?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/resin-sdk/pull/253#issuecomment-271620582,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgGCC6d7dUr8DArJDjKleh1OQ_DPgMEks5rQ69zgaJpZM4LfhQ4
.

--
Eugene Mirotin
Senior Frontend Engineer
site: Resin.io https://resin.io/, twitter: @resin_io
https://twitter.com/resin_io

Ah, wait. There's still the other module-exclusion bundling problem. The config in this module currently lets us exclude some of its deps, which keeps downstream bundles smaller, and we don't share any of that info if we don't use the bundle when bundling downstream. Interesting...
This is where the browser field is supposed to come in: if we point it at source that never even require()s the modules we want to exclude (i.e. statically never even considers requiring them, rather than just hiding it behind an IS_BROWSER test) then browserify won't ever try to include them at all, even downstream. In principle that's doable with some refactoring, but it's a fairly wide ranging change. We'd need to build browser/non-browser versions of the relevant bits of this module and the other used resin modules, so that as browserify walks the tree it never sees rindle, for example.
For now though, as above, I think we still want to drop the browser field. Note that this means we're expecting downstream consumers to manually exclude modules though (but that's ok since the main downstream consumer right away will be us). We can pick up a separate task later to provide browserify/webpack-friendly builds with automagically exclude the right dependencies, since that's a larger job and it should be easily backward compatible anyway.
I've now pushed a browser-less update. Let me know if you're happy with all this and I'll merge and file an issue to look at the rest later.

We can pick up a separate task later to provide
browserify/webpack-friendly builds with automagically exclude the right
dependencies, since that's a larger job and it should be easily backward
compatible anyway.

Yeah I've mentioned that as a nice to have thing though I don't know yet
how to implement it properly.
Anyway right now the only browser consumer is us indeed so in the works
case other users would just get suboptimal bundle size.
LGTM to merge.
Could you also add a small section to the readme listing the modules that
can be safely dropped when bundling for the browser?
--
Eugene Mirotin
Senior Frontend Engineer
site: Resin.io https://resin.io/, twitter: @resin_io
https://twitter.com/resin_io

Readme note added, merging.


Remember previously opened folders

For now we need to re-open the folders manually after reloading the page.
Maybe the previous folder should be automatically opened is possible (best effort). That could be convenient for those always working with the same folder.
This could also be made opt-in or opt-out via the settings.

Maybe we can change the behavior introduced in this commit, and instead of .cd('/') do a .cd( to the stored directory.
Ideally we would store the state on a per-root basis.


Transformed in package

Hi, I've made some changes to your project, hope you accept my pull request.
Principal Changes:

Transformed the executables in embedded resources. This way we can ship them directly inside the dll and we don't have to worry with paths on disk. It enables the project to be packaged and published to Nuget.org;
Created a solution with Visual Studio to help manage package stuff;
Create an MIT License to allow the package to be publish in Nuget.org;
Published on Nuget at https://www.nuget.org/packages/PhantomJs.NetCore/;

Hi there @JoaoLucasGtr
This is really amazing. I would be more than happy to merge.
Left comments for just some cosmetic changes and I'd be merging this.
Also would you be able to add some docs to the README.cs file regarding how to install and use it in a project. Because that is really going to help allot of people. I know its really basic but for the sake of completeness.

Hey, I've applied the cosmetic changes you requested. It really looks better now.
I didn't touch the README.md file before because I wasn't sure you would ever answer my pull request. lol

Hi guys,
thank you so much for your work! I couldn't believe my best bet to get PDF creation in .net core to work was a 19 days old nuget package 😬
However, this package doesn't work for me on OSX with the latest 3.1 SDK. There are two reasons:

Wrong file paths for zip files
Missing writing permission for the unpacked exe
I could fix both issues in a fork of this branch. Please have a look at the changeset: https://github.com/JoaoLucasGtr/PhantomJs.NetCore/compare/master...fashiontale:master
However, I wonder why it worked for you and I hope I can contribute to something that works everywhere ;)

Hi @Bettelstab, thanks for your feedback.
The whole purpose of this package is to work on all operating systems and it would be great to have your contribution
to achieve this.
I got this working on Windows and Linux (Xubuntu 20.04) but I don't have a Mac to test it out. However, it makes all sense
to change mod to +x before executing the unzipped exe on Unix like systems.
So, I'll take a look at it again later on and get your changes on my fork version if it's all ok.
Again, thank you for your help!

I can confirm that 1.0.1 works as expected on OSX :)

Awesome! This looks really nice @JoaoLucasGtr
Apologies for the reeeeeeeally slow response. I'll be sure to answer them quick the next time.
Thank you all for your contributions. :+1:


MAHOUT-1693: Override .toString() in AbstractMatrix using VectorView

I still have to test this out a bit, but this is a fix for the memory issues caused by the shell triggering .toString() after the instantiation of large  DenseMatrix, SparseMatrix and FunctionalMatrixViews (MAHOUT-1693).  This is set to display an (arbitrarily sized)10x20 upper left block of the matrix.  For sparse matrices this does affect the printout, so it may not be acceptable.

I'm going to push this to master tonight since it's a better fix than we have in place already, and I'm not sure how much time I'll have tomorrow.  We can always adjust the size of the matrix block to be displayed.

10 * 20 to display is fine IMO. +1 to push this to master.


sleep for 2 seconds after broadcasting

The problem was that our function was returning immediately, leaving no time to the peers to request the new transaction with getdata.
Closes https://github.com/cloudhead/nakamoto/issues/154

Closing because it wasn't building with the last master of sp_lib so I'll push the same fix on another branch


Support slots, events and external .js

Do you plan to add support for support slots, events, mixins and external .js?
my .vue:
<template>
.....
</template>

<script src="./my.js"><script>

Hello,
Nope I didn't plan anything, but this can be nice to have slots and events with @vue-slot my-slot-name Description....
For mixins, do you think to a particular behavior?

will it be configurable with @vue-mixin MyMixin?
should a link for this mixin be displayed on generated documentation?

For external .js files, I don't see why it should be useful to have them. :thinking:

For external .js files, I don't see why it should be useful to have them.
To dont dificult temlate, to .vue was max clear and contains only template.

This bad?

should a link for this mixin be displayed on generated documentation?

This main aimp!

Mmmh, okay.
I understand what you are saying, and yes those are interesting functionalities (but not really for external .js files :thinking:).
@vue-slot and @vue-event will be easy to implement, @vue-mixin will be a little harder :thinking:
Feel free to open a pull request, thanks! :level_slider:

... but not really for external .js files 🤔 ...

Why? What is the reason?

Firsly, I think it's counter-productive to split a .vue in multiple files (.vue for template, a .js for javascript, and maybe a .css for your styles).
If your JavaScript code directly acts on your template, then it should be kept inside your .vue in my opinion.
Secondly, this is not how JSDoc works (I think?).
Yes we can dev something to inject your .js on-the-fly, then it will be able to be parsed and a documentation will be generated, but it's dirty and will result into some weird behaviors. :disappointed:

In such cases, how will myxins belong to this component? Mixins are precisely defined in separate files.

... counter-productive

https://vuejs.org/v2/guide/single-file-components.html#What-About-Separation-of-Concerns

Thank you, I know this feature exists, that why I said "I think".
For mixins, you should use @vue-mixin Foo I guess.

I also use computed and data selection in mixin, but all definitions
 /**
   * @vue-prop {Number} initialCounter - Initial counter's value
   * @vue-prop {Number} [step=1] - Step
   * @vue-data {Number} counter - Current counter's value
   * @vue-computed {String} message
   */

are located in .vue.
How to deal with these fields?

Mmmh...
Good question. Maybe @vue-mixin can take a filename that will be read and parsed by jsdoc-vuejs?
And then after parsing, we populate component's prop/data/computed?
What do you think?

@kolesoffac Did you find a solution when using external files? Or did you switch to another solution?

Hi guys
Both slots (scoped) and events have an ability to pass parameters. It would be great if we had a @vue-slot and @vue-event annotation, which would allow us to follow it with @param annotations. @params would then describe the slots and events for us. The result would be a table for slots and a separate table for events, just like we get for @vue-prop.
For example
/**
 * The s-popup component displays a popup window with your text and an optional title.
 *
 * @vue-slot activator Clicking this content will display the popup
 * @param {object} item This is purely fictional, just to demonstrate how the @param would be used
 *
 * @vue-slot [title] An optional popup title
 * @vue-slot default The content to be displayed
 *
 * @vue-event close
 * @param {string} result The button that the user clicked (OK or Cancel)
 *

Is this feasible?

I don't think this is feasible in JSDoc core, when you have one comment block, @param will apply for the whole comment block.

I see.
Well then @vue-slot and @vue-event, even without @param, will still be much better then nothing at all :)
And I can use separate @typedef blocks to define the parameters and then refer to them in the slot/event descriptions.

Update: @event can be used to document events already, like this
/**
 * Toggle flag that displays this list
 * @event toggle-show-list
 * @property val
 */

/**
 * Emits event to the parent to remove the given UUID
 * @event remove-delegate
 * @property {uuid} UUID
 */

/**
 * Tell the parent to close the delegate form
 * @event close-delegate-form
 */

@Kocal did you ever get around to building out the @vue-slot? I see this issue is still opened.
@pbastowski did you ever get it working?

@Elaniobro hi, no I didn't work on it, but you are free to send a PR if you need it.

@Elaniobro Sorry, I don’t remember exactly what I did with that. It’s been almost two years since then.

@Kocal have you seen vuese?  It works really well for documenting vue components.  Personally the only reason I've avoided using it is because it seems to be specific to vue and I don't think integrates the rest of jsdocs like your plugin does.  But it might provide ideas for implementation