Wither Boss drops 9 Million Coins

It has come to my attention that my players are grinding wither bosses. They seem to drop 9 Million coins every 10 kills or so. The 10 kills could be bad luck as I checked my config and it is still set to default (set to 1/4 kill to drop ratio). My max coin drop is set to the default ~36 or so as well.
Not only to fixing this bug, but could we also have an option to only drop the lowest coin value? This could help limit any further bugs like this as well. Although less fun :\
http://i.imgur.com/MWkZxZQ.png

The one out of ten might be due to random numbers not being truly random. I'll see if I can improve that.
What would be a good amount to drop for withers? When I wrote the formula for dropping coins based on health, I didn't expect wither farming. I was thinking about the ender dragon and it being a one time drop.
Right now, the formula is:
int dropped = (int) (randomDropValue * Math.pow((health / 20), 4) * (event.lootingLevel + 1));
This results in up to 7,290,000 being dropped for the 300 health a wither has when a looting III item is used. Up to 1,822,500 with an unenchanted kill
What about switching to a linear drop formula so a mob with 200 health drops 10x a mob with 20 health? Keeping the random drop value and the looting multiplier. This would put the wither boss drops at up to 540 (2,160 with looting III).
I could add a configurable 1000x multiplier for the ender dragon. It would drop up to 360,000 by default (1,440,000 with looting III)

Thats it indeed!
I love the idea of Looting III changing the coin drop outcome. We should keep that but do more of a linear drop formula. I feel that dropping a max of 10 coins per hp seems fair as long as the drop-rate is still accounted for.
As for specific mobs such as the Ender Dragon, perhaps it could be listed under the config as "creatures always-drop" in which the section could be toggled as well as configured.
I know that everyone does something different for economies and customization is key. For a server like mine, I welcome this mod as it creates a slowly inflating economy. A fixed monetary system only works if people always keeps money flowing and continue to play on the server (every never-returning player removes their cash from the economy). So I would probably still keep Ender Dragon drops rather low. Perhaps a 100% 10k drop to accompany the ender-egg. This way parties can at least split loot. Other than this, a linear drop table would ensure a steady supply of coins into the game.
Now and idea: detect if single-player (or if an option is selected in settings?) in which the drops would be the "int dropped = (int) (randomDropValue * Math.pow((health / 20), 4) * (event.lootingLevel + 1));" formula. This high-coin formula would be more well suited in a single-player environment where hoarding coins is fun :).
I know I'm verbose. Sorry about that :P

I've changed the mob drop handler to drop directly proportional to the mob health. I also added a multiplier for the ender dragon and changed it so the dragon kill always drops coins. The default settings drop up to 240k with no enchantment. Fortune III will drop up to 1M coins.


trouble in importing pydantic_output_parser from langchain

Describe the bug
Once ragas is installed I want to import it and I got an error on the import of pydantic output parser from langchain.
Ragas version: 0.1.6
Python version: 3.10
LangChain version: 0.1.14
Code to Reproduce
import ragas
Error trace
`---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
Cell In[6], line 1
----> 1 import ragas
File /anaconda/envs/azureml_py310_langchain/lib/python3.10/site-packages/ragas/init.py:1
----> 1 from ragas.adaptation import adapt
2 from ragas.evaluation import evaluate
3 from ragas.run_config import RunConfig
File /anaconda/envs/azureml_py310_langchain/lib/python3.10/site-packages/ragas/adaptation.py:7
5 from ragas.llms import llm_factory
6 from ragas.llms.base import BaseRagasLLM, LangchainLLMWrapper
----> 7 from ragas.metrics.base import MetricWithLLM
10 def adapt(
11     metrics: t.List[MetricWithLLM],
12     language: str,
13     llm: t.Optional[BaseRagasLLM] = None,
14     cache_dir: t.Optional[str] = None,
15 ) -> None:
16     """
17     Adapt the metric to a different language.
18     """
File /anaconda/envs/azureml_py310_langchain/lib/python3.10/site-packages/ragas/metrics/init.py:1
----> 1 from ragas.metrics._answer_correctness import AnswerCorrectness, answer_correctness
2 from ragas.metrics._answer_relevance import AnswerRelevancy, answer_relevancy
3 from ragas.metrics._answer_similarity import AnswerSimilarity, answer_similarity
File /anaconda/envs/azureml_py310_langchain/lib/python3.10/site-packages/ragas/metrics/_answer_correctness.py:10
7 import numpy as np
8 from langchain_core.pydantic_v1 import BaseModel
---> 10 from ragas.llms.output_parser import RagasoutputParser, get_json_format_instructions
11 from ragas.llms.prompt import Prompt
12 from ragas.metrics._answer_similarity import AnswerSimilarity
File /anaconda/envs/azureml_py310_langchain/lib/python3.10/site-packages/ragas/llms/output_parser.py:6
3 import typing as t
5 from langchain_core.exceptions import OutputParserException
----> 6 from langchain_core.output_parsers import PydanticOutputParser
7 from langchain_core.pydantic_v1 import BaseModel
9 from ragas.llms import BaseRagasLLM
ImportError: cannot import name 'PydanticOutputParser' from 'langchain_core.output_parsers' (/anaconda/envs/azureml_py310_langchain/lib/python3.10/site-packages/langchain_core/output_parsers/init.py)`
Expected behavior
I expect the import to be without any errors. A quick fix would be to change the import in the file: ragas/tree/main/src/ragas/llms/output_parser.py
from
from langchain_core.output_parsers import PydanticOutputParser
to
from langchain.output_parsers import PydanticOutputParser

hey @kluskaj that is very strange - could you share which version of langchain core you have too?
try updating is as well?

Hey @jjmachan,
The version of langchain_core was: 0.1.22
Updating to 0.1.40 indeed solved the problem.
Sorry, should I have tried that...

updating langchain-core did not resolve the problem for me:
Python version: 3.8
Ragas version==0.1.7
langchain==0.1.1
langchain-community==0.0.16
langchain-core==0.1.40
langchain-openai==0.0.6

We're getting this too

I have the same problem

seems like we have to pin the langchain-core version for this as the solution
will do that

Updating langchain_core, doesnt help

this is ok:
ragas==0.1.8
langchain == 0.1.20
langchain-community ==0.38
langchain-core==0.1.52
langchain-openai == 0.0.8
langchain-text-splitters==0.0.2
langsmith == 0.1.77

closing this now 🙂


Use master branch for production deployment

This should fix the problem with production deployments.

@Zhanybek This PR is ready for review. Let me know if there are any questions.

@kz-userstat Actually this one was intended to be merged. Could you try pressing "Re-open pull request", and then pressing "Merge pull-request"?


Country redirect: Handle special language cases

Don't replace - with _ in the normalized language-variable because
the HTTP_ACCEPT_LANGUAGE-languages use - and the variable is
splitted anyway. Also, the array TO_FULL_INVERTED uses - in the
keys, so the special cases are now used.
Tested locally with pt-BR (Portuguese/Brazil in Firefox), fixes #60

I'm guessing there was a reason I did it this way, but I can't remember... I'll deploy this, thanks.


Fix reference creation when two types are provided

Previously the type from param definition would be used to documentation even if we try to override it in the documentation hash.
It caused Swagger UI to render, for example, "Unknown Type: Color" instead of using the provided entity.
It terms of code, before this change we would return something like this:
{ color: { type: 'Color' }
instead of:
{ color: { '$ref' => 'ColorEntity' }
if Color is not inherited from Grape::Entity
Having different types can be useful when two different classes are used for parsing and presenting an attribute.
E.g. the input format for Base64 File can be represented as a Hash (content, content_type and filename), whereas the type after parsing can be ActionDispatch::Http::UploadedFile.
In the current situation the solution to this problem is to put coercion methods to the same entity and specify type only for the param without using documentation.

thanks @bikolya


terraform_0_14: 0.14.9 -> 0.14.10

Motivation for this change
https://github.com/hashicorp/terraform/releases/tag/v0.14.10
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 118755 run on x86_64-darwin 1

1 package built:

terraform_0_14

Result of nixpkgs-review pr 118755 at 03bd054f run on aarch64-linux 1

1 package built successfully:

terraform_0_14

4 suggestions:

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/applications/networking/cluster/terraform/default.nix:155:17:
    |
155 |     patches = [ ./provider-path.patch ];
    |                 ^

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/applications/networking/cluster/terraform/default.nix:144:9:
    |
144 |         (fetchpatch {
    |         ^

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/applications/networking/cluster/terraform/default.nix:163:17:
    |
163 |     patches = [ ./provider-path.patch ];
    |                 ^

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/applications/networking/cluster/terraform/default.nix:143:9:
    |
143 |         ./provider-path.patch
    |         ^


How to 'port build.cs to build.hx'

I don't know all haxe syntax but I'm very interesting to this project, but please give me an example of porting .build. Cause I'm stuck at that process. Can we use tool ? If not, how ?
Thank you.

Also, what's the supported UE version?

Thank you for a quick reply. :-)
I'm trying on 4.11.

Yes indeed for the latest master, the supported version is Unreal 4.11 with Haxe 3.2.1 . As for your question, take a look at https://github.com/proletariatgames/UE4Hx-Tests/blob/master/Source/HaxeUnitTests/HaxeUnitTests.Build.hx and see if that helps you. If not, feel free to reopen the issue

Also I plan to have a good example project and better getting started docs ready for the WWX talk

Thank you very much, I'll try your suggestion. ☺
It would be better if you add the UE4Hx-Tests link to the README.md.
by the way. Goodluck at WWX !

@waneck if you come to IRC, I'll annoy you about how to get started with this thing :-P

Thank you :)
BTW, you can ignore all the Sys.getEnv / FileSystem tests when writing your own file

Sorry to troubling you guys again.
I've successed the build.hx process. I created AMyActor.hx in the static folder and copy the example from README.md and compile it in UE4, And got this.
/AMyActor.hx:5: lines 5-23 : Unreal Glue Extension: Do not extend Unreal types on the global namespace. Use a package
here's the full log.
fulllog.txt
Thank you.

I'm sorry, you need a package for any class that extends unreal stuff. I plan to lift that limitation soon

So I've to put it in a folder ?

Sorry. I'll try this http://old.haxe.org/ref/packages
Thank you


edit requirements

Add requirements for GitHub Actions. Manual build work only for integration tests.
Integration tests were rewrite for reduce time working.
Locally integration tests worked as well as GitHub Actions in 15-20 minutes.
Three main types of functions are tested in integration tests:

examples
cases
metrics

It seems to me that tests for examples and cases can be reduced by simply checking their performance and not running the composer on them.
I also think it is worth adding tests for metrics on other datasets in the future, because only one test for the framework's performance metric is used (comparison with baseline and xgboost).

I also think it is worth adding tests for metrics on other datasets in the future, because only one test for the framework's performance metric is used (comparison with baseline and xgboost).

Да, разумно. Можешь отдельный issue создать на эту тему, чтобы не забыть.


Emit lookup stat correctly

Previously the lookup stat was emitted from the event-handler inside of ringpop.go when a LookupEvent was emitted. However, the lookup-event is emitted on ringpop itself so it's internal event-handler isn't triggered.

Coverage increased (+0.3%) to 94.64% when pulling 166a8e5cd38fb21d971143d6236b6fc09e476294 on menno/emit-lookup-stats into 5ac47e8ed00bb2960de5a42035f342747e257fa0 on dev.

Coverage increased (+0.2%) to 94.593% when pulling 166a8e5cd38fb21d971143d6236b6fc09e476294 on menno/emit-lookup-stats into 5ac47e8ed00bb2960de5a42035f342747e257fa0 on dev.

Coverage increased (+0.1%) to 94.468% when pulling 7e60fd3c2f9948ac8fb0e49e9db7969b305d8fb4 on menno/emit-lookup-stats into 5ac47e8ed00bb2960de5a42035f342747e257fa0 on dev.

Just one question about event from LookupN. Otherwise, lgtm. I've double checked that there are no other events that are processed in Ringpop HandleEvent and emitted form Ringpop itself.

Coverage increased (+0.3%) to 94.68% when pulling 38f3d7322da53461f73cbd5ebd7f62c3b9b3e6a6 on menno/emit-lookup-stats into 5ac47e8ed00bb2960de5a42035f342747e257fa0 on dev.

Coverage increased (+0.3%) to 94.664% when pulling a98e286d6ebc31ca6707f09d6cb9249c3d6553e9 on menno/emit-lookup-stats into 5ac47e8ed00bb2960de5a42035f342747e257fa0 on dev.

Coverage increased (+0.6%) to 94.851% when pulling f4397b7cf3a725ba3f1865b678c3a8f304882964 on menno/emit-lookup-stats into 3b513c714b0dffcd96aef8e0c90da469fab99200 on dev.

It's better to rebase on top of origin/dev rather than merge it to your branch. Could you do that?

LGTM

Coverage increased (+0.6%) to 94.781% when pulling eb5422f1a04a358f240bc945fc61bf830f4dce28 on menno/emit-lookup-stats into 3b513c714b0dffcd96aef8e0c90da469fab99200 on dev.

lgtm


国产音乐播放器为啥菜单是英文呢？

By this way u could learn English.

I have no problem with all this in English. 🙃
and I like it in English, maybe its same with the dev.

因为很多UI改成中文了会没有英文好看🤣🤣

no very difficult word, and the author may like use English in coding like me.


Error while deploying to goerli with truffle

The verify is not working. It seems to be an error in the nomiclabs plugin https://github.com/NomicFoundation/hardhat/issues/2247
I updated all the dependencies, truffle, npm node and all the nomiclabs plugins.
Any idea?
`Error in plugin @nomiclabs/hardhat-etherscan: The contract verification failed.
Reason: Fail - Unable to verify
NomicLabsHardhatPluginError: The contract verification failed.
Reason: Fail - Unable to verify
at SimpleTaskDefinition.verifySubtask [as action] (/Users/ronaldo/projects/ndj/genesis-note/genesis-note-nft-contracts/smart-contract/node_modules/@nomiclabs/hardhat-etherscan/src/index.ts:350:9)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Environment._runTaskDefinition (/Users/ronaldo/projects/ndj/genesis-note/genesis-note-nft-contracts/smart-contract/node_modules/hardhat/src/internal/core/runtime-environment.ts:308:14)
at async Environment.run (/Users/ronaldo/projects/ndj/genesis-note/genesis-note-nft-contracts/smart-contract/node_modules/hardhat/src/internal/core/runtime-environment.ts:156:14)
at async Environment._runTaskDefinition (/Users/ronaldo/projects/ndj/genesis-note/genesis-note-nft-contracts/smart-contract/node_modules/hardhat/src/internal/core/runtime-environment.ts:308:14)
at async Environment.run (/Users/ronaldo/projects/ndj/genesis-note/genesis-note-nft-contracts/smart-contract/node_modules/hardhat/src/internal/core/runtime-environment.ts:156:14)
at async main (/Users/ronaldo/projects/ndj/genesis-note/genesis-note-nft-contracts/smart-contract/node_modules/hardhat/src/internal/cli/cli.ts:272:7)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.`
Here is how to get the version numbers requested below:

project version: is the one you downloaded or cloned from the repo
operating system and version: https://www.google.com/search?q=how+to+know+know+operating+system+version
NodeJS version: node --version
NPM version: npm --version
Yarn version: yarn --version
Truffle version: truffle --version
-->

General information

Description
Value

Project version
X.Y.Z

Operating system and version
???

NodeJS version
X.Y.Z

NPM version
X.Y.Z

Yarn version
X.Y.Z

Truffle version
X.Y.Z

Describe the bug
A clear and concise description of what the bug is.
How to Reproduce
Steps to reproduce the behavior (please provide a reproducer project for complex bugs):

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Ahh, and yes, I'm using the ethereumTestnet pointing to goerli.
In this error I was using truffle dashboard

gm @rrigoni, chiming in from Etherscan. We did have our Goerli node go down around this time causing contract verifications to remain as pending or failing.
Do try this again and if it works for you, otherwise we'll need to look into other possibilities!

Thank you @0xV4L3NT1N3, for taking time to reply here. I really appreciate the helpful information.

This was an issue with Goerli being unstable.

Thank you @rrigoni for taking time to update on this. Glad to hear it was finally solved.


[5.2] Update paginator

Several minor refactorings of paginators.

CS fix
Implement Htmlable in AbstractPaginator so people can use {{ $paginator }} without calling ->render() as it was possible before.
Make sure __toString() and toHtml() casts render result to string to avoid errors.
Implement JsonSerizlizable and use jsonSerialize() method in toJson() conversion.

Please rebase.

Please make this 2 PRs too.

"Implement JsonSerializable in paginators" and "	Use paginators as Htmlable".

Done.


Range slider component

Hi everyone,
I am looking for a range slider component, on the lines of "vue-slider-component" or a multiselect version of input type = range. I have not been able to find anything yet. Any pointers on this, given the conventional input type = range is not supported by weex.
Thanks!

This PR/issue doesn't received response since Weex migrated to Apache two years ago and this repository is no longer active yet.
Feel free to ask question in new repository and thanks for your contribution.

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.


Prevent GitHub API call for install docker-compose

The GitHub API has rate limits.

Good suggestion. There's a couple other spots that could get updated as well.


Fix stack overflow from massive MaxWidth chains during width inference

Fixes ucb-bar/chisel3#420
Also added a test, would be better as a Chisel test

Removed huge file, will add test to Chisel instead


Run hooks over commit range

Is it possible to run the overcommit hooks over a specific range of commits?
Because the overcommit --run – for CI integration – does only run pre-commit hooks.
It would be nice if we can check the commits additionally in our CI/CD pipeline because this helps to enforce specific rules for creating the commit messages and developers can't skip them.
Since I do not know ruby very well, would it be easy to implement such a feature?

This is not currently possible with Overcommit today.
You could implement this by using pre-receive hooks on GitHub (or whatever Git hosting service you use) to prevent pushing of commits not adhering to policy for the repos/branches where you want to enforce a convention for commit messages.
In terms of Overcommit supporting this in general, I'm not sure what this would look like. The nature of hooks like commit-msg is that they are run at a point in the Git workflow where there are certain assumptions about your environment and the state of your Git repo which may not be true when run via something like overcommit --run. Not only do you need to add support for --run to support commit-msg hooks, but you also need to include some way for the --run feature to only inspect specific commit ranges, which might not make sense in all contexts.
Would not be opposed to a well-tested pull request adding this functionality.

I've "added" this functionality via our CI pipeline, where this bash script runs over all (new) commits:
#!/bin/bash -
#===============================================================================
#
#          FILE: overcommit_run.sh
#
#         USAGE: ./overcommit_run.sh
#
#   DESCRIPTION: Runs overcommit hooks MANUALLY over the following commit range:
#                ${CI_DEFAULT_BRANCH}..${CI_COMMIT_REF_NAME}
#
#       OPTIONS: ---
#  REQUIREMENTS: overcommit, git
#          BUGS: ---
#         NOTES: ---
#        AUTHOR: Francesco Emanuel Bennici (l0nax<EMAIL_ADDRESS>#  ORGANIZATION: FABMation GmbH
#       CREATED: 06/05/2020 10:32:03 AM
#      REVISION:  ---
#===============================================================================

set -eo nounset                              # Treat unset variables as an error and exit on non-zero return

#########################
##        const        ##
#########################

## COMMITS_FILE contains the (new) commits of the current merge request.
COMMITS_FILE="/tmp/commits_list"

COMMIT_MSG="/tmp/commit_msg"

## IS_FAILED is set to true if a hook returned a non-zero exit code.
IS_FAILED=false

## FAILED_COMMITS contains a list of all commits where the hook return >0.
FAILED_COMMITS=()

##########################
##        Code         ##
##########################

## get_commits gets the new commits and saves them into ${COMMITS_FILE}.
get_commits() {
  OVERCOMMIT_DISABLE=1 git pull origin ${CI_DEFAULT_BRANCH}
  OVERCOMMIT_DISABLE=1 git log --format='%H' origin/${CI_DEFAULT_BRANCH}.. > ${COMMITS_FILE}
}

## get_commit_msg saves the commit Subject and body into ${COMMIT_MSG}
##
## Arguments:
##    $1: SHA1 hash of the commit
get_commit_msg() {
  git show --no-patch --pretty=format:"%B" ${1} > ${COMMIT_MSG}
}

## run_commit-msg runs the commit-msg hook
##
## Arguments:
##    $1: SHA1 hash of the commit
run_commit-msg() {
  ## we need to handle the error if the hook fails so we can process ALL commits
  ./.git/hooks/commit-msg ${COMMIT_MSG} || { IS_FAILED=true; FAILED_COMMITS+=("${1}"); }
}

## print_commit_info prints commit information as one-liner in the following format: "* %H (%an) - %s"
##
## Example:
##    * be12b0948e6b2e7076fc8c0f588040f8dad0e7cc (Emanuel Bennici) - CI: Configure git user in overcommit job
##
## Arguments:
##    $1: SHA1 hash of the commit
print_commit_info() {
  git show --no-patch --pretty=format:"* %H (%an) - %s" ${1}
}

### loop over commits and start processing them
get_commits

for i in $(cat ${COMMITS_FILE}); do
  ## get commit message
  get_commit_msg ${i}

  echo "+--------------------------------------------------+"
  echo "|      ${i}    |"
  echo "+--------------------------------------------------+"
  echo " "

  ## skip if starts with "Merge " or "Revert "
  title=$(cat ${COMMIT_MSG} | tail -n 1)
  case "${title}" in
    Merge*)
      echo "This is a Merge commit! skipping..."

      ;;
    Revert*)
      echo "This is a Revert commit! skipping..."

      ;;
    *)
      ### stage #1: commit-msg
      run_commit-msg ${i}

      ;;
  esac

  echo -e "\n \n "
done

### ==> END: clean up and report

## exit with 1 if a hook has failed
if [ "$IS_FAILED" = true ]; then
  echo -e "\n \n \nThe following commits did not pass our checks"
  echo "============================================="

  for i in "${FAILED_COMMITS[@]}"; do
    print_commit_info ${i}
  done

  exit 1
else
  echo -e "\n \n \nAll checks passed!"
fi

We use GitLab as our Git server, for anyone who is interreted in adding this to his own pipeline, here the pipeline definition:
overcommit:
  stage: .pre
  image: docker.io/ruby:2.7.1-alpine3.11
  extends: .qa:rules:not-default-refs
  variables:
    ## do not shallow any commits
    GIT_DEPTH: 0
    OVERCOMMIT_COLOR: 1
  rules:
  before_script:
    - gem install overcommit
    - apk add git bash
    - git config --global user.email "XXXXX"
    - git config --global user.name "XXXXX"
  script:
    - overcommit --sign
    - overcommit --install
    ## start check
    - ./.gitlab/ci/script/overcommit_run.sh

As you said, I also think that it will be difficult to implement such a feature into the code base of overcommit.
Thanks for your support @sds !
I will close this Issue since I don't think it will be implemented.


bootstrap classes are not working with native script components

I have the dependencies in my package.json
"dependencies": {
"@angular/common": "2.4.3",
"@angular/compiler": "2.4.3",
"@angular/core": "2.4.3",
"@angular/forms": "2.4.3",
"@angular/http": "2.4.3",
"@angular/platform-browser": "2.4.3",
"@angular/platform-browser-dynamic": "2.4.3",
"@angular/router": "3.4.3",
"nativescript-angular": "1.4.0",
"nativescript-theme-core": "~1.0.2",
"reflect-metadata": "~0.1.8",
"rxjs": "~5.0.1",
"tns-core-modules": "2.5.1"
}
Below snippet is inside my component app.component.html

The btn style is not reflecting when i run  this in IOS.
Here is the sample app:
sample.zip

I got the issue. I had to import in app.css as below by providing the full path
@import 'nativescript-theme-core/css/core.light.css';


handle removed children category container

Image you have a column with dynamic amount of columns.
When you decrease the column count the children container for the last column gets removed.
If that container had elements inside then these elements stay in the schema node as invisble artifacts.
If you increase the column count again these artifacts are again visible.
Proposal for handling:

delete the nodes of the deleted children container
move the nodes of the deleted children container to another still existing container

I think we should go with deleting the children because it is way easier as former doesn't easily know what other containers might be existing.


Problem with Always on Top option

Brief description of your issue
If the option is enabled,almost all windows that come from SytemInformer appear behind the main window so you have to either minimize the main window or move it
Basically the affected window don't appear with AlwaysOnTop status
Steps to reproduce (optional)
No response
Expected behavior (optional)
All windows should appear infront of the main window
Actual behavior (optional)
No response
Environment (optional)
No response

Duplicate of #200

The Always on Top bug fixes were blocked on #1572 and should be resolved later this week 👍


fully qualify objects

As it stands, objects do not need to specify a namespace which makes creating resources with the same name but in different namespaces a bit awkward. Since config keys cannot clash, the metadata.name must be explicitly set and the duplicate config name (i.e., example2 here) is now something arbitrary and ignored, e.g.,
{
  kubernetes.resources.pods = {
    example.metadata.namespace = "default";
    example2.metadata = {
      name = "example";
      namespace = "other";
    };
  };
}

Whereas we could treat an object's namespace in the same way we treat its name and it becomes something like:
{
  kubernetes.namespaces = {
    default.resources.pods.example = {};
    other.resources.pods.example = {};
  };
}

The new namespaces key is useful (as opposed to just kubernetes.${namespace}) to prevent clashing with a namespace named resources or helm, for example. And non-namespaced resources can remain defined in the old kubernetes.resources location.
{
  kubernetes = {
    namespaces.default.resources.pods.example = {};
    resources.persistentvolumes.example = {};
  };
}

Along these lines, it might also be useful to create a context key in order to move toward multi-cluster deployments.
{
  kubernetes.${context}.namespaces.${namespace}.resources = {};
}

So the full config, with unambiguous namespace and context, becomes:
{
  kubernetes.my-cluster = {
    kubeconfig = "/path/to/kubeconfig";
    namespaces.default.resources = {}; # namespaced
    resources = {};                    # non-namespaced
  };
}

This is a bit more verbose but I think it might be decent a step towards deterministic executions as it no longer relies on the user's environment to determine the current context/namespace (obviously we're still pulling arbitrary kubeconfig files as string values but those contain sensitive data so should be handled with a proper nix secrets manager).

How about using kubenix submodule for grouping resources into different namespaces? You should be able to set a default namespace per submodule instance. I can create an example of how to do this tomorrow.

Yeah, that could work! Still learning the ins and outs of (sub-)modules so would definitely appreciate an example :+1:

I think the code is here, not just that you can set the namespace per module, apparently you can also set k8s version. https://github.com/hall/kubenix/blob/main/modules/k8s.nix#L439

Thanks @matejc! For some reason I'd missed your comment here.
Will take a look at your config (along with the docs MR Adrian submitted) and give it a go. I'll leave this issue open for now but will close it if I don't run into any trouble.


ignore def with parameters

This is discussed in #77

Just had an after-merge-thought: do things still work with empty-parens defs? (def a(): A = ...)

Checked, works :)


update brew command

brew cask was deprecated according to this comment. Should be brew install.

Thank you.
I have several questions because I don't use macOS/homebrew:
Is --cask necessary, like here: 192fbd8450058deb5e70aa1b9bfec3637b5c5e72 (#2004)
What is the latest openjdk version available? For consistency, could it be changed from 8 to 11?
(see f8524a2be738e6471ed2e48265f2663d8c21c0be and 7b51a0313ed9423f9252108fa573af68c11e6a2c)

Isn't --cask necessary?

No, for now there is no --cask option anymore.

What is the latest openjdk version available?

For now, the latest openjdk is version 16. However we can use openjdk version 8 LTS or version 11 LTS.

I rebased/squashed.
Is this commit ok for you d50c678a5f9174b6ba99b27bed8faa789ed5e070?
I also added 2812de8a9a0f20fa17126924407ecb6f613ac7e4 after your commit, is it ok?
(They are not merged yet, I'll merge after your confirmation.)

Yes. It's ok for me.

Thank you. Merged into master.


@match (Regex) suggestion

Hello, I have a suggestion for regex even if I don't know how tamper monkey would use it exactly, just tried => https://regexr.com/6kp6m like this you would need only 1 @match, isn't it better ?

I’m very fluent when it comes to regex but:
@match only works on the protocol/scheme, host, and pathname of a URL.
To trigger off the query parameters, you can either use @include or use @match and also test the URL yourself.
Note that the @match approach performs faster.
With @include, you can use a regex syntax. See, also Include and exclude rules.
But the documentation seems to discourage of include.
I think match is more readable to end users, I would switch to include + regex is the match gets unsustainable

Ah sad I didn't knew sorry :(
Is the verification performed only once or every time you load a new url ?


Apply AndroidJUnit4 runner and truth library for Unit Tests

Take a look at prefser project, where it was already done. Similar tests were also implemented in sqlbrite project.
References:

AndroidJUnit4 - Reference
AndroidJUnitRunner - User Guide
Google Truth

Done.


[inference] poor Promise.race inference

https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoAxnAdgZwC5gAmApjAIYCeYAvGABQC2OANGAG5kwCUNAfGFmJIACgCc4DAJY5idUcRxwYbYnzABvVGDAy8AFUkNicAK546dHtX7zFy2R26smXVAF9XGbPjAAHAII0RKSUdACMAAwRrABEZDgxrpi4BL4AQkEk5BThUax4oibEnmIS0sQAdKJk6LIA2gGs6QC6XBV4ABbEWHSOan0A1OycrqVSMlU19Y1+-q3tXT191sMwYEOOXEA
In contrast to TypeScript
http://www.typescriptlang.org/play/#src=const delay %3D <T>(ms%3A number%2C val%3A T)%3A Promise<T> %3D> new Promise(resolve %3D> {
  setTimeout(() %3D> resolve(val)%2C ms)%0D%0A%7D)%0D%0A%0D%0Aconst%20pA%20%3D%20delay(100%2C%20%22as%22)%0D%0Aconst%20pB%20%3D%20delay(100%2C%20true)%0D%0A%0D%0APromise.race(%5BpA%2C%20pB%5D).then(val%20%3D%3E%20val%20%2B%20val)%0D%0APromise.race(%5BpA%2C%20pA%5D).then(val%20%3D%3E%20val%20%2B%20val)%0D%0A

The issue can be mitigated by adding a generic to the function (like this), but imho it should be possible to infer this without it.


Breaking change in patch version 10.3.2 to 10.3.3

Describe the bug
The following used to work (in 10.3.2):
import SyntaxHighlighter, { registerLanguage } from 'react-syntax-highlighter/dist/prism-light';
import jsx from 'react-syntax-highlighter/dist/languages/prism/jsx';

registerLanguage('jsx', jsx);

Now I'm getting (in 10.3.3):
Module not found: Error: Can't resolve 'react-syntax-highlighter/dist/languages/prism/jsx' in
Module not found: Error: Can't resolve 'react-syntax-highlighter/dist/prism-light'

let me republish 10.3.2 sa 10.3.4 (those were cruft files and publish 11 as a new maor sorry about that)

@ryanthemanuel sorry about this, can you try 10.3.5

That worked. Thanks!

Thank you!

great to hear, sorry for the thrash


XSLT Intellisense

Is there some way to activate Intellisense for XSL/XSLT files?

There is an XML plugin on the marketplace, not sure if that covers XSL or not.
https://marketplace.visualstudio.com/search?term=XSL&target=VSCode&sortBy=Relevance

I've tried XML Tools but it doesn's seem to cover XSL.
The IntelliSense with XSL works fine in Visual Studio 2015.  It would be great to have the feature in VS Code too.

Closing as extension-canidate


Allow enums to be specific elements of a table and not the whole table

The Minetest engine give access to most of his API with the minetest global table (+300 fields).
Some functions except an enum, but the enum values are stored in the global table:
https://github.com/minetest/minetest/blob/master/doc/lua_api.txt#L5668-L5673
A way to make an enum out of specific values of a table should be added IMO.

I think you can just use ---@alias instead of ---@enum

I can't use something like this:
---Block emerge status constants (for use with `minetest.emerge_area`)
minetest.EMERGE_CANCELLED = 0

---Block emerge status constants (for use with `minetest.emerge_area`)
minetest.EMERGE_ERRORED = 1

---Block emerge status constants (for use with `minetest.emerge_area`)
minetest.EMERGE_FROM_MEMORY = 2

---Block emerge status constants (for use with `minetest.emerge_area`)
minetest.EMERGE_FROM_DISK = 3

---Block emerge status constants (for use with `minetest.emerge_area`)
minetest.EMERGE_GENERATED = 4

---@alias emerge_status
---| minetest.EMERGE_CANCELLED
---| minetest.EMERGE_ERRORED
---| minetest.EMERGE_FROM_MEMORY
---| minetest.EMERGE_FROM_DISK
---| minetest.EMERGE_GENERATED

Type names are undefined in that case.
I don't want to alias the real values, since these values are internal and should not be used directly.

---@alias emerge_status
---| `minetest.EMERGE_CANCELLED`
---| `minetest.EMERGE_ERRORED`
---| `minetest.EMERGE_FROM_MEMORY`
---| `minetest.EMERGE_FROM_DISK`
---| `minetest.EMERGE_GENERATED`

Thanks it works!!
Maybe this usecase could be added to the ---@alias  tag tooltip?


Updates to accessions.tsv (74308 new, 3787 removed, 1 changed) seqs downloaded 2021-09-06

Most of the lost sequences were caused by getting IMS-... IDs in BioSample from RKI in Germany that don't bear any resemblance to the GISAID names.  Previously the name matching was a little too loose (accepting just Germany/2021 as close enough) and the new IMS- names cause a name mismatch.  I'll see if I can get a better name mapping from RKI.
I have found some cases of too-loose name matching with identical WA-UW-# sequences and will be changing some of those in a future update (hopefully the next one).

Thank you as always Angie!
Always strange when the names start to deviate a lot - seems like more work on the side of the submitter. But RKI is sending quite a lot, so we could try to reach out, if you think it would help at all? Either to find out what their pattern is, or to see if they might be able to keep it more consistent? Let us know!

Sadly, AFAICT there is no pattern with the two sets of RKI IDs -- they are independent sets (IMS-<long hex/text strings> in ENA/INSDC/BioSample and https://github.com/robert-koch-institut/SARS-CoV-2-Sequenzdaten_aus_Deutschland vs. XX-RKI-Y-NNNN in GISAID, where NNNN is a serial number and I don't see any relationship between the NNNN serial number and the long IMS ID strings, although maybe I just haven't looked hard enough 😆).  Tantalizingly, SARS-CoV-2-Sequenzdaten_Deutschland.csv.xz has an alternate ID column, but when it's populated, it turns out to have 64-character hex strings.  🙃  Just what we needed, another set of IDs that are even longer and less human-readable!
I heard back from someone at RKI that they do plan to add the RKI IDs to BioSample, but due to staffing constraints, they won't have time for that until November.  In the meantime, I may just decide that when there is a 1-to-1 sequence identity with IMS- and -RKI- (as opposed to a set of identical sequences with multiple IMS-'s and multiple RKI's), they are the same, because there are ~150k RKI's and ~130k IMS's, so probably ~100k of those unambiguous matches.


French using new Spacy's language model

Spacy has a French model since 1.8.2 (https://spacy.io/docs/usage/models).
How hard would it be to support French in Rasa?

it should be as easy as setting "language": "fr", "spacy_model_name": "fr_depvec_web_lg" in your configuration. any issue with that?

That's good news! There is still a dependency on #284, right?

Since we removed entity training using spacy all together (one should use the ner_crf component instead), I don't think this should be an issue anymore. Didn't try it yet though.

I will this afternoon and I'll let you know here how it goes. Thanks

@znat that would be awesome, thanks.

@tmbo , when training (from python directly), I have the following error:
Traceback (most recent call last):
  File "/Users/nzylber1/git/ww_training/prepare.py", line 197, in <module>
    model_dir = train(train_set)
  File "/Users/nzylber1/git/ww_training/prepare.py", line 134, in train
    trainer.train(training_data)
  File "/Users/nzylber1/anaconda/envs/rasa/lib/python2.7/site-packages/rasa_nlu/model.py", line 157, in train
    updates = component.train(*args)
  File "/Users/nzylber1/anaconda/envs/rasa/lib/python2.7/site-packages/rasa_nlu/extractors/crf_entity_extractor.py", line 78, in train
    dataset = [self._from_json_to_crf(q, spacy_nlp) for q in train_data]
  File "/Users/nzylber1/anaconda/envs/rasa/lib/python2.7/site-packages/rasa_nlu/extractors/crf_entity_extractor.py", line 262, in _from_json_to_crf
    doc = spacy_nlp(json_eg[0])
  File "/Users/nzylber1/anaconda/envs/rasa/lib/python2.7/site-packages/spacy/language.py", line 350, in __call__
    proc(doc)
  File "spacy/tagger.pyx", line 205, in spacy.tagger.Tagger.__call__ (spacy/tagger.cpp:6251)
  File "spacy/morphology.pyx", line 78, in spacy.morphology.Morphology.assign_tag_id (spacy/morphology.cpp:4693)
KeyError: 139255

@znat is that using the french model?

@tmbo Tes!
Le jeu. 18 mai 2017 5:03 p.m., Tom Bocklisch<EMAIL_ADDRESS>a
écrit :

@znat https://github.com/znat is that using the french model?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/golastmile/rasa_nlu/issues/376#issuecomment-302540910,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADhgKqQd5UqFx_2oK6qPCBv1KmZUm3j4ks5r7LItgaJpZM4Ncj_m
.

But you didn't modify that model right? So this seems to be more of an issue on the spacy end but it would be interesting to know which sentence it fails on.

After further investigation, it's related to the diverted way I use synonyms. Let me explain. I'm parsing search queries into what and where ("looking for a plumber in Montreal").  where could be a city, or a neighborhood. Many exists in several provinces (there are 7 "Westmount" in Canada). So the synonym value is a stringified array of all possible results. So to boot synonyms, I start the training with utterances like (those break Spacy in FR only, but are fine in EN):
 {
        "text": "I'm looking for a vehicle towing in [\"Westmount, Vaughan, ON\", \"Westmount, Edmonton, AB\", \"Westmount, West Vancouver, BC\", \"Westmount, NS\", \"Westmount, Toronto, ON\", \"Westmount, Montréal, QC\", \"Westmount, Saskatoon, SK\"]",
        "entities": [
            {
                "start": 18,
                "end": 32,
                "value": "vehicle towing",
                "entity": "what"
            },
            {
                "start": 36,
                "end": 220,
                "value": "[\"Westmount, Vaughan, ON\", \"Westmount, Edmonton, AB\", \"Westmount, West Vancouver, BC\", \"Westmount, NS\", \"Westmount, Toronto, ON\", \"Westmount, Montréal, QC\", \"Westmount, Saskatoon, SK\"]",
                "entity": "where"
            }
        ]
    },

Then I feed normal examples and map them to synonym values (which Spacy is happy about):
 {
        "text": "I'm looking for a vehicle towing in Westmount",
        "entities": [
            {
                "start": 18,
                "end": 32,
                "value": "vehicle towing",
                "entity": "what"
            },
            {
                "start": 36,
                "end": 220,
                "value": "[\"Westmount, Vaughan, ON\", \"Westmount, Edmonton, AB\", \"Westmount, West Vancouver, BC\", \"Westmount, NS\", \"Westmount, Toronto, ON\", \"Westmount, Montréal, QC\", \"Westmount, Saskatoon, SK\"]",
                "entity": "where"
            }
        ]
    },

I can't really say it's a bug then.
In the process of debugging this I realized I don't need to boot synonyms as shown above. Feeding normal examples is enough as long as I make sure every where value is trained at least once.
Accuracy looks similar but I can't measure it precisely yet because of #355
So I'm closing.

right - that makes sense - thanks for adding that to the issue for future reference. there is actually a PR open that will allow to specify all the synonyms at once - without adding examples for each of them (isn't ready to merge yet though).

Reopening because I still have the error in French. Thousands of examples work fine and then one of those fails (those are the last ones, not sure if the last printed is the one causing the error)
{'text': u'je cherche une boutiques \xe0 place longueuil', 'entities': [{'start': 15, 'end': 24, 'value': u'boutiques', 'entity': 'what'}, {'start': 27, 'end': 42, 'value': u'["Place Longueuil, Longueuil, QC"]', 'entity': 'where'}]}
{'text': u'Y a-t-il un boutiques \xe9rotiques pres de Opasquia', 'entities': [{'start': 12, 'end': 31, 'value': u'boutiques \xe9rotiques', 'entity': 'what'}, {'start': 40, 'end': 48, 'value': u'["Opasquia, ON"]', 'entity': 'where'}]}
{'text': u'je cherche un boutiques \xe9rotiques vers opasquia', 'entities': [{'start': 14, 'end': 33, 'value': u'boutiques \xe9rotiques', 'entity': 'what'}, {'start': 39, 'end': 47, 'value': u'["Opasquia, ON"]', 'entity': 'where'}]}
{'text': u'envie de magasins de gros appareils \xe9lectrom\xe9nagers a Ajax Southwest', 'entities': [{'start': 9, 'end': 51, 'value': u'magasins de gros appareils \xe9lectrom\xe9nagers', 'entity': 'what'}, {'start': 54, 'end': 68, 'value': u'["Southwest Ajax, Ajax, ON"]', 'entity': 'where'}]}
{'text': u'cherche magasins de gros appareils \xe9lectrom\xe9nagers pres de ajax southwest', 'entities': [{'start': 8, 'end': 50, 'value': u'magasins de gros appareils \xe9lectrom\xe9nagers', 'entity': 'what'}, {'start': 59, 'end': 73, 'value': u'["Southwest Ajax, Ajax, ON"]', 'entity': 'where'}]}
{'text': u'travailleurs sociaux autour de Les Basques', 'entities': [{'start': 0, 'end': 20, 'value': u'travailleurs sociaux', 'entity': 'what'}, {'start': 31, 'end': 42, 'value': u'["Les Basques, QC"]', 'entity': 'where'}]}
{'text': u'cherche des travailleurs sociaux pres de les basques', 'entities': [{'start': 12, 'end': 32, 'value': u'travailleurs sociaux', 'entity': 'what'}, {'start': 41, 'end': 52, 'value': u'["Les Basques, QC"]', 'entity': 'where'}]}
{'text': u'je cherche une massoth\xe9rapeutes vers Randolph', 'entities': [{'start': 15, 'end': 31, 'value': u'massoth\xe9rapeutes', 'entity': 'what'}, {'start': 37, 'end': 45, 'value': u'["Randolph, MB"]', 'entity': 'where'}]}
{'text': u'massoth\xe9rapeutes randolph', 'entities': [{'start': 0, 'end': 16, 'value': u'massoth\xe9rapeutes', 'entity': 'what'}, {'start': 17, 'end': 25, 'value': u'["Randolph, MB"]', 'entity': 'where'}]}
{'text': u"besoin d'une toilettage & tonte d'animaux domestiques a Lenore", 'entities': [{'start': 13, 'end': 53, 'value': u"toilettage & tonte d'animaux domestiques", 'entity': 'what'}, {'start': 56, 'end': 62, 'value': u'["Lenore, MB"]', 'entity': 'where'}]}
{'text': u"cherche une toilettage & tonte d'animaux domestiques vers lenore", 'entities': [{'start': 12, 'end': 52, 'value': u"toilettage & tonte d'animaux domestiques", 'entity': 'what'}, {'start': 58, 'end': 64, 'value': u'["Lenore, MB"]', 'entity': 'where'}]}
{'text': u'Y a-t-il un entrepreneurs en b\xe9ton pres de Saint  James Town', 'entities': [{'start': 12, 'end': 34, 'value': u'entrepreneurs en b\xe9ton', 'entity': 'what'}, {'start': 43, 'end': 60, 'value': u'["Saint  James Town, Toronto, ON"]', 'entity': 'where'}]}

Any idea what the cause could be?

What is the error?

Same as above.
Traceback (most recent call last):
  File "/Users/nzylber1/git/ww_training/trainer.py", line 214, in <module>
    model_dir = train(train_set)
  File "/Users/nzylber1/git/ww_training/trainer.py", line 143, in train
    "common_examples": [example]
  File "/Users/nzylber1/anaconda/envs/rasa/lib/python2.7/site-packages/rasa_nlu/model.py", line 159, in train
    updates = component.train(*args)
  File "/Users/nzylber1/anaconda/envs/rasa/lib/python2.7/site-packages/rasa_nlu/extractors/crf_entity_extractor.py", line 78, in train
    dataset = [self._from_json_to_crf(q, spacy_nlp) for q in train_data]
  File "/Users/nzylber1/anaconda/envs/rasa/lib/python2.7/site-packages/rasa_nlu/extractors/crf_entity_extractor.py", line 262, in _from_json_to_crf
    doc = spacy_nlp(json_eg[0])
  File "/Users/nzylber1/anaconda/envs/rasa/lib/python2.7/site-packages/spacy/language.py", line 350, in __call__
    proc(doc)
  File "spacy/tagger.pyx", line 205, in spacy.tagger.Tagger.__call__ (spacy/tagger.cpp:6251)
  File "spacy/morphology.pyx", line 78, in spacy.morphology.Morphology.assign_tag_id (spacy/morphology.cpp:4693)
KeyError: 139255

Not sure how this could related (event if it's a fixed issue) https://github.com/explosion/spaCy/issues/665

Ok, I'd suggest the following (this doesn't seem to be an issue with rasa but rather this looks like an issue with the pretrained spacy model):

wrap the line doc = spacy_nlp(json_eg[0]) in crf_entity_extractor.py, line 262 with a try & except block and log the input json_eg[0] that is causing the error.
open the python console, load the french spacy model and pass in the phrase that resulted in the exception

Can you do that, or do you need help with that?

Sure, I'll do that when I'm back to work on Tuesday. Thanks!
Le sam. 20 mai 2017 6:59 a.m., Tom Bocklisch<EMAIL_ADDRESS>a
écrit :

Ok, I'd suggest the following (this doesn't seem to be an issue with rasa
but rather this looks like an issue with the pretrained spacy model):

wrap the line doc = spacy_nlp(json_eg[0]) in crf_entity_extractor.py,
line 262 with a try & except block and log the input json_eg[0] that
is causing the error.
open the python console, load the french spacy model and pass in the
phrase that resulted in the exception

Can you do that, or do you need help with that?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/golastmile/rasa_nlu/issues/376#issuecomment-302866119,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADhgKsbpdUlruXGCShjaqBtftOA3dt3Bks5r7seLgaJpZM4Ncj_m
.

Hi @tmbo, so here is the error:
Sentence:"Y a-t-il une poissonerie proche de North East  Airdrie"
Note the 2 spaces between East and Airdrie.
It happens to any sentence where an entity has 2 spaces. Preprocessing data to remove double spaces fixes the issue, however I don't think 2 spaces should break so I'll let you decide what to do with this issue. Thanks again
    model_dir = train(train_set)
  File "/Users/nzylber1/git/ww_training/trainer.py", line 142, in train
    "common_examples": [example]
  File "/Users/nzylber1/anaconda/envs/rasa/lib/python2.7/site-packages/rasa_nlu/model.py", line 159, in train
    updates = component.train(*args)
  File "/Users/nzylber1/anaconda/envs/rasa/lib/python2.7/site-packages/rasa_nlu/extractors/crf_entity_extractor.py", line 78, in train
    dataset = [self._from_json_to_crf(q, spacy_nlp) for q in train_data]
  File "/Users/nzylber1/anaconda/envs/rasa/lib/python2.7/site-packages/rasa_nlu/extractors/crf_entity_extractor.py", line 266, in _from_json_to_crf
    print("Error:" + e)
TypeError: coercing to Unicode: need string or buffer, exceptions.KeyError found

Alright, I had a look at the spacing issue and there is a spacy issue that is responsible for the behaviour. https://github.com/explosion/spaCy/issues/1052
I will close this issue, as there is nothing we can do about it.

Hello,
Would it be possible to add to documentation how to change langage (to french) with the docker container ?
Thanks,


build: Use exported targets for libjpeg-turbo and bump min to 2.1

libjpeg-turbo has exported cmake configs since its version 2.1. Relying on this simplifies the build and allows us to completely remove the troublesome Findlibjpeg-turbo.cmake. This implies raising the floor for libjpeg-turbo support to 2.1 (the current release is 3.0) which was released in April 2021 (beta in Nov 2020).
That's cutting it a little close (we usually support dependencies going back at least 3 years at a minimum, and often significantly longer).  But since this is an optional dependency anyway and simplifies the build, I'm tempted to do so.

The solution fits my needs, but I am probably not a representative user ;-)
Alternatively, the find file could be ranamed to Findlibjpeg-turbo.cmake and provide the libjpeg-turbo::jpeg instead of defining the variables.
This way it would be transparent if the find file or the config was used.
I think, the preferred one should be the config file, but I don't know how to give it priority. Maybe the find file could start with checking for config file.

We definitely prefer config files. The Find modules only exist because dependencies didn't export cmake config files (or don't have them as far back as the oldest version we try to support).
I hadn't realized that libjpeg-turbo had finally added them (I guess a couple years ago now, I didn't think to check, it certainly didn't in 2016 when I first added support for libjpeg-turbo). I would rather switch to using it. The only controversial part is that this requires us to bump our minimum to 2.1, which is a hair under 3 years old, which is a little more recent than we usually like to support. But since it's an optional dependency anyway, I'm tempted to do it anyway.


Crosshair: use a transparent line instead of dashed line for the vertical part

Because using a dashed line obscure the wicks.
Example:

By the way from the screenshot it seems that the box width for the volume is a bit larger than the candle.
My modification (hardcoded values):
diff --git a/src/components/js/crosshair.js b/src/components/js/crosshair.js
index 551535f..261300d 100644
--- a/src/components/js/crosshair.js
+++ b/src/components/js/crosshair.js
@@ -39,8 +39,14 @@ export default class Crosshair {
             ctx.moveTo(0, this.y)
             ctx.lineTo(this.layout.width - 0.5, this.y)
         }
+        ctx.stroke()
+        ctx.restore()

         // V
+        ctx.save()
+        ctx.beginPath()
+        ctx.strokeStyle = 'rgba(255, 255, 255, 0.1)'
+        ctx.lineWidth = 10
         ctx.moveTo(this.x, 0)
         ctx.lineTo(this.x, this.layout.height)
         ctx.stroke()

I found that the misalignment between the candle and the volume bar is from the 0.5 in this line https://github.com/C451/trading-vue-js/blob/master/src/components/js/layout.js#L69
If the 0.5 is removed, the bars are aligned.

I'm afraid this is not possible: the layouts for candles and volbars are different. The same thing with tv.com :

Yeah, I have tried several method with no luck. Also I will close this issue since it does not follow tradingview design.


Problem with v0.0.1

https://github.com/AwePhD/td_baseline/tree/v0.0.1 of the TD baseline is not satisfying. Its aim is to compare the D-ReID (PSTR) with a T-ReID (CLIP) based on detections - crops are provided by a model, they are not handcrafted by a database. Namely, currently, it performs detections on each frame. Then it computes the similarities between query / gallery (in a SYSU fashion) by weighting the CLIP features from detections. We do not retrain PSTR and CLIP for the moments.
In the next version of the base line we want to have 2 ways to compute similarities:

PSTR way (D-baseline) is the reference way to have similarities. Here, we do not use the captions. We know that we should have +90mAP with this method.
TD Baseline : we generate crops by PSTR detector. Then we extract features from them using CLIP. We                             also consider the captions from the query. Here we can manipulate the balance between image and captions features.

The point of this setup is to compare the metrics to a reference. If we have a weak option 2 then it might mean that there is a big gap between the detections task and the reid with good quality crops.

The tag v0.0.2 fixes this issue. See commit message for more information.


Simpler escaping in the grammar, and fix to quoted values

In top-level strings, the only backslashes that can and should be
escaped are those preceding an interpolation. For instance, if "x"
is a node evaluating to "X":

        \${x}   -> ${x}
        \\${x}  -> \X
        \\\${x} -> \${x}
        ${x}\\  -> X\\

In quoted strings, the only backslashes that can and should be escaped
are those preceding a quote of the same type as the enclosing quotes.
For instance:

        "abc\"def"   -> abc"def
        "abc\\"      -> abc\
        "abc\\\"def" -> abc\"def
        "abc\\\'def" -> abc\\\'def

This also fixes a bug with the parsing of quoted strings (see #617).
Fixes #615
Fixes #617

Right now we don't really have a documentation on the grammar. I wonder if there should be one?

In top-level strings, the only backslashes that can and should be
escaped are those preceding an interpolation. For instance, if "x"
is a node evaluating to "X":

I annotated them, is this correct?
        \${x}   -> ${x}  # prevent interpolation resolution
        \\${x}  -> \X    # add a single backslash, resolve interpolation (x is similar to X, I didn't understand initially)
        \\\${x} -> \${x} # prevent resolution and add a backslash before the interpolation
        ${x}\\  -> X\\   # are you saying that \\ is only escaped \ before an interpolation?

In quoted strings, the only backslashes that can and should be escaped
are those preceding a quote of the same type as the enclosing quotes.
For instance:

I annotated them:
        "abc\"def"   -> abc"def    # add a quote similar to the outer quote.
        "abc\\"      -> abc\          # add a backslash at the end of the string (avoiding escaping the trailing quote)
        "abc\\\"def" -> abc\"def  # add a backslash in the middle of the string and also a double quote.
        "abc\\\'def" -> abc\\\'def  # I guess this is saying that double backslash is only a backslash if it's before a a matching quote?

One thing I am wondering about is quoted string inside nested interpolationn.
Is this possible?
'foo ${env:FOO,'X'} bar'

Do you need to use double quotes on the inner string ('X')?
What happens if you have another nesting level?

Right now we don't really have a documentation on the grammar. I wonder if there should be one?

Yes, I think we need it (can come after 2.1.0rc1 but before 2.1.0).

        \${x}   -> ${x}  # prevent interpolation resolution
        \\${x}  -> \X    # add a single backslash, resolve interpolation (x is similar to X, I didn't understand initially)
        \\\${x} -> \${x} # prevent resolution and add a backslash before the interpolation
        ${x}\\  -> X\\   # are you saying that \\ is only escaped \ before an interpolation?

Correct (including the last one -- the motivation is to avoid "escaping hell" when we start getting into quoted strings => I want to escape only the backslashes that must be escaped)

        "abc\"def"   -> abc"def    # add a quote similar to the outer quote.
        "abc\\"      -> abc\          # add a backslash at the end of the string (avoiding escaping the trailing quote)
        "abc\\\"def" -> abc\"def  # add a backslash in the middle of the string and also a double quote.
        "abc\\\'def" -> abc\\\'def  # I guess this is saying that double backslash is only a backslash if it's before a a matching quote?

All correct.

One thing I am wondering about is quoted string inside nested interpolationn.
Is this possible?
'foo ${env:FOO,'X'} bar'

Do you need to use double quotes on the inner string ('X')?
What happens if you have another nesting level?

Assuming that 'foo ${env:FOO,'X'} bar' is the list of characters in a quoted value (similar to the list of examples just above), then your expression is invalid, it should be one of:
'foo ${env:FOO,\'X\'} bar'
'foo ${env:FOO,"X"} bar'

Generally speaking, through proper escaping you should be able to go as deep as you want. The tests have one example: 'AB${test:\'CD${test:\\\'EF\\\'}GH\'}'

Yes, I think we need it (can come after 2.1.0rc1 but before 2.1.0).

Ok, noted

This approach is unconventional.
Usually escaping handled in simpler way.

Correct (including the last one -- the motivation is to avoid "escaping hell" when we start getting into quoted strings => I want to escape only the backslashes that must be escaped)

Can you show me some examples of hard cases that would happen if escaping would be handled more uniformly?
Here are some simple cases to start from:
'a' -> a
'a\\' -> a\
'\\a' -> \a # different than your proposed solution
'a\'b' -> a'b
'a"b' -> a"b
'a\"b' -> a"b # not needed, but should be harmless

# Everything above with outer double quote and inner single quote (where there is an inner quote).

Can you show me some examples of hard cases that would happen if escaping would be handled more uniformly?

#615 has an example (scenario 3, we need to use the second option instead of the first one). Copying it here:
cfg = OmegaConf.create({
  "msg": r'${identity:"The root drive is: \\\\${drive}:\\"}',
  "drive": "C",
})
print(cfg.msg)  # The root drive is: \C:\

This is because of the double un-escaping that is described in the issue. With this PR, the escaped interpolation is not un-escaped when un-escaping the quotes, so we can get away with simply \\${drive}:\\.
Initially I thought I could get rid of the double un-escaping, but I was wrong (I think). I can explain more if needed.
Another example is when we were discussing https://github.com/omry/omegaconf/pull/606#discussion_r596009899
Here's what I had ended up with in order to be able to obtain the "dynamic" DictConfig discussed there:
cfg = OmegaConf.create({
  "b":  "${oc.decode:'{foo:\"\\\\\\\\\\${a}\"}'}"
})

This gave me some headache and triggered this whole thing. This PR cuts down the number of backslashes in half.
I tend to agree with you that it's a bit unconventional, but I personally feel like the pros outweigh the cons here. It also feels natural: you only escape things that need escaping (instead of having multiple options leading to the same result).

Let's see, with the objective of getting the following in a quoted string
# before resolution
The root drive is: \${drive}:\

This seems to be enough:
# before resolution
"The root drive is: \\\${drive}:\\"

Double backslash at the trailing \ to avoid escaping the quote.
One backslash before the $ to escape the interpolation, and double backslash before that to get an a ,
In this form, any other \ is assumed to be escaping something so free \ that are not matching an escapable characters should be an error.
The above doesn't seem too bad.
Note that the double unescaping is an implementation detail.
I don't think 4 backslashes are correct before the $:
\ should match the $, and you end up with 3. two are matching together and you have another free one.
arguably it's not an error because it's escaping the "new" backslash.
Looking at the second example now.

Can you show what is the desired output for this? I want to work from there.
b: "${oc.decode:'{foo:\"\\\\\\\\\\${a}\"}'}"

With this as the target, let's see if what I expect it similar to what you had to do:
b:  "${oc.decode:{'foo:\${a}'}"

The intention I read in my comment is to get this output:
${oc.decode:{'foo:\${a}'}

The first interpolation should be resolved, so we leave it as is.
The ${a} interpolation is escaped so it should not be resolved.
When we process the outer string we will unescape the nested ${a}, so we need it double escape it.
${oc.decode:{'foo:\\${a}'}

This means that after processing the outer string, we end up with
${oc.decode:{'foo:\${a}'}

And after processing the inner string we should have
'foo:${a}'

Which seems correct to me.
I just noticed that you also used double quotes in the string while I used single quotes.
Any reason for that?

Several points below (including answers to your question):
Additional motivation
I forgot to mention another motivation for this change, which is to be more intuitive, in the sense that users wouldn't need to worry about escaping until they run into situations where they need to escape interpolations or quotes (or if they want to use special characters in unquoted strings, but that's a completely different topic).
On current master we have this potentially surprising behavior:
cfg = OmegaConf.create({
    "no_inter": "Two backslashes \\\\ and two slashes //",
    "inter":    "Two backslashes \\\\ and two slashes ${slash}${slash}",
    "slash": "/",
})
print(f"no_inter: {cfg.no_inter}")  # Two backslashes \\ and two slashes //
print(f"inter   : {cfg.inter}")     # Two backslashes \ and two slashes //  <== actually ONE backslash!!

Another similar (i.e., potentially surprising) situation occurs with quoted strings:
print("Two backslashes \\\\ and two slashes //")  # Two backslashes \\ and two slashes //

OmegaConf.clear_resolvers()
OmegaConf.register_new_resolver("print", lambda x: print(x))
cfg = OmegaConf.create({
    "x": '${print:"Two backslashes \\\\ and two slashes //"}'  # <== same quoted string as above
})
cfg.x  #  Two backslashes \ and two slashes //  <== actually ONE backslash!!

With the current PR, in both situations the extra backslash is preserved.
Quoted strings ending with a backslash
One subtle but important change to this PR is that quoted strings ending with a single \ aren't valid anymore, e.g., "C:\" is invalid. This is similar to how x = "C:\" is a SyntaxError in Python. This is a consequence of the new regex I'm using to fix #617 (and I'm not sure if there would be a way to fix #617 while still allowing such strings).
Just pointing it out to be sure you are ok with this as well.
Answers to your comments & questions

Let's see, with the objective of getting the following in a quoted string
# before resolution
The root drive is: \${drive}:\

I think this wasn't clear, the objective in this example is to write The root drive is: \C:\.
Also I believe what you wrote is how you think things should work, now how they work right now on master (just pointing it out to be sure we're on the same page).

This seems to be enough:
# before resolution
"The root drive is: \\\${drive}:\\"

I agree (that's actually how it works in this PR).

In this form, any other \ is assumed to be escaping something so free \ that are not matching an escapable characters should be an error.

Generally speaking I think enforcing \ to escape things would make things worse, for instance The path is ${drive}:\folder wouldn't be a valid config value anymore.

Note that the double unescaping is an implementation detail.

Just to be sure it's clear, it has an important role in how things currently work on master, and one objective of this PR is meant to address the issues it causes.
I'm still unsure how to solve it otherwise. I think I'll need to expand on that, but this comment is already long enough.

I don't think 4 backslashes are correct before the $:
\ should match the $, and you end up with 3. two are matching together and you have another free one.
arguably it's not an error because it's escaping the "new" backslash.

That's something we need to agree on. Personaly I think \\\\${drive} should be interpreted as "two escaped backslashes followed by a regular (non-escaped) interpolation". Similar to how print("\\\\n") in Python prints \\n.

Can you show what is the desired output for this? I want to work from there.
b: "${oc.decode:'{foo:\"\\\\\\\\\\${a}\"}'}"

Currently it behaves on master as I want it to behave, i.e. cfg.b is the DictConfig {'foo': '${a}'}

With this as the target, let's see if what I expect it similar to what you had to do:
(...)

I'm having hard time following this example, at least in part because there are things that clearly don't work (braces that don't match, decode taking as input something that looks like a dictionary while it should be a string).
Can you rewrite it in a way that's more correct, with the objective of obtaining the same DictConfig as I just mentioned for cfg.b?

Converting to draft to focus on fixing #617 as a first step.

Superseded by #695 => closing


fix(Beaker): connection to hub timing out

mrack was failing with an exception when
Beaker hub was not replying to requests for
some time. With this we accept the fact that
hub may not respond and we use previous
result and continue the wait for resource.
Signed-off-by: Tibor Dudlák<EMAIL_ADDRESS>

Let me re-base and run something.

I am ok with merging this if @dav-pascual is also in favor of that.

Fine by me as well!


RPCContext doesn't work with native-thrift

It looks like RPCContext doesn't work when native-thrift is enabled. Need to look into further. The corresponding example is: https://github.com/apache/dubbo-samples/tree/master/dubbo-samples-thrift

Because RpcContext.removeContext(); operation is done in ConsumerContextFilter

@beiwei30  native thrift don't support attachment transmission.


implementing study start and stop dates

This PR is definitely not in it's final state, but I just want to keep this thread open so you can provide feedback.
I implemented an endpoints_from_preprocessed utility function which makes 1 allocation. It would probably be faster than the current method, if not for all the logic involved in calculating the study start and stop points.
I sort of imagined this as a utility and then the main API would just do something like -
intervals = [(endpoints[i-1], endpoints[i]) for i in 2:size(endpoints, 1)]

Any thoughts on a better way of doing things?

Doing this as a PR is not the right way to do it, I think I should just do another gist on the issue.


Improve Intellisense

When Intellisense works (see #2), it's still not quite what I expect.
I have to type at least // : and press ctrl-space to see the dropdown.
It would be much nicer if the dropdown showed up as soon as I enter a : (as long as I'm in a comment).

Yeah I made it this way because currently we do not detect that we're in a comment, and we even allow emojis outside of comments. That needs to be fixed first. Otherwise you're going to get prompted whenever you use a C# ternary expression :)

I use the Chinese system, "Ctrl-space" is the input method Toggle shortcut key, shortcut key conflicts with intelligence tips.
Can I customize a shortcut?


Add possibility to upload to Harbor

doc: update Readme with the new upload to Harbor (via Harbor API)
feature: add Harbor to he UploadMojo (https://github.com/kiwigrid/helm-maven-plugin/issues/83)
feature: upload to Nexus, Harbor and Chartmuseum now support username/pwd from settings.xml file https://github.com/kiwigrid/helm-maven-plugin/issues/105

Hi! Any chance of an update here?

Closing due of age.


add eso-pic compatibility

Lists eso-pic as partially-compatible because the content of \AddToShipoutPictureBG is not always tagged as Artifact, for example when it contains an image. I'm not actually sure about this but in my mind if the content appears on every page then it doesn't make sense in the flow of the document.

eso-pic is nowadays a small wrapper round the shipout/backgroud and shipout/foreground hook. So the task imho here is to handle the tagging of these hooks. Probably suspending tagging by default plus some tools to reenable if wanted is needed here.  Something like this (needs some testing to be sure that the literals are not nested somewhere).
\DocumentMetadata
  {
    lang=en-US,
    pdfversion=2.0,
    pdfstandard=ua-2,
    testphase={phase-III,math,title,table,firstaid},
    uncompress,xmp=false
  }
\documentclass{article}
\usepackage{graphicx,lipsum}
\ExplSyntaxOn
\cs_set:Npn \__shipout_picture_overlay:n #1 {
    \__shipout_init_page_origins:
    \kern -\c__shipout_horigin_tl \scan_stop:
    \vbox_to_zero:n {
      \kern -\c__shipout_vorigin_tl \scan_stop:
      \unitlength 1pt \scan_stop:
      \hbox_set_to_wd:Nnn \l__shipout_tmp_box \c_zero_dim
        {\tagmcbegin{artifact} %with pdftex \pdf_bmc:n{Artifact}/pdf_emc: is more straightforward, but
        % with luatex we should set the attribute to avoid nested bmc.
         \SuspendTagging{shipout}\ignorespaces #1 \hss
         \ResumeTagging{shipout}\tagmcend
        }
      \box_set_ht:Nn \l__shipout_tmp_box \c_zero_dim
      \box_set_dp:Nn \l__shipout_tmp_box \c_zero_dim
      \box_use:N \l__shipout_tmp_box
      \tex_vss:D
    }
}
\ExplSyntaxOff
\begin{document}
\ExplSyntaxOn
xxx\AddToHook{shipout/background}{\put(3cm,-5cm)
   {TEXT%
    \ResumeTagging{shipout}
    \tagmcend\includegraphics{example-image-duck}
    \tagmcbegin{artifact}\SuspendTagging{shipout}}}
blub
\ExplSyntaxOff

\AddToHook{shipout/background}{\put(3cm,-5cm){MORE TEXT}}

blub

\end{document}

Guess this should get an issue with a link to  Ulrike's comments


Minor decoded text bug fix

Decoding output stream used to duplicate final output, now does not duplicate so added back the code for saving those outputs

@felixp8 Is this ready for review?


Index out of bounds exception

When trying to apply dedupe to a small dataset, there is a chance to get an index out of bounds exception if the algorithm is not able to find any blocked pairs when computing the threshold. The error happens on api.py:79 when trying to compute the recall value in case expected_dupes is empty.
To be fair, I am feeding dedupe with a test dataset (30 records, all already deduped) but I guess it could be nice not to output an "Index out of bounds" exception, but state something like "No blocks could be computed.".

Hi @AMongeEntytle, this should have gotten fixed in the last release. Can you try upgrading?

Hi @fgregg, no I didn't sorry. I will update and come back with the status.

Fixed in 1.6.1 (Error now is much more verbose). Thank you @fgregg !!


Music Editor: Scaling?

When you open the Music Editor, it takes up the entire screen.
It's a bit jarring... takes you out of the coding context.  It's good for small screens, but huge for large screens.
Small -

Large -

I wonder if we can do some better scaling or responsive UI based on screen size?  Like have a smaller field editor window for large screens, and a full-screen editor for small screens and when both treble and base lines are shown?

Let's do this beyond the release in hotfix if need be.


Script doesn't works at all

Doesn't works both on nixos (i have tried steam from nixpkgs and from flatpak and even steam from arch distrobox to test if it's related to nixos or nah) and on fedora
Game just crashes immediately after hitting the play button
I tried running wine thcrap_loader.exe confname.js game or just adding this command as non steam game both ways it works.
I'm 100% sure that this isn't the problem on my side or problem with configuration because i literally tried 6 ways to run the touhou games with this script. It just produces the same log error on every distro
The games i have tried to launch (th09, th10, th11)
Launch options: ~/.local/bin/thcrap_proton -e %command%
Launch log:
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
GameAction [AppID 1100140, ActionID 23] : LaunchApp changed task to SynchronizingCloud with ""
GameAction [AppID 1100140, ActionID 23] : LaunchApp changed task to SynchronizingControllerConfig with ""
GameAction [AppID 1100140, ActionID 23] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 1100140, ActionID 23] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 1100140, ActionID 23] : LaunchApp waiting for user response to CreatingProcess ""
GameAction [AppID 1100140, ActionID 23] : LaunchApp continues with user response "CreatingProcess"
/bin/sh\0-c\0~/.local/bin/thcrap.sh -e /home/ashuramaru/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=1100140 -- /home/ashuramaru/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/app/share/steam/compatibilitytools.d/Proton-Exp'/proton waitforexitandrun  '/media/games/SteamLibrary/steamapps/common/th10/th10.exe'\0
Game process added : AppID 1100140 "~/.local/bin/thcrap.sh -e /home/ashuramaru/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=1100140 -- /home/ashuramaru/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/app/share/steam/compatibilitytools.d/Proton-Exp'/proton waitforexitandrun  '/media/games/SteamLibrary/steamapps/common/th10/th10.exe'", ProcID 4476, IP <IP_ADDRESS>:0
chdir /media/games/SteamLibrary/steamapps/common/th10
ERROR: ld.so: object '/home/ashuramaru/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/ashuramaru/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
pid 4478 != 4476, skipping destruction (fork without exec?)
ERROR: ld.so: object '/home/ashuramaru/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
pid 4477 != 4476, skipping destruction (fork without exec?)
--------------------GENERATED COMMAND--------------------
/home/ashuramaru/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/reaper
---------------------------------------------------------
ERROR: ld.so: object '/home/ashuramaru/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/ashuramaru/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
reaper: no sub-command!
Game process removed: AppID 1100140 "~/.local/bin/thcrap.sh -e /home/ashuramaru/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=1100140 -- /home/ashuramaru/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- '/app/share/steam/compatibilitytools.d/Proton-Exp'/proton waitforexitandrun  '/media/games/SteamLibrary/steamapps/common/th10/th10.exe'", ProcID 4476
Uploaded AppInterfaceStats to Steam
GameAction [AppID 1100140, ActionID 23] : LaunchApp changed task to WaitingGameWindow with ""
GameAction [AppID 1100140, ActionID 23] : LaunchApp changed task to Completed with ""

Be sure to add double quotes around "%command%" in the launch options.

OMG it works!!! I thought those double quotes were unnecessary.
Is there anyway to change the script to actually make it work without those double quotes?
Because it confused me and probably confused a lot of other people who weren't aware that they are necessary


[DOCFIX] Correct wrong code example

@calvinjia PTAL

LGTM

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8598/
Test FAILed.


feat(dashboard): Dashboard metadata models

RFC for this change: https://github.com/linkedin/datahub/pull/1778
Checklist

[X] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[X] Docs related to the changes have been added/updated (if applicable)

For a big feature like this, it might be a good idea to start using RFC to understand, at least, what aspects should be included for dashboard entity.

+1 to RFC - I'm not close enough to the code to comment on the implementation, but glad to contribute feedback on use cases, user stories, impact, etc.
From what I can tell, this captures the vast majority of the entities & use cases we discussed on 7/22/20; thanks for your quick and thorough work on this, @keremsahin1!

For a big feature like this, it might be a good idea to start using RFC to understand, at least, what aspects should be included for dashboard entity.

Created RFC: https://github.com/linkedin/datahub/pull/1778
Please review.

+1 to RFC - I'm not close enough to the code to comment on the implementation, but glad to contribute feedback on use cases, user stories, impact, etc.
From what I can tell, this captures the vast majority of the entities & use cases we discussed on 7/22/20; thanks for your quick and thorough work on this, @keremsahin1!

Thanks @maggiehays . Created RFC: https://github.com/linkedin/datahub/pull/1778
Please review.


SAA-996: Multi-week schedule updates

Codecov Report
Patch coverage: 86.27% and project coverage change: +0.10 :tada:

Comparison is base (1e805b2) 84.86% compared to head (a1d4018) 84.97%.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #472      +/-   ##
============================================
+ Coverage     84.86%   84.97%   +0.10%
+ Complexity     2246     2239       -7
============================================
  Files           290      290
  Lines          8352     8319      -33
  Branches        506      504       -2
============================================
- Hits           7088     7069      -19
+ Misses         1011      997      -14
  Partials        253      253

Impacted Files
Coverage Δ

...activitiesmanagementapi/entity/ActivitySchedule.kt
95.20% <83.33%> (+0.38%)
:arrow_up:

...activitiesmanagementapi/service/ActivityService.kt
74.60% <84.61%> (+0.53%)
:arrow_up:

...vitiesmanagementapi/service/PrisonRegimeService.kt
88.00% <100.00%> (+1.63%)
:arrow_up:

... and 2 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Statistics for session pools

This should all be trivial.
The SessionPoolTest.cs is just an empty partial class for the moment, to allow grouping. It will be populated eventually :)

As you said this one was trivial :), specially compared with the others!


class_cast_exception raised when sorting by unnest-ed object column

CrateDB version: 4.1.6
Steps to reproduce:
create table test (a string, b string, c array(object as (d string, e string)));
>> Table TEST created.
insert into test (a, b, c) values ('x', 'y', [ { d = '1', e = '2' }, { d = '3', e = '4' } ]);
>> 1 row inserted.
select a, b, unnest(c['d']), unnest(c['e']) from test order by 1,3;
ERROR: NotSerializableExceptionWrapper: class_cast_exception: class io.crate.expression.tablefunctions.ColumnOrientedRowsIterator cannot be cast to class java.lang.String (io.crate.expression.tablefunctions.ColumnOrientedRowsIterator is in unnamed module of loader 'app'; java.lang.String is in module java.base of loader 'bootstrap')

Thank you for the bug report.
This is already fixed in master and a workaround would be to wrap the unnest parts into a sub-query and apply the ORDER BY outside of it:
select * from (select a, b, unnest(c['d']), unnest(c['e']) from test) t order by 1, 3

We'll have a look at backporting the fix for the upcoming 4.1.7

Should be fixed via https://github.com/crate/crate/pull/10127


Failed transactions messages

Problem
We started posting events on failed transaction https://github.com/artsy/exchange/pull/233, we need to post slack messages for these events.
Solution
Update existing commerce slack view to also handle transaction.failed routing keys.

going to merge this PR and will address any suggestions in follow up so i can test on staging.


Add active owned projects

Is your feature request related to a problem? Please describe.
I would like to see a section full of active work being done.
Describe the solution you'd like
New section detailing OSS projects I created and maintain.
Describe alternatives you've considered
Nothing.  Do not show off?
Additional context

Immediately relevant projects include dotfiles, dotcom, and Microsoft Graveyard

Closed by #126


PostgreSQL 9.4: ERROR: column t.reltoastidxid does not exist

Various operations (most notably EvmDatabase.seed) fail on postgres 9.4 because there is no longer a pg_class.reltoastidxid in 9.4.
[----] E, [2015-02-09T13:47:29.364467 #11639:3fbda1b59e94] ERROR -- : MIQ(abstract_adapter) Name: [Text Table Indexes], Message: [PGError: ERROR:  column t.reltoastidxid does not exist
LINE 7:              AND i.oid = t.reltoastidxid
                                 ^
:            SELECT distinct i.relname, d.indisunique, d.indkey, i.oid
           FROM pg_class t
           INNER JOIN pg_index d ON t.oid = d.indrelid
           INNER JOIN pg_class i ON d.indexrelid = i.oid
           WHERE i.relkind = 'i'
             AND t.relkind = 't'
             AND i.oid = t.reltoastidxid
             AND t.relname = 'pg_toast_85302'
             AND i.relnamespace IN (SELECT oid FROM pg_namespace WHERE nspname = 'pg_toast' )
          ORDER BY i.relname
]

Used in vmdb/tools/dba.rb:
374:                      WHERE oid = (SELECT reltoastidxid FROM pg_class

and in vmdb/lib/extensions/ar_adapter/ar_dba/postgresql.rb:
668:             AND i.oid = t.reltoastidxid

Relevant postgres patch<EMAIL_ADDRESS>

hmmm...I wonder if we will need to make this version specific.  cc @tenderlove @jrafanie .  This is some of that code that we want to move into a gem (or merge into that pg stat/diagnostic gem).

10:46:27 ~/Code/manageiq/vmdb (master) (2.1.5) + git grep -n reltoastidxid
lib/extensions/ar_adapter/ar_dba/postgresql.rb:668:             AND i.oid = t.reltoastidxid
tools/dba.rb:374:                      WHERE oid = (SELECT reltoastidxid FROM pg_class

Yeah, toast tables, while useful, probably shouldn't break in this way.  The stat/diagnostic gem should be safer to run.  I'm not quite sure what this code is doing other than it's trying to get toast table information as part of the db diagnostics part of the UI.

The existing stat/diagnostic gem (I can't find it right now) doesn't do this...we were thinking of moving this code into that gem somehow.  Yes, this code get the toast tables for stat/diagnostic purposes.


feat: log timing and attempt details

This commit adds additional fields to the access and error log to aid with troubleshooting performance issues and better understanding of the time spent in the system.
Access log fields:

failed_attempts: number of attempts that failed
failed_attempts_time: time spent on attempts that failed
dns_time: time spent looking up DNS records
dial_time: time spent dialing the network connection
tls_time: time spent performing the TLS handshake
backend_time: time spent waiting for the backend to respond

Error log fields:

backend-time: time spent waiting for the backend to respond

Resolves: cloudfoundry/routing-release#304

[X] I have viewed signed and have submitted the Contributor License Agreement
[X] I have made this pull request to the main branch
[X] I have run all the unit tests using scripts/run-unit-tests-in-docker from routing-release.Summarizing 1 Failure:
[FAIL] Router Integration prometheus metrics [It] starts a prometheus https server
/routing-release/src/code.cloudfoundry.org/gorouter/integration/main_test.go:732

It seems like the prometheus setup is not working in the docker container, but this change is unrelated to prometheus.
[ ] (Optional) I have run Routing Acceptance Tests and Routing Smoke Tests on bosh lite
[ ] (Optional) I have run CF Acceptance Tests on bosh lite

Before merging I will squash the commits and adapt the commit message accordingly.


How to get WindowChrome

Hi guys,
I want to manipulate some property inside WindowChrome, but whenever I tried to get the value from my Window I always got null, below is the snippet:
void WindowBase_Loaded(object sender, RoutedEventArgs e)
{
      var chrome = WindowChrome.GetWindowChrome(this);
}

Is there anything wrong in my code?

Is your window derived from MetroWindow? The WindowChrome property is initialized by BorderlessWindowBehavior, which is set in MetroWindow's style.

@myrnazhou any news here?

Thanks @thoemmi,  yes it's derived from MetroWindow, I think the problem is because WindowChrome class is defined inside mahapps solution not the one from Windows.Shell.WindowChrome, so I still can't get it.

@myrnazhou you should use the Microsoft.Windows.Shell.WindowChrome namespace
void MainWindow_Loaded(object sender, RoutedEventArgs e)
{
    var chrome = Microsoft.Windows.Shell.WindowChrome.GetWindowChrome(this);

    // or

    var chrome = this.GetValue(Microsoft.Windows.Shell.WindowChrome.WindowChromeProperty);
}

I've tried that as well, I got 'WindowChrome' is inaccessible due to its protection level. Then I tried to use Microsoft.Windows.Shell from the nuget, but then it's different type than the one that is added from BorderlessWindowBehavior, so it returns null.

I can't reproduce your issue. WindowChrome is a public type.
I just added this working code to the c'tor of MainWindow in MetroDemo:
Loaded += (sender, args) => {
    var chrome = WindowChrome.GetWindowChrome(this);
};

and it works:

I think that's the problem, I can get the object when using the demo but not when in my own project. I added MahApps from nuget.

Maybe you're using an additional NuGet package coming with its own copy of Microsoft.Windows.Shell?

Yes I've mentioned it in my prev comment, I'm using Microsoft.Windows.Shell from nuget, since it won't compile without it. With just including MahApps, I got 'WindowChrome' is inaccessible due to its protection level.

Sorry, I didn't notice you rcomment. In fact, WindowChrome was internal, but was changed to public with commit 82aca23c.
Can you please try the latest pre-release?

Ah ok, thanks, it works now. Never realized there was pre-release build. :)


Pasting in a PIN should move focus to the last digit

Right now pasting PINs works but, for example, pasting a four digit PIN into the first text input of a four digit input results in the second digit's input being focused. Ideally focus would move to the first empty input after the pasted content, or if all the inputs are filled out, the last one.

i know this is three years later, but i updated the component to work this way (focus moves to the first empty input after the pasted content, or if all the inputs are filled out, the last one) on paste. i also published it to npm as @acusti/react-code-input if you want to try it out (npm i @acusti/react-code-input or yarn add @acusti/react-code-input).


Log snapshot cache entry age in ObtainSnapshot telemetry

Fixes: https://github.com/microsoft/FluidFramework/issues/7967
This logs the age of the snapshot cached entry which is fetched from cache in fetch snapshot sequence.
This will help hosts to see effectiveness of caching, and also using other data (how many ops were on top of such snapshot) to figure out effective caching duration.

Ping


WIP on retrospective fits for gbq_no_level model

This is code to produce retrospective fits for gbq_qr_no_level. Evidence that it works:

files in retrospective-hub
here's a plot of the predictions

for reference, here's a plot of the predictions for the same time frame that were produced in real time for gbq_qr, expected to be qualitatively similar but not identical:

R code for plots, not committed:
library(hubVis)
library(dplyr)
library(purrr)

files <- Sys.glob("retrospective-hub/model-output/UMass-gbq_qr_no_level/*.csv")

forecast <- purrr::map_dfr(files, read.csv) |>
    dplyr::mutate(model_id = "UMass-gbq_qr_no_level")

target_data <- read.csv("data-raw/influenza-hhs/hhs-2024-03-27.csv") |>
    dplyr::mutate(observation = inc)

plot_step_ahead_model_output(
    forecast,
    target_data |> dplyr::filter(date >= "2023-10-01", date <= "2024-01-01"),
    x_col_name = "target_end_date",
    x_target_col_name = "date",
    intervals = 0.95,
    facet = "location",
    facet_scales = "free_y",
    facet_nrow = 15,
    use_median_as_point = TRUE,
    interactive = FALSE,
    show_plot = TRUE,
    group = "reference_date"
)

files <- gsub("_no_level", "", files)
files <- gsub("retrospective", "submissions", files)

forecast <- purrr::map_dfr(files, read.csv) |>
    dplyr::mutate(model_id = "UMass-gbq_qr")

plot_step_ahead_model_output(
    forecast,
    target_data |> dplyr::filter(date >= "2023-10-01", date <= "2024-01-01"),
    x_col_name = "target_end_date",
    x_target_col_name = "date",
    intervals = 0.95,
    facet = "location",
    facet_scales = "free_y",
    facet_nrow = 15,
    use_median_as_point = TRUE,
    interactive = FALSE,
    show_plot = TRUE,
    group = "reference_date"
)

Updated PR coming tonight or tomorrow.  Here's more evidence that the fits have expected behavior, reproducing the gbq_qr_no_level fit from 2023-12-30, a reference date for which correct fits for that model were produced in real time.  Plot compares UMass-gbq_qr and UMass-gbq_qr_no_level.  Note locations like 4, 6, 18, 22, 32, 48, and US, where there is some divergence between predictions from the two models, with gbq_qr_no_level continuing recent trends more than gbq_qr.

This matches the behavior seen in the plots of those predictions that were produced in real time:


Test mode: Validate test case data on clicking OK

When the test case data is saved, it needs to be validated to see if its compatible with the current source output schema.
The sources can be edited and schema changed later, and that looks OK because validation will be also happening at runtime.

Assigning this to myself as well since the need to work on the UI side of things.

Rasied PR https://github.com/hortonworks/streamline/pull/926


[SB] Add await to async call

/azp run python - servicebus - tests

API change check
API changes are not detected in this pull request.


The is-module dep looks pretty dead

I notice that rollup-plugin-node-resolve depends on is-module, but that is-module's homepage on npmjs.com leads to a 404 on github.
Wouldn't there be a more viable dep somewhere?

I would like to challenge your statement: its homepage-typed-by-url seems to work fine: https://www.npmjs.com/package/is-module, its homepage key in package.json is https://github.com/component/is-module and its downloads seem growing and healthy: https://npmcharts.com/compare/is-module
Please confirm you still want to keep this issue open.

Well, last commit from three years ago isn't very live, but the author answered to my request to tag a release there pretty fast, so indeed I think it's ok to close.


Decompose _setup_schema_elements_of_kind

This PR intends to decompose _setup_schema_elements_of_kind into smaller functions. In a future PR I will decompose _get_element_properties into two functions: one addressing non-link properties and another addressing link-properties.

Coverage increased (+0.007%) to 93.619% when pulling 970142ce9fdff6f64237a77bed707d92585b3711 on decompose-setup-schema-elements-of-kind into 01e271623cb75552041635354eaddd19f485d753 on refactor-schema-graph.


Better descriptions for configuration settings in docs

From a number of discussions and opened issues, it's become obvious that some of the configuration settings purpose wasn't clear.
I've updated the descriptions to be a little more clear on both the purpose of the settings as well as how they affect licensed at runtime.

Going to merge this to get it into the release, 👍 to continue iterating on the docs and examples if there are things that could be improved or changed.


Celsius to Fahrenheit

Title of article
Write a C++ program to convert the temperature from Celsius to Fahrenheit.
Additional information
Input ( C )  : -40
Output ( F ) : -40

Code of Conduct

[X] I have read and agree to the Codinasion project's Code of Conduct

Hello, could I please be assigned this issue?

Hey @AlfredoR-CSUF
Thanks for showing your interest in this open source project.
But a PR has already been raised for this issue #475
Could you please work on other issue


PTYHON-4287: Multi index support

Support multiple index creation for our AI-ML testing pipeline

There are no tests for this feature. We need tests of the testing framework itself.

I agree here. I'm thinking we should make this a separate task seeing as there's quite a bit that would need tests.


Fix new_fulltext() ignoring the version parameter.

The new_fulltext() method was not using the since= query string when calling the Zotero API. Thus the version specified by the caller was always ignored.
This PR also renames the version parameter to since. The latter seems more consistent with other Pyzotero method parameters, and with the Zotero API. The Pyzotero docs also mention since, not version, although no one using positional parameters would notice.

Coverage increased (+0.05%) to 47.368% when pulling fdc517f88cff817ea4c702ea70c34377a61cccba on davidlesieur:new-fulltext-since into 3a07628d8b3e665f8274c1b62e26d7e53679519f on urschrei:dev.

Oh, hmm I wonder why I had originally set it as a header and not part of the query string. Thanks for this – I'll review and merge it tomorrow and push out a point release.


KEA for DHCPv6

Thanks for the IPv4 Integration of KEA DHCP.
For dual Stack Operation it's neccesary to have a DHCP for IPv4 and IPv6.
Could you please integrate KEA for DHCPv6 for the replacement of ISC DHCPv6?
Thanks
bueste

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue
Describe the bug
Feautre Request:
For dual Stack Operation it's neccesary to have a DHCP for IPv4 and IPv6.
Could you please integrate KEA for DHCPv6 for the replacement of ISC DHCPv6?
To Reproduce
Expected behavior
Describe alternatives you considered
Screenshots
Relevant log files
Additional context
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 24.1.r1 (amd64).


c# and  c++/clI System.BadImageFormatException:

c#  invokes c++/cli and shows that
System.BadImageFormatException:
“Could not load file or assembly 'xxxxx, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.

Without more information to help me debug the problem, I'm at a dead end :C

In Addition to this issue.
I have got the same issue when i was having the  .dll and .lib both  the reference in my CLI .netcore project.
but when i have referenced only  static lib .lib of native c++ , i was not the issue.
please help me proceed further.


Figure out if we still need to shim MessageChannel

We have a few places where we've shimmed MessageChannel, because it was so new when we started using it: https://github.com/mozilla/brackets/blob/master/src/main.js#L117 for example.
We should see if it's still necessary.  Firefox 41 started shipping it by default, for example.

http://caniuse.com/#search=messagechannel seems to think that we can remove this now.


Cannot see min required channel size

Trying to open a lightning channel with v0.1.6-7 but it fails due to low channel balance. Problem is the error is so small that minimum channel size doesn't fit and isn't visible, so I can't tell how large channel I should create :|

Is it fixed in the new version?