A 'not a tty' file generated from the proxy command

For some reasons, a new empty not a tty file is created under my current directory after I've run ssh i-XXXXXXX via this proxy script.
I'm not sure what is causing this, and it's not from the echo ... >/dev/tty line 🤔

thanks for the report I will investigate tomorrow.

I could reproduce this issue only once, however I don't know why this is happening.
I've added a check if tty is available before echo to tty, maybe this helps.

I replaced out redirection from >/dev/tty with >/dev/stderr that way I could get rid of using tty at all.

I could reproduce this issue only once, however I don't know why this is happening.

Hmm... I'm on a mac using zsh, and I can reproduce this all the time.
I did troubleshot this a bit yesterday, and it looks like this empty file was created from the aws CLI calls instead of the echo lines. I'm still not sure why that needs a tty though.

Maybe it happens if you need to enter an MFA token during connecting?

I have the same setup mac an zsh. Maybe it is caused by mfa input?
I use aws-sessen so generate session credentials in upfront, that's why I don't have this file created.
Any I dont know how to fix that aws cli behaviour :-/

Ah... yes, i do have MFA setup for my AWS credentials, and I use aws-vault and setup credential_process in my ~/aws/config to get the admin session via assume-role:
[profile ro]
region=us-east-1
output=json
credential_process=sh -c 'aws-vault exec ro --json 2> $(tty)'
mfa_serial=<MY_MFA_TOKEN>

[profile admin]
source_profile=ro
role_arn=<ADMIN_ROLE>

If I don't have an active session which I've input my MFA token earlier, I couldn't use this SSH proxy setup at all. Now this indeed sounds like related to the issue I'm seeing, but i'm also not sure how to fix this... 🤔

can you try to replace $(tty) by /dev/tty
alternativly you youd use my cli aws-session https://pypi.org/project/aws-session/
it will resolve an arbitrary profile to a session profile (PROFILE_NAME--session) with resolved session  credentials

or maybe try to add -it to sh command like sh -it -c 'aws-vault exec ro --json 2> $(tty)'

or maybe just credential_process = aws-vault exec ro --json --prompt=osascript
thats from the aws-vault documentation see https://github.com/99designs/aws-vault/blob/master/USAGE.md#using-credential-helper


Sample: resize a VMDK

Demonstrate how to resize a VMDK.

Do you solve this issue? if you do ,can you tell how ?


Replay button now will be shown only for the last video in playlist

@VerizonAdPlatforms/mobile-sdk-developers: Please review.

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


[lib] Add missing PerformanceServerTiming definition

Flow's is missing the definition of PerformanceServerTiming.
The exported definition of PerformanceResourceTiming is missing the serverTiming attribute.
PerformanceServerTiming definition : https://www.w3.org/TR/resource-timing-2/#sec-performanceresourcetiming
PerformanceResourceTiming extension: https://w3c.github.io/server-timing/#extension-to-the-performanceresourcetiming-interface

@rittme You will need to rebase on top of latest master, since the base commit you are on uses a xcode target no longer supported by Circle CI.

Thanks @SamChou19815! I rebased it and it seems it's all passing now.


Factor combinations

Combination of factors on the user end? Maybe I'm not using it right, but wondering if instead of looking at counts for link type (positive/null/negative), if you can look at link type X dependent variable (each task), or if it can be setup so the user can create their own combinations. Example, the counts for each dependent variable.

Does this address the issue? The option to add multiple filters should be possible once I update the app. I'll leave the issue open for the meantime.

Yes, I believe so. Except was wondering more on the plot side. For example, if I wanted to look at dependent variable VerbalPairedAssociates and VerbalFluency and then wanted to know the different link types associated with them.


Add view-source support (#118)

https://github.com/sindresorhus/normalize-url/issues/118#issuecomment-687667546
Out of curiosity, how are you even ending up with view-source: URLs?

For example "view-source:view-source:view-source:view-source........." ?
Great, I'll fixed that

@iakgoog That did not answer my question.

My apology. English is not native language.
I'm not sure if I understand your question correctly.
Are you asking me the reason why I decided to contribute to this issue @118?

No, I'm asking you why you need this? Where are you encountering view-source: URLs?

nowhere except View page source on the browser

So why do you need support for it in normalize-url? What's your use-case?

Just in case someone neeed it when they have a list of various kind or URLs to normalize.

Sorry, I'm going to pass on this. I don't want to end up having to support an endless amount of non-standard protocols. And you have not presented an actual use-case or need for this.

I already commented in https://github.com/sindresorhus/normalize-url/issues/118#issuecomment-687667546 that I welcome a pull request for a better error message, not an implementation for this.

That is acceptable.
Thank you for your time.


writeFile, writeTextFile and renameRundown are unsafe

All of these functions follow this pattern:
try {
    return new Promise(resolve => {
      // ... do stuff
      resolve()
    )
} catch (error) {
  logger.error('spx.writeFile - Error while saving: ' + filepath + ': ' + error);
  return
}

The try block will never fail, as the promise doesn't execute immediately
It should be:
return new Promise((resolve, reject) => {
  try {
    // ... do stuff
    resolve();
  } catch (error) {
    logger.error('spx.duplicateFile - Error while duplicating: ' + fileRefe + ': ' + error);
    reject();
  }
})

I will keep these here as a reminder for a future update. Thanks for pointing this out!


Erro when compiled pure start version in Phonegap Build

Error - Some official plugins have to be updated if using PhoneGap >= 4.0.0. Please upgrade the version of any plugins that may include the following file: FileTransfer.java - You can fix this here

I use phone gap version 3.7 to resolve that error for now.

Thank. Its working
I put  in my config.xml and working.
Thanks


Broken link on documentation website - docs/example

Caught this broken link while reading the docs:

URL: https://drift.simonbinder.eu/docs/examples/

Good catch, thank you! I have updated that page in ca6758d8b1907ce0be839a527cb6626fa7e420b7.


Amazon.S3.Transfer TransferUtility.UploadAsync() throwing exception under .Net 8 with latest MS and AWS SDK NuGet packages

Describe the bug
We have updated our Batch tool to run under .Net 8 and also updated all the NuGet packages to the latest, this is now causing a exception to be thrown from the class method TransferUtility.UploadAsync().
If the Batch tool NuGet packages are reverted to old versions then everything works as expected and the file uploads to S3.
The Batch tool is running on the AWS Batch Fargate compute environment.
Previous NuGet package versions when the exception did not happen, worked correctly:
"Amazon.Extensions.Configuration.SystemsManager" Version="5.0.2"
"AWSSDK.Extensions.NETCore.Setup" Version="3.7.5"
"CommandLineParser" Version="2.9.1"
"Microsoft.Extensions.Configuration.Json" Version="6.0.0"
"Microsoft.Extensions.DependencyInjection" Version="6.0.1"
"Microsoft.Extensions.Hosting" Version="6.0.1"
"Microsoft.Extensions.Options.ConfigurationExtensions" Version="6.0.0"
"Serilog.Sinks.Console" Version="4.1.0"
"AWSSDK.RedshiftDataAPIService" Version="<IP_ADDRESS>"
"AWSSDK.S3" Version="<IP_ADDRESS>"
"CsvHelper" Version="30.0.1"
"JWT" Version="10.0.2"
"Microsoft.Extensions.Options" Version="6.0.0" />
"Polly" Version="7.2.3" />
"RestSharp" Version="109.0.1" />
"Serilog" Version="2.12.0" />
Latest NuGet package versions where the exception is happening, not working correctly:
"Amazon.Extensions.Configuration.SystemsManager" Version="6.2.1"
"AWSSDK.Extensions.NETCore.Setup" Version="3.7.301"
"CommandLineParser" Version="2.9.1"
"Microsoft.Extensions.Configuration.Json" Version="8.0.0"
"Microsoft.Extensions.DependencyInjection" Version="8.0.0"
"Microsoft.Extensions.Hosting" Version="8.0.0"
"Microsoft.Extensions.Options.ConfigurationExtensions" Version="8.0.0"
"Serilog.Sinks.Console" Version="6.0.0"
"AWSSDK.RedshiftDataAPIService" Version="3.7.400.4"
"AWSSDK.S3" Version="3.7.400.4"
"CsvHelper" Version="33.0.1"
"JWT" Version="10.1.1"
"Microsoft.Extensions.Options" Version="8.0.2"
"Polly" Version="8.4.1"
"RestSharp" Version="111.4.1"
"Serilog" Version="4.0.1"
Running under the .Net 8 runtime makes no difference, the S3 method works as expected with the old NuGet package versions. The issue is a NuGet library version update that has introduced a new bug.
Expected Behavior
The method completes successfully and uploads the file to S3.
Current Behavior
The exception details are as follows:
exception={
"AmazonId2": "hidden",
"AmazonCloudFrontId": null,
"ResponseBody": null,
"Message": "The request signature we calculated does not match the signature you provided. Check your key and signing method.",
"ErrorType": 0,
"ErrorCode": "SignatureDoesNotMatch",
"RequestId": "hidden",
"StatusCode": 403,
"Retryable": null,
"Data": {
},
"InnerException": {
"Response": {
"StatusCode": 403,
"IsSuccessStatusCode": false,
"ContentType": "application/xml",
"ContentLength": 0,
"ResponseBody": {
  }
},
"Message": "Exception of type 'Amazon.Runtime.Internal.HttpErrorResponseException' was thrown.",
"Data": {

},
"InnerException": null,
"HelpLink": null,
"Source": "AWSSDK.Core",
"HResult": -2146233088,
"StackTrace": " at Amazon.Runtime.HttpWebRequestMessage.ProcessHttpResponseMessage(HttpResponseMessage responseMessage)\n at Amazon.Runtime.HttpWebRequestMessage.GetResponseAsync(CancellationToken cancellationToken)\n at Amazon.Runtime.Internal.HttpHandler`1.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.RedirectHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.Unmarshaller.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.S3.Internal.AmazonS3ResponseHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.ErrorHandler.InvokeAsync[T](IExecutionContext executionContext)"

},
"HelpLink": null,
"Source": "AWSSDK.Core",
"HResult": -2146233088,
"StackTrace": " at Amazon.Runtime.Internal.HttpErrorResponseExceptionHandler.HandleExceptionStream(IRequestContext requestContext, IWebResponseData httpErrorResponse, HttpErrorResponseException exception, Stream responseStream)\n at Amazon.Runtime.Internal.HttpErrorResponseExceptionHandler.HandleExceptionAsync(IExecutionContext executionContext, HttpErrorResponseException exception)\n at Amazon.Runtime.Internal.ExceptionHandler`1.HandleAsync(IExecutionContext executionContext, Exception exception)\n at Amazon.Runtime.Internal.ErrorHandler.ProcessExceptionAsync(IExecutionContext executionContext, Exception exception)\n at Amazon.Runtime.Internal.ErrorHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.Signer.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.S3.Internal.S3Express.S3ExpressPreSigner.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.EndpointDiscoveryHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.EndpointDiscoveryHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.CredentialsRetriever.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.RetryHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.RetryHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.CallbackHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.S3.Internal.AmazonS3ExceptionHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.ErrorCallbackHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.Runtime.Internal.MetricsHandler.InvokeAsync[T](IExecutionContext executionContext)\n at Amazon.S3.Transfer.Internal.SimpleUploadCommand.ExecuteAsync(CancellationToken cancellationToken)\n at
Our code code methods
}
Reproduction Steps
Code where the method is called:
public async Task WriteFileToS3Async(Stream stream, string outputFileName)
{
var s3Utility = new TransferUtility(_client);
await s3Utility.UploadAsync(stream, $"{_environmentVariables.S3BucketName}/{_environmentVariables.OutputDir}", outputFileName);
}
The class member '_client'  object is a IAmazonS3 interface that is injected on app start-up i.e. 'services.AddAWSService IAmazonS3 ();'
The 'stream' object passed in is a FileStream type.
Possible Solution
No response
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
"Amazon.Extensions.Configuration.SystemsManager" Version="6.2.1"
"AWSSDK.Extensions.NETCore.Setup" Version="3.7.301"
"CommandLineParser" Version="2.9.1"
"Microsoft.Extensions.Configuration.Json" Version="8.0.0"
"Microsoft.Extensions.DependencyInjection" Version="8.0.0"
"Microsoft.Extensions.Hosting" Version="8.0.0"
"Microsoft.Extensions.Options.ConfigurationExtensions" Version="8.0.0"
"Serilog.Sinks.Console" Version="6.0.0"
"AWSSDK.RedshiftDataAPIService" Version="3.7.400.4"
"AWSSDK.S3" Version="3.7.400.4"
"CsvHelper" Version="33.0.1"
"JWT" Version="10.1.1"
"Microsoft.Extensions.Options" Version="8.0.2"
"Polly" Version="8.4.1"
"RestSharp" Version="111.4.1"
"Serilog" Version="4.0.1"
Targeted .NET Platform
.Net 8
Operating System and version
AWS Batch Fargate, Linux docker container

Hi @AlexanderDarbyVerisk,
Thank you for reporting the issue. To confirm, the new version of AWSSDK.Core is 3.7.400.4 or above, right?
Also, it would be great if you are able to provide a self-contained code sample that can help to reproduce the error reliably.
Regards,
Chaitanya

It is a bit strange though that the latest version of the AWS NuGet pacikage AWSSDK.Extensions.NETCore.Setup is version 3.7.301?
The previous old version was 3.7.5 that we used.
Looks like the latest version number has gone down?

@AlexanderDarbyVerisk Do you still see the error if you change your code to use this instead?
await s3Utility.UploadAsync(stream, _environmentVariables.S3BucketName, $"{_environmentVariables.OutputDir}/{outputFileName}");

The SDK used to support a key prefix (i.e. the / character) in the bucket name but that's changed in the latest version of the AWSSDK.S3 package (see https://github.com/aws/aws-sdk-net/issues/2622#issuecomment-1581208688 for a longer explanation).

@dscpinheiro
That has fixed our issue. Thanks for the help!


feat(locales): support German language

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


🐧💻 Error While Loading Shared Libraries (´；ω；｀)ｳｯ…

Hello! First issue on GitHub! Hopefully I'm not butchering it... 🙇💦
Anyways, I was trying to compile Hello.emojic from the Official Guide before I ran into this error:
kawanerio@kawanerio-Lenovo-G70-35:~/Emojicode-1.0-beta.2-Linux-x86_64$ ./emojicodec 👋.🍇
./emojicodec: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory

🤔🤔🤔🤔🤔
...Maybe it was the 👋EmojiFilename.🍇 on my Linux🐧Machine that's causing the issue💡, I thought. So, I've tried changing the filename.📄:
kawanerio@kawanerio-Lenovo-G70-35:~/Emojicode-1.0-beta.2-Linux-x86_64$ ./emojicodec test.emojic
./emojicodec: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory

(´Д｀)ﾊｧ…
...🔎After a little bit of Googling🔍, I tried making a symbolic libtinfo.so.5 link in /usr/lib/ from libtinfo.so via ln:
kawanerio@kawanerio-Lenovo-G70-35:~/Emojicode-1.0-beta.2-Linux-x86_64$ sudo ln -s /usr/lib/libtinfo.so /usr/lib/libtinfo.so.5
[sudo] kawanerio のパスワード:
すみません、もう一度試してください。
[sudo] kawanerio のパスワード:
kawanerio@kawanerio-Lenovo-G70-35:~/Emojicode-1.0-beta.2-Linux-x86_64$ ls
🍇➕➕  👋.🍇  emojicodec  include  install.sh  packages
kawanerio@kawanerio-Lenovo-G70-35:~/Emojicode-1.0-beta.2-Linux-x86_64$ cd ..
kawanerio@kawanerio-Lenovo-G70-35:~$ ls
Emojicode-1.0-beta.2-Linux-x86_64  テンプレート  ドキュメント  ピクチャ      公開
ダウンロード                       デスクトップ  ビデオ        ミュージック  展開
kawanerio@kawanerio-Lenovo-G70-35:~$ cd E*
kawanerio@kawanerio-Lenovo-G70-35:~/Emojicode-1.0-beta.2-Linux-x86_64$ ./emojicodec 👋.🍇
./emojicodec: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory

...Still can't compile it😅💦. So, I've tried 💻installing⬇ the previous version, beta 1.0, from scratch💡:
kawanerio@kawanerio-Lenovo-G70-35:~/ダウンロード$ cd Emojicode-1.0-beta.2-Linux-x86_64
kawanerio@kawanerio-Lenovo-G70-35:~/ダウンロード/Emojicode-1.0-beta.2-Linux-x86_64$ ./install.sh
👨💻  Hi, I’m the Emojicode Installer!

I’ll copy the Emojicode Compiler to /usr/local/bin.
Then I’ll copy the default packages to /usr/local/EmojicodePackages.
Finally, I’ll copy the Emojicode API headers to /usr/local/include/emojicode.
If you prefer different locations you can rerun me and provide me with other locations like so:
	 ./install.sh [binary location] [packages location] [include location]

If you want to proceed type y. ➡  y
/usr/local/bin is not writeable from this user.
I can try to rerun myself with sudo.
If you wish me to do so type y. ➡  y
[sudo] kawanerio のパスワード:
I’ve super user privileges now and will try to perform the installation.
If you want to proceed type y. ➡  y
Copying builds
Copying packages
✅  Emojicode was successfully installed.
kawanerio@kawanerio-Lenovo-G70-35:~/ダウンロード/Emojicode-1.0-beta.2-Linux-x86_64$ echo '🏁 🍇
>   😀 🔤Hello World!🔤❗
> 🍉' > hello.emojic
kawanerio@kawanerio-Lenovo-G70-35:~/ダウンロード/Emojicode-1.0-beta.2-Linux-x86_64$ ./emojicodec hello.emojic  # Compile it
./emojicodec: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
kawanerio@kawanerio-Lenovo-G70-35:~/ダウンロード/Emojicode-1.0-beta.2-Linux-x86_64$ ./hello  # Run it!
bash: ./hello: そのようなファイルやディレクトリはありません

...But with no luck 😭😭😭
Emojicode works on my 💻Chromebook (Virtual Debian) but I can't get it to work on my Lenovo G70 with Linux Mint 20 inside (´；ω；｀)
🥺Can someone show me the way❓

Specification:
kawanerio@kawanerio-Lenovo-G70-35:/home$ cat /etc/linuxmint/info
RELEASE=20
CODENAME=ulyana
EDITION="Xfce"
DESCRIPTION="Linux Mint 20 Ulyana"
DESKTOP=Gnome
TOOLKIT=GTK
NEW_FEATURES_URL=https://www.linuxmint.com/rel_ulyana_xfce_whatsnew.php
RELEASE_NOTES_URL=https://www.linuxmint.com/rel_ulyana_xfce.php
USER_GUIDE_URL=https://www.linuxmint.com/documentation.php
GRUB_TITLE=Linux Mint 20 Xfce

Try installing ncurses:
sudo apt-get install libncurses-dev

If that doesn't help, try compiling Emojicode from source.

I see... apparently, I am missing a lot of important stuff to make this work. I am actually in the midst of Linux Transition, so I'll get back to making emojicode work on my machine as soon as my partition is cleaned up and so (may be several weeks ahead, but I really want to master this language).
Thank you so much for your super quick reply! I am honored to be in touch with the creator himself!

I solved this by installing libncurses5
sudo apt install libncurses5
Credit: https://stackoverflow.com/a/51333801

Just throwing it out there that this occurs on Manjaro too. libtinfo.so is provided by ncurses, which I have installed, however it currently has libtinfo.so.6 not 5. And Manjaro does not have older versions in its repositories (so I can't install libncurses5 as suggested by @OSDVF ).
I'm assuming this won't be an issue if I compile emojicodec from source, since that was already mentioned. But this will probably lead a lot of people using rolling release distros not being able to use the existing binary...

Same problem here with Fedora 37 which have only libtinfo.so.6

I solved this by installing libncurses5 sudo apt install libncurses5 Credit: https://stackoverflow.com/a/51333801

Greetings from Kubuntu! I ran into this exact same error that I apparently ran into 3 years ago, but this comment solved it for me! Thanks a thousand and happy coding! 😀
Screenshot of me running to this exact issue 3 years later, but fixing it with a single command
![image](https://github.com/emojicode/emojicode/assets/61252570/06bbd913-29bb-4f86-8f91-e1445ed0d616)


sumneko-lua-language-server: 3.6.3 -> 3.6.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/sumneko/lua-language-server/releases.
meta.description for sumneko-lua-language-server is: "Lua Language Server coded by Lua"
meta.homepage for sumneko-lua-language-server is: "https://github.com/sumneko/lua-language-server"
meta.changelog for sumneko-lua-language-server is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.6.4 with grep in /nix/store/kj7m4m0jfal9iq6z8g4fi539h5g0dhrc-sumneko-lua-language-server-3.6.4
found 3.6.4 in filename of file in /nix/store/kj7m4m0jfal9iq6z8g4fi539h5g0dhrc-sumneko-lua-language-server-3.6.4

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
sumneko-lua-language-server
vscode-extensions.sumneko.lua

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kj7m4m0jfal9iq6z8g4fi539h5g0dhrc-sumneko-lua-language-server-3.6.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sumneko-lua-language-server https://github.com/r-ryantm/nixpkgs/archive/469b1ecaae57e670ec0c409ebdd0e177b04488c0.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kj7m4m0jfal9iq6z8g4fi539h5g0dhrc-sumneko-lua-language-server-3.6.4
ls -la /nix/store/kj7m4m0jfal9iq6z8g4fi539h5g0dhrc-sumneko-lua-language-server-3.6.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

sumneko-lua-language-server
vscode-extensions.sumneko.lua

Maintainer pings
cc @sei40kr for testing.

@ofborg build sumneko-lua-language-server

Tests seems to be flaky.


Merge screens/ helpers with root helpers in Decentraland app?

@marcelomorgado I think we can close this, right?

Yes :+1:

Closing this.


fix: Panics caused by BoundingBox API returning nil

The boundingBox playwright API may return nil for the bounding box without setting an error.
The Go implementation doesn't support this case, causing null dereference and panics when trying to remap the nil to the matching struct.
We handle this by checking if the value is nil before remapping values.
This PR fixes this bug by checking for nil value before remapping.
We can also change the implementation of the remapping but it will require passing pointer to a pointer (**) in order to set nil values for variables.
Reference - https://github.com/microsoft/playwright/blob/59a50cf59603850c645830a17ccb05178eb96f50/packages/playwright-core/src/client/elementHandle.ts#L185
Panic Trace
	/usr/local/go/src/runtime/panic.go:785 +0x124
reflect.flag.mustBe(...)
	/usr/local/go/src/reflect/value.go:218
reflect.Value.MapKeys({0x0?, 0x0?, 0x27f7f58?})
	/usr/local/go/src/reflect/value.go:1828 +0x1f4
github.com/playwright-community/playwright-go.remapValue({0x0?, 0x0?, 0x4003bd3c18?}, {0x209e2c0?, 0x4004203240?, 0x0?})
	/go/pkg/mod/github.com/playwright-community/playwright-go@v0.4700.0/helpers.go:161 +0x5c8
github.com/playwright-community/playwright-go.remapMapToStruct({0x0?, 0x0?}, {0x1b21b60?, 0x4004203240?})
	/go/pkg/mod/github.com/playwright-community/playwright-go@v0.4700.0/helpers.go:174 +0x100
github.com/playwright-community/playwright-go.(*elementHandleImpl).BoundingBox(0x1b61a60?)
	/go/pkg/mod/github.com/playwright-community/playwright-go@v0.4700.0/element_handle.go:193 +0x84
github.com/playwright-community/playwright-go.(*locatorImpl).BoundingBox.func1({0x28f0108?, 0x4002b940a0?})
	/go/pkg/mod/github.com/playwright-community/playwright-go@v0.4700.0/locator.go:143 +0x2c
github.com/playwright-community/playwright-go.(*locatorImpl).withElement(0x4003bd3d18?, 0x24ba0d0, {0x4006773d40?, 0x1c3c3c0?, 0x1?})
	/go/pkg/mod/github.com/playwright-community/playwright-go@v0.4700.0/locator.go:846 +0x5c
github.com/playwright-community/playwright-go.(*locatorImpl).BoundingBox(0x40039ab230, {0x40066ccfb0?, 0x1?, 0x0?})
	/go/pkg/mod/github.com/playwright-community/playwright-go@v0.4700.0/locator.go:142 +0x8c
...
reflect: call of reflect.Value.MapKeys on zero Value

Sure, added a test (display: hidden) and added your refence


Text size varies greatly

Describe the Bug
Bookstack has a 39.55 pixel difference between text displayed, for example, here: https://demo.bookstackapp.com/shelves/demo-content .
The largest text is too large and the smallest text is too small. It seriously hampers legibility, and is very aesthetically unpleasing:

For more detail on proper typography for the web, see:https://practicaltypography.com/websites.html
Steps to Reproduce

Go to https://demo.bookstackapp.com/shelves/demo-content
Read the text.

Expected Behaviour
Text should be sized between 15-25 pixels. Headers should be slightly larger than the body text. For example, if we decide that the body text should be 15 pixels, a header could be 16 pixels. The smallest and largest sizes of text on a page should not be drastically different.
Screenshots or Additional Context
No response
Browser Details
No response
Exact BookStack Version
whatever the demo is running

All of this is easy to adjust with custom CSS in the settings. Most BookStack admins are going to change the typography to suit their needs anyway.
While I also would tweak some things about BookStack’s typographic defaults, I don’t agree with a fellow typography nerd swooping in here and labeling this as a bug. I also know Matthew Butterick, and I don’t think he would be enthused about his work being used in service of drive-by nitpicking (see, e.g., 1, 2). If you want to evangelize about good typography, do so through your own good typographic works 😉

Thanks for the input @nat-418,
In my view, consistency of font sizes for sure could be improved.
In regards to range of font sizes, I don't doubt a tighter range could visually improve things, but I'm not sure I'd want to tighten things too much in the platform defaults.
The example you're showing has a particularly large range due to the shelf heading.
This heading is aligned with the sizes of that for books, chapters and pages so the names of these core items appear consistent as your travel down.
Since the is a platform of user-content, and users have access to a range of headers, by default the main heading is quite large since we accommodate several options levels beneath this.
I like to ensure these are distinct without much additional opinionated design/style thrown in, and therefore sizing is used.
If you don't like the sizes/styles used, you can always customize/override the styles.

For example, if we decide that the body text should be 15 pixels, a header could be 16 pixels.

A 1px difference is quite hard to see in my opinion. Of course you could use other methods of distinguishment, but as said above I like to keep the defaults fairly vanilla & free of much additional styling choices.
I'm happy to take on this input, for choices I make going forward, but I don't expect to change things to work to the range you're requesting, and I may close this off as opionated change requests such as this can be hard to manage.

All of this is easy to adjust with custom CSS in the settings. Most BookStack admins are going to change the typography to suit their needs anyway.
While I also would tweak some things about BookStack’s typographic defaults, I don’t agree with a fellow typography nerd swooping in here and labeling this as a bug. I also know Matthew Butterick, and I don’t think he would be enthused about his work being used in service of drive-by nitpicking (see, e.g., 1, 2). If you want to evangelize about good typography, do so through your own good typographic works 😉

I don't care who you are or who you know. I tried out using Bookstack and found it hard to read. I don't think that is "drive-by nitpicking". If the maintainers of this project do not want user feedback in the form of issues, then they should restrict or close the ability of users to submit issues.

Thanks for the input @nat-418, In my view, consistency of font sizes for sure could be improved. In regards to range of font sizes, I don't doubt a tighter range could visually improve things, but I'm not sure I'd want to tighten things too much in the platform defaults.
The example you're showing has a particularly large range due to the shelf heading. This heading is aligned with the sizes of that for books, chapters and pages so the names of these core items appear consistent as your travel down. Since the is a platform of user-content, and users have access to a range of headers, by default the main heading is quite large since we accommodate several options levels beneath this. I like to ensure these are distinct without much additional opinionated design/style thrown in, and therefore sizing is used.
If you don't like the sizes/styles used, you can always customize/override the styles.

For example, if we decide that the body text should be 15 pixels, a header could be 16 pixels.

A 1px difference is quite hard to see in my opinion. Of course you could use other methods of distinguishment, but as said above I like to keep the defaults fairly vanilla & free of much additional styling choices.
I'm happy to take on this input, for choices I make going forward, but I don't expect to change things to work to the range you're requesting, and I may close this off as opionated change requests such as this can be hard to manage.

Thanks for taking the time to respond. I checked out Bookstack because I saw your posts when looking for a good self-hosted wiki. I noticed you called it opinionated software. If you don't' want to do such a small range that I suggested,  I respect your decision as the project maintainer. I think you could figure out a way to reduce the range between huge and tiny text, but if you don't want to do that, that's your free choice.

Thanks for your understanding. I'm going to close this off since I don't see enforcing a specific rule on the project, or a specific action to target right now, but I'll keep this feedback in mind when working on default design elements going forward.


[tw] Localize Continuous Deployment (CD) for Traditional Chinese

Localize Continuous Deployment (CD) for Traditional Chinese
https://glossary.cncf.io/continuous-deployment/

感謝幫忙


makeShaderWithChildren is executed upon every render

e.g. in the Hue example: Every time another color is selected via touch, makeShaderWithChildren is executed, even though the Shader does not depend on the color.

This means that we could rewrite the example to not use uniforms. But that doesn't have any implication with the current Shader component implementation right?
Closing for now. If there are indeed a way to rethink the Shader component implementation please reopen.

indeed in the Hue example the Shader declaration should never change, will double check what is happening here


Declare minimum sphinx version required for docs as 4.

As title. Patches up the build scripts to enforce and docs to note
this.

xref: https://github.com/numba/numba/pull/7122#issuecomment-863380498 confirming the minimum version.

It looks like there are some issues building the documentation on Azure Pipelines with this PR. This is strange b/c #7122 was seemingly fine when building on RTD.

Possibly this: https://stackoverflow.com/questions/63080103/how-to-reference-built-in-c-types-with-rst

It looks like there are some issues building the documentation on Azure Pipelines with this PR. This is strange b/c #7122 was seemingly fine when building on RTD.

I think it's because of this: https://github.com/numba/numba/pull/7125/files#diff-319afae18279ecbf9d01cb17a6091e1103ddccadda228ace0a011a5590aa3667L88

I tried the following patch:
 💣 zsh» gin stash show -p
diff --git a/docs/source/reference/pysupported.rst b/docs/source/reference/pysupported.rst
index d55c44c968..a50f285393 100644
--- a/docs/source/reference/pysupported.rst
+++ b/docs/source/reference/pysupported.rst
@@ -1229,29 +1229,29 @@ Third-party modules
 Similarly to ctypes, Numba is able to call into `cffi`_-declared external
 functions, using the following C types and any derived pointer types:

-* :c:type:`char`
-* :c:type:`short`
-* :c:type:`int`
-* :c:type:`long`
-* :c:type:`long long`
-* :c:type:`unsigned char`
-* :c:type:`unsigned short`
-* :c:type:`unsigned int`
-* :c:type:`unsigned long`
-* :c:type:`unsigned long long`
-* :c:type:`int8_t`
-* :c:type:`uint8_t`
-* :c:type:`int16_t`
-* :c:type:`uint16_t`
-* :c:type:`int32_t`
-* :c:type:`uint32_t`
-* :c:type:`int64_t`
-* :c:type:`uint64_t`
-* :c:type:`float`
-* :c:type:`double`
-* :c:type:`ssize_t`
-* :c:type:`size_t`
-* :c:type:`void`
+* :c:expr:`char`
+* :c:expr:`short`
+* :c:expr:`int`
+* :c:expr:`long`
+* :c:expr:`long long`
+* :c:expr:`unsigned char`
+* :c:expr:`unsigned short`
+* :c:expr:`unsigned int`
+* :c:expr:`unsigned long`
+* :c:expr:`unsigned long long`
+* :c:expr:`int8_t`
+* :c:expr:`uint8_t`
+* :c:expr:`int16_t`
+* :c:expr:`uint16_t`
+* :c:expr:`int32_t`
+* :c:expr:`uint32_t`
+* :c:expr:`int64_t`
+* :c:expr:`uint64_t`
+* :c:expr:`float`
+* :c:expr:`double`
+* :c:expr:`ssize_t`
+* :c:expr:`size_t`
+* :c:expr:`void`

 The ``from_buffer()`` method of ``cffi.FFI`` and ``CompiledFFI`` objects is
 supported for passing Numpy arrays and other buffer-like objects.  Only

But the resulting formatting isn't what we want:
Before

After


CARDS-2127: Reusable Logo component; CARDS-2125: Affiliation logo on the login page; CARDS-2126: Affiliation logo on error pages

Includes:

CARDS-2127 - Reusable Logo component that displays the app logo and includes the affiliation logo if the latter is defined
CARDS-2125 - The error pages should display the affiliation logo when it is defined
CARDS-2126 - The login page should display the affiliation logo when it is defined
CARDS-1927 - Center title of the patient's survey

Reviewing:

commit by commit is recommended

Testing:

test prems, proms, lfs, heracles as admin

login page - should have affiliation logo for prems; should appear unchanged for others
inline login dialog - after signing in as admin, sign out in a different tab, then try to click a link in the side bar in the current tab - the inline login dialog should pop up, check that it looks right for all projects
error pages - while signed in as admin, navigate to a non-existing page, e.g. http://localhost:8080/c - check that in prems it has app logo and affiliation logo, while in other projects it is unchanged
Note: the affiliation logo is currently not displayed in the main UI in the sidebar; that is intentional.

test prems, proms as patient

in prems, the affiliation logo should now be displayed when navigating to http://localhost:8080/Survey.html unauthenticated
in prems, test the unsubscribe page
in proms, check that the header of the survey ui after sign still looks good
in proms, test the new look of header of the DATA-PRO survey ui after sign in with and without a token (CARDS-1927)

test proms with an affiliation logo

build the test branch CARDS-2127_test, where the DATA logo is configured as affiliation logo
start in proms
test landing page, admin login, error pages, patient login, unsubscribe page
test the new look of header of the DATA-PRO survey ui after sign in with and without a token (CARDS-1927)

Is the logo on the "To fill out surveys, please follow the personalized link that was emailed to you." page intentionally bigger? Only happens in proms if you disable tokenless auth. Everything else looks good.

The size of the logo appears to have always been bigger on error pages, and it was preserved in this refactoring. We can get back to it in a separate iteration.
https://github.com/data-team-uhn/cards/pull/1389/files#diff-a9f0c2df0b69b88e3de910f0e8a0479d21405f4d5448d0c0586f9ffed7fb4d1dL39-R58


[map] highlighting a small location looks odd

That black thing above is supposed to be the border.  Probably worth seeing if we can scale thickness depending on the zoom level or something... Low pri.

Also a problem when highlighting of small countries in Earth view:

For small countries in Earth view - that was the best option I could come up with that would make it visible (granted, the color is lost, but the data shows up on the tooltip).
The thick border on zoom looks really janky though


tracing-tracy suppresses tracing to stdout

Bevy version
0.9.1
What you did
Enabling tracing-tracy via the trace_tracy feature.
What went wrong
Once enabled, info! and debug! type messages that would have been routed to stdout no longer appear.
It would be nice to be able to have tracing-tracy enabled but also see info! and debug! messages.

Will be fixed by #6955.


Dark theme

What would you like the app to enable you to do?
I would like to use a dark interface theme so that my eyes are not so tired in a dark room
Describe alternatives you've considered
Additional context
https://developer.apple.com/design/human-interface-guidelines/foundations/dark-mode/

I would clarify that I also need the so-called “pure black color theme” / "AMOLED theme" with a background color of #000.

@sbruens, am I correct in understanding that this thread is discussing dark client theme for all platforms the app is currently compiled for?

Looks like OP updated the issue. I've also added tags for each individual platform to make that clear.

With Google Android 10, there is an easy way to implement a dark theme using the Force Dark method.
There's a feature with the same name in Google Android 14 that lets you display some apps in a dark theme even if the app developer hasn't implemented it. But it doesn't always work. In my case, it had no effect on the appearance of Outline.


how to change the editor's locale?

hi
i want to know how to change editor's locale?
eg: change en-us to zh-cn
thanks

Please see https://github.com/Microsoft/monaco-editor-samples/tree/master/sample-localized

get~
thanks

Link is broken, any suggestions?

Also how could we achieve localization with the esm import ?

hi
i want to know how to change editor's locale?
eg: change en-us to zh-cn
thanks

你好，我想问一下你知道 monaco-editor 在esm版本下如何汉化吗？

Link is broken, any suggestions?

It's now under https://github.com/microsoft/monaco-editor-samples/blob/master/browser-amd-localized/index.html


biome: 1.4.1 -> 1.5.3

Description of changes
Updating Biome from 1.4.1 to 1.5.3 (current).

Between 1.4.0 and current there has been a number of bug fixes and increased compatibility with Prettier. At v1.5.0 Biome scores 97% compatibility with Prettier.
I'm very new to NixOS so if there's anything I messed up I'm happy to fix it or create another pr. Thank you for reviewing.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

The source has a hash mismatch:
unpacking source archive /build/v1.5.3.tar.gz
error: hash mismatch in fixed-output derivation '/nix/store/54pn6a636mgyvgdd62n6dyywlafi6cfr-source.drv':
         specified: sha256-0xLpZIqBaM4hTWsJzkVZMuDySFSXCLpQm/maCaXDJQo=
            got:    sha256-70LHsmS01ssD4yCbHfBouV+NyhMIlBbX0jcHFu8aLMw=

And also need to update the cargo hash to sha256-wf6X6aY1O9EABQ6sDNAb3XsVrC0lgUtpgoieiPZ7r3k=.

It seems that the build is failing at the check phase.
failures:

---- commands::explain::explain_logs stdout ----
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Snapshot Summary ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Snapshot file: crates/biome_cli/tests/snapshots/main_commands_explain/explain_logs.snap
Snapshot: explain_logs
Source: crates/biome_cli/tests/snap_test.rs:429
────────────────────────────────────────────────────────────────────────────────
Expression: content
────────────────────────────────────────────────────────────────────────────────
-old snapshot
+new results
────────────┬───────────────────────────────────────────────────────────────────
    4     4 │
    5     5 │ ```
    6     6 │
    7     7 │ ```block
    8       │-<BIOME_DIR>/biome-logs
          8 │+<TEMP_DIR>/biome-logs
    9     9 │ ```
   10    10 │
────────────┴───────────────────────────────────────────────────────────────────
To update snapshots run `cargo insta review`
Stopped on the first failure. Run `cargo insta test` to run all snapshots.
thread 'commands::explain::explain_logs' panicked at /build/biome-1.5.3-vendor.tar.gz/insta/src/runtime.rs:569:9:
snapshot assertion for 'explain_logs' failed in line 429
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    commands::explain::explain_logs

test result: FAILED. 304 passed; 1 failed; 4 ignored; 0 measured; 0 filtered out; finished in 0.30s

However when I test directly on the source, it succeeds.

The source has a hash mismatch:
unpacking source archive /build/v1.5.3.tar.gz
error: hash mismatch in fixed-output derivation '/nix/store/54pn6a636mgyvgdd62n6dyywlafi6cfr-source.drv':
         specified: sha256-0xLpZIqBaM4hTWsJzkVZMuDySFSXCLpQm/maCaXDJQo=
            got:    sha256-70LHsmS01ssD4yCbHfBouV+NyhMIlBbX0jcHFu8aLMw=

And also need to update the cargo hash to sha256-wf6X6aY1O9EABQ6sDNAb3XsVrC0lgUtpgoieiPZ7r3k=.

thank you. Updated!

@figsoda anything else I need to do?

The package should be successfully built.
And the test fails and needs to be fixed or skipped.

@honnip how can I make it build in CI?
All CI jobs are either passed or not ran

Check the Details button next to the job biome, biome.passthru.tests on _platform_


CI: Rebuilding a job doesn't cancel its childen jobs

When using the web UI from datakit-ci, if I rebuild a job, the jobs that are depending on it will still be in the resource pool unless they are cancelled one by one there.
Is there anything in the API that can help or can datakit-ci do that ?

Currently, it always lets a job run to completion once started (but it won't start any new jobs if noone wants the result).
You could do some kind of mark-and-sweep in Engine.recalc_loop to cancel jobs as soon as they are not needed by some active PR or branch.
However, people sometimes expect to be able to see the results of builds, even if a newer build came along later. e.g. if I push a new commit to a PR, I might still want to know the result for the previous commit.

If I'm not mistaken those logs do not appear anywhere. Can't we make this the default ?
I'm really unsure of how to patch that since I basically know nothing about the datakit codebase. Also I would really like to avoid depending on a locally patched dependency.
If it's definitely not possible, could you give me some pointers ?

One thing that could also be done in the meantime as a temporary fix (but still maybe useful anyway) would be to have some sort of "cancel-all button" on the main page. Is that conceivable ?

If I'm not mistaken those logs do not appear anywhere.

Even when no PR, tag or branch head still wants a result, it can still be accessed from many places, including:

The GitHub PR page (click on the test result for a non-head commit).
Visiting a previous state of a target (the "Previous state" controls at the top of each page).
Using the the various "History" links in the UI.
Looking directly in the results database.

TravisCI has an option to do that, that I find quite useful (as it free up resources more quickly). In some cases you don't care about building every commit, you are just by the latest one on each tags/branches.


SocketCAN FD support : "RTNETLINK answers: Operation not supported"

I'm working through testing out the FD settings. Can't seem to get the FD mode to return anything other than, "RTNETLINK answers: Operation not supported"

Same issue. Have you found a solution? I can set up "normal CAN" successfully, but something went wrong when I set up CAN FD. I tried this in Ubuntu20.
~ ➤ sudo ip link set can0 down
~ ➤ sudo ip link set can0 up type can bitrate 500000
~ ➤ candump can0
  can0  123   [2]  12 34
^C%
~ ➤ sudo ip link set can0 down
~ ➤ sudo ip link set can0 up type can bitrate 500000 dbitrate 8000000 restart-ms 1000 berr-reporting on fd on

RTnetlink answers operation not supported

no solution found here. hopefully Eric will bring insight as to why.

Hi @mitchdetailed, Eric told me that the driver cantact-pro used not support CAN FD yet, he made a patched driver.
I have installed this driver in my Ubuntu20, but the problem still exists.  Anyway, you can try it.
gs_usb_fd ➤ lsmod | grep can
can_dev                32768  2 gs_usb_fd,gs_usb
gs_usb_fd ➤ sudo ip link set can0 up type can bitrate 500000 dbitrate 8000000 restart-ms 1000 berr-reporting on fd on
RTNETLINK answers: Operation not supported

sudo apt install kernel-headers-$(uname -r)
returns :
E: Unable to locate package kernel-headers-5.4.0-72-generic
E: Couldn't find any package by glob 'kernel-headers-5.4.0-72-generic'
googling yeilds no legitimate results. interested in input
On Mon, Mar 29, 2021 at 2:59 AM azreborn @.***> wrote:

Hi @mitchdetailed https://github.com/mitchdetailed, Eric told me that
the driver cantact-pro used not support CAN FD yet, he made a patched
driver https://github.com/linklayer/gs_usb_fd.
I have installed this driver in my Ubuntu20, but the problem still exists.
Anyway, you can try it.
gs_usb_fd ➤ lsmod | grep can
can_dev                32768  2 gs_usb_fd,gs_usb
gs_usb_fd ➤ sudo ip link set can0 up type can bitrate 500000 dbitrate 8000000 restart-ms 1000 berr-reporting on fd on
RTNETLINK answers: Operation not supported
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/linklayer/cantact-pro-fw/issues/1#issuecomment-809161842,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI62NLUELZ467L7CITZAW43TGAXNDANCNFSM4YYU35OA
.

--
Mitch Minton<PHONE_NUMBER>
Bridgestone - USW1055

i was able to install the kernel object on my machine (linux mint ) by doing the following:
~$ sudo apt-get install linux-source
~$ git clone https://github.com/linklayer/gs_usb_fd.git
~$ cd gs_usb_fd/
~$ sudo make
~$ sudo insmod gs_usb_fd.ko
but when i attempt to run a fd bitrate, i still receive a "RTNETLINK answers: Operation not supported" value returned

Hey @mitchdetailed
The CANtact Pro doesn't support changing of bit error reporting (berr-reporting on), this is why your command fails. Try:
sudo ip link set can0 up type can bitrate 500000 dbitrate 8000000 restart-ms 1000 fd on


Make radio sensor easier to use in graphs and automations

Is your feature request related to a problem? Please describe.
The current radio sensor is combing two values into one as a string that makes graphing and creating automations more difficult.
Describe the solution you'd like
Break the signal level and channel number into different entities.
Signal level should be a number with a unit of measurement that allows it to be easily graphed in Home Assistant using the built in support for numeric entities.
Channel number is probably more of an attribute than a separate entity, It should rarely change.
For either entity consider using the  "entity_category": "diagnostic" feasture so that it doesn't get added to the dashboard.
Describe alternatives you've considered
(I haven't thought of any)
Additional context
discussion in issue https://github.com/gazoodle/gecko-home-assistant/issues/58

Fixed in v0.1.9


Determine used and unused iam entities for GCP

@ganeshjagdale9545 can you please show me the code where we determine the ASSUME_ROLE relationship between IAM entities?


get_asset terminology

is there a reason we use get_asset instead of seek_asset?
the 'get' terminology is really confusing because it seems like it should be a synonym of pull, not of seek...

there's no reason at all..

this issue is similar to #84. We need to rename (or add if missing) RefGenConf methods so that they perform identical functions as the CLI commands, but output python objects


data-rule's not working

No idea whats going on but none of the data-rules's are working i've attempted
data-rule-required="true"
data-rule-email="true"
and
data-rule-equalTo="#providerEmail"
am i missing something?

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.
To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!


added styling to the about page

Good work Steve, your parts are coming along nicely. Code is DRY and easy to follow along.


Issue #3353 - Print error messages to STDERR

This solution uses a less-than-ideal method to add Thor-formatted printing to STDERR. Because Thor doesn't offer this out-of-the-box, I've used Thor's internals to format a message and pass it to Thor's stderr.
Since this uses protected methods, changes under the hood in Thor may break this. If this happens, tests will fail.
I also added basic tests to ensure other print methods from Bundler::UI::Shell continue printing to STDOUT.
#3353

I'm pretty uneasy about breaking the encapsulation of Thor like this. Can we make a change upstream to Thor to enable us to do this more cleanly?

I am okay with this approach because Thor is effectively part of our local codebase, but I would also prefer that Thor offered Shell#say_error or something like that. @jnraine can you fix the tests for this change and/or submit a PR to Thor that adds a method to print to stderr?

Thanks @jnraine, this was cherry-picked into 2-0-dev as https://github.com/bundler/bundler/commit/300fcbe2a06b9b44d1935e01a1548be22949ffaa.

Awesome @segiddins.


ExcitedStatesEigensolver does not return excited states

Environment

Qiskit Nature version: 0.6.2
Python version:  3.10.6
Operating system: Linux (WSL)

What is happening?
Hi guys, I was running this tutorial on excited state solvers on my local machine and found that the ExcitedStatesEigensolver was not actually returning any excited states. When I ran the tutorial on the IBM cloud, the same error was produced. In fact that tutorial page itself does not have any excited states produced by the numpy eigensolver.
Upon checking the Japanese (JA) version of the same tutorial, it seems that the tutorial used to be in fact working.
How can we reproduce the issue?
You can check the tutorial itself, or try running the code from the tutorial and the problem should reproduce itself.
What should happen?
The ExcitedStatesEigensolver should produce the energies for the excited states of H2.
Any suggestions?
No response

That is very odd :eyes:
I can indeed reproduce this locally. Two things stand out to me:

the excited states are even missing when I remove the filter_criterion from the NumPyEigensolver
the QEOM results report particle numbers of 0

Not sure what is going on yet, but I will do some digging. Thanks for raising this! :+1:

Okay, the NumPyEigensolver issue was a simple mistake after the deprecation of the NumPyEigensolverFactory.
The number of eigenvalues computed by that solver (which exists in Terra) defaults to k=1. Thus, all we need to do to fix this is to set k=4 and our issue is resolved :+1:
(looking into the QEOM auxiliary operators next)

And with QEOM its also a matter of not having updated the tutorial. In this PR (#971) the codebase of QEOM was refactored and we introduced the EvaluationRule which allows the user to configure the rules for which operators to be evaluated.
I will update the tutorial accordingly.

The fixed tutorial is now live here: https://qiskit.org/ecosystem/nature/tutorials/04_excited_states_solvers.html


Phaser renderer mobile controls

On computer its working fine, but on mobile is not working - old problem with phaser on mobile phone, not part of this PR anyway.

@Grenagar Let's wait a bit in case cors issues can be fixed soon.

https://github.com/moddio/taro/pull/346/files#diff-bbc42b4b2e957c22446e44954bb292b71d6f6111f72a79d1824ad9978ce894c9R130-R140
you can uncomment this to test other input controls


Ensure number of processes is not 0 in multithreading

Fixes #74 (hopefully), thanks to @pllim for the suggestion there.

Maybe it is time to drop Python 3.9. Python 3.13 beta is already out.

I think until https://github.com/spacetelescope/stregion/issues/19 (and any other things that might crop up after this one is fixed) is resolved, I don't think you can install this package on Windows. Did this package ever work on Windows before?

All the Linux jobs passed. 🤞

Maybe it is time to drop Python 3.9. Python 3.13 beta is already out.

I've been considering it.

I've been considering it.

Unless you somehow need to use this package in a very old environment for some ultra stable pipeline that is slow to upgrade or frozen, there is no reason to keep supporting it.

I bumped the python min version, after realizing that if we manage to update drizzlepac to use regions instead of stregion, regions is min 3.10 anyway. I think that's the path to getting the Windows tests working, so might as well do it now.

Looks like you still not gotten rid of stregion yet in your stack according to Windows failure.
Failed to build stregion

Looks like you still not gotten rid of stregion yet in your stack according to Windows failure.
Failed to build stregion

Right, that's what I was saying - drizzlepac uses stregion and so we'd need changes there.

AFAIK no one working on replacing stregion with regions in drizzlepac.  If that's the case, they should at least be updating stregion.

AFAIK no one is working on replacing stregion with regions in drizzlepac. If that's the case, they should at least be updating stregion.

That was also my understanding, which is why I was planning to hack on it later this week if I have time 😬

If you cannot control upstream, your option would be down to making drizzlepac option and not install it on Windows. Or dropping Windows support altogether. (A lot of HST tools have a history of not supporting Windows due to resource limitations.)

I'll merge this since the scope was to fix the Ubuntu tests. Windows is a separate issue.


Fix light and multimesh crashes

Fixes: https://github.com/godotengine/godot/issues/29778
Fixes: https://github.com/godotengine/godot/issues/33007
#29778 results from passing in values outside of the possible values for the MultiMeshColorFormat and MultiMeshCustomDataFormat enums. Now the engine will treat values outside that range as if *NONE had been selected.
#33007 Results from not checking for the existence of a pointer before accessing it.

Thanks!


Fixed all typos and improved README.md and added some documentation

Resolved issue #9

Added Code_of_Conduct.md
Added MIT LICENSE
Minor Changes in Contributing.md
Beautified README.md
Typos fixed
Added Contributors section in README.md

Great job


Updates NanoVG to the latest commit.

This commit updates NanoVG's bgfx backend to match the original NanoVG's latest commit, which has significant changes about composite operation implementation as mentioned in pull request https://github.com/memononen/nanovg/pull/312.

See bx::uint32_cnttz here: https://github.com/bkaradzic/bgfx/blob/64922762df3e817aa720dd27b9e0eba76377bccd/examples/common/nanovg/nanovg_bgfx.cpp#L703

Got it. Just reverted the glnvg_convertBlendFuncFactor() function.

I'm trying to reconcile changes with your commit and latest nanovg, but it seems there is discrepancy. What version you used? Ideally all changes are applied here https://github.com/bkaradzic/nanovg for integration with origin.

@bkaradzic This commit adapts the latest version in original NanoVG (https://github.com/memononen/nanovg/commits/master).

Yes, my fork of nanovg is tracking that. See: https://github.com/bkaradzic/nanovg/commits/master
Just when I integrate files over I see more changes...

@bkaradzic Sorry, I just realized that I forgot to include the changes in some older commits. I will fix that and submit another PR.


google-cloud-task: Question on using CloudTasksClient

We are trying to use the cloud task api in a spring boot app and wanted to find out if CloudTaskClient is thread safe.  There will be a high frequency use of this service (singleton bean) using this api and wondering if the right path is to upfront create the client once (CloudTasksClient.create()) and reuse the client to add tasks.
Thanks!

@dannychane
The Cloud Tasks service is designed for asynchronous work. It does not provide strong guarantees around the timing of task delivery and is therefore unsuitable for interactive applications where a user is waiting for the result so you could say it's not thread safe.
CloudTaskClient bean can be singleton and should be reused for furthur task creation and bean itself not a threadsafe. As client creation on each request could be costly which in terms of increase response time.

Thx.

@athakor sorry for bringing this up again, but I am having a bit of trouble parsing your response above.

CloudTaskClient bean can be singleton and should be reused for furthur task creation but bean itself not a threadsafe.

if the bean is singleton and should be reused for task creation in the entire application, doesn't that imply it is thread safe?


Page flickers whenever enters a different page under non-default color mode

Describe the bug
The web page will flicker whenever enters a different page under non-default color mode. For example, if my default color theme is 'minimal' (which is bright), after switching to dark theme, I'll have an issue of page flickering whenever enters a new page.
To Reproduce

go to https://sourcethemes.com/academic/docs/
change to dark theme
click Updates on the nav bar
you will see a flicker, which might be pretty annoying in the dark

Steps to reproduce the behavior:

go to https://sourcethemes.com/academic/docs/
change to dark theme
click Updates on the nav bar
you will see a flicker, which might be pretty annoying in the dark

Expected behavior
After switching to a color theme, the screen will not flicker whenever enters a new page.
Technical details:

Academic Version: latest
Hugo Version: latest
Browser/OS: chrome

@gcushen Here's the gif, hope it explains the issue

This is due to the page loading and in particular the various plugins which the Docs site has enabled. There are many approaches for improving the page load. One is to disable any features your site might not need like math, diagrams, etc. Another approach is to take a look over files like academic.js and contribute a PR to refactor the code, such as to further prioritise the theming code.

Okay, thanks for the answer, I'll close this issue for now

This is unfortunate, disabling features doesn't seem to have a large impact... is the javascript refactor mentioned in the works, or does it entirely depend on someone stepping up?

I'm afraid the flickering is still happening when switching languages:


Handling Enterprise specific routes for GitHub Apps

Due to a need to avoid route conflicts with customers that have Organizations in GHE called /apps, once Apps ships in Enterprise, the route will be:
http(s)://[hostname]/github-apps/[app]/
instead of
https://github.com/apps/[app]
I think this means we'll need to add Enterprise specific logic for these routes:
https://github.com/octokit/node-github/blob/072a53f6d8f5e8fe642284c13af93177def6abbe/lib/routes.json#L1079
https://github.com/octokit/node-github/blob/072a53f6d8f5e8fe642284c13af93177def6abbe/lib/routes.json#L1163
https://github.com/octokit/node-github/blob/072a53f6d8f5e8fe642284c13af93177def6abbe/lib/routes.json#L1172
I wasn't sure what the optimal way would be to implement, so I wanted to open this issue first so we can discuss. I'm happy to help test once we have release candidates of GHE with Apps enabled.

perfect, thanks for the heads-up @tcbyrd 👍
I think we shouldn’t be affected by the App installation routes that you open in the browser, node-github is only using the API endpoints for which I don’t think the conflict will apply? E.g. the full route for GET /app/installations is https://<host name>/api/v3/app/installations. The route to an organization called app would be https:///api/v3/orgs/app`.
Or am I missing something?

@gr2m Nope my brain was totally not thinking straight here. You're right. API routes are not changing!


Using signin when deployed on Vercel repeats the base site url twice in call to api/auth/signin

This seems a bit odd and perhaps is a Vercel bug - I'll be following up with them as well.
My options are configured like so:
const options = {
  site: process.env.NEXT_PUBLIC_SITE ?? 'http://localhost:3000',
  providers: [
    Providers.Facebook({
      clientId: process.env.FB_CLIENT_ID,
      clientSecret: process.env.FB_CLIENT_SECRET,
      scope:
        'email instagram_basic instagram_manage_insights user_location user_link user_hometown user_gender user_friends user_birthday user_age_range',
    }),
  ],
  secret: process.env.NEXT_AUTH_SECRET,
  session: {
    jwt: true,
  },

This runs locally just fine using both yarn dev and vercel dev. When I deploy to a Vercel preview environment, and make sure to set the NEXT_PUBLIC_SITE preview environment variable to the preview site URL, when signin is called, I'm redirected to https://{my-preview-site}.vercel.app/{my-preview-site}.vercel.app/api/auth/signin. (note that the base url repeats)
This still happens even if I hardcode the Vercel url like site: 'https://{my-preview-site}.vercel.app', or (I don't think these would work anyway, just testing) site: '/' or  site: 'http://localhost:3000'.
It also happens if I remove site completely from the options in [...nextauth].ts and just include it in the AuthProvider like this:
<AuthProvider
  options={{
    site: '{my-preview-site}.vercel.app',
  }}
  session={session}
>

The component to call sign in is a simple button:
<Button
  className={classes.button}
  variant='contained'
  color='primary'
  type='submit'
  onClick={signin}
>
  Sign in
</Button>

Oddly, the error doesn't happen if I do this:
<AuthProvider
  options={{
    site: 'http://localhost:3000',
  }}
  session={session}
>

Then

Deploy to Vercel
Run the site locally so that localhost:3000 is available
Navigate to the Vercel deployment site at https://{my-preview-site}.vercel.app/
Hit the Sign In button and it redirects to http://localhost:3000/login?callbackUrl=http://localhost:3000 as expected

[ ] Found the documentation helpful
[ ] Found documentation but was incomplete
[x] Could not find relevant documentation
[ ] Found the example project helpful
[x] Did not find the example project helpful

Perhaps related to https://github.com/vercel/next.js/pull/14804

48 hours later and cooler heads have prevailed. The url I was using for the Vercel site did not include https, and therefore must have been interpreted as a route.

No worries, thanks for updating! We've seen this before but wasn't certain it was the same issue.
Version 3.0 includes changes to prevent this from being an issue.


Container fails to restart after upgrading (from 0.10.1 to 1.0.1)

This is likely more informational and nothing actionable now.  It looks like a flag changed and it made it so my container could not start the container (nor did it start upon upgrading)
Removing the container and restarting it fixes it; just seems :(
flag provided but not defined: -driver
Usage of /var/lib/docker/aufs/mnt/c26ffda627d74b4a2568932b04fa96343a3f22fc35fb8f3705bd124624fc316f/.dockerinit:
  --api-enable-cors=false                Enable CORS headers in the remote API
  -b, --bridge=""                        Attach containers to a pre-existing network bridge
                                           use 'none' to disable container networking
  --bip=""                               Use this CIDR notation address for the network bridge's IP, not compatible with -b
  -D, --debug=false                      Enable debug mode
  -d, --daemon=false                     Enable daemon mode
  --dns=[]                               Force docker to use specific DNS servers
  --dns-search=[]                        Force Docker to use specific DNS search domains
  -e, --exec-driver="native"             Force the docker runtime to use a specific exec driver
  -G, --group="docker"                   Group to assign the unix socket specified by -H when running in daemon mode
                                           use '' (the empty string) to disable setting of a group
  -g, --graph="/var/lib/docker"          Path to use as the root of the docker runtime
  -H, --host=[]                          The socket(s) to bind to in daemon mode
                                           specified using one or more tcp://host:port, unix:///path/to/socket, fd://* or fd://socketfd.
  --icc=true                             Enable inter-container communication
  --ip="<IP_ADDRESS>"                         Default IP address to use when binding container ports
  --ip-forward=true                      Enable net.ipv4.ip_forward
  --iptables=true                        Enable Docker's addition of iptables rules
  --mtu=0                                Set the containers network MTU
                                           if no value is provided: default to the default route MTU or 1500 if no default route is available
  -p, --pidfile="/var/run/docker.pid"    Path to use for daemon PID file
  -r, --restart=true                     Restart previously running containers
  -s, --storage-driver=""                Force the docker runtime to use a specific storage driver
  --selinux-enabled=false                Enable selinux support
  --storage-opt=[]                       Set storage driver options
  --tls=false                            Use TLS; implied by tls-verify flags
  --tlscacert="//.docker/ca.pem"         Trust only remotes providing a certificate signed by the CA given here
  --tlscert="//.docker/cert.pem"         Path to TLS certificate file
  --tlskey="//.docker/key.pem"           Path to TLS key file
  --tlsverify=false                      Use TLS and verify the remote (daemon: verify client, client: verify daemon)
  -v, --version=false                    Print version information and quit

considering this involves a version pre-1.0 closing

That's a shame; close a valid issue even though it's old :(
Any chance issues can be worked instead of closed @jfrazelle?

its pre 1.0
On Wed, Feb 25, 2015 at 1:00 PM, Scott M. Likens<EMAIL_ADDRESS>wrote:

That's a shame; close a valid issue even though it's old :(
Any chance issues can be worked instead of closed @jfrazelle
https://github.com/jfrazelle?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/6604#issuecomment-76055903.

@damm what would be an easy way of reproducing this?

@jfrazelle The comment here https://github.com/docker/docker/issues/6604#issuecomment-46901823 is very promising but unfortunately no one has paid attention to this issue since June 26th of 2014.
No need to have a negative attitude about pre 1.0 or post 1.0.
@tiborvass the easiest would be to run a very old version of Docker 0.10.1 and then upgrade it to a version that supports libcontainer could even be the current version.  Older versions of the package surely should still be around.

Well the main problem at hard here is upgrading a docker version fails to
restart container, and I upgrade my docker version almost everyday and all
my containers restart, after docker 1.2 and the --restart policies this has
no longer been an issue.
On Wed, Feb 25, 2015 at 6:26 PM, Scott M. Likens<EMAIL_ADDRESS>wrote:

@jfrazelle https://github.com/jfrazelle The comment here #6604 (comment)
https://github.com/docker/docker/issues/6604#issuecomment-46901823 is
very promising but unfortunately no one has paid attention to this issue
since June 26th of 2014.
No need to have a negative attitude about pre 1.0 or post 1.0.
@tiborvass https://github.com/tiborvass the easiest would be to run a
very old version of Docker 0.10.1 and then upgrade it to a version that
supports libcontainer could even be the current version. Older versions
of the package surely should still be around.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/6604#issuecomment-76111024.

And if you have a Container from 0.10 and upgrade to 1.2? with the new restart policies does it work?


Fix and pan

Added pan via an option (see the related e2e test). Next step is to find a cool interface so that the outer world can actually use this ^^.
Also fixed tooltip under Firefox.

Great, I will review this PR tomorrow ;)

Great PR, there are some details to be discussed but in general everything looks pretty good. I like how clean such a feature can be implemented in the new architecture! Well down :100:

Dammit, merge conflicts ! I'll solve this tomorrow ! Thanks for the comments !

Alright, merge conflict solved :)


feat(eval): add global pass rate threshold

This PR addresses #1441 It introduces a configurable pass rate threshold for evals. The command now exits with PROMPTFOO_FAILED_TEST_EXIT_CODE if the pass rate falls below the specified threshold. When the threshold is not set, the existing behavior (0 failures allowed) is maintained.

Add PROMPTFOO_PASS_RATE_THRESHOLD environment variable (default: 100%)
Modify exit behavior to consider the pass rate threshold
Update documentation to reflect new functionality

CC @MatanYadaev

Amazing @mldangelo ! WDYT about allowing the user to configure the pass rate threshold inside the configuration, instead of in a environment variable? In my use case, I have many different promptfoo configurations, each one has different pass rate threshold.

Amazing @mldangelo! WDYT about allowing the user to configure the pass rate threshold inside the configuration, instead of in an environment variable? In my use case, I have many different promptfoo configurations, each one has a different pass rate threshold.

@MatanYadaev This is a great idea! Luckily, it is already supported! In your promptfoo config files, you can set:
env:
  PROMPTFOO_PASS_RATE_THRESHOLD: 76.54

Thanks again for the product feature suggestion.


squishes up my header DIV

When using this inside a md-tab container, my header div that is above it gets squished up when I open a mdp-time-picker. Any reason for this? I'll see if I can get some example but its on my intranet sites at work.

To add to this, I added min-height CSS to my header class and it fixed some of it but now it adds a overflow scroll bar to my tabs area when the mdp-time-picker dialog is active. Then when it goes away the main overflow scroll for the page comes back causing the title to shift. Not sure if it's an issue or just something unique to my page.

i am not maintainer but you should create codepen example

Well I think I fixed it. I set a min-height for my DIV and removed the  around my whole form body and works fine now. So I believe it was just a unique situation. Closing


Cannot Find MBus meter using Libmbus: Collisions at all 250 addresses

I am trying to connect to an MBus meter and using a TechBase MBus 10 converter to RS232. Then I use an RS232 to USB and connected to a RPI3 with Raspian. Every time I scan (mbus-serial-scan -b 2400 /dev/ttyUSB0), it reports (Collision at address ###) for the addresses from 0 to 250. And it does not detect the meter. I have tried that with two meters with no luck. Can anyone give me any insights to this issue?
Thanks alot.

Can you compile with debug and post the output?! Or at all the complete output?

Please provide the output after adding the debug parameter "-d".
Did you try it with a PC?

Thanks a lot for the replies. This is a sample of the output I am getting:
Scanning primary addresses:
0 [2018-05-10 13:17:15] SEND (005): 10 40 00 40 16
[2018-05-10 13:17:15] RECV (001): 00
[2018-05-10 13:17:15] RECV (001): 00
[2018-05-10 13:17:15] RECV (001): 00
[2018-05-10 13:17:15] RECV (001): 40
[2018-05-10 13:17:15] RECV (001): 04
Collision at address 0
1 [2018-05-10 13:17:16] SEND (005): 10 40 01 41 16
[2018-05-10 13:17:16] RECV (001): 00
[2018-05-10 13:17:16] RECV (001): 00
[2018-05-10 13:17:16] RECV (001): 00
[2018-05-10 13:17:16] RECV (001): 00
[2018-05-10 13:17:16] RECV (001): 04
Collision at address 1
2 [2018-05-10 13:17:16] SEND (005): 10 40 02 42 16
[2018-05-10 13:17:16] RECV (001): 00
[2018-05-10 13:17:16] RECV (001): 00
[2018-05-10 13:17:16] RECV (001): 00
[2018-05-10 13:17:16] RECV (001): 02
[2018-05-10 13:17:16] RECV (001): 04
Collision at address 2
3 [2018-05-10 13:17:16] SEND (005): 10 40 03 43 16
[2018-05-10 13:17:16] RECV (001): 00
[2018-05-10 13:17:16] RECV (001): 00
[2018-05-10 13:17:16] RECV (001): 03
[2018-05-10 13:17:16] RECV (001): 02
[2018-05-10 13:17:16] RECV (001): 04
Collision at address 3
4 [2018-05-10 13:17:16] SEND (005): 10 40 04 44 16
[2018-05-10 13:17:16] RECV (005): 10 00 00 00 06
Collision at address 4
5 [2018-05-10 13:17:16] SEND (005): 10 40 05 45 16
[2018-05-10 13:17:17] RECV (001): 00
[2018-05-10 13:17:17] RECV (001): 00
[2018-05-10 13:17:17] RECV (001): 00
[2018-05-10 13:17:17] RECV (001): 00
[2018-05-10 13:17:17] RECV (001): 04
Collision at address 5
6 [2018-05-10 13:17:17] SEND (005): 10 40 06 46 16
[2018-05-10 13:17:17] RECV (001): 00
And it goes on scanning all 250 addresses and have collisions at all of them.

If I set the baud rate to 300, This is the output:
0 [2018-05-10 13:30:43] SEND (005): 10 40 00 40 16
[2018-05-10 13:30:43] RECV (005): 10 40 00 40 16
1 [2018-05-10 13:30:43] SEND (005): 10 40 01 41 16
[2018-05-10 13:30:43] RECV (005): 10 40 01 41 16
2 [2018-05-10 13:30:43] SEND (005): 10 40 02 42 16
[2018-05-10 13:30:43] RECV (005): 10 40 02 42 16
3 [2018-05-10 13:30:43] SEND (005): 10 40 03 43 16
[2018-05-10 13:30:44] RECV (005): 10 40 03 43 16
4 [2018-05-10 13:30:44] SEND (005): 10 40 04 44 16
[2018-05-10 13:30:44] RECV (005): 10 40 04 44 16
5 [2018-05-10 13:30:44] SEND (005): 10 40 05 45 16
[2018-05-10 13:30:44] RECV (005): 10 40 05 45 16
6 [2018-05-10 13:30:44] SEND (005): 10 40 06 46 16
[2018-05-10 13:30:44] RECV (005): 10 40 06 46 16
7 [2018-05-10 13:30:44] SEND (005): 10 40 07 47 16
[2018-05-10 13:30:44] RECV (005): 10 40 07 47 16
8 [2018-05-10 13:30:44] SEND (005): 10 40 08 48 16
[2018-05-10 13:30:45] RECV (005): 10 40 08 48 16
9 [2018-05-10 13:30:45] SEND (005): 10 40 09 49 16
[2018-05-10 13:30:45] RECV (005): 10 40 09 49 16
10 [2018-05-10 13:30:45] SEND (005): 10 40 0A 4A 16
[2018-05-10 13:30:45] RECV (005): 10 40 0A 4A 16
11 [2018-05-10 13:30:45] SEND (005): 10 40 0B 4B 16
[2018-05-10 13:30:45] RECV (005): 10 40 0B 4B 16
12 [2018-05-10 13:30:45] SEND (005): 10 40 0C 4C 16
[2018-05-10 13:30:45] RECV (005): 10 40 0C 4C 16
13 [2018-05-10 13:30:45] SEND (005): 10 40 0D 4D 16
[2018-05-10 13:30:46] RECV (005): 10 40 0D 4D 16
14 [2018-05-10 13:30:46] SEND (005): 10 40 0E 4E 16
[2018-05-10 13:30:46] RECV (005): 10 40 0E 4E 16
...

So 300 baud works except the fact that the Meter doesn't answer because of wrong baudrate?
Please provide more information:

Which libmbus version do you use?
Which Raspberry Pi kernel / OS do you use?

I guess you have a local echo. Back in 2012 implemented a simple echo cancelation, but this isn't perfect. It's the best to fix this in hardware or configuration.

I am using the latest one online (http://www.rscada.se/libmbus/). libmbus-0.8.0.tar.gz.
This is the version returned  by uname -a: Linux raspberrypi 4.9.80-v7+ #1098 SMP Fri Mar 9 19:11:42 GMT 2018 armv7l GNU/Linux
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 9.3 (stretch)
Release:        9.3
Codename:       stretch

Unfortunately the "latest" release was in 2012. You better take the current state from github. This wont fix your problem. Your Raspberry Pi is receiving garbage and libmbus doesn't any chance to decode it.
Here my ideas to narrow down the issue:

Connect the Raspberry Pi via USB to RS232 adapter to a PC and check the UART communication
Use a M-Bus Master with Echo Cancelation
Try the setup on a PC instead of Raspberry Pi
Make sure that your USB to RS232 adapter provides the necessary power on the handshake lines

I also did a check on Windows with mbus readout Software first and after that worked I had all Infos also to use on Linux.

I am using an FTDI USB/RS232 convertor (https://www.digikey.ca/products/en/computers-office-components-accessories/adapters-converters/882?k=rs232 to UARt). The usb is connected to the PI and the RS232 side is connected to the Master.
I will try it with windows and report the results back

I am not sure if I am testing it properly on windows, but I have installed bash and followed the same procedure. Now after installing everything from rscada, it gives the following error everytime I try to scan
mbus_serial_connect: failed to open tty.mbus_connect_serial: Failed to setup serial connection to M-bus gateway on /dev/ttyUSB0.
Failed to setup connection to M-bus gateway

On windows you need to use specific MBus software ... google for it ... There are also free versions.
I used https://www.relay.de/en/products/software/mbconf/
rscada library is not working under windows ... I have an experimental windows-build-branch in my fork but without all the binaries at the moment.

Did you tried the combination PC + Linux + MBus master + USB adapter?

I would just like to mention that I a bit new to the whole Linux thing but I am figuring out through reading and searching online ... just in case I asked some trivial question :)
If you mean running Linux on a Windows maching, then yes I have tried that as well and it gave me an error. I will replicate the error and insert it in the comment now.

There is also this flag everytime I run the ./configure command
Compiler flags:         -g -O2

No, from Windows 10 store, I have downloaded an Ubuntu (bash?) and used it. I dont know if that counts as a virtual machine. Here is a screenshot.

It seems I misunderstood what you meant by "PC + Linux + MBus Master + USB Adapter". Could you please elaborate on that?

Sorry, this won't work. You will need a native Linux (for example Ubuntu, Debian) running on your PC.

I have just installed xubuntu on my PC and still the same error. As if the adapter is not working with Linux on PC for some reason. Although it did work with the Pi

It's possible that the serial adapter introduce a too long delay. I will prepare a test branch.

@lategoodbye Hi Stephan,
Thank you very much for your followups. I have figured out the problem and it also relates to issue #84. I was installing and building the package in the normal user mode while using sudo. However, i tried everything in the (su) mode as root. And it all worked perfectly. Now the question is: what are the packages that are involved in the library or installation that needs an (su) permission level?
When I connect three meters, and scan through the primary addresses, it gives a collision at address 0. Just to confirm with you, that has to do with the primary address on the actual meters, is not it? This means that all if the meters are set to a primary address of 0.
When I tried scanning through the secondary addresses, it showed all three different meters and I was able to pull data from them using the mbus-serial-request-data command and their individual addresses.
Just to confirm, when we connect the meters, they are all connected in parallel, is not it?

This confuses me. What did you change to make it working? Does is works under Raspberry Pi, too?
Answers to your questions:

libmbus doesn't require special permission, but  access to serial interfaces like /dev/ttyUSB0 does.
Yes, primary addresses must be configured before using. Otherwise you will get collisions.
In case you have general questions about M-Bus please look at http://www.m-bus.com/files/MBDOC48.PDF

Nevertheless i prepared a extended version of mbus-serial-scan, which provides an option to specify an additional timeout in 1/10 seconds. Btw i reverted my last change to the serial timeouts.
Example with 1 second additional delay:
mbus-serial-scan -d -t 10 /dev/ttyUSB0
Relevant branch:
https://github.com/rscada/libmbus/tree/adjustable-timeout
@Apollon77 What's your opinion?

@lategoodbye literally all what I did is install the last library while being in su mode and it worked perfectly.
At first I installed the libmbus on the third party Pi, which had its own MBus code and always launches in su mode. The libmbus worked perfectly. This gave me the idea to try the libmbus in su mode on my RPi3 and that’s what I have done. Literally did not change a thing in the setup, and it worked perfectly on both my RPi and the Linux on PC as well.

Usually you also always need superuser rights to install libraries. libmbus doesn't have any influence on that. After installation it's necessary to call ldconfig, which also requires higher privileges.

@lategoodbye change seems reasonable. As soon as you officially commit that I can take the new default timings in my node-lib and receive user feedback too .. and if needed can build the same logic to use the new offset for slower systems if users need that.

@lategoodbye Hello,
I cannot find the mbus-serial-set-address command in the libmbus. Is it by any chance included in an updated version of the library?

I don't have access to the rscada website. How about downloading the latest version from github?

That works nicely. Thank you very much Stefan.

<EMAIL_ADDRESS>

Hi Stefan @lategoodbye,
Thank you for all the help so far. I was wondering, is there a way to read stored data in the meter? The meter at hand stores up to 30 days of data. So I was wondering if I can access that data using the Libmbus library.
Thank you.

Hi Stefan @lategoodbye
Hope this message finds you well.
I was wondering if the library can be used to retrieve historical data from the meters. As of now, it pulls the instantaneous values from the meter, However, what about historical data that is stored in the meter?

As long as the datapoints are described within the standard or MBDOC48 it should be possible. Sorry, how should i answer such a unspecific question.

Hi @lategoodbye,
I have figured out that this issue would have to do with the meter firmware and not with the library. I was able to retrieve historical data from the meter that was originally stored by the meter as past variables. So I get back from the meter say 20 variables with 7 of them historical values.
Thanks for the feedback.

@MZourob since you are new to this, i have couple of simple questions but i would rather avoid asking it here. Could you send me an email?

Mohammed.zourob<EMAIL_ADDRESS>Best Regards,
Mohammed Omar Zourob, Ph.D., M.E.Sc.
Electrical/Electronics Engineer
On Jun 29, 2018, at 5:39 PM, nardev <notifications<EMAIL_ADDRESS>wrote:
@MZourobhttps://github.com/MZourob since you are new to this, i have couple of simple questions but i would rather avoid asking it here. Could you send me an email?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/rscada/libmbus/issues/138#issuecomment-401480912, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlUjBqaihShS714s5sbdlmd61L6YB6wUks5uBp6egaJpZM4T4u6N.


Intent Relayer

Add a POC relayer that accepts EIP-712 signTypedData and uses Alchemy's AA paymaster to sponsor user intents.
To reconstruct the transaction, the request should come with a payload that includes all relevant arguments and parameters. These parameters can be validated by reconstructing the signature message and validating the signature.
Once validated, the relayer constructs the userOperation and forwards the request to Alchemy, which will sponsor the gas cost of the op.
This endpoint's role is to whitelist a specific relayer address on Alchemy and forward valid intent requests through this endpoint. The request payload is arbitrary, so I've tried to focus on providing relevant error messages when certain parameters are missing.

Looks like this was branched from a different branch so there are additional changes

@arjun-io thoughts on keeping the /genSig endpoint could allow users to bypass SDK use if they just want to generate intents. Was using it for testing but we could keep it in there?