bitfinex v2 fetch_ohlcv empty / null response handling

It seems, that bitfinex v2 fetch_ohlcv sometimes returns empty / null responses. I guess some problems on bitfinexs side. I get these warnings in my errorlog:
PHP Warning:  array_key_exists() expects parameter 2 to be array, null given in /srv/www/htdocs/crypt/includes/classes/ccxt.php on line 4772
PHP Warning:  array_values() expects parameter 1 to be array, null given in /srv/www/htdocs/crypt/includes/classes/ccxt.php on line 917
PHP Warning:  Invalid argument supplied for foreach() in /srv/www/htdocs/crypt/includes/classes/ccxt.php on line 918
The $response in line 4771 is empty, the parameters for the fetch2 call are:
$body: (is empty)
$path:candles/trade:{timeframe}:{symbol}/hist
$params (print_r): Array\n(\n    [symbol] => tBTCUSD\n    [timeframe] => 1m\n)\n
Would it be possible to have some kind of handling there for empty responses?

@ralondo hi! Thanks for reporting! I'll take a look into it. In the meantime, can you show your code, please? These symptoms may indicate that you are hitting their rate limit... Do you actually throttle your requests?

What code do you need? How can I check with ccxt if I hit the rate limit? Anyway, I do throttle my requests by having my own scheduler, in average only one call every 12 seconds to bitfinex. According to their API-docs the the rate limit on the REST-API is 10-90 calls per minute, so I could make at least 1 call every 6 seconds.
The warning doesn't always come, only every few minutes. I lowered my rate now a little bit to a max. of one call every 14 seconds. Maybe it will help.

@ralondo ok, no need for the code... Unfortunately, they state it clear, v2 is beta. We will add more checks to handle for empty responses. Thx!

No problem. I just changed the code for me a bit to get rid of those annoying warnings:
       if (!is_array($response)) {         	logtext($response." BODY:".$body." PATH:".$path." PARAMS:".print_r($params,true));         	$response = array(); 				} else { 	        if (array_key_exists ('message', $response)) { 	            if (mb_strpos ($response['message'], 'not enough exchange balance') !== false) 	                throw new InsufficientFunds ($this->id . ' ' . $this->json ($response)); 	            throw new ExchangeError ($this->id . ' ' . $this->json ($response)); 	        } 				}
I just don't have to forget to reinsert this code after upgrading ccxt ;)

With examples/php/bitfinex2-fetch-ohlcv.php I'm also having some errors from Bitfinex v2:
2017-10-25T14:32:00.000+00:00	120
2017-10-25T14:32:00.000+00:00	120
2017-10-25T14:33:00.000+00:00	120
PHP Fatal error:  Uncaught exception 'ccxt\RequestTimeout' with message 'bitfinex2 GET https://api.bitfinex.com/v2/candles/trade:1m:tBTCUSD/hist 28 Operation timed out after 10000 milliseconds with 0 bytes received' in /Users/igorkroitor/ccxt/build/ccxt.php:629
Stack trace:
#0 /Users/igorkroitor/ccxt/build/ccxt.php(765): ccxt\Exchange->raise_error('RequestTimeout', 'https://api.bit...', 'GET', 28, 'Operation timed...')
#1 /Users/igorkroitor/ccxt/build/ccxt.php(650): ccxt\Exchange->fetch('https://api.bit...', 'GET', NULL, NULL)
#2 /Users/igorkroitor/ccxt/build/ccxt.php(4771): ccxt\Exchange->fetch2('candles/trade:{...', 'public', 'GET', Array, NULL, NULL)
#3 [internal function]: ccxt\bitfinex2->request('candles/trade:{...', 'public', 'GET', Array)
#4 /Users/igorkroitor/ccxt/build/ccxt.php(593): call_user_func(Array, 'candles/trade:{...', 'public', 'GET', Array)
#5 [internal function]: ccxt\Exchange->ccxt\{closure}(Array)
#6 /Users/igorkroitor/ccxt/build/ccxt.php(1327): call_user_func_array(Object(Closure), Array)
#7 /Users/igork in /Users/igorkroitor/ccxt/build/ccxt.php on line 629
mbp:ccxt igorkroitor$

So, yes, I am adding the handling for it now.

This issue was addressed and fixed in 1.9.262. Thx again for your feedback! Really appreciate it!


Add brazilian portuguese translations

Hi, guys.
Sorry for the wait to make this PR, I was very busy during the week.
I want to point that my last commit was a fix to the changes made in the turkish file after committing (idk what happened tbh, sorry about any mess that this may cause).
While translating, I created a function to make "one line texts" (I don't like to scroll horizontally xD). Hope that's OK. Also, during testing, I found three texts without translation available through files, so I changed them. Hope that's OK also.
Last but not least, sorry about the unformatted commits, I totally forgot about git cz (in 12 minutes, because my first commit was using it, smh).

@housseindjirdeh I just committed updating the branch with the last master commit, changing what lex requested and, following your request, adding myself as contributor (to spare another PR). I guess everything is okay now? If not, let me know, please.

Looks all good except for the small merge conflicts. I can try to resolve.


Cropper with preview broke without updates (1.3.0)

Describe the bug
I've been using react-cropper on my website for a few months and it has always worked flawlessly until sometime in the past 20 days when something broke and now the cropper is behaving weirdly (see GIF).
I'm using version 1.3.0 of react-cropper and I've verified that this happens both on Chrome(v.84.0.4147.105) and on Safari(v.13.1.1 )
The issue: A copy of the image always shows in the background that should not be visible, and when the image is scaled it will reposition itself which is not expected.
A person on our team that uses the cropping tool has verified that it worked as expected 21 days ago, but when she opened it today it was broken. We have not done any changes to the code during that time, nor updated any dependencies.
Screenshots

@hronnro Thanks for opening the issue here and providing a detailed description of the issue.
But seems like a issue associated with cropperjs.
I think if you open the issue there then you might be able to find a quicker solution to your problem.
If possible, please try to repro and post a codesandbox of your issue and I'll try to take a look too.

I've figured what caused the bug - this website is running a few different tools along with the cropper tool, and a .css file for one of the tools was updated with
img {
...
}

that updated all img properties globally, which affected the cropper..
Sorry for not digging deeper before reporting, and thanks for your help! 🙏

Thanks for posting the clarification.


Fix issue #2164 Links open with handleWebUrl.

Description (required)
Open links with the in-app tabbed browser, as opposed to launching them in the external browser.

AboutActivity links now open with the in-app tabbed browser.
UploadActivity license and policy links now open with the in-app tabbed browser.

Fixes #2164 Links out of the app should use Utils.handleWebUrl
What changes did you make and why?

Made handleWebURL set flag for CustomTabsIntent : Intent.FLAG_ACTIVITY_CLEAR_TASK.
This is because before, if you opened something with handleWebUrl, then a second call to handleWebUrl, then press back button, it would return you to the activity (web page) from the first handleWebUrl.
Now that its cleared on each browser launch, calling handleWebUrl then back button is guaranteed to return to previous (in-app) activity.

Made helper methods in UploadActivity that setup onClick handlers only when the links (URLSpan) are clicked. This overrides the default Spannable onClick that was launching the external browser from LinkMovementMethod. We now launch the in-app tabbed browser.

Tests performed (required)

Checked that AboutActivity : Privacy Policy, Translate, Credits, and FAQ links open in tabbed browser.
Checked that UploadActivity : License, and Policy links open in tabbed browser.
Checked that top left corner tabbed browser exit button returns to previous activity.
Checked that bottom right back button either returns to previous activity, or if navigated multiple pages within the browser, that the back button returns to previous web page.

Tested betaDebug on Samsung Galaxy Note 8 with API level 26.
Note: Please ensure that you have read CONTRIBUTING.md if this is your first pull request.

Codecov Report

Merging #2220 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #2220      +/-   ##
=========================================
- Coverage    5.88%   5.87%   -0.02%
=========================================
  Files         231     231
  Lines       11601   11621      +20
  Branches     1082    1083       +1
=========================================
  Hits          683     683
- Misses      10860   10880      +20
  Partials       58      58

Impacted Files
Coverage Δ

app/src/main/java/fr/free/nrw/commons/Utils.java
24.39% <0%> (ø)
:arrow_up:

...ava/fr/free/nrw/commons/upload/UploadActivity.java
0% <0%> (ø)
:arrow_up:

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 af291a5...9f5ad63. Read the comment docs.


[Feature Request] Shortcut to open links/pages/tags in a block

Thanks a lot for this. I was really waiting for this plugin in Logseq, and it is working quite well 👍🏻
I was using Roam Research before with roam-toolkit plugin, and the only feature I miss from that one is to be able to open links/pages/tags with a shortcut.
Basically, that plugin adds a "hint" under each link when a block is highlighted so it can be accessed using just the keyboard. Something like this:

Perhaps there are other ways to do it, but that's just an idea.
Thanks in advance!

I just implemented this action in v0.0.2 using VIM-like combo action, Number+[ctrl+enter] to choose which one to go into.
For now the external link is not supported though.

Yes, it is working for me (num + cmd+shift+enter). Thanks a lot!


truffle init doesn't create App folder

thank you for help

As far as I know it won't create App folder like before.
http://truffleframework.com/docs/getting_started/project

It will not by default. The default project now only provides contracts,
migrations and tests.
You can get a default web app though, which does have an app folder, via
truffle init webpack.
On Thu, Mar 16, 2017 at 3:03 AM andre-zh<EMAIL_ADDRESS>wrote:

As far as I know it won't create App folder like before.
http://truffleframework.com/docs/getting_started/project
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ConsenSys/truffle/issues/374#issuecomment-287010426,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFp1RSL3pAGnd2OYKoMWktmptyVHYiLks5rmQjqgaJpZM4MdmYk
.

thank you :)


I can't do ANYTHING in the laucher

Describe the bug
Can't login in or even do anything in the laucher
Steps to Reproduce
1: Download the laucher
2: Run it
Expected behavior
I could do something in the laucher
Additional information and data
.
Operating System
Windows 10
Hydra Version
2.1.7
Before opening this Issue

[X] I have searched the issues of this repository and believe that this is not a duplicate.
[X] I am aware that Hydra team does not offer any support or help regarding the downloaded games.

Be more specific, what is happening in the login? Provide screenshots/videos/logs
What can't you do? What did you try? Did you try any solution that already exists in the closed issues?

I ran the installer of the same version, and it fixed the error.

I ran the installer of the same version, and it fixed the error.

In the last ~40 minutes we were doing maintenance in the server, so your error was because of this. OP's error is something else

I ran the installer of the same version, and it fixed the error.

In the last ~40 minutes we were doing maintenance in the server, so your error was because of this. OP's error is something else

Ah, ok thanks for reply.

to passando por algo parecido nao consigo instalar nem um jogo do launcher e nao sei o porque disso

@Rotivzera did you add your download sources to have available downloads?

This is happening to me on 3.0.7:


Update dependencies

This updates the dependencies in cabal.project and stack.yaml, and brings those two files in line with each other. I also verified for each of these changes that they were indeed an update (and not a downgrade).
                | update? | cabal.project     | stack.yaml
dependency      |         | before   after    | before   after
--------------------------|---------------------------------------
cardano-base    | yes     | 2f33cbf9 b6761609 | b6761609 --------
  binary        |         |                   |
  binary/test   |         |  (new)            |  (new)
cardano-ledger  | yes     | 595cfb5b 68419565 | 20afe954 68419565
  ./            |         |                   |
  crypto/       |         |                   |
  test          |         |  (new)            |  (new)
  crypto/test   |         |  (new)            |  (new)
cardano-prelude | yes     | e1fb84b1 a136c424 | a136c424 --------
  ./            |         |                   |
  test/         |         |  (new)            |
cardano-shell   | yes     | -------- 5db8e79d | acf5b26f 5db8e79d
cardano-sl-x509 | n/a     | -------- e8bfc129 | e8bfc129 --------
bimap           | n/a     | -------- 997fbb38 | 997fbb38 --------

Draft PR because stack is still building :)
These updates are necessary for the integration work.

I have test it with Stack, and it works :+1:
I did not check the byron-proxy.

Verified that the byron proxy works on nix, and the top-level stack file can also build it.


Force a resync if too many Syncer failures

After discussing #343 with @robbrockbank, we think we should be more defensive and break out of the watch loop if we hit too many failures.

@fasaxc could you provide a bit more information for this? What is it trying to solve? What sorts of failures does this cover?

Work in progress on this PR but I haven't had time to finish off the UTs: https://github.com/projectcalico/libcalico-go/pull/380


Unable to load .riv files with Rollup

Are there any examples of using Rive with Rollup?
I am trying to use Rive with React (Vite) and Svelte. Both use rollup to bundle, and are showing similar errors that prevent .riv files from loading.
Here is a sandbox for Svelte. If you open the app in New Window and inspect the dev tools, it fails with Cannot read property 'getContext' of null. When running a Vite app, it fails with ReferenceError: color is not defined. Both errors are coming from rive.js (v0.0.4).

I went ahead and created an additional sandbox for Vite. As mentioned in my first comment, if you open the app in New Window and inspect dev tools, you will see ReferenceError: color is not defined.

We've not used this with Rollup; we use Webpack which should be working fine.
We'll take a look at Rollup and see what might be happening.

We've heavily refactored how the package is being packed; once this is close to being released, we'll test it with Rollup to see if it's helped the problem.

Looks like the new packing is working; I forked your sandbox and updated to the new API:
https://codesandbox.io/s/svelte-rive-test-forked-kx23t?file=/public/index.html

This might not be the best way though; there's now also rive.dev.js, which is ES6 friendly and designed to be imported through npm for use in React, Next, etc.
Let me know how you get on with 0.1.0 beta.

Appreciate the update. Do you mind clarifying on "might not be the best way"? Not sure how I should go about adding the new API to my project.

@mjohnsullivan I went ahead and tried 0.1.0 beta (imported from unpkg) in a local Svelte app and it fails with: wasm streaming compile failed: LinkError: WebAssembly.instantiate(): table import 40 is smaller than initial 900, got 773.
Feel free to close this issue as you see fit. I plan to experiment with the web API once it reaches a stable version. I'm sure most of the problems I am having will be resolved by then, so not sure if this issue is worth keeping open with the API being in constant flux. Thanks again for the help.

There's a problem with the older packages that always pulled the latest wasm instead of the compatible one.
For v6 files, please use v0.6.1, which should do the right thing.
For v7, please use the latest build (currently v0.7.2).

And this was a very useful issue to highlight some of the issues folk are having; thanks for doing this.

The 0.7.2 release just yesterday fixed this issue for me! Big thanks, works well now with Svelte / Rollup, although it was a bit tricky. Happy to share some example code if it would be helpful

Excellent! If you could share some example code, that'd be great. We're in the process of changing up our pipeline for building the package to make it easier to use in web frameworks and I'd love see what hoops you had to jump through so we can try and improve matters.


Missing bundler-audit reference in Gemfile [v1.54.0]

Good day and howdy!
I'm unable to create new apps using 1.54.0, and it seems it's because of the bundler-audit entry in the Gemfile. Running suspenders app goes as expected up until the advisories generator triggers a bundle install. At the point an error occurs because bundler-audit can't be found using the specified references. It looks like a few subsequent generators are attempted, but they complain about the missing bundler-audit and don't seem to accomplish their objectives. I took a shot and modified the Gemfile, and was able to bundle install successfully. Unfortunately, running bin/setup fails with a syntax error, and the server fails to start because webpacker is missing.
The problem disappears when I build/install Suspenders locally using commit ecd95f6, which I assume is because #1042 is included atop the changes in 1.54.0. Doing that (or hopping back to 1.53.0) works fine for me, but I'd like to be sure that I'm not missing something that would make it unnecessary.
Here's what happens when the advisories generator is run:
generate  suspenders:advisories
       rails  generate suspenders:advisories
W, [2020-06-30T16:14:19.997456 #64556]  WARN -- Skylight: [SKYLIGHT] [4.3.1] Running Skylight in development mode. No data will be reported until you deploy your app.
(To disable this message for all local apps, run `skylight disable_dev_warning`.)
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
     gemfile  https://github.com/rubysec/bundler-audit.git
[DEPRECATED] `Bundler.with_clean_env` has been deprecated in favor of `Bundler.with_unbundled_env`. If you instead want the environment before bundler was originally loaded, use `Bundler.with_original_env` (called at /Users/you/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/gems/suspenders-1.54.0/lib/suspenders/generators/advisories_generator.rb:11)
         run  bundle install from "."
Fetching https://github.com/rubysec/bundler-audit.git
fatal: Needed a single revision
Git error: command `git rev-parse --verify 0.7.0` in directory /Users/you/rails_apps/app has failed.
Revision 0.7.0 does not exist in the repository https://github.com/rubysec/bundler-audit.git. Maybe you misspelled it?

And then the remaining output until the new app creation process ends:
create  lib/tasks/bundler_audit.rake
      append  Rakefile
    generate  suspenders:runner
       rails  generate suspenders:runner
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application
    generate  suspenders:preloader
       rails  generate suspenders:preloader
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application
    generate  suspenders:staging:pull_requests
       rails  generate suspenders:staging:pull_requests
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application
    generate  suspenders:production:single_redirect
       rails  generate suspenders:production:single_redirect
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application
    generate  suspenders:production:compression
       rails  generate suspenders:production:compression
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application
    generate  suspenders:production:force_tls
       rails  generate suspenders:production:force_tls
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application
    generate  suspenders:production:email
       rails  generate suspenders:production:email
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application
    generate  suspenders:production:timeout
       rails  generate suspenders:production:timeout
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application
    generate  suspenders:production:deployment
       rails  generate suspenders:production:deployment
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application
    generate  suspenders:production:manifest
       rails  generate suspenders:production:manifest
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application
Congratulations! You just pulled our suspenders.
Run 'bundle exec honeybadger heroku install' with your API key.
         run  bundle install
Fetching https://github.com/rubysec/bundler-audit.git
fatal: Needed a single revision
Git error: command `git rev-parse --verify 0.7.0` in directory /Users/you/rails_apps/app has failed.
Revision 0.7.0 does not exist in the repository https://github.com/rubysec/bundler-audit.git. Maybe you misspelled it?
If this error persists you could try removing the cache directory
'/Users/you/.rbenv/versions/2.6.6/lib/ruby/gems/2.6.0/cache/bundler/git/bundler-audit-93551729fd6da9275b2d8fb48dbea6638e9e07ea'
         run  bundle binstubs bundler
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your
application
         run  bundle exec spring binstub --all
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application
       rails  webpacker:install
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application
    generate  suspenders:views
       rails  generate suspenders:views
The git source https://github.com/rubysec/bundler-audit.git is not yet checked out. Please run `bundle install` before trying to start your application

The bin/setup failure:
$ ./bin/setup
The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mingw32, x64-mingw32, x86-mswin32, java. To add those platforms to the bundle, run `bundle lock --add-platform x86-mingw32 x64-mingw32 x86-mswin32 java`.
The Gemfile's dependencies are satisfied
yarn install v1.22.4
[1/4] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 0.06s.
W, [2020-06-30T16:15:50.406704 #64922]  WARN -- Skylight: [SKYLIGHT] [4.3.1] Running Skylight in development mode. No data will be reported until you deploy your app.
(To disable this message for all local apps, run `skylight disable_dev_warning`.)
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Database 'app_development' already exists
Database 'app_test' already exists
./bin/setup: line 28: syntax error near unexpected token `fi'

Thanks for the report. This was fixed in https://github.com/thoughtbot/suspenders/commit/d6b0a3c04448a0849a29a48c00944467b6b84bfe. I will go ahead and release v1.54.1 now.


feat(eslint-plugin): Add calls support for order

Extend the eslint’s order rule to support call expressions, and apply it to clsx.

Can you add some tests? Thanks

@antfu I looked into adding tests, but I can’t seem to find where the tests for the eslint plugin reside. There is test/sort-rules.test.ts, which tests the core rather than the eslint plugin.
I will be happy to look into adding a test suit for the plugin, but just making sure I’m not missing anything...

We do have a simple fixture. But yeah it's missing the automation. Would be great if you can help improving that.

I did this https://github.com/antfu/eslint-config/blob/main/test/fixtures.test.ts, for your reference


Add UUID to messages

I think messages need an ID - otherwise an agent can receive a ResponseMessage but not know what message is being responded to.

This would also mean an agent would have to keep track of what messages they have sent

Can't we just have a pointer to the original message contained in the reply


Clarity on Prerequisites

In the below statement you are excluding M365 Enterprise plans? Does this mean it is not supported?
"User has an Office 365 E1, E3, E5, A1, A3, A5, M365 Business, Business Premium or Business Essentials"

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

ID: 976b8a9b-5a3e-1f3b-b848-d1dfbfd3389d
Version Independent ID: 2b13a471-3baf-0086-439a-f94abb162fd6
Content: Teams cloud meeting recording - Microsoft Teams
Content Source: Teams/cloud-recording.md
Service: msteams
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

@Gweffs Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Greetings,
Is there a option to make setting as below?
"If anybody of the meeting participant/Organizer starts the meeting recording, it should disable to other participants."

@Gweffs thank you for reaching out and helping improve MS Docs.  Anything that is not directly mentioned in the article is usually not supported.  Let me double check with the team and get back to you soonest.

Hi @scanum
This can be closed now. Thank you!

@Gweffs Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


earlier is the wrong count

I know its an old repo but the counts are off sometimes. An example is:
[src/main.rs:138] wordsworth::syllable_counter("earlier") = 4
https://www.howmanysyllables.com/words/earlier claims its 3.
I have not looked in to why or for a larger list. Hopeful it is obvious to you what the issue is.
thanks!
using wordsworth = "*" if it matters.

I found this page had a file of words in the source code
http://www.delphiforfun.org/programs/Syllables.htm
rust didnt like the dot so i replaced it with a |.  using the code below there was 7800 mismatches out of the 42443 words in the file.
    let mut string = fs::read_to_string("/home/becker/trash/corpus/Syllables.txt").unwrap();
    for line in string.lines() {
        let mut s = line.splitn(2, "=");
        let word = s.nth(0).unwrap();
        let count = s.nth(0).unwrap().split("|").count();
        let s = wordsworth::syllable_counter(&word);
        if count != s as usize {
            println!("{} file:{} function:{}", word, count, s);
        }
    }


Add Blazor keyboard composition events to what's new

See https://github.com/dotnet/AspNetCore.Docs/issues/32042#issuecomment-2040200923

Internal previews

📄 File
🔗 Preview link

aspnetcore/release-notes/aspnetcore-9.0.md
What's new in ASP.NET Core 9.0

BTW @tdykstra ... Dan would sort of like these to go live around the time of the release. Was this for Pre3? ... and sorry if I missed it ... my head has been down blasting through non-.NET 8 backlogged issues lately. I do need to catch up with the PU on anything missed for Pre3 (not much I think) and for Pre4 upcoming.

Nevermind!!! Yes, Pre3 ... I see it. OK ... all good. Thanks again!


Investigate automatic language detection for Compiler selection

We could do this in a fairly straightforward way

[ ] Implement python scikit-learn feature extraction vector
[ ] Create large set of random circuits in various languages
[ ] Train feature extraction on that set
[ ] Integrate with xacc::Program.build() and friends

This issue was moved to eclipse/xacc#12


[Enhancement] add authentication for master admin api

Currently, the config of the fuse_client has the master address, and some body can send http requests to the master through this address, including deleting mp/dp whitout permission control.
We should add more permission control to the following http requests which can manage cluster:
//Master API cluster management
proto.AdminClusterFreeze
proto.AddRaftNode
proto.RemoveRaftNode
proto.AdminSetNodeInfo
proto.AdminSetNodeRdOnly
// Master API volume management
proto.AdminCreateVol
proto.AdminDeleteVol
proto.AdminUpdateVol
proto.AdminVolShrink
proto.AdminVolExpand
// Master API meta partition management
proto.AdminLoadMetaPartition
proto.AdminDecommissionMetaPartition
proto.AdminChangeMetaPartitionLeader
proto.AdminCreateMetaPartition
proto.AdminAddMetaReplica
proto.AdminDeleteMetaReplica
proto.QosUpdate
proto.QosUpdateZoneLimit
proto.QosUpdateMasterLimit
proto.QosUpdateClientParam
// Master API data partition management
proto.AdminCreateDataPartition
proto.AdminDataPartitionChangeLeader
proto.AdminLoadDataPartition
proto.AdminDecommissionDataPartition
proto.AdminAddDataReplica
proto.AdminDeleteDataReplica
proto.AdminSetDpRdOnly
// Master API meta node management
proto.AddMetaNode
proto.DecommissionMetaNode
proto.MigrateMetaNode
proto.AdminSetMetaNodeThreshold
proto.AdminUpdateMetaNode
// Master API data node management
proto.AddDataNode
proto.DecommissionDataNode
proto.MigrateDataNode
proto.CancelDecommissionDataNode
proto.DecommissionDisk
proto.AdminUpdateNodeSetCapcity
proto.AdminUpdateNodeSetId
proto.AdminUpdateDomainDataUseRatio
proto.AdminUpdateZoneExcludeRatio
proto.RecommissionDisk
// Master API user management
proto.UserCreate
proto.UserDelete
proto.UserUpdate
proto.UserUpdatePolicy
proto.UserRemovePolicy
proto.UserDeleteVolPolicy
proto.UserTransferVol
// Master API zone management
proto.UpdateZone
Base on the origin auth node framework, the authentication process is represented below.

Codecov Report

Merging #1857 (bdef1a7) into master (e1ac90f) will increase coverage by 0.21%.
The diff coverage is 75.45%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master    #1857      +/-   ##
==========================================
+ Coverage   48.10%   48.32%   +0.21%
==========================================
  Files         455      454       -1
  Lines       78386    79174     +788
==========================================
+ Hits        37707    38257     +550
- Misses      37678    37894     +216
- Partials     3001     3023      +22

Impacted Files
Coverage Δ

blobstore/access/stream_alloc.go
58.82% <0.00%> (ø)

blobstore/api/blobnode/client.go
85.71% <ø> (ø)

blobstore/api/clustermgr/config.go
0.00% <0.00%> (ø)

blobstore/api/clustermgr/disk.go
0.00% <0.00%> (ø)

blobstore/api/clustermgr/kv.go
0.00% <0.00%> (ø)

blobstore/api/clustermgr/proto.go
0.00% <ø> (ø)

blobstore/blobnode/base/qos/qos.go
49.20% <0.00%> (ø)

blobstore/blobnode/base/workutils/stripe_utils.go
85.71% <ø> (-2.39%)
:arrow_down:

blobstore/blobnode/config.go
22.51% <0.00%> (-26.76%)
:arrow_down:

blobstore/blobnode/core/config.go
15.38% <0.00%> (-0.75%)
:arrow_down:

... and 77 more

... and 27 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@M1eyu2018 Does the check is configurable,the online environment may not have the authnode

@M1eyu2018 Does the check is configurable,the online environment may not have the authnode

Yes, config is in master. If authenticate is true,  interceptor which checks authentication will work. @leonrayang

@M1eyu2018 please resolve the conflicts,thank you.

@M1eyu2018 please resolve the conflicts,thank you.

@leonrayang done

@M1eyu2018 please resolve the conflicts

This has been merged 6+ months ago - can we get it into a CubeFS release for usage please? :)


MIMIC-CXR dataset changes

cxr-study-list.csv.gz is either no longer provided by physionet for the mimic dataset or was never uploaded to the repo. References to 'path' are therefore broken.
It seems that other changes or data cataloging specifics are causing issues, however that is out of scope of this issue.
https://github.com/rajpurkarlab/BenchMD/blob/2d1fe92290c65b685ad524b2f3c42306c704e212/src/datasets/chest_xray/mimic_cxr.py#L105C9-L105C102

Note to future users, cxr-study-list.csv.gz is found on physionet for mimic-cxr non compressed dataset


Multiple Example title has been removed in OneHotIoU

Multiple Example title has been removed in OneHotIoU file.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 60.25%. Comparing base (e072189) to head (90720a5).

:exclamation:  There is a different number of reports uploaded between BASE (e072189) and HEAD (90720a5). Click for more details.
HEAD has 6 uploads less than BASE

Flag
BASE (e072189)
HEAD (90720a5)

keras
4
1

keras-torch
1
0

keras-tensorflow
1
0

keras-jax
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #20587       +/-   ##
===========================================
- Coverage   82.37%   60.25%   -22.12%
===========================================
  Files         516      516
  Lines       48436    48436
  Branches     7564     7564
===========================================
- Hits        39898    29187    -10711
- Misses       6711    17475    +10764
+ Partials     1827     1774       -53

Flag
Coverage Δ

keras
60.25% <ø> (-21.96%)
:arrow_down:

keras-jax
?

keras-numpy
60.25% <ø> (-0.01%)
:arrow_down:

keras-tensorflow
?

keras-torch
?

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


We should audit Via HTML cookie handling behavior

There is concern that pywb may leak information from one domain to another.
It's believed that they attempt to get around this by scoping cookies to paths which include the domain. This should cause the browser not to send any cookies for other paths (and so domains).
Questions we'd like answered:

[x] How does Via HTML handle cookies by default? (Split by path)
[x] Can it leak from one site to another? (Based on a reasonable effort at investigation, not a cast iron guarantee) (Not as far as I can tell)
[ ] What is our stance on proxying authenticated content?
[ ] What's the reason for this stance?
[ ] If we are unhappy with it, is there a way of blocking this without disabling non-authenticate sites?

Next steps:

Is the above acceptable? If not what action should be taken?

How does viahtml store cookies?

pywb accesses content on itself on a number of different URLs which sometimes relate to the content type. For example

/proxy/https://example.com
/proxy/if_/https://example.com/sub-page

I've asked a question about the authorized stuff in: https://hypothes-is.slack.com/archives/C4K6M7P5E/p1604327632468500

From that link, as summary of a discussion with @klemay :

It's either no work, or not much work either way
From a product point of view, it's actually a massive plus if our customers can do this, and it's something that's on our road map
Allowing these headers in ViaHTML doesn't guarantee we'll actually deliver this, but it means we aren't taking active steps against it
The remaining spheres to consider are technical (can we do it) and legal/policy (are we allowed to)
On the technical side, we certainly can not block it
As mentioned above, this doesn't ensure people can annotate content behind a login, but it does raise the probability higher than 0%
On the policy / legal side @arti is probably the best person to talk to when she's feeling better
We might want to consult Subgraph
For the purposes of book-keeping and the sprint, this is probably enough of an answer for the spike. If we get back an alternative view from Arti then we can file a ticket to do remedial work.

So for now this is probably enough to allow us to proceed.


[Dashboard] - Remove server-only import on  files

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR primarily removes the import of "server-only" from multiple files across the project, likely to streamline the code or address potential issues related to server-only functionality.
Detailed summary

Removed import "server-only"; from:

apps/dashboard/src/app/login/auth-actions.ts
<EMAIL_ADDRESS>apps/dashboard/src/app/(dashboard)/support/create-ticket/components/create-ticket.action.ts
apps/dashboard/src/app/team/[team_slug]/(team)/~/ecosystem/create/actions/create-ecosystem.ts

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#5551  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


[WIP] Revise early chapters

I'm working on revising some of the earlier chapters for the pdf, to complement #90.
Not ready to merge yet.

@ketch: I shortened some lines by indenting continuations of function call argument lists differently, with less white space before the continued lines so that some calls would fit and/or would fit into fewer lines.  Particularly in Shallow_water and Euler_approximate_solvers.
If this and other changes seem ok, this could be merged.

I'm a very strong believer in lining up continuations of function arguments with the parentheses for the function, and this breaks that.  But I don't know what the optimal solution is, and I suspect we'll revisit this before the book is finished, so I'll go ahead and merge this.


Sublime syntax highlighter available?

I'm finding it difficult to write nocode without highlighting, anybody got any ideas on how to implement this?

Worked for me:

Worked for me:

API changed in v2:

Thanks for you replies, neither seem to work.
I'm getting this error in Sublime's console:

By the way, is that nocode v2 or Sublime v2?
I forgot to mention I'm using Sublime 3.

Please refer to the documentation.
https://github.com/kelseyhightower/nocode/blob/master/README.md


Move updatecertificate js-confirm to a confirm modal.

Search 'confim' to see what is meant here.

Changed mind about this modal. Is needlessly complicated for an MVP. The user is just warned with an sAlert instead.


No module named 'ga_connector_updated'

I download it and try the command rasa run with :
rasa==1.0.1
rasa-core==0.14.4
rasa-core-sdk==0.14.0
rasa-nlu==0.15.0
rasa-sdk==1.0.0
rasa-x==0.19.0

Exception: Failed to find input channel class for 'ga_connector_updated.GoogleConnector'. Unknown input channel. Check your credentials configuration to make sure the mentioned channel is not misspelled. If you are creating your own channel, make sure it is a proper name of a class in a module.

Add the path where the ga_connector_updated project exists by
Windows:
set PYTHONPATH=%PYTHONPATH%;C:/pathtoyourproject;
Linux:
export PYTHONPATH=~/pathtoyourproject/:$PYTHONPATH


Fix Bosh contributor agreement links.

The PDF's linked from the Bosh contributing document are broken. The
helpful bot that tells you to sign a contribution agreement linked me to
these correct versions.

The corporate CLA has now been correctly filed. Can this pull request be considered now?


fix documentation

Description
This PR fixes two issues in Liqo documentation:

default k3s CIDR was wrong
there was a typo in a namespace

/rebase

/rebase

/rebase


fix: validate every item of QuerySpec filterExpression

What this PR changes/adds
Validate all the Criterion.filterExpression items instead of the first one only.
Why it does that
fix bug
Further notes

improved the Criterion validation itself, the "rightOperand" must be considered mandatory as in the EDC there are no operators that permit an empty rightOperand
some documentation added

Linked Issue(s)
Closes #3424
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

Codecov Report
Patch coverage: 87.50% and project coverage change: +0.01% :tada:

Comparison is base (f981237) 72.09% compared to head (958dee7) 72.11%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3467      +/-   ##
==========================================
+ Coverage   72.09%   72.11%   +0.01%
==========================================
  Files         836      836
  Lines       16985    16987       +2
  Branches      947      947
==========================================
+ Hits        12246    12250       +4
+ Misses       4335     4333       -2
  Partials      404      404

Files Changed
Coverage Δ

...alidator/jsonobject/validators/MandatoryValue.java
90.00% <0.00%> (-10.00%)
:arrow_down:

.../edc/validator/jsonobject/JsonObjectValidator.java
100.00% <100.00%> (ø)

...sonobject/validators/model/CriterionValidator.java
88.88% <100.00%> (+0.65%)
:arrow_up:

...sonobject/validators/model/QuerySpecValidator.java
92.85% <100.00%> (ø)

... and 2 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


DNS_PROBE_FINISHED_NXDOMAIN issue

Before opening, please confirm:

[X] I have checked the custom domains troubleshooting guide.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d3f9mt4lztg5ah
Region
eu-west-1
Step
Domain Activation
Status
Success
Issue or question
After the domain activation succeed, impossible to access to the website, the following error is shown:
DNS_PROBE_FINISHED_NXDOMAIN
Error message
DNS_PROBE_FINISHED_NXDOMAIN
Additional information
No response

Hi @anaji 👋 , thank you for reaching out to us and we apologize for the delayed response on the thread.
I observed that your Amplify app d3f9mt4lztg5ah has a custom domain (orbiticons.com) associated to it. Additionally, the custom domain has been successfully activated and it seems to be resolving as expected.
That being said, if the issue resurfaces I would highly recommend reviewing this article which outlines some potential root causes of the DNS_PROBE_FINISHED_NXDOMAIN error.
I am going to close this thread since the issue seems to have been resolved but please feel free to open a new GitHub issue if you are experiencing issues with Amplify Hosting.


How can create off canvas with RTL layout

I find this snippet for create off canvas menu but in layout-direction: RTL it's not right please checkout this codepen
tanx

Closing for now. If it is an issue you still find present in recent versions, please make a new issue!


Missing notification_priority  in Go SDK

Environment Details

Operating System version: WIndows 10
Firebase SDK version: 3.10.0
Firebase Product: Firebase Cloud Messaging

As Per firebase document, we can set the parameter notification_priority to determine message priority.
https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages#androidnotification
{
    "title": string,
    "body": string,
    "icon": string,
    "color": string,
    "sound": string,
    "tag": string,
    "click_action": string,
    "body_loc_key": string,
    "body_loc_args": [
      string
    ],
    "title_loc_key": string,
    "title_loc_args": [
      string
    ],
    "channel_id": string,
    "ticker": string,
    "sticky": boolean,
    "event_time": string,
    "local_only": boolean,
    "notification_priority": enum (NotificationPriority),

I am trying to use firebase admin go client but when I see the message struct, I cannot see that element
Struct Defined is as follows:
https://godoc.org/firebase.google.com/go/messaging#AndroidNotification
type AndroidNotification struct {
     Title        string   `json:"title,omitempty"` // if specified, overrides the Title field of the Notification type
     Body         string   `json:"body,omitempty"`  // if specified, overrides the Body field of the Notification type
     Icon         string   `json:"icon,omitempty"`
     Color        string   `json:"color,omitempty"` // notification color in #RRGGBB format
     Sound        string   `json:"sound,omitempty"`
     Tag          string   `json:"tag,omitempty"`
     ClickAction  string   `json:"click_action,omitempty"`
     BodyLocKey   string   `json:"body_loc_key,omitempty"`
     BodyLocArgs  []string `json:"body_loc_args,omitempty"`
     TitleLocKey  string   `json:"title_loc_key,omitempty"`
     TitleLocArgs []string `json:"title_loc_args,omitempty"`
     ChannelID    string   `json:"channel_id,omitempty"`
     ImageURL     string   `json:"image,omitempty"`
 }

Is there any discrepancy in firebase documentation and struct or am I missing something?
Issue is, message are delivered to device but no sound or on screen display if device is sleeping. ( Happening on one plus 7 pro, only sometimes)
I checked the events using following commands
   1.  Dial *#*#426#*#* to open the FCM Diagnostics page.
   2.  Tap the EVENTS button to show the event log.
   3.  Check whether the message was delivered to the device. There should be a log entry reading

and saw that youtube message are coming with HIGH priority and priority of my messages is shown as UNKNOWN.
How I can send message with high priority as described in documentation?

Please let me now in case extra information is needed

Hi, for now it's not supported by go SDK, there is an open Feature request #273

Thanks @chemidy , is there any timeline by when this feature will be available?

I started working on it :)   hope to have some time this weekend to finish


[Bug]: v2.2.9 breaks NextJS apps

Current Behavior
The const APP_INITIAL_STATE' is accessing the window` object before it being initialized in a NextJS app and so it throws.
Expected Behavior
The const APP_INITIAL_STATE could have this code instead
wallets: [],     walletModules: [],     chains: [],     accountCenter: {         enabled: true,         position: 'topRight',         expanded: false,         minimal: typeof window != 'undefined' && getDevice().type === 'mobile'     },     locale: ''
Steps To Reproduce
No response
Onboard Version
2.2.9
Node Version
next^12.1.6
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Anything else?
No response

This has been previously covered at https://github.com/blocknative/web3-onboard/pull/931, but I'm facing the same issue too. You can't just import the module and run it on a Next.js context.
The line causing the issue:
https://github.com/blocknative/web3-onboard/blob/09df2e1a8ddeb5100566db78f57b1b88bf406cd5/packages/core/src/utils.ts#L29

@aaronbarnardsound @taylorjdawson any update? This is a breaking change for me, so pls this needs to be resolved.

Will be taking a look at this today :)


Non-generic signal Declare method.

Right now it's only possible to declare signals using following syntax:
Container.DeclareSignal<TSignal>(), however we prefer being less explicit in this case and we implemented registration by convention. To do that we added new variant of DeclareSignal method that accepts Type argument instead of generic parameter.

Thanks.  Merged into https://github.com/svermeulen/Extenject with 7afd3cbf


[Core][Distributed] enable multiple tp group

Improve the code to support multiple groups. An ongoing effort to support pipeline parallel https://github.com/vllm-project/vllm/pull/4412 in the end.
cc @simon-mo when we have 4 GPU CI machines ready, tests in this PR can be merged. I tested it locally, and it works.

adding...

ok node is up, try setting num_gpus to 4 in the pipeline yaml?

ok node is up, try setting num_gpus to 4 in the pipeline yaml?

Only run this test in 4 gpu machine, or run all distributed tests in 4 gpu machine?

@simon-mo is 4 gpu machine up? The test cannot start.

TODO: we can also use 4 GPU node to test pipeline parallel and multi-node setup, by using two docker containers with 2 GPUs each.


weex 插件市场链接失效

weex官网下的插件市场链接失效，希望官网解决一下

The Weex Market will be rebuilt on next month, it will be reopened after we finish our work.


Compile error

OS: Macos
Arch: arm64(Darwin)
Steps to reproduce:

Clone zld
With the latest binary (dev.1836+28364166e)

zig_repo/zig build
/_path_/zld/build.zig:27:8: error: no field or member function named 'addPackagePath' in 'Build.CompileStep'
    lib.addPackagePath("dis_x86_64", "zig-dis-x86_64/src/dis_x86_64.zig");
    ~~~^~~~~~~~~~~~~~~
/path_to_zig_repo/lib/std/Build/CompileStep.zig:1:1: note: struct declared here
const builtin = @import("builtin");

Earlier binaries produce other compile errors.

Apparently this issue is caused by zld not implementing updated breaking zig API:
https://github.com/ziglang/zig/pull/14498


ImportError: No module named opendbc

This is what I've got by running /.run_docker_test.sh, seems like the PYTHONPATH was not set right?
Successfully built b4ab4237c798
Successfully tagged tmppilot:latest
Traceback (most recent call last):
  File "./test_longitudinal.py", line 14, in <module>
    from selfdrive.test.plant.maneuver import Maneuver
  File "/tmp/openpilot/selfdrive/test/plant/maneuver.py", line 4, in <module>
    from plant import Plant
  File "/tmp/openpilot/selfdrive/test/plant/plant.py", line 8, in <module>
    from opendbc import DBC_PATH
ImportError: No module named opendbc

Run git submodule update --init --recursive, I hear they moving to git subtrees on next release.

@energee  Thanks! It works!


First stab at changes to add lnaddress

Signed-off-by: Brian of London (Dot<EMAIL_ADDRESS>I moved the Lightning block info out of the main Value.md because they're separate. Lightning is A value block system not THE value block system.
This is a follow up to pull request  #384 about lnurl.

lnaddress should take priority if exists
The well-known/keysend should refer to the Lightning Address spec. One thing that is missing here is routing hints support.

lnaddress should take priority if exists

Ok.

The well-known/keysend should refer to the Lightning Address spec. One thing that is missing here is routing hints support.

I seem to remember route hints being in the spec but can't find any reference to them in the current version. I don't think I've ever seen them in the wild and I must admit that my Node had some unadvertised channels but I stopped using those a while back.

I just added the details for a bare endpoint response to signify a server which is acting as a lookup for Keysend.

This looks great!
Should we also have a custom error returned when the Lightning address does not exist, but the provider still supports keysend? This would eliminate the need of making an additional request to https://example.com/.well-known/keysend.
@MerryOscar suggested having something like "status" = "UNKNOWN". Here's the relevant discussion on podcastindex.social: https://podcastindex.social/@dovydas/109746270989356454
Personally, I think HTTP status 404 with JSON field "tag" = "keysend" would be sufficient.

This looks great!
Should we also have a custom error returned when the Lightning address does not exist, but the provider still supports keysend? This would eliminate the need of making an additional request to https://example.com/.well-known/keysend.
@MerryOscar suggested having something like "status" = "UNKNOWN". Here's the relevant discussion on podcastindex.social: https://podcastindex.social/@dovydas/109746270989356454
Personally, I think HTTP status 404 with JSON field "tag" = "keysend" would be sufficient.

I actually send out a 422 if the name isn't a valid Hive account name.
I do not, however, check if the account has been created on Hive (that's a somewhat slow lookup)
You can see this here:
https://api.v4v.app/.well-known/keysend/122345

I'm just thinking how to make the spec precise, yet not too difficult to implement. @brianoflondon, summarizing what you wrote and adding some more info, would the following work?

Providers (say, example.com) supporting .well-known/keysend lookup scheme should implement the following:
GET https://example.com/.well-known/keysend
GET request to https://example.com/.well-known/keysend should return HTTP status code 200 and a JSON with at least the following fields

status (required): "OK"
message (required): string describing what information is returned through this lookup scheme

GET https://example.com/.well-known/keysend/{lightningUsername}
GET request to https://example.com/.well-known/keysend/{lightningUsername} should return the following based on the value of {lightningUsername}:

If Ligthning address<EMAIL_ADDRESS>exists, HTTP status code 200 and a JSON with at least the following fields should be returned:

status (required): "OK"
tag (required): "keysend"
pubkey (required): string representing destination node's public key
customData (optional): array of CustomData, which has fields

customKey (required): number
customValue (required): string

Optionally, if the syntax for the Lightning address at example.com does not allow username {lightningUsername}, HTTP status code 422 and a JSON with at least the following fields should be returned:

status (required): "UNPROCESSABLE_ENTITY"
tag (required): "keysend"
message (optional): string describing why the username is invalid

In any other case, HTTP status code 404 and a JSON with at least the following fields should be returned:

status (required): "NOT_FOUND"
tag (required): "keysend"

A few other comments:

Is the JSON field status really necessary? Does it indicate any extra information that HTTP status code doesn't already provide?
Could the message in JSON returned from https://example.com/.well-known/keysend be optional instead? For most services, it's pretty straightforward—they host Lightning wallets and return their details. It's only in special cases like that of v4v.app where the mechanism is different.

The status and message field comes from FastAPI which is what I'm using, that's it's default behaviour for 422 and this happens outside of any code I write.
I'll try to take your suggestion and put it in this proposal soon.

Got it! Well, then maybe this could be simplified by simply having a 404 with an optional message, which might say something like "the string does not match regex xyz"?

Got it! Well, then maybe this could be simplified by simply having a 404 with an optional message, which might say something like "the string does not match regex xyz"?

That's a part of FastAPI which I'm sure could be altered but I'm not going to try :-) The way FastAPI generates the docs and handles all the input sanitization is somewhere close to miraculous to my eyes!

I don't think I've ever seen them in the wild

Are you talking about something like this @brianoflondon ?
https://api.fountain.fm/v1/lnurlp/dave/keysend

I don't think I've ever seen them in the wild

Are you talking about something like this @brianoflondon ?
https://api.fountain.fm/v1/lnurlp/dave/keysend

This is what I meant: I've never seen anyone put routing hints in a value block. I can't find any explanation of what these look like in the current spec though I seem to remember they were once in the spec.

The well-known/keysend should refer to the Lightning Address spec. One thing that is missing here is routing hints support.

The routing hints are the customKey/customValue properties.

The routing hints are the customKey/customValue properties.

Maybe that's what you meant in the spec but "routing hints" has a special meaning in Bolt 11 Invoices and concerns nodes connected to the rest of the network by purely private or un-announced channels.
When I started up my V4VApp Voltage node I used private channels and soon realised that in order for funds to get to me the invoices my node generated were huge and the QR codes very detailed. That was because, if you decoded them, you got a list of public node addresses for nodes that I had private channels to. Those were the route hints.
The simple reality is that using a node only connected by these private channels for receiving keysend is not very practical.
Also Keysend payments would only come in on public channels.
https://docs.lightning.engineering/the-lightning-network/payment-lifecycle/understanding-lightning-invoices
r (3): One or more entries containing extra routing information for a private route.
These routing hints include a

pubkey (264 bits)
short_channel_id (64 bits)
fee_base_msat (32 bits, big-endian)
fee_proportional_millionths (32 bits, big-endian)
cltv_expiry_delta (16 bits, big-endian)

I agree with Brian. Name needs to be different from routingHints. Can be almost anything but that to avoid confusion

I think the current version assumes that the domain name and web server will be accessible. What happens if one or both of those are temporarily or permanently inaccessible/unresolvable? Should it hard fail the split as if the server returned a 404/NOT_FOUND? Should it have a "temporarily inaccessible - retry later" mode?
How should applications handle lnaddress lookup failures? Should unresolvable splits be skipped over or should the entire payment fail with a message to the user?

How should applications handle lnaddress lookup failures? Should unresolvable splits be skipped over or should the entire payment fail with a message to the user?

Splits fail, clients just need to handle this regardless of the reason.
Usually apps just fail a specific split.


Message retry performance implications and architectural issues

This is an issue to discuss the current state of the retry logic for syslog messages,
As there are some implications, that are problematic.
just listed here shortly for an overview:

having a syslog drain fail with high load will drop messages for other drains.
This will also put the cpu consumption of the syslog agent over 1 cpu, not sure why
the syslog-batching implementation is not able to use the retry mechanic, as there is no state about the batching being done in the retry writer.

I will add details and my testing results here later in a better formatted way.

I dived a little deeper into the syslog writer code recently and I think that we were incorrect in some of our previous assertions about the synchronized nature of the agent. If you check out the syslog connector, which the manager uses to create new drains, each drain is provided with an egress diode. Since writing to the diode should be non-blocking, I think that the envelope writing loop is in fact asynchronous to some degree.
At least, a problematic syslog drain shouldn't directly prevent other drains from continuing to receive messages.

High CPU usage of the agent is a known problem. Unfortunately, none of the logging and metrics agents currently have any kind of memory or CPU limitation placed upon them. They will expand as necessary to meet demand.
We took a pprof dump a while ago and saw that marshalling/unmarshalling envelopes was a primary performance limitation of most of our agents. Part of what I hope to accomplish by merging every agent into the OTel collector is to reduce the number of marshal/unmarshal steps required to egress an individual envelope from a VM.

I did some testing as well, and your assumption about every drain getting its own diode is also my understanding why there is some sort of concurrency happening.
Imho, this is also unwanted behaviour, as this does not allow to set the wanted max resource consumption, so the syslog-agent is able to overload other components.

At least, a problematic syslog drain shouldn't directly prevent other drains from continuing to receive messages.
Yes, this is what I see with testing.
It only allows a "dos" overload, where the dropped messages on the other non malicious receiver seem to be random.

(the image shows the inflowing data on the receiving side, should be 50log/s)

@nicklas-dohrn to confirm the state of this issue, the current concerns are:

Syslog Agent has the potential for high CPU usage under load that has the potential to overload other components.
https-batch drains in Syslog Agent has no retry logic when it fails and does not propagate any error log message.

Is that correct? If so, I'd move to ignore the first concern in this issue as I consider it to be a general known issue with CF-D components – what we really want is some BPM-specific way to indicate CPU shares.

Syslog Agent has the potential for high CPU usage under load that has the potential to overload other components.
your assumption is correct, that this the expected behaviour for the loggregator agent as I see it as well.
2)https-batch drains in Syslog Agent has no retry logic when it fails and does not propagate any error log message.
This behaviour was observed with the normal http enpoint, I was not making use of the https_batch implementation to make sure this is indeed a problem I did not introduce.
To me, it looked like the uptake of new messages was disrupted if the agent was overloaded, not the sending side.


getting error while running tests

running the tests cause some errors like below:
import near_api
File "near-api-py/near_api/__init__.py", line 6, in <module>
   import near_api.account
File "near-api-py/near_api/account.py", line 21, in <module>
   class Account(object):
File "near-api-py/near_api/account.py", line 36, in Account
    def _sign_and_submit_tx(self, receiver_id: str, actions: list['transactions.Action']) -> dict:
TypeError: 'type' object is not subscriptable

how can I solve this issue ? I did everything provided in the doc

Can you provide more details? I cannot reproduce the issue:

I think it's got something to do with the version I'm using. I'm using python3.8 and it seems in python3.8 you can not define methods like this :
def _sign_and_submit_tx(self, receiver_id: str, actions: list['transactions.Action'])
I changed this to :
def _sign_and_submit_tx(self, receiver_id: str, actions: list) -> dict:
and now everything is working fine. I did not test your code with 3.9 but this is the only thing I can come up with right now.

@iliya-hajjar can you try List['transactions.Action'] with a capital L?


unable to configure the slate set up in windows

i have forked and then used the slate in the windows. have run the commands like bundle install , then bundle exec middleman server
but after navigating to the links provided getting both the issues.

the gemfile and gemlock configurations

kindly guide me through the process, am really working on deadlines

i have edited the source and the index.md file and hosted the GitHub pages but was unable to create the index.html for deploying the pages
kindly guide me through


TR-1 / CT-1

Initial draft PR to add TR-1 / CT-1. Please let me know if the content and/or format is okay, so I can make any changes necessary.

Considering adding some more specific frameworks and/or tooling for this based on https://github.com/finos/ai-readiness/issues/27. What is the general guidance here?

thanks for addressing the review feedback :-)


Update release doc

After prepping the v0.51 release I saw that the release doc was out of date:

references circleci
doesnt have windows release info

Can just make the change on master after the release; I didnt want to mix those changes since they were easily seperable and one was auto generated while the other actual content changes.

https://github.com/vmware-tanzu/sonobuoy/pull/1297


CSS and Javascript appears to be hardcoded to top level path

I'm trying to set up a blog under a sub-folder, and when I generate the layout with Hugo, I see this HTML:
https://github.com/vividvilla/ezhil/blob/74e9ee7758cb3e8a8698c43a043cb0f87b4cbe6b/layouts/partials/header.html#L21-L22
Which leads to a site that looks like:

If I go into dev tools and change it to css/normalize.css and css/main.css (removing the leading /) the site correctly displays the theme.
I think this is also a problem for
https://github.com/vividvilla/ezhil/blob/74e9ee7758cb3e8a8698c43a043cb0f87b4cbe6b/layouts/partials/header.html#L27
and
https://github.com/vividvilla/ezhil/blob/74e9ee7758cb3e8a8698c43a043cb0f87b4cbe6b/layouts/partials/header.html#L29

It looks like (just looking at a different hugo theme), these need to be changed to:
<link rel="stylesheet" href="{{ .Site.BaseURL }}css/normalize.css">
<link rel="stylesheet" href="{{ .Site.BaseURL }}css/main.css">

@vividvilla I could probably submit a PR for this if you're interested?

I would appreciate that :)

Thanks for notifying the issue, its fixed https://github.com/vividvilla/ezhil/commit/411c986a01939b053d386441872528e790eb72f7

It looks like (just looking at a different hugo theme), these need to be changed to:
<link rel="stylesheet" href="{{ .Site.BaseURL }}css/normalize.css">
<link rel="stylesheet" href="{{ .Site.BaseURL }}css/main.css">

etc (for all the hardcoded links)

I understand this was closed but just noting here that the BaseURL has to be appended with a '/'. Site wasn't loading any css for me, that was why.


Start/Stop is now in GA.

[Enter feedback here]
This link says that Start/Stop feature of MySQL is now in GA. This page should reflect the change.
https://azure.microsoft.com/en-in/updates/general-availability-stopstart-functionality-for-azure-database-for-mysql/

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

ID: db4b5208-1b5f-873c-d2ae-91078eb2a58b
Version Independent ID: 18fbf5e4-b528-d96e-b459-8c0ddcafe4c4
Content: Server concepts - Azure Database for MySQL
Content Source: articles/mysql/concepts-servers.md
Service: mysql
GitHub Login: @savjani
Microsoft Alias: pariks

@amneshgoel7 We are closing this as duplicate to https://github.com/MicrosoftDocs/azure-docs/issues/70381


[EUWE] Update the azure-armrest dependency to 0.7.3

This PR upgrades the azure-armrest gem to 0.7.3. The latest version includes some enhancements to the method that gathers private image data which prevents the refresh parser from failing due to sporadic ECONNREFUSED and TimeoutException's.
In conjunction with https://github.com/ManageIQ/manageiq-providers-azure/pull/74, it keeps the branches in sync, too.
Note that I also updated the nokogiri gem dependency. Not only does the azure-armrest gem depend on the newer version, we should update anyway because there was a CVE. See https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md for details.
https://bugzilla.redhat.com/show_bug.cgi?id=1456044

@miq-bot add_label darga/yes

@simaishi Note on the labeling...this is direct to euwe, but also requested for darga.

As long as we can bundle on darga with the newer nokogiri, we should be ok.  They're pretty good at not breaking us.

@jrafanie - Can you approve the upgrade of nokogiri (on Euwe)? Thanks.

@bronaghs @djberg96 While I think it's ok to upgrade nokogiri on euwe, darga would be riskier.  It's unclear why a patch release would require a minor nokogiri upgrade when nokogiri usually backports CVEs to older versions like 1.6.x.  I want my gems on the latest versions of things but we shouldn't force upgrades when they're not required.

'master' branch has nokogiri version set to ~>1.7.1 in manageiq-gems-pending, so we should probably bump that to ~>1.7.2 first. Otherwise Euwe will require later version than master/Fine branches.

@miq-bot remove_label darga/yes

@jrafanie Ok, I've removed the label for darga. @simaishi I'll create a PR to bump the Nokogiri version for master.

@djberg96 I'm going to merge this. When you have a PR to bump Nokogiri for master, please link the PR here.

@simaishi https://github.com/ManageIQ/manageiq-gems-pending/pull/204
Do you want a PR for Fine as well?

@djberg96 thanks - I'll backport the 'master' PR to Fine once merged


Remove bigint

BigInt does not need to be imported to grains.spec.js

Thanks for taking care of this.

No worries!


mvregen not working

MV Core build 688 has broken the /mvregen command.  MV is unable to delete the region folder.  Full error messages: http://pastebin.com/QqudzqQ4
Running:
Multiverse-Core 2.5-b688
Multiverse-Inventories 2.5-b374
Multiverse-NetherPortals 2.5-b682
Multiverse-Portals 2.5-b710
mvregen was apparently broken during an attempt to fix #1392. With build 686 an exception occured, but at least the world was regenerated.  Now the world can't be regenerated at all.

Hey there @Bobcat00, is this still occurring on the latest builds? Sorry for the update nearly 3 years down the line however it's quite a big issue, I'm unable to reproduce this myself but if you could provide logs if it is that'd be great. For now, closed.


feat: add avatarshape component

add avatar shape component

Merged in https://github.com/decentraland/js-sdk-toolchain/pull/181/


run in an existing webserver

Feature request: could it be possible to expose a ring handler as part of the API?
This would allow:

reuse machine port/resources, no need to start httpkit
add authentication etc. in the app before calling the ring handler (my particular target would be ring/yada

Thanks for doing this!

Very good idea, I'll work on that soon.

I moved the final handler to a new var at nightlight.core/app in 52af45837a1b570f31b3848dd938e8fc1f7898aa. I'm not that experienced with ring middleware stuff so please let me know if there is more I can do.


Document how to use lib without validator

Closes #244

Also marked validator as an optional peer dependency in the PR.


Robust Incremental Structure-from-Motion with Hybrid Features

Hi,
Really great work. Am I to understand the plan is to release the code from the ECCV paper as an update to this repo? I’m very interested in trying it out.
If so, when do you expect the code release to roughly be?
Thanks

Hey. Thanks for the question. Yes I can confirm that this is the plan. The rough timeline is to release by the end of this month. And we will make sure that the code is released before the conference (end of September).

Fantastic! Enjoy the conference and congrats

I am looking forward to your work very much

Due to overloaded schedule for my internship and the actively moving target of COLMAP (we plan to support the new code release with the newest COLMAP version), we will have to delay the code release to ensure that it is as good and flexible as possible. Sorry for that and stay tuned for our updates!

Hey thanks for update!
By any chance, have u done ablation studies on synthetic dataset like tartan air using recent approach?
(would have been cool ig)
I used limap 1.0 on a lot of synthetic dataset..but as expected it broke where i expected it to..
Just curious about your opinion.
Thanks again!

@B1ueber2y No worries! Thanks for putting out such great work


Refactor the initial example loading in Playground (#22544)

Resolves #22544
This refactors the initial loading of examples that used to be in playground_page_providers.dart:

Example loading descriptors were introduced. Each descriptor contains all the info to load an example from a given source.
StandardExampleLoadingDescriptor defines loading by an example name.
CatalogDefaultExampleLoadingDescriptor defines loading the default example for a given SDK.
EmptyExampleLoadingDescriptor defines loading empty content while setting a given SDK.
An option to load arbitrary code with code query parameter was removed. It was not allowing to set SDK so it was likely not used in practice. It was only allowed in the embedded version thus introducing unwanted distinctions between the two views. Should we need this option, we must add a loading descriptor class for it.
Example loaders were introduced. Each loader class loads an example from a given source using a particular descriptor class.
PlaygroundState now links to ExampleState. This is because the loading complications were stemming from their separation. The loading code had to await events from both of them. ExampleState is no longer provided in the widget tree, all code consuming ExampleState from the tree was changed to consume PlaygroundState.

As we were completing 'Share any code' feature, this refactoring emerged as a requirement. Without it, adding another source of source code would render the old loading unmaintainable.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @damondouglas


pagination: handle missing paginated responses

In the event a method tries to perform pagination without the ResultInfo present, just return the first page instead of sitting there indefinitely.

Codecov Report

Merging #1327 (8563e89) into master (b9ac804) will increase coverage by 0.08%.
The diff coverage is 56.25%.

@@            Coverage Diff             @@
##           master    #1327      +/-   ##
==========================================
+ Coverage   48.33%   48.42%   +0.08%
==========================================
  Files         133      133
  Lines       13023    13056      +33
==========================================
+ Hits         6295     6322      +27
- Misses       5201     5205       +4
- Partials     1527     1529       +2

Impacted Files
Coverage Δ

logpush.go
51.81% <46.15%> (-0.30%)
:arrow_down:

access_policy.go
70.27% <100.00%> (ø)

pagination.go
100.00% <100.00%> (+28.57%)
:arrow_up:


Can't set margin on calendar container

Due to the way this is implemented, you can't set margins on the container itself.
For example, the library uses DEVICE_WIDTH everywhere. Meaning, we have to override the styles and subtract the margin everywhere that DEVICE_WIDTH is used.

Have you tried the latest release? #106 should address this.

I haven’t. Will do.
Enviado do meu iPhone
Em 12 de out de 2017, à(s) 09:39, coderdave <notifications<EMAIL_ADDRESS>escreveu:
Have you tried the latest release? #106https://github.com/christopherdro/react-native-calendar/pull/106 should address this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/christopherdro/react-native-calendar/issues/127#issuecomment-336120428, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABbjhVDrm3T77DdFunxrD3JEML8pNF_vks5srgiSgaJpZM4NFor0.


Add input validation for component name inputs

What needs to be done?
We need to add input validation for the component name inputs to ensure they satisfy the default format specified in the backstage architectural decisions docs:

Strings of length at least 1, and at most 63 (from testing, it's observed that it should actually be at most 62 chars)
Must consist of sequences of [a-z0-9A-Z] possibly separated by one of [-_.]

For this default format, we will need to add the following pattern validation for the input field:
properties:
  <propertyName>:
    title: Component Name
    type: string
    pattern: "^[a-z0-9A-Z-_.]+$"
    maxLength: 62

The 62 maxLength is because the catalog appears to actually not accept names that are 63 characters long.

Tested with c0mponent-name_1234567890.abcdefghijklmnopqrstuvwxyz-abcdefghi_ which is exactly 63 chars long, but it got rejected.

Tested with c0mponent-name_1234567890.abcdefghijklmnopqrstuvwxyz-abcdefghi, and it was accepted and ingested into the catalog/

This should prevent invalid names from being entered:

Correction: It seems I have misinterpreted the backstage entity name requirements. The [-_.] characters have to be used as separators not as leading or ending characters.
Which is why c0mponent-name_1234567890.abcdefghijklmnopqrstuvwxyz-abcdefghi_ doesn't work. However something like c0mponent-name_1234567890.abcdefghijklmnopqrstuvwxyz-abcdefghij will work.

Update: should be using ^([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]$ instead


Support Xcode 7 beta 6 via Carthage

Crashes at runtime
dyld: lazy symbol binding failed: Symbol not found: _TFSs24withUnsafeMutablePointeru0_rFTRq_FGVSs20UnsafeMutablePointerq__q0__q0
Referenced from: /Users/mdellagi/Library/Developer/CoreSimulator/Devices/5EEB8704-4DA7-4D43-B767-658CDD7C2E33/data/Containers/Bundle/Application/C589F01D-F6DB-4CB1-A69D-A28AA8013FE1/meinmd.app/Frameworks/Locksmith.framework/Locksmith
Expected in: /Users/mdellagi/Library/Developer/CoreSimulator/Devices/5EEB8704-4DA7-4D43-B767-658CDD7C2E33/data/Containers/Bundle/Application/C589F01D-F6DB-4CB1-A69D-A28AA8013FE1/meinmd.app/Frameworks/libswiftCore.dylib
dyld: Symbol not found: _TFSs24withUnsafeMutablePointeru0_rFTRq_FGVSs20UnsafeMutablePointerq__q0__q0
Referenced from: /Users/mdellagi/Library/Developer/CoreSimulator/Devices/5EEB8704-4DA7-4D43-B767-658CDD7C2E33/data/Containers/Bundle/Application/C589F01D-F6DB-4CB1-A69D-A28AA8013FE1/meinmd.app/Frameworks/Locksmith.framework/Locksmith
Expected in: /Users/mdellagi/Library/Developer/CoreSimulator/Devices/5EEB8704-4DA7-4D43-B767-658CDD7C2E33/data/Containers/Bundle/Application/C589F01D-F6DB-4CB1-A69D-A28AA8013FE1/meinmd.app/Frameworks/libswiftCore.dylib
switch type {
        case .Create:
            status = withUnsafeMutablePointer(&result) { SecItemAdd(requestReference, UnsafeMutablePointer($0)) }
        case .Read:
            status = withUnsafeMutablePointer(&result) { SecItemCopyMatching(requestReference, UnsafeMutablePointer($0)) }
        case .Delete:
            status = SecItemDelete(requestReference)
        case .Update:
            status =  Locksmith.performUpdate(requestReference, result: &result)
}

Woah that's pretty terrifying! What's the version of iOS/Swift/Locksmith you're using? When was the most recent pod install/pod update? (FYI introduced some breaking API changes to master yesterday, so if you need 1.2 support check out the 1.2.2 branch :) .)

I am using the latest commit in the 2.0 branch. The one from my pull request, really ;-)
I fixed it in my fork by dropping just working with the pointer directly…
Not sure if that is a bad thing or not.
case .Create:
status = SecItemAdd(requestReference, &result)
case .Read:
status = SecItemCopyMatching(requestReference, &result)
fixes it.

Ah okay. Master is now on Swift 2/iOS 9, so it's the recommended way of using Locksmith. The 2.0 branch is obsolete and will probably be deleted soon.
I wonder if this is an issue in master as well now though... doesn’t seem to be from the tests, but you can never be certain with stuff like this.
I think I'm going to close this, but feel free to reopen if you think it's an issue in master and I'll definitely look into it more. Thanks very much for your help 😀

master does not compile at all when using carthage.
The following build commands failed:
CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler

Would be good if you could provide a working branch for Xcode 7 Beta 6 and Carthage.

Agreed. I think this is my fault for not testing that it'd all work ok. Will have to look into this more for sure. I assume the output of xcode-select -p is the correct Xcode beta?

Yes its the correct beta. /Applications/Xcode-beta.app/Contents/Developer
I only have Xcode 7 Beta 6 installed on my machine.
Your 2.0 does compile fine.
The only problem is, it crashes at run time.
My fork at frnde/Locksmith is working and I do not really see the necessity for the UnsafeMutablePointer stuff in your switch. After removing it and working directly with the pointer everything is working as expected.

Sent you a pull request

I am not able to compile using Xcode 7 Beta 6 with Carthage too, and I have the same "CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler" error. Thanks and hope you can fix this soon!

I believe this has been fixed in #55, but let me know if not :)

Yep.

master is working fine here now


Missing event attributes compared to analytics-android

Describe the bug
Missing attributes for event tracking compared to analytics-android lib.
The crucial ones are device.advertisingId and traits
However, triaits only appears when calling identify(...) but not when calling track(...) function
{
  "context": {
    "device": {
      "adTrackingEnabled": true,
      "advertisingId": "xxx",
      ...
    },
    "traits": {
      "email": "xxxxx",
      "first_name": "xxxx",
      ...
    },
    ...
  },
  ...
}

To Reproduce
Steps to reproduce the behavior:

Call identify with traits analytics.identify(userId = ..., traits = ...)
Call analytics.track(...)
Check Segment sources debugger

Expected behavior
analytics-kotlin should send the same attributes as analytics-android does
Platform (please complete the following information):

com.segment.analytics.kotlin:android:1.9.0
com.segment.analytics.android:analytics:4.10.4

hey @napas-pomelo, we no longer append traits to the track call since some destinations has PII constraints on that data. however, you can append the data by yourself with a simple plugin like below:
class TraitsPlugin: EventPlugin {
    override val type: Plugin.Type = Plugin.Type.Enrichment
    override lateinit var analytics: Analytics
    private lateinit var traits: Traits

    override fun track(payload: TrackEvent): BaseEvent? {
        val event = super.track(payload)

        if (event is TrackEvent) {
            event.context = updateJsonObject(event.context) {
                it["traits"] = traits
            }
        }

        return event
    }

    override fun identify(payload: IdentifyEvent): BaseEvent? {
        traits = payload.traits
        return super.identify(payload)
    }
}

in terms of advertisingId, we have a sample plugin provided for you to use. you can grab it as is or customize it according to your needs. all you need to do is to call analytics.add to add these plugins. the event will flow with the attributes you want.

Should this be flagged in the Upgrade notes? This one caught us out as it was an unexpected/undocumented change in behaviour from Analytics-Android and we didn't notice for a while

hi @empowerHamish that's a good call out. will add it to the upgrade notes. thanks for bring this to our attention


Migration scripts for CSVs and nodegroups

It is tedious to update the CSVs and nodegroups when the ontology changes.
Supposedly, the task could be automated to some extent, given a description of the ontology changes.
This issue will keep track of an effort to try and support an automated migration script, that we can ship to other performers so as to ease their transition path when we make changes.
Marking this as cli since I may make this a rack command.

I've had similar feature request from other SemTK users so I'd like to push this as far upstream as possible into SemTK.  I'm willing to help, of course.
One easy operation is to detect that a node's property doesn't exist in the model, and substitute another with a very similar name (sometimes it is exactly the same name but a different base URI).
Another thought is that this operation should not be fully automatic.  I'm fairly certain we'll want the user involved.   This introduces a bit of a user interface development problem.   One easier way around this might be to do it in semtk-python3 and use a simple text-based UI (present a list of options and the user hits a number).     ...just brainstorming here.

I wasn't sure where to post this so apologies for the repetition.  If there's a better or correct place, let me know.
I have a few questions about the migration tool.

The documentation says it will only migrate v4.1 to v5.0.  Is this still true, or has it been upgraded to handle v5.0 to v5.1?
I've followed (I believe) the installation instructions (including reinstalling the RACK CLI at the v5.1 version), and I'm getting an error about a missing module 'rack.commits'.  Any idea if this is an error on my part, or whether there is some piece that may not have made it into the installation?  (Full error below.)

$ rack_migrate --log-level=DEBUG --from-folder v5.0 --to-folder v5.1
Traceback (most recent call last):
  File "/home/gnelson/testing/ARCOS/RACK/bin/rack_migrate", line 4, in <module>
    __import__('pkg_resources').run_script('rack-migrate==0.0.0', 'rack_migrate')
  File "/home/gnelson/testing/ARCOS/RACK/lib/python3.7/site-packages/pkg_resources/__init__.py", line 651, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/home/gnelson/testing/ARCOS/RACK/lib/python3.7/site-packages/pkg_resources/__init__.py", line 1455, in run_script
    exec(script_code, namespace, namespace)
  File "/home/gnelson/testing/ARCOS/RACK/lib/python3.7/site-packages/rack_migrate-0.0.0-py3.7.egg/EGG-INFO/scripts/rack_migrate", line 23, in <module>
ModuleNotFoundError: No module named 'rack.commits'

Sorry @GregIthaca I tried debugging your problem 2 and never came back here to reply.
For question 1, we try and keep the tool up to date with each release, so once I update it, it should be able to migrate from any version (>= 4.0) to any newer version.
For question 2, I'm not sure what happened. I can try and help debugging if you pasted the output of pip install . from the migration directory (after having sourced the Python virtual environment in that directory). And maybe the output of which rack_migrate, to make sure there aren't stale copies of the executable on your PATH.

Closing, further trouble with the migration scripts should have their own issues.


Add isTruelyInvalid property

Add isTruelyInvalid property to validations as opposite of isTruelyValid.
My usecase is to make button disabled until form is valid, and it would be much cleaner to have something like this
<button disabled={{model.validations.isTruelyInvalid}}>Action</button>

instead of this
<button disabled={{unless model.validations.isTruelyValid true}}>Action</button>

Won't this work?
hbs```
<button disabled={{not model.validations.isTruelyValid}}>Action

@artemgurzhii please check out ember-truth-helpers.

@offirgolan This solves the problem for people, who are using this library, but not for people who don't. But as I have thought, it would be great to have this property builtin inside this library, as opposed to isTruelyValid method.
This will also be intuitively clear for people who are not very familiar with this library, such as me because there will be opposite property for all properties you have(isValid -> isInvalid, isValidating -> isNotValidating etc).

@artemgurzhii that's valid. I'll try to get it in as soon as I can. PR is also welcome 😄

You guys misspelled truly :\


Unnecessary warning "This construct causes code to be less generic ..."

Repro steps

Compile either of these repros .

Repro 1
namespace Library1

type MyOption<'T>(value : 'T option) =

    member this.Bind(f : 'T -> 'U option) =
        let variable = MyMutableOption<'U>()
        variable.Set(Option.bind f value)
        variable.ToMyOption()

and MyMutableOption<'X>() =
    let mutable variable = None
    member this.Set(v : 'X option) = variable <- v
    member this.ToMyOption() : MyOption<'X> = MyOption(variable)

Repro 2:
namespace Library1

type MyList<'T> (list : 'T list) =

    member this.Choose(f : 'T -> 'U option) =
        let accu = MyListBuilder<'U>()
        for x in list do
            match f x with
                | Some y -> accu.Add(y)
                | None -> ()
        accu.ToMyList()

and MyListBuilder<'X>() =

    let mutable accu = []

    member this.Add(x : 'X) =
        accu <- x :: accu

    member this.ToMyList() : MyList<'X> = MyList<'X>(accu)

Expected behavior
Compile without warning message.
Actual behavior

Warning message "This construct causes code to be less generic than indicated by the type annotations. The type variable 'U has been constrained to be type ''X'." is reported. But 'U and 'X are used in different type definitions so they should be independent of each other.
Known workarounds
Renaming type variable 'X to 'U suppresses the warning.
Or, adding explicit type annotation to line 17, as below, suppresses the warning.
    member this.Add(x : 'X) : unit =
Related information
Windows 10 64bit
Visual Studio 2015 Update 3

This is more compact repro.
namespace Library1

type MyOption<'T>(value : 'T option) =

    member this.Bind(f : 'T -> 'U option) =
        let variable = MyMutableOption<'U>()
        variable.Set(Option.bind f value)
        variable.ToMyOption()

and MyMutableOption<'X>() =
    let mutable variable = None
    member this.Set(v : 'X option) = variable <- v
    member this.ToMyOption() : MyOption<'X> = MyOption(variable)

I think the compiler should compile without warning, or give up type interference and ask for more type annotations.
There was one thing I misunderstood. I thought that type variable 'X was scoped within line 10 to 13, even after renaming it to 'U. But it wasn't. This is the screenshot after renaming. All 'U symbols in both of two types are highlighted.

So it is not surprising that renaming 'X to 'U changes the result.

This is a bug (IMO) and has been around for a long time. I filed a bug report on it a couple of years ago, but it was closed as a non-issue; it may have been the repro case I provided was a little too specific and unnecessarily conflated this bug with the F# value restriction (i.e., generic let-bound values).
Here's my earlier bug report:
https://visualfsharp.codeplex.com/workitem/99
Repro case (linked in that bug report, but linking again here for posterity):
https://gist.github.com/jack-pappas/48f83f6f1887fdcf7028
This bug is really non-intuitive to understand and workaround when it occurs -- it's bitten me a few times over the years -- so I'd really like to see it fixed.

It's certainly a nasty limitation and the error message could at least be better, asking to add full-type-signature type annotations on any members called before their point of definition.
For example, simply add "unit" as the return type of Set works here (because it enables early-generalization of Set).

namespace Library1

type MyOption<'T>(value : 'T option) =

    member this.Bind(f : 'T -> 'U option) =
        let variable = MyMutableOption<'U>()
        variable.Set(Option.bind f value)
        variable.ToMyOption()

and MyMutableOption<'X>() =
    let mutable variable = None
    member this.Set(v : 'X option) : unit = variable <- v
    member this.ToMyOption() : MyOption<'X> = MyOption(variable)

@nshibano @jack-pappas This is still considered by design I'm afraid, at least for F# 4.0/4.1.  The best thing would be to file an F# language suggestion on this. http://github.com/fsharp/fslang-suggestions.
There is a workaround in the case above by adding extra annotations to enable early generalization of methods.


[BUG] Y axis is inverted

Description
I saw this existing issue https://github.com/mono/SkiaSharp/issues/231 but not sure if it is related. Basically when I draw a simple Path, the more increase the Y axis, path is moving down not to the upper direction as i would expect. Here is the code sample.

   var  indicatorStrokePaint = new SKPaint
            {
                Style = SKPaintStyle.Stroke,
                StrokeWidth = 6,
                Color = strokeColor,
                IsAntialias = true
            };

               var start = new SKPoint(500, 70);
                var end = new SKPoint(500, 100);

                canvas.DrawLine(start, end, indicatorStrokePaint);

Screenshot for above code red line is the path I am drawing

if i increase those numbers like
   var start = new SKPoint(500, 100);
                var end = new SKPoint(500, 130);

you can see below that red path was drawn more below than the gauge.

Expected Behavior
I would expect that the more i increase the y axis, it should draw more upper.
Actual Behavior
goes down
Basic Information

Version with issue:   skiasharp.views.forms 2.80.1

Platform Target Frameworks:

Android: 9.0

SkiaSharp uses the top-left origin. Positive X is to the right, positive Y is down.
This is counter to macOS coordinates and GPU. However, it is pretty common with 2D screen-based rendering engines.

oh ok good to know. I thought that there is a bug :) thanks for making it clear for me.


Refactor, put all logic in vanilla JS files

It's a bit untidy to have all the logic in .njk files, and need to run eleventy in order to perform tests. It would be better if all the logic would be put in, say, app.js, and the generated output could be put in, say app.bundle.js (which could contain all the words).
This would also allow for testing with i.e. Jest (by adding a app.test.js file), which doesn't require a bunch words from another file to work.

Should consider inlining everything into one file.


weights converted in wrong order

Hi @Vladkryvoruchko , I noticed  you convert the parameter of bn layer in caffe to the numpy array by the order of  'mean = v[0], variance = v[1], scale = v[2], offset = v[3]' . However, the v[0-3] actually hold the value for scale, offset, mean, variance respectively according to the caffe blob's definition in bn layer.
The reason that you can still reproduce the results is that you reverse the order again when you try to restore the parameter for the keras model from the numpy array, i.e. model.get_layer(layer.name).set_weights([mean, variance, scale, offset]).
This may not hurt when using your code completely, but it is very unexpected for those people who just use the parameter converted by the code.
Thanks for your efforts!

@scenarios Seems like a valid point. Can you check #32? Do you have pycaffe installed to test converting the weights again?

@jmtatsch Checked and everything works well now.

@scenarios  Perfect. Would you be so kind and contribute new npy weights for the models? I don't have the whole PSPNET, pycaffe etc chain running anymore ...