Match asks for passphrase multiple time

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
When I initialize match it asks me for repository passphrase. After I typed in the passphrase and confirm it again, the cli just asks me again for the password. It goes on three or four times, then it proceeds
Complete output when running fastlane, including the stack trace and command used

~> fastlane match development
[✔] 🚀
[14:40:33]: fastlane detected a Gemfile in the current directory
[14:40:33]: however it seems like you don't use `bundle exec`
[14:40:33]: to launch fastlane faster, please use
[14:40:33]:
[14:40:33]: $ bundle exec fastlane match development
[14:40:33]:
[14:40:33]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[14:40:34]: Successfully loaded '/Users/William/Documents/work/clients/perceptolab/safehome/ios_app/fastlane/Matchfile' 📄
+---------+----------------------------------------------------------------+
|               Detected Values from './fastlane/Matchfile'                |
+---------+----------------------------------------------------------------+
| git_url | https://bitbucket.org/perceptolab_dev_team/sh-ios-certificates |
| type    | development                                                    |
+---------+----------------------------------------------------------------+
+-----------------------+----------------------------------------------------------------+
|                               Summary for match 2.102.0                                |
+-----------------------+----------------------------------------------------------------+
| type                  | development                                                    |
| git_url               | https://bitbucket.org/perceptolab_dev_team/sh-ios-certificates |
| git_branch            | master                                                         |
| app_identifier        | ["com.perceptolab.Safe-Home-test"]                             |
| username              |<EMAIL_ADDRESS>                                  |
| keychain_name         | login.keychain                                                 |
| readonly              | false                                                          |
| team_id               | C8FLG9R5F5                                                     |
| verbose               | false                                                          |
| force                 | false                                                          |
| skip_confirmation     | false                                                          |
| shallow_clone         | false                                                          |
| clone_branch_directly | false                                                          |
| force_for_new_devices | false                                                          |
| skip_docs             | false                                                          |
| platform              | ios                                                            |
+-----------------------+----------------------------------------------------------------+
[14:40:34]: Cloning remote git repo...
[14:40:34]: If cloning the repo takes too long, you can use the clone_branch_directly option in match.
[14:40:35]: 🔓  Successfully decrypted certificates repo
[14:40:35]: Verifying that the certificate and profile are still valid on the Dev Portal...
[14:40:38]: Couldn't find a valid code signing identity in the git repo for development... creating one for you now
+---------------+----------------------------------------------------+
|                      Summary for cert 2.102.0                      |
+---------------+----------------------------------------------------+
| development   | true                                               |
| force         | true                                               |
| username      |<EMAIL_ADDRESS>                      |
| team_id       | C8FLG9R5F5                                         |
| keychain_path | /Users/William/Library/Keychains/login.keychain-db |
| platform      | ios                                                |
+---------------+----------------------------------------------------+
[14:40:38]: Starting login with user<EMAIL_ADDRESS>[14:40:39]: Successfully logged in
[14:40:43]: Successfully generated 7TF86PW77Y which was imported to the local machine.
[14:40:43]: Verifying the certificate is properly installed locally...
[14:40:43]: Successfully installed certificate 7TF86PW77Y
+-------------------------------------+--------------------------------------------------+
|                                Summary for sigh 2.102.0                                |
+-------------------------------------+--------------------------------------------------+
| app_identifier                      |                    |
| username                            |                       |
| force                               | true                                             |
| cert_id                             | 7TF86PW77Y                                       |
| provisioning_name                   |  |
| ignore_profiles_with_different_name | true                                             |
| team_id                             | C8FLG9R5F5                                       |
| platform                            | ios                                              |
| development                         | true                                             |
| adhoc                               | false                                            |
| skip_install                        | false                                            |
| skip_fetch_profiles                 | false                                            |
| skip_certificate_verification       | false                                            |
| readonly                            | false                                            |
+-------------------------------------+--------------------------------------------------+
[14:40:44]: Starting login with user ''
[14:40:46]: Successfully logged in
[14:40:46]: Fetching profiles...
[14:40:47]: Verifying certificates...
[14:40:47]: No existing profiles found, that match the certificates you have installed locally! Creating a new provisioning profile for you
[14:40:50]: Creating new provisioning profile for 'com.perceptolab.Safe-Home-test' with name 'match Development com.perceptolab.Safe-Home-test' for 'ios' platform
[14:40:52]: Downloading provisioning profile...
[14:40:53]: Successfully downloaded provisioning profile...
[14:40:53]: Installing provisioning profile...
/var/folders/n5/hjsycrj55rlbd82pw270cmdr0000gn/T/d20180828-38207-6gh784/profiles/development/Development_com.perceptolab.Safe-Home-test.mobileprovision
[14:40:53]: Installing provisioning profile...
[14:40:54]: Enter the passphrase that should be used to encrypt/decrypt your certificates
[14:40:54]: This passphrase is specific per repository and will be stored in your local keychain
[14:40:54]: Make sure to remember the password, as you'll need it when you run match on a different machine
[14:40:54]: Passphrase for Git Repo: *****************
[14:44:36]: Type passphrase again: *****************
[14:45:09]: Enter the passphrase that should be used to encrypt/decrypt your certificates
[14:45:09]: This passphrase is specific per repository and will be stored in your local keychain
[14:45:09]: Make sure to remember the password, as you'll need it when you run match on a different machine
[14:45:09]: Passphrase for Git Repo: *****************
[14:45:58]: Type passphrase again: *****************
security: SecKeychainAddInternetPassword : The specified item already exists in the keychain.
[14:46:15]: Enter the passphrase that should be used to encrypt/decrypt your certificates
[14:46:15]: This passphrase is specific per repository and will be stored in your local keychain
[14:46:15]: Make sure to remember the password, as you'll need it when you run match on a different machine
[14:46:15]: Passphrase for Git Repo:

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.13.6

Ruby
2.3.7

Bundler?
false

Git
git version 2.15.2 (Apple Git-101.1)

Installation Source
~/.rvm/gems/ruby-2.4.0/bin/fastlane

Host
Mac OS X 10.13.6 (17G65)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib

OpenSSL Version
LibreSSL 2.2.7

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
9.4.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

platform :ios do
  desc "Updates development devices list"
  lane :updateDevDevices do
    register_devices(
      devices_file: "./dev_devices.txt"
    )
    match(
      type:"development",
      force_for_new_devices:true
    )
  end

  desc "Push a new beta build to TestFlight"
  lane :beta do
#    ensure_git_status_clean
    sync_code_signing
    match(type:"distribution")
    build_app(scheme: "Safe Home")
    upload_to_testflight
#    increment_build_number
#    commit_version_bump
#    add_git_tag
#    push_to_git_remote
  end
end

`./fastlane/Appfile`
app_identifier("com.perceptolab.Safe-Home-test") # The bundle identifier of your app
<EMAIL_ADDRESS># Your Apple email address

itc_team_id("118866831") # App Store Connect Team ID
team_id("C8FLG9R5F5") # Developer Portal Team ID

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.102.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.0

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.6.0

rouge
2.0.7

xcpretty
0.2.8

terminal-notifier
1.8.0

unicode-display_width
1.4.0

terminal-table
1.8.0

plist
3.4.0

public_suffix
2.0.5

addressable
2.5.2

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.6.5

tty-cursor
0.6.0

tty-spinner
0.8.0

babosa
1.0.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.62.0

faraday
0.15.2

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20180417

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.3

gh_inspector
1.1.3

json
<IP_ADDRESS>

mini_magick
4.5.1

multi_json
1.13.1

multi_xml
0.6.0

rubyzip
1.2.1

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.5.0

bundler
1.16.4

faraday_middleware
0.12.2

naturally
2.2.0

simctl
1.6.5

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mime-types-data
3.2018.0812

mime-types
3.2.2

jwt
2.1.0

memoist
0.16.0

os
1.0.0

signet
0.9.0

googleauth
0.6.6

httpclient
2.8.3

google-api-client
0.23.6

emoji_regex
0.1.1

io-console
0.4.5

generated on: 2018-08-28

Hi thank you for the response!
So the suggestion is to have a lane used to setup a brand new keychain just for fastlane and to pick up the password from environment.
Then when I set up a machine for deployment:

Run this keychains lane the first time
Run my beta lane (that will deploy a testflight) to publish

It that right?
This could be ok, but I didn't find any reference of this on the documentation. Therefore I ask: are we sure there isn't some bug somewhere in fastlane? Or maybe it's my computer having problem? 🔮
Because I can clearly see on my keychain (I'm running on macos) that the password has been created. It just seems that it doesn't get read by fastlane for some reason.
In the meantime I'll try the solution of setting up the keychains as suggested, I'll let you guys know what happens.
Thank you!


Can I add FLAG_NO_CLEAR

Can I write this with pugnotification library ?
Notification noti = new NotificationCompat.Builder(this).setContentTitle("Title").setSmallIcon(R.drawable.icon).build();
noti.flags |= Notification.FLAG_NO_CLEAR;
nm.notify(MAIN_NOTIFICATION, noti);

its have pull request for this issue
https://github.com/halysongoncalves/pugnotification/pull/25

Hello,
First I'm sorry for the delay! library already has a method for this: setDefaults (flags). This method is not meeting your case?

Hi @sytolk
Managed to check and test the new version?

Hi @sytolk
By check in version 1.7.0 now available!

Yes with ongoing(true) works now. Thanks!


Glob returns different files if ran from npm script

Heya,
I'm getting different results from globs when I run them directly through the CLI than I get when I run the same CLI command via a npm script.
I created a very simple repo to exemplify the CLI behaviour: https://github.com/filipesilva/glob-cli-test. It just runs console.log(glob.sync(process.argv[2])); and has a glob-cli-test binary.
Here is the issue in practice:
filipe.silva@DESKTOP-7ND6T3R MINGW64 /E/sandbox/glob-test
$ ls -la
total 13
drwxr-xr-x 1 filipe.silva filipe.silva   0 Apr  6 14:50 ./
drwxr-xr-x 1 filipe.silva filipe.silva   0 Apr  6 14:21 ../
-rw-r--r-- 1 filipe.silva filipe.silva   0 Apr  6 14:06 file.ts
drwxr-xr-x 1 filipe.silva filipe.silva   0 Apr  6 14:46 node_modules/
-rw-r--r-- 1 filipe.silva filipe.silva 162 Apr  6 14:42 package.json

filipe.silva@DESKTOP-7ND6T3R MINGW64 /E/sandbox/glob-test
$ cat package.json
{
  "scripts": {
    "glob": "glob-cli-test '**/*.ts'"
  },
  "dependencies": {
    "glob-cli-test": "git+https://github.com/filipesilva/glob-cli-test.git"
  }
}

filipe.silva@DESKTOP-7ND6T3R MINGW64 /E/sandbox/glob-test
$ cat file.ts

filipe.silva@DESKTOP-7ND6T3R MINGW64 /E/sandbox/glob-test
$ ./node_modules/.bin/glob-cli-test '**/*.ts'
[ 'file.ts' ]

filipe.silva@DESKTOP-7ND6T3R MINGW64 /E/sandbox/glob-test
$ npm run glob

> @ glob E:\sandbox\glob-test
> glob-cli-test '**/*.ts'

[]

filipe.silva@DESKTOP-7ND6T3R MINGW64 /E/sandbox/glob-test
$

I forgot to mention: I am running Windows 10, using gitbash.
As far as I can tell, this doesn't happen in OSX/Linux.

As per https://github.com/eslint/eslint/issues/5796#issuecomment-206717297, the issue is completely unrelated to glob but rather a quirk of cmd, and npm scripts use cmd.
For npm scripts to correctly pass arguments to node binaries, double quotes (") must be used instead of single quotes (').
The above example works perfectly well with double quotes:
filipe.silva@DESKTOP-7ND6T3R MINGW64 /E/sandbox/glob-test
$ ./node_modules/.bin/glob-cli-test "**/*.ts"
[ 'file.ts' ]

filipe.silva@DESKTOP-7ND6T3R MINGW64 /E/sandbox/glob-test
$ npm run glob

> @ glob E:\sandbox\glob-test
> glob-cli-test "**/*.ts"

[ 'file.ts' ]


Use maybe instances to fix compiler warnings

When installing with Node.js v6.9.2 there are compiler warnings. It should be possible to avoid the warnings with maybe instances.
$ npm install spi-device

><EMAIL_ADDRESS>install /home/pi/spi-device/node_modules/spi-device
> node-gyp rebuild

make: Entering directory '/home/pi/spi-device/node_modules/spi-device/build'
  CXX(target) Release/obj.target/spi/src/spi.o
  CXX(target) Release/obj.target/spi/src/spidevice.o
../src/spidevice.cc: In static member function ‘static v8::Local<v8::Object> SpiDevice::Open(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/spidevice.cc:53:61: warning: ‘v8::Local<v8::Object> v8::Function::NewInstance(int, v8::Local<v8::Value>*) const’ is deprecated (declared at /home/pi/.node-gyp/6.9.2/include/node/v8.h:3269): Use maybe version [-Wdeprecated-declarations]
   v8::Local<v8::Object> instance = cons->NewInstance(0, NULL);
                                                             ^
../src/spidevice.cc: In static member function ‘static v8::Local<v8::Object> SpiDevice::OpenSync(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/spidevice.cc:69:61: warning: ‘v8::Local<v8::Object> v8::Function::NewInstance(int, v8::Local<v8::Value>*) const’ is deprecated (declared at /home/pi/.node-gyp/6.9.2/include/node/v8.h:3269): Use maybe version [-Wdeprecated-declarations]
   v8::Local<v8::Object> instance = cons->NewInstance(0, NULL);
                                                             ^
  CXX(target) Release/obj.target/spi/src/open.o
  CXX(target) Release/obj.target/spi/src/close.o
  CXX(target) Release/obj.target/spi/src/transfer.o
  CXX(target) Release/obj.target/spi/src/getoptions.o
  CXX(target) Release/obj.target/spi/src/setoptions.o
  SOLINK_MODULE(target) Release/obj.target/spi.node
  COPY Release/spi.node
make: Leaving directory '/home/pi/spi-device/node_modules/spi-device/build'
/home/pi/spi-device
└─┬<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/spi-device/package.json'
npm WARN spi-device No description
npm WARN spi-device No repository field.
npm WARN spi-device No README data
npm WARN spi-device No license field.
$

Fixed with 39c77a6b993446e0a0005d67db44f8a4fcb687fb in v0.2.5.


Editing the user model to incorporate tournament tokens

In this issue, we will edit the user model to add an attribute for tournament tokens. All users start with one token and will eventually automatically get a new token every 30 days. The maximum token balance will be 3.

Issue Score: Satisfactory
Comments:
Good minor change! Missing closing statement and included two team labels and thus satisfactory.


e2e: Fix string type conversions

This PR removes string(...) type conversions where stringer can be used; introduces fmt.Sprintf for readability.

Codecov Report

Merging #3672 (6cc7e02) into main (c83b94b) will increase coverage by 0.38%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3672      +/-   ##
==========================================
+ Coverage   67.04%   67.42%   +0.38%
==========================================
  Files         178      181       +3
  Lines        8696     8773      +77
==========================================
+ Hits         5830     5915      +85
+ Misses       2835     2825      -10
- Partials       31       33       +2

Flag
Coverage Δ

unittests
67.42% <ø> (+0.38%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/service/types.go
25.00% <0.00%> (-8.34%)
:arrow_down:

pkg/kubernetes/announcement_handlers.go
71.42% <0.00%> (-5.72%)
:arrow_down:

pkg/configurator/methods.go
68.49% <0.00%> (-0.53%)
:arrow_down:

cmd/osm-controller/osm-controller.go
14.09% <0.00%> (-0.29%)
:arrow_down:

pkg/envoy/xdsutil.go
89.13% <0.00%> (-0.18%)
:arrow_down:

pkg/utils/service.go
100.00% <0.00%> (ø)

pkg/configurator/mock_client_generated.go
0.00% <0.00%> (ø)

cmd/osm-controller/log_handler.go
84.00% <0.00%> (ø)

pkg/catalog/gateway.go
100.00% <0.00%> (ø)

pkg/constants/constants.go
0.00% <0.00%> (ø)

... and 13 more

Continue to review full report at Codecov.

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


Little directory correction

Only changing the directory in the beginning of instructions since the one proposed does not make sense

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1081   +/-   ##
=======================================
  Coverage   41.84%   41.84%
=======================================
  Files          69       69
  Lines       13207    13207
  Branches     2204     2204
=======================================
  Hits         5526     5526
  Misses       7257     7257
  Partials      424      424

Continue to review full report at Codecov.

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


Component root node changing is broken

http://codepen.io/localvoid/pen/WojeKN

@localvoid hmm - I'm not sure I'm seeing the bug?

@developit I think you were checking the wrong implementation, for React. The repro for Preact is here: https://jsfiddle.net/localvoid/h84zogmc/

Bleh, shouldn't have done issue triage before finishing my morning coffee.

what feedback needed ? this issue looks dangerous when using preact with preact-compat and react 3rd party libraries

I had labelled it prior to realizing I was looking at the React version. It's a corner case that I have not yet seen any third party react library rely on, likely since very few libraries render the root element for a complete application.


Dynamic Hub implementation

Sketch from meeting
public interface IClientProxy {
    Task InvokeAsync(string methodName, params object[] args);
}

public class DynamicClientProxy : DynamicObject {
    // Take an IClientProxy and wrap it in Dynamic goodness
    // Kindly do the needful
}

// The interface formerly known as IHubConnectionContext<TClient> (remove the generic)
public interface IHubClients {
    IClientProxy All { get; }
    IClientProxy User(string userId);
    IClientProxy Group(string group);
    IClientProxy Client(string connectionId);
}

public class DynamicHubClients {
    private IHubClients _inner;

    dynamic All { get; } = new DynamicClientProxy(_inner.All);

    // Not sure how best to cache this. We'd need to cache per userId/group/connectionId etc,
    dynamic User(string userId) => new DynamicClientProxy(_inner.User(userid));
    dynamic Group(string group); // Etc..
    dynamic Client(string connectionId); // Etc..
}

public class Hub {
    // ... everything else ...

    // This already exists, except with the old name for IHubConnectionContext<TClient>
    IHubClients Clients { get; set; }

    // ... everything else ...
}

public class DynamicHub : Hub {
    private dynamic _clients;

    public new dynamic Clients {
        get { return _clients ?? new DynamicHubClients(base.Clients); }
        set { _clients = value; }
    }
}

// Remove IHubContext<THub, TClient>
public interface IHubContext<THub> where THub: Hub {
    // ... everything else ...

    // This doesn't change, other than the rename:
    public IHubClients Clients { get; }

    // ... everything else ...
}

Careful with https://github.com/aspnet/SignalR/blob/dev/src/Microsoft.AspNetCore.SignalR/Internal/HubReflectionHelper.cs, don't replace Hub<> with Hub, just delete typeof(Hub<>) and such

Done in cfaa4b69d7db134a759da920fa80d74374cc6b3a and 8ba29b578da537af40d3e4942da6580963d7812c


[incubator/kafka] advertise listeners on NodePort when external type is NodePort

Signed-off-by: S.Cavallo<EMAIL_ADDRESS>What this PR does / why we need it:
See - https://github.com/helm/charts/pull/10817
We use NodePort and all our listeners connect to our nodes via the NodePort IPs.
The PR above changed the advertised listeners from the IP of the pod (internal - default or external - when nodeport ) to a hostname which resolves in kube DNS.  When using NodePort, we don't want to use DNS - we want to use the NodePort, so we'd like to advertise all the nodes on the NodePort IPs.
I feel like the intention of advertisedListenersOverride is to override the listeners.
The current behavior is to append.  I can certainly change this PR so that advertisedListenersOverride actually overrides the value instead of appending to it.  If that route is acceptable I can do that instead, and then the .Values.external.type "NodePort" conditional isn't required.  It could simply be overridden using existing functionality.
I would prefer to do that, especially since the current behavior feels like a bug.  Maybe I'm misunderstanding of that value or how the advertisement works.  Hoping you could advise there.
Which issue this PR fixes
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X ] DCO signed
[X ] Chart Version bumped
[X ] Variables are documented in the README.md
[X ] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @benjigoldberg

/assign @benjigoldberg
(had to bump the chart version)

/ok-to-test

/lgtm


Add testcases for multiasset empty asset name and change output

Motivation: gitmachtl found out that empty asset names are failing on Ledger: https://github.com/LedgerHQ/app-cardano/pull/6#discussion_r575789114 and also change addresses with tokens are not being shown properly: https://github.com/LedgerHQ/app-cardano/pull/6#discussion_r574796166
These bugs were already fixed in the ledger app and this PR modifies existing testcase with multiple tokens to contain one with empty name and adds a new testcase with tokens in the change output.
Testing:
yarn test-integration --grep signTxOrdinaryMary passes

oh wow, is empty asset name even allowed by the blockchain? :facepalm:

@ppershing Yes, there are mentions of it even in the CIP for their bech32 id: https://github.com/cardano-foundation/CIPs/pull/64/files#diff-4c43a9bbb8cbb0ad1fc0800c7369e8ad640d6fe97d40cea94c41ed50f9089a94R22


javascript heap out of memory

Thank you for your attention to my question！
In my project, after several times change and recompile, the node process crashed with error "javascript heap out of memory". So, I want to know why every time it recompile will consume so much memory (Probably increased by 900MB) ? Is there a memory leak in webpack-hot-middleware ?
I had set --max_old_space_size to 8192, but it can't fundamentally solve the problem.

Have same problem. have some way to solve this?

ping!

I’ve never seen this behaviour, and judging by the small number of comments here, it’s rather rare.
It is unlikely to be related to this module, but could be down to webpack’s compiler or another plugin - as no-one has included any steps to reproduce the issue, there’s nothing more I can add at this point.


[srp-server] implement TTL processing

Not directly related to this PR but a thought on handling of TTL and SRP replication:
I guess we need to  inform what TTL value was used by the original SRP server which processed the SRP Update Message so other SRP server can follow and we have consistent service info. I guess we can use a similar mechanism to how we include granted "lease" info along with SRP update message in SRPL (and include granted TTL). @Abhayakara thoughts?


Unknown element 'patient' found while parsing

I try to create an encounter and link a patient to this encounter by method resource.setPatient. I get this error
c.u.fhir.parser.LenientErrorHandler [LenientErrorHandler.java:150] Unknown element 'patient' found while parsing
The environemnt I am using is HAPI FHIR JPA SERVER DSTU3 and as client

ca.uhn.hapi.fhir
hapi-fhir-structures-dstu3
2.2

ca.uhn.hapi.fhir
hapi-fhir-base
2.2

had to use 2.5 client. Problem fixed


[Deploy] Google Chat Integration?

Service

https://chat.google.com/
Link to your repository

Additional Information

sorry, just found that the integration already exists under "hangouts chat". never mind.


npm ERR! could not determine executable to run when trying to install

Describe the bug

When trying to install project via npx create astro@latest -- --template eliancodes/brutal, I get the error:
npm ERR! could not determine executable to run
Minimal example
Link to minimal example:
https://github.com/ElianCodes/brutal
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
npm version 10.2.4
node version v20.11.0

ah yeah, this behaviour changed. Can you try if npm create astro@latest -- --template eliancodes/brutal works for you?

Yes, that worked!


How should "belongs to" relations be kept up to date?

Lets say I have two models, Users and Posts. A user has many posts.
const user = new Schema('users');
const post = new Schema('posts');

user.define({
  posts: arrayOf(post)
});

When a user creates a new post, our API call responds with the JSON representing the new post:
entities: {
  posts:  {
    123: {
      user_id: 3,
      title: "How to use Normalizr",
      content: "A great library for normalizing your data."
    }
  }
},
result: 123

This is great for updating my store's entities.posts, however now my entities.users[3].posts is out of date since it doesn't have this new post.
What is the correct way to keep the user's posts up to date?
This seems similar to #70, except extra declarations seem unnecessary since we know the relationship.

My approach to this problem is to takes the result IDs and concatenate it to the correct field of my data structure.
What helps a lot is that I have some metadata about how should I process those results, basically it's something like this:
(redux context)
const createPost = (title, content) => dispatch => {
  // Let's assume that the authenticated user is creating the post.
  const userId = getCurrentUser().id
  return dispatch(WebAPI.createPost({title, content}))
  .then(resp => resp.data)
  .then(data => normalize(data, PostSchema))
  .then(({entities, result} => dispatch(receivePosts(entities, result)))
  .then(postIds => dispatch(receiveId('users', userId, 'posts', postIds)))
}

receiveId reducer could be implemented like the following:
function handleNewID (state, entityKey, entityIds) {
  return {
    ...state,
    [entityKey]: [...state[entityKey], ...entityIds]
  }
}

// some reducer code
function reduceNewID (state, action) {
   // containerKey = 'users'
  // containerId = userId
  handleNewID(state[action.containerKey][action.containerId], action.entityKey, action.entityIds)
}

But well, it could be a bad approach, I know it works quite good, and it could be a lot more improved using combineReducers. What I hate with this is that I require that receiveId is somehow verbose about how to update it.
You could combine this with ImmutableJS.
What do you think?


Add kotlin-logging as logging framework

Description
Refactor output written to stdout / stderr to log statements where applicable.
The kotlin-logging framework uses SLF4J as underlying logging framework. The latter framework does not allow to change the desired log level to be changed at runtime. As ktlint supports the command line flag "--debug" to print additional logging, it was needed to add logback as underlying logging framework.
The IndentationRule and the RuleExtension class both changed the logging behavior based on the environment variable KTLINT_DEBUG. This variable could be assigned multiple values. This variable is now split into two distinct variables KTLINT_UNIT_TEST_TRACE and KTLINT_UNIT_TEST_DUMP_AST which can either be set to "on" to enable TRACE resp. DUMP_AST functionality or anything else to disable it. End users of ktlint should use the new command line flag "--trace" resp. the existing "--print-ast".
Solved a bug in DumpASTRule when retrieval of the linenumber results in a IndexOutOfBoundsException cause by an AST mutation resulting in an invalid offset.
In RuleExtension improved the logic regarding dumping the AST. When invoked from the extension, the DumpASTRule print the output to STDOUT instead of STDERR.
Following needs explicit attention while reviewing:

Check the way the Gradle dependencies are added. I have little knowledge of Gradle.
I was not able to find published checksums for the added dependencies, so I have added the Gradle generated keys

Closes #589
Checklist

[ ] tests are added
[X] CHANGELOG.md is updated

FYI, as a consequence of this change, if any of these modules are used in a classpath with an existing logger (e.g. in an IDE), it will throw a java.lang.LinkageError unless slf4j is excluded as a transitive dependency:
api("com.pinterest.ktlint:ktlint-core:0.45.1") {
    exclude("org.slf4j")
}

Just a gotcha for any other ktlint library consumers 😁


Add Proper Style to Source Codes

It'd be a good idea to prettify source code in blog posts, as of now they're pretty bland.

We should also limit the width of source code boxes, as they're overflowing blog post content box:

I was already to report this.
Checkout this links to help us improve this
https://github.com/PrismJS/prism
https://highlightjs.org/

Will do.
Thanks @acidiney

Fixed in https://github.com/Henry-Keys/portfolio-and-blog/pull/20


Could you add onFinishedUpload callback?

@nd0ut I would like to get an uploaded image's url when upload process is finished
I am looking for something like this:
      <lr-file-uploader-inline ref={ref} class={classNames}>
        <lr-upload-ctx-provider ref={widgetContext}></lr-upload-ctx-provider>
      </lr-file-uploader-inline>

...

widgetContext.current.setOnUploadFinished((uploadedFileUrls) => {
// some react state changes from my app
})

Hey @karol-unum-la,
we're workin on that in https://github.com/uploadcare/uc-blocks/pull/226/
you'll be able to catch uploading finished event from the lr-data-output block

Hey @karol-unum-la,
see https://uploadcare.github.io/blocks/docs/events/


Change API domain to sailoperator.io

PR needs rebase.

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-sigs/prow repository.

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

Test name
Commit
Details
Required
Rerun command

gencheck_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test gencheck

scorecard_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test scorecard

e2e-kind_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test e2e-kind

unit-tests_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test unit-tests

lint_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test lint

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

gencheck_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test gencheck

scorecard_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test scorecard

e2e-kind_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test e2e-kind

unit-tests_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test unit-tests

lint_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test lint

unit-tests-arm64_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test unit-tests-arm64

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

scorecard_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test scorecard

e2e-kind_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test e2e-kind

unit-tests_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test unit-tests

lint_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test lint

unit-tests-arm64_sail-operator_main
95f32dae2e5e52e76c23ee88199e9ee2c97ec4c5
link
true
/test unit-tests-arm64

gencheck_sail-operator_main
9c2283d855a4ad71af58d98ff9e68dc143646d86
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

PR needs rebase.

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-sigs/prow repository.

@dgn: 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

gencheck_sail-operator_main
51ad810af4344b37fa03a2de5a7c99dc41efdb27
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

PR needs rebase.

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-sigs/prow repository.

@dgn: 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

gencheck_sail-operator_main
cdf5c617a96fa103d775d79fedb09f577d5f216e
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

gencheck_sail-operator_main
cdf5c617a96fa103d775d79fedb09f577d5f216e
link
true
/test gencheck

integ-tests-arm64_sail-operator_main
cdf5c617a96fa103d775d79fedb09f577d5f216e
link
true
/test integ-tests-arm64

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

integ-tests-arm64_sail-operator_main
cdf5c617a96fa103d775d79fedb09f577d5f216e
link
true
/test integ-tests-arm64

gencheck_sail-operator_main
d7f0d4190d5b6464f58e33c33014ba71539f17c6
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

gencheck_sail-operator_main
d7f0d4190d5b6464f58e33c33014ba71539f17c6
link
true
/test gencheck

lint_sail-operator_main
b4a96be7e6b199c5239fe9e6141a0e8c9a15d65d
link
true
/test lint

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

gencheck_sail-operator_main
d7f0d4190d5b6464f58e33c33014ba71539f17c6
link
true
/test gencheck

lint_sail-operator_main
b4a96be7e6b199c5239fe9e6141a0e8c9a15d65d
link
true
/test lint

scorecard_sail-operator_main
b4a96be7e6b199c5239fe9e6141a0e8c9a15d65d
link
true
/test scorecard

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

lint_sail-operator_main
b4a96be7e6b199c5239fe9e6141a0e8c9a15d65d
link
true
/test lint

scorecard_sail-operator_main
b4a96be7e6b199c5239fe9e6141a0e8c9a15d65d
link
true
/test scorecard

gencheck_sail-operator_main
b4a96be7e6b199c5239fe9e6141a0e8c9a15d65d
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

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

Test name
Commit
Details
Required
Rerun command

lint_sail-operator_main
b4a96be7e6b199c5239fe9e6141a0e8c9a15d65d
link
true
/test lint

scorecard_sail-operator_main
b4a96be7e6b199c5239fe9e6141a0e8c9a15d65d
link
true
/test scorecard

gencheck_sail-operator_main
9f1989d4378696a00322259633f05b04cf0b7243
link
true
/test gencheck

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-sigs/prow repository. I understand the commands that are listed here.

Any chance we can use sailoperator.io instead of sail-operator.io? Having to type dashes in apiVersion always feels weird to me.

Any chance we can use sailoperator.io instead of sail-operator.io? Having to type dashes in apiVersion always feels weird to me.

Hmm. It's a good point but having the repo name as sail-operator and API domain as sailoperator would be inconsistent

PR needs rebase.

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-sigs/prow repository.

PR needs rebase.

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-sigs/prow repository.

In response to a cherrypick label: #209 failed to apply on top of branch "release-0.1":
Applying: Change API domain to sailoperator.io
.git/rebase-apply/patch:844: trailing whitespace.
$ kubectl get istiorevisions.sailoperator.io
.git/rebase-apply/patch:853: trailing whitespace.
    $ kubectl get istiorevisions.sailoperator.io
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	Makefile.core.mk
M	bundle/manifests/operator.istio.io_istiocnis.yaml
M	bundle/manifests/operator.istio.io_istiorevisions.yaml
M	bundle/manifests/operator.istio.io_istios.yaml
M	bundle/manifests/operator.istio.io_remoteistios.yaml
M	bundle/manifests/sailoperator.clusterserviceversion.yaml
M	chart/crds/operator.istio.io_istiocnis.yaml
M	chart/crds/operator.istio.io_istiorevisions.yaml
M	chart/crds/operator.istio.io_istios.yaml
M	chart/crds/operator.istio.io_remoteistios.yaml
M	docs/api-reference/operator.istio.io.md
M	hack/download-charts.sh
M	tests/e2e/controlplane/control_plane_test.go
Falling back to patching base and 3-way merge...
Auto-merging tests/e2e/controlplane/control_plane_test.go
Auto-merging hack/download-charts.sh
Auto-merging docs/api-reference/sailoperator.io.md
Auto-merging chart/crds/sailoperator.io_remoteistios.yaml
CONFLICT (content): Merge conflict in chart/crds/sailoperator.io_remoteistios.yaml
Auto-merging chart/crds/sailoperator.io_istios.yaml
CONFLICT (content): Merge conflict in chart/crds/sailoperator.io_istios.yaml
Auto-merging chart/crds/sailoperator.io_istiorevisions.yaml
CONFLICT (content): Merge conflict in chart/crds/sailoperator.io_istiorevisions.yaml
Auto-merging chart/crds/sailoperator.io_istiocnis.yaml
CONFLICT (content): Merge conflict in chart/crds/sailoperator.io_istiocnis.yaml
Auto-merging bundle/manifests/sailoperator.io_remoteistios.yaml
Auto-merging bundle/manifests/sailoperator.io_istios.yaml
Auto-merging bundle/manifests/sailoperator.io_istiorevisions.yaml
Auto-merging bundle/manifests/sailoperator.io_istiocnis.yaml
Auto-merging bundle/manifests/sailoperator.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in bundle/manifests/sailoperator.clusterserviceversion.yaml
Auto-merging Makefile.core.mk
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Change API domain to sailoperator.io
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to a cherrypick label: new issue created for failed cherrypick: #287


Update Backgroun images for SDK and libraries

https://www.figma.com/file/6NA1usM50PE2DG74CjL8A5/SDK%2FLibraries?node-id=181%3A1467
Currently, in this page: https://developer.thenewboston.com/developer-tools , we are using generic images for the various libraries and SDK. We should update the images to the ones shown in the figma.
You can grab the images either on figma, or ask @kristykjlee directly for the images.

This issue is reserved for @akandejaphet


brief explanation every line

Hello, i just want to request to add some brief explanation every line of that psp_ident output in README, like what is difference between firmware and shipped firmware or what is the meaning of that addresses, is that version, memory location or something, thank you!

You can learn all this things from PSP Dev Wiki.


segfault using php7?

Technical details

YOURLS version: 1.7.2
PHP version: 7.0.19-1~dotdeb+8.1
Debian 8.8 VPS server using MariaDB  10.0.30-MariaDB-0+deb8u2

Reproducible Bug Summary

Install yourls
admin backend login works
using shortlinks breaks
Neither the redirect us nor the statistcs view of the short links works. It just gets back no data from the webserver.

I don't get error log entries in the vhost apache logs but massive entries in the central error log like

Everything is in this sentence!
It shouldn't be related to YOURLS directly, this is often more general.
Preliminary debugging: did you try your server with a very basic PHP page?

As I wrote the admin part runs, the setup did work, and the server runs some other virtual hosts like piwik. So I don't think that ticket should be closed so fast.
Back to my question: php7 is supported?

php7 is supported

Yes.

Very yes. 🐕

If admin part works and redirection doesn't, then the problem mostly sits between the apache, its conf and the mod_rewrite module.
Basically if admin part works, YOURLS works. The redirection part is very simple in itself and if there's a problem then it's a server config problem. Check https://github.com/YOURLS/YOURLS/wiki/Troubleshooting-first-steps


Your projecteuler problems are not visible on the website now.

It shows that the Data cant be shown now. Please look into it.

Hi, i can view the problem https://projecteuler.net/problem=53

Yes solutions.md in solutions folder is not updated, can you help in updating it ? or maybe writing a script that will search for solution folders and create solutions.md file ?

I can add the script to run in github actions, so during deployment we can deploy all the added solutions to the website

Okay maybe it was some issue on my end, it's working now.


don't try to use sched_getcpu() if glibc is < 2.6

In addition to not being available in musl, sched_getcpu() is not
available if the glibc version is less than 2.6.  Fall back to not
determining the correct current CPU if the call is not available,
similar to what is done when musl is used.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

@grpc-testing seems to be very eager to test the pull request :smirk_cat:

I don't think that we've ever claimed to support glibc < 2.6 . My concern is that adding this will put in a code path that we didn't test but nevertheless have to maintain indefinitely. Is there a more general workaround?

It's the same code path that would be taken if GPR_MUSL_LIBC_COMPAT would be defined.  But defining that to get gRPC working with an older version of glibc doesn't seem right.
What do you mean by more general workaround?

Could we do something akin to what we do in env_linux.c (using dlfcn to probe the binary to see if a symbol is available, and grabbing a function pointer to that)

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

dlsym seems to be used to load either getenv or its secure version in env_linux.c. But This seems be done because the we can gracefully degrade the requirements in that case (secure_getenv to getenv). Note that directly beneath this is a glibc version check just like that. In this case, there are no gracefully degraded alternatives. We simply return 0. So I don't think it makes sense to dlsym sched_info when we have already implemented the version check that is also present in env_linux.c

I agree with @osadalakmal here.  I don't quite see the benefits of using dlsym to grab the function pointer if it's available.  Is there any advantage to doing that that I'm missing?
(I'm happy to make the changes if that's the direction we want to go in.  I'm just wondering if there's a reason that would make it worth supporting the extra complexity of doing that)

We got the OS upgraded on the last machines that only had glibc < 2.6, so as there seems to be no interest in this, and I personally don't care about this anymore, I'm going to close this PR.


Ukrainian locale name is incorrect

Version
5.4.0
Link to Minimal Reproduction
No response
Steps to Reproduce
Ukrainian locale code is "UK" and not "UA", as it is in version 5.4.0
Current Behavior
Locale code for Ukrainian language is "UA"
Expected Behavior
Locale code for Ukrainian language should be "UK"
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
No response

Reference PR #17244

Thanks for your feedback! You are welcome to open a PR to fix it. :)


Implemented publish twist state

Added a new state which publishes the given geometry_msgs::Twist to the given topic.

Looks good, thank you!


Update illustrations to include cell type report

We will need to update all of our illustrations on the download page to account for the new cell type report that will be included in downloads.
The new structure is as follows:
Project Download
project_id
├── README.md
├── bulk_metadata.tsv
├── bulk_quant.tsv
├── sample_id
│   ├── SCPCL000000_filtered.rds
│   ├── SCPCL000000_processed.rds
│   ├── SCPCL000000_qc_report.html
|   ├── SCPCL000000_celltype_report.html*
│   ├── SCPCL000000_unfiltered.rds
└── single_cell_metadata.tsv

Sample Download
sample_id
├── README.md
├── SCPCL000000_filtered.rds
├── SCPCL000000_processed.rds
├── SCPCL000000_qc_report.html
├── SCPCL000000_celltype_report.html*
├── SCPCL000000_unfiltered.rds
└── single_cell_metadata.tsv

Note that we will need to make the updates in both illustrations for downloading SCE objects and AnnData objects. For all illustrations, the new report should be added at the same level as the RDS/HDF5 files (within the sample_id folder).

Note to self: Add accessed data to the project-id and sample-id

Single-cell Project Download

Single-cell Sample Download

AnnData Project Download

AnnData Sample Download

AnnData CITE-seq Download

Changing the <download_date> to <accessed-date> per #176 and sizing up to improve image quality
Single-cell Project Download

Single-cell Sample Download

AnnData Project Download

AnnData Sample Download

AnnData CITE-seq Download

Does this look correct?

Perfect, thank you!

Closed by #191


Handle 404 receipt statuses properly

Add code to RRM receipt service to get status from the content and handle appropriately

Closed in #29


Automatically convert numpad's . to a whatever symbol separates integers and decimals in the locale

A good thing would be to automatically convert numpad's . to a whatever symbol separates integers and decimals (e.g. comma), like gnumeric does.

Originally posted by @bordam in https://github.com/nlogozzo/NickvisionMoney/issues/11#issuecomment-1312789887

Should be fixed with https://github.com/nlogozzo/NickvisionMoney/commit/2f4cc4e743e78eca3c10622266ee22a63da438d1

Please keep in mind that if your keyboard locale is en, then that gets interpreted as . for the decimal separator. If your keyboard locale, for your case, is in it, then it should input as ,.

Hmm, it only works on xorg for me and when I write a . the blinking cursor goes back to the beginning of the amount...

The fact that it only works on xorg is out of my control. Must be an issue with wayland and gdk events.
However, i will fix it so the cursor stays at the end.

Gnumeric manages to do it just fine... is it a gtk4 issue at this point? I think we should report it, in that case

Yes I believe it night be a gtk4 issue, which seems to happen a lot on Wayland...

Please keep in mind that if your keyboard locale is en, then that gets interpreted as . for the decimal separator. If your keyboard locale, for your case, is in it, then it should input as ,.

Yesterday I tested this on a PC with AMD videocard using radeon driver (idk if it does matter, but just in case) and Wayland. Now I tested on another PC with NVIDIA card and proprietary driver. On Wayland, works as expected. On Xorg, if I run the app with en locale it works as expected, but with ru locale it always inputs , for both en and ru keyboard layout, but if the layout is en, the cursor goes to the beginning of a line.

@bordam The position of the cursor should be fixed in the latest commit: https://github.com/nlogozzo/NickvisionMoney/commit/9b54008665c2b420733a024cc80a7a115537a6e8

Bad news, with the latest commit a crash occours to desktop whenever I type . in xorg
Video del 2022-11-23 17-35-13.webm

And if the application still crashes, would you be able to run it from the terminal and provide me with any error messages you get when it crashes.

Screencast from 2022-11-23 12-27-50.webm
I'm on xorg with NVIDIA drivers and it works no problem for me...

what happens if you go on wayland?

Nothing: . is not converted and no CTD occurs

I guess it is best if I remove this feature from the release until we can get it working correctly for you.

This feature works on both x and wayland for gnome calculator (gtk4+libadwaita)
Maybe we can borrow some code from it?

I will look at how gnome calculator handles it.
Is your keyboard locale set for it_IT? I know for @fsobolev it automatically changes to , when his keyboard layout is in his locale and uses . when in en_US, which is to be expected.

Sorry for late answer!!
Keyboard layout is Italian indeed. LC_ALL is it_IT.utf8 and localectl status outputs it as keyboard and x11 layouts.
I have an AMD GPU.

@fsobolev Any idea what to do with this?
You say this is already working correctly when you switch the keyboard layout to ru_RU for you, correct? When you type numpad . you get ,?

@bordam Is this still an issue for you in the new Denaro version?

@nlogozzo maybe this will work differently in C#... I mean, maybe there will be no crash and the feature will work correctly even if it will be implemented the same way it was in C++ version. We can try.

Yes, it’s still an issue for me.

@bordam Does this work correctly in gnome calculator?

Yes, it works correctly and it almost seems like it’s not “converting” the character, but it’s rather automatically inserting the correct one

https://github.com/nlogozzo/NickvisionMoney/releases/tag/2023.2.0-rc1-f1


[Security] Security Issue

Environment
Self-Hosted (Docker)
System
No response
Version
No response
Describe the problem
First of all I'd like to say thank you for developing Dashy, this tool is very useful.
I send you multiples emails about security vulnerability (SSRF) in a certain Dashy endpoint and never get and answer, maybe I have the wrong email ?
Additional info
No response
Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

I think backend security is not currently in scope for the development. There is an open issue #668 on this topic, which has been open for quite a while now.


[1.0.1] Fix to #5738 - Query Perf: Selecting entire table for navigation properties in projections

Fixes #5738
Fix is to allow more queries to be translated to SQL, specifically subqueries that are correlated with outer query, e.g.
customers.Select(c => c.Orders.FirstOrDefault())
would be translated to:
customers.Select(c => orders.Where(o => o.CustomerId == c.Id).FirstOrDefault())
This would previously produce outer query to fetch all the customers and for each customer another query, fetching ALL the orders each time filtering out the orders for each customer and returning only the first one on the client (because we didn't know how to handle o.CustomerId in this case)
With this change we will convert o.CustomerId into a SQL parameter, whose value is set for each iteration of the outer query - this can be easily translated to SQL and produce much more efficient queries:
SELECT [t].[CustomerID]
FROM [Customers] AS [c]
@_outer_CustomerID: ALFKI (Size = 450)
SELECT TOP(1) [o].[OrderID], [o].[CustomerID], [o].[EmployeeID], [o].[OrderDate]
FROM [Orders] AS [o]
WHERE @_outer_CustomerID = [o].[CustomerID]
We achieve this by introducing a new query method that creates additional parameters before enumerating it's source, and then removing those parameters after all elements have been enumerated or the enumerator has been disposed.
This way we make sure that the additional parameters only exist in the scope that the inner query is executed.
This also forces some changes in the CommandCache - we used QueryContext.ParameterValues as cache key, but since now the parameter values are modified during query execution we need to rely on cloning them at and used the cloned values as the cache key.

@anpete


Disable some css transformations (such as inset)

Command
build
Description
When building our project there seems to be some css optimizations we don't want. Specifically, this code will get optimized
top: 0;
right: 0;
bottom: 0;
left: 0;

into
inset: 0;

This doesn't work on some older browsers, and breaks our UI completely. Seems like this isn't done by SCSS, and I can't find a way to disable it. Changing .browserslistrc doesn't seem to have an effect.
Describe the solution you'd like
A way to disable some transformations.
Describe alternatives you've considered
No response

Hi @BojanKogoj,
Can you please share the output of ng version, and your browserslist configuration?

But I've tried to change last version, no change. Our issue came from iPhone 11 pro (iOS 14), which seems is no longer supported?

Indeed IOS 14 is no longer officially supported. However, adding ios_14 to the browserslist configuration will generate the expected CSS.
styles.bed628adee984d5d.css:
*{top:0;right:0;bottom:0;left:0}

Unfortunately it doesn't work for some reason. If I use ios_14, I get
An unhandled exception occurred: Unknown browser query `ios_14`. Maybe you are using old Browserslist or made typo in query.

If I use ios_saf 14 it will build but still use inset.

It was supposed to be ios 14 (without the underscore), although ios_saf 14 does result in the same output.

One thing you could try is to re-generate the lock file. Maybe you have some outdated dependencies if the lock file is unmaintained.
rm -rf node_modules package-lock.json
npm i

You were right; the problem was our UI library was already transforming it. For some reason it wasn't transformed for storybook, but was transformed when building library.


Comments should remain associated with the element they comment

Executed:
const Yawn = require('yawn-yaml/cjs')
const input = `
- foo # 1st comment
- bar # 2nd comment
`
const original = new Yawn(input)
const json = original.json

json.push('biz')

original.json = json
console.log(original.yaml)

Expected:
- foo # 1st comment
- bar # 2nd comment
- biz

Observed:
- foo # 1st comment
- bar
- biz # 2nd comment

With:
    "yawn-yaml": {
      "version": "1.3.4",
      "resolved": "https://registry.npmjs.org/yawn-yaml/-/yawn-yaml-1.3.4.tgz",
      "integrity": "sha1-FMUaGUAkJJwi9TS20lQaVNCryt0=",
      "requires": {
        "js-yaml": "3.9.1",
        "lodash": "3.10.1",
        "yaml-js": "0.1.5"
      },
      "dependencies": {
        "lodash": {
          "version": "3.10.1",
          "resolved": "https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz",
          "integrity": "sha1-W/Rejkm6QYnhfUgnid/RW9FAt7Y="
        }
      }
    },

Very similarly:
const Yawn = require('yawn-yaml/cjs')
const input = `
foo: bar # 1st comment
baz: biz # 2nd comment
`
const original = new Yawn(input)
const json = original.json

json.moo = 'baa'

original.json = json
console.log(original.yaml)

Expected:
foo: bar # 1st comment
baz: biz # 2nd comment
moo: baa

Observed:
foo: bar # 1st comment
baz: biz
moo: baa # 2nd comment

Probably the same case.

It doesn't travel across levels:
const Yawn = require('yawn-yaml/cjs')
const input = `
a:
  foo: bar # 1st comment
  baz: biz # 2nd comment
b: c # 3rd comment
`
const original = new Yawn(input)
const json = original.json

json.a.moo = 'baa'
json.d = 'e'

original.json = json
console.log(original.yaml)

Expected:
a:
  foo: bar # 1st comment
  baz: biz # 2nd comment
  moo: baa
b: c # 3rd comment
d: e

Observed:
a:
  foo: bar # 1st comment
  baz: biz
  moo: baa # 2nd comment
b: c
d: e # 3rd comment


Lacking segment type for whole register load/store

we are glad to see the vector spec add whole register load/store instructions,
they help compiler/gcc to create more efficient code for spilling register without vsetvl* instructions :)
but there are not any instructions for unit-stride segment type ?
I think the this type also have same requirement like normal memory load/store,
so I suggest that we should add instructions for the type like bellow :
# Format
vlseg<nf>e<eew><emul>.v vd, (rs1), vm      # Unit-stride segment load template
vsseg<nf>e<eew><emul>.v vs3, (rs1), vm     # Unit-stride segment store template
# Examples
vlseg8e8m2.v vd, (rs1), vm   # Load eight vector registers with eight byte fields in 2 lmul.
vsseg3e32m2.v vs3, (rs1), vm  # Store packed vector of 3*4-byte segments from vs3,vs3+1,vs3+2 to memory in 2 lmul.

These operations can be emulated just by inserting a vsetvli (to select the desired LMUL and set vl to maximum) and using an existing unit-stride segment load or store.  Plus, it doesn't seem like they would provide much value.
The justification for the whole register loads and stores was to avoid the need to override vtype/vl in spill/fill code.  But that argument seems irrelevant here, since it doesn't make sense to use segment loads/stores in spill/fill code.

These operations can be emulated just by inserting a vsetvli (to select the desired LMUL and set vl to maximum) and using an existing unit-stride segment load or store. Plus, it doesn't seem like they would provide much value.
The justification for the whole register loads and stores was to avoid the need to override vtype/vl in spill/fill code. But that argument seems irrelevant here, since it doesn't make sense to use segment loads/stores in spill/fill code.

I mean gcc use segment loads/stores in spill/fill code actually, so we need to avoid the need to override vtype/vl.

@kito-cheng any thought for this requirement ?

GCC probably needs to change.  Even ignoring this discussion, some implementations will execute segment loads and stores at lower performance than regular unit-stride loads and stores.  If you need to e.g. spill registers 12 - 16, you should use vs4r v12 then vs1r v16, rather than vsseg5 v12.

@topperc How to spill about for unit-stride segment loads and stores in LLVM ?
it's same as @aswaterman mentioned ?

@topperc How to spill about for unit-stride segment loads and stores in LLVM ?
it's same as @aswaterman mentioned ?

LLVM uses multiple whole register load and store instructions. Incrementing a scalar pointer register by VLENB * LMUL between each. We use the LMUL from the segment load/store. We don't optimize to use a larger load/store for multiple registers that are more aligned than the LMUL.

I think use multiple whole register load and store should be right way to fix that issue on GCC, many of GCC implementation are done before whole register load and store added...and we didn't have put too much engineer there now :(

@aswaterman @topperc @kito-cheng
Thanks for your feedback,
I will make the patch for GCC also :)


Find and set $WINDOWID to X11 window ID

Closes issue #471.
The window ID is retrieved from Display (from Window) in run and passed to tty::new, which uses builder.env to set it.
ns ~> echo $WINDOWID
62914562
ns ~> xdotool getactivewindow
62914562

What is the setup for this build? https://travis-ci.org/jwilm/alacritty/jobs/235577841
Either way, it looks like glutin::os::unix is only available in some configurations. Does anybody have any recommendations for how it should get to this?

The unix module is available in this configuration, which means something like this would work:
#[cfg(any(target_os = "linux", target_os = "dragonfly", target_os = "freebsd", target_os = "openbsd"))]
pub fn get_window_id(&self) -> Option<usize> {
	use glutin::os::unix::WindowExt;

	match self.glutin_window.get_xlib_window() {
		Some(xlib_window) => Some(xlib_window as usize),
		None => None
	}
}

#[cfg(not(any(target_os = "linux", target_os = "dragonfly", target_os = "freebsd", target_os = "openbsd")))]
pub fn get_window_id(&self) -> Option<usize> {
	None
}

This still seems a bit awkward, though. Is there any better way to do this based on whether glutin::os::unix is available?

In src/font/lib.rs the only two variants are macOS or not macOS.
#[cfg(not(target_os = "macos"))]
extern crate freetype;

#[cfg(target_os = "macos")]
extern crate core_text;

Thanks @portify!


Fix #11

Fixed this while refactoring some code so didn't get a chance to merge it, but I'm gonna add you to the mod credits still, thank you!


Gas analysis of sendTransfer

The gas cost of sendTransfer is currently higher than we would like (200k+), and we need to figure out where the sinks are in order to plan where we should optimize.
The goal here is to figure out where the biggest sinks of gas cost is when doing sendTransfer.
This work might be smart to wait with until we have done #95, which might affect the gas cost of sendTransfer.

Relevant discussion from Serdar:
sendTransfer should be purely in solidity as we need snappiness here. This is something the user is expected to interact with directly. And also this is the step the user is sending funds, the result of that needs to resolve immediately.
Acks are out of scope for this issue as we are investigating only the sendTransfer function. At the moment, sendTransfer is more than twice as expensive as an aggregated ack operation. Not to mention that success acks are not even necessary.
Let's not use ZK here please as there is no serious computation happening. Here are the gas posts in Serdar's opinion:

ERC20 transfer
4 way call due to new eureka specs to support multipacket workflows:
ICS20 -> ICS26 -> ICS20 -> ICS26
Packet serde logic
Needless store writing

Hey @gjermundgaraba, could you provide more details about how the 200k gas for sendTransfer was computed?
In the transferTest file at line 58 we have the test_success_sendTransfer which executes the sendTransfer function.
Running on the main branch the command forge test --match-path test/ICS20TransferTest.t.sol --match-test test_success_sendTransfer -vvvv  gives in output the following trace:
This trace shows that the entire test consumes 73336 gas with the sendTransfer function consuming only 32046 which actually seems pretty cheap.
Where is 200k gas for sendTransfer coming from?

Ok, so I guess that the test used to compute the 200k is the IntegrationTest test_success_sendICS20PacketFromICS20Contract
Here’s the analysis of the sendTransfer function call and all the internal calls it makes resulting from analizyng the output trace of the command forge test --match-path test/IntegrationTest.t.sol --match-test test_success_sendICS20PacketFromICS20Contract  -vvvv

ICS20Transfer::sendTransfer

Gas: 221,227

Internal Calls within sendTransfer

TestERC20::fullDenomPath

Gas: 188
Result: Reverted (EvmError: Revert).

ICS26Router::sendPacket

Gas: 188,992

Internal Calls within sendPacket

ICS02Client::getCounterparty

Gas: 12,217

IBCStore::nextSequenceSend

Gas: 25,324

ICS20Transfer::onSendPacket

Gas: 82,315

Internal Calls within onSendPacket

TestERC20::balanceOf (Escrow)

Gas: 558

TestERC20::transferFrom

Gas: 23,850

TestERC20::balanceOf (Escrow)

Gas: 558

IBCStore::commitPacket

Gas: 35,096

Internal Operations

Multiple calls to PRECOMPILES::sha256 for hash calculations.
Total cost per hash: 72 gas.

What I would also like to find here are the missing pieces. There are clearly some sections inside both IC26Router and ICS20Transfer spending quite a bit of gas. It would be good to find out how much is spent on for instance encoding back and forth from string to addresses/bytes, abi encoding, etc. A good starting place would be getSendERC20AddressAndSource and getReceiveERC20AddressAndSource. They are doing quite a bit of string parsing and so on that I am curious the cost of.

O yeah, for that I discussed with aditya to do two PoCs:

1 we prepare the data on the cosmos side to be perfectly matching the expected type on the Eth side (e.g. using EVM address type instead of strings) to check how much we gain.
2 inspect if can manage the denom differently than strings concatenation.

I think we should be able to get a general idea of the cost with low effort by either adding gas section snapshots inside the contracts or expose and test the individual sections in unit tests to find the unknown gas. Then, we can see which area to focus on.


⚠ Bofrost.at has degraded performance

In f950cab, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 990 ms

Resolved: Bofrost.at performance has improved in 0c38d3c.


[BUG]: [ERROR] Unable to download selected episode 1 [WARN] No full streams found!

Program version
5.1.4
Operating System
Windows
Type
CLI
Service
Crunchyroll
Command used
aniDL --service "crunchy" -s G6WEC315N -e 1 --novids --noaudio --chapters false --dlsubs ar
Show ID
G6WEC315N
Episode
1
Console Output
=== Multi Downloader NX 5.1.4 ===

USER: ********
Your Country: ********

[S:G6WEC315N] No Longer Allowed in Another World (Season: 1) [SIMULCAST, SUB]
  - Subtitles: en, es-419, es-ES, pt-BR, fr, de, ar, it, ru
 ✓[01|E:GG1U2J9Q1] ☆ 1 - I Must Commit Double-Suicide! [23m40s, SUB, STREAM]
    - Subtitles: en, es-419, es-ES, pt-BR, fr, de, ar, it, ru

Requesting: [GG1U2J9Q1] No Longer Allowed in Another World - 1 - I Must Commit Double-Suicide!
[WARN] No full streams found!
[ERROR] Unable to download selected episode 1

Additional Information
No response

Do you have mp4decrypt and a CDM?

Do you have mp4decrypt and a CDM?

Yes I have

I found out what caused this problem
It was in the bin-path.yml file
By default it was like this
ffmpeg: "ffmpeg.exe"
mkvmerge: "mkvmerge.exe"
ffprobe: "ffprobe.exe"
mp4decrypt: "mp4decrypt.exe"
After I modified it
ffmpeg: ".\bin\ffmpeg.exe"
mkvmerge: ".\bin\mkvmerge.exe"
ffprobe: ".\bin\ffprobe.exe"
mp4decrypt: ".\bin\mp4decrypt.exe"
The script is now working

The script is now working

I tried your solution and now it's more broken cries


Add documentation to this project

[x]  Install mkdocs
[x]  configure mkdocs in the current project.
[x]  Add Get started.
[x]  API reference.

DONE


Does filtering return JSON support?

xray(“{a:1,b:2}”, '*')(function(err, res) {   console.log(res)  })
Some sites return JSON instead of HTML.

There isn't direct support for JSON. Sorry.
On Fri, Sep 18, 2020 at 9:28 AM chunfytseng<EMAIL_ADDRESS>wrote:

xray(“{a:1,b2}”, '*')(function(err, title) { console.log(title) // Google
})
Some sites return JSON instead of HTML.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/matthewmueller/x-ray/issues/369, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAT6ISWDLAOMEGHGWJ5NNDSGNVBPANCNFSM4RSCJG7A
.


Expected behaviour with .then() attached to resolved promise

@othiym23 can I ask your opinion on something? (this isn't an issue about CLS per se)
I've been having some problems using CLS, bluebird and co together, with CLS context sometimes getting lost. By way of trying to narrow down the problem, I've written a set of tests which run against various different bluebird CLS shims to see how they all behave in different circumstances.
Please see: https://www.github.com/overlookmotel/cls-bluebird-test
There's one weird case...
(NB cls-bluebird2 is the beginnings of an attempt at a new cls-bluebird shim)
var Promise = require('bluebird');
var cls = require('continuation-local-storage');
var clsBluebird = require('cls-bluebird2');
var assert = require('assert');

var ns = cls.createNamespace('test');
clsBluebird(ns, Promise);

// CASE 1
var promise;
ns.run(function() {
	ns.set('test', 123);
	promise = Promise.resolve().then(function() {
		assert(ns.get('test') == 123);
	});
});

promise.then(function() {
	assert(ns.get('test') == 123);
});

Both assert statements pass in this case. I think that's the correct behaviour - the .then() outside of ns.run() should inherit CLS context from the previous promise in the chain.
But how about this:
// CASE 2
var promise;
ns.run(function() {
	ns.set('test', 123);
	promise = Promise.resolve();
});

promise.then(function() {
	assert(ns.get('test') == 123);
});

In this 2nd case, the assert statement fails.
Should it? My first thought was that it should execute in the context of the promise chain, in the same way as case 1. On the other hand, it's chaining onto a promise which is already resolved. So in what sense is it "following on from" that promise in the way that a node callback "follows on" immediately from the function that calls it?
What's your opinion?
More generally speaking, there are quite a lot of subtleties in reasoning the desired behaviour of CLS context passing with promises. async-listener's shim of native promises takes the view that it's all about following the chain of execution down the promise chain (and so both the above cases pass), whereas cls-bluebird executes code in a .then() in the context in which .then() was called (so both above cases fail).
Has anyone written down any kind of spec, or made a set of tests to define desired behaviour?

A more complete discussion here: https://github.com/othiym23/node-continuation-local-storage/issues/64


Extension file cannot be loaded

Hello,
I have downloaded the project files and tried to load the chrome extension program as instructed in README but it seems there's some problem with the extension file.

Re-building the extension file may be the way to go.
Thank you

The error says it couldn't load the built file. So make sure you've followed the build instruction correctly.

Go to the root directory. Root directory contains package.json.
Run the scripts below

$ npm install
$ npm run build

Check if the file webuffet.built.js is generated under the /extension/build/ directory.
Load the directory 'extension' from the Chrome.

I close this issue since it's not directly related to the source codes.


Problems with metro bundler

For some weird reason metro bundler does not work properly. When I ran the "npm run bundler" to generate bundled file, it works fine without any warnings. But when I run it on the device it threw an error "util.inherits is not a function". Although, my node app works completely fine when I am running webpack to bundle.
How to reproduce

just bundle the following code and try running it on ios

const dht = require("@hyperswarm/dht");
const crypto = require("crypto");
const { LiquidCore } = require("liquidcore");

// A micro service will exit when it has nothing left to do.  So to
// avoid a premature exit, set an indefinite timer.  When we
// exit() later, the timer will get invalidated.
setInterval(() => {}, 10000);

console.log("Hello, World!");

// Listen for a request from the host for the 'ping' event
LiquidCore.on("ping", () => {
  // When we get the ping from the host, respond with "Hello, World!"
  // and then exit.
  LiquidCore.emit("pong", { message: "Hello, there" });
});

// Ok, we are all set up.  Let the host know we are ready to talk
LiquidCore.emit("ready");

const node = dht({
  // just join as an ephemeral node
  // as we are shortlived
  ephemeral: true,
});

const topic = crypto
  .createHash("sha256")
  .update("Some-Random-Channel")
  .digest();

// announce a port

node.unannounce(topic, { port: 12345 }, function (err) {
  if (err) throw err;

  console.log("began announcing");
});

If you need help with this let me know

Which version of LiquidCore are you using?  There was definitely a problem using the metro bundler with the minifier turned on, which is the default for bundling.  I turned it off by default in one of the latest releases.  Can you confirm that the bundle is not minified?


Terraform throws an error if prefect_token variable not set

Describe the bug
Terraform throws an error if prefect_token variable not set

Can you elaborate, that is an expected behaviour, its is set in CI for automated deployment and for local you have to set TF_VAR_prefect_token environment variable or pass it as CLI using -var ?

Can you elaborate, that is an expected behaviour, its is set in CI for automated deployment and for local you have to set TF_VAR_prefect_token environment variable or pass it as CLI using -var ?

Ah, I see what you mean, I just saw the check for if prefect set is incorrect:
https://github.com/Quansight/qhub-cloud/blob/74fc27b80529c18b2516867b04fc0c840beb1ef8/qhub/template/{{ cookiecutter.repo_directory }}/infrastructure/variables.tf#L89
It should be rather: {% if cookiecutter.prefect is true -%}, I'll create a PR in a sec.


openshift: thanos receive guaranteed QoS

This commit is a follow up from previous incidents. It puts the Thanos
receiver in the QoS class. This will also give yield more consistent
scaling characteristics once we introduce HPA.
Signed-off-by: Lucas Servén Marín<EMAIL_ADDRESS>This is a follow up from our last incident.
cc @metalmatze @brancz @kakkoyun

Not sure how this is going to conflict with the work @brancz is doing.

Yeah I don't think this is gonna be fun to resolve. I'm happy to incorporate it into my PR or do it as a follow up on top. It would be trivial on top, just like this patch is.

No, let’s just wait. There’s no rush to merge this but I also don’t want to
lump in more unrelated things into your PR
El El mié, feb. 5, 2020 a las 15:20, Frederic Branczyk <
<EMAIL_ADDRESS>escribió:

Yeah I don't think this is gonna be fun to resolve. I'm happy to
incorporate it into my PR or do it as a follow up on top. It would be
trivial on top, just like this patch is.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/observatorium/configuration/pull/171?email_source=notifications&email_token=AE4JAP7WHTBY3Z3YD5URM7LRBLDK7A5CNFSM4KQKT4K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK3SYHI#issuecomment-582429725,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE4JAPYTP5VD2LY7KPRKYDTRBLDK7ANCNFSM4KQKT4KQ
.

rebased and ready to review :ship: :)


[LIVE-5682] Feature - Address Poisoning Filter

📝 Description
This PR aims at temporarly remove ERC20 transactions with an amount = 0 from the UI to prevent address poisoning.
Once possible, this fix should be directly applied to the respective coin integrations.
❓ Context

Impacted projects: coin-framework, live-common, ledger-live-desktop, ledger-live-mobile
Linked resource(s): https://ledgerhq.atlassian.net/browse/LIVE-5682

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo
https://user-images.githubusercontent.com/44363395/220674281-47019685-b193-42db-be10-d7ac53e4fc2c.mov
https://user-images.githubusercontent.com/44363395/220674823-d5124ed3-7e16-4f5c-b419-7728a88b4a1f.mp4
🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

/generate-screenshots

/generate-screenshots


Xcode crippled when debugging programmatically created UI with chunkwm running

I have a weird issue I've been struggling with which is only seen when debugging in Xcode. It is only seen when using a programmatically created window, and seems to be caused by the FFM plugin.
System
Mojave 10.14.1
Xcode 10.1 (Swift 4.2.1)
Steps to reduce

Load chunkwm with the FFM plugin and scripting additions.
Open an Xcode project (sample that reproduces issue)
Programmatically launch a swift app using NSApplicationMain and create a window then show using window.makeKeyAndOrderFront(nil)
Put a breakpoint in your window code and try to step through
Observe the speed you are able to step through or use the Xcode UI.

I assume this has something to do blocking the main thread, but it doesn't happen at all if chunkwm is disabled. Most interestingly, I tried to get some logs by running chunkwm from the command line, and got this message:
2018-11-20 07:50:57 WARN : chunkwm: plugin 'tiling' is not loaded.
objc[96057]: Class OverlayView is implemented in both /Users/ryan/.chunkwm_plugins/border.so (0x10f552918) and /Users/ryan/.chunkwm_plugins/tiling.so (0x10f59b710). One of the two will be used. Which one is undefined.
2018-11-20 07:50:59 ERROR: chunkwm: plugin 'Focus Follows Mouse' init failed!

And the problem did not occur, so is presumably in the ffm plugin. Unfortunately FFM is one of the main appeals of chunkwm so I'd prefer not to disable it.
Does anyone have any idea what's going on? Seems to be a main loop blocking issue but I'm not sure how to take it further.

The ffm plugin is a fairly simple, single file implementation.
I suspect the issue you are seeing is because it returns false here:
https://github.com/koekeishiya/chunkwm/blob/master/src/plugins/ffm/plugin.cpp#L200
I can't currently say why it fails, but that is very likely the issue. It all boils down to the pretty crappy accessibility API..

Thanks, I'll try and debug it some more when I'm back from leave next week.


Documentation incorrect: lang().months returns function rather than months array

Documentation states:
var fr = moment().lang('fr');
fr.lang().months // ["janvier", "février", "mars", ...]

but on a Node.js REPL:
var fr = moment().lang('fr');
fr.lang().months // [Function]

Side note: executing the function throws an error
fr.lang().months()
TypeError: Cannot call method 'month' of undefined
    at Object.Language.months (./node_modules/moment/moment.js:352:35)
    at repl:1:12
    at REPLServer.self.eval (repl.js:109:21)
    at Interface.<anonymous> (repl.js:248:12)
    at Interface.EventEmitter.emit (events.js:96:17)
    at Interface._onLine (readline.js:200:10)
    at Interface._line (readline.js:518:8)
    at Interface._ttyWrite (readline.js:736:14)
    at ReadStream.onkeypress (readline.js:97:10)
    at ReadStream.EventEmitter.emit (events.js:126:20)
    at emitKey (readline.js:1058:12)
    at ReadStream.onData (readline.js:807:7)

2 years later and the doc is still wrong...


feat(phar): add phar tooling and autobuilding on CI

I tested to download then execute the PHAR. Everything works 👏🏼


Documentation link is broken

Hello!
Thank you for this great library!
However, the documentation link in the README is broken:
http://guzzle3.readthedocs.io/en/latest/
Where do I find docs for this version of Guzzle?
Thanks!

I've tried to build it myself using make html, but I'm getting the error: unsupported theme option 'github_user' given.

Just found the docs here:
http://guzzle3.readthedocs.io/http-client/client.html#request-options
I hope they are up to date to the version of this repo. Please fix the link in the README please.
Thanks!

I've updated the readme to remove the docs link.
https://github.com/guzzle/guzzle3/commit/f7778ed85e3db90009d79725afd6c3a82dab32fe


Added Flutter Based Expense Tracker App

Title and Issue number

Close #3869

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

please check this out @MohitGupta121, thanks!


Transmit AddSource errors and handle schedule()

Handle errors as part of register in the add_source method on the event
loop
Also ensure that multiple calls to schedule will always call the last
wake callback scheduled.

Re-use the Slot abstraction from the futures crate to coordinate inserting
values and arranging callbacks.

r? @aturon
Curious what you think of the strategy here, I'm not sure if it's readily applicable to the transmission of the error on schedule, deschedule, and drop_source, but I'd like to remove those unwrap calls before we start benchmarking as well. Transmission of these errors seems like they may have a bit of an impact on the "happy path".

OK, so yes I was missing that on_full doesn't consume the value. Nice!
re: the error transmission strategy: I would prefer to avoid this expense on every registration if at all possible. I can see some ways to do that. When we add a source, we have an opportunity to create some arbitrary shared state between the event loop and the IO futures. We also know that at most one future is using each "direction" of a source. So we can stash the error in some atomic (perhaps even just stashing the raw OS error suffices?), and immediately invoke the associated Wake. On the other side, when polling readiness, we can check the associated error slot and propagate.
If that sounds plausible to you, I'm happy to implement.

Yeah I was thinking that's basically what we'd have to do if we do anything at all. It's a good point that we only have two futures at most looking for readiness, means we can control the outcomes a little better.
It's a bit of a shame to do so many allocations for each I/O object created, but I think we can at least consolidate them all down to one and that's probably not too bad in the long run.
You feel good about this general strategy though? Basically having a slot which is filled in and then the future is responsible for communicating that error back at some point. I'd want to implement all of it (communicating errors) and do some benchmarking to ensure we're not losing too much perf, the overhead here may be slightly worrisome.

SGTM


Account settings

What this PR does / why we need it:
This PR contains UI screens for Account Settings Tab.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #1749
Checklist

[x] Does this PR have a corresponding GitHub issue?
[ ] Have you included relevant README for the chaoslib/experiment with details?
[ ] Have you added debug messages where necessary?
[x] Have you added task comments where necessary?
[ ] Have you tested the changes for possible failure conditions?
[ ] Have you provided the positive & negative test logs for the litmusbook execution?
[ ] Does the litmusbook ensure idempotency of cluster state?, i.e., is cluster restored to original state?
[ ] Have you used non-shell/command modules for Kubernetes tasks?
[ ] Have you (jinja) templatized custom scripts that is run by the litmusbook, if any?
[ ] Have you (jinja) templatized Kubernetes deployment manifests used by the litmusbook, if any?
[ ] Have you reused/created util functions instead of repeating tasks in the litmusbook?
[ ] Do the artifacts follow the appropriate directory structure?
[ ] Have you isolated storage (eg: OpenEBS) specific implementations, checks?
[ ] Have you isolated platform (eg: baremetal kubeadm/openshift/aws/gcloud) specific implementations, checks?
[ ] Are the ansible facts well defined? Is the scope explicitly set for playbook & included utils?
[ ] Have you ensured minimum/careful usage of shell utilities (awk, grep, sed, cut, xargs etc.,)?
[ ] Can the limtusbook be executed both from within & outside a container (configurable paths, no hardcode)?
[ ] Can you suggest the minimal resource requirements for the litmusbook execution?
[ ] Does the litmusbook job artifact carry comments/default options/range for the ENV tunables?
[ ] Has the litmusbooks been linted?

Special notes for your reviewer:

/preview

/preview

/preview

/preview

/preview 20


[Usage] Merging LoRa weights into llava-13b fails with bizarre error

Describe the issue
Issue:
I have fine-tuned liuhaotian/llava-v1.5-13b on an OCR task using LoRa. I am now trying to use this model for inference but when I try to merge the LoRa weights it throws a bizarre error both saying that the Llava configs (LlavaConfig, LlavaMptConfig, LlavaMistralConfig) are installed and simultaneously that they don't exist. I am using the latest version of the repo (Commit: c121f04) and the default conda environment, with the only difference being that i installed protobuf because it threw an error if it wasn't installed. I have been able to replicated this across multiple cloud machines.
transformers==4.37.2 and tokenizers==0.15.1
Command:
python scripts/merge_lora_weights.py \
    --model-path ./checkpoint-200/ \
    --model-base 'liuhaotian/llava-v1.5-13b' \
    --save-model-path merge_model

Log:
Traceback (most recent call last):
  File "/home/shadeform/LLaVA/scripts/merge_lora_weights.py", line 22, in <module>
    merge_lora(args)
  File "/home/shadeform/LLaVA/scripts/merge_lora_weights.py", line 8, in merge_lora
    tokenizer, model, image_processor, context_len = load_pretrained_model(args.model_path, args.model_base, model_name, device_map='cpu')
  File "/home/shadeform/LLaVA/llava/model/builder.py", line 128, in load_pretrained_model
    model = AutoModelForCausalLM.from_pretrained(model_base, low_cpu_mem_usage=True, **kwargs)
  File "/home/shadeform/miniconda3/envs/llava/lib/python3.10/site-packages/transformers/models/auto/auto_factory.py", line 569, in from_pretrained
    raise ValueError(
ValueError: Unrecognized configuration class <class 'transformers.models.llava.configuration_llava.LlavaConfig'> for this kind of AutoModel: AutoModelForCausalLM.
Model type should be one of BartConfig, BertConfig, BertGenerationConfig, BigBirdConfig, BigBirdPegasusConfig, BioGptConfig, BlenderbotConfig, BlenderbotSmallConfig, BloomConfig, CamembertConfig, LlamaConfig, CodeGenConfig, CpmAntConfig, CTRLConfig, Data2VecTextConfig, ElectraConfig, ErnieConfig, FalconConfig, FuyuConfig, GitConfig, GPT2Config, GPT2Config, GPTBigCodeConfig, GPTNeoConfig, GPTNeoXConfig, GPTNeoXJapaneseConfig, GPTJConfig, LlamaConfig, MarianConfig, MBartConfig, MegaConfig, MegatronBertConfig, MistralConfig, MixtralConfig, MptConfig, MusicgenConfig, MvpConfig, OpenLlamaConfig, OpenAIGPTConfig, OPTConfig, PegasusConfig, PersimmonConfig, PhiConfig, PLBartConfig, ProphetNetConfig, QDQBertConfig, Qwen2Config, ReformerConfig, RemBertConfig, RobertaConfig, RobertaPreLayerNormConfig, RoCBertConfig, RoFormerConfig, RwkvConfig, Speech2Text2Config, TransfoXLConfig, TrOCRConfig, WhisperConfig, XGLMConfig, XLMConfig, XLMProphetNetConfig, XLMRobertaConfig, XLMRobertaXLConfig, XLNetConfig, XmodConfig, LlavaConfig, LlavaMptConfig, LlavaMistralConfig.

Notice that according to the error LlavaConfig, LlavaMptConfig, LlavaMistralConfig are installed.

add llava in the folder name

where exactly? @NandhaKishorM

@sumit-mahaseel  same issue, did you fix it?


why can't find path

I did that
You can try to install CK as described here: https://github.com/ctuning/ck#windows
and then try to install Caffe using related CK package:
$ ck pull repo --url=https://github.com/dividiti/ck-caffe
$ ck install package:lib-caffe-bvlc-master-cudnn-universal --env.CAFFE_BUILD_PYTHON=ON
CK should automatically detect your Visual Studio, CUDA, cuDNN and attempt to build Caffe - hope it will work ...
From the back of my mind, I didn't have problems with CUDA 9.0 when using VS 2015. Current problems are when using CUDA 9.x with the latest VS 2017 release.
find is ok
C:\Users\LF2>ck find repo:ck-caffe
C:\Users\LF2\CK\ck-caffe
install is error...
C:\Users\LF2>ck install package:lib-caffe-bvlc-master-cudnn-universal --env.CAFFE_BUILD_PYTHON=ON
CK error: [package] can't find path to CK entry "module:package" (?:032630d041b4fd8a:?)!
I don't know what to do...

@SuperPowerLF2 That's very weird. module:package is in repo:ck-env:
$ ck find module:package
/home/anton/CK_REPOS/ck-env/module/package

which should be pulled in by CK due to the dependencies.
Could you please do:
$ ck pull repo:ck-env

and try again?

Hi @SuperPowerLF2 . Yes, looks like somehow ck-env was not pulled.
Can you please also list what is in your C:\Users\LF2\CK directory?
You can also try to update all repositories as follows and then try again:
$ ck pull all

Thanks!