Fix decoding single config values

Decoding configuration keys one by one, in contrast to decoding the whole thing into a case class, always results in an error:
import com.typesafe.config.ConfigFactory
import io.circe.config.parser

val config = ConfigFactory.parseString("a = 1")
// Returns: Left(io.circe.ParsingFailure: String: 1: a has type NUMBER rather than OBJECT)
// Expected: Right(1)
parser.decodePath[Int](config, "a")

The problem stems from the Config#root call in the toJson method in the parser, where a pathed Config may hold a string, and int, etc., and thus is not a ConfigObject. The fix is to call Config#getValue(path) when the path is present, and Config#root otherwise.

This looks reasonable to me but I'll defer to @jonas.


"function '__gmpz_init' not found" Settings work, addon completly broken

Bug report
Your Environment

Netflix add-on version: 1.6.1 (tested nighly build too)
Operating system version/name: W10 x64 2004 (19041.388)
Kodi: 18.7 x64

Describe the bug
The installation was successful. Once finished I simply tried to access the plugin, getting the displayed error on the screen about kodi services in background are unable to start because: "function '__gmpz_init' not found"
Log: https://pastebin.com/yqFKHERL
Expected behavior
Work fine
Actual behavior
I can access to addon settings, but nothing more.
Steps to reproduce the behavior

Open Kodi
Try to Open Netflix Addon

Debug log
Log (No debug): https://pastebin.com/yqFKHERL
Log (Debug): https://pastebin.com/aeJ07THQ

I'm sorry but what rule has been ignored?
The problem, the steps to follow, the system, the link to the logs have been described...
One is true that is "stripped" but is not verbose, so is not requested, , the other one with the debugging options enabled since the options are enabled until the problem is triggered.
What is wrong?


[chore] reivew pipeline using node 12

This run is affected:
https://github.com/bradtaniguchi/nx-template/actions/runs/3606991687
It seems like the entire pattern of saving the state, and thus how the "gen-affected" code works wont be sustainable 😢 due to underlying changes.
I think now is the time to focus back into #90.

Closing, as now the pipeline doesn't use these techniques.


Any chanse of support for navidrome?

It would be great if you add navidrome support
github link
github.com/navidrome/navidrome
preview
demo.navidrome.org

Woah I was actually looking for something like this recently, will definitely add support for this!

Done, will be available in the next version.


Add simple brb feature

It's not complete, but here it is...

Other than those things, looks pretty good. If you can fixup the random places where there are extra spaces between your last statement and the closing brace and more than 1 space between statements then we're good to go. Great feature!

👍


Access control: on- and off-boarding core members

📌 Summary
Document the onboarding and off-boarding process, with the aim of eventually automating most steps.
📝 Background
When a user joins any of the conda-forge teams, members of the core team need to manually provision the permissions across the required services.
The list of services and the required permissions are not fully enumerated,
and members sometimes acquire the needed credentials by manually requesting it to other members, as needed.
This also means there's no comprehensive list or way of knowing who has access to each service.
🚀 Tasks / Deliverables
- [ ] https://github.com/Quansight-Labs/czi-conda-forge-mgmt/issues/61
- [x] Added a PR to document onboarding and offboarding.
- [x] Automate provisioning as much as possible
- [X] https://github.com/conda-forge/admin-requests/pull/904
- [X] https://github.com/conda-forge/admin-requests/pull/906

📅 Estimated completion
This task should be finished in the first six months.
ℹ References

...
...
...

Pending: Consult conda-forge core team whether they want this information (already written) published in the website or internally.

Only https://github.com/Quansight-Labs/czi-conda-forge-mgmt/issues/61 left. Closing this one.


LSP-pyright crashed with AttributeError

Got the following traceback when opening a python file of a ST package with .python-version in its root.
LSP: LSP-pyright crashed (4 / 5 times in the last 180.0 seconds), exit code 1, exception: None
LSP-pyright: WARN: .python-version detected but pyenv not found
LSP-pyright: Using python path "python"
Error handling request
Traceback (most recent call last):
  File "C:\Apps\Sublime Text 40xx\Data\Installed Packages\LSP.sublime-package\plugin/core/sessions.py", line 2081, in on_payload
    handler(result, req_id)
  File "C:\Apps\Sublime Text 40xx\Data\Installed Packages\LSP.sublime-package\plugin/core/sessions.py", line 1804, in m_client_registerCapability
    watcher = self._watcher_impl.create(folder.path, [pattern], kind, ignores, self)
  File "C:\Apps\Sublime Text 40xx\Data\Installed Packages\LSP-file-watcher-chokidar.sublime-package\watcher.py", line 92, in create
    return file_watcher.register_watcher(root_path, patterns, events, ignores, handler)
  File "C:\Apps\Sublime Text 40xx\Data\Installed Packages\LSP-file-watcher-chokidar.sublime-package\watcher.py", line 120, in register_watcher
    self._on_watcher_added(root_path, patterns, events, ignores, handler)
  File "C:\Apps\Sublime Text 40xx\Data\Installed Packages\LSP-file-watcher-chokidar.sublime-package\watcher.py", line 133, in _on_watcher_added
    self._start_process()
  File "C:\Apps\Sublime Text 40xx\Data\Installed Packages\LSP-file-watcher-chokidar.sublime-package\watcher.py", line 175, in _start_process
    process = node_runtime.run_node(
AttributeError: 'NodeRuntimePATH' object has no attribute 'run_node'

LSP: LSP-pyright crashed (5 / 5 times in the last 180.0 seconds), exit code 1, exception: None

Most likely lsp_utils is not updated. Can you try to manually update it?

Sounds reasonable

Still had 2.0.0 installed due to my custom python 3.8 channels.


Add parameter freyja_depthcutoff

PR checklist
Solves issue #405
Freyja is throws a known error if it deals with samples of low coverage. It got fixed in this PR https://github.com/andersen-lab/Freyja/pull/145 by including the option --depthcutoff.

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs- [ ] If necessary, also make a PR on the nf-core/viralrecon branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

@nf-core-bot fix linting

Maybe you should add the changes to the CHANGELOG.md?

Maybe you should add the changes to the CHANGELOG.md?

Forgot, I'll do my other PR as well.


middel klick gets stuck when useing Wacom Intuos BT M

Description
when clicking in the shortcut for middelklick on the wacom pen it gets stuck
To Reproduce
Steps to reproduce the issue program in the shortcut for the pen in wacom softwear and when you try to scroll with it in pinta it gets stuck the only way to get it unstuck is to midelclick with a mouse
Additional Info
https://drive.google.com/file/d/1A_8kJ_QmyK4WYt3fL6n4Pu2ojrquvvXq/view?usp=sharing
Version
windows 10 Pinta version 2.2

The google drive link says that I don't have permissions - if it's a video, you should also be able to attach it directly in the GitHub comments too

sorry i just filmed it on my phone so it was easier for me to do it truth gdrive but the video is larger than 10MB https://drive.google.com/file/d/1A_8kJ_QmyK4WYt3fL6n4Pu2ojrquvvXq/view?usp=sharing but this link should work

Thanks, that video worked.
To verify I'm understanding, you're activating a middle-click through the pen and then trying to scroll / pan the image, but then you can't "release" the middle-click afterwards?


Expose font size and weight as Themeable properties

Description
Font family is exposed as themeable, but font size is not. The font I'd like to use to be consistent with brand guidelines on a project I'm working on doesn't display well with the default of 14px, making the page less accessible. I'd like to be able to configure the fontSize properties when generating a themed build of Cloudscape to maintain accessibility guidelines with a brand consistent font.
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate requests

Hello Sam!
Allowing this does seem like a sensible addition to the system, however we don’t have any plans for making this change at the moment. We will keep this issue open to collect any additional feedback or use cases.
Thank you.

This is a pretty crucial feature for being able to adopt this design system to match most designs.

"Design system" means that there is already a predefined design. Theming was never intended to convert our design system to another design. It is only to make small visual adjustments

That's fair. But I'd consider adjusting font sizes and weights to fall under the classification of "small visual adjustments".

The ticket stays open, because the OP request is something we want to address. However "match most designs" is not a goal for our project.

Apologies for my wording. By "most designs", I really only meant derivative designs of the underlying system. Things like tuning color palette, fonts, and border radiuses. Most of these are already supported.

We have released themeable tokens for font sizes and font weights. You can find the list of tokens in the "Typography" tab of our token list on our website.


Panic or Invalid JSON when shadowing embedded fields of composite type

I found several issues when tried to encode a struct with shadowed embedded fields (container struct fields and embedded struct fields have the same json tags).
Issue 1: Invalid JSON when embedded struct has shadowed fields of type map/slice/struct and non shadowed fields.
package main

import (
	stdjson "encoding/json"
	"fmt"

	gojson "github.com/goccy/go-json"
)

type Embedded struct {
	ID   string            `json:"id"`
	Name map[string]string `json:"name"`
}

type Container struct {
	Embedded
	Name string `json:"name"`
}

func main() {
	c := &Container{
		Embedded: Embedded{
			ID:   "1",
			Name: map[string]string{"en": "Hello", "es": "Hola"},
		},
		Name: "Hi",
	}

	gjsonB, _ := gojson.Marshal(c)
	stdjsonB, _ := stdjson.Marshal(c)

	fmt.Printf("go-json: %s\n", string(gjsonB))
	fmt.Printf("encoding/json: %s\n", string(stdjsonB))
}

Result:
go-json: {"id":"1",null,"name":"Hi"}
encoding/json: {"id":"1","name":"Hi"}

Issue 2: Panic when embedded struct has only one shadowed field of type map.
package main

import (
	"fmt"

	gojson "github.com/goccy/go-json"
)

type Embedded struct {
	Name map[string]string `json:"name"`
}

type Container struct {
	Embedded
	Name string `json:"name"`
}

func main() {
	c := &Container{
		Embedded: Embedded{
			Name: map[string]string{"en": "Hello", "es": "Hola"},
		},
		Name: "Hi",
	}

	gjsonB, _ := gojson.Marshal(c)

	fmt.Printf("go-json: %s\n", string(gjsonB))
}

Result:
fatal error: concurrent map iteration and map write

Issue 3: JSON includes field of embedded struct when embedded struct has only one shadowed field of type slice/struct.
package main

import (
	stdjson "encoding/json"
	"fmt"

	gojson "github.com/goccy/go-json"
)

type Embedded struct {
	Name []string `json:"name"`
}

type Container struct {
	Embedded
	Name string `json:"name"`
}

func main() {
	c := &Container{
		Embedded: Embedded{
			Name: []string{"Hello"},
		},
		Name: "Hi",
	}

	gjsonB, _ := gojson.Marshal(c)
	stdjsonB, _ := stdjson.Marshal(c)

	fmt.Printf("go-json: %s\n", string(gjsonB))
	fmt.Printf("encoding/json: %s\n", string(stdjsonB))
}

Result:
go-json: {"name":["Hello"],"name":"Hi"}
encoding/json: {"name":"Hi"}

@goccy Hi There,  can you point to the place we may fix this issue? I would be happy if I can help and send a PR.

Thank you for the reporting. I got enough information, so I will fix this issue :)


Library with version 7 is older than the schema with version 8

Hi,
I moved from an AWS box to a different server using ubuntu where I just installed postgres following the documentation but when I try to run the test script, I get this error:

AssertionError: Library with version 7 is older than the schema with version 8

on this line:
db = nfldb.connect()
I imported the given database .
What else can I check?
Thanks

nfldb.connect() is purposely making sure the API version and database schema version are the same.
What version of nfldb are you using?  The API version in the current nfldb release is version 8 here.

You are absolutely right. Upgrading to the latest version fixed it. Thanks!


Probabilistic Forecasting

We know that LightGBM currently supports quantile regression, which is great,  However, quantile regression can be an inefficient way to gauge prediction uncertainty because a new model needs to be built for every quantile, and in theory each of those models may have their own set of optimal hyperparameters, which becomes unwieldy from a production standpoint if you're interested in multiple quantiles as you can end up with many models.  One of the main issues with machine learning is point predictions, as businesses are often interested to know what the probability distribution is for a given prediction.  There are various methods to do this with neural networks, and only recently there have been new ways to address this with tree based models.
The NGBoost library has attempted to do this as per below
https://stanfordmlgroup.github.io/projects/ngboost/
Additionally there has been a paper on adapting XGBoost to be able to do this (in a different manner) although the author has not yet posted an implementation.
https://github.com/StatMixedML/XGBoostLSS
Something to consider as a feature as it would make LightGBM infinitely more valuable in regression scenarios.

Seconded - I think this would make LightGBM incredibly more useful for the same regression problems it is used to tackle now, as well as additional problems that require a more probabilistic approach.
Some of the ngboost team's ideas for next steps, on predicting joint probability distributions, as they mention in their slides ( https://drive.google.com/file/d/183BWFAdFms81MKy6hSku8qI97OwS_JH_/view ), are particularly interesting as well:
Demonstrate use for joint-outcomes regression (e.g. ”what’s the probability that it rains >3 inches and is >15C tomorrow?”)

Thanks @MotoRZR for referring to my repo https://github.com/StatMixedML. In fact, I am currently also working on an extension of LightGBM to probabilistic forecasting, see the repo here https://github.com/StatMixedML/LightGBMLSS

This would be a wonderful addition. FWIW - Catboost has recently rolled out support for something like this as well, in version 0.24 via RMSEWithUncertainty. I don't know how they implemented it yet.

FWIW - Catboost has recently rolled out support for something like this as well, in version 0.24 via RMSEWithUncertainty. I don't know how they implemented it yet.

Thanks to GitHub we can find the corresponding commit: https://github.com/catboost/catboost/commit/af88523dcb4dbaececac1891b26316a9cc23c384.

@kmedved Thanks for pointing towards the RMSEWithUncertainty! Very interesting, even though I am not sure how it is implemented exactly.
The fact that the RMSE is used as a loss function makes me doubt that it is truly a probabilistic approach. The reason is that, as splitting procedures that are internally used to construct trees can detect changes in the mean only, standard implementations of machine learning models are not able to recognize any distributional changes (e.g., change of
variance), even if these can be related to covariates. Since RMSE is a loss function that is minimal if the estimator is the mean, I am not sure how it deals with changes in variance, skewness etc.

That's a good note @StatMixedML, although I am actually not totally sure they're using plain RMSE as a loss function (despite the name). An explainer notebook is coming, but if you try it out, the validation loss on the model does not match (or even resemble RMSE). I've put together an example Colab notebook here., where on the CA housing dataset, without any tuning, the RMSE loss is 0.5166607793912465, while the RMSEWithUncertainty loss is 0.06206563547371406. So they seem to be using some custom scoring for RMSEWithUncertainty loss.

@kmedved Thanks for the interesting comparison! Indeed, it seems as if RMSEWithUncertainty != RMSE.
Anyways, I am not sure how one would evaluate RMSEWithUncertainty within a probabilistic framework; say how well the forecast uncertainty is calibrated, using something like a scoringRule. I agree that mostly point forecasts are used, but having a good estimation of the uncertainty is at least as, if not even more important, than point estimates. I can't remember where if found the quote, but it is a nice one

It’s better to be approximately right than exactly wrong.

The first half, of course, relates to a probabilistic forecast, whereas the second half aims at point forecasts.

Keep in mind that LightGBM already includes Quantile Regression. Even though it may not enjoy the probabilistic properties of a true bayesian forecast, it is still the most used method nowadays for variance forecast estimation.

Keep in mind that LightGBM already includes Quantile Regression. Even though it may not enjoy the probabilistic properties of a true bayesian forecast, it is still the most used method nowadays for variance forecast estimation.

Quantile regression is fine if you're only interested in specific quantiles.  If you want to the full distribution it's not as useful.  Also, with quantile regression it's inefficient to have a model for each quantile with different sets of hyperparameters.
With neural nets there are various ways to do this like:
-variational inference i.e., have two targets for the network, the mean and standard deviation
-bayesian regression
-dropout based approach http://mlg.eng.cam.ac.uk/yarin/PDFs/NIPS_2015_deep_learning_uncertainty.pdf
With GBDT not as many tools, only recently has NGBoost has come on the scene.  Seems like StatMixedML also has something in the works.  Quantile regression is ok, but not the magic bullet solution for the reasons mentioned.

This article also points out some of the flaws of quantile regression.  Not specifically LightGBM related but still relevant.
https://medium.com/@qucit/a-simple-technique-to-estimate-prediction-intervals-for-any-regression-model-2dd73f630bcb

@MotoRZR yes, I recall reading that article a while ago.
IMO, the most interesting approach is the one where the parameters of a distribution are estimated (this is, the first one you mentioned two messages above). In fact, that distribution parameter estimation method is what Amazon uses in their DeepAR paper (which happens to be the default model in their AWS Forecaster service).
However, I am not sure whether this should be added as a new objective. It is relatively easy to get it up and running with the existing API.
MC dropout for boosted trees is something I have been thinking about. However, at least in neural nets MC dropout generates distributions that usually end up having low variance (and therefore narrow prediction intervals) compared to more conventional bayesian inference fitting methods. But perhaps it is worth exploring for GBDT...

Closed in favor of being in #2302. We decided to keep all feature requests in one place.
Welcome to contribute this feature! Please re-open this issue (or post a comment if you are not a topic starter) if you are actively working on implementing this feature.

Closed in favor of being in #2302. We decided to keep all feature requests in one place.
Welcome to contribute this feature! Please re-open this issue (or post a comment if you are not a topic starter) if you are actively working on implementing this feature.

I have just released LightGBMLSS, which is an extension of LightGBM to probabilistic forecasting. Currently, it supports prediction of all parameters of a Gaussian, but I will add more distributions soon. It has a very similar functionality (and soon same distributions) as XGBoostLSS which is also under current development.
I hope this is helpful for bringing LightGBM to a probabilistic setting. Looking forward to your feedback!

I have just released LightGBMLSS, which is an extension of LightGBM to probabilistic forecasting. It has a very similar functionality as XGBoostLSS which is also under current development.
I hope this is helpful for bringing LightGBM to a probabilistic setting. Looking forward to your feedback!

Can this be integrated into the main lightgbm package?  Looks rather interesting.

@onacrame Thanks for your interest in LightGBMLSS. In principle, it is possible to create a Pull-Request and integrate it into lightgbm itself. As of now, I am not planning to do this since there are still some additions I want to bring to LightGBMLSS.

I found this very interesting:
https://www.semanticscholar.org/paper/Probabilistic-Gradient-Boosting-Machines-for-Sprangers-Schelter/8ec78ba7eb40f5a834753c94e245517d855ea3e0
https://github.com/elephaint/pgbm

In our latest paper, we extend LightGBM to a probabilistic setting using Normalizing Flows. Hence, instead of assuming a parametric distribution, we approximate the conditional cumulative distribution function via a set of transformation, i.e., Normalizing Flows. You can find the paper on the repo
https://github.com/StatMixedML/DGBM
Yet, we are still struggling with the runtime. I have create an issue on the repo
https://github.com/StatMixedML/DGBM/issues/1
That also has a link to a more thorough description of where the computational bottleneck might be.
Appreciate any support on this.

This was locked in error, sorry.

Hi
Do we know if there is any possibility of including LightGBMLSS, or NGBoost like functionality within LightGBM?
This would be a very powerful addition to what we have currently in lightGBM.


Fix spelling errors

Proposed changes:

Fixed spelling erros in docs and code

Status (please check what you already did):

[ ] added some tests for the functionality
[x] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

@ancalita, done!
sry for the delay

@thiagohdaqw in order to merge this PR, we need to fix the Code Quality fail (the other failing job is flaky, so we can re-run it until it passes. The linter is a bit temperamental, so even if you had not modified those specific lines, it will check for any irregularities in the file you made edits, let us know if you need any direction with solving these errors. Once solved, you can run make lint in your terminal to check if everything passes.
Error: rasa/core/channels/mattermost.py:121:1: D102 Missing docstring in public method
Error: rasa/core/channels/slack.py:297:1: D202 No blank lines allowed after function docstring


Add entry to beginning of the file

I have a config file similar to this
Host host1
...

Host host2
...

Host *
...

I want to add host3. But if host3 is added at the end, the * config will be used which is not intended. It would be good to have an option to add the entry to beginning of the file.

I have added the before_host arg to the add() method. Let me know if it resolves the issue.
Thanks, Soren


Use multiple requests for BSO data if more than 10.000 results

2 separate requests for bso-publications and bso-datacite ?
splitted by "published_date" on bso-publications, "created" on bso-datacite ?

=> number of slices should be calculated according to the number of results

The FOSM max limit is still in place by default, set to 10 00 results


Connected Computation Graph

This is a very cool I have a project. I'm working on a similar project where I need to count instances of objects in a given set of objects in an image.
My current naive approach just uses a trained Retina-net model but suffers from the duplications mentioned in your paper. I would like to hopefully improve my model by linking the existing  computation graph of retinanet to the counting module you have written. Currently my model is based off of this implementation of retinanet.
My project isn't a VQA scenario i.e I don't need to do any seq2seq on a query string, i just need to count objects but I still think this is relevant. Is this something you have already done? Can you recommend a pytorch implementation of retina net that works well with your code? Or if possible include an example of how to do this?
Thank you.

I haven't worked with RetinaNet, but it should be possible to use the counting component with it. The important bit is to tell it what proposals are relevant with a score from 0 to 1. In the paper, this is done with an attention model conditioned on the question, which you would want to replace with the probability of each bounding box, determined by the RetinaNet.
I imagine that the set-up would look like this:
Image ---[RetinaNet]---> bounding boxes, probability of each box ---[counting component]---> count
A relatively simple thing to get started is to take your existing model in Keras, get bounding boxes and probabilities for each bounding box out of it, and just feed those into the counting component. If the counting component seems to help, then you can use find a RetinaNet in PyTorch and do end-to-end training.

Thank you this is exactly what I had in mind. Again really great work. I enjoyed the article and your response to the reviewers. I will update you later in the month with how my experiments proceed. When you trained this did you get you use an end to end computation graph with the object detection component, or did you run the counting component individually?


Chaining rules should raise an error

Hello.
I have a strange situation where the order in which I chain methods in a schema attribute changes the result:
SPECIAL_TOKENS = ["test_approval", "test_denial"]

# Consider the following different possible definitions of the same attribute
# inside a schema. The schema is called with: {private_token: "test_approval"}

# these two work without error with the indicated valid input
required(:private_token).value(inclusion?: SPECIAL_TOKENS)
required(:private_token).value(inclusion?: SPECIAL_TOKENS).str?

# But this the following gives: (...)
# messages={ :private_token=>[ "must be a string",
# "must be one of: test_approval, test_denial" ]
required(:private_token).str?.value(inclusion?: SPECIAL_TOKENS)

The only difference is that in some cases str? comes in the end or is absent because it would be implied in the inclusion validation. However I don't see why they would fail in the third case, str? should pass and the inclusion validation should pass as well.
Am I missing a usage rule here or is this indeed a bug where order shouldn't be meaningful in this explicit case and something's unexpectedly colliding somewhere?

Sorry but chaining is actually not supported, we just need to intercept it and raise an error. I'll leave this open for a reference and close it once I improve the DSL so that it doesn't allow chaining

I should mention that you can simply do value(inclusion: SPECIAL_TOKENS) as str? is pretty much redundant in such cases

Thanks for the clarification, I did indeed feel that str? as redudant. I updated the title of the issue to reflect the actual issue.

We indeed improved the DSL, this will raise an error in the next version.


Streaming Updates for v6

Just getting started but wanted to enumerate the priorities. I'm sure I'm missing a few but here's some things that I think should be on the punchlist:

[ ] exponential back-off reconnects as defined under Reconnecting section of Twitter docs
[ ] site stream controls
[ ] update and reconnect (see #565)
[ ] 100% c0 code coverage for streaming
[x] additional message support (see #649)

@mroth I did investigate delimited mode in em-twitter. I can't quite remember what transpired (the branch I was fiddling in is long gone) but I'll definitely see if it makes sense here.

@sferik any thoughts as to why the builds are failing on travis? Looks like master had changed a bit since my original fork. I fixed all the rubocop warnings in master and rebased, expecting a clean build in the streaming branch, but was surprised to see all these failures.

I’ll look into why the build is failing on master and rebase this branch after I fix the problem. Just be sure to git pull --rebase in your local branch before you start working on this again.

@stve Okay, the build should be passing now. Please remember to git pull --rebase in your local branch.

all good now, thanks @sferik :smiley_cat:

@stve Thanks for all the work you put into this last night. Looks like you’re making good progress. :heart_eyes_cat:

@stve @sferik I've started a repo comparing functionality and performance of various Twitter Streaming API solutions here: https://github.com/mroth/twitter-streaming-showdown
It's not done yet, but providing here now in case it informs any of the work towards v6.  Let me know if I can help with anything, keep up the great work!

@mroth That’s awesome! Now that you mention it, GZip compression is another feature we’d love to support. I’ll create an issue for that. Hopefully we can ship it as part of the v6 milestone, but since it can be added transparently, it might slip to 6.1.

Coverage increased (+0.37%) to 99.95% when pulling 209a0f7dd99314a8cb4844c9428929d2605696ef on streaming-updates into bf6a90d2eb70c29b61de112a308fd0abba8e1484 on master.

Coverage increased (+0.37%) to 99.95% when pulling 209a0f7dd99314a8cb4844c9428929d2605696ef on streaming-updates into bf6a90d2eb70c29b61de112a308fd0abba8e1484 on master.

@sferik can you take a look at the cursor implementation on c1a8f3a0e4fe513169dd313368c60b3b69a2ff4d
It needs more tests, but mainly I wasn't sure that I fully grokked what the code was doing so I figured I'd pause before continuing.

@mroth nice work pulling all that information together. Hopefully we can address the boxes that aren't checked on rb-twitter.
Limit message support has already been added and once I wrap up Site stream controls, I'm going to refocus on reconnects and delimited support. I had a devil of a time trying to get GZip support to work on em-twitter and ultimately abandoned my attempt, but it seems like combining delimited support could make that a good deal easier.

@stve Cursor stuff :eyes: :+1:

Coverage increased (+0.37%) to 99.95% when pulling f2859b192feb632ab54d29be5e109ac1fdbcf593 on streaming-updates into bf6a90d2eb70c29b61de112a308fd0abba8e1484 on master.

@sferik I wanted to point out 342a59f1d195bb1266c41f4b86d6543980ae9ad4 which is a breaking change to the public API. I made this change primarily because I wanted to be able to use the credentials of one client to instantiate another:
rest =  cTwitter::REST::Client.new(consumer_key: 'CK', consumer_secret: 'CS', access_token: 'AT', access_token_secret: 'AS')
stream = Twitter::Streaming::Client.new(rest.credentials)

Previously, the way the keys were mutated in credentials meant that an additional method would have been needed. I think this also make sense as credentials can now return the same keys/values that a class is instantiated with.
Generating the credentials hash for purposes of OAuth header generation has been moved into the Twitter::Headers class: 2de4a339e74cb6817bf5ac9a644d071750878d52
I hope this makes sense. I had mixed feelings about introducing a breaking change here, but the more I thought about it, the more it seemed like the right thing to do.

@sferik sidenote: the build is failing due to the fact that 1.9.3's JSON parser doesn't elegantly handle empty responses (which the streaming control API returns).
Any thoughts as to the best way to avoid parsing in such situations?
I could add to the options hash that gets passed through Twitter::REST:Utils#perform_post but it needs to be passed all the way down to Twitter::REST::Request in order to prevent response body parsing. I'm fine doing that, as I don't see another way of accomplishing with minimal disruption otherwise. I just wanted to make sure you were ok with it first.

Coverage increased (+0.37%) to 99.95% when pulling 937d4ec7961d716037f0f96db7279fe41704962d on streaming-updates into bf6a90d2eb70c29b61de112a308fd0abba8e1484 on master.

Any thoughts as to the best way to avoid parsing in such situations?

Can we specify a dependency on a newer version of the json gem instead of relying on the version that ships with the standard library?

Any thoughts as to the best way to avoid parsing in such situations?

Alternately, we could bump the required Ruby version to 2.0.0. Support for Ruby 1.9.3 will end on February 23. Assuming twitter gem version 6.0.0 comes out around the same time, I’m not sure it makes sense to release a gem that supports an unsupported Ruby version.
That said, I think there are still a good number of people using Ruby 1.9.3. I’m very curious to see the results of this year’s Ruby survey. Last year, there was still 18% using Ruby 1.9 (and 2% using Ruby 1.8). If that number drops below 5%, I’d feel comfortable dropping support for it.

@sferik I require the json gem for now. We'll keep an eye on the Ruby survey to see if we can drop 1.9.3.  In terms of ETA on this branch, I still have quite a bit to do but we're getting there.

Coverage increased (+0.37%) to 99.95% when pulling 00e0b55fcd73ef42729808e25da6218165d1010e on streaming-updates into bf6a90d2eb70c29b61de112a308fd0abba8e1484 on master.

Coverage increased (+0.37%) to 99.95% when pulling 00e0b55fcd73ef42729808e25da6218165d1010e on streaming-updates into bf6a90d2eb70c29b61de112a308fd0abba8e1484 on master.

@sferik do you have any thoughts around a suitable interface for updating a stream? My main goal is creating something that's simple to use and doesn't disrupt the experience all that much. The simplest way I can think of is something like this:
handler = Proc.new do |object|
  puts object.text if object.is_a?(Twitter::Tweet)

  client.filter(track: 'nba')
end

client.filter(track: 'nhl', &handler)

Basically, invoking filter without passing a block/proc does one of two things:

when not connected to a stream raises an error since there's nothing to handle the response data, it already does this (but doesn't consider a potential existing connection)
when connected, halts the connection and reconnects with the new request parameters, reusing the existing proc from the previous connection

The downside to this approach is that it puts more onus on the user to manage their streaming criteria. My observation from tweetstream is that most users were comfortable assuming that responsibility. I'm going to continue to think this through a bit more, feedback welcome!

FYI, it looks like Twitter just added a new user_update streaming message type.

@sferik yep, I get those notifications too. Been a busy few weeks but should be getting back to this soon.
Any thoughts on my comment above from Feb. 7?

@stve Cool. I didn’t realize you already subscribed to the API Changelog for Twitter.
Here’s an alternative to your proposed interface for updating a stream. What if the methods yielded an optional second object, the connection, back to the block? Like this:
client.filter(track: 'nba') do |object, connection|
  puts object.text if object.is_a?(Twitter::Tweet)

  connection.update(track: 'nhl')
end

I’m not sure if this is any better than what you proposed. Maybe the method should be called reconnect instead of update. It’s just another idea for you to consider.
I guess the common use-case for reconnecting is broadening a search. Maybe we can ask the creator (and commenter) of https://github.com/sferik/twitter/issues/565 how they’d like the interface to look. If I understand that use-case correctly, this approach would work by polling the database for updates after each tweet. Perhaps there should also be a way to interrupt the connection from the outside (sending a signal from another process). Is that too crazy? I fell like there must be a better solution but I don’t know what it would be.

@sferik maybe it should just be an overloaded reconnect method on the Twitter::Streaming::Client. Something that can be used to reconnect (as is) or reconnect with revised parameters, like:
client.reconnect # reconnects the stream (w/ no changes)

client.reconnect(track: 'nhl') # reconnects and changes the parameters

I agree that a common use case is updating the stream based on some data set coming out of a DB/queue/etc. This could be accomplished with the timers gem like so (some of this is pseudo-code):
require 'timers'
require 'db'

tracklist = db.list

client = Twitter::Streaming::Client.new({})

timers = Timers::Group.new

timers.every(60) do
  tracklist = db.list
  client.reconnect(track: tracklist)
end

client.filter(track: tracklist)

@stve I suppose an alternative is to use the Celluloid::IO TCP/SSL socket classes, so these methods calls become non-blocking:
tracklist = db.list
stream = client.filter(track: tracklist) { |tweet| puts tweet.text } # Non-blocking

loop do
  sleep 60
  tracklist = db.list
  stream.update(track: tracklist)
end

Just spitballing here. I’m not sure if this is any better or worse than what you’ve proposed. I do like that it uses sleep instead of requiring something like timers.

Or maybe even build sleep into the interface:
tracklist = db.list
stream = client.filter(track: tracklist) { |tweet| puts tweet.text } # Non-blocking

loop do
  stream.block(60)
  tracklist = db.list
  stream.update(track: tracklist)
end

where #block is simply defined as:
def block(seconds)
  sleep seconds
end

@sferik the Ruby Survey results just landed, while it was close, looks like we'll potentially support 1.9 for another year:

1.8 (0.9%)
1.9 (6.9%)

The issue that prompted that discussions was JSON parsing of nil behavior in 1.9 which is remedied by the json gem so this isn't really a problem per se, just something I wanted to document if we end up scratching our heads on it at some point down the road.

That said, I think there are still a good number of people using Ruby 1.9.3. I’m very curious to see the results of this year’s Ruby survey. Last year, there was still 18% using Ruby 1.9 (and 2% using Ruby 1.8). If that number drops below 5%, I’d feel comfortable dropping support for it.

The 2015 survey closed on February 13. I believe there are three factors that have already caused (or will shortly cause) users to upgrade to Ruby 2.

Ten days after the survey closed, the MRI team dropped support for Ruby 1.9.3. I wish the survey was conducted after that date, since I suspect it pushed many users to upgrade to Ruby 2. If the survey was held again today, I wouldn’t be surprised if the number of Ruby 1.9 users was already below 5%.
Rails 5 will require Ruby 2 and is scheduled to ship a beta release in less than a month at RailsConf. Once it’s released, I believe this will be another major factor pushing users to upgrade from Ruby 1.9.
The latest version of JRuby (1.7) still ships with Ruby 1.9 as the default mode. I suspect a majority of the users who reported using Ruby 1.9 in are JRuby users (according to the same survey, JRuby is the preferred interpreter for 4.2% of respondents). JRuby <IP_ADDRESS> (a.k.a. JRuby 9000, a.k.a. JRuby 9k) will be the first version to ship in Ruby 2 mode by default. The first JRuby 9 beta was released in January and the final release is scheduled for Q1 2015 (any day now). Once JRuby 9 is released, I suspect many JRuby users to make the jump from Ruby 1.9 to Ruby 2.

I believe any of these individual factors could push the number of Ruby 1.9 users below 5%. Taken together, I’m highly confident that the number of Ruby 1.9 users will drop from 6.9% to less than 5% in the next few months.
In the past, I made a significant effort to support Ruby 1.8.7 for four major reasons:

The migration path from Ruby 1.8.7 to 1.9 wasn’t easy and many legacy applications were stuck on Ruby 1.8 (including Twitter itself).
JRuby was still shipping with Ruby 1.8 as the default mode until October 2012, more than two years after Ruby 1.9.2 was released.
Mac OS X was still shipping with Ruby 1.8.7 until version 10.9 (Mavericks) was released on July 27, 2013.
The official Ubuntu package installed Ruby 1.8.7 until version 14.04 (Trusty Tahr) was released on April 17, 2014. :cry:

Thankfully, the ruby package in Ubuntu 14.10 (Utopic Unicorn) ships with Ruby 2.1, however this is not an LTS release. The next Ubuntu LTS release isn’t scheduled to ship until April 2016.
In conclusion, I think it would be a shame to ship a version of the twitter gem that doesn’t work on the latest stable JRuby. If we want to ship v6 before JRuby 9 is released, I think we should continue Ruby 1.9.3 support. Likewise, if we care about Ubuntu LTS users, there’s an argument for maintaining Ruby 1.9.3 support through April 2016. Unfortunately, there is no survey data about what operating system Ruby users run in development/production, so I’m not sure if this constituency is worth supporting.

Update: I’ve opened up a few issues in the Ruby Survey project to give us better information in the future.

@sferik, @stve: If you allow me to give any imput: I like the solution proposed by @sferik on https://github.com/sferik/twitter/pull/631#issuecomment-78371061 better for several reasons:

We keep control of the individual filters instead of closing all the connections on the client.
We can set up more than one filter operation.
We can trap kernel messages like Kernel.trap( "INT" ) { exit_requested = true } and handle how/when to close connections.

If you don't want to break the public API, what do you think about including a blocking argument:
stream = client.filter(track: tracklist, blocking: false) { |tweet| puts tweet.text }

I rebased of master (:scream:) around the 5.15.0 release because I wanted to get some of the non-6.0.0-specific features and bug fixes out into the world (see the CHANGELOG for details), since it had been more than 6 months since the previous release. I was hoping 6.0.0 would be released by now but it’s been slower going than expected for a variety of reasons, many of which are out of our control (e.g. blockers in the http gem and extremely high churn in the Twitter Ads API). That means that 6.0.0 is probably not coming any time soon, unless we dramatically start cutting scope.
In the best-case scenario, I’ll get a large chunk of dedicated time to work on this library in December and we can ship around the New Year. Worst-case is probably mid-2016, at which point, I’ll agressively start cutting scope just to ship whatever’s ready and start working on adding non-breaking changes in 6.1.0 and breaking changes in 7.0.0.
The good news is there is a clean diff between the 5-stable and master branches: master is based on 5-stable and includes only the changes that are specific to version 6. The bad new is all other branches based on master need to be rebased. This will be a relatively painful rebase (~50 commits). I apologize in advance for making you go through that, but I think it will be worth having a clean separation between the branches as we push toward a 6.0.0 release.


Broken URLs in patient JSON

The following URLs found in Patient.JSON lead to a 404 (file not found).
http://standardhealthrecord.org/fhir/extensions/placeOfBirth
-- what should it be? -->
http://standardhealthrecord.org/fhir/extensions/fathersName
-- should it be? --> http://standardhealthrecord.org/fhir/StructureDefinition-shr-demographics-FathersName-extension.html
http://standardhealthrecord.org/fhir/extensions/passportNumber
-- should it be? --> http://standardhealthrecord.org/fhir/StructureDefinition-shr-demographics-PassportNumber-extension.html

Thanks for the bug report. The SHR has changed since the code that generated those records was written.
placeOfBirth should now be http://hl7.org/fhir/StructureDefinition/birthPlace
The others suggestions are correct.

@kjmahalingam please make sure these extensions get fixed when you update the FHIR code.


Touch outside map messes up zooming/panning on WP8

Device: Windows Phone 8
Openlayers version : 2.13.1
Issue also exists on:
http://openlayers.org/dev/examples/mobile.html
http://openlayers.org/dev/examples/mobile-jq.html#mappage
Panning/Zooming works fine until I go outside the map (move off the screen with my finger), that mouse position stays registered. The result of this is when I want to pan the map (drag it with 1 finger) it starts to zoom. Somehow it thinks there is still a finger holding a spot outside the map (even outside the phone screen). As far as I can tell this only works on the bottom/top of the phone, the sides are not bugged (X-axis works, Y-axis is bugged).
I tested further and reduced the div size, it looks like there is a tiny border outside the map, all events on this border are registered but never cleared.

OpenLayers: 2.14 dev
Device: Windows 8 tablet
I just encountered the same problem, and I think I found the fix.
It seems that metteo is correct with his EDIT3 comment in that the issue lies in the MSPointer* events handling by OpenLayers.Events. Specifically, the problem lies in the addMsTouchListenerStart method of OpenLayers.Events. In this function, MSPointerOut is bound to the internalCb function. internalCb only removes the touch if it satisfies the following two checks:
if (this.clientWidth != 0 && this.clientHeight != 0) {
if ((Math.ceil(e.clientX) >= this.clientWidth || Math.ceil(e.clientY) >= this.clientHeight)) {
touches.splice(i, 1);
}
}
I'm not sure about the first if-statement (why does a no-size element have pointer events?), but the second if statement seems to be causing the problem for me. You should probably expand it to also remove the touch if the e.clientX < 0 or the e.clientY < 0, to prevent moving off the top or left side.
In our case, we sometimes have an html element on top of the map on the left side, so in that case the e.clientX < 300 (the element's width) but not < 0. I chose to remove the second if-statement altogether, and for now it all seems to work fine.
I'm not sure why the statement was added, and if removing it can cause other bugs, so please keep that in mind when trying this fix.

@tkdejong My findings apply to ol 2.13.1. 2.14 dev was updated in this commit https://github.com/openlayers/openlayers/commit/ec348da963d9b3537090dab87e607e872db4b0cd which points to #1290


Images & diagrams for the "BIOS & The Wilderness of the Firmware".

The text writing of this article is 99% done. Just need to add a "Final Words" section and I'm done with it.
Now come's the more colorful & exciting part: drawing & creating images. These will be done mostly by me using Adobe tools. However I might also use public images from Wikipedia or Unsplash.
Here's the list of images or diagrams that needs to be created:

header.png
all-the-terms-above-cute.png
volatile-vs-non-volatile.png
software-env-requirements.png
high-vs-low-level-app-req.png
different-bootloaders-screen-and-website.png
cpu-memory-motherboard.png
storage-devices.png
different-programs-detected-by-grub2.png
magic-headers.png
bootloader-asking-which-os-to-load.png
grub-cfg.png
loading-program-into-memory-elf.png
bootloader-and-the-program-in-the-memory.png
assembly-stub-program-entry-label.png
kinds-of-software.png
releationship-between-hw-fw-sw.png
software-vs-firmware.png
first-stage-to-second-stage.png
x86-boot-overview.png
diff-x86-cpu-modes.png
x86-memory-map.png
arm-boot-overview.png
raspberry-pi4-board.png
arm-exception-levels.png
arm-device-tree-structure.png

My god.. this is going to be a LOOONG ride. Good luck future me ❣

Finally done as of 411ff41. I didn't except to "learn" more about X86 & ARM while doing this. Although this was a simple gathering of images and creation of diagrams, it DID help me learn a lot! So, ig I'm happy?
Anyway. Marking this as "Complete".


Logdb

Codecov Report
Attention: Patch coverage is 36.80851% with 297 lines in your changes missing coverage. Please review.

Project coverage is 40.29%. Comparing base (c6dd837) to head (8284c15).

Files
Patch %
Lines

logdb/logdb.go
37.03%
63 Missing and 5 partials :warning:

sessions.go
0.00%
51 Missing :warning:

logdb/restore.go
7.69%
45 Missing and 3 partials :warning:

files.go
0.00%
25 Missing :warning:

buffer.go
0.00%
23 Missing :warning:

logdb/segment.go
63.46%
13 Missing and 6 partials :warning:

logdb/scan.go
0.00%
18 Missing :warning:

server/server.go
60.00%
14 Missing and 4 partials :warning:

git/filereader.go
0.00%
9 Missing :warning:

server/aggregate.go
72.41%
5 Missing and 3 partials :warning:

... and 4 more

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main       #3       +/-   ##
===========================================
- Coverage   72.08%   40.29%   -31.80%
===========================================
  Files          22       21        -1
  Lines         670      742       +72
===========================================
- Hits          483      299      -184
- Misses        157      404      +247
- Partials       30       39        +9

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


How do I disable linter-xo for typescript?

Setup:
I have a Javascript project that I lint with XO and within that project I have a firebase/functions directory for Firebase cloud functions, written in Typescript.
project
|-- firebase/functions
    |-- package.json
    |-- tslint.json
|-- package.json

firebase/functions/tslint.json is basically { "extends": "tslint-xo" }.
Problem:
I don't want the linter-xo extension to lint my typescript file, because it doesn't lint it properly, e. g. for const y = (x: number) => x it reports
[XO] Parsing error: Unexpected token :

I tried setting "xo": { "extensions": [ "js" ] } in my package.json as well as in the VS Code setting ("xo.options"), but the linter still lints my Typescript files. I also tried "xo": false in firebase/functions/package.json, but that didn't work either.

I assume that the way to solve this is to use tslint for firebase/functions instead, however I can't disable linter-xo for Typescript and the file gets linted by both.
Alternatively, is there a way of making linter-xo work for typescript (so I don't need tslint and tslint-xo)?

try "xo.options": { ignores: ["**/*.ts", "**/*.tsc"] }
https://github.com/xojs/xo#ignores

Thanks, ignoring works.
Just in case someone else has a similar setup, I also had to set
"typeRoots": ["node_modules/@types"]

in firebase/functions/tsconfig.json, otherwise the build complained about missing dom lib types for the types in the root project (../../node_modules/@types).


fix(spinner): Prefix animation and transformation

Short description of what this resolves:
Resolves driftyco/ionic#8145.
Changes proposed in this pull request:
Prefix animation and transformation values so that spinner works in iOS 8.
Ionic Version: 2.x
Fixes:
Webkit prefixes are needed for iOS 8, which still has significant market share.

Just fixed this issue but with a different approach:
https://github.com/driftyco/ionic/commit/a2ffa63fd178f0f19d266042adacad3b4ea6f460
Thanks anyway for the PR!


Flesch Reading Ease Function not working

Here is my sample program:
import textstat
text = "The cat sat on the mat."
print textstat.flesch_reading_ease(text)
Here is the output:
AttributeError: 'module' object has no attribute 'flesch_reading_ease'
I attempted to use "flesch_reading_ease(text)" but it resulted in the output: "NameError: name ''flesch_reading_ease' is not defined"
None of the other readability functions seem to work either. Am I doing something wrong?

use ->
from textstat.textstat import textstat
instead of
import textstat

update readme

hi @4rshdeep!
Sorry for any confusion, we made a change recently that means you can just do import textstat.
This change is not on pypi yet though.


Keep init-nodes as fallback if all nodes fail

If all nodes change their IP addresses, the init node could be a hostname that resolves to the IP updated addresses. If we keep the init node address, we can use it as a fallback if we've lost connection to all nodes.

It used to work that way. Maybe you just need to revert this commit:
https://github.com/Ericsson/ered/commit/7d6c461f1fa2c4890e836145668206531218e291

Yeah, I know. I must have missed the reasoning for why it was done that way, but now I know.
I don't think we should keep the unused connection though, as we used to do.
When the init-nodes is a service name (a hostname that maps to multiple IP addresses, and updated whenever the node IPs change) then it makes sense to keep it around, but a user can also just use an IP of one of the nodes as the init node and later this IP is no longer part of the cluster. In the worst case, that node is later configured as part of another cluster, so CLUSTER SLOTS from this node returns something completely wrong. In this case it is not a good idea to keep it around and use it for slot mapping updates.
I want to use the init nodes just as a fallback when all nodes fail. It is more agnostic to how the cluster is deployed and used.

In the original design the initial nodes were preferred when sending an heartbeat with the intent of avoiding the situation where the client is connected to a cluster and a new cluster is formed using the configured address. If for some reason there are two active clusters I think the expected behavior is that the client is connected to the cluster containing the configured address, anything else would seem very odd to me!
Maybe I am not getting the use case here. Is your example based on any real world scenario?

No user asked for it, if that's what you mean, but OTOH we don't have very many users.
A scenario is a rolling upgrade of the database nodes, while the application (where ered is running) is not stopped. The database nodes are replaced one by one. Afterwards, the init node is no longer part of the cluster. Later its IP may be reused for another microservice, application node or possibly database node of another cluster. The init nodes just that: a node to use for initializing the client, not a node that is always part of the cluster. It's hypothetical but not unrealistic in my understanding.
Another case where we have another preference for CLUSTER SLOTS: When we get a MOVED redirect, we want to send CLUSTER SLOTS to the node that returned the MOVED redirect, since we know that it's aware of the slot migration and it's typically the old owner of the slot. Not all other nodes maybe be aware of it yet.


c++ inference time is different with python

I met a very puzzled question，Imodel inference time is 16ms by python，and then I use c++ to get inference time is 50ms.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

It has been 16 days with no activity and the awaiting response label was assigned. Is this still an issue?

Please provide details about what platform you are using (operating system, architecture). Also include your TensorFlow version. Also, did you compile from source or install a binary?
Make sure you also include the exact command if possible to produce the output included in your test case. If you are unclear what to include see the issue template displayed in the Github new issue template.
We ask for this in the issue submission template, because it is really difficult to help without that information. Thanks!

It has been 17 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 34 days with no activity and the awaiting response label was assigned. Is this still an issue?

We are closing this issue for now due to lack of activity. Please comment if this is still an issue for you. Thanks!


Unable to initialize testfairy

I followed all the steps on testfairy website for integrating with react-native. However when i tried to perform
import TestFairy from 'react-native-testfairy'; , it throws me an error saying TestFairy is not defined.
Can you give me pointers what might be causing this?

Hi,
I've just pushed a new version of this library (version 2.6.0) that now supports react-native link. Perhaps you should give this a try and see if it resolves your problem.

@vijaysharm
I'm having this same issue and I am running v. 2.6.0. This is the error it's giving me. I ran react-native link and got this feedback:
➜  app-mobile-iphone git:(integratesTFSDK) ✗ react-native link react-native-testfairy

Scanning 1152 folders for symlinks in /Users/robertmcelligott/Documents/advisorconnect/app-

mobile-iphone/node_modules (22ms)

rnpm-install info Android module react-native-testfairy is already linked

rnpm-install info iOS module react-native-testfairy is already linked

rnpm-install info Linking assets to ios project

rnpm-install info Linking assets to android project

rnpm-install info Assets have been successfully linked to your project

The code it's failing on is very standard:

import './App/Config/ReactotronConfig';
import { AppRegistry } from 'react-native';
import App from './App/appEntry';

import TestFairy from 'react-native-testfairy';

TestFairy.begin("keystring");

TestFairy.log("Your log message here");

AppRegistry.registerComponent('AppName', () => App);

Any help would be much appreciated. Thank you,

Hi @ArtyEmsee Thank you for letting us know. I just tried to create a new app and linked TestFairy without problems. Are you able to provide me with a sample that's failing for you, as I cannot seem to reproduce this problem on my end.

This might be silly, but have you tried to replace the import line with this line:
const TestFairy = require('react-native-testfairy');

I tried that, no luck. Can you tell me the process you used to create an app and and what version of test fairy you used? I'm going to try to replicate it on my end and isolate test fairy from the app I'm trying to test it on.

Hello, sorry for not getting back to you right away.
So the steps to create an app was pretty straight forward. I used the following commands

react-native init TestFairy
cd TestFairy
npm install --save react-native-testfairy
react-native link

And i followed the steps in our documentation to initialize the sdk.
You can download a copy of a project i created that works with TestFairy, have a look at this link
In case this information helps, here are the versions i used
> react-native --version
react-native-cli: 2.0.1
react-native: 0.53.2

Was having an error:
TypeError: undefined is not an object (evaluating 'TestFairyBridge.begin')
I have this finally working on iOS after long hours of investigation:
Go to Build Phases -> Link Binary With Libraries, and select "libReactNativeTestFairy.a"
More info here:
https://stackoverflow.com/questions/39342002/react-native-undefined-is-not-an-object-evaluating-rni18n-locale#answer-45806929
@vijaysharm i suggest to add this step to Manual Installation steps here https://docs.testfairy.com/Platforms/React_Native.html

Has the issue been fully addressed?
I am having a similar issue while trying to run the app on Android using a machine running Ubuntu (thus the solution presented by @dmitryn is not satisfactory).
I am registering the app in a similar way as @ArtyEmsee presented and it results in the following error:
TypeError: null is not an object (evaluating 'TestFairyBridge.begin')

Unfortunately, I cannot provide any parts of the code as the project I am a part of is not open source.

I guess just running npm install is not sufficient. We need to open the xcodeworkspace from /ios folder and drag and copy the node_modules/react-native-testfairy/ios (ios) folder to Library folder of the xcworkspace (create new files if necessary ticked). Then we need to install certain Frameworks as documented in the video https://youtu.be/HpLOsNwd_FM

Also refer: https://docs.testfairy.com/Platforms/React_Native.html


Shift+Enter instead of Ctrl+Enter on tutorial

In the tutorial, ctrl+enter doesn't run the code, it's shift+enter that does the trick.

Thanks @jm2242 that must have been an oversight.  I can probably update it later this week, or if you want to enter a PR that would be much appreciated!


HTML

HTML
User Story
As a novice Bootcamp student
I want the prework notes to be structured on a webpage
so that I can easily find the information
Acceptance Criteria
GIVEN a prework study website
WHEN I visit the website in my browser
THEN I see 4 boxes titled HTML, CSS, Git, and Javascript with associated notes listed

Followed all the instructions and did all the git pushing and pulling


this is hassane task

hello w u checke it please

ChechboxesTest, Content, DragDrop, DropDownTest, DynamicControl, Iframe, Js_Error, Notification_Message, RightClickTest assertions are missing. Please use at least one Page Object in your tests and it's not needed to visit  http://techfios.com/test/billing/?ng=admin/ before running a test.


[1pt] PR: Add csv file to capture processing time for each HUC

Capturing the processing time for each HUC into a csv file will allow the ability to easily analyze performance/cost efficiency for different variations of the -jb option. This will aid in specifying the appropriate resources on AWS.
Small changes:
Update error handling in check_huc_inputs.py  to correctly print the HUC number if it is not in the accepted huc set.
Fix broken unit tests, pytest currently prints:  25 passed, 3 skipped.
Testing
Ran fim_pipeline.sh with one HUC, three HUCs, and a HUC list of 10.
Checklist
You may update this checklist before and/or after creating the PR. If you're unsure about any of them, please ask, we're here to help! These items are what we are going to look for before merging your code.

[x] Informative and human-readable title, using the format: [_pt] PR: <description>
[x] Links are provided if this PR resolves an issue, or depends on another other PR
[x] If submitting a PR to the dev branch (the default branch), you have a descriptive Feature Branch name using the format: dev-<description-of-change> (e.g.: dev-revise-levee-masking)
[x] Changes are limited to a single goal (no scope creep)
[x] The feature branch you're submitting as a PR is up to date (merged) with the latest dev branch
[x] Changes adhere to PEP-8 Style Guidelines
[x] Any change in functionality is tested
[x] Passes all unit tests locally (inside interactive Docker container, at /foss_fim/, run: pytest unit_tests/)
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged / future todos are captured in comments
[x] Project documentation has been updated (CHANGELOG and/or README)
[x] Reviewers requested

Code looks good. I will do a quick test run on it, then I can approve it.

Looks good. A couple of tidbits:

The changelog has stuff in the "additions" section but there was no file additions. All items in this PR should be in the "changes" section. It refers to the additions, changes or removals of file.
That block in the changelog.md should be in this PR conversation as well.
I did a three huc test and it looks good. I did open the csv in xcel. That format did not let me do a sum or average, but maybe you have  an idea in mind how to that in libre, xcel or will build a tool to figure the average.  I was initially thinking that you may want three columns, even though it appears somewhat redundant, but it kinda isn't. Different data formats and values. But.. your call. Go ahead and fix the Changelog and this PR and I can approve it for you. :)

@RobHanna-NOAA Thanks for the review and testing. Having three columns in the .csv file in my eyes is not necessary. The MM:SS format is pretty easy to grasp if the processing times will be less than 2 hours.


request for a feature to sort variables in debugger

I searched 'sort variables' but didn't see any relevant issues. If I missed something, please forgive and let me know. Thanks.

Can we have a feature of 'sort variables' in debugger? this is very handy when dealing with big chunk of variables and need to do cross check among the variables. PyCharm has this feature and I use it as a default setting.

Can you clarify what the feature would be, precisely? Variables are normally sorted by name.


Rendering issue on Wasm

examples/sprites:

This happens on Chrome and Safari. Not sure other browsers.

Nvm, there is an issue of my experimental html, that included an extra  element.


Packer v3

Rebased PR #799 ("packer-v2") on top of the latest obc-peer/master:HEAD.
No functional changes from PR 799.  One notable change from mainline is I omitted the "install vim" directives that were added since vim is already included in the ubuntu-based docker that this patch series introduces.
As with 799, this PR is intended to be accepted together with PR 49 from the obc-dev-env repository.
Test+Behave tests pass
Signed-off-by: Greg Haskins<EMAIL_ADDRESS>

Note, relates to Issue #741, which was documented in PR #799 but I neglected to carry forward in the rebase notes.

I've been running with this PR and https://github.com/openblockchain/obc-dev-env/pull/49 and can also confirm that tests are passing.

Reviewed and confirmed that all tests are passing.


Add Housing.com to showcase

https://medium.com/engineering-housing/how-we-built-our-react-native-app-3380a33811ac

Thanks for sending this pull request. For consistency the Showcase is now fully managed by the open source team at Facebook and we unfortunately cannot accept more pull requests to it. Feel free to post about the app in the React Native Community group on Facebook to increase visibility.

@hramos how to add my app in the React Native Community group on Facebook  and react-native website showcase?

You can find a link to the Community group on the React Native website. Anyone can join and post to the group.


Windows CI: Enable some more build tests

Signed-off-by: John Howard<EMAIL_ADDRESS>Enables a few more builder tests on Windows CI. And corrects a typo too :smile:

LGTM 🐸

LGTM


added workaround for NPE in FullTextParser

workaround for https://github.com/kermitt2/grobid/issues/676
probably doesn't solve some underlying issue

Coverage decreased (-0.01%) to 38.255% when pulling b347f6388dc3684683dbbf1b4d11a1648088b3ee on elifesciences:workaround-fulltext-npe into 506c00afad2bfc93d8b8820857b1c3756cab7cad on kermitt2:master.

Might be the opportunity to refactor a bit the FulltextParser, when the string is null, we might want to skip all the processing of figures and tables directly.

Might be the opportunity to refactor a bit the FulltextParser, when the string is null, we might want to skip all the processing of figures and tables directly.

Yes, this is just a workaround to the issue that I encountered, but don't fully understand. e.g. is it normal that featSeg is not null but doesn't produce any text? If so, in what situation would it be null?
In general the function could probably do with breaking up. It might be good to get refactored code merged quickly to avoid conflicts. Perhaps that would work well for pairing. (Although not so well with major timezone differences)

I close this as the commit has been included in #684


Configure dependabot on the release branches

This should cause dependabot to open PRs when new point-releases of Submariner become available.
Signed-off-by: Stephen Kitt<EMAIL_ADDRESS>

/cc @dfarrell07 @sridhargaddam

/lgtm

/lgtm

/lgtm
/approve

/retest

Please merge it Prow :eyes:


Filters act as though their container is the entire stage

For example if I apply a DisplacementFilter or a AlphaMaskFilter to a DisplayObjectContainer, I'd expect the filter output to match where that container is on the stage.
A scenario of where this could be used is a DisplayObjectContainer with a wobbly jelly monster in it, at a position of 50,50. This container would use the DisplacementFilter, but for the correct visuals the filter output should be matching the containers position.
What actually happens is, if a container has a particular position or scale...neither of these seem to effect the filter:

The filter remains at a position of 0,0. So if you are trying to have a DisplayObjectContainer at a position of 50,50 with the filter appearing at that same position...the filter is unable to match the position of the container it is applied to.
The filter remains at a scaled size of 1,1. So if you are trying to have a DisplayObjectContainer with a scaled size of 2,2 (200%) with the filter using the same scaling...the filter is unable to match the scaled size of the container it is applied to.

This seems rather limiting.
I noticed that example 15 (the filter example) bypasses this issue by default because the rendered content is stretched to the window size.
How this came about:
I was investigating #639, specifically the fact that Pixi.js already contains a filter called "AlphaMaskFilter", which seemed like it could achieve what I was attempting for that issue.
This filter is not in the filter examples and the documentation for it is incorrect...it talks about the DisplacementFilter instead.
Any input on this is helpful as it will be useful for understanding what intentions I should have when using filters :)

We are adding local-space as an option for filters in v3.

@englercj Sounds good, looking forward to it! :)

v3 now uses a sprite as a displacement map source. Works much more intuitively now! enjoy :+1:


Update sbt-typelevel to 0.4.4

Updates org.typelevel:sbt-typelevel from 0.4.3 to 0.4.4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "sbt-typelevel" } ]

labels: sbt-plugin-update, early-semver-minor, semver-spec-patch, commit-count:n:2

Uh oh 😕  This is https://github.com/typelevel/sbt-typelevel/issues/140. You can skip this update for now.

Superseded by #501.


⚠ Bofrost.lu has degraded performance

In 096e79e, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 4865 ms

Resolved: Bofrost.lu performance has improved in 518b245.


New release?

We have some bug fixes, new features, and QoL improvements. I think we should cut a new release. I believe it would be a point release.

By looking at the CHANGELOG.md it seems we have more changes than both of the previous releases including new features, perhaps this would be better suited as a minor release than a patch release such as v0.12.0?


refactor/move-prompts-to-jinja-templates

Purpose
This pull request addresses the request made by @pamelafox in #2123 to refactor the code for improved prompt management.
All prompts are now stored in a separate folder using .jinja files. This makes it easier to manage and update prompts across the application.
Does this introduce a breaking change?
[ ] Yes
[ X ] No

Does this require changes to learn.microsoft.com docs?
This repository is referenced by this tutorial
which includes deployment, settings and usage instructions. If text or screenshot need to change in the tutorial,
check the box below and notify the tutorial author. A Microsoft employee can do this for you if you're an external contributor.
[ ] Yes
[ X ] No

Type of change
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ X ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

Code quality checklist
See CONTRIBUTING.md for more details.

[ ] The current tests all pass (python -m pytest).
[ ] I added tests that prove my fix is effective or that my feature works
[ ] I ran python -m pytest --cov to verify 100% coverage of added lines
[ ] I ran python -m mypy to check for type errors
[ ] I either used the pre-commit hooks or ran ruff and black manually on my code.

Additional Notes
This refactoring aims to improve the overall code structure without changing functionality. It should make the codebase more maintainable and easier to work with for future development.

Thank you! My main suggestion is that we keep few shots as JSON files, while still keeping the nice organization into separate folder.

I’ve incorporated the above comments in the latest commit. Thanks for taking the time to review!

@jeannotdamoiseaux Thanks for the changes!
To give us one more idea for how we could approach this, I've put together this PR: https://github.com/Azure-Samples/azure-search-openai-demo/pull/2178
It uses a file format called Prompty that was developed by Microsoft but is intended to be generically useful.
I'm 50/50 on which approach is best, would love to get some more feedback from the community on these branches. See my comments in that PR about benefits/drawbacks.
CCing recent contributors:
@bnodir @zedhaque @cforce @fujita-h @EMjetrot

@jeannotdamoiseaux Thanks for the changes! To give us one more idea for how we could approach this, I've put together this PR: #2178 It uses a file format called Prompty that was developed by Microsoft but is intended to be generically useful. I'm 50/50 on which approach is best, would love to get some more feedback from the community on these branches. See my comments in that PR about benefits/drawbacks.
CCing recent contributors: @bnodir @zedhaque @cforce @fujita-h @EMjetrot

My suggestion would be to move all prompts to a separate folder using Jinja files first to create a clearer overview and better structure. Once that’s in place, we could consider using Prompty later if it aligns well with the project's needs. For now, though, I don’t see this as something that would significantly push my project forward.

Thanks for the PR! Based on the high Package Health Score of Jinja2, I favor sticking with it over Prompty, which has a lower score (details here). Jinja2’s stability and support make it a safer choice for long-term use.
That said, I’m open to hearing more about specific cases where Prompty might offer clear advantages.
Looking forward to hearing others' feedback on this!
CC: @zedhaque @cforce @fujita-h @EMjetrot

I understand that Jinja2 and Prompty are being compared as approaches to organizing prompts.
Jinja2 has a proven track record as a template engine for Flask, Django, etc., and I think it is a very good option.
On the other hand, Prompty is a tool designed for LLM apps, so I think it is suitable for this project.
This decision is very difficult. I think Jinja2 is sufficient as an approach to achieve the goal of organizing the current prompts. If I were forced to make this choice for my own production project, I would definitely choose Jinja2.
However, considering that this project is "Azure Samples", I think it is better to be adventurous, so I will vote for Prompty.


Added the view own infractions claim to allow for people to see their…

… self claims

implements #540


Package name with dots in it causes failure

» letmegrpc --addr=localhost:65021 --port=8080 -proto_path ~/go/src/content_api/domains/border/category ~/go/src/content_api/domains/border/category/category.proto

2016/09/05 19:03:53 panic: runtime error: index out of range

goroutine 1 [running]:
panic(0x55e280, 0xc42000a180)
        /usr/lib/go/src/runtime/panic.go:500 +0x1a1
github.com/gogo/letmegrpc/html.(*html).generateFormFunc(0xc4200f3570, 0xc4200efd82, 0xe, 0xc4200134a0)
        /home/u/go/src/github.com/gogo/letmegrpc/html/html.go:93 +0x4e1
github.com/gogo/letmegrpc/html.(*html).Generate(0xc4200f3570, 0xc4200da1b0)
        /home/u/go/src/github.com/gogo/letmegrpc/html/html.go:169 +0x2dce
github.com/gogo/protobuf/protoc-gen-gogo/generator.(*Generator).generatePlugin(0xc42009e000, 0xc4200da1b0, 0x63c7e0, 0xc4200f3570)
        /home/u/go/src/github.com/gogo/protobuf/protoc-gen-gogo/generator/helper.go:330 +0x142
github.com/gogo/protobuf/protoc-gen-gogo/generator.(*Generator).GeneratePlugin(0xc42009e000, 0x63c7e0, 0xc4200f3570)
        /home/u/go/src/github.com/gogo/protobuf/protoc-gen-gogo/generator/helper.go:309 +0x22d
main.main()
        /home/u/go/src/github.com/gogo/letmegrpc/protoc-gen-letmegrpc/main.go:59 +0x32e
--letmegrpc_out: protoc-gen-letmegrpc: Plugin failed with status code 2.
 exit status 1

Seems like it happens if package name has dots in it.

Good to know.
Interested in contributing a fix?

@awalterschulze Yeap, I'll look into it.

That will be great thanks.
Just be warned this is some of the worst code I have ever written.
Unfortunately it works quite well.

There is a different failure right now.
Assume this command:
protoc --letmegrpc_out=. -I. tmp.proto

Building this file works:
# tmp.proto
syntax = "proto3";
package com;
message Blah {
};
service Asd {
  rpc Foo(Blah) returns (Blah);
}

Building this file does not:
# tmp.proto
syntax = "proto3";
package com.example;
message Blah {
};
service Asd {
  rpc Foo(Blah) returns (Blah);
}

Error produced:
2017/02/23 00:21:24 protoc-gen-gogo: error:can't find object with type .com.example
--letmegrpc_out: protoc-gen-letmegrpc: Plugin failed with status code 1.

Error still talks about com.example even if I change the package name to com.example.project.

Its a bug that concerns the dot character
On Thu, 23 Feb 2017, 01:22 Ivan Vučica<EMAIL_ADDRESS>wrote:

There is a different failure right now.
Assume this command:
protoc --letmegrpc_out=. -I. tmp.proto
Building this file works:
tmp.proto
syntax = "proto3";package com;message Blah {
};service Asd {
rpc Foo(Blah) returns (Blah);
}
Building this file does not:
tmp.proto
syntax = "proto3";package com.example;message Blah {
};service Asd {
rpc Foo(Blah) returns (Blah);
}
Error produced:
2017/02/23 00:21:24 protoc-gen-gogo: error:can't find object with type .com.example
--letmegrpc_out: protoc-gen-letmegrpc: Plugin failed with status code 1.
Error still talks about com.example even if I change the package name to
com.example.project.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gogo/letmegrpc/issues/22#issuecomment-281849697, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABvsLUKwPdnrAnFa2WOn44vgvYWpXtvwks5rfNFJgaJpZM4J1MLz
.

That much is obvious both from my report and this bug's title, no?

Yes thats true :)
I'll look into this as soon as I get some time.
On Thu, 23 Feb 2017 at 10:51 Ivan Vučica<EMAIL_ADDRESS>wrote:

That much is obvious both from my report and this bug's title, no?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gogo/letmegrpc/issues/22#issuecomment-281946122, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABvsLS2_3f-vO5220iW1DvjncRXbGGdgks5rfVaOgaJpZM4J1MLz
.

Thanks! 😂
On February 23, 2017 9:54:11 AM GMT+00:00, Walter Schulze<EMAIL_ADDRESS>wrote:

Yes thats true :)
I'll look into this as soon as I get some time.
On Thu, 23 Feb 2017 at 10:51 Ivan Vučica<EMAIL_ADDRESS>wrote:

That much is obvious both from my report and this bug's title, no?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gogo/letmegrpc/issues/22#issuecomment-281946122,
or mute
the thread

https://github.com/notifications/unsubscribe-auth/ABvsLS2_3f-vO5220iW1DvjncRXbGGdgks5rfVaOgaJpZM4J1MLz

.

--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/gogo/letmegrpc/issues/22#issuecomment-281946844

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Finally got some time.
Fixed
https://github.com/gogo/letmegrpc/commit/2d46be80c34f4f5e7dafb7db6be3880ccb3f4193


Setting for default model

Now that you have different LLM's like o1-preview, cloude-sonnet, ... available, it would be great to be able to set a default model in the settings of VS Code. Currently, I have to re-select if on each start.

We don't plan to add a setting as this is treated as view state, but I do not have re-select on each start.

I select Claude
I reboot VS Code
Claude is still selected.

Are you not seeing this?

No ... that's why I introduced this request ... on my VS Code after closing and opening the default model is always GPT 4o ... I have to re-set it all the time, which is very annoying

@roblourens Not sure if that is expected or not. it is not what I'm seeing 🤔

@roblourens Not sure if that is expected or not. it is not what I'm seeing 🤔

can i provide some debug info? instruct me on how to collect it

Hm, do you have multiple VS Code windows open?

@roblourens After executing "F1 > Reload Windows" once, the selected model (Claude) remained. Now it stays selected even if I "x"-close VS Code and re-open it. That resolved the issue


Joe test

John, pls review.

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: globalization/index.yml
100
100
100
100

:white_check_mark: globalization/input/japanese-ime.md
92
100
83
79

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: globalization/index.yml
94
100
70
100

:white_check_mark: globalization/input/japanese-ime.md
92
100
83
79

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: globalization/index.yml
94
100
70
100

:white_check_mark: globalization/input/japanese-ime.md
93
100
94
79

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: globalization/index.yml
94
100
70
100

:white_check_mark: globalization/input/japanese-ime.md
93
100
94
79

:white_check_mark: globalization/localization/localization-overview.md
79
100
91
48

:white_check_mark: globalization/methodology/global-product-delivery.md
85
100
85
73

:white_check_mark: globalization/methodology/international-design.md
79
100
65
59

:white_check_mark: globalization/methodology/software-internationalization.md
94
100
93
77

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: globalization/index.yml
94
100
70
100

:white_check_mark: globalization/input/japanese-ime.md
93
100
94
79

:white_check_mark: globalization/localization/localization-overview.md
79
100
88
48

:white_check_mark: globalization/methodology/global-product-delivery.md
85
100
85
73

:white_check_mark: globalization/methodology/international-design.md
79
100
65
59

:white_check_mark: globalization/methodology/software-internationalization.md
94
100
93
77

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: globalization/index.yml
94
100
70
100

:white_check_mark: globalization/input/japanese-ime.md
93
100
83
83

:white_check_mark: globalization/localization/localization-overview.md
79
100
88
48

:white_check_mark: globalization/methodology/global-product-delivery.md
87
100
92
73

:white_check_mark: globalization/methodology/international-design.md
79
100
65
59

:white_check_mark: globalization/methodology/software-internationalization.md
94
100
93
77

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum total score of 80 is required.
Select the total score link to review all feedback on clarity, consistency, tone, brand, terms, spelling, grammar, readability, and inclusive language. You should fix all spelling errors regardless of your total score. Fixing spelling errors helps maintain customer trust in overall content quality.

Article
Total score(Required: 80)
Words + phrases(Brand, terms)
Correctness(Spelling, grammar)
Clarity(Readability)

:white_check_mark: globalization/index.yml
94
100
70
100

:white_check_mark: globalization/input/japanese-ime.md
93
100
83
83

:white_check_mark: globalization/localization/localization-overview.md
79
100
88
48

:white_check_mark: globalization/methodology/global-product-delivery.md
87
100
92
73

:white_check_mark: globalization/methodology/international-design.md
80
100
65
60

:white_check_mark: globalization/methodology/software-internationalization.md
94
100
93
77

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx