decodeURIComponent key

Issue #, if available:
key cannot be used to manipulate S3 files as it needs decoding first.
Description of changes:
Run decodeURIComponent on key for generated example function.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@deanbarrow can you provide an overview of the use case you are solving with this PR and the strategy of your implementation? Based on our contributing guide for a change of this size, I would recommend first opening an issue to discuss the feature and your design / approach.
It's also possible that the diff is just stale and it's a much smaller change than it looks. In that case, if you rebase your branch we can continue reviewing this.


Hide EditableString implementation details

Previously, EditableString had many public members because it needed to
implement the KeyboardClient interface. However, that's confusing
because these methods cannot be called directly.
Now EditableString holds a private implementation of the KeyboardClient,
which hides the implementation details.
Fixes #208
Fixes #209

@jason-simmons


On VMS with 64-bit pointers: No "64" in OSSL$INSTROOT:[SYS$STARTUP] DCL scripts

OpenSSL version 3.0.7, 3.0.12, and, I assume, many others.
(Inspection suggests that 3.2.0 is similarly afflicted, so I'd guess
that 3.1.x is, too, as well as older ones.)
On VMS, in a build with 64-bit pointers, various file specs and
logical names in the OSSL$INSTROOT:[SYS$STARTUP] DCL scripts are not
getting the desired/expected "64" modifier.  Many things fail when the
wrong ("64"-less) names are used.
Cause: Error in templates for OSSL$INSTROOT:[SYS$STARTUP] DCL
scripts:
  [.VMS]openssl_ivp^.com.in
  [.VMS]openssl_shutdown^.com.in
  [.VMS]openssl_startup^.com.in:

In each of these "*^.com.in" templates:
$       pz   := {- $target{pointer_size} -}
should be:
$       pz   := {- $config{pointer_size} -}
(Compare "pz" with, for example, "OPENSSLDIR" in
"[.VMS]openssl_startup^.com.in".  Refer to "[]vmsconfig.pm" to see where
"pointer_size" really is.)
Note: The actual files (.OLB, .EXE) are created with the "64" in
their names; only the OSSL$INSTROOT:[SYS$STARTUP] DCL scripts which
(should) point to them are wrong.

While we're looking at VMS stuff, here's an unrelated complaint:
Some VMS-specific code uses obsolete conditions like:
  # ifdef __alpha
  #if defined __alpha

which, I'd venture, should be replaced by things like, say:
  # ifndef __VAX
  $if !defined __VAX

For many purposes, the VMS world is divided into (1) VAX and
(2) everything after VAX (Alpha, IA64, x86_64, ...).  In almost all
cases, testing for VAX makes more sense than testing for any particular
post-VAX architecture (such as "__alpha").
  [.apps.lib]vms_term_sock.c
  [.providers.implementations.rands.seeding]rand_vms.c

Around here:
ITS $ @ config -64 --prefix=UTILITY_DEV:[UTILITY.SOURCE.OPENSSL.3_0_12-64z] -
_ITS $  --openssldir=UTILITY_DEV:[UTILITY.SOURCE.OPENSSL.3_0_12-64z]
ITS $ mms
ITS $ mms test
ITS $ mms install
ITS $ tcpip show version ! (Not that it matters much)
 HP TCP/IP Services for OpenVMS Industry Standard 64 Version V5.7 - ECO 5
 on an HP rx2600  (1.50GHz/6.0MB) running OpenVMS V8.4-2L3

ITS $ cc /version
VSI C V7.4-001 on OpenVMS IA64 V8.4-2L3

@levitte , do you have any VMS-related suggestions here?

For many purposes, the VMS world is divided into (1) VAX and
(2) everything after VAX (Alpha, IA64, x86_64, ...). [...]

This is true for vms_term_sock.c, but rand_vms.c is more complicated.
In rand_vms.c, the "#if defined __alpha" conditions may be correct, but
the "#if defined __ia64" might want to include __x86_64 as well.  (Or be
replaced by "#if !defined __VAX && !defined __alpha".)
My suggestions should be available at/under: http://antinode.info/ftp/openssl/3_0_12/

I frankly haven't looked at the pointer-size issue for some time, and things have slipped.  Full admission.
I do have it on my personal TODO list to take a closer look at this again.  Thanks, @Antinode-org, for the reminder and the pointers, they will certainly help.

Re rand_vms.c, I fully expected SYS$GET_ENTROPY to be present on x86_64, so the data collection method shouldn't be relevant there.  I do not know, though, 'cause I've only just started building on x86_64, and am encountering other building issues that I've had some trouble figuring out

[...] I fully expected SYS$GET_ENTROPY to be present on x86_64, [...]

I was too lazy to figure out when which method gets used, and it
looked easy enough to adjust the old one to work everyplace.

[...] am encountering other building issues that I've had some trouble
figuring out

With my weak psychic powers, there's not much I can do with "other
building issues" as a problem description.  With my changes, the worst I
saw were a couple of %CC-I-IMPLICITFUNC (socket_fd and getpid -- header
files not included), and a typical assortment of %CC-I-QUESTCOMPARE,
where some type or other is unsigned on VMS.
I haven't been keeping my x86_64 software up to date, so I used:
V87 $ cc /version
VSI C X7.4-785 (GEM 50X65) on OpenVMS x86_64 V9.2-1
and I haven't yet installed the available OS update kits.

[...] I fully expected SYS$GET_ENTROPY to be present on x86_64, [...]

I was too lazy to figure out when which method gets used, and it looked easy enough to adjust the old one to work everyplace.

[...] am encountering other building issues that I've had some trouble
figuring out

With my weak psychic powers, there's not much I can do with "other building issues" as a problem description.

At the time I wrote that, I didn't remember the details.  I do now.  Here's the trouble I stumble into:
LIBRARY/CREATE/OBJECT OSSL$libcrypto.OLB
...
LIBRARY/REPLACE OSSL$libcrypto.OLB [.providers.implementations.ciphers]libdefault-lib-cipher_aes_ocb.OBJ
%LIBRAR-E-DUPGLOBAL, global symbol aes_ocb_cipher from file USER:[LEVITTE.WRK._OPENSSL-3_3_0-DEV-X86_64.providers.implementations.ciphers]libdefault-lib-cipher_aes_ocb.OBJ;2 already in library USER:[LEVITTE.WRK._OPENSSL-3_3_0-DEV-X86_64]OSSL$LIBCRYPTO.OLB
%MMS-F-ABORT, For target OSSL$LIBCRYPTO.OLB, CLI returned abort status: %X108680B2.
%MMS-F-ABORT, For target BUILD_SW, CLI returned abort status: %X10EE8034.

It is true that this particular symbol exists in two places, but...:
$ git grep ' aes_ocb_cipher('
crypto/evp/e_aes.c:static int aes_ocb_cipher(EVP_CIPHER_CTX *ctx, unsigned char *out,
providers/implementations/ciphers/cipher_aes_ocb.c:static int aes_ocb_cipher(void *vctx, unsigned char *out, size_t *outl,

... considering they're static, I'm a bit stumped, can't quite figure out why they became global.  As building issues go, this one got the better of me for the moment.
(I'm still trying to put together a small example that reproduces this, to make a simple bug report...  but alas, it eludes me)
This is, BTW, with a fully updated kit:
$ cc/version
VSI C x86-64 X7.4-843 (GEM 50XB9) on OpenVMS x86_64 V9.2-1

Re my LIBRARY issue, I just saw on VSI's forum that someone else has reported that same issue, with a working reproducer.  I'll work my way from there

Regarding the $target{pointer_size} vs $config{pointer_size}, the move to using the former was deliberate: e30545e9bd84e3ace70fb1e1c5ad6d824545fe36
However, it seems that build of vmsconfig.pm wasn't adapted accordingly, which is the cause of the discrepancy you see.  So, I'll propose a different change to try (coming up in a few)

@Antinode-org, #23081 is my proposed fix for the main issue you reported here.  It's in draft pending tests, but may be worth having a look at and try out?
Not sure how comfortable you are with git, so I'm attaching a tarball with the modified files as well:
fix-22899.tar.gz

Re my LIBRARY issue, I just saw on VSI's forum [...]

Yeah, %LIBRAR-E-DUPGLOBAL was instantly recognizable.  I've been
following that VSI forum thread, but my software-update laziness seems
to have protected me from that problem, so far.

Not sure how comfortable you are with git, [...]

Less than I should be, I'm sure.

fix-22899.tar.gz

Thanks.  That seems to work on IA64.  On x86_64,
Configurations/10-main.conf still needs some help.  (Add sections for
"vms-x86_64-p32" and "vms-x86_64-p64", else "@ config -32" or
"@ config -64" fails on x86_64.)  My x86_64 build is still running, but
I expect it to work.
Also, I claim that apps/lib/vms_term_sock.c should use <iosbdef.h> on
all post-VAX architectures, not only Alpha, but that's more of an
esthetic problem than a practical one.
http://antinode.info/ftp/openssl/3_0_12/apps/lib/vms_term_sock.c
http://antinode.info/ftp/openssl/3_0_12/Configurations/10-main.conf

Regarding preprocessor selectors, there's really no need to check for __VAX, as we've dropped support for VAX builds a long time ago.  Remaining VAX stuff is really just that, remains of a time passed.  So regarding the iosb fixup, the condition can be safely removed altogether.

[...] I expect it to work.

And it did, eventually, which should shut me up for a while.  Thanks.

I'll raise another issue for the cleanups to be done that have been mentioned here


New Module - Shared Image Gallery

Adding the Module that includes the following capabilities :

To create Shared Image Galleries dynamically
To create Image Definitions within the  Image Gallery
To generate a Packer template that renders input from Terraform variables
A Sample Packer template to create Custom Images from Marketplace source images
To create an Image Version(within Image Gallery) and VM Custom image using Packer and Ansible
As the Image is created outside of Terraform, necessary hooks are in place to ensure the order of creation/destroy

Example configuration is included.
Please review and advise.

Closing this PR; will open from another branch.


Queries on Equation 5 and 6 Notations

Hi, Thank you for sharing such a great work!
While reading, I have two questions regarding Eqs. 5 and 6:

In Eq. 5, what do the transition matrices $W_{VO}^{l, h}$ represent? I understand that Eq. 5 is the formal definition of the CLS token for layer $l$ following Elhage et al., but I'm a bit confused about the role of $W_{VO}^{l, h}$. Could you please provide more details about what "transition" refers to?
In Eq. 6, does $T^{l-1}$ refer to $Z^{l-1}$? (I guess it's a typo)

Thanks in advance!

Hi, thank you for your interest in the paper!

The $W_{VO}^{l,h}$ presents the OV circuit, discussed in Elhage et al.. This is the multiplication of the Values matrix by the Output matrix of self-attention layer, and it is split into different heads (because it is linear).

Yes, you are correct. We fixed it in the openreview version

Thank you for your quick reply!
Now I understand more about Eq. 5, and I have more questions about it:

I thought that the dimension of $z_i^{l-1}$ and $W_{VO}^{l, h}$ should be represented by $d$ (as it is an internal logic of the ViT), but the dimension is described as $d'$ (in the sentence right after Eq. 5), which is the dimension of the joint vision-and-language space after the projection matrix $P$ (Eq. 2). Did I miss something by any chance?

Is there a reason for using the term $W_{VO}^{l, h}$ instead of $W_{OV}^{l, h}$? I believe the relevant part of the reference article (OV circuit) is this section, where they define $W_{OV}=W_{O}W_{V}$ (since $W_{O}W_{V}$ always works together). I'm unclear whether $W_{OV}$ and $W_{VO}$ are equivalent, but as of now, $W_{OV}$ seems more reasonable to me because $W_{O}W_{V}z_{i}^{l-1}$ can be decomposed as: (1) calculation of the value vector ($v_{i} = W_{V}z_{i}^{l-1}$), (2) compute the result vector ($r_{i} = \alpha_{i}^{l, h}v_{i}$), and (3) compute the output vector of the head ($h_{i} = W_{O}r_{i}$).

Thanks again!

Yes, you are correct again. You did not miss anything, and it is a typo and it should be $d \times d$. We will fix it. Thank you!
This is indeed the OV circuit, and it is probably not the best naming from our side. Please treat it as $VO$ instead of $OV$.

Sounds good! I will close the issue. Thanks again for the interesting work!


[SP-3362][PDI-15976] Spoon v 7.0 cannot remove "Lock" from transformation/job

added checking canUnlock in repository if it remote and Proxy
added test
fixed check style problems

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f plugins/pdi-pur-plugin/build.xml clean-all resolve jacoco && ant -f plugins/pdi-pur-plugin/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  plugins/pdi-pur-plugin/src/org/pentaho/di/ui/repository/pur/repositoryexplorer/controller/RepositoryLockController.java
  plugins/pdi-pur-plugin/test/org/pentaho/di/ui/repository/pur/repositoryexplorer/controller/RepositoryLockControllerTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.ui.repository.pur.repositoryexplorer.controller.RepositoryLockController

Branch Change:  + 13.89%
Complexity Change:  + 6.12%
Instruction Change:  + 15.56%
Line Change:  + 17.01%
Method Change:  + 23.08%

org.pentaho.di.ui.repository.pur.repositoryexplorer.controller.RepositoryLockController.new BindingConvertor() {...}

Complexity Change:  + 14.29%
Instruction Change:  + 14.63%
Line Change:  + 10.00%
Method Change:  + 33.33%

org.pentaho.di.ui.repository.pur.repositoryexplorer.controller.RepositoryLockController.new ResourceBundle() {...}

Complexity Change:  + 33.33%
Instruction Change:  + 42.86%
Line Change:  + 33.33%
Method Change:  + 33.33%


Remove linked list from questionnaire manager

What is the context of this PR?
This is the final change to remove the state storage and pickling from the system to enable more flexibility in software upgrades/changes and more robust data handling.
How to review

No reference to the linked list in the system anymore
JSON pickle is no longer a dependency
Answers are stored via QuestionnaireStore as simple JSON/text (not pickled).

Not sure if this story has caused this, but choosing 'other' on the first page throws a 500

Are we saying that once a block is valid you can never make it invalid again?


Force result to be formated as json pretty

Is there a workaround to force httpie to pretty the body of the http result as json format (indent, ...)?
As the code https://github.com/jakubroztocil/httpie/blob/master/httpie/output/formatters/json.py#L13 the mime-type of the response, such a response is not well formatted if the response does not contain json as mime-type
http --session=admin -j --pretty=all --verbose http://localhost:8181/hawtio/jolokia/list/java.lang/type=Memory
GET /hawtio/jolokia/list/java.lang/type=Memory HTTP/1.1
Accept: application/json
Accept-Encoding: gzip, deflate
Authorization: Basic YWRtaW46YWRtaW4=
Connection: keep-alive
Content-Type: application/json
Cookie: JSESSIONID=1e4hs0o1sidfc4edui24da7jb
Host: localhost:8181
User-Agent: HTTPie/0.9.2

HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Cache-Control: no-cache
Content-Length: 681
Content-Type: text/plain;charset=UTF-8
Date: Mon, 04 May 2015 13:10:13 GMT
Expires: Mon, 04 May 2015 12:10:13 GMT
Pragma: no-cache
Server: Jetty(8.1.16.v20140903)
X-Frame-Options: SAMEORIGIN

{"timestamp":1430745013,"status":200,"request":{"path":"java.lang\/type=Memory","type":"list"},"value":{"desc":"Information on the management interface of the MBean","op":{"gc":{"ret":"void","desc":"gc","args":[]}},"attr":{"Verbose":{"desc":"Verbose","type":"boolean","rw":true},"ObjectPendingFinalizationCount":{"desc":"ObjectPendingFinalizationCount","type":"int","rw":false},"NonHeapMemoryUsage":{"desc":"NonHeapMemoryUsage","type":"javax.management.openmbean.CompositeData","rw":false},"HeapMemoryUsage":{"desc":"HeapMemoryUsage","type":"javax.management.openmbean.CompositeData","rw":false},"ObjectName":{"desc":"ObjectName","type":"javax.management.ObjectName","rw":false}}}}

Result should be displayed as such :
{
  "timestamp":<PHONE_NUMBER>,
  "status": 200,
  "request": {
    "path": "java.lang\/type=Memory",
    "type": "list"
  },
  "value": {
    "desc": "Information on the management interface of the MBean",
    "op": {
      "gc": {
        "ret": "void",
        "desc": "gc",
        "args": []
      }
    },
    "attr": {
      "Verbose": {
        "desc": "Verbose",
        "type": "boolean",
        "rw": true
      },
      "ObjectPendingFinalizationCount": {
        "desc": "ObjectPendingFinalizationCount",
        "type": "int",
        "rw": false
      },
      "NonHeapMemoryUsage": {
        "desc": "NonHeapMemoryUsage",
        "type": "javax.management.openmbean.CompositeData",
        "rw": false
      },
      "HeapMemoryUsage": {
        "desc": "HeapMemoryUsage",
        "type": "javax.management.openmbean.CompositeData",
        "rw": false
      },
      "ObjectName": {
        "desc": "ObjectName",
        "type": "javax.management.ObjectName",
        "rw": false
      }
    }
  }
}

I believe this is of interest to me because I also have a Content-Type that passes valid json but or request is not set to Content-Type: json; can't say what the value really is. I didn't see a way to force the output to be pretty printed. Our Content-Type value is necessary but returns valid json responses.

@cmoulliard and @drobati If you can provide a publicly available endpoint with this type of response that would be helpful.

I have a potential fix for this, will send a PR after some additional testing:
(venv)jay@ubuntu:~/git/httpie$ http :8000/
HTTP/1.1 200 OK
Content-Length: 34
Content-Type: text/plain;charset=UTF-8
Date: Thu, 02 Jul 2015 05:29:07 GMT

{"hello":"world","testing":"json"}

(venv)jay@ubuntu:~/git/httpie$ http :8000/ --force-mime=text/json
HTTP/1.1 200 OK
Content-Length: 34
Content-Type: text/plain;charset=UTF-8
Date: Thu, 02 Jul 2015 05:29:10 GMT

{
    "hello": "world",
    "testing": "json"
}

@jcrumb opened his PR in #368

:+1: @kfix
Couldn't provide a public link as it was a private API. Looking forward to this merge.

+1

Now with the --json, -j option HTTPie tries to detect JSON responses when the Content-Type is unknown or text/plain.

Great work @jcrumb and @jkbrzt! :clap: :clap: :clap:

Ideally if you specify --json it should just override the content type completely. For example this public API returns "text/html;charset=UTF-8" for a json resource
http https://api.nicehash.com/api?method=stats.global.current
Which is obviously wrong (from the resource perspective) but it would seem the setting --json should just override the returned content type.
Thanks


Possible errors with PF2

Errors reported in the Foundry Discord #module-troubleshooting channel.

Video of the problem in action...
https://www.dropbox.com/s/1d8s1ydqcb09dh3/GridScaler.mov?dl=0

I couldn't repro the bug myself, but I did find some bugs in the code. Hopefully this is fixed in v1.4.1.


CI: Use new Ruby, separate out JRuby

This PR updates the CI matrix to use latest releases. Update: too early for rvm! Seems these named versions from the https://www.ruby-lang.org/en/news/ from today are not yet available.

Use different JDKs for 9.1 and 9.2+

Thank you @olleolleolle !


Execution failed for task ':camera_deep_ar:bundleDebugAar'.

Execution failed for task ':camera_deep_ar:bundleDebugAar'.

Direct local .aar file dependencies are not supported when building an AAR. The resulting AAR would be broken because the classes and Android resources from any local .aar file dependencies would not be packaged in the resulting AAR. Previous versions of the Android Gradle Plugin produce broken AARs in this case too (despite not throwing this error). The following direct local .aar file dependencies of the :camera_deep_ar project caused this error: /Users/trevin/Development/Tools/flutter/.pub-cache/hosted/pub.dartlang.org/camera_deep_ar-0.0.1/android/libs/deepar.aar

I've tried similar fixes by using the below snippet, but it still bugged.
allprojects {
repositories {
google()
jcenter()
maven {
// [required] camera_deep_ar
url "${project(':camera_deep_ar').projectDir}/libs"
}
}
}

Execution failed for task ':camera_deep_ar:bundleDebugAar'.

Direct local .aar file dependencies are not supported when building an AAR. The resulting AAR would be broken because the classes and Android resources from any local .aar file dependencies would not be packaged in the resulting AAR. Previous versions of the Android Gradle Plugin produce broken AARs in this case too (despite not throwing this error). The following direct local .aar file dependencies of the :camera_deep_ar project caused this error: /Users/trevin/Development/Tools/flutter/.pub-cache/hosted/pub.dartlang.org/camera_deep_ar-0.0.1/android/libs/deepar.aar

I've tried similar fixes by using the below snippet, but it still bugged.
allprojects {
repositories {
google()
jcenter()
maven {
// [required] camera_deep_ar
url "${project(':camera_deep_ar').projectDir}/libs"
}
}
}

change gradle version to older one it works fine for ex. in build.gradle(in app module)
classpath 'com.android.tools.build:gradle:3.5.0 this version works fine

Execution failed for task ':camera_deep_ar:bundleDebugAar'.

Direct local .aar file dependencies are not supported when building an AAR. The resulting AAR would be broken because the classes and Android resources from any local .aar file dependencies would not be packaged in the resulting AAR. Previous versions of the Android Gradle Plugin produce broken AARs in this case too (despite not throwing this error). The following direct local .aar file dependencies of the :camera_deep_ar project caused this error: /Users/trevin/Development/Tools/flutter/.pub-cache/hosted/pub.dartlang.org/camera_deep_ar-0.0.1/android/libs/deepar.aar

I've tried similar fixes by using the below snippet, but it still bugged.
allprojects {
repositories {
google()
jcenter()
maven {
// [required] camera_deep_ar
url "${project(':camera_deep_ar').projectDir}/libs"
}
}
}

change gradle version to older one it works fine for ex. in build.gradle(in app module)
classpath 'com.android.tools.build:gradle:3.5.0 this version works fine

Yes, this worked fine for me as well, but why is this issue occurring and how come this is not in the documentation. Someone should add this.

Execution failed for task ':camera_deep_ar:bundleDebugAar'.

Direct local .aar file dependencies are not supported when building an AAR. The resulting AAR would be broken because the classes and Android resources from any local .aar file dependencies would not be packaged in the resulting AAR. Previous versions of the Android Gradle Plugin produce broken AARs in this case too (despite not throwing this error). The following direct local .aar file dependencies of the :camera_deep_ar project caused this error: /Users/trevin/Development/Tools/flutter/.pub-cache/hosted/pub.dartlang.org/camera_deep_ar-0.0.1/android/libs/deepar.aar

I've tried similar fixes by using the below snippet, but it still bugged.
allprojects {
repositories {
google()
jcenter()
maven {
// [required] camera_deep_ar
url "${project(':camera_deep_ar').projectDir}/libs"
}
}
}

change gradle version to older one it works fine for ex. in build.gradle(in app module)
classpath 'com.android.tools.build:gradle:3.5.0 this version works fine

Thanks for the solution @Vvimal27

3.5.0

Thank you so much !!

This doesn't fix the issue when using gradle version 4.1.2 because other packages are using a newer version

someone found a better solution?

any solution?

Any solution to this problem?

I've fixed this on my Fork, have a look, hope it helps.
https://github.com/KalanaPerera/FlutterDeepAR

I've fixed this on my Fork, have a look, hope it helps.
https://github.com/KalanaPerera/FlutterDeepAR

Please how do i use it from your repo

@silentl007
  camera_deep_ar:
    git:
      url: https://github.com/KalanaPerera/FlutterDeepAR


Docstring Checks

This PR adds a test to make sure all the functions/classes have a docstring. This is another contribution towards more tests.

All tests are passing now. I think we can merge that such that I can move on with the rest of the tests I would like to implement. @anautsch will take a look at all the new test right before releasing the new version of speechbrain.


currently the dashboard shows a default time frame like 01/DEC/2018 — 03/DEC/2018 , can this time frame be altered?

The date/time format? or a filtering option? For the former, #1310, for the later #117.

filtering within a particular time tinterval ex. 01/DEC/2018 12:48 to 01/DEC/2018 12:56..

#117 will address this.


Air conditioner - incorrect outside temperature

I am using this integration with air conditioner Haier Expert 2.8 kW. Everything seems to work just fine, but I noticed that the outside temperature sensor gives bogus values that are also different from those reported by the hOn mobile app. For example, today the sensor reported 4°C throughout the whole day. This might possibly have been the lowest temperature in the morning, but during the day real outside temperature rose up to 16˚C, and hOn app tracked the changes during the day quite faithfully.

Hello,
I have a similar problem, outside sensor shows the set temperature for the A/C and not the outside temperature.
The outside temperature I see on the card to manage the AC.
my model is HAIER SPLIT GEOS GREEN 35 R32
Thanks for this integration!

That's strange. I've updated slightly the sensor (and added the indoor temperature sensor).
Can you check if the problem is still there?

I've pulled the changes and restarted HA. The indoor temperature sensor gives the same temperature as hOn app, but there is still a difference in outdoor temperature: the sensor reports 6˚C but h0n 9˚C. Currently I don't have an independent outdoor measurement but 9˚C is also shown in weather apps (that don't measure it directly at my place though). I wonder if the h0n app really uses the temperature measurement from the outdoor unit. Is there anything I could check?
Thanks, Lada

I've updated the main branch to show all the available sensors (like temperatures). Please tell me what do you have now

The outdoor temperature sensor shows 20˚C whereas hOn app reports 13.5˚C. Here are all the attributes od the device entity:

I need to analyse some logs to understand.
Please add this to the configuration.yaml and restart HA
logger:
  logs:
    custom_components.hon: info

After go to the log page '/config/logs' and click to access all logs.
Share any of the logs starting with:
[custom_components.hon.hon] {"payload":
Thanks!

Here it is:
2023-03-24 09:54:15.484 INFO (MainThread) [custom_components.hon.hon] {"payload":{"resultCode":"0","shadow":{"parameters":{"voiceStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"tempCoilerIndoor":{"parNewVal":"22.00","lastUpdate":"2023-03-24T01:38:45Z"},"tempSel":{"parNewVal":"22.00","lastUpdate":"2023-03-22T06:49:15Z"},"totalWorkTime":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"halfDegreeSettingStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"tempAirOutdoor":{"parNewVal":"32","lastUpdate":"2023-03-23T15:01:44Z"},"debugEnabled":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:43Z"},"co2ValueIndoor":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"tempInAirOutdoor":{"parNewVal":"-64","lastUpdate":"2022-06-21T16:17:26Z"},"selfCleaningStatus":{"parNewVal":"0","lastUpdate":"2022-12-27T20:57:46Z"},"pm2p5ValueIndoor":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"fanStatusOutdoor":{"parNewVal":"2","lastUpdate":"2022-06-21T16:17:26Z"},"tempUnit":{"parNewVal":"0","lastUpdate":"2022-07-11T18:01:10Z"},"stdTransRate":{"parNewVal":"3600","lastUpdate":"2022-06-21T16:16:43Z"},"intelligenceStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"airQuality":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"machMode":{"parNewVal":"4","lastUpdate":"2023-02-04T16:01:09Z"},"humidityIndoor":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"energySavingStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"vocValueIndoor":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"errors":{"parNewVal":"00","lastUpdate":"2022-06-21T16:16:43Z"},"defrostStatus":{"parNewVal":"0","lastUpdate":"2023-03-03T09:35:57Z"},"compressorFrequency":{"parNewVal":"0","lastUpdate":"2023-03-23T14:16:29Z"},"tempIndoor":{"parNewVal":"19.50","lastUpdate":"2023-03-24T02:08:56Z"},"healthMode":{"parNewVal":"0","lastUpdate":"2023-02-27T18:34:40Z"},"fourWayValveStatus":{"parNewVal":"2","lastUpdate":"2022-06-21T16:17:26Z"},"10degreeHeatingStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"freshAirStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"expansionValveOpenDegree":{"parNewVal":"350","lastUpdate":"2023-03-23T14:18:30Z"},"windDirectionVertical":{"parNewVal":"5","lastUpdate":"2022-11-08T05:36:05Z"},"muteStatus":{"parNewVal":"0","lastUpdate":"2022-06-25T20:19:39Z"},"onOffStatus":{"parNewVal":"0","lastUpdate":"2023-03-23T14:50:54Z"},"lockStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"highTransRate":{"parNewVal":"1","lastUpdate":"2022-06-21T16:16:43Z"},"ch2oCleaningStatus":{"parNewVal":"0","lastUpdate":"2023-02-27T18:34:40Z"},"errAckFlag":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"windDirectionHorizontal":{"parNewVal":"0","lastUpdate":"2022-11-08T05:36:05Z"},"power":{"parNewVal":"0","lastUpdate":"2022-06-21T16:17:26Z"},"ch2oValueIndoor":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"machineModeHK":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"acType":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"tempCoilerOutdoor":{"parNewVal":"-64","lastUpdate":"2022-06-21T16:17:26Z"},"pm2p5LevelIndoor":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"heatAccumulationStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"sensingResult":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"screenDisplayStatus":{"parNewVal":"1","lastUpdate":"2023-03-21T05:20:33Z"},"silentSleepStatus":{"parNewVal":"0","lastUpdate":"2023-03-21T05:20:33Z"},"humanSensingStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"energySavePeriod":{"parNewVal":"15","lastUpdate":"2022-06-21T16:16:45Z"},"filterChangeStatusLocal":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"tempDefrostOutdoor":{"parNewVal":"20","lastUpdate":"2023-03-23T14:50:54Z"},"operationSource":{"parNewVal":"3","lastUpdate":"2022-11-08T05:36:05Z"},"pm2p5ValueOutdoor":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"lightStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"statusSyncRate":{"parNewVal":"1440","lastUpdate":"2022-07-20T13:54:28Z"},"electricHeatingStatusIndoor":{"parNewVal":"0","lastUpdate":"2022-06-21T16:17:26Z"},"tempOutdoor":{"parNewVal":"20.00","lastUpdate":"2023-03-23T15:01:44Z"},"pm2p5CleaningStatus":{"parNewVal":"0","lastUpdate":"2023-02-27T18:34:40Z"},"voiceSignStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"selfCleaning56Status":{"parNewVal":"0","lastUpdate":"2022-09-10T12:17:46Z"},"compressorCurrent":{"parNewVal":"51.10","lastUpdate":"2022-06-21T16:17:26Z"},"humiditySel":{"parNewVal":"30","lastUpdate":"2022-06-21T16:16:45Z"},"pmvStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"operationName":{"parNewVal":"","lastUpdate":"2022-07-19T20:40:48Z"},"echoStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"windSpeed":{"parNewVal":"5","lastUpdate":"2022-06-21T16:18:51Z"},"errCode":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"specialMode":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"windSensingStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"transMode":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:43Z"},"electricHeatingStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"compressorStatus":{"parNewVal":"0","lastUpdate":"2023-03-23T14:16:29Z"},"humidificationStatus":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"totalElectricityUsed":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"},"fanStatusIndoor":{"parNewVal":"0","lastUpdate":"2023-03-23T14:18:30Z"},"rapidMode":{"parNewVal":"0","lastUpdate":"2022-06-21T16:16:45Z"}}},"activity":{},"commandHistory":{"command":{"macAddress":"24-d7-eb-05-27-d4","commandName":"stopProgram","applianceOptions":{},"programName":"PROGRAMS.AC.IOT_HEAT","ancillaryParameters":{"remoteActionable":{"fixedValue":"1","typology":"fixed","category":"general","mandatory":0},"remoteVisible":{"fixedValue":"1","typology":"fixed","category":"general","mandatory":0}},"applianceType":"AC","attributes":{"prStr":"Vytápění","channel":"mobileApp","origin":"standardProgram"},"device":{"appVersion":"1.53.7","deviceModel":"oriole","osVersion":"33","mobileId":"13f0215ebba6cb58","mobileOs":"android"},"parameters":{"onOffStatus":"0"},"transactionId":"24-d7-eb-05-27-d4_2023-03-23T14:50:54.225Z","timestamp":"2023-03-23T14:50:54.225Z"},"timestampAccepted":"2023-03-23T14:50:52.6Z","timestampExecuted":"2023-03-23T14:50:53.3Z"},"lastConnEvent":{"macAddress":"24-d7-eb-05-27-d4","category":"CONNECTED","instantTime":"2023-03-24T08:50:43Z","timestampEvent":1679647843946}},"authInfo":{}}

So the only interesting values are these one:
"tempCoilerIndoor":"22.00",
"tempSel": "22.00"
"tempAirOutdoor":"32"
"tempIndoor": "19.50"
"tempDefrostOutdoor":"20"
"tempOutdoor":"20.00"
The hOn app still display a value lower than 20?

The game is to find in the list the value shown by the app :)

The app now shows 16˚C, which is not among the values above. Weird.

I'm closing this issue because it seems the hOn app is taking this value from another place.
Still a strange case :)


VIPM Crash on Windows 10

Hi James,
Have you seen this VIPM Crash?
Any chance you have instructions on how to install manually?

Thanks. I fixed it by starting from scratch :( and installing LabVIEW 2017 64 bits. I'll keep working on it, I'm learning how to integrate it with Jenkins, and so far not other issues.


faq: add answer for how to run ExternalDNS under service account

Just a quick win to document service account setup.
As a result of https://github.com/kubernetes-incubator/external-dns/issues/283#issuecomment-318320780

:+1:


Pip warns about non-standard dependency specifier

Bug description
When I used pip install copy lighting=1.7.7 on ubuntu20.04, the following problem occurred：
DEPRECATION: pytorch-lightning 1.7.7 has a non-standard dependency specifier torch>=1.9.*. pip 23.3 will enforce this behaviour change. A possible replacement is to upgrade to a newer version of pytorch-lightning or contact the author to suggest that they release a version with a conforming dependency specifiers. Discussion can be found at https://github.com/pypa/pip/issues/12063
What version are you seeing the problem on?
v1.7
How to reproduce the bug
No response
Error messages and logs
# Error messages and logs here please

Environment

Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0):
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 2.0):
#- Python version (e.g., 3.9):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(`conda`, `pip`, source):
#- Running environment of LightningApp (e.g. local, cloud):

More info
No response

This was fixed in later releases. Is there a specific reason you need to use this old version and can't jump to a newer one? The only other was trying to make one more/pst release with this fix...

This was fixed in later releases. Is there a specific reason you need to use this old version and can't jump to a newer one? The only other was trying to make one more/pst release with this fix...
Just checking, and 1.8 shall have it fixed

In my case, I need to use an older version because of the restrictions of other libraries: pyannote.audio==0.0.1 requires pytorch_lightning<1.7

not really :c

Closing since this was fixed in all the recent versions. For the older versions that see this deprecation, we can't really make any new releases. The workaround will be either ignore the warning or downgrade pip to an earlier version that didn't warn.


Using Bootstrap 3.3.x on Rails 3.2.x

I'm not sure if I understand this correctly, but in the README, it says:

bootstrap-sass is no longer compatible with Rails 3. The latest version of bootstrap-sass compatible with Rails 3.2 is v<IP_ADDRESS>.

As I understand, bootstrap-sass' version reflects the exact Twitter Bootstrap version it says. Does that mean I won't be able to use the newer versions of Twitter Bootstrap (beyond 3.1.1) unless I move to Rails 4?

No versions newer than <IP_ADDRESS> support Rails 3. It is reportedly possible to use backports of the gems that enable Bootstrap compatibility with Rails 3: https://github.com/twbs/bootstrap-sass/issues/806#issuecomment-70167287.

bootstrap-sass' version reflects the exact Twitter Bootstrap version it says.

Not since v3.3.3+ as we switched to semver.

Good to know. Thanks for clarifying!


Support environment variables in config file 'aem.yml'

to be able to inject e.g home path into paths

done
java:
  home_path: {{ .Env.JAVA_HOME }}


Update component docs

This PR:

copies docs from Hackpad, GOV.UK elements and the GOV.UK frontend toolkit
adds component previews to the documentation
adds an "intro" section for each component

👍  huge improvement. I noticed we're missing a README for scopes (http://localhost:3000/components/detail/scopes doesn't work), but thats not a blocker for this PR.


In-memory file system

Is it possible to use js-git with memfs? If not, where would be a good point for me add it?

js-git has it's own internal implementation of an in-memory filesystem. You can see the sparsely documentation of it here. It should be possible to add memfs support, but last time I used it the internal implementation was working just fine.

This should also work:
import { fs } from 'memfs';
require('js-git/mixins/fs-db')(repo, fs);


[WIP] New API should allow prediction functions and scoring

The new API should allow metric learning algorithms that fit on tuples of points to also predict, score, etc on tuples, Therefore being usable in scikit-learn's cross-validation routines.

[x] Take previous tests from https://github.com/metric-learn/metric-learn/pull/85, and refactor them using pytest, and to allow already formed tuples (3D arrays) instead of ConstrainedDatasets.
[x] Take previous code from https://github.com/metric-learn/metric-learn/pull/85 and adapt it to formed tuples
[x] Make tests work
[ ] Make some modifications if needed

Move docstrings from _fit to fit
Remove unused imports

I just merged with the recently merged PR, so changes introduced by this PR are now clearer.


jmeter 3.2 Smtp smapler The same script Different in different versions running state, jmeter 3.2 false, jmeter 3.1 true, why?  Can someone answer that?

Mr-Bear (Bug 61319):
Created attachment QQ截图20170719185918.jpg: Sampler-500 false

Severity: major
OS: All

Can you please delete or hide the question, the uploaded information contains account information, thank you


mkpr

Applied mkpr on package.json
sed s/"npm-pkgbuild": "^.*"/"npm-pkgbuild": "^6.10.8"/

Pull Request Test Coverage Report for Build 2329

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.509%

Totals

Change from base Build 2319:
0.0%

Covered Lines:
361

Relevant Lines:
375

💛  - Coveralls


Warns about file not being saved, even after export?

Maybe I've misunderstood this alert / dialog, but....
macOS 10.12.6:
Kap Version: 2.0.0(681)
Steps to reproduce
Create a recording
Export > MP4 - (which seems to be working these days)
Close Kap using the red cross icon in its menubar
Current behaviour
Displays an alert "Are you sure you wish to discard this recording?  It will not be saved"
Expected behaviour
As I've just 'saved' (exported) my recording this seems a little confusing?
Workaround
n/a /  ignore it

It refers to the original recording, if you close the window you'll lose it and no longer be able to export it. I think the language is what's confusing here, especially if you've already exported once. I suggest we change the copy to something along the lines of "You'll no longer be able to edit and export the original recording".

What is the concept of 'original recording' in Kap please?
I get the basic concept, say Sketch might have a native .sketch "original" file format used for opening & saving work and also some export options such as PNG, JPG etc.   Does Kap have the concept of Saving the 'original recording' in a native KAP file format?  I couldn't find any Save options, only export.
In which case if exporting is the only way of Saving my recording then I don't understand what the warning is about.  I will lose my work unless I......take what steps?

The video you see in the editor is the "original recording", it is the temporary file that the actual recording library (https://github.com/wulkano/aperture) gives to Kap when the recording is ended (via menubar click). Once you close the editor this file is no longer accessible and thus the "original recording" will be  "lost". Does that make sense? 😊

Yup.  Got it, thanks.
Case; I have TextEdit open, type some words and click the close control.  I correctly get a warning about losing my work unless I save it first. Makes sense - the action I need to take to not see a warning is save my work.
What are the steps I need to take to satisfy the warning in Kap?
I've already exported my file - what else can I  do?  There doesn't seem to be a Save option to save the original file so..... ?

I suggest we change the copy to something along the lines of "You'll no longer be able to edit and export the original recording".

Could I go ahead and implement this change?

@stevenpeniche I still think a point is being missed here (or I still don't understand).   It's not so much about the wording and more about what action can I take to not get this warning.
Back to my example of TextEdit:  user gets a warning that they'll lose their unsaved work unless they File > Save.  So they use File > Save and the warning no longer applies, they can close their document and all is well.
What steps in Kap would satisfy the "You'll lose your work" alert so user can close the Kap window without seeing a warning.
Here is my workflow within Kap:

Create a recording
Export as MP4
Close Kap window.

I don't need or want a warning about losing the work that I've just saved (exported).  Especially as I can't find any other way of "saving" my work.
What have I missed?  ;-)

@steveharman The way I see it is this.
Workflow:

Create a recording.
Export as MP4.
Confirm that you've exported the recording in the format you desire.
Close Kap window.

That third step helps validate that the user doesn't have any second thoughts in regards to size, fps or file format.

Another idea I have had is to show a list of previous Kaptures, as the original file is still accessable (it's in os.tmpDir()) so we could keep a list in memory of the last kapture, that way we could add a button in the interface to export the last recorded kapture (in the same app session), maybe that's another way to help users? @skllcrn thoughts?

Maybe ´Save...´ instead of ´Export´could help clarify this?

I have also found this behavior very confusing, and I actually haven't know what I've done wrong until I read this issue.

Confirm that you've exported the recording in the format you desire.

I personally don't feel that this step is necessary. The way I would personally prefer would be to switch "export" to "save" (per @willedahlbo suggestion) and then only warn if I close the window without having used any of those buttons (e.g. I haven't exported a single file)

That might help @willedahlbo In conjunction with not alerting user they may lose work after they've performed an export / save action.
To my mind it's:

Create a recording.
Export (or Save...) in chosen format.
Close Kap window without alert

And tbh I'd personally be happier that Kap did point 3 for me, automatically.  Recording > Export > End of.  Without needing to close the window.
As it stands I can't understand what risk the alert is trying to protect user from after they have exported (Saved)?  User has saved their work.  End of story?  What is it they're at risk of losing?

@skllcrn It would be awesome to show some checkbox in this dialog which you can check if you're no longer interested in this warning. This warning is really annoying.
Actually I would also like an option for the window to automatically close after export. I can open another issue for that.

Agreed with @skllcrn
It just seems a little strange - iirc we can Cmd-Q the app and don't get warned about losing anything, yet after using the export options (to save our work to MP4, for example) we get this warning about potentially losing work.
If the warning has validity for some users then I'm cool with that - but personally I find it annoying and a "Don't warm me again" checkbox would seem to cover all cases.

I agree a checkbox would be nice here! I'm using the discard button on the touchbar which does not require confirmation, so I'm unaffected by this.

This behaviour is completely removed in 3.0 as we've introduced export history, allowing you to reopen the original recordings for the duration of your session.

I still get an "Are you sure that you want to discard this recording?" alert in 3.0.0 Beta 5 @skllcrn - is that expected behaviour?
I took it from https://github.com/wulkano/kap/issues/399#issuecomment-423510473 that the alert wouldn't be shown after the user has exported their recording?
Thanks

I think this check is, as the message says, for the original recording. Even if you exported let's say as a gif, closing the app means that you will lose that original mp4 unedited recording (since we save it in the tmp directory). If you have an editor that is opened from a local file (i.e. by dropping a file in the icon) then you don't get that message when trying to close, since you can just re-open the file.


irq: Remove return value from IRQ_CONNECT and IRQ_DIRECT_CONNECT

The return value of the interrupt is never used, so remove the
functionality from the API.  We ripple this change into the
ARCH_IRQ_CONNECT and ARCH_IRQ_DIRECT_CONNECT implementations.  With
this change we can also remove the compound expression as that is
not needed anymore.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

Please don't merge until @joerchan has had a chance to look at it

Please don't merge until @joerchan has had a chance to look at it

All good. Thanks.


Custom fonts option on class file

Add pre-define and custom fonts option on class file
Now, you must change it on preample.tex file

added to class and preamble files
pre-defined font is arial
configure custom font at  preable.tex file


Context Menu Manager Utility (PowerContext, PowerMenu)

Description of the new feature / enhancement
When I say "Manager", I mean for user custom menu items within a context menu through file explorer, not editting existing items and not editing context menus through other applications unrelated to PowerToys. So the manager will give you an option to create a new Menu Item or a new List for Menu Items, Lists can be embedded within other Lists and Menu Items can be given options such as Icon, File/Folder filter to enable on either or both, if File then perhaps an option to target specific file types. Then the obvious command to run or just an option to pick an installed program. If the command is custom then perhaps a preview to show you what arguments will be passed so you can alter their location within the command
Example of the custom command preview(EDIT: looking back, I remember %1 implies the file or folder the command is running for and couldnt be bothered to redraw it out)

Also I'm not saying it shouldn't include the full context menu for you to edit and remove existing items that other programs have implemented, I just don't think it's a great idea to edit something you didn't create in that way. Though I can say it would be nice to do, but there are other programs that can do this already, perhaps adding another with a nicer more friendly UI wouldn't be such a bad thing.
Scenario when this would be used?
I tend to have quite a lot of programs that are exclusively command line tools that I use on files/folders from time to time and having to remember the full command and arguments is tedious and this feature just adds an easy way of implementing a simple single click option for what could be a large command. It also means you can have "presets" for things at a click of a button, such as for ffmpeg like changing it codec with different variations of quality settings or maybe like in the image above adding a item for sdelete with different passes or just something like being able to add a item to open up a frequently used folder like the quick access in file explorer but on the context menu for the desktop.
Supporting information
Existing software already exists that almost implement everything I'd want, but is either outdated and no longer works or is lacking a feature I'd like

Ultimate Windows Context Menu Customizer, Very basic, no custom nest lists and no file extension target support and contains all items added by other programs so an inexperienced user may cause harm to their context menu
Context Menu Manager by Fahmy Corporation (2011 software, site is dead), lots of options, no custom nest lists and no longer works, imo if this worked I wouldn't ask for this feature in PowerToys
Context Menu Tuner, while it does work and does have most of the features I'd like it's missing a crucial one and thats being able to created nested lists since I imagine myself to have a lot of custom items and that would clutter the context menu

From what I know adding a menu item is a registry thing but I have seen programs add items to the context menu without it and it was done through C# code, which is good seeing as PowerToys is half C#.
I understand if this is a very niche feature and doesn't benefit the majority of the users causing it to be denied or ignored, but I thought it could help the power users.

/dup #33


use indexmap instead of hashmap for attributes?

First of all, thank you for your hard work on this library! I was excited to see a mjml implementation in rust, it works great and is very fast.
Second, would you be open to using an IndexMap instead of a HashMap?
I am trying to write a test that asserts the output of a MRML template with an expected/known constant value but am running into problems with the ordering of an element's attributes. I believe that using an indexmap would order the attributes based their insertion order, which should allow for rendering a stable output value between MRML instances.
The example below helps illustrate the problem I am running into.
let source = "<mjml><mj-body><mj-section><mj-column><mj-text>hi</mj-text></mj-column></mj-section></mj-body></mjml>";
let options = mrml::prelude::render::Options::default();

let root_1 = mrml::parse(source).unwrap();
let root_2 = mrml::parse(source).unwrap();

let output_1 = root_1.render(&options).unwrap();
let output_2 = root_2.render(&options).unwrap();
// fails
assert_eq!(output_1, output_2);

If you're open to this change, I can try to open a PR in the next couple of days with a possible solution.

👋 Thank you for this PR.
I'm curious about this issue. I'll take a look at it a bit more but of course I'd be open to switch to IndexMap.
I'll also take a look at the overhead of IndexMap in term of performances 😉


Feature request: add FlareSolverr solver to bypass CloudFlare protection

Ther are a lot of sites that use cloudflare as protection, checking sites that use cloudflare can result in 403, would be nice to have support for FlareSolverr  to fix this situation.
Related:
https://github.com/lycheeverse/lychee/issues/1157
https://github.com/jobobby04/TachiyomiSY/pull/1124

First time I hear of FlareSolverr, but it looks nice. We wanted to add proxy support anyway at some point. There's a proxy config file that browsers like Firefox use. Not sure if it could also be used to call FlareSolverr.

The proxy support request I was referring to: https://github.com/lycheeverse/lychee/issues/869
Would it "just work" if we added support for that?

Looks like FlareSolverr requires data to be sent as a JSON POST request? So the proxy approach wouldn't work.
There's a prototype for WebAssembly support, which could be used to modify the request. @thomas-zahner, this should work, right?

Yes this seems like a perfect use case of the recently implemented RequestChain. The WebAssembly part is indeed only a prototype and not merged yet. However, the request chain itself is already fully functional and available in lychee_lib through the ClientBuilder.
An example on how to make use of the RequestChain can be found here: https://github.com/lycheeverse/lychee/blob/master/examples/chain/chain.rs

Another example https://github.com/Suwayomi/Suwayomi-VaadinUI/commit/712ca2a86b9d853a7e0dfcc067b72c00cb399844

So I've created an example on how to use the RequestChain to call the FlareSolverr proxy instead of the actual website and then use the status code returned inside FlareSolverr's response body. Here you can find the branch: https://github.com/thomas-zahner/lychee/commit/297c2e93dfab3e46985bc34146ca03c67d8513df
Note that I didn't test it on a protected website. But as long as the status code returned by FlareSolverr is accurate it should work as expected. I felt that FlareSolverr's documentation is not very good as I didn't see the "official" JSON response schema, so I've used their provided "example response" which hopefully should represent the consistent JSON response schema.

Noticed a bug in my implementation, currently Status:Ok is always returned. Fix would be a little hacky (copy paste) so I've opened up an issue


fix: how config vgv with build-modes in flutter

Description
how config vgv with build-modes in flutter
fix: how config vgv with build-modes in flutter https://docs.flutter.dev/testing/build-modes
Steps To Reproduce
Expected Behavior
Screenshots
Additional Context

@erlangparasu thanks for opening an issue.
As far as I know, Very Good CLI doesn't expose any command to "run" your project, hence you should use flutter run instead. The Build modes documentation specifies how. For example flutter run --profile uses profile mode.
I'll be closing this issue, if this answer doesn't solve it feel free to re-open the issue with a comment explaining why.


Update LegacyConversions.java

I have fixed a possible bug when mixing displayTitle with title which causes displayTitle to appear when displayTitle should appear in legacy MediaControllers.

Thanks for your pull request.
Can you elaborate a bit on what the bug is about, what the symptoms of the bug is and how this change fixes it?
I'm asking because this is implemented in a specific way right now that takes into account expected behaviour for instance of the AVRPC also.
After your change I think displayTitle never makes it into the legacy metadata object I think. So if this is correct, then we should understand this and know for which use cases it works better that before didn't work. I think never using displayTitle doesn't feel right to me specifically when looking at L857 and the logic around PREFERRED_DESCRIPTION_ORDER.

Hmm, I actually have changed that on request of Auto and AAOS people and its reviewed by them. I can make them look at your request. For our information:

In legacy MediaControllers, for example in Android Auto, the title appears on
the main playback screen, however the user will see the displayTitle, which, in my opinion, is not correct.

I don't understand this. How does the user see 'displayTitle' when the 'title' is displayed?
Can you let me know what the intention of a developer is who sets title and displayTitle differently in a Media3 MediaMetadata instance?
With the current implementation before your change, setting the displayTitle would use that. If a developer doesn't want this, they can not set the displayTitle because then the title is used. This can be an issue if the developer wants to set the displayTitle but it should not be used when converting to the legacy MediaMetadataCompat. Which use case would suffer when not using displayTitle in such a case?
I will check with the Auto team also to discuss this.

I don't understand this. How does the user see 'displayTitle' when the 'title' is displayed?

The title is displayed, but since it has been assigned displayTitle, the contents of displayTitle will be seen in Android Auto.
NOTE: This also occurs in the MediaStyled media session notification. Please, check it.

Can you let me know what the intention of a developer is who sets title and displayTitle differently in a Media3 MediaMetadata instance?

Here I am not referring to the developer but to the content/metadata of an audio or video file.

With the current implementation before your change, setting the displayTitle would use that. If a developer doesn't want this, they can not set the displayTitle because then the title is used. This can be an issue if the developer wants to set the displayTitle but it should not be used when converting to the legacy MediaMetadataCompat. Which use case would suffer when not using displayTitle in such a case?

I don't think there is any use case that would suffer any problems in such a case.

Here I am not referring to the developer but to the content/metadata of an audio or video file.

Now, I'm confused.
You send a pull for MediaDescriptionCompat convertToMediaDescriptionCompat(MediaItem item, @Nullable Bitmap artworkBitmap). That method gets passed in a MediaItem and produces a MediaDescriptionCompat.
This is called in three places. The first two:

From MediaControllerImplLegacy to create queue items passed into controllerCompat.addQueueItem(MediaDescriptionCompat) when accessing a legacy session.
From MediaSessionLegacyStub to create queue items to be served to legacy controllers accessing a Media3 session.

these  two are not used by Android Auto/AAOS I think.
The remaining callsites are calling convertToMediaDescriptionCompat  indirectly through convertToBrowserItem from MediaLibraryServiceLegacyStub. That's what is involved in Auto regarding your change I think. When Auto/AAOS accesses a MediaLibraryService as a mediaBrowserCompat and for instance gets children that are MediaBrowserCompat.MediaItem.
These come from what an app returns from for instance MediaLibrarySession.Callback.onGetChildren():LibraryResult<List<MediaItem>>.

Here I am not referring to the developer but to the content/metadata of an audio or video file.

How do you think is the metadata from the audio or video file leaking into these media items that are returned from the callback methods?

NOTE: This also occurs in the MediaStyled media session notification.

That's another case. If I'm not mistaken, here the media notification indeed may receive metadata from onMediaMetadatdaChanged() that is converted to the legacy metadata and then System UI uses this.
So if we can find evidence that some metadata from either in-band metdata (vid/audio files), ICY headers or other sources produces a displayTitle that we merge into the metadata emitted by Player.Listener.onMediaMetadatdaChanged(), then that could happen.
But we wouldn't need to change LegacyConversions.convertToMediaDescriptionCompat but rather look into LegacyConversions.convertToMediaMetadataCompat()  I think which is implemented differently.
Sorry, for asking this again. Can you elaborate a bit on what the bug is about, what the symptoms of the bug is and how this change fixes it? I'm afraid I insist, so please accept my apologies. I want to understand the change first, before starting to review.

Let's consider this scenario:
I have an mp3 audio file stored on an Android phone.
My app accesses its metadata using the MediaStore database and creates a MediaItem.
During this process, my app sets the song title field in the metadata to title (e.g., "Viva la vida") and sets the file name to displayTitle (e.g., "01 Viva la vida.mp3"). I think this way of assignment is the most logical.
When I play this MediaItem using ExoPlayer and connect the phone to Android Auto, the Android Auto playback screen shows the file name instead of the song title.
I think it makes more sense to show the title of the song.
If displayTitle!=null, why does the MediaDescriptionCompat returned by convertToMediaDescriptionCompat() contain displayTitle instead of title? It is assigned for no reason on line 850, since there is no nullity check for title.
As far as I can see, line 850 of LegacyConversions is the only place where diplayTitle is assigned to title, where the variables are swapped for no reason.

These come from what an app returns from for instance MediaLibrarySession.Callback.onGetChildren():LibraryResult<List>.

From what I've been able to verify, Android Auto seems to do what you're saying.

That's another case. If I'm not mistaken, here the media notification indeed may receive metadata from onMediaMetadatdaChanged() that is converted to the legacy metadata and then System UI uses this.

I have also seen this effect in the notification so it somehow reads information from the same place.
Regarding convertToMediaMetadataCompat(), it is a very simple method, just variable assignments, I don't think it needs to be modified at all.

my app sets the song title field in the metadata to title (e.g., "Viva la vida") and
sets the file name to displayTitle (e.g., "01 Viva la vida.mp3").
In this case, I think your app should not do that.

Adding to that, and maybe explaining the confusion: The display title is meant to be the preferred string that is displayed to the user instead of the regular title. This is pretty much the reason we prefer the displayTitle field over title if both are set. And I guess from your example you may want to set the two fields the other way round?

As previously stated, the core issue is:
When displayTitle is not null, why does convertToMediaDescriptionCompat() return a MediaDescriptionCompat containing displayTitle instead of title?
Line 850 of LegacyConversions prioritizes displayTitle by assigning it to title, even if metadata.title is present and contains a value. This effectively ignores the value of metadata.title.


Add possibility to run integration tests using key file authentication

Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

Fixes SNOW-1141159

Please describe how your code solves the related issue.

This enables developers that use key file authentication to run integration tests when testing their code locally.

I'm closing the PR, please free feel to reopen if you want anything else


At start up, validation collects validationIndicatorCol on the driver leading to crashes/hangs.

When the validation feature is in use, the validationIndicatorCol is collected on the driver and then broadcast to all the workers. If the data set is large enough, then this results in out of memory errors and really long hangs on the driver.
You can see the problem at
https://github.com/Azure/mmlspark/blob/f2bf39fb02ad648de7b5fe77a37ec35919162b5a/src/main/scala/com/microsoft/ml/spark/lightgbm/LightGBMBase.scala#L123
where .collect() is called before the info being broadcast to the worker.

Hi, folks!
validationIndicatorCol (str): Indicates whether the row is for training or validation
def setValidationIndicatorCol(value: String): this.type = set(validationIndicatorCol, value)
}
Is it means just string col with two values "training" or "validation" litteraly?

"Is it means just string col with two values "training" or "validation" litteraly?"
sorry this reply is so late, it's a boolean col, not a string col - for whether the dataset is in validation set or training set


is AWS Redshift supported?

Hi 👋🏼
I was just wondering if AWS Redshift is supposed to work with Atlas since if I run
psql "postgresql://USER:PASSWORD@HOST:PORT/DBNAME"

the connection is made
but doing
atlas schema inspect --url "postgres://USER:PASSWORD@HOST:PORT/DBNAME?sslmode=disable"

throws the following error Error: postgres: unexpected number of rows: 0
Any thoughts? Thanks

Hi @jccguimaraes
Thanks for reaching out. Currently Redshift is not supported by Atlas. Atlas should be able to initiate a connection since iirc Redshift supports the pg wire format, but my guess is that the information schema tables are structured differently which is probably why you're seeing that error.
Support for many more databases will come to Atlas this year, can you share information about your use case for using Atlas
with Redshift?
Thanks

Hi @rotemtam,
Thank you for the reply, so bottom line I was keen on using Atlas to manage our AWS Redshift databases through GitHub Actions or other ways.
We're constantly changing the cluster due to the nature of the project and deploying through Terraform so it would be ideal to have Atlas implemented to being able to manage instead of using a TF provider to do that 😓 .
Hope it clears what is my use case for Atlas.

Do you plan to manage users and migrations as well? or just schemas?

Thanks for the reply. That sounds really cool. Do you mind joining our Discord server? we have some cool things coming this quarter that might be interesting to you.
https://discord.gg/zZ6sWVg6NT
And yes Atlas will be used to manage users and grant permissions and support more traditional "versioned migrations". A terraform integration is also in the works

of course. thanks

I may be interested also by RedShift support. Looking forward to it

I'm also interested on the support for Redshift

And we are also really interested for Redshift support :)

Would love to see this for Redshift! :)

Hey @jccguimaraes @alexlobanov @dnascimento @fabricef-p @JianTray ,
@a8m and I are looking to interview some Redshift users about your expectations and problems that Atlas can solve. Feel free to schedule some time with us here, if this is still relevant:
https://calendly.com/rotemtam-ariga/atlas-redshift-users

Hey all!
Redshift support was added in Atlas 0.23. See: https://atlasgo.io/blog/2024/05/21/atlas-v-0-23
Please give it a try and share your feedback with us here or on our Discord server.


Make code base compliant with PEP-8 E-261.

This PR will track the commits which will eventually lead our code base to 100% compliance with the PEP-8 E-261. According to E-261 two spaces must be used before making an inline comment.

Automated message from Dropbox CLA bot
@adnrs96, it looks like you've already signed the Dropbox CLA. Thanks!

In this Last 10 commits relating to zerver/views can cause possible conflicts to other PR's which would be as follows:
zerver/views/auth.py PR#1747(+48-26) PR#3318(+28-23)
zerver/views/home.py PR#4156(+1-0) PR#3317(+1-0) PR#3318(+25-21) PR#3382(+1-0) PR#4452(+5-12)
zerver/views/integrations.py PR#3318(+9-6)
zerver/views/invite.py PR#3318(+8-9)
zerver/views/messages.py PR#4110(+1-1) PR#4177(+3-0) PR#4279(+24-0) PR#4793(+11-1) PR#3318(+41-43) PR#1289(+21-8) PR#3346(+5-1) PR#378(+1-1) PR#2450(+3-0) PR#3051(+32-6)
zerver/views/presence.py PR#3318(+4-3)
zerver/views/realm.py PR#4156(+6-1) PR#3318(+15-16) PR#2997(+6-4) PR#4586(+3-0)
zerver/views/registration.py PR#3318(+34-29) PR#4352(+1-1) PR#4393(+14-28)
zerver/views/streams.py PR#1122(+24-14) PR#3318(+34-25) PR#1432(+13-2) PR#2984(+10-1)
zerver/views/user_settings.py PR#3318(+26-17) PR#850(+16-1) PR#382(+9-2)
Also the commit relating to tools/lint has possible conflict:
tools/lint PR#4792(+2-0) PR#4723(+4-2) PR#4756(+1-0)
Although I feel all these conflicts are very minimal or the PR they are conflicting is most probably already stale from the looks at least.
There are still files pending to do for this PEP8 standard stuff, maybe sometime soon i can get them done as well.

I reviewed the conflicts; a couple of those PRs were ready to be closed, which I did, and most of the rest don't seem to be material conflicts.  So I went ahead and merged this, thanks @adnrs96!
It looks like we only have a few hundred to go!


"aurelia_framework_1.singleton is not a function" after bundeling

@MaartenThomassen commented on Fri Mar 04 2016
Hello,
In my Aurelia app, I am using a Typescript development environment which transpiles to ES5 and in my code i use the @autoinject attribute and Aurelia's dependency injection framework.
When I build my app and run it locally, everything works fine. When I bundle my app (i made 2 bundles, one with all Aurelia deps i use and 1 with all my own code), i get the following error:
system.js:41 Uncaught (in promise) Error: aurelia_framework_1.singleton is not a function
This error in turn causes:
Error: key/value cannot be null or undefined. Are you trying to inject/register something that doesn't exist with DI?
I did some debugging, and when running without bundles, the aurelia_framework_1 module contains both the .singleton() function definition and the .FrameworkConfiguration.singleton() . When I run with bundles, the aurelia_framework_1 module does NOT contain the .singleton() function definition but DOES contain the .FrameworkConfiguration.singleton().
I can't figure out what the difference between the unbundled and bundled versions are. I also can't figure out how, at runtime, the framework "copies" the .singleton() function directly in the aurelia_framework_1 module, since when i dove into the Aurelia code and Typescript definitions, the .singleton() function is only present in the FrameworkConfiguration whitin the aurelia-framework module.
The error happens when i try to do a custom registration into the DI container:
aurelia.container.registerSingleton(UserManager_1.UserManager);
Where UserManager is a class in my own UserManager module.
NOTE: I use the latest version of Aurelia Beta
"aurelia-framework"<EMAIL_ADDRESS>NOTE 2:
The error happens exactly at this line:
UserManager = __decorate([aurelia_framework_1.singleton(), aurelia_framework_1.autoinject, __metadata('design:paramtypes', [IAuthentication_1.IAuthentication, ToCRUDConverter_1.ToCRUDValueConverter])], UserManager);
At the bottom of  'System.register("src/libraries/UserManager.js",...' int he bundled file. there, both the aurelia_framework_1.singleton() and aurelia_framework_1.autoinject are undefined, causing the UserManager to not get defined, breaking the DI function call mentioned above.

@ahmedshuhel Please take a look at this.

Any updates on this?

This is a bug in the Babel compiler or SystemJS where it isn't treating re-exported values correctly. To get around it, import from the original module that the export comes from. For example singleton is re-exported from 'aurelia-frameworkfor convenience, but it is originally exported fromaurelia-dependency-injection` so import it from there instead. If that doesn't work, then there may be an issue with your bundle configuration. Let us know.

@EisenbergEffect Thank you for the workaround. I'm going to implement this today and report back to you.
For the record, i am not using Babel (im directly compiling typescript with the typescript version included with gulp-typescript to ES5), so its possibly a bug in SystemJS in combination with the Aurela Bundler.

@EisenbergEffect
I replaced the (auto)inject and singleton imports as you suggested, also replaced my binding imports to import directly from aurelia-templating.
This "seems" to fix the problem, however, I am now getting a different issue, which is also probably a SystemJS issue but since its still in combination with the Aurelia loader, I'll post it here, perhaps you can suggest a better place for me to post it:
When using the text plugin, the aurelia bundler compiles the bundled files with references to text files inside the bundle like this:
(function() {
var define = System.amdDefine;
define("github:necolas/normalize.css<EMAIL_ADDRESS>[], function() {
  return <TEXT HERE>;
});

However, as soon as SystemJS configures itself (at line 1804 of system.js), it decanonicalizes the bundle dependencies (at line 1902: var normalizedBundleDep = loader.decanonicalize(cfg.bundles[p][i]);)
However, this cuases SystemJS to register the above dependency in its loader bundle as:
"http://localhost:9000/jspm_packages/github/necolas/normalize.css<EMAIL_ADDRESS>Adding the entire "http://localhost....." bit to the text plugin bit which is not present in the actual bundle .js file, causing the lookup of the file to fail.
Any idea how to fix this?

@ahmedshuhel Can you take a look at this please?

Actually @MaartenThomassen I'm going to close this issue. Can you open a new issue on the bundler repo?


Code duplication in keybindingsSync.ts <=> tasksSync.ts

Running npx jscpd . -c ./.jscpd.json over our sources with .jscpd.json containing:
{
	"ignore": [
		"**/*.svg",
		"**/node_modules/**",
		"**/.git/**",
		"**/fixtures/**",
		"**/*.test.ts",
		"**/*.integrationTest.ts",
		"**/keybinding/test/**",
		"**/browser/keyboardLayouts/**",
		"**/out/**",
		"test/**",
		"extensions/**"
	],
	"reporters": ["console"],
	"minLines": 30
  }

Revealed:
Clone found (typescript):
 - src/vs/platform/userDataSync/common/keybindingsSync.ts [183:28 - 223:28] (40 lines, 355 tokens)
   src/vs/platform/userDataSync/common/tasksSync.ts [146:22 - 186:22]

Restructuring this is not worth an engineering effort and can be error prone.


fix(floating-menu): positioning in scrollable container maintained

Override style of default render to position offscreen to the right
to prevent the window.scrollY from being affected right before
measuring the size of the menu.
This seems to only be an issue in the latest version of react (16.3) probably
due to the asynchronous rendering changes.

Thanks alot @psachs21 for finding the issue and trying to fix! The fix signals that we need to better understand the problem ourselves. Meanwhile, if you have more details on your findings it’ll very nice. Thanks!

@asudoh the issue is pretty simple: when the menu first renders, it's rendered as is (without position: absolute) in the regular flow of the document. So depending on the layout of the document, it may adjust the scrollY position (if there are enough elements). This was theoretically a bug before react 16.3, but I suspect was only exposed due to async rendering changes in core React. I think the fix of positioning the element of screen is the easiest solution.

@asudoh I've also been able to reproduce the issue in the playground, you just need to set some css:
html, body, #root, [role='main'] {
  height: 100%;
}

And make sure your example story has a top level div that also has height: 100%.
I haven't submitted an update to the story because I don't think it serves much of a purpose other than to demonstrate the bug.


added few changes and made navbar responsive

based on issue #1
also pls refer to changes.txt

Hello @SaahilSabu  , There is a conflict with the style.css file due to recent file updates.
If you could please resolve it, I will merge it.
Thank You

@Nish251103 i have resolved the issues pls check once again to see if its working

@Nish251103 i have resolved the issues pls check once again to see if its working
It works Perfectly.
Thank you


Issue Installing simple_ra on linux

Hi! I'm trying to install simple_ra on linux, using this documentation and the README file here. I've fetched your repository, and installed build_gnuradio, and made it executable.
This is the error that I get:
make
Using .:{{}:/usr/local/lib/python2.7/dist-packages:}:/usr/lib/python2.7/dist-packages/: for compile...
grcc -d . simple_ra_receiver.grc
Block key "ra_synch_folder2" not found
Block key "vector_normalize" not found
[INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.git-128-g379f922d
serial import failed.  You'll be missing calibration functionality
Validation failed:

Block - blocks_keep_one_in_n_1 - Keep 1 in N(blocks_keep_one_in_n):
    Source - out(0):
   	 Port is not connected.

Block - blocks_vector_to_stream_1 - Vector to Stream(blocks_vector_to_stream):
    Sink - in(0):
   	 Port is not connected.

Block - pulsar_probe - Probe Signal Vector(blocks_probe_signal_vx):
    Sink - in(0):
   	 Port is not connected.
Error during file compilation.
Makefile:15: recipe for target 'simple_ra_receiver.py' failed
make: *** [simple_ra_receiver.py] Error 1

Hi, elliesch.
Try installing this first: https://github.com/patchvonbraun/gr-ra_blocks

@patchvonbraun (Very) late reply, but could you mention what the differences are between the new spectro_radiometer application and this version (simple_ra)? Not sure which one I should install and use.
Thanks!

On 11/20/2018 09:30 PM, 0xCoto wrote:

@patchvonbraun https://github.com/patchvonbraun (Very) late reply,
but could you mention what the differences are between the new
spectro_radiometer application and this version (simple_ra)? Not sure
which one I should install and use.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/patchvonbraun/simple_ra/issues/3#issuecomment-440506172,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAx5L2FZzJwa8XzAnHqMSQLqHtjcyEMjks5uxLrKgaJpZM4M123M.

Simple_ra uses the now-obsolete WxGUI toolkit, and has a more-ambitious
(and thus, less-performant) internal structure.
The spectro_radiometer app uses the newer QtGUI toolkit, and is the one
that is getting all the maintenance love these days.

That sounds like a reasonable reason for me to shift to the new repository then! Is there a document or a README that describes how to compile/install/run spectro_radiometer?

On 11/21/2018 12:46 PM, 0xCoto wrote:

That sounds like a reasonable reason for me to shift to the new
repository then! Is there a document or a README that describes how to
compile/install/run |spectro_radiometer|?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/patchvonbraun/simple_ra/issues/3#issuecomment-440754142,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAx5L_TLB8P5tEIxUZTb9rbjqtMNAt0yks5uxZGCgaJpZM4M123M.

It comes with a Makefile.
There's no documentation at this point.  My "to do" list is annoyingly
large.
It requires a reasonably-recent installation of Gnu Radio + friends
If you run it with the --help option, it displays the command-line
parameters.

Oh, I didn't notice, thanks! Are there any screenshots available, or would everything look similar to simple_ra's plots?

On 11/21/2018 12:54 PM, 0xCoto wrote:

Oh, I didn't notice, thanks! Are there any screenshots available, or
would everything look similar to |simple_ra|'s plots?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/patchvonbraun/simple_ra/issues/3#issuecomment-440756942,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAx5L2l8hTnZcrOT63NctgFj3-gndrrtks5uxZM_gaJpZM4M123M.

No, I don't have any screenshots.
The visual organization is a bit different than simple_ra, but overall
functionality is the same.

@patchvonbraun So, I tried installing spectro_radiometer but I get an error:
coto@ubuntu:~/Documents/spectro_radiometer$ ls
do_interf.awk  Makefile  README.md  spectro_helper.py  spectro_radiometer.grc
coto@ubuntu:~/Documents/spectro_radiometer$ make
grcc -d . spectro_radiometer.grc
Warning: Can't parse color code "#000" for domain "gr_message"
Warning: Can't parse color code "#000" for domain "gr_stream"
Block key "osmosdr_source" not found
Validation failed:

Block - fft_filter_xxx_0 - FFT Filter(fft_filter_xxx):
	Sink - in(0):
		Port is not connected.

Block - fft_filter_xxx_0_0 - FFT Filter(fft_filter_xxx):
	Sink - in(0):
		Port is not connected.
Error during file compilation.
make: *** [Makefile:2: spectro_radiometer.py] Error 1
coto@ubuntu:~/Documents/spectro_radiometer$

On 03/09/2019 08:57 AM, 0xCoto wrote:

@patchvonbraun https://github.com/patchvonbraun So, I tried
installing spectro_radiometer but I get an error:
|coto@ubuntu:~/Documents/spectro_radiometer$ ls
do_interf.awk  Makefile  README.md  spectro_helper.py  spectro_radiometer.grc
coto@ubuntu:~/Documents/spectro_radiometer$ make
grcc -d . spectro_radiometer.grc
Warning: Can't parse color code "#000" for domain "gr_message"
Warning: Can't parse color code "#000" for domain "gr_stream"
Block key "osmosdr_source" not found
Validation failed:
Block - fft_filter_xxx_0 - FFT Filter(fft_filter_xxx):
Sink - in(0):
Port is not connected.
Block - fft_filter_xxx_0_0 - FFT Filter(fft_filter_xxx):
Sink - in(0):
Port is not connected.
Error during file compilation.
make: *** [Makefile:2: spectro_radiometer.py] Error 1
coto@ubuntu:~/Documents/spectro_radiometer$
|
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/patchvonbraun/simple_ra/issues/3#issuecomment-471179242,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAx5L8gfLTxw-GvGj5Q6ZTsG2AQYq-eoks5vU72sgaJpZM4M123M.

Your Gnu Radio installation doesn't have gr-osmosdr in it.
You'll need those blocks -- they provide a generic interface to various
radio hardware.

After doing some research, I still can't find a way for GNU Radio to detect its presence (after my attempt to install it). By the way when I open up GNU Radio, I only see "Core" on the box on the right, while others seem to have more 'categories' there. Is this normal, or is GNU Radio installation generally buggy in Ubuntu?

On 03/09/2019 10:28 AM, 0xCoto wrote:

After doing some research, I still can't find a way for GNU Radio to
detect its presence (after my attempt to install it). By the way when
I open up GNU Radio, I only see "Core" on the box on the right, while
others seem to have more 'categories' there. Is this normal, or is GNU
Radio installation generally buggy in Ubuntu?

How did you install Gnu Radio?  What version of Ubuntu?
I'm running 18.04 on some of my machines, and I just installed the
standard packages, and I have everything.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/patchvonbraun/simple_ra/issues/3#issuecomment-471189266,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAx5LxNCj-tclhUyoXLkTBDHidWD5KwDks5vU9MpgaJpZM4M123M.

Update: I just followed this video and it worked! https://www.youtube.com/watch?v=YN2WfutNJQE
Gonna let you know if I have any question with using the program, thanks!


close() sets the internal stream pointer to NULL

I split this into three commits, because they have quite different implications.
I think setting the stream pointer to NULL (abf1f19839059453436738d8d2979d22772c101c) has no negative implications.
AFAICT, the error messages are the same as when using an invalid pointer after close(). But it might be safer on some systems (see mailing list link below).
The .closed property (8370db2cf4ff08a23119824f2cecd08ad15a1165) seems harmless, Python file objects tend to have such a thing, so it shouldn't be too uncommon.
The last commit (9af4e43a387e312e1c79e35eacb65b138b816c83) actually changes the behavior. Instead of throwing an exception, it now returns active == False on closed streams (without actually checking activeness).
I think that is logically justifiable, because a closed stream can never ever be active, but I'm not quite sure.
The background to all this is that a derived class might have some state (as "private" instance variables) that's written by the callback function (possibly in C and without holding the GIL!). While the callback is running, this shouldn't be accessed, but afterwards it's OK. Even after the stream was closed.
If I'm not mistaken, this cannot be checked with the current public API, but it could be checked with a combination of .closed and .active. Or, with the third commit, this could simply be checked by .active alone.
@tgarc You seem to be an expert in that area, what do you think about this?
See also https://lists.columbia.edu/pipermail/portaudio/2017-March/001074.html.

Hey mgeier. The closed property seems like a nice addition. What was the motivation to add these changes though? These behaviors kind of diverge from the PortAudio stream's behavior.
I was interested in making changes like this because I wanted to use Streams in a multi-threaded context where I wanted to do things like for example abort the stream in the main thread if it had not already been closed by the subthread. (Of course, I still had to add a stream mutex to make these functions thread safe.)
Either way, I do think the closed property is a useful feature. And I can't see anything about these changes that could be harmful or limiting to users. I'm in favor of these changes 👍

Thanks @tgarc, I very much appreciate your feedback!
I tried to hint on the general motivation above, but I'll make it more concrete: in rtmixer (currently in the fetch-stats branch) I'm planning to add a .stats attribute (a property, to be more exact) to get e.g. the number of xruns that happened during the runtime of the callback. This attribute should not be queried while the callback is running, because the underlying structure is not protected by a lock or anything. For this reason, I'm checking stream.active in the implementation of the property.
So far so good. But I would like to use it somewhat like that:
with rtmixer.Mixer() as stream:
    # run the stream for some time
print(stream.stats.output_underflows)

The problem is that exiting the context manager calls close() (which I think makes sense), which invalidates the stream pointer, and the check for stream.active that's done while getting stream.stats will raise an exception.

These behaviors kind of diverge from the PortAudio stream's behavior.

Yeah, that's why I'm a bit unsure about this.
It is a change of behavior, but this change is either invisible to users (setting the pointer to NULL) or only changes errors into non-errors.

PS: I would like to add that the checking .closed in .active is really only a convenience, if we don't do this, users would just have to do this on their own, which wouldn't be a big problem, but I think it would be a bit annoying.
I also want to point out that .active and .stopped would be somewhat asymmetrical in my current proposal, because .stopped would still raise an exception after .close().
Initially, I thought that after .close() we cannot tell if a stream was "stopped". But now that I'm thinking about it, there might also be a logic argument for that: the documentation says that .close() behaves as if abort() had been called, therefore a .closed stream must always be .stopped, right?
Shall I adapt the .stopped property, too?

I would adapt the .stopped property like you said to be more consistent.
In general I would say that if it ain't broke don't fix it, but I think the change in behavior is okay and will make things a little more robust.


Checksum Methods

Added

to_checksum_address that returns a checksum address
is_valid_checksum_address that returns a boolean if that address is checksummed
duplicated the tests from ethereumjs/ethereumjs-util

First time really working with elixir so feel free to gut it out  :)

This is awesome! Very lightweight.
A couple things:

Use this method ExthCrypto.Hash.Keccak.kec for the hashing.
Check out the travis build (I think it might've been broken before by me lol so no worries)

Oh gotcha! Took me a while to find a hashing method, that one looks good I implemented it with that function
Travis build is passing now also

Dope!


add rustls feature

By default, reqwest uses native-tls. This adds a feature flag to optionally use rustls-tls instead

@kaichaosun switched to using reqwest/default

Thank your for the PR!

Thanks for your review @kaichaosun :) Could you make a release with this patch please? :pray:

@MarinPostma released!


New pipeline to copy CodeQL work items from ADO to GitHub

Fixes #minor
Description
CodeQL analysis creates work item bugs in ADO here: https://dev.azure.com/fuselabs/SDK_v4/_workitems/recentlyupdated/
This new pipeline, Copy-CodeQL-Workitems-to-Github, copies those work items to their appropriate repos in GitHub.
Work items for botbuilder-dotnet are copied here: https://github.com/microsoft/botbuilder-dotnet/issues
Work items for botbuilder-js are copied here: https://github.com/microsoft/botbuilder-js/issues
After copying, each work item is tagged and commented thus:

Sample: https://dev.azure.com/fuselabs/SDK_v4/_workitems/edit/77284/
Each new GitHub issue is assigned to tracyboehrer, labeled "bug", and shows a link back to the originating work item, thus:

Sample: https://github.com/microsoft/botbuilder-dotnet/issues/6486
Specific Changes
Create pipeline (see link above).
Add Powershell script.

Pull Request Test Coverage Report for Build 325045

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.01%) to 79.07%

Files with Coverage Reduction
New Missed Lines
%

/libraries/AdaptiveExpressions/BuiltinFunctions/GetNextViableTime.cs
1
90.91%

/libraries/AdaptiveExpressions/BuiltinFunctions/GetPreviousViableTime.cs
1
90.91%

/libraries/Microsoft.Bot.Connector.Streaming/Application/TimerAwaitable.cs
1
68.25%

/libraries/Microsoft.Bot.Streaming/Payloads/StreamManager.cs
1
90.0%

Totals

Change from base Build 324277:
-0.01%

Covered Lines:
25579

Relevant Lines:
32350

💛  - Coveralls


Additional pagination members

Perhaps I am missing something, but if the server needs to define additional members of links, related to pagination, i.e. something beyond prev, next, first, last, how can it be done? For example, the server wishes to return the total number of pages, or something else?
Perhaps it would be even better to group pagination-related members under a separate member of links, e.g., under links.pagination, to avoid polluting the namespace of links with arbitrary custom keys?
@ColtonProvias, this should hopefully resolve #384. I would appreciate your opinion on it.

I'm :+1: to this adjustment. @dgeb?

A link object can also contain a meta member "that contains non-standard meta-information about the relationship."
In this way, meta-information can be included about relationships in the same way that it can be included about primary resources.

I'm also pro keeping the pagination keywords at the top-level of the links object and just putting extra stuff in "meta". Because the user can't add custom pagination members anyway without using "meta" (to preserve future extensibility for us), and keeping the keys at the top level makes them much more easily interpretable as standard link relations—the keywords for which we're not-so-accidentally reusing.

In my apis I never use pagination, I find offset and limit to be far more versatile and more fundamental than an artificial pages.
I support just using meta as @dgeb has suggested and not try to pick a flavor of partial collections.

I'm in favor of closing this, but willing to hear rebuttals.

that contains non-standard meta-information about the relationship

@dgeb, perhaps I'm missing something, but I thought top-level links does not allow meta. That said, I agree that meta would be a better place for this.
Should I update this PR to add meta to top-level links instead of its current content?

I thought top-level links does not allow meta

That's correct - I was referencing the top-level meta.

Should I update this PR to add meta to top-level links instead of its current content?

I don't think this is necessary.

I am also :-1: , for the same reasons as @dgeb

@dgeb, I see now, thanks! Closing it, although I still find it somewhat weird that

custom pagination information must be placed under another top-level key (meta) than the reserved 4 pagination links, and
if an API chooses to define other pagination links besides the reserved 4, those links will also have to go under top-level key meta.


C2ME incompatibility

https://discord.com/channels/805088174085767219/842663123549683742/985937467834265630
https://discord.com/channels/756715786747248641/855382586193215489/985941140329070653

added a temporary solution in 96c01eb4cbcf947ec4bf99dd9385ab8f5b4c1189


Fix ReflectionProbe AABB

This PR resolves some issues in the AABB calculation of the reflection probe:

The AABB of ReflectionProbe is now calculated from corner to corner
Removed the origin_offset from the AABB calculation. Origin_offset should not have any bearing on the bounding box.

Additionally I've also removed the green wire-frame, since the bounding box is displayed on top of it anyways.

4.3
This PR

Thanks!


feat: delete unused function: HelmReconciler.DeleteAll

Please provide a description of this PR:
delete unused function: HelmReconciler.DeleteAll()

Hi @chinaran. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/test unit-tests

@chinaran: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@chinaran: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
691c2104280d37faedc56b764f887f9f90d5744f
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes


⚠ Fortnite has degraded performance

In 702bd65, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1626 ms

Resolved: Fortnite performance has improved in d4ab969.


Types problem when using <script setup> alongside normal <script> since v1.8.14

Hello, I have a types problem in vue projects where <script setup> is being used alongside the normal <script>. Since v1.8.14 and v1.8.15, property types inside the normal <script> aren't being recognized. Before v1.8.14 using both at the same time used to work without any problem and properties were all recognized, I don't know if the changes in recent versions broke something or if this is intended to encourage not using both definitions. I'll be looking forward to your response thanks <3

And when removing  <script setup>  the problem disappears

Example code:
<script setup lang="ts">
// some code
</script>

<template>
  {{ hello_world }}
</template>

<script lang="ts">
export default {
  data () {
    return {
      hello_world: "Hello World!"
    };
  }
};
</script>

Duplicate of #3598


Web catch-up updates

Support RenderState (SamplerState, BlendState, RasterizerState)
ESSL Definition for GLSL ES shaders

Great!


July 2021 feature set

UCSC genome browser-like annotation block style
UCSC genome browser-like intron, exon, 5'UTR, 3'UTR feature count labeling
Boxplot (Tukey box-and-whisker) annotation block style
Color applied from BED12 annotation field (unless overwritten by user-specified options, or unspecified and determined by strand, if available)
Canonical or APPRIS isoform highlight flag and color options
Improved PNG/SVG export for all blockStyle modes
Can now specify maximum row rendering for constrained device viewport (i.e., mobile)

Some example animations of block style modifications:

Feature counts and custom coloring:

UCSC genome browser-like block style:

Tukey boxplot block style:

Canonical isoform highlighting:

Just wanted to check in on this.

I will have a look today. Sorry it took so long.

Thanks — will work through these and follow up.

I think I resolved the concerns outlined here, except for the question about how to get the "current" higlass container.
I may add some more commits from performance testing, as it does a bit more work than the generic gene annotations track and so slows down rendering a bit more than we were hoping.
Still, if there are any outstanding issues with what is there currently, please let me know!

I'm not entirely sure what to look for. Do you have a viewconf I can use to try to replicate this locally?

You are not seeing the flickering issue locally? I used the transcript track configuration from https://higlass.io/app/?config=Yzld015XRFaCfCIYbB2MZQ

I'll try to set up a site to load your viewconf to try to reproduce things locally.
I did not see flickering in the GIF you posted. It otherwise looks normal to me, but the amino acid view is not my typical use case.
Is there an easy way to repeat the same animation, but with the stock version of the plugin ("expected" vs "observed")? If not, that's fine.


Profile — Testing #9

Can see bills followed; don't know how to follow organizations
Try to follow an organization on a bill but couldn't click into their bill page

an actual organization has to be:
(these are all backend values)
a) set public: true
this is going to be set to mandatorily true for organizations in the future, but isn't enforced yet as far as I know
b) set organization: true
this is likely to change as the team reorganizes how they want to use the role value

I believe we're planning to get rid of the organization: boolean field and just relying on the role field moving forward

links to public/org pages from testimony should work now
follow related elements (follow button, follow tab) are functional but hidden until email functionality is ready for Prod